Database Users

[GUIDE] How To Enter Fastboot Mode

This is the method tried on H815T model. But I think this should work with also other H815 models (other devices cannot say). Thanks to @autoprime, @thecubed and @Unjustified Dev for this.
Disclaimer: I am not responsible if your device gets into any more trouble for this.
Steps:
1. Download & clean install LG Drivers in your pc if u don't have it already.
2. Go into download mode by presing down the UP button and connecting the usb cable to the pc.
3. Go into LG ROOT folder. see this link to download: http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
4. Double click on ports.bat to know your COM port. Let's say it's COM4.
5. Open a windows command promt by Shift+Rt Click into the Lg Root folder.
6. Now send these commands:
Code:
Send_Command.exe \\.\COM4
It will reply
Code:
SPECIAL COMMAND : ENTER , LEAVE
#
7. Now command type
Code:
id
It should reply
Code:
uid=(0)root gid=(0)root
#
8. Now type
Code:
dd if=/dev/zero bs=8192 seek=35840 count=5120 of=/dev/block/mmcblk0
It will reply
Code:
#
9. Now pull out your battery, put it back in, go into HARD RESET mode by pressing down DOWN BUTTON+POWER BUTTON together and when the LG logo apprears, release the power button for a second and press it back again.
10. Now in HARD RESET, it will ask you whether you want to reset everything or not. Select "No" and it will take you to fastboot mode.
Special note:
1. @autoprime told me to factory reset everything before starting this whole process. I did as my bootloader was locked. Don't know how it affects in unlocked bootloader.
2. How to get out of fastboot normally: I don't know it quitely. My bootloader was locked, so neither I could flash any system file through fastboot, nor "fastboot reboot" or "fastboot reboot bootloader" worked for me. @autoprime told me to get out of fastboot, manually go into download mode, then pull out your battery and put back in. Actually you can't get out of the fastboot that way until you flash a KDZ.
Thank u. Reply in the comments if fastboot could help you any.

delete

Hi,
Thank you very much for this Guide. Unfortunately, having tried to unbrick my device (H815) previously by hard resetting and not having access to Android to re-activate ADB, the Shell (Send_command.exe) didn't help me (at every command it returns a "FAIL" message, my phone is recognized by Windows by the way).
So I couldn't get into Fastboot by following this Guide.
Hope it works for others, waiting for results!

TheBledard said:
Hi,
Thank you very much for this Guide. Unfortunately, having tried to unbrick my device (H815) previously by hard resetting and not having access to Android to re-activate ADB, the Shell (Send_command.exe) didn't help me (at every command it returns a "FAIL" message, my phone is recognized by Windows by the way).
So I couldn't get into Fastboot by following this Guide.
Hope it works for others, waiting for results!
Click to expand...
Click to collapse
You couldn't get into fastboot or u couldn't flash anything in fastboot? I cannot make my device recognised in adb too, but it is recognised in fastboot. U need to have the adb and fastboot setup in your pc. But I couldn't flash anything in fastboot as it shows my device is locked although someone said, theoritically it was supposed to flash system files through fastboot.

nipun1110 said:
You couldn't get into fastboot or u couldn't flash anything in fastboot? I cannot make my device recognised in adb too, but it is recognised in fastboot. U need to have the adb and fastboot setup in your pc. But I couldn't flash anything in fastboot as it shows my device is locked although someone said, theoritically it was supposed to flash system files through fastboot.
Click to expand...
Click to collapse
I couldn't get into Fastboot at all. Any command typed in send_command.exe gives "Fail" as result... Phone is connected in Download Mode and recognized in Windows, DIAG1 port is COM4.
Screenshot attached

lock bootloader , fastboot unnecessary

29y6145 said:
lock bootloader , fastboot unnecessary
Click to expand...
Click to collapse
True. I didn't realise that before, so gave it a try. But this may help those with unlocked bootloader.
Sent from my LG-H815 using Tapatalk

I always get a "FAIL" reply. Any ideas?

nipun1110 said:
True. I didn't realise that before, so gave it a try. But this may help those with unlocked bootloader.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
With an unlocked bootloader...
Code:
adb reboot bootloader

nobnut said:
With an unlocked bootloader...
Code:
adb reboot bootloader
Click to expand...
Click to collapse
Hahahah tru!

nobnut said:
With an unlocked bootloader...
Code:
adb reboot bootloader
Click to expand...
Click to collapse
maybe u r suggesting to say
fastboot reboot bootloader
right?
Sent from my LG-H815 using Tapatalk

This does not work for me, I have an unlocked bootloader, but just get the response "FAIL".

And... Why don't you just zero the laf partition instead through an adb shell? What does this do that's different?

If we can get into fastboot, can we then do something like
Code:
fastboot boot recovery.img
to get into a custom type recovery and do a backup? I'm on the AT&T H810 version, locked bootloader, I don't know if that means a big fat NO lol or if this method of getting into fastboot mode would even work on my variant.

petermg said:
If we can get into fastboot, can we then do something like
Code:
fastboot boot recovery.img
to get into a custom type recovery and do a backup? I'm on the AT&T H810 version, locked bootloader, I don't know if that means a big fat NO lol or if this method of getting into fastboot mode would even work on my variant.
Click to expand...
Click to collapse
no one should be wiping laf or recovery to get into fastboot. it's a dumbed down fastboot that doesn't let anything flash or boot. the directions I gave OP were in a PM as a last resort because he was stuck in download mode with no booting and wanted to try fastboot. It was never meant to be suggested in public to users who might think they can get anywhere with it.

autoprime said:
no one should be wiping laf or recovery to get into fastboot. it's a dumbed down fastboot that doesn't let anything flash or boot. the directions I gave OP were in a PM as a last resort because he was stuck in download mode with no booting and wanted to try fastboot. It was never meant to be suggested in public to users who might think they can get anywhere with it.
Click to expand...
Click to collapse
Ok then if u suggesting me I should delete the post, I will ask Moderator to do so.
Sent from my LG-H815 using Tapatalk

It's good

Holly molly sir! You are a legend. Long story not so short. My lg got the bootloop bug. Took 2 months to fix, but apparently they changed my locked to three uk H815 "eu open" motherboard with actually unlocked one. So I was finally able to unlock boot-loader, root and **** up (LOL). Apparently I didn't install twrp properly (you'd think "fastboot boot twrp.img" would not install it but run it once) And i was following this to get Android M on. But it requires reboot before boot-loader is flashed. Right when i clicked reboot i figured it wont start in twrp but in stock recovery. So I couldn't even get proper bootloop, it would cut half way into the LG logo. I reckon kdz-ing would havedone the trick, but god it takes ages to DL the kdz file. So in the mean time i found this legendary post. The odd thing was i had to click Yes, on the factory reset screen, but it got me to "Fastboot mode started" and from there i booted into twrp and finished what it had started, currently its Optimising app 35 of 55. Nice one OP, Nice One!

hi i have unlocked bootloader. but i keep getting FAIL as response

nipun1110 said:
8. Now type
Code:
dd if=/dev/zero bs=8192 seek=35840 count=5120 of=/dev/block/mmcblk0
It will reply
Code:
#
Click to expand...
Click to collapse
Hi,
how can I change it back to default Factory reset??

Stuck in Bootloop

US996 Unlocked, stock rom. I was in XDA Forums and saw there were app updates, one being Play Store. I updated. When I tried to get into Play Store, the message "this version of play store is incompatible with your device, go to settings and disable app update (or something like that). I tried but the app was not listed in settings. I tried to reboot and now the phone bootloops. All I can get is the warning that the software cannot be checked for corruption and then a quick display of the LG logo, then screen off, and then LG logo again and then warning screen, etc. If I try to reboot into recovery I get the Factory data reset screens and I answer both "yes" and the phone goes into adb mode.. From adb mode I can fastboot reboot, which puts me back into the above loop, or fastboot bootloader, which merely returns me to the adb screen. What can I do now?

Maybe try relocking the bootloader. I am pretty sure (someone correct me if I am wrong) that that pop-up of the "cannot check for corruption" usually only shows when the bootloader is unlocked.

XP_1 said:
Maybe try relocking the bootloader. I am pretty sure (someone correct me if I am wrong) that that pop-up of the "cannot check for corruption" usually only shows when the bootloader is unlocked.
Click to expand...
Click to collapse
Is that even possible? Don't know how to do it.

PhoneBull said:
Is that even possible? Don't know how to do it.
Click to expand...
Click to collapse
Try entering
Code:
fastboot oem device-info
into Fastboot on your computer to see if it says it is unlocked when in fastboot mode.

XP_1 said:
Try entering
Code:
fastboot oem device-info
into Fastboot on your computer to see if it says it is unlocked when in fastboot mode.
Click to expand...
Click to collapse
I get "FAILED (remote: unknown command)"

Do you have fastboot installed on your computer? (Something you would have had to have intentionally installed) If not google Minimal Fastboot /ADB and install it, enter the supposed ADB screen you are talking about and see if it makes contact with your phone.

XP_1 said:
Do you have fastboot installed on your computer? (Something you would have had to have intentionally installed) If not google Minimal Fastboot /ADB and install it, enter the supposed ADB screen you are talking about and see if it makes contact with your phone.
Click to expand...
Click to collapse
I have the fastboot on the PC that I used to unlock the bootloader.. I enter fastboot on the PC via the administrative command prompt. With the phone in the fastboot mode, I type "fastboot devices" on the PC and get a proper response (LGUS996ab**** fastboot). If I enter ""fastboot reboot" I get the bootloop. If I enter "fastboot bootloader" I wind up in Fastboot Mode on the phone again. I was hoping there was a "fastboot recovery" command but there doesn't seem to be. I don't know what to do next. I am not all that familiar with what can be done from fastboot. My only experience with it was when I unlocked the phone. I am desperate!

Okay, so if you do not have TWRP installed on your phone, then I don't know if you can save your data. You can try to
Code:
fastboot erase cache
and see if it helps, or if not and just reset the device fastboot oem lock I think. Maybe ask around in the unlocking help threads or perhaps someone with more knowledge will chime in. If none of this works, then there are some instructions on how to get your phone back to stock in the News and Guides section.
EDIT: Maybe try the power+volume down. It may work? I have tried it and never got it to successfully work. But you can try it.

XP_1 said:
Okay, so if you do not have TWRP installed on your phone, then I don't know if you can save your data. You can try to
Code:
fastboot erase cache
and see if it helps, or if not and just reset the device fastboot oem lock I think. Maybe ask around in the unlocking help threads or perhaps someone with more knowledge will chime in. If none of this works, then there are some instructions on how to get your phone back to stock in the News and Guides section.
Click to expand...
Click to collapse
Thanks for your help. I DO have TWRP installed and have used it often for backups. But now the only way I know to TRY to get to it is by the power/vol down until LG logo, then release/repress power button sequence but this just gets me into fastboot mode. II have some recent backups saved on my micro SD card - is there any way to flash one of them through fastboot if I load one onto the PC?

Yeah. My bad. Okay, so how I get into TWRP is through the EasyRecowvery.
Go ahead and download it from Git-Hub (1.3b3).
Now extract it and run the cmd program. Enter 5. which is extras and stuff and then enter 5 again in the sub menu which will let you boot into recovery. When you are in recovery, and plugged into your computer, you should be able to either flash or drag and drop like a flash drive on the the phone. Hope that helps a little bit.

XP_1 said:
Yeah. My bad. Okay, so how I get into TWRP is through the EasyRecowvery.
Go ahead and download it from Git-Hub (1.3b3).
Now extract it and run the cmd program. Enter 5. which is extras and stuff and then enter 5 again in the sub menu which will let you boot into recovery. When you are in recovery, and plugged into your computer, you should be able to either flash or drag and drop like a flash drive on the the phone. Hope that helps a little bit.
Click to expand...
Click to collapse
I don't have T-Mobile. I have Verizon Wireless on the US996. Will that work?

PhoneBull said:
I don't have T-Mobile. I have Verizon Wireless on the US996. Will that work?
Click to expand...
Click to collapse
Since you are only rebooting into recovery and not flashing anything it might. If not, it will just fail and not harm anything. Last thing to try is the
Code:
adb reboot recovery
which is the only thing I can think of and I think you already tried it. Otherwise you will need to just go stock.

[ZE552KL] Bizzare issue when flashing TWRP

On my ZF3, I'm on Nougat with the bootloader unlocked and I've confirmed that.
Followed instructions on the XDA ZF3 ROOTING GUIDE thread & ZF3 Toolkit, I can't seem to flash TWRP due to an error.
"
sending 'recovery' (26636 KB)...
OKAY [ 0.912s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 1.075s
"
I've enabled USB debugging and even restarted, redownloaded drivers, changed USB ports and re did again but still the same error.
Any tips and solution?

Try booting TWRP first, then flashing from within TWRP.
The command is "fastboot boot <path to TWRP image>".

sensi277 said:
Try booting TWRP first, then flashing from within TWRP.
The command is "fastboot boot <path to TWRP image>".
Click to expand...
Click to collapse
Just tried right now, did the command but its stuck at booting. My zf3 didn't boot the .img

Prev was too blurry

Have you been able to flash anything via fastboot from that computer?
Which OS are you using, windows? Firewall disabled? Do you have another computer you can try it on? From what I've read, it's a driver issue causing this and since you've tried reinstalling them, I'd try downloading the USB bootable version of Linux and try again. The commands are the same.
You may be able to flash it through an adb shell too, but I'd try the Linux USB first. On the ze552kl, the recovery partition is #59, so the command would be "dd if=/sdcard/TWRP.bin of=/dev/block/mmcblk0p59".
Edit: I see you posted in the other section you tried other computers so i guess try the DD command. Only thing is, you should back up your original partition first just in case because something is definitely bizarre. Run "dd if=/dev/block/mmcblk0p59 of=/sdcard/recoverybak.bin" first so you can revert if it goes awry.

wang1chung said:
Have you been able to flash anything via fastboot from that computer?
Which OS are you using, windows? Firewall disabled? Do you have another computer you can try it on? From what I've read, it's a driver issue causing this and since you've tried reinstalling them, I'd try downloading the USB bootable version of Linux and try again. The commands are the same.
You may be able to flash it through an adb shell too, but I'd try the Linux USB first. On the ze552kl, the recovery partition is #59, so the command would be "dd if=/sdcard/TWRP.bin of=/dev/block/mmcblk0p59".
Edit: I see you posted in the other section you tried other computers so i guess try the DD command. Only thing is, you should back up your original partition first just in case because something is definitely bizarre. Run "dd if=/dev/block/mmcblk0p59 of=/sdcard/recoverybak.bin" first so you can revert if it goes awry.
Click to expand...
Click to collapse
How do you restore that ".bin" if anything fails? And if it does fail, what's the "problem" that I'll be having to fix?

TiTAN-O-One said:
How do you restore that ".bin" if anything fails? And if it does fail, what's the "problem" that I'll be having to fix?
Click to expand...
Click to collapse
You restore it with the same DD command you used to flash the TWRP recovery bin (dd if=/sdcard/recovery.bin of=/dev/block/mmcblk0p59)
No access to recovery is the problem you'll have.
edit: wait, do you get the warning screen on bootup now since unlocking? The one where you hit the volume keys to get to recovery/bootloader mode?

wang1chung said:
You restore it with the same DD command you used to flash the TWRP recovery bin (dd if=/sdcard/recovery.bin of=/dev/block/mmcblk0p59)
No access to recovery is the problem you'll have.
edit: wait, do you get the warning screen on bootup now since unlocking? The one where you hit the volume keys to get to recovery/bootloader mode?
Click to expand...
Click to collapse
I unlocked my ZF3 via the "0.unlock_ze522kl.bat" way. Some people complained that the official way of unlocking frm the Asus website broke their devices or smth.

Got me a "No such file or directory" when I dd. "Failed to open /sdcard/TWRP.bin"
No warning screen as far as ik. I unlock unofficially. Am I right to say that under the Asus bootloader, a barcode will be seen when it is unlocked?
Im on Nougat officially.

TiTAN-O-One said:
Got me a "No such file or directory" when I dd. "Failed to open /sdcard/TWRP.bin"
No warning screen as far as ik. I unlock unofficially. Am I right to say that under the Asus bootloader, a barcode will be seen when it is unlocked?
Im on Nougat officially.
Click to expand...
Click to collapse
Not sure about the unofficial way but with the official way you get that bootup menu I mentioned along with a warning screen that your phone isn't secure or something. I believe the unofficial way only works on marshmallow, did you use it on nougat?
You have to take the TWRP bin and place it in the root of your sdcard and then try the command.

wang1chung said:
Not sure about the unofficial way but with the official way you get that bootup menu I mentioned along with a warning screen that your phone isn't secure or something. I believe the unofficial way only works on marshmallow, did you use it on nougat?
You have to take the TWRP bin and place it in the root of your sdcard and then try the command.
Click to expand...
Click to collapse
Okay i can confirm the "Bootup and device is insecure" screen is the official way to Unlock your bootloader. I didn't do via that way cos I'm on Nougat. I did the unofficial way cos that's meant for nougat.
As for the TWRP flash, i did everything and still the same. TWRP.bin is at the chosen directory. Just to confirm, its all done under ADB right? And then simply use the dd command right?

TiTAN-O-One said:
Okay i can confirm the "Bootup and device is insecure" screen is the official way to Unlock your bootloader. I didn't do via that way cos I'm on Nougat. I did the unofficial way cos that's meant for nougat.
As for the TWRP flash, i did everything and still the same. TWRP.bin is at the chosen directory. Just to confirm, its all done under ADB right? And then simply use the dd command right?
Click to expand...
Click to collapse
We're talking internal sdcard, right? While in the adb shell, cd to /sdcard and do an ls and verify you can see your TWRP.bin there.....I think it's case sensitive too.
Also, remember I said to back your original one up just in case, so try to do that and verify everything is working.
I was under the impression the unofficial unlock didn't work on nougat and the official did? I thought it was some people doing the unofficial unlock that bricked their phones, which is why I chose the official, lol.

wang1chung said:
We're talking internal sdcard, right? While in the adb shell, cd to /sdcard and do an ls and verify you can see your TWRP.bin there.....I think it's case sensitive too.
Also, remember I said to back your original one up just in case, so try to do that and verify everything is working.
I was under the impression the unofficial unlock didn't work on nougat and the official did? I thought it was some people doing the unofficial unlock that bricked their phones, which is why I chose the official, lol.
Click to expand...
Click to collapse
Right guess what m8. I realised that I didnt and now couldn't unlock my bootloader. Here's what I did for the Unofficial Nougat way of unlocking ZF3 bootloader
Download this Zip file containing a folder called RootZenfone3-master.
Inside this folder contains 4 .bat files that is automated and named orderly so users can easily unlock and root their ZF3.
1st bat file being UnlockzeXXX.bat
2nd bat FlashRecovery.bat
3rd bat GetRoot.bat
Now 1st bat is obvly the bat file to unlock bootloader, ran it, followed the instructions to boot to bootloader etc and waited, only to know that unlocking the bootloader was unsuccessful.
Neermind that, if the bat file wasnt working, you can manually "Fastboot flash all" a file called unlock_ze552kl.raw that i believe contains a partition to unlock the bootloader.
So yes I ran the command but now i have an error that says
"FAILED (remote: Partition flashing is not allowed)"
Same error for both my Linux and Windows machine.

Found a thread here and a user says
"The ASUS Zenfone 3 comes shipped encrypted by default. This is required by Google's Play Services agreement for phone OEMs. You cannot remove decryption on the Zenfone 3 without using a custom ROM"
I had this annoying "reboot and type my pin password" whenever I restart my phone.
Any idea how to remove or decrypt this? I believe this is the issue to all the failed and permission denied errors i guess.

TiTAN-O-One said:
Right guess what m8. I realised that I didnt and now couldn't unlock my bootloader. Here's what I did for the Unofficial Nougat way of unlocking ZF3 bootloader
Download this Zip file containing a folder called RootZenfone3-master.
Inside this folder contains 4 .bat files that is automated and named orderly so users can easily unlock and root their ZF3.
1st bat file being UnlockzeXXX.bat
2nd bat FlashRecovery.bat
3rd bat GetRoot.bat
Now 1st bat is obvly the bat file to unlock bootloader, ran it, followed the instructions to boot to bootloader etc and waited, only to know that unlocking the bootloader was unsuccessful.
Neermind that, if the bat file wasnt working, you can manually "Fastboot flash all" a file called unlock_ze552kl.raw that i believe contains a partition to unlock the bootloader.
So yes I ran the command but now i have an error that says
"FAILED (remote: Partition flashing is not allowed)"
Same error for both my Linux and Windows machine.
Click to expand...
Click to collapse
That "FAILED (remote: Partition flashing is not allowed)" error means you're bootloader isn't unlocked. I believe that is the root cause of your issue.
Use the official unlock, works every time.
The pin at the beginning bootup is a security setting. I believe there was a thread where someone said to disable security lock and then reenable it but chose "no" when it asks to use pin to start device. Give that a shot first and see.

For the official bootloader unlock, is it compatible with Nougat?

Good news, it IS compatible with Nougat. Now my bootloader is unlocked and TWRP is installed successfully. However, i don't seem to get any root access despite flashing the latest supersu.zip nunerous of times. Any ideas why?

TiTAN-O-One said:
Good news, it IS compatible with Nougat. Now my bootloader is unlocked and TWRP is installed successfully. However, i don't seem to get any root access despite flashing the latest supersu.zip nunerous of times. Any ideas why?
Click to expand...
Click to collapse
Do you see the SuperSU icon in your app drawer?
Did you follow this guide and install all four zips?
I had an issue and needed to update busybox, but that was easily done from the playstore.

wang1chung said:
Do you see the SuperSU icon in your app drawer?
Did you follow this guide and install all four zips?
I had an issue and needed to update busybox, but that was easily done from the playstore.
Click to expand...
Click to collapse
Great! Everything is settled and Im unlocked and rooted successfully too. Thanks for the help.

Glad you got it sorted, now make a TWRP backup of all your partitions and go crazy flashing lol

Can't downgrade back to Nougat.

I want to downgrade back to the last version of the sprint nougat firmware. I want to use the phone as my daily driver again, I cannot afford to have any surprise bugs that a beta oreo might bring.
1 - I am using a mac that is currently updated to macOs High Sierra 10.13.3
2 - I have the latest android platform tools downloaded released in december
3 - I have no problems executing ./adb devices or ./adb reboot bootloader commands
4 - I have no problems executing ./fastboot devices or ./fastboot flashing unlock/./fastboot flashing lock commands
5 - I cannot how ever execute the ./flashall.sh command when I do it returns the message permission denied.
The phone is currently on the latest oreo beta build, I have tried every firmware that has been listed on essentials dev page. Each time I try ./flashall.sh I get permission denied. I have reached out to essential for the guide to downgrading but when you have an actual problem their response time seems to increase 10 fold.
6 - To upgrade to the beta I used the side load method, I put the phone in to recovery mode and select the apply update from adb. In the terminal I would run ./adb flash update.zip.(I changed the firmware name to update.zip)
7 - Can the apply update from adb method work to downgrade to an earlier firmware, I want to try but I dont want to risk bricking the phone. Then I will have a titanium and ceramic paper weight for my desk .

swagglepuff said:
I want to downgrade back to the last version of the sprint nougat firmware. I want to use the phone as my daily driver again, I cannot afford to have any surprise bugs that a beta oreo might bring.
1 - I am using a mac that is currently updated to macOs High Sierra 10.13.3
2 - I have the latest android platform tools downloaded released in december
3 - I have no problems executing ./adb devices or ./adb reboot bootloader commands
4 - I have no problems executing ./fastboot devices or ./fastboot flashing unlock/./fastboot flashing lock commands
5 - I cannot how ever execute the ./flashall.sh command when I do it returns the message permission denied.
The phone is currently on the latest oreo beta build, I have tried every firmware that has been listed on essentials dev page. Each time I try ./flashall.sh I get permission denied. I have reached out to essential for the guide to downgrading but when you have an actual problem their response time seems to increase 10 fold.
6 - To upgrade to the beta I used the side load method, I put the phone in to recovery mode and select the apply update from adb. In the terminal I would run ./adb flash update.zip.(I changed the firmware name to update.zip)
7 - Can the apply update from adb method work to downgrade to an earlier firmware, I want to try but I dont want to risk bricking the phone. Then I will have a titanium and ceramic paper weight for my desk .
Click to expand...
Click to collapse
You need to unlock the boot loader.
You will need to go into developer mode and check the oem unlock.
In fast boot you need to unlock and unlock_critical.
They you should be able to revert.

tech_head said:
You need to unlock the boot loader.
You will need to go into developer mode and check the oem unlock.
In fast boot you need to unlock and unlock_critical.
They you should be able to revert.
Click to expand...
Click to collapse
Awesome, no where in essentials guide does it ever mention unlock_critical, all it says it to use fastboot flashing unlock. Even then it still says permission denied. After I unlock the bootloader i will go back to the fastboot menu and the run ./fastboot flashing unlock_critical or is it ./fastboot unlock_critical

tech_head said:
You need to unlock the boot loader.
You will need to go into developer mode and check the oem unlock.
In fast boot you need to unlock and unlock_critical.
They you should be able to revert.
Click to expand...
Click to collapse
Here is my exact steps of what I just did.
open terminal set directory to required folder
./adb devices- recognizes phone and shows model number
./adb reboot bootloader- executes no problem now in fastboot mode
./fastboot devices- recognizes device and show model number
./fastboot flashing unlock-prompt screen shows on PH-1 select yes for unlocking bootloader
Do a quick set up and get back to the fastboot screen.
./fastboot flashing unlock_critical-prompt screen shows on PH-1 select yes for unlocking bootloader
Do a quick set up again, get back to the fastboot screen
./flashall.sh-permission denied
In the fastboot menu on the phone it says status is unlocked. Up next the spectacular smashing on a essential phone with a hammer!!!!!!!!!!!!!!!!

swagglepuff said:
Here is my exact steps of what I just did.
open terminal set directory to required folder
./adb devices- recognizes phone and shows model number
./adb reboot bootloader- executes no problem now in fastboot mode
./fastboot devices- recognizes device and show model number
./fastboot flashing unlock-prompt screen shows on PH-1 select yes for unlocking bootloader
Do a quick set up and get back to the fastboot screen.
./fastboot flashing unlock_critical-prompt screen shows on PH-1 select yes for unlocking bootloader
Do a quick set up again, get back to the fastboot screen
./flashall.sh-permission denied
In the fastboot menu on the phone it says status is unlocked. Up next the spectacular smashing on a essential phone with a hammer!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Do you have the script file set to execute?
Sent from my PH-1 using XDA Labs

avd said:
Do you have the script file set to execute?
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
That was my next question.
chmod +x flash-all.sh

[Solved] Huawei P9 Lite Bricked

Hello, I was curious if anyone could help me with unbricking my phone, my phone has no custom recovery installed, the bootloader is apparently unlocked (OEM unlocking is disabled), FRP lock is enabled, I cannot flash anything (Command not allowed), relock bootloader (Root type is at risk), Unlock bootloader (Command not allowed), any help would be appreciated.
Edit: I also cannot boot a from a recovery img locally using fastboot (Command not allowed)
EDIT: Fixed it using DC Pheonix and flashing VNS-L22C636B140 OEMINFO and flashing B160

Hi, try my way. https://forum.xda-developers.com/showpost.php?p=77307223&postcount=30 Just pick CxxxBxxx that suits your model. Try to unlock bootloader again via SRKTool, I think FRP must be unlocked too...
Check this also: https://forum.xda-developers.com/huawei-p9lite/help/p9-lite-bricked-please-help-t3415275

4uvak91 said:
Hi, try my way. https://forum.xda-developers.com/showpost.php?p=77307223&postcount=30 Just pick CxxxBxxx that suits your model. Try to unlock bootloader again via SRKTool, I think FRP must be unlocked too...
Check this also: https://forum.xda-developers.com/huawei-p9lite/help/p9-lite-bricked-please-help-t3415275
Click to expand...
Click to collapse
I cannot flash anything, so any of these do not help, thanks for trying I guess

wheellzzz said:
I cannot flash anything, so any of these do not help, thanks for trying I guess
Click to expand...
Click to collapse
Are you sure you run from inside the folder where adb.exe and fastboot.exe is? Boot to bootloader and use terminal pointed to fastboot.exe. Shift+right click -> open command line here. Make sure your devices is listed: adb devices. If device is shown: adb reboot bootloader, to reboot to bootloader. If not, install adb drivers / huawei drivers.

4uvak91 said:
Are you sure you run from inside the folder where adb.exe and fastboot.exe is? Boot to bootloader and use terminal pointed to fastboot.exe. Shift+right click -> open command line here. Make sure your devices is listed: adb devices. If device is shown: adb reboot bootloader, to reboot to bootloader. If not, install adb drivers / huawei drivers.
Click to expand...
Click to collapse
Yes I am sure, also, I have no way to access ADB since there is no recovery on the phone.
Only thing I can do is boot to that eRecovery screen with the option to download, reboot or shutdown. (Automatticly goes to here), or boot to bootloader

wheellzzz said:
Yes I am sure, also, I have no way to access ADB since there is no recovery on the phone.
Only thing I can do is boot to that eRecovery screen with the option to download, reboot or shutdown. (Automatticly goes to here), or boot to bootloader
Click to expand...
Click to collapse
Well if you can access to bootloader then you able to use fastboot commands. ADB is not related to recovery anyhow, you use windows command prompt to use adb and fastboot. IF FRP is locked, unlock bootloader again. I quiet don't understand how the command are not allowed or so. You are definitely doing something wrong.

4uvak91 said:
Well if you can access to bootloader then you able to use fastboot commands. ADB is not related to recovery anyhow, you use windows command prompt to use adb and fastboot. IF FRP is locked, unlock bootloader again. I quiet don't understand how the command are not allowed or so. You are definitely doing something wrong.
Click to expand...
Click to collapse
The problem is I cannot unlock bootloader again, flash anything or boot into any image in fastboot mode, I always get "ERROR: (Command not allowed)", attempting to relock the bootloader shows "ERROR: (Root type is at risk)"
EDIT: I have done some research for the dload method, If I want to dload to hopefully fix it, I'll need VNS-L22C636B381, but the official link from the hicloud is dead, if anyone could help me with that, that'd be great.
Last EDIT: Ended up scratching the above idea as it didn't work, gritted my teeth as I bought DC Phoenix and will update if it works out with the .APP from the latest package I found on firmware finder.