Hi guys, i tried to install that ROM
( http://forum.xda-developers.com/showthread.php?t=1396224 )
on my Nexus S i9020 with cwm.
Now when i try to turn on the phone i can only see the starting animation in loop, or, if i turn on my device in fastboot mode, i can't access the recovery mode, 'cause when i click it i can see the green droid for about 1 sec, but after that only a black screen XD
Before trying to install ICS i had Cyanogen mod 7, then i flashed the stock rom, and then i tried to install ICS
Does anyone know how can i go back to my previous ROM? thanks
Did you try flash this by installing the zip file or did you extract it to your sd card and use backup and restore?
Hmm, it says in the thread title that the nandroid backup is from I9023, not I9020.
If you can still access the fastboot mode then it's supposed to be easy. Just flash CWM recovery again and then use it to flash any custom ROM you want. Also wipe cache and dalvik-cache just in case.
Bryo92 said:
Hi guys, i tried to install that ROM
( http://forum.xda-developers.com/showthread.php?t=1396224 )
on my Nexus S i9020 with cwm.
Now when i try to turn on the phone i can only see the starting animation in loop, or, if i turn on my device in fastboot mode, i can't access the recovery mode, 'cause when i click it i can see the green droid for about 1 sec, but after that only a black screen XD
Before trying to install ICS i had Cyanogen mod 7, then i flashed the stock rom, and then i tried to install ICS
Does anyone know how can i go back to my previous ROM? thanks
Click to expand...
Click to collapse
you need to reflash your recovery(cwm or twrp) via fastboot then restore the nandroid backup that you made(you made a nandroid backup, right?) if no nandroid backup was made, flash a rom that you know will boot. you did realize that you restored a nandroid backup from a 9023 when you have a 9020? and it said tested on a 9023. anyways, you shouldnt restore other peoples nandroid backups, you should flash your roms. by restoring other peoples roms, you pickup other peoples issues as well.
Hi guys, I'm facing the same problem as the thread starter here. Using I9023. I still can load the fastboot mode but how do I reflash CWM in fastboot mode?
Sorry if this seems like a noob question. Thanks a lot!
thanks everyone, i solved it downloading the cwm img from the cwm's site, flashing it with fastboot and then restoring my backup
Hi Bryo92, may I know how you flash it using fastboot?
aaron.ng91 said:
Hi Bryo92, may I know how you flash it using fastboot?
Click to expand...
Click to collapse
fastboot flash recovery your-recovery-file.img
Hi suksit, I have installed the SDK, and placed the CWM recovery file image in the same folder as the fastboot executable. i tried the below command line on terminal but it says no such command is found.
i didn't placed the CWM recovery file image in the same directory as the fastboot.exe; i placed it in my desktop and then i wrote in the command prompt
"cd C:\path\to\fastboot.exe\"
and then
" fastboot flash recovery C:\path\to\desktop\recovery.img "
aaron.ng91 said:
Hi suksit, I have installed the SDK, and placed the CWM recovery file image in the same folder as the fastboot executable. i tried the below command line on terminal but it says no such command is found.
Click to expand...
Click to collapse
You're in the wrong directory.
If you're using Windows 7, press Shift + Right click on the folder which contains fastboot.exe and CWM recovery image, select "Open command window here", then type the command.
Or you could do what Bryo92 suggested, use the command cd directory-that-contains-fastboot first, then type the command.
Related
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
SounderBruce said:
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
Click to expand...
Click to collapse
Ok! first download : http://www.4shared.com/zip/XG506hyV/icsroot-fastboot-recovey.html
just unpack, connect your device and click run.bat.....Good luck!
I ran the .bat, but I get an error saying "Device already rooted", but it is still not recognized as rooted by SuperUser.
Alternatively, is it possible to completely wipe the phone of everything (including root) so I can start over with a fresh phone?
Of course you can, and might be the best idea if you don't mind doing it.
Make sure you have the latest CWM recovery on your phone, download the FULL ROM from this thread (i'm not american so i don't know exactly, but from what i know yours is the I9020T, so get that ROM) and copy it to the SDCard. Now go into recovery, wipe system/data and dalvik cache, then flash the ROM.
Do make sure you have the right ROM though. This will get you 100% fresh and untouched 4.0.3. You can probably clear out any non-personal folders on the sdcard too, but that shouldn't do any harm anyway.
After this, use the attached file from this thread to root, and feel free to update root/superuser.
Actually, that's what I did...I can't use CWM recovery because its displaying an error of no root. So how do I wipe this or fix CWM?
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Harbb said:
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Click to expand...
Click to collapse
My bootloader is apparently unlocked and I'm trying to flash through fastboot.
Are you sure the following is satisfied:
-open padlock and google logo on boot
-fastboot (on phone) says "bootloader status: unlocked" or something of the like
-you are using: "fastboot flash recovery "C:\path\to\recovery.img""
-you are using the above command while connected to the PC via USB (with working drivers) and that you are in fastboot mode on the phone (turn off phone --> hold Vol. Up then hold Power TOGETHER for about 2 seconds, should give you reboot and recovery options)
It is necessary to be in the bootloader/fastboot interface on the phone when you run the command. Hopefully it was something simple that i said above, otherwise i'm completely lost.
1. Yes
2. Yes
3. I didn't use that method to root...
4. I'll try that.
3 is just flashing recovery, that is the code u type into cmd/terminal to reflash the recovery img. It isn't rooting the phone. 4 is how to get into the mode on the phone to use the command.
Its a bit confusing at first but makes much more sense once you do it one or two times.
Where do I go to get the recovery image?
The latest ClockWorkMod Recovery can be found on this page. Just scroll down to Nexus S and download 5.0.2.0 crespo .img. Then just direct fastboot to the folder you have it saved in while using the "fastboot flash recovery C:\path\to\recovery.img" command.
Ok. I've tried this, but in command prompt, I get the following error:
C:\Users\Bruce>fastboot flash recovery C:\Users\Bruce\Downloads\recovery.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Check out this rooting guide, however only go up to step 5 (and do NOT type "fastboot oem unlock", do everything up until that point). This will setup fastboot for you, and setup drivers for your computer. Once this is done, do what you did above and it should work successfully.
Remember to cd (change directory) in cmd to where you unzipped that folder.
There isn't a link...
Sorry, stuffed that up. I fixed the link in my previous post pointing to NexusSHacks - How to Root Nexus S.
It's worked, but when I try to go to the recovery menu, the Google/unlocked padlock screen freezes or it displays an Android with its chest compartment open and a red triangular ! symbol.
I just had a really long reply and managed to lose it by closing the page..
That's the stock bootloader you see there, it probably didnt flash or you rebooted your phone. And make sure that you are flashing the latest CWM you downloaded before.
I flashed the latest CWM, but when I try to go to recovery, my phone freezes at the Google logo with the unlocked padlock.
Have you tried flashing it again, or maybe redownloading the file? And of course making sure it is the NEXUS S version which you are downloading.
Alternatively, try just "fastboot boot recovery.img", replacing recovery.img with the full name and path of cwm.
edit: btw, i'll be gone for an hour or two Bruce so i can answer any more questions/issues when i get back
please dont shout, just take pitty on me.
I have been getting into the world of rooting and have used the HTC Bootloader unlock, and have installed clockwork. i then had a few issues but managed to get some roms working but Im still not fully understanding exactly what im doing.
but i can flash by:
1. Power on'ing and vol down,
2. fastboot - bootloader - loading PG58IMG
3. recovery -wipe data/factory reset - yes
4. install zip from sdcard - chose zip from sdcard - Sensation_3.32.401.5_deodexed - Yes
5. wait for: install from sdcard complete
7. go back - rebootsystem now
Ive tried a few roms, 2 didnt work but this is the 3rd (Sensation_3.32.401.5_deodexed) that has loaded up.
My issue is I dont get how to get my wireless to work. If someone could give simple instructions Id be more than helpfl as all guides i read are too full of jargon. . . . .im not afraid to hit your thanks buttons . . .
Thanks
Tim
PS
my cid is VADAP001
my MID is PG5813000
taffytim said:
please dont shout, just take pitty on me.
I have been getting intot he world of routing and have used the HTC Bootloader unlock, and have installed clockwork. i then had a few issues but managed to get some roms working but Im still not flly understanding exactly what im doing.
but i can flashing by
1. Power on'ing and vol down,
2. fastboot - bootloader - loading PG58IMG
3. recovery -wipe data/factory reset - yes
4. install zip from sdcard - chose zip from sdcard - Sensation_3.32.401.5_deodexed - Yes
5. wait for: install from sdcard complete
7. go back - rebootsystem now
Ive tried a few roms, 2 didnt work but this is the 3rd (Sensation_3.32.401.5_deodexed) that has loaded up.
My issue is I dont get how to get my wireless to work. If someone could give simple instructions Id be more than helpfl as all guides i read are too full of jargon. . . . .im not afraid to hit your thanks buttons . . .
Thanks
Tim
Click to expand...
Click to collapse
Hi,
Are you talking about wifi?
Have you got a router?
When you use HTC Dev to unlocj your bootloader it does unlock the Recovery, System, and Boot partitions to allow your device to write to those partitions and not just read rose partitions. But Terri is a catch, if you want to flash a custom recovery you have to use ABD fastoot commands to flash it. When you flash as ROM in a .zip file via Recovery, it only flashes the System partition. You then have to open the dot zip file and extract the boot.img and then use ADB fastboot commands to flash the boot.img to your boot partition. If you do not you will still have the boot.img of the ROM you was using before you flashed te New ROM.
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just watt te name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of eat is called a Lenox kernel. This means that your bootloader boots the Lenox kernel and the hardware of the device. The Lenox kernel then boots the Android OS. The kernel is also te connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on te system partition you will have troubles like WiFi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for te ROM are you will more than likely have troubles.
Malybru, i do have a router but my wifi wont turn on so i cant connect to it.
T-Macgnolia said:
When you use HTC Dev to unlocj your bootloader it does unlock the Recovery, System, and Boot partitions to allow your device to write to those partitions and not just read rose partitions. But Terri is a catch, if you want to flash a custom recovery you have to use ABD fastoot commands to flash it. When you flash as ROM in a .zip file via Recovery, it only flashes the System partition. You then have to open the dot zip file and extract the boot.img and then use ADB fastboot commands to flash the boot.img to your boot partition. If you do not you will still have the boot.img of the ROM you was using before you flashed te New ROM.
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just watt te name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of eat is called a Lenox kernel. This means that your bootloader boots the Lenox kernel and the hardware of the device. The Lenox kernel then boots the Android OS. The kernel is also te connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on te system partition you will have troubles like WiFi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for te ROM are you will more than likely have troubles.
Click to expand...
Click to collapse
That is very informative thanks T-Macgnolia. I understand the theorybut i cant work out the process?
How do i get to flash the boot image?
If i go into my rom folder on my pc then try to open the boot file i just get a Windows Disc Image Burner message box asking me to burn to disc.
I used to burn images using virtal drives when making dvds. Will i need to do the same again here with a virtual drive?
Can you break the process down for me?
taffytim said:
That is very informative thanks T-Macgnolia. I understand the theorybut i cant work out the process?
How do i get to flash the boot image?
If i go into my rom folder on my pc then try to open the boot file i just get a Windows Disc Image Burner message box asking me to burn to disc.
I used to burn images using virtal drives when making dvds. Will i need to do the same again here with a virtual drive?
Can you break the process down for me?
Click to expand...
Click to collapse
First you have to download and install the Android SDK. Here is a video by Elite Recognized Developer Adam Outler that shows you how to install the Android SDK. After you have the SDK installed and all the packages are downloaded and installed. Take the boot.img and copy it to the same folder in ADB that has fastboot in it. Now while you are in the folder with fastboot in it hold down the shift key and right click anywhere on the screen and select "open command promt here". This will open a command promt with you already on the right directory. Now boot your Sensation into Hboot by holding the volume down button down while booting your Sensation. when in Hboot select fastboot and connect your Sensation to your computer with your USB cable. Now type the following into the command promt.
Code:
fastboot flash boot boot.img
That is all it is to it. Also the boot.img is a iso file that is why you get that message when you try to open it. You have to use a Android kitchen or another program that can decompile the file if you want to open it and look around.
T-Macgnolia said:
First you have to download and install the Android SDK. Here is a video by Elite Recognized Developer Adam Outler that shows you how to install the Android SDK. After you have the SDK installed and all the packages are downloaded and installed. Take the boot.img and copy it to the same folder in ADB that has fastboot in it. Now while you are in the folder with fastboot in it hold down the shift key and right click anywhere on the screen and select "open command promt here". This will open a command promt with you already on the right directory. Now boot your Sensation into Hboot by holding the volume down button down while booting your Sensation. when in Hboot select fastboot and connect your Sensation to your computer with your USB cable. Now type the following into the command promt.
Code:
fastboot flash boot boot.img
That is all it is to it. Also the boot.img is a iso file that is why you get that message when you try to open it. You have to use a Android kitchen or another program that can decompile the file if you want to open it and look around.
Click to expand...
Click to collapse
You sir deserve a big pint of something great. Point by point I:
1. I already had sdk installed so didnt need to install this.
2. I cleared the phone back to factory with Recovery (Power on with holding -Vol, RECOVERY, Wipe data/Factory Reset, Power Off)
3. I went into HBOOT (by powering on holding down -vol)
4. Opened FASTBOOT and connected phone to computer via USB
5. Opened up command prompt on PC (start menu, typed cmd in the search box)
6. I then Typed the following:
7. "cd c:\Android" (to get me into the folder where my files are)
8. "fastboot flash boot boot.img"
9. this then loaded my boot file and bosh, Im done.
I then restarted the phone and bobs your mothers brother Im using wiresless again. Its such an easy process but on the first go it seems like rocket science.
You cant appreciate how greatful i am for your help. Thank you more than a lot.
If i chose a different ROM at what point is it best to do this stage? Are you able to do this to the boot image before you use recovery to 'insatll zip from sd card'? Or do you have to install then come back to it like i did?
For every custom rom you install you need to follow the same procedure.
1. First flash/install the rom via recovery
2. Get the boot.img and flash it via fastboot (some rom's have more than one kernel then choose the best you want)
As long as you stay in HTC unlocked bootloader the above steps are necessary to flash the rom completely to prevent bootloops and wifi errors
sent from my blazing fast pyramid through sonic waves
ta gane shp, this is a good place with good people
Thanks this post helped me a lot!
I got Android Revolution fully working, but I'm trying to flash the newest OC Kernel of SebastianFM over it. But his zip doesn't have a "boot.img", it does however contain the following: mkbootimg, mkbootimg.sh and unpackbootimg. Is it any of those I need to flash, if not, which "boot.img" do I flash then?
Asskicker2 said:
Thanks this post helped me a lot!
I got Android Revolution fully working, but I'm trying to flash the newest OC Kernel of SebastianFM over it. But his zip doesn't have a "boot.img", it does however contain the following: mkbootimg, mkbootimg.sh and unpackbootimg. Is it any of those I need to flash, if not, which "boot.img" do I flash then?
Click to expand...
Click to collapse
Hi,
I believe the boot.img refers to the ROM you are flashing.
This is a kernel.
So,make a nandroid backup,
wipe cache and dalvik,
and flash the kernel from the root of the sd card,choosing install zip from sd card in recovery.
malybru said:
Hi,
I believe the boot.img refers to the ROM you are flashing.
This is a kernel.
So,make a nandroid backup,
wipe cache and dalvik,
and flash the kernel from the root of the sd card,choosing install zip from sd card in recovery.
Click to expand...
Click to collapse
Yeah, that isn't working.
Wifi ain't working now.
Asskicker2 said:
Yeah, that isn't working.
Wifi ain't working now.
Click to expand...
Click to collapse
Hi,
Just restore the nandroid backup you made.
malybru said:
Hi,
Just restore the nandroid backup you made.
Click to expand...
Click to collapse
Yeah, but I wanted to update to newest kernel. Thanks though
Doesn't work with me.
taffytim said:
You sir deserve a big pint of something great. Point by point I:
1. I already had sdk installed so didnt need to install this.
2. I cleared the phone back to factory with Recovery (Power on with holding -Vol, RECOVERY, Wipe data/Factory Reset, Power Off)
3. I went into HBOOT (by powering on holding down -vol)
4. Opened FASTBOOT and connected phone to computer via USB
5. Opened up command prompt on PC (start menu, typed cmd in the search box)
6. I then Typed the following:
7. "cd c:\Android" (to get me into the folder where my files are)
8. "fastboot flash boot boot.img"
9. this then loaded my boot file and bosh, Im done.
I then restarted the phone and bobs your mothers brother Im using wiresless again. Its such an easy process but on the first go it seems like rocket science.
You cant appreciate how greatful i am for your help. Thank you more than a lot.
If i chose a different ROM at what point is it best to do this stage? Are you able to do this to the boot image before you use recovery to 'insatll zip from sd card'? Or do you have to install then come back to it like i did?
Click to expand...
Click to collapse
I tried this with OrDroid and ViperS laterst versions and the wifi still doesnot work with my device.
It does nor even turn on from the settings, someone please help!
Wi-Fi Issues
theumairahmad said:
I tried this with OrDroid and ViperS laterst versions and the wifi still doesnot work with my device.
It does nor even turn on from the settings, someone please help!
Click to expand...
Click to collapse
Post 3 in this thread explains exactly where the problem is. But ........you will never unlock that boot partition if ur phone is S-ON. The trick with the wire works...it took me couple of times to do it but it worked. Then.....the lates ViperS version does it for you. You do not have to use ADB or whatever that program was to flash the boot.img It is all in the ROM. I even flashed the newest bricked 1.4 kernel on top.....but that 3rd comment is the key to all problems with Wi-Fi and other kernel issues:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
I rooted my NS4G running stock ics but I get an error when try to flash cwm recovery using ROM Manager. Any advise, I need help please.thanks
Galaxy Note
I'm assuming you unlocked via fastboot? You might be better off flashing the recovery image through there instead. You'll have better luck that way:
Snag the recovery image from here
Make sure the file is in the same location as adb. Turn your phone off and then power it on to the bootloader screen (pwr + vol up). Once there, open your command prompt, attach the phone via USB, and type fastboot devices to make sure your phone is recognized. Once you're okay there, proceed to type
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo4g.img, this is assuming you haven't changed the name of the image. You can copy it and paste it as well.
Once you get the recovery image flashed, you'll need to ensure that the stock recovery doesn't replace CWM. Steps can be found in
This post
HTH
Hello everyone!
I've used ROM manager to flash clockwork mod recovery and it worked great until I realised that this clockwork doesn't see my SD card! I just wanted to know is there a solution to this without going back to stock etc?
Sent from my Xoom using XDA Premium HD app
Never fear! Fastboot is here!
Fastboot flash recovery recovery.img from the command line of your computer (you must have motorola drivers installed plus adb/fastboot tools)
I recommend Rogue Recovery, it's over in the android development section. Others prefer TWRP and EOS recovery. Take your pick. All support the internal SD card.
Thanks for your reply!
I thought about it initially, wanted to repeat steps used to flash it when original recovery was on. But first command re-booted xoom and took me to clockwork (no s..t, Sherlock? ) and then I thought I better stop before I end up with a brick.
So just to be clear, connect my xoom, go to the right folder on my pc and type:
fastboot flash recovery file-name.img
is that correct? do I need to be in recovery?
xywojtek said:
Thanks for your reply!
I thought about it initially, wanted to repeat steps used to flash it when original recovery was on. But first command re-booted xoom and took me to clockwork (no s..t, Sherlock? ) and then I thought I better stop before I end up with a brick.
So just to be clear, connect my xoom, go to the right folder on my pc and type:
fastboot flash recovery file-name.img
is that correct? do I need to be in recovery?
Click to expand...
Click to collapse
So you need to be in bootloader mode, not recovery. You can either turn the xoom on then press the down button about 2 seconds after you see the splash screen or use 'adb reboot bootloader'. I think it says 'starting fastboot protocol', can't quite remember from memory. then as you said, go to the right folder type fastboot flash recovery file-name.img
then fastboot reboot
then you'll be able to get into your custom recovery
love you man!
I wanted to go back to stock CM. So I went to TWRP and erased everything. Next thing it said was that I don't have any OS in the phone.
Now I want to sideload the stock CM into to the phone.
Please tell me step by step solution as I am a nooby.
Please help.
Thanks in advance
Of course you don't have an OS if you wiped system. Did you not put stock CM onto your device before wiping everything? Google search 'how to adb sideload' and you'll did plenty of guides. Maybe hold up on doing anything else to your device until you have a better understanding of what you're doing.
Transmitted via Bacon
samdubai said:
I wanted to go back to stock CM. So I went to TWRP and erased everything. Next thing it said was that I don't have any OS in the phone.
Now I want to sideload the stock CM into to the phone.
Please tell me step by step solution as I am a nooby.
Please help.
Thanks in advance
Click to expand...
Click to collapse
If you lost the recovery aswell:
- fastboot mode
- download twrp recovery to your fastboot file and rename it to "recovery"
- (pc) open comand window and type "adb flash recovery recovery.img"
- open recovery
- advanced
- adb sideload
- download stock rom
- (pc) adb sideload (rom name).zip
I find it hard to believe that people who own a "hackers phone" don't save a nandroid on their pc. Still, you got your solution there.
Please help
badjoras said:
If you lost the recovery aswell:
- fastboot mode
- download twrp recovery to your fastboot file and rename it to "recovery"
- (pc) open comand window and type "adb flash recovery recovery.img"
- open recovery
- advanced
- adb sideload
- download stock rom
- (pc) adb sideload (rom name).zip
I find it hard to believe that people who own a "hackers phone" don't save a nandroid on their pc. Still, you got your solution there.
Click to expand...
Click to collapse
I am now in stock rom. I downloaded it from Cynogenmod website. I have done it through fastboot adb sideload.
I saved nandroid but can't transfer that zip file to my phone. How can I side load it through fastboot?
Please help
samdubai said:
I am now in stock rom. I downloaded it from Cynogenmod website. I have done it through fastboot adb sideload.
I saved nandroid but can't transfer that zip file to my phone. How can I side load it through fastboot?
Please help
Click to expand...
Click to collapse
take a look in the backup. Are there image files in it?
You can flash image files with fastboot.
But why does USB not work in stock-rom?
Lei M said:
take a look in the backup. Are there image files in it?
You can flash image files with fastboot.
But why does USB not work in stock-rom?
Click to expand...
Click to collapse
I don't know the reason. I could not upload zip file into my phone through TWRP recovery.
So eventually I sideloaded stock rom through fastboot.
Which effectively means that I am back to unrooted and no TWRP.
Also, 33R seams to be buggy. Battery performance is still jittery and it can't detect wifi automatically. I need to switch it off and on to make it work again.
So, I want to go back to my earlier backup which was 25R. I need a fool proof process to do so.
Would really appreciate all your help