Having some issues while trying to root my 7T, I followed the guide here and everything seemed to work perfectly until I tried adding a fingerprint, at which point I was met with this message. It comes up straight away before I can even attempt to press the fingerprint sensor.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I thought maybe I did something wrong and went back to stock, but I still encountered the issue. I then re-locked the bootloader and the fingerprint sensor became fully functional again. I've tried to search for solutions but I can't find other people experiencing this on the 7T.
I've also tried using a different OS, I went with MSM Xtended v12.0 which allows the fingerprint screen to open but it won't actually register any touches at all.
I've seen mention of a fix to the error relating to persist.img on other Oneplus phones but I'm unsure if this would apply to me seeing as the sensor works perfectly with a locked bootloader, basically I'm stuck at this point and would appreciate any advice
I have an unlocked bootloader and have no issues with my sensor. TMobile converted to International.
Revert to stock and try again.
jcotterman said:
I have an unlocked bootloader and have no issues with my sensor. TMobile converted to International.
Revert to stock and try again.
Click to expand...
Click to collapse
Yeah it seems to be working perfectly for everybody else on this device which is why I'm so confused.
I've gone from MSM Extended back to stock OOS 10.0.8 (HD65BA) and I still get the same error that's in the OP, I've now re-locked the bootloader and it's back to working again
RainingTerror said:
Yeah it seems to be working perfectly for everybody else on this device which is why I'm so confused.
I've gone from MSM Extended back to stock OOS 10.0.8 (HD65BA) and I still get the same error that's in the OP, I've now re-locked the bootloader and it's back to working again
Click to expand...
Click to collapse
It can be that something in /persist is broken. It happened to several others too but mostly it is a user error. This message pops up if the fingerprint sensor calibration data is missing or broken. You can try this guide to try to fix it (unless you have a persist.img backup which you can use): https://forum.xda-developers.com/on...de-fix-persist-img-loss-finger-print-t4125909
Keep in mind that the MSM tool doesn't touch /persist so using it isn't going to fix the issue if it due to /persist. But first try to unlock your bootloader again and see if this error pops up again. Maybe it fixed itself
Related
Hello experts,
I hard bricked my phone, but with the tool I managed to repair it. But after unbricking it while starting phone, it got stuck in boot logo and screen appear to be broken but its not.
This is how phone look like and everytime it happene same.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https ://drive.google.com/open?id=0B_S-tkD3eHy5Y3h3NnB3Y013Uy1qbTZycnpTWHN3OXlEc05F
What to do in this case? I don't have any idea now.
Please provide any solution.
unnat1993 said:
Hello experts,
I hard bricked my phone, but with the tool I managed to repair it. But after unbricking it while starting phone, it got stuck in boot logo and screen appear to be broken but its not.
This is how phone look like and everytime it happene same.
https ://drive.google.com/open?id=0B_S-tkD3eHy5Y3h3NnB3Y013Uy1qbTZycnpTWHN3OXlEc05F
What to do in this case? I don't have any idea now.
Please provide any solution.
Click to expand...
Click to collapse
It appears to get to the part where it starts to load the OS. In this case try to get into recovery. If you can get into recovery, great! Then just adb sideload the latest ROM from OnePlus.
ZVNexus said:
It appears to get to the part where it starts to load the OS. In this case try to get into recovery. If you can get into recovery, great! Then just adb sideload the latest ROM from OnePlus.
Click to expand...
Click to collapse
Did it, but after sideloading latest ROM from oneplus, it runs perfectly for sometime and again doing same thing.
Un brick by method 2
unnat1993 said:
Did it, but after sideloading latest ROM from oneplus, it runs perfectly for sometime and again doing same thing.
Click to expand...
Click to collapse
This actually sounds like a hardware issue to me, but I have no idea what I am talking about so idk.
drmuruga said:
Un brick by method 2
Click to expand...
Click to collapse
Did it, problem persist. :crying:
I'm not see the video but why you flash twrp and flash any other rom and try ?
Finally, OnePlus has told me that motherboard is not working. So have to change phone.
Phone always greets me with this pixelloided screen.
Its becoming an issue slowly.
Whenever I press the power button i get this screen. It persists for a while and goes off by itself.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
meher777 said:
Phone always greets me with this pixelloided screen.
Its becoming an issue slowly.
Whenever I press the power button i get this screen. It persists for a while and goes off by itself.
Click to expand...
Click to collapse
These are the screen snaps
hemanth.k said:
These are the screen snaps
Click to expand...
Click to collapse
do you have a custom rom?
Mr bubbles said:
do you have a custom rom?
Click to expand...
Click to collapse
No
hemanth.k said:
No
Click to expand...
Click to collapse
odd then that usual happens on custom roms you might need to re flash stock rom then.
Mr bubbles said:
odd then that usual happens on custom roms you might need to re flash stock rom then.
Click to expand...
Click to collapse
How to do that without unlocking BL?
hemanth.k said:
How to do that without unlocking BL?
Click to expand...
Click to collapse
Not that I'm aware of, you might want to try a Factory Data Reset first. After doing the appropriate backups first of course.
If that fails, unlock the BL, flash stock. Once you verify it works lock the BL again. You might have to FDR again to get the Play Store to show Certified if clearing data under Apps doesn't work.
I wish I could still trust my Robin, but I have a battery heating issue that nothing seems to fix. Hence my signature showing my former backup phone as my DD.
Sent from my ZTE B2017G using XDA Labs
Hello, I will use the Google translator because I am Brazilian
Today I ended up trying to install a custom rom on my moto g8, but it ended up giving some errors and I ended up blocking my bootloader manually, but now it doesn't start the phone and I can't install any stock rom with the bootloader blocked, all end up showing an error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This website has instructions to flash stock firmware on Sofia. Everything but the link to download firmware should apply to Rav. https://www.droidwin.com/install-stock-firmware-on-motorola-g8-power-via-fastboot-commands/
Not because my bootloader is not unlocked
andr3ycarvalho said:
Not because my bootloader is not unlocked
Click to expand...
Click to collapse
A week ago I bricked my Moto g fast by attempting to flash RetUS firmware without unlocking the bootloader first. Even though most of the fastboot commands failed a handful succeeded and that was enough to prevent my phone from booting to anything but bootloader mode.
I downloaded and flashed the official Boost firmware from lolinet and while the flash succeeded my phone was still bricked.
I installed the Lenovo Motorola Rescue and Smart Assistant tool from https://support.lenovo.com/us/en/downloads/ds101291 and used it to download official firmware for my phone but the rescue tool failed at 14%.
I tried a few other things that also didn't help before I ran the LMSA rescue tool again. This time it took several minutes to complete and my phone worked again. I am not sure why it failed at first but happy to have a working phone again.
hello, i'm also brazilian and i have a problem similar to yours, after leaving a custom rom the other day, and reinstalling the stock and blocking the bootloader, my phone called with the message that it was corrupted and it wouldn't start and now i can only access his bootloader and I can't flash anything, not even the stock rom, I don't know how to solve it, but I'm in a situation similar to yours
Hello, I have a problem with my Moto G8 (XT 2045-1). I tried to install a stock rom to fix a bug, however the phone no longer connects in bootloader mode, nor does it unlock the same and I can't even install any stock rom. Can someone help me?
SIM card not detect and WIFI does not work after returning from AOSP to STOCK Adroid Pie
Restoring copies in TWRP does not help.
After installing other versions of Android, SIM CARD and WIFI also not working
Help please ;(
Pawel_pecet20 said:
SIM card not detect and WIFI does not work after returning from AOSP to STOCK Adroid Pie
Restoring copies in TWRP does not help.
After installing other versions of Android, SIM CARD and WIFI also not working
Help please ;(
Click to expand...
Click to collapse
What variant do you have?
H930.
I have now installed HAVOC OS and the phone is restarting with the GOOGLE logo
I installed V31a and in the settings does not see the MAC addresses for the WIFI card and the address for the BLUETOOTH
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It also doesn't see the firmware version and bandwidth
Never heard of any such issue. Try flashing kdz.
After installing software using LGUP, the phone keeps resetting itself
It works!!! For those in need: I turned on LGUP and selected the "ChipErase" option
Pawel_pecet20 said:
It works!!! For those in need: I turned on LGUP and selected the "ChipErase" option
Click to expand...
Click to collapse
But now you have wiped your IMEI and serial number. In all my guides I warn people not to use that option.
Right. I haven't checked it out. There is no IMEI or SN now. Can it be restored somehow?
Such things are not allowed to be discussed here on XDA, as far as I have heard. You'll have to find another site to see if there's a way to do that.
In the future, don't go running around without knowing what you're doing, because you will break things, as you have just now done. Most people should never use Chip Erase, as detailed on many threads here.
Success with adding IMEI. Now there is still SN
schwinn8 said:
Such things are not allowed to be discussed here on XDA, as far as I have heard. You'll have to find another site to see if there's a way to do that.
In the future, don't go running around without knowing what you're doing, because you will break things, as you have just now done. Most people should never use Chip Erase, as detailed on many threads here.
Click to expand...
Click to collapse
Yeah this sounds a lot worse than playing with Windows Regedit.
Cloned hdd copies are a beautiful thing...
Anyone else had this issue, or any known fix for this? Had just flashed SparkOS.
Hello,
Install xiaomi.eu rom, you should be able from-> fingerprint unlock->payment with fingerprint to redownload widevine certificate. My language is italian maybe name of settings are a little bit different from what I write
Bye
Claudio67 said:
Hello,
Install xiaomi.eu rom, you should be able from-> fingerprint unlock->payment with fingerprint to redownload widevine certificate. My language is italian maybe name of settings are a little bit different from what I write
Bye
Click to expand...
Click to collapse
Right on cue, just got my phone working again. I saw this method, and flashed EU ROM via orange fox from Spark OS. Phone sadly got bricked. At the time, MiFlash wasn't recognizing my device and all I could do was fastboot.
Lots of YouTube and 3 hours later, finally was able to sideload stock ROM, then MiFlashed to clean everything, then installed SparkOS again. L1 is back.
I'm thinking the L1 certificate got lost due to Magisk?
Nice, I don't think it's a magisk issue, I've installed and still widevive is l1
Cool! I think I'll pass Magisk for now haha. The trauma!
In any case, if ever I do get Magisk again, can I see what ur modules are?
I'm using sparkOS too, still have it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
lkamio said:
I'm using sparkOS too, still have it
View attachment 5845023
Click to expand...
Click to collapse
Got mine fixed. Looks like I messed up something during flashing.
glidarts0730 said:
Cool! I think I'll pass Magisk for now haha. The trauma!
In any case, if ever I do get Magisk again, can I see what ur modules are?
Click to expand...
Click to collapse
Hi,
I use safetynet fix (needed with magisk) and viper4android