Related
After many searches to no avail, I figured I'd open a thread and see what's going on.
I recently purchased a Nexus One that was rooted and had an unlocked bootloader. The hboot is 0.33.2012 with radio 5.12.00.00
I am trying to convert back to stock so I can access Gingerbread when it goes OTA. I have tried 20 times now to use the PASSIMG.zip method of reverting and every single time, some text loads very fast, and the last thing I see is something along the lines of:
"Loading... [nv.img]"
Is there anyone that can suggest an easy fix? I have tired using FRG33 and FRF91, but both will not work. With my luck, I'm just doing something nubish. Any help would be greatly appreciated.
Well this should work : I replied to you via the twitters - but I'll post this here for posterity.
@du57in Ok I'll bite. I restored my N1 to stock due to wifi issues yesterday. Download FRG83 from here http://tinyurl.com/26jy7tt
@du57in Step 2: follow the steps in this thread http://tinyurl.com/2dlmzsl using the FRG83 from the first link
@du57in You're going to want to use the first FRG83 listed in bold MD5: a801dcc43e9244d323e57bbd5705eaea
Here's my summary:
Download that original signed HTC FRG83 image
setup fastboot if you haven't already
unzip it
Plug in Nexus One with USB to computer (enable usb and debug modes)
$ adb reboot bootloader
(which will boot into the bootloader)
Confirm fastboot connection
$ fastboot devices
$ fastboot erase userdata
- did not work for me, I went into the bootloader recovery and wiped the data on my device instead
$ fastboot erase cache
Go to the directory that you stored your unzipped files.
$ fastboot flash userdata userdata.img
(I actually skipped this one, but you might want to flash it since you're coming from a custom rom)
$ fastboot flash boot boot.img
$ fastboot flash system system.img
$ fastboot reboot
OK, I'm working on that and I will update with what happens.
Goodluck with fastboot. Theres always the throwing it against the wall method if fastboot fails.
Fastboot never fails. NEVER
7on said:
Well this should work : I replied to you via the twitters - but I'll post this here for posterity.
@du57in Ok I'll bite. I restored my N1 to stock due to wifi issues yesterday. Download FRG83 from here http://tinyurl.com/26jy7tt
@du57in Step 2: follow the steps in this thread http://tinyurl.com/2dlmzsl using the FRG83 from the first link
@du57in You're going to want to use the first FRG83 listed in bold MD5: a801dcc43e9244d323e57bbd5705eaea
Here's my summary:
Download that original signed HTC FRG83 image
setup fastboot if you haven't already
unzip it
Plug in Nexus One with USB to computer (enable usb and debug modes)
$ adb reboot bootloader
(which will boot into the bootloader)
Confirm fastboot connection
$ fastboot devices
$ fastboot erase userdata
- did not work for me, I went into the bootloader recovery and wiped the data on my device instead
$ fastboot erase cache
Go to the directory that you stored your unzipped files.
$ fastboot flash userdata userdata.img
(I actually skipped this one, but you might want to flash it since you're coming from a custom rom)
$ fastboot flash boot boot.img
$ fastboot flash system system.img
$ fastboot reboot
Click to expand...
Click to collapse
This will not revert your recovery to stock. The OTA will still fail.
mortzz said:
This will not revert your recovery to stock. The OTA will still fail.
Click to expand...
Click to collapse
Yes it will, smart ass
Make sure your downloads aren't corrupt. That was my noobish mistake just yesterday haha
Rusty! said:
Yes it will, smart ass
Click to expand...
Click to collapse
+1, I believe recovery will be reflashed after the next reboot.
get the ota or not be sure that it will be available online for rooted users
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
I Can't flash recovery for my moto x, I have unlocked the bootloader and appears to me on fastboot: Device is UNLOCKED. Status Code:3
I don't know if this is right, but I can't flash a recovery in it.
Error:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8030 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.116s
I tested various recovery's but don't work.
Sorry for my bad english
Murilo900 said:
I Can't flash recovery for my moto x, I have unlocked the bootloader and appears to me on fastboot: Device is UNLOCKED. Status Code:3
I don't know if this is right, but I can't flash a recovery in it.
Error:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8030 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.116s
I tested various recovery's but don't work.
Sorry for my bad english
Click to expand...
Click to collapse
Are you using mfastboot? You should be..
Sent From Droid Ultra
In addition to mFastboot, make sure your battery is charged more than 80%
Caseyk621 said:
Are you using mfastboot? You should be..
Sent From Droid Ultra
Click to expand...
Click to collapse
KidJoe said:
In addition to mFastboot, make sure your battery is charged more than 80%
Click to expand...
Click to collapse
Yes,
I did on mfastboot and appears the same thing, and the battery is full, when I try to flash on moto x appears : getvar-download-size
Murilo900 said:
Yes,
I did on mfastboot and appears the same thing, and the battery is full, when I try to flash on moto x appears : getvar-download-size
Click to expand...
Click to collapse
What ROM is on your phone right now? Which recovery are you trying to flash?
What state was your phone in when you started trying to flash recovery?
KidJoe said:
What ROM is on your phone right now? Which recovery are you trying to flash?
What state was your phone in when you started trying to flash recovery?
Click to expand...
Click to collapse
The ROM on my phone is 4.4.2 KitKat, I tried to flash twrp recovery 2.6.3.1 and cwm recovery for motox
The state was the same, I unlocked bootloader, following tutorials on internet but I'm stuck on flash the recovery because this problem, I get this error and on my phone appears getvar-download-size, and Download Failed.
Murilo900 said:
The ROM on my phone is 4.4.2 KitKat, I tried to flash twrp recovery 2.6.3.1 and cwm recovery for motox
The state was the same, I unlocked bootloader, following tutorials on internet but I'm stuck on flash the recovery because this problem, I get this error and on my phone appears getvar-download-size, and Download Failed.
Click to expand...
Click to collapse
Ok.
Try the mfastboot from inside -> http://mark.cdmaforums.com/X-STUFF/Mfastboot-4.4.zip (will have to rename fastboot.exe to mfastboot.exe).. or from -> http://mark.cdmaforums.com/X-STUFF/ADB-MFASTBOOT.zip they are the ones I use and they have worked for me.
and is this the twrp you are using? -> http://goo.im/devs/Hashcode/motox/unlocked/twrp-2.6.3.1-ghost-4.4.img
Oh god! Thanks, this mfastboot you just send works!, I don't know if the problem was my mfastboot that I have here, but finally I flashed! Leveraging the topic can you suggest me some roms for moto x, and if you know some way to take off the boot the sign that the bootloader is unlocked blablabla, Anyway thank you.
Murilo900 said:
Oh god! Thanks, this mfastboot you just send works!, I don't know if the problem was my mfastboot that I have here, but finally I flashed! Leveraging the topic can you suggest me some roms for moto x, and if you know some way to take off the boot the sign that the bootloader is unlocked blablabla, Anyway thank you.
Click to expand...
Click to collapse
I run stock, unlocked and rooted, so I can't suggest an alternate roms.
As for the unlocked bootloader warning message... sure. there is a big thread -> http://forum.xda-developers.com/moto-x/themes-apps/moto-x-boot-logos-t2417961 start around post 150 of that thread for how to make your own... in a couple of hours I'll refresh this file -> http://mark.cdmaforums.com/X-STUFF/X-LogoBins.zip adding even more logo.bin files (i have about 7 or 8 more to test before I can re-zip and upload it)
HELP!!
I am at a loss. No matter what fastboot/mfastboot I use, no matter what YouTube video I follow, I can not flash recovery.
I get the same error as the OP. I tried the links posted a few posts up, it wont work.
I type the commands, I get the top error message (among others depending on the mfastboots I try) and then nothing.
I am truly at a loss.
Verizon Developer Moto X
4.4.2
Device is: Unlocked
Status Code: 3
In one video I watched it said that I needed to have it say Status Code:1. Is that where I am going wrong?
Any help would be greatly appreciated.
Thanks!!
n99hockey said:
I am at a loss. No matter what fastboot/mfastboot I use, no matter what YouTube video I follow, I can not flash recovery.
I get the same error as the OP. I tried the links posted a few posts up, it wont work.
I type the commands, I get the top error message (among others depending on the mfastboots I try) and then nothing.
I am truly at a loss.
Verizon Developer Moto X
4.4.2
Device is: Unlocked
Status Code: 3
In one video I watched it said that I needed to have it say Status Code:1. Is that where I am going wrong?
Any help would be greatly appreciated.
Thanks!!
Click to expand...
Click to collapse
What recovery are you trying to flash? Stock or other? Unlocked Status Code 3 is needed to flash an alternate or 3rd party recovery.
Besides the error listed in the first post, exactly what "others" do you see as error codes?
Things to try... (in no special order)
this mfastboot -> mfastboot-442.zip
re-download the recovery you are trying to flash
update your ADB and Platform Tools
There are several versions of TWRP that can work.
Unofficial TWRP 2.6.3.1 for 4.4 -> http://goo.im/devs/Hashcode/motox/unlocked/twrp-2.6.3.1-ghost-4.4.img
Unofficial TWRP 2.7.0.0 -> http://androidhosting.org/Devs/Dhacker29/MotoX/TWRP-2.7.0.0-moto_msm8960dt.img
Official TWRP 2.7.1.1 -> http://techerrata.com/browse/twrp2/ghost
of those, I've only used the 2.6.3.1 on my VZW Dev X with 4.4.2 and below.
KidJoe said:
What recovery are you trying to flash? Stock or other? Unlocked Status Code 3 is needed to flash an alternate or 3rd party recovery.
Besides the error listed in the first post, exactly what "others" do you see as error codes?
Things to try... (in no special order)
this mfastboot -> mfastboot-442.zip
re-download the recovery you are trying to flash
update your ADB and Platform Tools
There are several versions of TWRP that can work.
Unofficial TWRP 2.6.3.1 for 4.4 -> http://goo.im/devs/Hashcode/motox/unlocked/twrp-2.6.3.1-ghost-4.4.img
Unofficial TWRP 2.7.0.0 -> http://androidhosting.org/Devs/Dhacker29/MotoX/TWRP-2.7.0.0-moto_msm8960dt.img
Official TWRP 2.7.1.1 -> http://techerrata.com/browse/twrp2/ghost
of those, I've only used the 2.6.3.1 on my VZW Dev X with 4.4.2 and below.
Click to expand...
Click to collapse
Thanks for the reply.
However I should have known better, I changed the USB port and it worked just fine with the mfastboot I downloaded longer than I would like to admit before I posted my question.
</sigh>
Still can't flash custom recovery
I have a Verizon XT1060 Developer Edition. Unlocked bootloader. Drivers seem to be installed correctly, "Fastboot devices" identifies the phone. Battery is 90%+. Fastboot menu says "Device is unlocked. Status Code 3". I have tried different USB ports on the PC, different cables to connect the phone and just about every other variable that I can think of.
I have followed all of the suggestions listed in this post and I still cannot flash a custom recovery. I have tried multiple versions of TWRP, Fastboot, Mfastboot etc.. Here is the error message...
(bootloader) Variable not supported!
error: cannot open 'twrp-2.6.3.1-ghost-4.4.img'
Actually depending on the method I am trying at the time, fastboot mfastboot etc., I may get a couple of additional lines that mention Max download size etc. but it always starts with the bootloader comment and ends with "Cannot open......"
Searching for "(bootloader) Variable not supported!" returns a lot of hits but I have not found anything to clear the issue. Any help would be appreciated.
Ric214 said:
....Here is the error message...
(bootloader) Variable not supported!
error: cannot open 'twrp-2.6.3.1-ghost-4.4.img'
...
Click to expand...
Click to collapse
That usually means that mFastboot (or fastboot) can't find the IMG file on your PC.
My first question would be... does that file exist in your current directory/folder?
i.e... at the command prompt.. type dir *.img is the twrp file listed there? If no, that is your issue. change to the folder (directory) where the TWRP IMG file is, and try it.
It is there. Here is what I got.
C:\Users\Ric\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x86
_64-20140321\sdk\platform-tools>dir *.img
Volume in drive C is OS
Volume Serial Number is 76F9-C97B
Directory of C:\Users\Ric\Downloads\adt-bundle-windows-x86_64-20140321\adt-bund
le-windows-x86_64-20140321\sdk\platform-tools
06/13/2014 10:54 PM 8,417,280 openrecovery-twrp-2.7.1.1-ghost.img
06/03/2014 11:10 PM 10,090,496 twrp-2.6.3.1-ghost-4.4.img
2 File(s) 18,507,776 bytes
0 Dir(s) 426,324,336,640 bytes free
Since this has been driving me crazy for a couple of days I have several folders with different versions of Fastboot and Mfastboot in them along with some different versions of TWRP and CWM and I am getting the same error with all of them. This last time I just stuck the TWRP file in my platform -tools folder to try and make sure I had a good Fastboot file.
Thanks for the reply. If you have any other ideas I am eager to hear them.
Ric214 said:
It is there. Here is what I got.
C:\Users\Ric\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x86
_64-20140321\sdk\platform-tools>dir *.img
Volume in drive C is OS
Volume Serial Number is 76F9-C97B
Directory of C:\Users\Ric\Downloads\adt-bundle-windows-x86_64-20140321\adt-bund
le-windows-x86_64-20140321\sdk\platform-tools
06/13/2014 10:54 PM 8,417,280 openrecovery-twrp-2.7.1.1-ghost.img
06/03/2014 11:10 PM 10,090,496 twrp-2.6.3.1-ghost-4.4.img
2 File(s) 18,507,776 bytes
0 Dir(s) 426,324,336,640 bytes free
Since this has been driving me crazy for a couple of days I have several folders with different versions of Fastboot and Mfastboot in them along with some different versions of TWRP and CWM and I am getting the same error with all of them. This last time I just stuck the TWRP file in my platform -tools folder to try and make sure I had a good Fastboot file.
Thanks for the reply. If you have any other ideas I am eager to hear them.
Click to expand...
Click to collapse
Had you made ANY prior modifications to your unit before now? Any possibility you used one of the previous root/write protect disable exploits, and THEN got the bootloader unlocked?
I've seen alot of users in this situation recently -thanks to middleman
I suggest you follow the 'return to stock' thread here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
You should flash the 4.4.2 VZW SBF file from here: http://sbf.droid-developers.org/phone.php?device=0
SBFing back to stock is very different from a Factory Reset in that it can actually repair a damaged filesystem, and even un-do any previous exploits you may have used.
There are 2 methods - many report that the "Manual Method" is easier than using RSD Lite. Either should work equally well, but pay close attention to the steps.
You will want to do a couple of things just a little bit differently. First, use mfastboot as suggested by KidJoe for ALL flashing commands.
Second, once your phone has been placed into bootloader mode (AP Fastboot), before you proceed with the fastboot commands listed under Manual Method, do this first:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
Your device should reboot back to the bootloader. NOW, proceed with the entire list of commands (using mfastboot for all of them). Yes, you will be flashing partition and motoboot again...don't worry. It is intentional.
After you have completed the rest of the steps, you will likely be able to flash TWRP (or custom recovery of your choice) without issue.
Let us know if this fixes your issues.
samwathegreat said:
Had you made ANY prior modifications to your unit before now? Any possibility you used one of the previous root/write protect disable exploits, and THEN got the bootloader unlocked?
I've seen alot of users in this situation recently -thanks to middleman
I suggest you follow the 'return to stock' thread here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
You should flash the 4.4.2 VZW SBF file from here: http://sbf.droid-developers.org/phone.php?device=0
SBFing back to stock is very different from a Factory Reset in that it can actually repair a damaged filesystem, and even un-do any previous exploits you may have used.
There are 2 methods - many report that the "Manual Method" is easier than using RSD Lite. Either should work equally well, but pay close attention to the steps.
You will want to do a couple of things just a little bit differently. First, use mfastboot as suggested by KidJoe for ALL flashing commands.
Second, once your phone has been placed into bootloader mode (AP Fastboot), before you proceed with the fastboot commands listed under Manual Method, do this first:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
Your device should reboot back to the bootloader. NOW, proceed with the entire list of commands (using mfastboot for all of them). Yes, you will be flashing partition and motoboot again...don't worry. It is intentional.
After you have completed the rest of the steps, you will likely be able to flash TWRP (or custom recovery of your choice) without issue.
Let us know if this fixes your issues.
Click to expand...
Click to collapse
I had not done any modifications prior to unlocking the bootloader but going back to stock is about the only thing that I could think of that I have not already tried. I will give this a shot tomorrow night and let you know how it went. Thanks for your help.
Ric214 said:
I had not done any modifications prior to unlocking the bootloader but going back to stock is about the only thing that I could think of that I have not already tried. I will give this a shot tomorrow night and let you know how it went. Thanks for your help.
Click to expand...
Click to collapse
One last thing I can suggest before return to stock:
Are you trying to flash the recovery -while booted into Android-? If so, you have to have USB Debugging enabled. Some users have experienced difficulty using fastboot while booted into Android even with USB debugging enabled.
----------------
You can try flashing from bootloader (AP Fastboot Mode) instead.
To do this, unplug the phone from USB. Power off the phone. Hold down VOL DOWN and power the phone back on. You should now be booted into bootloader.
Now plug the USB back in, and try:
mfastboot flash recovery twrp_filename.img
samwathegreat said:
One last thing I can suggest before return to stock:
Are you trying to flash the recovery -while booted into Android-? If so, you have to have USB Debugging enabled. Some users have experienced difficulty using fastboot while booted into Android even with USB debugging enabled.
----------------
You can try flashing from bootloader (AP Fastboot Mode) instead.
To do this, unplug the phone from USB. Power off the phone. Hold down VOL DOWN and power the phone back on. You should now be booted into bootloader.
Now plug the USB back in, and try:
mfastboot flash recovery twrp_filename.img
Click to expand...
Click to collapse
Thanks for the advice but I am not booted into Android. I started with the phone off and got into the bootloader exactly as you suggested. I will have some time over the next few days to flash back to stock and start over again. I will post the results. In the meantime if you think of anything else, let me know. Thanks for your help.
Ric214 said:
Thanks for the advice but I am not booted into Android. I started with the phone off and got into the bootloader exactly as you suggested. I will have some time over the next few days to flash back to stock and start over again. I will post the results. In the meantime if you think of anything else, let me know. Thanks for your help.
Click to expand...
Click to collapse
try shortening the path the IMG resides in...
i.e. make a folder off the root of drive C call it FLASH... drop the TWRP.img into c:\flash and try flashing it from there.
Updated to latest firmware using fastboot successful, flashed latest twrp recovery - said success. Says entering recovery then hangs loading from fastboot or manually. April 2014 drivers. Windows 8.1. Bell(at&t) phone. Supercid s-off. Boots fine I'm using it right now. Any solutions someones could offer? Thanksgiving:cyclops:
Cray0la said:
Updated to latest firmware using fastboot successful, flashed latest twrp recovery - said success. Says entering recovery then hangs loading from fastboot or manually. April 2014 drivers. Windows 8.1. Bell(at&t) phone. Supercid s-off. Boots fine I'm using it right now. Any solutions someones could offer? Thanksgiving:cyclops:
Click to expand...
Click to collapse
Code:
fastboot flash recovery <name of recovery>.img
[B]fastboot erase cache[/B]
and make sure MD5 of the recovery is correct
Requirements:
you need to have a pc with adb working
a stock firmware on your device (any)
unlocked bootloader
a working backup just in case
Pro:
you will not lose your data / application
Cons:
you will lose all system modification (root, busybox, custom kernel...)
you'll take all the risk of operation (I've tested on my device)
Guide:
some file names changes depending on version so please complete the {version_here} placeholder with the file you download
* prepend "sudo" on command line if you are on a Linux machine
download last version for your device here (if you want to root download the zip file in the section below to speed up the operations)
extract
extract image-{device_here}-{version_here}.zip in the same folder (no subdir)
command line* (or reboot device with vol down pressed):
Code:
adb reboot bootloader
command line*:
Code:
cd {your_path_here}
command line*:
Code:
fastboot flash bootloader bootloader-{device_here}-{version_here}.img
command line*:
Code:
fastboot reboot-bootloader
command line*:
Code:
fastboot flash radio radio-{device_here}-{version_here}.img
command line*:
Code:
fastboot flash system system.img
command line*:
Code:
fastboot flash boot boot.img
ONLY IF YOU FOUND A VENDOR.IMG IN THE ZIP command line*:
Code:
fastboot flash vendor vendor.img
command line*:
Code:
fastboot flash cache cache.img
command line*:
Code:
fastboot reboot
Now you have the lastest stock image and all your data.
Change recovery (TWRP) and root:
Note that we haven't flash the stock recovery, but during every boot of an unmodified system there's a script that do that (supersu usually deactive this behavior during install).
If you had TWRP installed and the SuperSU zip on your device, at the end of the above procedure you can boot directly from bootloader to recovery and go directly to last step:
download: TWRP image (twrp-{version_here}-{device_here}.img) for your device
download: chainfire SuperSU 2.71 on your device
command line*:
Code:
fastboot flash recovery twrp-{version_here}-{device_here}.img
alternatively you can keep the original recovery and use TWRP one time with
Code:
fastboot boot twrp-{version_here}-{device_here}.img
boot in recovery and flash supersu zip
working fine for me, all correct, thanks
Just tried with flash_all.bat. I'm getting the message "Can not generate image". How can I solve this, please?
Thank you, works like a charm!
Same here, cant flash system
There's not flash-all.bat in my steps (that delete you data!), can't give help about it sorry
i've gone your way, but i tried also the flash-all.bat with the -w switch, didnt work.
Tnx mate. Helped a lot
Cant flash the system.img manually. All the other img are working. I get this error message :
Code:
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
The old system.img from lrx22c works also.
Someone know whats going on?
Sp0KI said:
Cant flash the system.img manually. All the other img are working. I get this error message :
Code:
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
The old system.img from lrx22c works also.
Someone know whats going on?
Click to expand...
Click to collapse
I think that all who has flashed the developer preview got an broken filesystem or the partitions missmatch.
Before i used the preview the -w update flag worked well to rebuild the partitions, now it didnt work anymore, tried all factory images don to 4.4
c3k said:
Requirements:
you need to have a pc with adb working
a stock firmware on your device (any)
a working backup just in case
Click to expand...
Click to collapse
so if i have twrp, before i have to return stock 5.0.1??
or i flash directly 5.1 over twrp?
tnx
chikess said:
I think that all who has flashed the developer preview got an broken filesystem or the partitions missmatch.
Before i used the preview the -w update flag worked well to rebuild the partitions, now it didnt work anymore, tried all factory images don to 4.4
Click to expand...
Click to collapse
I didn't flash the preview.
Sp0KI said:
I didn't flash the preview.
Click to expand...
Click to collapse
Hmm ok, but u got the same problems. So, in this way we had to wait for a flashable zip or maybe ota.
@c3k why do you mention to flash twrp while in steps above stock recovery is not included to flash... ? Doesn't that mean that custom recovery (twrp) is still on device?
Doesn't this require an unlocked bootloader, and not necessarily root, or am I confused?
Sp0KI said:
Cant flash the system.img manually. All the other img are working. I get this error message :
Code:
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
The old system.img from lrx22c works also.
Someone know whats going on?
Click to expand...
Click to collapse
Are you using the latest version for the fastboot.exe file?
foosion said:
Doesn't this require an unlocked bootloader, and not necessarily root, or am I confused?
Click to expand...
Click to collapse
This requires an unlocked bootloader. But, there are users like us who have rooted the stock ROM.
This guide is meant for the users who has unlocked bootloader with rooted stock ROM.
This guide will also work for phones with unlocked bootloaders with STOCK ROM(rooted or un-rooted).
efrant said:
Are you using the latest version for the fastboot.exe file?
Click to expand...
Click to collapse
I had faced the same issue while flashing LRX22C. It got fixed by rebooting the phone and switching the cable to a different USB port. Might work for him too.
PS: I have flashed the images from Linux.
In my case I guess all the issues are from a previous attempt to flash OptiPop ROM. The flashing process it's a little tricky to understand (with that F2FS file system). I remember that after flashed OptiPop and the phone didn't boot, I tried to restore to stock ROM and it was a lot of errors until it worked fine again.
efrant said:
Are you using the latest version for the fastboot.exe file?
Click to expand...
Click to collapse
I'm using the newest Minimal ADB.
The strange thing is, that i can flash the LRX22C system.img and all other new lmy47d files but not the lmy47d system.img.
I guess i'll wait for the OTA update and hope it works then.
Tried rebooting and switching port and usb cabel..
You actually don't need to manually install supersu or root. Flash the 5.1 images and then (after the first full boot) flash twrp.
Once you boot into twrp and exit out of it, you will be promoted with a message that your phone is not rooted, and you're asked if you want to install supersu. It's built into twrp.
If you're like me and tried out some of the roms and hosed yourself, I just managed to recover this. I got here by doing the below:
Used rootjunkys AmazonFire5thGenSuperTool and disabled OTA, Root the device, install Flashfire, Set Nova as default
Then I used Flashfire to flash forum.xda-developers.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714 Fire Nexus ROM - LMY49G [09 Feb 2016]
Installed Flashfire.apk from AmazonFire5thGenSuperTool
Attempted to flash [UNOFFICIAL] CM-12.1 and that's where it Flashfire borked and I was hosed
Your symptoms are:
Power+Volume Down or Up get you either FASTBOOT => or RECOVERY =>
Just powering on with no buttons pressed you you get the CM recovery flashing thingy
At this point you appear hosed, but here's what I did. After correctly setting up ADB and Fastboot, download the below
http://rootjunkysdl.com/getdownload...h gen/SuperTool/AmazonFire5thGenSuperTool.zip
http://rootjunkysdl.com/getdownload...ate-kindle-global-37.5.4.1_user_541112720.bin
https://www.androidfilehost.com/?fid=24269982086987951 2015-11-04-cm-12-recovery.img
Unzip AmazonFire5thGenSuperTool.zip. Copy 2015-11-04-cm-12-recovery.img and update-kindle-global-37.5.4.1_user_541112720.bin into the AmazonFire5thGenSuperTool\files directory. Now do the below:
Boot to FASTBOOT=> with power+volume up (I can't remember which to be honest)
fastboot.exe boot 2015-11-04-cm-12-recovery.img
select apply update, then choose adb
then do adb sideload update-kindle-global-37.5.4.1_user_541112720.bin
it will take a while but you should see "Total xfer: 1.00x" at the end
then fastboot reboot
You should see the Fire logo. Hope that helps someone...I can tell you I was sure bummed when this happened to me
I Dont Get It
Could you help me out here?
When I type fastboot.exe boot 2015-11-04-cm-12-recovery.img I get the following:
downloading 'boot.img'...
OKAY [ 0.239s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.251s
I'm not sure what i'm doing wrong. Any suggestions?
So.Far.Gone said:
Could you help me out here?
When I type fastboot.exe boot 2015-11-04-cm-12-recovery.img I get the following:
downloading 'boot.img'...
OKAY [ 0.239s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.251s
I'm not sure what i'm doing wrong. Any suggestions?
Click to expand...
Click to collapse
Can you verify that you don't have the Amazon Recovery using power+volume down? Power+volume up is FASTBOOT, and every recovering, I get that same message as well.
DigiAngel69 said:
Can you verify that you don't have the Amazon Recovery using power+volume down? Power+volume up is FASTBOOT, and every recovering, I get that same message as well.
Click to expand...
Click to collapse
Yes, this is true, I don't have Amazon Recovery. But I do get FASTBOOT.
So.Far.Gone said:
Yes, this is true, I don't have Amazon Recovery. But I do get FASTBOOT.
Click to expand...
Click to collapse
What do you get when you hold power and volume up? Just the RECOVERY=> thing?
DigiAngel69 said:
What do you get when you hold power and volume up? Just the RECOVERY=> thing?
Click to expand...
Click to collapse
When I hold Power, and Volume up, it shows small white text in the corner that reads "=> FASTBOOT...". But when I use Volume down, and Power, It freezes on the boot logo.
So.Far.Gone said:
When I hold Power, and Volume up, it shows small white text in the corner that reads "=> FASTBOOT...". But when I use Volume down, and Power, It freezes on the boot logo.
Click to expand...
Click to collapse
Ah....alas I am not familiar with a device that isn't able to get to RECOVERY=> I suspect you have a different issue
DigiAngel69 said:
Ah....alas I am not familiar with a device that isn't able to get to RECOVERY=> I suspect you have a different issue
Click to expand...
Click to collapse
Then what are the instructions above for?
They are for folks that can get to FASTBOOT=> and RECOVERY=>...like the situation I was in.
Sorry DigiAngel, you are mistaken here
DigiAngel69 said:
fastboot.exe boot 2015-11-04-cm-12-recovery.img
Click to expand...
Click to collapse
This does not work on normal 5.1.1 devices.
So.Far.Gone said:
When I type fastboot.exe boot 2015-11-04-cm-12-recovery.img I get the following:
downloading 'boot.img'...
OKAY [ 0.239s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.251s
I'm not sure what i'm doing wrong. Any suggestions?
Click to expand...
Click to collapse
You are doing nothing wrong. This just doesn't work on normal 5.1.1 devices. "FAILED (remote: unknown command)" is always the result on a these devices.
Amazon removed the ability to boot images from fastboot. This can only be done on 5.0, 5.0.1 devices. And also on devices which have been upgraded to 5.1.1 through a specific safe multi-step procedure. There is a how-to thread with details.
---------- Post added at 01:41 PM ---------- Previous post was at 01:32 PM ----------
DigiAngel69 said:
They are for folks that can get to FASTBOOT=> and RECOVERY=>...like the situation I was in.
Click to expand...
Click to collapse
People who can still access the stock amazon recovery ( RECOVERY=> ) and who are on 5.1.1 can reinstall FireOS 5.1.1 through amazon's recovery. The people who are bricked on 5.1.1 are those who can not access the stock amazon recovery.
blueberry.sky said:
Sorry DigiAngel, you are mistaken here
This does not work on normal 5.1.1 devices.
You are doing nothing wrong. This just doesn't work on normal 5.1.1 devices. "FAILED (remote: unknown command)" is always the result on a these devices.
Amazon removed the ability to boot images from fastboot. This can only be done on 5.0, 5.0.1 devices. And also on devices which have been upgraded to 5.1.1 through a specific safe multi-step procedure. There is a how-to thread with details.
---------- Post added at 01:41 PM ---------- Previous post was at 01:32 PM ----------
People who can still access the stock amazon recovery ( RECOVERY=> ) and who are on 5.1.1 can reinstall FireOS 5.1.1 through amazon's recovery. The people who are bricked on 5.1.1 are those who can not access the stock amazon recovery.
Click to expand...
Click to collapse
Hrmmm...this device was just ordered 3 weeks ago and came with 5.1.1 on it. Is it possible this was upgraded? Very confusing.
Your Fire came new from amazon? And not a replacement for a defective Fire, right? I understand they may send refurbished Fires as warranty replacements.
The fact that we can't boot our custom recovery images (twrp or CM recovery) on 5.1.1 has been (and continues to be) a serious problem. No one has reported a normal 5.1.1 device that can load anything via fastboot.
Did you see FireOS 5.1.1 listed in settings before you flashed a custom rom?
Note that a 5.0.1 or 5.1.1 device only refers to the FireOS version, not any custom rom you might have flashed. For example, I have 5.0.1 devices with SlimLP 5.1.1 on them. It's still a 5.0.1 device as long as FireOS 5.1.1 never got on it (through a normal way).
DigiAngel69 said:
Is it possible this was upgraded?
Click to expand...
Click to collapse
You should remember if you did the process to upgrade to FireOS 5.1.1 while still keeping the old 5.0.1 fastboot & preloader. It's a multi step process, you would have had to follow a how-to thread.
---------- Post added at 10:09 AM ---------- Previous post was at 10:01 AM ----------
Try to do this part again on your Fire
DigiAngel69 said:
Boot to FASTBOOT=> with power+volume up (I can't remember which to be honest)
fastboot.exe boot 2015-11-04-cm-12-recovery.img
Click to expand...
Click to collapse
By the way, power+volume up is indeed the correct combo to get into fastboot.
Your Fire should show:
downloading 'boot.img'...
OKAY [ 0.239s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.251s
I believe you previously had 5.0.1 so it worked the first time. But you flashed 5.1.1 at this step:
DigiAngel69 said:
then do adb sideload update-kindle-global-37.5.4.1_user_541112720.bin
Click to expand...
Click to collapse
So at that point you upgraded from 5.0.1 to 5.1.1. And you should be no longer able to load anything via fastboot.
Hrmmm. I can tell you that out of the box this was Fire 5.1.1. I had to use FlashFire to do anything out of the box, so I believe this really was 5.1.1. After doing the adb sideload, I now have the official amazon recovery menu back, if that helps or shows what version or anything like that. I can tell you that I've now done my initial process of using the SuperTool on two other tablets and these also came out of the box with 5.1.1. So I dunno...maybe these were different...I can say that I can still fastboot the recovery.img....so who knows. I hope folks get their stuff unbricked though.
DigiAngel69 said:
I can tell you that out of the box this was Fire 5.1.1. I had to use FlashFire to do anything out of the box, so I believe this really was 5.1.1.
Click to expand...
Click to collapse
If you can load CM recovery then you do not need to use FlashFire.
And the ability to load custom recovery via fastboot shows that it's a 5.0.1 device.
DigiAngel69 said:
I can say that I can still fastboot the recovery.img....so who knows.
Click to expand...
Click to collapse
If you can still load a recovery via fastboot then it seems CM recovery is unable to flash anything other than the rom. Normally, when flashing the FireOS 5.1.1 update file using amazon's recovery, it actually flashes more than just the rom. It also changes fastboot, killing our ability to load recoveries via fastboot.
You flashed 5.1.1 but CM recovery failed to change your fastboot so you were able to keep the 5.0.1 fastboot. You lucked out.
blueberry.sky said:
If you can load CM recovery then you do not need to use FlashFire.
And the ability to load custom recovery via fastboot shows that it's a 5.0.1 device.
If you can still load a recovery via fastboot then it seems CM recovery is unable to flash anything other than the rom. Normally, when flashing the FireOS 5.1.1 update file using amazon's recovery, it actually flashes more than just the rom. It also changes fastboot, killing our ability to load recoveries via fastboot.
You flashed 5.1.1 but CM recovery failed to change your fastboot so you were able to keep the 5.0.1 fastboot. You lucked out.
Click to expand...
Click to collapse
@blueberry.sky thanks...you clearly know a lot more about this than I do. I was hoping I'd found a method to help out folks, but it looks like not So if I understand this....if I can connect USB and fastboot a recovery file, I'm still on 5.0.1 fastboot?
DigiAngel69 said:
So if I understand this....if I can connect USB and fastboot a recovery file, I'm still on 5.0.1 fastboot?
Click to expand...
Click to collapse
Yep, if fastboot will allow you to load a recovery image then you have a 5.0.1 device.
If instead fastboot gives you "FAILED (remote: unknown command)" when you try to load a recovery image then you have 5.1.1.
blueberry.sky said:
Yep, if fastboot will allow you to load a recovery image then you have a 5.0.1 device.
If instead fastboot gives you "FAILED (remote: unknown command)" when you try to load a recovery image then you have 5.1.1.
Click to expand...
Click to collapse
Ok cool...with a running CM12 I can currently boot to the official amazon recovery with the menu, or fastboot that errors out with the FAILED unknown command. Thanks for taking the time to enlighten me!