Cant boot into any ROM including stock - ZTE Axon 7 Questions & Answers

For some reason after dirty flashing the 11/22 CM build no SIM card was detected (but IMEI was intact). Because of this I decided to do a clean flash of CM 13 and that resulted in me being unable to boot it at all. After this I decided to restore back to a stock backup and that wouldnt boot at all. Later I flashed the b29 bootstack thinking this would resolve my issue and tried flashing CM again and I still couldnt boot into it (would start the boot animation then freeze and go black this happened previously and when I went back to stock). After all this I decided to flash the b29 system and that booted but now no IMEI shows up at all and I cant turn on wifi (as if the EFS partition was corrupt). Restored the EFS partition that did nothing. Tried reflashing CM after this and that still wont boot. Please help me!

ethanscooter said:
For some reason after dirty flashing the 11/22 CM build no SIM card was detected (but IMEI was intact). Because of this I decided to do a clean flash of CM 13 and that resulted in me being unable to boot it at all. After this I decided to restore back to a stock backup and that wouldnt boot at all. Later I flashed the b29 bootstack thinking this would resolve my issue and tried flashing CM again and I still couldnt boot into it (would start the boot animation then freeze and go black this happened previously and when I went back to stock). After all this I decided to flash the b29 system and that booted but now no IMEI shows up at all and I cant turn on wifi (as if the EFS partition was corrupt). Restored the EFS partition that did nothing. Tried reflashing CM after this and that still wont boot. Please help me!
Click to expand...
Click to collapse
There is a method through adb to restore your efs. Two months ago I had this problem.
Sent from my ZTE A2017U using XDA-Developers mobile app

troy5890 said:
There is a method through adb to restore your efs. Two months ago I had this problem.
Sent from my ZTE A2017U using XDA-Developers mobile app
Click to expand...
Click to collapse
he already have the device up and running.....hoping doesn't make the same mistake again. :silly:

DrakenFX said:
he already have the device up and running.....hoping doesn't make the same mistake again. :silly:
Click to expand...
Click to collapse
Whoops, glad he fixed and restored it to working condition [emoji2]
Sent from my ZTE A2017U using XDA-Developers mobile app

ethanscooter said:
For some reason after dirty flashing the 11/22 CM build no SIM card was detected (but IMEI was intact). Because of this I decided to do a clean flash of CM 13 and that resulted in me being unable to boot it at all. After this I decided to restore back to a stock backup and that wouldnt boot at all. Later I flashed the b29 bootstack thinking this would resolve my issue and tried flashing CM again and I still couldnt boot into it (would start the boot animation then freeze and go black this happened previously and when I went back to stock). After all this I decided to flash the b29 system and that booted but now no IMEI shows up at all and I cant turn on wifi (as if the EFS partition was corrupt). Restored the EFS partition that did nothing. Tried reflashing CM after this and that still wont boot. Please help me!
Click to expand...
Click to collapse
did u do a back up?/ id u did use the abd way to restore it

Yeah Unjustified dev showed me there's no point in backing up your efs because you can always simply rebuild it by running these two adb commands in twrp.
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 bs=16384
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2 bs=16384
Was able to get it booting and I fixed a OnePlus 2 that had a similar issue.

No cellular connection - please help
ethanscooter said:
Yeah Unjustified dev showed me there's no point in backing up your efs because you can always simply rebuild it by running these two adb commands in twrp.
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 bs=16384
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2 bs=16384
Was able to get it booting and I fixed a OnePlus 2 that had a similar issue.
Click to expand...
Click to collapse
Would you elaborate on this please? I flashed A2017U (and now A2017G) and lost all cellular connectivity although wifi works fine. I have no idea why this is happening as the rest of the phone seems to be working fine! I've tried 2 sim cards that work on other phones but the Axon 7 doesnt detect any networks.
Weirdly I had network service (4G) right after I flashed the A2017U B29 but was having a bug where I couldnt access Dual SIM settings (kept crashing) so I installed @DrakenFX s BootStack which fixed the settings crash - but I lost cellular connectivity... I've been stuck since
I gather its some issue with EFS - not sure how I can rebuild or repair it if as I suspect I've ruined it with all my installing. Please help!

Related

Accidentally wiped OS... need NOOB answer

To make a long story short, after unlocking bootloader and rooting a friend of mine thought it would be a GREAT idea to install Layers on a stock ROM... after that my phone goes black after the Motorola screen. Ended up wiping the OS off the phone and didn't have a chance to do a nandroid backup... I can get into TWRP just fine... is there anyway to get this thing working again... btw i tried the WIndows Tool with no success and tried it on a Mac with Terminal with no luck... Any ideas?
What exactly have you tried so far. The solution to issues like this is typically to get hold of a factory system image and ADB reflash the system partition while in fastboot mode.
See this post http://forum.xda-developers.com/showpost.php?p=63074207&postcount=89
The same happened to me and I if you are able to boot into TWRP, then you can follow the exact steps to re-flash the image files and be able to restore to factory stock.

Nexus 6p with Android 7.0 in bootloop cannot access recovery

Hi Guys,
I'm Kinda new about making a new thread, so if anything's wrong let me know.
Just last evening my nexus 6p (on Android 7.0 official) got into a boot loop from a normal state. It just boots & right after when the white google logo transforms into 4 round object, it just reboots (it takes about 3-5 secs). I can access the boot loader but was unable to access to recovery from there as that takes it to bootloop again. I've tried flashing it, but since i had already updated to Nougat official version & the official image for 6p is yet to come, i tried with some earlier version of Marshmallow. but that failed as well. can it be that i need to select the right version of factory image as i really do not remember my old marshmallow versions anymore.
It seems i'm out of options right now. :crying:
Any advice guys??
TIA
Found this on Nexus 6p help forum. Haven't tried it though so I'm unable to confirm if it works or not.
https://productforums.google.com/forum/#!topic/nexus/hdrNONCCoNE
@sirluigi, this EXACT thing just happened to me ..
stock nougat, only bootloader unlocked ((( and since I've got no access to recovery and no Nougat image, I don't know what to do next
minicoop7, unfortunately, for that guide I need to go into recovery mode
ciocu said:
@sirluigi, this EXACT thing just happened to me ..
stock nougat, only bootloader unlocked ((( and since I've got no access to recovery and no Nougat image, I don't know what to do next
minicoop7, unfortunately, for that guide I need to go into recovery mode
Click to expand...
Click to collapse
Have you tried using fastboot to temp boot to recovery?
fastboot boot twrp-3.0.2-1-angler.img
downloading 'boot.img'...
OKAY [ 0.409s]
booting...
OKAY [ 0.680s]
finished. total time: 1.097s
Click to expand...
Click to collapse
same behavior, nothing but a bootloop
I'm dowloading an official MM image, just to get the stock recovery and see if I can temp boot in it
edit: not possible, I even tried to flash twrp, I tried flashing stock recovery from MTC20F.. tried to temp boot in both, all with no luck and with phone constantly alternating between the "Your device cannot be checked for corruption" screen and the white Google screen with the open lock.
sirluigi said:
Hi Guys,
I'm Kinda new about making a new thread, so if anything's wrong let me know.
Just last evening my nexus 6p (on Android 7.0 official) got into a boot loop from a normal state. It just boots & right after when the white google logo transforms into 4 round object, it just reboots (it takes about 3-5 secs). I can access the boot loader but was unable to access to recovery from there as that takes it to bootloop again. I've tried flashing it, but since i had already updated to Nougat official version & the official image for 6p is yet to come, i tried with some earlier version of Marshmallow. but that failed as well. can it be that i need to select the right version of factory image as i really do not remember my old marshmallow versions anymore.
It seems i'm out of options right now. :crying:
Any advice guys??
TIA
Click to expand...
Click to collapse
Guys its very simple, flash the stock mtc20f image first. After that boot it, it wont work but don't worry. Onece it bootloops go into bootloader and fastboot flash twrp 3.0.2-0. once thats done boot into twrp recovery. Onece in twrp make a backup of the image you just flashed that don't work. Once thats done mount system in recovery. Once mounted plug phone into computer and open the twrp folder you will see on your internal wich will have the backup that you just made. Transfer an old working backup into that folder that way twrp will recognize that backup. Once the backup is in the folder you shoukd see 2 backups in there, your new one that doesn't boot and your old one that does work wich you just put into the twrp folder. Once done go to restore and restore the backup of the working rom you just put in there, make sure to check off all on restore. Once done reboot system and it should boot. This will only work if you have a backup of an old working rom.
---------- Post added at 01:13 AM ---------- Previous post was at 01:00 AM ----------
sirluigi said:
Hi Guys,
I'm Kinda new about making a new thread, so if anything's wrong let me know.
Just last evening my nexus 6p (on Android 7.0 official) got into a boot loop from a normal state. It just boots & right after when the white google logo transforms into 4 round object, it just reboots (it takes about 3-5 secs). I can access the boot loader but was unable to access to recovery from there as that takes it to bootloop again. I've tried flashing it, but since i had already updated to Nougat official version & the official image for 6p is yet to come, i tried with some earlier version of Marshmallow. but that failed as well. can it be that i need to select the right version of factory image as i really do not remember my old marshmallow versions anymore.
It seems i'm out of options right now. :crying:
Any advice guys??
TIA
Click to expand...
Click to collapse
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help
disbeyad999989 said:
Guys its very simple, flash the stock mtc20f image first. After that boot it, it wont work but don't worry. Onece it bootloops go into bootloader and fastboot flash twrp 3.0.2-0. once thats done boot into twrp recovery. Onece in twrp make a backup of the image you just flashed that don't work. Once thats done mount system in recovery. Once mounted plug phone into computer and open the twrp folder you will see on your internal wich will have the backup that you just made. Transfer an old working backup into that folder that way twrp will recognize that backup. Once the backup is in the folder you shoukd see 2 backups in there, your new one that doesn't boot and your old one that does work wich you just put into the twrp folder. Once done go to restore and restore the backup of the working rom you just put in there, make sure to check off all on restore. Once done reboot system and it should boot. This will only work if you have a backup of an old working rom.
---------- Post added at 01:13 AM ---------- Previous post was at 01:00 AM ----------
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help
Click to expand...
Click to collapse
Unfortunately, this didn't work for me.
I believe you should be fine with just trying to flash an earlier recovery version using fastboot... if you're trying to save your data and then factory flash MM and then restore your data to the phone, you should be able to use fastboot pull and then copy them back once you've got a working device by simple copy from windows.
disbeyad999989 said:
Guys its very simple, flash the stock mtc20f image first. After that boot it, it wont work but don't worry. Onece it bootloops go into bootloader and fastboot flash twrp 3.0.2-0. once thats done boot into twrp recovery. Onece in twrp make a backup of the image you just flashed that don't work. Once thats done mount system in recovery. Once mounted plug phone into computer and open the twrp folder you will see on your internal wich will have the backup that you just made. Transfer an old working backup into that folder that way twrp will recognize that backup. Once the backup is in the folder you shoukd see 2 backups in there, your new one that doesn't boot and your old one that does work wich you just put into the twrp folder. Once done go to restore and restore the backup of the working rom you just put in there, make sure to check off all on restore. Once done reboot system and it should boot. This will only work if you have a backup of an old working rom.
---------- Post added at 01:13 AM ---------- Previous post was at 01:00 AM ----------
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help
Click to expand...
Click to collapse
Can you elaborate the steps pls? also have you had an earlier back up of your phone which i don't have?
Has anyone been able to get this to work without being able to get into TWRP? I can't get into recovery whether it is a temp boot to it, or fastboot flash either version..
I have compiled a list of the 20+ methods from various users in THIS thread. It's the second post.
Stuck in a bootloop still @tr4nqui1i7y but will try your methods as well... Fingers crossed..
So I do not if this may help anyone who as run into this issue but still may want to retrieve their data before formating their data or factory resetting. While running TWRP 3.0.3 and flashing the latest 7.1.1 files for angler. I would sometimes be able to boot into the recovery like 3/10 tries ( from the bootloader menu). My data was encrypted and it woul freeze constantly when trying to decrypt soo i decided once I finally got it to boot again in the recovery menu(TWRP after hours mind you) I let the phone stay idle for a few mins should the cpu would cool down that my battery percentage would drop around 41% and the tried to decrypt data which went tru successfully. I retrieve what I Could and it froze during a process of a nandroid backup and started bootlooping again. I believe the battery percentage may be linked to the early shutdown issues that many user were reported having and the bootloop of death we are experiencing. Hopefully this info may help someone else.

Bootloops when flashing System, Data

It first started this morning when my phone suddenly started rebooting while I was using it. Then I thought it as a ROM issue and flashed a new ROM over it. Everytime I try to flash something on system. TWRP Hangs and the phone restarts itself.
Tried repairing data, system partitions from TWRP, same thing happens. Bootloops when I try to repair data partition
Tried restoring nandroid backup. When it says flashing data, TWRP freezes and the phone starts bootlooping.
Can anyone help?
I have tried doing the EFS flash via adb from PC.
I'm stuck with the exact same problem since months.
CallMeAldy said:
I'm stuck with the exact same problem since months.
Click to expand...
Click to collapse
No luck?
Have you tried Claiming Warranty?
try doing a re flash of recovery, because your issue will be to get your recovery working properly or else you cant remount anything else.
StarRavier said:
try doing a re flash of recovery, because your issue will be to get your recovery working properly or else you cant remount anything else.
Click to expand...
Click to collapse
I flashed TWRP 3.0.2,3.0.2-2,3.0.2-3
Loads of it. Tried doing full stock + unroot from Nexus toolkit. That usually fixed all my problems Everytime I was in dire problems like this.
TJ_bab said:
I flashed TWRP 3.0.2,3.0.2-2,3.0.2-3
Loads of it. Tried doing full stock + unroot from Nexus toolkit. That usually fixed all my problems Everytime I was in dire problems like this.
Click to expand...
Click to collapse
I've never used that toolkit. Since day 1, ive used skipsoft android toolkit. just keep on trying. Does it crash at all when doing backups?
StarRavier said:
I've never used that toolkit. Since day 1, ive used skipsoft android toolkit. just keep on trying. Does it crash at all when doing backups?
Click to expand...
Click to collapse
Doesn't crash during backup but crashes during restore.
TJ_bab said:
Doesn't crash during backup but crashes during restore.
Click to expand...
Click to collapse
Well in your case what I would do is a backup,
Then wipe, flash custom rom. Use phone til reboot.
If reboot, flash stock IMG. Use till reboot
If still rebooting, then come back. I guess I never asked.what rom.your using
StarRavier said:
Well in your case what I would do is a backup,
Then wipe, flash custom rom. Use phone til reboot.
If reboot, flash stock IMG. Use till reboot
If still rebooting, then come back. I guess I never asked.what rom.your using
Click to expand...
Click to collapse
it doesn't boot at all.
It bootloops
I have the exact same problem. Last week upgraded to 7.0, root, stock room, viper4arise audio and EX kernel and that's it. while taking pictures it froze then that boot loop, somehow I managed through a combination of flashing factory image through fastboot, locking, unlocking, reflahsing, to get it to boot normally, then yesterday I was taking pictures again and it refroze then bootloops. Now I am able to fastboot factory images but it doesn't get me out of the bootloops, and in TRWP same as you, I cannot flash anything on data or system. Repairing the file system doesn'T change anything, I did like on other threads also and flashed factury, restored nandroid then flash factory but the restore on TRWP always hangs up.
I was wondering if there is someone knowing the adb dd commands to impose the raw copying back of the restore ? Maybe that would work.
Did you try wiping system under wipe > advanced in TWRP?
In twrp, can you open a terminal and check the results of this (basically, doing a full read-only test of your flash)
Code:
dd if=/dev/block/mmcblk0 of=/dev/null

[HELP] Phone stuck at RR boot animation

Hi all!
So I have a Moto G4 Plus on 7.1.2 RR with Magisk root. I installed ElementalX kernel and overclocked and disabled fsync. However, as I was watching YouTube, my phone randomly froze and rebooted and wouldn’t boot up. It’d be stuck at the boot animation forever. Seeing this, I took a logcat and here is a link to it. I noticed that this line kept looping:
Code:
java.lang.NullPointerException: Attempt to read from field 'java.lang.String com.android.server.pm.Settings$VersionInfo.fingerprint' on a null object reference
I searched the error up on Google, and it led me to this StackExchange site. I had the same symptoms (the jobs.xml file was empty, I turned off fsync, etc.), so I did as it said (I backed up my data partition and did rm -rf /data/system), and I thought my problem was solved, but when I tried booting up my phone again, it still got stuck at the boot animation. Granted, the logcat was different now (here is a link to it), but it keeps looping at:
Code:
waiting for service sensorservice
or
Code:
waiting for service AtCmdFwd
I tried googling for that, but I couldn’t find any useful results, so I guess now I'm stuck. Any suggestions where to go from here?
Thanks so much!
@strongst and @sd_shadow, would you guys be willing to give some advice? I've been stuck without a phone for a couple of weeks now...
matetoes said:
@strongst and @sd_shadow, would you guys be willing to give some advice? I've been stuck without a phone for a couple of weeks now...
Click to expand...
Click to collapse
I would just reflash firmware, Fastboot.exe
sd_shadow said:
I would just reflash firmware, Fastboot.exe
Click to expand...
Click to collapse
Which partitions? Can I do it without losing my data (i.e. only reflash system or something)?
matetoes said:
Which partitions? Can I do it without losing my data (i.e. only reflash system or something)?
Click to expand...
Click to collapse
You can try reflashing just system, but I wouldn't count on any method saving data.
Sent from my Gemini 4G using XDA Labs
sd_shadow said:
You can try reflashing just system, but I wouldn't count on any method saving data.
Sent from my Gemini 4G using XDA Labs
Click to expand...
Click to collapse
I just gave up and updated to Pie with Arrow OS ¯\_(ツ)_/¯. At least it wasn't a hardware problem.
In these type of cases, flash RR on on top of your current ROM (without wiping anything i.e dirty flashing).
It seems like kernel issue and when you flash RR again, it will replace the custom kernel and you will have your RR kernel back.
Edit: you won't lose any data by this method.
Heeth21 said:
In these type of cases, flash RR on on top of your current ROM (without wiping anything i.e dirty flashing).
It seems like kernel issue and when you flash RR again, it will replace the custom kernel and you will have your RR kernel back.
Edit: you won't lose any data by this method.
Click to expand...
Click to collapse
Yeah, I tried that. I first wiped the data partition as instructed by the [URL="hthttps://android.stackexchange.com/questions/157601/marshmallow-not-bootlooping-but-not-starting]StackExchange post[/URL] then dirty flashed latest RR, but after waiting 10-15 minutes, I could still see those two messages (waiting for service sensorservice and waiting for AtCmdFwd). I have Nandroid backups of that bootlooped state but I'm kinda stumped on how to recover it at this point
matetoes said:
Yeah, I tried that. I first wiped the data partition as instructed by the [URL="hthttps://android.stackexchange.com/questions/157601/marshmallow-not-bootlooping-but-not-starting]StackExchange post[/URL] then dirty flashed latest RR, but after waiting 10-15 minutes, I could still see those two messages (waiting for service sensorservice and waiting for AtCmdFwd). I have Nandroid backups of that bootlooped state but I'm kinda stumped on how to recover it at this point
Click to expand...
Click to collapse
No, no need to wipe any partition......Just reflash RR without wiping anything except cache/dalvik.
And are you using some mods like Xposed? If yes, first flash their uninstalling zip from TWRP i.e uninstall them, then flash RR again(without wiping anything).
If that doesnt work too, then it doesn't seems like kernel issue.
Heeth21 said:
No, no need to wipe any partition......Just reflash RR without wiping anything except cache/dalvik.
And are you using some mods like Xposed? If yes, first flash their uninstalling zip from TWRP i.e uninstall them, then flash RR again(without wiping anything).
If that doesnt work too, then it doesn't seems like kernel issue.
Click to expand...
Click to collapse
I didn't using anything like Xposed. I had systemless root with Magisk and passed SafetyNet.
Actually, I did not wipe data, I just removed /data/system because some files like jobs.xml were empty and the phone didn't know how to start if those were empty. The reasoning was that if /data/system was gone, the phone would regenerate all those files and I could copy those files to my computer, restore the Nandroid backup before the removal of that folder, then copy back those files.
Alas, the phone still would not boot after removing /data/system so there must be some other problem going on (perhaps kernel issue, as you mentioned). I took Nandroid backups before and after every step I took so if you have any idea how to fix it we can always go back if something gets messed up.

Encryption, BAAHHHH! I just want to keep my data.

So, I decided to upgrade my OP6T with Renovate on it. Booted into TWRP (official from their website), did a Nandroid Backup. Now, I did remove my fingerprint and other security before starting. Flashed the full 9.0.14, reflashed TWRP, rebooted into TWRP, flashed Magisk, and then trid to boot into system. Got a bootloop where the phone was jumping in and out of the bootloader message. I tried to stop it by pressing power and volume down and it ended up booting into safe mode. I didn't like that so I booted into TWRP and restored my Nandroid. And that's when the fight started.
It won't boot into anything but TWRP now and everything is encrypted. I have been here before but last time, I got the device totally corrupt message and used MSM to recover. But that was within two weeks of owning the phone. Now it's been three months or so and I do not relish loosing all the pictures and other setting/changes I've made to my apps etc. I am NOT liking this decryption stuff.
So, is there something, anything I can do short of a fastboot rom and/or MSM tool that we all know will wipe out all data. What if I used the unofficial TWRP? Sideload the ROM again?
Any help is appreciated. I hope I didn't make this too long, but long enough to give enough detail of how I got here and that I somewhat know what I'm doing. Been doing this since the OG Motorola Droid almost 10 years ago.
That's usually why backup is always a good idea and in some case, mandatory.
It usually depends on what TWRP version you are using, the recent unofficial TWRP can decrypt the whole /data directory no problem. However, it's possible to brick a slot, and be able to salvage your files in other slot. I have this problem, so I will have to figure out how to remove the encryption keys after backing up my stuff off the phone so I can have both slots functional (Slot A in my OnePlus 6T is bricked, so right now I'm on Slot B, with AOSiP, FrancoKernel and TWRP 3.3.1-6 on it). Dual-boot setup can be both your friend and enemy.
Nevertheless, I would give TWRP 3.3.1-6 bootable image via fastboot a try, and see if you could be able to recover your files from thereon.
Sent from my ONEPLUS 6T using Tapatalk
I tried asking about this in the twrp thread no replies as of yet.... man I miss the days of epic4g touch (s2) days I could flash a rom , brick my phone and just restore my twrp or clockwork mod recovery back ups...I used to show off all the roms I had from back ups....I tried making a back up when we first got root and twrp for this phone and I definitely had to use msm tool to get my phone back up and running
mlock420 said:
I tried asking about this in the twrp thread no replies as of yet.... man I miss the days of epic4g touch (s2) days I could flash a rom , brick my phone and just restore my twrp or clockwork mod recovery back ups...I used to show off all the roms I had from back ups....I tried making a back up when we first got root and twrp for this phone and I definitely had to use msm tool to get my phone back up and running
Click to expand...
Click to collapse
Me too. This a/b partition crap and force decryption takes all the fun out of trying new roms. So far it seems to be pointless taking a Nandroid if restoring it just soft bricks your phone. And from what I'm reading, flashing even a updated ROM almost always has to be done very clean, heck it seems like wiping your 'sdcard' is also mandatory. I'm just hoping the above suggestion of trying the different TWRP will allow me to at least get some stuff off my 'sdcard' but I secretly hope I can get into system once just to take a titanium.
Then it's wipe and trade for the oneplus 7 pro, root it and rom it once and call it a day.
I can back up and restore nandroid no issue although I remove any pin code/face unlock/fingerprint prior to backing up. No issues.
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app
ozzmanj1 said:
I can back up and restore nandroid no issue although I remove any pin code/face unlock/fingerprint prior to backing up. No issues.
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Just curious, what TWRP version are you on? I checked the TWRP website and they only have 3.2.?.? available there while mauronofrio (who is named as maintainer at TWRP) has 3.3.1.6 available in the thread here at XDA:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
So. Today I tried to get this thing up and running. I went to the TWRP thread mentioned above and downloaded the latest files. Booted into bootloader, ran flashboot boot xxx.img and it booted into 3.3.1.6 just fine. The 'sdcard' was still encrypted so I couldn't copy the .img file and flash it via the newst instructions, , so I did an adb sideload of the installer file. That flashed just fine and I used TWRP to reboot recovery. Check. 'sdcard' still encrypted. Since this encryption issue seems to happen if you upgrade to a newer security patch and I had tried to do an nandroid restore of an earlier version, at the end I tried this (I did try those steps with 9.0.12 full ROM first, the version of my nandroid):
adb sideload of the full 9.0.14 rom (the upgrade that got me into this dang fix). Then adb sideload of the TWRP installer. Then adb sideload of Magisk since I have read that this needs to be done after TWRP to make your phone boot. Still no good. Won't boot into anything but recovery. Tried the 3.3.1.6 advanced 'fix recovery reboot' or whatever it is, still to no avail.
At least I still have the yellow exclamation point and not the red one. And TWRP 3.3.1.6 stuck, so I am at the latest TWRP there is, at least from what I know.
Any more help or ideas so I can at least boot into my system one last time so I can do some Titanium or even the OnePlus backup? I just have some data that to backup correctly, I need to be able to boot system without wiping my data.
Please?
teddyearp said:
So. Today I tried to get this thing up and running. I went to the TWRP thread mentioned above and downloaded the latest files. Booted into bootloader, ran flashboot boot xxx.img and it booted into 3.3.1.6 just fine. The 'sdcard' was still encrypted so I couldn't copy the .img file and flash it via the newst instructions, , so I did an adb sideload of the installer file. That flashed just fine and I used TWRP to reboot recovery. Check. 'sdcard' still encrypted. Since this encryption issue seems to happen if you upgrade to a newer security patch and I had tried to do an nandroid restore of an earlier version, at the end I tried this (I did try those steps with 9.0.12 full ROM first, the version of my nandroid):
adb sideload of the full 9.0.14 rom (the upgrade that got me into this dang fix). Then adb sideload of the TWRP installer. Then adb sideload of Magisk since I have read that this needs to be done after TWRP to make your phone boot. Still no good. Won't boot into anything but recovery. Tried the 3.3.1.6 advanced 'fix recovery reboot' or whatever it is, still to no avail.
At least I still have the yellow exclamation point and not the red one. And TWRP 3.3.1.6 stuck, so I am at the latest TWRP there is, at least from what I know.
Any more help or ideas so I can at least boot into my system one last time so I can do some Titanium or even the OnePlus backup? I just have some data that to backup correctly, I need to be able to boot system without wiping my data.
Please?
Click to expand...
Click to collapse
This is the actual way to install or upgrade an OS
Boot to TWRP
ADB sideload oos 9.0.14
ADB sideload TWRP installer
Reboot system (Yes boot to system not TWRP..don't flash Magisk too now)
Let the phone boot
Go back to TWRP
Install Magisk
teddyearp said:
So, I decided to upgrade my OP6T with Renovate on it. Booted into TWRP (official from their website), did a Nandroid Backup. Now, I did remove my fingerprint and other security before starting. Flashed the full 9.0.14, reflashed TWRP, rebooted into TWRP, flashed Magisk, and then trid to boot into system. Got a bootloop where the phone was jumping in and out of the bootloader message. I tried to stop it by pressing power and volume down and it ended up booting into safe mode. I didn't like that so I booted into TWRP and restored my Nandroid. And that's when the fight started.
It won't boot into anything but TWRP now and everything is encrypted. I have been here before but last time, I got the device totally corrupt message and used MSM to recover. But that was within two weeks of owning the phone. Now it's been three months or so and I do not relish loosing all the pictures and other setting/changes I've made to my apps etc. I am NOT liking this decryption stuff.
So, is there something, anything I can do short of a fastboot rom and/or MSM tool that we all know will wipe out all data. What if I used the unofficial TWRP? Sideload the ROM again?
Any help is appreciated. I hope I didn't make this too long, but long enough to give enough detail of how I got here and that I somewhat know what I'm doing. Been doing this since the OG Motorola Droid almost 10 years ago.
Click to expand...
Click to collapse
What you should have done is not flashed magisk, but booted back to recovery, flashed oos again so you have it on both slots. Flashed TWRP again, booted back to recovery then flashed magisk and then to system.
If you had encountered encryption, you could either start fresh with MSM and have to re-root. Or you could have wiped data and sideloaded OOS & TWRP from an OTG or PC so you wouldn't have to go through the process of using adb and re-rooting.
Well, thank you two very much, but . . . . crud. Here's what I've done now:
per sanjeev7 I did this:
Code:
boot to TWRP (it won't boot to anything else, lol)
adb sideload OnePlus6TOxygen_34_OTA_021_all_1905281358_e3b3.zip
adb sideload twrp-3.3.1-6-fajita-installer.zip
Reboot system
It didn't boot to system, but booted back into TWRP so the additional step to sideload Magisk was moot.
So, then I went with what ebproject said above which on the surface looked more promising(?):
Code:
Boot TWRP
adb sideload OnePlus6TOxygen_34_OTA_021_all_1905281358_e3b3.zip
adb sideload twrp-3.3.1-6-fajita-installer.zip
Reboot to TWRP via phone
adb sideload OnePlus6TOxygen_34_OTA_021_all_1905281358_e3b3.zip
adb sideload twrp-3.3.1-6-fajita-installer.zip
Reboot TWRP via phone
adb sideload Magisk-v19.3.zip
Reboot System
Still would not boot into system, but just back to recovery (TWRP).
I know I could probably do a data wipe after sideload TWRP installer, but I'm being stubborn. I have an app called Fuel Log that I track all my vehicle expenses on. I can make a backup within the software that I can then copy from the 'sdcard'. And I also have pdf maps which I would like to be able to access my 'sdcard' to get the most recent maps from, but it would be easy enough to get the two or six newest maps since my last backup of the files from my 'sdcard'. And then there's my stock tracking app which I don't think I can backup my current stuff without doing a Titanium. Still could be done manually. So at the end of the day, I really wish I could get into system just once to backup fuel log.
None of it is the end of the world, as I am going to receive a Oneplus 7 Pro tomorrow. I just wish I could make as seamless a transition as possible. I do have Titanium backups from a few months ago for all these above named apps, but like I said, if anyone has any ideas, please let me know.
What if I did the second set using OOS 9.0.12 instead of 9.0.14 since that is the version of the Nandroid backup that I restored? Or, and this is a long shot I know, what if I flashed a different ROM altogether? I do know that dirty flashing a different ROM is almost impossible, but maybe?
That's a classic symptoms of the loss of encryption keys for the /data directory (for some reasons, despite the dual-boot setup sharing the same /data directory, but uses two separate different keys for each slots - a definite bad idea).
Sent from my ONEPLUS 6T using Tapatalk
teddyearp said:
Well, thank you two very much, but . . . . crud. Here's what I've done now:
per sanjeev7 I did this:
Code:
boot to TWRP (it won't boot to anything else, lol)
adb sideload OnePlus6TOxygen_34_OTA_021_all_1905281358_e3b3.zip
adb sideload twrp-3.3.1-6-fajita-installer.zip
Reboot system
It didn't boot to system, but booted back into TWRP so the additional step to sideload Magisk was moot.
So, then I went with what ebproject said above which on the surface looked more promising(?):
Code:
Boot TWRP
adb sideload OnePlus6TOxygen_34_OTA_021_all_1905281358_e3b3.zip
adb sideload twrp-3.3.1-6-fajita-installer.zip
Reboot to TWRP via phone
adb sideload OnePlus6TOxygen_34_OTA_021_all_1905281358_e3b3.zip
adb sideload twrp-3.3.1-6-fajita-installer.zip
Reboot TWRP via phone
adb sideload Magisk-v19.3.zip
Reboot System
Still would not boot into system, but just back to recovery (TWRP).
I know I could probably do a data wipe after sideload TWRP installer, but I'm being stubborn. I have an app called Fuel Log that I track all my vehicle expenses on. I can make a backup within the software that I can then copy from the 'sdcard'. And I also have pdf maps which I would like to be able to access my 'sdcard' to get the most recent maps from, but it would be easy enough to get the two or six newest maps since my last backup of the files from my 'sdcard'. And then there's my stock tracking app which I don't think I can backup my current stuff without doing a Titanium. Still could be done manually. So at the end of the day, I really wish I could get into system just once to backup fuel log.
None of it is the end of the world, as I am going to receive a Oneplus 7 Pro tomorrow. I just wish I could make as seamless a transition as possible. I do have Titanium backups from a few months ago for all these above named apps, but like I said, if anyone has any ideas, please let me know.
What if I did the second set using OOS 9.0.12 instead of 9.0.14 since that is the version of the Nandroid backup that I restored? Or, and this is a long shot I know, what if I flashed a different ROM altogether? I do know that dirty flashing a different ROM is almost impossible, but maybe?
Click to expand...
Click to collapse
Okay, to start off, before you started any of this what was you OS were you running?
That's what you need to try and sideload to try get the encryption back to normal because of the mismatch in security patches.
teddyearp said:
Well, thank you two very much, but . . . . crud. Here's what I've done now:
per sanjeev7 I did this:
Code:
boot to TWRP (it won't boot to anything else, lol)
adb sideload OnePlus6TOxygen_34_OTA_021_all_1905281358_e3b3.zip
adb sideload twrp-3.3.1-6-fajita-installer.zip
Reboot system
It didn't boot to system, but booted back into TWRP so the additional step to sideload Magisk was moot.
So, then I went with what ebproject said above which on the surface looked more promising(?):
Code:
Boot TWRP
adb sideload OnePlus6TOxygen_34_OTA_021_all_1905281358_e3b3.zip
adb sideload twrp-3.3.1-6-fajita-installer.zip
Reboot to TWRP via phone
adb sideload OnePlus6TOxygen_34_OTA_021_all_1905281358_e3b3.zip
adb sideload twrp-3.3.1-6-fajita-installer.zip
Reboot TWRP via phone
adb sideload Magisk-v19.3.zip
Reboot System
Still would not boot into system, but just back to recovery (TWRP).
I know I could probably do a data wipe after sideload TWRP installer, but I'm being stubborn. I have an app called Fuel Log that I track all my vehicle expenses on. I can make a backup within the software that I can then copy from the 'sdcard'. And I also have pdf maps which I would like to be able to access my 'sdcard' to get the most recent maps from, but it would be easy enough to get the two or six newest maps since my last backup of the files from my 'sdcard'. And then there's my stock tracking app which I don't think I can backup my current stuff without doing a Titanium. Still could be done manually. So at the end of the day, I really wish I could get into system just once to backup fuel log.
None of it is the end of the world, as I am going to receive a Oneplus 7 Pro tomorrow. I just wish I could make as seamless a transition as possible. I do have Titanium backups from a few months ago for all these above named apps, but like I said, if anyone has any ideas, please let me know.
What if I did the second set using OOS 9.0.12 instead of 9.0.14 since that is the version of the Nandroid backup that I restored? Or, and this is a long shot I know, what if I flashed a different ROM altogether? I do know that dirty flashing a different ROM is almost impossible, but maybe?
Click to expand...
Click to collapse
I replicated ur situation...and I have one cheat code for u
Boot into SLOT B if u r in SLOT A or vice versa!
The other SLOT is taking backup of current system before flashing successfully!! Try this!
---------- Post added at 11:31 AM ---------- Previous post was at 11:29 AM ----------
sanjeev7 said:
I replicated ur situation...and I have one cheat code for u
Boot into SLOT B if u r in SLOT A or vice versa!
The other SLOT is taking backup of current system before flashing successfully!! Try this!
Click to expand...
Click to collapse
U can WhatsApp me on +918898340211
I would like to help u coming out! I have some experience in this!
If you are not sure how to boot into either slots in Fastboot, here's the slot switch command;
fastboot --set-active=a
(Set to Slot A, substitute with B if you want to boot into Slot B.)
Afterwards, reboot (you can alternatively reboot into the bootloader by typing into "fastboot reboot-bootloader" so you can retry the data salvation via fastbooted TWRP).
Sent from my ONEPLUS 6T using Tapatalk
ebproject said:
Okay, to start off, before you started any of this what was you OS were you running?
That's what you need to try and sideload to try get the encryption back to normal because of the mismatch in security patches.
Click to expand...
Click to collapse
I was on 9.0.12. I did already sideload the 9.0.12 app then sideload TWRP (version I mentioned above) then sideload Magisk. I obviously took a bit of a break, rec'd my OnePlus 7 Pro last night. And of course, like any good Andoird'er I had to get it all rooted and stuff, you know, first things first, lol. So tonight I will probably try some more.
As in I'll sideload 9.0.12, sideload TWRP, reboot system and if it works I'll not really worry about magisk since I will be in.
Thank you very much.
sanjeev7 said:
I replicated ur situation...and I have one cheat code for u
Boot into SLOT B if u r in SLOT A or vice versa!
The other SLOT is taking backup of current system before flashing successfully!! Try this!
---------- Post added at 11:31 AM ---------- Previous post was at 11:29 AM ----------
U can WhatsApp me on +918898340211
I would like to help u coming out! I have some experience in this!
Click to expand...
Click to collapse
Wow, thanks. I don't have Whatsapp and as my signature says, I usually try to read read read, then after doing some steps with fail, I give up and post, lol. So I was done by the time I posted.
Like I said in my previous post, I rec'd my 7 Pro last night and got it ready to be set the rest of the way up, so tonight I will try this new method. Just curious, should I do the slot switch within TWRP or should I do it as Dr. Mario said and use fastboot to switch?
Thanks a bunch everyone.
teddyearp said:
Wow, thanks. I don't have Whatsapp and as my signature says, I usually try to read read read, then after doing some steps with fail, I give up and post, lol. So I was done by the time I posted.
Like I said in my previous post, I rec'd my 7 Pro last night and got it ready to be set the rest of the way up, so tonight I will try this new method. Just curious, should I do the slot switch within TWRP or should I do it as Dr. Mario said and use fastboot to switch?
Thanks a bunch everyone.
Click to expand...
Click to collapse
U can simply go to TWRP and click on REBOOT...u will get option...SLOT A....SLOT B....try both the slots...one one time...I hope u boot!!
I was able to!
Either fastboot or TWRP, you can use either methods of switching the active slots. TWRP is much easier though.
Sent from my ONEPLUS 6T using Tapatalk
Well boys, I can't say I/we didn't give it the old college try. Dang it!
So, I'm not going to put out as much detail as I did before since by now you know what I'm doing step by step. I'll point out that the 9.0.12 file (yes I used that one) I used is this one: OnePlus6TOxygen_34_OTA_019_all_1901231347_fb09dd2d4.zip
So:
Boot into TWRP
sideload ROM
sideload TWRP
Went to reboot menu (in TWRP) saw that I was on slot a, but just used the Recovery reboot button. Once back into TWRP, I went again to the Reboot menu and saw that I was already now on slot b. Repeated above and then sideloaded Magisk. Reboot. Back to TWRP only. Ugh! Tried it again, but instead of rebooting TWRP after the one slot, just changed slots without rebooting TWRP and repeated. Did not sideload Magisk. Still a fail.
I'm about done here, but there was one message on my computer within the command window that was shown after the second flash of the ROM on both tries:
ADB: Failed to read command: no error.
What a journey! Thanks guys. And/or girls if any of you are girls, hehe.
ozzmanj1 said:
I can back up and restore nandroid no issue although I remove any pin code/face unlock/fingerprint prior to backing up. No issues.
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app
Click to expand...
Click to collapse
teddyearp said:
<snip> Now, I did remove my fingerprint and other security before starting. <snip>
Click to expand...
Click to collapse
Thank you, but I do believe that I did do that.

Categories

Resources