Related
Hello all,
I have a shiny new Sprint LG G2 that I want to flash with CM11. I haven't done anything to it yet; it's currently installing the ZV8 OTA update (and has been for about half an hour, but that's another story).
Before I flash it with anything, I want to make double sure that I can restore it to stock (or to stock post-OTA). Unfortunately, I run Ubuntu, and the only return-to-stock tutorials I have seen are like this one and require hacking up a copy of LG's Windows-only "LG Flash Tool".
I have found a procedure to recover from a few different kinds of soft-bricking, including trying to do an OTA on a non-stock recovery, or having messed up one's boot partitions so the secure boot checks do not pass. It appears that when the phone is in "qhsusb_bulk" mode, Ubuntu will automatically (with no additional drivers) detect it as a 36-partition block device, whereupon you can just dd things to and from all of the various partitions on the phone.
1. If were to get my phone into "qhsusb_bulk" mode, could I just dd all 36 partitions to their own image files from the host PC, and restore them later by doing the reverse?
2. How do I put a Sprint G2 variant (LS980) into "qhsusb_bulk" mode? Do I have to screw up something so that it will fail to boot?
3. Is there any documentation I can read on "qhsusb_bulk" mode? Is it possible to brick the phone so badly by overwriting the wrong partition that I can't get into it to fix it?
4. Is there some other equivalent of the LG Flash Tool process for Linux?
Thanks in advance!
You should just install custom recovery, backup stock ROM, factory reset everything, Install CM11 & GAPPS, and move the stock backup to your laptop or keep on your phone?
That's what I did when i first got my phone, I right away went home backed up stock ROM and flash Paranoid Android. I just went back to stock yesterday from my backup and it's working great
I'm running Ubuntu 13.10 and if anything goes wrong, meaning if you get into a bootloop or recoveryloop, I always adb sideload a ROM and get it up and running again.
xxxrichievxxx said:
You should just install custom recovery, backup stock ROM, factory reset everything, Install CM11 & GAPPS, and move the stock backup to your laptop or keep on your phone?
That's what I did when i first got my phone, I right away went home backed up stock ROM and flash Paranoid Android. I just went back to stock yesterday from my backup and it's working great
I'm running Ubuntu 13.10 and if anything goes wrong, meaning if you get into a bootloop or recoveryloop, I always adb sideload a ROM and get it up and running again.
Click to expand...
Click to collapse
That sounds like it will cover everything but the recovery partition.
How is the stock recovery image backed up in this method, if you overwrite it with the custom recovery as the first step? Is it not backed up? Does the factory reset somehow restore it?
OK, I've done some more experimenting and poking around on IRC, and I have found this (for Sprint models, because that's what I have):
1. ioroot15 can temporarily root the device, without replacing anythig or even instaling su. Just ctrl+c it at the prompt.
2. Once that's done, "adb shell" gives you root, so you can dd the stock recovery (or anything else) from its partition to an .img, and dd TWRP over it like this:
Code:
cd /sdcard
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=stock-recovery.img
dd if=openrecovery-twrp-2.6.3.2-g2spr.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
3. If you don't even want to make your own backup the Sprint ZV8 stock partition images are all available for download. I can't tell you where they are, because I am apparently not allowed to post links. So if you ever need them you will have to cry and curse the forum admins. They can be flashed back with the temp-root method.
So, you can back up your recovery, flash a custom recovery, backup the rest of your system, and keep both those backups. To return to stock, restore your backup with your custom recovery, then do the temp-root and restore the stock recovery.
I have a Zenfone 3 that while trying to unroot I have soft bricked. I can get into TWRP recovery, but after installing the tizen ROM, I can not boot into it, but can still access the TWRP recovery. Is there a toolkit or any suggestion you might have as to how I could fix this issue.
Canukboy said:
I have a Zenfone 3 that while trying to unroot I have soft bricked. I can get into TWRP recovery, but after installing the tizen ROM, I can not boot into it, but can still access the TWRP recovery. Is there a toolkit or any suggestion you might have as to how I could fix this issue.
Click to expand...
Click to collapse
Do you have an official recovery? If yes, you can recover back your device again. Just use 'adb sideload <filename>' to do this.
I've also trying to unroot my device and end up in boot logo, but after flash the official ROM, it's finally work again. Also my data (/data) isn't formatted.
android_101_ said:
Do you have an official recovery? If yes, you can recover back your device again. Just use 'adb sideload <filename>' to do this.
I've also trying to unroot my device and end up in boot logo, but after flash the official ROM, it's finally work again. Also my data (/data) isn't formatted.
Click to expand...
Click to collapse
I only have the Twrp recovery.
Canukboy said:
I only have the Twrp recovery.
Click to expand...
Click to collapse
TWRP supports adb sideload but there's no point flashing stock recovery, TWRP is superior in every way.
Go into TWRP, plug in your USB cable and it'll mount your sdcard . Copy the firmware onto the sdcard and install it. Perform a wipe cache/dalvik and reboot.
How are you removing root?
wang1chung said:
TWRP supports adb sideload but there's no point flashing stock recovery, TWRP is superior in every way.
Go into TWRP, plug in your USB cable and it'll mount your sdcard . Copy the firmware onto the sdcard and install it. Perform a wipe cache/dalvik and reboot.
How are you removing root?
Click to expand...
Click to collapse
I used a app called KingRoot while I was on the bus, it caused the phone to freeze, after about 10 mins I hard reset the phone and it has not worked since.
I tried to sideload the stock rom, but it will not accept it. I think I may have something to do with the bootloader. I think my TWRP recovery could be in the Android partition, but I am unsure.
Canukboy said:
I used a app called KingRoot while I was on the bus, it caused the phone to freeze, after about 10 mins I hard reset the phone and it has not worked since.
I tried to sideload the stock rom, but it will not accept it. I think I may have something to do with the bootloader. I think my TWRP recovery could be in the Android partition, but I am unsure.
Click to expand...
Click to collapse
Forget sideloading it, edit the update script in the firmware, see this
thread, part 1, step 2-4.
Then copy the firmware to your sdcard (like I mentioned above) and install it. You can use the guide here, tip #4. You should read the entire guide afterwards.
if TWRP loads when you select recovery, it's on the correct partition. You'll have to reinstall TWRP after you flash the stock Rom again as it'll update recovery as well. Then create an nandroid backup, tip #2 and you're set.
Forget sideloading it, edit the update script in the firmware, see this
thread, part 1, step 2-4.
Then copy the firmware to your sdcard (like I mentioned above) and install it. You can use the guide here, tip #4. You should read the entire guide afterwards.
if TWRP loads when you select recovery, it's on the correct partition. You'll have to reinstall TWRP after you flash the stock Rom again as it'll update recovery as well. Then create an nandroid backup, tip #2 and you're set.
Click to expand...
Click to collapse
Hy Wang.. I followed your guide - modified updater-script, but I can't install the stock rom .zip from TWRP.
It says "can't extract updater-binary", I tried few times thinking that the file is corrupt, but the result still same.
FYI, I use stock ROM "UL-ASUS_Z012D-WW-14.2020.1709.68-user.zip", and TWRP 3.1.1.
Please help me if you have experienced it before. Thanks
@rzahunn
I've never had that error before and you're on the latest version of TWRP so I'm going to guess it has to do with your modification of the updater script.
You edited updater-script not updater-binary, correct? There are two files with similar names
There's a detailed guide by @kyle_l88 on how to return to stock.
Here's the link: https://forum.xda-developers.com/zenfone-3/development/how-to-to-stock-rom-recovery-zenfone-3-t3666223
Do note that the original recovery link is dead. The updated link is: https://mega.nz/#F!LIhwiCia!b_pyuHXS9E7f2VbyXcLyXA
TWRP Bootloop
Sorry if my reply is irrelevant, but I need some helps.
I am also using Zenfone 3, but stuck in TWRP bootloop.
I cannot flash using fastboot (not detected on PC), reflashing ROM doesn't help either.
I've tried all the possible methods I found on Google, such as dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota method but still has no luck.
Restoring backup would end me in TWRP too.
@Xytce
Are you factory resetting after you flash? Clearing cache and dalvik? It will take 5-10min to boot up initially after that.
Otherwise, try the guide Rizzed referenced.....as long as you have the correct firmware and TWRP flashes successfully, there's no reason it shouldn't work that I can think of.
wang1chung said:
@Xytce
Are you factory resetting after you flash? Clearing cache and dalvik? It will take 5-10min to boot up initially after that.
Otherwise, try the guide Rizzed referenced.....as long as you have the correct firmware and TWRP flashes successfully, there's no reason it shouldn't work that I can think of.
Click to expand...
Click to collapse
I've managed to fix the bootloop after following the guide. I missed that somehow, thanks for pointing that to me.
I've thanked you (pressed the Thanks button).
dm verity
Canukboy said:
I have a Zenfone 3 that while trying to unroot I have soft bricked. I can get into TWRP recovery, but after installing the tizen ROM, I can not boot into it, but can still access the TWRP recovery. Is there a toolkit or any suggestion you might have as to how I could fix this issue.
Click to expand...
Click to collapse
does it hangs on logo then start again? then reflashing the rom then flashing the dm verity zip again hope it works
Hey guys,
so I tried flashing Omni 8.0 rom and I was stuck at the boot screen. so I went back into twrp tried to reflash still nothing. I flashed a new version of twrp the one that can use multirom and it erased all my data. I flashed back the twrp I started with and now I can not sideload the full OTA zip to get back to stock. It says "cannot load one.zip" which is what I have it labeled as. I tried to download the recovery tool and I can't seem to figure out how to get the driver to work so it will see me on my comm port. Does anyone have any ideas on what to do or what happened? I'm stuck in twrp.
almost looks like it can't mount the system
IDK, maybe a broken download. I'd try to restore a backup if you have one, if not Wipe > Factory Reset. If it still doesn't boot after 20 minutes, refer to this thread: https://forums.oneplus.net/threads/i-have-to-go-back-to-oxygen-os.649947/#post-16907420. Basically, download the OOS ROM onto your computer and use an ADB/USB Sideload in TWRP recovery (you can flash Oxygen Recovery from TWRP if TWRP doesn't work) to install it. May take a while to boot.
I have no idea how it happened but I got my system mounted again that was my problem. I'm back.
thread can be closed
keeganjk said:
IDK, maybe a broken download. I'd try to restore a backup if you have one, if not Wipe > Factory Reset. If it still doesn't boot after 20 minutes, refer to this thread: https://forums.oneplus.net/threads/i-have-to-go-back-to-oxygen-os.649947/#post-16907420. Basically, download the OOS ROM onto your computer and use an ADB/USB Sideload in TWRP recovery (you can flash Oxygen Recovery from TWRP if TWRP doesn't work) to install it. May take a while to boot.
Click to expand...
Click to collapse
thanks for the reply mate
snipeez1987 said:
thanks for the reply mate
Click to expand...
Click to collapse
yw
snipeez1987 said:
Hey guys,
so I tried flashing Omni 8.0 rom and I was stuck at the boot screen. so I went back into twrp tried to reflash still nothing. I flashed a new version of twrp the one that can use multirom and it erased all my data. I flashed back the twrp I started with and now I can not sideload the full OTA zip to get back to stock. It says "cannot load one.zip" which is what I have it labeled as. I tried to download the recovery tool and I can't seem to figure out how to get the driver to work so it will see me on my comm port. Does anyone have any ideas on what to do or what happened? I'm stuck in twrp.
Click to expand...
Click to collapse
Easy fix for "Cannot load xxx.rom": you have to patch the adb.exe with a large address awareness program. Google it, I found one in another XDA thread.
Reason: the ROM filesize is too large. For small ROMs (like custom ROMs) adb would recognise it without any problems.
ipredatorv said:
Easy fix for "Cannot load xxx.rom": you have to patch the adb.exe with a large address awareness program. Google it, I found one in another XDA thread.
Reason: the ROM filesize is too large. For small ROMs (like custom ROMs) adb would recognise it without any problems.
Click to expand...
Click to collapse
Awesome. I'll keep that in mind. I'm sure I'll mess it up again lol. Hopefully not though.
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.
Hey hopefully someone could help me.
So i wanted to install android 10 on my Mi9t. After unlocking and installing TWRP i have wiped the Phone (everything accept usb OTG) after that i got stuck in Fastboot. Now ive get to managed it in to TWRP again but couldnt install any rom. Ive tried with Miflash it says Rollback check error. I Have anti:1. Im Lost..
Does anyone have an idea? I´ve installed Miflash on C:
BimSxx said:
Hey hopefully someone could help me.
So i wanted to install android 10 on my Mi9t. After unlocking and installing TWRP i have wiped the Phone (everything accept usb OTG) after that i got stuck in Fastboot. Now ive get to managed it in to TWRP again but couldnt install any rom. Ive tried with Miflash it says Rollback check error. I Have anti:1. Im Lost..
Does anyone have an idea? I´ve installed Miflash on C:
Click to expand...
Click to collapse
Never wipe everything
Go to fastboot and flash via there the ROM, maybe even the persist partition
Pupet_Master said:
Never wipe everything
Go to fastboot and flash via there the ROM, maybe even the persist partition
Click to expand...
Click to collapse
THX for your answer. I´ve tried to install via Fastboot. With MIFLASH but i got the anti rollback check error. I´ve read an tutorial where it stands Wipe everything execpt USB OTG. Now im Smarter...
After i installed boot.img recovery.img and system.img with the official Rom. it boots up to the original recovery.
So after you erased all but OTG, you did not install a rom? Cause you only mentioned "after that".
BimSxx said:
THX for your answer. I´ve tried to install via Fastboot. With MIFLASH but i got the anti rollback check error. I´ve read an tutorial where it stands Wipe everything execpt USB OTG. Now im Smarter...
After i installed boot.img recovery.img and system.img with the official Rom. it boots up to the original recovery.
Click to expand...
Click to collapse
Try via fastboot on ADB console, not miflash.
Start with the persist partition and then flash TWRP again and flash a ROM that you are positive that TWRP flash fine (some don't). Stock MIUI i'm speaking.
Wmateria said:
So after you erased all but OTG, you did not install a rom? Cause you only mentioned "after that".
Click to expand...
Click to collapse
After i wiped it i cant install on OS. There were no Folders...
Pupet_Master said:
Try via fastboot on ADB console, not miflash.
Start with the persist partition and then flash TWRP again and flash a ROM that you are positive that TWRP flash fine (some don't). Stock MIUI i'm speaking.
Click to expand...
Click to collapse
Yes did it with ADB fastboot. I can install the Rom complete fine but nothing works. I´ve tried with TWRP. Will do that again.
Im Sorry you mean first: flash persist.img? and then the twrp recovery and after that install the rom over twrp?
Soo I flashed an older version it works. But No Wifi i will try to Update it over LTE. Do i have to flash the persist.img ?
Everything is fine now! Thank you for you´re Help!
BimSxx said:
Soo I flashed an older version it works. But No Wifi i will try to Update it over LTE. Do i have to flash the persist.img ?
Everything is fine now! Thank you for you´re Help!
Click to expand...
Click to collapse
If the sensors are not working (gyroscope, camera, etc) you will need.
If you solve the Wifi issue then no need