Related
Ok, I'm going to preface this thread with the statement "I am a noob".
Now... I'm working on unlocking the bootloader so that I can start checking out roms (Virtuous Prime and Cornerstone). I rooted the tablet last night, and then tried to unlock the bootloader, but keep getting the message "Failed to unlock your device, please try again later". What is the problem here? It's been mentioned to me to try flashing the Asus .15 update from the site onto the tablet, and then trying a factory reset afterwards if that doesn't work. Anyone else had this problem and fixed it? I have tried unrooting and doing it also. When I try this, I am connected to the internet. Also, I am on the latest .15 update via an OTA update. I have not tried to unlock the boot loader or root previous to last night.
Thanks.
i to am having the same issue ! any help would be apprieciated.
Deathbyfugu said:
Yes, I did get it solved. I had to download the full 9.4.2.15 update from Asus, extract the .zip and rename the other .zip contained within it to "SD201_UPDATE.zip" and place it on the Micro SD. Then reboot the Prime and hold Vol Down and Power until some text appears on the upper left and then press Vol Up. This will reflash the official firmware and after that is done you can either try once more or do a factory reset. After a factory reset (if it didn't work after the initial process) it should work without an issue.
Click to expand...
Click to collapse
This is what I was told via a PM as he also had the same problem. I don't have an sd card here large enough to put the whole update on to flash (if I'm even understanding how this all works correctly)(it's only 512MB and the update is 547 or so).
I didn't want to do a factory reset quite yet as I need to backup the photos and things on my tablet. Although, I'm not sure; I may lose everything once I install a rom? I'm still researching all of this...
Go to Settings, About and check to see if you have a serial.
If not..
http://androidroot.mobi/2012/01/31/introducing-ratchet-the-unknown-serial-fix/
Have a nice day
Under "Status", the field that says "Serial number" is filled in with my correct/matching serial number, yes.
yes same here i had an unkown serial issues but i fixed that a couple days ago and havent been able to unlock this mug
I'll be giving the method mentioned to me via PM a try this evening when I get home from work if I don't have any other answers regarding how to make it work, and report back. Already backed up most of my important data.
Having the exact same problems plus I'm having trouble getting ANY updates working prior to wanting to unlock my bootloader... thought unlocking and update with new ROM would solve things...
Add me to the list of: "Failed to unlock your device. Please try again later"- serial number is listed and correct... :-/
Sent from my HTC ThunderBolt using Tapatalk
Sounds like something isn't working right on the server side. Maybe Asus is doing maintenance on the server or it crashed or they even disabled it.
Of course, when I finally decide, "OK, it's relatively safe to unlock, flash CWM and get some custom ROMs on here..." the unlock tool stops working. Hopefully just a temporary thing
Sent from my Transformer Prime TF201 using Tapatalk
Same issue here
I too am getting the issue. I re-downloaded .15 firmware, reinstalled, and factory reset and still no luck. Hoping its just something on the Asus end of things. really want some custom rom love on my prime.
same thing here everyone ughh
Hmm, well I guess at least it's not just me. Fudge, was really looking forward to getting this going.
Reloaded83 said:
Hmm, well I guess at least it's not just me. Fudge, was really looking forward to getting this going.
Click to expand...
Click to collapse
Yea me to. i wonder why its happening. I never had a serial issue and i received all the updates no problem
AndroidPhan said:
Yea me to. i wonder why its happening. I never had a serial issue and i received all the updates no problem
Click to expand...
Click to collapse
Same here.
I have a feeling Asus retracting the tool. or not allowing people to unlock anymore from all the complaining going on.
demandarin said:
I have a feeling Asus retracting the tool. or not allowing people to unlock anymore from all the complaining going on.
Click to expand...
Click to collapse
Why ASUS, why must you do such a thing?
For me the same problem, I received ota updates at .15 and I can not unlock. Solutions?
Thanks
Worked this morning 3/2/12 at 7:15 am Eastern time
Woke up this morning and figured I'd try again to unlock my prime, and what do you know, worked the very first time. Looks like maybe it was things on the Asus end. Please let me know if anyone else gets this to work today.
i want to update my unlocked atrix to 2.3.6 but i see that people say that it's gonna brick my phone so there is no way to update it?
my atrix is on stock 2.3.4
unlocked
rooted i guess
career unlocked by unlock code
plz someone help me :S
If you use a fruitcake, you'll be fine. If you wipe all data/system/etc and use the sbf, you will also be fine. The worst I've heard of is a soft brick that takes a hell of a lot of time and effort to fix. So, I'd go with fruitcake if I were you. I did it yesterday, and it worked like a charm.
http://forum.xda-developers.com/showthread.php?p=22552497#post22552497
Fun498 said:
If you use a fruitcake, you'll be fine. If you wipe all data/system/etc and use the sbf, you will also be fine. The worst I've heard of is a soft brick that takes a hell of a lot of time and effort to fix. So, I'd go with fruitcake if I were you. I did it yesterday, and it worked like a charm.
http://forum.xda-developers.com/showthread.php?p=22552497#post22552497
Click to expand...
Click to collapse
what about OTA ? will it hard brick my phone?
soudy1994 said:
what about OTA ? will it hard brick my phone?
Click to expand...
Click to collapse
There is risk that it can
Sent from my MB860 using Tapatalk
Fun498 said:
If you use a fruitcake, you'll be fine. If you wipe all data/system/etc and use the sbf, you will also be fine. The worst I've heard of is a soft brick that takes a hell of a lot of time and effort to fix. So, I'd go with fruitcake if I were you. I did it yesterday, and it worked like a charm.
http://forum.xda-developers.com/showthread.php?p=22552497#post22552497
Click to expand...
Click to collapse
Do you still have that file and can you post it some where?
The file you linked to is not valid anymore and I'm in desperate need to get it.
Thanks for any help
there is no other way? cuz i never used adb before and i'm afraid i will do something wrong
c'mon guys i need help
A few pages later on the new link is posted. I forget exactly where. It's a mediafire link if I remember correctly. And I wouldn't risk a hard brick if I were you. I flashed a SBF to return my broken phone back to Motorola and attempt warranty, but the phone was useless either way. It worked, but I had to wipe nearly every partition. Please don't risk. Fruitcake is proven
this thread isn't TOO dead
I thought there was a way to officially update the atrix to 2.3.6 since that is the official version O/S it supports?
Just picked one up yesterday and it has 2.3.4
redking117 said:
this thread isn't TOO dead
I thought there was a way to officially update the atrix to 2.3.6 since that is the official version O/S it supports?
Just picked one up yesterday and it has 2.3.4
Click to expand...
Click to collapse
Yeah I just went into "about phone" and hit update... what's wrong with that?
Can't you still root 2.3.6?
If your phone is working fine now do yourself a favor and leave it alone. OTA update has caused many problems like killing wifi and many people have had problems playing with roms and you can't go back. This is good advice.
Sent from my MB860 using XDA
I was subscribed to this and just want to add my data point:
on unlocked (bootloader) phone ("Unlocked" printed on boot screen), upgraded to 2.3.6 over the air. This caused Unlocked to disappear from boot screen but I believe I was still technically unlocked. I went through the unlock process again just to be safe. which put "unlocked" back on boot screen, then unrooted by normal flash recovery method, and running fine an dandy all along
I did have a problem with a bad sim card previously, which made it seem like 2.3.6 was a problem, but it is not, for me at least.
I bought a Razr Maxx from Amazon, it came from Hong Kong with AsiaRetail ROM, it works fine with except the encoding of music tags. I want to switch to the same Motorola's Android version but from another region (For example: US). I was reading a few procedures, but all they explains migratations from GB to ICS and I am already on ICS (673.94.328.XT910.AsiaRetail.en.03). Does anybody knows any procedure to download and install Motorola's Android stock ROM?
Thanks in advance.
You can use RSDLite to install any european ICS version. I did it in mine too, from an Asian ROM to Retail.eu (Rtail British)
http://forum.xda-developers.com/showthread.php?t=1850683
http://sbf.droid-developers.org/umts_spyder/list.php
EDIT: also this one I posted a while ago: http://forum.xda-developers.com/showthread.php?p=31477142#post31477142
davizera said:
You can use RSDLite to install any european ICS version. I did it in mine too, from an Asian ROM to Retail.eu (Rtail British)
http://forum.xda-developers.com/showthread.php?t=1850683
http://sbf.droid-developers.org/umts_spyder/list.php
EDIT: also this one I posted a while ago: http://forum.xda-developers.com/showthread.php?p=31477142#post31477142
Click to expand...
Click to collapse
Thank you so much. It worked just fine, I had issues on the first boot but I applied a factory reset and it solved.
I have 2 questions:
- Is it totally secure the sbf files from droid-developers? (I had never hear it before)
- I can't share my data conection, i don't have Internet on my computer through the phone
rcdeoliveira said:
Thank you so much. It worked just fine, I had issues on the first boot but I applied a factory reset and it solved.
I have 2 questions:
- Is it totally secure the sbf files from droid-developers? (I had never hear it before)
- I can't share my data conection, i don't have Internet on my computer through the phone
Click to expand...
Click to collapse
I really think that the sbf files are safe, there's no reason to think differently. It's not like they would put a worm on it, but I think they are pretty safe, coming from a leak.
About the data connection, did you try changing from open to WEP to WPA and so on?
davizera said:
I really think that the sbf files are safe, there's no reason to think differently. It's not like they would put a worm on it, but I think they are pretty safe, coming from a leak.
About the data connection, did you try changing from open to WEP to WPA and so on?
Click to expand...
Click to collapse
Ummmm, i didn't try that, but i have connection to the gateway IP (ping), but i can't go beyond it.
I have another issue, encryption for applications and disk doesn't work, I always get a black screen and never finish the process.
davizera said:
I really think that the sbf files are safe, there's no reason to think differently. It's not like they would put a worm on it, but I think they are pretty safe, coming from a leak.
Click to expand...
Click to collapse
Various components of the firmware need to be signed by Motorola in order to be flashable via fastboot. That's one of few pros of a locked bootloader.
rcdeoliveira said:
Ummmm, i didn't try that, but i have connection to the gateway IP (ping), but i can't go beyond it.
I have another issue, encryption for applications and disk doesn't work, I always get a black screen and never finish the process.
Click to expand...
Click to collapse
Try a different set if sbf files. You may have gotten a corrupt down load. Or possibly a modded set.
Sent from my DROID RAZR using xda app-developers app
sttierney said:
Try a different set if sbf files. You may have gotten a corrupt down load. Or possibly a modded set.
Click to expand...
Click to collapse
Mate, you clearly don't know what are you talking about - please stop giving wrong advice. There are checksums and digital signatures in place, which are verified by RSD Lite and phone prior to flashing, thus modified/damaged file won't be accepted by the device. Only genuine files, which were signed by Motorola, can be flashed to the phone in the fastboot mode.
@rcdeoliveira: With regard to your network issue, please debug your upstream connection - e.g. TTL. This feature definitely works for me. Regarding the whole device encryption, initial run may take up a lot of time, so be sure to leave the device at the "black screen" overnight attached to a charger.
I need help. I just bought used droid razr maxx. Then When I got home, i realize it cant be rooted,something bout the su binary cant be pushed?Then I did some research,and I realize,since my razr maxx is from china,it somehow is different? Anybody know how to change this? For god sake,I cant even install some simple apps such ass foursquare?? Can I just place Any region update files in the MicroSD n update?My firmware is GAS_ASIA_SPYDERICS_P008 n System version 67.213.906.XT910.ChinaRetail.en.CN . I read about flashing using fastboot but my pc cant detect my fone when in flashboot,why is that? All the drivers are already installed. Now I cant root or use custom ROM. T_T
Hi ,guys, got a real big problem here
Before this bug happen, i set smartlock via security setting.
but then, its kinda annoying so i try to remove it, but some smartlock (none, pattern, password) setting is disable, said restriction administrator bla bla bla..
so i decide to remove all certificate through security settings, after that only administrator restriction bla bla bla not displayed, then i continue to set lockscreen as slide only, no password or pattern at all.
and then i reboot my device, works ok.. BUT here things get funny, i press power button to lock and turn off screen, its show the lockscreen and half second later screen is off
so i try to turn on screen again with power button, its still not wake up.
so i try again and again,wait wait wait, nothing happen, so i try to press volume button, yah i can hear the sound.
so i try to reboot again, the same thing happen when i turn off screen, so i decide to call my z ultra, its ringing but the screen wont turn on.
So i though this must be some setting that got messed up
i factory reset, wont help either
so i try reflash Lolipop 14.5.A.0.242 via Flashtool
same issue happen, but this time its waking up, but need to wait half minute, but mostly the screen wont ever turn on again.
and then i decide to reflash kitkat,
the issue not fully fix, coz i need to wait a little like half second to wakeup the screen.
Tested again, on kitkat, everythings working fine, the issue gone.
I already try to reflash Lolipop with locked bootloader, unlocked bootloader
The issue still persist on Lolipop , the screen wont turn on after locked, even after reflash, while on setup wizard, if I turn off the screen, it wont turn on again doesnt matter how many time I press and wait.
its all start with after i remove the certificate on security settings.
anyone got idea?
its really annoying.
Please Help..
curiouso9 said:
Hi ,guys, got a real big problem here
Before this bug happen, i set smartlock via security setting.
but then, its kinda annoying so i try to remove it, but some smartlock (none, pattern, password) setting is disable, said restriction administrator bla bla bla..
so i decide to remove all certificate through security settings, after that only administrator restriction bla bla bla not displayed, then i continue to set lockscreen as slide only, no password or pattern at all.
and then i reboot my device, works ok.. BUT here things get funny, i press power button to lock and turn off screen, its show the lockscreen and half second later screen is off
so i try to turn on screen again with power button, its still not wake up.
so i try again and again,wait wait wait, nothing happen, so i try to press volume button, yah i can hear the sound.
so i try to reboot again, the same thing happen when i turn off screen, so i decide to call my z ultra, its ringing but the screen wont turn on.
So i though this must be some setting that got messed up
i factory reset, wont help either
so i try reflash Lolipop via Flashtool
same issue happen, but this time its waking up, but need to wait half minute, but mostly the screen wont ever turn on again.
and then i decide to reflash kitkat,
the issue not fully fix, coz i need to wait a little like half second to wakeup the screen.
Tested again, on kitkat, everythings working fine, the issue gone.
I already try to reflash Lolipop with locked bootloader, unlocked bootloader
The issue still persist on Lolipop , the screen wont turn on after locked, even after reflash, while on setup wizard, if I turn off the screen, it wont turn on again doesnt matter how many time I press and wait.
its all start with after i remove the certificate on security settings.
anyone got idea?
its really annoying.
Please Help..
Click to expand...
Click to collapse
Which lollipop rom did you try flash.
RealityFails said:
Which lollipop rom did you try flash.
Click to expand...
Click to collapse
owh, sorry for not put it in details, sony stock rom 14.5.A.0.242
I also did try twrp, wipe, system, data. still not fixing the issue
fresh install using FTF 14.5.A.0.242 also failed to fix the issue. :crying:
whens screen turn of, it wont wake up, but the touch is registered.
Lolipop only, on kitkat fresh install, all working fine..
curiouso9 said:
owh, sorry for not put it in details, sony stock rom 14.5.A.0.242
I also did try twrp, wipe, system, data. still not fixing the issue
fresh install using FTF 14.5.A.0.242 also failed to fix the issue. :crying:
whens screen turn of, it wont wake up, but the touch is registered.
Lolipop only, on kitkat fresh install, all working fine..
Click to expand...
Click to collapse
I'm guessing your BL is locked. Reflash a kk ftf once on kitkat root, dual recovery. You can flash a pre rooted lollipop ROM its in the download section.
RealityFails said:
I'm guessing your BL is locked. Reflash a kk ftf once on kitkat root, dual recovery. You can flash a pre rooted lollipop ROM its in the download section.
Click to expand...
Click to collapse
Already tested your step above, pre-root lolipop flashed with twrp, of course my bootloader is unlocked.
same thing keep happening.
Before, I already test stock Lolipop (fresh install with Flashtool) for 2 weeks with no issue at all,
but its all happen after i remove credentials to fully disable smartlock, then this thing start happening.
Got any other idea?
RealityFails said:
I'm guessing your BL is locked. Reflash a kk ftf once on kitkat root, dual recovery. You can flash a pre rooted lollipop ROM its in the download section.
Click to expand...
Click to collapse
I didn't know xda has a download section?
Can you please help me find it? I am looking for ftf files for kk and lollipop for your phones.
TIA!
BragaisG said:
I didn't know xda has a download section?
Can you please help me find it? I am looking for ftf files for kk and lollipop for your phones.
TIA!
Click to expand...
Click to collapse
For FTF you can download using XPeriFirm tool, just google it
then compile it using FlashTool
back to my problem. anyone got any other idea?
curiouso9 said:
For FTF you can download using XPeriFirm tool, just google it
then compile it using FlashTool
back to my problem. anyone got any other idea?
Click to expand...
Click to collapse
Did you redownload the ftf? If it continues it maybe hardware related
BragaisG said:
I didn't know xda has a download section?
Can you please help me find it? I am looking for ftf files for kk and lollipop for your phones.
TIA!
Click to expand...
Click to collapse
Why do you want ftf? If your bootloader is unlocked you can flash any xzu ROM......flash ftf for lb and repairs
RealityFails said:
Did you redownload the ftf? If it continues it maybe hardware related
Why do you want ftf? If your bootloader is unlocked you can flash any xzu ROM......flash ftf for lb and repairs
Click to expand...
Click to collapse
I do have a locked BL the reason I need FTF.
I am currently in Lollipop and am looking into downgrading to KK, root, unlock BL, and bla bla bla...
Then flash Lollipop again to obtain root.
BragaisG said:
I do have a locked BL the reason I need FTF.
I am currently in Lollipop and am looking into downgrading to KK, root, unlock BL, and bla bla bla...
Then flash Lollipop again to obtain root.
Click to expand...
Click to collapse
Oh it's the other hand guy.
Yeah use an Ftf. There's a one for the C6806 C6833 not sure about the others. Flash the kitkat, use easy root tool, install recovery and you can flash a stock/Sony signed rom. If you unlock your bootloader you can flash anyone in the section. If you don't want to unlock the bootloader I'd stay on kitkat.... That's just me though
seems not many take interest of this issue
well this quite tough one i ever had since owning an Android
solution that i did try
- hard reset
- reflash stock lolipop via sony pc companion
- reflash stock lolipop via flashtool
- reflash stock lolipop via twrp
- relfash custom rom (lolipop) cm 12.1 based, well the issue did not happen on the custom rom, but when i reflash back to stock lolipop, it happen again.
so i turn back thinking what did triggering the issue for first time.. SMART LOCK
I reflash back to stock lolipop rom, navigate to security
then I playing the smartlock, i activated all option in it,
so this step having me to install Google now and set it as default launcher, for waking the device via voice command
after i done it alll, i try to turn off the screen., then i try to turn it on via power button, yeah, no more delay.
So after that i disable smart lock, then reflash back to kitkat, and lolipop for rooting.
Done, thanks for those who willing to help
I also did disscuss this on official sony forum
well the solution they had is to send to service center
funny, because i already explain its due to smartlock
maybe some partition, memory that store smartlock setting
so what i did to resolved this, is by triggering back the smartlock settings.
curiouso9 said:
seems not many take interest of this issue
well this quite tough one i ever had since owning an Android
solution that i did try
- hard reset
- reflash stock lolipop via sony pc companion
- reflash stock lolipop via flashtool
- reflash stock lolipop via twrp
- relfash custom rom (lolipop) cm 12.1 based, well the issue did not happen on the custom rom, but when i reflash back to stock lolipop, it happen again.
so i turn back thinking what did triggering the issue for first time.. SMART LOCK
I reflash back to stock lolipop rom, navigate to security
then I playing the smartlock, i activated all option in it,
so this step having me to install Google now and set it as default launcher, for waking the device via voice command
after i done it alll, i try to turn off the screen., then i try to turn it on via power button, yeah, no more delay.
So after that i disable smart lock, then reflash back to kitkat, and lolipop for rooting.
Done, thanks for those who willing to help
I also did disscuss this on official sony forum
well the solution they had is to send to service center
funny, because i already explain its due to smartlock
maybe some partition, memory that store smartlock setting
so what i did to resolved this, is by triggering back the smartlock settings.
Click to expand...
Click to collapse
This bug is fixed in .270 firmware.
i already check the changelog, didnt mention above issue.. did i miss something?
and did this bug affecting your device too ?
curiouso9 said:
i already check the changelog, didnt mention above issue.. did i miss something?
and did this bug affecting your device too ?
Click to expand...
Click to collapse
Well in official changelog they didn't mention many things. They just wrap it as bug fix and performance improvements. No i wasn't affected, but some guy from Czech Xperia forum was and he said that after flashing .270 firmware his problem was fixed. And i know SONY were fixing this particular bug in firmware for newer Xperia series (Z3/Z3).
Well atleast you can try.
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.