Hi. I use Redmi Note 3 (Snapdragon).
I want to install CM 13.0 by Santhosh M, so I unlocked my device officially.
I checked my device unlocked sucessfully via "fastboot oem device-info" . it says,
"...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.050s]
finished. total time: 0.053s
"
Then I installed TWRP 3.0.0.2-2 using FLASHER TOOLKIT v1.05, then I also flashed Alka recovery update.
But either recoveries didn't show battery status. Right-top is just blank..
Ignoring battery status, I'm going on installing CM13.0. But after installed, battery status is stucked at "-2%". Also fingerprint isn't working.
ONLY IT HAPPENS ON CUSTOM ROM. NOT ON STOCK ROM. MIUI stock rom shows battery stats correctly, and fingerprint works.
I guess bootloader unlock has a bug. Can anybody help me?
geinna.dev said:
Hi. I use Redmi Note 3 (Snapdragon).
I want to install CM 13.0 by Santhosh M, so I unlocked my device officially.
I checked my device unlocked sucessfully via "fastboot oem device-info" . it says,
"...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.050s]
finished. total time: 0.053s
"
Then I installed TWRP 3.0.0.2-2 using FLASHER TOOLKIT v1.05, then I also flashed Alka recovery update.
But either recoveries didn't show battery status. Right-top is just blank..
Ignoring battery status, I'm going on installing CM13.0. But after installed, battery status is stucked at "-2%". Also fingerprint isn't working.
ONLY IT HAPPENS ON CUSTOM ROM. NOT ON STOCK ROM. MIUI stock rom shows battery stats correctly, and fingerprint works.
I guess bootloader unlock has a bug. Can anybody help me?
Click to expand...
Click to collapse
There is a problem with a bunch of RN3 because they use different Fp sensor and don't support custom Rom, and I'm one of those but i contacted a developer and he said i will try and fix that problem so Finger crossed
Sent from my Redmi Note 3 using Tapatalk
Thanks Liri2000
LiRi2000 said:
There is a problem with a bunch of RN3 because they use different Fp sensor and don't support custom Rom, and I'm one of those but i contacted a developer and he said i will try and fix that problem so Finger crossed
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
I see. Thank you for answering Liri2000! It is very helpful for me.
Having same problem on all custom ROMS.
Battery is stuck either on -2% or 50%
Also, no battery indicator in TWRP.
Can't find the solution
Same problem here. I've tried unlocking the bootloader unofficially at first, then officially. No luck either way.
I'm referring to the battery bug, didn't even try the fingerprint reader. This is so uncool.
Same here...
MIUI already fixed it, cant wait to get fixed for custom roms.
Sent from my Redmi Note 3 using Tapatalk
FYI I flashed TWRP and then installed Xiaomi.eu ROM. Although TWRP didn't show any battery indicator on the top right corner (tested with multiple versions), when I booted into Xiaomi.eu MIUI everything was fine. So the problem only affects AOSP ROMs and not MIUI based custom ROMs. Maybe something is missing from the kernel, preventing the ROM from reading the battery status on a batch of phones with slightly different hardware.
geinna.dev said:
Hi. I use Redmi Note 3 (Snapdragon).
I want to install CM 13.0 by Santhosh M, so I unlocked my device officially.
I checked my device unlocked sucessfully via "fastboot oem device-info" . it says,
"...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.050s]
finished. total time: 0.053s
"
Then I installed TWRP 3.0.0.2-2 using FLASHER TOOLKIT v1.05, then I also flashed Alka recovery update.
But either recoveries didn't show battery status. Right-top is just blank..
Ignoring battery status, I'm going on installing CM13.0. But after installed, battery status is stucked at "-2%". Also fingerprint isn't working.
ONLY IT HAPPENS ON CUSTOM ROM. NOT ON STOCK ROM. MIUI stock rom shows battery stats correctly, and fingerprint works.
I guess bootloader unlock has a bug. Can anybody help me?
Click to expand...
Click to collapse
Could u have still the problem
Try this
I tried it once, didn't worked.
hurricanexx said:
I tried it once, didn't worked.
Click to expand...
Click to collapse
Which recovery u used
It will also depends on that thing
N u hav 2 reflash n see
Am not sure about it
Just sharing
geinna.dev said:
Hi. I use Redmi Note 3 (Snapdragon).
I checked my device unlocked sucessfully via "fastboot oem device-info" . it says,
"...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.050s]
finished. total time: 0.053s
Click to expand...
Click to collapse
Hi, i checked my device and it says like yours.
With "device critical unlocked : true".
And I want to ask, If I go back to MIUI 8 (fastboot method) my bootloader will relock or still unlock?
Do you know how to back to miui8, without brickibg my device.
Thanks for your help.
illall said:
Hi, i checked my device and it says like yours.
With "device critical unlocked : true".
And I want to ask, If I go back to MIUI 8 (fastboot method) my bootloader will relock or still unlock?
Do you know how to back to miui8, without brickibg my device.
Thanks for your help.
Click to expand...
Click to collapse
Your bootloader will relock flashing MIUI. Make sure it is a clean flash (wipe system, data, cache, dalvik) and to always backup. Also, this thread is months old, please just make a new one next time.
Related
ok so writesecureflag brings back
~/android/sdk/platform-tools$ fastboot oem writesecureflag 0
...
(bootloader) This project does not support SD card
OKAY [ 0.000s]
finished. total time: 0.000s
now would it be possible to trick the device into thinking sdcard and let it load off it self?
No, because the bootloader won't just allow you to change the s flag. The bootloader doesn't even have access to change it if it wanted to.
CastleBravo said:
No, because the bootloader won't just allow you to change the s flag. The bootloader doesn't even have access to change it if it wanted to.
Click to expand...
Click to collapse
well what allows to writesecureflag?i know 0 is unlock and 3 is oem lock . i am working very hard on figuring this out although no one will tell me anything about ways others have done it. though it is normally a file from oem placed on sdcard and flashed to radio or bootloader?but as far as i can tell if writescure will not work ever then the exploit has to be either flashed with ruu somehow or through usb
also brute force would take forever to crack a 256byte data encyption key wouldnt it?
I need to do a warranty exchange and my bootloader is unlocked, how can i relock it?
How can i relock it without using a USB?
Cannot relock without USB. You would need to run
fastboot oem lock
Sent from my LG-H901 using Tapatalk
Did you end up successfully locking it? Does it still display the 'unlocked' message on the logo boot screen?
-LBT- said:
Did you end up successfully locking it? Does it still display the 'unlocked' message on the logo boot screen?
Click to expand...
Click to collapse
Necro to say: YES, you can run "fastboot oem lock" to RELOCK the bootloader. "fastboot getvar unlocked" returns "unlocked: no".
Just tried it on my (two hour old) phone here.
Code:
C:\Assorted Programs\LGV10 Toolkit>fastboot getvar unlocked
unlocked: no
finished. total time: 0.007s
C:\Assorted Programs\LGV10 Toolkit>fastboot oem unlock
...
OKAY [ 3.374s]
finished. total time: 3.374s
C:\Assorted Programs\LGV10 Toolkit>fastboot getvar unlocked
unlocked: yes
finished. total time: 0.008s
C:\Assorted Programs\LGV10 Toolkit>fastboot oem lock
...
OKAY [ 1.764s]
finished. total time: 1.765s
C:\Assorted Programs\LGV10 Toolkit>fastboot getvar unlocked
unlocked: no
finished. total time: 0.005s
hi guys
am not able to boot into bootloader to unlock it
I tried
adb reboot bootloader
and
adb reboot boot-loader
it's just making a restart
even I tired the manual way by pwr + - volume but didn't work
my model is LG-H960
any ideas!!
I'm going to be upgrading real soon and I'm stuck between the v10 and note 5. I must have root
Sent from my Nexus 6 using Tapatalk
How did you unlock the bootloader ?
melorib said:
How did you unlock the bootloader ?
Click to expand...
Click to collapse
It will factory reset your device so make sure you are sure that you actually want to do it
reboot to bootloader then use the following:
Code:
fastboot oem lock
Sent from my S7 Edge using XDA Labs
KAsp3rd said:
It will factory reset your device so make sure you are sure that you actually want to do it
reboot to bootloader then use the following:
Code:
fastboot oem lock
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Thanks, I will do it when/if I move to marshmallow
melorib said:
Thanks, I will do it when/if I move to marshmallow
Click to expand...
Click to collapse
Hi, Have you been able to Relcok it successfully? Does bootloader unlock still appears on your screen or it is gone?
Waxim1 said:
Hi, Have you been able to Relcok it successfully? Does bootloader unlock still appears on your screen or it is gone?
Click to expand...
Click to collapse
I dont think my phone bootloader was ever unlocked, at least I never noticed such message, but since I rooted in lolipop I get this funny screen everytime I reboot, even after upgrading to marshmallow
KAsp3rd said:
It will factory reset your device so make sure you are sure that you actually want to do it
reboot to bootloader then use the following:
Code:
fastboot oem lock
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Thanks, it worked
if we relock the bootloader after doing root and debloat the stock rom, when they factory reset everything the root stay or just be gone after do the relock? are we able to unlock it again if we need TWRP?
other thing, the "cant check software for corruption" message will still appear or be gone when re-locked?
Hi guys!
A little background. I am trying to unlock the bootloader, after seeing the root status: unknown, a second time after re-flashing back to stock rom. I could unlock the bootloader perfectly fine on the first try on firmware .251 but after updating to .260, the
Code:
fastboot -i 0x0fce oem unlock 0x<key>
command keeps failing. I was trying to flash a custom rom from FreeXperia, but after several attempts of not being able to send the system.img into the tablet, I decided to re-flash to stock using Flashtool, and had selected all the option for wipe and no exclude.
Which leads to my question: Does the
Code:
fastboot getvar all
retrieves anything at all? I also tried
Code:
fastboot getvar boot
fastboot getvar version-main
but also retrieves nothing.
This is the log:
Code:
C:\Users\Aotsubame\AppData\Local\Android\sdk\platform-tools>fastboot devices
CB5A27L24G fastboot
C:\Users\Aotsubame\AppData\Local\Android\sdk\platform-tools>fastboot getvar all
all:
finished. total time: 0.007s
C:\Users\Aotsubame\AppData\Local\Android\sdk\platform-tools>fastboot getvar version-main
version-main:
finished. total time: 0.006s
C:\Users\Aotsubame\AppData\Local\Android\sdk\platform-tools>fastboot getvar boot
boot:
finished. total time: 0.013s
C:\Users\Aotsubame\AppData\Local\Android\sdk\platform-tools>fastboot -i 0x0fce oem unlock 0x<key>
...
FAILED (remote: Command not allowed)
finished. total time: 0.014s
special flash command for the large partitions
flash system like outlined here:
http://developer.sonymobile.com/kno...ocked-xperia-devices/#build-aosp-lollipop-5-1
What do you expect from the getvar command?
DHGE said:
flash system like outlined here:
What do you expect from the getvar command?
Click to expand...
Click to collapse
Hi, thanks for the reply! I was trying to get back root and unlock bootloader after splendidly failing to successfully flash a custom rom to my Z4 tablet. I was searching around Google for the remote: command not allowed error, and actually found out that some of the users actually have output for the getvar all command, which was bootloader version information and other stuff. I should also point out that I have successfully unlocked the bootloader the first time but not the second time.
Another question: Will downgrading the firmware change the rooting status in the service menu?
Edit: Will re-flashing the stock rom lock the bootloader?
Going to try the link you posted! Will report back if there's any disaster that I've made.
you better search here on XDA and not on the web
SONY devices are a bit special in terms of partitions and bootloaders:
http://forum.xda-developers.com/crossdevice-dev/sony/noob-guide-to-sony-ericsson-xperia-t3209012
AFAIK bootloader stays unlocked whatever you flash after unlocking and only using Flashtool or SONY PC Companoin (the latter useless for unlocked devices) you should be on the safe side.
fastboot flash ... is a bit more dangerous but I would never flash anything were I have a hunch the developer is taking too many chances and were there is no README. And it really has to be for your specific device!
Sometimes I think people complaining here have flashed obscure phone ROMs to their tablet or Wifi ROM to their LTE device or any weird pre Lollipop root tricks (there are scams easiliy found via web search).
I just tried downloading the Flashtool from Sony's website. The Emma one.
However, the program says that my bootloader is locked for some odd reason. I'm inclined to think I am in a state where I can't unlock my bootloader any more though.
I also did enable My Xperia after I reflashed the stock rom during the initial setup, but immediately deactivated it. I wonder if this is causing it to have this error.
the fora for newer Xperia devices are plastered with MyXperia "accidents"
riveria said:
I also did enable My Xperia after I reflashed the stock rom during the initial setup, but immediately deactivated it. I wonder if this is causing it to have this error.
Click to expand...
Click to collapse
Emma is useless. Does not work on our Lollipop devices. Updates of Emma seem to be automatic but no improvement. Maybe they forgot to switch off their update bot.
You bricked your device.
From SONY (READ before you do risky things!!!):
After unlocking your device, you should not enable My Xperia (found in the settings menu under security on some devices running Android 5.0) as this might cause the device to malfunction.
Click to expand...
Click to collapse
source: http://developer.sonymobile.com/unlockbootloader/
DHGE said:
Emma is useless. Does not work on our Lollipop devices. Updates of Emma seem to be automatic but no improvement. Maybe they forgot to switch off their update bot.
You bricked your device.
From SONY (READ before you do risky things!!!):
Click to expand...
Click to collapse
Oh ok, so there's no chance of me unlocking the bootloader? The device still boots up normally though.
riveria said:
Oh ok, so there's no chance of me unlocking the bootloader?
Click to expand...
Click to collapse
I do not know.
I do not think so though - if you could unlock the MyXperia Software would be no protection at all. Thieves could just unlock the BL of the stolen device and lough at SONY.
The device still boots up normally though.
Click to expand...
Click to collapse
You are lucky then - there are reports where only a repair at SONY could revive the device:
http://fxpblog.co/2015/07/03/dont-destroy-your-unlocked-device.html
DHGE said:
I do not know.
I do not think so though - if you could unlock the MyXperia Software would be no protection at all. Thieves could just unlock the BL of the stolen device and lough at SONY.
You are lucky then - there are reports where only a repair at SONY could revive the device
Click to expand...
Click to collapse
Alright! Thanks for the help! I guess no more rooting for me then. I'll try reflashing the stock rom again and see what are the results.
Reflashing doesn't change the rooting status. So a reminder to all: Don't enable My Xperia.
Hi friends!
I'm new in Mi 8 Lite community. I wonder a thing. If i unlock my bootlader, can i lock it again ?
Thanks for your answers.
Absolutely you can
https://youtu.be/O6qU57iGhBg
hamidezat20 said:
https://youtu.be/O6qU57iGhBg
Click to expand...
Click to collapse
Will this work on Mi 8 Lite ?
Yes this method works on all xiaomi devices
Hello!
Some people claim that locking up the bootloader on newer Xiaomi devices could brick the phone.
Does this information proceed?
Has anyone tested?
---------- Post added at 08:51 PM ---------- Previous post was at 08:31 PM ----------
hamidezat20 said:
https://youtu.be/O6qU57iGhBg
Click to expand...
Click to collapse
This video shows how to install stock ROM. But no to lock bootloader.
I dont understand the language. So, I dont see when he lock bootloader.
Sorry! Bad english... ::laugh:
alxsduarte said:
Hello!
Some people claim that locking up the bootloader on newer Xiaomi devices could brick the phone.
Does this information proceed?
Has anyone tested?
---------- Post added at 08:51 PM ---------- Previous post was at 08:31 PM ----------
This video shows how to install stock ROM. But no to lock bootloader.
I dont understand the language. So, I dont see when he lock bootloader.
Sorry! Bad english... ::laugh:
Click to expand...
Click to collapse
This video don´t show how to lock bootloader so the essential part is missed, maybe the guy is talking about but most of users won´t understand what he says and is not reflected on the options that he is using.
If you want to lock bootloader using MiFlashTool then at time to flash a stock rom you have to check on "Clean All and Lock" option down at the right in the tool.
Locking bootloader can´t never brick device by itself, the problem is that some users tried to do it using a custom rom, a custom recovery, rooted or with a cross-firmware that was not released originally in the device and happened that after device was locked again then refuses to boot to android system so bootloader detects that some partition/s was/were altered.
If you only unlocked bootloader and you are using all stock and non rooted you can relock it without need of use mi flash but using only the typical fastboot command
Code:
fastboot oem lock
then check if it was correct with
Code:
fastboot oem device-info
BUT never try to lock it of this way if some non-stock file was flashed and currently using on your device be custom rom, custom recovery, root, logo, custom kernel, etc.
SubwayChamp said:
This video don´t show how to lock bootloader so the essential part is missed, maybe the guy is talking about but most of users won´t understand what he says and is not reflected on the options that he is using.
If you want to lock bootloader using MiFlashTool then at time to flash a stock rom you have to check on "Clean All and Lock" option down at the left in the tool.
Locking bootloader can´t never brick device by itself, the problem is that some users tried to do it using a custom rom, a custom recovery, rooted or with a cross-firmware that was not released originally in the device and happened that after device was locked again then refuses to boot to android system so bootloader detects that some partition/s was/were altered.
If you only unlocked bootloader and you are using all stock and non rooted you can relock it without need of use mi flash but using only the typical fastboot command
Code:
fastboot oem lock
then check if it was correct with
Code:
fastboot oem device-info
BUT never try to lock it of this way if some non-stock file was flashed and currently using on your device be custom rom, custom recovery, root, logo, custom kernel, etc.
Click to expand...
Click to collapse
Thank you, bro!
All my doubts are clear now!
you cant lock bootloader if you firmware was originally chinese and you have changed to global..
if your firmware was global and you unlocked , yes you can lock it again using flashtool and oficial GLOBAL fastboot rom,developer or stable..:good:
Hello, I've been trying to unlock my Mi8 Lite for a while (bootloader) but it is always stuck at 50% on MiUnlock, I've tried multiple drivers and disabling driver signature in Windows 10. It never gets beyond that point and always shows a '-1' error. Did anyone encounter this or better yet solved it? I've searched many times on Google and Youtube but with no success.
I had requested an unlock from Xiaomi and disabled all my other devices from my account.
Any help would be appreciated as this has become unnecessarily complicated, Thanks!
Shillopellos9 said:
Hello, I've been trying to unlock my Mi8 Lite for a while (bootloader) but it is always stuck at 50% on MiUnlock, I've tried multiple drivers and disabling driver signature in Windows 10. It never gets beyond that point and always shows a '-1' error. Did anyone encounter this or better yet solved it? I've searched many times on Google and Youtube but with no success.
I had requested an unlock from Xiaomi and disabled all my other devices from my account.
Any help would be appreciated as this has become unnecessarily complicated, Thanks!
Click to expand...
Click to collapse
Check again if it´s correctly binded your MiAccount on Developer Options and try with other MiUnlock version.
Shillopellos9 said:
Hello, I've been trying to unlock my Mi8 Lite for a while (bootloader) but it is always stuck at 50% on MiUnlock [...] It never gets beyond that point and always shows a '-1' error. Did anyone encounter this or better yet solved it?
Click to expand...
Click to collapse
Yes, I had the same issue and got it solved by using Mi Unlock on another PC. My main PC is using AMD Ryzen 2700 CPU, my laptop Intel Core i7-4712HQ. Wasted like 2 hours on my PC, while it worked first try on my laptop. Please note, the software told me to now wait 360 hours - it didn't unlock right away (this looks like expected behavior).
tolga9009 said:
Yes, I had the same issue and got it solved by using Mi Unlock on another PC. My main PC is using AMD Ryzen 2700 CPU, my laptop Intel Core i7-4712HQ. Wasted like 2 hours on my PC, while it worked first try on my laptop. Please note, the software told me to now wait 360 hours - it didn't unlock right away (this looks like expected behavior).
Click to expand...
Click to collapse
Soo i saw your reply and straight away tried unlocking with stock drivers on freshly bought laptop (today) with a Celeron, it worked straight away, Thanks! (i have a Ryzen 1600 desktop)
Witch version of Mi unlock software you suggest for unlocking bootloader?
I have China phone redmi note 8..and i want to flash global ROM but all Google say that if u lock the bootloader again...the phone will brick...so help me
Also, i have a question! My phone is on EU version, but i prefer the global version. Can i lock the bootloader back after i flash the version in fastboot mode?
Flash Mi 8 Lite image with mi flash tool and make sure you select clean all and lock in right bottom..
ThePscho said:
Hi friends!
I'm new in Mi 8 Lite community. I wonder a thing. If i unlock my bootlader, can i lock it again ?
Thanks for your answers.
Click to expand...
Click to collapse
You can flash fastboot ROM and set to clean all and lock, then the bootloader will be locked by a script from fastboot ROM
alicization said:
You can flash fastboot ROM and set to clean all and lock, then the bootloader will be locked by a script from fastboot ROM
Click to expand...
Click to collapse
Once i unlocked the bootloader, after i set a new password and fp it just kept saying that i need to enter my password every 0 hours. Tbh it did warn me when i accepted the oem unlocking that security features like fp, face recognision and find device will be disabled. So here is the question, is there any way at all to lock the bootloader without factory resetting?
P.S. : I have flashed twrp and miui 12, because i destroyed the miui 11 [:
Hello guys I'm trying to save my bricked P20 Lite but I am running into some issues. I unlocked the bootloader using testpoint but twrp won't flash or boot. Flashing gives me a flash write failure, booting gives me a invalid command error and I can't wipe cache either. I could really use your help.
Advanced07 said:
flash write failure
Click to expand...
Click to collapse
"flash write failure" - it might be due to a locked bootloader or hardware issue, AFAIK.
Try explaining what exactly happened, step by step.
-Alf- said:
"flash write failure" - it might be due to a locked bootloader or hardware issue, AFAIK.
Try explaining what exactly happened, step by step.
Click to expand...
Click to collapse
I unlocked my bricked P20 lite bootloader with the test pin method, then I tried to flash TWRP in fastboot and I got those errors.
Advanced07 said:
I unlocked my bricked P20 lite bootloader with the test pin method, then I tried to flash TWRP in fastboot and I got those errors.
Click to expand...
Click to collapse
Are you sure that bootloader is unlocked? (With unlocked BL you will see that message each time when you reboot: "Your device has been unlocked and can't be trusted").
Have you enabled in Developer menu
"OEM unlock" ?
In fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
-Alf- said:
Are you sure that bootloader is unlocked? (With unlocked BL you will see that message each time when you reboot: "Your device has been unlocked and can't be trusted").
Have you enabled in Developer menu
"OEM unlock" ?
In fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Click to expand...
Click to collapse
1. Yes I do get that message that it's unlocked.
2. My device is bricked so that's impossible to enable. I unlocked it after it started bootlooping.
3. Gonna do those commands and tell the results
(bootloader) :ANE-LX1 9.1.0.372(C432E7R1P7)
(bootloader) ANE-LX1
vendorcountry: hw/eu
(bootloader) :ANE-LX1-CUST 9.1.0.7(C432)
(bootloader) :ANE-LX1 9.1.0.132(C432E5R1P7)
What shows Fastboot screen, at the bottom, Phone unlocked and FRP unlock ?
-Alf- said:
What shows Fastboot screen, at the bottom, Phone unlocked and FRP unlock ?
Click to expand...
Click to collapse
Phone unlocked and FRP unlock.
I unlocked the phone and the frp went away but it still gave me errors. Rebooted and frp lock was back + bootloader unlock gives error
Advanced07 said:
Rebooted and frp lock was back + bootloader unlock gives error
Click to expand...
Click to collapse
as i mentioned a month ago :
-Alf- said:
IMO it might be the HW problem , dead memory or damaged motherboard
Click to expand...
Click to collapse
Probably your emmc memory is fried. Not being able to unlock BL & FRP permanently is a sure sign. But I'm just an amateur and an android fan, maybe I'm wrong.
-Alf- said:
as i mentioned a month ago :
Probably your emmc memory is fried. Not being able to unlock BL & FRP permanently is a sure sign. But I'm just an amateur and an android fan, maybe I'm wrong.
Click to expand...
Click to collapse
It does have water damage could it be because of that? That would be unfortunate.
Advanced07 said:
It does have water damage could it be because of that? That would be unfortunate.
Click to expand...
Click to collapse
- known failure due to water exposure , although the write failures are intermittent.
P.S.: since January are you trying unbrick a water damaged phone?
-Alf- said:
- known failure due to water exposure , although the write failures are intermittent.
P.S.: since January are you trying unbrick a water damaged phone?
Click to expand...
Click to collapse
Nope i already know it was dead (repairs say it was total loss) but when I saw the new unlock method I thought it might be saved. Guess I was wrong but oh well I tried anyways.
Advanced07 said:
Nope i already know it was dead (repairs say it was total loss) but when I saw the new unlock method I thought it might be saved. Guess I was wrong but oh well I tried anyways.
Click to expand...
Click to collapse
Hi i have a query, the phone that you unlocked was it running on emui 9.1? If yes did you use potato nv to unlock? I wanna try it myself
apexashwin said:
Hi i have a query, the phone that you unlocked was it running on emui 9.1? If yes did you use potato nv to unlock? I wanna try it myself
Click to expand...
Click to collapse
It was running on the latest version and yes I did use potato NV
Advanced07 said:
It was running on the latest version and yes I did use potato NV
Click to expand...
Click to collapse
Hello thanks for your quick reply,I finally managed to unlock my p20 lite using potato nv.