My bootloader is locked and my phone's rooted I also have TWRP, and Xposed installed, so now I was trying to Stock reset my phone but it failed unconditionally. No matter how much times I've flashed the stock it failed. The error was "Failed the device is locked" so I tried unlocking it with the ADB commands but what happens is the after the passing the commands the device boots to TWRP, I tried clearing the data, internal storage, cache, and Dalvik cache and then I checked the device info via adb it's still locked. I cannot even install the stock recovery because it throws the error "Device is locked". What do I do now?
MaddySayaji said:
My bootloader is locked and my phone's rooted I also have TWRP, and Xposed installed, so now I was trying to Stock reset my phone but it failed unconditionally. No matter how much times I've flashed the stock it failed. The error was "Failed the device is locked" so I tried unlocking it with the ADB commands but what happens is the after the passing the commands the device boots to TWRP, I tried clearing the data, internal storage, cache, and Dalvik cache and then I checked the device info via adb it's still locked. I cannot even install the stock recovery because it throws the error "Device is locked". What do I do now?
Click to expand...
Click to collapse
Hello buddy,
I had the same problem on my op2 device and tried all the troubleshooting steps you mentioned in your post.
I got it fixed after figuring out another way all thanks to devs.
Twrp has an option called adb sideload.
Copy the stock rom on your pc.
Now in the click on the adb sideload option in settings whilst your phone is connected to a pc.
Simultaneously press hold the shift key on your keyboard and click the right mouse button to open a command prompt.
First command would be adb devices.
Once your phone shows up in the list type in the second command I.e
Adb side load (your rom file name.zip)
It will take some time but will load the stock rom in your phone.
i tried this but it shows an error "Invalid zip file"
okay tried it again with proper zip file but did not work
SOLVED! i just flashed the recovery.img file from stock via TWRP and later unlocked my bootloader and flashed stock rom and relocked my bootloader.
thank you for your help
Related
I rooted my Nexus 7 months ago, but today I decide I wanted to try a new ROM and was wiping by data and system partitions for a fresh install of CM10, and I accidentally chose format all data. So my device is wiped except for TWRP.
Im in TWRP and when I run "adb devices" from my pc I get the following...015d2994a62bf403 sideload
but when I tried to use adb sideload, but i get the error "failed to write data 'protocol fault <no status>'
I'm screwed here...
You are not screwed, you still have a working bootloader (which I presume to be unlocked).
If the recovery keeps coming up in sideload mode after re-starting it, try soft-booting a recovery instead of booting it off the (previously flashed) recovery stored on the device
(with fastboot/bootloader showing on the N7)
Code:
fastboot boot recovery-image-file.img
This will certainly let you use a newer recovery as well if you want.
If that works and your drivers are correctly set up, you can push a file
(with soft-booted recovery running)
Code:
adb push My-Favorite-ROM.zip /sdcard/My-Favorite-ROM.zip
and then if that completes successfully, flash that ROM.
good luck
Hello All
I've rooted and installed TWRP recovery. And accidently wiped all partitions (system, data, caches...). Currently no OS installed.
Tried installing Cyanogen mods and also default ROMs via TWRP but getting error saying
====
Unknown command "screenshot"
E: Unable to mount /spare
====
Also tried flashing default ROMs...same error . No luck.
Tried wiping all partitions again.
connected to my linux lap
Device is connected and listed while running command "lsusb". (USB data connection working)
But not detecting under adb devices also not shown under fastboot mode. (So no luck to flash via PC).
All forums saying "check usb debugging" to show under adb devices. How can I ..if there is no ROM
Also TWRP is restarting after some time.
-------------------*******helppp******************************
Hi,
I have the same problem, few post below.
During my searching I found this post, but I get error during
fastboot erase spare
It hard to say what wrong is with this partition.
Maybe you will be have more luck
Elokwentnyemu said:
Hi,
I have the same problem, few post below.
During my searching I found this post, but I get error during
fastboot erase spare
It hard to say what wrong is with this partition.
Maybe you will be have more luck
Click to expand...
Click to collapse
In my case, the phone is not listed under fastboot devices But it's connected to computer in fastboot mode and we can see the device is listed when command lsusb is executed.
antoponline said:
In my case, the phone is not listed under fastboot devices But it's connected to computer in fastboot mode and we can see the device is listed when command lsusb is executed.
Click to expand...
Click to collapse
I checked on Manjaro and my phone is present under fastboot. Try reinstall drivers or use other PC to connect by fastboot.
so sad for both of you guys i've already encountered this before try this any of these.
- use adb sideload via TWRP using stock firmware UL-ASUS_T00F-WW-2.22.40.54-user.zip
- if you have a back up restore it, then boot to fastboot and flash the fastboot, boot and recovery of this firmware UL-ASUS_T00F-WW-2.22.40.54-user.zip then boot to recovery and side again using this firmware.
- try this link if it's work http://forum.xda-developers.com/android/development/hard-bricked-zenfone-unbrick-method-to-t3131911
sorry guys i forgot how i managed to solve this i will update this thread. just always remember use always this firmware UL-ASUS_T00F-WW-2.22.40.54-user.zip and back your current rom even if it's stock or custom this is most important. if you can access bootloader just do the flashing fastboot, boot and recovery this would be easy if you can access bootloader.
Ok, I'm going to start by explaining everything I did up to this point to eliminate any troubleshooting sugggestions i may have already done.
I rooted and installed recovery the same way everyone else did. After a couple of days, I tried to install a ROM but im assuming i was encrypted because i was stuck in a loop that would only boot me into TWRP. Did my research and took the necessary steps to get around that and decrypt and boot into the new ROM.. FINALLY!!! Only one problem, this rom doesn't have Super SU installed, Alright... so i download the proper Super SU build and put it on my Micro SD card and try to boot into TWRP to flash....
This is where the problem begins. I never get the prompt to authorize my PC from my phone to allow anything, and i never did each time i reset. I'm almost certain the adb on this rom is messed up, i've wiped about 4-5 times to re-enable usb debugging from scratch in order to adb or fastboot into recovery via command prompt, however when i try adb, i get that unauthorized error an there's no option on the LG V20 to revoke under developer settings. Fastboot i just get the same "waiting for device" message. Also keep in mind that i set it to photo mode, every mode that was available and nothing. Tried different USB Cords and did this on both my laptop and my PC at work
I've tried uninstalling and reinstalling all of the drivers, re-installed the latest version of adb and fastboot to my PC, that didn't work either. Tried deleting the adbkeys file in the .android folder and still nothing.
When i try to boot in recovery manually, i just get the wipe data option and when i click yes to everything, it actually wipes my data. I'm unable to reflash TWRP because I can't access ADB or Fastboot due to the unauthorized error.
Someone, PLEASE HELP!!!!
any luck?
ahq1216 said:
Ok, I'm going to start by explaining everything I did up to this point to eliminate any troubleshooting sugggestions i may have already done.
I rooted and installed recovery the same way everyone else did. After a couple of days, I tried to install a ROM but im assuming i was encrypted because i was stuck in a loop that would only boot me into TWRP. Did my research and took the necessary steps to get around that and decrypt and boot into the new ROM.. FINALLY!!! Only one problem, this rom doesn't have Super SU installed, Alright... so i download the proper Super SU build and put it on my Micro SD card and try to boot into TWRP to flash....
This is where the problem begins. I never get the prompt to authorize my PC from my phone to allow anything, and i never did each time i reset. I'm almost certain the adb on this rom is messed up, i've wiped about 4-5 times to re-enable usb debugging from scratch in order to adb or fastboot into recovery via command prompt, however when i try adb, i get that unauthorized error an there's no option on the LG V20 to revoke under developer settings. Fastboot i just get the same "waiting for device" message. Also keep in mind that i set it to photo mode, every mode that was available and nothing. Tried different USB Cords and did this on both my laptop and my PC at work
I've tried uninstalling and reinstalling all of the drivers, re-installed the latest version of adb and fastboot to my PC, that didn't work either. Tried deleting the adbkeys file in the .android folder and still nothing.
When i try to boot in recovery manually, i just get the wipe data option and when i click yes to everything, it actually wipes my data. I'm unable to reflash TWRP because I can't access ADB or Fastboot due to the unauthorized error.
Someone, PLEASE HELP!!!!
Click to expand...
Click to collapse
different route but im in the same boat. any luck?
I fixed this shortly after. Wanted to avoid returning to stock as. The only option was you and I was on 10d. I had to go back to stock but luckily the recovery method still works.
Hi guys,
Unable to boot after c*cking up a manual upgrade from B10 to B11 on my A2017G and would love your input. I feel like if I can just install TWRP again it should be an easy fix. Here's some specifics:
1. my phone is unlocked, rooted and running stock firmware.
2. I was trying to install stock recovery to install the B11 update. I did so but also tried to install another zip (B10 bootloader?) which I seem to have flashed wrong. Now just get the screen as shown on attachment and cannot boot.
3. Stock recovery seems to have been flashed and I can boot to this. From here I can boot to bootloader but can't seem to do anything from there.
4. I try update via ADB with the sideload command, but get the message "E:footer is wrong. E: Signature verification failed. Installation aborted".
5. I try to Update from SD as have the firmware zip file and TWRP on the root of my external SD card, but get the message "Couldn't Mound /sdcard, aborted."
6. The only time my phone shows as a connected device in ADB is when I try to sideload files. No other ADB code seems to work, only get the message "error: closed" on the terminal.
Assuming I've got all the firmware files (and full backups on my external SD) I feel like if I can just install TWRP again it should be an easy fix. So, any ideas on how I install TWRP given situation above?
Best,
Neil
nstirton said:
Hi guys,
Unable to boot after c*cking up a manual upgrade from B10 to B11 on my A2017G and would love your input. I feel like if I can just install TWRP again it should be an easy fix. Here's some specifics:
1. my phone is unlocked, rooted and running stock firmware.
2. I was trying to install stock recovery to install the B11 update. I did so but also tried to install another zip (B10 bootloader?) which I seem to have flashed wrong. Now just get the screen as shown on attachment and cannot boot.
3. Stock recovery seems to have been flashed and I can boot to this. From here I can boot to bootloader but can't seem to do anything from there.
4. I try update via ADB with the sideload command, but get the message "E:footer is wrong. E: Signature verification failed. Installation aborted".
5. I try to Update from SD as have the firmware zip file and TWRP on the root of my external SD card, but get the message "Couldn't Mound /sdcard, aborted."
6. The only time my phone shows as a connected device in ADB is when I try to sideload files. No other ADB code seems to work, only get the message "error: closed" on the terminal.
Assuming I've got all the firmware files (and full backups on my external SD) I feel like if I can just install TWRP again it should be an easy fix. So, any ideas on how I install TWRP given situation above?
Best,
Neil
Click to expand...
Click to collapse
Are you able to boot into EDL mode by typing ADB reboot edl ?
If so you can flash desired recovery with axon7tool
marcus.linkenbach said:
Are you able to boot into EDL mode by typing ADB reboot edl ?
If so you can flash desired recovery with axon7tool
Click to expand...
Click to collapse
Hi, thanks for your reply. Unfortunately not, just get the message "error: closed" in the terminal. Is there a button combination I could press in order to get into EDL?
nstirton said:
Hi, thanks for your reply. Unfortunately not, just get the message "error: closed" in the terminal. Is there a button combination I could press in order to get into EDL?
Click to expand...
Click to collapse
Try vol+ + vol- + power
it seems that the only time my device will show as connected in ADB is when I navigate through Recovery and select the "Apply Update from ADB" option. But even then, whilst it shows as connected, it only seems to allow the "sideload" command. Please see screenshot of Terminal. So at no other time will it show as a connected device.
Similarly, to have it show up in Device Manager, it'll only show when I switch the phone off, hold down Vol+ & Vol- and attached the power cable.
You are still on MM. So you are able to boot into bootloader.
adb reboot bootloader
fastboot devices
Now it should show your device as fastboot
If so you can now flash recovery with “fastboot flash recovery recovery.img“
marcus.linkenbach said:
You are still on MM. So you are able to boot into bootloader.
adb reboot bootloader
fastboot devices
Now it should show your device as fastboot
If so you can now flash recovery with “fastboot flash recovery recovery.img“
Click to expand...
Click to collapse
Thanks for your reply. Unfortunately as mentioned the only time my device shows as connected in Terminal is when I select "Update via ADB" whilst in recovery. Otherwise the device never shows as connected in adb.
So unfortunately fastboot doesn't seem to be an option for me.
Perhaps my drivers are out of whack but assuming what I've done to my phone hasn't changed that, it must be something PC - side.
nstirton said:
Thanks for your reply. Unfortunately as mentioned the only time my device shows as connected in Terminal is when I select "Update via ADB" whilst in recovery. Otherwise the device never shows as connected in adb.
So unfortunately fastboot doesn't seem to be an option for me.
Perhaps my drivers are out of whack but assuming what I've done to my phone hasn't changed that, it must be something PC - side.
Click to expand...
Click to collapse
But what if it shows your device as sideload? Can't you there reboot into fastboot?
No, it doesn't accept the command. Only one accepts is sideload. You can see from my screenshot a few posts back that the device is connected but shows different to how it normally would.
Breakthrough!
I seemed to follow the steps I've tried 100 times today and I now have TWRP installed again!
Thanks again to those who helped
After some problems (corrupted data partition and sticking in bootloop after reboot) on LineageOS 14.1 and PA 7.2.2, I decided to reflash the EMUI. That didn't work and through a series of my mistakes I have no recovery, no system and can't flash anything.
Fastboot gives me the "remote: command not allowed" error whatever I try to do except for "fastboot reboot" and "fastboot oem get-bootinfo" (which says the bootloader is unlocked). The fastboot screen says : Phone Unlocked, FRP Lock.
I can connect to adb after a few minutes of waiting at the "Your device is booting now..." screen that also shows 3 options. But I have nothing in /system/, which means /system/bin/sh doesn't exist so I can't get a shell into the phone. "adb ls" does work, though (don't know how).
I've also tried to push at least a shell into /system/ with "adb push", but it says that the partition is mounted read-only. Is there a way to mount it read-write without using "adb shell"?
Is my phone recoverable or is it bricked beyond repair? Any suggestions on how to repair it without changing the motherboard?
Thanks in advance!
CanIHelp said:
After some problems (corrupted data partition and sticking in bootloop after reboot) on LineageOS 14.1 and PA 7.2.2, I decided to reflash the EMUI. That didn't work and through a series of my mistakes I have no recovery, no system and can't flash anything.
Fastboot gives me the "remote: command not allowed" error whatever I try to do except for "fastboot reboot" and "fastboot oem get-bootinfo" (which says the bootloader is unlocked). The fastboot screen says : Phone Unlocked, FRP Lock.
I can connect to adb after a few minutes of waiting at the "Your device is booting now..." screen that also shows 3 options. But I have nothing in /system/, which means /system/bin/sh doesn't exist so I can't get a shell into the phone. "adb ls" does work, though (don't know how).
I've also tried to push at least a shell into /system/ with "adb push", but it says that the partition is mounted read-only. Is there a way to mount it read-write without using "adb shell"?
Is my phone recoverable or is it bricked beyond repair? Any suggestions on how to repair it without changing the motherboard?
Thanks in advance!
Click to expand...
Click to collapse
https://forum.xda-developers.com/huawei-p9lite/how-to/unified-help-thread-huawei-p9-lite-t3649152
Post 5. Unbricking EMUI 5. Don't take for granted it will work, but considering FRP is locked, this is the only way not needing a unlocked bootloader.
Doesn't work. It's still stuck at the "Your device is booting now..." under the vmall link screen.
Isn't the 3-button method counting on the original recovery being in the recovery partition?
I only have the second recovery working (that eRecovery which only lets you "download and install the latest recovery and system"...and doesn't do anything).
Is there a way to override the frp lock? I saw a couple of tools online claiming to do that, but none worked. I haven't tried DC-Unlocker. If I'm gonna pay for it, might as well go to a service
Dload method uses the secondary recovery, It should be there if you press all three buttons.
From what i have heard, DC-Unlocker works.
Plug your phone on computer.
You see yellow advice? Appears automatically.
Juste after this advice, tip "fastboot reboot bootloader".
After, unlock your bootloader again "fastboot oem unlock YOUR_OEM_CODE"
Ok now shutdown and hold buttons for boot to TWRP recovery, if not appears, flash it on "fastboot flash recovery recovery.img"
Warning command not allowed on fastboot is 90% time du at bootloader unlocked (even if he says it's good)
dariomrk said:
Dload method uses the secondary recovery, It should be there if you press all three buttons.
From what i have heard, DC-Unlocker works.
Click to expand...
Click to collapse
It did boot in the secondary recovery (had to hold onto the 3 button for 3-4 minutes continuously). But it said that "Software install failed/ Incompatibility with current version. Please download the correct update package."
I'm now trying the B160 image in that thread. Wish me luck!
EDIT: It worked. The B160 image flashed using the three button method. I'm now at the setup screen. And the keyboard is there. (Also had the problem where I'd only have the voice input keyboard)
Thank you very much!
CanIHelp said:
It did boot in the secondary recovery (had to hold onto the 3 button for 3-4 minutes continuously). But it said that "Software install failed/ Incompatibility with current version. Please download the correct update package."
I'm now trying the B160 image in that thread. Wish me luck!
EDIT: It worked. The B160 image flashed using the three button method. I'm now at the setup screen. And the keyboard is there. (Also had the problem where I'd only have the voice input keyboard)
Thank you very much!
Click to expand...
Click to collapse
No problem mate, nice to hear you did it without problems.