My Hero come from service center clean and updated to latest RUU so i trying to get custom bootloader.
First i try to downgrade Hero to 2.73.405. But on my computer with Win7 fails with error 171. Then i tried on friend machine with Win XP and there i got error 140. I tried RUU from xda ftp and one from HTC and after this fails i tried other RUU from xda ftp. (i created and have gold card)
After that i try different approach. I rooted Hero using one click apk and then use latest flashrec. Flashrec gives me error "Flash FAILED: Could not run command."
After that i tray this:
Code:
C:\and\platform-tools>adb shell reboot bootloader
C:\and\platform-tools>fastboot boot rec.img
and i got this error
Code:
downloading 'boot.img'... FAILED (remote: not allow) finished. total time: 0.000s
if i try
Code:
C:\and\platform-tools>fastboot flash recovery rec.img
sending 'recovery' (3972 KB)... FAILED (remote: not allow) finished. total time: 0.000s
I maybe do i very very stupid thing and extracted flash_image from some Hero ROM and using cat put it in /system/bin/
I am desperate and i don’t know what to do next.
Hero:
3.36.405.1
HBOOT 1.76.0007 (HERO 1000)
Radio 6.35.15.11
try this
run cmd
cd C:\and\platform-tools>
fastboot boot rec.img
i am not sure about it
Try place recovery on your SD card, name it recovery img. Then run via terminal or adb:
su
flash_image recovery /recovery.img
reboot recovery
Press enter after each line
sent with love from me to you
Habarug said:
Try place recovery on your SD card, name it recovery img. Then run via terminal or adb:
su
flash_image recovery /recovery.img
reboot recovery
Press enter after each line
sent with love from me to you
Click to expand...
Click to collapse
It says ran out of memory :/ It's very annoying I've had the same problems as op and still can't do it.
Did you use goldcard to downgrade? AFAIK all bootloaders from 1.5 were locked down. Is error 140 mismatched. CID? If it is, you need a goldcard.
EDIT: just noticed you said you made a goldcard. Are you sure it stuck? Some sdcards aren't suitable for being a goldcard.
Sent from my GT-I9100 using XDA App
Hello im very new to this rooting and roming and i have no idea why i cant or wont let me do flash recovery im using fastboot
heres what comes up when trying:
sending 'recovery' <1250 KB>...
FAILED <remote: not allow>
finished. total time: 0.016s
i push volume down and power after turning off phone
this is what i see:
Click PVT Ship S-ON
HBOOT-0.52.0001 (CLIC10000)
MICROP-0203
RADIO-3. 35. 07 . 20
Sep 22 2009, 14:40:39
i followed what it says to go about fastboot but nothing worked
is there anyway i could fix to work????
thanks
look here.
http://forum.xda-developers.com/showthread.php?t=950759
firstly install htc sync, to have driver. Then enable usb debugging mode.
You can download CWM 5.0.2.0 recovery img and put that downloaded file to your SD card, run Terminal emulator for your phone and install it manually.
Commands for Terminal Emulator said:
su
flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
Notice: You need to have su and flash_image files on your SD card before doing anything. (Root required)
so i unlocked my bootloader using the htcdev guide. this updated my hboot to 1.02.000 and when i try to flash CWM i get this error.
Code:
sending 'recovery' (1685 KB)... OKAY
writing 'recovery'... FAILED (remote: image error! (BootMagic check fail))
The Usual Suspect said:
so i unlocked my bootloader using the htcdev guide. this updated my hboot to 1.02.000 and when i try to flash CWM i get this error.
Code:
sending 'recovery' (1685 KB)... OKAY
writing 'recovery'... FAILED (remote: image error! (BootMagic check fail))
Click to expand...
Click to collapse
how (which method) are you trying to flash the recovery?
Here's the quick guide
Install hTc drivers successfully on pc.
Remove hTc sync and other related apps.
Now download clockworkmod recovery(whichever you want) and fastboot+adb kit on pc.
Open fastboot.
Connect ur phone. Load the bootloader and then fastboot. Fastboot mode(something like that) should be on your phone. Paste recovery and boot image in fastboot folder.
Type fastboot devices
Type fastboot flash boot boot.img(boot.img can be found in ur stock ruu )
Type fastboot flash recovery 'recoveryname'.zip
After that disconnect ur phone.
Select recovery.
(If u dont see anything, it was unsuccessful, hold vol up+power to see default recovery.)
Now install roms like this(http://forum.xda-developers.com/showthread.php?t=1851096):p(my rom) via recovery.
Hit Thanks.
You are done
Note:s off is not required for flashing a custom rom, however an unlocked bootloader is.
help needed.
hey der. i have rooted my phone with s-on. but i am facing the same problem as i cannot boot in cwm recovery mode and hence cannot install a custom rom. i am no developer. so please can you elaborate your above method step by step. sorry i am a noob here.
thanx anywayz
Have you managed to install cwm?
I recently used Captain Throwback's method of achieving S-off and through the method my phone was given CWM Recovery... I wanted to flash Smelkus Recovery but am having an issue doing so.. tried flashing from Recovery and CMD Prompt... any ideas/input would be appreciated.
Command Prompt Info:
C:\Android\sdk\platform-tools>fastboot flash recovery recovery-ra-supersonic-4.3-smelkus-tmdirt2.img
sending 'recovery' (4156 KB)...
OKAY [ 1.123s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.139s
BootLoader Info:
SUPERSONIC EVT3 SHIP S-OFF
HBOOT-2.10.0001
MICROP-041f
Touch Panel-ATMEL224_16ab
RADIO-2.15.00.11.19
Oct 15 2010,12:07:00
MonsterBoX said:
I recently used Captain Throwback's method of achieving S-off and through the method my phone was given CWM Recovery... I wanted to flash Smelkus Recovery but am having an issue doing so.. tried flashing from Recovery and CMD Prompt... any ideas/input would be appreciated.
Command Prompt Info:
C:\Android\sdk\platform-tools>fastboot flash recovery recovery-ra-supersonic-4.3-smelkus-tmdirt2.img
sending 'recovery' (4156 KB)...
OKAY [ 1.123s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.139s
BootLoader Info:
SUPERSONIC EVT3 SHIP S-OFF
HBOOT-2.10.0001
MICROP-041f
Touch Panel-ATMEL224_16ab
RADIO-2.15.00.11.19
Oct 15 2010,12:07:00
Click to expand...
Click to collapse
Switching from CWM to Smelkus can only be done through bootloader and not through recovery.
Rename the file PC36IMG.zip and put it on your SD card... make sure it is not inside a folder as it must be in the root directory.
Hold down your power off button, hit reboot, and select the bootloader option instead of recovery. It will reboot your phone. When it powers up on the bootloader screen, follow the command prompts to install the PC36IMG.zip image.
Once complete, the phone will reboot with Smelkus Recovery.
Sent from my PC36100 using xda app-developers app
This is the same process used to flash new splash screens now that you have s-off.
Kfunk said:
Switching from CWM to Smelkus can only be done through bootloader and not through recovery.
Rename the file PC36IMG.zip and put it on your SD card... make sure it is not inside a folder as it must be in the root directory.
Hold down your power off button, hit reboot, and select the bootloader option instead of recovery. It will reboot your phone. When it powers up on the bootloader screen, follow the command prompts to install the PC36IMG.zip image.
Once complete, the phone will reboot with Smelkus Recovery.
Sent from my PC36100 using xda app-developers app
This is the same process used to flash new splash screens now that you have s-off.
Click to expand...
Click to collapse
+ 1 :highfive:
Kfunk said:
Switching from CWM to Smelkus can only be done through bootloader and not through recovery.
Rename the file PC36IMG.zip and put it on your SD card... make sure it is not inside a folder as it must be in the root directory.
Hold down your power off button, hit reboot, and select the bootloader option instead of recovery. It will reboot your phone. When it powers up on the bootloader screen, follow the command prompts to install the PC36IMG.zip image.
Once complete, the phone will reboot with Smelkus Recovery.
Sent from my PC36100 using xda app-developers app
This is the same process used to flash new splash screens now that you have s-off.
Click to expand...
Click to collapse
OK... Very Cool... I have been flashing Roms for awhile now... had Samsung Epic that went bad, then I found a good deal on a used Evo 4g and have been flashing Roms w/ S-On... but got the Boot Manager which needed S-Off as well as flashing Radios and such... it seems that I got Unity Rom to work on Boot Manager but I tried Black Dahlia and another where I had to add zips to flash w/ the roms and my phone is getting stuck on the HTC screen with those
....also noticed on Bootloader screen when checking PC36IMG.zip ... it checks P36DIAG.zip... and says no image found... not sure if that's normal or not.
it's normal. ignore.
i seem to have managed to get along without Boot Manager all this time. if it works for you, great.
Kfunk said:
Switching from CWM to Smelkus can only be done through bootloader and not through recovery.
Click to expand...
Click to collapse
Actually it is possible, the updater-script would just be writing the recovery.img to the right partition and thats it
Code:
write_raw_image("recovery-smelkus.img", "/recovery");
And splash screens can also be flashed through fastboot (in the right format) :thumbup:
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.