[Q] Nexus 6 - Unlocking OEM from bootloader is possible? - Nexus 6 Q&A, Help & Troubleshooting

Hi All,
I know I have messed up, but want to know is there any remote possible way to do this?
I tried to flash and it failed and on top of that I used
Code:
fastboot oem lock
which has made it even more miserable. I am not able to recover anything now. This what I have tried to unlock OEM -
Code:
C:\>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.014s
C:\>fastboot oem get_unlock_data
...
(bootloader) This command is not needed to unlock. Run fastboot oem
(bootloader) unlock directly.
OKAY [ 0.029s]
finished. total time: 0.031s
I tried to install Google Stock by pressing on flash-all -
Code:
error: cannot load 'bootloader-shamu-moto-apq8084-71.08.img'
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
error: cannot load 'radio-shamu-d4.0-9625-02.95.img'
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
error: failed to load 'image-shamu-lmy47i.zip': No such file or directory
Press any key to exit...
Screens have been attached
Is there any remote possibility on what can be done?
What I learned is when new stuffs arrive study it properly before messing with it around :laugh:

stygianblizzard said:
Hi All,
I know I have messed up, but want to know is there any remote possible way to do this?
I tried to flash and it failed and on top of that I used
Code:
fastboot oem lock
which has made it even more miserable. I am not able to recover anything now. This what I have tried to unlock OEM -
Code:
C:\>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.014s
C:\>fastboot oem get_unlock_data
...
(bootloader) This command is not needed to unlock. Run fastboot oem
(bootloader) unlock directly.
OKAY [ 0.029s]
finished. total time: 0.031s
I tried to install Google Stock by pressing on flash-all -
Code:
error: cannot load 'bootloader-shamu-moto-apq8084-71.08.img'
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
error: cannot load 'radio-shamu-d4.0-9625-02.95.img'
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
error: failed to load 'image-shamu-lmy47i.zip': No such file or directory
Press any key to exit...
Screens have been attached
Is there any remote possibility on what can be done?
What I learned is when new stuffs arrive study it properly before messing with it around :laugh:
Click to expand...
Click to collapse
If you don`t have TWRP installed you`re screwed and you have to send it in for repair .....

gee2012 said:
If you don`t have TWRP installed you`re screwed and you have to send it in for repair .....
Click to expand...
Click to collapse
Ya its there... I switch to TWRP or bootloader and trying to experiment more to get out of it. Thing is I am not able to flash anything. I tried pushing google stock files using ADB commands but when I am trying to install them its failing.

stygianblizzard said:
Ya its there... I switch to TWRP or bootloader and trying to experiment more to get out of it. Thing is I am not able to flash anything. I tried pushing google stock files using ADB commands but when I am trying to install them its failing.
Click to expand...
Click to collapse
Try this: Reboot to bootloader, select recovery mode, enter TWRP, mount MTP and push/sideload and flash a flashable image from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.

gee2012 said:
Try this: Reboot to bootloader, select recovery mode, enter TWRP, mount MTP and push/sideload and flash a flashable image from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
TWRP cannot flash the stock images. Only flash able zips. The modified zips linked by @gee2012 should work

gee2012 said:
Try this: Reboot to bootloader, select recovery mode, enter TWRP, mount MTP and push/sideload and flash a flashable image from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
Just few mins got img downloaded. That was bloody awesome. I dont know how to thank you :laugh::laugh::laugh::good:
Superb
Its working again!!!!!

Related

Unable to unlock Z1 bootloader - LP 270

I had unlocked, installed dual recovery and rooted my phone with LP. This latest update (270) removed my root and locked my bootloader (Service meuu says unlock allowed = Yes) . I tried to unlock it again using flash tool and adb cmd and both seem to fail. In flashtool it keeps saying that my code is wrong (I created a folder in custom folder with ulcode name and a txt file with the ulcode) still din work. In adb cmd i am getting
version: 0.5
finished. total time: 0.003s
FAILED (remote: Command did not succeed)
finished. total time: 0.021s
FAILED (remote: Device is already rooted)
finished. total time: 0.004s
I have installed all drivers in my system too. Any help?
ravi_buz said:
I had unlocked, installed dual recovery and rooted my phone with LP. This latest update (270) removed my root and locked my bootloader (Service meuu says unlock allowed = Yes) . I tried to unlock it again using flash tool and adb cmd and both seem to fail. In flashtool it keeps saying that my code is wrong (I created a folder in custom folder with ulcode name and a txt file with the ulcode) still din work. In adb cmd i am getting
version: 0.5
finished. total time: 0.003s
FAILED (remote: Command did not succeed)
finished. total time: 0.021s
FAILED (remote: Device is already rooted)
finished. total time: 0.004s
I have installed all drivers in my system too. Any help?
Click to expand...
Click to collapse
Try unlocking from Sony's site ( official method ) http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Good Luck :fingers-crossed:
Found the solution
Please check my post here http://forum.xda-developers.com/showpost.php?p=61450689&postcount=390

BootLoop HTC 626g (lock bootloader, mod recovery, firmware)

There HTC 626G, revision 1.79.401.100. During the study, on new devices starting with the revision (build) 1.72.401.101, with modified firmware recovery phone goes bootloop. Initially it was assumed that the problem was incompatible version recovery (old and new versions). new recovery was made under my revision, and after flashing turned bootloop.
When loading stock version:
fastboot flash recovery recovery_stock.img responses with:
sending 'recovery' (10240 KB)...
OKAY [ 0.417s]
writing 'recovery'...
FAILED (remote:
Security deny - Err:0x2017
)
finished. total time: 0.430s
Since version error recovery not confirmed, it remains an unlocked bootloader.
When you enter the command:
C:\Users\bugae\Desktop\android>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.007s
C:\Users\bugae\Desktop\android>fastboot oem identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.006s
C:\Users\bugae\Desktop\android>fastboot oem token
...
FAILED (remote: unknown command)
finished. total time: 0.020s
fastboot oem unlock (the tablet responses with a question screen where I can select "yes, unlock bootloader" and "no, don't unlock bootloader", but when I select yes it responses with an error "Unlock failed - Err:0x7000")
Standard methods do not work!(
How to be? What to do?
Backup 4pda.ru/forum/index.php?s=&showtopic=756527&view=findpost&p=53005677
Try using win droid toolkit, I had the same issue with my 626 and I fixed mine here's a link
http://forum.xda-developers.com/devdb/project/?id=1314#downloads
https://forum.xda-developers.com/showpost.php?p=77300835&postcount=2

Can I still battery charging after a Fullwipe?

Hello, I was on Android Marshmellow 6.0.1 + SU and I made with TWRP a full backup (+TA.img). I wiped:
+Dalwik
+Cache
+Data
+System
+Internal Storage
-Micro SDcard
Then booting into the TRWP 3.1.0.1 revovery did not work anymore (only Sony logo) and I thought I have to flash TWRP again. I used cmd administrator with this commands:
C:\adb>fastboot.exe -i 0x0fce oem unlock 0xxxx640DA639C0xxx
...
OKAY [ 3.281s]
finished. total time: 3.281s
C:\adb>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (13092 KB)...
OKAY [ 0.547s]
writing 'recovery'...
OKAY [ 0.875s]
finished. total time: 1.422s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.000s
I hold the volume down button and i was able to come into TWRP menu. Problem: I forgot to save my Lineage files on Micro SDcard, so flashing was not possible for me and I made it off (Volup + Power) After copieng with the pc the needed flash files to micro sdcard I tried again booting to TWRP recovery but does still not work. Then I tried some more commands:
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\adb>fastboot reboot
rebooting...
finished. total time: -0.000s
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.406s]
booting...
OKAY [ 0.063s]
finished. total time: 0.484s
C:\adb>fastboot reboot
< waiting for any device >
rebooting...
finished. total time: -0.000s
C:\adb>adb ls -h
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: error: failed to get feature set: no devices/emulators found
C:\adb>adb shell
error: no devices/emulators found
C:\adb>adb devices
List of devices attached
C:\adb>fastboot devices
YT9119CPJT fastboot
C:\adb>
I´m still in a bootloop and i can not see that my smartphone is charging the battery. At last it saw only 50% in TRWP
and I don´t realy know what I have to do now. Need HELP :crying:
P.S.: I am on Windows 10 home (64 bit) and flashtool-0.9.25.0 told me all drivers was succefuly installed (with Win10 Disable Driver Signature Enforcement) and I used twrp-3.0.2-1-z3c.img
Edit: After some research, I read the battery can not charging, because it's in bootloader mode and i have to flash the stock rom back. I did it succesfully with flashtool

Unable to unlock/flash recovery

I am trying to unlock the bootloader and flash TWRP for the first time. I followed the steps from here: https://wiki.lineageos.org/devices/s2/install
I turned on the unlock option in settings and unlocked via fastboot, rebooted it manually (it didn't reboot), and then tried to flash:
Code:
$ ./fastboot oem unlock-go
OKAY [ 0.007s]
Finished. Total time: 0.007s
$ ./fastboot flash recovery twrp-3.3.1-0-s2.img
Sending 'recovery' (24618 KB) OKAY [ 0.859s]
Writing 'recovery' FAILED (remote: 'Partition flashing is not allowed')
fastboot: error: Command failed
$ ./fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.001s
$ ./adb reboot bootloader
$ ./fastboot flash recovery twrp-3.3.1-0-s2.img
Sending 'recovery' (24618 KB) OKAY [ 0.779s]
Writing 'recovery' FAILED (remote: 'Partition flashing is not allowed')
fastboot: error: Command failed
$ ./fastboot oem unlock-go
OKAY [ 0.007s]
Finished. Total time: 0.007s
$ ./fastboot flash recovery twrp-3.3.1-0-s2.img
Sending 'recovery' (24618 KB) OKAY [ 0.836s]
Writing 'recovery' OKAY [ 0.231s]
Finished. Total time: 1.071s
$ ./fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.001s
However, I got into the stock recovery page instead of TWRP. You can see above that the flash failed before I rebooted, but succeeded after that. Interesting observations:
- The above webpage indicates that the device should reset when I reboot, but it didn't, which means the unlock didn't work.
- When I went back to bootloader, the first attempt to flash failed, but when I ran another unlock it worked though apparently it did nothing.
Am I missing a step? I am using fastboot version 29.0.6-6198805 on Mac OS Mojave 10.14.6.
Don't reboot to recovery via a command after flashing it.
Try rebooting using buttons, vol-up + power.
kalehrl said:
Don't reboot to recovery via a command after flashing it.
Try rebooting using buttons, vol-up + power.
Click to expand...
Click to collapse
Thank you! That got me into TWRP with a dialog titled "Unmodified System Partition" with a slider to allow modifications. I am googling to see what this dialogue is about and how to get TWRP to permanently get installed.
That's normal. Just enable modifications and that's it.
kalehrl said:
That's normal. Just enable modifications and that's it.
Click to expand...
Click to collapse
OK, I don't remember seeing it before (I haven't flashed in at least a couple of years). I ran `adb reboot recovery` and it did go back into TWRP, so I am assuming that it did get persisted. For some reason "Never show this screen..." option didn't work, which is fine, but does it indicate that something is still readonly?
I don't think so.
You're good to proceed.
I was able to sideload the ROM and opengapps nano and it is booting up for the first time. I skipped the optional step to install root (AddonSU), I guess I can do it later too if I feel the need to get root. Thanks a lot for your quick help.
No problem.
If you want to root it, do it with Magisk.
Nowadays, LineageOS team recommend it.

(solved) Can't either unlock OEM or install recovery (Preflash validation failed)

Hello
I just purchased a cheap new Moto G7 Plus, only to install LineageOS on it. The phone is brand new and I just upgraded it to the latest Android 10.
I followed all instructions so far, and I am stuck, can't unlock the bootloader and/or install a recovery.
To unlock the bootloader I carefully followed instructions on the LineageOS wiki
Then I followed instructions on Motorola website
I received an email from Motorola with the unlock code
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock CODE_RECEIVED_IN_THE_MAIL
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: 0.016s
Despite the fact that it says OKAY, when I reboot in fastboot flash mode, I still see the message "oem_locked". So I am not totally sure that the unlock succeeded.
Then whatever I try, I can't install TWRP, see below :
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
Z*****F5RR fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock CODE_RECEIVED_IN_THE_MAIL
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot twrp-3.4.0-0-lake.img
target reported max download size of 536870912 bytes
sending 'boot' (30080 KB)...
OKAY [ 0.686s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.708s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp-3.4.0-0-lake.img
downloading 'boot.img'...
OKAY [ 0.686s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.702s
C:\Program Files (x86)\Minimal ADB and Fastboot>
I obviously googled a few time but can't find any working solution. Some says its because my OEM is still locked, others because the USB port or cable might be problematic. I tried on 5 USB ports and a USB hub and I have the same issue, and my cable is brand new. I also restarted the whole unlocking procedure, received another mail from Motorola, with exactly the same unlock key, unlocked 10 times, nothing changes.
Any hint ?
Cheers
Ok forget it, its solved. I am an idiot I forgot to activate developer mode in the settings
Fastboot boot twrp 3.4 infinitely?
Unlocked my oem, adp whenever I fastboot boot twrp 3.4 it just gets stuck on downloading. No fail code just stays on downloading infinitely. Would love some help!
same
Richard2707 said:
Unlocked my oem, adp whenever I fastboot boot twrp 3.4 it just gets stuck on downloading. No fail code just stays on downloading infinitely. Would love some help!
Click to expand...
Click to collapse
trying on my xt1965-2 and having this same issue, did you manage a workaround?
The twrp file needs to be in the correct location and the name needs to be exact.
I use linux so check up on which locations to use in windows.
But on linux I open a terminal in the folder where twrp is located.
So if the filename for twrp is for instance "twrp-3.3.1-0-lake.img", the command needs to be:
fastboot boot twrp-3.3.1-0-lake.img (NO spaces in the file name!)
Fastboot then pushes the file to the phone and boots it.

Categories

Resources