Develop Bugs

[Q] HTC One M8 - Bootloop PLEASE HELP

Hi everyone,
I've been running ARHD on my HTC One M8 (S-ON) for the past few days. Recently I decided to get S-OFF using the firewater method.
In step one, I downloaded the OTA 3.0.7-3.0.8 Insertcoin ROM onto my device, instead of the full ROM. Without knowing this, I proceeded to make a nandroid backup from TWRP, then did an Ådvanced Wipe, checking Dalvik Cache, System, Cache, and Data. I then realised I had the wrong Insertcoin ROM file. So with the realisation that I had to download the correct one and transfer it onto my M8, I downloaded the correct one on my Mac and did a restore of the TWRP backup that I had done previously (this was because HTC Sync Manager had to recognise my device, and it couldn't do that whilst it was in TWRP).
I restored, and rebooted the system. It looked like everything had gone smoothly, except after ~20 seconds, my M8 entered into a bootloop, where it would show the white HTC screen with the red letters "This build is for development purposes only...". Sometimes it starts up as normal, but always after a few moments it restarts again into the bootloop.
Any ideas/suggestions? Help would be greatly appreciated!

rkdku said:
Hi everyone,
I've been running ARHD on my HTC One M8 (S-ON) for the past few days. Recently I decided to get S-OFF using the firewater method.
In step one, I downloaded the OTA 3.0.7-3.0.8 Insertcoin ROM onto my device, instead of the full ROM. Without knowing this, I proceeded to make a nandroid backup from TWRP, then did an Ådvanced Wipe, checking Dalvik Cache, System, Cache, and Data. I then realised I had the wrong Insertcoin ROM file. So with the realisation that I had to download the correct one and transfer it onto my M8, I downloaded the correct one on my Mac and did a restore of the TWRP backup that I had done previously (this was because HTC Sync Manager had to recognise my device, and it couldn't do that whilst it was in TWRP).
I restored, and rebooted the system. It looked like everything had gone smoothly, except after ~20 seconds, my M8 entered into a bootloop, where it would show the white HTC screen with the red letters "This build is for development purposes only...". Sometimes it starts up as normal, but always after a few moments it restarts again into the bootloop.
Any ideas/suggestions? Help would be greatly appreciated!
Click to expand...
Click to collapse
Hi!
What version of TWRP have you installed? Did you checked the compression options when you did your nandroid backup?
I ask about the compression because I have read some people having problems with compressed nandroid backups.
If you have TWRP 2.7.1.0, just try again to wipe the same partitions like you did before, and then restore your nandroid backup. But depending on the TWRP version you have installed, wiping data partition could also wipe the sdcard partition (internal storage, not external sdcard).
Some apps store information in that partition, if one of them is having troubles trying to get information, it could lead to a bootloop.
Here you have also nandroid backups for different versions if there is no way to recover your one: http://forum.xda-developers.com/showthread.php?t=2701376
Now that you are s-off, be careful about what you flash to your M8, specially firmwares, because now nothing prevents you to do brick your phone.
Read twice what you downloaded before flashing. Check also if the TWRP version you have matches your device, I think there are different TWRP builds available for different carriers like verizon, international, etc.
Good luck & cheers!
---------- Post added at 08:50 PM ---------- Previous post was at 08:47 PM ----------
You could also install ARHD again and select wipe everything from the installer (clean install), that should work. But you will have to reconfigure everything again...

ducted said:
Hi!
What version of TWRP have you installed? Did you checked the compression options when you did your nandroid backup?
I ask about the compression because I have read some people having problems with compressed nandroid backups.
If you have TWRP 2.7.1.0, just try again to wipe the same partitions like you did before, and then restore your nandroid backup. But depending on the TWRP version you have installed, wiping data partition could also wipe the sdcard partition (internal storage, not external sdcard).
Some apps store information in that partition, if one of them is having troubles trying to get information, it could lead to a bootloop.
Here you have also nandroid backups for different versions if there is no way to recover your one: http://forum.xda-developers.com/showthread.php?t=2701376
Now that you are s-off, be careful about what you flash to your M8, specially firmwares, because now nothing prevents you to do brick your phone.
Read twice what you downloaded before flashing. Check also if the TWRP version you have matches your device, I think there are different TWRP builds available for different carriers like verizon, international, etc.
Good luck & cheers!
---------- Post added at 08:50 PM ---------- Previous post was at 08:47 PM ----------
You could also install ARHD again and select wipe everything from the installer (clean install), that should work. But you will have to reconfigure everything again...
Click to expand...
Click to collapse
Hey, thanks for the reply.
So I got things working again, by adb sideloading the v1.94 SuperSU.zip to my internal storage and flashing it through TWRP. That seemed to get rid of the bootlooping issue. It also meant that I had to reinstall SuperSU on my device (it wasn't there when it booted). Going into SuperSU, it told me that binaries needed to be updated. The installation finished, and I rebooted my device... but then the bootloops started again.
Right now I've re-flashed the SuperSU.zip so I have things working again, it's just that I can't update my SuperSU binary because of the bootloop issue.
Oh and also, I never managed to get S-OFF in the end - I got the ***** device patched by HTC, you are out of luck ***** message ... seems like I downloaded an OTA or something.

You can get s-off by using sunshine which costs around 20/25$ because of the licence...but it's worth it..
It will s-off your phone without problems as long as you are on stock Rom and stock kernel

Stuck on boot after re-installing stock recovery

Hi, when I got the phone I rooted it by installing TWP recovery, it was all working fine after that until an OTA update popped up, after some research I learned that in order to install OTA updates you need to install stock recovery. Firstly, not knowing entirely what I was doing I installed the stock recovery for the wrong software version. The phone booted however and I tried to install the OTA update, upon restarting I was met with the "red triangle" error screen. I restarted the phone and it booted up fine.
Then having found the correct stock recovery (4.16.401.10) I installed it and ran the update again. It seemed to be going fine with the loading bars moving along nicely when it got stuck on the HTC bootup logo. From here I restarted it and now the phone turns on, shows the htc logo, then gets stuck on a black screen,
Please help, Thanks.

http://forum.xda-developers.com/htc-one-m8/help/boot-loop-problem-t3194508

ckpv5 said:
http://forum.xda-developers.com/htc-one-m8/help/boot-loop-problem-t3194508
Click to expand...
Click to collapse
Hi, thanks for that, I guess I should have searched around harder. One question though, you mention that there is a way to restore just system to keep your data, I don't wanna loose all of my data so I'd like to do that, I'm just not sure how to apply that to your guide, what is it that I have to do differently to keep my data?
Thanks.

DarwinW said:
Hi, thanks for that, I guess I should have searched around harder. One question though, you mention that there is a way to restore just system to keep your data, I don't wanna loose all of my data so I'd like to do that, I'm just not sure how to apply that to your guide, what is it that I have to do differently to keep my data?
Thanks.
Click to expand...
Click to collapse
2 options :
1.
In step 8, select dalvik cache, cache, system but don't select data
In step 9, tick only boot & system and don't tick data
or
2.
Make a nandroid backup of your current ROM
Do all the steps, once completed the OTA reinstall TWRP and restore only data from your earlier made nandroid backup

Thank you so much, you're amazing. Just creating a backup now. So once I've flashed the stock rom and the TWRP recovery to restore my data, if I then install the stock recovery again, should it all work fine? or does changing the recovery at any point stop OTA updates working?
The reason I rooted my phone to start with was to use titanium backup to restore apps from a previous phone, so if I can get the phone all stock just with my data, then I don't really need root.
Thanks!

DarwinW said:
Thank you so much, you're amazing. Just creating a backup now. So once I've flashed the stock rom and the TWRP recovery to restore my data, if I then install the stock recovery again, should it all work fine? or does changing the recovery at any point stop OTA updates working?
The reason I rooted my phone to start with was to use titanium backup to restore apps from a previous phone, so if I can get the phone all stock just with my data, then I don't really need root.
Thanks!
Click to expand...
Click to collapse
That's almost same as option 1 above. You need stock recovery for OTA to work.
Most important is the system part must be stock with nothing changed.
Personally, I always do option 2 to make sure OTA is successfully done .. then restore data.
One thing to note ... you don't need to relock bootloader doing all these process.

Also, now that I've created the backup (stored to the phones storage), how do I transfer that to my PC, since the phone doesn't boot, the computer doesn't recognize the storage.
Thanks.

In TWRP you have option to enable MTP then both your internal storage and microSD can be opened on PC
Make sure to use TWRP 2.8.4.0 or newer or latest. I'm still on TWRP 2.8.6.0

It seems I'm on an older version of twrp (2.7.0.2), I made the backup using this version. If I update to a newer version now will the restore work properly?
Thanks.

Usually yes we can restore a backup made with older TWRP version but I'm not so sure about 2.7.0.2 as that is the buggiest TWRP among all versions but very popular because it is included in one very old and not updated toolkit.
Why don't install latest/newer TWRP then redo the backup then transfer to PC.

I'm having trouble viewing files on my pc, I select "mount" from the main twrp menu, it then shows a screen to select which partitions to mount, I tick them, then nothing happens. There's no button to actually start the mount.

I did mentioned enable MTP function ... see below on the right side you should see Disable MTP or Enable MTP (beside Mount USB Storage) .. not those partitions to mount (but in the same screen)

I think you were right about that version being buggy. Those buttons on the bottom were missing. Just installed the latest twrp and I can mount now as the buttons to mount are showing up. Hopefully all will be fine now
Thanks.

Hi, I'm following the guide now and when I try to wipe the phone it doesn't work, I get:
Wipe Complete
Failed
"Unable to mount /cache
failed to wipe dalvik"
This error repeats a few times.
Thanks.
EDIT** scratch that, sorted it

Horray! Everything has now worked out and my phone is back to it's old self with the update, thank you so much ckpv5! you're the best.

CWM Recovery on HTC One M8 didn't work

Hello,
I installed the CWM Recovery and created a backup of my phone. But after I restored the backup, the phone doesn't start but only boots in to the CWWM recovery everytime. I didn't found the problem, so I hope anyone here, can probably help me.
1. How can I get back to the original software of the phone (even if in blank state) – because for some reason, factory reset also don't work anymor
2. If the phone works again, how can I create a backup and restore a backup, this time so that it works
3. Or is it possible to restore the backup I have? Maybe I did something wrong (I followed the steps)
Sincerely Veggie

CWM recovery ? I think it doen't support M8 on newer android version.
Use TWRP.
1. Either restore a nandroid backup or install a RUU if available.
Post fastboot getvar all minus serial & imei no. to see which one that you need.
2. Install correct version TWRP and make backup
3. Not sure but most probably cannot.

Question about a full backup and rooting

Hi,
I recently tried a custom rom on my old phone and it worked pretty well. I liked the OS and now want to also do that on my current phone. But i do still have a few questions i hope you can help me with.
- Can i make a full backup of my phone (with app data) to my PC or maybe to my old phone? I am currently not rooted and tried helium backup but saw that sadly not all apps allow a backup.
- I know about titanium backup. Is there some way (if the above cant be done) i can root my phone without wiping the phone? So i can then use titanium backup to make a proper backup with data, then install the custom rom and after restore the apps+data.
In short: I hope i can somehow make a full backup with app data so i can install the custom rom and restore my app data again.
Looking forward to your replies.
Thanks in advance.

Nothing? No one ? =(

To root you need to unlock the bootloader, which wipes all user data. So you can't use root to backup your data. This is why I unlock the bootloader immediately after getting a phone.
You can try an adb backup though.

razr96 said:
To root you need to unlock the bootloader, which wipes all user data. So you can't use root to backup your data. This is why I unlock the bootloader immediately after getting a phone.
You can try an adb backup though.
Click to expand...
Click to collapse
Thank you for your reply and thx for the tip. Ill be doing that too from now on when i get a phone.
As long as i can make a full backup with abd (with app data), Im fine with wiping to root it. But just wanted to make sure i can get app data back after the root process.
Do you happen to have a link to a proper backup using abd guide?
Thanks

no

sm00th4f3 said:
https://forum.xda-developers.com/android/general/how-to-backup-restore-android-device-t3602583
You might wanna read this and try it
https://forum.xda-developers.com/android/help/adb-fastboot-commands-bootloader-kernel-t3597181
Click to expand...
Click to collapse
Well with a few side searches i was able to open the cmd (admin), do a adb devices (which found a device) and then run the app + data command.
('adb backup -apk -shared -all -system -f C:\backup.ab')
I saw the screen on my phone to start it, which i did but it stays on Shared Storage (where before this mentioned the apk's that were being backed up). This is taking pretty long (as in hours). Is this normal or did something went wrong and is it stuck on that part?
Edit (Update): I stopped the whole thing and tried again. Now it finished in about 10 - 15 min. I did get a message "backup finished". However in the folder i gave up, there is nothing to see. folder is still empty
Edit2 (update): Found the backup.ab file. Apparently it was in a different folder i thought it would be. So if i then also make a copy of the internal storage and do this command, i should be good right? After doing that, unlock and root, i can use the 'adb restore C:\backup.ab' and have all apps + app data back as it was before the unlock/root ?

no

sm00th4f3 said:
In a sense. Yes, but you might wanna read some threads about that first.. Otherwise. No one would wanna go back after unlocking his phone. Since restoring a backup from a locked phone on an unlocked phone can cause some issues.
Click to expand...
Click to collapse
I'm not really sure what you mean though.
If i unlock my phone with my code and then make the backup with adb and just in case, a copy of my internal storage, can't i use restore on the unlocked/rooted phone to have the apps + their data back and use them again ?

no

sm00th4f3 said:
No you can't. It will brick your device. The backup can only be used when your phone is still locked. So it is basically not needed at all.
Click to expand...
Click to collapse
So you are saying that there is no possibility to backup my apps+data, unlock/root/custom rom, and then restore my apps+data at all?
That was some what the question of my first post.
So its either, fully wipe with everything lost, then root etc. etc. or just keep it the way i have it now?

no

sm00th4f3 said:
The normal procedure is as follows:
After an unlock.- your data always gets formatted. So a backup is totally wasted time.
The backup isn't wasted time - if it is done after unlocking your phone, while it still has stock rom.
In case flashing goes wrong, make the backup while not having flashed twro etc at all.
You don't have to wipe anything if you just want root, since the phone will reset-wipe your data on its very own.
Just unlock it, let it reboot, Flash twrp, install root zip file. Reboot
In case of flashing a custom rom. Flash twrp, boot to twrp. Use the Reboot menu and reboot again into recovery
Reboot->Recovery (in twrp menu).
Then Wipe-> Factory Reset
Wipe-> Advanced Wipe-> Wipe System partition only
Wipe-> Advanced wipe-> select Data partition-> Change file system to ext4
Reboot Menu in TWRP->Recovery
Wipe Dalvik and Cache
Flash Rom
Flash Gapps if not stated otherwise in Instructions of Rom Thread
Flash Magisk or SUperSu , depends if you want root or not. If you don'T want encryption on older Roms, flash one of the two.
Encryption will later on be optional through Phone Security Options.
Wipe dalvik and cache.
Reboot.
Wait a bit.
Setup phone, done.
Click to expand...
Click to collapse
Yes but as you mentioned, unlocking means a full wipe. And i cant restore apps + their data from a stock phone backup to an unlocked phone as it can cause issues.
In my very first post i asked if i could make a backup of the apps + their data to restore them after unlocking/rooting/custom rom or whatever. Simple answer then is no.
So i either have to just wipe my phone and basically start all over, only unlock/root etc etc first.
Or just keep my phone stock like how it is now and just do nothing and wait until i get a new phone (which will be in a long time still)

Restore a TWRP backup with A/B system slots!

CHANGED: You must flash the dm-verity.zip on ROM install to use the backup/restore feature of TWRP. It won't work if /data is encrypted. I jumped the gun when making this thread.

EDIT2: I had also flashed dm-verity on install so /data wasn't encrypted.

Which Dm Verity did you use which version??

Does this mean even today with the latest versions of twrp and magisk you cant restore the backups made of an encrypted phone? I just got a new Moto G7 Power and got it setup with those two things and made a backup - havnt tried restoring yet. Does your solution of flashing the dm-verify.zip thing mean the phone will be unencryped then? Because I cant have that, I rather not have backups. What about the old "adb backup" type command line does that still work?

I've had my phone since the day they were available at metro and I can't and don't even try to backup or restore anything anymore. On roms it always has broken lockscreen where you cannot secure phone. Because of this I stay encrypted and setup my **** all over again when I change roms.

flash713 said:
I've had my phone since the day they were available at metro and I can't and don't even try to backup or restore anything anymore. On roms it always has broken lockscreen where you cannot secure phone. Because of this I stay encrypted and setup my **** all over again when I change roms.
Click to expand...
Click to collapse
I see, too bad it's a nice function to backup/restore I guess I'll just backup my important data individually and try not to mess up my Rom.

TaZeR369 said:
I see, too bad it's a nice function to backup/restore I guess I'll just backup my important data individually and try not to mess up my Rom.
Click to expand...
Click to collapse
Check this out. I haven't used it yet but I'm about to try it. Join «Migrate - Custom ROM Migration Tool» on Telegram: https://t.me/migrateApp
https://forum.xda-developers.com/android/apps-games/app-migrate-custom-rom-migration-tool-t3862763
There's a new add-on for it on telegram link

TaZeR369 said:
I see, too bad it's a nice function to backup/restore I guess I'll just backup my important data individually and try not to mess up my Rom.
Click to expand...
Click to collapse
Me too. I haven't a bit of luck with encrypted stock restores. I was told it would work if you don't restore /data, but when I made a backup without /data, it failed to restore. I HAVE been able to restore unencrypted customs though. I only backed up system, data, and boot when I succeeded. It's been a while. I think you have to wait a long time for the 1st boot after the restore, as if it were rebuilding ART or something. Haven't had any luck stopping stock from encrypting either. I hate not messing up my ROM. Boring.....

Perhaps I am missing a critical detail, but I just successfully restored my latest LOS(lineage-17.1-20200524-UNOFFICIAL-ocean) & older CRD(crDroidAndroid-10.0-20200405-ocean-v6.4) backups(*) using TWRP(twrp-installer-3.3.1-2-ocean).
SELinux is NOT enforced, but "Trust"(lulz) claims the phone is encrypted.
My methodology requires installing the same base f/w I used when originally installing the ROM(former newest RETAIL for CRD & newest RETUS for LOS), root, flash copy partitions zip, flash>factory reset>1st boot of the original ROM zip, enable debug, install TWRP, boot into TWRP, wipe all & restore backup(*).
I just restored successfully 2x's on my xt1955-5.
I loaded LOS 10 & 3rds from scratch, made all my settings tweaks & made Titanium b/u(JIC), made TWRP b/u(*) then restored my previous CRD daily install using steps above. Then I repeated the above steps(again) to go back to my new, fresh LOS. It is annoying to have to reload f/w, et al, but def easier than reloading & retweaking the OS & all 3rds from scratch... Titanium fails to restore most settings + other nits.
To restore a backup(*) of a ROM I am currently running, I just boot to TWRP, wipe all & restore.
*: To make the original TWRP backup, I will run it & it will fail. I open the log file and find the last file/folder that "error"ed, delete the offender & re-run backup(boot, data & system). It works for me, no DM-verity flash required.
As always, YMMV.
Edit: PS: The problems seem to be stemming from beta testing the new "Trust"(lulz) framework, on all 10 ROMs(?). Would be nice to get that ironed out. A new Recovery wouldn't hurt, either. AFAIK, these problems exist in OFR, too.

googleverifysux said:
Perhaps I am missing a critical detail, but I just successfully restored my latest LOS(lineage-17.1-20200524-UNOFFICIAL-ocean) & older CRD(crDroidAndroid-10.0-20200405-ocean-v6.4) backups(*) using TWRP(twrp-installer-3.3.1-2-ocean).
SELinux is NOT enforced, but "Trust"(lulz) claims the phone is encrypted.
My methodology requires installing the same base f/w I used when originally installing the ROM(former newest RETAIL for CRD & newest RETUS for LOS), root, flash copy partitions zip, flash>factory reset>1st boot of the original ROM zip, enable debug, install TWRP, boot into TWRP, wipe all & restore backup(*).
I just restored successfully 2x's on my xt1955-5.
I loaded LOS 10 & 3rds from scratch, made all my settings tweaks & made Titanium b/u(JIC), made TWRP b/u(*) then restored my previous CRD daily install using steps above. Then I repeated the above steps(again) to go back to my new, fresh LOS. It is annoying to have to reload f/w, et al, but def easier than reloading & retweaking the OS & all 3rds from scratch... Titanium fails to restore most settings + other nits.
To restore a backup(*) of a ROM I am currently running, I just boot to TWRP, wipe all & restore.
*: To make the original TWRP backup, I will run it & it will fail. I open the log file and find the last file/folder that "error"ed, delete the offender & re-run backup(boot, data & system). It works for me, no DM-verity flash required.
As always, YMMV.
Edit: PS: The problems seem to be stemming from beta testing the new "Trust"(lulz) framework, on all 10 ROMs(?). Would be nice to get that ironed out. A new Recovery wouldn't hurt, either. AFAIK, these problems exist in OFR, too.
Click to expand...
Click to collapse
Have u tried the new 3.5 twrp

Lol...and here it is a couple years later and I'm still searching whether a force-encrypted twrp backup of stock has been figured out how to restore...Pulled up my own thread. Lol.

i miss being able to backup android properly. it made me behave completely differently with my phone. it was a toy instead of just some tool. i'd just install every single rom, kernel modem operating system i could find or i'd just plagiarize the hell out of you guys for sh*ts and giggles and man i loved android so much back then but now its my cell phone. :\ i just liked the colorful language, i wasn't signing anybody else's code.

it's such a tedious thing now, even compared to before and i suppose that's their intention perhaps.