Related
Hello there,
I updated my LG P700 to the v20c 4.1.2 JB version. After that, I couldn't find a wayu to root it, but found Framaroot app and succeeded with it. I got a little cocky how easy it was and downloaded ROM Manager. From it, I chose the CWM installation option and the window said it was a success. However, when I clicked to reboot into the recovery, only this little error appeared - "Secure Booting Error! Cause: Boot certification verify." in the left uper corner of the screen. Nothing worked, so I took out the battery and after turning the phone on, I noticed that all the internal memory got factory reseted or something like that and it is just a blank fresh android - all data was lost.
Long story short: flashing recovery from ROM Manager caused the wipe of the memory.
What happened?
[UPDATE] It could be caused by not unlocking the bootloader. I assumed that ROM Manager checks these things or flashes them with the recovery.
If that's the case (pls tell me) then I should unlock the bootloader. Maybe with this - http://forum.xda-developers.com/showthread.php?t=2197429 Does it work with v20c 4.1.2 android on my LG L7?
yes, the bootloader is locked, you need to unlock
Thanks, now I'm at least on to something. Does the method from the link works on v20c 4.1.2. version?
Sent from my LG-P700 using xda app-developers app
Macors said:
Thanks, now I'm at least on to something. Does the method from the link works on v20c 4.1.2. version?
Sent from my LG-P700 using xda app-developers app
Click to expand...
Click to collapse
it doesn`t matter if you have ICS or JB, it must work
I tried unlocking the bootloader with the Flash_Bootloader.bat file, but the error windows flashes only for a split second. I barely caught it and attached the screenshot of it saying "the system cannot find the path specified". What should I do now?
Phone connected in pc software mode, debuggin is on.
[Update] I moved the CWM folder directly to the local disk C and it worked, but didn't reboot the phone. I had to unplug it and then turn on. How to check if my bootloader is unlocked? I don't want any more fails with flashing the recovery ;/
Macors said:
I tried unlocking the bootloader with the Flash_Bootloader.bat file, but the error windows flashes only for a split second. I barely caught it and attached the screenshot of it saying "the system cannot find the path specified". What should I do now?
Phone connected in pc software mode, debuggin is on.
[Update] I moved the CWM folder directly to the local disk C and it worked, but didn't reboot the phone. I had to unplug it and then turn on. How to check if my bootloader is unlocked? I don't want any more fails with flashing the recovery ;/
Click to expand...
Click to collapse
you were needed to write adb reboot to rebbot your phone after, and the only way to chech the bootlaoder is to go on download mode or recovery
Everything is working, just rebooted into Recovery from the rom manager. By the way, how does this adb work? Do I have to run the .exe file after the .bin ?
Macors said:
Everything is working, just rebooted into Recovery from the rom manager. By the way, how does this adb work? Do I have to run the .exe file after the .bin ?
Click to expand...
Click to collapse
start - run cmd - cd %ADB% - and here you are
same here
Im using an lg lucid vs840 and is recently rooted, i downloaded rom manager and cyanogen mod 11, but when i try to install rom from sd card it reboots saying,
boot errer cause boot certification verify
Enter fast reboot...
Enter fast reboot...
Long time no see!
I can still use my phone but i cant install a new rom, any one help?
Thank you for reading.
lol nobody ever answers this same question many times on this site.... sorry first post but I get all my info from hereeeeee for a long time now
Hi...
This is the tutorial to root any Moto G
To root any Moto G, three basic steps need to be followed... you can either do them manually or use a tool do them for you. It is advised to follow them manually so that if there's some bug in the tool you don't get into any trouble.
CAUTION - You will lose all data and files so better back them up.
For Google Play edition devices, the process is same and only the recovery.img file is different. For GPe CWM Advanced Edition recovery go here https://goo.im/devs/philz_touch/CWM_Advanced_Edition/ and select falcon_gpe and download the latest one.
For AT&T and Verizon models don't do anything written above. Just download the Towelroot app. Its a one click root app and doesn't require a PC. Itis trustworthy but is not guaranteed to work but you must give it a try since it won't do any harm and claims of never bricking a phone. Please reply with the result and your android and kernel version.It will probably not work on phones build after June 3 but you can give it a try. You can download it from the website https://towelroot.com
The three steps are :-
1) UNLOCKING THE BOOTLOADER
2) FLASHING CUSTOM RECOVERY
3) INSTALLING SuperSu.zip FILE THROUGH RECOVERY. (SuperSu is acknowledge as the best app to give superuser and root rights)
UNLOCKING THE BOOT LOADER - The instructions to unlock the boot loader are given in the official Motorola website here https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a . Don't be scared by their warnings.
UPDATE - There currently seems to be an issue with unlocking the bootloader on devices running 4.4.4 though it works for 4.4.2. The issue is with Motorola and is that, the unlock code given by the company is showing an error. They are fixing it and it may take some time though you can give it a try as it won't do any harm. Or you can downgrade the boot loader to 4.4.2 and then unlock it.
As confirmed by the Motorola agent, the problem of unlocking bootloader on 4.4.4 has been fixed
FLASHING CUSTOM RECOVERY :-
To flash a custom recovery, you need these things
1) PC and a USB data cable
2) Android SDK ( developer.android.com/sdk/index.html ) For flashing recovery only SDK is needed but it's your wish if you want to download the ADT bundle. After downloading and unzipping the sdk , open the SDK manager and download only the platform tools for this.. rest is your wish..... and separately download ADB tools and fastboot and extract them minimal-adb-and-fastboot.software.informer.com/1.1/
3) Recovery.img file - You can either use CWM foum.xda-developers.com/showthread.php?t=2563599 or CWM advanced editionforum.xda-developers.com/showthread.php?t=2639583 or TWRP forum.xda-developers.com/showthread.php?t=2561757. EDIT - If your phone had come pre installed with 4.4.4 then use only CWM Advanced Edition. CWM Advanced Edition doesn't make backup on XT1033
4) Motorola drivers https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97326/p/30,6720,9050
5) Enable USB Debugging mode in your phone by going to Settings-About Phone and then tap the build number until you get the toast 'You are a developer'. Now go to Settings again and you will see a new Developer Options there. Go there and enable USB debugging.
6) Have at least 25% of charge on your phone.
After getting all these things:-
1) Download the recovery.img file to your PC and copy paste it to android SDK/platform tools folder.
2) Boot your phone to fastboot mode by first switching it off and holding the volume down and power button for 3 seconds.
3) When in fastboot mode, connect your phone to pc, go to the platform tools folder, there pres shifft and right mouse click simultaneously and select 'open command prompt window here'.
4) In the command window enter
Code:
fastboot devices
If it shows a number and fastboot then we are good..
5) Then enter
Code:
fastboot flash recovery recovery.img
( where in recovery.img the recovery is the name of your recovery file. Example if the name of recovery file is ABC then enter fastboot flash recovery ABC.img)
5) Press enter and if the command prompt window displays the message okay then the recovery is successfully flashed.
6) Now just boot your phone to recovery mode through fastboot mode by following the on screen instructions and in recovery mode select Reboot System Now to reboot your phone normally.
(see attached images below for screenshots)
INSTALLING SuperSu
To install SuperSu :-
1) Download SuperSu zip file download.chainfire.eu/452/SuperSU/ and transfer it to your phone
2) Reboot to recovery via fastboot.
3) Select install zip and select choose from SD card.
4) Locate the file and install it.
5) Now reboot your phone.
YUP.. YOU ROOTED YOUR PHONE!
Download any root checker app from the Play Store to check whether your phone is rooted or not.
If you get into any trouble, please contact and don't forget to hit thanks if it helped
Consider rating the thread by going to the option 'rate thread' which is located above the thread on the right side. You can also participate in the poll
I have a huawei p6 but I'm absolutely not satisfied with that and I bought a moto g for my girlfriend and that is awesome.
The only thing why I haven't bought the g for myself as well is the rooting. That time I didn't find an easy way to root it.
If it is a working method than I will buy the 4g verson with sd card support
Sent from my HUAWEI P6-U06 using XDA Free mobile app
sisqoboy said:
I have a huawei p6 but I'm absolutely not satisfied with that and I bought a moto g for my girlfriend and that is awesome.
The only thing why I haven't bought the g for myself as well is the rooting. That time I didn't find an easy way to root it.
If it is a working method than I will buy the 4g verson with sd card support
Sent from my HUAWEI P6-U06 using XDA Free mobile app
Click to expand...
Click to collapse
Yup dude...this works for sure..!
I also added screenshots.. check them out.
Meuuks13 said:
Yup dude...this works for sure..!
Click to expand...
Click to collapse
Does this work with the latest bootloader on 4.4.4? Im still stock but i wanna root it so much
Thanks
motocruiser said:
Does this work with the latest bootloader on 4.4.4? Im still stock but i wanna root it so much
Thanks
Click to expand...
Click to collapse
I looked into it just now... Currently there's an issue with Motorola with unlocking the bootloader when on 4.4.4...As people say, the unlock code given my Motorola is showing an error... You can still try it.. maybe it's even fixed by now.. Even if it fails there wouldn't be any harm.. Though the unlocking works fine with 4.4.2... You can revert back to 4.4.2, unlock the bootloader and then update to 4.4.4... The thing will be same as you will lose all data and files when unlocking the bootloader and so in reverting to 4.4.2.....(Remember, only unlocking doesn't mean you won't recieve updates, you won't receive updates only if you flash a custom recovery.)
EDIT - I added it to the OP. Thanks for bringing it to attention.
And does this work for Verizon model
Sent from my XT1028 using XDA Premium 4 mobile app
xrilex said:
And does this work for Verizon model
Sent from my XT1028 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You have Verizon I see. The only you will probably face is unlocking the bootloader.. Oh, wait first let me laugh... lol...OK....At one point of time you couldn't unlock the bootloaders for AT&T and Verizon and then we were blessed by the 'one click root' app by the famous hacker geohot called TowelRoot. This app claims to root all the AT&T and Verizon devices with just a click. You don't even need a PC. Just download the app and in the app chick 'make it rain'. Though this is not guaranteed to work but must give a try as it won't do any harm but there's a chance of bricking the phone but you can easily recover from a soft brick by flashing the stock firmware.
Towelroot - https://towelroot.com/
P.S. - Please reply if you tried this and if it didn't work reply with your android version and kernel version. Well reply with your android version and kernel version anyway.
Edit- I added it to the OP
Meuuks13 said:
I looked into it just now... Currently there's an issue with Motorola with unlocking the bootloader when on 4.4.4...As people say, the unlock code given my Motorola is showing an error... You can still try it.. maybe it's even fixed by now.. Even if it fails there wouldn't be any harm.. Though the unlocking works fine with 4.4.2... You can revert back to 4.4.2, unlock the bootloader and then update to 4.4.4... The thing will be same as you will lose all data and files when unlocking the bootloader and so in reverting to 4.4.2.....(Remember, only unlocking doesn't mean you won't recieve updates, you won't receive updates only if you flash a custom recovery.)
EDIT - I added it to the OP. Thanks for bringing it to attention.
Click to expand...
Click to collapse
thanks for your help dude but i heared that if you flash back to 4.4.2 your bootloader is still the latest so its still unlockable...
i have found a fix on a motorola customer forum for this problem, but when i flash this testdrive motoboot image file it goes wrong and i cant fix it by my self
motocruiser said:
thanks for your help dude but i heared that if you flash back to 4.4.2 your bootloader is still the latest so its still unlockable...
i have found a fix on a motorola customer forum for this problem, but when i flash this testdrive motoboot image file it goes wrong and i cant fix it by my self
Click to expand...
Click to collapse
Sorry I didn't know that. Downgrading the bootloader is a very risky process.
What did you exactly do?
Hey! I have followed all the steps. When i flash de recovery.img, the command prompt says everything is ok, but when i try to reboot into recovery trough the fastboot, it just turns off! It dosn't rebot into recovery! Thanks man!
t.lou91 said:
Hey! I have followed all the steps. When i flash de recovery.img, the command prompt says everything is ok, but when i try to reboot into recovery trough the fastboot, it just turns off! It dosn't rebot into recovery! Thanks man!
Click to expand...
Click to collapse
Please tell which android version your phone came preinstalled with and what recovery you used.
Also when you reboot to recovery, after the blank screen do you see the android logo lying down with a red triangle?
t.lou91 said:
Hey! I have followed all the steps. When i flash de recovery.img, the command prompt says everything is ok, but when i try to reboot into recovery trough the fastboot, it just turns off! It dosn't rebot into recovery! Thanks man!
Click to expand...
Click to collapse
Please tell your phone's android version and the recovery you used and what did you enter at the command prompt?
Meuuks13 said:
Sorry I didn't know that. Downgrading the bootloader is a very risky process.
What did you exactly do?
Click to expand...
Click to collapse
Well it doesnt go wrong like you think so my phone is actually not bricked.
But the command window says that the operation failed so i think something is wrong with this testdrive image from the moto forum.
thanks
motocruiser said:
Well it doesnt go wrong like you think so my phone is actually not bricked.
But the command window says that the operation failed so i think something is wrong with this testdrive image from the moto forum.
thanks
Click to expand...
Click to collapse
Testdrive image?
Meuuks13 said:
Testdrive image?
Click to expand...
Click to collapse
Yeah they say, if you on 4.4.4 and want to unlock your bootloader you have to flash the motoboot_testdrive.img file wich downgrades the bootloader to i think it was called 40.15 or so after that you have to unlock your bootloader and then flash the motoboot 4.4.4 stock image so that you have the actual one but for me it failed while i try to flash this testdrive image
motocruiser said:
Yeah they say, if you on 4.4.4 and want to unlock your bootloader you have to flash the motoboot_testdrive.img file wich downgrades the bootloader to i think it was called 40.15 or so after that you have to unlock your bootloader and then flash the motoboot 4.4.4 stock image so that you have the actual one but for me it failed while i try to flash this testdrive image
Click to expand...
Click to collapse
So basically you want to downgrade the bootloader and then unlock it?
Well if you are on KitKat you can downgrade the bootloader by flashing 4.3 , then unlocking the bootloader and then updating to KitKat
Thanks for the guide. I've already recommended it to someone who was having problems.
jselene said:
Thanks for the guide. I've already recommended it to someone who was having problems.
Click to expand...
Click to collapse
Cool.
Thanks Meuuks13. This worked well.
Also, I've found that you can remove the "unlocked bootloader warning message" shown on boot-up by following the method in the Moto X forum:
http://forum.xda-developers.com/moto-x/general/4-4-3-remove-unlocked-bootloader-message-t2548566
JDCGW said:
Thanks Meuuks13. This worked well.
Also, I've found that you can remove the "unlocked bootloader warning message" shown on boot-up by following the method in the Moto X forum:
http://forum.xda-developers.com/moto-x/general/4-4-3-remove-unlocked-bootloader-message-t2548566
Click to expand...
Click to collapse
I got something wayyyy better than that!
I let you remove that sign and use the pics given here forum.xda-developers.com/moto-g/themes-apps/shareboot-logos-t2875147 or you can give me the pic you want and I will make it in such a way that you can use it.
Hello Devs
I want to roll back from Android Nougat to Marshmallow by installing TWRP.... I have my bootloader unlocked on my Nexus 6P but since I have the error of Download Mode DISABLED in fast boot mode Im unable to flash the firmware through ADB.
Kindly help.:crying:
amandeepparmar said:
Hello Devs
I want to roll back from Android Nougat to Marshmallow by installing TWRP.... I have my bootloader unlocked on my Nexus 6P but since I have the error of Download Mode DISABLED in fast boot mode Im unable to flash the firmware through ADB.
Kindly help.:crying:
Click to expand...
Click to collapse
If you have an unlocked bootloader and can boot into it, does it not recognize your phone or simply not allow you to run commands? My download mode reads as DISABLED in my bootloader and I can run fastboot commands. I think you're a little confused on terminology, too. You'd sideload software via ADB with TWRP or for an OTA, your stock recovery. You'd fastboot flash partitions via the bootloader.
ultyrunner said:
If you have an unlocked bootloader and can boot into it, does it not recognize your phone or simply not allow you to run commands? My download mode reads as DISABLED in my bootloader and I can run fastboot commands.
Click to expand...
Click to collapse
I can boot into fast boot mode by hardware button combo pressed but its not recognising any fast boot or ADB commands when I connect it on my laptop
When connected by USB and in your bootloader, run 'fastboot devices' and if it doesn't show your serial # then it isn't recognizing your phone, likely a driver issue.
Sent from my Nexus 6P using Tapatalk
amandeepparmar said:
Hello Devs
I want to roll back from Android Nougat to Marshmallow by installing TWRP.... I have my bootloader unlocked on my Nexus 6P but since I have the error of Download Mode DISABLED in fast boot mode Im unable to flash the firmware through ADB.
Kindly help.:crying:
Click to expand...
Click to collapse
Do not try to do that. We have a lot of bricked devices (Including Mine) after we tried rolling back to Marshmallow. Just a warning. If you still want to take a risk, go ahead by all means.
Driver issue....resolved.....Working now!!...Thank you
amandeepparmar said:
Driver issue....resolved.....Working now!!...Thank you
Click to expand...
Click to collapse
No problem. I would listen to Indian84 and stay on Nougat until you can flash full factory images.
Sent from my Nexus 6P using Tapatalk
Hello XDA Community,
I am George and I bricked my Nexus 6P.
To be more accurate, this is what I've done (will try to list them by order):
1. Unlocked Bootloader, Rooted and installed TWRP custom recovery
2. Installed a working custom kernel
3. Installed a sound mod I found on a forum (can specify the sound mod, I am just not sure if it is allowed)
Boom, phone softbricked
4. Flashed factory image (through Nexus Root Toolkit by WugFresh)
Still softbricked
Done it again and again with different angler versions, while I was formatting everything before flashing.
Still softbricked, but recovery accessible
5. Locked bootloader ( ... I thought factory image needs bootloader locked for the very first boot ...)
So now I have a Nexus 6P that have Bootloader locked, when I simply start it (power button) it bootloops (about 10 seconds stuck at Google logo), with access to stock recovery and 6.0.1/MTC20F/3031278 OS version.
(PS: I was also letting the smartphone do the bootloop-like restarts after the factory image flashes for about 30 minutes.)
I need help, I bought the smartphone before 7 days and I acted childish ...
I've tried Rescue OTA Guide by Techno Bill but still exactly the same state. (adb sideload ota.zip)
(drive.google.com/file/d/0Bz6x7k-VkpUJRjl6WjRhVmdXU0E/view)
Best regards, George.
I would, get into fastboot, unlock bootloader, then install twrp , go into recovery, and do a full wipe off everything! Even type in yes to format data, then reboot to bootloader from twrp reboot menu, then from there use wugs tool to flash stock MM it should boot for you.
Sent from my Nexus 6P using XDA-Developers mobile app
Pipiou211 said:
Hello XDA Community,
I am George and I bricked my Nexus 6P.
To be more accurate, this is what I've done (will try to list them by order):
1. Unlocked Bootloader, Rooted and installed TWRP custom recovery
2. Installed a working custom kernel
3. Installed a sound mod I found on a forum (can specify the sound mod, I am just not sure if it is allowed)
Boom, phone softbricked
4. Flashed factory image (through Nexus Root Toolkit by WugFresh)
Still softbricked
Done it again and again with different angler versions, while I was formatting everything before flashing.
Still softbricked, but recovery accessible
5. Locked bootloader ( ... I thought factory image needs bootloader locked for the very first boot ...)
So now I have a Nexus 6P that have Bootloader locked, when I simply start it (power button) it bootloops (about 10 seconds stuck at Google logo), with access to stock recovery and 6.0.1/MTC20F/3031278 OS version.
(PS: I was also letting the smartphone do the bootloop-like restarts after the factory image flashes for about 30 minutes.)
I need help, I bought the smartphone before 7 days and I acted childish ...
I've tried Rescue OTA Guide by Techno Bill but still exactly the same state. (adb sideload ota.zip)
(drive.google.com/file/d/0Bz6x7k-VkpUJRjl6WjRhVmdXU0E/view)
Best regards, George.
Click to expand...
Click to collapse
You shouldn't have relocked the bootloader. You are out of luck now, but I might be wrong. Some expert could shed light on this issue especially Heisenberg.
Just to check, you did enable OEM unlocking in Developer Options?
Pipiou211 said:
So now I have a Nexus 6P that have Bootloader locked, when I simply start it (power button) it bootloops (about 10 seconds stuck at Google logo), with access to stock recovery and 6.0.1/MTC20F/3031278 OS version.
Click to expand...
Click to collapse
Hi George,
Welcome to the XDA Forums;
Can you try the following and tell me what the result is?
1. Boot your device into the bootloader for fastboot
-If the phone is boot-looping, hold down the power button until the screen turns off, then hold VOLUME DOWN + Power
2. Plug your device into your PC
3. Open your command prompt and type fastboot devices
-If properly connected, you will see your devices serial #
4. Type fastboot flashing unlock
And then return here and post the results.
Thanks
If you relocked the bootloader it's game over man, no unlocked bootloader no fastboot commands.
defcondev said:
Hi George,
Welcome to the XDA Forums;
Can you try the following and tell me what the result is?
1. Boot your device into the bootloader for fastboot
-If the phone is boot-looping, hold down the power button until the screen turns off, then hold VOLUME DOWN + Power
2. Plug your device into your PC
3. Open your command prompt and type fastboot devices
-If properly connected, you will see your devices serial #
4. Type fastboot flashing unlock
And then return here and post the results.
Thanks
Click to expand...
Click to collapse
I can run fastboot commands but I cannot "fastboot flashing unlock" because 'OEM Unlock' is not enabled INSIDE the broken OS of my phone :/ ...
(When I do fastboot flashing unlock it errors me the thing I just wrote you)
Greetings, George.
Edit:
Thank you for welcoming me here,
Im here to stay !
Download the factory image.
You should not need the bootloader unlocked to flash a factory image.
The image is signed and unlocking the bootloader is necessary for unsigned images.
tech_head said:
Download the factory image.
You should not need the bootloader unlocked to flash a factory image.
The image is signed and unlocking the bootloader is necessary for unsigned images.
Click to expand...
Click to collapse
I already tried that, Im using flash-all.bat inside the factory.zip I download and by using fastboot, it informs me that the bootloader is locked, unable to flash ... :/
Is this possible? Factory image had to be possible to get flashed ..
PS: Google announced today the new update for my device, I should download the FULL OTA UPDATE (900+ mb) and adb sideload ota.zip?
Pipiou211 said:
I already tried that, Im using flash-all.bat inside the factory.zip I download and by using fastboot, it informs me that the bootloader is locked, unable to flash ... :/
Is this possible? Factory image had to be possible to get flashed ..
PS: Google announced today the new update for my device, I should download the FULL OTA UPDATE (900+ mb) and adb sideload ota.zip?
Click to expand...
Click to collapse
If you can sideload the new update go ahead its worth a try but don't count your chickens because if the previous builds failed that are singed by google i'd say the chances of it working this time around are about 0.0000001%
"If you're upgrading a device running Lollipop or higher, make sure Enable OEM unlock is checked" is a phrase you can read for the last few years on many devices.
Its unfortunate for you but you have indeed learnt the hardway, however there is a bit of discussion about editing some values via the second bootloader (aboot) however this is for the N9 but if you can be bothered with twitting around . . . . per chance can you run "fastboot oem get_unlock_ability" ?
this would return this
Code:
# Before
[email protected]:/ # od -A x -t x4 /dev/block/platform/sdhci-tegra.3/by-name/PST
000000 00000000 00000000 00000000 00000000 # No oem unlock - nada
*
080000
# After
[email protected]:/ # od -A x -t x4 /dev/block/platform/sdhci-tegra.3/by-name/PST
000000 00000000 00000000 00000000 00000000 # Still entirely empty...
* # ...
07fff0 00000000 00000000 00000000 01000000 # ... save 1 bit ( Unlock Enabled/allowed)
080000
More info here - http://forum.xda-developers.com/nexus-9/help/to-toggle-allow-oem-unlock-via-fastboot-t3091119/page2
Annnnnnd here - http://newandroidbook.com/Articles/Nexus9.html
hutzdani said:
If you can sideload the new update go ahead its worth a try but don't count your chickens because if the previous builds failed that are singed by google i'd say the chances of it working this time around are about 0.0000001%
"If you're upgrading a device running Lollipop or higher, make sure Enable OEM unlock is checked" is a phrase you can read for the last few years on many devices.
Its unfortunate for you but you have indeed learnt the hardway, however there is a bit of discussion about editing some values via the second bootloader (aboot) however this is for the N9 but if you can be bothered with twitting around . . . . per chance can you run "fastboot oem get_unlock_ability" ?
this would return this
Code:
# Before
[email protected]:/ # od -A x -t x4 /dev/block/platform/sdhci-tegra.3/by-name/PST
000000 00000000 00000000 00000000 00000000 # No oem unlock - nada
*
080000
# After
[email protected]:/ # od -A x -t x4 /dev/block/platform/sdhci-tegra.3/by-name/PST
000000 00000000 00000000 00000000 00000000 # Still entirely empty...
* # ...
07fff0 00000000 00000000 00000000 01000000 # ... save 1 bit ( Unlock Enabled/allowed)
080000
More info here - http://forum.xda-developers.com/nexus-9/help/to-toggle-allow-oem-unlock-via-fastboot-t3091119/page2
Annnnnnd here - http://newandroidbook.com/Articles/Nexus9.html
Click to expand...
Click to collapse
No I cannot run the "fastboot flashing unlock" (Android 6.0.x new "fastboot oem unlock" command).
I am getting the error that actually the oem is locked.
Actually the real fastboot oem unlock as I can see does not exist, I have to do it from the inside (Android>Settings>Developer Options)
Soo .. let me take a look at the topic you gave me, Do I have to be rooted?
*Checked the links*
I cannot run adb shell command the only thing I can run is the sideload command ... :/
Tommorow I am starting a RMA request ...
Have a nice day and thank you for trying to help me,
George.
Pipiou211 said:
I can run fastboot commands but I cannot "fastboot flashing unlock" because 'OEM Unlock' is not enabled INSIDE the broken OS of my phone :/ ...
(When I do fastboot flashing unlock it errors me the thing I just wrote you)
Greetings, George.
Edit:
Thank you for welcoming me here,
Im here to stay !
Click to expand...
Click to collapse
At this point, I would contact Google for a replacement. As far as I know, without enabling OEM unlocking, you cannot do anything.
You locked yourself out of any possible fix.
Sent from my Nexus 6P using XDA Labs
You can try osm0sis' Nexus boot unlocked zip. Angler isn't listed in script bit there's a line that does enable fastboot oem unlocking..
http://forum.xda-developers.com/showthread.php?t=2239421
Sent from my Nexus 6P using Tapatalk
Brianp27 said:
You can try osm0sis' Nexus boot unlocked zip. Angler isn't listed in script bit there's a line that does enable fastboot oem unlocking..
http://forum.xda-developers.com/showthread.php?t=2239421
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I've sent it for replacement/ repair. But hey that is an awesome thread.
By the way, Nougat 7.0 OTA update has been released, that was a solution too I guess (adb sideload nougat.zip).
Anyway, I will inform you what happened!
Cheers,
George.
tech_head said:
Download the factory image.
You should not need the bootloader unlocked to flash a factory image.
The image is signed and unlocking the bootloader is necessary for unsigned images.
Click to expand...
Click to collapse
That is a completely false statement. Flashing any images via fastboot requires an unlocked bootloader. This is and has always been true with nexus devices.
Brianp27 said:
You can try osm0sis' Nexus boot unlocked zip. Angler isn't listed in script bit there's a line that does enable fastboot oem unlocking..
http://forum.xda-developers.com/showthread.php?t=2239421
Click to expand...
Click to collapse
That's an interesting thread and utility, but it looks like that's a flashable zip which would require TWRP to be installed with the locked bootloader.
toknitup420 said:
That is a completely false statement. Flashing any images via fastboot requires an unlocked bootloader. This is and has always been true with nexus devices.
Click to expand...
Click to collapse
I stand corrected.
Some devices allow flashing of factory signed images without an unlocked bootloader.
I guess the major blunder in the whole scenario is:
"5. Locked bootloader ( ... I thought factory image needs bootloader locked for the very first boot ...)"
PSA -> Once you start flashing.. NEVER, EVER RE-LOCK THE BOOTLOADER.
defcondev said:
That's an interesting thread and utility, but it looks like that's a flashable zip which would require TWRP to be installed with the locked bootloader.
Click to expand...
Click to collapse
Not necessarily, I've installed multiple zips simply by side loading. It's meant to be an emergency boot unlocker, situation like this definitely warrants. And I agree , any self updates would certainly require unlocking first. Google will even say so on their firmware download site.
Apologies to the thread... Apparently Tapatalk renamed me to "Brianp27".
If it's bootloader locked and not rooted just RMA it,
Sent from my Nexus 6P
Papote3 said:
If it's bootloader locked and not rooted just RMA it,
Click to expand...
Click to collapse
I was honest with Huawei in an email to their support, about me trying to fix the boot loop with a factory image, and they wrote back that any firmware tampering voids their warranty. I'll never know if this boot loop is hardware or software related, but if it it is software related, then I have proven that it is possible to brick a Nexus 6p.
I've read and tried every fix on XDA with no positive outcome, but I guess it will now be a tinkering hobby for me over the next year. I can view the recovery logs, so maybe they will give me a clue once I can decipher what it all means.
UPDATE:
I successfully unlocked the bootloader, flashed twrp, rooted, updated kernel and roms, tweaking gpu cpu for performance in pubg etc, greenify, flashify, power nap everything.
xposed framework take you in bootloop for this device.
now i am on kernel mk2000, superv20 rom, h91810u, 7 nougat.
if in future anyone feels any problem i am always here.
remember: linus is your friend for this device, and windows 10 suck.
and
sudo $(which fastboot) did miracles for me....
old post:
Hello everyone.
i am new here and i am sorry in advance if i did something wrong. i will come directly to the point.
model number: LG V20 T-MOBILE VERSION, H91820H, NON USA, Currently on oreo android 8.
we are not talking about any kind of roms kernels roots or anything here. just a simple question. " can this model's boot loader be unlocked ? like ever ? or not "
cause i have tried everything, when i say everything i mean everything. followed several posts on internet videos on you tube posts on XDA, tried using multiple PCs, multiple data cables, multiple drivers but for some reason i don't know what, this model's boot loader cannot be unlocked.
THE ERROR:
<WAITING FOR DEVICE> till eternity.
what i have done till now ?
1. lg drivers installed.
2. adb drivers installed with adb fastboot files.
3. updating legacy android adb interface driver, done.
4. went in to boot loader then connected the data cable and updated driver, done.
5. usb debugging oem unlock options activated, done.
6. restarted pc multiple times to update drivers, done.
we all know all it takes is 3 easy commands to unlock bootlaoder
adb reboot bootloader
fastboot oem unlock
fastboot reboot
but in my case i always stuck at 2nd command. waiting for device is shown and nothing happens.
then i ran command, adb devices>> it shows
List of devices attached
adb server is out of date. killing...
* daemon started successfully *
LGH9182bfc6bdc device
next i put the command, fastboot devices and nothing is shown i just go to the next line... c:\adb>
so this is for sure that my device is not connected to the fastboot.
now my only question is, can this device bootloader unlock or not ? so that i stop pushing my limits.
any help will be appreciated.
regards.
X_BlackBurn_X said:
Hello everyone.
i am new here and i am sorry in advance if i did something wrong. i will come directly to the point.
model number: LG V20 T-MOBILE VERSION, H91820H, NON USA, Currently on oreo android 8.
we are not talking about any kind of roms kernels roots or anything here. just a simple question. " can this model's boot loader be unlocked ? like ever ? or not "
cause i have tried everything, when i say everything i mean everything. followed several posts on internet videos on you tube posts on XDA, tried using multiple PCs, multiple data cables, multiple drivers but for some reason i don't know what, this model's boot loader cannot be unlocked.
THE ERROR:
<WAITING FOR DEVICE> till eternity.
what i have done till now ?
1. lg drivers installed.
2. adb drivers installed with adb fastboot files.
3. updating legacy android adb interface driver, done.
4. went in to boot loader then connected the data cable and updated driver, done.
5. usb debugging oem unlock options activated, done.
6. restarted pc multiple times to update drivers, done.
we all know all it takes is 3 easy commands to unlock bootlaoder
adb reboot bootloader
fastboot oem unlock
fastboot reboot
but in my case i always stuck at 2nd command. waiting for device is shown and nothing happens.
then i ran command, adb devices>> it shows
List of devices attached
adb server is out of date. killing...
* daemon started successfully *
LGH9182bfc6bdc device
next i put the command, fastboot devices and nothing is shown i just go to the next line... c:\adb>
so this is for sure that my device is not connected to the fastboot.
now my only question is, can this device bootloader unlock or not ? so that i stop pushing my limits.
any help will be appreciated.
regards.
Click to expand...
Click to collapse
Are you following this > https://r.tapatalk.com/shareLink/to...3&share_fid=3793&share_type=t&link_source=app
[ROOT] - lafsploit - H918 (any version up to and including 20h) - now n00b friendly
Sent from my HD1907 using Tapatalk
Thanks for thanks for replying on a short notice I have seen this post there is no reason to follow any of the post because the very first stage is to unlock the bootloader but as I cannot unlock the bootloader there is no point in following any of the posts my problem is what ever way I follow I am unable to to unlock the bootloader in fact what I can see is whenever I try to type in command ADB devices IC e my phone but when I type fastboot devices nothing happens it's like my phone is not in the fastboot that is why why I cannot unlock the bootloader I have tried every possible step mentioned on the internet and on various forums I also go through some videos on YouTube those guys follow the same steps and unlock their bootloader but my device cannot unlock for some reason so if you lovely people can help me out and figure out what exactly I am doing wrong as I have followed every step of unlocking the bootloader I've installed all the drivers I have updated all the drivers I have done exactly e all three steps which has been asked but still no luck thank you
clsA said:
Are you following this > https://r.tapatalk.com/shareLink/to...3&share_fid=3793&share_type=t&link_source=app
[ROOT] - lafsploit - H918 (any version up to and including 20h) - now n00b friendly
Sent from my HD1907 using Tapatalk
Click to expand...
Click to collapse
To be very precise after following the first step while unlocking the bootloader in the second step when we type fast boot devices it should show some hexadecimal numbers and it should confirm us that our device is in the fastboot mode but in my case whenever I type this command nothing happens that means my device is not recognised to go in the bootloader this is the main problem there is no point in following any of the posts if you cannot complete the very first stage of unlocking your bootloader if you can figure out what exactly is the problem I will be thankful to you because I have followed every step possible I've updated every ADB drivers LG drivers but nothing is helping out as even before starting the procedure of unlocking the bootloader my device is not going in the fast boot also I noticed one thing when I try to go inside the bootloader screen before that in my device manager it is shown as composit device but after that I think it gets disconnected fastboot oem unlock cannot work as it gives a message of waiting for the device after going are using the command ADB reboot bootloader so my problem is the command fastboot oem unlock is pretty useless as it waits for the device and it's stuck there forever please help me out if you can I will be thankful to you regards
X_BlackBurn_X said:
To be very precise after following the first step while unlocking the bootloader in the second step when we type fast boot devices it should show some hexadecimal numbers and it should confirm us that our device is in the fastboot mode but in my case whenever I type this command nothing happens that means my device is not recognised to go in the bootloader this is the main problem there is no point in following any of the posts if you cannot complete the very first stage of unlocking your bootloader if you can figure out what exactly is the problem I will be thankful to you because I have followed every step possible I've updated every ADB drivers LG drivers but nothing is helping out as even before starting the procedure of unlocking the bootloader my device is not going in the fast boot also I noticed one thing when I try to go inside the bootloader screen before that in my device manager it is shown as composit device but after that I think it gets disconnected fastboot oem unlock cannot work as it gives a message of waiting for the device after going are using the command ADB reboot bootloader so my problem is the command fastboot oem unlock is pretty useless as it waits for the device and it's stuck there forever please help me out if you can I will be thankful to you regards
Click to expand...
Click to collapse
Did you downgrade to software version H91810P? Because that should be the first thing you have to do to get everything else to work afterwards.
C D said:
Did you downgrade to software version H91810P? Because that should be the first thing you have to do to get everything else to work afterwards.
Click to expand...
Click to collapse
Thanks for the reply.
Can you please clear me one thing. To downgrade from h91820h to h91810p you need to unlock bootloader if i am not wrong. And in that case we will be back to square 1.
Its not about installing custom rom kernel recovery root or anything. Its only about unlocking the bootloader which i cannot do.
I hope you understand my pain.
I just want to unlock my bootloader thats it.
It used only 3 commands.
1. Adb devices - shows my device.
2. Fastboot devices - no fastboot device found.
This is the problem. When you cannot find any fastboot device even updating driver by going inside the bootloader the entire mission gets failed.
I cant find any solution for this. I dont know for what reason my device cannot be listed in fastboot mode.
X_BlackBurn_X said:
Thanks for the reply.
Can you please clear me one thing. To downgrade from h91820h to h91810p you need to unlock bootloader if i am not wrong. And in that case we will be back to square 1.
Its not about installing custom rom kernel recovery root or anything. Its only about unlocking the bootloader which i cannot do.
I hope you understand my pain.
I just want to unlock my bootloader thats it.
It used only 3 commands.
1. Adb devices - shows my device.
2. Fastboot devices - no fastboot device found.
This is the problem. When you cannot find any fastboot device even updating driver by going inside the bootloader the entire mission gets failed.
I cant find any solution for this. I dont know for what reason my device cannot be listed in fastboot mode.
Click to expand...
Click to collapse
fastboot doesn't work when the phone is booted up
adb reboot bootloader
followed by fastboot devices
Note: flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP
Example:
D:\fastboot>adb devices
List of devices attached
LGUS99740047103 device
D:\fastboot>adb reboot bootloader
D:\fastboot>fastboot oem device-id
...
(bootloader) ----------------------------------
(bootloader) Device-ID
(bootloader) F3D7DE171C893D55082EAE38270125EF
(bootloader) DA7CB3E78B1DB5709A2CA8********
(bootloader) ----------------------------------
OKAY [ 0.060s]
finished. total time: 0.060s
D:\fastboot>fastboot reboot
rebooting...
finished. total time: 0.008s
D:\fastboot>adb reboot bootloader
D:\fastboot>fastboot getvar unlocked
unlocked: no
finished. total time: 0.003s
Click to expand...
Click to collapse
X_BlackBurn_X said:
Thanks for the reply.
Can you please clear me one thing. To downgrade from h91820h to h91810p you need to unlock bootloader if i am not wrong. And in that case we will be back to square 1.
Its not about installing custom rom kernel recovery root or anything. Its only about unlocking the bootloader which i cannot do.
I hope you understand my pain.
I just want to unlock my bootloader thats it.
It used only 3 commands.
1. Adb devices - shows my device.
2. Fastboot devices - no fastboot device found.
This is the problem. When you cannot find any fastboot device even updating driver by going inside the bootloader the entire mission gets failed.
I cant find any solution for this. I dont know for what reason my device cannot be listed in fastboot mode.
Click to expand...
Click to collapse
As clsA said, flashing firmware does not require an unlocked bootloader.
Look at parts 1 and 2 of the other step by step guide here:
https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
clsA said:
fastboot doesn't work when the phone is booted up
adb reboot bootloader
followed by fastboot devices
Note: flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP
Example:
Click to expand...
Click to collapse
Thanks for the solution. May be this is it. All the time i have been doing it wrong.
Solution : flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP.
I will downgrade from 20h to 10p now and will give you feedback on this soon. Thanks a ton for showing a noob like me the right direction to work.
X_BlackBurn_X said:
Thanks for the solution. May be this is it. All the time i have been doing it wrong.
Solution : flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP.
I will downgrade from 20h to 10p now and will give you feedback on this soon. Thanks a ton for showing a noob like me the right direction to work.
Click to expand...
Click to collapse
No problem the link @C D posted above seems to have all the working links for you
clsA said:
No problem the link @C D posted above seems to have all the working links for you
Click to expand...
Click to collapse
well we have a new problem now.
lgup error 0x2bc invalid command response code = 0x80000202 at 4 percent while flashing.
did i just brick my phone now ? as it says dont unplug until you are done and we have been getting same error again and again.
used the provided kdz file flashing as an upgrade.
ok so the new problem is... may be i was trying to flash h91810p naugaut on to a oreo h91820h
and if i am not wrong at this stage i messed up pretty bad my phone is stuck in donwload mode wont boot up and i need to flash back 20h again to get out of this mess. can anyone hlp me ....
i just wanna know h91810p downgrading from 91820h is possible or not ? cause one is naugaut and one is oreo.
UPDATE:
i was flashing wrong h91810p thats why it was showing error. on another website i got the file compatible to my phone t mobile version and flash was successful.
now i am on h91810p software version andriod 7.
problem UPDATE:
i still cant unlock bootloader. same problem as before downgrading from h91820h.
adb devices shows device.
adb reboot bootloader
fastboot devices gives no result.
phone cannot enter in fastboot mode. the problem still remains the same even after changing the software.
kindly help guys
clsA said:
fastboot doesn't work when the phone is booted up
adb reboot bootloader
followed by fastboot devices
Note: flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP
Example:
Click to expand...
Click to collapse
hello clsA
"
D:\fastboot>adb devices
List of devices attached
LGUS99740047103 device
D:\fastboot>adb reboot bootloader
D:\fastboot>fastboot oem device-id
after this it only says waitng for device"
now i am on h91810p as i was instructed. can you please help.
its all happening the same way it was happening when was on h91820h.
fastboot devices cannot be found.
once it reboots in bootloader then it should detect a fastboot device but it doesnot and adb is also lost there.
kindly help.
NEW UPDATE:
my lg v20 now on software h91810p is actually a T MOBILE version. and when i researched more about it i found out T MOBILE deliberately locks the boot loader of many devices and its unlockable.
possible work around can be if the software version installed on your phone can some how be an international version of your ROM, then only you can unlock the bootloader else none of your commands will work. now i am trying to flash this phone using an international ROM version if i succeed i will update. but according to my knowledge flashing other roms other than t mobile ones will definitely give errors in LGUP.
X_BlackBurn_X said:
NEW UPDATE:
my lg v20 now on software h91810p is actually a T MOBILE version. and when i researched more about it i found out T MOBILE deliberately locks the boot loader of many devices and its unlockable.
possible work around can be if the software version installed on your phone can some how be an international version of your ROM, then only you can unlock the bootloader else none of your commands will work. now i am trying to flash this phone using an international ROM version if i succeed i will update. but according to my knowledge flashing other roms other than t mobile ones will definitely give errors in LGUP.
Click to expand...
Click to collapse
Do not flash another model's firmware onto the H918! Doing so will permanently brick your phone. The H918 in particular is incompatible with all other variants' software. Also, flashing H918 firmware onto any other model will also brick that phone.
C D said:
Do not flash another model's firmware onto the H918! Doing so will permanently brick your phone. The H918 in particular is incompatible with all other variants' software. Also, flashing H918 firmware onto any other model will also brick that phone.
Click to expand...
Click to collapse
hello
thanks for the reply.
i know we cannot flash any other phones firmware on to this model.
i was thinking of flashing specifically lg v20 h91810p international stock firmware, one is t mobile and one is international stock rom of same model.
cause t mobile is not allowing me to unlock the bootloader but an international stock rom will.
i have seen people doing on t mobile on youtube videos i dont know how they are doing it.
my problem is :
" as in message sent to various senior on this topic"
LG V20 H91810P, T MOBILE BOOTLOADER CANNOT BE UNLOCKED
HELLO
can you please help me out on a quest to unlock my bootloader of lg v20 h91810p. i have downgraded from h91820h to h91810p and still all the adb commands fail to make my phone go in to fastboot mode. i just cannot enter in fastboot mode,
adb devices shows my device
|but fastboot devices in bootloader mode doesnot show my device at all.
updated all the drivers used multiple pcs usb ports but no luck at all.,
what am i possibly doing wrong can you please help me out? i will be thankful to you.
on a side note i think t mobile has lockedd my bootloader so that i canoot unlock it,
regards
X_BlackBurn_X said:
hello
thanks for the reply.
i know we cannot flash any other phones firmware on to this model.
i was thinking of flashing specifically lg v20 h91810p international stock firmware, one is t mobile and one is international stock rom of same model.
cause t mobile is not allowing me to unlock the bootloader but an international stock rom will.
i have seen people doing on t mobile on youtube videos i dont know how they are doing it.
my problem is :
" as in message sent to various senior on this topic"
LG V20 H91810P, T MOBILE BOOTLOADER CANNOT BE UNLOCKED
HELLO
can you please help me out on a quest to unlock my bootloader of lg v20 h91810p. i have downgraded from h91820h to h91810p and still all the adb commands fail to make my phone go in to fastboot mode. i just cannot enter in fastboot mode,
adb devices shows my device
|but fastboot devices in bootloader mode doesnot show my device at all.
updated all the drivers used multiple pcs usb ports but no luck at all.,
what am i possibly doing wrong can you please help me out? i will be thankful to you.
on a side note i think t mobile has lockedd my bootloader so that i canoot unlock it,
regards
Click to expand...
Click to collapse
Did you make the Linux USB boot stick
Are you following the guide at all?
PART 3: CREATING A BOOTABLE LINUX USB USING FWUL
DOWNLOAD FWUL_v2.7_x86_64_15GB.zip FROM THE LINK BELOW AND EXTRACT THE IMAGE FILE SOMEWHERE IN YOUR PC.
https://androidfilehost.com/?w=files&flid=214529
DOWNLOAD RUFUS FROM BELOW AND INSTALL
https://rufus.akeo.ie/
INSERT A PEN DRIVE IN YOUR PC AND RUN RUFUS.
INSIDE RUFUS SELECT THE IMAGE FILE AND SELECT START (AFTER SELECTING START SELECT DD MODE IN THE DIALOGUE BOX) TO CREATE A BOOTABLE PEN DRIVE (WARNING: THIS WOULD FORMAT YOUR PEN DRIVE)
NOW YOU SHOULD BOOT YOUR PC FROM THE BOOTABLE USB STICK WHICH YOU HAVE JUST CREATED
THIS WOULD MAKE YOUR PC RUN LINUX OS
TYPE PASSWORD AS linux AND ENTER
Sent from my HD1907 using Tapatalk
clsA said:
Did you make the Linux USB boot stick
Are you following the guide at all?
PART 3: CREATING A BOOTABLE LINUX USB USING FWUL
DOWNLOAD FWUL_v2.7_x86_64_15GB.zip FROM THE LINK BELOW AND EXTRACT THE IMAGE FILE SOMEWHERE IN YOUR PC.
https://androidfilehost.com/?w=files&flid=214529
DOWNLOAD RUFUS FROM BELOW AND INSTALL
https://rufus.akeo.ie/
INSERT A PEN DRIVE IN YOUR PC AND RUN RUFUS.
INSIDE RUFUS SELECT THE IMAGE FILE AND SELECT START (AFTER SELECTING START SELECT DD MODE IN THE DIALOGUE BOX) TO CREATE A BOOTABLE PEN DRIVE (WARNING: THIS WOULD FORMAT YOUR PEN DRIVE)
NOW YOU SHOULD BOOT YOUR PC FROM THE BOOTABLE USB STICK WHICH YOU HAVE JUST CREATED
THIS WOULD MAKE YOUR PC RUN LINUX OS
TYPE PASSWORD AS linux AND ENTER
Sent from my HD1907 using Tapatalk
Click to expand...
Click to collapse
thanks again for the showing me the right direction. i was talking about unlocking the bootloader in step 1.
i will go through your links and try to study this.
just one more question.
does this method unlocks the bootloader ?
if yes please reply yes i will be thankful to you.
i will follow this step now.
regards
X_BlackBurn_X said:
hello clsA
"
D:\fastboot>adb devices
List of devices attached
LGUS99740047103 device
D:\fastboot>adb reboot bootloader
D:\fastboot>fastboot oem device-id
after this it only says waitng for device"
now i am on h91810p as i was instructed. can you please help.
its all happening the same way it was happening when was on h91820h.
fastboot devices cannot be found.
once it reboots in bootloader then it should detect a fastboot device but it doesnot and adb is also lost there.
kindly help.
Click to expand...
Click to collapse
Why does adb show your device as a 997 which is the Sprint variant
Sent from my LG-H910 using XDA Labs