Hi
I installed CWM 5 on my Nexus S. I can reboot one time and go back to CWM but after a second reboot, the recovery is back to default and I have to reflash it
Does any of you already experienced this problem ?
happens to me. i go to rom manager and re flash cwm then reboot to recovery.
Are you both using stock? The stock rom has a script that restores the default recovery when you reboot.
Delete / rename /etc/install-recovery.sh
This script writes the stock recovery on boot.
Sent from my Nexus S using xda premium
I've experienced this as well, and plan to re-name install-recovery.sh.
For those that are continually re-flashing the recovery image, do you think there is a possibility of writing to that area too many times?
I've heard of NAND flash dying in flash drives after very data intensive operations, and I've also heard of ROM storage areas having a limited number of writes.
Just wanted to test the waters.
rican408 said:
happens to me. i go to rom manager and re flash cwm then reboot to recovery.
Click to expand...
Click to collapse
Always flash through Fastboot, Better than flashing from Rom manager.
I renamed /etc/install-recovery.sh and it works
Thanks
Happens to me until I started flashing twice everytime I flash a Rom ... =] try it
Sent from my Nexus S using xda premium
Related
Hey guys..
I just today rooted my lovely Nexus S, 9023 or what its called (non branded or nothing)
But i cant load recovery.. went fine when i rooted it, but now that i want to load an custom rom it fails.. i followed this guide to root: http://forum.xda-developers.com/showthread.php?t=883032
Anyone have some ideas??
I just get a android logo and triangle + ! in it.. as error.. (
Best regrads
n0ta
Just tested with ROM Mananger, it can backup just fine.. as soon i choose a ROM to install it loads recovery and fails, just like when you do it manually.
n0ta said:
Just tested with ROM Mananger, it can backup just fine.. as soon i choose a ROM to install it loads recovery and fails, just like when you do it manually.
Click to expand...
Click to collapse
Sounds like stock recovery installed itself. If you are rooted remove/rename /etc/install-recovery.sh then reflash cwm manually or through rom manager.
Sent from my Nexus S 4G using XDA Premium App
I have had this happen on my NS4G. I know they are a little different, but it seems like you are having the same thing happen that I did and to solve it, I open Windows command prompt(or terminal depending on you OS) and fastboot flash recovery (insert recovery.img name here) and reflashed the recovery partition with clockwork. Very easy fix. Just make sure you boot straight into recovery after flashing and flash the Rom you want to flash before booting back into stock(also make a nandroid before that). After that you shouldn't have any more problems unless you unroot. There must be a small glitch somewhere when flashing the clockwork doesn't fully erase stock recovery partition.
krohnjw said:
Sounds like stock recovery installed itself. If you are rooted remove/rename /etc/install-recovery.sh then reflash cwm manually or through rom manager.
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
Works now thanks all to both of you.
n0ta said:
Works now thanks all to both of you.
Click to expand...
Click to collapse
Pretty common lately...Android for Nexus S recovers its recovery if it is changes...
"You dawg, we heard you like recovering your recoveries, so we made recovery recover in recovery." and all that...
bender_123 said:
Pretty common lately...Android for Nexus S recovers its recovery if it is changes...
"You dawg, we heard you like recovering your recoveries, so we made recovery recover in recovery." and all that...
Click to expand...
Click to collapse
The Nexus one did the same thing. Most OTAs verify / replace this file. It's easy enough to deal with if you're unlocked and rooted.
Sent from my Nexus S 4G using XDA Premium App
This is about the third or fourth time this question has come up over the past week...
bender_123 said:
This is about the third or fourth time this question has come up over the past week...
Click to expand...
Click to collapse
I assure you it won't be the last.
Sent from my Nexus S 4G using XDA Premium App
Is there a way to fully wipe cwm from the phone if it was flashed with NV flasher? I flashed the internal support one when I started flashing roms and now I notice that trying to flash external support roms has put me in a pickle. I've asked before whether I needed to switch support or something and was told the newest rom manager supports both... this is wrong. Upon installing eaglesblood 2.3.5 and installing rom manager...no cwm detected, so I flash it. Now when I reboot doing power and down I boot into an old internal support cwm that only has old backups and access to the internal SD. If I reboot from rom manager it will boot into the new cwm. How do I erase the old NV flash version. It wont hold any new backups, so if I crash it will leave me with old cwm. Plus its a pain when I don't have access to downloads I do via rom manager.....
Summary - old version of cwm bootable through power and down (nvflash version) . New version flashed by rom manager only shows up booting through rom manager. Want to erase NV flash version so there's only one. Frustrated.
Sent from my LG-P999 using XDA App
No need to erase, just nvflash over current will replace old.....if you flash newest 5.0.1.6 i belive, it lets you choose zip from sd card or internal memory....BUT have the latest nvflash one, its a must if you are gonna flash roms.
http://db.tt/Rl6YH0B
I see, what about flashing through rom manager? Is there a way to rid the rom manager install before I do the NV flash... should I not flash through rom manager?
Sent from my LG-P999 using XDA App
unique77 said:
I see what about flashing through rom manager. Is there a way to rid that one before I do the NV flash... should I not flash through rom manager?
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Just have both, make sure both are latest, but the nvflash one is most important. That one will/can save your life (phone)
For all intents and purposes, you cannot actually flash CWM from ROM manager with this phone. All it can do is reboot into CWM from the app. If you ever need to access CWM from a power-off state (bad flash, bootloop, etc.) you will only be able to enter the NVFlash version. Strongly recommend always having the NVFlashed version of CWM. Maybe even give up using ROM Manager altogether.
If you can't do without ROM Manager, keep using it. But it would be a good idea to flash CWM 5.x.x.x through NVFlash so that you have an emergency recovery that can read both internal and external memory.
Thanks Frisco and r4. Totally understand now. Relief. Now to Eb 1.9!
Sent from my LG-P999 using XDA App
Hi all,
when i boot my g2x into recovery (clockworkmod) and try to backup, it says it cant mount the system. first it used to say cant mount sd card but the solution was just taking out the sd card and putting it back in. unfortunately i cant do this with the system
anybody have any solutions
That happened to me too... download the update.zip from rom manager and boot that or flash the new recovery image
How do I get the update.zip though? And when I go on rom manager and click on flash clockworkmod, it flashes the latest version 5.0.2.0 but it only stays in that version if I click on restart into recovery. If I exit and turn my phone off then boot into recovery, I still have version 3.0.2.7 and the same can't mount system problem occurs
Sent from my LG-P999 using XDA App
I just fixed this problem today.
The version of CWM that you have flashed as recovery doesn't have the capability of mounting an ext4 file system. Most likely your file system was converted to ext4 somewhere along the way. You need to flash CWM again and it can't be through rom manager since Rom manager only gives you what is considered a "fake flash", which is why you see 2 different versions when you boot into your recovery.
Use the search feature to find information about how to install CWM 5.0.2.0.
There is a one click installation script somewhere in the development section for the G2x with very good instructions on how to permanently flash a newer version of CWM that can handle ext3 and ext4.
Doing this completely fixed this issue for me.
Hopefully it will do the same for you.
Sent from my LG-P999 using XDA App
EgyptianBoi said:
How do I get the update.zip though? And when I go on rom manager and click on flash clockworkmod, it flashes the latest version 5.0.2.0 but it only stays in that version if I click on restart into recovery. If I exit and turn my phone off then boot into recovery, I still have version 3.0.2.7 and the same can't mount system problem occurs
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
NEVER, EVER FLASH RECOVERY WITH ROM MANAGER!
rom manager only does a FAKE FLASH on your phone, if you want a real recovery, always flash with NVFlash
dserber said:
I just fixed this problem today.
The version of CWM that you have flashed as recovery doesn't have the capability of mounting an ext4 file system. Most likely your file system was converted to ext4 somewhere along the way. You need to flash CWM again and it can't be through rom manager since Rom manager only gives you what is considered a "fake flash", which is why you see 2 different versions when you boot into your recovery.
Use the search feature to find information about how to install CWM 5.0.2.0.
There is a one click installation script somewhere in the development section for the G2x with very good instructions on how to permanently flash a newer version of CWM that can handle ext3 and ext4.
Doing this completely fixed this issue for me.
Hopefully it will do the same for you.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
le66450146 said:
NEVER, EVER FLASH RECOVERY WITH ROM MANAGER!
rom manager only does a FAKE FLASH on your phone, if you want a real recovery, always flash with NVFlash
Click to expand...
Click to collapse
Thanks a lot guys i managed to flash the newest version of cwm using the link dserber was talking about. http://forum.xda-developers.com/showthread.php?t=1056847&highlight=clockworkmod# thats the link if anyone would like everything is working fine now
Yeah. That's the link. Good to hear you got it worked out!
Sent from my LG-P999 using XDA App
so just rooted my HOX last night using the new 2.20 method
finally got the bootloader unlocked and installed twrp
figured out how to use twrp and tried to install paranoid rom...
from what i read on another thread i was to extract the boot.img from the rom zip and flash that boot.img from the pc
then restart in recovery/twrp and install the paranoid rom zip
restarted my phone and got to the loading screen for the paranoid rom but just hags
restarted in recovery/twrp and restored my backup
for some reason the restore didn't work and got the endless boot
went back into twrp and did a factor wipe which i think also removed my backup (which didn't work the 1st time anyways)
so now what lol? help.. basically all i can do now is get into twrp - is there a stock backup file i can use to restore from twrp?
you always need to "fastboot flash boot boot.img" from bootloader anytime you are flashing a new rom or backup you are restoring, but you should already know this if you could read.
also make sure you flash gapps if you are flashing a aosp rom.
also NEVER factory reset in bootloader which will corrupt your sdcard.
what you need to do now is what i said above, then rewipe everything in twrp, mount your sdcard in twrp and copy a rom from your pc to your sdcard, unmount sdcard from pc then unmount from twrp, then you can install rom and gapps if its a aosp rom. if you didnt already "fastboot flash boot boot.img" you can reboot into bootloader and run the command instead of reboot system.
DvineLord said:
you always need to "fastboot flash boot boot.img" from bootloader anytime you are flashing a new rom or backup you are restoring, but you should already know this if you could read.
also make sure you flash gapps if you are flashing a aosp rom.
also NEVER factory reset in bootloader which will corrupt your sdcard.
what you need to do now is what i said above, then rewipe everything in twrp, mount your sdcard in twrp and copy a rom from your pc to your sdcard, unmount sdcard from pc then unmount from twrp, then you can install rom and gapps if its a aosp rom. if you didnt already "fastboot flash boot boot.img" you can reboot into bootloader and run the command instead of reboot system.
Click to expand...
Click to collapse
yeah i did the fastboot flash boot boot.img for the paranoid rom - i think my problem was that i left the boot.img in the zip
rezipping now and trying to mount
goot tip on the factor reset from bootloader to bad i already did it lol
i have never modified the actual rom zip before and have never had a problem. it just takes a little longer to install. i am a md5 junkie and never modify offical releases.
DvineLord said:
you always need to "fastboot flash boot boot.img" from bootloader anytime you are flashing a new rom or backup you are restoring, but you should already know this if you could read.
also make sure you flash gapps if you are flashing a aosp rom.
also NEVER factory reset in bootloader which will corrupt your sdcard.
what you need to do now is what i said above, then rewipe everything in twrp, mount your sdcard in twrp and copy a rom from your pc to your sdcard, unmount sdcard from pc then unmount from twrp, then you can install rom and gapps if its a aosp rom. if you didnt already "fastboot flash boot boot.img" you can reboot into bootloader and run the command instead of reboot system.
Click to expand...
Click to collapse
k think the sdcard is corrupt since i did do the factor reset from bootloader..
getting unable to mount sdcard
failed to do a system wipe because of this as well
:crying:
Plug it in to.computer.and enter twrp. When comp recognizes it, it'll ask to format the disk drive (sdcard).. then use instructions above
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
InflatedTitan said:
Plug it in to.computer.and enter twrp. When comp recognizes it, it'll ask to format the disk drive (sdcard).. then use instructions above
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
Click to expand...
Click to collapse
worked..
setting up cm10 right now but i dont have a recovery backup to fall back on
how do i go about doing this or should i just make a backup of the cm10 rom in twrp
probably in backup =)
Good job bro. Just *dont* do anymore factory resets in bootloader. Enjoy the Roms. Be careful with cm10 though. I been hearing of a few glitches in it. If anything arises, ask first and don't freak out
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
InflatedTitan said:
Good job bro. Just do do anymore facto resets in bootloader. Enjoy the Roms. Be careful with cm10 though. I been hearing of a few glitches in it. If anything arises, ask first and don't freak out
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
Click to expand...
Click to collapse
*don't *factory
DvineLord said:
*don't *factory
Click to expand...
Click to collapse
Lol, edited
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
So far so good with latest cm10 nightly.. Only crashed once when loading camera.
Now how do i get the default software back on my phone as a backup? Download 2.20 ruu.. Flash.. Then backup in twrp.. Then re flash cm10 from backup?
Sent from my One X using xda app-developers app
silent1643 said:
So far so good with latest cm10 nightly.. Only crashed once when loading camera.
Now how do i get the default software back on my phone as a backup? Download 2.20 ruu.. Flash.. Then backup in twrp.. Then re flash cm10 from backup?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Well. That's a HUGE pain, and I'll tell you why
If you wanted a backup of stock, you would have to do this
1. Relock Bootloader
2. Run RUU
3. Unlock Bootloader
4. Flash TWRP
5. Backup your ROM
6. Wipe your System
7. Factory Reset
8. Flash CM10 boot.img
9. Flash CM10
10. Flash Google apps
and after that.. you have a stock backup, and you are back on CM10.. Now what if you wanted to revert to stock? Well... Sigh
1. Wipe System
2. Factory Reset
3. Flash boot.img from your backup
4. Flash your backup
and now you are back to your stock backup..
What's easier though.
1. Download a stock rooted ROM
2. Wipe system
3. Factory Reset
4. Flash the boot.img from stock
5. Flash stock
6. Make a backup
From here you can either keep stock, or go back to CM10. but, if switching between CM10 and your stock backup, you should wipe system and factory reset. you will need to flash the boot.img every time you switch
Stock rooted rom? Isnt that the ruu
Or are you talking about sense roms based off stock.
I basically want to be able to flash back to stock if i ever sell the phone
Sent from my One X using xda app-developers app
silent1643 said:
Stock rooted rom? Isnt that the ruu
Or are you talking about sense roms based off stock.
I basically want to be able to flash back to stock if i ever sell the phone
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
A stock rooted rom is.. a stock ROM with root installed.. some of them have removed AT&T apps (what we call bloatware)
You can't get root on a stock ROM unless you unlock your bootloader, flash twrp, then flash su.zip
If you want to sell the phone.. just relock the boot loader and run the RUU
Thanks!
Enlightened... If i may how do i handle nightly builds with cm10?.. The rom itself can check for updates but i also see them posted on the url link.. Whats the best way to keep flashing night lies without setting up my settings each time.. Should also mention already backing apps up with titanium pro with Dropbox
Sent from my One X using xda app-developers app
silent1643 said:
Thanks!
Enlightened... If i may how do i handle nightly builds with cm10?.. The rom itself can check for updates but i also see them posted on the url link.. Whats the best way to keep flashing night lies without setting up my settings each time.. Should also mention already backing apps up with titanium pro with Dropbox
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
You can try an 'upgrade' which means you just flash overtop of your installation. I don't know if this will keep your settings. What it may do is break some stuff, if that's the case, do not report errors unless you have a clean install.
Your best bet is to find your favorite/stable nightly build and stick with it for a while
Good advice will stick with current until something major is updated in cm10..
But essentially i could make a backup of my current cm10 install and try other roms.. Then restore from backup to revert to cm10 with all my settings intact
Sent from my One X using xda app-developers app
silent1643 said:
Good advice will stick with current until something major is updated in cm10..
But essentially i could make a backup of my current cm10 install and try other roms.. Then restore from backup to revert to cm10 with all my settings intact
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Yes. But don't forget to flash the boot.img for your CM10 backup before flashing the backup.
The boot.img that came with the cm10 zip or the boot.img from the twrp cm10 backup
Sent from my One X using xda app-developers app
When trying to update my TF I accidentally flashed an incomplete Rom (got lazy and didn't check MD5...) Anyway, ever since then it ALWAYS boots into CWM (5.8.3.4) If I boot w/Vol DN and let it cold-boot then it will go into a fresh install and setup fine. However, on the next reboot it will go back to CWM 5.8.3.4 I have flashed the newer CWM 6.0.1.4 v2 but it won't "take" the install seems to go fine but it always boots back to the old CWM. I've also flashed other ROMS and they don't "take" either.
Confused...
mikeprachar said:
When trying to update my TF I accidentally flashed an incomplete Rom (got lazy and didn't check MD5...) Anyway, ever since then it ALWAYS boots into CWM (5.8.3.4) If I boot w/Vol DN and let it cold-boot then it will go into a fresh install and setup fine. However, on the next reboot it will go back to CWM 5.8.3.4 I have flashed the newer CWM 6.0.1.4 v2 but it won't "take" the install seems to go fine but it always boots back to the old CWM. I've also flashed other ROMS and they don't "take" either.
Confused...
Click to expand...
Click to collapse
Install different recovery... use easy flash and push either TWRP recovery or rogue recovery... personally I prefer TWRP recovery.. once you have a new recovery wipe everything ( internal memory also) and install a better ROM...
Sent from my Transformer using xda app-developers app
udupa82 said:
Install different recovery... use easy flash and push either TWRP recovery or rogue recovery... personally I prefer TWRP recovery.. once you have a new recovery wipe everything ( internal memory also) and install a better ROM...
Sent from my Transformer using xda app-developers app
Click to expand...
Click to collapse
I'll give TWRP a shot - thanks!
Try this
http://forum.xda-developers.com/showpost.php?p=29632231&postcount=3