Thinking about switching my recovery from Twrp 2.7.0.1 to Philz touch. no current cool looking themes for Twrp,so just wanna check out Philz. I do have a couple questions though hopefully someone can answer....
1) Should i restore from my custom rom on Twrp to my stock backup i made before switching Recoveries?
2)when i switch Recoveries, do my backups delete on twrp? i know the backups on twrp won't carry over on philz but, if i do not like philz and decide to go back to twrp will all my backups be there?
3)Am i screwed if the philz recovery fails and something messes up? or will twrp still be there.
Thanks for any help.
1) You dont need to be on any certain rom, you just need to fastboot flash what ever recovery you want.
2) Your backuls will still be on your storage untill you delete them.
3) If philz dosent flash right, it may not boot to recovery or you may be left with twrp. But either way you can just fastboot flash back to the twrp you were on before.
The Flashify app works great for switching recoveries too. Just remember to check your md5 before you fastboot flash anything. Bad things can happen if you fastboot flash a bad img.
Sent from my HTC6525LVW using Tapatalk
disconnecktie said:
The Flashify app works great for switching recoveries too. Just remember to check your md5 before you fastboot flash anything. Bad things can happen if you fastboot flash a bad img.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I only use fastboot. If your flash fails, just flash it again. Philz is the best, imo. Just put it in fastboot mode then "fastboot flash recovery recovery.img" and you are done(where recovery.img is the name of your image file, ijust switch all my current ones to recovery.img when i dump them into my adb folder and erase the old one).
Related
I for some reason can't get the stock recovery to flash the root file or any stock firmware. Also I can't get it to change recoveries for some reason I've tried in terminal with a few different ones and tried flashing the stock one also but it won't change. Does anything know how to fix this? Is there a back to stock thing I can flash it? I've been searching for days with no luck. Thanks
Sent from my X9006 using XDA Free mobile app
You have to flash the latest stock recovery! They patched the stock recovery and hashed for that!
Flash a custom recovery and make a nandroid backup. Save your backup for security reasons to your pc then install coloros completely new from 1.2.1and only update it with ota to 1.2.4 . Now use fastboot to boot from a custom recovery like Philz.(fastboot boot recovery.img)
Recovery.img should be replaced with the name of your recovery. Twrp won't work for this plan!, cause it don't backs up the recovery. Now make again a backup. Save the recovery.img from backup safely. Now restore your old backup and flash the captured stock recovery. Tada now your ota update should work fine!
Cheers
got it thanks a lot!! got root and that custom recovery worked! thanks again!!
Zoltan-X said:
You have to flash the latest stock recovery! They patched the stock recovery and hashed for that!
Flash a custom recovery and make a nandroid backup. Save your backup for security reasons to your pc then install coloros completely new from 1.2.1and only update it with ota to 1.2.4 . Now use fastboot to boot from a custom recovery like Philz.(fastboot boot recovery.img)
Recovery.img should be replaced with the name of your recovery. Twrp won't work for this plan!, cause it don't backs up the recovery. Now make again a backup. Save the recovery.img from backup safely. Now restore your old backup and flash the captured stock recovery. Tada now your ota update should work fine!
Cheers
Click to expand...
Click to collapse
mr2guy18 said:
got it thanks a lot!! got root and that custom recovery worked! thanks again!!
Click to expand...
Click to collapse
How did you get stock 2.0 to your phone?
I've HTC dev bootloader unlocked desire hd with custom recovery. I've tried flashing boot.img (from rom.zip) in fastboot before and after flashing rom in recovery mode. The phone gets past htc logo screen and then goes blank with back light on and stays there forever. I've tried 4 different roms. The only rom I was able to flash was CM7.
The phone is currently at h-boot 2.00.0029, is this why I can't flash new roms?
Any help is really appreciated
tt33333 said:
I've HTC dev bootloader unlocked desire hd with custom recovery. I've tried flashing boot.img (from rom.zip) in fastboot before and after flashing rom in recovery mode. The phone gets past htc logo screen and then goes blank with back light on and stays there forever. I've tried 4 different roms. The only rom I was able to flash was CM7.
The phone is currently at h-boot 2.00.0029, is this why I can't flash new roms?
Any help is really appreciated
Click to expand...
Click to collapse
Update your recovery.img to either of following;either one is good. But make backup of any rom you're on so that you may revert it back in future.
-TWRP 2.7.1.0
-Philz touch CWM
-4EXT Recovery Touch 1.0.0.6 RC 3
By the way which four roms you've tried? if recovery is up-to-date then phone should boot normally.
I have already tried philz touch and twrp. One thing I noticed was when i did a backup in recovery and tried restoring it and always get a md5 error. The same issue with different recoveries and on multiple tries. So I just flashed system.img and boot.img to get my phone back to stock rom.
Thanks
tt33333 said:
I have already tried philz touch and twrp. One thing I noticed was when i did a backup in recovery and tried restoring it and always get a md5 error. The same issue with different recoveries and on multiple tries. So I just flashed system.img and boot.img to get my phone back to stock rom.
Thanks
Click to expand...
Click to collapse
Strange....
Well unmark md5 check on restore. And clear cache/dalvic before rebooting it,Let's see how it goes.Also want to know which perticular rom you've tried so far where you were facing this issue. Also did you format devlog partition before installing CM11 nigthlies 20140618 onwards? If not then try doing so and let me know where you gets stuck?
I'm also S-ON where most other already made S-OFF so feel free to ask me. I'll help as much as i know :good:
Still no luck, it basically does the same thing for all roms. HTC logo shows up and then the screen goes blank with black light on. I've tried these roms:
cm-11-20140710-UNOFFICIAL-M8.1-ace.zip
ICESenseV1.1.zip
cm-7-20130301-NIGHTLY-ace.zip
MK44.4-ace-140719-RELEASE.zip
AoCP6_UW1_Port_for_Ace
I don't get any errors during the flashing process for all except the last one (AoCP6).
Also, the cm7 works sometimes and on other occasions it does the same thing as well. Could it be the sequence? I do a wipe, flash rom and then boot.img? Also, I've a broken volume button, so I flash the rom in recovery and then I do "adb reboot bootloader" and then flash boot.img, could this be causing this issue?
If it's not too much trouble could you upload system.img and boot.img backup from your phone of any custom rom? I would like to flash those from fastboot.
Thanks
tt33333 said:
Still no luck, it basically does the same thing for all roms. HTC logo shows up and then the screen goes blank with black light on. I've tried these roms:
cm-11-20140710-UNOFFICIAL-M8.1-ace.zip
ICESenseV1.1.zip
cm-7-20130301-NIGHTLY-ace.zip
MK44.4-ace-140719-RELEASE.zip
AoCP6_UW1_Port_for_Ace
I don't get any errors during the flashing process for all except the last one (AoCP6).
Also, the cm7 works sometimes and on other occasions it does the same thing as well. Could it be the sequence? I do a wipe, flash rom and then boot.img? Also, I've a broken volume button, so I flash the rom in recovery and then I do "adb reboot bootloader" and then flash boot.img, could this be causing this issue?
If it's not too much trouble could you upload system.img and boot.img backup from your phone of any custom rom? I would like to flash those from fastboot.
Thanks
Click to expand...
Click to collapse
Except Mokee 4.4.4 Release and CM11 M8.1 i used Philz but before that i was on CWM 5.8.1.5 and i had no issues with it. Also i've tried TWRP 2.7.1.0 too. Works perfect but i'm used to reboot into recovery by default option,which only available in CWM. Other recoveries boots into blank screen,If you powered off the device and put on charge.
Nope there isn't any sequence.... either you flash boot.img first or last it only helps in device to boot and have proper connectivity. Even if you don't flash boot.img then only your device should hang on bootloop or boots but no wifi reception. So these is something different.
Sure i can provide system.img and boot.img of M8.1 which i'm currently on. But how sure you're that it will work? I mean do you have a backup of it? Or fresh install. Also wanted to know have you ever tried format devlog partition and FULL WIPE your device?
Try using following attachments. FULL WIPE it's just an alternative of manual wipes,works with every recovery out there. And devlog partition will be formatted if any means of corrupted or remnant leftover using format_devlog zip. Meanwhile provide me details whether you got backup of M8.1 CM11 or going to flash fresh install. So that i can provide boot and system.img of it.
It's working now. Installed 4ext recovery and ran you'r script.
Thanks for all the help
[Please help]Bootloop, adb "unauthorized, fastboot flash not working, CWN not working
Hi everybody!
First of all, I'm not an Android noob, I've experience with fastboot and adb commands, android app developement and Stock/Custom Roms/recoveries in general.
Also, I extensively used google and the xda search for this issue but unfortunately didn't come any further.
To make things a little shorter, and avoid a wall of text, here are my problems.
- I'm using CM11 and CWM on a rooted Maguro.
- Initial Problem: Device is stuck in a Bootloop and I want to backup my personal data
- Therfore, wiping is not desired.
- I can boot into Downloading Mode (e.g. for Odin) and Bootloader Mode
- I can boot into recovery (CWM 6.0.4.7) through bootloader menu or fastboot
- In recovery, adb recognizes the device but it is displayed as "unauthorized", so I cant pull any files that way
- Afaik, the device should be accessible in recovery mode, so I thought maybe it would be a good idea, if I installed TWRP instead of CWM and see if it works then.
- I tried installing the new recovery (TWRP) through fastboot (fastboot erase recovery, fastboot flash recovery), and fastboot states, that it was successfull. HOWEVER, when I reboot, the recovery is still CWM and untouched.
- I read, that CM11 may under certain circumstances overwrite any recovery with CWM ob boot, so I made sure to direktly boot into recovery from the bootloader after flashing TWRP over fastboot. Still, CWM is untouched.
- I tried installing TWRP over Odin. Odin too states, that flashing the recovery was successful, but again, CWM remains untouched.
- Then I tried erasing and reflashing "bootloader", "radio", "boot" and a stock "system" through fastboot. (I carefully did not erase "userdata"). All finished successfully according to fastboot but a reboot showed the system in the same state as before.
- At this point, I assume, that I don't have write-access to the device anymore, as silly as that sounds.
At this point, I'm stuck at a dead end and don't know how to proceed, so every help you could provide would be incredibly appreciated.
Of course, I'm also willing to go into more details, but in order to keep this post from getting too long, I didn't do it in the first place.
Many thanks in advance for oyu assistance!
Greetings
Jules
i have the same problem
jules.renz said:
Hi everybody!
First of all, I'm not an Android noob, I've experience with fastboot and adb commands, android app developement and Stock/Custom Roms/recoveries in general.
Also, I extensively used google and the xda search for this issue but unfortunately didn't come any further.
To make things a little shorter, and avoid a wall of text, here are my problems.
- I'm using CM11 and CWM on a rooted Maguro.
- Initial Problem: Device is stuck in a Bootloop and I want to backup my personal data
- Therfore, wiping is not desired.
- I can boot into Downloading Mode (e.g. for Odin) and Bootloader Mode
- I can boot into recovery (CWM 6.0.4.7) through bootloader menu or fastboot
- In recovery, adb recognizes the device but it is displayed as "unauthorized", so I cant pull any files that way
- Afaik, the device should be accessible in recovery mode, so I thought maybe it would be a good idea, if I installed TWRP instead of CWM and see if it works then.
- I tried installing the new recovery (TWRP) through fastboot (fastboot erase recovery, fastboot flash recovery), and fastboot states, that it was successfull. HOWEVER, when I reboot, the recovery is still CWM and untouched.
- I read, that CM11 may under certain circumstances overwrite any recovery with CWM ob boot, so I made sure to direktly boot into recovery from the bootloader after flashing TWRP over fastboot. Still, CWM is untouched.
- I tried installing TWRP over Odin. Odin too states, that flashing the recovery was successful, but again, CWM remains untouched.
- Then I tried erasing and reflashing "bootloader", "radio", "boot" and a stock "system" through fastboot. (I carefully did not erase "userdata"). All finished successfully according to fastboot but a reboot showed the system in the same state as before.
- At this point, I assume, that I don't have write-access to the device anymore, as silly as that sounds.
At this point, I'm stuck at a dead end and don't know how to proceed, so every help you could provide would be incredibly appreciated.
Of course, I'm also willing to go into more details, but in order to keep this post from getting too long, I didn't do it in the first place.
Many thanks in advance for oyu assistance!
Greetings
Jules
Click to expand...
Click to collapse
ROM: FML-AOSP-5.0-20141207-maguro.zip (http://forum.xda-developers.com/galaxy-nexus/development/rom-fml-fork-life-06-05-2014-v2-t2764064)
Recovery: CWM V6.0.5.1
majeida said:
ROM: FML-AOSP-5.0-20141207-maguro.zip (http://forum.xda-developers.com/galaxy-nexus/development/rom-fml-fork-life-06-05-2014-v2-t2764064)
Recovery: CWM V6.0.5.1
Click to expand...
Click to collapse
Sorry, but I can't see, how this is supposed to help, since my problem is not "I'm looking for a new ROM"
sorry for the misunderstanding
jules.renz said:
Sorry, but I can't see, how this is supposed to help, since my problem is not "I'm looking for a new ROM"
Click to expand...
Click to collapse
sorry i have the same problem .
I'm using FML-AOSP-5.0-20141207-maguro and CWM V6.0.5.1 on a rooted Maguro.
Your personal data includes what?? Apps or photos and videos?
varadparulekarofficial said:
Your personal data includes what?? Apps or photos and videos?
Click to expand...
Click to collapse
yes
have you tried using the fastboot boot "/path/to/recovery.img-name-here" fastboot option to just directly boot into twrp without installing it? I used to use fastboot boot for different recovery and boot imgs I wanted to test out first before actually installing them. and I had a similar issue to what yours sounds like before in which I was able to use fastboot boot recovery.img when I wasn't able to get different custom recovery to install at the time.
ashclepdia said:
have you tried using the fastboot boot "/path/to/recovery.img-name-here" fastboot option to just directly boot into twrp without installing it? I used to use fastboot boot for different recovery and boot imgs I wanted to test out first before actually installing them. and I had a similar issue to what yours sounds like before in which I was able to use fastboot boot recovery.img when I wasn't able to get different custom recovery to install at the time.
Click to expand...
Click to collapse
I used this method
*I boot into costum temporary recovery "TWRP 2.8.3.0" Then I tried erasing and reflashing "bootloader", "radio", "boot" and new "system" through recovery All finished successfully according to TWRP but a reboot showed the system in the same state as before
The recovery images all over this site seem really sketchy, but roms often come with great recovery and updates. I can flash the rom's boot.img during the update, but I also see that fastboot has a flash to recovery option. Is it OK to flash the boot.img to recovery or do I have to somehow extract recovery out of the boot.img? If I do a flash to recovery does that make TWRP permanent or can it still be overwritten by flashing new roms?
bananabytes said:
The recovery images all over this site seem really sketchy, but roms often come with great recovery and updates. I can flash the rom's boot.img during the update, but I also see that fastboot has a flash to recovery option. Is it OK to flash the boot.img to recovery or do I have to somehow extract recovery out of the boot.img? If I do a flash to recovery does that make TWRP permanent or can it still be overwritten by flashing new roms?
Click to expand...
Click to collapse
Get twrp from here - http://forum.xda-developers.com/sony-xperia-z1-compact/general/twrp-3-0-1-amami-t3350827 and flash with Rash for non-stock roms. For stock roms, net's xzdr is best - http://nut.xperia-files.com/
If a rom has a recovery included, it will probably overwrite your recovery. For best staying power, make sure you use real recovery - http://forum.xda-developers.com/son...ral/bootloader-devices-real-recovery-t3117568 but even then you might still have to reflash your img, depending on the rom you install.
levone1 said:
Get twrp from here - http://forum.xda-developers.com/sony-xperia-z1-compact/general/twrp-3-0-1-amami-t3350827 and flash with Rash for non-stock roms. For stock roms, net's xzdr is best - http://nut.xperia-files.com/
If a rom has a recovery included, it will probably overwrite your recovery. For best staying power, make sure you use real recovery - http://forum.xda-developers.com/son...ral/bootloader-devices-real-recovery-t3117568 but even then you might still have to reflash your img, depending on the rom you install.
Click to expand...
Click to collapse
Thank you so much. I had the latest TWRP from the AICP rom but it was within the boot image and I couldn't seem to find a plain TWRP image that wasn't on some sketchy thread.
Also I was unaware that my firmware was out of date. When I was installing a rom I saw a number that related to the latest firmware so I assumed I had it. I was confused why using flashboot to flash to recovery wasn't working. It looks like the recovery image was always within the boot image and was getting wiped out with roms that didn't include a recovery image in there (AH HEM PARANOID ANDROID). It seems that I was able to flash the img to the special recovery now and I don't think it's getting wiped out. Thanks very much.
Hi guys i flashed the 3.5.3 CM today but i decided to go back with 3.26 again, so i followed a guide that tells me to install stock recovery over twrp before i install the rom but after i fastboot flash the recovery i cannot go into the recovery anymore.
i tried to flashed the modified twrp and then boot to recovery but still wont open it.
the phone works and can go into fastboot still but it just wont access recovery
anyway to fix it? sorry if this has been discussed before. im on a mac for more info
TIA
1+3
Is your OS booting?
yea
Got the same problem here. Can boot into system and fastboot but if boot to recovery i get the oneplus logo and the bootloaderscreen and then i get a black screen where i should get my recovery. And if wanna Force shutdown my oneplus it freezes somehow. I tried everything to fix this with no result. Stock recovery doesnt work too.
Hi I just had the same problem, I have sent it back to Oneplus for repair. According to the ticket, I had a faulty motherboard, which has been replaced. If you can, do it. I only had to wait for a week before it was sent back.
Had the same problem last night. Following method nr 2 in thos thread solved it.
http://forum.xda-developers.com/showthread.php?t=3405700
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
using fastboot to wipe the recovery partition then fastboot flashing modified twrp twice worked for me, i think the oneplus recovery image thats doing the rounds doesn't want to play nice lol
If youre phone boots in to system, download Flashify from play, flash recovery.img (you need to extract .img file). Go to recovery to check if it works. If not try other recovery.
after flashing the community build i cant boot my device in fastboot mode, it wont start the recovery or boot the system sucessfully.
danxtian said:
Hi guys i flashed the 3.5.3 CM today but i decided to go back with 3.26 again, so i followed a guide that tells me to install stock recovery over twrp before i install the rom but after i fastboot flash the recovery i cannot go into the recovery anymore.
i tried to flashed the modified twrp and then boot to recovery but still wont open it.
the phone works and can go into fastboot still but it just wont access recovery
anyway to fix it? sorry if this has been discussed before. im on a mac for more info
TIA
Click to expand...
Click to collapse
If your device is unlocked, flash the recovery.img from fastboot.
You can download TWRP for oneplus 3 from their site.
Rename the downloaded recovery to recovery.img.
And open fastboot in the path of the recovery image.
Use the command:
Code:
fastboot flash recovery recovery.img
Hopefully this helps
g3ck08 said:
If your device is unlocked, flash the recovery.img from fastboot.
You can download TWRP for oneplus 3 from their site.
Rename the downloaded recovery to recovery.img.
And open fastboot in the path of the recovery image.
Use the command:
Code:
fastboot flash recovery recovery.img
Hopefully this helps
Click to expand...
Click to collapse
managed to fix it the other day, by flashing the modded twrp.. somehow that one worked after that i flashed the 3.26 plus the 3.26 modem ones because if i didnt, my touch screen wont work...
For me, I flashed the twrp from fastboot.
But still the 1+ logo shows when I try to boot in to recovery for 5 sec and shuts down with 2 dots of lights in the navigation button area
The normal boot is working fine. Did flash the recovery using apps like TWRP Manager, Flashify etc. It will show successfulll. But when I try to boot in to recovery, same result.
Please help