New video guide below
VIDEO GUIDE
1. *VERY IMPORTANT* We need to back up your broken persist.img and store it in a safe place. PC preferred. We will need this later. Do not leave the backup on the device as the next step will wipe the device.
*IF YOU LOOSE THIS PERSIST.IMG BEFORE WE MODIFY IT WITH A CALIBRATION, YOU LOOSE ALL CHANCE OF FIXING THIS YOURSELF*
*IT HOLDS IMPORTANT FP CALIBRATION DATA THAT WE WILL BE OVERWRIGHTING IN THE NEXT FEW STEPS*
Note: This requires root
Type this into terminal or ADB shell with root privileges.
Code:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Backup the partition to another device. Preferably a PC as you may need one in the later steps.
2. Next we have to restore our OS to an earlier OOS. (10.5.4 is what I used and recomended)
Use the MSMTool to restore your device to 10.5.4.Note: You will loose your unlocked bootloader and will be required to unlock your bootloader once more.
Guide and Source for MSMTool
MSMTool 10.5.4 Download
3. Next step is to unlock the built in 'Factory Mode' I have a guide on how to do this below.
[GUIDE] Unlock Factory Mode *root*
4. Now we need to perform a FP calibration. We want to fail.
Enter Factory Mode as shown in the previous guide. (*#801# in the stock dialer)
Swipe over to "Device Debugging"
Select "Finger print test"
Select "Finger print calibration test(Pure White - 90% Blue)
Select "Start Test"
Keep on going through the tests (You must hold an object or your finger over sensor on all BUT THE BLACK RUBBER TEST of these test for it to work!)
The test will fail and this is what we want. There should be a lot of red lines, if you only have one or two try again.
5. We need to extract the the old broken persist.img
NOTE: It is important that we extract the backed up persist.img as it has been unmodified by our recent calibration. This persist.img although broken still has all our working calibrations on it including Finger Print calibrations.
The way I did this is by opening it extracting it via 7-ZIP on my PC
Once extracted move the 'DATA' folder and the 'ENGINEERMODE' folder to the root of your sdcard.
6. Download a root explorer. I highly recommend 'Solid Explorer' from the Play Store.
Open 'DATA' folder and delete 'gf_persist.so'
Select the 'DATA' and 'ENGINEERMODE' folders you just put on the device and place them at /mnt/vendor/persist/
It should ask you if you want to keep the old or new files. Select to keep the new.
Reboot.
7. If you followed all my steps correctly this you should be able to go into settings and add your fingerprints.
Why does this work?
Good question... I think what is happening is something in the persist partition breaks which causes the device to think that the sensor is not calibrated when in fact it still is.
When we start and fail a new calibration this fixes whatever was broken in our partition. But now we have a failed calibration.
So what we do is take the files from our backed up persist partition and move over all the necessary files that have our original calibration. But now our partition has the part of it that wasn't working fixed.
I spent a good many days working on this fix (1-2 hundred hours or so). I hope you can be respectful if you have issues. Please kindly ask below and I'll do my best to help.
Thanks worked on.my TMobile OnePlus.
I can confirm working on OOS 1.5.6 too. I downgraded from 10.5.9 with downgrade rom, which restores OOS to 10.5.6, and followed your guide and it worked as a charm. The only problem is that i cannot lock back the bootloader, cause it breaks FP again. Did you maybe try to lock it to try? Nice work man.
T-Mobile OnePlus 8 here. Stock firmware, orginally had my bootloader unlocked, rooted with TWRP and Magisk, backed up modem, converted to international firmware (10.5.7), lost signal, had to restore modem, ota'd to 10.5.9, unlocked bootloader again, rooted, etc. All while having a working FP the whole time. Ended up flashing EdXposed via Magisk, broke SafetyNet, etc, did a factory reset on TWRP (3.4.0-1 test), wiped data, rebooted recovery, rebooted system, booted back to TWRP. Installed Magisk to see if it'll boot with root, same thing. MSM'd back to T-Mobile firmware, then converted to international again. After the conversion was done and I unlocked bootloader and rebooted to system, my FP was broken. Ended up MSM'ing back to T-Mobile stock to see if it would work again, nothing.
TL;DR does this method only work if I had a working FP to begin with like it did stock out of the box?
TheKnux said:
T-Mobile OnePlus 8 here. Stock firmware, orginally had my bootloader unlocked, rooted with TWRP and Magisk, backed up modem, converted to international firmware (10.5.7), lost signal, had to restore modem, ota'd to 10.5.9, unlocked bootloader again, rooted, etc. All while having a working FP the whole time. Ended up flashing EdXposed via Magisk, broke SafetyNet, etc, did a factory reset on TWRP (3.4.0-1 test), wiped data, rebooted recovery, rebooted system, booted back to TWRP. Installed Magisk to see if it'll boot with root, same thing. MSM'd back to T-Mobile firmware, then converted to international again. After the conversion was done and I unlocked bootloader and rebooted to system, my FP was broken. Ended up MSM'ing back to T-Mobile stock to see if it would work again, nothing.
TL;DR does this method only work if I had a working FP to begin with like it did stock out of the box?
Click to expand...
Click to collapse
Just follow the guide, you'll have it working. You just have to backup your current persist
dzontra83 said:
Just follow the guide, you'll have it working. You just have to backup your current persist
Click to expand...
Click to collapse
So back it up even though it's broken? I'm on T-Mobile stock again, locked BL. Should I unlock, root, then pull persist and back it up?
TheKnux said:
So back it up even though it's broken? I'm on T-Mobile stock again, locked BL. Should I unlock, root, then pull persist and back it up?
Click to expand...
Click to collapse
Exactly, a T-Mobile user confirmed guide to work, check 2nd post
While on 10.5.7, unlocked bootloader, I flash TWRP, then reboot, and it boots back to TWRP. When I flash Magisk 20.4 zip in TWRP, it goes to boot, then enters CrashDump Mode. When I try and use the flash-all to downgrade to 10.5.4, I get a bunch of fastboot "cannot flash critical partitions" errors, it fails, and goes back to CrashDump Mode. What am I doing wrong? Also, is it really necessary to downgrade to an earlier version of OOS to use Engineering Mode or can I use 10.5.7?
TheKnux said:
While on 10.5.7, unlocked bootloader, I flash TWRP, then reboot, and it boots back to TWRP. When I flash Magisk 20.4 zip in TWRP, it goes to boot, then enters CrashDump Mode. When I try and use the flash-all to downgrade to 10.5.4, I get a bunch of fastboot "cannot flash critical partitions" errors, it fails, and goes back to CrashDump Mode. What am I doing wrong? Also, is it really necessary to downgrade to an earlier version of OOS to use Engineering Mode or can I use 10.5.7?
Click to expand...
Click to collapse
When you unlock bootloader, only boot into TWRP, then install magisk, i thin it Is still recommend to only boot into TWRP, not to flash it.
dzontra83 said:
When you unlock bootloader, only boot into TWRP, then install magisk, i thin it Is still recommend to only boot into TWRP, not to flash it.
Click to expand...
Click to collapse
Thank you so much, that worked! New problem, what do I do since I can't downgrade to an earlier OOS (10.5.4)?
Performing the test on T-Mobile 10.5.7, when performing the test, nothing is failing after pressing start test. Its all passing, what should I do?
When trying to downgrade using the 10.5.4 MSM Tool. it gives an error of "Unsupported Target TMO" and "param preload" and fails.
TheKnux said:
Thank you so much, that worked! New problem, what do I do since I can't downgrade to an earlier OOS (10.5.4)?
Performing the test on T-Mobile 10.5.7, when performing the test, nothing is failing after pressing start test. Its all passing, what should I do?
When trying to downgrade using the 10.5.4 MSM Tool. it gives an error of "Unsupported Target TMO" and "param preload" and fails.
Click to expand...
Click to collapse
Did you follow the instructions in test exactly? In second test you must't press the sensor.
Can help you with TMobile model, I have international one.
I figured it out. I was just being a dumbass I guess. Has anyone noticed the fingerprint sensor not being able to read that well compared to before it was broken? It seems like it fails a lot more before it succeeds. Unless now that it's working, we can perform the calibration again and it'll work better?
TheKnux said:
I figured it out. I was just being a dumbass I guess. Has anyone noticed the fingerprint sensor not being able to read that well compared to before it was broken? It seems like it fails a lot more before it succeeds. Unless now that it's working, we can perform the calibration again and it'll work better?
Click to expand...
Click to collapse
Don't know about that, mine works just fine
So I think I messed up, I ended up performing the calibration again, while it was already working, and now it says "fingerprint hardware not present" any suggestions on how to fix? I performed the instructions in the guide (again) and nothing worked. When the error pops up, if I press back, the error message goes away and the FP icon is there. When I tap on it, it lights up white but doesn't vibrate or register anything. I already used the MSM tool to go back to Tmobile stock, then used the fastboot ROM to go to Global 10.5.7, followed the guide again, still nothing.
TheKnux said:
So I think I messed up, I ended up performing the calibration again, while it was already working, and now it says "fingerprint hardware not present" any suggestions on how to fix? I performed the instructions in the guide (again) and nothing worked. When the error pops up, if I press back, the error message goes away and the FP icon is there. When I tap on it, it lights up white but doesn't vibrate or register anything. I already used the MSM tool to go back to Tmobile stock, then used the fastboot ROM to go to Global 10.5.7, followed the guide again, still nothing.
Click to expand...
Click to collapse
The initial backup of the persist.img should do the trick, if you repeat the process once again, it should work
dzontra83 said:
The initial backup of the persist.img should do the trick, if you repeat the process once again, it should work
Click to expand...
Click to collapse
I tried that, multiple times. Still not working. Is it possible for someone to upload their persist.img so I can try it or is it device specific? Granted, I pulled my initial persist.img from stock rooted Tmobile ROM AFTER I broke it even though it worked before (long story). I wasn't able to downgrade to 10.5.4 because when I tried using the MSM tool, it gave me a TMO device error and I couldn't use a fastboot ROM to go to 10.5.4 cause it kept entering CrashDump mode every time it tried rebooting to fastboot to finish the flash process .
TheKnux said:
I tried that, multiple times. Still not working. Is it possible for someone to upload their persist.img so I can try it or is it device specific? Granted, I pulled my initial persist.img from stock rooted Tmobile ROM AFTER I broke it even though it worked before (long story). I wasn't able to downgrade to 10.5.4 because when I tried using the MSM tool, it gave me a TMO device error and I couldn't use a fastboot ROM to go to 10.5.4 cause it kept entering CrashDump mode every time it tried rebooting to fastboot to finish the flash process .
Click to expand...
Click to collapse
Your cannot use someone else's persist, you must't use yours.
dzontra83 said:
Your cannot use someone else's persist, you must't use yours.
Click to expand...
Click to collapse
What about someone else's DATA and ENGINEERINGMODE folders? I've tried everything. Even recalibrating multiple times. It's not giving me a bunch of errors like it did before, just one error. The last error is FAIL! OPERATION_STEP_GET_KB_CALIBRATION TEST FAIL:GF_ERROR_GENERIC
Just wondering, what is the point of downgrading to an earlier OOS? If I was able to do it on the Tmobile firmware with success, is there an importance in downgrading?
Thank you so very very much!!! I have a T-Mobile 7T Pro 5G McLaren which hasn't had a working fp in almost 2 months. I hadn't made a backup of persist before the fp broke, so I thought I was completely screwed. Luckily, I did make a backup of persist before trying to use the fp calibration tool myself without any luck shortly after it broke (basically just clicking stuff and guessing lol). Found this thread and I had my FP scanner working again perfectly in less than 15 minutes!!!! Thank you soooo much for all the hours and effort you put into figuring this out!!!!!!!
Didn't have to run the msm tool to revert to older version of OOS and lose all my data either!!
Just one question and it's just for my curiosity. Why do we delete "gf_persist.so" from our original persist.img before copying/pasting into /persist partition after "calibration"? Is gf_persist.so not a file containing part of the original calibration? Is that the file which is being fixed by running the hidden calibration commands?
If anyone can help me, it would be much appreciated. https://forum.xda-developers.com/oneplus-8/help/broken-persist-img-problems-t4129587
Related
Hi everyone, sorry for a noob problem but I seemed to have soft bricked my phone and was hoping that somebody here would be able to help me out. I have an A2017U in the US.
A short history:
I had been using my phone on B20 rooted/locked with tenfar's tool for about 3 months now, and decided I would try and update it finally before the new year.
To update it, after reading it seemed I would need to unlock the bootloader to keep root on B29 so I decided first step would be to unlock the bootloader and then update to B29. I did the following steps today
1) Unlock bootloader using DrakenFX's guide here http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 The unlocked proved successful and I was able to boot back into B20 after all the data was wiped, and I followed the instruction to backup the Boot in TWRP. All good.
2) I then decided to follow another of DrakenFX's guides (https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2) to update from B20 to B29. I followed the instructions exactly again, but then the phone just hangs on the ZTE logo on boot infinitely. I wondered if I made a mistake when re-initializing TWRP after unlocking the bootloader. I did a search and found in "Mount" to uncheck "Mount system partition read-only" and unchecked it. The System partition however is unmounted, I'm not sure if that's normal now or not. Even when I check it, after rebooting it goes away. I've checked the MD5 of the ZTE_A2017U.B29_StockSystem_by_DrakenFX.zip file and it's good. I then flashed through fastboot to the new 3.0.3-0 TWRP which I'm now using, and still nothing. It appears I don't have an OS installed. I'm going to guess here the issue is with a setting in TWRP but I've tried everything I could find. Unfortunately I don't seem to have a copy of my stock recovery right now to flash either. I've tried several times to flash ZTE_A2017U.B29_StockSystem_by_DrakenFX.zip and reboot but to no avail. I even tried this tip from rczrazor to delete DATA first and others one by one (https://forum.xda-developers.com/showpost.php?p=69428659&postcount=136) but no such luck for me. Still stuck on the ZTE logo.
tl;dr - I have access to fastboot and TWRP, but apparently no ROM installed even though have flashed now multiple times.
If anybody could help me I would greatly appreciate it. I'm even willing to pay a few bucks in Paypal to help get me going again.
Thank you all in advance.
shyguy88 said:
Hi everyone, sorry for a noob problem but I seemed to have soft bricked my phone and was hoping that somebody here would be able to help me out. I have an A2017U in the US.
A short history:
I had been using my phone on B20 rooted/locked with tenfar's tool for about 3 months now, and decided I would try and update it finally before the new year.
To update it, after reading it seemed I would need to unlock the bootloader to keep root on B29 so I decided first step would be to unlock the bootloader and then update to B29. I did the following steps today
1) Unlock bootloader using DrakenFX's guide here http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 The unlocked proved successful and I was able to boot back into B20 after all the data was wiped, and I followed the instruction to backup the Boot in TWRP. All good.
2) I then decided to follow another of DrakenFX's guides (https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2) to update from B20 to B29. I followed the instructions exactly again, but then the phone just hangs on the ZTE logo on boot infinitely. I wondered if I made a mistake when re-initializing TWRP after unlocking the bootloader. I did a search and found in "Mount" to uncheck "Mount system partition read-only" and unchecked it. The System partition however is unmounted, I'm not sure if that's normal now or not. Even when I check it, after rebooting it goes away. I've checked the MD5 of the ZTE_A2017U.B29_StockSystem_by_DrakenFX.zip file and it's good. I then flashed through fastboot to the new 3.0.3-0 TWRP which I'm now using, and still nothing. It appears I don't have an OS installed. I'm going to guess here the issue is with a setting in TWRP but I've tried everything I could find. Unfortunately I don't seem to have a copy of my stock recovery right now to flash either. I've tried several times to flash ZTE_A2017U.B29_StockSystem_by_DrakenFX.zip and reboot but to no avail. I even tried this tip from rczrazor to delete DATA first and others one by one (https://forum.xda-developers.com/showpost.php?p=69428659&postcount=136) but no such luck for me. Still stuck on the ZTE logo.
tl;dr - I have access to fastboot and TWRP, but apparently no ROM installed even though have flashed now multiple times.
If anybody could help me I would greatly appreciate it. I'm even willing to pay a few bucks in Paypal to help get me going again.
Thank you all in advance.
Click to expand...
Click to collapse
This happened to me once - boot to TWRP, format data, reboot to TWRP, advanced wipe everything but the external SD card,reboot to TWRP, flash DrakenFX B29 bootstack, reboot to TWRP, flash DrakenFX B29 system.
shyguy88 said:
Hi everyone, sorry for a noob problem but I seemed to have soft bricked my phone and was hoping that somebody here would be able to help me out. I have an A2017U in the US.
If anybody could help me I would greatly appreciate it. I'm even willing to pay a few bucks in Paypal to help get me going again.
Thank you all in advance.
Click to expand...
Click to collapse
I have bricked my AXON 7 many times during the last week. The Zip files from DrakenFX are very good. But in case those were still failling...
First, check for corrupted downloads, just check the zip file integrity using 7zip, winRAR or any other tool.
Use TWRP 3.0.3
Try a different ROM such as ZADMix or even CM13.
If everything fails:
Flash TWRP 3.0.2 signed.
Flash the original Stock B29 Boot partition and reboot to recovery
Flash again the verified DrakenFX files.
Hi,
1. If somebody experience this issue with lack of netwrok after Nougat full Rom update, like:
https://forum.xda-developers.com/showpost.php?p=71063185&postcount=121
than follow this fix from another thread:
https://forum.xda-developers.com/showpost.php?p=71054990&postcount=1456
for me it all seems to work fine now.
2. If somebody has issues with MiFlash, I think it is actually better to do the flash within first 5-10, after that it gives strange errors. If so, restrt EDL and press flash on MiFlash a bit faster .
Regards
I failed to boot nougat using these steps:
Boot to edl.
Flashed using miflash full b15 file and then b15 twrp file.
Flashed in twrp a2017 N modem.
Then it gets stuck at 5 secs screen and phone just reboots back to edl. Am i doing it wrong?
However it boots to nougat if only flashing just the b15 full.
Hi,
I had stock B13 Chinese. I MiFlahed fastboot_unlock packge,
did fastboot oem unlock,
MiFlashed B15 twrp,
copied NON-HLOS.bin file from Chinese modem(link above) into extracted B15 Full package folder(which replaced exsiting file in there) ,
reset dalvik etc.from twrp,
flashed B15 full which included already new modem file,
I let it boot finally till the end into standard mode.
This way I don't even have twrp now and all works fine.
Regards
RubiCom said:
Hi,
I had stock B13 Chinese. I MiFlahed fastboot_unlock packge,
did fastboot oem unlock,
MiFlashed B15 twrp,
copied NON-HLOS.bin file from Chinese modem(link above) into extracted B15 Full package folder(which replaced exsiting file in there) ,
reset dalvik etc.from twrp,
flashed B15 full which included already new modem file,
I let it boot finally till the end into standard mode.
This way I don't even have twrp now and all works fine.
Regards
Click to expand...
Click to collapse
Hi, what you mean you don't have twrp? Is it possible to install it somehow again? Is it possible to install SuperSU then? I'm asking this because I want to install A2017U B15 firmware (with OTA support) on A2017 (Chinese model with B13, stock recovery and locked bootloader) and just want to be sure in everything before I start Many thanks!
Wuchko said:
Hi, what you mean you don't have twrp? Is it possible to install it somehow again? Is it possible to install SuperSU then? I'm asking this because I want to install A2017U B15 firmware (with OTA support) on A2017 (Chinese model with B13, stock recovery and locked bootloader) and just want to be sure in everything before I start Many thanks!
Click to expand...
Click to collapse
Hi,
If you MiFlash B15 Full package it overwrites recovery partition...it is a full package after all. If you want TWRP on your nougat after that you need to Miflsh the B15 TWRP package. However inside the TWRP package, there is also modem driver file which you need to first replace with the new modem file, same as with B15 FULL package.
It is al soooo simple. I had some issues with MiFlash initially, as I read somewhere to "keep the vol up down, power fo 5 sec, release, wait 5seconds and than flash"
However I had near 100% success rate when I did press the flash button around 2-5 seconds after booting into EDL mode. Once you do oem unlock, the process is simple as burning ISO image on a CD
I have it now without that last step. It is unlocked, but without TWRP. I did however MiFlashed TWRP yesterday and it did work fine than as well. I don't however think I need TWRP anymore. I did Dalvik etc. reset during upgrading to Nougat... and that's all I needed it for. Maybe I'm wrong and I will MiFlash it again some day, but honestly, this was first time I flashed any Android phone as I come from Nokia- Windows Phone and all I wanted is working Daydream, Netflix VR for my long business flights. It works now. The rest I might need I will install from play store.
It does have that message about unlocked bootloader when you boot the phone, but it does not bother me and I read somewhere that it is better not to relock he phone.
How do I even know if it's OTA capable? When I checked updates, it says your phone is up to date.
Regards
Ok, now is everything much more clear to me, thank you!
Please help fellow china version users... @RubiCom
I have flashed b15 and the updated modem for china but my signal is still unusable. It keeps restarting the sim and when I go to sim settings, "com.android.phone" crashes. Some other settings related to calls/sim also crashes.
my sim is working fine when I'm on LOS. I really just want to use stock system since audio isn't fully fixed with LOS.
BTW, i'm already BL unlocked since b13. Do I still have to flash b15 twrp? I mean I could just fastboot flash twrp after installing full b15. Is there something special miflashing the b15 twrp package?
otaconremo said:
Please help fellow china version users... @RubiCom
I have flashed b15 and the updated modem for china but my signal is still unusable. It keeps restarting the sim and when I go to sim settings, "com.android.phone" crashes. Some other settings related to calls/sim also crashes.
my sim is working fine when I'm on LOS. I really just want to use stock system since audio isn't fully fixed with LOS.
BTW, i'm already BL unlocked since b13. Do I still have to flash b15 twrp? I mean I could just fastboot flash twrp after installing full b15. Is there something special miflashing the b15 twrp package?
Click to expand...
Click to collapse
I follow all the steps in original thread and after all everything works (at least for me) . But, it was a little bit complicated to make it work
So, first after unlocking I installed B15 TWRP, then entered into TWRP and deleted cache, dalvik, etc.. After that I put my phone into EDL again and flashed B15 original (I didn't boot phone to OS between flashing ROM's at all). But, on boot B15 original I still had some chinese symbols and I couldn't finish setup (phone stuck at google account setup). So, I repeated this three steps (installation of B15 TWRP, wiping everything in TWRP and installation of B15 original) again. This time I've got "android encrypted" or some similar message on boot B15 original(??!!), but after reboot everything was completely normal (except message that bootloader is unlocked, which is normal). I don't have TWRP, but 2G/3G/4G signal is great on both SIM's without lose and I have official updates. Comparing with chinese MM, this Nougat is far more better and faster, like I have a new phone
Wuchko said:
I follow all the steps in original thread and after all everything works (at least for me) . But, it was a little bit complicated to make it work
So, first after unlocking I installed B15 TWRP, then entered into TWRP and deleted cache, dalvik, etc.. After that I put my phone into EDL again and flashed B15 original (I didn't boot phone to OS between flashing ROM's at all). But, on boot B15 original I still had some chinese symbols and I couldn't finish setup (phone stuck at google account setup). So, I repeated this three steps (installation of B15 TWRP, wiping everything in TWRP and installation of B15 original) again. This time I've got "android encrypted" or some similar message on boot B15 original(??!!), but after reboot everything was completely normal (except message that bootloader is unlocked, which is normal). I don't have TWRP, but 2G/3G/4G signal is great on both SIM's without lose and I have official updates. Comparing with chinese MM, this Nougat is far more better and faster, like I have a new phone
Click to expand...
Click to collapse
I figured out what's wrong my my setup but still I can't find a way to fix this.
It seems that when I use my original sim cards (2 sims with the same provider), they both get disconnected every second.
When I put another sim from another provider, it does work but still my original sim doesn't get signal. even when changing slots.
I'm really confused how to make them work together.
otaconremo said:
I figured out what's wrong my my setup but still I can't find a way to fix this.
It seems that when I use my original sim cards (2 sims with the same provider), they both get disconnected every second.
When I put another sim from another provider, it does work but still my original sim doesn't get signal. even when changing slots.
I'm really confused how to make them work together.
Click to expand...
Click to collapse
That's weird. I'm also using SIM's from same providers, but without any problems.. Don't know what to tell, maybe you can try install B15 TWRP and wipe everything, then install B15 original and try again.. First time I also had some weird problems...
Wuchko said:
That's weird. I'm also using SIM's from same providers, but without any problems.. Don't know what to tell, maybe you can try install B15 TWRP and wipe everything, then install B15 original and try again.. First time I also had some weird problems...
Click to expand...
Click to collapse
this is actually wierd. I had this problem my my sims. And I had flashed this many times already trying out different methods including miflash and even stock flashable zips from draken. all yields to the same results.
Do you have any idea where to tweak carrier settings from system files? i tried *#*#4636*#*# but still fails.
Unfortunately I don't know it. I guess I had plenty of luck flashing these ROM's, considering how many people have problems..
First of all why did this happen, presumably I wasn't doing anything wrong or uninformed. I just unlocked the bootloader successfully, afterward as many threads claimed I flashed twrp-3.3.1-2-davinci-fix, and now it simply wont boot neither to system nor twrp. Why did this happen?
Does anyone know how to fix this? Thank you!
Mi 9T (M1903F10G)
Did you try to power off and then turn back on holding power and volume up? I had this issue yesterday but doing the vol up and power got me to twrp then did format and it booted up
cmlucht said:
Did you try to power off and then turn back on holding power and volume up? I had this issue yesterday but doing the vol up and power got me to TWRP then did format and it booted up
Click to expand...
Click to collapse
Thank you for your reply. You can't even power off, it will simply bootloop forever into fastboot. Nonetheless I managed to fix it by flashing fastboot ROM using MIFlash, but man, didn't expect root solutions to be this complicated, unstable, and outdated for our beloved Mi 9T. I simply want to achieve root in the stock rom, and wasted 7 hours yesterday and still got nowhere. I come from a classic LG G2, when things were much simple and straight forward back then. You can stop reading here, but now I had to:
Wait 1 week for bootloader unlock.
Flash TWRP, which soft bricked my phone right away. Why on earth, a recovery image provided in many reliable tutorials from multiple sources cause soft-brick in the second step is beyond my comprehension. I am still genuinely curious why did this happen, and why such a broken image is still circulating here?
Then I had to inform myself all about Anti Rollback, in order to prevent it happening, and concluded that MiFlash is safe, so I got MiFlash and a fastboot rom.
Apparently Mi Flash is terribly buggy and kept showing .net error exceptions because a "LOG" folder was missing in root folder, so let's waste one hour scratching our heads what the hell is happening because the developer missed a simple MkDir line during development.
After creating LOG folder, and installing drivers, couldn't flash any fastboot ROM because my 9T antiroll back number is 1 while fastboot rom ARB index was 0.
Then it appears that this error has actually nothing to do with ARB, but it is because I had to a) start MiFlash from C:\, b) remove name spaces in target address and c) shorten fastboot ROM folder name. So I had to get all these 3 variables right in order to resurrect my phone. MiFlash terrible programming didn't stop at step 4) but it extends into showing entirely confusing ARB errors that have nothing to with the real problem, rather petty programming bugs such as folder naming.
Finally managed to boot up 9T, and we're back at square one.
Afterward successfully flashed mauronofrio TWRP including vbmeta and got recovery working.
I decided to try out few custom ROMs since all my data were erased anyway, but it appears my system was encrypted and TWRP showed encrypted alphanumeric characters, so I had to format data in order to flash files.
Now every-time I flash stock ROM .zip I lose TWRP, and every-time I reflash mauronofrio TWRP I end up in recovery bootloop, and so I can't manage to have both at same time in order to move with the Magisk flash.
10 steps and 7 hours later and still got nowhere, just risked bricking my phone.
Now we have to deal with
a) bootloader wait,
b) twrp encryption mess,
c) anti roll back risk,
d) buggy MiFlash
e) safety net measures
f) no custom ROMs that are pre-rooted and simple
g) dependency of stock ROM files - meaning you can't wipe everything including system and just flash custom ROM .zips, like I used to do with 5 android phones before this one. Now you are somehow dependent on original ROM files which probably means you will have to base install stock MI before you flash anything Xiaomi.EU, Evolution X, PixelExperience etc. When did things get so complicated? It seems every year new limitations are introduced and the sheer combination to get them all right give headaches.
Anyway, all I want is to install latest stock ROM from TWRP and keep TWRP so I can also flash Magisk. In other words, how to simply have a rooted stock?
Your mistake is to not use Official TWRP instead of an old TWRP version...
Micdu70 said:
Your mistake is to not use Official TWRP instead of an old TWRP version...
Click to expand...
Click to collapse
Thanks for your reply! Yes, that must have been it. Those outdated tutorials should be removed.
Now I flashed miui_DAVINCIEEAGlobal_V11.0.4.0.QFJEUXM through latest TWRP, but it removed TWRP. When I reflash latest TWRP then it ends up in bootloop.
EDIT: Ended up reflashing all over again using MiFlash. Now the only problem remaining is which version of Magisk is compatible with miui_DAVINCIEEAGlobal_V11.0.4.0.QFJEUXM?
What are you flashing with? I am now using xiaomitools v2 and it installed twrp and magisk with no problems.
I flashed the EU custom stable, I was global but I wanted to compare the 2 and I like the EU better.
I came from a non rootable lg g7.
I have not flashed custom ROMs since my old Galaxy note days.
cmlucht said:
What are you flashing with? I am now using xiaomitools v2 and it installed twrp and magisk with no problems.
I flashed the EU custom stable, I was global but I wanted to compare the 2 and I like the EU better.
I came from a non rootable lg g7.
I have not flashed custom ROMs since my old Galaxy note days.
Click to expand...
Click to collapse
Never heard of XiaomiTools v2, it seems like a great alternative. I used buggy MiFlash to flash fastboot ROM, flashed TWRP, then got a bootloop, formatted data from TWRP and flashed Magisk. It seems everything is working fine now, but in the future I'll make sure to check XiaomiTools v2.
I never used stock ROMs in any of my past phones, first thing I did when I bought a new phone is unlock bootloader and install Lineage or Cyanogenmod back in the days. But somehow I like MIUI so all I needed was root.
It is hard to believe that there are actually phones that have no root at all.
blackmatrix64 said:
Thank you for your reply. You can't even power off, it will simply bootloop forever into fastboot. Nonetheless I managed to fix it by flashing fastboot ROM using MIFlash, but man, didn't expect root solutions to be this complicated, unstable, and outdated for our beloved Mi 9T. I simply want to achieve root in the stock rom, and wasted 7 hours yesterday and still got nowhere. I come from a classic LG G2, when things were much simple and straight forward back then. You can stop reading here, but now I had to:
Wait 1 week for bootloader unlock.
Flash TWRP, which soft bricked my phone right away. Why on earth, a recovery image provided in many reliable tutorials from multiple sources cause soft-brick in the second step is beyond my comprehension. I am still genuinely curious why did this happen, and why such a broken image is still circulating here?
Then I had to inform myself all about Anti Rollback, in order to prevent it happening, and concluded that MiFlash is safe, so I got MiFlash and a fastboot rom.
Apparently Mi Flash is terribly buggy and kept showing .net error exceptions because a "LOG" folder was missing in root folder, so let's waste one hour scratching our heads what the hell is happening because the developer missed a simple MkDir line during development.
After creating LOG folder, and installing drivers, couldn't flash any fastboot ROM because my 9T antiroll back number is 1 while fastboot rom ARB index was 0.
Then it appears that this error has actually nothing to do with ARB, but it is because I had to a) start MiFlash from C:\, b) remove name spaces in target address and c) shorten fastboot ROM folder name. So I had to get all these 3 variables right in order to resurrect my phone. MiFlash terrible programming didn't stop at step 4) but it extends into showing entirely confusing ARB errors that have nothing to with the real problem, rather petty programming bugs such as folder naming.
Finally managed to boot up 9T, and we're back at square one.
Afterward successfully flashed mauronofrio TWRP including vbmeta and got recovery working.
I decided to try out few custom ROMs since all my data were erased anyway, but it appears my system was encrypted and TWRP showed encrypted alphanumeric characters, so I had to format data in order to flash files.
Now every-time I flash stock ROM .zip I lose TWRP, and every-time I reflash mauronofrio TWRP I end up in recovery bootloop, and so I can't manage to have both at same time in order to move with the Magisk flash.
10 steps and 7 hours later and still got nowhere, just risked bricking my phone.
Now we have to deal with
a) bootloader wait,
b) twrp encryption mess,
c) anti roll back risk,
d) buggy MiFlash
e) safety net measures
f) no custom ROMs that are pre-rooted and simple
g) dependency of stock ROM files - meaning you can't wipe everything including system and just flash custom ROM .zips, like I used to do with 5 android phones before this one. Now you are somehow dependent on original ROM files which probably means you will have to base install stock MI before you flash anything Xiaomi.EU, Evolution X, PixelExperience etc. When did things get so complicated? It seems every year new limitations are introduced and the sheer combination to get them all right give headaches.
Anyway, all I want is to install latest stock ROM from TWRP and keep TWRP so I can also flash Magisk. In other words, how to simply have a rooted stock?
Click to expand...
Click to collapse
Hey, I'm facing the same issue you faced here. Waited 7 days to unlock bootloader, after unlocking it, flashed a twrp i found on one of the youtube tutorials. Immediate bootloop. Im fairly new to all of this, and dont understand what certain words even mean tbh. Do you mind guiding me in fixing my phone? Any help would be really appreciated. Thank you.
blackmatrix64 said:
Never heard of XiaomiTools v2, it seems like a great alternative. I used buggy MiFlash to flash fastboot ROM, flashed TWRP, then got a bootloop, formatted data from TWRP and flashed Magisk. It seems everything is working fine now, but in the future I'll make sure to check XiaomiTools v2.
I never used stock ROMs in any of my past phones, first thing I did when I bought a new phone is unlock bootloader and install Lineage or Cyanogenmod back in the days. But somehow I like MIUI so all I needed was root.
It is hard to believe that there are actually phones that have no root at all.
Click to expand...
Click to collapse
i miss the Cyanogenmod days
Hey guys,
first time posting here so i dont kow how to style the text, so sorry about that.
last time i rooted a phone was on my sony xperia sp , where all i had to do was to go to towelroot .com and click to root.
I tryed to root my OP6T yesterday, after some setbacks i managed to sucessfully do it.
I did it like this:
1. Downloaded full ROM of OOS 10.3.2,
2. copied the payload to a program called payload dumper that extracted the boot image.
3. Copied the boot image to the phone
4. opened Magisk manager and selected install from source where i chose the boot.img
5. it created a copy called magisk_patched.img
6. booted in fastboot
7. on my pc used the command prompt to "fastboot boot magisk_patched.img"
booted normally and i had root.
but then problem appeared
#Problem 1
everytime i rebooted my phone i would loose root and it would say Magisk not installed. To get it back i would need to perform step 7 again and it was not ideal to do that everytime i turned off my phone.
#Problem 2
While tryng to solve problem 1 i read that i needed to open magisk manager and "Install to Inactive Slot (After OTA)."
After doing that it rebooted but now it wont boot at all, even if i try to "fastboot boot magisk_patched.img" the cmd gives me error:
fastboot boot magisk_patched.img
downloading 'boot.img'...
OKAY [ 0.838s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.845s
now my phone is just sitting there i dont want to reset it again. it would be the 4th time that i need to set up my phone in 2 days, so im trying to see if there are alternatives.
If reset is really the only way, i read that with root you can make a full backup of your phone and then restore it. How to do that? can i do it in the situation im in?
How can i root my OP6T running OOS10.3.2, and keep it? Whats the right method bc the one i followed seemed flawed.
I also tried one that had TWRP but maybe i did something wrong bc it didnt work., also there is no official one working for 10.3.2.
What is happening is normal with those instructions (they aren't right).
All you need to do is install TWRP. Do not use the official one, it is out of date. Use TWRP from this thread Link here. The TWRP from that thread is from the official maintainer. It works fine with OOS 10.
- You need to get the phone in fully working order again. Which may mean you need to use the fastboot ROM, as you've probably "goofed" something up at this point. (no offense meant). Make sure your phone boots and such after this.
- For OOS 10 with the phone in fastboot, fastboot boot recoveryimgfilename.img (<-- For OOS 10 you will need TWRP 3.3.1-32 Q Unofficial by mauronofrio from the thread I linked to above) This will boot to TWRP.
- Now run TWRP 3.3.1-32 Unofficial Installer by mauronofrio this will install TWRP. The installer is the same for Android 9 and 10, doesn't matter.
- Once the installer runs, click back, choose reboot to recovery. If you boot to the system, you have to start over. Reboot to recovery!
- Install Magisk 20.3 <-- The current version. The official download page. After that you can reboot to the system. You should now have a rooted, phone with Magisk, and TWRP installed.
Any questions ask.
OhioYJ said:
What is happening is normal with those instructions (they aren't right).
All you need to do is install TWRP. Do not use the official one, it is out of date. Use TWRP from this thread Link here. The TWRP from that thread is from the official maintainer. It works fine with OOS 10.
- You need to get the phone in fully working order again. Which may mean you need to use the fastboot ROM, as you've probably "goofed" something up at this point. (no offense meant). Make sure your phone boots and such after this.
- For OOS 10 with the phone in fastboot, fastboot boot recoveryimgfilename.img (<-- For OOS 10 you will need TWRP 3.3.1-32 Q Unofficial by mauronofrio from the thread I linked to above) This will boot to TWRP.
- Now run TWRP 3.3.1-32 Unofficial Installer by mauronofrio this will install TWRP. The installer is the same for Android 9 and 10, doesn't matter.
- Once the installer runs, click back, choose reboot to recovery. If you boot to the system, you have to start over. Reboot to recovery!
- Install Magisk 20.3 <-- The current version. The official download page. After that you can reboot to the system. You should now have a rooted, phone with Magisk, and TWRP installed.
Any questions ask.
Click to expand...
Click to collapse
So getting it straight, i need to first reset my phone and then do the steps you described.
Can i backup the data first with TWRP to restore it later and avoid setting up everything again?
Davide1713 said:
So getting it straight, i need to first reset my phone and then do the steps you described.
Can i backup the data first with TWRP to restore it later and avoid setting up everything again?
Click to expand...
Click to collapse
Supposedly. I've never used that function of TWRP. Some people have luck with, some people restore things that shouldn't be restored and end up having to wipe the phone again. Personally I just use TitaniumBackup like I always have. I would search for information on that in the TWRP thread if you want to try method. I don't know enough on that to provide solid information.
OhioYJ said:
Supposedly. I've never used that function of TWRP. Some people have luck with, some people restore things that shouldn't be restored and end up having to wipe the phone again. Personally I just use TitaniumBackup like I always have. I would search for information on that in the TWRP thread if you want to try method. I don't know enough on that to provide solid information.
Click to expand...
Click to collapse
Hey man,
Thank you so much. It worked and i stay rooted even after reboot.
May i ask how you use the Titanium Backup, i think back in the days all i used it for was uninstalling system apps. Or if you know some nice guides. If you know other good things to checkout now that i have root i would appreciate it, i have been far away from rooting for too long.
Once again thank you so much
Davide1713 said:
Hey man,
Thank you so much. It worked and i stay rooted even after reboot.
May i ask how you use the Titanium Backup, i think back in the days all i used it for was uninstalling system apps. Or if you know some nice guides. If you know other good things to checkout now that i have root i would appreciate it, i have been far away from rooting for too long.
Click to expand...
Click to collapse
I use it to back up app and app data primarily. It allows me to restore data to apps after a clean install. Since I have the Pro version it's just a batch action (one click essentially). There is also a way to create a flashable .zip you can use in TWRP, although I haven't tried that method, as I'm typically not restoring apps, just data. I also use it remove apps from time to time.
OhioYJ said:
I use it to back up app and app data primarily. It allows me to restore data to apps after a clean install. Since I have the Pro version it's just a batch action (one click essentially). There is also a way to create a flashable .zip you can use in TWRP, although I haven't tried that method, as I'm typically not restoring apps, just data. I also use it remove apps from time to time.
Click to expand...
Click to collapse
Hey man, im sorry i am once again in need.
Idk why but at first i can reboot the system normally without issues. but after a while once i set up everything it just doesnt boot anymore. Am i missing something? do i have to do anything with magisk? download a module or something?
Could it be that google security update is the fault?
Davide1713 said:
Hey man, im sorry i am once again in need.
Idk why but at first i can reboot the system normally without issues. but after a while once i set up everything it just doesnt boot anymore. Am i missing something? do i have to do anything with magisk? download a module or something?
Could it be that google security update is the fault?
Click to expand...
Click to collapse
When you installed everything originally did you fix everything with a clean install? Both slots are the same version of Android? (Like you don't have something weird going on like Android 9 on one and Android 10 on another?)
You definitely have something abnormal going on. There shouldn't be anything in Magisk that you have to do, at least not to prevent crashing. I normally hide it, but that has to do with keeping apps from detecting root.
OhioYJ said:
When you installed everything originally did you fix everything with a clean install? Both slots are the same version of Android? (Like you don't have something weird going on like Android 9 on one and Android 10 on another?)
You definitely have something abnormal going on. There shouldn't be anything in Magisk that you have to do, at least not to prevent crashing. I normally hide it, but that has to do with keeping apps from detecting root.
Click to expand...
Click to collapse
I got it to boot by uninstalling magisk,
I am 100% sure i dont have two different version of android in different slots, bc yesterday i was in big trouble and nothing was working and i flashed on both slots the same version of android 10(dont remember exactly wich one as i tried a couple, but they were the same).
Today when i couldnt boot anymore i went into stock recovery, factory reset -> when it booted i placed the stockOS.zip file in the phone and applied update from local file -> after that i factory reset again from the system settings, so i think the phone should have installed it properly.
Only after that i did what you told me and installed TWRP and Magisk. and as i said it worked and i could restart my device etc..
After a while when i restarted i couldnt boot anymore and went to bootloader. Removing Magisk fixed it,apperantly on install magisk creates a copy of the boot.img that it restores on uninstall, and i booted to system.
Now i can use my phone but dont have root.
Im very thankful for you being there and helping me out trough this, i cant thank you enough
GuestD2272 said:
I got it to boot by uninstalling magisk,
I am 100% sure i dont have two different version of android in different slots, bc yesterday i was in big trouble and nothing was working and i flashed on both slots the same version of android 10(dont remember exactly wich one as i tried a couple, but they were the same).
Today when i couldnt boot anymore i went into stock recovery, factory reset -> when it booted i placed the stockOS.zip file in the phone and applied update from local file -> after that i factory reset again from the system settings, so i think the phone should have installed it properly.
Only after that i did what you told me and installed TWRP and Magisk. and as i said it worked and i could restart my device etc..
After a while when i restarted i couldnt boot anymore and went to bootloader. Removing Magisk fixed it,apperantly on install magisk creates a copy of the boot.img that it restores on uninstall, and i booted to system.
Now i can use my phone but dont have root.
Im very thankful for you being there and helping me out trough this, i cant thank you enough
Click to expand...
Click to collapse
Not sure if you're still having this issue but I'll post the solution just in case anyone gets stumped, does a google search, and comes across this post. You were using the wrong command.
"fastboot boot" just lets you boot with the img so you can verify that root works.
"fastboot FLASH boot" will flash it and root will stick after reboot.
No need to jump through hoops with TWRP and such.
Hi there,
So I unknowingly did something kinda risky and of course, it backfired. I used the in-system update feature of linage OS to upgrade my version on my Oneplus 6T. Can't exactly remember which one the old version was, but it was at least 4 versions older than the newest nightly one. Afterward, the phone got stuck in a boot loop. Also, in recovery, it can't bind/ mount the system, because there is no file directory. "E:Failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: No such file or directory." I tried the following:
- went into recovery, factory reset the device, then flashed new clean lineage os [multiple different versions]. Gets back to boot loop afterward. (note that Fastboot shows no bootloader version or baseband version)
- tried unlocking the bootloader via fastboot flashing unlock. It fails with error code: (remote: Unrecognized command flashing unlock)
- tried copying the contents of slot a to b, in case one was severely outdated as the cause for the soft brick as stated in this guide. Didn't change mentioned issue after flashing os.
- installed Qualcomm USB drivers, to get the PC to detect the phone as a USB device
- after that, tried using the ms-downloader tool to reset and re-flash the phone. It does not get detected and the downloader tool waits for the full 15s before returning the error for no detected device.
- tried unlocking the bootloader itself via fastboot flashing unlock_critical. same error as with normal unlock: (remote: Unrecognized command flashing unlock)
Maybe overwriting the possibly corrupt bootloader would be a good bet, but as mentioned, I cannot unlock the device to make the command for that useable.
Hey, so I am not really knowledgeable enough to help fix this, but I did notice one thing: Why are you using the wiki page from Lineage for the OnePlus 6 (enchilada) instead of the 6t (fajita)?
state_azure said:
Hey, so I am not really knowledgeable enough to help fix this, but I did notice one thing: Why are you using the wiki page from Lineage for the OnePlus 6 (enchilada) instead of the 6t (fajita)?
Click to expand...
Click to collapse
I didn't even notice it was for enchilada, but iirc the file I loaded was only to copy the contents of slot a to slot b. I could search for a fajita version of this. Still, thanks for your reply.
Hi there,
I have the exact same problem. After updating my OP 6T, the cell phone was broken. It's stuck in a reboot loop. Which surprises me, however, because the documentation for this device type recommends that the update be carried out using the system's internal update process. I also noticed that some OTA updates work and some don't. Unfortunately, this is the only way to make use of it very little fun because you never know if the phone is working again when you update. And the security weaknesses show that updates are also important for Lineageos. thanks for the feedback
Zak0r said:
Hi there,
So I unknowingly did something kinda risky and of course, it backfired. I used the in-system update feature of linage OS to upgrade my version on my Oneplus 6T. Can't exactly remember which one the old version was, but it was at least 4 versions older than the newest nightly one. Afterward, the phone got stuck in a boot loop. Also, in recovery, it can't bind/ mount the system, because there is no file directory. "E:Failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: No such file or directory." I tried the following:
- went into recovery, factory reset the device, then flashed new clean lineage os [multiple different versions]. Gets back to boot loop afterward. (note that Fastboot shows no bootloader version or baseband version)
- tried unlocking the bootloader via fastboot flashing unlock. It fails with error code: (remote: Unrecognized command flashing unlock)
- tried copying the contents of slot a to b, in case one was severely outdated as the cause for the soft brick as stated in this guide. Didn't change mentioned issue after flashing os.
- installed Qualcomm USB drivers, to get the PC to detect the phone as a USB device
- after that, tried using the ms-downloader tool to reset and re-flash the phone. It does not get detected and the downloader tool waits for the full 15s before returning the error for no detected device.
- tried unlocking the bootloader itself via fastboot flashing unlock_critical. same error as with normal unlock: (remote: Unrecognized command flashing unlock)
Maybe overwriting the possibly corrupt bootloader would be a good bet, but as mentioned, I cannot unlock the device to make the command for that useable.
Click to expand...
Click to collapse
Whatever you do in your device,they will not touch critical partition such as bootloader and many more of it, do u still have twrp or other recovery on your device?
Prinçe çharming ap said:
Whatever you do in your device,they will not touch critical partition such as bootloader and many more of it, do u still have twrp or other recovery on your device?
Click to expand...
Click to collapse
I still got the stock recovery. Booting from TWRP image didn't work on my last try, I don't remember the exact specifics anymore. I'll try again.
Zak0r said:
I still got the stock recovery. Booting from TWRP image didn't work on my last try, I don't remember the exact specifics anymore. I'll try again.
Click to expand...
Click to collapse
Zak0r said:
I still got the stock recovery. Booting from TWRP image didn't work on my last try, I don't remember the exact specifics anymore. I'll try again.
Click to expand...
Click to collapse
Tell me the exact problem you with your phone and maybe i can help
once again,
today got informed via updater that a new update is available. I try do install it, but now i stuck again in recovery. And the only think i can do is a factory reset and everything is lost.
can anybody give an info if it is safe to update the 6T trough OTA? It doesn't look like that.
zero4one said:
once again,
today got informed via updater that a new update is available. I try do install it, but now i stuck again in recovery. And the only think i can do is a factory reset and everything is lost.
can anybody give an info if it is safe to update the 6T trough OTA? It doesn't look like that.
Click to expand...
Click to collapse
Oof, I thought mine only got bricked because I tried to upgrade across 4 versions. It seems as though even normal updates now cause soft bricks, neat.
I tried again today but there seems to be a connection to the error. I had an update pending, which could be installed without any problems. After the restart, I was informed that there was another update, after installing this update there was a total failure again. Could it be that this is somehow related to slot A / B?
zero4one said:
I tried again today but there seems to be a connection to the error. I had an update pending, which could be installed without any problems. After the restart, I was informed that there was another update, after installing this update there was a total failure again. Could it be that this is somehow related to slot A / B?
Click to expand...
Click to collapse
Why don't you try to flash Stock rom on both slots via MSM tool and then just try ota to update to latest build for you specific device
How can i verify if there is an difference between slot a and slot b?
If i flash the stock rom i will be back on oos and that is not what i want i will continue using los, or do we have an idea missmatch there?
thanks for help
zero4one said:
How can i verify if there is an difference between slot a and slot b?
If i flash the stock rom i will be back on oos and that is not what i want i will continue using los, or do we have an idea missmatch there?
thanks for help
Click to expand...
Click to collapse
What do you exactly want ?