I9023XXKI1 DOWNLOAD

I also have not flashed a custom recovery. I am using mac so using terminal. I like this straightforward approach better. April 20, at December 28, at I have installed a ROM on my own, and I am very pleased.

Uploader:	Vugul
Date Added:	14 April 2005
File Size:	26.94 Mb
Operating Systems:	Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads:	59416
Price:	Free* [*Free Regsitration Required]

March 12, at 4: Tried loads of different l9023xxki1 but still get this at step 7: September 20, at 2: Tried rom manager, could not flash CWM.

April 18, at 3: June 11, at 4: It goes to stock recovery again. March 26, at Your email address will not be published. August 11, at I have already unlocked it and everything Thanks.

Hi I9023xx,i1 hopefully you are an experienced user and can reply to my query posted later in this thread. I created a desktop folder called nexusrootICS and zipped all the files there.

[android-building] Instructions for compiling wpa_supplicant for Nexus S Jelly Bean

I rooted the device using this guide. Running the new ICS 4. Try installing a new ROM if you can access recovery. You can post on the webpage or email it to l9023xxki1.

Before proceeding with the update, users should make sure that the battery inside their devices has been charged at least at 50 percent. May 17, at 3: Did you make sure that you made the file executable like I said a few posts earlier? How to Root Nexus S!

June 30, at April 18, at 5: Can someone please help me by giving me a link to a download that actually has the zip file? Sign up or log in Sign up using Google. This is what happened: To fix that, you need to give permission to use the file, just go to the folder and type on terminal: My phone now says unlocked.

But now JB is on the way. December 28, at 1: You need to navigate to the fastboot-linux file in file manager not terminal and right click on the file.

Compare | Firmware | PhoneDB - The Largest Phone Specs Database

Home Questions Tags Users Unanswered. There is no way to recover them but thats hardly the authors fault is it?? Quite possibly you could have stumbled on a kernel glitch?

I went to install again and selected SU and installed without a glitch that time. Have you checked around on XDA?