Related
Guys help!! All sensors in my onplus two is not working, fingerprint, light sensor, auto rotat its not even listed in the test screen *#808#, and I tried everything about factory reset and flash different roms, please help
Take a look at this thread: http://forum.xda-developers.com/showthread.php?t=3269543 should solve your problem
Sent from my ONE A2001 using Tapatalk
wooly909 said:
Guys help!! All sensors in my onplus two is not working, fingerprint, light sensor, auto rotat its not even listed in the test screen *#808#, and I tried everything about factory reset and flash different roms, please help
Click to expand...
Click to collapse
Same Problem here.
All Sensors are dead...
@deletescape:
tried your link. flashed complete but some Prob.
Update:
After flashing this in Recovery (TWRP) all Sensors are back...
https://drive.google.com/file/d/0BzZGP6ljwL-XdGlsTFZRajk3NTA/view?usp=docslist_api
Found here:
http://forum.xda-developers.com/one...gmercians-hydrogen-os-h2os-1-2-5-1-1-t3289566
wooly909 said:
Guys help!! All sensors in my onplus two is not working, fingerprint, light sensor, auto rotat its not even listed in the test screen *#808#, and I tried everything about factory reset and flash different roms, please help
Click to expand...
Click to collapse
I am still having this issue, can anyone help?
Edit: I have solved the problem, it had to do with flashing the persist file for my rom
Wagi99 said:
Same Problem here.
All Sensors are dead...
@deletescape:
tried your link. flashed complete but some Prob.
Update:
After flashing this in Recovery (TWRP) all Sensors are back...
https://drive.google.com/file/d/0BzZGP6ljwL-XdGlsTFZRajk3NTA/view?usp=docslist_api
Found here:
http://forum.xda-developers.com/one...gmercians-hydrogen-os-h2os-1-2-5-1-1-t3289566
Click to expand...
Click to collapse
If you don't mind will you upload the working link of the file.which will help all members,because the thread you indicaded is closed.
Flash Oxygen OS again via Stock Recovery.
It will Fix this
kumu.bandara said:
Flash Oxygen OS again via Stock Recovery.
It will Fix this
Click to expand...
Click to collapse
Not if it's a persist issue - the flashable zips don't contain persist.img.
Tapatalked via OnePlus 2
oldwabi said:
I am still having this issue, can anyone help?
Edit: I have solved the problem, it had to do with flashing the persist file for my rom
Click to expand...
Click to collapse
Hi, could you plz tell where to download the persist file for oxygen 5.1？
http://forum.xda-developers.com/one...overy-teamwin-recovery-project-3-0-0-t3310713
Download this zip it contains the persist.img file
Flash it using fastboot
Elstron said:
http://forum.xda-developers.com/one...overy-teamwin-recovery-project-3-0-0-t3310713
Download this zip it contains the persist.img file
Flash it using fastboot
Click to expand...
Click to collapse
thanks!
Stock ROM replace the Stock Recovery after Flashing !!
I downloaded the recovery package with the persist.img, did a terminal backup of the persist.img in place. Did a erase form fastboot and flashed the one form the device recovery image.
All working again.
hbvdh said:
I downloaded the recovery package with the persist.img, did a terminal backup of the persist.img in place. Did a erase form fastboot and flashed the one form the device recovery image.
All working again.
Click to expand...
Click to collapse
Bro
M new to one plus 2 community and my proximity and light sensors are not working...Guide me to the fix..M on Oxygen Os 3.5.6 ...plzzz
RGulati24168 said:
Bro
M new to one plus 2 community and my proximity and light sensors are not working...Guide me to the fix..M on Oxygen Os 3.5.6 ...plzzz
Click to expand...
Click to collapse
First download cpu-z from the play store and install it, go to sensors tab and see if sensors are showing, if they are showing sensors are working. If they are showing you have a different problem.
If not find a guide to backup the persist image first. It took me a while to find the right partition to backup. This step i very important.
I don't have the links for all the download you have to do, maybe someone here can provide them.
I'm not responsible for bricking devices, this is on your own risk.
Step 1: backup your current persist.img.
Step 2: download qualcomm recovery tool for oneplus 2 (1,2 GB) and extract it to your pc, this will have the original persist.img file.
Step 3: download fastboot and adb
Step 4: put phone in to fastboot mode
Step 5: run fastboot erase persist, now all your sensors are gone!!!
Step 6: run fastboot falsh persist persist.img
Step 7: reboot and look if sensors are working.
If your not comfortable doing this steps, please contact Oneplus support, they can help you with one of there remote sessions.
Hoped i helped.
RGulati24168 said:
Bro
M new to one plus 2 community and my proximity and light sensors are not working...Guide me to the fix..M on Oxygen Os 3.5.6 ...plzzz
Click to expand...
Click to collapse
Did you solve the problem with light / prox sensors?
flaektrem said:
Did you solve the problem with light / prox sensors?
Click to expand...
Click to collapse
I have the same problem.
RGulati24168 did you solved the problem ???
It Worked!!!!!!
hbvdh said:
First download cpu-z from the play store and install it, go to sensors tab and see if sensors are showing, if they are showing sensors are working. If they are showing you have a different problem.
If not find a guide to backup the persist image first. It took me a while to find the right partition to backup. This step i very important.
I don't have the links for all the download you have to do, maybe someone here can provide them.
I'm not responsible for bricking devices, this is on your own risk.
Step 1: backup your current persist.img.
Step 2: download qualcomm recovery tool for oneplus 2 (1,2 GB) and extract it to your pc, this will have the original persist.img file.
Step 3: download fastboot and adb
Step 4: put phone in to fastboot mode
Step 5: run fastboot erase persist, now all your sensors are gone!!!
Step 6: run fastboot falsh persist persist.img
Step 7: reboot and look if sensors are working.
If your not comfortable doing this steps, please contact Oneplus support, they can help you with one of there remote sessions.
Hoped i helped.
Click to expand...
Click to collapse
Tysm buddy
UPDATE (07-Jan-2017):
If your OnePlus 2's IMEI#2 = 0, (IMEI#1 is showing correct IMEI)
Because you run these commands in fastboot mode:
"fastboot erase modemst1 "
"fastboot erase modemst2 "
"fastboot erase cache"
Then,
A fix has been made into this zip file.
https://www.androidfilehost.com/?fid=529152257862693598
Kindly thank Tony.L & Crystal.Z from OnePlus OOS team.
You have to be on OOS 3.5.6 (Clean-Flashed, non-rooted, from whatever ROM you are currently on).
I had TWRP Hybrid Recovery v3.4 installed.
IMEI#2 will come back again.
Now, Remember to backup EFS using terminal method.
& DONT erase modem ever again.
mine have same problem..only IMEI2 shows "0"..my phone keep random rebooting until now
osr.arora said:
I will be really grateful, if anybody can help me recover/write IMEI#2 on my OnePlus 2.
IMEI#2 currently shows as "0", (IMEI#1 is showing correct IMEI)
I don't have a EFS backup.
Device is out of warranty.
OnePlus's L2 support team, flashed OOS v3.1.0 via Qualcomm recovery method via remote session, but still no fix.
Lastly (I think, some may consider this illegal, but I'm just trying to write the missing IMEI on my phone),
I searched for IMEI writer softwares ( WriteDualIMEI(W+G_eMMC), Read&Write_Tool_v1.3) on internet, but somehow, i couldn't make them work (Maybe incorrect Qualcomm drivers on my PC, or idk what )
*********How did this all happen*********
I read a blog, that In order to increase the download speed from the Jio SIM, preferred LTE Band should be switched (from 3 to 40).
So, I pressed *#*#4636#*#*, >> Phone Info page >> three dot menu >> select radio band >> SELECTED Band mode 40.
Immediately after that,
Vodafone Sim stopped working in any of the SIM-Slots, But Jio sim (4G) was working in both the slots.
*****
Then I ran these commands in fastboot mode:
"fastboot erase modemst1 "
"fastboot erase modemst2 "
"fastboot erase cache"
Immediately, Both the SIM slots stopped working.
*****
Then I flashed "new-modem.zip" from benschhold (https://androidfilehost.com/?fid=24407100847293158)
which makes SIM-Slot-1 work with both Vodafone & Jio,
But SIM-Slot-2 only detects the sim, but with 0 network bars i.e. "No service| Vodafone"
I would appreciate your help.
Click to expand...
Click to collapse
***************************************
lockmunk said:
mine have same problem..only IMEI2 shows "0"..my phone keep random rebooting until now
Click to expand...
Click to collapse
Lesson for you guys. The first thing to do after flashing a custom recovery is to make a complete nandroid backup..
Tunatje said:
Lesson for you guys. The first thing to do after flashing a custom recovery is to make a complete nandroid backup..
Click to expand...
Click to collapse
FYI, a full nandroid backup doesn't backup the two EFS partitions even though EFS is an option in TWRP's backup menu.
You need to manually backup the modemst1 & modemst2 partitions
Spannaa said:
FYI, a full nandroid backup doesn't backup the two EFS partitions even though EFS is an option in TWRP's backup menu.
You need to manually backup the modemst1 & modemst2 partitions
Click to expand...
Click to collapse
True. Done it myself through terminal. Forgot about the dual sim :laugh:
osr.arora said:
I will be really grateful, if anybody can help me recover/write IMEI#2 on my OnePlus 2.
IMEI#2 currently shows as "0", (IMEI#1 is showing correct IMEI)
I don't have a EFS backup.
Device is out of warranty.
OnePlus's L2 support team, flashed OOS v3.1.0 via Qualcomm recovery method via remote session, but still no fix.
Lastly (I think, some may consider this illegal, but I'm just trying to write the missing IMEI on my phone),
I searched for IMEI writer softwares ( WriteDualIMEI(W+G_eMMC), Read&Write_Tool_v1.3) on internet, but somehow, i couldn't make them work (Maybe incorrect Qualcomm drivers on my PC, or idk what )
*********How did this all happen*********
I read a blog, that In order to increase the download speed from the Jio SIM, preferred LTE Band should be switched (from 3 to 40).
So, I pressed *#*#4636#*#*, >> Phone Info page >> three dot menu >> select radio band >> SELECTED Band mode 40.
Immediately after that,
Vodafone Sim stopped working in any of the SIM-Slots, But Jio sim (4G) was working in both the slots.
*****
Then I ran these commands in fastboot mode:
"fastboot erase modemst1 "
"fastboot erase modemst2 "
"fastboot erase cache"
Immediately, Both the SIM slots stopped working.
*****
Then I flashed "new-modem.zip" from benschhold (https://androidfilehost.com/?fid=24407100847293158)
which makes SIM-Slot-1 work with both Vodafone & Jio,
But SIM-Slot-2 only detects the sim, but with 0 network bars i.e. "No service| Vodafone"
***************************************
I would appreciate your help.
Click to expand...
Click to collapse
Did you managed to get any info on that??
I also encountered the exactly same issue..
ashu01 said:
Did you managed to get any info on that??
I also encountered the exactly same issue..
Click to expand...
Click to collapse
No Fix, as of yet !
Somebody said, he flashed modem files from beanstalk Rom thread, & that fixed the missing IMEI issue.
I haven't tried it yet,
If you try it, & it fixes this problem, update me on thia thread !
Hi
Like I wrote in another thread, this is what I did to get working modem after testing out the unstable H2OS firmware
1. Ran TWRP backup of CM14 install
2. Restored OOS 3.1 OTA zip
3. Formatted modemst1 and 2 and persist partition using fastboot
4. Did factory reset and booted up OOS and powered down the phone
5. Powered up into fastboot and restored persist partition with the persist.img dump found in some thread in this forum
6. Restored back my CM14 install and now everything is working again (except for losing some configuration probably stored in the persist partition like button swapping and battery text on icon)
Best regards
pitrus- said:
Hi
Like I wrote in another thread, this is what I did to get working modem after testing out the unstable H2OS firmware
1. Ran TWRP backup of CM14 install
2. Restored OOS 3.1 OTA zip
3. Formatted modemst1 and 2 and persist partition using fastboot
4. Did factory reset and booted up OOS and powered down the phone
5. Powered up into fastboot and restored persist partition with the persist.img dump found in some thread in this forum
6. Restored back my CM14 install and now everything is working again (except for losing some configuration probably stored in the persist partition like button swapping and battery text on icon)
Best regards
Click to expand...
Click to collapse
Can u send me persist.img pls
My email is [email protected]
Would be better, if you upload persist file here.
pitrus- said:
Hi
Like I wrote in another thread, this is what I did to get working modem after testing out the unstable H2OS firmware
1. Ran TWRP backup of CM14 install
2. Restored OOS 3.1 OTA zip
3. Formatted modemst1 and 2 and persist partition using fastboot
4. Did factory reset and booted up OOS and powered down the phone
5. Powered up into fastboot and restored persist partition with the persist.img dump found in some thread in this forum
6. Restored back my CM14 install and now everything is working again (except for losing some configuration probably stored in the persist partition like button swapping and battery text on icon)
Best regards
Click to expand...
Click to collapse
We are facing missing IMEI#2 issue,
Did your steps, fix this issue ?
osr.arora said:
We are facing missing IMEI#2 issue,
Did your steps, fix this issue ?
Click to expand...
Click to collapse
Yes they did, after flashing the H20S firmware and going back to OOS firmware I was missing IMEI on both modems/incompatible modemst partitions. Formatting these and booting up OOS recreated these and after also restoring persist partition both IMEIs was reported and Cyanogenmod no longer bootlooped.
pitrus- said:
Yes they did, after flashing the H20S firmware and going back to OOS firmware I was missing IMEI on both modems/incompatible modemst partitions. Formatting these and booting up OOS recreated these and after also restoring persist partition both IMEIs was reported and Cyanogenmod no longer bootlooped.
Click to expand...
Click to collapse
Before flashing H2Os firmware,
What was your OP2 running ?
Also can you list all links to files, which helped you.
Just an hour ago, i flashed "ResurrectionRemix-6.0-OOS-2.2.1-Modem.zip" on my OnePlus 2 (running Oxygen OS 3.1.0 with TWRP) & it went into bootloop.
So now i'm downloading @Spannaa 's "Oxygen OS 2.1.1 fastboot.zip" , to make my phone working again.
osr.arora said:
We are facing missing IMEI#2 issue,
Did your steps, fix this issue ?
Click to expand...
Click to collapse
I though my phone was fine, then I noticed my swedish BankID just didn't want to work. Turns out my SIM2 has null IMEI just like yours. Tried Qualcomm restore to OOS 3.0.2 but still IMEI2:0, so it looks like trying out the H2OS 2.5 beta firmware and going back was a real killer for my phone. I get signal on both SIM cards and strangely I can call using both SIM cards even though one is showing no IMEI
Update
After analyzing the nv data of my phone, I can tell that the IMEI for SIM card 1 is there, and there does not seem to be any address register for a second IMEI so the phone must figure this out itself. For me the first IMEI ends with a 99 and second with a 81 which means a difference of -18, perhaps second IMEI is always -18 hexadecimal from the first and therefore automatically calculated and registered by the modem firmware?
@pitrus-
Do you have a European A2003 model? I remember that the difference between European and Chinese models was that the Chinese has only 1 IMEI. Maybe this H20S firmware changed your European model effectively to Chinese. FYI my IMEIs, untoutched by H2OS, differ by 8, 72 vs 64. You can check your original IMEIs from the red box that the phone shipped in, if you still have it.
To resolve this, Oneplus customer service recommends to replace the motherboard:
https://forums.oneplus.net/threads/those-who-lost-their-imei-please-read.475930/page-5#post-15427155
pryggi said:
@pitrus-
Do you have a European A2003 model? I remember that the difference between European and Chinese models was that the Chinese has only 1 IMEI. Maybe this H20S firmware changed your European model effectively to Chinese. FYI my IMEIs, untoutched by H2OS, differ by 8, 72 vs 64. You can check your original IMEIs from the red box that the phone shipped in, if you still have it.
To resolve this, Oneplus customer service recommends to replace the motherboard:
https://forums.oneplus.net/threads/those-who-lost-their-imei-please-read.475930/page-5#post-15427155
Click to expand...
Click to collapse
Yes, it's an A2003 European model. If only I had a dump of a working A2003 NV Data so I could find the difference between them. Whoever could give me this could just zap out 00550 NV Item (IMEI) so as not to share it with me. That would tell us which NV Items to change to swap between single och dual sim card modell.
@pitrus-
I have the IMEIs on my OP2 still intact, I have not flashed latest H2OS beta, nor have I used the fastboot erase/format commands. So I can analyse the /dev/block/mmcblk0p17 and /dev/block/mmcblk0p18 dd dumps. Could you tell me which tools to use, or how can I edit out my IMEIs?
Really confused, what to flash, what not to flash (to fix the IMEI issue) !!!
I restored my OP2 to OOS 2.1.1 with Qualcomm Restore Files (from OnePlus Forums) as @Spannaa 's fastboot file, didn't worked, idk why !
osr.arora said:
Really confused, what to flash, what not to flash (to fix the IMEI issue) !!!
I restored my OP2 to OOS 2.1.1 with Qualcomm Restore Files (from OnePlus Forums) as @Spannaa 's fastboot file, didn't worked, idk why !
Click to expand...
Click to collapse
It doesn't mather what you flash, our nv data is incompatible with all modems other than the unstable H2OS 2.5 one. Only solution is to wait for a OxygenOS modem that uses the same nv data structure if you like me didn't make a dump of the nv data before flashing the H2OS ROM. If you do want to go back to CM14, just flash H2OS 2.5.x and then format system, data, cache and flash latest CM14. You will still get null IMEI on second SIM slot, there's no solution for this right now. (You could also Qualcomm restore back to OxygenOS 3.1, this will give you the TZ needed by CM14).
pitrus- said:
It doesn't mather what you flash, our nv data is incompatible with all modems other than the unstable H2OS 2.5 one. Only solution is to wait for a OxygenOS modem that uses the same nv data structure if you like me didn't make a dump of the nv data before flashing the H2OS ROM. If you do want to go back to CM14, just flash H2OS 2.5.x and then format system, data, cache and flash latest CM14. You will still get null IMEI on second SIM slot, there's no solution for this right now. (You could also Qualcomm restore back to OxygenOS 3.1, this will give you the TZ needed by CM14).
Click to expand...
Click to collapse
i also used fastboot erase command..and in the same situation of showing imei2 0.
do you think the oos update will have a fix for this issue??
I am using a OnePlus 2 device i had Halogen OS installed on it along with H2OS modem...
I later decided to go back to Oxygen OS after the OOS 3.5.6 update so i called customer care for remote flashing but after the flashing completed my device didn't had it's WiFi SSID along with random reboots and no network...
I researched some more some said to delete and flash persist.img and reserve4.img with fastboot to fix ...but i didn't flashed reserve4.img becuase somewhere in the post it was mentioned to not flash it... it didn't work...
So i just flashed H2OS 2.5 in some hope and got the network on one of the sim and rest was working(I didn't checked the sensors but they might be working) fine then i flashed OOS 3.5.6 because they both are almost same...and everything worked except the sensors...and IMEI 2 was still 0 so i found one of the post where Tony Lau provided me with OOS 3.5.7 OTA .. so i reflashed OOS 3.5.6 and flashed the OTA... I got the IMEI 2 back but lost the camera....Plz help me
Got a second Redmi 7A, I'm 99.99% certain it came with *global* 10.2.5 PCMMIXM (it was what ordered, and saw it too, pretty certain), decided to let it upgrade OTA, it picked 11.0.6 OTA, and it came to:
MIUI Global 11.0.6 PCMEUXM (notice the EU there), which, I'm assuming from this url: https://mirom.ezbox.idv.tw/en/phone/pine/
to be this one:
Code:
Redmi 7A – EEA Stable ROM
Lstest V11.0.6.0.PCMEUXM(History)
MIUI 11
Android 9.0
Update at 2019-10-31 19:05:57
Changelog Expand Official Link
Recovery miui_PINEEEAGlobal_V11.0.6.0.PCMEUXM_bcc90ca1df_9.0.zip
Filesize 1.5G
MD5 bcc90ca1df89a4f3d8cc7b9705a70d83
which is a bit confusing, it says Global, but has "EU" in the name.. in any event, flashed TWRP as per:
https://xiaomifirmware.com/guides-and-tips/how-to-install-twrp-and-magisk-root-on-redmi-7a/
choose the LRTeam version:
Code:
2a3296af05267160cba2891bff446203 TWRP-3.3.1-1003-REDMI7A-CN-wzsx150.img
seemed newest, all is great, it boots into TWRP recovery.. Next, trying to get Magisk on it, got the manager apk installed 7.4 all fine, it says 20.1 needs to be installed so...
unzipped the boot.img from above zip file, it has this md5, this is original , unmodified boot.img:
Code:
036d1b6c5a99e9417f8d3e98d5718368 boot_Global_V1106PCMEUXM.img
following this guide: https://romprovider.com/2019/01/create-pre-rooted-patched-boot-img-magisk/
Magisk successfully patched the boot.img on the same phone (running 11.0.6) and got this file:
Code:
dad219422c9302a460d4d2370adafb4f magisk_patched_Global_V1106PCMEUXM.img
transferred to PC, attempted to flash:
Code:
c:\XiaomiADB\bin>fastboot flash boot magisk_patched_Global_V1106PCMEUXM.img
target reported max download size of 535822336 bytes
sending 'boot' (14914 KB)...
OKAY [ 0.470s]
writing 'boot'...
OKAY [ 0.190s]
finished. total time: 0.665s
c:\XiaomiADB\bin>fastboot reboot
rebooting...
finished. total time: 0.003s
Phone boots fine, however, magisk still says it needs to be installed...
in developer's options, the USB debugging is enabled, and boot loader is definitely unlocked, it says on splash screen and the OEM Unlocking is greyed out and says "bootloader already unlocked".
Also, attempted to flash boot image from within TWRP, selecting the above boot.img file and selecting the boot partition, flashes OK, however, after normal reboot, as if nothing happened, phone boots, but magisk is NOT installed (no root).
Is there anything missing in these steps? does anyone have a correctly patched 11.0.6 image with magisk in it from an 7A phone?
Only thing that appears as an "error" are these family of cmds to unlock boot loader:
Code:
fastboot oem unlock
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.004s
however, i think that is normal/expected, since the bootloader is already unlocked.. able to flash twrp, etc.
Thanks so much for any ideas...
Stormy.
Forgot to mention that attempted to install Magisk 20.1 zip file downloaded by the app, from within TWRP, attached screenshot of how that looks like all seems okay but after reboot it still says that magisk needs to be installed... Very strange..
Appreciate any thoughts..
Stormy
noticed in above screenshot that it detected a patched boot image so decided to try installing the
v20.1 Magiskk zip file with the stock Boot, the install results in a screenshot, after reboot it still says that magisk has to be installed.!
also attaching screenshots showing the device is unlocked as well as USB debugging and OEM unlocking are all there.
Should this be posted in The magisk forum or is this something specific to the 7A? Or my steps?
How to debug further?
Attempted with the other TWRP image TWRP_v3.3.1-1_all.img, same results also reinstall the magisk manager 7.4 and same results....hmm.. maybe the OTA update took wrong ROM version. (EU and not pure Global)?...
Digging a bit more, found this pretty cool tool: https://www.xiaomitool.com/V2/latest called: "XiaoMiTool V2 ", which basically automated (almost) Everything !! Tried to do TWRP, as well as Magisk, it too followed similar steps I did, all automatically, rebooting, patching, etc. but outcome is still same, when phone boots normally, Magisk Manager says that Magisk 20.1 needs to be installed...
Then tried to flush miui_PINEGlobal_V11.0.4.0.PCMMIXM_674ed79f0b_9.0.zip using that tool, it said all is OK, phone rebooted , wiped all, but it still runs the EU version for some reason.. Now trying to find the path to "downgrade" from 11.0.6 to 11.0.4, or switch from EU to Global.. maybe that's the source of all issues, not sure what else to try
Reporting progress, to keep track of what was attempted. So, decided to WIPE all and start with 11.0.4 Global fresh, from TWRP, wiped everything, to the point it said "no OS installed, are you sure u want to reboot" it rebooted into fastboot, then downloaded the 11.0.4 Global .tgz and flashed, phone booted OK this time into 11.0.4 Flashed TWRP, and then attempted to flash Magisk via both routes, one by patching the boot.img from the .tgz and flashing, all using the Phone (to avoid any PC/driver/adb issues). The flashing worked fine, but upon reboot, Magisk Manager claimed that Magisk is not installed. Second try was to flash the stock boot.img, then flash magisk zip file, did that for v20.1, v19.4 and 19.3, each time from stock boot.img, and reboots to test, none of them showed that magisk is installed...
all this time, usb debugging is enabled despite most work done on the actual redmi 7A phone itself.
Then uninstalled magisk manager 7.4, and tried with 7.2, but that doesn't change much since any action there wants to update to v7.4..
next step will wipe again, and go for the Global 10.2.5... if that doesn't work then I really don't know what can be going on...
If anyone does have a 7A with MIUI 11 with a properly patched boot.img, would love to try it... all my patching attempted booted fine, but none showed that Magisk is installed... finding it hard to think it's a magisk bug, more likely some MIUI 11, lets see how 10 works out...
Stormy
OK, some success! so, wiped ALL again, to the point of no-OS installed; phone only boots into fastboot (brick), using flash_all.sh from 10.2.5 fastboot Global ROM flashed entire phone and it booted OK.
btw, not easy to find 10.2.5 now, as places already updated links to 11.0.x..
Once in 10.2.5, tried to patch Magisk in all possible ways (twrp or patching boot.img on phone the flashing from Windows10/PC) as also described in this thread few weeks ago:
https://forum.xda-developers.com/showpost.php?p=80498891&postcount=179
but it did NOT work, well, the procedure appeared OK, no errors and when booting, it says magisk needs to be installed.
The only thing that works is the provided boot global .img file [size 14.5 MB (15,269,888 bytes)], as soon as this one is flashed, via phone/twrp or PC, then the magisk is correctly detected.
Very mysterious, why only that boot.img is working on my 7A phones.. maybe there's an additional step, to "sign" or fix the boot.img before it can be flashed?
now took a full TWRP backup, and will try to move to 11.0.4 see if magisk is retained, and if not, if possible to re-gain it.. if not, then, will restore from TWRP backup.
Any thoughts welcomed..
Stormy.
Did not manage to get it working with MIUI 11 yet, so backed to MIUI 10.2.5.. all is fine there.
Noticed that TWRP did not "stick", flash but after normal boot, it came back to original recovery. I think this is b/c of Verify Boot in android Pie/9.. so I *think* what helped here is to flash a vbmeta.img from first post of this thread:
https://forum.xda-developers.com/redmi-7a/how-to/custom-gsi-firmware-t3965820
Even after flashing this, and even in 10.2.5, patching the STOCK 10.2.5 from the phone using Magisk 20.1 and installing using TWRP did not work, not sure if this is a bug in magisk or what, but only way to get root was using the provided boot.img as described above. I'll keep using 10.2.5 for now. feel free to add any ideas here , maybe one day will get more time and a spare phone to try MIUI 11
Stormy.
hey , I have the same problem. I noticed you mentioned 'sign', what should I sign what things? and how to sign?
I was going to ask for the same thing : is there any method to root Redmi 7A under MIUI 11?
For my case :
-I can flash and boot to TWRP,
-I can 'flash' (install) Magisk through TWRP,
-However : this has no effect. Still Magisk Manager tells me that Magisk was not found!
The Redmi is unlocked and I can install custom roms (Mokee, LineageOS...). I see no reason why the phone can't be rooted it's probably just some bad configuration.
Thank you very much
depaul9999 said:
I was going to ask for the same thing : is there any method to root Redmi 7A under MIUI 11?
For my case :
-I can flash and boot to TWRP,
-I can 'flash' (install) Magisk through TWRP,
-However : this has no effect. Still Magisk Manager tells me that Magisk was not found!
The Redmi is unlocked and I can install custom roms (Mokee, LineageOS...). I see no reason why the phone can't be rooted it's probably just some bad configuration.
Thank you very much
Click to expand...
Click to collapse
Don't bother rooting Redmi 7A, it just isn't possible, not even with the miui 10 (I've tried). There's no way to flash magisk successfuly, because when you do, magisk is still uninstalled, therefore no root and if you try SU instead, it happens some kind of error. If you try magisk without TWRP and flash a patched recovery it still doesn't work either. Since I can only follow tutorials because I understand nothing about Android I can say that there is no tutorial out there that works and all of them are wrong. I just don't understand why people bother to make tutorials that do not work just to make people waste their time.
KnowTheyself said:
Don't bother rooting Redmi 7A, it just isn't possible.
Click to expand...
Click to collapse
Thanks indeed that's the case for the moment. Hopefully we could soon manage to root the phone successfully.
My biggest motive is to install App2SD and move games to external storage, since with my 16GB version I can barely install one or two games and MIUI only allows installation to internal. (I know I should've bought a phone with bigger storage).
depaul9999 said:
Thanks indeed that's the case for the moment. Hopefully we could soon manage to root the phone successfully.
My biggest motive is to install App2SD and move games to external storage, since with my 16GB version I can barely install one or two games and MIUI only allows installation to internal. (I know I should've bought a phone with bigger storage).
Click to expand...
Click to collapse
I've read that the 16GB version of the Redmi 7A is possible to put a micro SD card and format it as internal storage and that was the reason I've bought it, although I'm not yet sure because I'm waiting to buy a microSD card, it's still on the way.
I want to root it because of privacy reasons and that's the only reason. For now I'm using a VPN to block 99% of the google and xiaomi apps, etc. to the internet this way I got some privacy. I have unlocked the phone too so I did uninstalled several apps from the system using the PC.
KnowTheyself said:
Don't bother rooting Redmi 7A, it just isn't possible, not even with the miui 10 (I've tried). There's no way to flash magisk successfuly, because when you do, magisk is still uninstalled, therefore no root and if you try SU instead, it happens some kind of error. If you try magisk without TWRP and flash a patched recovery it still doesn't work either. Since I can only follow tutorials because I understand nothing about Android I can say that there is no tutorial out there that works and all of them are wrong. I just don't understand why people bother to make tutorials that do not work just to make people waste their time.
Click to expand...
Click to collapse
I don't think that's correct.. I've rooted several 7A, as many others on the forum, just look around, all these posts, many HAVE done based on the topics...
There are few more mysteries, even to experts, so don't feel bad (like how to path boot.img from Magisk, did it for other phones, but not possible for this one for some reason).. agree, there is no current/updated guide that works for everyone, but one can piece things together..
The reason there is no complete guide is not b/c people want to waste your time, they are really trying to SAVE time, however, there are many FACTORS at play, like initial ROM/state of the phone, some Global, some EU, some 10.x other 11.x and so forth, which change over time...
Once the bootloader is unlocked, then one should be able to:
- flash vbmeta.img
- flash twrp (I'm using 3.3.1-1003 'wzsx150').
boot into twrp and flash a properly patched boot.img (that matches your phone), now that's the tricky part, b/c one cannot be re-generated, u'd have to dig through some of the posts, like this: https://forum.xda-developers.com/redmi-7a/how-to/custom-gsi-firmware-t3965820 and find the boot.img that works, it had magisk 19.3 in it, but then update is easily possible.
it's important to flash vbmeta otherwise the "verified boot" will revert things back to a "working state", and you'll lose twrp..
Once my phone got to MIUI 11 it was not possible to root (since there is no boot.img that's patches correctly, and i couldn't do it), so i've flashed the whole phone back to 10.2.5 and from there rooting was pretty easy, the trick is to find the right boot.img.
Good luck.
stormy1777 said:
I don't think that's correct.. I've rooted several 7A, as many others on the forum, just look around, all these posts, many HAVE done based on the topics...
There are few more mysteries, even to experts, so don't feel bad (like how to path boot.img from Magisk, did it for other phones, but not possible for this one for some reason).. agree, there is no current/updated guide that works for everyone, but one can piece things together..
The reason there is no complete guide is not b/c people want to waste your time, they are really trying to SAVE time, however, there are many FACTORS at play, like initial ROM/state of the phone, some Global, some EU, some 10.x other 11.x and so forth, which change over time...
Once the bootloader is unlocked, then one should be able to:
- flash vbmeta.img
- flash twrp (I'm using 3.3.1-1003 'wzsx150').
boot into twrp and flash a properly patched boot.img (that matches your phone), now that's the tricky part, b/c one cannot be re-generated, u'd have to dig through some of the posts, like this: https://forum.xda-developers.com/redmi-7a/how-to/custom-gsi-firmware-t3965820 and find the boot.img that works, it had magisk 19.3 in it, but then update is easily possible.
it's important to flash vbmeta otherwise the "verified boot" will revert things back to a "working state", and you'll lose twrp..
Once my phone got to MIUI 11 it was not possible to root (since there is no boot.img that's patches correctly, and i couldn't do it), so i've flashed the whole phone back to 10.2.5 and from there rooting was pretty easy, the trick is to find the right boot.img.
Good luck.
Click to expand...
Click to collapse
Well, if you say so... If you're right then I got the wrong Redmi 7A model. It came with the EU version of the miui.
I already knew the tutorial in the link you gave, but that seems very complicated and I do not really know what's going on there so it's better I do not try it. And if I followed that tutorial I would have to flash the phone again with the miui 10, because I have the 11 now. I already wasted many hours trying to root the phone and I had to flash the rom about 4 times because the phone became bricked. Anyway the tutorials I've followed were not the one in the link above and all the other ones I've tried did not work and yet they claim it does, specially using magisk only, without TWRP.
I'll wait for an easier method than the one you shared, if that will ever happen. For now I just use a VPN, it's the closest thing to root I have found, to deny system and apps permission to the internet.
Thank you
In case you're not aware, there are scripts to flash the entire phone automatically, I've done that 10's of times BEFORE putting the phone into "production" use, root was a _must-have_,phone's now heavily used, so can't toy with it much, unless forced to (see below), i may get another phone to play with, but not much TIME to justify it...
Was getting tired of typing:
Code:
:/ # pm list packages|grep xyz
followed by:
:/ # pm uninstall -k --user 0 com.google.android.apps.tachyon
Success
Decided to give some "highly-rated" app a try, it claims to be able to remove system apps: "System app remover (root needed)":
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en_US
Took a full TWRP backup, installed, all seems great.. remove, goes to recycle bin, ok.. now, lets REBOOT..
Opps.. phones goes into FASTBOOT... OK!! that's what the backup is for.. go into TWRP, flush SYSTEM, CACHE, DATA, reboot, again, we're in Fastboot, and this time no RECOVERY boot is possible, just goes into FASTBOOT directly.. much like i've described in this thread:
https://forum.xda-developers.com/showpost.php?p=80509823&postcount=111
so, TWRP on phone doesn't help much, took the TWRP backup from SD Card to PC (since phone can only do fastboot at this point), thought it would be easy/possible to fastboot flash all the TWRP into the phone from PC, however, that is NOT simple, since TWRP breaks files, one must concatenate them before flashing..
I was not in the mood, nor did i think a huge change took place, it was just something silly that app did. hmm.. here, i can't exactly explain what took place, but a sequence of flashing of boot.img recovery.img and vbmeta.img all from STOCK and the TWRP backup, was "all it took" to recover the phone fully..
After about 30+ flashes and reboots it came to life much like the last boot, went into that APP again, tried to RESTORE the apps, it failed, and a reboot again, went into FASTBOOT! twrp was there, again, tried recovery, this time only SYSTEM, again, phone lost recovery, and went into, fastboot only... and.. again, sequence of flashing from fastboot, i can tell that vbmeta (Verify Boot) takes a *major* role in this version/device, if something is not right, it just reverts things or decides to go into fastboot.
I saw it work once, so was not going to give up and wipe/start fresh.. kept trying..
I think the app somehow made "direct" modifications to the system partition without proper interface, and thus ruined the "signature" or encryption, otherwise not sure how it could trash the phone so badly..
in any event, after long struggles, flashing the LATEST did _not_ work, it's almost as if the phone had to be taken back to original setting, let it boot into recovery, then reboot again, and flash things in steps, not all at once, at least based on this experience. I know it's silly, b/c in Android 6 I've restored/cloned phones all the time using TWRP directly from phone.. not sure, it does not work on my 7A's...
eventually, phone booted, with 10.2.5 magisk/boot.img (no root, since it did not recognize magisk), then fastboot flashed the canary boot.img, and got root.
anyways, point is, it was pretty ugly, and I'm not complaining, just saying this is pretty complicated stuff, it's a miracle that this even works
keep up the great work everyone, if i can help in any way, let me know...
All this is on Global phone, I don't have an EU/ROM/phone, so can't help u directly, but someone may have a root boot.img EU boot, that's really the key, and the vbmeta.img of course as for MIUI11? so what if that's what you have, it can be flashed, it's a matter of choice, flash to miui 10.2.5 and get root, or try to do it on MIUI11, or, let it be and use w/o root.. which was not an option for me
good luck.
Stormy.
btw, the magisk/patching boot.img did not work for me, and was reported in that same thread:
https://forum.xda-developers.com/showpost.php?p=80560039&postcount=206
MDV106 said that both EU and global boot.img were posted in that thread, and i agree i used one of them, not sure exactly which, but definitely it was the Global, not the EU. and i think it's not goot to mix up.. if u have an EU, stick with it, it might impact Wifi or similar "regional" things..
Same problem, but it works on mokee
Add-on-su on mokee open source ROM works fine, can enable root from developer options only, magisk and supersu don't work.
I have been trying to make them work but it seems impossible, I have looked in system/xbin and found no su files, maybe the problem is in the meta-INF because it doesn't properly know where to install it.
boody shaban said:
Add-on-su on mokee open source ROM works fine, can enable root from developer options only, magisk and supersu don't work.
I have been trying to make them work but it seems impossible, I have looked in system/xbin and found no su files, maybe the problem is in the meta-INF because it doesn't properly know where to install it.
Click to expand...
Click to collapse
Thanks for this data point, yeah, root was/is also possible with MIUI 10.2.5, I'm sure other ROMs can root pretty easily.. the "goal" of this thread is to somehow figure how to do it on MIUI 11 so we can take the security updates and still retain rootness
working root redmi 7a
Working root for Redmi 7a
thank you stormy1777 - it is your tutorial, I only put it together. It is the only tutorial that works
links unavailable due to site rules:
google for: ROM v10.2.5. global V10.2.5.0.PCMMIXM/pine_global_images_V10.2.5.0.PCMMIXM_20190805.0000.00_9.0_global_efb78ff9c3.tgz
google for: patched boot v10.2.5. under: xiaomifirmware (dot) com how-to-install-twrp-and-magisk-root-on-redmi-7a
google for: TWRP: under: androidweblog(dot)com xiaomi-redmi-7a-root-install-twrp-recovery I took the version 3.3.1.-0
google for Magisk: Magisk-v20.1.zip
Install in fastboot mode and with Mi Flash Tool
flash: pine_global_images_V10.2.5.0.PCMMIXM_20190805.0000.00_9.0_global
option: clean all
wait until the mobile phone is fully installed (will reboot automatically)
copy Magisk into the root directory on your phone
restart in fastboot mode (volume down + power button)
on PC:
rename twrp file to recovery.img
rename boot file to boot.img
copy boot.img and recovery.img on the PC in the directory, where adb drivers are
open power shell on the PC in the directory, where adb drivers are
type in the power shell window:
fastboot flash recovery recovery.img
Enter
then type in the power shell window
fastboot flash boot boot.img
Enter
then hold volume up + power button until it 2x starts and vibrates, then wait, it opens in TWRP
type install, find Magisk.zip in the phone root directory a flash
restart into system
done
New video guide below
VIDEO GUIDE
1. *VERY IMPORTANT* We need to back up your broken persist.img and store it in a safe place. PC preferred. We will need this later. Do not leave the backup on the device as the next step will wipe the device.
*IF YOU LOOSE THIS PERSIST.IMG BEFORE WE MODIFY IT WITH A CALIBRATION, YOU LOOSE ALL CHANCE OF FIXING THIS YOURSELF*
*IT HOLDS IMPORTANT FP CALIBRATION DATA THAT WE WILL BE OVERWRIGHTING IN THE NEXT FEW STEPS*
Note: This requires root
Type this into terminal or ADB shell with root privileges.
Code:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Backup the partition to another device. Preferably a PC as you may need one in the later steps.
2. Next we have to restore our OS to an earlier OOS. (10.5.4 is what I used and recomended)
Use the MSMTool to restore your device to 10.5.4.Note: You will loose your unlocked bootloader and will be required to unlock your bootloader once more.
Guide and Source for MSMTool
MSMTool 10.5.4 Download
3. Next step is to unlock the built in 'Factory Mode' I have a guide on how to do this below.
[GUIDE] Unlock Factory Mode *root*
4. Now we need to perform a FP calibration. We want to fail.
Enter Factory Mode as shown in the previous guide. (*#801# in the stock dialer)
Swipe over to "Device Debugging"
Select "Finger print test"
Select "Finger print calibration test(Pure White - 90% Blue)
Select "Start Test"
Keep on going through the tests (You must hold an object or your finger over sensor on all BUT THE BLACK RUBBER TEST of these test for it to work!)
The test will fail and this is what we want. There should be a lot of red lines, if you only have one or two try again.
5. We need to extract the the old broken persist.img
NOTE: It is important that we extract the backed up persist.img as it has been unmodified by our recent calibration. This persist.img although broken still has all our working calibrations on it including Finger Print calibrations.
The way I did this is by opening it extracting it via 7-ZIP on my PC
Once extracted move the 'DATA' folder and the 'ENGINEERMODE' folder to the root of your sdcard.
6. Download a root explorer. I highly recommend 'Solid Explorer' from the Play Store.
Open 'DATA' folder and delete 'gf_persist.so'
Select the 'DATA' and 'ENGINEERMODE' folders you just put on the device and place them at /mnt/vendor/persist/
It should ask you if you want to keep the old or new files. Select to keep the new.
Reboot.
7. If you followed all my steps correctly this you should be able to go into settings and add your fingerprints.
Why does this work?
Good question... I think what is happening is something in the persist partition breaks which causes the device to think that the sensor is not calibrated when in fact it still is.
When we start and fail a new calibration this fixes whatever was broken in our partition. But now we have a failed calibration.
So what we do is take the files from our backed up persist partition and move over all the necessary files that have our original calibration. But now our partition has the part of it that wasn't working fixed.
I spent a good many days working on this fix (1-2 hundred hours or so). I hope you can be respectful if you have issues. Please kindly ask below and I'll do my best to help.
Thanks worked on.my TMobile OnePlus.
I can confirm working on OOS 1.5.6 too. I downgraded from 10.5.9 with downgrade rom, which restores OOS to 10.5.6, and followed your guide and it worked as a charm. The only problem is that i cannot lock back the bootloader, cause it breaks FP again. Did you maybe try to lock it to try? Nice work man.
T-Mobile OnePlus 8 here. Stock firmware, orginally had my bootloader unlocked, rooted with TWRP and Magisk, backed up modem, converted to international firmware (10.5.7), lost signal, had to restore modem, ota'd to 10.5.9, unlocked bootloader again, rooted, etc. All while having a working FP the whole time. Ended up flashing EdXposed via Magisk, broke SafetyNet, etc, did a factory reset on TWRP (3.4.0-1 test), wiped data, rebooted recovery, rebooted system, booted back to TWRP. Installed Magisk to see if it'll boot with root, same thing. MSM'd back to T-Mobile firmware, then converted to international again. After the conversion was done and I unlocked bootloader and rebooted to system, my FP was broken. Ended up MSM'ing back to T-Mobile stock to see if it would work again, nothing.
TL;DR does this method only work if I had a working FP to begin with like it did stock out of the box?
TheKnux said:
T-Mobile OnePlus 8 here. Stock firmware, orginally had my bootloader unlocked, rooted with TWRP and Magisk, backed up modem, converted to international firmware (10.5.7), lost signal, had to restore modem, ota'd to 10.5.9, unlocked bootloader again, rooted, etc. All while having a working FP the whole time. Ended up flashing EdXposed via Magisk, broke SafetyNet, etc, did a factory reset on TWRP (3.4.0-1 test), wiped data, rebooted recovery, rebooted system, booted back to TWRP. Installed Magisk to see if it'll boot with root, same thing. MSM'd back to T-Mobile firmware, then converted to international again. After the conversion was done and I unlocked bootloader and rebooted to system, my FP was broken. Ended up MSM'ing back to T-Mobile stock to see if it would work again, nothing.
TL;DR does this method only work if I had a working FP to begin with like it did stock out of the box?
Click to expand...
Click to collapse
Just follow the guide, you'll have it working. You just have to backup your current persist
dzontra83 said:
Just follow the guide, you'll have it working. You just have to backup your current persist
Click to expand...
Click to collapse
So back it up even though it's broken? I'm on T-Mobile stock again, locked BL. Should I unlock, root, then pull persist and back it up?
TheKnux said:
So back it up even though it's broken? I'm on T-Mobile stock again, locked BL. Should I unlock, root, then pull persist and back it up?
Click to expand...
Click to collapse
Exactly, a T-Mobile user confirmed guide to work, check 2nd post
While on 10.5.7, unlocked bootloader, I flash TWRP, then reboot, and it boots back to TWRP. When I flash Magisk 20.4 zip in TWRP, it goes to boot, then enters CrashDump Mode. When I try and use the flash-all to downgrade to 10.5.4, I get a bunch of fastboot "cannot flash critical partitions" errors, it fails, and goes back to CrashDump Mode. What am I doing wrong? Also, is it really necessary to downgrade to an earlier version of OOS to use Engineering Mode or can I use 10.5.7?
TheKnux said:
While on 10.5.7, unlocked bootloader, I flash TWRP, then reboot, and it boots back to TWRP. When I flash Magisk 20.4 zip in TWRP, it goes to boot, then enters CrashDump Mode. When I try and use the flash-all to downgrade to 10.5.4, I get a bunch of fastboot "cannot flash critical partitions" errors, it fails, and goes back to CrashDump Mode. What am I doing wrong? Also, is it really necessary to downgrade to an earlier version of OOS to use Engineering Mode or can I use 10.5.7?
Click to expand...
Click to collapse
When you unlock bootloader, only boot into TWRP, then install magisk, i thin it Is still recommend to only boot into TWRP, not to flash it.
dzontra83 said:
When you unlock bootloader, only boot into TWRP, then install magisk, i thin it Is still recommend to only boot into TWRP, not to flash it.
Click to expand...
Click to collapse
Thank you so much, that worked! New problem, what do I do since I can't downgrade to an earlier OOS (10.5.4)?
Performing the test on T-Mobile 10.5.7, when performing the test, nothing is failing after pressing start test. Its all passing, what should I do?
When trying to downgrade using the 10.5.4 MSM Tool. it gives an error of "Unsupported Target TMO" and "param preload" and fails.
TheKnux said:
Thank you so much, that worked! New problem, what do I do since I can't downgrade to an earlier OOS (10.5.4)?
Performing the test on T-Mobile 10.5.7, when performing the test, nothing is failing after pressing start test. Its all passing, what should I do?
When trying to downgrade using the 10.5.4 MSM Tool. it gives an error of "Unsupported Target TMO" and "param preload" and fails.
Click to expand...
Click to collapse
Did you follow the instructions in test exactly? In second test you must't press the sensor.
Can help you with TMobile model, I have international one.
I figured it out. I was just being a dumbass I guess. Has anyone noticed the fingerprint sensor not being able to read that well compared to before it was broken? It seems like it fails a lot more before it succeeds. Unless now that it's working, we can perform the calibration again and it'll work better?
TheKnux said:
I figured it out. I was just being a dumbass I guess. Has anyone noticed the fingerprint sensor not being able to read that well compared to before it was broken? It seems like it fails a lot more before it succeeds. Unless now that it's working, we can perform the calibration again and it'll work better?
Click to expand...
Click to collapse
Don't know about that, mine works just fine
So I think I messed up, I ended up performing the calibration again, while it was already working, and now it says "fingerprint hardware not present" any suggestions on how to fix? I performed the instructions in the guide (again) and nothing worked. When the error pops up, if I press back, the error message goes away and the FP icon is there. When I tap on it, it lights up white but doesn't vibrate or register anything. I already used the MSM tool to go back to Tmobile stock, then used the fastboot ROM to go to Global 10.5.7, followed the guide again, still nothing.
TheKnux said:
So I think I messed up, I ended up performing the calibration again, while it was already working, and now it says "fingerprint hardware not present" any suggestions on how to fix? I performed the instructions in the guide (again) and nothing worked. When the error pops up, if I press back, the error message goes away and the FP icon is there. When I tap on it, it lights up white but doesn't vibrate or register anything. I already used the MSM tool to go back to Tmobile stock, then used the fastboot ROM to go to Global 10.5.7, followed the guide again, still nothing.
Click to expand...
Click to collapse
The initial backup of the persist.img should do the trick, if you repeat the process once again, it should work
dzontra83 said:
The initial backup of the persist.img should do the trick, if you repeat the process once again, it should work
Click to expand...
Click to collapse
I tried that, multiple times. Still not working. Is it possible for someone to upload their persist.img so I can try it or is it device specific? Granted, I pulled my initial persist.img from stock rooted Tmobile ROM AFTER I broke it even though it worked before (long story). I wasn't able to downgrade to 10.5.4 because when I tried using the MSM tool, it gave me a TMO device error and I couldn't use a fastboot ROM to go to 10.5.4 cause it kept entering CrashDump mode every time it tried rebooting to fastboot to finish the flash process .
TheKnux said:
I tried that, multiple times. Still not working. Is it possible for someone to upload their persist.img so I can try it or is it device specific? Granted, I pulled my initial persist.img from stock rooted Tmobile ROM AFTER I broke it even though it worked before (long story). I wasn't able to downgrade to 10.5.4 because when I tried using the MSM tool, it gave me a TMO device error and I couldn't use a fastboot ROM to go to 10.5.4 cause it kept entering CrashDump mode every time it tried rebooting to fastboot to finish the flash process .
Click to expand...
Click to collapse
Your cannot use someone else's persist, you must't use yours.
dzontra83 said:
Your cannot use someone else's persist, you must't use yours.
Click to expand...
Click to collapse
What about someone else's DATA and ENGINEERINGMODE folders? I've tried everything. Even recalibrating multiple times. It's not giving me a bunch of errors like it did before, just one error. The last error is FAIL! OPERATION_STEP_GET_KB_CALIBRATION TEST FAIL:GF_ERROR_GENERIC
Just wondering, what is the point of downgrading to an earlier OOS? If I was able to do it on the Tmobile firmware with success, is there an importance in downgrading?
Thank you so very very much!!! I have a T-Mobile 7T Pro 5G McLaren which hasn't had a working fp in almost 2 months. I hadn't made a backup of persist before the fp broke, so I thought I was completely screwed. Luckily, I did make a backup of persist before trying to use the fp calibration tool myself without any luck shortly after it broke (basically just clicking stuff and guessing lol). Found this thread and I had my FP scanner working again perfectly in less than 15 minutes!!!! Thank you soooo much for all the hours and effort you put into figuring this out!!!!!!!
Didn't have to run the msm tool to revert to older version of OOS and lose all my data either!!
Just one question and it's just for my curiosity. Why do we delete "gf_persist.so" from our original persist.img before copying/pasting into /persist partition after "calibration"? Is gf_persist.so not a file containing part of the original calibration? Is that the file which is being fixed by running the hidden calibration commands?
If anyone can help me, it would be much appreciated. https://forum.xda-developers.com/oneplus-8/help/broken-persist-img-problems-t4129587