Related
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.
I'm trying to flash my stock recovery to recover from a bootloop, but for some reason none of the commands I try seem to work. fastboot devices shows my device info, and fastboot reboot reboots the phone. Those would indicate that fastboot is working, but when I try fastboot boot recovery.img terminal shows downloading 'boot.img' . . . and just hangs. Same thing when I try fastboot flash recovery recovery.img, terminal says sending recovery and just hangs. I'm not sure why this is happening. I'm new to tinkering with Android and am pretty out of my depth here, though I am learning. I think this may be happening because the bootloader is still locked (?) and that is preventing any changes to the recovery partition, but that's just a guess. The phone is rooted, but I don't know if the bootloader is unlocked or not. I've tried to find out using fastboot commands, but big surprise, they just hang too.
I have the proper drivers installed, phone is in fastboot mode, USB is plugged into the back of my PC, and i'm using the latest version of fastboot. I'm just not sure what i'm missing here. Has anyone else experienced something similar or can at least guide me in the right direction? Thanks.
Thanks for the reply. Yes this about the @#[email protected] Coolpad. To answer your questions, trying fastboot oem device-info returns "failed (command write failed (no error))". Unfortunately, finding a full stock ROM for this device has proven to be impossible. I've been searching for weeks without luck. Coolpad is a little known brand outside of China it seems. Even going to Yulong's website (Coolpads manufacturer) and relying on google translate to slog through all the Chinese text i've found no mention of this particular phone. Plenty of other Coolpad models, just not this one. And apparently Coolpad Quattro is the same in chinese as it is in english so I know I didn't miss anything because of translation.
Without a stock ROM to use, and with my stock recovery being overwritten it seems like the recovery.img that Flashify created is all I have to work with. As for your last question, i'm not sure what kitchen it is. The download was linked from a Youtube video about porting custom recoveries. It seems to be just a series of BAT files (unpackimg, repacking, and cleanup).
Okay guys, I'm in full panic mode. I was just getting ready to reinstall my X with Lineage OS. I had CM 13.0 up until now. I've backuped everything, then powered off my phone (simple, normal power down).
After that I was trying to get into TWRP (I had 2.x.x.x installed), but VolDown+Power got me in a boot loop. The OnePlus Logo flashes, phone vibrates short then reset and it flashes/vibrates again. I tried booting normally, that doesn't work either.
The only thing I can do is get into fastboot, but I can't flash anything! The phone says it's locked (though I unlocked it before I put CM 13.0 on it)
Code:
c:\Android>fastboot flash recovery twrp-3.1.1-1-onyx.img
target reported max download size of 536870912 bytes
sending 'recovery' (16002 KB)...
OKAY [ 0.505s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.509s
c:\Android>fastboot oem unlock
...
FAILED (remote: oem unlock is disabled)
finished. total time: 0.005s
c:\Android>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.010s]
finished. total time: 0.011s
Help! I can't boot my phone and I can't flash anything either. Is there anything I can do or missed?
After 2 hours of trying everything I found I'm now at a point where I could install the original (?) recovery via the MSM DownloadTool 2.0.2. Now I have a recovery which looks like stock... I can "Install from local" and "Install from USB". Tried the latter and I get the "adb sideload" mode. Tried to upload the latest Lineage OS Nightly through this sideload, but it fails after 47%.
If possible Flashing oos 3 might help or there's unbricking guide for opx you might want to see
intoxicated.mad said:
If possible Flashing oos 3 might help or there's unbricking guide for opx you might want to see
Click to expand...
Click to collapse
Thanks! That was actually the solution: the stock recovery can only flash OOS, it seems. I flashed OOS 3.1.4, then enabled oem unlock, flashed TWRP and Lineage.
Still no idea why my phone wouldn't boot after powering it off or why my bootloader was locked in the first place.
Anyway you got out of trouble ??
I have the exact same problem, only I am running Sultan's ROM. Unfortunately, my phone is not backed up, because I wasn't going to install a new rom or anything. Is there any way to restore my phone without losing data. I downloaded the MsmDownloadTool V2.0, and am wondering if I could replace the stock recovery.img in there with the one for my ROM, or would this not work?
Ok, so I tried replacing the recovery.img, and it didn't work, so I used the original one from the tool and dirty flashed OOS 3.1.4. All my original files and apps are still there, but none of them will open, except for google apps, which I assume came in the OOS ROM (Google Play works but says 'download pending' if I try to download an app). Unfortunately, this mix of software doesn't let me enable developer options in the settings (when I tap the build number nothing happens) so I can't use ADB to make a backup. I think the only way to get things working is to do a clean install OxygenOS, which would lose all my files. I'll think I'll try to use a file manager to copy the contents of the internal storage to a USB device, then do a full clean install.
Also, in this weird state of software, only the back button works, the home and recent apps keys don't, so if I do something in Chrome, I need to restart the phone to do something else
drunken_m said:
Thanks! That was actually the solution: the stock recovery can only flash OOS, it seems. I flashed OOS 3.1.4, then enabled oem unlock, flashed TWRP and Lineage.
Still no idea why my phone wouldn't boot after powering it off or why my bootloader was locked in the first place.
Click to expand...
Click to collapse
I also faced that issue too and it happens when you have installed custom rom or recovery without first unlocking the bootloader. Do It Now If you haven't
Actually the bootloader was already unlocked (I needed that to install CM in the first place), but I think I accidentally re-locked it when I tried to remove root (to install a banking app).
As I wrote I already fixed the issue by installing the original bootloader/recovery and OOS over a serial link, then unlocked the bootloader again and installed the latest TWRP And Lineage. So all is fine now.
adamantiumXT said:
Ok, so I tried replacing the recovery.img, and it didn't work, so I used the original one from the tool and dirty flashed OOS 3.1.4. All my original files and apps are still there, but none of them will open, except for google apps, which I assume came in the OOS ROM (Google Play works but says 'download pending' if I try to download an app). Unfortunately, this mix of software doesn't let me enable developer options in the settings (when I tap the build number nothing happens) so I can't use ADB to make a backup. I think the only way to get things working is to do a clean install OxygenOS, which would lose all my files. I'll think I'll try to use a file manager to copy the contents of the internal storage to a USB device, then do a full clean install.
Also, in this weird state of software, only the back button works, the home and recent apps keys don't, so if I do something in Chrome, I need to restart the phone to do something else
Click to expand...
Click to collapse
Rule #1 of flashing: always have a backup ready.
If you have TWRP installed and can get into recovery you can pull your files via ADB. After that I'd also recommend a clean install (full wipe).
drunken_m said:
Rule #1 of flashing: always have a backup ready.
If you have TWRP installed and can get into recovery you can pull your files via ADB. After that I'd also recommend a clean install (full wipe).
Click to expand...
Click to collapse
I have to agree, but I wasn't flashing when the phone decided to brick itself , so I didn't have a recent backup. In the bricked state I could only access fastboot mode, not recovery . I ended up copying what I could from the internal storage partition (which basically had everything I needed anyway), then clean installing a new ROM, and restoring my files.
For anyone else who gets into the same situation, I recommend that you make sure to not turn on WiFi or mobile data after you dirty flash OxygenOS, and remove your Google account. This will mean that Google's backup of your phone and apps (if you turned that feature on) will be of your working setup. As I tried to use Google Play in the messed up system, Google decided to replace my backup with the bad config so I couldn't restore in the new ROM - although looking at the Google Drive app now, the good setup is backed up, only I have no way to restore it
Maybe I have the same problem, not sure. I can't boot the phone. Holding vol down + power only makes the phone reboot over and over until I let go. It turns off afterwards, never enters recovery mode. I can access fastboot mode, but my bootloader is locked so I can't flash anything. Any suggestions?
Ciao tutti!
I have a T-Mobile DE2118 with Android 12 DE2118_11_C.16, SIM and bootloader unlocked. The goal is to get TWRP installed and to root the device. When I try to fastboot from Linux using either of the TWRP images from EnumC (twrp-3.5.2-11-holi.img and twrp-3.5.2-11-2-dre8t.img) I get this:
Code:
fastboot boot twrp-3.5.2-11-2-dre8t.img
downloading 'boot.img'...
OKAY [ 2.752s]
booting...
FAILED (remote: unknown command)
finished. total time: 2.752s
Is this expected because I have done something wrong? There are some additional steps for the DE2118? A different TWRP? Perhaps there is a special Windows fastboot as I have seen references to fastboot enhanced? I see detailed references for how to do things for the DE2117 but I believe I am missing something with this DE2118.
Thanks for some clues or help!
A working TWRP has not been ported to this device.
You can convert your device to STOCK OEM and root with my guides and this will also bring you up to C_17.
Thanks! In fact, yesterday I used your "Full Convert Tmobile...dummies" to prepare an old Windows-7 partition to do this but I have been working up the courage to make the attempt. It is reassuring to hear that I am on the right track.
katooom said:
Thanks! In fact, yesterday I used your "Full Convert Tmobile...dummies" to prepare an old Windows-7 partition to do this but I have been working up the courage to make the attempt. It is reassuring to hear that I am on the right track.
Click to expand...
Click to collapse
Make sure you install .net v4.5 on there before you install Fastboot Enhance
scanman0 said:
Make sure you install .net v4.5 on there before you install Fastboot Enhance
Click to expand...
Click to collapse
Thanks! By chance, it seems that I already had .net 4.8 installed from 2019. However, during setup I did have to setup the Visual Studio 2015 redistributable package.
katooom said:
Ciao tutti!
I have a T-Mobile DE2118 with Android 12 DE2118_11_C.16, SIM and bootloader unlocked. The goal is to get TWRP installed and to root the device. When I try to fastboot from Linux using either of the TWRP images from EnumC (twrp-3.5.2-11-holi.img and twrp-3.5.2-11-2-dre8t.img) I get this:
Code:
fastboot boot twrp-3.5.2-11-2-dre8t.img
downloading 'boot.img'...
OKAY [ 2.752s]
booting...
FAILED (remote: unknown command)
finished. total time: 2.752s
Is this expected because I have done something wrong? There are some additional steps for the DE2118? A different TWRP? Perhaps there is a special Windows fastboot as I have seen references to fastboot enhanced? I see detailed references for how to do things for the DE2117 but I believe I am missing something with this DE2118.
Thanks for some clues or help
Click to expand...
Click to collapse
here is a working .IMG file for the Nord N200 DE2118. for some reason it won't let me upload it
Working TWRP for OnePlus Nord N200 .img file why won't it let me upload it
The problem is that's for Android 11, your running android 12. Best case scenario you brick your device
I know this from personal experience lol
katooom said:
Ciao tutti!
I have a T-Mobile DE2118 with Android 12 DE2118_11_C.16, SIM and bootloader unlocked. The goal is to get TWRP installed and to root the device. When I try to fastboot from Linux using either of the TWRP images from EnumC (twrp-3.5.2-11-holi.img and twrp-3.5.2-11-2-dre8t.img) I get this:
Code:
fastboot boot twrp-3.5.2-11-2-dre8t.img
downloading 'boot.img'...
OKAY [ 2.752s]
booting...
FAILED (remote: unknown command)
finished. total time: 2.752s
Is this expected because I have done something wrong? There are some additional steps for the DE2118? A different TWRP? Perhaps there is a special Windows fastboot as I have seen references to fastboot enhanced? I see detailed references for how to do things for the DE2117 but I believe I am missing something with this DE2118.
Thanks for some clues or help!
Click to expand...
Click to collapse
If your trying to root, use magisk.
I have two N200.
I successfully rooted both of them. Some how the second phone got updated to android 12 and lost the root. Ever since this is a headache. Phone is already unlocked boot loader and shows "Device state - unlocked" in fastboot mode.
I wanted to try booting from the patched boot.img i had earlier (From version 11 i assume) just to see if it works but the command fails:
fastboot boot boot.img
Sending 'boot.img' (98304 KB)
Booting Failed (remote: 'unknown command')
fastboot: error: Command failed
Also maybe this is due to being on android 12? If so how can i downgrade? I downloaded the zip file from:
Software Upgrade - OnePlus.com
Get the latest OxygenOS updates for your device.OxygenOS is always evolving. Learn about the latest features and improvements, and get even more out of your device.
www.oneplus.com
Thank you.
First, I don't think you can use your previous boot. Scanman has a thread on this forum with all pre-rooted boot files, you just need to match according to the FW you're on. Second, after A12 they don't allow fastboot boot anymore, the file has to be flashed instead with fastboot flash.
Again, make sure you use the correct boot otherwise it won't work and you may cause yourself a bigger headache.