Related
Hello everyone this is my fist guide so be kind with the formatting, i will get better as I post more. I am writing this guide, because like you, the reader, I had installed lineageOS 14.1 and set up the phone and realized there was encryption on it, and with that tried to wipe it in twrp just to find out that it only wiped the encryption key, but not the encryption itself. Don't panic, it isn't all your fault, XD. Stay calm, the last thing you need is to be freaking out, flashing random zips in hopes of fixing it. I will give credit to all of the developers whose tools i am linking at the bottom.
Now that the introductions are out of the way, time for the complimentary dose of warning.
WARNING: Doing this won't guarantee that this will fix it, as every situation can vary. I am not responsible for any bricked devices, thermal reactors coming from your phone after this, or modding before it was cool.
Assuming you can still get into fastboot first you need to gather these files if you don't have them yet.
- Minimal adb and fastboot on windows after installing just drag to desktop to add files to it
- Qualcomm fastboot drivers for axon7tool.exe and for fastboot and adb
- TWRP 3.0.4-1 official for Axon 7
- B29 rollback modded zip on the second tab
- Nougat modem and bootstack
- Tenfar's axon7root.exe (just in case you can't use fastboot. that's what i used because i don't know how to use axon7tool.exe)
- Fastboot image to get fastboot working again flash it in twrp after getting twrp installed again through axon7root.exe
- Some time because this will likely take an hour of your time, assuming you have the drivers and files already downloaded, longer if not and slow internet.
- LineageOS 14.1
- GAPPS 7.1.1 ARM 64
- almost forgot, you also need a microsd card to store the files because we will be wiping your entire internal with this, so back up your lovely dank memes or forever hold the loss.
Step 0.5. if you don't have fastboot working flash the bootloader unlock file by drakenfx to get it working again. if you don't have twrp for whatever reason go to the guide for axon7root.exe linked above and reboot to edl mode by holding all buttons down and have your phone connected to computer to know you are there. there won't be a vibration to let you know, just your computer telling you it has a connected device. now flash twrp, by first renaming the recovery to recovery.img and putting it in the adb folder along with the the root exe and do 'axon7root.exe -p (insert your com number listed in device manager) -r' (without the ' obviously) and it should send the recovery. if it doesn't see your device. make sure you have the drivers installed and make sure you have put down your com number where i left the () at
Step 1. assuming your device boots to this beautiful screen. you need to go back to twrp and drag the B29 zip from your computer to your external sd card from mtp and go to mount and mount system read-only this is very important.
Step 2. flash the B29 modded and let it go through. this will take a few minutes. if the progress bar automatically jumps to the end, you didn't go read only.
Step 3. after it finishes reboot into system and let it set up your system, you can skip through because we will be resetting again anyhow.
Step 4. reboot back to recovery. you can do this by using that pesky bl unlocked message by pressing up on volume as soon as it shows and selecting recovery. there you can see you have stock recovery, don't panic this is what we need. select wipe data factory reset and let it do it
Step 5. go back and skip set up again and reboot to bootloader where you can now 'fastboot flash recovery recovery.img' to get back twrp.
Step 6. flash the nougat bootstack and modem i had you download. after flashing that, go to wipe: Advanced wipe. Select Dalvik, system, data, cache and swipe to wipe. this will format it as ext4 which is what is required to get to lineageOS
Step 7. flash lineageos 14.1 and your gapps category and wait to let it finish. Note, you don't have to flash the modem more than once after flashing lineageos, even for updating. just after leaving B29
Step 8. reboot to make sure your encryption problem is not there
Step 9. set up phone and profit.
If you have done everything right, you shouldn't have bricked and should be back to lineageos 14.1 with no further problems. If you skipped around and got yourself bricked, congratulations because i am not the best at fixing problems, and i can try to help, but you will be at the mercy of the Best devs this community has to offer.
Now to the part where I thank all the Devs who, without their tireless time and effort, would not have made this guide possible and development into this phone in the first place. @Unjustified Dev for the lineageOS build i use as my daily driver for now; you rock dude. ^^
@DrakenFX oh god where do i begin. for the bl unlock zip, B29 modded ota, inspiration to the rest of the community, etc.
@tenfar for the axon7root.exe tool used
@sixohtew for his constant help and advice with not only this guide, but with teaching me to build android. if you are interest in learning how to compile android for any device, he can probably help. he has a very fair deal and is amazing at what he does.
Thank you all for your copious hours of time spent in the building of each great tool and to the community as a whole. Everyone, these guys are amazing, even if i have only talked to one of them. Be sure to stop by and donate.
If i have left anyone's name out, please hit me up and i will add you to the credits, and to that i apologize.
Happy flashing!
I read through your guide several times. I'm missing the point here. At which step does the decryption get removed?
gpz1100 said:
I read through your guide several times. I'm missing the point here. At which step does the decryption get removed?
Click to expand...
Click to collapse
Sorry for delayed response, it gets removed when you do the factory reset in stock recovery. For some reason TWRP can't remove it from /data in nougat but stock recovery can in B29.
Wipe->Format Data in TWRP removes all encryption from /data and /sdcard. Did you try that before reinstalling the stock recovery? I've had weird experiences in the past with stuck encryption.
QuantumFluxx said:
Wipe->Format Data in TWRP removes all encryption from /data and /sdcard. Did you try that before reinstalling the stock recovery? I've had weird experiences in the past with stuck encryption.
Click to expand...
Click to collapse
I did try it. It doesn't wipe it because there is a bug with TWRP for our phone. I would wipe and even format data and it wouldn't work. If you go to the official TWRP thread it even warns you that if you have encryption to not wipe. We had a dev who wiped and it got rid of the encryption key and not the encryption, like what happened to me. I tried to wipe so many times and had to revert. Long process but I got my phone to work again
Rip me
So I was bricked to the point where I was able to access TWRP and if I flashed any ROM, even after formatting data, I would reach a Decryption unsuccessful screen on my A2017U. I followed the guide from step 0.5, since fastboot was not working. After flashing the bootloader unlock file via TWRP, I was not able to access anything, further bricking the device. It boots within a second to a black screen, and reboots to it if I hold the power button or any combination for recovery.etc. I can not go to EDL mode; Axon7tool detects it though when it is in this state, and is able to send files successfully. However, it still stays in this black screen. Is there any way to get back to a functioning phone at this point?
Edit: It is apparently always in EDL? It shows up and is identified by my PC as QUSB_BULK...
navsterama said:
So I was bricked to the point where I was able to access TWRP and if I flashed any ROM, even after formatting data, I would reach a Decryption unsuccessful screen on my A2017U. I followed the guide from step 0.5, since fastboot was not working. After flashing the bootloader unlock file via TWRP, I was not able to access anything, further bricking the device. It boots within a second to a black screen, and reboots to it if I hold the power button or any combination for recovery.etc. I can not go to EDL mode; Axon7tool detects it though when it is in this state, and is able to send files successfully. However, it still stays in this black screen. Is there any way to get back to a functioning phone at this point?
Edit: It is apparently always in EDL? It shows up and is identified by my PC as QUSB_BULK...
Click to expand...
Click to collapse
Can you still get into recovery with power & vol+? and what happened as soon as you flashed the zip?
twilighttony said:
Can you still get into recovery with power & vol+? and what happened as soon as you flashed the zip?
Click to expand...
Click to collapse
Nope :crying:. The EDL combo and the recovery combo result in the same screen and duration of boot. After flashing the bootloader unlock file, I remember reading the script to see that it was successful and yielded a result of 1 before resulting in this screen.
navsterama said:
Nope :crying:. The EDL combo and the recovery combo result in the same screen and duration of boot. After flashing the bootloader unlock file, I remember reading the script to see that it was successful and yielded a result of 1 before resulting in this screen.
Click to expand...
Click to collapse
I am not sure what happened to that, were you originally on B15? i was simply on the modem/bootstack which allowed me to succeed in flashing that file. that could be a variable. i will be sure to look into a tool ive heard of called miflash which works through edl mode to unbrick.
navsterama said:
Nope :crying:. The EDL combo and the recovery combo result in the same screen and duration of boot. After flashing the bootloader unlock file, I remember reading the script to see that it was successful and yielded a result of 1 before resulting in this screen.
Click to expand...
Click to collapse
try this.
twilighttony said:
I am not sure what happened to that, were you originally on B15? i was simply on the modem/bootstack which allowed me to succeed in flashing that file. that could be a variable. i will be sure to look into a tool ive heard of called miflash which works through edl mode to unbrick.
Click to expand...
Click to collapse
Yea, I was on B15. Trying miFlash right now though. I'll update you when its done...:good:
navsterama said:
Yea, I was on B15. Trying miFlash right now though. I'll update you when its done...:good:
Click to expand...
Click to collapse
ok that does make sense as to why it failed. i was on the modded modem file that allowed me to install los
twilighttony said:
ok that does make sense as to why it failed. i was on the modded modem file that allowed me to install los
Click to expand...
Click to collapse
Wait...in terms of the bootstack I was also on the modded one for LOS 14.1. However, it was when the last unofficial build came out (Feb 3rd???). I tried to clean flash LOS Weekly today and thats when I ran into the dilemma of the decryption. Idk why I said yes for being on B15, for some reason that translated to generally Nougat bootstack in my head. My bad, OP.
---------- Post added at 10:47 PM ---------- Previous post was at 10:30 PM ----------
navsterama said:
Yea, I was on B15. Trying miFlash right now though. I'll update you when its done...:good:
Click to expand...
Click to collapse
Unbricked, booted up, now its on the "beautiful" screen. Thanks!
twilighttony said:
try this.
Click to expand...
Click to collapse
This is posted in the dev section. No need for external linkage.
navsterama said:
Wait...in terms of the bootstack I was also on the modded one for LOS 14.1. However, it was when the last unofficial build came out (Feb 3rd???). I tried to clean flash LOS Weekly today and thats when I ran into the dilemma of the decryption. Idk why I said yes for being on B15, for some reason that translated to generally Nougat bootstack in my head. My bad, OP.
---------- Post added at 10:47 PM ---------- Previous post was at 10:30 PM ----------
Unbricked, booted up, now its on the "beautiful" screen. Thanks!
Click to expand...
Click to collapse
glad that worked. perhaps i will edit the guide to where fastboot is added at the end as an extra. seems that if we at least have twrp we can go from there. do you still have an unlocked bl?
lafester said:
This is posted in the dev section. No need for external linkage.
Click to expand...
Click to collapse
will remember for future reference. thanks
lafester said:
This is posted in the dev section. No need for external linkage.
Click to expand...
Click to collapse
At least the poster of the blog gives credit to the original author and thread.
The method referenced at the blog is confusing though. If one is in a bricked state (edl only), they can't access developer options or even boot into android.
gpz1100 said:
At least the poster of the blog gives credit to the original author and thread.
The method referenced at the blog is confusing though. If one is in a bricked state (edl only), they can't access developer options or even boot into android.
Click to expand...
Click to collapse
If you are in edl only with an unlocked bootloader than the part of enabling bl unlock won't apply.
twilighttony said:
If you are in edl only with an unlocked bootloader than the part of enabling bl unlock won't apply.
Click to expand...
Click to collapse
Right, I understand that, but the person reading your blog won't, and thus the confusion.
This guide really needs to be stickied or higher up. Restarted my phone yesterday and it randomly got encrypted upon booting. Was locked out of everything and no keyboard was popping up to be able to put in a PIN or Password. This guide saved me. Thank you.
Does anyone have one or the other? Either a full twrp backup of stock/untouched system/boot/(maybe)data, or all of the img's extracted from a kdz? I need to restore stock, but I can't as I don't have access to a pc to use the lg up software, and I don't have any backups. Did the bootloader unlock and flashed twrp, but after flashing the no-verity and supersu zips, I can only boot up to an "encryption unsuccessful" screen, with a "reset phone" button that just takes me back to twrp.
hi i just made an stock zip it works for me im also on metro
Zhono said:
Does anyone have one or the other? Either a full twrp backup of stock/untouched system/boot/(maybe)data, or all of the img's extracted from a kdz? I need to restore stock, but I can't as I don't have access to a pc to use the lg up software, and I don't have any backups. Did the bootloader unlock and flashed twrp, but after flashing the no-verity and supersu zips, I can only boot up to an "encryption unsuccessful" screen, with a "reset phone" button that just takes me back to twrp.
Click to expand...
Click to collapse
i just made an stock zip it works for me im also on metro.
I extracted for the kdz and then modded the update script to lineage.
I take no credit for any of it just hopes it helps someone.
I was on lineage and used this to revert to stock so I'm guessing it works.
but like anything on this site try at own risk.
message me and ill try to see how I can upload it
androidpimpz said:
i just made an stock zip it works for me im also on metro.
I extracted for the kdz and then modded the update script to lineage.
I take no credit for any of it just hopes it helps someone.
I was on lineage and used this to revert to stock so I'm guessing it works.
but like anything on this site try at own risk.
message me and ill try to see how I can upload it
Click to expand...
Click to collapse
I forgot I even made this thread. I actually ended up buying a cheapo Windows 10 tablet on Amazon and used that to flash the KDZ. So My phone is good now. Still, I'm sure I'm not the only one running into the issue of needing to get to stock without the use of a Windows machine, so feel free to upload/link whatever you have for anyone else that might stumble upon this tread.
Stock Zip
Stock Zip
Contains factory boot.img
factory system.img
i didn't include the stock recovery however when i did this some how i ended back with stock recovery.
All Files came from the extracted kdz files.
MetroPCS
Wipe Data /Davik .... the usual.
YOU WILL LOSE ROOT!!
As With Everything on this site you do so at own risk!
https://www.dropbox.com/s/0hcdxodgmxqokga/lgstyloplus3stock.zip?dl=0
awesome I'm going to give this a shot because as soon as Lineage updates for fast charging and nfc and the minor glitches here and there I want to be on the stock rom rooted with Magisk and ill remove the bloatware myself on the stock. But Lgup nor Lg Bridge detect my phone, lgup does say something in the com part but when selected says please select a compatible device or something of that nature so Ill try this flash this with TWRP and hope it does the job p.s. I also used uppercut program too it as well didn't work for my phone
Please let me know if it works for you also it will look like it gets stuck u just got to be patient until it says done. Used it quite a few times instead of the whole computer route.
---------- Post added at 08:22 PM ---------- Previous post was at 08:21 PM ----------
Also u will have to use DM_verify to unencrypy data b4 u flash su or magisk again.
Esin8785 said:
awesome I'm going to give this a shot because as soon as Lineage updates for fast charging and nfc and the minor glitches here and there I want to be on the stock rom rooted with Magisk and ill remove the bloatware myself on the stock. But Lgup nor Lg Bridge detect my phone, lgup does say something in the com part but when selected says please select a compatible device or something of that nature so Ill try this flash this with TWRP and hope it does the job p.s. I also used uppercut program too it as well didn't work for my phone
Click to expand...
Click to collapse
note: This was done on a MetroPCS phone, LG G stylo 3 plus MP450, if you try a different model number do at your own risk
I have completed the process and it indeed worked like a charm, I am now back on stock rom, just let the twrp do it's thing and it will be done. It looks like it hangs up but just let it do it's thing, I went and smoked a cigg came back and twrp said it was done, WIPE THE DEV when booting for first time it's going to take some time again let it do it's thing it will turn on, thank you so much for this, this should be a recommend post for the top, I wonder if you can make backups for other model's tmobile boost what ever...
You will loose root, you will loose TWRP, they are simple go to this post to do re root or to just put on TWRP, https://forum.xda-developers.com/android/development/recovery-twrp-v3-lg-stylo-3-plus-t3649621
Just FYI, you do NOT need to do anything to your encrypted data partition before flashing Magisk. I restored my phone back to stock(using LGUP) and when I flashed twrp, I did NOT swipe to make changes to system, and I didn't touch the data partition at all. I simply flashed the Magisk zip and rebooted. Works great. I want to make a TWRP backup before trying stuff like xposed, but I'm still a bit nervous about trying to make the backup with the encrypted data or the read-only system, especially if I need to actually restore it. Decrypting/wiping the data partition is what completely borked my phone the first time around and I don't have access to Windows anymore to use LGUP again. Maybe I should just leave well-enough alone at this point. It's been a million years since I've used xposed and I don't even know if there's anything in there I'd want.
Zhono said:
Just FYI, you do NOT need to do anything to your encrypted data partition before flashing Magisk. I restored my phone back to stock(using LGUP) and when I flashed twrp, I did NOT swipe to make changes to system, and I didn't touch the data partition at all. I simply flashed the Magisk zip and rebooted. Works great. I want to make a TWRP backup before trying stuff like xposed, but I'm still a bit nervous about trying to make the backup with the encrypted data or the read-only system, especially if I need to actually restore it. Decrypting/wiping the data partition is what completely borked my phone the first time around and I don't have access to Windows anymore to use LGUP again. Maybe I should just leave well-enough alone at this point. It's been a million years since I've used xposed and I don't even know if there's anything in there I'd want.
Click to expand...
Click to collapse
You can always flash back to stock using TWRP with the link provided above if someone something goes wacked, I can't use LGUP it does not detect my phone so this was a easier solution for me instead of using a pc you can do it from your phone so long as it's MP450 version
Esin8785 said:
You can always flash back to stock using TWRP with the link provided above if someone something goes wacked, I can't use LGUP it does not detect my phone so this was a easier solution for me instead of using a pc you can do it from your phone so long as it's MP450 version
Click to expand...
Click to collapse
Did you use UPPERCUT with LGUP? I started right out that way and it had no trouble detecting and flashing my phone. I installed the lg drivers, installed LGUP, plugged in the phone and ran uppercut.exe. From taking the computer out of the box, to flashing the phone, was like 10 minutes. Packed up the computer and returned it at the UPS store an hour later. And I'm using the same phone as you, so I don't see why it shouldn't work. Although if the TWRP backup works, that's far more convenient anyway, so it's kind of a moot point. Still, it would be good to have access to LGUP in the future, just in case you somehow get to a point where the twrp backup can't save you.
Zhono said:
Did you use UPPERCUT with LGUP? I started right out that way and it had no trouble detecting and flashing my phone. I installed the lg drivers, installed LGUP, plugged in the phone and ran uppercut.exe. From taking the computer out of the box, to flashing the phone, was like 10 minutes. Packed up the computer and returned it at the UPS store an hour later. And I'm using the same phone as you, so I don't see why it shouldn't work. Although if the TWRP backup works, that's far more convenient anyway, so it's kind of a moot point. Still, it would be good to have access to LGUP in the future, just in case you somehow get to a point where the twrp backup can't save you.
Click to expand...
Click to collapse
I did use UPPERCUT with no luck, I even re updated my drivers and ran it with no luck even right clicking run as admin with no luck, I'm not sure why, lgup does say there is a device but says not compatible
Esin8785 said:
I did use UPPERCUT with no luck, I even re updated my drivers and ran it with no luck even right clicking run as admin with no luck, I'm not sure why, lgup does say there is a device but says not compatible
Click to expand...
Click to collapse
I vaguely remember LGUP telling me my device was not compatible. I was able to ignore that and flash anyway. I also had to use the upgrade option, instead of the refurbish option, and then manually do a factory reset before being able to fully boot the phone.
Zhono said:
I vaguely remember LGUP telling me my device was not compatible. I was able to ignore that and flash anyway. I also had to use the upgrade option, instead of the refurbish option, and then manually do a factory reset before being able to fully boot the phone.
Click to expand...
Click to collapse
i would do that but no option u have retry and cancel when opening, but it will work on stock when I re flashed the phone back to stock it will bring it up and the program will open up
Other variants are possible.
Esin8785 said:
note: This was done on a MetroPCS phone, LG G stylo 3 plus MP450, if you try a different model number do at your own risk
I have completed the process and it indeed worked like a charm, I am now back on stock rom, just let the twrp do it's thing and it will be done. It looks like it hangs up but just let it do it's thing, I went and smoked a cigg came back and twrp said it was done, WIPE THE DEV when booting for first time it's going to take some time again let it do it's thing it will turn on, thank you so much for this, this should be a recommend post for the top, I wonder if you can make backups for other model's tmobile boost what ever...
You will loose root, you will loose TWRP, they are simple go to this post to do re root or to just put on TWRP, https://forum.xda-developers.com/android/development/recovery-twrp-v3-lg-stylo-3-plus-t3649621
Click to expand...
Click to collapse
I can make for other models I just got to download there kdz's and extract them. If there is a need for other models let me know and I'll be more then happy to make.
I want the t mobile one
Stock Zip for T-Mobile
rlcbm said:
I want the t mobile one
Click to expand...
Click to collapse
https://www.dropbox.com/s/axxk4ma4zm7gd7e/lgstyloplus3stockT-mobile.zip?dl=0
androidpimpz said:
https://www.dropbox.com/s/axxk4ma4zm7gd7e/lgstyloplus3stockT-mobile.zip?dl=0
Click to expand...
Click to collapse
that broke my fingerprint reader
Fingerprint
rlcbm said:
that broke my fingerprint reader
Click to expand...
Click to collapse
Fingerprint broken is a known problem when reverting to stock from lineage
Someone has found a solution though,
this is from the lineage post
.
---------- Post added at 09:15 PM ---------- Previous post was at 09:03 PM ----------
["Well luckily, I remembered the fix. And I remembered why I made a complete twrp backup of the lineage install before going back to stock. I made a backup of my fully configued stock, wiped everything but internal storage(obviously)and restored the lineage backup. Booted in, deleted all of the registered prints and the pin, then rebooted(back into lineage to make sure everything sticks). Then just back into twrp, wipe again, restore my stock backup. Booted in once, then rebooted once for good measure. Added a pin and a few fingerprints and it works as it should now. I don't remember which phone it was(maybe my Note 4), but it was always very important to delete your prints/pins before wiping/flashing/restoring to any other rom, or even just an backup. Not sure what happened if you no longer have a backup of lineage where you registered prints. Maybe install/setup a fresh lineage, add prints and a pin, then delete them all, then revert/restore to stock?" ]
i did not find this just letting you know a solution i take no credit for this.
can someone reupload the stock flashable zip for metro?
https://1drv.ms/u/s!AuMZKmd4ajArgb8stmaVcrIzKZCwbg
Metro Pcs Stock
Hi!
I have a big problem to return to stock after trying the Elemental v. 1.1.
I have tried the full backup from here: https://forum.xda-developers.com/ma...other-development/oeminfo-collection-t3762385 but it says that it is rooted when I boot it.
I then tried: https://forum.xda-developers.com/ma...evelopment/stock-rom-rne-l21c185b142-t3764065 (I know it is the wrong localization, but I was desperate, sorry ) and this actually booted with no problem, no notice of being rooted BUT now I faced that the unit had been turned into a NEO-L21.
I thought that I could fix that with the first links change of OEM, but it would not work...what am I doing wrong?
And does anyone have a backup without root, or a way to fix it using the newly published Full-OTA that have started to come for our device?
Thanks in beforehand!
davurleon said:
Hi!
I have a big problem to return to stock after trying the Elemental v. 1.1.
I have tried the full backup from here: https://forum.xda-developers.com/ma...other-development/oeminfo-collection-t3762385 but it says that it is rooted when I boot it.
I then tried: https://forum.xda-developers.com/ma...evelopment/stock-rom-rne-l21c185b142-t3764065 (I know it is the wrong localization, but I was desperate, sorry ) and this actually booted with no problem, no notice of being rooted BUT now I faced that the unit had been turned into a NEO-L21.
I thought that I could fix that with the first links change of OEM, but it would not work...what am I doing wrong?
And does anyone have a backup without root, or a way to fix it using the newly published Full-OTA that have started to come for our device?
Thanks in beforehand!
Click to expand...
Click to collapse
to remove the NEO-L21 phone settings.
you should restore the boot backup only.
Backup BOOT RNE-L21C432B133 clean
** https://mega.nz/#F!s4s1WKIQ!kDwYTMP9YmGan1thThXRfA
and restart.
boot
Chisetdel31260 said:
to remove the NEO-L21 phone settings.
you should restore the boot backup only.
Backup BOOT RNE-L21C432B133 clean
** https://mega.nz/#F!s4s1WKIQ!kDwYTMP9YmGan1thThXRfA
and restart.
Click to expand...
Click to collapse
I don't know what goes wrong, but it does not boot with this boot partition. Could it be because the NEO-L21 backup I restored is Android 6.0?
davurleon said:
I don't know what goes wrong, but it does not boot with this boot partition. Could it be because the NEO-L21 backup I restored is Android 6.0?
Click to expand...
Click to collapse
It's not Android 6.0. The info in "About Phone" is just wrong. You are on android 7.0. I would recommend you to do what I have done for myself.
https://forum.xda-developers.com/ma...pilation-firmware-flasheables-huawei-t3761483
Follow the instruction in this topic which is:
(Remember to get the unlock code for bootloader before you flash anything !!)
1.Flash the OEM info from cust432 or whatever cust you want.
2.Unlock the bootloader and flash TWRP
3.Flash the firmware proper for your cust from the above topic and everything should work. I did this for my phone that was cust c738 before and it works like a charm now and I am on cust432. The only thing for me is that I can't do an OTA update to B133. I am on full stock without root, but I have unlocked BL. I tried to relock it to see if it changes anything but then my phone is stuck on bootloop.
So since I'm here can anyone tell me...Do I have to be on locked BL in order to perform an OTA update ?
If yes how do i relock it ? Because if i do "fastboot oem relock code" then my phone is stuck on bootloop....
We can't back to stock rom, since huawei not release online, we can go to customer service thay said.
I'd like to keep this simple. I tried rooting and not a single tutorial on here has ended with root privileges for various reasons. I'm done with it. I flashed stock firmware in hopes of removing any trace of files that may have been altered during the various root tutorials I followed, but Samsung Pass says the device is still rooted.
What do I need to do to return to 100% stock?
noxarcana said:
I'd like to keep this simple. I tried rooting and not a single tutorial on here has ended with root privileges for various reasons. I'm done with it. I flashed stock firmware in hopes of removing any trace of files that may have been altered during the various root tutorials I followed, but Samsung Pass says the device is still rooted.
What do I need to do to return to 100% stock?
Click to expand...
Click to collapse
I assume you unlocked the bootloader. Try Relocking and flash the firmware again.
Weather that will work is anybodys guess.
Rooting is a pretty simple procedure I can't think of any reason it didn't work except user error.
This method works perfectly on T860.
***********************
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
jhill110 said:
I assume you unlocked the bootloader. Try Relocking and flash the firmware again.
Weather that will work is anybodys guess.
Rooting is a pretty simple procedure I can't think of any reason it didn't work except user error.
Click to expand...
Click to collapse
Well, this isn't the first time I've rooted a device and I followed every step of every tutorial I found on here and, for some reason, it would not root. This is the first, and only, device I've had this much trouble with.
The tutorial for rooting without TWRP: I made the patched AP file and flashed it; however, I could not boot into recovery or download mode and it always stuck on the boot logo.
The tutorial for installing TWRP didn't have a link for the encryption disabler and the one I found did absolutely nothing and the folders in storage just showed as a string of numbers and letters.
Maybe, if someone could put together a full tutorial with the files being used within the tutorial, it would have worked.
noxarcana said:
Well, this isn't the first time I've rooted a device and I followed every step of every tutorial I found on here and, for some reason, it would not root. This is the first, and only, device I've had this much trouble with.
The tutorial for rooting without TWRP: I made the patched AP file and flashed it; however, I could not boot into recovery or download mode and it always stuck on the boot logo.
The tutorial for installing TWRP didn't have a link for the encryption disabler and the one I found did absolutely nothing and the folders in storage just showed as a string of numbers and letters.
Maybe, if someone could put together a full tutorial with the files being used within the tutorial, it would have worked.
Click to expand...
Click to collapse
Did you get the bootloader unlocked?
Unlocking the bootloader:
https://www.getdroidtips.com/how-to...to_Unlock_Bootloader_on_Samsung_Galaxy_Tab_S6
To get to download mode it's volume up and volume down then plug your pc into device. NOT POWER AND VOLUME DOWN. This can be a pain in the back side.
If you do it this way you'll get the option unlock / lock bootloader or go to bootloader mode.
If you follow the instructions perfectly and then follow the instructions for rooting it will work.
Move on to root.
ROOTING :
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
AP SLOT = PATCHED FILE
BL SLOT = BL FILE
CP SLOT = CP FILE (T865) NOT T860... T860 HAS NO CP FILE
CSC SLOT =HOME CSC FILE
DON'T forget to setup WiFi before installing magisk manager. ^^^^^^^^^
Install TWRP.
TWRP :
https://forum-xda--developers-com.c...b-s6/development/recovery-twrp-3-3-1-t3975587
I hope this helps you out.
If you have anymore questions just ask.
Disable DM VERITY ENCRIPTION DISABLER
PATCHED ODIN
jhill110 said:
Did you get the bootloader unlocked?
Click to expand...
Click to collapse
Yep, bootloader unlock was easy. I'll give root another try with your steps in a couple of days when I'm off work. Sorry if I came across a bit aggressive in my previous posts; I have a tendency to do so even when I'm not frustrated.
This has been so frustrating to me because I know rooting is usually a simple process; as you said previously.
jhill110 said:
ROOTING :
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
AP SLOT = PATCHED FILE
BL SLOT = BL FILE
CP SLOT = CP FILE (T865) NOT T860... T860 HAS NO CP FILE
CSC SLOT =HOME CSC FILE
DON'T forget to setup WiFi before installing magisk manager. ^^^^^^^^^
Click to expand...
Click to collapse
So, yea, I'm a bit late getting around to this. Sorry.
This is where things get hung up. Everything flashes just fine and I can even get into TWRP; however, when I try to boot the tablet i get the Galaxy Tab S6 screen, then the warning about the bootloader being unlocked, and back to the Galaxy Tab S6 screen but with a "unofficial software" warning....and repeat. It just boot loops and this is where I've since I started this thread.
Also, returning to stock doesn't completely remove root traces as I can't use Samsung Pass and I simply get a warning about the device seemingly being rooted even though it isn't.
If you installed TWRP, then you tripped Knox tripping Knox will permentally disable Samsung Pay as far as I'm aware. You'll never get it back, regardless of root or no root access.
Also, I'm not sure why you're installing TWRP AND trying to flash a Magisk patched OS. It's one or the other, you don't need to do both. Unless something has changed in Android 10?
If you're flashing TWRP, you just need to flash Magisk in TWRP(along with the other files!), no need to patch AP.
bartleby999 said:
If you installed TWRP, then you tripped Knox tripping Knox will permentally disable Samsung Pay as far as I'm aware. You'll never get it back, regardless of root or no root access.
Also, I'm not sure why you're installing TWRP AND trying to flash a Magisk patched OS. It's one or the other, you don't need to do both. Unless something has changed in Android 10?
If you're flashing TWRP, you just need to flash Magisk in TWRP(along with the other files!), no need to patch AP.
Click to expand...
Click to collapse
Not Samsung Pay, I couldn't care less about that, but Samsung Pass; I guess it looks for knox being tripped now too. That sucks, but I'll make do without it.
I was following the guides posted above. The root guide said to flash a Magisk patched OS and then there was a guide for installing TWRP. I never had this many issues or this much confusion with my 1st gen Tab S; maybe I just haven't kept as close of an eye on these things since I've been without a tablet for awhile before getting the Tab S6.
Anyway, for clarification, all I need to do is flash TWRP and then flash magisk from within TWRP? Or, just install the magisk apk after booting into Android?
noxarcana said:
Not Samsung Pay, I couldn't care less about that, but Samsung Pass; I guess it looks for knox being tripped now too. That sucks, but I'll make do without it.
I was following the guides posted above. The root guide said to flash a Magisk patched OS and then there was a guide for installing TWRP. I never had this many issues or this much confusion with my 1st gen Tab S; maybe I just haven't kept as close of an eye on these things since I've been without a tablet for awhile before getting the Tab S6.
Anyway, for clarification, all I need to do is flash TWRP and then flash magisk from within TWRP? Or, just install the magisk apk after booting into Android?
Click to expand...
Click to collapse
My bad for some reason I just read that as Samsung Pay. But yeah Samsung Pass also doesn't work with root, I'm not sure if that is permanent though as I've never used Samsung Pass, but did come across this thread https://forum.xda-developers.com/general/rooting-roms/samsung-pass-knox-tripped-devices-t3687977 it is possible to get some components of Knox to function again, (I have a working Secure Folder) so might be worth taking a look.
As for you question...
You should give this thread a good read... https://forum.xda-developers.com/galaxy-tab-s6/development/recovery-twrp-3-3-1-t3975587
Basic steps are... Unlock the bootloader and then boot into system and ensure it's unlocked in settings. You may need to connect to the web, I can't remember tbh
First you need to install TWRP, once that is done you need to reboot but YOU HAVE TO boot directly back into TWRP. You cannot boot into system, or TWRP will be overwritten by stock recovery and you'll need to start over again. Once TWRP is installed, boot into TWRP and format data then reboot recovery, flash Kernel then flash encryption disabler then unmount the system and flash Magisk 20.4 - Finally reboot to system.
I'd seriously and strongly suggest reading that TWRP thread to ensure things go smoothly.
bartleby999 said:
First you need to install TWRP, once that is done you need to reboot but YOU HAVE TO boot directly back into TWRP. You cannot boot into system, or TWRP will be overwritten by stock recovery and you'll need to start over again. Once TWRP is installed, boot into TWRP and format data then reboot recovery, flash Kernel then flash encryption disabler then unmount the system and flash Magisk 20.4 - Finally reboot to system.
I'd seriously and strongly suggest reading that TWRP thread to ensure things go smoothly.
Click to expand...
Click to collapse
I'll give those threads a thorough reading over tonight and tomorrow night while at work and then see if I can get this all sorted out Monday when I'm off. I remember Pass still working with root on the original Tab S so I'm hoping it hasn't changed.
Thanks for jumping in to try and help me with this. I'll update within a few days instead of months like my last update. ?
noxarcana said:
I'll give those threads a thorough reading over tonight and tomorrow night while at work and then see if I can get this all sorted out Monday when I'm off. I remember Pass still working with root on the original Tab S so I'm hoping it hasn't changed.
Thanks for jumping in to try and help me with this. I'll update within a few days instead of months like my last update. ?
Click to expand...
Click to collapse
It has definitely changed. Pass doesn't work on my Tab S6 and I'm rooted, I guess Knox is now integrated with alot of Samsung apps now. Not sure if it's possible or not to get it working again though, I've never bothered to research it as I don't need it for anything - But as I said, I got Secure Folder working again, so there's some hope for Pass I guess - That first thread I linked looked promising, but I only skimmed it, because frankly I'm not interested.
If you need anymore help, report back -I'll try my best. Also, the TWRP thread I linked is full of helpful people. :good:
bartleby999 said:
It has definitely changed. Pass doesn't work on my Tab S6 and I'm rooted, I guess Knox is now integrated with alot of Samsung apps now. Not sure if it's possible or not to get it working again though, I've never bothered to research it as I don't need it for anything - But as I said, I got Secure Folder working again, so there's some hope for Pass I guess - That first thread I linked looked promising, but I only skimmed it, because frankly I'm not interested.
If you need anymore help, report back -I'll try my best. Also, the TWRP thread I linked is full of helpful people. :good:
Click to expand...
Click to collapse
Perhaps I'm just not meant to have root with this device. Flashing that kernel causes Wifi not to work, but it does boot. Not flashing the kernel also booted, but I couldn't install Magisk Manager. Other than the bootloader still being unlocked, I'm back on stock firmware.
noxarcana said:
Perhaps I'm just not meant to have root with this device. Flashing that kernel causes Wifi not to work, but it does boot. Not flashing the kernel also booted, but I couldn't install Magisk Manager. Other than the bootloader still being unlocked, I'm back on stock firmware.
Click to expand...
Click to collapse
What firmware are you running?
I remember seeing something about one of the newer Kernels effecting WIFI on Android 10. Assume you're running that?
If that's the case, give the TWRP thread a browse - You maybe able to find an older version of the Kernel that'll work - As far as I'm aware, an older Kernel than what you currently installed will work, but a newer version than currently installed will possibly cause bootloop.
I can't help much with Android 10 specific stuff as I'm still running Android 9 because it's stable.
bartleby999 said:
What firmware are you running?
I remember seeing something about one of the newer Kernels effecting WIFI on Android 10. Assume you're running that?
If that's the case, give the TWRP thread a browse - You maybe able to find an older version of the Kernel that'll work - As far as I'm aware, an older Kernel than what you currently installed will work, but a newer version than currently installed will possibly cause bootloop.
I can't help much with Android 10 specific stuff as I'm still running Android 9 because it's stable.
Click to expand...
Click to collapse
I am definitely on the latest Android 10 update so I'll see if I can find an earlier version that will work. I'll see what I can find out on the TWRP thread.
noxarcana said:
I am definitely on the latest Android 10 update so I'll see if I can find an earlier version that will work. I'll see what I can find out on the TWRP thread.
Click to expand...
Click to collapse
If you can't find an older Kernel (I'm not sure there is one for Android 10), it may be the case that you'll need to wait for the Kernel to be updated.
bartleby999 said:
If you can't find an older Kernel (I'm not sure there is one for Android 10), it may be the case that you'll need to wait for the Kernel to be updated.
Click to expand...
Click to collapse
Yea, it looks like Samsung made some "wifi improvements" in OneUI 2.5 and that's causing some kernel issues preventing wifi from working. I think I could find a kernel fairly easily, but I think I'm just going to wait for a kernel update. If it never comes, I'll find an older kernel. Thanks for the help!
Hello,
I was installing different custom ROMS for this phone, then reverted back to Stock ROM. It updated itself, and IMEI got erased somehow.
Is there any way possible to flash a custom ROM, or even custom recovery using MSMDownloadTool? I had a global version N10, so it was sim unlocked and bootloader unlockable, and I do actually have my IMEI on the back of my box, but can't put it into my phone as I have to root it. But I can't root it because the bootloader is now locked, and the bootloader is now locked because there is no IMEI......
This leaves me locked out of fastboot, so the only option is edl, which works just fine. However, only MSMDownloadTool is compatible with this mode, and it only installs Stock ROMs.
I tried extracting the .OPS files, replacing the stock recovery with twrp (and then renaming it to recovery.img), repacking the .ops then installing it. It installs, but then never boots and is just stuck in edl mode until I reflash the normal stock rom with the stock recovery.
What Do I do?
Thanks
CrustyBurger33 said:
Hello,
I was installing different custom ROMS for this phone, then reverted back to Stock ROM. It updated itself, and IMEI got erased somehow.
Is there any way possible to flash a custom ROM, or even custom recovery using MSMDownloadTool? I had a global version N10, so it was sim unlocked and bootloader unlockable, and I do actually have my IMEI on the back of my box, but can't put it into my phone as I have to root it. But I can't root it because the bootloader is now locked, and the bootloader is now locked because there is no IMEI......
This leaves me locked out of fastboot, so the only option is edl, which works just fine. However, only MSMDownloadTool is compatible with this mode, and it only installs Stock ROMs.
I tried extracting the .OPS files, replacing the stock recovery with twrp (and then renaming it to recovery.img), repacking the .ops then installing it. It installs, but then never boots and is just stuck in edl mode until I reflash the normal stock rom with the stock recovery.
What Do I do?
Thanks
Click to expand...
Click to collapse
If your bootloader was relocked, encryption and partition checking were enabled again.
TWRP would only cause your phone to register as modified and lock itself...and due to streamlining of a lot of functions, you can't even use the dialer to enter the menu needed.
Best you can do is totally wipe everything on your phone and generate a new android ID. (You have to do this from the actual OS instead of recovery though. Recovery format uses predetermined instructions. The format option from the android settings panel has a different set of instructions and one of them is to generate a new android ID, which includes IMEI)
Thanks for the reply, although im kinda confused by your answer. How do I generate a new android ID? (what does that even mean lol). I checked in my settings and I can't find any "format option"
CrustyBurger33 said:
Thanks for the reply, although im kinda confused by your answer. How do I generate a new android ID? (what does that even mean lol). I checked in my settings and I can't find any "format option"
Click to expand...
Click to collapse
Android ID is what determines your phone is the phone it claims to be when pinging google services.
Move any files you want to keep to somewhere safe. Format your phone, android will push you a new id number. It won't fix your IMEI, but it'll keep your phone from being absolutely useless in the process.
After your phone is formated and has booted back into the OS, you can enable adb. Adb into fastboot, use fastboot to determine if your device is still bootloader unlocked using the fastboot oem device-info command
ninjasinabag said:
After your phone is formated and has booted back into the OS, you can enable adb. Adb into fastboot, use fastboot to determine if your device is still bootloader unlocked using the fastboot oem device-info command
Click to expand...
Click to collapse
I tried everything you said, reset everything, still no IMEI, and even if the Android ID is different it hasn't really changed anything. Just to be clear, when I flashed the stock ROM earlier, everything worked as intended apart from the SIM card (which doesnt work at all) and the WiFi (which keeps dropping after 5 seconds of connection). Those problems persist even now.
Guess I'll be messing around with the SMT mode in MSMDownloadTool since I've already lost my IMEI, see what I can do from that. If there's anything I do actually end up finding out, I'll post it on xda.
Update
I installed an update by download a zip, installed update via settings. System rebooted to complete update, and somehow the oem unlock option opened!!
From this point, fixing it will be pretty straight forward I think
Thanks for your help
CrustyBurger33 said:
Update
I installed an update by download a zip, installed update via settings. System rebooted to complete update, and somehow the oem unlock option opened!!
From this point, fixing it will be pretty straight forward I think
Thanks for your help
Click to expand...
Click to collapse
Nice! If everything is working properly besides the IMEI at this point, there's a couple of PC applications you can use.
I'd recommend write dual imei, not gonna post a link since IMEI fudging is against the rules (even if you're just trying to repair your IMEI)
Use the IMEI that's on your device sticker or on your phone packaging specifically.
Either way, hoping you get your phone back up to 100%.
As it turns out, it's not easy at all. My WiFi has exactly the same issue... keeps dropping, No SIM card, no baseband version. What's crazy is that I have rooted, and even repaired the IMEI via a tool. If I read the IMEI via the tool (and different ones just to be sure), they will all show the IMEI the same as the one that I wrote (which were the original ones).
But for some reason the phone still doesnt recognize it. I reboot it. Same story. The tool recognizes, the phone doesn't. I know for a fact that the issue cannot be hardware, at least for WiFi. If it was, it wouldn't connect to any network, but it does, and then disconnects after a few seconds. I think I have been all over every post on the internet regarding this issue, but still no luck.
Honestly, check with OnePlus if you're under the 1 year warranty window. This sounds like an issue that can really only be fixed with a replacement device.
CrustyBurger33 said:
As it turns out, it's not easy at all. My WiFi has exactly the same issue... keeps dropping, No SIM card, no baseband version. What's crazy is that I have rooted, and even repaired the IMEI via a tool. If I read the IMEI via the tool (and different ones just to be sure), they will all show the IMEI the same as the one that I wrote (which were the original ones).
But for some reason the phone still doesnt recognize it. I reboot it. Same story. The tool recognizes, the phone doesn't. I know for a fact that the issue cannot be hardware, at least for WiFi. If it was, it wouldn't connect to any network, but it does, and then disconnects after a few seconds. I think I have been all over every post on the internet regarding this issue, but still no luck.
Click to expand...
Click to collapse
Hi I have a similar problem.. My phone oneplus 8t is stuck in 'SMT Download failed error' mode. I was tryimg out custom roms which has caused this. My phone says can only be fixed via SMT Download mode. Can you help me out using the SMT download mode? I have tried MSM Tool normally to unbrick my phone but it doesn't work.
hello @nightfury04
If you have a Oneplus 8T you have to download the appropriate MSMDownloadTool (specifically for it) and make sure the version is correct too. Is your phone global/ locked to a carrier?