Related
This guide was made before Kingroot was able to root the official update. But thanks to @oskar and @TheDerekHarper on XDA and to @josephwv on Android forums it is now comfirmed that Kingroot will root the official update. But first you must still follow steps #1 through #6 so Kingroot can root your device.
Now before Kingroot was able to root the update I figured out how to root the official update and it is not all to complicated. The following guide will walk you through the root process. But I am not responsible for anything that happens to your devices by using this guide as you are responsible for your device.
What you need:
1. A computer running Linux or Windows with adb and fastboot installed. (I used Ubuntu)
2. If you are using Windows you need all the drivers for your device installed. Linux users will not have to worry about this.
3. A functioning USB cable for your device.
4. Battery charged at least 50% just for safety.
5. The TWRP revovery.img, this is the same TWRP recovery we already have for the LG G Stylo I have just renamed it to recovery.img to make it easier to type the name in while typing fastboot commands.
6. The SuperSU-v2.65-20151226141550.zip by Chainfire. (All credit to Chainfire for this awesome zip.)
How to root your device:
1. I suggest you first go to Settings/General/About Phone/Software info and tap on the "Build number" until it says"You are now a developer". Then back out of until you are in Settings/General and go to "Developer options" and turn "Enable OEM unlock" on. This is to allow TWRP recovery to be able to boot. Also turn on "USB debugging" while you are there.
2. Download the SuperSU-v2.65-20151226141550.zip to your device. You need to move the zip file from your Downloads folder to somewhere on your external SD card as it will not be deleted from there when you use the "fastboot oem unlock" command in step #6.
3. Download the recovery.img to your computer. If you do not have adb and fastboot setup globally for linux or in your path for windows you need to move the recovery.img to the directory your adb and fastboot is in and open a terminal or command line (depending on your OS) in that directory or cd to that directory. If you do have adb and fastboot globally or in your path you can just open a terminal or command line in the directory you have the recovery.img or cd to the directory you have the recovery.img.
4. Once you have the terminal or command line open run the command "adb devices" to make sure your devices is detected by adb. You may get a toast pop up on your device asking if you to "Allow usb debugging". Except this as this is the RSA key you need to allow your computer to communicate with your device via adb. You should see something like "LGH631dffacad9 device" in your terminal or command line. If you see "unauthorized" instead of "device" you have not excepted the RSA key.
5.Now type the following command in your terminal or command line. Type "adb reboot bootloader". This will reboot your device to fastboot mode. Once in fastboot mode use the "fastboot devices" to make sure your device is recognized by fastboot. You should see something like "dffacad9 fastboot". If you are in Linux and get a error message you may have to use "sudo fastboot devices" for fastboot to work. (If you are using Windows and are having trouble with fastboot recognizing your device you need to install the device drivers. If it still does not work install the drivers again with your device connected to your computer in fastboot mode.)
6. To fully unlock your bootloader you have to use the command "fastboot oem unlock". You have to do this or this root method will not work. But be warned that if you do use this command it will factory reset your device. Plus you will get a line of text saying the bootloader is unlocked on the splash screen when you boot your device.
6-1: If you are wanting to use Kingroot to root your device you can reboot your device now. Open the Kingroot app and let it root your device and then use Flashify, Rashr, or a similar app to flash the recovery. Then boot to recovery and flash the SuperSU.zip in recovery and it will remove Kingroot and have SuperSU installed on your device.
7. Now you can do this two ways if you do not want to keep the stock recovery you can use the command "fastboot flash recovery.img" to install the recovery and then use the command "fastboot reboot recovery" to boot to the TWRP recovery. (If this command gives you issue like it seems to be for many then just use the the following method and then use Flashify or Rashr app to install TWRP after you are done rooting.) If you want to keep the stock recovery you can use the command "fastboot boot recovery.img" to boot to the TWRP recovery.
8. Once you are booted to the TWRP recovery you should make a full backup first so you have a backup to restore to in case things go bad. After you make a backup then select install and then find the SuperSU-v2.65-20151226141550.zip and install it. Once it is installed reboot your device to system. If TWRP gives you a warning about the su binaries missing and asks if you want to install thee su binaries before you reboot select no or it will interfere with the rooting process of the SuperSU.zip. When your device reboots it will boot to the LG splash screen and then reboot again. But then it will boot to the OS but it will take a minute. Make sure you let your device reboot all the way to the lockscreen or home screen depending on if you have a lockscreen enabled or not. You should be fully rooted after this, enjoy.
Resserved in case needed later.
Thank you.
target reported max download size of 268435456 bytes
sending 'recovery' (11300 KB)...
OKAY [ 0.359s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.359s
ok so i know this is 100% my fault for not reading, but why would you even include step 6? it wipes everything including the supersu.zip. the files i'm pissed about, but i can get over. mostly music plus some ****ty pictures. contacts can text me. but the main thing is i had to restart my phone, get it started up and everything, then put the super su.zip back onto the phone. just a tedious task.
Can I use this guide with my G4 Stylus (H635)?
wtf... i get this same error
C:\adb>fastboot flash recovery v10.img
target reported max download size of 268435456 bytes
sending 'recovery' (11230 KB)...
OKAY [ 0.390s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.390s
I've tried multiple versions of the TWRP for the g stylo on adroidforum and none of it flashes with the fastboot flash recovery .....img option. Every single one fails. Please tell me how you flashed the recovery... Also I cant run it through Flashify because my SuperSU says no binary is installed... I'm completely lost at this point
aaron2z said:
wtf... i get this same error
C:\adb>fastboot flash recovery v10.img
target reported max download size of 268435456 bytes
sending 'recovery' (11230 KB)...
OKAY [ 0.390s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.390s
I've tried multiple versions of the TWRP for the g stylo on adroidforum and none of it flashes with the fastboot flash recovery .....img option. Every single one fails. Please tell me how you flashed the recovery... Also I cant run it through Flashify because my SuperSU says no binary is installed... I'm completely lost at this point
Click to expand...
Click to collapse
Someone mentioned using the Kingroot app and I gotta admit, I was skepticle at first but after testing. I can confirm it works.
Just go go KingRoot.net, download their apk, install and run the root program. Igll work out of the box after, sadly I couldn't get the above method to work either with super su.
aaron2z said:
wtf... i get this same error
C:\adb>fastboot flash recovery v10.img
target reported max download size of 268435456 bytes
sending 'recovery' (11230 KB)...
OKAY [ 0.390s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.390s
I've tried multiple versions of the TWRP for the g stylo on adroidforum and none of it flashes with the fastboot flash recovery .....img option. Every single one fails. Please tell me how you flashed the recovery... Also I cant run it through Flashify because my SuperSU says no binary is installed... I'm completely lost at this point
Click to expand...
Click to collapse
do the fastboot boot recovery.img so it boots up twrp then flash the supersu zip then boot your phone you should be rooted then flash twrp using flashify
I was getting the same error, ( in step 7 don't flash the recovery )
just use "fastboot boot recovery.img" and it will boot to TWRP without installing it
you can then install SU, ( note ) when you exit or re boot from TWRP it will say SU in not installed do you want to install it, I did the first time and it seemed to hose up, so I did everything over and the second time selected no to re install.
once booted I used flashify to install the TWRP img, and I am able to boot to recovery using Quickboot apk
on a side note I have SU installed, I can use root explorer and other apps that ask for SU access, but Titanium backup
doesn't seem to uninstall apps anymore, they seem to re install after a reboot
Hope this helps yall's
aaron2z said:
wtf... i get this same error
C:\adb>fastboot flash recovery v10.img
target reported max download size of 268435456 bytes
sending 'recovery' (11230 KB)...
OKAY [ 0.390s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.390s
I've tried multiple versions of the TWRP for the g stylo on adroidforum and none of it flashes with the fastboot flash recovery .....img option. Every single one fails. Please tell me how you flashed the recovery... Also I cant run it through Flashify because my SuperSU says no binary is installed... I'm completely lost at this point
Click to expand...
Click to collapse
TheDerekHarper said:
Someone mentioned using the Kingroot app and I gotta admit, I was skepticle at first but after testing. I can confirm it works.
Just go go KingRoot.net, download their apk, install and run the root program. Igll work out of the box after, sadly I couldn't get the above method to work either with super su.
Click to expand...
Click to collapse
I gotta be honest... I'm pretty skeptical to try it. I've read of everyone having either a softbrick boot loop or the root just not staying after reboot. Yours worked for H631 T-mobile 6.0 and stayed? If you confirm T-mobile variant and 6.0 I'll try it. There's a lot of headache with this method for me (not saying it doesn't work). I bricked my phone trying to get the binary files for SU by trying to reroot. But unbricked it with LG Flash Tools and a stock kdz. So I don't want to brick it again twenty minutes later lol
aaron2z said:
I gotta be honest... I'm pretty skeptical to try it. I've read of everyone having either a softbrick boot loop or the root just not staying after reboot. Yours worked for H631 T-mobile 6.0 and stayed? If you confirm T-mobile variant and 6.0 I'll try it. There's a lot of headache with this method for me (not saying it doesn't work). I bricked my phone trying to get the binary files for SU by trying to reroot. But unbricked it with LG Flash Tools and a stock kdz. So I don't want to brick it again twenty minutes later lol
Click to expand...
Click to collapse
Made a tutorial on how to get the marshmallow update (i.e. rom i've used.)
And then afterwards i downloaded Minimal ADB & Fastboot, OEM Unlocked the device (for safety) and downloaded the Kingroot Apk.
Installed it, and just allowed the program to root. It was pretty simple, haven't had any issues (i've even disabled OEM Unlock from the phone & USB Debugging.)
Hell, even adoptable storage is enabled for my phone too (but that's another tutorial from somewhere else.)
I do plan to make a root video, just so someone could see it and grab their opinion.
To be clear: I'm using a metroPCS LG Stylo. Also, only time the phone had issues was when i factory reset it to get rid of root. (didn't work)
so i had to follow the steps from the above tutorial to reflash the stock rom.
jothe1 said:
do the fastboot boot recovery.img so it boots up twrp then flash the supersu zip then boot your phone you should be rooted then flash twrp using flashify
Click to expand...
Click to collapse
well this did it, the root actually worked.
I got a permanent root from the procedure listed on page one of this thread. The only thing I did differently was, when booted into TWRP and you try to re boot the system you will get the question if you want TWRP to install root. If you do allow TWRP to install root, you wont get root. At this point select the option to just reboot the phone. The LG Logo will appear twice before it fully boots. When the device is fully up, you will have root.
Foamp said:
ok so i know this is 100% my fault for not reading, but why would you even include step 6? it wipes everything including the supersu.zip. the files i'm pissed about, but i can get over. mostly music plus some ****ty pictures. contacts can text me. but the main thing is i had to restart my phone, get it started up and everything, then put the super su.zip back onto the phone. just a tedious task.
Click to expand...
Click to collapse
My apologies as I made a typo in the guide. The correct command is "fastboot flash recovery recovery.img" to flash the recovery. I will fix this along with another rework about putting the SusperSU.zip only on your SD card.
oskar5510 said:
Can I use this guide with my G4 Stylus (H635)?
Click to expand...
Click to collapse
I do not know if you can use it or not as I do not have that device. But you can try it bit if your device does not boot to fastboot mode when you issue the adb reboot bootloader command then your device's bootloader is not unlockable and this root method will not work for you. But from the posts in this thread point out that Kingroot now works on the 6.0 update so you can also try Kingroot to see if it willroot your device.
aaron2z said:
wtf... i get this same error
C:\adb>fastboot flash recovery v10.img
target reported max download size of 268435456 bytes
sending 'recovery' (11230 KB)...
OKAY [ 0.390s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.390s
I've tried multiple versions of the TWRP for the g stylo on adroidforum and none of it flashes with the fastboot flash recovery .....img option. Every single one fails. Please tell me how you flashed the recovery... Also I cant run it through Flashify because my SuperSU says no binary is installed... I'm completely lost at this point
Click to expand...
Click to collapse
Again sorry as this is fully my fault for making the typo on the fastboot command to flash recovery. I am fixing it as soon as I am done with this post.
TheDerekHarper said:
Someone mentioned using the Kingroot app and I gotta admit, I was skepticle at first but after testing. I can confirm it works.
Just go go KingRoot.net, download their apk, install and run the root program. Igll work out of the box after, sadly I couldn't get the above method to work either with super su.
Click to expand...
Click to collapse
Thank you for posting this.
jothe1 said:
do the fastboot boot recovery.img so it boots up twrp then flash the supersu zip then boot your phone you should be rooted then flash twrp using flashify
Click to expand...
Click to collapse
Yes this is how I did it when I rooted my device. I will edit the guide some to point this out.
AgainstTheFlow said:
I got a permanent root from the procedure listed on page one of this thread. The only thing I did differently was, when booted into TWRP and you try to re boot the system you will get the question if you want TWRP to install root. If you do allow TWRP to install root, you wont get root. At this point select the option to just reboot the phone. The LG Logo will appear twice before it fully boots. When the device is fully up, you will have root.
Click to expand...
Click to collapse
Thank you for posting this so others can see this does work.
infektedpc said:
target reported max download size of 268435456 bytes
sending 'recovery' (11300 KB)...
OKAY [ 0.359s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.359s
Click to expand...
Click to collapse
I also apologize to you for my mistake. It will be corrected shortly.
TheDerekHarper said:
Made a tutorial on how to get the marshmallow update (i.e. rom i've used.)
And then afterwards i downloaded Minimal ADB & Fastboot, OEM Unlocked the device (for safety) and downloaded the Kingroot Apk.
Installed it, and just allowed the program to root. It was pretty simple, haven't had any issues (i've even disabled OEM Unlock from the phone & USB Debugging.)
Hell, even adoptable storage is enabled for my phone too (but that's another tutorial from somewhere else.)
I do plan to make a root video, just so someone could see it and grab their opinion.
To be clear: I'm using a metroPCS LG Stylo. Also, only time the phone had issues was when i factory reset it to get rid of root. (didn't work)
so i had to follow the steps from the above tutorial to reflash the stock rom.
Click to expand...
Click to collapse
Thanks for posting this I will add this to the post as another option to root seeing as it is comfirmed. I will give credit to you and @oskar for this info.
Is there anyway to do this without wiping your data from 'fastboot oem unlock'? My bootloader keeps saying locked in fastboot mode even though I checked Enable OEM Unlock in settings. It won't let me boot the recovery.img because it's locked.
supersonic125 said:
Is there anyway to do this without wiping your data from 'fastboot oem unlock'? My bootloader keeps saying locked in fastboot mode even though I checked Enable OEM Unlock in settings. It won't let me boot the recovery.img because it's locked.
Click to expand...
Click to collapse
Are you trying to use the fastboot boot recovery.img command?
Yeah, if I try to flash instead of booting I get:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (11300 KB)...
OKAY [ 0.380s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.401s
supersonic125 said:
Yeah, if I try to flash instead of booting I get:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (11300 KB)...
OKAY [ 0.380s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.401s
Click to expand...
Click to collapse
Hmmm looks like maybe fully unlocking the bootloader enables all fastboot commands. You can try downloading and installing Kingroot and root with it as the posts here comfirm it will root the update now. Or just u lock the bootloaderb but your device will be reset if you do.
T-Macgnolia said:
Hmmm looks like maybe fully unlocking the bootloader enables all fastboot commands. You can try downloading and installing Kingroot and root with it as the posts here comfirm it will root the update now. Or just u lock the bootloaderb but your device will be reset if you do.
Click to expand...
Click to collapse
What if we just enable oem unlock in both the system and the bootloader then use adb to push the recovery, superuser, and busybox to the system. King Root caused too many system instabilities, it had injected itself as a system app and after unrooting and uninstalling after a reboot I was left with a soft brick due to a secure boot error 1003. A stock 5.1.1 kdz and the lg flash tool was able to bring my Stylo back to life.
It could all be done by running a simple batch file bundled with everything we need for our device. Linux would probably be the better option but it could work the same in windows.
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.
Hello I'm trying to flash stock ROM via adb, specifically cust.img, boot.img, system.img, Because I've bricked my phone and it stuck on huawei logo, but when i try to flash, i got the following error "FAILED (remote: Command not allowed)"
Code:
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (304183 KB)...
OKAY [195.875s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 195.899s
c:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21690 KB)...
OKAY [ 13.671s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 13.694s
c:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [314.622s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 314.665s
Please how I can unbrick my phone and reinstall the firmware
Obs. My bootloader is unlocked and I'm using TWRP recovery
Is your phone really shows Unlocked in red color when it's in fastboot mode?
Was your phone rooted, if yes, with which method?
You should try doing:
fastboot erase cache
fastboot erase userdata
These commands perform the same thing as Factory Reset do.
If it's not working, try to do the "dload" method with your original firmware your phone was shipped with.
Create a folder, called "dload" in your sdcard root, put the UPDATE.APP file of the firmware in it, and without connecting it to PC, press Vol + and Vol - and Power button until it starts flashing the firmware, and see what happens.
In later days, we've got a lot of troubleshooting topic opened up with your problem, the users cannot flash even with unlocked bootloader, and yet, there's no real solution to them.
I suggest that you use Windows 10? If I'm right sometimes this version of Windows cannot be used to flash via adb
I recommend you to use Windows 8.1 or 7 . My best way is of course using Linux
daviddosa said:
Is your phone really shows Unlocked in red color when it's in fastboot mode?
Was your phone rooted, if yes, with which method?
You should try doing:
fastboot erase cache
fastboot erase userdata
These commands perform the same thing as Factory Reset do.
If it's not working, try to do the "dload" method with your original firmware your phone was shipped with.
Create a folder, called "dload" in your sdcard root, put the UPDATE.APP file of the firmware in it, and without connecting it to PC, press Vol + and Vol - and Power button until it starts flashing the firmware, and see what happens..
Click to expand...
Click to collapse
Yes, it shows PHONE unlocked in red name, and I've made the root using an app called kingroot
I've tried to erase cache and userdata using adb but I can't, still got the same error "FAILED (remote: Command not allowed)"
I can't make dload method because I don't have stock recovery, and I can't flash the stock recovery using adb because its keep saying "FAILED (remote: Command not allowed)".
I don't know what to do
sokkoban said:
I suggest that you use Windows 10? If I'm right sometimes this version of Windows cannot be used to flash via adb
I recommend you to use Windows 8.1 or 7 . My best way is of course using Linux
Click to expand...
Click to collapse
I'm using windows 7 is this moment, maybe I try to flash using Linux later
Seems like all the guys with the same problem used KingRoot to root...that is the common thing amongst all.
I dont't think you need the stock recovery to update via the "dload" method, but I'm not sure.
If you don't have your original firmware's UPDATE.APP yet, download it, as well as the Huawei Update Extractor.
Load your file into the program, select ONLY BOOT.IMG, CUST.IMG(if it has one), SYSTEM.IMG and RECOVERY.IMG(optional, if selected, restores original recovery) right click on one, and press Create Flashable Zip.
Copy this to your sdcard and try to flash it.
I did not thest this above method, and don't know it the created flashable zip is really flashable, but I'm running out of possible solutions slowly.
Let us know what happens.
daviddosa said:
Seems like all the guys with the same problem used KingRoot to root...that is the common thing amongst all.
I dont't think you need the stock recovery to update via the "dload" method, but I'm not sure.
If you don't have your original firmware's UPDATE.APP yet, download it, as well as the Huawei Update Extractor.
Load your file into the program, select ONLY BOOT.IMG, CUST.IMG(if it has one), SYSTEM.IMG and RECOVERY.IMG(optional, if selected, restores original recovery) right click on one, and press Create Flashable Zip.
Copy this to your sdcard and try to flash it.
I did not thest this above method, and don't know it the created flashable zip is really flashable, but I'm running out of possible solutions slowly.
Let us know what happens.
Click to expand...
Click to collapse
So I tried to create a flashable zip using the Huawei Update Extractor however, was not possible, it's showing the following message "no suitable files selected. Check profiles.xml"
I've tried also creating flashable zip manually and flash it using TWRP, but TWRP reboot every time I try to flash theses files, that's why I think dload method work only with stock recovery
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
sokkoban said:
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
Click to expand...
Click to collapse
Thanks for the help but this method didn't work, everytime I try to flash the files, I got the same error "FAILED (remote: Command not allowed)” I don't know what is happening my bootloader is unlocked, why I can't flash the files with adb
Code:
target max-download-size: 450MB
sending 'boot' (21690 KB)...
OKAY [ 13.912s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 13.919s
target max-download-size: 450MB
sending 'recovery' (34264 KB)...
OKAY [ 21.963s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 21.985s
target max-download-size: 450MB
sending 'cust' (304183 KB)...
OKAY [191.580s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 191.603s
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [366.120s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 366.144s
ROM flashed , if all went well
You must be restarted.
If you leave the recovery to hard reset and restart the phone
Created by sokoban. Thank you for using my release
rebooting...
finished. total time: 0.054s
Pressione qualquer tecla para continuar. . .
This is very strange. May be you really have locked bootloader
Post answer from this command in fastboot mode:
Code:
fastboot oem get-bootinfo
sokkoban said:
This is very strange. May be you really have locked bootloader
Post answer from this command in fastboot mode:
Code:
fastboot oem get-bootinfo
Click to expand...
Click to collapse
This was the result
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
As you can see the ADB says that the bootloader is unlocked, but I'm still having trouble
Same issue with Huawei G6-U10
I'm having the same problem with Huawei Ascend G6-U10
Currently running on ROM b146, since it has some issues I was trying to downgrade or upgrade ( there is a b330 out).
I'm not an expert.
This morning I've unlocked the boot loader and then tried to flash a couple of different ROMs and I always get the same error message:
c:\adb>fastboot flash BOOT ./G6-U10verb330/boot.img
target reported max download size of 536870912 bytes
sending 'BOOT' (9696 KB)...
OKAY [ 0.310s]
writing 'BOOT'...
FAILED (remote: Command not allowed)
finished. total time: 0.321s
c:\adb>fastboot oem get-bootinfo
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
I'm guessing this is not a G6-U10 specific issue so if anyone can give any hint it'll be very appreciated.
Thanks.
I have the same problem with a honor 4x.
Rooted with kingroot. We haven't writing permission in /system. That's why we can't install the recovery. If you try to install superSU and update the binary I guess you get an error.
Now the question is: how we can do to make writeble /system with fast boot?
"mount -o rw,remount -t ext3 /dev/block/xxxxxxxxx /system" in terminal doesn't work...
Similar thing happened to me. Even if command for showing unlocked bootloader said it was unlocked that was false because I used Kingroot previously. Only thing that helped was to unlock the bootloader through fastboot again. Then it was really unlocked and I could flash recovery (in my case TWRP) which before I was unable to.
Diego Sousa said:
This was the result
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
As you can see the ADB says that the bootloader is unlocked, but I'm still having trouble
Click to expand...
Click to collapse
Have you tried it with linux yet?
And have you used the Update.APP and dload method?
Maybe a driver problem? Have administrator rights? And debug mode on?
Try to connect your phone (power on) to the pc and wait to be recognized. In cmd type this:
Code:
adb devices
It has to show you your serial number right? If doesn't your device is not being recognized by adb.
Next type:
Code:
adb reboot-bootloader
This will restart your phone into fastboot and now you can type "fastboot devices" like first command and it has to show you your serial number again.
Try rebooting into bl with this, not by plugin in the phone, and install the rom again
Huawei P8 Lite
Hello I have a problem with my phone. I do not know how to hell I fix it.
It says error cannot load system.img but still I can install boot.img and others.
I¨d tryed that "dload" with update.app doesnt work.
phone is Huawei P8 Lite
this is my first time here
Have you tried install it in twrp? You don't have a twrp backup of stock rom?
In this case if you go in the Huawei eRecovery you can restore stock rom and twrp will be overwrited downloading the last rom , i tried it with my p8 lite 2017 .
Tuki2 said:
Hello I have a problem with my phone. I do not know how to hell I fix it.
It says error cannot load system.img but still I can install boot.img and others.
I¨d tryed that "dload" with update.app doesnt work.
phone is Huawei P8 Lite
this is my first time here
Click to expand...
Click to collapse
What are you using to go into fastboot mode? Is it ADB from Android SDK?? It turns out that using ADB from Android SDK lets you flash small files but not large files... I suggest you try flashing the file through Minimal ADB & Fastboot
sokkoban said:
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
Click to expand...
Click to collapse
i have the same issue as well, but just with Cust.img
Ahh, hind sight is a wonderful thing.
After trying to use kingroot to get root access, it failed. And a few days later after rebooting.
I'm now stuck at bootup with Start Up Failed.
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
I've now tried lot's of different things, over the last few hours.
RSDLite (show device brings no thing up)
Unlock bootloader (request key, but error regarding OEM unlock not being set - no access to now set it LOL)
Downloaded stock X_Play_UK_Retail_XT1562_LPD23.118-10_CFC.xml.zip, and tried using various guides on fastboot but keep getting remote failed.
I'm on stock recovery (obviously still locked).
Any thoughts, or hope from anyone?
Obviously, not sure what support Motorola would provide for what is essentially my own fault?
Have you tried manually flashing each bit of the stock firmware/image. That might help. There's a good guide here which I followed to unbrick my device. Just follow the instructions http://theunlockr.com/2015/09/22/how-to-unroot-the-motorola-moto-x-play/
Or try this one.
http://forum.xda-developers.com/showthread.php?t=2499926
Tried the first fastboot oem lock begin but get ... (althought my phone is locked already)
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.063s
So stepping to next command, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.166s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.078s
sharebubbles said:
Tried the first fastboot oem lock begin but get ... (althought my phone is locked already)
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.063s
So stepping to next command, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.166s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.078s
Click to expand...
Click to collapse
I think you need to unlock the bootloader and then start with the 'fastboot oem lock begin' command. You can't flash a system image with a locked bootloader. Let me know how it goes!
DTLblaze said:
I think you need to unlock the bootloader and then start with the 'fastboot oem lock begin' command. You can't flash a system image with a locked bootloader. Let me know how it goes!
Click to expand...
Click to collapse
I run the unlock command, with my unique key but I get ..
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.013s
And since I can't get into the phone, I can't therefore check the "allow OEM unclock"
Have you tried any erase data commands or reset commands? Perhaps you could reset the phone so kingroot is un-installed and then try to turn on the phone. Short of that I'm stuck for ideas really, accept booting into 'fastboot and then erasing all data and factory reset in there. Let me know.
DTLblaze said:
Have you tried any erase data commands or reset commands? Perhaps you could reset the phone so kingroot is un-installed and then try to turn on the phone. Short of that I'm stuck for ideas really, accept booting into 'fastboot and then erasing all data and factory reset in there. Let me know.
Click to expand...
Click to collapse
I tried the wipe data/factory reset and wipe cache partition from the stock recovery.
And if I try from fastboot:-
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.196s]
finished. total time: 0.198s
And then a fastboot reboot.
Back to the now standard "start up failed"
And the
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from normal boot mode
Sickaxis79 said:
Or try this one.
http://forum.xda-developers.com/showthread.php?t=2499926
Click to expand...
Click to collapse
Have downloaded, and tried that - but the crux appears to be the fact that my bootloader is locked and I can't access the OEM checkbox. And therefore the tool itself can't unlock or equally install TWRP.
Unless I'm missing something in it's usage.
sharebubbles said:
I tried the wipe data/factory reset and wipe cache partition from the stock recovery.
And if I try from fastboot:-
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.196s]
finished. total time: 0.198s
And then a fastboot reboot.
Back to the now standard "start up failed"
And the
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from normal boot mode
Click to expand...
Click to collapse
That really does sound like you bricked the device. If you where on lollipop software you wouldn't have the issue with check bootloader OEM unlock. If it was me I would either contact Motorola or go to a repair shop and have a motd experienced person take a look at it.
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
sharebubbles said:
Have downloaded, and tried that - but the crux appears to be the fact that my bootloader is locked and I can't access the OEM checkbox. And therefore the tool itself can't unlock or equally install TWRP.
Unless I'm missing something in it's usage.
Click to expand...
Click to collapse
Strange. This is the tool I used to unlock my bootloader.
drmuruga said:
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
Click to expand...
Click to collapse
I've ben used the latest rom so far why trying to flash (and failing) when I look at recovery I have a LPD23.118-10 number that matches to an earlier 5.1.1 rom (I had been upgraded to 6.0.1 via OTA updates) - do I therefore take that LPD ID to mean that I should actually use the 5.1.1 rom - I'm in the UK, so I'm assuming I'd use the UK one rather than Europe (I'm looking at roms on https://github.com/motoxplay/stock).
Thanks
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
sharebubbles said:
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
Click to expand...
Click to collapse
And also never try kingroot.
sharebubbles said:
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
Click to expand...
Click to collapse
Most in the threads suggesting using rsdlite or manual flash/root and you decided to use kingroot,haha.
Welcome back.
Guys I have been searching EVERYWHERE on how to unbrick my moto x play, I used kingroot and it bricked, been a week and I TRIED everything. CAN ANYONE HELP PLEASE!!!!!!
---------- Post added at 05:26 AM ---------- Previous post was at 05:14 AM ----------
Guys I have been searching EVERYWHERE on how to unbrick my moto x play, I used kingroot and it bricked, been a week and I TRIED everything. CAN ANYONE HELP PLEASE!!!!!!
Tried restoring it, deleted everything and the phone is still on bootloader (LOCKED) and i dont even know how to fix it, I know nothing on how to root, friend suggested it, downloaded it, installed it, didnt work and then i restarted my phone and now its stuck on bootloader screen and the screen has the message "Start up failed: your device didnt start up successfully. Use the software repair assisstant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant." <- Downloaded it, tried it and it was stuck on 6% on repairing, left it over night and it was still on 6%.
ALSO under the message "AP Fastboot Flash Mode(Secure) is there)
Hai same problem for my moto x play ple.......s help contact.7708892303(WhatsApp no.)
pravin kkr said:
Hai same problem for my moto x play ple.......s help contact.7708892303(WhatsApp no.)
Click to expand...
Click to collapse
Download and flash this firmware
https://mega.nz/#!H5YlDCrD!T8tAAW7nHVS-erizRiqg5-Yp_p23hKParMjjHD4diQA credits @kumeipark
Use RSD lite to flash the firmware
http://rsdlite.com/rsd-lite-download/
Moto drivers
http://motorola-mobility-en-in.custhelp.com/app/answers/detail/a_id/88481
If you have problems installing device drivers using Windows 8.1 or Windows 10 follow this guide
https://www.youtube.com/watch?v=gmw86KplqmU
And don't post your contact no. in public forums for everyone to see.
what is the decryption key for the mega link
drmuruga said:
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
Click to expand...
Click to collapse
provide the decryption key
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.