Hello, I'm new to xda, in fact I registered just to ask for help. My p9 lite got stuck on huawei logo, when i try to turn off the device it just reboots 2 times and then just stays on huawei logo. I can enter fastboot and rescue mode, but i have not enabled usb debugging and oem unlock on the device earlier. To be honest this is my first android device, in the past i used only windows phones, so you could say i'm completely new to this. Any suggestions on how to recover my phone or flash any rom into it? I'd be very glad if someone helped me find the solution to this problem. Not sure if i made a thread in the correct place, direct me if i'm mistaken
There are few different versions of P9 Lite, look at the back of the phone to the bottom to see the numbers beside VSN and let us know.
1) Also when the phone is turned off plug in the usb to a computer or charging adapter
2) Hold down volume up & power
3) Let go of the power button when you feel the buzz while still holding the volume up button
4) Download latest version & recovery.
5) Go to Settings>Developer Options>USB Debugging On
5B) If you don't see Developer Options in settings, then go to Settings>About Phone>Build Number & ( tap the Build Number untill it unlocks)
6) Update us on the status, hope it works out.
GloryNation said:
There are few different versions of P9 Lite, look at the back of the phone to the bottom to see the numbers beside VSN and let us know.
1) Also when the phone is turned off plug in the usb to a computer or charging adapter
2) Hold down volume up & power
3) Let go of the power button when you feel the buzz while still holding the volume up button
4) Download latest version & recovery.
5) Go to Settings>Developer Options>USB Debugging On
5B) If you don't see Developer Options in settings, then go to Settings>About Phone>Build Number & ( tap the Build Number untill it unlocks)
6) Update us on the status, hope it works out.
Click to expand...
Click to collapse
tried to enter recovery, still not work. can't go to developer options because phone is stuck on logo, can't power off. couldn't find any solution that works anywhere, been searching for more than 6 hours, still no use. phone model is VNS-L21 forgot to mention earlier
What exactly were you doing before this happened and does your computer recognize your phone when plugged in at all.
Try holding volume up & down together & plug phone in when it reboots on you, & report back with what you see. If anything at all.
GloryNation said:
What exactly were you doing before this happened and does your computer recognize your phone when plugged in at all.
Try holding volume up & down together & plug phone in when it reboots on you, & report back with what you see. If anything at all.
Click to expand...
Click to collapse
I tried to install nougat update, computer recognizes it only in fastboot. holding volume buttons haven't changed anything still no progress. the thing is i had installed nougat a moth or so ago and it worked fine, then rolled back to marshmallow and now this. i'm pretty sure i tried to install correct package, because it was the same i had installed earlier
Did you download a adb tool on your computer that have the 'fastboot.exe' file? If so open that folder,
Have the mouse curser hover in that folder, hold down shift & right click the mouse
Open command prompt
Connect phone as is in fastboot mode
Type adb devices & press enter
Type adb continue & press enter
Hi,
I have the same issue as ellanyx.
my phone can only be stucked while booting or if I connect my phone to a computer, I'm able to boot it in fastboot.
as ellanyx, I didn't enable usb-debug nor OEM unlock option...
so when I'm in fastboot, I type the command "fastboot oem unlock xxxxxx" (hopefully the different data needed are the correct ones mentioned on the box of the phone) I get this error message:
C:\Users\Dieu\Downloads\SRKToolHuawei-STABLE-V1.3-20160619>fastboot oem unlock xxxxx
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
and off course the other options like "fastboot flash recovery recovery.img "... doesn't work.
I can't use the adb commands neither.
when I type the commande, as mentioned above, "adb devices" or "adb continue", nothing works.
So I'm a bit desesperate
do you have any solution for this kind of issue?
thanks
Dude, so the last firmware on your phone was MM or N? If it was MM you should put stock firmware appropriate for your model in dload folder on SD card and put volume+volume-power, and thats it. If you stack on N,....then I dont know because dload method doesnt work with N, or maybe works if you can find stock firmware with recovery for N.
Regards
Unfortunately I can't update with the 3 button update otherwise it would indeed solvemy problem.
pyromana said:
Unfortunately I can't update with the 3 button update otherwise it would indeed solvemy problem.
Click to expand...
Click to collapse
Probably you didnt have correct Oeminfo for MM if dload method didnt work....Try to conect phone with Toolkit and follow procedure for flashing oeminfo and custombin, after that flash stock recovrry and b161 via dload metod. You will find it on forum here.
Regards
the procedure from SRK toolkit?
would it be possible to provide it? because I can't unlock the OEM and I didn't tick the USB debug think.
Maybe problem with the ps not phone so u can not connect with adb
Try with different pc you must have flash oem with fast boot without enable adb from phone if u in fastboot
I can only boot my phone in fastboot (vol- + power) and not in recovery (vol+ + power).
also when using the SRK toolkit, the first screen tells me to be sure that the usb debugging is enable, which I haven't done...
if I'm not mistaken, fastboot is to use the fastboot command and recovery the adb commands
the connection with fastboot works on my computer, the link is made. however when I type the command to unlock the OEM, I get an error stating that the command is not allowed.
when I use the SRK toolkit, with the different questions, he tries to connect the phone with adb and waiting.... waiting...
is there a command to reboot in recovery but from fastboot? in the otherway around it exists but it doesn't seem that from fastboot to recovery it exists.
thanks.
Alexxxx1 said:
Dude, so the last firmware on your phone was MM or N? If it was MM you should put stock firmware appropriate for your model in dload folder on SD card and put volume+volume-power, and thats it. If you stack on N,....then I dont know because dload method doesnt work with N, or maybe works if you can find stock firmware with recovery for N.
Regards
Click to expand...
Click to collapse
dload method works on N. I downgraded my phone from unofficial N update back to official MM update using this method yesterday. You just have to enable OEM at developer options on settings.
It looks like people can't be bothered to read the 1st post properly before they reply.
HE CAN NOT BOOT TO ANDROID SO HE CAN NOT ENABLE OEM OR ACTIVATE USB DEBUGGING!!!!
What he CAN do, is go into eRecovery and Fastboot.
With that in mind, I would suggest using the dload method through fastboot.
Also, make sure it is Huawei SRK Tools 2.0 that is used, as it actually asks if you are in debug mode or fastboot.
Note that there is a few bugs in SRK 2.0:
The TWRP recovery file has the wrong filename in the package, so it WILL fail unless you name it correctly.
Also, when trying to root, do NOT use the "P9 Lite" method as that WILL fail too. Use the "P9/P9 Plus" method.
I am trying to set up a complete guide that can restore the phone when it is stuck in fastboot, however I apparently went a step too far...
ellanyx said:
Hello, I'm new to xda, in fact I registered just to ask for help. My p9 lite got stuck on huawei logo, when i try to turn off the device it just reboots 2 times and then just stays on huawei logo. I can enter fastboot and rescue mode, but i have not enabled usb debugging and oem unlock on the device earlier. To be honest this is my first android device, in the past i used only windows phones, so you could say i'm completely new to this. Any suggestions on how to recover my phone or flash any rom into it? I'd be very glad if someone helped me find the solution to this problem. Not sure if i made a thread in the correct place, direct me if i'm mistaken[/QUOTE
Do you have TWRP recovery ?
---------- Post added at 09:55 AM ---------- Previous post was at 09:50 AM ----------
ellanyx said:
Hello, I'm new to xda, in fact I registered just to ask for help. My p9 lite got stuck on huawei logo, when i try to turn off the device it just reboots 2 times and then just stays on huawei logo. I can enter fastboot and rescue mode, but i have not enabled usb debugging and oem unlock on the device earlier. To be honest this is my first android device, in the past i used only windows phones, so you could say i'm completely new to this. Any suggestions on how to recover my phone or flash any rom into it? I'd be very glad if someone helped me find the solution to this problem. Not sure if i made a thread in the correct place, direct me if i'm mistaken
Click to expand...
Click to collapse
Boot into fastboot mode and flash a custom recovery by meticulus. Link : meticulus.co.vu
Then whenyou get stuck hold power and vol down button for 2 minutes the phone will reboot and then when it says that your device has been unlocked and cant be trusted then only press vol up key ( dont press power button then). The u get into huawei recovery. From that u should power off the phone. Now get a custom rom by meticulus into your device sd card ( Cyanogenmod 13 is recommended ). Then insert sd card in a powered off phone. Now press vol up and power key and flash gapps and custom rom and you are good to go.
Click to expand...
Click to collapse
So, MY question:
I have tried 4 times to get Nougat installed, but every time I got the SMALL package (1.25gb) which means it is not complete.
I decided to try ONE more time, but think I have made a serious mistake.
I was on B161 and tried to downgrade to B160 without upgrading to Nougat first.
This has caused my phone to be stuck at boot with the message "Your device is booting now..."
I can NOT get into eRecovery or fastboot no matter what I do.
If I just leave the phone, then it discharge very fast, but as soon as I plug it in, it starts up and gets stuck at the same screen again.
Does anyone have ANY idea about how I can get out of this problem?
UPDATE:
I have managed to boot to fastboot while connected to my pc.
The phone is unlocked but FRP is LOCKED, which means I can't flash anything.
I read about using Miracle Loader to remove the FRP lock, but it can't "see" my phone. Maybe I am doing it wrong?
SnowmanDK said:
So, MY question:
I have tried 4 times to get Nougat installed, but every time I got the SMALL package (1.25gb) which means it is not complete.
I decided to try ONE more time, but think I have made a serious mistake.
I was on B161 and tried to downgrade to B160 without upgrading to Nougat first.
This has caused my phone to be stuck at boot with the message "Your device is booting now..."
I can NOT get into eRecovery or fastboot no matter what I do.
If I just leave the phone, then it discharge very fast, but as soon as I plug it in, it starts up and gets stuck at the same screen again.
Does anyone have ANY idea about how I can get out of this problem?
UPDATE:
I have managed to boot to fastboot while connected to my pc.
The phone is unlocked but FRP is LOCKED, which means I can't flash anything.
I read about using Miracle Loader to remove the FRP lock, but it can't "see" my phone. Maybe I am doing it wrong?
Click to expand...
Click to collapse
Try to relock and then unlock the bootloader again. And make sure oem unlocking is enabled in dev options
Arsaam said:
Try to relock and then unlock the bootloader again. And make sure oem unlocking is enabled in dev options
Click to expand...
Click to collapse
Please read my previous post again
I can NOT boot normally. And as FRP is locked, then I can't relock or unlock the bootloader.
SnowmanDK said:
Please read my previous post again
I can NOT boot normally. And as FRP is locked, then I can't relock or unlock the bootloader.
Click to expand...
Click to collapse
Go to fast boot mode and from their try to flash meticulus recovery.
You can also try the adb method as well.
Visit meticulus.co.vu
Related
After Android tried to update itself to the newest version, it seemed that this failed and has caused a "boot failed" message. The tablet refuses to go into recovery mode, its marked as red. The only accessible mode is going into bootloader. After reading many forums and trying my luck with toolkits of all sorts (Nexus 7 Root Toolkit, Nexus Root Toolkit, Android SDK commands), the bootloader refuses to unlock. I have successfully installed the usb drivers since my pc recognizes the device. fastboot devices recognizes the devise but adb devices doesn't. The bootloader is locked and nothing else is accessible, whats worse is that through all of these toolkits and commands bootloader refuses to unlock, trying to unlock it always results in a failure message (unknown error). Commands such as format, unlock or erase fail in reviving the system. Anyone have any experience with this? I have searched for over a week now and im terribly frustrated by this. :silly:
AndiS21 said:
After Android tried to update itself to the newest version, it seemed that this failed and has caused a "boot failed" message. The tablet refuses to go into recovery mode, its marked as red. The only accessible mode is going into bootloader. After reading many forums and trying my luck with toolkits of all sorts (Nexus 7 Root Toolkit, Nexus Root Toolkit, Android SDK commands), the bootloader refuses to unlock. I have successfully installed the usb drivers since my pc recognizes the device. fastboot devices recognizes the devise but adb devices doesn't. The bootloader is locked and nothing else is accessible, whats worse is that through all of these toolkits and commands bootloader refuses to unlock, trying to unlock it always results in a failure message (unknown error). Commands such as format, unlock or erase fail in reviving the system. Anyone have any experience with this? I have searched for over a week now and im terribly frustrated by this. :silly:
Click to expand...
Click to collapse
do it the right way, dont use toolkits.
to unlock the bootloader, go into the bootloader(fastboot), connect the divice via usb, type..
fastboot devices(to make sure your device is visable)
fastboot oem unlock(to unlock the bootloader)
if you get an error, reboot the bootloader and try again. i had an error the first time on my replacement seven, second time it unlocked.
simms22 said:
do it the right way, dont use toolkits.
to unlock the bootloader, go into the bootloader(fastboot), connect the divice via usb, type..
fastboot devices(to make sure your device is visable)
fastboot oem unlock(to unlock the bootloader)
if you get an error, reboot the bootloader and try again. i had an error the first time on my replacement seven, second time it unlocked.
Click to expand...
Click to collapse
Thanks for the reply, i tried this several times, each time rebooting bootloader, but the command still posts an error in unlocking the bootloader. Recovery and Restart bootloader are marked in red font, Start is in Green, Power off White. I also tried flashing the recovery, since its inaccessible but because of bootloader being locked in won't allow me. :S Anything else you know that can be done ?
Reflash the bootloader?
edit: making VERY sure that you DON'T erase the existing bootloader first.
Try a manual update
AndiS21 said:
After Android tried to update itself to the newest version, it seemed that this failed and has caused a "boot failed" message. The tablet refuses to go into recovery mode, its marked as red. The only accessible mode is going into bootloader. After reading many forums and trying my luck with toolkits of all sorts (Nexus 7 Root Toolkit, Nexus Root Toolkit, Android SDK commands), the bootloader refuses to unlock. I have successfully installed the usb drivers since my pc recognizes the device. fastboot devices recognizes the devise but adb devices doesn't. The bootloader is locked and nothing else is accessible, whats worse is that through all of these toolkits and commands bootloader refuses to unlock, trying to unlock it always results in a failure message (unknown error). Commands such as format, unlock or erase fail in reviving the system. Anyone have any experience with this? I have searched for over a week now and im terribly frustrated by this. :silly:
Click to expand...
Click to collapse
You can try a manual update. Download the update and run adb sideload. That was not working for me, cause my Nexus it's allready updated, but hopefully it will work for you.
dave_uk said:
Reflash the bootloader?
edit: making VERY sure that you DON'T erase the existing bootloader first.
Click to expand...
Click to collapse
fortunatley though bootloader doesn't allow any command even the erase, it wouldn't allow me, nor formatting it as well. So i think the bootloader is intact. This is the screen i get from pressing Power and Vol Down.
pettymro said:
You can try a manual update. Download the update and run adb sideload. That was not working for me, cause my Nexus it's allready updated, but hopefully it will work for you.
Click to expand...
Click to collapse
As i have come to learn, adb can only function when debugging is enabled, in my device it wasn't unabled. Also the recovery program cannot be opened so sideloading through commands cannot be done. At least according to how some forums described the How To sideload through adb
try do it on another pc
AndiS21 said:
Thanks for the reply, i tried this several times, each time rebooting bootloader, but the command still posts an error in unlocking the bootloader. Recovery and Restart bootloader are marked in red font, Start is in Green, Power off White. I also tried flashing the recovery, since its inaccessible but because of bootloader being locked in won't allow me. :S Anything else you know that can be done ?
Click to expand...
Click to collapse
Can you post here the error message?
Israafiyl said:
Can you post here the error message?
Click to expand...
Click to collapse
Sure here it is. When i type in fastboot oem unlock, the message to unlock on my nexus comes up and when i click yes to unlock does the procedure start and end with failure.
AndiS21 said:
Sure here it is. When i type in fastboot oem unlock, the message to unlock on my nexus comes up and when i click yes to unlock does the procedure start and end with failure.
Click to expand...
Click to collapse
I don't know if fastboot let you flash the stock bootloader/recovery without unlocking but you may try:
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot flash recovery recovery-stock-jro03d-nakasi.img
Israafiyl said:
I don't know if fastboot let you flash the stock bootloader/recovery without unlocking but you may try:
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot flash recovery recovery-stock-jro03d-nakasi.img
Click to expand...
Click to collapse
thanks for the files, but bootloader won't allow me to change a single thing on it. Trying to flash recovery or the bootloader results in Failure result:bootloader locked!. :S
AndiS21 said:
thanks for the files, but bootloader won't allow me to change a single thing on it. Trying to flash recovery or the bootloader results in Failure result:bootloader locked!. :S
Click to expand...
Click to collapse
try one more time with a different port/pc if it daesn't work it may be a hardware fault, i think a corrupted sd.
(you will have to send it to warranty but don't worry, asus have a really good assistence, you may have a new nexus in a less than 2 days)
Manual update
AndiS21 said:
As i have come to learn, adb can only function when debugging is enabled, in my device it wasn't unabled. Also the recovery program cannot be opened so sideloading through commands cannot be done. At least according to how some forums described the How To sideload through adb
Click to expand...
Click to collapse
Use the volume up/down keys to navigate to "Recovery mode", then press the power button.
When the Android with the red exclamation point appears, hold down power first, followed quickly by volume down and volume up. (So that to start, you're holding down power, then you're holding down all three). After 2-3 seconds, release all three keys.
Use the volume up/down keys to select "apply update from ADB," then press power to select it.
On your computer, open up a command prompt or terminal window.
Using the command line, navigate to the folder containing the ADB executables and the update file.
type:
adb.exe sideload <update filename>
On my Nexus with Jelly 4.2 usb debugging is not enabled too, but I still get the option in recovery mode menu. Operation not succesful cause I cannot upgrade from 4.2 to 4.2. I will wait for another update and then try it again. Good luck!
Israafiyl said:
try one more time with a different port/pc if it daesn't work it may be a hardware fault, i think a corrupted sd.
(you will have to send it to warranty but don't worry, asus have a really good assistence, you may have a new nexus in a less than 2 days)
Click to expand...
Click to collapse
I tried it on the laptop too, even changed the drivers to universal naked drivers, but nothing! Restart bootloader is with red, clicking it wont reboot the tablet, also recovery mode red, the only working button is the Start (green) but that leads to boot failure and power off.
pettymro said:
Use the volume up/down keys to navigate to "Recovery mode", then press the power button.
When the Android with the red exclamation point appears, hold down power first, followed quickly by volume down and volume up. (So that to start, you're holding down power, then you're holding down all three). After 2-3 seconds, release all three keys.
Use the volume up/down keys to select "apply update from ADB," then press power to select it.
On your computer, open up a command prompt or terminal window.
Using the command line, navigate to the folder containing the ADB executables and the update file.
type:
adb.exe sideload <update filename>
On my Nexus with Jelly 4.2 usb debugging is not enabled too, but I still get the option in recovery mode menu. Operation not succesful cause I cannot upgrade from 4.2 to 4.2. I will wait for another update and then try it again. Good luck!
Click to expand...
Click to collapse
recovery mode cannot be opened, the text font is red on the tablet and clicking it does nothing. :S
Also tried to completley flash the device but unable to. Going back and doing an fastboot oem unlock yields the same feedback.
Unlock Bootloader on 4.2
Hello, I was wondering if the bootloader in 4.2 can be unlocked the same way as it was on 4.1.2? I recently got a new nexus 7 and updated to 4.2.
Thanks and Cheers!
After some research into my issue, i have discovered that other users have posted "unbricking" solutions through a program called nvflash, when the device is put in APX mode. But unfortunatley i've yet to find a nvflash solution for nexus 7. I will experiment with the commands and what the others have reported as a solution.
ErnestoV31 said:
Hello, I was wondering if the bootloader in 4.2 can be unlocked the same way as it was on 4.1.2? I recently got a new nexus 7 and updated to 4.2.
Thanks and Cheers!
Click to expand...
Click to collapse
Yes it can.
Sent from my GT-I9300 using Tapatalk 2
Hi i need to unroot and factory reset the phone. Oneplus 2 What ive already done or tried: I started to try unrooting it through superSU but that didnt work i just waited waited and nothing hapened. so then i tried to fastboot img but just got error the device is locked even though i did enable oem unluck and usb debuging. so then i wrote in cmd: fastboot oem unlock and now the phone starts up to the op logo then restard into it again after a second D'=
Im not familiar with forums and very stressed to get my phone working so i would be very very gratefull for help.
now i cant even charge it the batery logo doesnt come up after i did fasboot oem unlock again.... rip
spacebite said:
Hi i need to unroot and factory reset the phone. Oneplus 2 What ive already done or tried: I started to try unrooting it through superSU but that didnt work i just waited waited and nothing hapened. so then i tried to fastboot img but just got error the device is locked even though i did enable oem unluck and usb debuging. so then i wrote in cmd: fastboot oem unlock and now the phone starts up to the op logo then restard into it again after a second D'=
Im not familiar with forums and very stressed to get my phone working so i would be very very gratefull for help.
Click to expand...
Click to collapse
spacebite said:
no i cant even charge it the batery logo doesnt come up after i did fasboot oem unlock again.... rip
Click to expand...
Click to collapse
Got to OnePlus support center and go in download section and download official ROM. Hold power and volume up bottons and connect it to PC. After that go in folder where adb files are located on your PC (If you don't have them, search on Google for "adb install 15 sec"). Hold left shift on your keyboard and right click your mouse in that folder on an empty space. Click something related with command window and type "fastboot devices". If you get some kind of feedback it's 2minute of work! If you don't have anything come up, try to start your device in fastboot mode again (second sentence in this post). After you got a feedback from command "fastboot devices" flash custom recovery (I suggest TWRP, Google it and download the .IMG file for your device). To flash a custom recovery type this in command line: "fastboot flash recovery IMAGE_NAME.img"
*replace IMAGE_NAME with actual image name...
After that boot in recovery by disconnecting the phone and powering off the phone. Press and hold power button and volume down buttons till blue TWRP logo appears. After that connect your device on PC and transfer your .Zip file(ROM) to internal memory of your device. You should go back to main menu of recovery and select wipe>advanced wipe, select everything BUT INTERNAL STORAGE!!!***IMPORTANT***
Then you just install ROM like you would normally do...
Press thanks it i helped! Hope I didn't missed something.
This is written in mind with that you have unlocked bootloader like you have written in your post...
x8Cooler said:
Got to OnePlus support center and go in download section and download official ROM. Hold power and volume up bottons and connect it to PC. After that go in folder where adb files are located on your PC (If you don't have them, search on Google for "adb install 15 sec"). Hold left shift on your keyboard and right click your mouse in that folder on an empty space. Click something related with command window and type "fastboot devices". If you get some kind of feedback it's 2minute of work! If you don't have anything come up, try to start your device in fastboot mode again (second sentence in this post). After you got a feedback from command "fastboot devices" flash custom recovery (I suggest TWRP, Google it and download the .IMG file for your device). To flash a custom recovery type this in command line: "fastboot flash recovery IMAGE_NAME.img"
*replace IMAGE_NAME with actual image name...
After that boot in recovery by disconnecting the phone and powering off the phone. Press and hold power button and volume down buttons till blue TWRP logo appears. After that connect your device on PC and transfer your .Zip file(ROM) to internal memory of your device. You should go back to main menu of recovery and select wipe>advanced wipe, select everything BUT INTERNAL STORAGE!!!***IMPORTANT***
Then you just install ROM like you would normally do...
Press thanks it i helped! Hope I didn't missed something.
This is written in mind with that you have unlocked bootloader like you have written in your post...
Click to expand...
Click to collapse
thanks i will try when i get home
Fallow this and don't trust any guides written out of memory with likely any mistakes.. (no offense)
This guide has various approaches to recover your phone, remember to research first and don't type carelessly any adb commands, it's not enough to just tick "oem unlock" in developer options, you'd have to type command on fastboot too, to unlock the bootloader.. there are many guides and youtube tutorials on this subject, absolutely unnecessary to blindly kill it, anyways I'll never understand how you can be so reckless with your phone..
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Edit: the state you brought your phone into is called "hard bricked" - have fun..
Sent from my OnePlus2 using XDA Labs
spacebite said:
thanks i will try when i get home
Click to expand...
Click to collapse
Don't!
If you get no joy from following the instructions in the link given by @Sam Nakamura, try @fareed_xtreme's Official OP2 Stock Reset to OOS 3.0.2
Sam Nakamura said:
Fallow this and don't trust any guides written out of memory with likely any mistakes.. (no offense)
This guide has various approaches to recover your phone, remember to research first and don't type carelessly any adb commands, it's not enough to just tick "oem unlock" in developer options, you'd have to type command on fastboot too, to unlock the bootloader.. there are many guides and youtube tutorials on this subject, absolutely unnecessary to blindly kill it, anyways I'll never understand how you can be so reckless with your phone..
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Edit: the state you brought your phone into is called "hard bricked" - have fun..
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Aight thank you i had some suspicion it might be ...-bricked didnt know which though so thank you
If you can get in the bootloader then possibly the device is still OK. Just need to get the right ROM.
Try different TWRP versions. Sometimes, one particular version can save the world.
I ran into a bit of an issue and am stuck with a bootlooping G6 US997.
What got me into this pickle:
I unlocked the bootloader
I flashed TWRP successfully, by:
Running fastboot flash recovery TWRP.img
Unplugging USB and holding Vol- and Power from fastboot, then lifting and re-pressing Power when the LG logo appeared
Hitting Yes, Yes
Being in TWRP and allowing modification of System
Formatting Data (Wipe > Format Data > Yes)
I installed the DM verity and encryption file so that it would boot
I wiped Cache/Dalvik
I rebooted into System
It booted successfully so I went back to TWRP and installed Lineage OS, Open Google Apps, and the Lineage SU addon
This booted successfully, so I went and with OEM unlock disabled booted into fastboot to see if I could get rid of the annoying orange screen at the start saying that the bootloader was unlocked
To do this, I ran fastboot oem lock, not seeing/ignoring the red text at top telling me to Please check "Enable OEM unlock" in Developer options.
I then rebooted with fastboot reboot and I encountered a red warning: "Your device has failed a routine safety check and will not boot." It is now in a bootloop at that screen, cycling between black, the LG logo, and the warning.
I managed to enter recovery mode (with the key-combo) and got the stock recovery "factory reset and wipe" option, which I had been previously getting when entering TWRP, so I selected "Yes, Yes" and then it went back into the bootloop, completely avoiding TWRP.
Where I currently am:
I can get into fastboot mode (Vol- with usb plugged in) and I can get into the factory reset mode which is the gateway into TWRP. I cannot get into TWRP, and I cannot flash anything, boot into any images, or unlock the bootloader ( Please check "Enable OEM unlock" in Developer options). If I could do that I think I can get it fixed.
My questions:
How can I do the OEM unlock without access to Developer Options? (I have the unlock file to flash, just need access)
Or How can I bypass the red warning page and boot into Lineage OS?
Any help would be appreciated, I really would like to get this working.
Have you tried to boot in download mode and flash the original firmware with LGUp+Uppercut?
Killua96 said:
Have you tried to boot in download mode and flash the original firmware with LGUp+Uppercut?
Click to expand...
Click to collapse
I've been trying to, I forgot to update the post though. I found the US99715a_05_0908 KDZ, and I installed Uppercut, LGUP, and the drivers from the Uppercut thread, but whatever I do it never recognizes the device. And when I go into download mode it quickly pops back out to the warning screen after about 10 seconds. After the warning it reboots in 10 seconds, I have a pretty small window.
I was thinking of trying LG Flash Tool 2.0.1.6, yet I haven't figured out how to use it yet. I may try more with Uppercut, maybe different drivers? If there were a way to keep it in download mode longer, that would really help. Thank you for replying, I've seen your name around the forums!
mwsundberg said:
I've been trying to, I forgot to update the post though. I found the US99715a_05_0908 KDZ, and I installed Uppercut, LGUP, and the drivers from the Uppercut thread, but whatever I do it never recognizes the device. And when I go into download mode it quickly pops back out to the warning screen after about 10 seconds. It looks like it might still be in download mode, but interrupted by the warning, the way the screens flash. After the warning it reboots in 10 seconds, I have a pretty small window.
I was thinking of trying LG Flash Tool 2.0.1.6, yet I haven't figured out how to use it yet. I may try more with Uppercut, maybe different drivers? Thank you for replying, I've seen your name around the forums!
Click to expand...
Click to collapse
I know this could be a stupid question, but have you tried to run the unlock command? If yes, what does it says?
Killua96 said:
I know this could be a stupid question, but have you tried to run the unlock command? If yes, what does it says?
Click to expand...
Click to collapse
fastboot flash unlock unlock.bin gives:
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.047s]
writing 'unlock'...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.063s
I had flashed it before but forgot to reenable the option in developer tools, I can't find a way to enable it from fastboot yet.
mwsundberg said:
fastboot flash unlock unlock.bin gives:
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.047s]
writing 'unlock'...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.063s
I had flashed it before but forgot to reenable the option in developer tools, I can't find a way to enable it from fastboot yet.
Click to expand...
Click to collapse
You can't, fastboot is a mode that allows many things but it's not a God-like mode where you can do everything.
By locking the bootloader while having unsigned partions flashed you have essentially hard bricked the device, and if the only way to flash stock signed partitions (lgup+Uppercut) doesn't work it means that you have to find a way to boot the phone in qhsusb9008 (usually by hardware) and try to flash a tot file, if there is one.
Sorry but is highly unlikely that you will able to recover your G6, hope to be wrong.
Killua96 said:
You have to find a way to boot the phone in qhsusb9008 (usually by hardware) and try to flash a tot file, if there is one.
Sorry but is highly unlikely that you will able to recover your G6, hope to be wrong.
Click to expand...
Click to collapse
How might I go about doing this, or is there a chance I can actually access LGUP and have just been messing up so far? If there were a video of what using LGUP and Uppercut properly looked like, that would be really helpful.
Also, is there any hope of LG or a phone store with LGUP being able to fix this (for less than the price of a new G6)?
mwsundberg said:
Also, is there any hope of LG or a phone store with LGUP being able to fix this (for less than the price of a new G6)?
Click to expand...
Click to collapse
It depends on how much it'll cost to you a new G6, they could ask you maybe 200-250 bucks.
mwsundberg said:
How might I go about doing this, or is there a chance I can actually access LGUP and have just been messing up so far? If there were a video of what using LGUP and Uppercut properly looked like, that would be really helpful.
Click to expand...
Click to collapse
Go in fastboot with the phone connected to the PC, keep pressed vol- and power until the phones turn off in that exact moment leave those two buttons and keep pressing only the vol+ one, this should bring you in download mode, if it stuck then you could use LGUP and Uppercut, otherwise there is nothing software related that you can do, imho obviously
Killua96 said:
Go in fastboot with the phone connected to the PC, keep pressed vol- and power until the phones turn off in that exact moment leave those two buttons and keep pressing only the vol+ one, this should bring you in download mode, if it stuck then you could use LGUP and Uppercut, otherwise there is nothing software related that you can do, imho obviously
Click to expand...
Click to collapse
Managed to get a messed up G6 from a friend working again. Thanks. XDA forever
Guys, need help !!!
I have tried to install SEA oreo version on Indian phone via LGUP... Flash was successful (100%) but it got stuck on LG Logo..
Procedure followed for H870DS (IND)
1. Downloaded SEA Oreo KDZ File (H870DS20a_00_OPEN_SG_DS_OP_0518.kdz)
2. Installed LGUP... Made new Common folder inside C/Prog file/LG/Model
3. Extracted DLL file from KDZ & renamed it LGUP_Common.dll and kept in Common folder
4. Entered in download mode
5. Opened LGUP.. selected KDZ and Upgrade..
6. Boom.. 100% completed.. it has shown that phone is rebooting..
7. But then it got stuck on LG Screen
I cant access recovery now
I can open Hard Reset option (Vol down+Power) only.. Made hard reset but no use
I cant enter in download mode
I dont know if it is charging or not
It is not even switching off by pressing power button for long time
Pl help me...
---------- Post added at 08:33 PM ---------- Previous post was at 08:30 PM ----------
it has anything to do with "Enable OEM unlock" in Developer options"
There is a way to enter download mode. Just hold down button and power button. Just when you see LG logo leave power button for a second. Push power button again and hold with down button. Now press yes twiche for the hard reset prompt. Now IMPORTANT, when screen goes black immediately press and hold up button. While holding up button plug usb cable into the PC. Now use Uppercut 1.0.0.0 and flash your kdz.
Same issue, Just that I was trying downgrade to Nougat. Oreo messed up my phone to the extent that, none of the sensors (including Fingerprint are not working). The load was a success, but after 1st restart it went into boot loop.
I only had USB Debug enabled in the DO before this issue, so it might work with the OEM unlock dissabled.
Software needed...
LG Bridge
Meathod...
Please charge the phone before this is done, at least 80%, will be better.
Connect the computer with LG G6 H870DS (Indian), might work for all models. "not tested"
If the USB debug is enabled, you will hear the USB disconnection and connection notification sound during bootloop
When you hear disconnection sound, press the "volume up key" until the Firmware Update mode appears
Once you are in Firmware Update mode, the USB connection will be stable (In bootloop, it keeps disconnecting)
Disconnect the USB cable
Start LG Bridge/Software Updates, connect when App asks to connect the phone
This will update you phone to the latest official software update..
This solution can work for all phones that have a hardware based menu to get into Firmware Update mode, definitely works on all LG phones to get out of bootloop. I have tested on LG G2, G4 and G6 Indian devices.
And a suggestion to all mates is, to enable USB debugging and the OEM unlock as soon as you get hands on your new devices. Always saves the hassle of running around the LG service center, its a big issue in India at-least. I love LG for its hardware quality but sadly LG smartphones have a bad history of software issues
Good evening! I hope you can help me.
I flashed LineageOS 14.1, but I wanted to go back to EMUI. I made all the wipes and tried to flash different stock firmwares through a forced update (volume buttons + power button), but it never worked. At that point, I read about a guy in this forum who suggested to create a flashable zip with Huawei Update Extractor: I followed the suggestion and tried to flash it with TWRP. No error was given, but when I tried to restart, TWRP told me I had no OS installed. I thought it was strange, so I tried to restart anyway. That's when I got in rescue mode. I can't get into the recovery and I can't use fastboot. What rescue mode shows me is:
RESCUE MODE
Attention!
Please update system again
Update User Guide:
*link*
*android avatar*
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
Pressing the three buttons, I'm able to force an update. The problem is I can't find a firmware that doesn't get rejected. With Lollipop firmwares, it starts to install, but it fails at 12%. With Marshmallow ones, the installation process doesn't even start.
What can I do to make it work again? I'm very sad because this phone was gifted to me a couple of days ago and I already messed it up. I don't even know how to turn it off.
What can I do to get in fastboot mode? At that point, what should I do to flash the stock firmware? Or maybe do I need to find the first stock firmware ever installed into this phone to make the forced update work?
Please, I need help. Thank you in advance!
P.S. The phone's model is ALE-L21. I live in Italy, so I assume it's a European version.
Did you managed to fix this?
Jhon_Locke said:
Did you managed to fix this?
Click to expand...
Click to collapse
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
ErikChimello said:
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
Click to expand...
Click to collapse
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Jhon_Locke said:
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Click to expand...
Click to collapse
No, it doesn't show anything if I write that command...
I guess mine won't ever boot into the rom because it seems like there's no system installed. I made some researches and found out there are some softwares that let you reflash the partitions IF the phone is recognized as "HUAWEI USB COM 1.0". I'm still trying to figure out how to do it correctly though. I feel like if I do something wrong, then my phone won't probably turn on again.
In your case, you should be able to flash a custom rom without any issue. You just have to be very careful and inform you as much as you can: I don't want your phone to end up like mine?. Anyway, it seems pretty hard to go back to the stock rom, so think about it before you flash a custom rom. Also, make a Nandroid Backup is very important.
Hi,
I want to install a custom ROM in my Note 4 and upgrade from Android 6.01 to Android 11, and I know that the first step is to unlock the bootloader to avoid issues later on in the process.
I've researched different ways of doing it, and this is what I found:
1. Enable the OEM unlocking option in the phone.
The phone does not have the option to enable OEM unlocking in the developer options of the phone.
2. Go to download mode (starting phone with Power+Home+Vol Down keys).
At this point 3 options should appear. One of them being Press Vol Up to enter Device unlock mode. Well, only 2 options appear and the one missing is Enter
Device unlock mode.
3. Start in Recovery Mode, then select Enter Fastboot.
I started the phone using Power+Volume up+Home to enter Recovery Mode, and a menu presented with several options which should have included the
Enter Fastboot option, but the option is missing in the menu.
4. Use your PC to issue adb+fastboot commands.
I successfully connected the phone to the PC and tried to issue the corresponding commands using adb and fastboot. Adb commands work well. Fastboot
commands do not "see" the phone. (just in case I've tried several different drivers)
At this point I've run out of options, and everything points to the "hard-to-believe" fact that this phone doesn't have the fastboot mode.
Is it possible that the phone does not have a way to unlock the bootloader? or at least checking that the bootloader is unlocked in a way that leaves no doubt about it? (I can't risk bricking the phone based on the assumption that the bootloader is factory unlocked)
I will really appreciate any help in working this sort of mystery out.
Thank you!!
I
rfernandez2007 said:
Hi,
I want to install a custom ROM in my Note 4 and upgrade from Android 6.01 to Android 11, and I know that the first step is to unlock the bootloader to avoid issues later on in the process.
I've researched different ways of doing it, and this is what I found:
1. Enable the OEM unlocking option in the phone.
The phone does not have the option to enable OEM unlocking in the developer options of the phone.
2. Go to download mode (starting phone with Power+Home+Vol Down keys).
At this point 3 options should appear. One of them being Press Vol Up to enter Device unlock mode. Well, only 2 options appear and the one missing is Enter
Device unlock mode.
3. Start in Recovery Mode, then select Enter Fastboot.
I started the phone using Power+Volume up+Home to enter Recovery Mode, and a menu presented with several options which should have included the
Enter Fastboot option, but the option is missing in the menu.
4. Use your PC to issue adb+fastboot commands.
I successfully connected the phone to the PC and tried to issue the corresponding commands using adb and fastboot. Adb commands work well. Fastboot
commands do not "see" the phone. (just in case I've tried several different drivers)
At this point I've run out of options, and everything points to the "hard-to-believe" fact that this phone doesn't have the fastboot mode.
Is it possible that the phone does not have a way to unlock the bootloader? or at least checking that the bootloader is unlocked in a way that leaves no doubt about it? (I can't risk bricking the phone based on the assumption that the bootloader is factory unlocked)
I will really appreciate any help in working this sort of mystery out.
Thank you!!
Click to expand...
Click to collapse
If your phone is exynos, just factory data reset and go to download mode and flash TWRP.
SweptDevUwU said:
I
If your phone is exynos, just factory data reset and go to download mode and flash TWRP.
Click to expand...
Click to collapse
Thank you for your answer!
It is Exynos indeed.
Have you tried this in a similar situation? or in case you haven't, could you please explain how you are certain that this will work well?
Because it is difficult to ignore the large number of warnings about going on with the flashing without being sure that the bootloader is unlocked.
rfernandez2007 said:
Thank you for your answer!
It is Exynos indeed.
Have you tried this in a similar situation? or in case you haven't, could you please explain how you are certain that this will work well?
Because it is difficult to ignore the large number of warnings about going on with the flashing without being sure that the bootloader is unlocked.
Click to expand...
Click to collapse
Hello, I'm using exynos as well, just like he said just install a compatible TWRP then flash a custom rom you want
https://forum.xda-developers.com/t/...xy-note-4-custom-recovery-07-28-2021.4311777/
karlsuu said:
Hello, I'm using exynos as well, just like he said just install a compatible TWRP then flash a custom rom you want
https://forum.xda-developers.com/t/...xy-note-4-custom-recovery-07-28-2021.4311777/
Click to expand...
Click to collapse
Hi!
Thank you for your answer.
Ok. I'll review/follow the procedure in the link you suggested and let you know how it goes.
Hi,
It worked!!
Thank you very much to both of you!