Database Info

[Completed] fastboot boot <recoverimgename>.img

I am having trouble getting consistent results with the "fastboot boot <recoverimgname>.img" command.
I am working with both an Amazon Fire 5th generation tablet, a Nexus 4 and HTC One X.
I followed the directions and youtube video posted by awesomeslayerg and rootjunkysdl for rooting the Amazon Fire, and was successfully able to do so (CyanogenMod version 12.1-20151115-UNOFICCIAL-ford, Android 5.1.1).
http://forum.xda-developers.com/amazon-fire/development/wip-achieving-root-thread-t3238152
I was also able to put Android version 6.0 on the Nexus 4 by following these directions:
http://forum.xda-developers.com/nexus-4/development/rom-unofficial-cm13-marshmallow-builds-t3236487
The one thing I'm struggling with is the fastboot command "fastboot boot <recoverimgename>.img".
On both devices, I'm able to get the devices in communication with the PC (ie "fastboot devices" returns the appropriate information about the devices).
I then run the "fastboot boot <recoverimgename>.img" command:
For Fire: "fastboot boot TWRP_Fire_2.8.7.0.img" (obtained from http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery)
For Nexus 4: "fastboot boot twrp-2.8.7.0-mako.img" (obtained at https://dl.twrp.me/mako/)
In both cases the recovery file is in the same directory from which I am running adb/fastboot.
The issue with both is that sometimes they'll reboot into the respective recovery, and sometimes they won't.
When they won't, the Nexus 4 hangs at the Google splash screen. The Amazon Fire boots to the system.
I can't figure out why they don't consistently boot to the recovery.
I've tried getting into fastboot mode via "adb reboot bootloader", by shutting the devices off and booting into fastboot manually (volume button + power switch), by rebooting to recovery then to fastboot, etc.
Also tried waiting a long time after getting the correct response to "fastboot devices" to make sure things had settled down.
Nothing seems to have given a consistent response.
I'd like to be sure that I can boot into a recovery on the PC when I need to (from fastboot on the device). At the moment it seems to be luck whether I can or not, but I assume there must be some cause that I can solve.
Anyone else experience this problem? Have ideas how to solve? Or can point me to a forum which is addressing this?
Thanks.

fastboot boot <recoverimgename>.img Inconsistency
I've just looked through the entire forum discussion on rooting the Amazon Fire 5th gen tablet, and not found an answer to this problem.
I've already rooted the Fire (Ford) and gotten Cyanogenmod 12.1-20151115-UNOFFICIAL-ford running on it, so this device is OK.
But I have continue to have erratic results booting to a recovery on the PC using fastboot: C
I can get the tablet connected to the PC in fastboot mode, fastboot devices gives me the right answer, my driver is Android Composite ADB Interface, and everything seems OK.
But most of the time when I enter the "fastboot boot TWRP_Fire_2.8.7.0.img" command the Fire reboots to system, and occasionally to Amazon's recovery version. Only occasionally to TWRP, and I don't know why.
How can I consistently boot into the TWRP_Fire_2.8.7.0.img recovery on the PC that I used when I rooted the thing in the first place?
Any ideas?

Hi,
Here's a guide you could try to be sure you are set up properly, http://forum.xda-developers.com/showthread.php?p=48915118
And as far as specific help for each device, you would be best to ask in those devices Q&A sections,
http://forum.xda-developers.com/nexus-4/help
http://forum.xda-developers.com/amazon-fire/help
Or ask in the threads you linked yourself. :good:
Good luck!

Thanks much. I'll try the guide. I've managed to get it all to work (ie "fastboot boot TRWP_Fire_2.8.7.0.img") on another PC, so it must be the setup on the 1st PC. I'm really struggling with the drivers.
I'd post questions in the other threads, but don't have the status yet...
I also see that Amazon's new update has throw a monkey wrench into fiddling with the Fire. I'll keep working at it.
Darth said:
Hi,
Here's a guide you could try to be sure you are set up properly, http://forum.xda-developers.com/showthread.php?p=48915118
And as far as specific help for each device, you would be best to ask in those devices Q&A sections,
http://forum.xda-developers.com/nexus-4/help
http://forum.xda-developers.com/amazon-fire/help
Or ask in the threads you linked yourself. :good:
Good luck!
Click to expand...
Click to collapse

Go to your device sections and contribute some meaningful posts to threads that interest you, and you'll be able to post in the other threads in no time. :good:

[Completed] How to unbrick Xperia S lt26i [not a noob]

I have a Xperia S running cm 12.1 with unlocked bootloaders TWRP installed and i tried to partition my SD card [http://forum.xda-developers.com/showthread.php?t=2584759] but clearly something went wrong and now the phone wont boot. I made a lot of research and tried everything but all the guides require to be able to boot into flashmode . My phone is dead the only sign of life is a red led when its charging which after some hours of charge will shut off. When the light is off and the phone connected on PC, the PC can recognize the device on unspecified devices (QHSUSB_DLOAD). i have installed all the needed drivers from Sony, google drivers from sdk, and adb drivers(adb wont see the device and i tried everything to do so, but nothing seem to work). I got a market for android on my pc called mobogenie that when i connect the phone it detects that a phone is connected but wont see what phone.The hardware reset buttons work but its useless in the current position. Concluding, the phone is bricked and wont open in fastboot-flashboot-bootloader-TWRP, its recognized as a device but not as "Xperia s" i got all the drivers and i want to flash the original firmware (already downloaded) to fix it. A possible problem is that the partition table is destroyed and after the flash it will hopefully be restored. The problem is not on the hardware but on software. I tried to trigger the download mode with the Samsung way (USB jig, 300k ohm ) but nothing happened as expected. Every solution i found required flash mode which is not accessible at the moment and i tried lots of things to go into fastboot(ever the rubber band trick,remove the battery etc). PLEASE help i dont know what to do, please help me flash it (i already got flashtool, Emma) or anohter solution. Thanks for the help in advance. (its my first thread in the forum, i hope to post it on the right section, i posted it here because i need the assistance of the developers i guess)

Hello,
Welcome to XDA.
The XDA Assist forum isn't what you think it is. We merely assist by helping to point users with issues in the right direction for their issue.
Try posting your question in the forum linked below.
http://forum.xda-developers.com/xperia-s/help?nocache=1&z=2025285740382969
The experts there may be able to help.
Register an XDA account to post and reply in the forums.

[Completed] Oneplus One bootloop with Linux

Apologies if something similar has already been posted on here already. I have had a look, but can't seem to find anything.
I was trying to root my oneplus one this evening, and was following a very useful link here....
https://forums.oneplus.net/threads/like-a-boss-how-to-root-your-oneplus-one.58493/
....and got to the bit that says "sudo fastboot oem unlock" - waited a minute, and the phone rebooted showing the android and 1+ logo. But before anything else happens it turns itself off, then back on again. And continues to do this indefinitely. I can get it into fastboot mode, but not recovery. When it is in fastboot mode the pc doesn't recognise it. Something obviously isn't right, but I'm not sure what. I'm guessing something is possibly corrupt.
What I think I need to do is firstly, get the pc to recognise the phone somehow. Secondly, install a recovery on to it and thirdly, flash a rom. I've been scratching my head all night trying to work out how to get the phone recognised, and Googling like a teenager who's just discovered porn is available on the Internet.
Is there anybody out there who is familiar with Linux who can possibly walk me through what I need to get my phone working again?
Thanks for taking the time to read this, and for any help that may be offered.

XDA Visitor said:
Apologies if something similar has already been posted on here already. I have had a look, but can't seem to find anything.
I was trying to root my oneplus one this evening, and was following a very useful link here....
https://forums.oneplus.net/threads/like-a-boss-how-to-root-your-oneplus-one.58493/
....and got to the bit that says "sudo fastboot oem unlock" - waited a minute, and the phone rebooted showing the android and 1+ logo. But before anything else happens it turns itself off, then back on again. And continues to do this indefinitely. I can get it into fastboot mode, but not recovery. When it is in fastboot mode the pc doesn't recognise it. Something obviously isn't right, but I'm not sure what. I'm guessing something is possibly corrupt.
What I think I need to do is firstly, get the pc to recognise the phone somehow. Secondly, install a recovery on to it and thirdly, flash a rom. I've been scratching my head all night trying to work out how to get the phone recognised, and Googling like a teenager who's just discovered porn is available on the Internet.
Is there anybody out there who is familiar with Linux who can possibly walk me through what I need to get my phone working again?
Thanks for taking the time to read this, and for any help that may be offered.
Click to expand...
Click to collapse
Hi and welcome to XDA.
Your device has a dedicated forum here:
OnePlus One > ONE Q&A, Help & Troubleshooting
All questions regarding your device belong in the forum linked above. You'll need to create an account first so you can post in the main forums.

[Completed] T-Mobile lg v20 becomes un-visible when put into bootloader mode.

I can't add any comments on XDA forum where this wuestion belongs because I don't have 10 or more comments posted instructions other than programming and ROMs. however I did post it on the XDA assist forum but i was sent to check out a forum that had nothing to do with my problem. I have the correct drivers I have everything I need to have and as soon as I put my phone into the bootloader mode for some reason the computer cannot recognize it anymore. on the command prompt I type in ADB devices and nothing shows up however, before I put my phone into bootloader mode when I type in ADB devices my phone shows up. apparently this is a phenomenon that only happens to 3% of the people that try to flash this device. I'm not the only one apparently.

Redhat1 said:
I can't add any comments on XDA forum where this wuestion belongs because I don't have 10 or more comments posted instructions other than programming and ROMs. however I did post it on the XDA assist forum but i was sent to check out a forum that had nothing to do with my problem. I have the correct drivers I have everything I need to have and as soon as I put my phone into the bootloader mode for some reason the computer cannot recognize it anymore. on the command prompt I type in ADB devices and nothing shows up however, before I put my phone into bootloader mode when I type in ADB devices my phone shows up. apparently this is a phenomenon that only happens to 3% of the people that try to flash this device. I'm not the only one apparently.
Click to expand...
Click to collapse
Greetings and welcome to assist. Unfortunately it seems you know more about this issue than us, have you tried following this guide
http://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903
when flashing your device to see if it works
Good Luck
Sawdoctor

Question Rog Phone 5 Brick

Hello to all,
I apologize in advance for this message.
I mistakenly bricked my phone,
It was running WW-18.0840.2201.226 (Android 11).
I'm not sure if I'm going to be able to use it again, but I'm sure I'll be able to use it again in the future.
The recovery mode does not work anymore. It remains stuck on the logo.
Concerning the device manager :
In Bootloader, nothing is detected
When I test the recovery mode, it detects 'Android Composite ADB interface'.
However, the ADB commands do not work (Unauthaurized)
This is a call for help, I don't know which tutorial to look at to help me.
Do I need to get a Deep Flash Cable to restore the phone?
Excuse my English, I'm French ^^'

Hi, I'm not sure, but I think you will have to delete this POST... It doesn't respect the forum rules... That said, you can follow this link for your problem. https://forum.xda-developers.com/t/...to-unlock-bootloader-to-modify-country-cn-to- ww.4353865/não lido

Hi Rico,
If I have to delete the post I will do it, it's not a problem.
Do you think I can put this post in the topic you gave me?
I had come across it in my research but I didn't know if it needed a Deep Flash Cable
I didn't know that my problem was similar to the one in the post because I don't have a 9008 mode
B.

Balmyr said:
Hi Rico,
If I have to delete the post I will do it, it's not a problem.
Do you think I can put this post in the topic you gave me?
I had come across it in my research but I didn't know if it needed a Deep Flash Cable
I didn't know that my problem was similar to the one in the post because I don't have a 9008 mode
B.
Click to expand...
Click to collapse
There is nothing wrong with your post at all.
Do you have access to see and send Fastboot commands to the phone when on the bootloader screen? You need to get that right first and get your driver on your PC sorted. Forget ADB, that's not going to help you here.
Once you have sorted the above, doing a RAW flash following one of the guides you can find on this form with a rom version that matches your device should get you back on track.
At this stage you shouldn't need EDL or a deep flash cable before exploring the above option.
Good luck.

Hello Andrologic,
Thanks for your reply
I only have access to the Bootloader with 'Start / Restart Bootloader / Recovery Mode / Power Off'.
I bought a Deep Cable, this one detects me when I connect it to the pc, previously my other cables did not want it
So I can indeed use the Fastboot commands whereas before I couldn't

Andrologic said:
There is nothing wrong with your post at all.
Do you have access to see and send Fastboot commands to the phone when on the bootloader screen? You need to get that right first and get your driver on your PC sorted. Forget ADB, that's not going to help you here.
Once you have sorted the above, doing a RAW flash following one of the guides you can find on this form with a rom version that matches your device should get you back on track.
At this stage you shouldn't need EDL or a deep flash cable before exploring the above option.
Good luck.
Click to expand...
Click to collapse
Thank you very much Andrologic!
The phone works like magic again, I can't believe it T_T
When I should do the updates, should I reflash the phone?
It doesn't offer me any new ones even though I'm on Android 11
B.

Balmyr said:
Thank you very much Andrologic!
The phone works like magic again, I can't believe it T_T
When I should do the updates, should I reflash the phone?
It doesn't offer me any new ones even though I'm on Android 11
B.
Click to expand...
Click to collapse
Nice. No, I would suggest updating the conventional way, i.e download ROM for ASUS and let the device pick it up and flash it. If you have TWRP installed, you can flash from there too, but there is no need for that unless the first method is not working