My phone was rooted for the longest time without any problems, but some time ago (I'm assuming after the Treble update) apps would not detect root, although any app that was already using root could continue doing so.
I checked Magisk, which said root was not installed. I booted my phone into recovery, and somehow my phone had the stock recovery flashed on it. I tried flashing TWRP on it again, and it worked. Except, when I rebooted my phone into recovery later again, it went back to stock recovery.
I have no idea what's going on, and would really appreciate some help.
(PS: I do know how to update my phone without the phone reverting to stock recovery, I've done it many times before, so that can't be the problem)
update: I tried flashing TWRP again (through bootloader), and this time I jumped straight to recovery. It showed all the directories as if my phone had just been completely wiped. Internal memory 0M. No files anywhere. Didn't even have a downloads folder.
In a panic, I rebooted my phone, but my phone was actually untouched, no data wipe whatsoever. I'm even more confused about what the hell is happening now.
The stock OOS will automatically reflash the stock recovery if it detects it has changed to something else.
You have to boot into TWRP right after installing it and either let it mount /system read-write (likely to cause problems later) or install something like Magisk that will prevent overwriting the recovery.
TWRP was not able to read your data partition, which can happen depending on which kind of encryption you have. Try the BlueSpark TWRP, it supposedly supports encryption better than the official one.
It's the version. If I use 3.2.3.0 or 3.2.2.0 I get no files. But 3.2.1.1 works for some reason. You can also install pie now. There is a link in the one plus 5 forums here to hydrogen os. It's Chinese version but that doesn't matter. It is in English. You will need to uninstall a few Chinese bloatware apps and flash gapps. But besides that I don't see much difference. If anything the hydrogen os looks nicer. I'll add some screenshots . Developer options was enabled from first boot, with the advanced reboot menu I noticed.
Also, if you have root the TWRP app can flash recovery from in the OS.
Fif_ said:
The stock OOS will automatically reflash the stock recovery if it detects it has changed to something else.
You have to boot into TWRP right after installing it and either let it mount /system read-write (likely to cause problems later) or install something like Magisk that will prevent overwriting the recovery.
TWRP was not able to read your data partition, which can happen depending on which kind of encryption you have. Try the BlueSpark TWRP, it supposedly supports encryption better than the official one.
Click to expand...
Click to collapse
It's frustrating for sure. Lol
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.
Hi All
So I decided to try a custom ROM on my 6T the other day, but am having no end of trouble trying to get it to work.
To start, I was running 10.3.1 on my phone, and was Unlocked, but not Rooted, since i lost TWRP+Magisk after installing the last OS update.
So I go into fastboot, boot up the latest TWRP-Q image, and try to install magisk, but all my sdcard folders are just garbage text - can't do anything with them. I assume this is some sort of encryption thing, so i reboot to go back to the OS and see if a can disable it.
However - the phone won't boot now - just loops back into Recovery everytime. Tried everything i can think of, nothing seems to work, so I cut my losses and reboot to fastboot and flash the fastboot 10.3.1
let that start up and everything seems fine, so i reboot to fastboot, boot up TWRP again, and then "install recovery ramdisk" like the instructions say t, and then reboot to recovery. all good so far.
Next, i copy on the 10.3.1 flashable ZIP, and the PixeN OS zip. instructions there say to flash 10.3.1 followed by TWRP twice, so i do that, rebooting to recovery between each, and then install the PixeN OS zip and TWRP as well.
Reboot after that, and phone just loops back into TWRP, and all my sdcard folders are garbage again!
I've no idea what I'm doing wrong, but i've tried the same process with 3 different custom roms so far and get the same result every time.
Flash the OOS fastboot image, boot and install TWRP, install OOS flashable and TWRP twice, then the ROM zip and TWRP, and then everytime after that, my phone just loops into recovery every time - and shows the same garbled folder names.
I'm at a loss as to what's going wrong - can anyone help?
The only thing I can come up with is what they all keep saying in the topics; have you disabled the lockscreen? I haven't yet tried to flash a custom rom but that's what I am missing in your story.
You have backed up your phone?
Then reinstall OxygenOS 10.3.1 in all slots, and reinstall TWRP, and finally do factory reset and data wipe, and reboot back into TWRP. And, copy the files you want installed back on the phone (TWRP will mount the phone as a MTP storage drive on the computer, of course) and then install your favorite OS and TWRP in both slots then reboot back into recovery one final time. Finally install Magisk and gapps (if you want to), and reboot (then install any Magisk add-ons once you get back into your phone).
That's because OxygenOS' SSD encryption is a bit strict for our liking.
Sent from my ONEPLUS A6013 using Tapatalk
Dr. Mario said:
You have backed up your phone?
Then reinstall OxygenOS 10.3.1 in all slots, and reinstall TWRP, and finally do factory reset and data wipe, and reboot back into TWRP. And, copy the files you want installed back on the phone (TWRP will mount the phone as a MTP storage drive on the computer, of course) and then install your favorite OS and TWRP in both slots then reboot back into recovery one final time. Finally install Magisk and gapps (if you want to), and reboot (then install any Magisk add-ons once you get back into your phone).
That's because OxygenOS' SSD encryption is a bit strict for our liking.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
OK thanks - that's pretty much what I did, but I'll try again following your exact steps - thanks for the help!
Be sure whatever you installed is in both slots or the SSD will keep corrupting. I had to do that on both slots so I don't keep bricking it - I have bricked the converted T-Mobile OnePlus 6T about eight to ten times figuring out why I wasn't able to install anything atop OxygenOS 10.3.1 ROM.
Sent from my ONEPLUS A6013 using Tapatalk
Got it working?
Sent from my ONEPLUS A6013 using Tapatalk
It worked! yesssss
Thanks so much - Pixen is booting up on my phone right now
Good. I am glad you got it running.
Sent from my ONEPLUS A6013 using Tapatalk
Hi,
I'm sure someone else will have had my problem but I can't seem to find a straight forward solution.
I am wanting to upgrade my Samsung S7 Edge, SM-G935F Exynos, to the latest Lineage OS with Android 10 as Samsung are no longer supporting my phone. The phone is unlocked as supplied from Samsung.
I downloaded Odin v3.14 and successfully flashed TWRP 3.4.0.0 hero.2lte.img.tar. I activated Developer Options and OEM unlock before flashing.
I can enter TWRP but am unsure what I do regarding the Unmodified System Partition options on the 1st TWRP screen so I hit 'Keep Read Only' and then 'Reboot' only to find that the phone attempts to restart, I see the Samsung Galaxy S7 Edge splash screen which then goes off and restarts again repeatedly, so I can't check if all my data etc. is ok on the phone. I did back up Whatsapp and made s Smart Switch backup too but forgot to do Samsung & Google account backups before the flashing.
I'm assuming I've missed something out in the flashing procedure but am not sure of exactly what. I have previously flashed and upgraded Galaxy S3, S3 Mini & a Tab2 10.1 using earlier TWRP versions so it's not that I'm a total beginner. I also tried to do a rom backup via TWRP but that failed and also a wipe Dalvik cache but that also failed.
Please advise:
1. what I've done wrong if anything?
2. Best way to restore the phone without losing existing data if possible perhaps with stock rom flashing? I could try the Smart Switch Emergency Software recovery & Initialisation but I understand that resets the phone to Factory settings loosing all data.
3. Procedure to flash Lineage rom that's 'idiot proofed'?
Thanks in advance.
rebgershon said:
Hi,
I'm sure someone else will have had my problem but I can't seem to find a straight forward solution.
I am wanting to upgrade my Samsung S7 Edge, SM-G935F Exynos, to the latest Lineage OS with Android 10 as Samsung are no longer supporting my phone. The phone is unlocked as supplied from Samsung.
I downloaded Odin v3.14 and successfully flashed TWRP 3.4.0.0 hero.2lte.img.tar. I activated Developer Options and OEM unlock before flashing.
I can enter TWRP but am unsure what I do regarding the Unmodified System Partition options on the 1st TWRP screen so I hit 'Keep Read Only' and then 'Reboot' only to find that the phone attempts to restart, I see the Samsung Galaxy S7 Edge splash screen which then goes off and restarts again repeatedly, so I can't check if all my data etc. is ok on the phone. I did back up Whatsapp and made s Smart Switch backup too but forgot to do Samsung & Google account backups before the flashing.
I'm assuming I've missed something out in the flashing procedure but am not sure of exactly what. I have previously flashed and upgraded Galaxy S3, S3 Mini & a Tab2 10.1 using earlier TWRP versions so it's not that I'm a total beginner. I also tried to do a rom backup via TWRP but that failed and also a wipe Dalvik cache but that also failed.
Please advise:
1. what I've done wrong if anything?
2. Best way to restore the phone without losing existing data if possible perhaps with stock rom flashing? I could try the Smart Switch Emergency Software recovery & Initialisation but I understand that resets the phone to Factory settings loosing all data.
3. Procedure to flash Lineage rom that's 'idiot proofed'?
Thanks in advance.
Click to expand...
Click to collapse
1] You didn't formatted /data and/or flashed magisk or supersu after booting into twrp first time.
Note that you need to format /data under wipe in twrp and type yes and then again reboot in twrp. This is necessary step to disable encryption. And after that flash magisk without any reboot or flash your required rom by following your respective rom thread.
Please note that keeping system read only will cause you to flash in systemless root mode like magisk or super su in systemless mode. There is no difference between normal root mode and systemless root mode except that you will need to allow system modifications in twrp in normal root which will in turn trigger dm verity check and you will need to flash no verity zip to make phone bootable when system modification method (normal root) is selected. Plus system modification will cause certain apps to detect root easily plus increasing complications like I said above. So just keep read only and flash magisk and you will get root in systemless mode without any cons !
Here, you said you're getting a verification screen after rebooting twrp..
This can be caused either by.
1. Not formatting /data after booting twrp for first time
2. Not flashing magisk after formatting /data
3. Enabling system modifications and not flashing no verity zips/magisk
4. Oem unlock is not enabled..
2] You cannot restore data if you didn't back it up before messing with it, or you made a titanium backup/twrp backup.
Smart switch cannot flash phone anymore ..
Yes, flashing stock firmware using home_csc in odin, will not delete data and may restore your phone, but no guarantee that it will work, you can try though. Thats why its strictly advised to do backup before messing your phone in anyway..
3. Pls refer or ask in your respective rom thread.
Sent from my hero2lte using XDA Labs
shah22 said:
1] You didn't formatted /data and/or flashed magisk or supersu after booting into twrp first time.
Note that you need to format /data under wipe in twrp and type yes and then again reboot in twrp. This is necessary step to disable encryption. And after that flash magisk without any reboot or flash your required rom by following your respective rom thread.
Please note that keeping system read only will cause you to flash in systemless root mode like magisk or super su in systemless mode. There is no difference between normal root mode and systemless root mode except that you will need to allow system modifications in twrp in normal root which will in turn trigger dm verity check and you will need to flash no verity zip to make phone bootable when system modification method (normal root) is selected. Plus system modification will cause certain apps to detect root easily plus increasing complications like I said above. So just keep read only and flash magisk and you will get root in systemless mode without any cons !
Here, you said you're getting a verification screen after rebooting twrp..
This can be caused either by.
1. Not formatting /data after booting twrp for first time
2. Not flashing magisk after formatting /data
3. Enabling system modifications and not flashing no verity zips/magisk
4. Oem unlock is not enabled..
2] You cannot restore data if you didn't back it up before messing with it, or you made a titanium backup/twrp backup.
Smart switch cannot flash phone anymore ..
Yes, flashing stock firmware using home_csc in odin, will not delete data and may restore your phone, but no guarantee that it will work, you can try though. Thats why its strictly advised to do backup before messing your phone in anyway..
3. Pls refer or ask in your respective rom thread.
Thanks for your reply Shah though I'm still a bit confused by it.
UnIock OEM was enabled as was USB debugging.
Fortunately, I was able to reflash the stock rom and phone is working again but what sort of backup are you indicating in part 2. above), NAND, Smartswitch or just back up to google, Samsung & Whatsapp accounts?
In 1). of your reply you say 'You didn't formatted /data and/or flashed magisk or supersu after booting into twrp first time.
Note that you need to format /data under wipe in twrp and type yes and then again reboot in twrp. This is necessary step to disable encryption. And after that flash magisk without any reboot or flash your required rom by following your respective rom thread.'
I thought that if I do format /data my data would be lost and I want to make a NAND backup of the existing rom and data before flashing/modifying but if that doesn't loose the data, I assume then the steps are as follows:
1. Flash TWRP with Odin
2. Boot into Recovery-TWRP
3. Tap on the Read Only button on the 1st TWRP screen
4. Format /data under wipe in TWRP and tap yes and then reboot in TWRP. - Do you mean reboot the phone into TWRP of just go back into the TWRP main menu & when do I make the NAND backup?
5. Flash magisk or supersu from SD card no reboot
6. Flash Lineage OS rom from SD card.
7. Reboot.
Please correct any errors above as I've now tried 3 times since my original post without success but always managed to reflash the stock rom to get me going again.
Click to expand...
Click to collapse
rebgershon said:
Thanks for your reply Shah though I'm still a bit confused by it.
Click to expand...
Click to collapse
Thats why you read forums again and again and unless you are sure and know what you're doing, don't proceed with these things and read again.
rebgershon said:
UnIock OEM was enabled as was USB debugging.
Fortunately, I was able to reflash the stock rom and phone is working again but what sort of backup are you indicating in part 2. above), NAND, Smartswitch or just back up to google, Samsung & Whatsapp accounts?
Click to expand...
Click to collapse
Upto you which backup you prefer, saving data on separate storage is the main goal as rooting and flashing custom rom would erase all your data from phone.
rebgershon said:
I thought that if I do format /data my data would be lost and I want to make a NAND backup of the existing rom and data before flashing/modifying but if that doesn't loose the data, I assume then the steps are as follows
Click to expand...
Click to collapse
What you mean exactly ? What doesn't loose the data ? Flashing custom rom first time/rooting always erases your data and yes you need to backup before flashing/modifying.
rebgershon said:
1. Flash TWRP with Odin
2. Boot into Recovery-TWRP
3. Tap on the Read Only button on the 1st TWRP screen
4. Format /data under wipe in TWRP and tap yes and then reboot in TWRP. - Do you mean reboot the phone into TWRP of just go back into the TWRP main menu & when do I make the NAND backup?
5. Flash magisk or supersu from SD card no reboot
6. Flash Lineage OS rom from SD card.
7. Reboot.
Click to expand...
Click to collapse
In step 4. Reboot again in twrp after formatting /data.
When do you make nand backup?? Lol, at this point your phone would have nothing to backup, you should have made a backup the first time you tried modifying your phone. Because flashing stock rom like you said you did many times, already formats the phone.
If you mean you want to backup your phone again, then you can't backup in twrp in this stage. Backup before flashing twrp through any means.
Step 5 is correct, I don't know about step 6. I never flashed lineage and have no experience about it. Pls refer lineage's respective rom thread for exact steps. Good luck
Sent from my hero2lte using XDA Labs
shah22 said:
Thats why you read forums again and again and unless you are sure and know what you're doing, don't proceed with these things and read again.
Upto you which backup you prefer, saving data on separate storage is the main goal as rooting and flashing custom rom would erase all your data from phone.
What you mean exactly ? What doesn't loose the data ? Flashing custom rom first time/rooting always erases your data and yes you need to backup before flashing/modifying.
In step 4. Reboot again in twrp after formatting /data.
When do you make nand backup?? Lol, at this point your phone would have nothing to backup, you should have made a backup the first time you tried modifying your phone. Because flashing stock rom like you said you did many times, already formats the phone.
If you mean you want to backup your phone again, then you can't backup in twrp in this stage. Backup before flashing twrp through any means.
Step 5 is correct, I don't know about step 6. I never flashed lineage and have no experience about it. Pls refer lineage's respective rom thread for exact steps. Good luck
Sent from my hero2lte using XDA Labs
Click to expand...
Click to collapse
Thanks again Shah for your reply/help.
I followed the instructions and got the lineage rom installed and Gapps but I don't think Gapps installed properly as I wasn't able to restore any of the saved data from my google account and it wouldn't allow me to add any other accounts except email so for now I've restored the stock rom and my data.
Is there another Android 10 rom you can recommend besides lineage that will have a similar appearance to Samsung?
rebgershon said:
Thanks again Shah for your reply/help.
I followed the instructions and got the lineage rom installed and Gapps but I don't think Gapps installed properly as I wasn't able to restore any of the saved data from my google account and it wouldn't allow me to add any other accounts except email so for now I've restored the stock rom and my data.
Is there another Android 10 rom you can recommend besides lineage that will have a similar appearance to Samsung?
Click to expand...
Click to collapse
I don't recommend any rom except a stock rooted debloated one.. (like Alexndr's devbase)
Reason : because full custom roms have a high chance to mess up your phone's efs and permanent soft brick issues.
But, I'm in love with infinity wallpapers, dark mode and android 10 in general like all others these days.. so if you really want samsung android 10 for S7 edge, then Floyd V4 is your best bet.. see on rom and software developer section of s7 edge to find floyd v4. Its a s9 android 10 one ui 2 port...
Personally, I'm using latest alexndr's devbase rom. Because I'm still paranoid about fully custom or ported roms
Alexndr's devbase is a full stock oreo - debloated rom. Which has option to root during flashing in twrp too. Its perfect for my needs.
But maybe soon, I will change to Floyd v4 to experience the future.. who knows
Sent from my Legendary Hero2LTE using Tapatalk
shah22 said:
I don't recommend any rom except a stock rooted debloated one.. (like Alexndr's devbase)
Reason : because full custom roms have a high chance to mess up your phone's efs and permanent soft brick issues.
But, I'm in love with infinity wallpapers, dark mode and android 10 in general like all others these days.. so if you really want samsung android 10 for S7 edge, then Floyd V4 is your best bet.. see on rom and software developer section of s7 edge to find floyd v4. Its a s9 android 10 one ui 2 port...
Personally, I'm using latest alexndr's devbase rom. Because I'm still paranoid about fully custom or ported roms
Alexndr's devbase is a full stock oreo - debloated rom. Which has option to root during flashing in twrp too. Its perfect for my needs.
But maybe soon, I will change to Floyd v4 to experience the future.. who knows
Shah,
Many thanks for the recommendation of the FloydQ rom.
I installed it yesterday after making all backups inc. Smartswitch.
Very easy to install both from flashing and Aroma installation viewpoints. Ran 1st time without a glitch and phone now thinks its an S9+ running Android 10 a la Samsung. I even managed to transfer my Smartswitch backup to my wife's old S7 Edge and then used Smartswitch to transfer from that phone to the 'S9+'.
Only glitch was logging into my Samsung account but sorted that as well so all in all very happy so far.:good:
Click to expand...
Click to collapse