Database Info

cant load recovery

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

Strange TWRP problem, no OS detected etc. Boots fine to stock

I ran the causal root applet on a new SG3 on 4.1.2. Ran root, the unlock script and installed TWRP. Booted into recovery and I got the error for a locked bootloader. I used download mode to get back to the stock rom and then used E-Z unlock to unlock the bootloader. Was able to boot into recovery this time but TWRP read internal and external memory as 0mb, unable to make a backup, and gave a no OS error when went to reboot. I updated TWRP with TWRP manager but the problems are still persistent. Phone boots fine and reboots fine at the moment.
I'm not sure what to do now though. I'm at the point were I don't care if I get stuck with the OTA update but I'm afraid that will brick the phone. I'm not sure what went wrong with TWRP, since this is the second S3 I've rooted.
Any sugestions? I'm afraid to use odin or try anything else since the phone currently works fine. But I'd prefer to not have to sleep in fear it might force the OTA update while I'm asleep and wake up to a bricked phone.
I tried searching, the best I could find is that newer versions of TWRP can't read the memory on a 4.1.2 rom, but the problems were there when I originally started with the recommended version.
Thanks for any help anyone can give.

Try to use cwm or philz and see if you have the same issue.
Sent from my SCH-I535 using Tapatalk 2

Xx

BadUsername said:
Try to use cwm or philz and see if you have the same issue.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Can you install a different custom recovery over one using the causal applet? I was planning on trying to reinstall TWRP but I wasn't sure if I had to do it a certain way like through odin or Using the unified tool kit?
Thanks for the help so far!

Smogon said:
Can you install a different custom recovery over one using the causal applet? I was planning on trying to reinstall TWRP but I wasn't sure if I had to do it a certain way like through odin or Using the unified tool kit?
Thanks for the help so far!
Click to expand...
Click to collapse
No.
Download latest philz touch recovery d2lte zip, then flash it in recovery, then reboot recovery.
Then check and see if you're getting a similar error message.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
No.
Download latest philz touch recovery d2lte zip, then flash it in recovery, then reboot recovery.
Click to expand...
Click to collapse
I can't, recovery doesn't detect my internal or external memory. That's my main issue.

Smogon said:
I can't, recovery doesn't detect my internal or external memory. That's my main issue.
Click to expand...
Click to collapse
OK.
Then download the Odin version and flash through that. Then boot the phone into recovery.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
OK.
Then download the Odin version and flash through that. Then boot the phone into recovery.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'll try the second option, Thanks!

BadUsername said:
OK.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I tried CWM and the stock recovery through EZ, both gave the same error as TWRP, unable to mount /
I'm really confused as to whats wrong. At this point I don't care if I get stuck with the OTA 4.3, but I don't want to try to update it with the recovery still not reading either my SD cards.
Any Ideas?

Are you sure of your phone model? I believe it puts it on the screen in download mode and also on a sticker under the battery. I'm mostly curious because you mention that this is a new phone with 4.1.2. Are you trying older versions of cwm as well?
Sent from my SCH-I535 using XDA Premium 4 mobile app

Smogon said:
I ran the causal root applet on a new SG3 on 4.1.2. Ran root, the unlock script and installed TWRP. Booted into recovery and I got the error for a locked bootloader. I used download mode to get back to the stock rom and then used E-Z unlock to unlock the bootloader. Was able to boot into recovery this time but TWRP read internal and external memory as 0mb, unable to make a backup, and gave a no OS error when went to reboot. I updated TWRP with TWRP manager but the problems are still persistent. Phone boots fine and reboots fine at the moment.
I'm not sure what to do now though. I'm at the point were I don't care if I get stuck with the OTA update but I'm afraid that will brick the phone. I'm not sure what went wrong with TWRP, since this is the second S3 I've rooted.
Any sugestions? I'm afraid to use odin or try anything else since the phone currently works fine. But I'd prefer to not have to sleep in fear it might force the OTA update while I'm asleep and wake up to a bricked phone.
I tried searching, the best I could find is that newer versions of TWRP can't read the memory on a 4.1.2 rom, but the problems were there when I originally started with the recommended version.
Thanks for any help anyone can give.
Click to expand...
Click to collapse
by any chance did u try to setup dualboot? I have a similar issue where nothing gets mounted and o mb for storage, .only receovery i get to work is cwm. im pretty sure its a partition issue but idk. i tried flashing pit files for my phone but so far the issue remains.

xevildoerxx said:
by any chance did u try to setup dualboot? I have a similar issue where nothing gets mounted and o mb for storage, .only receovery i get to work is cwm. im pretty sure its a partition issue but idk. i tried flashing pit files for my phone but so far the issue remains.
Click to expand...
Click to collapse
No I just used the causal tool.
dpeeps74 said:
Are you sure of your phone model? I believe it puts it on the screen in download mode and also on a sticker under the battery. I'm mostly curious because you mention that this is a new phone with 4.1.2. Are you trying older versions of cwm as well?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm pretty sure, has all the verizon bloat and logos, also I'm pretty sure the causal applet bricks the international ones. I don't remember the version of twrp that the causal script flashed, but I tried that one, the most recent one, and 2.5 i think from EZ recovery. The stock recovery from EZ has the same issue now though which is what really confuses me. at the moment I have root dissabled and the bootloader is locked and its back with the stock recovery, it still says custom when i reboot the phone though.

New m8 wants to update

I just got my m8 and want to s-off but I'm traveling and won't be able to figure that out until I'm back on my pc next week. The update keeps prompting me to take it. Is it safe to do so? Sorry if this was already answered trying to figure out the best way to browse with tapatalk.
I don't have root or anything yet...
Sent from my HTC6525LVW using Tapatalk

I used Firewater's method for permanent root, s-off and custom recovery. If I allow my phone to update will I mess things up or lose root?

Same boat here... s-off, permanent root, TWRP
The update to 1.55 downloaded but when I tried to let it install it just rebooted my phone into TWRP and that was it. Rebooted back to system and I'm still on the 1.12.605.11 software. Checking software update status shows "Result: Update Failed,410"

N00bs. Lol. You need a stock recovery to flash an OTA. Also, I am s-off and I had a flashback to a stock recovery to flash the OTA . Everything is still fine and then I flashed back to a custom recovery no problem
Sent from my HTC One M8

Totally a noob here, How do you flash to a stock recovery?
Sent from my HTC6525LVW using Tapatalk

You guys need the stock recovery in order to install the OTA. It won't work with a custom recovery, it'll just boot to the custom recovery and not do anything. You can install the OTA with s off and root but you still need the stock recovery. You install the stock recovery the same way as you did the custom. Adb -> flashboot flash recovery *path of recovery*.
http://www.megafileupload.com/en/file/520717/stockrecovery-img.html
There are also videos on YouTube on flashing recoveries to the m8 if you need more help.
Sent from my HTC6525LVW using Tapatalk

Justintoxicated said:
I just got my m8 and want to s-off but I'm traveling and won't be able to figure that out until I'm back on my pc next week. The update keeps prompting me to take it. Is it safe to do so? Sorry if this was already answered trying to figure out the best way to browse with tapatalk.
I don't have root or anything yet...
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
You can install the update, and when you have the chance you can s-off using the weaksauce/supersu/firewater method. I picked up a new M8 a couple nights ago and took the update, and afterwards did the temproot/firewater method and it worked just fine. Hope this helps.

I flashed stock recovery and tried the OTA and it failed twice. I can't seem to get it on my phone through any of the methods for some reason.

In order to install update, you need to have STOCK recovery and STOCK Rom....NOT debloated or with mods....STOCK.
Again, you need STOCK recovery using a STOCK Rom.
If you have modified the system in anyway, it WONT work until you put it back to STOCK.
Sent from my HTC6525LVW using xda app-developers app

^you can have bloatware frozen and it'll work, just can't be removed.
Sent from my HTC6525LVW

dadams312 said:
I flashed stock recovery and tried the OTA and it failed twice. I can't seem to get it on my phone through any of the methods for some reason.
Click to expand...
Click to collapse
z-man79 said:
Totally a noob here, How do you flash to a stock recovery?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
KnightDavid said:
Same boat here... s-off, permanent root, TWRP
The update to 1.55 downloaded but when I tried to let it install it just rebooted my phone into TWRP and that was it. Rebooted back to system and I'm still on the 1.12.605.11 software. Checking software update status shows "Result: Update Failed,410"
Click to expand...
Click to collapse
z-man79 said:
I used Firewater's method for permanent root, s-off and custom recovery. If I allow my phone to update will I mess things up or lose root?
Click to expand...
Click to collapse
No need to take ota. Ota us our enemy. Lol. The ota has been pulled an you can simply flash the firmware an that's half of the ota an then flash a stock Rom based off 1.55 or install the backup that was posted of a pure stock 1.55 Rom. After those 2 things you will have the full ota. New radios everything.. flashing a stock recovery taking ota flashing back is not needed.
Sent from my HTC6525LVW using XDA Premium 4 mobile app

Thanks guys it was annoying having that update keep popping up and no real computer to lookup info or soff. As for getting updates after roming the phone usually just wait for authors to incorporate the updates. But I did not realize you can't have two recoveries like you can on Motorola phones which is good to know.
Sent from my HTC6525LVW using Tapatalk

New to android here.
I rooted the device with WeakSauce and use Firewater for S-Off. I didn't flash any custom recoveries. I did freeze some apps with Titanium Backup. If I do the OTA, 1) will it work? and 2) will it remove my root and/or s-off?

NoFanboy said:
You guys need the stock recovery in order to install the OTA. It won't work with a custom recovery, it'll just boot to the custom recovery and not do anything. You can install the OTA with s off and root but you still need the stock recovery. You install the stock recovery the same way as you did the custom. Adb -> flashboot flash recovery *path of recovery*.
megafileupload.com/en/file/520717/stockrecovery-img.html
Click to expand...
Click to collapse
For clarification, after flashing the stockrecovery.img you posted and installing the update, there should be no problem flashing back to CWM recovery after the fact?
Thank you for your help and your time!

skivvies said:
For clarification, after flashing the stockrecovery.img you posted and installing the update, there should be no problem flashing back to CWM recovery after the fact?
Thank you for your help and your time!
Click to expand...
Click to collapse
Nope there will be no problem.
Sent from my HTC6525LVW using Tapatalk

richii0207 said:
In order to install update, you need to have STOCK recovery and STOCK Rom....NOT debloated or with mods....STOCK.
Again, you need STOCK recovery using a STOCK Rom.
If you have modified the system in anyway, it WONT work until you put it back to STOCK.
Sent from my HTC6525LVW using xda app-developers app
Click to expand...
Click to collapse
All your big words confuse me...will it work with custom rom's and recoveries?

I don't remember ever having to have stock recovery and stock rom for my old DNA to take an update. Normally devs would update their rom with the updates and all we had to do was fastboot flash the new radio.

NoFanboy said:
You guys need the stock recovery in order to install the OTA. It won't work with a custom recovery, it'll just boot to the custom recovery and not do anything. You can install the OTA with s off and root but you still need the stock recovery. You install the stock recovery the same way as you did the custom. Adb -> flashboot flash recovery *path of recovery*.
http://www.megafileupload.com/en/file/520717/stockrecovery-img.html
There are also videos on YouTube on flashing recoveries to the m8 if you need more help.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
So I flash the file you linked to, thank you but when I try to get into recovery I get a red triangle with an exclamation point in it. Seemed pretty straight forward.

sfreemanoh said:
All your big words confuse me...will it work with custom rom's and recoveries?
Click to expand...
Click to collapse
Lol, I had to. I just know someone is going to start a thread saying "update won't work, it just boots into twrp"
Sent from my HTC6525LVW using xda app-developers app

z-man79 said:
So I flash the file you linked to, thank you but when I try to get into recovery I get a red triangle with an exclamation point in it. Seemed pretty straight forward.
Click to expand...
Click to collapse
Hold the volume up button and pressed the power button to get to the recovery menu.

[Q] ******Please help I bricked my N5******

Hi guys,
I have recently rooted my device and flashed a custom ROM (CyanogenMod), after 2 days there was an update for CM. Update was installed perfectly but then after the reboot "settings" on the phone stopped working. closed unfortunately. I went into recovery mode to flash the previous ROM. I am using "TWRP" recovery tool. This where I have done the blunder, I have wiped the system data and all of it. At the moment phone doesnt have any ROM to boot on. Please suggest me to how to flash the factory ROM or any other ROM. Can't really do anything as the phone wont boot up in regular mode (GOOGLE) thats all.
HELP HELP HELP HELP HELP HELP HELP HELP HELP

Jz flash any cm rom zip just a soft brick easily recoverable

Shibazeet said:
Hi guys,
I have recently rooted my device and flashed a custom ROM (CyanogenMod), after 2 days there was an update for CM. Update was installed perfectly but then after the reboot "settings" on the phone stopped working. closed unfortunately. I went into recovery mode to flash the previous ROM. I am using "TWRP" recovery tool. This where I have done the blunder, I have wiped the system data and all of it. At the moment phone doesnt have any ROM to boot on. Please suggest me to how to flash the factory ROM or any other ROM. Can't really do anything as the phone wont boot up in regular mode (GOOGLE) thats all.
HELP HELP HELP HELP HELP HELP HELP HELP HELP
Click to expand...
Click to collapse
adb push a rom zip onto your sdcard and flash it in recovery
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
adb push a rom zip onto your sdcard and flash it in recovery
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Can you sideload in TWRP?' It's even faster than pushing for the unpatient folk like me. lol
And yeah jd I still have the Rocket.

that was his first and only post, i bet he wont be back. sounds like a root toolkit child.

How?
Having said that I cannot detect the phone in the PC, how can i put the ROM in a folder?

Guess what? He's back!
@Shibazeet
You need to follow this thread to setup adb/fastboot: http://forum.xda-developers.com/showthread.php?t=2588979

Use NRT nexus root toolkit 1.8.4
& recommend to install stock image nexus from official google website , just search " stock image nexus 5 "
SORRY FOR MY BAD EN !!
Sent from my Nexus 5 using XDA Premium 4 mobile app

http://forum.xda-developers.com/showthread.php?t=2277112
Use this guide to setup fastboot. Then download the factory image to your computer. Use fastboot to install it and any other future roms.

Lokke9191 said:
http://forum.xda-developers.com/showthread.php?t=2277112
Use this guide to setup fastboot. Then download the factory image to your computer. Use fastboot to install it and any other future roms.
Click to expand...
Click to collapse
My friend, you don't use fastboot to flash "ROMs".

Sorry woke up 5min before writing that. Running on 4hrs sleep now. Meant use fastboot to install stock image, flash a recovery. Then use custom recovery to flash future roms. Just pointing him in the right direction. With a little reading, he'll figure it out.

Boot recovery.img from phone

Is it possible to boot a recovery image from the phone without flashing? If not is it ok to reflash backups of stock recovery? Tnx

and313 said:
Is it possible to boot a recovery image from the phone without flashing? If not is it ok to reflash backups of stock recovery? Tnx
Click to expand...
Click to collapse
It is possible via android sdk. You can use command: fastboot boot twrp.img
where twrp.img is the name of the recovery that you downloaded and not twrp.img

Alexandar92zr said:
It is possible via android sdk. You can use command: fastboot boot twrp.img
where twrp.img is the name of the recovery that you downloaded and not twrp.img
Click to expand...
Click to collapse
Yes i know but i would like to do it from the phone... There are tons of flash recovery apps but no boot recovery apps

ROM manager used to do it years ago until people got into trouble with it and it was removed.
If you intend on flashing things AMD backing up, flash a recovery. If you're not willing to flash a recovery, don't modify your phone
Sent from my Nexus 5 using Tapatalk

and313 said:
Yes i know but i would like to do it from the phone... There are tons of flash recovery apps but no boot recovery apps
Click to expand...
Click to collapse
Try flashify

AndreIrawan97 said:
Try flashify
Click to expand...
Click to collapse
That flashes recovery. Clue is in the name.
Sent from my Nexus 5 using Tapatalk

rootSU said:
ROM manager used to do it years ago until people got into trouble with it and it was removed.
If you intend on flashing things AMD backing up, flash a recovery. If you're not willing to flash a recovery, don't modify your phone
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The problem with flashing is that you loose the ota update ability. That's why i would like to keep the stock recovery and just boot into cwm when i need it... But i guess i can restore the stock recovery via flashify before the ota is being installed so thats a solution... I just dont like flashing this stuff via apps

and313 said:
The problem with flashing is that you loose the ota update ability. That's why i would like to keep the stock recovery and just boot into cwm when i need it... But i guess i can restore the stock recovery via flashify before the ota is being installed so thats a solution... I just dont like flashing this stuff via apps
Click to expand...
Click to collapse
1) you do not lose OTA update ability with custom recovery. Read "OTA help-desk" available via my signature
2] what's the big deal about OTA? Its the worst way of updating available to everyone. Why bother? If you rely on OTA, remain unrooted, unmodified. Rooting is not for you.
Sent from my Nexus 5 using Tapatalk

Ugh lol OK, so worried about the ota? No worries, flash whatever recovery you want twrp,cwm,philz whatever floats your boat. Then when your ota comes out use Rashr to reflash stock recovery so you can update(you have to be on stock obviously).
I've done this numerous times, works every time.
Sent from my Nexus 5 using XDA Free mobile app

todorcim said:
Ugh lol OK, so worried about the ota? No worries, flash whatever recovery you want twrp,cwm,philz whatever floats your boat. Then when your ota comes out use Rashr to reflash stock recovery so you can update(you have to be on stock obviously).
I've done this numerous times, works every time.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
One of the problems with OTA is the slow delivery and partial nature.
If I wasn't rooted, i'd always update using factory images. But since I am, the best way is for flash a pre-rooted stock ROM via recovery. They're usually available within an hour of the factory image becoming available
Sent from my Nexus 5 using Tapatalk

rootSU said:
One of the problems with OTA is the slow delivery and partial nature.
If I wasn't rooted, i'd always update using factory images. But since I am, the best way is for flash a pre-rooted stock ROM via recovery. They're usually available within an hour of the factory image becoming available
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Agreed 100%, I normally stay rooted,this most recent preview though I'm staying stock. After running L for the last couple months its hard to go back to KitKat(I've tried several times). I have no intention of flashing another rom atm, I'll worry about root after the 3rd.
As for buddy worrying about the ota, really you have two choices.
#1 root and flash a recovery then wait for someone to post a root stock ROM
#2 wait for the ota
The only real benefit I see in waiting for the ota is you will probably get to keep all your apps on your phone. Me personally? I'd just fastboot the preview and wait till the 3rd.
Materialized From The DarkSide