Related
Followed the steps to root this phone . Got the bootloader unlocked and also flashed the recovery . But when I try to go into recovery I get a green android with no command on the screen .
What do i need to do to sucessfully flash TWRP and get this of this green android ..
flash twrp again.
sguy156 said:
Followed the steps to root this phone . Got the bootloader unlocked and also flashed the recovery . But when I try to go into recovery I get a green android with no command on the screen .
What do i need to do to sucessfully flash TWRP and get this of this green android ..
Click to expand...
Click to collapse
You haven't flashed recovery properly.
Try flashing it again.
Use the flash command not the boot command.
Sent from my XT1562 using Tapatalk
I did used the flash command to flash recovery and got success message . Boot command was to boot th phone into recovery ..
sguy156 said:
I did used the flash command to flash recovery and got success message . Boot command was to boot th phone into recovery ..
Click to expand...
Click to collapse
When you are in that green android screen press:
Press Power and while pressing it tap Volume Up
ps are you sure you flashed the latest version of the recovery?
sguy156 said:
I did used the flash command to flash recovery and got success message . Boot command was to boot th phone into recovery ..
Click to expand...
Click to collapse
I Rooted my X play last night. I used r4 twrp. When I select recovery mode from boorloader menu, it jumps straight into recovery. No need for the power button and up. If you see the android with red exclamation then I would success flashing it again via fastboot. remeber it's "fastboot flash recovery *.*.*.*.img". You might have used boot instead of flash.
I am using the right recovery here is the output
C:\adb>fastboot flash recovery twrp-2.8.7.1-clark.img
target reported max download size of 536870912 bytes
sending 'recovery' (35332 KB)...
OKAY [ 0.993s]
writing 'recovery'...
OKAY [ 0.779s]
finished. total time: 1.774s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.001s
2.8.7.1 is the latest for this phone and when I press power when I get green android I get stock recovery . See attached .
sguy156 said:
I am using the right recovery here is the output
C:\adb>fastboot flash recovery twrp-2.8.7.1-clark.img
target reported max download size of 536870912 bytes
sending 'recovery' (35332 KB)...
OKAY [ 0.993s]
writing 'recovery'...
OKAY [ 0.779s]
finished. total time: 1.774s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.001s
2.8.7.1 is the latest for this phone and when I press power when I get green android I get stock recovery . See attached .
Click to expand...
Click to collapse
I don't know what model phone that is. Looks completely different to any Moto X Play I've seen. Not that I've seen to many. I'm using the XT1562. The recovery I used was:
http://forum.xda-developers.com/moto-x-play/orig-development/recovery-twrp-2-8-7-0-t3194656
I used r4. But the newest one is r5.
What model phone do you have?
I have moto X play pure edition ..
I have moto X play pure edition , i got the phone to go into recovery immediately flashing it . Now when i flash SU from the zip phone gets stuck at the boot screen only way to get the phone to boot is to restore the backup.
If you have flashed the recovery for Moto x play then I think you have made a mistake if your phone is Moto x pure edition as you have stated.This forum is for x play not for pure edition.So obviously all the files posted here are meant for only x play.So please go to the pure edition forum and search for what you want there.
sguy156 said:
Followed the steps to root this phone . Got the bootloader unlocked and also flashed the recovery . But when I try to go into recovery I get a green android with no command on the screen .
What do i need to do to sucessfully flash TWRP and get this of this green android ..
Click to expand...
Click to collapse
Play and Pure are different phones btw.
But I rooted my play two days ago using windroid's tool. I had the same issue. There was a silent failure and I thought it had been flashed when it hadn't. I found that I had to download a recovery image (save as Recovery.img, not Recovery1 as the tool seemed to have done) and flash the recovery manually.
sguy156 said:
I have moto X play pure edition , i got the phone to go into recovery immediately flashing it . Now when i flash SU from the zip phone gets stuck at the boot screen only way to get the phone to boot is to restore the backup.
Click to expand...
Click to collapse
You are in the wrong forum. This is for Moto X Play. You have the Moto X Pure.
To confirm. Go to Settings>About Phone and check your Phone model number.
I had the same problem
Although do not believe it, there is a rare version, XT1563 model, which is simple sim, and brings pure Android; I had the same problems, to install the Recovery, until I found a * .bat, what I modified to install the TWRP v2. I used it to install the r4 and r5 versions without any problems.
But it was not with, the rooting
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.
Hello and thanks in advance to everyone,
I am trying to root my moto g4 but I am stuck on installing a recovery. I did unlock the bootloader and when I turn on the phone i am greeted with"this device is unlocked and can't be trusted"
Yet when i try to flash the recovery it states that it failed to install since the package is unsigned:
C:\Users\Jelle\Desktop\Nieuwe map>mfastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (12496 KB)...
OKAY [ 0.405s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.344s]
finished. total time: 0.748s
Re-entering my unlock code also does not work as it gives me this message:
C:\Users\Jelle\Desktop\Nieuwe map>fastboot oem unlock NYRTWS*************
...
(bootloader) invalid boot state
OKAY [ -0.000s]
finished. total time: -0.000s
Does someone have any idea on what the issue is, am I missing something?
Thank you in advance!
Twrp is for motog4 plus aka athene. Make sure your device is the same.
Just reboot to recovery after you flash twrp using fast boot. Do not reboot your device to your home screen as your recovery partition will be rewritten with the stock recovery.
Do not worry about the message. It doesn't say that flashing failed. It only gives you a warning that it's not signed. That message is displayed even if you flash the stock recovery using fast boot.
Sent from my Moto G (4) using Tapatalk
Silesh.Nair said:
Twrp is for motog4 plus aka athene. Make sure your device is the same.
Just reboot to recovery after you flash twrp using fast boot. Do not reboot your device to your home screen as your recovery partition will be rewritten with the stock recovery.
Do not worry about the message. It doesn't say that flashing failed. It only gives you a warning that it's not signed. That message is displayed even if you flash the stock recovery using fast boot.
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
that totally worked! thank you very much
same problem mentioned above but after recovery mode my devicxe says no command.
help mw plzzz
sauravchandela95 said:
same problem mentioned above but after recovery mode my devicxe says no command.
help mw plzzz
Click to expand...
Click to collapse
If you're getting a screen with 'no command', that's the stock recovery on your device.
Are you rebooting to the recovery straight after flashing TWRP? Do you have an unlocked bootloader and what version of TWRP are you flashing? What commands are you using to flash?
You may wish to try booting with TWRP first:
1)On a device with an unlocked bootloader, boot to the bootloader screen.
2)Connect your device to your computer via a high quality USB data cable or the original USB cable.
3)Ensure your TWRP image is copied to your ADB folder.
4)Open an ADB terminal. Verify your device is communicating with your computer by typing 'fastboot devices' without quotes. Press Enter. You should get a serial number response.
5)If so, then type 'fastboot boot twrp.img' without quotes. Replace twrp.img with the actual full file name of your TWRP image in your ADB folder including the file extension. For example, if your TWRP image file name is shreps_twrp_3_1_1.img, the full command would be fastboot boot shreps_twrp_3_1_1.img You can type the first few letters of the file name and press Tab on your keyboard to automatically complete the file name if you so wish.
6)Press Enter, and your device should download TWRP and boot to TWRP.
Moto g4 XT1625 install TWRP 3.0.2 fail, Image not signed or corrupt.
unlock boot loader ok,
Install TWRP 3.0.2 from official (twrp-3.0.2-0-athene.img 12.2M 2016-06-08 17:50:53 EDT) fail with these message:
(bootloader) Image not signed or corrupt
I tried again, not work. After that, reboot, try to enter recovery mode, only get "no command" message with a dead Android robot on the screen.
I wanna root this device, but can't install TWRP at all.
Please give some help.
Reboot to recovery first after flashing twrp. Then reboot from twrp recovery.
Don't worry about the message. It's just a warning.
Sent from my Moto G (4) using Tapatalk
funplay said:
Moto g4 XT1625 install TWRP 3.0.2 fail, Image not signed or corrupt.
unlock boot loader ok,
Install TWRP 3.0.2 from official (twrp-3.0.2-0-athene.img 12.2M 2016-06-08 17:50:53 EDT) fail with these message:
(bootloader) Image not signed or corrupt
I tried again, not work. After that, reboot, try to enter recovery mode, only get "no command" message with a dead Android robot on the screen.
I wanna root this device, but can't install TWRP at all.
Please give some help.
Click to expand...
Click to collapse
do exactly what i give-
1.Put your device in bootloader mode(make sure the usb debugging is on)
2.Open adb (make sure adb and twrp are in the same folder)by shift+right click,then open command window here(do this where adb is installed).
3.Type: fastboot flash recovery [name of twrp image].img
4.Then in the bootloader menu toggle to restart bootloader .(Not restart because the recovery will get replaced by stock recovrey)
5.Open recovery.twrp should be installed
If you have any problem send the printscreen of cmd.
Step 4 : Choose Reboot to recovery mode using volume keys. Press power button to select.
Sent from my Moto G (4) using Tapatalk
First of all, thanks for all the reply.
I will leave more detail and keep trying.
turn on usb debugging. --> ok
adb reboot bootloader --> ok
fastboot devices --> ok show devices
fastboot flash recovery recovery.img --> enter everything right but only got fail & pain T_T
// The message:
fastboot flash recovery twrp.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (12496 KB)...
OKAY
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY
// end
Here, it said sending 'recovery' (12496 KB)...
which means, I guess it get that img file, but still fail.
By the way, some other user got the same problem and message.
I tried on XT1625 Moto g4, again and again, fail. close unnecessary program.
If I can unlock bootloader, hardly believe things could go south like this.
Maybe the key problem is
1 (bootloader) has-slot:recovery: not found
something must wrong, but where?
2 (bootloader) Image not signed or corrupt
XT1625 Moto g4, Moto g4 plus need different TWRP? But there's only one from TWRP official website.
I tried everything I can do, download again compare with md5 before I post.
I can't find way out.
Anyway, thanks alot.
updated, I'm not sure, but as you said, I tried again, suddenly, I could enter TWRP, I will try whether it work or not.
Another question is, after unlock bootloader, install TWRP, root. Can I update system or patch with OTA?
Thank you for reply and help.
funplay said:
updated, I'm not sure, but as you said, I tried again, suddenly, I could enter TWRP, I will try whether it work or not.
Another question is, after unlock bootloader, install TWRP, root. Can I update system or patch with OTA?
Thank you for reply and help.
Click to expand...
Click to collapse
Nupe.
Followed a tutorial on how to install lineage-14.1-20180817-UNOFFICIAL-cedric, but somehow missed a step or messed up.
I unlocked the bootloader, not exactly but in general: flashed the boot.img and rebooted, phone started and was able to use android.
But some strange problems occurred, like somehow my PIN was not recognized and device failed to factory reset.
Locked the bootloader again because of the warning (here's my mistake I guess) and now am unable to flash or revert to stock.
I am able to boot into android, did enable USB debug and bootloader unlock.
But everytime I boot I get the warning a different kernel has been installed (instead of wrong key before) and permission is always denied remotely.
C:\ad>fastboot flash logo logo.bin
Sending 'logo' (2186 KB) OKAY [ 0.068s]
Writing 'logo' (bootloader) flash permission denied
FAILED (remote: '')
Finished. Total time: 0.077s
This happens with everything, permission denied.
If I try to unlock it again via fastboot commandline (Windows) I get:
"(bootloader) invalid boot state"
Starting the phone in fastboot, the status is "flashing_locked".
What can I do now?
I am a noob, therefor the tutorial...
Thanks
thugscorpion said:
Followed a tutorial on how to install lineage-14.1-20180817-UNOFFICIAL-cedric, but somehow missed a step or messed up.
I unlocked the bootloader, not exactly but in general: flashed the boot.img and rebooted, phone started and was able to use android.
But some strange problems occurred, like somehow my PIN was not recognized and device failed to factory reset.
Locked the bootloader again because of the warning (here's my mistake I guess) and now am unable to flash or revert to stock.
I am able to boot into android, did enable USB debug and bootloader unlock.
But everytime I boot I get the warning a different kernel has been installed (instead of wrong key before) and permission is always denied remotely.
C:\ad>fastboot flash logo logo.bin
Sending 'logo' (2186 KB) OKAY [ 0.068s]
Writing 'logo' (bootloader) flash permission denied
FAILED (remote: '')
Finished. Total time: 0.077s
This happens with everything, permission denied.
If I try to unlock it again via fastboot commandline (Windows) I get:
"(bootloader) invalid boot state"
Starting the phone in fastboot, the status is "flashing_locked".
What can I do now?
I am a noob, therefor the tutorial...
Thanks
Click to expand...
Click to collapse
First, this thread is for g5 plus not for g5, so post in that thread.
Solution:- which firmware you are trying is it for g5 or g5+, if you flash wrong firmware then this happen, try downloading your firmware and then flash it.now you are on stock. If you don't know how to Flash, you can prefer XDA threads or use Lenovo Moto smart assistant app (pc) that will flash the firmware for you.
If you want to go on custom ROM then, first go to stock rom as it will restore your boot.img and custom ROM can work. If you directly want to go to custom rom (skiping above procedure) then flash boot.img from ADB or twrp and install custom ROM.
Here is the thread to Flash stock ROM:-
https://forum.xda-developers.com/g5...-flash-stock-romfactory-t3691396/post74221633
Link for Lenovo Moto smart assistant app:-
https://support.lenovo.com/in/en/downloads/ds101291
And if you are using XDA threads it has old firmware which can brick you Device you can get your firmware from here and chose which firmware channel you belong:-
https://mirrors.lolinet.com/firmware/moto/potter/official/
At last to not take risk remove bootloader and gpt commands from ADB.
It is a G5 Plus and I get permission denied with adb or fastboot.
In android I van go go developers option and OEM unlock is ON, if I go fastboot, flashing is locked.
thugscorpion said:
It is a G5 Plus
Click to expand...
Click to collapse
Well LOS14....-cedric is the G5 variant. You didn't flash the wrong firmware did you?
Apperently I did...
Is there a way to fix it?
the Lenovo recovery tool mentioned above doesn't do anything with the "flash" option.
Put the phone in fastboot mode and it is not recognized by the Lenovo application.
Can still manual send fastboot and adb via the Windows command line but still "locked" and "pemrission denied".
the command fastboot flashing unlock did the trick for now.
But, I want to revert to stock, what is the correct way?
Can someone point me to a good how to or tutorial with recent files?
EDIT: I see LineageOS officially is not supporting the G5 plus, but there is a unofficial version in the G5 plus forums.
I'm still thinking of customizing because of all the bloatware and sluggish performance.
reïnstalled TWRP, put Pixel Experience on an SD card, booted TWRP recovery, did several attempts to clean all data / cache etc. but got several errors, retried, rebooted, chose all options and installed Pixel.
First try phone did not boot, froze on Pixel boot, again wiped everything, again installed Pixel and now it boots.
good lesson.
Phone is not entirely recognized the correct way, google security speaks of a Moto X (4) and the phone itself mentions the exact model number instead of Moto G5 Plus.
thugscorpion said:
reïnstalled TWRP, put Pixel Experience on an SD card, booted TWRP recovery, did several attempts to clean all data / cache etc. but got several errors, retried, rebooted, chose all options and installed Pixel.
First try phone did not boot, froze on Pixel boot, again wiped everything, again installed Pixel and now it boots.
good lesson.
Phone is not entirely recognized the correct way, google security speaks of a Moto X (4) and the phone itself mentions the exact model number instead of Moto G5 Plus.
Click to expand...
Click to collapse
Yeah security does show as Moto X4. That's normal.
One final question: On reboot I always end up in the fastboot menu without holding power and volume down, I also always get the unlock warning.
Is this a sign the bootloader is still not okay?
And is there an easy way to fix it?