Hi Folks,
I'm kinda stuck here. Spent the lst 2 hours googling for a possible solution but no luck.
I've tried to OEM Unlock my OP2 to flash TWRP. When I typed fastboot oem unlock in cmd command, my phone started to reboot itself every 1 second.
I've installing the corect drivers using SDK Tools.
Please help as I'm not sure what else I can do.
Did you ticked under dev options allow oem unlock? Try to flash latest stock rom and then unlock.
acmerw said:
Did you ticked under dev options allow oem unlock? Try to flash latest stock rom and then unlock.
Click to expand...
Click to collapse
I did turn on OEM Unlock as well as USB Debugging. I've tried to unlock the bootloader using the app on this thread as well as via cmd command. In both scenarios the phone goes into continuos reboot cycle (every 1 sec). I'm able to boot into fastboot (it says Fastboot on the screen) by pressing and holding the power+volume up button.
I've tried flashing twrp or stock room with no success. Every time i try to flash something it says:
C:\Android>fastboot flash recovery twrp.img
< waiting for device >
target reported max download size of 536870912 bytes
sending 'recovery' (28144 KB)...
OKAY [ 0.808s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.836s
C:\Android>
Any advise would be greatly appreciated!
Got it working again by using the following commands while in fastboot mode:
"fastboot continue"
Thanks to below thread.
http://forum.xda-developers.com/oneplus-2/help/boot-locked-bootloader-installing-twrp-t3229828
Related
Hey, i tried to install the android 6.0 beta from this forum, but i was rooted, now its stuck in a loop where it turns off, turns on and tries to install it and fails at 0%, and again. I can enter Fastboot/rescue mode and thats it. I tried to flash recovery boot and system.img in adb and fastboot, but it shows this:
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (31630 KB)...
OKAY [ 1.265s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.265s
C:\Program Files\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (22796 KB)...
OKAY [ 0.858s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.874s
C:\Program Files\Minimal ADB and Fastboot>fastboot flash system.img
unknown partition 'SYSTEM.img'
error: cannot determine image filename for 'SYSTEM.im
C:\Program Files\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 471859200 bytes
Help pls. I tried everything...
System.img flash failed after 2 mins now too. Still no idea.
Looks like you've used the KingRoot method to root your phone.
Flashing via fastboot requires the fastboot to be unlocked.
The message "FAILED (remote: Command not allowed)" indicates, that the script tried to execute the command, but because the bootloader is still locked, it cannot do such thing.
There are 2 solutions:
Download the original firmware and try to update to it via the "dload" method. (sdCard>dload>UPDATE.APP)
Try to unlock the bootloader. But for unlocking, you'll need the Product ID, which as of now, only obtainable, when the phone is able to boot up.
I really recommend trying to download the firmware, and give the "dload" method a shot, because without an unlocked bootloader, nothing you can do at home.
Right, it's almost nothing. There's this site called DC-Unlocker, and with a fast runthrough, it should be able to unlock the bootloader, but I haven't tried, or tested it in any way. Still an interesting program, though.
Edit:
Just saw your post under the other similar topic.
You should try to do a Factory Reset, by hand, via fastboot, and then updating with the "dload" method again.
The commands are:
fastboot erase cache
fastboot erase userdata
Maybe this helps.
daviddosa said:
Looks like you've used the KingRoot method to root your phone.
Flashing via fastboot requires the fastboot to be unlocked.
The message "FAILED (remote: Command not allowed)" indicates, that the script tried to execute the command, but because the bootloader is still locked, it cannot do such thing.
There are 2 solutions:
Download the original firmware and try to update to it via the "dload" method. (sdCard>dload>UPDATE.APP)
Try to unlock the bootloader. But for unlocking, you'll need the Product ID, which as of now, only obtainable, when the phone is able to boot up.
I really recommend trying to download the firmware, and give the "dload" method a shot, because without an unlocked bootloader, nothing you can do at home.
Right, it's almost nothing. There's this site called DC-Unlocker, and with a fast runthrough, it should be able to unlock the bootloader, but I haven't tried, or tested it in any way. Still an interesting program, though.
Click to expand...
Click to collapse
Ive got all the informations for getting the bootloader unlock code, but when i type it in the thing by huawei to get the unlock code it tells me that its wrong... I could get it here if you could help me with it?
Hello,
I'd like to request a bootloader unlock code for my Huawei device
Information:
Product: HUAWEI ALE-L21
SN:
IMEI:Nvm
Product IDups.
Thank you!
So, this is the e-mail i sent to Huawei, they couldnt help me. Everything here is directly from the phone itself, so i dont think its wrong.
With the Product ID, you can get the code, but the details above are wrong, more precisely one of them, which is the Phone Name
Try it without the HUAWEI, it should look like this: "ALE-L21" (without the " of course).
If it somehow would not work for you, I sent you a PM with your unlock code in it.
Note: I recommend not to publish your information like this. The phone is blockable with the IMEI remotely by the service providers or the police. Please remove them for your own safety.
Tried the update again, now flashing doesnt even work.
For the last week I have been trying to root and install TWRP on my Huawei p8 Lite ALE21. Sofar every attempt has failed.
Steps taken:
Get Bootloader Code
Unlock bootloader with "fastboot oem unlock"
Flash TWRP with "fastboot flash recovery recovery.img"
Result:
When booting into recovery the default "Huawei eRecovery" opens, not TWRP
No app can detect root
Additional info:
TWRP form here: http://forum.xda-developers.com/p8lite/development/testing-twrp-2-8-7-x-huawei-p8lite-qcom-t3187758
Trying to debug the problem, I entered
Code:
fastboot getvar all
this returned
Code:
getvar:all FAILED (remote: Command not allowed)
Additional I have tried to downgrade to android 5.0 again, but after copying the Firmware to the "dload" folder and holding the Volume-Up and Down and Power buttons, the phone wouldn't do anything but show the huawei logo and turn off.
Any help would be very appreciated!
Thank you in advance,
Oisin
Oisins said:
For the last week I have been trying to root and install TWRP on my Huawei p8 Lite ALE21. Sofar every attempt has failed.
Steps taken:
Get Bootloader Code
Unlock bootloader with "fastboot oem unlock"
Flash TWRP with "fastboot flash recovery recovery.img"
Result:
When booting into recovery the default "Huawei eRecovery" opens, not TWRP
No app can detect root
Additional info:
TWRP form here: http://forum.xda-developers.com/p8lite/development/testing-twrp-2-8-7-x-huawei-p8lite-qcom-t3187758
Trying to debug the problem, I entered
Code:
fastboot getvar all
this returned
Code:
getvar:all FAILED (remote: Command not allowed)
Additional I have tried to downgrade to android 5.0 again, but after copying the Firmware to the "dload" folder and holding the Volume-Up and Down and Power buttons, the phone wouldn't do anything but show the huawei logo and turn off.
Any help would be very appreciated!
Thank you in advance,
Oisin
Click to expand...
Click to collapse
In order to boot in twrp recovery you should first remove your usb cable,once is done,press and hold volume up and power button,once you see huawei logo,release power button but keep press on volume up,about firmware witch build number do you have on your phone,share more info if you want a quick help
"No app can detect root"
TWRP isn't root
"fastboot flash recovery recovery.img"
Any error?
"....(remote: Command not allowed)"
i think you have to unlock bootloader
Thank you for you quick response!
Running "fastboot flash recovery recovery.img" returns
Code:
target reported max download size of 471859200 bytes
sending 'recovery' (27062 KB)...
OKAY [ 0.880s]
writing 'recovery'...
OKAY [ 2.084s]
finished. total time: 2.967s
I checked if the bootloader is unlocked with "fastboot oem get-bootinfo"
Code:
(bootloader) unlocked
OKAY [ 0.003s]
finished. total time: 0.003s
I also tried booting into recovery without the cable plugged it, but it still just booted into "eRocovery"
More info
Product: ALE-L21
Serial: W3D4C16916992523
Build: ALE-L21C432BB574
just try this:
1) (re) boot normally
2) attach to pc with usb cable
3) reboot into recovery using adb command: adb reboot recovery
ItalianWolf said:
just try this:
1) (re) boot normally
2) attach to pc with usb cable
3) reboot into recovery using adb command: adb reboot recovery
Click to expand...
Click to collapse
The phone reboots, shows the HUAWEI logo and then turn off again.
Sorry, i didn't read the post linked.
You need twrp 3.0.2 for B5xx, i was thinking you had the right one (2.8.7 works on kk and maybe lollipop), so here you are: http://forum.xda-developers.com/p8lite/general/twrp-3-0-0-0-p8-lite-kirin-t3343320
ItalianWolf said:
Sorry, i didn't read the post linked.
You need twrp 3.0.2 for B5xx, i was thinking you had the right one (2.8.7 works on kk and maybe lollipop), so here you are: http://forum.xda-developers.com/p8lite/general/twrp-3-0-0-0-p8-lite-kirin-t3343320
Click to expand...
Click to collapse
It worked! Thank you very very much! I spend sooo much time on this... wow thanks!
Folks,
I have a ZF2L aka ZE551KL which is currently in a bootloop. Why that happened I have no idea as I have not dinked with the stock rom or for that matter even unlocked the bootloader.
A little bit of history, over the weekend, I had plugged in my phone to charge it and then when it completed charging I unplugged it and then tried to reboot it. That was the last time I had it working. After the reboot the phone has been in a bootloop ever since.
In order to try to recover from the above, I started reading a bit on what to do and I came across the postings that mentioned the bootloader has to be dropped to the Lollipop level so that it can be unlocked and then the recovery can be upgraded to Marshmallow. While trying to get all of that done, I have ended up here.
I "think" I have unlocked the bootloader using the command
echo -ne "\x01" | dd obs=1 count=1 seek=16 of=/dev/block/bootdevice/by-name/devinfo
I ran the above command directly on the phone via the terminal in TWRP. I booted into TWRP using the following fastboot command
fastboot boot twrp-3.2.3-0-Z00T.img
Running the fastboot command, fastboot oem device-info gives me the following output
C:\Users\home\android\platform-tools\images>fastboot oem device-info
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
Finished. Total time: 0.016s
However when I try to flash a new recovery TWRP-3.2.3-0-Z00T I get the following error
C:\Users\home\android\platform-tools\images>fastboot flash recovery twrp-3.2.3-0-Z00T.img
Sending 'recovery' (29856 KB) OKAY [ 1.342s]
Writing 'recovery' FAILED (remote: 'Permission denied, phone is protected')
Finished. Total time: 1.388s
I'm a little lost on what's going on. The device-info tells me the bootloader is unlocked, however it appears that something else is still locked which is not allowing the recovery to get flashed.
The stock recovery I was on before this all started was asus/WW_Z00T/ASUS_Z00T/6.0.1/MMB29P/WW_user_21.40.1220.2181_20170805. The recovery I currently have is LRX22G.WW_user_1.16.40.763_20151201
Any pointers on what I could do to get this resolved would be helpful?
hi if ur bootloader is unlocked, u an do a fresh flash of all d partitions as sometimes things get messed up on its own.
download firmware from https://drive.google.com/file/d/0B43Ue6xY9MmdN0UzWVRFcno4N0U/view and extract, then run flashall.cmd (in fastboot mode i.e. pwr and vol up)
u should finish without any hiccups. u will lose twrp though
tried on mine it woks. but google frp may be active so keep ur email n pass handy. m not responsible for any damages though ...
I'm trying to flash and start the TWRP. I've already done this once on a LG G6 (h870).
I downloaded TWRP from there: twrp.me/h870
Code:
OEM is unlocked:
fastboot getvar unlocked
unlocked: yes
Code:
fastboot flash recovery twrp-3.2.3-0-h870.img
Sending 'recovery' (21420 KB) OKAY [ 0.911s]
Writing 'recovery' OKAY [ 0.190s ]
After the flash, I start the recovery mode by pressing the button combination. After that I get the factory reset request, -> I choose 2x "yes".
The LG logo appears and then the splash screen of TWRP. But instead of getting into TWRP, the screen gets dark again and the phone restarts in the system.
I didn't find the same problem anywhere in a forum. Does anyone know what I can try to do to successfully start TWRP? Thank you for your help!
Unlocking again did the trick
trubadur2 said:
I'm trying to flash and start the TWRP. I've already done this once on a LG G6 (h870).
I downloaded TWRP from there: twrp.me/h870
Code:
OEM is unlocked:
fastboot getvar unlocked
unlocked: yes
Code:
fastboot flash recovery twrp-3.2.3-0-h870.img
Sending 'recovery' (21420 KB) OKAY [ 0.911s]
Writing 'recovery' OKAY [ 0.190s ]
After the flash, I start the recovery mode by pressing the button combination. After that I get the factory reset request, -> I choose 2x "yes".
The LG logo appears and then the splash screen of TWRP. But instead of getting into TWRP, the screen gets dark again and the phone restarts in the system.
I didn't find the same problem anywhere in a forum. Does anyone know what I can try to do to successfully start TWRP? Thank you for your help!
Click to expand...
Click to collapse
For whatever reason, this was the solution:
Code:
fastboot flash unlock unlock.bin
Good news ...
I had the same problem as you with TWRP 3.2.3 H870 and i finally used the "unofficial twrp" developped by RunningNak3d" ...
In other words, you unlocked your phone twice !!!
Did your unlock it a second time, then flashed the TWRP official again OR did you simply flash a second time the unlock.bin ?
And this way, do you still have the "infamous" WARNING screen about bootloader locked made in Google ?
Hey guys, I need help with this Asus Zenfone 2 Laser that:
Cannot boot to any OS (asus logo pops up, freezes, and then a blue screen flashes for a really short period, before it powers off, see video here.)
Can't download the unlock app to unlock bootloader
Can't access ADB
Cannot access Recovery mode
Can't "factory reset", apply update over ADB, etc.
Bootloader is locked
Can't flash custom recovery, boot TWRP, or really anything...
See fastboot reference below for more info
Code:
$ fastboot boot twrp-3.7.0_9-0-Z00T.img
Sending 'boot.img' (31066 KB) OKAY [ 0.987s]
Booting FAILED (remote: 'unlock device to use this command')
fastboot: error: Command failed
$ fastboot flash recovery twrp-3.7.0_9-0-Z00T.img
Sending 'recovery' (31066 KB) OKAY [ 0.987s]
Writing 'recovery' FAILED (remote: 'Permission denied, phone is protected')
fastboot: error: Command failed
$ fastboot flash boot boot.img # (Original boot.img from factory image)
Warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 17980722).
Sending 'boot' (17559 KB) OKAY [ 1.478s]
Writing 'boot' FAILED (remote: 'Permission denied, phone is protected')
fastboot: error: Command failed
$ fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
$ fastboot oem device-info
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.003s]
Finished. Total time: 0.003s
As someone who has only worked with Google Pixel phones in the past, I'm very frustrated for a few reasons.
Firstly, why the hell is the ONLY WAY to unlock a bootloader through an app that was released in such a clandestine, under-the-table way?
Second, why is the manufacturer gatekeeping the recovery files? The only way I was able to find the stock recovery.img is through a comment on a Reddit post (ironically posted by an ASUS Employee).
Third, I've been scouring the internet for many, many days trying to find any kind of emergency recovery method, but every single tutorial acts on the assumption that the bootloader is unlocked, and that boot.img, recovery.img, etc. can be flashed.
Enough about the frustration. Now let's talk about what I've tried so far.
I tried ASUS Flash Tool (Finding ADB drivers was a whole different fiasco for this device), and came up empty handed, as it doesn't detect the device when in fastboot mode.
I tried using fastboot to flash boot, recovery, system, fastboot, and dnx/ifwi, to no avail.
I tried booting into recovery via `fastboot reboot recovery`, `fastboot reboot-recovery`, `fastboot oem reboot-recovery`, and by holding Vol Down while booting up. They all give the same result, which is just an instant (<1 second) reboot. My best guess is that recovery.img is either missing or badly corrupt, so the bootloader just gives up and exits immediately.
Please help. I don't want an expensive paperweight sitting in my drawer just because of a bootloop that wasn't my fault (seriously this device just bootlooped itself one day, I didn't flash a custom rom, root or anything like that).
Any help is appreciated,
Thanks in advance
you can flash on locked bootloader in EDL mode. search in the forum, don't hesitate to ask for clarity on search results. I give you a starting point.
(don't read the whole thread, it will only confuse you)
https://forum.xda-developers.com/t/...image-dump-file-raw-bin.4543217/post-88139417
alecxs said:
you can flash on locked bootloader in EDL mode. search in the forum, don't hesitate to ask for clarity on search results. I give you a starting point.
(don't read the whole thread, it will only confuse you)
https://forum.xda-developers.com/t/...image-dump-file-raw-bin.4543217/post-88139417
Click to expand...
Click to collapse
Probably a dumb question, but how can I put my device into EDL mode?
I've tried many key combinations in conjunction with plugging it into the computer, and I've tried connecting it without a battery.
if nothing else works you need to figure out test points
https://forum.xda-developers.com/t/...ed-to-unlock-bootloader.4531349/post-87944673
you still have fastboot? try this for EDL mode.
Code:
fastboot oem enter-dload
Good news and bad news. Good news is: I was able to enter EDL mode.
Bad news is, apparently my entire partition scheme was messed up, and upon running "edl w gpt gptboth0.bin", fastboot no longer works.
I have tried flashing aboot using edl ("edl w aboot emmc_appsboot.mbn") and it's not working.
Not to mention that it is almost impossible to find the firmware file with all the factory files such as "emmc_appsboot.mbn". The place where I got my file seemed very sketchy and I'm not surprised if the reason it's not working is because it's the wrong file.
Once again, this is a result of ASUS gatekeeping their recovery files to service centers to drive up repair sales.
If anyone has a link, or would like to provide a donor file, it would be VERY much appreciated.
what is inside official download?
https://www.asus.com/supportonly/asus zenfone 2 laser (ze551kl)/helpdesk_bios
alecxs said:
what is inside official download?
https://www.asus.com/supportonly/asus zenfone 2 laser (ze551kl)/helpdesk_bios
Click to expand...
Click to collapse
So yes, I was able to get fastboot back. However, I am now facing another issue.
In order to get fastboot back, I had to run this command
Bash:
edl qfil rawprogram0.xml patch0.xml image_dir
This seemed fine at first, but now, running "edl printgpt" returns nothing. Somehow, the phone is able to boot to fastboot without any GPT partitions visible.
However, when I try to flash gpt_main0, or gpt_both0, the phone now becomes unbootable.
This means, if I try to create a partition table to flash recovery onto, appsboot (and by extension, fastboot) no longer works.
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (18115 KB) OKAY [ 0.581s]
Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
fastboot: error: Command failed
"partition table doesn't exist"
If I try to create the partition table, the phone refuses to boot...
OS were
sj-dan said:
So yes, I was able to get fastboot back. However, I am now facing another issue.
In order to get fastboot back, I had to run this command
Bash:
edl qfil rawprogram0.xml patch0.xml image_dir
This seemed fine at first, but now, running "edl printgpt" returns nothing. Somehow, the phone is able to boot to fastboot without any GPT partitions visible.
However, when I try to flash gpt_main0, or gpt_both0, the phone now becomes unbootable.
This means, if I try to create a partition table to flash recovery onto, appsboot (and by extension, fastboot) no longer works.
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (18115 KB) OKAY [ 0.581s]
Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
fastboot: error: Command failed
"partition table doesn't exist"
If I try to create the partition table, the phone refuses to boot...
Click to expand...
Click to collapse
So we're you able to find a fix in any way? I find myself in just about the same situation tho for different reasons. I have a radiant max 5g att device i moronicaly tried to download a gsi using the dsu updater, but forgot to unlock bootloader or even enable USB debugging before attempt. So OS system is crashing an saying 'device corrupted' on boot attempt. Recovery mode gets the same result. Was able to use the bugjaegar app to connect ad run the bootloader but every repair attempt is blocked by the fact the USB debugging isn't on. To make matters worse I accidentky hit boot fastbootd command instead of normal and whatever that did wiped out my ability to even connect with bootloader so I'm kind of stuck.
faisaliteb said:
Mod. edit: spammer gone. alecxs
I found many tutorials about fixing bootloops on the Nexus but they all seem to require an unlocked bootloader.
The bootloader on the device is locked. I can see the device in fastboot devices but I can't unlock it.
Any idea how to repair this? Can I somehow flash a factory image onto the device even though OEM unlock is disabled? There is no data on the device that would need to be preserved. I'm ideally looking for a Linux-based solution. more info... ***
Click to expand...
Click to collapse
Yeah man I've been looking at this problem for over a week now and can't find much online at all to help. Except for this EDLmode some devices can boot into, and apparently you can flash a locked system using this emergency download mode. I dunno still researching.