[Q] Why ClockWorkMod Recovery not available despite installed ROM Manager? (Nexus S) - Nexus S Q&A, Help & Troubleshooting

Dear all,
I want to upgrade my Nexus S from CyanogenMod-7.1.0-NS to the latest cm-10.0.0.-crespo.zip. I have ROM Manager v5.0.2.4 installed.
It is the first upgrade since I installed CyanogenMod originally, please bear with me. ROM Mgr says I have CW Recovery 6.0.1.0 installed,
but starting into fastboot, the CW Recovery image is not found. Therefore I also cannot make backups.
Q1: I do not understand where did the Recovery img go? I never changed anything. I did 2-3 backups in the past, nothing else.
I thought that ROM Manager is EXACTLY there to help doing all this, managing the different ROMs (recovery and others), backups, etc.
What am I missing here?
Q2: If someone could explain, what is going on and how I get a working CW Recovery running to do a full backup before upgrading,
I would be very happy... Q3: I hope I do not have to go through the whole SDK installation thing again!?
Thanks a lot!
digisus

I am not sure what is happening with ROM Manager, Hopefully somebody else can throw some light on that.
In regards to installing CWM 6.0.1.0, try flashing the img file through fastboot using fastboot command, flash recovery recovery.img where the"recovery.img" will be your file name.
Once installed then you can do your backup and the installing of new ROM's without any issues.

digitalguy13 said:
I am not sure what is happening with ROM Manager, Hopefully somebody else can throw some light on that.
In regards to installing CWM 6.0.1.0, try flashing the img file through fastboot using fastboot command, flash recovery recovery.img where the"recovery.img" will be your file name.
Once installed then you can do your backup and the installing of new ROM's without any issues.
Click to expand...
Click to collapse
Thanks! Q1: To use fastboot I need to establish the whols Android SDK environment on the PC again, right? Q2: Or can I just copy the recovery img to the device and start it somehow via fastboot mode? I really would prefer not to set up the whole SDK environment again just to do a backup.
Q3: Anyone can shed some light on why ROM Manager is not working as expected?
Alternative: I made a manual backup by copying all files from the device to the PC. I know I am missing all the apps this way. Q4: What else is not covered by this backup method?
Thanks a lot for your help!
digisus

You will need the SDK tools directory to do the flash using fastboot.
With regards to backing up your apps, just use Titanium Backup.

Related

Boots into recovery after installation, then gives triangle exclimation

I've now flashed the recovery using both rom manager and fastboot 4 times, and each time it works fine the very first time after, but then the 2nd and succeeding times after lead to the little android and then the triangle and exclamation point. This is with the latest clockwork 3.1.0.1 on a Nexus S 4G. I have no idea what the problem could be and I'm hella frustrated.
Thanks for any help you can provide in advance.
http://forum.xda-developers.com/showthread.php?t=856999
Trying this, will update with results after I just try flashing cyanogen.
EDIT: UPDATE problem solved after flashing cyanogen. Sorry for taking up extra space. Here's the fix incase others were searching.
-Flash recovery
-Enter recovery while it's still working, nandroid backup, wipe, flash cyanogen.
-Done
If that doesn't work use the commands from that link.
The problem is solved cause CM fixed it for you.
If you don't have a ROM fixing it for you (eg stock Android), you need to rename the install-recovery.sh inside /system/etc to something else to make a recovery stick through reboots. Renaming system data requires root/super user.
The order would be:
Flash recovery
Flash su.zip
Boot into Android
Use a root explorer (eg Super Manager or Root explorer) to rename the file above
Flash recovery again

Restroing clockwork recovery on i9023 ??

Hi everyone,
I was using latest cyanogen on my i9023 till today and today I tried to go back to stock ROM, I downloaded a 100% stock nandroid backup and restored it with CWR, but not if I try to boot in to it, stucks in black in screen after the boot animation.
I tried to restore the cyanogen again by going back to recovery menu, but it seems that restoring the nandroid backup replaced it with a sort of more limited recovery menu (Android system recover <3e>). My bootloader is still unlocked, but I think I lost the root access...
How can i get the CWR back? I tried to install the img from computer, but I can't get to the phone at all... "adb devices" in terminal doesn't give me anything...
any help is greatly appreciated!
I just answered a question about this haha
I'm gonna assume you have a fastboot binary installed in ur tools folder of the android sdk?
if you do, then
try this:
1. Grab a recovery image from one of the threads or here:
http://wiki.cyanogenmod.com/wiki/Nex...Recovery_Image
2. Then, put it in your AndroidSDK tools folder, and go into terminal or command prompt and cd into that tools folder
3. fastboot flash recovery ____.img
(the ___ is the name of the recovery image file)
4. reboot ur phone into recovery and run a nandroid of some sort.
see if that works haha
THANK YOU!!
It worked out perfectly!!
thx!
this worked for me 2.

Multiple recoveries installed

I'm screwed. I attempted to install an updated TWRP, so i selected that option in ROM Toolbox Pro. Everything installed correctly (TWRP 2.7??). I decide let me see if TWRP installer will replace that with the updated 2.8.5. I run TWRP installer and it installs correctly. My assumption was that the TWRP installer would overwrite the ROM Toolbox version. Well, i reboot into the 2.8.5 recover (like it suggested) and i hit Reboot and then it reboots into 2.7. From there it thinks there is no OS installed. Rebooting from there just reboots me back in 2.7 recovery. I can get into Fastboot, and then back in 2.8.5 recovery. I flashed a new ROM, but that didn't fix it. I attempted to flash an RUU but i can't seem to get that working either. Am I completely screwed and should i call insurance on it?
Help me XDA, you're my only hope.
theoden144 said:
I'm screwed. I attempted to install an updated TWRP, so i selected that option in ROM Toolbox Pro. Everything installed correctly (TWRP 2.7??). I decide let me see if TWRP installer will replace that with the updated 2.8.5. I run TWRP installer and it installs correctly. My assumption was that the TWRP installer would overwrite the ROM Toolbox version. Well, i reboot into the 2.8.5 recover (like it suggested) and i hit Reboot and then it reboots into 2.7. From there it thinks there is no OS installed. Rebooting from there just reboots me back in 2.7 recovery. I can get into Fastboot, and then back in 2.8.5 recovery. I flashed a new ROM, but that didn't fix it. I attempted to flash an RUU but i can't seem to get that working either. Am I completely screwed and should i call insurance on it?
Help me XDA, you're my only hope.
Click to expand...
Click to collapse
To solve this, you could get phone into Fastboot and flash Dottat's RUU for the M8 - he made several versions.
For sure, add HTC_Fastboot.exe to your ADB folder and use it, NOT regular fastboot.
It will overwrite your previous recovery with stock and fix your phone. Then later, you could flash TWRP 2.8.7 thru Fastboot.
I put Dottat's RUU on my external SD card and it loaded, however, whenever it goes to reboot, it still goes back into the wrong recovery.
It's probably not necessary to run an RUU. You incorrectly flashed the new recovery to the wrong partition. Flash the new recovery VIA FASTBOOT, boot into it through the bootloader screen, and either flash a rom or restore a backup and you should be good to go. You definitely don't need to be worrying about an insurance claim for now.
Edit: by VIA FASTBOOT I mean with the command fastboot flash recovery <nameofrecoveryfile>.img
cntryby429 said:
It's probably not necessary to run an RUU. You incorrectly flashed the new recovery to the wrong partition. Flash the new recovery VIA FASTBOOT, boot into it through the bootloader screen, and either flash a rom or restore a backup and you should be good to go. You definitely don't need to be worrying about an insurance claim for now.
Edit: by VIA FASTBOOT I mean with the command fastboot flash recovery <nameofrecoveryfile>.img
Click to expand...
Click to collapse
I would flash firmware or ruu, if indeed he flashed recovery to wrong partition, that partition needs the correct one which firmware wlil do, and ruu will 100% do.
Personally I'd run ruu, go to stock recovery and run a factory reset.
theoden144 said:
I put Dottat's RUU on my external SD card and it loaded, however, whenever it goes to reboot, it still goes back into the wrong recovery.
Click to expand...
Click to collapse
Gotta use ADB and HTC_Fastboot.exe
Thanks for all the tips. I tried re-installing the old ROM after I ran the RUU and it worked. Hopefully it cleared out the incorrect recovery. Lesson learned: don't use apps to update the recovery!
Again thanks for all the help!
theoden144 said:
Thanks for all the tips. I tried re-installing the old ROM after I ran the RUU and it worked. Hopefully it cleared out the incorrect recovery. Lesson learned: don't use apps to update the recovery!
Again thanks for all the help!
Click to expand...
Click to collapse
Twrp manager is not a safe way to flash recovery because they aren't flashing by block name yet. They are still hard-coded to block number. The partitions have changed during ota already...so the app does hose things up a bit.
Sent from my Nexus 6 using Tapatalk

P5100 shows TWRP logo and resets

I just flashed many different versions of TWRP downloaded from their site(I got only the ones compatible with my P5100). After successfully flashing them all through Odin, I can't boot into recovery. The TWRP logo screen is shown and after 2 seconds the device reboots. I followed many guides, and they were all similar in this particular process. Am I missing something, or could there be anything wrong with my unit?
light401 said:
I just flashed many different versions of TWRP downloaded from their site(I got only the ones compatible with my P5100). After successfully flashing them all through Odin, I can't boot into recovery. The TWRP logo screen is shown and after 2 seconds the device reboots. I followed many guides, and they were all similar in this particular process. Am I missing something, or could there be anything wrong with my unit?
Click to expand...
Click to collapse
did you also installed a rom??
No. I'm running the stock rom, no root. I just wanted to get the twrp installed because I need to copy my personal files to an sd card. My stock rom is rebooting itself after completing the normal system startup. I can barely open any app. So I need to backup my files and do a factory reset. Any ideas? Thanks!
I think you need to get rid of TWRP and root the stock ROM, then flash TWRP using an app running on your tablet. Do not use a PC to flash the recovery. Also, if you are installing a zip, you must do it on the device, not through your PC.
Ka-B00M said:
I think you need to get rid of TWRP and root the stock ROM, then flash TWRP using an app running on your tablet. Do not use a PC to flash the recovery. Also, if you are installing a zip, you must do it on the device, not through your PC.
Click to expand...
Click to collapse
That doesn't make sense. Odin exists for the exact purpose of flashing through a PC, in case your recovery or anything gets damaged.

Need help recovering my phone from bootloop after trying to update custom rom

Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Edit: I ended up fixing my own issue by ADB flashing on a different release of TWRP, and then installing fcrypt disabler after the rom but before everything else.
Sanarise said:
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Click to expand...
Click to collapse
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Simoom Sadik said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
Unfortunately, I can't.
Trying to boot into TWRP just gets stuck on the 'Redmi' boot logo.
I just remembered that you can install TWRP over ADB, and that Peter's one says it works even when the system partition is empty, so maybe the issue is the TWRP I installed and could possibly undo this part of the issue over ADB.
It won't fix the issue preventing my from updating my rom, but recovery only is still better than a soft brick.
Edit: That worked, i've put Peter's TWRP back on, and it's launching into recovery mode/TWRP again now
twrp not boot after successfully flash in this rom
Sanarise said:
Unfortunately, I can't.
Trying to boot into TWRP just gets stuck on the 'Redmi' boot logo.
I just remembered that you can install TWRP over ADB, and that Peter's one says it works even when the system partition is empty, so maybe the issue is the TWRP I installed and could possibly undo this part of the issue over ADB.
It won't fix the issue preventing my from updating my rom, but recovery only is still better than a soft brick.
Edit: That worked, i've put Peter's TWRP back on, and it's launching into recovery mode/TWRP again now
Click to expand...
Click to collapse
flash latest twrp download from github, install twrpbuilder img twrp ,it boot fine and you will copy your data to pc and then install any other twrp img which u want , dont wipe anything from phone before phone boot.flash only original twrp builder 3.2.3.1 official,it boot only on latest updates.
Why nobody use orangefox?
is your issue solve or not tell,
Simoom Sadik said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
if your problem is not solve then tell me you need to flash a fastboot rom first with save user data.bat file and when it installed then you can install twrp builder 3.2.1. and then boot to twrp this methods working fine,if you recently flashed any android 10 rom then first you need to flash a miui fastboot rom,or flash it via command mode direct only 3 files
first click on extract a fastboot rom and copy boot system and vender file with flash.all bat file and make a new folder then click on flash.bat save user data file to flash these images
or you can do this manually
fastboot flash system system.img
fastboot flash vender vender.img
fastboot flash boot boot.img
then reboot device to fastboot again
now flash latest official twrp builder 3.2.3.1 img twrp and take all your data backup,
in fastboot flash latest miui do not downgrade direct otherwise you lost your data,
after this if you sucess then you can flash your old rom which is running before issue of boot loop of redmi logo
it will deincrypt your data safely and then root device and boot normally, if you lost anything then contact me with mail or whatsapp i will help you,7009197673 india
and this twrp work on all version from chines to global beta stable and indian stable
joke19 said:
Why nobody use orangefox?
Click to expand...
Click to collapse
In the end, I did try orangefox, and it might have been part of why it worked.
However, the crDroid installation instructions specifically mentions using Peter's TWRP, so I initially used that one.
anmoltinder said:
if your problem is not solve then tell me you need to flash a fastboot rom first with save user data.bat file and when it installed then you can install twrp builder 3.2.1. and then boot to twrp this methods working fine,if you recently flashed any android 10 rom then first you need to flash a miui fastboot rom,or flash it via command mode direct only 3 files
Click to expand...
Click to collapse
Thank you for the effort you put into typing up a guide to help me, but I ended up fixing my own problem.
I was able to use fastboot to flash on a better TWRP release, and then get the rom to install properly by installing fcrypt-disabler just after it.
Sanarise said:
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Edit: I ended up fixing my own issue by ADB flashing on a different release of TWRP, and then installing fcrypt disabler after the rom but before everything else.
Click to expand...
Click to collapse
help.I woke up yesterday and I turned on my phone and it is stuck on the Mi logo.All i can do is get it to fastboot thing.It seems like you and I have the same problem and I would love to have some help from you
Fcsubxrhi said:
help.I woke up yesterday and I turned on my phone and it is stuck on the Mi logo.All i can do is get it to fastboot thing.It seems like you and I have the same problem and I would love to have some help from you
Click to expand...
Click to collapse
If you can access fastboot, then flash TWRP.... Enter recovery, wipe your system partitions and then flash the Stock MIUI ROM or use the MiFlash tool. Make sure you aren't flashing an older version of the ROM than the onle already installed.
CongestedHangman said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
I have the same problem that stated after installing the update for derpfest and I can boot into twrp. Any solution for me?

Categories

Resources