[Q] Ap Fastboot fails at boot.img - Motorola Droid Bionic

Ok I’ve trying for days now to get my bionic to load the boot.img and every method has failed. I have tried RD lite both files ,Fast boot recovery by dhacker and R3l3AS3DRoot_V2_Windows. I accidently wiped webtop and now just boots to AP. Is there a way to manually open a term window and push this boot.img ? I’ve read a lot about ADB . Anyways Battery is good for now, it was full when I went stupid. I was rooted and fovever rooted on .893
Opened a cmd and tried sending flashboot boot.img answers back
boot 8192kb
INFOPreflash Validation failure
Failed (Remote)
System.img completes fine.
I've tried different computers and countless web sites

I don't believe you can fastboot flash the boot.img because of the locked bootloader. What happen is you pull the battery out and hold both volume buttons and power at same time and then select reboot normal. If you deleted your webtop you need to fastboot the grfs.img

rgb2448 said:
I don't believe you can fastboot flash the boot.img because of the locked bootloader. What happen is you pull the battery out and hold both volume buttons and power at same time and then select reboot normal. If you deleted your webtop you need to fastboot the grfs.img
Click to expand...
Click to collapse
Hey Thanks for replying, I was reading about that last night here---->mydroidworld.com/forums/droid-bionic-forum/9800-how-get-your-phone-back-upgrade-path
After reading what you said i went ahead and pushed that webtop.img to my and now it boots up. Now i just need to get root back, i've seen others at this point so it shouldn't be to tough.

! TuNaCaN ! said:
Hey Thanks for replying, I was reading about that last night here---->mydroidworld.com/forums/droid-bionic-forum/9800-how-get-your-phone-back-upgrade-path
After reading what you said i went ahead and pushed that webtop.img to my and now it boots up. Now i just need to get root back, i've seen others at this point so it shouldn't be to tough.
Click to expand...
Click to collapse
Go to the second post on the back on upgrade path and there is a one click root

Related

Unable to flash ANYTHING please help!

I keep on trying to flash ANYTHING to my bionic(stuck in ap fastboot with boot failure) and every time I go to flash something it keeps on shifting to "FAILED<remote: battery low>
I am at my wits end, I tried the fxz, and it failed, I tried the r3l3as3droot fix and it fails.... Can someone PLEASE help soon?
You've got to charge the battery. There are ways to do it by cutting off the end of a spare usb cable, and you can find that here somewhere.... I just don't remember where.
Try flashing via RSD lite. See if that works.
http://rootzwiki.com/topic/13105-a-easier-way-back-to-the-update-path/
Sent using xda premium
RSD fails almost immediately. I dont knwo what else to do. I think I officially bricked myself.
htcdesirezgeorge said:
RSD fails almost immediately. I dont knwo what else to do. I think I officially bricked myself.
Click to expand...
Click to collapse
Did you even read sreven.rn's post. You need to charge your battery. Fastboot/rsd will do nothing until you get that battery charged.
This post has the answer you seek
http://www.droidforums.net/forum/droid-x-tech-support/189467-need-help-dead-battery-trick.html
Sent from my DROID BIONIC using xda premium
That is a great tip dellenrules! I'll have to keep this one in mind.
Anyone know if the battery will charge in this FlashBoot mode?
I am on Battery Low, can't boot to phone screwed myself earlier with all the flashing. Not stuck at Flash Failed, can't RSD, can't flash via Flashboot because of low battery.
Wonder if I leave it there will it charge
smilepak said:
Anyone know if the battery will charge in this FlashBoot mode?
I am on Battery Low, can't boot to phone screwed myself earlier with all the flashing. Not stuck at Flash Failed, can't RSD, can't flash via Flashboot because of low battery.
Wonder if I leave it there will it charge
Click to expand...
Click to collapse
I'm 99% positive it will not charge in fastboot mode.
Crap. Was there like a USB hack somewhere that will get this to work? I can't remember. I am screwed!
HOW TO FIX A TOTALLY BRICKED BIONIC (& HOW TO McGUYVER CHARGE A DEAD BATTERY too)
I have prepared an uber zip file that contains all you need.
Wish I had it last night! I was up until 3am, worked on this for about 6 hours, and then this finally worked. I tried everything. fastboot, one click this, sd lite, etc. none of it worked.
You will praise me.
this worked - Got my phone back!
of course, I tried every solution in the world and was profoundly frustrated for hours and ran out of battery. but this WORKED. NOTHING else did.
I also had to do the McGuyver thing with an old blackberry usb charger.
snip the end off, strip the red and black wires, insert the red to positive on your battery (battery out of the phone!) insert black to negative, THEN plug in the charger. let it go for at least 1/2 hour.
my uper zip file - UNZIP THIS file to a FOLDER on YOUR DESKTOP.
http://dl.dropbox.com/u/12759680/fastboot.zip
also Manually copy files (update893 and update901) to your SD card!!!!!
(take out the micro sd, load the files onto it using an adapter.)
1. Put phone in Fastboot mode, connect to computer [hopefully you have the drivers installed. if not, search for Motorola_End_User_Driver_Installation_5.2.0_32bit or the 64 bit if that's your operating system
whenever there is a command, I copied it and pasted it in the command window (ctrl v does not work to paste, you must right click and then paste) dont copy the friggin quotation marks
2. Open a command terminal and go to the Stock folder ("cd C:\Documents and Settings\YOUR NAME\Desktop\fastboot")
3) type these commands in the terminal window and wait for the flashing to finish before going to the next line.
----> "moto-fastboot.exe flash webtop grfs.img" (This file will be flashed in 4 parts)
----> "moto-fastboot.exe flash preinstall preinstall.img"
----> "moto-fastboot.exe flash system system.img" (This file will be flashed in 2 parts)
----> "moto-fastboot.exe reboot"
be patient. some of these steps take a while and you think nothing is happening.
then you see some action in the command prompt box.
Then reboot into stock recovery (volume up+down and power; then select recovery then volume up)
When in recovery, hit both volume up+down, then go to wipe data
then flash update893.zip
If you come upon the triangle with the exclamation point and the android man, dont freak out, hit the power button, down volume, both volume at once, and eventually you will be in recovery.
you will so do a dance.
be patient. some of these steps take a while and you think nothing is happening.
then you see some action in the command prompt box.
wait a day. then, If you're feeling adventurous, reboot into stock recovery and flash 901!
I'm no maven, but I got my phone back and then to 901.
havent rooted again but I'm waiting for the developers to catch up to 901, which I downloaded and flashed after getting the damn phone back.
No dice for me
failed at flashing Web Top Frfs.img
Load_file: could not allocate xxxx
Pass preinstall.img
Failed system.img
Writing system .... INFOPreflash Validation Failure
FAILED (remote: )
Reboot phone...
Invalid Flash mode (s) (Boot Failed)
0A.61
Battery OK
OK to Program
Transfer Mode:
USB Connected
Invalid CG Version (CG: boot)
is where I am at now
finally got these two installed
----> "moto-fastboot.exe flash preinstall preinstall.img"
----> "moto-fastboot.exe flash system system.img" (This file will be flashed in 2 parts)
----> "moto-fastboot.exe reboot"
once reboot, did wipe cache and wipe data
update 893, failed during verify data....
crap..
Ok, here is the deal. It is IMPOSSIBLE to revive your phone from the process that I did. UNDER NO CIRCUMSTANCES SHOULD YOU FLASH 5.5.901 AND THEN DO A FACTORY RESTORE OR RECOVER IN TO A CUSTOM ROM. DO NOT ATTEMPT OR YOU WILL IRREPARABLE BRICK YOUR PHONE!
htcdesirezgeorge said:
Ok, here is the deal. It is IMPOSSIBLE to revive your phone from the process that I did. UNDER NO CIRCUMSTANCES SHOULD YOU FLASH 5.5.901 AND THEN DO A FACTORY RESTORE OR RECOVER IN TO A CUSTOM ROM. DO NOT ATTEMPT OR YOU WILL IRREPARABLE BRICK YOUR PHONE!
Click to expand...
Click to collapse
What are you talking about when you say factory restore? Are you talking about doing a factory data reset?
Because many have done FDR's without a problem.
Have you tried the one click script that P3Droid and the guys at rootzwiki came up with to get everybody back on the upgrade path?
That's weird.
I returned to stock from 901 using the method in the first link I posted without a hitch.
FYI
Sent from my DROID BIONIC using xda premium
I believe the second post was the answer to your problem.. now second option is to cut a usb cable and connect the negative and positive cables to your battery and leave it for an hour or so to charge..
Sent from my DROID BIONIC using XDA App
This guy obviously doesn't want any help.
He pops in once in a while with a frantic nonsensical post and doesn't bother to read our posts that can help him.
nateohio said:
This guy obviously doesn't want any help.
He pops in once in a while with a frantic nonsensical post and doesn't bother to read our posts that can help him.
Click to expand...
Click to collapse
Oh no, I definitely wanted help BUT I was dumb and used my bionic as my sole internet connection. I have my insurance replacement now($100 down the drain). I had tried ALL of the fixes but non even remotely succeeded. What ended up happening was that I somehow made it where it would not even begin to flash files. I purchased an extended battery but yyyyyeeeeaaaaahhhhh lol, so now I have shiney new supplied for my new phone lol.
Oh wells, you win some and lose some.
Fails for me on first line
idivorceyou said:
I have prepared an uber zip file that contains all you need.
Wish I had it last night! I was up until 3am, worked on this for about 6 hours, and then this finally worked. I tried everything. fastboot, one click this, sd lite, etc. none of it worked.
You will praise me.
this worked - Got my phone back!
of course, I tried every solution in the world and was profoundly frustrated for hours and ran out of battery. but this WORKED. NOTHING else did.
I also had to do the McGuyver thing with an old blackberry usb charger.
snip the end off, strip the red and black wires, insert the red to positive on your battery (battery out of the phone!) insert black to negative, THEN plug in the charger. let it go for at least 1/2 hour.
my uper zip file - UNZIP THIS file to a FOLDER on YOUR DESKTOP.
http://dl.dropbox.com/u/12759680/fastboot.zip
also Manually copy files (update893 and update901) to your SD card!!!!!
(take out the micro sd, load the files onto it using an adapter.)
1. Put phone in Fastboot mode, connect to computer [hopefully you have the drivers installed. if not, search for Motorola_End_User_Driver_Installation_5.2.0_32bit or the 64 bit if that's your operating system
whenever there is a command, I copied it and pasted it in the command window (ctrl v does not work to paste, you must right click and then paste) dont copy the friggin quotation marks
2. Open a command terminal and go to the Stock folder ("cd C:\Documents and Settings\YOUR NAME\Desktop\fastboot")
3) type these commands in the terminal window and wait for the flashing to finish before going to the next line.
----> "moto-fastboot.exe flash webtop grfs.img" (This file will be flashed in 4 parts)
----> "moto-fastboot.exe flash preinstall preinstall.img"
----> "moto-fastboot.exe flash system system.img" (This file will be flashed in 2 parts)
----> "moto-fastboot.exe reboot"
be patient. some of these steps take a while and you think nothing is happening.
then you see some action in the command prompt box.
Then reboot into stock recovery (volume up+down and power; then select recovery then volume up)
When in recovery, hit both volume up+down, then go to wipe data
then flash update893.zip
If you come upon the triangle with the exclamation point and the android man, dont freak out, hit the power button, down volume, both volume at once, and eventually you will be in recovery.
you will so do a dance.
be patient. some of these steps take a while and you think nothing is happening.
then you see some action in the command prompt box.
wait a day. then, If you're feeling adventurous, reboot into stock recovery and flash 901!
I'm no maven, but I got my phone back and then to 901.
havent rooted again but I'm waiting for the developers to catch up to 901, which I downloaded and flashed after getting the damn phone back.
Click to expand...
Click to collapse
My phone goes strait to AP Fastboot Flash Mode (S)(Invalid CDT) at power up.
When I enter the first line of these instructions "moto-fastboot.exe flash webtop grfs.img" I get an error that states
load_file: could not allocate 1397489664 bytes
error: cannot load 'grfs.img'
Any ideas?

stuck at red logo

Hey guys,
i did stupid things witch my razr i and now i'm completely lost…maybe someone can help?
I've been impatient enough to try to flash the leaked jb rom 3 days ago. That did'nt work
No, whenever i power up the phone it shows the red M logo and nothing happens.
I can power it down by holding vol+down and power for more than 4 seconds.
If i release the keys, it goes back to te red M,
If i keep holding vol+down it boot s into AP fastboot flash mode (secure boot) 20.0f
i can choose recovery and that'll work, but i don't have an update for external storage. rebooting from there leads to red M.
Normal Powerup, Factory and BP Tools are choosable, log says Booting into… but nothing happens after that, i'll stay in fastboot.
Power off works.
I tried to flash various images via »fastboot flash boot/recovery/system«, but nothing worked out.
I flashed the files from Razri_Root_Linux, two files (retail central europe) from here sbf.droid-developers, but nothing helped, every reboot leads to the red M.
I read about RSD-Lite, tried to install it under Win7, got it, but was lost after the Program always complained about an invalid xml.
Since i don't own that machine i went back to my linuxbox where i found sbf_flash, but i don't get it how to put the pieces together (which file/s to use)
Any hints on how to go from here?
[EDIT:] I downloaded 91.2.26001.Retail.en.EU.zip and did all the steps from flashandboot.bat, read
fastboot flash boot
fastboot flash system
fastboot flash recovery
next step ist to select recovery, did this an cwm comes up, sideloaded RAZRiRoot2.zip everything is pisitively quited, no errors are shown.
reboot leads to red M
wiped data/factory reset, reboot
red Logo.
I'm completely lost, please help
[\EDIT]
greetings, D.
I had same problem
Hello.
I had same problem because I did very stupid thing. I flashed homemade JB and because some apps don´t work I tried downgrade my i to ICS back....
My i stucked at the red M then I tried same thing as you and phone still booted into red M.
So I tried in windows cmd and FlashAndRoot.bat from this .zip "91.2.26001.Retail.en.EU - 4.1.2" it did nothing, but I tried to choose in fastboot mode BP Tools, then my i booted and started to flash JB what I can see in command window. Phone was still connected to PC. After next reboot my phone has work normally with JB.
I hope to help you. Let me know.
Lucki
Hi Lucki
thanks for jumping by.
Lucki_X said:
Hello.
So I tried in windows cmd and FlashAndRoot.bat from this .zip "91.2.26001.Retail.en.EU - 4.1.2" it did nothing, but I tried to choose in fastboot mode BP Tools,
Click to expand...
Click to collapse
I tried this, and display on razr i says »Booting into BP Tools mode…«
and nothing more happens, display stays on…
and after some time pc automounts a "cd-rom drive" with some motorola files (Autorun.inf MDMSetup.xml MotorolaDeviceManagerSetup.exe MDMSetup.ini MotorolaDeviceManager_2.2.28)
but it still won't reboot…
i don't know.
Hi.
I had opened command window, "FlashAndRoot.bat" was running (I pressed any key) process was running (it means freezing ) and at this time I chose in fastboot booting into BP tools mode. My phone did restart and after it "FlashAndRoot.bat" process started to flash JB. After flashing my phone is going normally with JB. But some apps don´t work in JB.
Lucki
Lucki_X said:
Hi.
I had opened command window, "FlashAndRoot.bat" was running (I pressed any key) process was running (it means freezing ) and at this time I chose in fastboot booting into BP tools mode. My phone did restart and after it "FlashAndRoot.bat" process started to flash JB. After flashing my phone is going normally with JB. But some apps don´t work in JB.
Lucki
Click to expand...
Click to collapse
Doesn't work. :crying:
since i use linux i opened FlashAndRoot.bat in texteditor and executed the comands from there in terminal
only chance for the script to stop and wait is IMHO(correct-me-if-i'm-wrong) "adb wait-for-device push RAZRiRoot2.zip /sdcard/RAZRiRoot2.zip & adb reboot bootloader"
but that message "Booting into BP Tools mode…" just stays there forever, or does it take longer than 5minutes?
dogo77 said:
but that message "Booting into BP Tools mode…" just stays there forever, or does it take longer than 5minutes?
Click to expand...
Click to collapse
In my case it booted within 10 second and ran.
I am noob, I am writing just my experience. I couldn´t give you another advice, sorry.
I'm not sure how far the real installation went, but i would find Windows computer, get RSD (6.0-6.14) and try to flash ICS first. If failed due to impossibility of downgrading, then try JB. While you are able to boot to Recovery - don't loose hope yet
okaban said:
I'm not sure how far the real installation went, but i would find Windows computer, get RSD (6.0-6.14) and try to flash ICS first. If failed due to impossibility of downgrading, then try JB. While you are able to boot to Recovery - don't loose hope yet
Click to expand...
Click to collapse
Yeah. I'm still stuck at the red logo, or indeed, at a blueish "Bootloader unlocked warnig" message since i was able to install parts of an image from sbf.droid-developers. But flashing always fails while trying to flash system.img_signed.
After reading and trying a lot these last days i think i have to install windows somewhere just to get rsd-lite to run.
sbf_flash for linux didn't work for me and fastboot gives stange warnings about "Invalid sparse file format at header magi"…
so i'll give rsd a try before i give up. As i read in posts by HSDPilot, this is the only tool that works
thanks for your help!

[Q] Moto x flashing recovery snafu - please help

RESOLVED!
so I just got my moto x dev edition, unlocked the bootloader, and then screwed it up...
i tried flashing the recovery as described here, http://forum.xda-developers.com/showthread.php?t=2458451 but didn't realize/understand that fastboot and mfastboot were not interchangeable. it looked like it went ok, but I wasn't able to reboot into recovery. so, now on boot to recovery i get the little android on his back with a red triangle. i'm pretty sure that the stock recovery is gone, but cwm is not installed either. which brings me to my next little problem...
so i did some reading and got mfastboot installed and thought ok I just need to reflash cwm on phone again. problem is, now the phone won't stay in usb debug mode so that i can see it when fastbooted. that is, when i reboot the phone into fastboot by holding the power/vol down I can't see the phone when doing 'adb devices', and whem I let it boot up i see usb debug is switched off. when i switch it on, then i can see the phone from adb again, but when i try to 'reboot bootloader' it gives me a not allowed error.
at this point i'm just sick and afraid i bricked it. i am coming from a galaxy nexus and never had anything like this happen before. i truly appreciate any help here, at this point i feel like puking and dreading telling the wife i just blew 450.... :-/
ps i'm on mac 10.7 so if i need rsd it will be via a virtual machine....
herrdrchili said:
so I just got my moto x dev edition, unlocked the bootloader, and then screwed it up...
i tried flashing the recovery as described here, http://forum.xda-developers.com/showthread.php?t=2458451 but didn't realize/understand that fastboot and mfastboot were not interchangeable. it looked like it went ok, but I wasn't able to reboot into recovery. so, now on boot to recovery i get the little android on his back with a red triangle. i'm pretty sure that the stock recovery is gone, but cwm is not installed either. which brings me to my next little problem...
so i did some reading and got mfastboot installed and thought ok I just need to reflash cwm on phone again. problem is, now the phone won't stay in usb debug mode so that i can see it when fastbooted. that is, when i reboot the phone into fastboot by holding the power/vol down I can't see the phone when doing 'adb devices', and whem I let it boot up i see usb debug is switched off. when i switch it on, then i can see the phone from adb again, but when i try to 'reboot bootloader' it gives me a not allowed error.
at this point i'm just sick and afraid i bricked it. i am coming from a galaxy nexus and never had anything like this happen before. i truly appreciate any help here, at this point i feel like puking and dreading telling the wife i just blew 450.... :-/
ps i'm on mac 10.7 so if i need rsd it will be via a virtual machine....
Click to expand...
Click to collapse
so, if i understand you correctly, u've held down the volume down button and power button? becasue that's your fastboot. That's where you need to be to use RSD, and that's what i'd do.
ADB commands aren't used in fastboot mode. You should be able to see the device in fastboot mode with the command fastboot devices. Also, remember that the stock rom will try to restore the stock recovery when it is booted so if you flash recovery in fastboot mode then let the stock rom boot it will reflash the stock recovery which shows you the little droid and the red triangle.
You should still be okay though. Shut the phone off and boot into fastboot manually with power and volume down. Reflash the recovery. I know there are warnings about using mfastboot but I used standard fastboot before I saw those and didn't have an issue. From the fastboot screen after flashing the recovery, use volume down to get to highlight recovery and then press volume up to select, not power. Power will just do a standard reboot.
If you flashed twrp recovery then rebooting system will prompt you to install su. I think clockwork does the same thing. Letting the recovery install su will also prevent the stock recovery from getting restored and from there you should be good.
herrdrchili said:
so I just got my moto x dev edition, unlocked the bootloader, and then screwed it up...
i tried flashing the recovery as described here, http://forum.xda-developers.com/showthread.php?t=2458451 but didn't realize/understand that fastboot and mfastboot were not interchangeable. it looked like it went ok, but I wasn't able to reboot into recovery. so, now on boot to recovery i get the little android on his back with a red triangle. i'm pretty sure that the stock recovery is gone, but cwm is not installed either. which brings me to my next little problem...
so i did some reading and got mfastboot installed and thought ok I just need to reflash cwm on phone again. problem is, now the phone won't stay in usb debug mode so that i can see it when fastbooted. that is, when i reboot the phone into fastboot by holding the power/vol down I can't see the phone when doing 'adb devices', and whem I let it boot up i see usb debug is switched off. when i switch it on, then i can see the phone from adb again, but when i try to 'reboot bootloader' it gives me a not allowed error.
at this point i'm just sick and afraid i bricked it. i am coming from a galaxy nexus and never had anything like this happen before. i truly appreciate any help here, at this point i feel like puking and dreading telling the wife i just blew 450.... :-/
ps i'm on mac 10.7 so if i need rsd it will be via a virtual machine....
Click to expand...
Click to collapse
ok then - i guess rsd has potential?
xpsychox said:
so, if i understand you correctly, u've held down the volume down button and power button? becasue that's your fastboot. That's where you need to be to use RSD, and that's what i'd do.
Click to expand...
Click to collapse
i can reboot into fastboot, but adb can't see the phone. I'll start trying to setup rsd and and see if it can do any better. any good links you know to get up to speed on that would be appreciated. if you know how to simply reflash the recovery via rsd that would be helpful too - thanks in advance!
herrdrchili said:
i can reboot into fastboot, but adb can't see the phone. I'll start trying to setup rsd and and see if it can do any better. any good links you know to get up to speed on that would be appreciated. if you know how to simply reflash the recovery via rsd that would be helpful too - thanks in advance!
Click to expand...
Click to collapse
the sites that I know of are for the device I have, a non devliper edition... I don't know if it makes a difference, I don't wanna make anything worse.
thanks for the sanity check,,,
btdonovan said:
ADB commands aren't used in fastboot mode. You should be able to see the device in fastboot mode with the command fastboot devices. Also, remember that the stock rom will try to restore the stock recovery when it is booted so if you flash recovery in fastboot mode then let the stock rom boot it will reflash the stock recovery which shows you the little droid and the red triangle.
You should still be okay though. Shut the phone off and boot into fastboot manually with power and volume down. Reflash the recovery. I know there are warnings about using mfastboot but I used standard fastboot before I saw those and didn't have an issue. From the fastboot screen after flashing the recovery, use volume down to get to highlight recovery and then press volume up to select, not power. Power will just do a standard reboot.
If you flashed twrp recovery then rebooting system will prompt you to install su. I think clockwork does the same thing. Letting the recovery install su will also prevent the stock recovery from getting restored and from there you should be good.
Click to expand...
Click to collapse
THANKS! just needed another set of eyes - man i need to not try doing this after a long day again i really appreciate your help. i got it now!
herrdrchili said:
THANKS! just needed another set of eyes - man i need to not try doing this after a long day again i really appreciate your help. i got it now!
Click to expand...
Click to collapse
Glad I could help!

I just killed my bootloader, only got ADB access, what to do now?

Hey xda devs,
I just f ed up very bad. I was trying to flash a new recovery onto my Moto X and I was careless typing commands into the terminal I guess that serves me right.... So I was just rebooting my phone into the bootloader by typing adb reboot bootloader, so I had the "bootloader" sticking in my head there and because I did it a thousand times already I just proceed to flashing the new recovery but I type "fastboot flash bootloader xxxx.img"
So now, I have basically flashed a recovery.img into my bootloader partition
I still have adb and root access though.. is there any way I could save my bootloader partition? like adb dd it maybe ? I dont know
Did you try to manually reflash the correct image file? Or sbf back to stock?
Travisdroidx2 said:
Did you try to manually reflash the correct image file? Or sbf back to stock?
Click to expand...
Click to collapse
I'm not in fastboot anymore, I guess that's what I should have done when I realized my mistake. Because I was well aware of what I had just done.. but I rebooted the phone and now I guess there is no way to enter fastboot anymore.
Without fastboot how can I flash the correct img. file into the bootloader partition?
And what do you mean with sbf back to stock?
yabbandroid said:
I'm not in fastboot anymore, I guess that's what I should have done when I realized my mistake. Because I was well aware of what I had just done.. but I rebooted the phone and now I guess there is no way to enter fastboot anymore.
Without fastboot how can I flash the correct img. file into the bootloader partition?
And what do you mean with sbf back to stock?
Click to expand...
Click to collapse
Ever use RSD to flash a SBF? RSD will need to recognize your device though. There is stickies I am sure. I will find one to link you to.
Hold the power button until the phone is off. Now press and hold both the power button and volume down button for 10 seconds. Then release the power button, but keep the volume down button held. You should then be in fastboot mode.
AGISCI said:
Hold the power button until the phone is off. Now press and hold both the power button and volume down button for 10 seconds. Then release the power button, but keep the volume down button held. You should then be in fastboot mode.
Click to expand...
Click to collapse
The problem is that his bootloader (The mode that you have to get into to use fastboot) is no more. If you could find the block number you could do a dd command.
Vekhez said:
The problem is that his bootloader (The mode that you have to get into to use fastboot) is no more. If you could find the block number you could do a dd command.
Click to expand...
Click to collapse
Yep, good suggestion. It will only work if he has busybox installed (the 'stericson' variant, from the play store).
This command should work (from and ADB SHELL) assuming busybox is installed. First motoboot.img would need to be copied to the working directory on the sdcard where you are running the command from. Might need to be superuser as well.
dd if=motoboot.img of=/dev/block/platform/msm_sdcc.1/by-name/bootloader
Let me know if you have success. After running the command, if it shows success, you should be able to power off and successfully boot into bootloader (AP fastboot mode).
samwathegreat said:
Yep, good suggestion. It will only work if he has busybox installed (the 'stericson' variant, from the play store).
This command should work (from and ADB SHELL) assuming busybox is installed. First motoboot.img would need to be copied to the working directory on the sdcard where you are running the command from. Might need to be superuser as well.
dd if=motoboot.img of=/dev/block/platform/msm_sdcc.1/by-name/bootloader
Let me know if you have success. After running the command, if it shows success, you should be able to power off and successfully boot into bootloader (AP fastboot mode).
Click to expand...
Click to collapse
You're my hero, Sam. I'm gonna try that. I thought about dd but I don't understand this command so well ^^. Thank you for writing it down. I have root access so I can install busybox. I will try :good::good:
edit: did it as root! I think you just saved my phone! A thousand thanks to you, because I love my moto x !!
.img of=/dev/block/platform/msm_sdcc.1/by <
by-name/ by-num/
/block/platform/msm_sdcc.1/by-name/bootloader <
3209+0 records in
3209+0 records out
1643008 bytes transferred in 0.086 secs (19104744 bytes/sec)
Click to expand...
Click to collapse
succcess, success, after that I could succesfully reboot into fastboot. Only my recovery seems to be lost, but I will try to reflash this one now using fastboot which is back and working !!! (will be more careful in the future)
SO HAPPY. THank you !
yabbandroid said:
SO HAPPY. THank you !
Click to expand...
Click to collapse
Fantastic, bud!!! Yep, dd can come in very handy sometimes, and it's good to know some native linux commands (they save our butts every now and then...)
Very glad to hear my method worked for you. :good:

Took OTA with custom recovery

Hi all, I did a dumb thing and I took the recent Verizon OTA on my dev ed moto x with a custom recovery installed (TWRP).
Now my phone seems to always stop booting at recovery, then if i hit 'reboot system' from recovery, I can get into my system for about 2-3 minutes, and then it reboots to recovery again.
Any help would be greatly appreciated!
boot your phone into fastboot/bootloader mode, then flash stock Recovery on your phone and reboot normally.
KidJoe said:
boot your phone into fastboot/bootloader mode, then flash stock Recovery on your phone and reboot normally.
Click to expand...
Click to collapse
Thanks KidJoe - I'm reading through your post on xda right now to see how you flash back to the stock recovery and I'm currently downloading the stock image from one of your links.
While I'm waiting, I'm going over my options for how to actually flash the stock recovery - your post said that i should try Rashr - however my device probably won't stay 'on' long enough for me to get through that process. After it boots into the system (e.g. I see my launcher and apps), it wants to restart since I guess it's trying to the upgrade. So I'm thinking of instead using adb to flash the recovery.img file. Is that the right path to take?
Also - would it be okay to use adb to flash the recovery.img using TWRP's adb sideload feature? I seem to be able to connect using adb that way, but for some reason 'adb devices' doesn't list anything under fastboot.
switch81 said:
Thanks KidJoe - I'm reading through your post on xda right now to see how you flash back to the stock recovery and I'm currently downloading the stock image from one of your links.
While I'm waiting, I'm going over my options for how to actually flash the stock recovery - your post said that i should try Rashr - however my device probably won't stay 'on' long enough for me to get through that process. After it boots into the system (e.g. I see my launcher and apps), it wants to restart since I guess it's trying to the upgrade. So I'm thinking of instead using adb to flash the recovery.img file. Is that the right path to take?
Also - would it be okay to use adb to flash the recovery.img using TWRP's adb sideload feature? I seem to be able to connect using adb that way, but for some reason 'adb devices' doesn't list anything under fastboot.
Click to expand...
Click to collapse
First, if you can't boot your phone into Android, you can't use Rashr.
Next... ADB needs you to be up in Android, and have the "USB Debugging" options checked. Also, it can not be used to flash the components of the SBF/ROM like recovery.img.
Fastboot mode works with Fastboot.exe or mFastboot.exe... ADB commands do not work when the phone is in fastboot mode.
Here is what you want to do AFTER you have the stock reocvery.img you want to flash... (this is pretty much exactly what you did to flash TWRP on there in the first place, except you will be flashing a stock recovery.img instead)
have the latest Moto drivers installed. You can get them from -> https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Make sure you have the Android SDK/Platform Tools installed (don't know how, see -> http://mark.cdmaforums.com/ADB.htm )
You need the latest version of Moto's fastboot, and it needs to be put in your windows Path (there are steps on -> http://mark.cdmaforums.com/ADB.htm )
Once you have that... do the following...
Unplug phone
Power down phone.
Hold Volume Down and Power
After a few seconds release Power, you should be in fastboot menu on phone.
Connect to PC.
open command prompt file and change to the folder you have your recovery.img you want to flash
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash recovery recovery.img
mfastboot reboot-bootloader
The device will display different BOOT OPTIONS
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
The device will display the Motorola logo and then the Android in distress (logo with Exclamation mark)
Press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key
You should enter STOCK recovery.
use the VOL DOWN Key to scroll and the POWER Key to select reboot.
The phone should reboot and and be ready for the update
I did the same thing and was able to undo it by clearing the cache. Now I'm back to where I was before, with the constant notification to update.
Wondering what the correct way to go about updating is..
*Edit: Thanks!
Moto X Dev
Thanks! I'm back up and running!
Sorry for the confusion on the adb vs fastboot stuff - I always mix those kinds of things up since I do it once ages ago to get myself into this mess, then I forget how I did it and what tools I used.
So basically what I did was use fastboot like you said and first booted into fastboot, then did a 'fastboot flash recovery recovery.img' from a stock recovery.
After a full reboot, android ended up giving me a 'update was unsuccessful' which I am totally 100% okay with. I ended pushing 'update' the first time really because I was tired of getting nagged - this time i just said 'don't install' and hopefully it won't bother me agian.
Thanks again!
slynke said:
I did the same thing and was able to undo it by clearing the cache. Now I'm back to where I was before, with the constant notification to update.
Wondering what the correct way to go about updating is..
*Edit: Thanks!
Moto X Dev
Click to expand...
Click to collapse
I'm sure KidJoe will respond, but I found this thread of his very useful:
http://forum.xda-developers.com/moto-x/general/ref-return-to-stock-recovery-rooted-t3027079
switch81 said:
Thanks! I'm back up and running!
Sorry for the confusion on the adb vs fastboot stuff - I always mix those kinds of things up since I do it once ages ago to get myself into this mess, then I forget how I did it and what tools I used.
So basically what I did was use fastboot like you said and first booted into fastboot, then did a 'fastboot flash recovery recovery.img' from a stock recovery.
After a full reboot, android ended up giving me a 'update was unsuccessful' which I am totally 100% okay with. I ended pushing 'update' the first time really because I was tired of getting nagged - this time i just said 'don't install' and hopefully it won't bother me agian.
Thanks again!
Click to expand...
Click to collapse
I was able to flash back to stock recovery and take the 212.166.3 build KXA21.12-L1.26-3 (which is still 4.4.4) OTA that Verizon is pushing out.
I didn't even have to disable Xposed or anything else. Then again, other than Xposed, root and twrp, I'm running stock. No tethering hacks, build.prop changes, no system files removed or renamed, etc.
---------- Post added at 01:18 PM ---------- Previous post was at 01:16 PM ----------
slynke said:
I did the same thing and was able to undo it by clearing the cache. Now I'm back to where I was before, with the constant notification to update.
Wondering what the correct way to go about updating is..
*Edit: Thanks!
Moto X Dev
Click to expand...
Click to collapse
Yup., Clearing cache will delete the OTA ZIP file that was downloaded. So the next time you reboot, it wont try to install, instead you'll be back to being notified that an update is available asking you if you want to download it.
But yup, those instructions I just typed should work...
This OTA seems so minimal in changes, any suggestions/recommendations if I should take it at all?
I'm also pretty much stock now as well - only root, xposed installed.
switch81 said:
This OTA seems so minimal in changes, any suggestions/recommendations if I should take it at all?
I'm also pretty much stock now as well - only root, xposed installed.
Click to expand...
Click to collapse
The release notes on VZW's page only seems to mention bug fixes.. no real details.
So far I haven't noticed any changes.
It will likely be a required step to get to lollipop. So either take it now, or wait and take it later, just before you upgrade to Lolliop

Categories

Resources