Phone unusable after unlock bootloader (is not bricked) - P8 Lite (2017) Discussion

Hello,
Yesterday I've decided that the Stock ROM was just an actual mess and decided to install a Custom one.
I have "experience" as I've done it in the past with Nexus, Sony, Motorola. But is the first time I come back to this stuff after some time, so I didn't follow all the events.
Said so I've basically unlocked the bootloader, following the usual steps and everything went well apparently.
The FRP was already red, and as well the Unlock bootloader from green became red.
I've rebooted the phone and I was "welcomed" by the "Your device has been unlocked and can't be trusted".
The phone rebooted and everything was deleted? lost all applications and the GAPPS are missing plus all the Huawei one.
Even weirder The keyboard never Pops-out, meaning I can't literally do anything. I tried all the following then:
Ok no panic...let's enable the Developer Option. Clicked 100 times on Build Number and nothing happens...
I was able to fastboot the phone and apparently flash the TWRP, as no error was raised, but I'm trying in every way to boot into recovery to install a custom ROM and it just doesn't. I always end up on that panel "Your device has been unlocked and can't be trusted".
From here I tried to go back into the Huawei recover interface ( Power button + UP/DOWN) and chose to recover the original Software, but of course it fails.
Ok... an other idea. A simple factory reset? Well it asks me for the PIN and I can't type anything due to the missing keyboard
I typed one of those special codes and chose factory reset. It says I can't do it because of lock screen which is activated. To remove it...I need to input the PIN
tried to fastboot boot twrp.img and no luck
installed FLashify but doesn't allow me to click anything
Kingo root fails at 90%
Offical TWRP download the twrp.img from somewhere but I don't get any option to search the .img path and load it, or whatever the app should help you to do
I am out of idea and with a Macbook available.
Cheers!

You could search for a keyboard on Play Store with your voice. If you don't have a microphone symbol in Play Store search bar, try flashing a bigger Gapps.zip which probably would include Google Voice Recognition.
EDIT: If you still can't manage it, flash the stock erecovery.img to your recovery partition, then do a restore from there. It will download stock firmware and format your data.

marstonpear said:
You could search for a keyboard on Play Store with your voice. If you don't have a microphone symbol in Play Store search bar, try flashing a bigger Gapps.zip which probably would include Google Voice Recognition.
EDIT: If you still can't manage it, flash the stock erecovery.img to your recovery partition, then do a restore from there. It will download stock firmware and format your data.
Click to expand...
Click to collapse
I'm in the same situation. After a lot of attempts I found a keyboard, fleksy(an horrible keyboard) but when finally i tried to make factory reset it hasn't work. I have no idea how fix this situation.

marco.riggio said:
I'm in the same situation. After a lot of attempts I found a keyboard, fleksy(an horrible keyboard) but when finally i tried to make factory reset it hasn't work. I have no idea how fix this situation.
Click to expand...
Click to collapse
eRecovery didn't work ?

dz3ro said:
eRecovery didn't work ?
Click to expand...
Click to collapse
Every time I tried to reset with eRecovery it's failed

Hi
In case someone still searching for solution, had the same problem, you need to relock bootloader using "fastboot oem relock #unlockId" then enable oem unlock from developer's options, unlock again in fastboot and you're good !

With HI SUITE
Hi
Install Keyboard APK (swiftkey for example) with HiSuite (http:/ /consumer.huawei.com/minisite/HiSuite_en/)

Unlock the bootloader again.
I already happened to have PHONE Unlocked and the bootloader is locked.
Go to bootloader and use the command (fastboot oem device-info) and you will have the bootloader information.

Related

Nexus 6 - Can't boot TWRP recovery

I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.
simms22 said:
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.
Click to expand...
Click to collapse
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.
briman0094 said:
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.
Click to expand...
Click to collapse
important thing to forget to mention
So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?
simms22 said:
important thing to forget to mention
Click to expand...
Click to collapse
I guess I assumed that when I said "continues to boot normally" people would assume I could re-enable "OEM Unlock" if needed
scryan said:
So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?
Click to expand...
Click to collapse
All the console output indicates success, and it boots to the initial "TEAMWIN" logo for a few seconds and reboots.
No Recovery Similiar issue
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.
ray6279 said:
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.
Click to expand...
Click to collapse
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it.
Click to expand...
Click to collapse
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.
nhizzat said:
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.
Click to expand...
Click to collapse
A screenshot of an e-mail from a Google employee regarding Android Pay and SafetyNet.
50% JOY No Fastboot?
simms22 said:
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .
Click to expand...
Click to collapse
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.
ray6279 said:
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.
Click to expand...
Click to collapse
one question.. what is perm recovery?? the only recovery that works on the n6 is twrp recovery.
and when you are in her recovery, is it showing you the right location where the files should be? if nit, you csn change the lication.
Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.
ray6279 said:
Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.
Click to expand...
Click to collapse
your welcome, but you are still off in one bit of fact. you use fastboot, not adb, to flash a recovery(and system.img)
edit.. you can use apps like flashify to flash recovery, if you have root already.
So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.
ray6279 said:
So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.
Click to expand...
Click to collapse
ok, when wiping, dont do the first option wipe, itll wipe your whole phone clean. you need to select the advanced options and pick what you want wiped. fastboot is the way to unlock your bootloader, or flash a recovery. also, you use it to flash a system.img or any part of it.
adb is a general linux that can be used with android, anywhere but in the bootloader(only fastboot in the bootloader).
bootloader isnt the usb connection between the device and the pc, its part of the phone that boots it and decides if the rom is safe to run. thats why we unlock it. so we can flash roms eithout googles key.
fastboot is the tool that you use to do whatever needs to be fone in the bootloader, adb everywhere else.
a recovery you need if you want to flash custom roms, kernels, supersu, or other mods. you can also wipe different partitions with the recovery, or make a "nandroid' backup. thats a bavkup of everything. its like a complete snapshot of everything during the time you made it. if you ever mess up your phone, you can restore it, and you will be at the exact same place when you made the backup.
anything else?

Htc one mini 2 stuck in startscreen - fastboot mode available.

About two months back, I rooted my htc one mini 2.
Unlocked the bootloader, installed a new recovery (This one) and finally rooted the device. I wanted to install different fonts for it, and in the process relocked the bootloader again.
Now, after several weeks of not doing anything regarding the root, my phone has errors after errors.
First, Google Play stopped working, and along with it, Youtube and the Play Store of course.
About two weeks later, even the "internet" app stopped working.
Today i wanted to start my phone only to find it stuck in the starting screen. (Looks like this)
What I want to do now is get my phone factory resetted, not rooted anymore and WORKING.
What I tried to do is get the phone into fastbood mode (this worked) and connecting it with the "Minimal ADB and Fastboot" console. (This did NOT work)
Rebooting the device from the fastboot menu did not work, it either gets stuck in the loading screen again or directly enters fastboot.
What can I do to make my phone work again?
I hope you can help me :/
Montor
Montor said:
About two months back, I rooted my htc one mini 2.
Unlocked the bootloader, installed a new recovery (This one) and finally rooted the device. I wanted to install different fonts for it, and in the process relocked the bootloader again.
Now, after several weeks of not doing anything regarding the root, my phone has errors after errors.
First, Google Play stopped working, and along with it, Youtube and the Play Store of course.
About two weeks later, even the "internet" app stopped working.
Today i wanted to start my phone only to find it stuck in the starting screen. (Looks like this)
What I want to do now is get my phone factory resetted, not rooted anymore and WORKING.
What I tried to do is get the phone into fastbood mode (this worked) and connecting it with the "Minimal ADB and Fastboot" console. (This did NOT work)
Rebooting the device from the fastboot menu did not work, it either gets stuck in the loading screen again or directly enters fastboot.
What can I do to make my phone work again?
I hope you can help me :/
Montor
Click to expand...
Click to collapse
Try unlocking the bootloader again.Flash the custom recovery and then flash the stock rom available in the development section. It looks like your system partition got corrupted
csoulr666 said:
Try unlocking the bootloader again.Flash the custom recovery and then flash the stock rom available in the development section. It looks like your system partition got corrupted
Click to expand...
Click to collapse
How can i unlock the bootloader again?
The only way i know is via the console and "fastboot oem unlock" - i cant get my phone to connect though.
The available devices the console gives me are an emulator and three times my phone, which is/are offline.
Edit:
Stupid me. "Fastboot oem devices" and it shows my phone in fastboot mode.
Next problem: "fastboot oem unlock" does not work, and flashing the recovery with "fastboot flash myrecovery.img" doesn't work either :/
Edit 2: Managed to unlock the bootloader again (mistook the android folder with de adb folder, no unlocktoken there of course)
Directly after unlocking the bootloader again, the device went into recovery mode, showed the recovery starting logo, and went black.
After turning it back on, it got stuck in the starting screen again - will have to wait for it to run out of battery.
Edit 3: Flashed the recovery, but i can't seem to find a stock rom (only one i did find is this here - and the files are down...)
Solved it!
Just did a factory reset in bootloader menu.
(I hope i didn't forget anything, since I don't know s*** about android development)

How to Re-Lock Bootloader?

I need to lock my bootloader to do an exchange at T-Mobile. I have 20R stock flashed, but it still says custom bootloader upon boot, how do I relock it safely?
I read that "fastboot oem lock" will work, but will brick it if I don't do it perfectly. Any advice on what to do?
TechGuruGJ said:
I need to lock my bootloader to do an exchange at T-Mobile. I have 20R stock flashed, but it still says custom bootloader upon boot, how do I relock it safely?
I read that "fastboot oem lock" will work, but will brick it if I don't do it perfectly. Any advice on what to do?
Click to expand...
Click to collapse
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
I'm terribly sorry if bumping is not ok.
Thought it wasn't worth making a new thread, since my post is about the one above.
Has anybody actually tried these steps above? (Since every other thread mentioning this says it's a one-way only thing..)
Does locking the bootloader means also loosing the custom recovery? (I'd expect that, but asking to be sure)
Does it return the phone to it's original state? (ie. before one unlocked the bootloader, or there are some differences?)
Does it also means I would be able to get official OTA updates and so on? (since with a custom recovery, that's not possible)
Thanks in advance.
Yes, it does work. I did it, worked perfectly. Yes it does return your device to it's original state. Just make sure the stock ROM is flashed and all should be well. I didn't try, but I see no reason why it wouldn't let you get OTA updates from T-Mobile. Let me know if you need help.
Nadeox1 said:
I'm terribly sorry if bumping is not ok.
Thought it wasn't worth making a new thread, since my post is about the one above.
Has anybody actually tried these steps above? (Since every other thread mentioning this says it's a one-way only thing..)
Does locking the bootloader means also loosing the custom recovery? (I'd expect that, but asking to be sure)
Does it return the phone to it's original state? (ie. before one unlocked the bootloader, or there are some differences?)
Does it also means I would be able to get official OTA updates and so on? (since with a custom recovery, that's not possible)
Thanks in advance.
Click to expand...
Click to collapse
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.
raptorddd said:
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.
Click to expand...
Click to collapse
Thanks both for replying.
And no @raptorddd , I did not mean that.
Your post is the only mentioning that locking the bootloader is possible, while all the other similar threads have ony people saying otherwise / it's not possible. I guess a slightly doubt is legit to have, don't take it wrongly
raptorddd said:
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
Click to expand...
Click to collapse
I have follow this instructions and now it giving me and error. Any fix??
WARMANH811 said:
I have follow this instructions and now it giving me and error. Any fix??
Click to expand...
Click to collapse
What error?
TechGuruGJ said:
What error?
Click to expand...
Click to collapse
Secure booting Error!
Error code: 1003
MODIFIED ! !
WARMANH811 said:
Secure booting Error!
Error code: 1003
MODIFIED ! !
Click to expand...
Click to collapse
are you sure you have h811.? i did not get that error ive tried this twice..
i remeber getting an security boot error on LG G2 i fix by flashing firmware .. so maybe KDZ could help..
if not am not sure then search for that error and find out how to fix.
raptorddd said:
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
Click to expand...
Click to collapse
My H811 T-mobile phone needs service. It has original 20v software version. It is unlocked with TWRP and rooted. Can I use this method? Do I first have to downgrade software to some other version? Will this method also take out TWRP and root or do I still have to take them out before doing this? How? Please help.
joecandle said:
My H811 T-mobile phone needs service. It has original 20v software version. It is unlocked with TWRP and rooted. Can I use this method? Do I first have to downgrade software to some other version? Will this method also take out TWRP and root or do I still have to take them out before doing this? How? Please help.
Click to expand...
Click to collapse
no need to downgrade. to remove root and any trace if phone works. is to use KDZ then once it boots into system do the lock procedure. so it locks and the small white letter are removed. this way its like stock rom and recovery and the above commmands will make bootloader locked. and sent to repair. if bootloops try the freezing method.
Used on an LG Aristo that has Cyanogen and it worked
raptorddd said:
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.
Click to expand...
Click to collapse
This was the only one i found that didnt brick my phone and trust me ive bricked and unbricked this phone many times
When you use the fastboot command to lock back your bootloader, the phone doesn't revert automatically to the stock recovery and actually that is partly the reason why it bricks and other main reason is that changes made to bootloader to obtain root brick the phone. before you relock bootloader, if you have SuperSU (in-app menu option) or Magisk (uninstall zip file), use their respective methods to unroot the phone, then use twrp to flash .image file of stock recovery to recovery partition then use the fastboot command to lock the bootloader. Even then it may or may not work because if whatever method the phone uses to check the integrity of bootloader and/or recovery, such as md5, if it doesn't match, the phone will still brick. Since all your data on phone will be erased regardless as soon as you lock the bootloader, i personally just fastboot lock the bootloader, remove battery to power down, use the volume up and plug usb cable in from pc to put phone in download mode and just use LGUP (uppercut) if have kdz file already, which i do, i just let LG Bridge download the file, find it in programs folder and copy it to another location before LG Bridge deletes it --OR-- just use error recovery option in Software Update tab in LG Bridge as both LGUP and LG Bridge will detect the phone in download mode even if it is bricked.
By the way, I have used both methods above dozens of times without any issues, someone above who mentioned phone boot-looping because of locking the bootloader, it is boot-looping not because of hardware flaw which was widespread in LG G3 but a software issue (phone boots up, doesn't find the software configuration it is looking for and just restarts) and they are not the same issues, no need to freeze the phone, won't help.
the method works, but no OTA from T-Mobile. "verification problem".
When I try to "adb reboot bootloader" I get "security error".
If I try reboot recovery, TWRP is definitely not there.
Just want to update from20Q to 20X.
Any help would be appreciated.
metropical said:
the method works, but no OTA from T-Mobile. "verification problem".
When I try to "adb reboot bootloader" I get "security error".
If I try reboot recovery, TWRP is definitely not there.
Just want to update from20Q to 20X.
Any help would be appreciated.
Click to expand...
Click to collapse
The above points to you not giving permission possibly because either you missed the permission pop-up or selected option that didn't allow permission.
Can anyone help me?
When i unlock bootloader on my lg velvet 4g the fingerprint stop working so i want to relock. But when i put this on cmd "adb reboot bootloader" it only restarts my phone. Doesnt shows me the bootloader menu it only restarts normaly
Lukasz23 said:
Can anyone help me?
When i unlock bootloader on my lg velvet 4g the fingerprint stop working so i want to relock. But when i put this on cmd "adb reboot bootloader" it only restarts my phone. Doesnt shows me the bootloader menu it only restarts normaly
Click to expand...
Click to collapse
managed to solve?

Semi working PRA-LX1C432

Hi !
I bought in January the nice P8 Lite 2017 and received a PRA-LX1C432 (dual sim europe no carrier).
It was with Android 7.0 and EMUI 5.0 and i wanted to root it.
I did it well, and was with the firmware PRA-LXA1C432B182 in stock and rooted with the tuto from this thread
https://forum.xda-developers.com/p8...ck-rom-huawei-prague-pra-xxxc432b182-t3727816
and uninstalled TWRP to put back stock recovery.
Later, I wanted to unroot my phone, and that's where things went wrong. I tried to do it with the superSU option and after a hard reset it was working and not rooted, but i'd still have the message "this phone can't be trust" so i tried to relock the bootloader and it did hard reset the phone again and now, i'm stuck with a phone that can send sms or go through the internet with LTE, but can't access fm, camera, google music, nfc is going on and off, calls don't work, etc... In dev options, Allow OEM unlock is greyed and I can't change anything. Phone is recognized by computer and I can acces memory of the phone.
I can hard reset it won't change, i ca also accessFastboot, or recovery or eRecovery, but in Fastboot mode it says "PHONE Unlock FRP Lock" and from my computer i can't do anything : if i try to flash twrp with fastboot command, i have the message "FAILED remote the command is not allowed", if i try to lock/unlock/relock bootloader it says "FAILED remote root type is risk".
Clearly, I don't know what to do. I'm used with rooting/unrooting smartphones from different brands (Samsung, LG, Sony, Huawei...), even though i'm far from being a master, and using Fastboot/ADB commands, but... I don't know.
If someone has any idea, I'm taking. I'm thinking about dload method but, of cooourse, I do NOT have a sdcard, so it's the last thing i would have tried from all i have seen on xda and elsewhere.
Thanks for reading and taking time to answer and help me, and sorry for not perfect english, i'm french but trying my best !
Run a eRecovery restore , it restore the entire smartphone to stock and also lock bootloader. Idk if this can solve your problems but i had ur same problem a days ago and i restored my phone enterely.
Fr0nK said:
Run a eRecovery restore , it restore the entire smartphone to stock and also lock bootloader. Idk if this can solve your problems but i had ur same problem a days ago and i restored my phone enterely.
Click to expand...
Click to collapse
I can't, it says that it can not get package infos from server. :/
MrCrumble34 said:
I can't, it says that it can not get package infos from server. :/
Click to expand...
Click to collapse
If you have twrp or if you can install it in someway , i can provide to you and ominfo.img to flash via twrp in ominfo partition to restore and remove package info error.
Fr0nK said:
If you have twrp or if you can install it in someway , i can provide to you and ominfo.img to flash via twrp in ominfo partition to restore and remove package info error.
Click to expand...
Click to collapse
TWRP is not installed, and I can't flash it in any way. Fastboot says "FAILED (remote : command not allowed)" if I try flashing recovery or system or anything. It also says "FAILED (remote : root type is risk) if I try to lock/unlock/relock the bootloader.
Ok, I'm actually trying something. I plugged the phone into my computer, and HiSuite told there was an update available for my phone, so I just clicked on it. It's doing right now, I will edit my post after it has finished (for good or bad).
EDIT : Ok, si it did work ! My phone is now on PRA-LX1C432B194, everything is working, not rooted. I relocked the bootloader with Fastboot, the command did work (guess I can root it again if I need now). But I think I'll leave it like that ^^'
Allow OEM unlock isn't greyed anymore, I came back to the original state of my phone but with an update not (yet) available in my country, no more "Device can't be trusted" message. Like if nothing had ever happened (expect it will be written PHONE Relocked).
This phone is really sensitive, haha^^
But as anyway I made it
Thanks anyway for trying to help !

Xiao Mi A2 "Can't load Android system"

Hi Guys,
My phone suddenly stuck at this screen since may :
Android Recovery
Xiaomi/jasmine/jasmine_sprout
9/PKQ1.180904.001/V10.0.9.0.PDIMIXM
user/release-keys
Use volume up/down and power.
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data store on this device.
- Try again
- Factory data reset
If i press try again, sometime it will go to fastboot screen.
I can go into recovery mode here but i not sure which step i should do next.
Reboot system nowreboot to bootloader
apply update from ADB
apply update from sd CARD
wipe data/factory reset
Mount/sstem
view recovery logs
run graphics test
run locale test
power off
I'm not a very tech savvy person, i would really appreciate some help as i have data inside my phone which i need. So if possible i would like to retain the data.
I tried like EDL,fastboot,and flashing none seem to work. Of course I may be doing it wrong.
Can anyone guide me step by step I be happy to give an reward via paypal.
I'm so sorry bro.... 80% of times this means you lost your data.
Is the bootloader unlocked?
blazessdd said:
I'm so sorry bro.... 80% of times this means you lost your data.
Is the bootloader unlocked?
Click to expand...
Click to collapse
Thank you so much for replying.
Nope, but I can do EDL to unlock bootloader, I already disassemble the device a few times.
Just that every time I try to flash it , it give me some error. like Bluetooth error or the version error .
Which I watch thousand of video to work but it's doesn't help. Or maybe I just watched the wrong video
Ok tell me exactly what are you doing and where you have downloaded the rom.
If it's corrupted and you try to flash it you will lose the data... Was debug USB activated on developer settings?
My device died too. After the October update, he never came back. It is looped on the home screen written "Android One".
I've tried several tutorials, it accesses the FastBoot screen, but when trying to use MI Flash appears a Bluetooth error and does not proceed.
I've tried using the adb flashing unlock_critical command, but it fails too.
He didn't have the bootloader unlocked, I now have a large paperweight.:crying:
epilifio said:
My device died too. After the October update, he never came back. It is looped on the home screen written "Android One".
I've tried several tutorials, it accesses the FastBoot screen, but when trying to use MI Flash appears a Bluetooth error and does not proceed.
I've tried using the adb flashing unlock_critical command, but it fails too.
He didn't have the bootloader unlocked, I now have a large paperweight.:crying:
Click to expand...
Click to collapse
You can try to short the edl points so you can flash the ROM again
blazessdd said:
You can try to short the edl points so you can flash the ROM again
Click to expand...
Click to collapse
I already made this attempt, "adb reboot edl" reports the message "error: '(null)' not found
Xiaomi never again

Categories

Resources