Related
Bricked your M5? Post here. I am one of three posters who have posted threads requesting assistance - we might as well create one thread where we can try and help each other.
My model? SHT-AL09 (C636). My story? I apparently made a bad change to my build.prop file, and had USB debugging disabled. I then probably dug myself a deeper hole trying to recover. I don't even get boot animation anymore. I'd happily pay someone to unbrick me.
The only potential progress I have made, is that I was able to install and successfully boot TWRP - although TWRP detects that I have no operating system installed and I am unable to mount any partitions except for my external SD card. Using TWRP's file manager, I can see that the system partition, for example, has not been entirely wiped, but many files seem to be missing. At the very least, TWRP allows me to turn the screen off without seeking to contantly reboot thereafter.
To install TWRP, I followed these instructions intended for Mate 9 owners:
duraaraa said:
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei.
It's just a preliminary build so I can't promise anything/everything will work! Keep that in mind. I'm not responsible if you brick your device.
EDIT: Does not work with Mate 10 series.
DOWNLOAD LINK:
https://drive.google.com/open?id=0B45NCsO2AL_1NEh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei/comments/75uwkd/october_12_first_official_android_o_beta_for/
and the official European beta.
To install:
First, have Android O running. Unlock the bootloader. Download the twrp image.
Then, run in fastboot mode:
fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
Then, reboot holding volume up, and you've got TWRP!
Note: With the Android O update, it is no longer possible to flash the recovery2 partition. Furthermore, the names of the partitions have changed. Please keep that in mind, and don't mess around too much with TWRP, to be sure you don't brick your system!
Click to expand...
Click to collapse
Hmm ... I wanted to ask you whether you have the full OTA package for your device? So you should be able to extract all the partition images from there and to fastboot flash them. But I checked on HFF and I do not see a full OTA package matching your device yet.
AndDiSa said:
Hmm ... I wanted to ask you whether you have the full OTA package for your device? So you should be able to extract all the partition images from there and to fastboot flash them. But I checked on HFF and I do not see a full OTA package matching your device yet.
Click to expand...
Click to collapse
I've tried flashing system.img/ramdisk.img from the c00 package. Maybe I have to wait for c636 firmware, or maybe I have to flash additional .imgs. I am pretty sure that the specs and hardware I have are the same as the c00.
I've tried flashing the entire update.zip file in TWRP...but as noted TWRP is unable to mount internal storage. I'm not sure if I need to wipe and reformat first. I also have no clue whether the TWRP build I installed is properly compatible with the device. I had nothing to lose by giving it a shot.
thref23 said:
I've tried flashing system.img/ramdisk.img from the c00 package. Maybe I have to wait for c636 firmware, or maybe I have to flash additional .imgs. I am pretty sure that the specs and hardware I have are the same as the c00.
Click to expand...
Click to collapse
This will not work as the boot chain will be broken due to mismatching checksums. You need to have the correct images. To flash a OTA image you also need to have the standard recovery image installed ...
So...will someone correct please correct me if this is wrong?
If I were to flash a c00 oeminfo file, I could then install a c00 update.zip via dload folder?
Would c432 work as well (with a flashed oeminfo), even though the Euro hardware has different bands than my hardware?
There is now a full OTA on FF for C635.....still nothing for c636...
Finally, a full OTA is available for c636.
But the 'dload' method (update.app on an sd card) failed at 5%. And flashing ramdisk/recovery/erecovery/system images also failed.
Is this possibly because the OTA is B153, whereas my M5 was shipped B121?
(I hate to be that guy bumping his own thread, sorry)
I'm unbricked!
For those in a similar spot, looking to rebrand, or otherwise interested...
I finally e-mailed Funky Huawei for assistance. Their unbrick tool did not work. However, their e-recovery method worked perfectly (basically, you point your router's DNS to Funky Huawei, enter stock recovery and connect to wi-fi, and Funky Huawei's servers mimic Huawei's servers. If they do not have your firmware on their server, they will add it by request (provided it exists on the internet).
I paid $65 for a 30 day pass - a little steep, but I was impatient. I'm not sure if I could have gotten away with paying less. If you want to try and use my FH account over the next 30 days PM me (although I don't want to get carried away with that).
For those looking to rebrand, if you can flash an OEMinfo file successfully (FH has a rebrand tool and I have no clue how well it works), you should be able to use FH's erecovery method to flash firmware (don't blame me if something goes wrong).
One reason for the trouble I was having, if because I bootlooped after making a change to the vendor/build.prop file. This file was on the vendor partition, not the system partition, and for whatever reason the vendor partition cannot be flashed via fastboot (in theory it can be flashed, in reality it returns an error that doesn't have to do with the size of the partition).
Before reverting to FH, I finally got TWRP installled and functioning, and after all the attempts I made to recover my device, the same build.prop file which initially caused a bootloop was still in the /vendor folder. And TWRP wouldn't mount the system and vendor partitions as read/writeable - that was frustrating.
Now off to experiment with AOSP GSIs while I feel like I have little to lose...
Please help me
hello everyone,
i tried to rebrand my m5pro with help of ministryofsolutions. Something went wrong and my tablet (CMR-AL19) is stucked in the recovery mode. how can i fix it? Someone who ca help me? I will pay
Greeztings
Luigi
thref23 said:
Bricked your M5? Post here. I am one of three posters who have posted threads requesting assistance - we might as well create one thread where we can try and help each other.
My model? SHT-AL09 (C636). My story? I apparently made a bad change to my build.prop file, and had USB debugging disabled. I then probably dug myself a deeper hole trying to recover. I don't even get boot animation anymore. I'd happily pay someone to unbrick me.
The only potential progress I have made, is that I was able to install and successfully boot TWRP - although TWRP detects that I have no operating system installed and I am unable to mount any partitions except for my external SD card. Using TWRP's file manager, I can see that the system partition, for example, has not been entirely wiped, but many files seem to be missing. At the very least, TWRP allows me to turn the screen off without seeking to contantly reboot thereafter.
To install TWRP, I followed these instructions intended for Mate 9 owners:
Click to expand...
Click to collapse
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
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.
Hi, i tried to install a custom rom in my device (y6 2018 ATU L21) and an error ocurred due to my ****ty usb cable, so now im in a big trouble because the phone is bricked.
I backup some partitions before the accident such as kernel, ramdisk but guess what, the most important (system.img) is corrupted and i can't do anything.
The phone boots and shows huawei logo and then black screen forever, i can't access TWRP nor Erecovery, im completly stuck.
I searched on "Huawei Firmware Finder" but any of the ROMs for ATUL21 works (some of them have missing partitions) so now i only depend on the community, if there is any good person that has this phone and wants to help me by sharing the partitions to me i will appreciate such act of generosity, if you want to help me you can follow those steps (Need to be root):
https://forum.xda-developers.com/t/guide-twrp-backup-current-partitions.3853831/
If you have any stock rom that works for this model im glad to accept it .
Have a good day.
I think I have this for you:
ATU-L21 BACKUP
Good luck!
mro92 said:
I think I have this for you:
ATU-L21 BACKUP
Good luck!
Click to expand...
Click to collapse
For people like you i never lose hope on the community and i always try to help others, thank you so much my brother. Bless you and your family.
Mimoun.
which tool do i use to write this file
Hello, it's been a while since the post but I still need your help. I have the same problem as describe. I downloaded the file from the nice man. Tried to flash it with fastboot but the phone still has the same problem. maybe you can solve your problem and can help me.
I only have access to fastboot because the rest doesn't work. maybe you also have a custom ROM that works on the device, which doesn't necessarily have to be original software.
Thanks in advance
Jannikoks06 said:
Hello, it's been a while since the post but I still need your help. I have the same problem as describe. I downloaded the file from the nice man. Tried to flash it with fastboot but the phone still has the same problem. maybe you can solve your problem and can help me.
I only have access to fastboot because the rest doesn't work. maybe you also have a custom ROM that works on the device, which doesn't necessarily have to be original software.
Thanks in advance
Click to expand...
Click to collapse
Hi, this is what i have done to recover the phone. First, there is one mistake that i made and it was trying to flash the files from fastboot, you can't do that because the phone is bricked, instead you need to download the firmware from "Huawei Firmware Finder" and then you need to dissasemble your phone to press the test point. look at this video for reference huawei test point once your PC is going to recognize your device as 'COM' on the device manager, and then you need to use a tool to flash the firmware, i can't share with you the tool since i have switched to Linux distro and i don't use Windows anymore. But if you were smart enough to flash your phone i think with a little bit of search you are gonna find.
Good Luck and have a good day.
Hello thanks for the answer, I have already downloaded stock roms from 2 different sites, both are the same.There are many subfolders in the file but after a long search you can find some .app files right? What should I do with the file exactly? Flash this directly? If so, do you happen to remember the name? Or did you extract the various files from this file, such as "Boot" or something else?