Related
Very weird problem here. The phone will boot into the OS just fine but whenever I try to boot into the recovery to flash a rom... it just hangs on the MT3G screen.
I've tried re-flashing RA 1.7.0G and the clockwork, same problem.
It's a 32B if that makes any difference.
I had this same problem where the recovery partition on the phone went corrupt on me. I have the same phone and carriuer as you. I read and read for a fix. The one that eventually worked for me was repeatedly trying to flash Amon RA 1.7.0 through rom manager. That was also what cause the problem seeing as I ran out of ram flashing it through there. I also tried fastboot and failed (I was able to do it once it was back up). and terminal and adb. GOOD LUCK MAN.
Jimmy Conley said:
I had this same problem where the recovery partition on the phone went corrupt on me. I have the same phone and carriuer as you. I read and read for a fix. The one that eventually worked for me was repeatedly trying to flash Amon RA 1.7.0 through rom manager. That was also what cause the problem seeing as I ran out of ram flashing it through there. I also tried fastboot and failed (I was able to do it once it was back up). and terminal and adb. GOOD LUCK MAN.
Click to expand...
Click to collapse
Much thanks for this advice...I didn't want to have to start all over again...I was able to get Amon's recovery working again by keeping retrying the flash...loll...it finally work...NOt messing with Rom Manager no more....
I had this happen to me today on RC1. I stupidly flashed Clockwork Recovery from within ROM Manager, only to discover that it wouldn't boot into recovery and just sat at the green MyTouch boot screen.
I was able to flash Amon_RA from within ROM Manager (the phone sat there for like 10 minutes before finally saying "Flash Successful!" or whatever), and I was then able to load RC2 without issue, clear the dalvik-cache, etc.
Never touching ROM Manager again.
I did the same thing. (Tried to flash Clockwork Recovery from within ROM Manager.) I haven't ever done a recovery like this...but I figured since it was an option on ROM Manager that everything would be fine and dandy. It wasn't. Hung at MT3G screen when booting into recovery. Flashed AMON_RA from ROM Manager and everything works now. No more ROM manager for me!
my phine (1st gen mytouch 3g) is rooted and has the current 5.08 blah blah version of cyanogenmod. i downloaded the new version today and tried flashing via rom manager (again a 1st timer with this app) and figured it would work. gets stuck at green mytouch logo. i will keeo trying to flash the amon ra back. the only laptop i have access too doesnt recognize any android phone so i cant transfer files back and forth >_< not a fun day
on the other hand it boots fine after about 20 min into cyanogen 5.8 blah blah version lol
That has happened to me also when using ClockworkMod Recovery & ROM Manager.
I recommend to use fastboot for recovery flashing:
(0. If you don't have the Android SDK, get it. Also get your favorite recovery img)
1. Copy fastboot.exe, adb.exe, AdbWinApi.dll & AdbWinUsbApi.dll to %WinDir%\System32
2. Connect your phone via usb to your PC. Shut it down and then boot while pressing back + power until you're in fastboot. Start CMD and run "fastboot devices"
3. If and when you get an ID, you're ready to go.
4. Type "fastboot erase recovery"
5. Move the recovery image to C's root folder (C:\) and in CMD type "CD.." for example like three times until you're in C:\.
6. Type "fastboot flash recovery [your recovery image]"
(for example "fastboot flash recovery recovery-RA-Magic32A-6.35-v1.6.2.img")
After that, shut down your device and reboot while pressing home + power until you're successfully in recovery!
This works for me.
hey guys i'm having some trouble. i just got the nexus (it's my first smartphone, ever) and i've tried to hit the ground running. here's what i've done to the phone so far.
i got all the drivers running on my win7 machine and also installed the android SDK folder onto C: as was described in this thread: http://forum.xda-developers.com/showthread.php?t=878786
i then unlocked the bootloader using the above guide as well. when I power on the phone using UP+POWER it says UNLOCKED.
I then proceeded to follow this guide: http://forum.xda-developers.com/showthread.php?t=875875
i used ADB to flash the clockwork crespo recovery. i then used fastboot to install Superuser.
at that point i had an unlocked bootloader, clockword recovery image and superuser permissions.
i then saw that the 2.3.1 update had been released. i wanted to learn how to tackle that so i started reading up. i noticed that people were using ROM Manager and Titanium. I got titanium and installed the BusyBox addon and it allowed me to do a full Batch Backup of all my programs, etc. i've got the 50MB or so backup folder on my PC now.
anyway, i then messed with Rom Manager. I installed the 3.0.0.0 ClockworkMod Recovery and everything went smoothly. now this is where my troubles begin.
when i go to Download ROM all i get is a Free Stuff area.
when i go to Check for ROM Updates it tells me my device isnt set up for OTA updates.
those are just minor issues.
this is the big and scary issue i have:
when i click on reboot to recovery, it takes me to the same screen that i go to when i power on with VOLUME UP+POWER. it doesnt take me to the recovery screen that i see in various youtube videos. instead, i'm at the main screen where it says UNLOCKED and i have 4 choices (reboot bootloader, recovery, reboot, power off). and on the very top in RED letters it says fastboot - no boot or img file. <-- this is the part that makes me nervous. If i manually power down the phone and boot to fastboot and click recovery, it just goes back to this same screen and says fastboot - no boot or img file. when i first rooted the phone, clicking recovery actually took me to a different screen where i was able to load up superuser.zip and install it.
did i accidetnally delete something that i wasnt supposed to? did installing ROM manager mess something up? i typically dont do anything until i confirm that i am supposed to. i think the problem is that i dont yet know how one thing i do on the phone affects another. i'm guessing when i used rom manager to update the CWmod it changed some folders/files? i dunno!
otherwise, the phone works fine and there are no glitches or hiccups or crashes. So if someone can please take a moment to just explain to me what i did wrong or what i failed to do i'd really, really appreciate it.
you don't have a recovery partition. Either flash one over manually using fastboot, or boot up and try to use ROM Manager to flash CWR.
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
kramer987 said:
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
Click to expand...
Click to collapse
yes, just follow the examples in http://forum.xda-developers.com/showthread.php?t=875875
kramer987 said:
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
Click to expand...
Click to collapse
Yes, 'cept it will be "fastboot flash recoveryrecovery-clockwork-3.0.0.0-crespo.img" without the quotes now.
But does it say that you're missing a boot.img or recovery.img?
Also, the "not set up for OTA" thing isn't for official OTAs. Some developers have made their custom ROMs capable of being updated that way.
unremarked said:
Yes, 'cept it will be "fastboot flash recoveryrecovery-clockwork-3.0.0.0-crespo.img" without the quotes now.
But does it say that you're missing a boot.img or recovery.img?
Also, the "not set up for OTA" thing isn't for official OTAs. Some developers have made their custom ROMs capable of being updated that way.
Click to expand...
Click to collapse
thank you luxferro and unremarked. i did it and it works perfectly. i am now able to access clockworkmod recovery 3.0.0.0. next step is backup my existing ROM and also to figure out how to put the OTA 2.3.1 on and restore all my data
oh and unremarked: it basically said no boot or img file and thats it after i would click on recovery or reboot to recovery trhough rom manager. it was just in red at the top. but now it takes me to the ClockworkMod Recovery
I have a rooted mytouch original with cyanogen 5.0.7/android 2.1 and want to upgrade to cyanogen 6.0.0/android 2.2.
Can I just install the new rom, or are their prior steps to prepare for this.
Thanks
DAve
Check CM wiki.. all the info is there!
yes, I had already read through the cm wiki before posting. I just read through it a second time, though the specific question that I had asked was not addressed as far as I could tell. Don't want to flash a new rom without first knowing its the right step to take. So if someone doesn't mind answering the question...
Just do a nandroid backup. Then you flash the CM 6 over the old one, do a cache+dalvic wipe and start it up.... It should be ok.
If not, then just revert back with the knowledge that you have to do a complete wipe, meaning that you need to start from scratch.
I now have initiated flashing new rom, starting with backing up data and wiping cash. However, I am now unable to go into recovery mode, whereas the phone is stuck on the logo when attempting to do so. I had installed through rom manager clockworkmod 2.5.0.1, got the message it installed correctly.
Here are the methods I have used to go into recovery:
1. click on "reboot into recovery"
2. backup current rom
3. flash alternative recovery with RA Recovery v.1.7.OH downloaded by rom manager, and use rom manager to restart into recovery mode
4. turn phone off, try to press home and power button together, for the new RA and the new clock work mod programs.
will not go into recovery mode, gets stuck on the boot up logo. Phone otherwise works fine, on the older Cyanogen Rom..., just can't go into recovery mode which I need to do to upgrade.
My original recovery was RAv1.2.0G.img, but this was I assume replaced by the rom manager.
In case this is important, my other software versions I have been using the past year:
Hboot 1.33.2005 (sapp30000), Cpld 10, Radio 2.22.19.261
will not go into recovery mode, gets stuck on the boot up logo. Phone otherwise works fine, on the older Cyanogen Rom...
any suggestions?
You flashed wrong recovery version...
You need RA Recovery v.1.7.OG and not H as stated above.
If all ****s up, then use my guide (check my signature) to flash a custom recovery... just skip the steps about root since you already got that!
Remember, G and NOT H.
lost recovery
mumilover
I do actually have v.1.7.0G installed, not H (my bad).
it just will not go into recovery.
Please let me know where your guide is, but right now I have been unable to communicate with my device through my xp desktop, get the "device not found" error (I assume you are suggesting that). Not sure how this will help though, since I already seem to have the correct recovery image installed.
Any help you can offer would be appreciated.
Dave
mumilover said:
You flashed wrong recovery version...
You need RA Recovery v.1.7.OG and not H as stated above.
If all ****s up, then use my guide (check my signature) to flash a custom recovery... just skip the steps about root since you already got that!
Remember, G and NOT H.
Click to expand...
Click to collapse
Download my fastboot commander (CHECK MY SIGNATURE, magic version).
Restart into fastboot mode.
Download this recovery image:
http://rapidshare.com/files/387932919/recovery-RA-sapphire-v1.7.0G.img
Using the tool and your eng spl, you can just flash the recovery image on the phone.
Just use the first tab -> recovery button -> navigate to the above image -> click "flash recovery". Done.
Restart into recovery by home + power combo.
You could also try this command:
Code:
adb shell reboot recovery
to force it to boot into recovery from the system.
[Problem is fixed. Thanks for your help.
I used my mac bootcamp (could not get sdk to run on my desktop or mac), and could find my device through adb. Then I pushed a separate version of the RA 1.7.0 G (the one the came with rom manager did not work!) to my phone via flash command. Voila, I am now able to go into recovery mode. 6.0 is installed and running.
QUOTE=mumilover;10252460]Download my fastboot commander (CHECK MY SIGNATURE, magic version).
Restart into fastboot mode.
Download this recovery image:
http://rapidshare.com/files/387932919/recovery-RA-sapphire-v1.7.0G.img
Using the tool and your eng spl, you can just flash the recovery image on the phone.
Just use the first tab -> recovery button -> navigate to the above image -> click "flash recovery". Done.
Restart into recovery by home + power combo.
You could also try this command:
Code:
adb shell reboot recovery
to force it to boot into recovery from the system.[/QUOTE]
My recovery mode does not work.
I have a rooted original mytouch that I have been using with Cyanogen 5.0.6 ROM for a year, decided recently to upgrade to 6.0.0. After downloading ROM manager premium, and installing the recommended recovery mode program, clockworkmod 2.5.0.1., I initiated flashing new rom, starting with backing up data and wiping cash. However, I am now unable to go into recovery mode, whereas the phone is stuck on the logo when attempting to do so.
Here are the methods I have used to go into recovery mode via rom manager
1. through clicking on "reboot into recovery"
2. through clicking on backup current rom
3. flash alternative recovery with RA Recovery v.1.7.OH downloaded by rom manager, and use rom manager to restart into recovery mode
4. turn phone off, try to press home and power button together, for the original RA and the new clock work mod programs.
will not go into recovery mode, gets stuck on the boot up logo. Phone otherwise works fine, on the older Cyanogen Rom..., just can't go into recovery mode which I need to do to upgrade.
My original recovery was RAv1.2.0G.img, but this was I assume replaced by the rom manager.
In case this is important, my other software versions I have been using the past year:
Hboot 1.33.2005 (sapp30000), Cpld 10, Radio 2.22.19.261
any suggestions?
leiko49 said:
My recovery mode does not work.
Here are the methods I have used to go into recovery mode via rom manager
...
3. flash alternative recovery with RA Recovery v.1.7.OH downloaded by rom manager, and use rom manager to restart into recovery mode
...
My original recovery was RAv1.2.0G.img, but this was I assume replaced by the rom manager.
In case this is important, my other software versions I have been using the past year:
Hboot 1.33.2005 (sapp30000), Cpld 10, Radio 2.22.19.261
any suggestions?
Click to expand...
Click to collapse
Let me get this straight... RA Recovery 1.2.0G worked and you tried RA Recovery 1.7.0H and you can't get that to work... right?
Wow... or am I just missing something?
Why not give RA Recovery 1.7.0G a try instead. Or better yet... since your using ROM Manager... try Clockwork for MyTouch/Ion devices for US T-Mobile devices or Magic for all SenseUI (native) devices.
I had not needed to use recovery for a long time, since I have just been happy with the phone.
Now I wanted to upgrade, and installed rom manager, and then rom manager directed me to upgrade the recovery software, which eliminated my original 1.2.0G, replacing it with clockwork for mytouch, which did not work. i then tried clockwork for Magic, which did not work. Through Rom manager I then installed and tried ra recovery 1.7.0H, which also did not work.
based on your suggestion, I downloaded RA Recovery 1.7.0G to my computer. It has been a year since I have attempted to flash software to my phone. What is the easiest way to flash 1.7.0G to my phone?
Thanks!
Dave
leiko49 said:
I had not needed to use recovery for a long time, since I have just been happy with the phone.
Now I wanted to upgrade, and installed rom manager, and then rom manager directed me to upgrade the recovery software, which eliminated my original 1.2.0G, replacing it with clockwork for mytouch, which did not work. i then tried clockwork for Magic, which did not work. Through Rom manager I then installed and tried ra recovery 1.7.0H, which also did not work.
based on your suggestion, I downloaded RA Recovery 1.7.0G to my computer. It has been a year since I have attempted to flash software to my phone. What is the easiest way to flash 1.7.0G to my phone?
Thanks!
Dave
Click to expand...
Click to collapse
1.7.0H will NOT WORK!
You MUST use G.
I suggest by fastboot.
place the recovery.img file (or whatever you want to name it. no spaces!) in c:\android\recovery (directory is just an example... feel free to use your own... again... no spaces!)
Power up your phone in bootloader
Then in cmd prompt
cd c:\android\recovery (or whatever directory you use)
fastboot flash recovery recovery.img (or whatever you named it)
Reboot in your new recovery.
Note... this will only be effective if you have S-OFF.
fastboot flash recovery 'recovery image name'
Make sure it's in the ADB folder.
EDIT: Did you really create a duplicate thread for the same problem? http://forum.xda-developers.com/showthread.php?t=894289
Something is not working here. my bootloader screen on my phone states that s-off.
I have placed phone in fastboot mode, and when connected to computer shows "fastboot usb".
I placed the recovery file on my desktop, directory c:\adb. In this directory is the adb.exe file.
I have now placed the fastboot.exe file in this directory as well
At my desktop command prompt, I go to the c:\adb directory, then type
fastboot flash recovery 'recovery image name'
I get the following message 'waiting for device'
As stated, it has been a while since I have used adb, so perhaps something else needs to be in the desktop c:\adb directory.
Sorry about the double post, not sure how to delete it.
Dave
Problem is fixed. Thanks for your help.
I used my mac bootcamp (could not get sdk to run on my desktop or mac), and could find my device through adb. Then I pushed a separate version of the RA 1.7.0 G (the one the came with rom manager did not work!) to my phone via flash command. Voila, I am now able to go into recovery mode. 6.0 is installed and running.
a summary of my problem
I am unable to go into recovery mode.
I have a rooted mytouch, running Cyanogenmod 5.0.7 with android 2.1. I have used it for about a year without problem, and without trying to make changes. Naturally, recovery mode worked last year when I first rooted it.
I recently initiated efforts to upgrade to cyanogen 6.0.0 with android 2.2
I started by installing Rom Manager, and immediately after using Rom Manager to install clockworkmod recovery, after which I attempted then to back up my current rom before upgrading it.
I have since been unable to go into recovery mode, using these methods
1. the features of rom manager, e.g., reboot into recovery
2. flash alternative recovery ra recovery v1.7.0G
3. with both 1.7.0G and clockworkmod, attempting to boot into recovery by powering up holding down home key and power key.
My original recovery, before installing rom manager and then installing clockworkmod was RAv1.2.0G.img, but I replaced this with the Rom manager.
In case this is important, my other software versions :
Hboot 1.33.2005 (sapp30000), Cpld 10, Radio 2.22.19.261
Any help would be appreciated.
Dave
Hi
I've searched for a solution but didn't find one for my problem so...
I was trying to flash an updated kernel through Kernel Manager application and then it said it cannot complete task and asked me to reboot system.
I then entered into the recovery and flashed the kernel manually.
When rebooted system I got the message "FASTBOOT MODE - NO BOOT OR RECOVERY IMG" in red at the top of the bootloader.
So naturally I thought maybe it lost the recovery so I went and flashed CWM recovery 3.0.2.5 (had 3.0.2.4 when all this happened) through fastboot and that went OK.
I then entered the recovery to make sure the recovery flashing went OK and pressed Restart system now.
But then it started the bootloader and the same message appeared "FASTBOOT MODE - NO BOOT OR RECOVERY IMG" in red at the top of the bootloader.
I repeated that process few times and same thing.
The strange thing is when I select "REBOOT BOOTLOADER" and it boots into bootloader I see "FASTBOOT MODE" in red at the top. But when I try to reboot the phose I see the message to the top again.
How can I get out of this?
Hi guys,
I've got the same problem, although I don't know if it IS a problem.
I'm running v7.0.0-NS and I'm going to upgrade to v7.0.3 ... just searching for instructions!!!
~AndrewGoldy
since I am able to enter the recovery Im trying to restore an earlier backup. Not sure it this will do anything since my problem is in the bootloader area.
If this makes my phone to start up normally then I really dont understand this.
*** I think that I've just fixed it ***
I opened up "Rom Manager v4.2.0.2", and then selected the option to "Flash ClockworkMod Recovery"
Once it had downloaded "ClockworkMod Recovery v3.0.2.4", I selected the option to "Reboot into Recovery".
That worked.
It now says "Fastboot Mode" when I boot into the Bootloader.
Success!!!! (I think)
Well it just finished restoring the backup.
It seems it solved the problem on mine to since it passed the bootloader and the boot animation is on.
I really cant understand this.
I've done the same but the Recovery Stil nor Bootloader works. However it does say Fast boot mode now instead of no boot or recovery img. But still can't flash or back up a rom!
Correction i got it work after flashing to oldest recovery that was an option
I fixed this problem (Nexus S) by reverting to an older (3.0.2.4) CMRecovery, just go down to the last option "All ClockworkMod Recoveries" and Flash an older version (mine was not working with 5.0.2.0).
Hi! Anyoane can help me ?
I disconnected by accidently the USB cable while the phone was at the ClockWorkMod Recovery v5.0.2.0/-mounts and storage/-mount USB storage, and after that ( adb , fastboot and usb died).
I installed Stock OTA 2.3.6 I9023 for my Nexus S I9023. During the day phone closed and no longer wanted to open (even replace the battery). After more hours the phone is open , adb and usb works not for a long time after several attempts ( during this time I managed it to root and install CWM 5.0.2.0 back)
I flashed ICS Kwiboo v3 . After reboot the phone began to froze , and shortaly closed.
Because the phone will no longer open I tried in CWM all ( wipe data:fact, wipe cache, wipe dalvik, format/all ) .
Now if reboot system on CWM I have Fastboot Mode - No Boot or Recovery IMG
but if I reboot bootloader or power off when is opened is just Fastboot Mode .
Adb , fastboot and mount USB still no work. ( I have SDK 14 on windows7 installed, all the driver for Nexus S was updated).
Because the PC not recognized my phon I can't install another ROM or CWM.
( When USB cable connecting on the phone it's charge the battery only!).
Thanks for your advice!
No recovery img & fastboot devices -> nothing
Hi all,
When I try to access the recovery mode on my NS, I have the same "no boot or recovery img". I change my CWM version from last to 3.0.2.4 and another version too. Still, I can't access the recovery mode.
I installed the SDK to restore a stock recovery image I found, hoping to use fastboot (from the sdk + a standalone version I found before). But it won't recognize my phone (fastboot devices -> nothing). I installed the PdaNet for the Android 1.0 driver, and the Android 4.0 driver from the SDK. Still nothing, although "adb devices" apparently sees my phone.
I've spent my whole night on this. Without recovery I can't backup, and I can't switch rom (heard of this ICS rolling-out ? I'd like to have some flavour of it), I can't wipe or whatever.
Please can someone point me to a solution for fastboot to see the phone, or even better, to reinstall a recovery tool ?
Thanks a huge lot
S
saychand said:
Hi all,
When I try to access the recovery mode on my NS, I have the same "no boot or recovery img". I change my CWM version from last to 3.0.2.4 and another version too. Still, I can't access the recovery mode.
I installed the SDK to restore a stock recovery image I found, hoping to use fastboot (from the sdk + a standalone version I found before). But it won't recognize my phone (fastboot devices -> nothing). I installed the PdaNet for the Android 1.0 driver, and the Android 4.0 driver from the SDK. Still nothing, although "adb devices" apparently sees my phone.
I've spent my whole night on this. Without recovery I can't backup, and I can't switch rom (heard of this ICS rolling-out ? I'd like to have some flavour of it), I can't wipe or whatever.
Please can someone point me to a solution for fastboot to see the phone, or even better, to reinstall a recovery tool ?
Thanks a huge lot
S
Click to expand...
Click to collapse
I can help you but....
1. In bootloader mod ADB working ? (if not try back off battery for 10 min or more) and try again..
2. Your device is rooted ?
I was going to suggest trying to reflash the latest recovery again in CWM, but I think you guys said that hasn't worked.
Every now and then when I flash a new ROM this happens to me. I usually just flash an older version, then reflash the newest version and the Recovery works just fine.
Maybe try using a different recovery program?
it does work, many have done it already, see all the duplicated topics
Sent from my SGH-T989 using xda premium
Thank you guys for your replys.
surdu_petru said:
I can help you but....
1. In bootloader mod ADB working ? (if not try back off battery for 10 min or more) and try again..
2. Your device is rooted ?
Click to expand...
Click to collapse
1. I removed the battery for 10mn. When I come back to the bootloader "ADB devices" doesn't return a device, so it doesn't see my phone. But when switched on, it can see it.
2. Yes, it is. There is the SuperUser app, and when apps ask for root, I can allow or deny. And the lock state is 'unlocked'
akabadnews said:
I was going to suggest trying to reflash the latest recovery again in CWM, but I think you guys said that hasn't worked.
Every now and then when I flash a new ROM this happens to me. I usually just flash an older version, then reflash the newest version and the Recovery works just fine.
Maybe try using a different recovery program?
Click to expand...
Click to collapse
I tried the latest, the oldest, the versions inbetween... nothing. I have the latest version of CWM and I reflashed the last Recovery from the app.
I can't flash another ROM, because I need recovery mode for that ; and my problem is that I can't access recovery indeed... :/ I feel like I need A to do B, and B to do A.
"No boot or recovery img": doesn't it mean that I should put some file somewhere ? I hope it would be that simple.
Do you have other ideas ?
---------- Post added at 01:33 PM ---------- Previous post was at 01:24 PM ----------
AllGamer said:
it does work, many have done it already, see all the duplicated topics
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I've tried several time, flashing different versions of CWM recovery. I've returned to bootloader -> recovery dozens of time and I still have the "no boot no recovery img". I'll try again.
All the threads which speak about it and mention to flash another rom -> yeah thanks, but I can't access recovery
Threads mentioning fastboot -> I tried with different drivers (including 1.0 and 4.0), but fastboot won't see/talk to my device
Do you see something else that I didn't try ?
---------- Post added at 02:16 PM ---------- Previous post was at 01:33 PM ----------
I also tried this which seems to be a good step
http://forum.xda-developers.com/showthread.php?t=1356319
Basically it says
adb shell
SU
flash_image recovery /sdcard/filename.img
But like the guy in thread, I have memory errors "mtd: read error at 0x00000000 (out of memory)" then write errors, then "failed with error: -1" and "error writing recovery"
It's ok now.
In case other it can help other people:
I tried again the PDAnet installation to get the android 1.0 drivers. (actually there is a binary called "install legacy usb drivers" which apparently worked well.)
Fastboot would detect my phone in bootloader mode.
So I could "fastboot flash recovery xxx.img" I first failed with a stock recovery, but for which I didn't know the exact reference and origins (I was stuck with the exclamation point in white triangle). As I couldn't find another stock recovery for Nexus S, I downloaded the CWM recovery from the website (not from the app), last version (5.0.2.0) and flashed it with fastboot.
It seems to work properly now, so i'm doing a rom backup, just in case for later, and I'll flash stock ICS
FYI: rom manager only caused me issues ; I don't know why Cyanogen uses it. Just use the recovery directly from recovery... Even CWM. just not Rom Manager.
Cheers and thanks to those who tried to help.
++
saychand said:
It's ok now.
In case other it can help other people:
I tried again the PDAnet installation to get the android 1.0 drivers. (actually there is a binary called "install legacy usb drivers" which apparently worked well.)
Fastboot would detect my phone in bootloader mode.
So I could "fastboot flash recovery xxx.img" I first failed with a stock recovery, but for which I didn't know the exact reference and origins (I was stuck with the exclamation point in white triangle). As I couldn't find another stock recovery for Nexus S, I downloaded the CWM recovery from the website (not from the app), last version (5.0.2.0) and flashed it with fastboot.
It seems to work properly now, so i'm doing a rom backup, just in case for later, and I'll flash stock ICS
FYI: rom manager only caused me issues ; I don't know why Cyanogen uses it. Just use the recovery directly from recovery... Even CWM. just not Rom Manager.
Cheers and thanks to those who tried to help.
++
Click to expand...
Click to collapse
THANKS! This helped A TON!
I did the PDA installation again, and for some reason this seemed to fix my inability to access recovery.
Agreed on Rom manager, I updated CWM through rom manager and I believe that's what buggered up my recovery, as I have never had trouble accessing it before I did that.
But again, a big THANKS for that suggestion!