Database Info

Can't update to Marshmallow

Every time I try to flash a MM ROM, I never get past the boot logo. It just continues on for 30 minutes before I finally turn it off with the 10 second power button hold. Then I don't have an OS and TWRP shows no files so I can't restore - it looks like the internal SD card was wiped. I figured out to make a nandroid over OTG so I could restore, but I have the same result trying to flash any MM ROM. I have tried to first flash plain CM, as well as the firmware/modem files beforehand, but that has not worked. I updated to TWRP 2.8.6.0 with no difference. Any ideas?

phoneturf said:
Every time I try to flash a MM ROM, I never get past the boot logo. It just continues on for 30 minutes before I finally turn it off with the 10 second power button hold. Then I don't have an OS and TWRP shows no files so I can't restore - it looks like the internal SD card was wiped. I figured out to make a nandroid over OTG so I could restore, but I have the same result trying to flash any MM ROM. I have tried to first flash plain CM, as well as the firmware/modem files beforehand, but that has not worked. I updated to TWRP 2.8.6.0 with no difference. Any ideas?
Click to expand...
Click to collapse
Hum. To me it sounds/feels like when I've tried to update, but forgot to flash the new modem... but you have tried that. I'd go back to TWRP 2.8.6, flash your old rom/modem, and see if you can get back there... and are able to boot into system
then if that works, full wipe, flash MM, the modem, google package and reboot.

I tried again a few days ago and was successful flashing to marshmallow using a plain CM13 rom. It was okay, but not an improvement over the LP rom I was using, and with less features, so I tried to nandroid back to LP. I kept getting an error with TWRP Restore. It looked like I was stuck on MM. I messed around in TWRP and changed system and data to EXT4 (figuring they were now F2FS and that was the problem). This worked. Once I formatted to EXT4, I was able to restore over OTG. Formatting to EXT4 wiped my internal memory so it was lucky I had a backup on OTG.

Samsung S6 stuck in boot loop

Hello,
I am new to rooting so I hope what i say makes sense.
I recently rooted my Samsung galaxy s6 G920IDVU3EPC6 yesterday. After seeing a update notification pop up it took me to twrp where I tried everything to get out of it, install the .zip thing. reboot. Nothing would get me out of the twrp menu. stupidly, I did an advanced wipe and it appears I got rid of all the system files or something like that.
Now the only thing I can do is enter the blue download menu or get stuck on the boot logo screen forever. I have made backups of my files on my PC. How do I get my phone back? please help me!

Hi,
Samsung OTAs (Over The Air) updates won't work on a rooted device. It has rebooted into TWRP, because normally it reboots into it's original Samsung recovery and installs the update. But because TWRP replaces the Samsung recovery, it doesn't work.
And if you have wiped the System partition, you no longer have anything installed. No Android, nothing.
The easiest thing to do would be to flash the original firmware for your device. Then you can do the update, then root your device.
A good habit to get into when you have TWRP installed is to do regular TWRP full backups. That way, if anything happens (like wiping your device), you can just restore that backup from TWRP, and the phone will be exactly as it was, with all partitions intact

the_scotsman said:
Hi,
Samsung OTAs (Over The Air) updates won't work on a rooted device. It has rebooted into TWRP, because normally it reboots into it's original Samsung recovery and installs the update. But because TWRP replaces the Samsung recovery, it doesn't work.
And if you have wiped the System partition, you no longer have anything installed. No Android, nothing.
The easiest thing to do would be to flash the original firmware for your device. Then you can do the update, then root your device.
A good habit to get into when you have TWRP installed is to do regular TWRP full backups. That way, if anything happens (like wiping your device), you can just restore that backup from TWRP, and the phone will be exactly as it was, with all partitions intact
Click to expand...
Click to collapse
I can't flash the original ROM. When I try to flash it on odin it never gets past setup connection or NAND write start. I tried different versions and cable and port and it doesnt work. PLEASE HELP
I can enter the TWRP menu but whenever I do something it says no OS installed.

There is apparently no way to restore a Nandroid backup under OOS 9.0.4...???

So I did what I thought was a routine thing, trying to restore system, boot, and data like I have on many phones before only to ended up in a bootloop or bootloader only not even able to boot a TWRP from fastboot.
After several hours of trying just about everything I finally faced the fact that I was not going to be able to restore any NANDROID backup I had do to A/B, encryption or the latest Android security patch?
However, you can get you phone running again quite easily with this thread: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 and using the flash-all option from a WIndows 10 VM (I am a Mac/Linux guy, but this does work from a Windows VM and is quick).
Before I re-installed anything I wanted to just verify that I could do a simple NANDROID backup of an empty phone with twrp / blu_spark and I can't under any case. Here's what I tried (with latest stock TWRP and latest Blu_Spark TWRP):
1) simple restore of data, system, boot -- > boots only to fastboot, need to recover with thread above
2) Recover with thread above, re-root (Magisk 18.1) and reinstall TWRP, boot ROM, then try restoring just data -- > same as #1
3) Recover using thread above, re-install TWRP, restore NANDROID, and re-run Magisk (suggest by a few) --> same as #1
My device is encrypted, and I could turn off encryption, but that is somewhat scary on a daily driver.
So has anyone successfully restored a NANDROID on a 9.0.4 rooted phone with the latest Android security patch and if so, what's the trick?
Thanks,
MW

MetroWestMA said:
So I did what I thought was a routine thing, trying to restore system, boot, and data like I have on many phones before only to ended up in a bootloop or bootloader only not even able to boot a TWRP from fastboot.
After several hours of trying just about everything I finally faced the fact that I was not going to be able to restore any NANDROID backup I had do to A/B, encryption or the latest Android security patch?
However, you can get you phone running again quite easily with this thread: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 and using the flash-all option from a WIndows 10 VM (I am a Mac/Linux guy, but this does work from a Windows VM and is quick).
Before I re-installed anything I wanted to just verify that I could do a simple NANDROID backup of an empty phone with twrp / blu_spark and I can't under any case. Here's what I tried (with latest stock TWRP and latest Blu_Spark TWRP):
1) simple restore of data, system, boot -- > boots only to fastboot, need to recover with thread above
2) Recover with thread above, re-root (Magisk 18.1) and reinstall TWRP, boot ROM, then try restoring just data -- > same as #1
3) Recover using thread above, re-install TWRP, restore NANDROID, and re-run Magisk (suggest by a few) --> same as #1
My device is encrypted, and I could turn off encryption, but that is somewhat scary on a daily driver.
So has anyone successfully restored a NANDROID on a 9.0.4 rooted phone with the latest Android security patch and if so, what's the trick?
Thanks,
MW
Click to expand...
Click to collapse
apparently is not matter of factly, i do nandroids and have restored from them various times with only 2-3 settings that i had to reset my way thereafter, hence it's apparently worth to retry, it works.
sometimes it helps to know that things are possible to put some more effort into something, knowing it can be worth it in case of success.
perhaps some remarks:
if your' phone is "empty" as you stated i recommend to first install factory image / stock rom latest OOS, i.e. 9.0.4
make nandroids of each partiton speparately and also restore them separately while don't nandroid the images, and cerrtainly don't restore those, only common partitions like system, boot, vendor, data.
system and vendor are present as normal partition as well as image partition, don't touch the later in any way.
all this only works if you restore on a phone that was bootable before you restore, for restoring to empty phones there are other procedures via fastboot commands and or stock rom via stock recovery if it's on device, else ADB comes in handy.
last but not least if you restore you have to restore everything, not only one partition especially not only system partition, won't work well or not at all depending.
1. Modem if corrupted, else not needed
2. EFS if corrupted, else not needed
3. Vendor start here if the previous rom was running well and make sure it's not been altered or you have to correct vendor backup in case you have more than one
4. System
5. Boot
6. Data
good luck

magnamentis said:
apparently is not matter of factly, i do nandroids and have restored from them various times with only 2-3 settings that i had to reset my way thereafter, hence it's apparently worth to retry, it works.
sometimes it helps to know that things are possible to put some more effort into something, knowing it can be worth it in case of success.
good luck
Click to expand...
Click to collapse
OK -- do tell, what settings did you use? And you have done this on OOS 9.0.4 with encryption, or did you disable decryption?
I'll happily delete or edit the post...it seems many are having problems with few solutions starting with 9.0.4...
Thanks,
MW

MetroWestMA said:
OK -- do tell, what settings did you use? And you have done this on OOS 9.0.4 with encryption, or did you disable decryption?
I'll happily delete or edit the post...it seems many are having problems with few solutions starting with 9.0.4...
Thanks,
MW
Click to expand...
Click to collapse
the last restore i did on 9.0.3, since then i gave up on custom roms since OOS rooted + a few useful apps make OOS close to perfect for me
i'd not delete the thread, many reported issues with nandroids because the normal procedure to take one single backup and restore from twrp to an empty device does not work, one always need to first flash stock OOS to a clean slate before installing anything else or restoring anything.
and backups should be in increments not one single backup like it was possible on single slot devices.
restoring one single partition usuelly ends up in a mess except boot partition, boot, efs and modem can be restored as standalone restores without issues in most cases while flashing a kernel + magisk is still easier and safer than restoring a boot partition.
as to setttings i dunno what you mean, exactly and as to encryption, my device is and has bee encrypted at all times.
it's most important to use twrp- recovery by blue_spark, official standard recovery has issues ( at least always had as long as i tried using it) especially with verification in TWRP on encrypted devices. there is a risk to end up encrypted without any way to boot back into system or into twrp menu, hence use blue_spark's and all is well, user error exempt of course

Since reinstalling everything is going to take forever (at least another 4 hours)...I am going to disable encryption and do some more testing. I am now more certain than ever, no-one has successfully restored a NANDROID on an encrypted OOS 9.0.4 phone ever.
I am going to disable Force Encryption and AVB 2.0/dm-verity and try my restore again -- maybe then I can use one of my NANDROIDS. But doing this on an encrypted phone seems impossible. I guess if you use a screen PIN you files are still vulnerable to someone that knows bootloader and / or recovery, but I'll have to live with that.... Not being able to NANDRIOD restore is a killer...

I know is an old discussion but I believe we still have this issue. I have a 6T, oos10.3.6 and neve succeeded to restore a nandroid backup. Does anyone found a working solution?
Thanks

Messed up upgrading to 10.3.4 - can't do anything now

Spent about 1 entire day now and I think am in worse shape than when started.
Rooted with Magisk went from 10.3.3 to 10.3.4, and the phone was working, but didn't have TWRP recovery.
So, putting that back on is when the trouble started. Got TWRP on, and all the phone would do was boot to recovery.
Have since tried lots of things, and learned, apparently a TWRP backup is of no use whatsoever - can't restore the phone from the backup. (Restore "restores" but it doesn't boot.)
As I tried different things (flashing the full 10.3.3 and/or 10.3.4 OTA), at one point I got the phone back booted, but wifi wouldn't turn on and the cell signal didn't work - and now, I'm at a point where with TWRP in either slot A or slot B, cannot mount Data partition.
Really stuck now - don't know what to do.
I have TWRP backup of 10.3.3 before I did the upgrade - but doesn't seem like it can be restored, and now I don't know if there's anything I can do to mount Data partition again?
What can I do?
Do I have to basically factory reset the phone? Any suggestions?
TIA!

relaxable said:
Spent about 1 entire day now and I think am in worse shape than when started.
Rooted with Magisk went from 10.3.3 to 10.3.4, and the phone was working, but didn't have TWRP recovery.
So, putting that back on is when the trouble started. Got TWRP on, and all the phone would do was boot to recovery.
Have since tried lots of things, and learned, apparently a TWRP backup is of no use whatsoever - can't restore the phone from the backup. (Restore "restores" but it doesn't boot.)
As I tried different things (flashing the full 10.3.3 and/or 10.3.4 OTA), at one point I got the phone back booted, but wifi wouldn't turn on and the cell signal didn't work - and now, I'm at a point where with TWRP in either slot A or slot B, cannot mount Data partition.
Really stuck now - don't know what to do.
I have TWRP backup of 10.3.3 before I did the upgrade - but doesn't seem like it can be restored, and now I don't know if there's anything I can do to mount Data partition again?
What can I do?
Do I have to basically factory reset the phone? Any suggestions?
TIA!
Click to expand...
Click to collapse
If you still have the cellular and wifi problem then you are not alone. Simply flashing android 9 image via edl mode and installing update to android 10 locally fixed for me. As you boot to 9 don't turn on wifi or cellular just download the update packages via pc, copy to internal storage then local update via system updates. Once you are on android 10 then install TWRP and root. TWRP backup only work if your data partition is decrypted.

relaxable said:
Spent about 1 entire day now and I think am in worse shape than when started.
Rooted with Magisk went from 10.3.3 to 10.3.4, and the phone was working, but didn't have TWRP recovery.
So, putting that back on is when the trouble started. Got TWRP on, and all the phone would do was boot to recovery.
Have since tried lots of things, and learned, apparently a TWRP backup is of no use whatsoever - can't restore the phone from the backup. (Restore "restores" but it doesn't boot.)
As I tried different things (flashing the full 10.3.3 and/or 10.3.4 OTA), at one point I got the phone back booted, but wifi wouldn't turn on and the cell signal didn't work - and now, I'm at a point where with TWRP in either slot A or slot B, cannot mount Data partition.
Really stuck now - don't know what to do.
I have TWRP backup of 10.3.3 before I did the upgrade - but doesn't seem like it can be restored, and now I don't know if there's anything I can do to mount Data partition again?
What can I do?
Do I have to basically factory reset the phone? Any suggestions?
TIA!
Click to expand...
Click to collapse
Hi,
Just a suggestion, was in this predicament before and the the thing that save me was my OTG USB stick with a USB C adapter, moved the latest rom(full rom 2.4gig) to it with TWRP installer , wiped( factory reset in twrp and installed the full update followed by TWRP installer. Reboot into recovery and did the same steps,
Reboot system,
Could never get MSM to work always param preload nonsense.... LOL.

relaxable said:
Spent about 1 entire day now and I think am in worse shape than when started.
Rooted with Magisk went from 10.3.3 to 10.3.4, and the phone was working, but didn't have TWRP recovery.
So, putting that back on is when the trouble started. Got TWRP on, and all the phone would do was boot to recovery.
Have since tried lots of things, and learned, apparently a TWRP backup is of no use whatsoever - can't restore the phone from the backup. (Restore "restores" but it doesn't boot.)
As I tried different things (flashing the full 10.3.3 and/or 10.3.4 OTA), at one point I got the phone back booted, but wifi wouldn't turn on and the cell signal didn't work - and now, I'm at a point where with TWRP in either slot A or slot B, cannot mount Data partition.
Really stuck now - don't know what to do.
I have TWRP backup of 10.3.3 before I did the upgrade - but doesn't seem like it can be restored, and now I don't know if there's anything I can do to mount Data partition again?
What can I do?
Do I have to basically factory reset the phone? Any suggestions?
TIA!
Click to expand...
Click to collapse
I'm not sure what you did.
How I normally upgrade is:
1. Local install
2. Install Magisk after OTA option
3. Reboot
4. Local install again, the other slot
5. TWRP zip install from Magic (do not reboot)
6. YOU ARE NOW UNROOTED.
7. Use Magisk Manager to do direct install (do not reboot)
8. Use Magisk Manager to do OTA install
9. Now reboot.
You have same firmware, TWRP and root on both slots.
If you can flash the stock boot image from 10.3.4 you can recover.

Thanks for all the replies.
I wish I could have done what Tech_Head wrote, but it wasn't happening for me.
I couldn't flash using OTG either as I couldn't mount USB with TWRP.
In the end, I was able to get back to life using the Fastboot flash method from This Thread, but, also not without complication

can't restore any TWRP backup

Hi there, Thaught, I was on the save side for 2 years, having my TWRP, made a backup after every change on the 12+, now I had to recover it...
Steady installed TWRP 3.3.1.0 on 1.68.401.6 does a restore without errors, restart ends with bootloop.
So I flashed new with 1.53.401.5, tried to fastboot boot twrp.3.2.3.3 and restore my backup -> bootloop
Flashed 1.53.401.5 again, made a backup of that fresh system with booted TWRP, to test that restore, brings the same bootloop.
Have to say, the twrp versions are the right ones for the used SW versions. Decryption is working.
Where is the blind spot in my brain??

Please delete my ask here, I'll try my luck in TWRP thread. Still my problem.