Database Develop

[Q] CWM to TWRP preserving ROM & data

Hello everyone.
Forgive me for asking how to change my recovery from CWM to TWRP once again, but all threads I have read so far don't answer my question, which is:
I would like to keep my PAC-Android with all data and just change CWM 6.0.3.1 to TWRP so that I can try other ROMs such as ViperOne or Revolution HD.
Most threads I've read point to Goo Manager which should be able to install OpenRecoveryScript. That gives me the notification that "no recoveries were found for my device". The next option is to use fastboot. For that, I need to unlock the bootloader of my device, which means that I will [theandroidsoul / htc-one-m7-bootloader-unlock-guide OUTSIDE LINK DELETED]lose all ROM data, apps, private data, just everything[/URL]. Since it's possible to flash TWRP over CWM via Goo Manager, I think it should be possible to do this without deleting all data.
I would appreciate any help.
For those of you who are wondering why I want to lose my PAC-Android:
Speakerphone does not work (works fine in Skype though) and I would like to try it on a custom ROM which is closer to stock.

I hope I understand your query correctly..
1. First of all, since you are initially using CWM. Backup your current PACAndroid using CWM.
2. Flash TWRP using your existing CWM recovery.
a. Here's the flashable zip: https://www.dropbox.com/s/716uhr84madvvjl/TWRP_2.6.3.4_m7.zip
3. Flash any ROM (Viper or ARHD)
If you would like to revert to PACAndroid.
1. Flash CWM recovery using your previously installed TWRP.
2. Restore backup.

double_ofour said:
I hope I understand your query correctly..
1. First of all, since you are initially using CWM. Backup your current PACAndroid using CWM.
2. Flash TWRP using your existing CWM recovery.
a. Here's the flashable zip: (outside-url deleted)
Click to expand...
Click to collapse
hum, didn't know it was that easy. thanks a lot for that. (I already had openrecovery-twrp-2.6.3.4-m7ul.img, I haven't flashed anything but zips yet. What about those .img files?)
double_ofour said:
3. Flash any ROM (Viper or ARHD)
If you would like to revert to PACAndroid.
1. Flash CWM recovery using your previously installed TWRP.
2. Restore backup.
Click to expand...
Click to collapse
So, just to be clear, that means that by flashing TWRP I only change my recovery and I will still be able to boot PAC-Android and I will not lose any data. Then, I can create a TWRP-based backup of my PAC-Android and dispose of all CWM-related stuff?

Everything OK. I flashed TWRP and will stick to it. Backup done.
Thank you a lot!

No problemo amigo!.. Hey hit thanks!..

FYI, you could have flashed the .img file without even rebooting (if you are rooted). The TWRP web site even has instructions--it just requires a single shell command. What happens in the background is very simple--the data in the .img is written to the phone's recovery partition.
This is how I last upgraded TWRP--it just works. (The command is called "dd", but I won't bore you by giving the full instructions.)

[Q] HTC One wont boot after nandriod recovery

I've had my HTC one for a little over half a year and I have been running cynogenmod 10.1 on it with no problems until I decided to update it to 10.2.1. when i had finished doing that I started having problems with it running and the just randomly rebooting frequently so I went back into my recovery (twrp 2.5.0.0) and went to recover into my nandriod backup. After I wiped the phone and used the backup i restarted it and now my phone just sits on the HTC One loading screen.
I can still enter into the recovery and bootloader (1.44 s-on), adb does find it in its device list when its connected to the computer. also when I go to restart the recovery I get a message saying "your device appears to not be rooted install supersu now? This will root your device". It doesn't do anything when i do say install or not to install it and just restarts the device. I did have it rooted before so I'm not sure if the recovering of the old phones image removed the root?
Not quite sure what I may have done wrong as I'm still fairly new to rooting and all but I'm unsure as to where to go from here. I've been digging through threads on the HTC one forum and I feel like I may be over thinking what i need to do. I couldn't really find a direct answer and i don't want to accidentally make it worse.
so here i am any help would be appreciated.

vash3100 said:
I've had my HTC one for a little over half a year and I have been running cynogenmod 10.1 on it with no problems until I decided to update it to 10.2.1. when i had finished doing that I started having problems with it running and the just randomly rebooting frequently so I went back into my recovery (twrp 2.5.0.0) and went to recover into my nandriod backup. After I wiped the phone and used the backup i restarted it and now my phone just sits on the HTC One loading screen.
I can still enter into the recovery and bootloader (1.44 s-on), adb does find it in its device list when its connected to the computer. also when I go to restart the recovery I get a message saying "your device appears to not be rooted install supersu now? This will root your device". It doesn't do anything when i do say install or not to install it and just restarts the device. I did have it rooted before so I'm not sure if the recovering of the old phones image removed the root?
Not quite sure what I may have done wrong as I'm still fairly new to rooting and all but I'm unsure as to where to go from here. I've been digging through threads on the HTC one forum and I feel like I may be over thinking what i need to do. I couldn't really find a direct answer and i don't want to accidentally make it worse.
so here i am any help would be appreciated.
Click to expand...
Click to collapse
update your twrp version, 2.5.0.0 is very outdated. then flash latest cm11

alray said:
update your twrp version, 2.5.0.0 is very outdated. then flash latest cm11
Click to expand...
Click to collapse
Alright ill give it a try and let you know if it works but im still confused why my backup didnt work. Could the old version of twrp?

vash3100 said:
Alright ill give it a try and let you know if it works but im still confused why my backup didnt work. Could the old version of twrp?
Click to expand...
Click to collapse
Maybe. Did you backed-up every partition (boot, system and data)?
You could try to restore you back-up with the latest twrp, it might also help to clear cache.

vash3100 said:
Alright ill give it a try and let you know if it works but im still confused why my backup didnt work. Could the old version of twrp?
Click to expand...
Click to collapse
Its most likely that the old recovery is the issue. 2.7.0.0 has been released and why not CM11, which is in its snapshot stage?? And, your HBOOT and firmware are also extremely outdated. 1.44 was the HBOOT at launch. 1.56 is the latest

It took awhile but everything is working again. I guess my backup was corrupt or something because it still didnt work after i flashed the recovery to a newer version.

[Q] Stuck at CM recovery after accepting newest official software update

Hi, device is rooted, and clockworkmod recovery 6.0.4.5 installed.
ROM is JB, the official update from LG. Today device reported there is an update to the installed firmware.
I rebooted in CM recovery, took a nandroid backup, booted, and accepted to download the official update to my official JB rom. After downloading I was asked to reboot (in order to install), and the phone reboots to the CM recovery.
From there I don't know what to do. I have tried rebooting, but again find myself to the CM recovery. I have tried "reboot to bootloader" and get stuck at the LG boot screen logo with the message "Now Ready!" in tiny white letters on the upper left corner.
I would try "install zip" but I don't know where the downloaded update is (if it even is in an acceptable zip format)
Phone isn't bricked, I guess I can always restore from the recently taken backup, but I really would like to know if there is a way to install this update.
Thank you

http://forum.xda-developers.com/showthread.php?p=50645445
Could you please please please try to search the next time I've seen this question for probably 3-4 times
Sent from my LG-P880 using xda app-developers app

you can't ota over unlocked bl/cwm, you must flash update manually

moneyvirus said:
http://forum.xda-developers.com/showthread.php?p=50645445
Could you please please please try to search the next time I've seen this question for probably 3-4 times
Click to expand...
Click to collapse
You're right, but you know, sometimes you just can't nail the right keywords especially if its not your native language. I searched, but obviously not good enough.
Rudjgaard said:
you can't ota over unlocked bl/cwm, you must flash update manually
Click to expand...
Click to collapse
Sadly, this seems to be the case.. bummer.
Thanks everyone

Not even my nandroid backup can help me get to where I was before? So much for nandroid being the ultimate backup, a "snapshot image" of the device...
So, what if, I use CM recovery to install a custom rom, and then restore from my nandroid backup (being the official JB) ?

Flash with kdz flasher original ROM then flash cwm you can put back your backup. I think the problem starts that the update pushes something in the boot section that is expecting an other (read original) recovery . when you installed cwm it boots up cwm so that's why an nandroid backup doesn't work I think ( to be honest I'm not 100% sure this is correct)
Sent from my LG-P880 using xda app-developers app

I can't even flash cyanogenmod???
I downloaded latest stable build, copied it to sd card, selected it from the CM recovery ("install zip"), installed fine, reboot, still stuck at CM recovery!!!
What gives?

EPa said:
I can't even flash cyanogenmod???
I downloaded latest stable build, copied it to sd card, selected it from the CM recovery ("install zip"), installed fine, reboot, still stuck at CM recovery!!!
What gives?
Click to expand...
Click to collapse
Have you yet followed the advice and installed the KDZ?

Trying to avoid that, as it seems too much work for a phone that was working fine, and stuck to recovery due to some silly boot flag or something.
Saw it as a chance to try cyanogenmod. But it seems having CM recovery and the cyanogenmod rom on the sd card won't cut it! Talk about failure..

EPa said:
Trying to avoid that, as it seems too much work for a phone that was working fine, and stuck to recovery due to some silly boot flag or something.
Saw it as a chance to try cyanogenmod. But it seems having CM recovery and the cyanogenmod rom on the sd card won't cut it! Talk about failure..
Click to expand...
Click to collapse
I don't think you will have a choice. If you created the nandroid backup on your SD card then you aren't going to lose it, so just flash the KDZ, root again and install your backup, or accept the LG update and rebuild all your software again.

Yes, one thing is for sure. I had to install the KDZ to be able to proceed with anything..
It's just funny having a working CWM recovery and a cyanogen rom on the device and after flashing it, still not having a device that boots. A "recovery"/flash tool, should be able to "recover" from such a situation..

EPa said:
Yes, one thing is for sure. I had to install the KDZ to be able to proceed with anything..
It's just funny having a working CWM recovery and a cyanogen rom on the device and after flashing it, still not having a device that boots. A "recovery"/flash tool, should be able to "recover" from such a situation..
Click to expand...
Click to collapse
You can't blame the recovery. It is clearly stated many, many times that you should never attempt an official OTA update with a non-standard (rooted or recovery installed) device. On other devices you could even hard-brick AFAIK, so consider yourself lucky that you only had to reflash a KDZ and start again.

For restoring stock rom use this: http://forum.xda-developers.com/showthread.php?t=2682146 I can confirm it works and it is (very) easy.

Yes that's what I used and I also confirm it works and is very easy.

[Q] HTc one md5 mismatch, no stock rom access and custom rom leads to bootloop

I am very new to the entire rooting side of android and my first try at getting a custom rom went bad.
I have an htc one international variant. I successfully rooted it. After rooting i tried installing a custom rom called Android_Revolution_HD-One_62.0, which once installed via 'recovery-clockwork-touch-6.0.3.1-m7' gave the installation prompts. after following them it just gets stuck in an endless boot loop alternating between htc logo screen and few seconds of clockwork mod screen.
I cleared all data, and cache before trying to install the above mentioned rom,
I made a backup of my stock version using the backup feature on clockwork mod but after failing with the custom rom, i tried to restore the back up but it gave me md5 mismatch issue.
So now I can't fix that issue on my phone and neither is the adb commands able to find my device to fix the md5 mismatch.
Please help me anyway possible.
Thank you

2411247 said:
I am very new to the entire rooting side of android and my first try at getting a custom rom went bad.
I have an htc one international variant. I successfully rooted it. After rooting i tried installing a custom rom called Android_Revolution_HD-One_62.0, which once installed via 'recovery-clockwork-touch-6.0.3.1-m7' gave the installation prompts. after following them it just gets stuck in an endless boot loop alternating between htc logo screen and few seconds of clockwork mod screen.
I cleared all data, and cache before trying to install the above mentioned rom,
I made a backup of my stock version using the backup feature on clockwork mod but after failing with the custom rom, i tried to restore the back up but it gave me md5 mismatch issue.
So now I can't fix that issue on my phone and neither is the adb commands able to find my device to fix the md5 mismatch.
Please help me anyway possible.
Thank you
Click to expand...
Click to collapse
The ARHD thread says you need TWRP 2.6.3.3 recovery for 62.0. Try installing that, full wipe then reflash.

cr1960 said:
The ARHD thread says you need TWRP 2.6.3.3 recovery for 62.0. Try installing that, full wipe then reflash.
Click to expand...
Click to collapse
I am trying that out right now but it seems to always get stuck on the 'entering recovery' screen. I flashed TWRP 2.6.3.3 and erased cache after, but still this happens.

Clockworkmod Recovery Galaxy s3 problems

Well guys this is my first time on the forums. My phone is rendered near useless right now. A few days ago, i rooted my phone via towelroot. as a friend reccomended, i installed ROM manager and flashed clockworkmod recovery. I backed up my stock, perfect ROM with CWM and decided to try installing cyanogenmod 10.3.1......... it wouldn't install. I even tried other apps like ROM installer. Then i came across the handy dandy Cyanogenmod Installer. This seemed great, i didn't have to do anything except click a few buttons on my PC. as i was ready to enjoy a new custom ROM, the following message popped up, "Root access possibly lost. Fix?". I was given the options of "No" and "Yes - Fix root (/system/xbin/su)". i chose the second one, and waited for my device to boot. when it did, it was stock Touchwiz Android version 4.4.2, just like i had initially. what's more is my imei and bandwidth version were both "unknown" and i my sim card was undetected. I decided that technology had gotten the better of my and i tried to flash my old stock ROM back on. i found the file in recovery mode but it kept saying "no files found" whenever i clicked on it. I tried the cyanogenmod installer again, this time choosing "No", resulting in exactly the same scenario. At this point, I would be fine having the stock ROM since i have had such bad luck with the "developer's world" of Android.......... PLEASE HELP!!!!!

Another note:
ROM manager now is telling me that CWM is not installed, yet it is present in recovery mode......

EddyTeddy01 said:
Another note:
ROM manager now is telling me that CWM is not installed, yet it is present in recovery mode......
Click to expand...
Click to collapse
Have you tried installing some other recovery, like TWRP? You won't be able to install CM from it, but you should be able to install other roms.

touchbattle.mika said:
Have you tried installing some other recovery, like TWRP? You won't be able to install CM from it, but you should be able to install other roms.
Click to expand...
Click to collapse
How do I replace CWM with twrp? If I flash twrp, wouldnt CWM stay on my phone as default recovery?

EddyTeddy01 said:
How do I replace CWM with twrp? If I flash twrp, wouldnt CWM stay on my phone as default recovery?
Click to expand...
Click to collapse
follow the guide and replace your recovery easily. after flashing, what recovery you have flashed will be default recovery, i recommend philz, they are all downloadable in the guide

MaHo_66 said:
follow the guide and replace your recovery easily. after flashing, what recovery you have flashed will be default recovery, i recommend philz, they are all downloadable in the guide
Click to expand...
Click to collapse
Would I have to uninstall CWM? I'm just wondering if the file for CWM will still be on my phone. I'll check out the link.

EddyTeddy01 said:
Would I have to uninstall CWM? I'm just wondering if the file for CWM will still be on my phone. I'll check out the link.
Click to expand...
Click to collapse
it´s the best if you also do a format of internal sd in recovery before changing the recovery, because sometimes there are some folders left of it in interrnal memory and you cant delete it, do that if this will be the case. but i think Philz and CWM use same folder, so if you flash philz it will be okay if im correct otherwise you can always format internal sd afterwards
Edit: dont use rom manager for recovery actions, use recovery itself, much more reliable

MaHo_66 said:
follow the guide and replace your recovery easily. after flashing, what recovery you have flashed will be default recovery, i recommend philz, they are all downloadable in the guide
Click to expand...
Click to collapse
That guide made it possible for me to install all custom roms. Witz the recovery installed first it did not work. Thx