EDIT: ALSO, use usb 2.0 ports to flash stuff, usb 3.0 is not working 100 percent yet.
EDIT, 14 Mar 2016: Kingroot got me to root and now I have twrp installed, http://www.kingroot.net/ .
I have a Sprint prepaid Moto E 2015 LTE, XT1526. I did the motorola bootloader unlock, that went fine.
The phone works and is activated on RingPlus, when it boots, I get the Red Warning, Bootloader unlocked, when normally booting.
When I try to flash a recovery to the phone (all that I could find here on XDA), I get this response:
S:\Phones\Moto_E-2015-2ndGen-XT1526\adb-and-fastboot>fastboot devices
TA0XXXXXXX fastboot (edited to take out SN)
S:\Phones\Moto_E-2015-2ndGen-XT1526\adb-and-fastboot>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (12916 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.015s
S:\Phones\Moto_E-2015-2ndGen-XT1526\adb-and-fastboot>adb kill-server
I've tried everything, and am providing as much info as I can, in case anyone seeing something that is 'new' or 'different' about my phone.
Double check and be sure you're attempting to flash the TWRP for the Moto E 2015 LTE "Surnia", not "Otus" (which is the Moto E 2015 3G). iirc, I used Squid's TWRP from here: http://forum.xda-developers.com/moto-e-2015/development/twrp-squid-twrp-recovery-moto-e-lte-t3137649 . If 3.0.0 doesn't work, try 2.8.7.
You should also try changing USB ports. I ran into a similar issue where I wasn't able to flash things when I plug into my most often used USB port. I suspect that the contacts got worn from how often I used it, so I tried another USB port and it worked fine.
I have done same procedure as yours and meet same problem yesterday.
I flashed twrp recovery with following command,
fastboot boot recovery.img
instead of
fastboot flash recovery recovery.img
here are the post which I followed.
http://www.xda-developers.com/how-to-root-the-moto-e-2015-and-unlock-the-bootloader-xda-tv/
http://forum.xda-developers.com/moto-e-2015/orig-development/twrp-moto-e-2015-recovery-t3049726
faheyd said:
When I try to flash a recovery to the phone (all that I could find here on XDA), I get this response:
S:\Phones\Moto_E-2015-2ndGen-XT1526\adb-and-fastboot>fastboot devices
TA0XXXXXXX fastboot (edited to take out SN)
S:\Phones\Moto_E-2015-2ndGen-XT1526\adb-and-fastboot>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (12916 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.015s
Click to expand...
Click to collapse
Thanks, but not working:
S:\Phones\Moto_E-2015-2ndGen-XT1526\adb-and-fastboot>fastboot boot recovery.img
downloading 'boot.img'...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.009s
S:\Phones\Moto_E-2015-2ndGen-XT1526\adb-and-fastboot>
You can get rid of the warning by method in post 2 of this link
http://forum.xda-developers.com/moto-e-2015/general/guide-unlock-bootloader-moto-e-2015-t3045748
Q1:How to remove the unlocked bootloader message?
Then, flash the twrp recovery again. Make sure you have right recovery.img. here is the one I used.
http://forum.xda-developers.com/devdb/project/?id=8591#downloads
llaalways said:
You can get rid of the warning by method in post 2 of this link
http://forum.xda-developers.com/moto-e-2015/general/guide-unlock-bootloader-moto-e-2015-t3045748
Q1:How to remove the unlocked bootloader message?
Then, flash the twrp recovery again. Make sure you have right recovery.img. here is the one I used.
http://forum.xda-developers.com/devdb/project/?id=8591#downloads
Click to expand...
Click to collapse
I know that, does not help. I've tried that recovery, one from cyanogenmod also, the recovery img is not the problem. Thanks anyway.
go to phone options and turn on USB debugging and when you go to flash it..
- turn off phone.
- hold volume down and power to get to boot loader screen..
Leave it there and connect to PC.
It should be showing you the bootloader screen.. you know what that is right ?
Then open "Minimal ADB and Fastboot" install folder..
Right click empty folder space while holding shift key down..
Select open cmd window here..
type in either,
fastboot devices
or
mfastboot devices
and make sure it says your device is listed
then paste into cmd window..
mfastboot flash recovery recovery.img
make sure your new recovery file has that name and is copied to that fastboot folder.
that should be it..
xpmule said:
go to phone options and turn on USB debugging and when you go to flash it..
- turn off phone.
- hold volume down and power to get to boot loader screen..
Leave it there and connect to PC.
It should be showing you the bootloader screen.. you know what that is right ?
Then open "Minimal ADB and Fastboot" install folder..
Right click empty folder space while holding shift key down..
Select open cmd window here..
type in either,
fastboot devices
or
mfastboot devices
and make sure it says your device is listed
then paste into cmd window..
mfastboot flash recovery recovery.img
make sure your new recovery file has that name and is copied to that fastboot folder.
that should be it..
Click to expand...
Click to collapse
As stated in my OP, I've done all that, but I'll do it again, please look at my pics and post, you'll see I've done all that already:
S:\Phones\Moto_E-2015-2ndGen-XT1526\mfastboot-v2>mfastboot devices
TA00000000 fastboot (edited to change serial number)
S:\Phones\Moto_E-2015-2ndGen-XT1526\mfastboot-v2>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (12916 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.007s
S:\Phones\Moto_E-2015-2ndGen-XT1526\mfastboot-v2>
Can a DEV please help ? If I need to go back to stock I'll be glad to do it and then unlock the bootloader again, however, I've posted in two diff forums trying to get someone to tell me the correct SPRINT img to bring back to stock, no answers.
XT1526_SURNIA_USC_5.0.2_LXI22.50-29.1_cid9_subsidy-DEFAULT_CFC.xml
XT1526_SURNIA_REPW_5.0.2_LXI22.50-56-1.1_cid6_subsidy-REPUB_CFC.xml
XT1526_SURNIA_BOOST_5.0.2_LXI22.50-14.8_cid9_subsidy-DEFAULT_CFC.xml
I think it's the boost, but it doesn't have the SPRINT label on it, like my phone.
You just said,
"Can a DEV please help ? If I need to go back to stock I'll be glad to do it and then unlock the bootloader again"
So why would you say that ?
Did you relock your bootloader ?
Maybe that is why you are having a problem ?
I never have relocked mine eh..
And i have had no problem flashing TWRP from Squid.. all his various updates overwriting the old one.
I have flashed a bunch of stock retail recoveries too and all of those worked fine too.
I am curious did you try and load recovery after to see if it actually changed or not ?
EDIT:
Can i ask you exactly what Custom Recovery you are trying to install ?
And did you verify the MD5 hash ?
I always do *if it's available..
xpmule said:
You just said,
"Can a DEV please help ? If I need to go back to stock I'll be glad to do it and then unlock the bootloader again"
So why would you say that ? On other models of phones it has solved a problem of this nature.
Did you relock your bootloader ? Of course not, if you had read the post, you would see that.
Maybe that is why you are having a problem ? No
I never have relocked mine eh.. Good for you, that doesn't help me.
And i have had no problem flashing TWRP from Squid.. all his various updates overwriting the old one.
I have flashed a bunch of stock retail recoveries too and all of those worked fine too. Good for you, that doesn't help me.
I am curious did you try and load recovery after to see if it actually changed or not ? I did, I get an icon with something that says no cmd,
EDIT:
Can i ask you exactly what Custom Recovery you are trying to install ? Surnia and CM's recovery, no difference.
And did you verify the MD5 hash ? Yes.
I always do *if it's available..
Click to expand...
Click to collapse
I've done all those things and tried to post as much info in my OP. Is there a Dev that can help me?
I've now tried to go back to stock in an effort to unlock this biatch using XT1526_SURNIA_BOOST_5.0.2_LXI22.50-14.8_cid9_subsidy-DEFAULT_CFC.xml, and it wont let me do that either. It's not letting me write to the GPT partition. This leads me to believe my phone is NOT unlocked, even though the bootloader shows UNLOCKED BOOTLOADER. Anyone know an answer?
I noticed something a while back when I attempted to flash recovery on a different phone (nexus 6) but failed. I tried a bunch of stuff to no avail. The solution was to simply get a new set of platform tools because mine was too old. Doesn't hurt to try.
Snorbro said:
I noticed something a while back when I attempted to flash recovery on a different phone (nexus 6) but failed. I tried a bunch of stuff to no avail. The solution was to simply get a new set of platform tools because mine was too old. Doesn't hurt to try.
Click to expand...
Click to collapse
Thank you for trying. I just found a post, (and now I can't find it), but the guy went through what I did, and then he used KingRoot, http://www.kingroot.net/ , and it worked.
So, I tried it too, and magic, it worked. I now have root and TWRP installed.
I could have sworn I tried KingRoot, but it must have been on another phone I had.
Are you sure your recovery file is called recovery.img and not twrp.xxx.img? If not you need to rename it
Another problem I had, I was using a USB 3.0 port on my computer. This is a not the way. Using a USB 2.0 port works on flashing stuff.
Hi faheyd, I also have XT1526 on android 5.0.2, but kingroot fails. I was told not to update OS to keep it working in India.
Doess ur phone run on 5.1?
Does USB debugging needs to be activated?
drshreenivaas said:
Hi faheyd, I also have XT1526 on android 5.0.2, but kingroot fails. I was told not to update OS to keep it working in India.
Doess ur phone run on 5.1?
Does USB debugging needs to be activated?
Click to expand...
Click to collapse
I have no idea, hopefully someone that knows will step in and help.
Related
OK, so I was rolling along just fine...
Got Fastboot up and running, got myself an unlocked bootloader, got myself the latest TWRP image, and no matter WHAT I DO, I can not get TWRP to flash to my device, and it is driving me absolutely INSANE. Below is what i am getting from command prompt. Any help is GREATLY appreciated.
Code:
C:\Users\saltam\Downloads\TWRP>fastboot flash recovery recovery.img
sending 'recovery' (13186 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
I am pulling what little hair I have out over here, and I am no beginner when it comes to this stuff. Please help if you can.
Only a couple of things I can think, which I'm sure you've already done. Have you re-downloaded the image file and you have renamed it recovery.img?
Edit, is your bootloader unlocked?
Sent from my Nexus 5 using XDA Free mobile app
Boot loader is unlocked, tried everything besides a different computer. Tried different cord, different USB port, everything. It's like once I unlocked the boot loader the tablet stopped communicating with fast boot. Anything I try to do hangs until I hit reboot fast boot then it fails. Irritating the hell out of me...
have you tired using the wugs Nexus root toolkit? http://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
I was having some trouble TWRP installing as well., and it was able to install TWRP just fine
Close any other running programs, especially Chrome. Then if still not doing it, install CWM Recovery instead, and if you still want TWRP flash it from CWM Recovery.
My N5 won't let me have TWRP, so if you just want the functions of a recovery, try a different one.
blakeslee14 said:
have you tired using the wugs Nexus root toolkit? http://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
I was having some trouble TWRP installing as well., and it was able to install TWRP just fine
Click to expand...
Click to collapse
Tried Wug's, and got the same result when I got to it sending the fast boot commands. Prompt just hangs until I select reboot fast boot.
craig.buckie said:
Close any other running programs, especially Chrome. Then if still not doing it, install CWM Recovery instead, and if you still want TWRP flash it from CWM Recovery.
My N5 won't let me have TWRP, so if you just want the functions of a recovery, try a different one.
Click to expand...
Click to collapse
I'm at my end right now, because I want to remove all this dumb Google bloatware so badly. Was thinking about trying to flash stock image, or relock and unlock boot loader again to see if that does anything, but I'm very nervous that those options might not work because of the fact that fast boot commands aren't working. Certainly don't want to end up with a $400 paperweight...
SwoRNLeaDejZ said:
Tried Wug's, and got the same result when I got to it sending the fast boot commands. Prompt just hangs until I select reboot fast boot.
I'm at my end right now, because I want to remove all this dumb Google bloatware so badly. Was thinking about trying to flash stock image, or relock and unlock boot loader again to see if that does anything, but I'm very nervous that those options might not work because of the fact that fast boot commands aren't working. Certainly don't want to end up with a $400 paperweight...
Click to expand...
Click to collapse
I assume you're on 5.0.1. Flash the boot or recovery image from the factory image in fastboot. See if that works. That might rule out a fastboot issue. If it flashed it won't do anything negative to your device
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I assume you're on 5.0.1. Flash the boot or recovery image from the factory image in fastboot. See if that works. That might rule out a fastboot issue. If it flashed it won't do anything negative to your device
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Going to give this a shot now..
Worth mentioning, I ran an OEM Lock command, and successfully relocked the bootloader, so it appears fastboot is at least partially working. Going to attempt to flash the bootloader in the image from Google, because that is all there is. Just bootloader and image, no recovery image. I will post results here. I don't know why fastboot commands are broken after unlocking bootloader, but there is one thing that seems odd to me:
When I run fastboot devices, it returns the following (has been like this from the beginning):
Code:
C:\Users\saltam\Downloads\TWRP>fastboot devices
???????????? fastboot
Thoughts?
Something's not right. Do you have the newest fastboot?
di11igaf said:
Something's not right. Do you have the newest fastboot?
Click to expand...
Click to collapse
Yes, recently updated it via the minimalist fastboot/adb tool. This is REALLY irritating the hell out of me at this point... Been trying to get recovery on this stupid tablet all damn day...
I am starting to think this is a read/write error.. It is getting the error whenever it tries to write to the tablet... (sending boot.img results in the error every time)... Anyone know of fastboot/adb commands to check/fix read and write errors
**EDIT**
So, much to my chagrin, it appears to just be my computer... Tried on a different laptop, and was able to get it rooted.. For some odd reason though, I don't think TWRP is installing correctly ??
I am going to try and boot into recovery, but every time i try to flash it with fastboot flash recovery recovery.img it says it was successful, but a boot into recovery mode comes up as the dreaded NO COMMAND laying down Android icon. Super frustrating..
**EDIT 2**
So after much trying of different methods, I was able to successfully flash TWRP with Flashify. Not sure why I couldn't do it manually through fastboot but I'm good now. Thanks for all the replies and suggestions. This can be marked as closed or solved. Thanks!
SwoRNLeaDejZ said:
I am starting to think this is a read/write error.. It is getting the error whenever it tries to write to the tablet... (sending boot.img results in the error every time)... Anyone know of fastboot/adb commands to check/fix read and write errors
**EDIT**
So, much to my chagrin, it appears to just be my computer... Tried on a different laptop, and was able to get it rooted.. For some odd reason though, I don't think TWRP is installing correctly ??
I am going to try and boot into recovery, but every time i try to flash it with fastboot flash recovery recovery.img it says it was successful, but a boot into recovery mode comes up as the dreaded NO COMMAND laying down Android icon. Super frustrating..
**EDIT 2**
So after much trying of different methods, I was able to successfully flash TWRP with Flashify. Not sure why I couldn't do it manually through fastboot but I'm good now. Thanks for all the replies and suggestions. This can be marked as closed or solved. Thanks!
Click to expand...
Click to collapse
To your first edit, twrp is probably working correctly. Lollipop forces the stock recovery. There are two files, one in /system and one in /system/bin that force the stock recovery upon boot. You can remove those files or first
fastboot boot twrp.img
Then flash supersu in twrp, then
fastboot flash recovery twrp.img
Sent from my Nexus 9 using XDA Free mobile app
Got the right USB driver
Dirty Unicorns /Uber / Beanstalk Yuga adm.
xtcdk said:
Got the right USB driver
Dirty Unicorns /Uber / Beanstalk Yuga adm.
Click to expand...
Click to collapse
Kind of mystified with your response... Had nothing to do with the USB drivers. Found out afterward that the problem was the security that my company had setup on my laptop (was using my company thinkpad). Switching laptops solved the problem.
Here is my issue, will try to explain as much as I can:
So I got the phone only booting to the LG logo and no further. So I read a couple threads which were mentioning about the LG Flash tool that I could try to use to restore the device, that did not work. So I tried to do Fastboot to see if that would help in any way. After trying, I was able to get Fastboot using @Lelus method ,now I cant get back the S/W upgrade mode, trying everything i could think of and still no progress. Would really love to fix this device and appreciate any help I can get.
days , I can help you. First download the drivers for your phone (if you have already remove them and re-load )
Next, download the LG Mobile Support Tool .
then go to your phone S / W upragade Mode (Press the volume up or down on the start)
then start the support tool as an administrator.
then press the Settings update recovery .
on the 90% of the phone restarts functional.
If you have any problem just say it to me!
-Mechen
mechen said:
days , I can help you. First download the drivers for your phone (if you have already remove them and re-load )
Next, download the LG Mobile Support Tool .
then go to your phone S / W upragade Mode (Press the volume up or down on the start)
then start the support tool as an administrator.
then press the Settings update recovery .
on the 90% of the phone restarts functional.
If you have any problem just say it to me!
-Mechen
Click to expand...
Click to collapse
Already tried all that. Phone does not boot or nothing. I can only access fastboot. I cant even flash the ICS u and x boot. When I try it says remote: partition doesn't exist.
Can you flash recovery through fastboot, and then acces it? I had similiar problem to yours, bricked my phone, barley made it to fastboot, i then flashed recovery using fastboot flash recovery recovery.img then booted to recovery and applied backup, or you might aswell flash a rom, if you don't have rom on your SD, use other phone to put ROM on sd, or card reader etc., the just install it. Just incase. i added recovery.img to my post.
Forgot to mention, after flashing recovery, try fastboot reboot recovery
trumpiks said:
Can you flash recovery through fastboot, and then acces it? I had similiar problem to yours, bricked my phone, barley made it to fastboot, i then flashed recovery using fastboot flash recovery recovery.img then booted to recovery and applied backup, or you might aswell flash a rom, if you don't have rom on your SD, use other phone to put ROM on sd, or card reader etc., the just install it. Just incase. i added recovery.img to my post.
Forgot to mention, after flashing recovery, try fastboot reboot recovery
Click to expand...
Click to collapse
Will try it right now and let you know
DIdnt work. It says
C:\fastboot\bin>fastboot flash recovery recovery.img
sending 'recovery' (5898 KB)...
OKAY [ 3.070s]
writing 'recovery'...
FAILED (remote: partition does not exist)
finished. total time: 3.077s
Liger878 said:
Will try it right now and let you know
DIdnt work. It says
C:\fastboot\bin>fastboot flash recovery recovery.img
sending 'recovery' (5898 KB)...
OKAY [ 3.070s]
writing 'recovery'...
FAILED (remote: partition does not exist)
finished. total time: 3.077s
Click to expand...
Click to collapse
Ok now thats strange, you have all the drivers? ADB, OMAP, FASTBOOT
Yeah, everything is installed and installed properly.
Sent from my SGH-T959 using XDA Free mobile app
Hi all,
I have a small problem, my phone does not boot and hanging on Logo. Now i can boot to fastboot menu, but i cannot really use it since i have FRP lock . Is there any chance to baypass it to make possible to flash recovery boot.img ?
When i try any command getting this error :
Code:
target reported max download size of 266338304 bytes
sending 'revocery' (4096 KB)...
OKAY [ 0.142s]
writing 'revocery'...
FAILED (remote: Necessary to unlock FRP! Navigate to Settings > Develope
finished. total time: 0.154s
Since my phone not booting i cannot use this option Please help
Hi, back again
As i can see, try not to mess with the names :revocery...
When you want to flash the boot.img don't change that name.
Just flash it like : fastboot flash boot boot.img
Use my last boot.img which i sent you. That's a good one out of my backup.
For the FRP (perhaps edit your thread tiltle ) i have no answer in a minute. Did the "fastboot oem unlock" gave anything better ?
raystef66 said:
Hi, back again
As i can see, try not to mess with the names :revocery...
When you want to flash the boot.img don't change that name.
Just flash it like : fastboot flash boot boot.img
Use my last boot.img which i sent you. That's a good one out of my backup.
For the FRP (perhaps edit your thread tiltle ) i have no answer in a minute. Did the "fastboot oem unlock" gave anything better ?
Click to expand...
Click to collapse
I have try also boot , try everything, not matter if youhave FRP lock fastboot oem unlock is only to unlock bootloader, which i have, that is not a problem.
See if this method works for you
http://forum.xda-developers.com/showthread.php?t=3261846
Sent from my Nexus 6 using Tapatalk
joyrida12 said:
See if this method works for you
http://forum.xda-developers.com/showthread.php?t=3261846
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
You cannot use this method since i have only FastBoot feature, adb is not possible to use, since phone never boot. This method can be used only for phones what can boot correctly, so unfortunately useless for me. but thx for link
michalss said:
You cannot use this method since i have only FastBoot feature, adb is not possible to use, since phone never boot. This method can be used only for phones what can boot correctly, so unfortunately useless for me. but thx for link
Click to expand...
Click to collapse
i have exactly the same problem. FRP is locked but my phone doenst boot. so how can i unlock the frp with the fastboot mode?
stiggu said:
i have exactly the same problem. FRP is locked but my phone doenst boot. so how can i unlock the frp with the fastboot mode?
Click to expand...
Click to collapse
same problem on my mate s
good to know that adb is not working for others
i thaught it was just me
I've the same problem , any idea ??
michalss said:
Hi all,
I have a small problem, my phone does not boot and hanging on Logo. Now i can boot to fastboot menu, but i cannot really use it since i have FRP lock . Is there any chance to baypass it to make possible to flash recovery boot.img ?
When i try any command getting this error :
Code:
target reported max download size of 266338304 bytes
sending 'revocery' (4096 KB)...
OKAY [ 0.142s]
writing 'revocery'...
FAILED (remote: Necessary to unlock FRP! Navigate to Settings > Develope
finished. total time: 0.154s
Since my phone not booting i cannot use this option Please help
Click to expand...
Click to collapse
activate "Developer options"
playing several times "compilation"
go to options and enable developer
"Enable OEM unlock"
Hey , the problem is the device won't boot , so how can we enable developer option?!!!!
Sent from my iPhone using Tapatalk
There was a time when xda where the place to get the right answer and quick!
nowadays most topics are full of people with same problem and no dev to come to help, pity.
on topic: I have the same problem, ( mine is a Y6 pro) and before bricking it I had debugging and oem unlock enabled but now can't flash boot etc using fastboot ( error , denied ..) and can't use spflashtools either : preloader vcom appears for 1 second and then disappears and phone turns on.
tried many drivers, 3 Os'es (7, 8.1 ,10) still no luck.
porcha18 said:
activate "Developer options"
playing several times "compilation"
go to options and enable developer
"Enable OEM unlock"
Click to expand...
Click to collapse
Danke!!!!!!!!!!!!! Nach ewigem Suchen diese einfache Lösung. Vielen Dank!! Tag gerettet
the same issue
Good day, i have the same issue on my p9 EVA-L19.
FRP lock. And i can't do anything...
My warranty says that they cannot recover data from the phone, but the information is very important. I need to unlock FRP and somehow boot into TWRP or something to recover my data.
Please help someone if you had a same issue and results.
For the Huawei Y6 you can return to Stock.
Try to fastboot boot recovery-twrp.img and put your stock firmware (dload) folder to the rootdir at your sdcard.
Reboot your device to bootloader and hold down vol+ + vol- and use the command: fastboot boot stockrecovery.img (keep the keys pressed until the stock recovery comes up and starts installing your stock rom.
You will see an emui logo and the recovery will install the complete stock rom if you did everything right.
Retry to boot the stock recovery with this way if it is not working at the first try.
EDIT: after i wiped /system and and all the other stuff i was able to flash stock recovery via fastboot.
Runner85sx said:
For the Huawei Y6 you can return to Stock.
Try to fastboot boot recovery-twrp.img and put your stock firmware (dload) folder to the rootdir at your sdcard.
Reboot your device to bootloader and hold down vol+ + vol- and use the command: fastboot boot stockrecovery.img (keep the keys pressed until the stock recovery comes up and starts installing your stock rom.
You will see an emui logo and the recovery will install the complete stock rom if you did everything right.
Retry to boot the stock recovery with this way if it is not working at the first try.
EDIT: after i wiped /system and and all the other stuff i was able to flash stock recovery via fastboot.
Click to expand...
Click to collapse
Is there a way to do this on a mac?
Ive got adb enabled on terminal and I have a recovery.img file in my downloads though Im not sure if its the right one.
I typed in fastboot devices and then fastboot flash recovery recovery.img but it said cannot load recovery.img
anditan said:
Is there a way to do this on a mac?
Ive got adb enabled on terminal and I have a recovery.img file in my downloads though Im not sure if its the right one.
I typed in fastboot devices and then fastboot flash recovery recovery.img but it said cannot load recovery.img
Click to expand...
Click to collapse
your recovery location in adb is wrong probably. try changing it to the correct path. atleast thats what worked for me
man u can'T do anything because FRP is ACTIVATED !!!
No solution till now
Use the Huawei Swype bypass Method
michalss said:
Hi all,
I have a small problem, my phone does not boot and hanging on Logo. Now i can boot to fastboot menu, but i cannot really use it since i have FRP lock . Is there any chance to baypass it to make possible to flash recovery boot.img ?
When i try any command getting this error :
Code:
target reported max download size of 266338304 bytes
sending 'revocery' (4096 KB)...
OKAY [ 0.142s]
writing 'revocery'...
FAILED (remote: Necessary to unlock FRP! Navigate to Settings > Develope
finished. total time: 0.154s
Since my phone not booting i cannot use this option Please help
Click to expand...
Click to collapse
Try to do:
fastboot boot recovery.img
This will boot up the device with the given image. With that you can put a custom rom to your sd-card and flash it.
I will upload a Nandroid (stock system, recovery, boot) from my Y6 SCL-L01 soon.
With that you can restore boot and recovery with twrp. For this way you don't need to have a frp unlock.
Procedure:
fastboot boot recovery-twrp.img
Put your stock firmware (dload folder) to the sdcard.
Put my Nandroid to your sdcard.
Restore my Nandroid, reboot your device with Vol+ and Vol- pressed.
This way only works for SCL-L01 up to SCL-L04.
I need to create an extra recovery.img that includes a dt image that fits for all SCL variants.
Work in progress...
I have just removed frp today, but its not free method, unfortunately
THIS GUIDE IS FOR THE MOTO G6 PLUS ONLY
3: Root (aka Magisk)
What is Root? The easiest way to explain it is that root gives you elevated permissions allowing you to modify system files that are not possible to be modified with out elevated permissions. This process requires you to use a PC and assumes you are running the stock firmware.
READ FIRST
Before we proceed you need to download some files on your PC.
*ADB and Fastboot Installer for Windows - (Download) - When prompted to install a driver type the number 0 and hit enter. This will install the latest version of adb and fastboot where it is system-wide. This eliminates the need for adb.exe or fastboot.exe to be in the same folder as the files you will be working with. NOTE: Windows will flag this as a virus! The installer is open source and made by a Moderator here on XDA. It is a False Positive. You can view a VirusTotal report (https://www.virustotal.com/en/file/25dc5dca2494d1b1d93832b37ba9852b4f076bba86cf5029b4c944a28a1a01a1/analysis/]HERE[/url]). 26 out of 67 virus scanners report it as a virus. If your Anti-Virus is one of the ones that flag it as a virus, I would suggest you explore other Anti-Virus software, but that’s not what this guide is about.
* TWRP - (Download) - This is a modified Recovery Software allowing you to flash files that will allow you to fipe your device and install custom roms and other various things. Thanks to XDA Member @khode_Erfan who has ported it to our device.
*Magisk - (Download) - Download the Stable version here. While not required, I do suggest you download the Latest Uninstaller and Latest Magisk Manager as well.
With ADB, Fastboot, and TWRP and Magisk on your pc get ready to root your device!
On your Phone
3A: Enable developer settings by going to Settings->System->About->Tap "Build Number" 5-7 times. You will see notification at the bottom of the screen stating that Developer Options have been Enabled.
3B: Tap the back button to go back to the System screen.
3C: Now tap on Developer Options.
3D: Find the setting that says "Android Debugging" and tap on it to enable adb to work on your device. You should get a prompt on your phone about a host key. Accept it.
On your PC:
3E: Place the file Magisk-v*.zip (*=version number, so for example version 17.1 would be Magisk-v17.1.zip) on your SD Card.
3F: Use Windows Explorer to navigate to the place you downloaded the file twrp-3.2.1-37-evert.img
3G: Hold the Shift Key on your Keyboard. While holding Shift, Right Click in the window(not on the file). Depending on your windows version you should see either "Open PowerShell Window here" or "Open Command Window here." Select which ever one applies.
3H: Now type, or copy and paste, the following commands one at a time and press enter to execute it:
Code:
adb reboot bootloader
fastboot boot twrp-3.2.3-42-evert.img
3I: In TWRP, first tap Backup -> Select Storage -> Micro SD Card - > OK
3J: You will see a section that says "Select Partitions to Backup." Make sure to select all of these boxes.
3K: At the bottom of the screen Swipe the Blue Button where it says Swipe to Backup.
3L: When this is done, tap the Home button.
3M: Tap "Install."
3N: Now tap on "Select Storage"
3O: Tap Micro SD Card
3P: Tap OK
3Q: Navigate to the location of the Magisk.zip file you placed on you sd card earlier and tap on it.
3R: At the bottom of the screen use the "Swipe to confirm Flash" function to flash Magisk.
3S: When it's done tap the button that says Reboot System at the bottom right corner of the screen.
If your device reboots to android, then you have done everything right! If not here are some possible fixes. Make sure the phone is in the bootloader and connected to the PC.
Troubleshooting:
If you are stuck in a bootloop something went wrong but we can fix it pretty easy. Magisk modifies your boot partition when it is flashed. Flashing the boot.img file from the stock firmware should fix this:
boot.img: (Download)
MD5: bd305bc3bc8c591ee7ebba8f5026bb06
Use the command:
Code:
fastboot flash boot boot.img
If you you have an error such as "Can't Load Android System" or "Startup Failed" your partition table is probably corrupt. You can try fixing it by flashing gpt.bin from the stock firmware.
gpt.bin: (Download)
MD5: 631af2ecab87fe627ab00e61b07ac964
Code:
fastboot flash gpt.bin
At the moment of writing, the Magisk link directs also to twrp download. Fixed.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
I have a problem with the G6 Plus Dual sim model XT 1926-7 (bootloader unlocked).
When I type the command "fastboot boot twrp.img" (so I called the file) it tells me in CMD:
Fastboot: Unknown error: downloading 'boot.img' ... OKAY [0.555s] booting ... FAILED (remote: unknown command) finished. Total time: 0.569s
I tried to reinstall the drivers, changed "minimal adb" to "platform tools" and remains the same.
Any idea how to fix it?
weazie said:
At the moment of writing, the Magisk link directs also to twrp download.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Fixed. Thanks for pointing that out!
Alexx_lml said:
I have a problem with the G6 Plus Dual sim model XT 1926-7 (bootloader unlocked).
When I type the command "fastboot boot twrp.img" (so I called the file) it tells me in CMD:
Fastboot: Unknown error: downloading 'boot.img' ... OKAY [0.555s] booting ... FAILED (remote: unknown command) finished. Total time: 0.569s
I tried to reinstall the drivers, changed "minimal adb" to "platform tools" and remains the same.
Any idea how to fix it?
Click to expand...
Click to collapse
Have you tried disconnecting the phone from the pc and reconnect it then try again.
Sent from my Moto G6 Plus using XDA Labs
Xplorer4x4 said:
Have you tried disconnecting the phone from the pc and reconnect it then try again.
Click to expand...
Click to collapse
Yes, i tried but not working, and on other PC have same problem
Alexx_lml said:
Yes, i tried but not working, and on other PC have same problem
Click to expand...
Click to collapse
Try using different usb cable and different usb slot (usb 2.0 is better for fastboot).
rafikowy said:
Try using different usb cable and different usb slot (usb 2.0 is better for fastboot).
Click to expand...
Click to collapse
I have not tried with another cable or another port, just with another pc, the weird thing is that I have unlocked the bootloader without problem, but I can not start TWRP.
(deleted)
OTA updates for unlocked, rooted Moto G6 Plus
My Moto G6 Plus is unlocked and rooted after following this guide. Today I got a notification of an update from Motorola, but the OTA update fails. Is there a way to get this update?
Relative newbie so excuse me if answer is obvious.
helzayyat said:
My Moto G6 Plus is unlocked and rooted after following this guide. Today I got a notification of an update from Motorola, but the OTA update fails. Is there a way to get this update?
Relative newbie so excuse me if answer is obvious.
Click to expand...
Click to collapse
Well, you cannot do OTA directly on a rooted device. You have basically two options:
1) unroot, lock bootloader, take OTA, unlock bootloader, root.
2) find images of this new update, flash them, profit.
x) take my advice with a grain of salt. that's how it used to be on older devices, I haven't tried it myself. Research, research, research before you actually try any of this.
weazie said:
Well, you cannot do OTA directly on a rooted device. You have basically two options:
1) unroot, lock bootloader, take OTA, unlock bootloader, root.
2) find images of this new update, flash them, profit.
x) take my advice with a grain of salt. that's how it used to be on older devices, I haven't tried it myself. Research, research, research before you actually try any of this.
Click to expand...
Click to collapse
Thanks for that information. As it seems to be a relatively minor update (OPWS27.113-89-2 to OPWS27.113-89-5) I think I will wait for now.
I am running stock ROM unrooted and updated to 9.0, will this still work?
Alexx_lml said:
I have a problem with the G6 Plus Dual sim model XT 1926-7 (bootloader unlocked).
When I type the command "fastboot boot twrp.img" (so I called the file) it tells me in CMD:
Fastboot: Unknown error: downloading 'boot.img' ... OKAY [0.555s] booting ... FAILED (remote: unknown command) finished. Total time: 0.569s
I tried to reinstall the drivers, changed "minimal adb" to "platform tools" and remains the same.
Any idea how to fix it?
Click to expand...
Click to collapse
Do you have problems with sim signals, IMEI or something when unlocked the BL?
Managed to boot into TWRP but when backing up I get error 255. I have attached the twrp log file.
Swizzy88 said:
Managed to boot into TWRP but when backing up I get error 255. I have attached the twrp log file.
Click to expand...
Click to collapse
Decryption is broken in TWRP, therefore TWRP back ups are useless. Use Titanium Backup or Migrate.
Sent from my Phh-Treble vanilla using Tapatalk
Alexx_lml said:
I have a problem with the G6 Plus Dual sim model XT 1926-7 (bootloader unlocked).
When I type the command "fastboot boot twrp.img" (so I called the file) it tells me in CMD:
Fastboot: Unknown error: downloading 'boot.img' ... OKAY [0.555s] booting ... FAILED (remote: unknown command) finished. Total time: 0.569s
I tried to reinstall the drivers, changed "minimal adb" to "platform tools" and remains the same.
Any idea how to fix it?
Click to expand...
Click to collapse
I had the same problem. Fixed itself when I went onto a new (my old) laptop. I guess it's something to do with drivers.
Swizzy88 said:
I am running stock ROM unrooted and updated to 9.0, will this still work?
Click to expand...
Click to collapse
Same situation here, i try and boot twrp, but everything was encrypted... stuck in this step...
Xplorer4x4 said:
3J: You will see a section that says "Select Partitions to Backup." Make sure to select all of these boxes.
Click to expand...
Click to collapse
In TWRP do I really need to back up every single partition I have or just the ones that get changed by Magisk? They won't all fit on the sd card I currently have, but one or two will fit.
f1r3br4nd said:
In TWRP do I really need to back up every single partition I have or just the ones that get changed by Magisk? They won't all fit on the sd card I currently have, but one or two will fit.
Click to expand...
Click to collapse
No. Backup efs and the rest you don't need to worry about. Besides, it's pointless to backup data right now. We can't decrypt data in twrp so the restore will always fail on restore or boot up.
Sent from my Moto G6 Plus using XDA Labs
XT1926-7 root
Xplorer4x4 said:
...
Click to expand...
Click to collapse
Has anyone successfully rooted XT1926-7?
It's intended for non-US markets and sold on Amazon
**XT2041-4**
hey folks,
i have the gpower/g8power (XT2041-4) and i was able to unlock the bootloader and i have been able to do the fastboot commands but it fails when i do the fastboot system, product, vbmeta commands for the crdroid, lineage and havok. i got into twrp and tried installing the zips for those roms but those failed too.
i got to the android OS start screen but the touchscreen is unresponsive. i have looked through a lot of the threads for this device and can't find anything that works.
any help will be much appreciated because this is my daily driver.
edit: title should be XT2041-4
your best option would be to connect an otg cable, ( best is to make sure you can have a double connection, one for mouse , on connected to the pc) then get into the phone with the non-touchscreen booted rom, connect it to LMSA , and extract the boot.img image that comes with the rom LMSA downloads. you should have a working touchscreen with the version LMSA downloads .
Reason you need a double connection: you need to accept the connection to your pc from the phone
you could also browse to the settings --> about this phone and take a look at the exact ROM that is installed, and find that image on lollinet , then extract and boot the boot.img from that rom.
Hey, I'm having the same problem but I found a workaround.
you can either go in fastboot mode and enter
fastboot set_active b
or go in TWRP and change the active slot to B then proceed to boot up the phone.
In my case, it showed warning saying "cannot boot into system......file maybe corrupted" etc etc, just choose "factory reset" on that screen and your phone should boot into slot B with stock ROM.
That way you can have a functional phone while waiting for the developers to figure out the kernel problem
Cheers
hey thanks guys for taking the time to respond much appreciated.
somehow, no idea, i magically got the phone back to stock and the touchscreen is working. the bootloader is still unlocked so i am not messing with it. that scared the crap out of me lol
Chosimise said:
waiting for the developers to figure out the kernel problem
Cheers
Click to expand...
Click to collapse
this bugged me out. so are you saying if i did everything right, those ROMs i downloaded still wouldn't technically work? even if i do the slot B thing?
uglyaf said:
hey thanks guys for taking the time to respond much appreciated.
somehow, no idea, i magically got the phone back to stock and the touchscreen is working. the bootloader is still unlocked so i am not messing with it. that scared the crap out of me lol
this bugged me out. so are you saying if i did everything right, those ROMs i downloaded still wouldn't technically work? even if i do the slot B thing?
Click to expand...
Click to collapse
I had a completely different issue with the exact same model. I made a post here asking if anyone had an easy fix, but my guess is that these are just growing pains. Give it a couple months and the roms will likely be much more stable. One of the reasons I bought this phone in the first place is because it usually gets official Lineage OS support at some point. With time, I'm sure things will work great. If you use Windows, going back to stock everything is pretty dead simple with the Lenovo Rescue and Recovery tool, so you can kind of experiment safely if you back everything up.
uglyaf said:
hey thanks guys for taking the time to respond much appreciated.
somehow, no idea, i magically got the phone back to stock and the touchscreen is working. the bootloader is still unlocked so i am not messing with it. that scared the crap out of me lol
this bugged me out. so are you saying if i did everything right, those ROMs i downloaded still wouldn't technically work? even if i do the slot B thing?
Click to expand...
Click to collapse
After some tinkering, I actually figured out my problem. There's a big difference between "fastboot mode" (the one you enter by pressing power and vol-) and "Fastbootd" mode.
I did all my flashing in "fastboot mode" and I got no touch screen afterward.
Then there's another hiccup for me (which is why I didn't go in "fastbootd" mode in the first place): When I type in the command in regular "fastboot mode"
Code:
fastboot reboot fastboot
I got an error message saying "reboot fastboot" is not a valid destination or something down those lines.
The problem being, they only added that option in fastboot version r30, so I had to update my ADB and fastboot environment.
And I ran into yet another problem, no matter what I do, the fastboot command is still run with the older version. I guess I messed up the previous installation and the pathing got messy. I ended up using my work laptop for a clean installation of all drivers and it finally solved my problem. I guess I'm saying you need to clean up previous adb and fastboot drivers before using the new ones, especailly if you installed it systemwise.
Anyways, after I booted into "fastbootd" mode and flashed everything with the latest version of fastboot driver, the phone worked flawlessly.
Hope it helps!
hey thanks again for the responses people!
i have managed to get root on stock but still cant get cutsom roms installed at all. they always fail with these 2 methods
a) twrp
unmounting system....invalid zip file format! error installing zip file '/external_sd/....zip' updating partition details....done'
b)using command line
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
i type fastboot devices and it finds my phone. it lists it there but i type fastboot reboot fastboot and it just spams a huge list of commands and nothing changes on the phone. ive seen videos and fastbootd looks just like the old school recovery from droid1 days but idk if thats the same skin look on all devices. i was able to switch the slot from a to b in twrp but that didnt help. i cant figure out how to get into fastboot'D' mode.
im really trying here and im sorry im dumb. as always, any suggestions would be much appreciated. thanks again!
uglyaf said:
hey thanks again for the responses people!
i have managed to get root on stock but still cant get cutsom roms installed at all. they always fail with these 2 methods
a) twrp
unmounting system....invalid zip file format! error installing zip file '/external_sd/....zip' updating partition details....done'
b)using command line
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
i type fastboot devices and it finds my phone. it lists it there but i type fastboot reboot fastboot and it just spams a huge list of commands and nothing changes on the phone. ive seen videos and fastbootd looks just like the old school recovery from droid1 days but idk if thats the same skin look on all devices. i was able to switch the slot from a to b in twrp but that didnt help. i cant figure out how to get into fastboot'D' mode.
im really trying here and im sorry im dumb. as always, any suggestions would be much appreciated. thanks again!
Click to expand...
Click to collapse
You have no stock recovery, so no fastbootd.
Reflash stock recovery to get fastbootd back
Beetle84 said:
You have no stock recovery, so no fastbootd.
Reflash stock recovery to get fastbootd back
Click to expand...
Click to collapse
thank you,
i downloaded "XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip"
is must be the wrong one?
i used the recovery.img from that and did fastboot devices and it showed up so i did "fastboot flash recovery recovery.img" and it had no errors, it worked just fine so i tried fastboot reboot fastboot but i still got that long list of commands (((
i dont get it, what am i doing wrong?
uglyaf said:
thank you,
i downloaded "XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip"
is must be the wrong one?
i used the recovery.img from that and did fastboot devices and it showed up so i did "fastboot flash recovery recovery.img" and it had no errors, it worked just fine so i tried fastboot reboot fastboot but i still got that long list of commands (((
i dont get it, what am i doing wrong?
Click to expand...
Click to collapse
Like the other user did a couple of posts up, you probably have to update your adb/fastboot version.
Beetle84 said:
Like the other user did a couple of posts up, you probably have to update your adb/fastboot version.
Click to expand...
Click to collapse
ok thanks i did that and got version 1.4.3 it sees my device but when i did the fastboot reboot fastboot i got
fastboot: usage: unknown reboot target fastboot
and nothing happened. does anyone know what that means?
ok yes indeed im a huge idiot. i finally got into fastbootd because i downloaded ADB version R30. THATS the most recent adb version and that did the trick! now i got the fastbootd recovery screen!
regardless, thank you all SOOOOO much for taking the time to respond. much appreciated.
im so excited to get flashing!
peace and love
Boot twrp,( no need to flash) -fastboot boot (whatever you named the recovery img).img- then -adb reboot fastboot-
Should go to fastbootd. future reference
brucedroid031 said:
Boot twrp,( no need to flash) -fastboot boot (whatever you named the recovery img).img- then -adb reboot fastboot-
Should go to fastbootd. future reference
Click to expand...
Click to collapse
good look thank you