I recently unlocked my bootloader and now have access to TWRP recovery, but whenever I try to backup, it shows "backup failed" and has a button at the bottom allowing me to reboot (to the lockscreen, homescreen, etc.)
I am trying to flash CyanogenMod 11 onto my device but first I would like to do a custom recovery before I do so, any help on that?
What options are you selecting to make the nandroid backup with? I made mine with all options checked except backing up the external sd... went through with no problem when everything was backed up together.
Related
Hello All,
Sorry if this has already been solved before, and thanks in advance for help. (I tried to post this in the ARHD41.0 thread, but as a newbie I cannot post there.)
I have an HTC One (AT&T) that had been updated to 4.3 OTA, then unlocked via htcdev, flashed with CWM 6.0.4.3 recovery, and then rooted with the Superuser zip on the CWM site. The device remained S-On. Made a backup through CWM recovery, transferred that to my PC, then figured I might as well celebrate the holidays by flashing my first ROM.
I downloaded the Android Revolution HD 41.0 ROM (forum.xda-developers.com/showthread.php?t=2183023), transferred to the SD, and then installed the zip through the CWM ROM manager (it seemed at least from what I read in the posts that followed that the ROM worked just fine with CWM). After going through the option selection process (I believe that this was the Aroma installer), I opted to wipe data since I was starting from a different ROM altogether (of course, silly me, this also wiped the backup on the SD). Seemed to install just fine, booted into what appears to be some part of the recovery where it asked if I wanted to root, I selected yes, and the phone rebooted.
Or, at least, tried to. It has been stuck at the beginning of the boot, where there is a white background with the HTC logo and "quietly brilliant" underneath, and it remains stuck there. If I press power and volume down for an abnormally long time, I can get into the bootloader and the recovery from there, but rebooting from there just leaves me at the boot screen again. As I said, there is no backup on the SD for me to restore. When in bootloader, I connected to the PC and fastboot turns to fastboot USB, but adb isn't showing anything when I enter abd devices.
I'm sure I probably did something very silly and am missing something very simple, but given that this is my first time, I have no idea what it is and how to go about fixing it.
Thanks again for all your help!
lyciansarpedon said:
Hello All,
Sorry if this has already been solved before, and thanks in advance for help. (I tried to post this in the ARHD41.0 thread, but as a newbie I cannot post there.)
I have an HTC One (AT&T) that had been updated to 4.3 OTA, then unlocked via htcdev, flashed with CWM 6.0.4.3 recovery, and then rooted with the Superuser zip on the CWM site. The device remained S-On. Made a backup through CWM recovery, transferred that to my PC, then figured I might as well celebrate the holidays by flashing my first ROM.
I downloaded the Android Revolution HD 41.0 ROM (forum.xda-developers.com/showthread.php?t=2183023), transferred to the SD, and then installed the zip through the CWM ROM manager (it seemed at least from what I read in the posts that followed that the ROM worked just fine with CWM). After going through the option selection process (I believe that this was the Aroma installer), I opted to wipe data since I was starting from a different ROM altogether (of course, silly me, this also wiped the backup on the SD). Seemed to install just fine, booted into what appears to be some part of the recovery where it asked if I wanted to root, I selected yes, and the phone rebooted.
Or, at least, tried to. It has been stuck at the beginning of the boot, where there is a white background with the HTC logo and "quietly brilliant" underneath, and it remains stuck there. If I press power and volume down for an abnormally long time, I can get into the bootloader and the recovery from there, but rebooting from there just leaves me at the boot screen again. As I said, there is no backup on the SD for me to restore. When in bootloader, I connected to the PC and fastboot turns to fastboot USB, but adb isn't showing anything when I enter abd devices.
I'm sure I probably did something very silly and am missing something very simple, but given that this is my first time, I have no idea what it is and how to go about fixing it.
Thanks again for all your help!
Click to expand...
Click to collapse
Hey,
Not to worry just run this command from fastboot (Power button +vol down while booting-> fastboot) plug your phone in and run
fastboot erase cache
Click to expand...
Click to collapse
and if its not fixed, just flash again. Make a back up next time! BTW if you need adb just get it from HERE (hint clickn 'here') if you need more help PM me, im always available
You need TRWP 2.6.3.3 or latest version (2.6.3.4) recovery!
Some members successfully flashed by CWM but also some of them face problems, so its better to you to follow FAQ to get good results : )
http://forum.xda-developers.com/showpost.php?p=48035061&postcount=62237
Ba7rani said:
You need TRWP 2.6.3.3 or latest version (2.6.3.4) recovery!
Some members successfully flashed by CWM but also some of them face problems, so its better to you to follow FAQ to get good results : )
http://forum.xda-developers.com/showpost.php?p=48035061&postcount=62237
Click to expand...
Click to collapse
I actually just saw the posts about the CWM issue a little while ago - that's what I get for not reading all the posts! I flashed with TWRP, the ROM installed, and the phone booted.
Now, this is where things get interesting. My backup that I had made with CWM before I initially tried to flash the ROM was still in \data\media\clockworkmod (where it had initially backed up to), and I wanted to check if I was still able to restore from it. TWRP doesn't recognize it as a backup folder/file (not sure if it would be compatible; this is also my first time restoring), and I flashed back to CWM recovery (phone still boots fine after that)...which doesn't recognize it either. I tried moving it to \sdcard\clockworkmod (where the md5 checksum file was originally generated), \sdcard (just in case, since the recovery option says "restore from \sdcard"), as well as \mnt\shell\emulated\clockworkmod (that's where the CWM ROM manager says that it would have backed up to), but the recovery says "No files found" for any of those as well. Any thoughts on where the backup ought to be located?
lyciansarpedon said:
I actually just saw the posts about the CWM issue a little while ago - that's what I get for not reading all the posts! I flashed with TWRP, the ROM installed, and the phone booted.
Now, this is where things get interesting. My backup that I had made with CWM before I initially tried to flash the ROM was still in \data\media\clockworkmod (where it had initially backed up to), and I wanted to check if I was still able to restore from it. TWRP doesn't recognize it as a backup folder/file (not sure if it would be compatible; this is also my first time restoring), and I flashed back to CWM recovery (phone still boots fine after that)...which doesn't recognize it either. I tried moving it to \sdcard\clockworkmod (where the md5 checksum file was originally generated), \sdcard (just in case, since the recovery option says "restore from \sdcard"), as well as \mnt\shell\emulated\clockworkmod (that's where the CWM ROM manager says that it would have backed up to), but the recovery says "No files found" for any of those as well. Any thoughts on where the backup ought to be located?
Click to expand...
Click to collapse
If you have Titanium backup pro you can restore from nandroid file
Menu > restore from Nandroid ..
* Its not recommended to restore system apps or data by Titanium
Found my mistake:
lyciansarpedon said:
\mnt\shell\emulated\clockworkmod\backup (that's where the CWM ROM manager says that it would have backed up to)
Click to expand...
Click to collapse
Missed that I needed to create that directory, oy. Recovery found it just fine, and restored it just as I left it.
Thanks all!
Hi
i was hoping for a little help the image attached is of a nandroid backup downloaded from here it matches my cid amongst other things how do i flash his to my phone is there a idiot proof way of doing this ?
at the moment i have unlocked bootloader via htcdev & twrp 6.2.33 installed i flashed viper but it said it didnt install properly so now the phone boots goes to lock screen if i try unlock it just goes back to htc splash screen then i press sleep button off then on brings the lock screen back then the same thing happens again then the phone reboots itself this happens continuously.
i can get into fastboot and recovery all i want is the phone working again
Are you sure it's a TWRP backup? Perhaps CWM?
How would i know ?
ive attached the recovery log from the backup
vattmann said:
How would i know ?
ive attached the recovery log from the backup
Click to expand...
Click to collapse
Clockworkmod recovery 6.0.4.4 and the beigining of the log file you posted
vattmann said:
How would i know ?
ive attached the recovery log from the backup
Click to expand...
Click to collapse
Its Clockworkmod recovery 6.0.4.4.
So you need to flash this recovery and try to restore. It should help.
Else if you want a custom rom, boot into recovery, and connect your phone to computer. enable mounting of internal storage. With this you can push a new custom rom (of your choice) onto your internal storage. flash it via recovery.
Hope this helps
Hey guys, I tried to unroot my XT1097 pressing the button at the SuperSU app, but when I restarted the phone, the phone wouldnt boot, I'm stuck at the motorola "water-ish" motorola logo. My bootloader is unlocked with TWRP. What can I do to fix it?
Thanks in advance (and sorry if I couldn't find an answer doing searches )
i have experienced this problem many times when trying to restore the MotoX 2014 from either a nandroid backup, "fix permissions" and even a factory reset in TWRP (when i did not also wipe the user files). it is worth noting that I never had these problems until after the lollipop update. perhaps it is a consequence of whatever they did to allow the option to encrypt bootloader (which is a feature I have opted out of).
the fix is simple but a real PITA assuming you do not have all your files like pictures etc backed up. I will list 3 options below. the first option is an attempt to get it to boot without wiping your files. be aware your options are contingent on the type of recovery you are running (i.e. TWRP or stock). the nutshell answer: In order to restore full functionality you must wipe everything including user files. I do not know what recovery you have, but if runnning TWRP then the basic factory wipe is not enough when running lollipop.
1-in TWRP recovery, go to "wipe" then "advanced wipe," check the "system and click "repair or change file system" then click "repair"
2-in TWRP recovery, go to "wipe" then "advanced wipe," check "dalvik cache", "data", "internal storage" and "cache".....DO NOT CHECK "system"
3-IF the above steps fail or if you have stock recovery, just perform a factory reset. you should be good to go at that point
I had this issue with my Nexus 7 after unrooting to take an OTA to 5.0.2. Unfortunately the only way I was able to fix it was to use stock recovery and clear user data and cache.
Summary:
1. Flash factory image onto phone successfully
2. Install twrp and make a backup
3. Restore backup after reboot and I'm stuck in a bootloop
I have a new fi Moto x4 running Android 8.1 that I'm attempting to set up. I've reset this phone a bunch of times so here is the standards process:
1. Flash factory firmware as shown in this thread:
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
I'm using: PAYTON_FI_OPW28.46-13_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
2. After flashing, start up the phone and it works fine.
3. Reboot into the bootloader and boot to twrp using: fastboot boot twrp-3.2.3-1-payton.img
4. Copy in the twrp install file using: adb push twrp-installer-payton-3.2.3-1.zip /sdcard
5. Install the zip via the twrp Install function
6. Reboot the phone into the bootloader then start recovery
7. Use the twrp Backup function to create a backup of the Boot, Data and System partitions on Internal Storage (plenty of space).
8. Reboot the phone into the bootloader then start recover
9. Use the twrp Restore function to restore the backup. Finishes fine.
10. Reboot phone to system but the load won't finish. Phone just alternates between the Android One and the Motorola splash screens. Left it for an hour at one point just to be sure. No love.
Things I have tried:
1. Using twrp via fastboot boot and a hard install
2. Making backups to the internal and external memory cards
3. Changing the partitions in the backup
4. Wiping everything except the external sim card before performing a restore
If anyone has any thoughts I would love to here them.
Thank you!
I'm having a similar problem and found this old thread. I am on stock pie rooted and made a twrp backup this morning so that I could try flashing some custom ROMs. After successfully installing a custom ROM I attempted to restore the backup and return to stock but just get bootloop. I am able to get back to to twrp and the phone will boot after a factory reset, but even if I just restore data I get bootloop. I'm wondering what I am doing wrong with restoring the backup. Any thoughts? Thanks.
I have the same problem as you are. After I finished install all applications, I made a backup with twrp-3.2.3-1-payton. Then next day I restore it from the backup, after finished backup, it goes to bootloop forever. My version is OPWS28.46.21.12, I download stock rom OPW28.46-13 but afraid to flash this rom since it is the lower version might be break the phone if not backward compatible. Then I search the web and found your message and follow this side fund a higher version of the stock rom OPWS28.46-21-14. I download it and flash it. After flashing complete and boot up, it saying new OTA update available, I don't want to update the rom since I want my phone rom version is same as the stock rom I have downloaded into my PC just in case in the future I accidentally doing something wrong I can flash back the stock rom without worrying the backward compatibility problem.
t-bob said:
I'm having a similar problem and found this old thread. I am on stock pie rooted and made a twrp backup this morning so that I could try flashing some custom ROMs. After successfully installing a custom ROM I attempted to restore the backup and return to stock but just get bootloop. I am able to get back to to twrp and the phone will boot after a factory reset, but even if I just restore data I get bootloop. I'm wondering what I am doing wrong with restoring the backup. Any thoughts? Thanks.
Click to expand...
Click to collapse
I'm a bit slow on the response - but my first thought is manually flash stock rom over your restore without wiping data
I'm able flash the latest stock rom of FI_9.0_PPWS29.69-26-4 and reinstall twrp-3.2.3-1-payton. Then I restore data only that backup from previous rom, I get bootloop again after restore the data only from TWRP. The I reflash FI_9.0_PPWS29.69-26-4 again, install twrp and root it with Magisk. Restore data from cloud google drive automatically. And this time is successfully without bootloop.
HI everyone,
Thank you for the custom roms (twrp, backup TA, and the other works... ) and making this phone up to date.
Long story short :
I've been using Havoc since 2 months and needed to restore a previous backup made with TWRP.
It didn't work as the result was that the system is hanging at 'Starting phone...' like @Rataplan626 in the LineageOS thread.
Anyway, trying by myself to understand why restoring does not work, I flashed HavocOS from start. At that point, everything was OK (I didn't need to provide a lockscreen pattern, It was already set).
Then I decided to remove the lockscreen pattern and the system can't even boot (nor Lineage neither Havoc, I even tried to revert to stock).
Currently, I am stuck with the recovery.
Could anyone guide me on how to make my phone work again (i.e. install a ROM) ?
Please find the recovery log if needed.
used to run Havoc v4.13 + TWRP 3.6.1
edit: I forgot to provide the logs
edit2: I did not forget, I just can't attach any file - I host the logs in a tier platform
Long story "long":
GOAL: RESTORING A BACKUP
Initially, my goal was to restore an old backup.
ACTION: RESTORING ANY BACKUP
Doing so hasn't been successful, I ended up with the 'Starting phone...' message indefinitely. The launcher didn't boot up. Same behavior with any my backups. I concluded with a TWRP 3.6.1 backup failure, even if I can retrieve my data browsing the backups.
ACTION: RESTORING PARTITIONS INDIVIDUALLY
Nevermind, I flash Havoc again and restore the partitions manually:
- after flashing the ROM, everything is OK
- restoring one or all the partitions (data & system) leads to the same behavior ('Starting phone...')
ACTION: TRYING A DIFFERENT RECOVERY
Another try with TWRP 3.5.2/3.6.0 : I can flash Havoc/Lineage from scratch but can't restore anything.
ACTION: REVIEWING THE BACKUP PROCESS
I decided to test the backup process by flashing fresh Havoc (no setup, no apps, nothing): I launch the ROM, restart to recovery, make a backup and restore immediatly this backup. Result: same !!! What ?!
ACTION: REMOVING THE LOCKSCREEN PATTERN
I noticed during this process that the lockscreen pattern is always set and never removed, I only set it up the first time I installed Havoc 2 months ago. Maybe, it is the cause of those failures.
Additionnally, when starting the phone, I've never been asked the pattern to decrypt the system. It starts right away and it is only needed on the launcher (my tablet needs the pattern before loading the system).
Well, I removed the pattern:
- I restore some backup: failure
- flash Havoc/Lineage: failure, oh no! -> bootloop straight to TWRP, no bootanimation (same with backup).
ACTION: REVERTING TO STOCK ROM
I thought: back to stock. I tried with newflasher, no error but results with TWRP bootloops and no bootanimation.
I failed with PC Companion because the phone is unlocked.
CONCLUSION: MY PHONE IS A RECOVERY (lol)
I am not asking to resolve all these issues but only to be able to flash a (successfully) ROM successfully.
By the way, I do not recommend using the restore feature at the moment (even if it worked for me the first I install Havoc 2 months ago).
Thanks for reading.
Solution: Format data (which is different to wipe)
In recovery: Wipe > Format Data > Type 'yes', valid and voilà!
My phone is a phone again.
I need to understand why recovery restore function doesn't work. But that's another topic.
edit: actually, it also solved the restore issue. I can restore any of my backups. 100% solved.
@Rataplan626 give it a go