Omg, I've been messing with this thing for 2 months trying to fix it, all because I didn't take a backup of my /persist as soon as I got the phone, but there is a way to fix it!!! The only pre-requisites are that:
A) you still have your own /persist (that came with your specific phone, didn't overwrite it with one from the forums and didn't save your original somewhere) AND
B) all sensors still work (only the fingerprint scanner is broken) AND
C) that you have NEVER ran the hidden fingerprint calibration tools accessible from *#808# (unless you have a backup of /persist from before you did that)
Follow these simple instructions and enjoy:
https://forum.xda-developers.com/oneplus-8/how-to/guide-fix-persist-img-loss-finger-print-t4126455
You can ignore the entire part about having to run the MSM tool to roll back to a previous version of OOS (Step 2). Therefore, no data is lost, no factory reset is required, etc.
Also in very first part of Step 4, you need to dial *#808#, not *#801#
It took me less than 15 minutes and now it's good as new!!! Please give the OP thanks! He spent almost 200 hours figuring this out (and I don't doubt it; I must have spent easily over 20 hours myself and didn't get anywhere...). All I did was find his genius instructions and post them here.
Edit: And to add one last step to the guide, after you finish and get the fp scanner working again, please be sure to take a backup of your now fixed persist partition and store it in at least two different locations. Because if you are reading this, you are most likely modding your phone with at least Magisk (why else unlock the bootloader? and almost anything can cause persist to be corrupted. For me, it was simply installing a bad build of magisk canary back in May that did it. It's not just important for those installing aftermarket ROMs. It's vital for anyone who even thinks about unlocking the bootloader on this device. Because even the act of relocking the bootloader has caused persist to be corrupted for some...
Edit2: If you run the MSM tool after fixing persist, or manually relock the bootloader, you'll wind up with your FP being broken again. I'm assuming because the checksum of the "fixed" persist doesn't match that of the original, unmodified persist, so it gets marked as corrupt again. So you'll need to unlock the bootloader and restore/flash your backed up, fixed persist (you did back it up this time, right? Impossible to run msm tool to get back to stock AND have FP working. Bootloader must be unlocked after using msm tool and fixed persist restored.
please help HD9010 indian firmware currently..before i had global
i messed up my persist too while reverting back from open beta to stable via fastboot
now fingerprint enrollment error
i tried the guide but its not the same with 7tpro
there wasnt 'gf_persist.so' in data folder of my extracted persist.img
and calibrating was confusing for me but i did it upro my limit but i didnt have those many reds as the original OP had in his guide video while calibrating the fp
so please can you be kind enough to share your whole process that you used to manage the fingerprint error issue?
like what roms you used before and after or during fix?
and lastly, since the backedup persist didnt work i deleted and again backedup the persist in next attempt so it means my fingerprint is gone permanently? maybe?
please help me..ive spent my whole night and day searching and trying workarounds flashing roms back and forth
the hellboy said:
i messed up my persist too while reverting back from open beta to stable via fastboot
now fingerprint enrollment error
i tried the guide but its not the same with 7tpro
there wasnt 'gf_persist.so' in data folder of my extracted persist.img
and calibrating was confusing for me but i did it upro my limit but i didnt have those many reds as the original OP had in his guide video while calibrating the fp
so please can you be kind enough to share your whole process that you used to manage the fingerprint error issue?
like what roms you used before and after or during fix?
and lastly, since the backedup persist didnt work i deleted and again backedup the persist in next attempt so it means my fingerprint is gone permanently? maybe?
please help me..ive spent my whole night and day searching and trying workarounds flashing roms back and forth
Click to expand...
Click to collapse
I used his exact instructions on my 7T Pro 5G McLaren edition from T-Mobile. With a few helpful tips I added. You must have the global version of the 7T Pro McLaren since you are talking about open beta and stable releases. Unfortunately I can't help you there. It seems that the TMobile 7T Pro 5G McLaren is much more similar to the OP8 in some ways than the global 7T Pro, especially when it comes to OOS, partitioning, extra security crap, etc.
Edit:. You are in the wrong forum. You don't even have the global 7T Pro McLaren. You have the HD1910 Global (originally Chinese version) 7T Pro. Wrong forum. The 7T Pros didn't even have this issue (or if they did, it was no where near as widespread, I've never even seen it mentioned a single time). To the best of my knowledge, it began with the 7T Pro 5G McLaren from T-Mobile which was the newest phone released by 1+ until the OP8.
And if you deleted your backup of your original persist after trying to fix it unsuccessfully, it's now broken forever regardless. You need to RMA.
Late response, but this worked 100% for me after switching back to stock from AOSiP.
Thank you!
derget1212 said:
Late response, but this worked 100% for me after switching back to stock from AOSiP.
Thank you!
Click to expand...
Click to collapse
Glad to hear it worked!
One important thing to add:
If you run the MSM tool after fixing persist, or manually relock the bootloader, you'll wind up with your FP being broken again. I'm assuming because the checksum of the "fixed" persist doesn't match that of the original, unmodified persist, so it gets marked as corrupt again. So you'll need to unlock the bootloader and restore/flash your backed up, fixed persist (you did back it up, right? . Impossible to run msm tool to get back to stock AND have FP working. Bootloader must be unlocked after using msm tool and fixed persist restored.
starcms said:
Glad to hear it worked!
One important thing to add:
If you run the MSM tool after fixing persist, or manually relock the bootloader, you'll wind up with your FP being broken again. I'm assuming because the checksum of the "fixed" persist doesn't match that of the original, unmodified persist, so it gets marked as corrupt again. So you'll need to unlock the bootloader and restore/flash your backed up, fixed persist (you did back it up, right? . Impossible to run msm tool to get back to stock AND have FP working. Bootloader must be unlocked after using msm tool and fixed persist restored.
Click to expand...
Click to collapse
in the guide it tells you to get your phone into factory mode but does not tell you to take it out of factory mode. of you turn factory mode off and use the msm tool will fingerprint still work afterwords
cgrimm9 said:
in the guide it tells you to get your phone into factory mode but does not tell you to take it out of factory mode. of you turn factory mode off and use the msm tool will fingerprint still work afterwords
Click to expand...
Click to collapse
Apparently you need to reread the instructions
I did step three says.
3. Next step is to unlock the built in 'Factory Mode' I have a guide on how to do this below.
https://forum.xda-developers.com/oneplus-8-pro/how-to/guide-unlock-factory-mode-root-t4118527
No where on this instructions says to relock the factory mode. I am just asking if you where to do that will fingerprint scanner work after doing msm tool.
I did the process 2 times now. Have no interest in doing it again unless I need to update. I just putting some thought in why I don't know if it's relavent or not just asking. sometimes a difficult problem can have a easy solution just got to figure it out
cgrimm9 said:
I did step three says.
3. Next step is to unlock the built in 'Factory Mode' I have a guide on how to do this below.
https://forum.xda-developers.com/oneplus-8-pro/how-to/guide-unlock-factory-mode-root-t4118527
No where on this instructions says to relock the factory mode. I am just asking if you where to do that will fingerprint scanner work after doing msm tool.
I did the process 2 times now. Have no interest in doing it again unless I need to update. I just putting some thought in why I don't know if it's relavent or not just asking. sometimes a difficult problem can have a easy solution just got to figure it out
Click to expand...
Click to collapse
Yes, you can relock factory mode when done. Just re-edit those 2 lines. And once you have your FP working again, please be sure to make a backup of your fixed persist.img. Then you'll never have to do all the steps again. Simply restore your fixed persist.img if FP ever breaks again.
starcms said:
Omg, I've been messing with this thing for 2 months trying to fix it, all because I didn't take a backup of my /persist as soon as I got the phone, but there is a way to fix it!!! The only pre-requisites are that:
A) you still have your own /persist (that came with your specific phone, didn't overwrite it with one from the forums and didn't save your original somewhere) AND
B) all sensors still work (only the fingerprint scanner is broken) AND
C) that you have NEVER ran the hidden fingerprint calibration tools accessible from *#808# (unless you have a backup of /persist from before you did that)
Follow these simple instructions and enjoy:
https://forum.xda-developers.com/oneplus-8/how-to/guide-fix-persist-img-loss-finger-print-t4126455
You can ignore the entire part about having to run the MSM tool to roll back to a previous version of OOS (Step 2). Therefore, no data is lost, no factory reset is required, etc.
Also in very first part of Step 4, you need to dial *#808#, not *#801#
It took me less than 15 minutes and now it's good as new!!! Please give the OP thanks! He spent almost 200 hours figuring this out (and I don't doubt it; I must have spent easily over 20 hours myself and didn't get anywhere...). All I did was find his genius instructions and post them here.
Edit: And to add one last step to the guide, after you finish and get the fp scanner working again, please be sure to take a backup of your now fixed persist partition and store it in at least two different locations. Because if you are reading this, you are most likely modding your phone with at least Magisk (why else unlock the bootloader? and almost anything can cause persist to be corrupted. For me, it was simply installing a bad build of magisk canary back in May that did it. It's not just important for those installing aftermarket ROMs. It's vital for anyone who even thinks about unlocking the bootloader on this device. Because even the act of relocking the bootloader has caused persist to be corrupted for some...
Edit2: If you run the MSM tool after fixing persist, or manually relock the bootloader, you'll wind up with your FP being broken again. I'm assuming because the checksum of the "fixed" persist doesn't match that of the original, unmodified persist, so it gets marked as corrupt again. So you'll need to unlock the bootloader and restore/flash your backed up, fixed persist (you did back it up this time, right? Impossible to run msm tool to get back to stock AND have FP working. Bootloader must be unlocked after using msm tool and fixed persist restored.
Click to expand...
Click to collapse
yep. same here spent so much time on it. Then me and that dev crossed paths. i told him what i found and he told me what he found and together it birthed that hack
fp also works in custom roms now
So this fixed my issue with registering my fingerprints, but even after registering 5 prints, when I go to unlock my phone or anything that uses my prints scanning fails like 90% of the time. I have to press really hard or just put in my pin to get my phone to unlock. I removed my screen protector and cleaned my screen. Is there a way to recalibrate the scanner?
Trevaryn said:
So this fixed my issue with registering my fingerprints, but even after registering 5 prints, when I go to unlock my phone or anything that uses my prints scanning fails like 90% of the time. I have to press really hard or just put in my pin to get my phone to unlock. I removed my screen protector and cleaned my screen. Is there a way to recalibrate the scanner?
Click to expand...
Click to collapse
Program each finger twice. Also, it'll get much, much, much better with time as it autocalibrates/learns over a week or so.
I don't quite follow step 5 in the guide:
5. We need to extract the the old broken persist.img. The way I did this is by opening it extracting it via 7-ZIP on my PC
Click to expand...
Click to collapse
Also, do you run the steps after flashing a custom ROM?
pgg285 said:
I don't quite follow step 5 in the guide:
Also, do you run the steps after flashing a custom ROM?
Click to expand...
Click to collapse
For step 5, just extract it as if it was a zip file on your PC.
After fixing persist and getting FP working, make sure you make a backup of the fixed persist.img and save it in at least 2 or 3 different places to be safe. Occasionally for custom ROMs, to get the FP working after flashing ROM, take your fixed persist, go to fastboot, and do "fastboot flash persist your_backed_up_fixed_persist.img"
i just wanted to say that for some weird or maybe lucky reason, i did not have to reflash my backed up persist after using the msm to get back to stock from the aosip custom rom. I used the bootloader unlock trick through modded msm to install the rom and i went back using msm and fingerprint worked on the get go. I did not have to unlock bootloader and reflash persist.img .. not sure why i didnt have to its weird ( i never flashed my persist at all, even after installing the custom rom)
i think i lost my fingerprint forever because i have never done any backup and i flashed custom rom so RIP my fingerprint.
Would it make a difference if i dont lock factory mode or leave it unlocked?
AssyrianHero said:
i think i lost my fingerprint forever because i have never done any backup and i flashed custom rom so RIP my fingerprint.
Click to expand...
Click to collapse
That's exactly what these instructions are meant to fix...
the hellboy said:
please help HD9010 indian firmware currently..before i had global
i messed up my persist too while reverting back from open beta to stable via fastboot
now fingerprint enrollment error
i tried the guide but its not the same with 7tpro
there wasnt 'gf_persist.so' in data folder of my extracted persist.img
and calibrating was confusing for me but i did it upro my limit but i didnt have those many reds as the original OP had in his guide video while calibrating the fp
so please can you be kind enough to share your whole process that you used to manage the fingerprint error issue?
like what roms you used before and after or during fix?
and lastly, since the backedup persist didnt work i deleted and again backedup the persist in next attempt so it means my fingerprint is gone permanently? maybe?
please help me..ive spent my whole night and day searching and trying workarounds flashing roms back and forth
Click to expand...
Click to collapse
Brother i am suffering the same problem with same device OP 7T PRO, Did you managed to solve the problem? It will be a great help if you tell me
My mail id - [email protected]
the hellboy said:
please help HD9010 indian firmware currently..before i had global
i messed up my persist too while reverting back from open beta to stable via fastboot
now fingerprint enrollment error
i tried the guide but its not the same with 7tpro
there wasnt 'gf_persist.so' in data folder of my extracted persist.img
and calibrating was confusing for me but i did it upro my limit but i didnt have those many reds as the original OP had in his guide video while calibrating the fp
so please can you be kind enough to share your whole process that you used to manage the fingerprint error issue?
like what roms you used before and after or during fix?
and lastly, since the backedup persist didnt work i deleted and again backedup the persist in next attempt so it means my fingerprint is gone permanently? maybe?
please help me..ive spent my whole night and day searching and trying workarounds flashing roms back and forth
Click to expand...
Click to collapse
The instructions only work for the T-Mobile 7T Pro 5G Mclaren edition, all OP8, all OP8 pro, no idea about OP8T. That's because this was the first device that OnePlus used a different format for persist. That's confirmed by you not having gf_persist.so.
You would need to look at the forums for the OnePlus 7T Pro for a possible answer: https://forum.xda-developers.com/c/oneplus-7t-pro.9327/ The forums you are in now are ONLY for the HD1925, the T-Mobile branded 7T Pro 5G Mclaren variant.
And lastly, if you deleted your original persist.img (the one with broken fp), which it sounds like you did, and then wiped persist again afterwards, then there is absolutely no hope of fixing it besides sending it to OnePlus. Because you've lost your entire original persist if that is the case, unless you still have a backup of original persist.img with broken fp from before you tried fixing it.
Related
Hello everybody.
I have a simple Question about root on this model, is it possible to do?
And if it is possible, tell me how Please.
Best regards
Wojtek
I am looking for the same too
Me too... Looks like it is still impossible
Only paid method and who knows it will be work on my p30 lite......hmm
Hello ppl,
I know this might be a little old.. any way just for the knowledge lets bring this thread back.
I had the same concern for a while, and kind of eager to get mine rooted.. until now.
I managed to unlock mine, and root it succesfully. Latest version of magisk, safty net passed, root essentials running like a charm, I can ADB in to it and su yey!
How? main issue here is my p30 lite MAR-LX3A was already in emui10, and somehow this little sucker wont allow the unlock of the bootloader regardless. I used a unlock tool that is advised to work for this model using testpoint short. how ever it was not working for me, until I read the EMUI had to be downgraded to 9.1.
Once runnig EMUI9.1 I didnt had to re-run the tool it was already unlocked. weird.
Any how the unlocker tool I used was not the ABD/fastboot tools, it was a paid app in case you are still interested in getting it done I can tell you how. Just keep in mind you will need to Open the back cover of the device.
Think is there is no custom recovery image available that works, neither a custom ROM, so all you have is pretty much root access.
I beleive this to be a pretty decent phone so I dont want just to ditch it, I am working to get a TWRP image, if I a managed to so I will get a ROM done as well. Think the whole device has been off the track for dedicated modders and devs, so it has just not been worked on.
which me luck. I'll keep you posted
I used an unlock bootloader service for 15$. First i had to downgrade my emui from 10 to 9.
I can run magisk without problem. My only problem is that i wan't super su. I was able to flash TWRP Recovery 3.2.1.0 (HiSilicon Kirin 710). But i couldn't use it because the folder are encrypted. So if anyone has any idea how to decrypt this let me know
aka_max said:
I used an unlock bootloader service for 15$. First i had to downgrade my emui from 10 to 9.
I can run magisk without problem. My only problem is that i wan't super su. I was able to flash TWRP Recovery 3.2.1.0 (HiSilicon Kirin 710). But i couldn't use it because the folder are encrypted. So if anyone has any idea how to decrypt this let me know
Click to expand...
Click to collapse
I'm gonna look for that TWRP img, I didnt find a working one acutally. is there a specific reason why you rather use super su ?
about encryption you usually need to make sure there is no password configured, I read somewhere about a guy that had his Face recognition still configured, and that was the reason he was unable to unencrypt. there are some zips you can flash somwhere around, but never tried them
blzbh said:
I'm gonna look for that TWRP img, I didnt find a working one acutally. is there a specific reason why you rather use super su ?
about encryption you usually need to make sure there is no password configured, I read somewhere about a guy that had his Face recognition still configured, and that was the reason he was unable to unencrypt. there are some zips you can flash somwhere around, but never tried them
Click to expand...
Click to collapse
I deactivated all passwords etc. But it didn't work for me. The only reason i need supersu is because i wan't recover some deleted contacts and mails after factory reset. And those Windows applications with real deep scan not works with magisk.
aka_max said:
I deactivated all passwords etc. But it didn't work for me. The only reason i need supersu is because i wan't recover some deleted contacts and mails after factory reset. And those Windows applications with real deep scan not works with magisk.
Click to expand...
Click to collapse
why dont you try getting an image of the partition with DD, convert it and mount it in the PC directly, I beleive using the scan software directly against the phone is more complicated than just scanning a directly attached block device.
Hello
Is there any way to decrypt the Huawei P30 Lite?I haven't found anything anywhere.
i have twrp on it but the system is encrypted :-(
i have read some posts about wipe data.. use stock rom etc... But i am to lazy to test it. Let me know if it will works. Be sure to make a backup before playing around
nominator64 said:
Hello
Is there any way to decrypt the Huawei P30 Lite?I haven't found anything anywhere.
i have twrp on it but the system is encrypted :-(
Click to expand...
Click to collapse
there are a few things to try... you can go to wipe menu in TWRP then use the fix/repair option against the system encrypted partition..
-try reparing it
-try changing the partition from ext4 (check first the type usually ext4) to ext2, then change it back to what it was, ext4
last resource:
-wipe all data/factory reset ***** You WILL loose all your personal data if you do this **** just make a backup MANUALLY before doing this.. if you use TWP backup pbby your back will be encrypted too...
I manage to get mine unencrypted with this last step, took a few attempts, but had to reflash Stock so its back to encryption
Maybe we should create our own TWRP version for the p30 lite. There are many tutorials ^^
aka_max said:
Maybe we should create our own TWRP version for the p30 lite. There are many tutorials ^^
Click to expand...
Click to collapse
agreed I have been working on one that truely works, but there are a few blanks about how TWRP really works.. and its boot process. I have learned a little this past week, but still think gonna have to reverse engineer a working img to get some answers.... I was actually thinking on building a orange fox image better not sure what would be easier..
I have lots of work so I do this in my free time, but let me know if you want a help perhaps we can get something and port a nice ROM that's worth the device
.
blzbh said:
there are a few things to try... you can go to wipe menu in TWRP then use the fix/repair option against the system encrypted partition..
-try reparing it
-try changing the partition from ext4 (check first the type usually ext4) to ext2, then change it back to what it was, ext4
last resource:
-wipe all data/factory reset ***** You WILL loose all your personal data if you do this **** just make a backup MANUALLY before doing this.. if you use TWP backup pbby your back will be encrypted too...
I manage to get mine unencrypted with this last step, took a few attempts, but had to reflash Stock so its back to encryption
Click to expand...
Click to collapse
thank you for the suggestions. unfortunately does not work :-(
Please keep us posted, really excited to see a custom rom for this phone, also could you elaborate on the process of unlocking the bootloader? My back cover is already broken so I have to open it up anyways
k.r.o.o.k said:
Please keep us posted, really excited to see a custom rom for this phone, also could you elaborate on the process of unlocking the bootloader? My back cover is already broken so I have to open it up anyways
Click to expand...
Click to collapse
Sure, ive been busy but will try my best.. about the unlock process I end up paying 19 euros... But try using fastboot unlock first.. may save you the money not sure...
1. Downgrade to emui 9.1 .. just plug the p30 lite to PC, install hsuite... Go for the firmware/software update... A pop up screen will show up with some small letters buttom rigth.. older releases or revert to older firmware something like that.. you will get too choose 9.1 only ... Choose that and apply.. Keep an eye out.. this will delete everything in your phone... Next boot you will be in 9.1.. avoid the automatic upgrade.
2. Turn the phone off, take the back cover and locate the testpoints.. short by using metal wire... The small aluminium wire wraps that come with bread and other bags for easy close are usefull just remove some plastic in each side... connect the usb cable to PC.. leave the phone side unplugged.. Touch test point with the wire while the other side touches a metal cover in the phone.. while doing it plug the phone to the USB cable.. the charging animation should not appear . . . Screen must stay black.. otherwise do it again.. if done right the device manager will detect COM port for your device
Identify the point with this video
3. use either app you want to detect testpoint mode and unlock... I managed to do it with a 3 day unlimited license for HCU client.. that did the trick their website have some tutorials easy to follow.
Hi all,
I have the same problem like a few other people. I unlocked the phone with HCU, and after I tried to root with magisk (by trwp) But the main issue, the phone is encrypted and the installation proccess of the magisk by the trwp got failed. How can I root this phone? Anybode has success with this?
Thank you!
huawei p30 lite device root support please
Hi to all, I wrote here after trying everything from a long time. I explain better :
Sometimes, randomly, my phone mess up with the various application and give me some heavy lag and freeze, he remove some of my personal data (sometimes whatsapp files, sometimes other files, randomly) after that it stuck with a black screen or some similar and if I try to restart he stuck at the boot logo. The first time that this happened I spent a lot of time for understand what was to do this problem and after some trying I noted that this problem coincided with an error in twrp about the "persist partition" (something like unable to mount or read persist partition). So searching around the various forum I understand that I have to flash a "partition.img" for resolve the problem and that is what I do. It apparently solved the problem but my phone continue randomly to make this problem, It seems that the more time passes, the more often it will do this problem. I read that can be a memory chip problem and than the only solution is to send to the assistance and make them to resolve this. Someone of you have the same problem ? And how you managed to solve this ?
aSaro12 said:
Hi to all, I wrote here after trying everything from a long time. I explain better :
Sometimes, randomly, my phone mess up with the various application and give me some heavy lag and freeze, he remove some of my personal data (sometimes whatsapp files, sometimes other files, randomly) after that it stuck with a black screen or some similar and if I try to restart he stuck at the boot logo. The first time that this happened I spent a lot of time for understand what was to do this problem and after some trying I noted that this problem coincided with an error in twrp about the "persist partition" (something like unable to mount or read persist partition). So searching around the various forum I understand that I have to flash a "partition.img" for resolve the problem and that is what I do. It apparently solved the problem but my phone continue randomly to make this problem, It seems that the more time passes, the more often it will do this problem. I read that can be a memory chip problem and than the only solution is to send to the assistance and make them to resolve this. Someone of you have the same problem ? And how you managed to solve this ?
Click to expand...
Click to collapse
Resolving Persist Issues
I have through instructions within these 2 posts, I have experienced this issue and have assisted numerous people with persist issues on XDA these solutions work.
https://forum.xda-developers.com/showpost.php?p=80544709&postcount=21
https://forum.xda-developers.com/showpost.php?p=80394181&postcount=15
your problem is similar to k20 pro problem that i had as well as so many other users.
looks like you did install FDE through magisk and it messed up your phone perminently
we've been trying to figure out a fix for the lag and freeze and wiping of the memory but its been almost 3 months without any fix.
so most likely it is unfixable
don't try to mess up anything and just send your phone to service center they will replace the motherboard . its the only available fix at the moment
I got this problem sometime when using MIUI 10, I didn't see that issue for 2 weeks after updated to MIUI 11.
Persist Issue Solution
sar78mad said:
your problem is similar to k20 pro problem that i had as well as so many other users.
looks like you did install FDE through magisk and it messed up your phone permanently
we've been trying to figure out a fix for the lag and freeze and wiping of the memory but its been almost 3 months without any fix.
so most likely it is unfixable
don't try to mess up anything and just send your phone to service center they will replace the motherboard . its the only available fix at the moment
Click to expand...
Click to collapse
It's not unfixable, it can be resolved by at least 4 different methods.
I have explained how to permanently resolve this issue with extensive instructions on at least 20 to 30 threads. Including the one above. And here: https://forum.xda-developers.com/showpost.php?p=79824537&postcount=2
As you can see, wasted time with no thanks given.
This issue is cause by encryption, that all there is no damage whatsoever. If you saved a Twrp backup the issue can be resolved in 2 seconds by restoring persist images.
It can also be resolved by flashing persist images from a dipper images rom, then immediately signing into your MiCloud account or by flashing a fastboot rom with XiaoMiFlash ( making sure to unclick relock bootloader) then boot and sign into MiCloud.
Another way is download all the required Dipper images Rom here :
Fastboot Rom Link : dipper_global_images_9.6.27_20190627.0000.00_9.0_global_30e0fc22ef.tgz
Filesize 2.43G
Download and unpack rom from the link above , as I mentioned on the link above, unpack twice to the desktop, ( the first time decompresses into a larger rom that also needs unpacking)
Open extracted images folder and look for “persist.img” file (it should be located in “Image” folder , see my attached screen, I keep these ready if ever needed).
Copy “persist.img” file to “/sdcard/persist.img”.
Boot into TWRP, go to Advanced/Terminal
In the terminal type the following command to convert the .img file from “sparse” to “raw” format.
PHP:
simg2img /sdcard/persist.img /sdcard/persist_EXT4.img
After it’s completed, type the following command in the terminal:
PHP:
dd if=/sdcard/persist_EXT4.img of=/dev/block/bootdevice/by-name/persist
After the flashing is completed, you can reboot into the system and start using your phone.
The next method is posted above, its an older method that uses the Kitchen app
Ideally you want the base firmware to be the same as the rom. but its not absolutely necessary, once you have flashed the persist image, immediately install a Miui Rom and sign into your account, once you are on the main desktop, reboot to Twrp and make a full backup, then copy it to your PC.
Make sure that the backup includes the persist images, modem, efs etc. As I said a full backup.
This backup will give you the peace of mind knowing, that you will never need to repeat the steps above again.
tsongming said:
Resolving Persist Issues
I have through instructions within these 2 posts, I have experienced this issue and have assisted numerous people with persist issues on XDA these solutions work.
https://forum.xda-developers.com/showpost.php?p=80544709&postcount=21
https://forum.xda-developers.com/showpost.php?p=80394181&postcount=15
Click to expand...
Click to collapse
I've seen many Xiaomi EU users facing this problem. Do you know why? After they fix persist partion, it doesn't stay for long. After few days, it again gets deleted.
alone_in_dark said:
I've seen many Xiaomi EU users facing this problem. Do you know why? After they fix persist partion, it doesn't stay for long. After few days, it again gets deleted.
Click to expand...
Click to collapse
I think it's related to dm-verity and magisk updates. I plan to make a post about it after I have researched it further and can provide sourced proof.
tsongming said:
I think it's related to dm-verity and magisk updates. I plan to make a post about it after I have researched it further and can provide sourced proof.
Click to expand...
Click to collapse
Well there are around 60 k20 pro users who got their phones useless after installing an old version of FDE (a magisk module), and no , just flashing persist wont fix the problem, so feel free to try to help us find a fix by joining to our telegram group and im sure that all 60 users will donate you alot of money if you find a permanent fix
link to telegram group : https://t.me/whateverk20pro
aSaro12 said:
Hi to all, I wrote here after trying everything from a long time. I explain better :
Sometimes, randomly, my phone mess up with the various application and give me some heavy lag and freeze, he remove some of my personal data (sometimes whatsapp files, sometimes other files, randomly) after that it stuck with a black screen or some similar and if I try to restart he stuck at the boot logo. The first time that this happened I spent a lot of time for understand what was to do this problem and after some trying I noted that this problem coincided with an error in twrp about the "persist partition" (something like unable to mount or read persist partition). So searching around the various forum I understand that I have to flash a "partition.img" for resolve the problem and that is what I do. It apparently solved the problem but my phone continue randomly to make this problem, It seems that the more time passes, the more often it will do this problem. I read that can be a memory chip problem and than the only solution is to send to the assistance and make them to resolve this. Someone of you have the same problem ? And how you managed to solve this ?
Click to expand...
Click to collapse
You speak me from the soul. I had this problem also already 3-4 times and it is 1:1 the same procedure that happens for me too. I have no clue what it is. My /data Partition does get ****ed up sometimes too
---------- Post added at 10:59 PM ---------- Previous post was at 10:53 PM ----------
tsongming said:
It's not unfixable, it can be resolved by at least 4 different methods.
I have explained how to permanently resolve this issue with extensive instructions on at least 20 to 30 threads. Including the one above. And here: https://forum.xda-developers.com/showpost.php?p=79824537&postcount=2
As you can see, wasted time with no thanks given.
This issue is cause by encryption, that all there is no damage whatsoever. If you saved a Twrp backup the issue can be resolved in 2 seconds by restoring persist images.
It can also be resolved by flashing persist images from a dipper images rom, then immediately signing into your MiCloud account or by flashing a fastboot rom with XiaoMiFlash ( making sure to unclick relock bootloader) then boot and sign into MiCloud.
Another way is download all the required Dipper images Rom here :
Fastboot Rom Link : dipper_global_images_9.6.27_20190627.0000.00_9.0_global_30e0fc22ef.tgz
Filesize 2.43G
Download and unpack rom from the link above , as I mentioned on the link above, unpack twice to the desktop, ( the first time decompresses into a larger rom that also needs unpacking)
Open extracted images folder and look for “persist.img” file (it should be located in “Image” folder , see my attached screen, I keep these ready if ever needed).
Copy “persist.img” file to “/sdcard/persist.img”.
Boot into TWRP, go to Advanced/Terminal
In the terminal type the following command to convert the .img file from “sparse” to “raw” format.
PHP:
simg2img /sdcard/persist.img /sdcard/persist_EXT4.img
After it’s completed, type the following command in the terminal:
PHP:
dd if=/sdcard/persist_EXT4.img of=/dev/block/bootdevice/by-name/persist
After the flashing is completed, you can reboot into the system and start using your phone.
The next method is posted above, its an older method that uses the Kitchen app
Ideally you want the base firmware to be the same as the rom. but its not absolutely necessary, once you have flashed the persist image, immediately install a Miui Rom and sign into your account, once you are on the main desktop, reboot to Twrp and make a full backup, then copy it to your PC.
Make sure that the backup includes the persist images, modem, efs etc. As I said a full backup.
This backup will give you the peace of mind knowing, that you will never need to repeat the steps above again.
Click to expand...
Click to collapse
That it is a encryption problem, i thought already before. Are you sure that signing into MiCloud fixes this problem? it can be ofc that xiaomi added such a system, but I have no clue.
NightScap3 said:
You speak me from the soul. I had this problem also already 3-4 times and it is 1:1 the same procedure that happens for me too. I have no clue what it is. My /data Partition does get ****ed up sometimes too
---------- Post added at 10:59 PM ---------- Previous post was at 10:53 PM ----------
That it is a encryption problem, i thought already before. Are you sure that signing into MiCloud fixes this problem? it can be ofc that xiaomi added such a system, but I have no clue.
Click to expand...
Click to collapse
Signing in does fix it.....sometimes,
Other times the solution is the adb fix, which usually always works.
However, the easiest fix of all, is restoring persist from a Twrp backup, But it has to be your persist backup, flashing someone else's apparently makes matters worse.
sar78mad said:
Well there are around 60 k20 pro users who got their phones useless after installing an old version of FDE (a magisk module), and no , just flashing persist wont fix the problem, so feel free to try to help us find a fix by joining to our telegram group and im sure that all 60 users will donate you alot of money if you find a permanent fix
link to telegram group : https://t.me/whateverk20pro
Click to expand...
Click to collapse
I have had this issue myself several times and you are right simply flashing persist doesn't always fix it.
However, I made a post with additional options here : https://forum.xda-developers.com/showpost.php?p=80623541&postcount=5.
I just mentioned this to someone else, do not flash someone else's persist backup, that will work temporarily and then makes matter's much worse.
On the Mi8 there are only a few versions of Twrp that will allow you to backup and restore that persist image alone. If Orange Fox is available on your device try using it. See attached image
Edit one last thing
If attempting to use the persist image extraction reflash method, the image must come from a fastboot "images' rom
tsongming said:
I have had this issue myself several times and you are right simply flashing persist doesn't always fix it.
However, I made a post with additional options here : https://forum.xda-developers.com/showpost.php?p=80623541&postcount=5.
I just mentioned this to someone else, do not flash someone else's persist backup, that will work temporarily and then makes matter's much worse.
On the Mi8 there are only a few versions of Twrp that will allow you to backup and restore that persist image alone. If Orange Fox is available on your device try using it. See attached image
Click to expand...
Click to collapse
My MI 8 works since 2 days without a Problem after flashing the persist.img that i extracted from the factory image in Orange Fox terminal like explained in your posts.
Duplicate Post
---------- Post added at 02:18 AM ---------- Previous post was at 01:59 AM ----------
apf95 said:
My MI 8 works since 2 days without a Problem after flashing the persist.img that i extracted from the factory image in Orange Fox terminal like explained in your posts.
Click to expand...
Click to collapse
Yes, those steps definitely work for those of us.with Mi8's
It should work for them too as long as the use the correct images.
tsongming said:
I have had this issue myself several times and you are right simply flashing persist doesn't always fix it.
Click to expand...
Click to collapse
Did you have this problem before using Xiaomi EU rom? I am on stock rom and planning to go to EU. But a lot of users in EU forum are also facing persist problem. I am using Mi 8 for almost 1 year with Global Beta/Stable rom. Nevar faced this issue.
Maybe it's caused by TWRP or EU rom?
alone_in_dark said:
Did you have this problem before using Xiaomi EU rom? I am on stock rom and planning to go to EU. But a lot of users in EU forum are also facing persist problem. I am using Mi 8 for almost 1 year with Global Beta/Stable rom. Nevar faced this issue.
Maybe it's caused by TWRP or EU rom?
Click to expand...
Click to collapse
It's not caused by the EU rom, the EU rom is really nothing more than official Beta Miui ( Chinese version, which is 3 to 4 months ahead of the Global version) So beta Miui with Google services added and useless bloatware and ads removed.
There have been many cases of people experiencing these issues on AOSP roms as well. For example, the many reports of WIFI, Data, Cellular Services, BT not working etc.
The issue is a permissions conflict, that is mostly likely caused by continuous flashing of Root and Dm-Verity. Albeit incorrectly.
If you have Twrp and no root then flash Dm-Verity. If you plan on using Root then don't use DM-Verity, it's not needed.
When I stopped flashing DM-Verity is when I stopped experiencing issues. But as I mentioned if you don't want root ,and you definitely want TWRP then you must flash DM-Verity otherwise TWRP will be overwritten when using a stock based rom.
@alone_in_dark
Edit: If you have been using stock the whole time, you will be blown away with how improved the latest Android 10 of Miui 11 is, check it out, its awesome.
tsongming said:
Signing in does fix it.....sometimes,
Other times the solution is the adb fix, which usually always works.
However, the easiest fix of all, is restoring persist from a Twrp backup, But it has to be your persist backup, flashing someone else's apparently makes matters worse.
Click to expand...
Click to collapse
Are you talking from permanent fixes?
Which adb method? Do you mean the over TWRP Terminal?
I will btw flash now miui after I flashed persist with ur method and then flash xposed to see if my /persist breaks
NightScap3 said:
Are you talking from permanent fixes?
Which adb method? Do you mean the over TWRP Terminal?
I will btw flash now miui after I flashed persist with ur method and then flash xposed to see if my /persist breaks
Click to expand...
Click to collapse
Permanent unless you mess it up again, as I described on this thread. The Adb steps are listed on this post : https://forum.xda-developers.com/showpost.php?p=80623541&postcount=5
tsongming said:
Permanent unless you mess it up again, as I described on this thread. The Adb steps are listed on this post : https://forum.xda-developers.com/showpost.php?p=80623541&postcount=5
Click to expand...
Click to collapse
Do you know why my /data partition gets broken too when this /persist mess up from magisk happens?
NightScap3 said:
Do you know why my /data partition gets broken too when this /persist mess up from magisk happens?
Click to expand...
Click to collapse
I believe that I do.
I choose to not encrypt my phone. However, certain roms, especially experimental may encrypt your data anyway. Back in early August I kept having bootloops and persist issues.
I stopped having issues when I went back to the flashing steps that I used with my previous phone. ( Rarely if ever using Dm_verity)
Edit: Comment below concerns Stock based Rom
Dm-Verity is needed if you want to use a custom recovery such TWRP, and you do not want or need Root.
If you are planning to root the device, then do not flash Dm-Verity. Magisk already has a function which takes care of Dm-Verity and Encryption. So there is no need to flash Dm-Verity.
The problem is that too many people think that Dm-verity is needed, along with Magisk and with every update, it's not unless you are not rooted and in most cases if you are rooted Magisk will check the the boot to ensure that it is still rooted. So flashing Magisk is not always needed ethier. As an extra precaution, I remove all passwords, pattern looks, and face unlocks prior to updating a Rom. I plan to make a post about Dm-Verity soon but will not have time to get to it until Monday or Tuesday.
I hope this helps.
tsongming said:
I believe that I do.
I stopped having issues when I went back to the flashing steps that I used with my previous phone. ( Rarely if ever using Dm_verity)
Dm-Verity is needed if you want to use a custom recovery such TWRP, and you do not want or need Root.
If you are planning to root the device, then do not flash Dm-Verity. Magisk already has a function which takes care of Dm-Verity and Encryption. So there is no need to flash Dm-Verity.
Click to expand...
Click to collapse
I want TWRP only (no root). So, Do I've to flash DM-Verity each time I update rom? Will flashing DM-Verity cause problem? And can you please share your steps of flashing ROM?
Thanks
Hello, so, I got the following problem. My fingerprint is not working on any custom roms out there. I have tried reflashing stock, flashing different roms but with no luck. Everything else is working (GPS, WiFi, Carrier) but fp is not working.
When booting into the OrangeFox Recovery I've noticed that the /persist partition is not mount. When mounting the partition, I've noticed that there's a persist folder appearing in the root directory, so I'm assuming that because of this, I can't get the fingerprint to work. I've also tried making the system R/W but yet, I had no luck with the FP.
Maybe I'm wrong, that's why I'm asking for your help. Why can't I mount the /persist partition?
I have the same problem too .. tried unbricking my phone ,flashing custom roms and flashing persist.img but still no solution...
But i think the solution is to look for someone who has a working fp in realme 7 pro and ask him to backup his persist.img and upload it so we can download it and flash it.
I think that's all what we need so we can get our fp working again.
So if there's anyone who wants to help us... you can by backing up persist.img and uploading it for us so we can download and flash it.
I hope someone sees this.
Thanks in advance.
About that, someone already gave me a backup, after flashing I have the exact same problem...
make sure its backed up directly from a working realme 7 pro not extracted from an original rom ofp..
if it doesn't work then all we can do is to go to realme customer service.
They'll blame it on the motherboard and will ask to pay for replacing while the problem îs software-related. The fingerprint issue it's weird, I've only heard people complain about this issue on Realme devices, both Mediatek and Qualcomm SoCs. This is similar to Samsung's KNOX, once tripped there's no way back.
In my case, I have the european variant, but my guess is that somehow this issue is triggered by flashing another region's OFP. I had someone flashing the OFP for me via MSM Tools.
So, maybe If we find the original OFP for our device, we could probably fix our issue. We could ask customer service but it's unlikelt they'll give it to us, but I Guess it's worth the try.
I tried to crossflash my G8X to the US Open A11 software and screwed up quite badly during the process. I've had to restore my phone from having no partitions and do not have the original LUN5 files, only the 7 required for the crossflash. I've also rooted and installed twrp on this device so if anything that could help needs that I'm able to use it.
I expected the fingerprint sensor not to work, however now the light sensor, accelerometer, gyroscope, magnetometer, etc. don't work either.
Is there something I can do to get this functionality back? I've mostly given up on fixing the imei and network issues but I would like to at least have the phone in a usable state on Wifi.
If more details are needed please do tell and I will do my best to provide them.
Guille05 said:
I tried to crossflash my G8X to the US Open A11 software and screwed up quite badly during the process. I've had to restore my phone from having no partitions and do not have the original LUN5 files, only the 7 required for the crossflash. I've also rooted and installed twrp on this device so if anything that could help needs that I'm able to use it.
I expected the fingerprint sensor not to work, however now the light sensor, accelerometer, gyroscope, magnetometer, etc. don't work either.
Is there something I can do to get this functionality back? I've mostly given up on fixing the imei and network issues but I would like to at least have the phone in a usable state on Wifi.
If more details are needed please do tell and I will do my best to provide them.
Click to expand...
Click to collapse
What original firmware was on it?Most definitely,always make a full back up first thing.
Surgemanxx said:
What original firmware was on it?Most definitely,always make a full back up first thing.
Click to expand...
Click to collapse
It was originally on version 20p of the sprint software. And yeah, I definitely hadn't quite read up on all of the important things I needed to backup beforehand.
Guille05 said:
I tried to crossflash my G8X to the US Open A11 software and screwed up quite badly during the process. I've had to restore my phone from having no partitions and do not have the original LUN5 files, only the 7 required for the crossflash. I've also rooted and installed twrp on this device so if anything that could help needs that I'm able to use it.
I expected the fingerprint sensor not to work, however now the light sensor, accelerometer, gyroscope, magnetometer, etc. don't work either.
Is there something I can do to get this functionality back? I've mostly given up on fixing the imei and network issues but I would like to at least have the phone in a usable state on Wifi.
If more details are needed please do tell and I will do my best to provide them.
Click to expand...
Click to collapse
The same thing happened to me, I came from a10 sprint and installed a11 from Canada, I was left without a network and without a fingerprint sensor, but the other sensors work without problem, to fix network and ntcode I think it is only possible by box, I don't know if of the fingerprint sensor is caused by the lack of serial and imei.
if you come up with a solution let me know bro
mclarenf195 said:
The same thing happened to me, I came from a10 sprint and installed a11 from Canada, I was left without a network and without a fingerprint sensor, but the other sensors work without problem, to fix network and ntcode I think it is only possible by box, I don't know if of the fingerprint sensor is caused by the lack of serial and imei.
if you come up with a solution let me know bro
Click to expand...
Click to collapse
Did you restore your 7 bin files after flashing the A11 software?
Guille05 said:
Did you restore your 7 bin files after flashing the A11 software?
Click to expand...
Click to collapse
They don't have a backup,that's the reason I ask what version software it was.
Guille05 said:
It was originally on version 20p of the sprint software. And yeah, I definitely hadn't quite read up on all of the important things I needed to backup beforehand.
Click to expand...
Click to collapse
Use this firmware.It will correct your issues.
Download LG Firmware for LG G8X ThinQ LMG850QM _Unknown kdz stock USA Rom
Download _Unknown KDZ stock firmware for download with direct link
lg-roms.com
Guille05 said:
Did you restore your 7 bin files after flashing the A11 software?
Click to expand...
Click to collapse
I have the backup of the 7 partitions but they are useless if all the original partitions have been deleted, that is what I understand, I restored the partitions of a KDZ a10 and then flashed it to a11
Surgemanxx said:
Use this firmware.It will correct your issues.
Download LG Firmware for LG G8X ThinQ LMG850QM _Unknown kdz stock USA Rom
Download _Unknown KDZ stock firmware for download with direct link
lg-roms.com
Click to expand...
Click to collapse
I've got version 30c of that firmware installed, you think going back one update would fix it?
mclarenf195 said:
I have the backup of the 7 partitions but they are useless if all the original partitions have been deleted, that is what I understand, I restored the partitions of a KDZ a10 and then flashed it to a11
Click to expand...
Click to collapse
When you flashed the A10 kdz, you followed netmsm's guide right? Did you get any errors when flashing the partitions with fhloader? When I extracted the kdz a few files were missing from the ones used by that code but every kdz I've extracted doesn't have them either.
Guille05 said:
I've got version 30c of that firmware installed, you think going back one update would fix it?
Click to expand...
Click to collapse
Yes,go to 30b it will all work.I tried 30c on my sprint model,and had issues with network connectivity as well.
Surgemanxx said:
Yes,go to 30b it will all work.I tried 30c on my sprint model,and had issues with network connectivity as well.
Click to expand...
Click to collapse
I have the 30a, it would be to try
Guille05 said:
When you flashed the A10 kdz, you followed netmsm's guide right? Did you get any errors when flashing the partitions with fhloader? When I extracted the kdz a few files were missing from the ones used by that code but every kdz I've extracted doesn't have them either.
Click to expand...
Click to collapse
yes, the netmsm's guide, fhloader only use it to restore the luns, restore the kdz partitions one by one with qfil, just try what Surgemanxx suggested first and tell me how it goes.
mclarenf195 said:
yes, the netmsm's guide, fhloader only use it to restore the luns, restore the kdz partitions one by one with qfil, just try what Surgemanxx suggested first and tell me how it goes.
Click to expand...
Click to collapse
It works very well.I tried 30c,and noticed it was slow and laggy and rolled back to 30b and it worked flawless.Fingerprint scanning and all worked with a T-Mobile sim with no issues.They should be good with 30b,all but the IMEI issue they have.
All right I completely erased the flash again and reinstalled following the steps very carefully. I'm now on 30b and can confirm that the sensors work once again. Although the major issues I think were deeper than just the update, because I updated before doing a full erase and it still wasn't working. Now I just have to keep trying to fix the IMEI and FP sensor.
Also I think I may have found my IMEI number thanks to having the ftm partition backed up and therefore still having the serial number. The first 8 digits are always 35886110 for the LG G8x sprint model (and maybe others in the US), the next 6 are the last 6 digits of the serial and the last one is a check digit that you can look up online. I've checked the number on multiple sites and it seems legit so I hope it's actually my number. Now I'll try to write it to the phone somehow, but at least having the IMEI back is a very big step forward.
IMEI is fixed, or at least it appears as such in the phone. I went through with the tutty method of installing the IMEI, and after much trouble (and tutty saying error to my command to write the IMEI) I was able to restore the IMEI to the phone. I confirmed this first using EFS Pro and going into qualcomm NV tools. The IMEI was still as 0 in my phone but after putting in a sim it appeared in the OS and has stayed there. However it still appears as permanently locked when a sim is inserted and the nt-code error does still happen, so the network doesn't work yet.
Guille05 said:
IMEI is fixed, or at least it appears as such in the phone. I went through with the tutty method of installing the IMEI, and after much trouble (and tutty saying error to my command to write the IMEI) I was able to restore the IMEI to the phone. I confirmed this first using EFS Pro and going into qualcomm NV tools. The IMEI was still as 0 in my phone but after putting in a sim it appeared in the OS and has stayed there. However it still appears as permanently locked when a sim is inserted and the nt-code error does still happen, so the network doesn't work yet.
Click to expand...
Click to collapse
That LUNS backup is for the Sprint U.S. model G850UM9.The IMEI is stored in modemst1 and 2 which is LUNS5 that I didn't include for that reason.The NT Code error shouldn't be there if it's the same model/region.Keep me posted.
Surgemanxx said:
That LUNS backup is for the Sprint U.S. model G850UM9.The IMEI is stored in modemst1 and 2 which is LUNS5 that I didn't include for that reason.The NT Code error shouldn't be there if it's the same model/region.Keep me posted.
Click to expand...
Click to collapse
I've flashed your backups and the NT Code error indeed disappeared. However I've still got the perm locked error (so my doesn't work), and the fp sensor still refuses record fingerprints. Was your phone network unlocked when you made that backup? Idk if that maybe interferes with the sim or something
Guille05 said:
I've flashed your backups and the NT Code error indeed disappeared. However I've still got the perm locked error (so my doesn't work), and the fp sensor still refuses record fingerprints. Was your phone network unlocked when you made that backup? Idk if that maybe interferes with the sim or something
Click to expand...
Click to collapse
Yes,it was network unlocked for sure.You're not the only one that has faced this after trying to repair the IMEI.It's perma blocked because it's embedded in the chipset itself,and so far I haven't seen any fix for it as of yet.
I was trying to bypass Google FRP lock on this phone, after having no success, I went online looking and downloaded Rom2Box to try to bypass frp.. When I was trying to get the program to discover my device, nothing happened, it never discovered it, but while it was attempting to discover it, my phone had a black screen with a red dot and 2 smaller white dots moving around the red dot in a circle pattern while bumping off of each other.. I don't know what it means, I never saw it before.. .. Now it won't turn on, or show that it's being charged so I think this program bricked my phone..?
I guess I'd like to give Odin a shot at fixing it for me.. But I don't know Odin, I never messed with phone's like this.. Is, this my best or only option?
Try MSM Tool
@Princess007 I've got the newest ROMt2Box .. if you need it.
@ScarletWizard
Firmware - https://mega.nz/file/EDwAAAIB#hUVmdbWUFI0bt0WQZVfaenTfVwoOqlfn2oexY5uC-Hs
romtoolboxpro - https://mega.nz/file/tTBSGagI#nYvCwk_prTrkM2E3VGk7Sh9qqw5NCn1PZhc73oxrl6U
Samsung Touch sensitivity is very Awesome..
Where can i find the firmware for oneplus nord n20 5g T-Mobile, current build number is GN2200_11_A.07?
Trying to extract boot.img and patch with Magisk
I can pull a rooted super and should have those already actually but if your system is not already magisk patched then you will not be able to boot. I have lost the stock July somewhere in all my backups but I'm willing to pull the boot and super for you if you need it. It is already RW system
Princess007 said:
I was trying to bypass Google FRP lock on this phone, after having no success, I went online looking and downloaded Rom2Box to try to bypass frp.. When I was trying to get the program to discover my device, nothing happened, it never discovered it, but while it was attempting to discover it, my phone had a black screen with a red dot and 2 smaller white dots moving around the red dot in a circle pattern while bumping off of each other.. I don't know what it means, I never saw it before.. .. Now it won't turn on, or show that it's being charged so I think this program bricked my phone..?
I guess I'd like to give Odin a shot at fixing it for me.. But I don't know Odin, I never messed with phone's like this.. Is, this my best or only option?
Click to expand...
Click to collapse
this usually happens because some component of your device is not loading due to either mismatched security pacthes, some system partition has been altered and cannot load or one of many other reasons. i have a device that works perfectly fine and boots with this oneplus logo rather than the tmobile splash that it used to boot with. for me this was caused by mixing components from different systems. i had to flash matching radios, boot, and system, vbmeta disabled to get the device to function with mismatched partitions but the only thing thats still not working is the tmobile splash, which i dont miss and have no desire to try to fix that so i have been running this device in that state for months with 0 problems other than when one of my mods breaks the system and i just have to undo whatever i modified and im back to a functioning state. thedot with 2 dots bouncing around it is fine so long as everything else works, just means that something in vendor is probably different than what it expects so that part doesnt load or some other partition..... disabling verity and verification can usually get me booting again if this happens whether everything else works and is important to you is your decision to fix it or not. going back stock should fix it all. best thing to do if ur gonna mod is make sure u pull backups of EVERY single partition on the device so you have matching images. would suck to lose efs partitions because they are unique and the only people that can get those back for you is the manufacturer
i recommend using partitions backup & restore from playstore. its free and you can pull all of your partitions for restoring in the future. i recommend setting the options to save as raw(.img) rather than archives and then after it pulls all of them, compress them all into one archive. this will save you from having to extract each image from 100 different archives if you need to do a full restore in the future. best of luck and thanks for your contribution
Glitchmob2640 said:
Where can i find the firmware for oneplus nord n20 5g T-Mobile, current build number is GN2200_11_A.07?
Trying to extract boot.img and patch with Magisk
Click to expand...
Click to collapse
theres alread an a.07 boot image posted thats already been patched. best to pull your own but if your gonna use one thats not pulled directly from your device you may as well just use the one thats already patched. i have attached the magisk-delta patched boot image that i use on my july device GN2200_11_A.07
magisk-delta patched boot image that i use on my july device GN2200_11_A.07
T-Mobile MSM tool
File folder on MEGA
mega.nz
DrScrad said:
T-Mobile MSM tool
File folder on MEGA
mega.nz
Click to expand...
Click to collapse
can someone post a link for the msmtool for the N20 from T-Mobile, this link is dead
Is there an MSM tool for the Metro version of the Nord N20 5G? I can't seem to find one anywhere.
ScarletWizard said:
Download MSM Download Tool: Unbrick any OnePlus Device [Video]
From this guide, you could download the MSM Download Tool for every OnePlus device and then use it to unbrick your OnePlus device.
www.droidwin.com
Click to expand...
Click to collapse
That one ain't gonna work.. you've gotta download the newest tool..
NewVersion_2.exe
drive.google.com
Does anyone have a link to just the msm tool without the rom?
I've got the rom, but no working tool, and I don't have the internet to download a whole other rom