I've managed to unlock the bootloader on a friend's Zenfone 2 (Z00A); or, at least, I believe I have, because the boot splash screen has the inverted colors that most threads on BL unlocking mention. I used this method, inside a Windows XP VM.
The thing is, I can't flash TWRP. If I try, it tells me permission was denied.
Code:
[email protected]:~/dev/android/sdk/platform-tools$ sudo ./fastboot flash recovery /media/michael/2D66-7551/Zenfone\ 2\ ZE551ML/twrp-3.0.0-0-Z00A.img
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'recovery' (15674 KB)...
OKAY [ 0.967s]
writing 'recovery'...
FAILED (remote: Permission denied
)
finished. total time: 1.123s
(The same thing happens if run from inside the XP VM.)
Could someone please steer me in the right direction?
Sorry i can't post any external link.
I had this kind of problem the first time, because you need to root the phone after you unlock the bootloader.
Follow this step : http://forum.xda-developers.com/zenfone2/general/tool-one-click-bootloader-unlock-root-t3155884
then
Enter that in google : gurus wizard/2015/07/root-and-unlock-bootloader-on-asus-zenfone-2.html
Related
I got a m8 yesterday after switching to T-mobile and I would really like to unlock/root/mod it. I've rooted other phones before and haven't had this much trouble with them.
I get through all of the steps, run fastboot flash unlocktoken Unlock_code.bin which runs fine (gives option to unlock or not, I select yes with the power button) and reboots the phone. The phone is wiped as it's supposed to be, and I turn off the fast boot and turn on usb debugging in the options after the basic set up. When I boot it into fastboot to install the recovery, it still says *** LOCKED *** at the top of the screen, and I get this when I try to install it
XXX-Inspiron-N5010:~/Downloads/fastboot$ sudo fastboot flash recovery Recovery.img
[sudo] password for XXX:
target reported max download size of 1830608896 bytes
sending 'recovery' (14818 KB)...
OKAY [ 1.635s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.169s
I've tried this on two different computers and with different recovery files, one running Windows 8 and the other Ubuntu five times and I can't find anyone else that has had the same problem. I would appreciate any help with this as it's getting quite frustrating
Ditt0 - I have the same problem
Kittycatpenut said:
I got a m8 yesterday after switching to T-mobile and I would really like to unlock/root/mod it. I've rooted other phones before and haven't had this much trouble with them.
I get through all of the steps, run fastboot flash unlocktoken Unlock_code.bin which runs fine (gives option to unlock or not, I select yes with the power button) and reboots the phone. The phone is wiped as it's supposed to be, and I turn off the fast boot and turn on usb debugging in the options after the basic set up. When I boot it into fastboot to install the recovery, it still says *** LOCKED *** at the top of the screen, and I get this when I try to install it
XXX-Inspiron-N5010:~/Downloads/fastboot$ sudo fastboot flash recovery Recovery.img
[sudo] password for XXX:
target reported max download size of 1830608896 bytes
sending 'recovery' (14818 KB)...
OKAY [ 1.635s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.169s
I've tried this on two different computers and with different recovery files, one running Windows 8 and the other Ubuntu five times and I can't find anyone else that has had the same problem. I would appreciate any help with this as it's getting quite frustrating
Click to expand...
Click to collapse
I'm experiencing the same thing. Can't flash recovery. Have followed instructions to Unlock bootloader through HTCdev and have gone through the process numerous times on different machines without any apparent error. Please help!
target reported max download size of 1830608896 bytes
sending 'recovery' (16576 KB)...
OKAY [ 1.479s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.093s
Dumb question #1
Have you tried different USB ports just to zero out all variables
---------- Post added at 07:07 AM ---------- Previous post was at 07:07 AM ----------
Either of you two
---------- Post added at 07:54 AM ---------- Previous post was at 07:07 AM ----------
@Kittycatpenut
@andersonwittekind
I would ask in the T-Mobile forum only cause you might find an answer faster
http://forum.xda-developers.com/showthread.php?t=2725099
My M8 was once upon a time a Rogers M8.
Quite some time ago i converted it to a GPE with 5.1.
It was rooted and is S-Off.
Last night I pushed the MM RUU from GraphixNYC. It worked and I was happy.
Except I like to teak the DPI so I root it.
This morning I installed TWRP2.8.7.0 recovery and allowed TWRP to SuperSu it.
Now when it boots I don't get past the loading screen.
I can put it in Fastboot, connect to it from my Mac, and to push the LP/MM RUUs.
Both fail in the same way (below). What can I do?
------ 5.1 ----
~/Documents/Android/platform_tools/Mac => ./fastboot devices
SH45LWM0nnnnn fastboot
~/Documents/Android/platform_tools/Mac => ./fastboot flash zip RUU51.zip
target reported max download size of 1826414592 bytes
sending 'zip' (649759 KB)...
OKAY [ 23.080s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 23.085s
~/Documents/Android/platform_tools/Mac =>
----- 6.0 ---
~/Documents/Android/platform_tools/Mac => ./fastboot flash zip RUU60.zip
target reported max download size of 1826414592 bytes
sending 'zip' (633780 KB)...
OKAY [ 22.373s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 22.378s
~/Documents/Android/platform_tools/Mac =>
----
I got this working.
I took the v6 RUU, put it on my external SD, renamed it as 0p6bimg and booted into HBOOT.
I guess I did this: http://forum.xda-developers.com/showthread.php?t=2708589
A second time, carefully following the directions I have MM + systemless root.
http://forum.xda-developers.com/htc-one-m8/general/root-root-marshmallow-gpe-supersu-t3242210
I delete my recovery and cant insatall a new recovery :/
Code:
C:\Users\xxx\Desktop\adb>fastboot flash recovery 3.35.617.12_recovery.img
target reported max download size of 800000000 bytes
sending 'recovery' (20716 KB)...
OKAY [ 2.106s]
writing 'recovery'...
(bootloader) HOSD CL#576582
FAILED (remote: 9: SD_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCK)
finished. total time: 3.128s
RUU back to stock ??
Your bootloader is locked...causing the failure...
Tick "allow bootloader unlock" in developer settings.
On your pc go to htcdev website and get your unlock token and push it via fastboot to your device. Then you can flash twrp, make a system backup!!!!! and flash supersu for root.
Beware, you lose ota ability. This is why you MUST make a backup with twrp BEFORE flashing supersu.
There is only one working supersu so choose wisely.
Sent from my HTC One M9 using Tapatalk
Hi,
what i did so far was:
unlocked the bootloader
download the twrp recovery img (...ruu.lalleman.net/HTC_M8S%28QL_UL%29/Recovery/twrp-recovery-2.8.7.0-m8s-qlul/)
set phone on Fastboot USB
over the cmd bar (windows 10) i used fastboot and got this result:
C:\Android>fastboot flash recovery twrp-2.8.7.0-m8s-qlul.img
target reported max download size of 16510976 bytes
Invalid sparse file format at header magi
sending sparse 'recovery' 1/2 (15368 KB)...
OKAY [ 1.899s]
writing 'recovery' 1/2...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.907s
I have no idea what i did wrong or how i can solve the problem. I just wanted run the twrp, use the Superuser. zip to have the rootet htc one m8s.
Thajin said:
Hi,
what i did so far was:
unlocked the bootloader
download the twrp recovery img (...ruu.lalleman.net/HTC_M8S%28QL_UL%29/Recovery/twrp-recovery-2.8.7.0-m8s-qlul/)
set phone on Fastboot USB
over the cmd bar (windows 10) i used fastboot and got this result:
C:\Android>fastboot flash recovery twrp-2.8.7.0-m8s-qlul.img
target reported max download size of 16510976 bytes
Invalid sparse file format at header magi
sending sparse 'recovery' 1/2 (15368 KB)...
OKAY [ 1.899s]
writing 'recovery' 1/2...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.907s
I have no idea what i did wrong or how i can solve the problem. I just wanted run the twrp, use the Superuser. zip to have the rootet htc one m8s.
Click to expand...
Click to collapse
Use HTC_fastboot and not the generic fastboot..
nopynel said:
Use HTC_fastboot and not the generic fastboot..
Click to expand...
Click to collapse
I have the same problem and just ask now because i am really confused about the hole stuff here.. Have we now to tipp in cmd
C:\Android>HTC_fastboot flash recovery twrp-2.8.7.0-m8s-qlul.img ??
Edit: Ok, i find HTC_Fastboot there > ruu.lalleman.net/HTC_M8S%28QL_UL%29/Tools/Fastboot/ and it solve this problem.
But i think its still not everything fine.. if i change to hboot on bootlader i get this infomations
fs5.directupload.net/images/160727/z9lr634u.jpg
whether unlock bootloader?
Hi, I have a OnePlus 3 that boot loops, with no recovery. Holding Volume Button + Power does not work, the only option is fast boot.
When trying to Flash a new recovery i get the following ..
Code:
c:\>fastboot flash recovery cm-13.0-20160814-NIGHTLY-oneplus3-recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (14952 KB)...
OKAY [ 0.397s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.445s
c:\>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s
My Question, Is there a way to unlock partitions via fastboot. or can you sugest a thread or solution to this issue.
Thanks
You must be able to toggle the "Allow OEM Unlock" switch in developer options to unlock the bootloader so unless you can get there then you've got a brick.
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus 3
I was stuck here as well. You can push an update through fastboot/adb. It takes FOREVER, but you'll at least have a phone that works. Try and push recovery once you can oem unlock
This Worked.
Thanks, This Worked for me.
mohsen8 said:
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus 3
Click to expand...
Click to collapse