I bricked my phone on Wednesday. I stupidly installed the JB update on 15% battery. I had the phone plugged into a charger during the update but turns out the charger was broken. I'm waiting on a Motorola Factory Cable so that I can use Fastboot to try to restore the phone.
However - since I was about 90% done with the Jelly Bean update when the phone shut off, will I be able to Fastboot ICS? Or am I bricked until JB Fastboot files are released?
TIA
have you tried a good wall charger?
depends on what state, phone is in when you reboot
if AP fastboot is still older version (0A.74), should be ok to flash ics xml
or may not need to anything
if AP fastboot version the new one (0A.77), you may need to wait...
Sent from my MILESTONE3 using xda premium
Yes, I have tried several different chargers. The phone boots up to the "M" splash screen and hangs there. I am able to get to Fastboot, and it is version 0A.74. What is "ICS XML"?
VRZ_XT894_6.7.2-180_DR4-16_M2-37_1FF.xml
and
How To flash droid 4 .xml Using RSD Lite
may need to buy a TBH’s Motorola Programing Cable, it will by-pass battery, so you can flash xml
also could try booting to Android Recovery, don't wipe data, try install update from cache
was phone rooted? if safestrap was installed, that would cause update to fail
Okay, thank you for the links. I have flashed that file several times before on this phone, I just didn't realize it had an "XML" extension. I have a TBH cable on its way from eBay. I cannot currently get to recovery. My phone was rooted, but I uninstalled SafeStrap before I updated.
I ended up getting antsy and building a TBH cable myself. I was able to Fastboot back to ICS 4.0.4 using the mentioned XML file. :victory: Thanks for the replies. This thread can be closed.
nice, glad it worked
now, jellybean?
---------- Post added at 07:00 PM ---------- Previous post was at 06:59 PM ----------
very lucky, fastboot had not been updated yet
Yes, VERY lucky! Especially because I suck at soldering! My cable looks like Frankenstein.
Jelly Bean now, but this time I think I will let my phone charge to 100% first
Related
I was running GB .219. I restored data from a backup I made. After that Safestrap was gone. I can still boot to the boot menu by holding the volume keys down when you turn on the phone. I tried flashing via RSD but would fail all the time at system.img. Now the battery is dead. All it does is stay at the Motorola dual-core screen. Nothing more. No black screen or bootloop. It just stays there unless I unplug the phone or hold vol - and power to reset.
I ordered a factory cable. Can I use that to flash a rom via RSD? I believe there is no Android OS. It may have corrupted somehow. Would using the factory cable save the phone? Or is it lost forever? I can still exchange the phone but I ordered online so I have to send it in first to receive the replacement. I just want to know possible options. I'm really banking on the factory cable.
Please help.
badboi_zero said:
I was running GB .219. I restored data from a backup I made. After that Safestrap was gone. I can still boot to the boot menu by holding the volume keys down when you turn on the phone. I tried flashing via RSD but would fail all the time at system.img. Now the battery is dead. All it does is stay at the Motorola dual-core screen. Nothing more. No black screen or bootloop. It just stays there unless I unplug the phone or hold vol - and power to reset.
I ordered a factory cable. Can I use that to flash a rom via RSD? I believe there is no Android OS. It may have corrupted somehow. Would using the factory cable save the phone? Or is it lost forever? I can still exchange the phone but I ordered online so I have to send it in first to receive the replacement. I just want to know possible options. I'm really banking on the factory cable.
Please help.
Click to expand...
Click to collapse
did you try to flash the 219 sbf or the 215?
---------- Post added at 04:02 PM ---------- Previous post was at 03:58 PM ----------
get into fastboot. use droid 4 utility 1.6 and install safe strap from there. switch to your non safe system and factory reset. if it still wont boot up then try the 219 sbf again. this time it should work.
I can't get into fastboot with the standard motorola usb cable. The battery is dead. I only have a laptop here in my dorm, no desktop.
Will I be able to do it using the factory cable? I hope so. I believe it's a soft brick with no android os on the phone. And I read an OS is needed to charge the battery. I also read the factory cable will bypass the "low battery, cannot program" warning, allowing flashing.
Does the phone still have hope with no OS and a dead battery? Will the factory cable be able to get the phne operable?
Yes, the factory cable will be able to power the phone directly and allow you to flash the FXZ.
That is what they are designed for!
Noob Question
cellzealot said:
Yes, the factory cable will be able to power the phone directly and allow you to flash the FXZ.
That is what they are designed for!
Click to expand...
Click to collapse
Sorry, but I have heard a lot about a factory cable in this and other posts. I was wondering, What is different between the factory cable and the standard, out-of-the-box cable?
___________________________________________________________________________________________________________________
Rooted D4 with FM radio!!
Stock Samsung Galaxy S/Facinate
Stock Nook
It use an extra pin in the micro USB I think pin 5 that tells the phone it can be flashed with a dead battery.. you can make your own...
Sent from my DROID4 using xda app-developers app
http://forum.xda-developers.com/showthread.php?t=1077414&highlight=motorola+factory+cable
That link explains in detail how to make your own factory cable and has diagrams for the pinout .
It works. Without an os the phone can still be saved as long as it's not hard bricked. Thanks, all.
Hi im trying to return galaxy 8.9 tablet back to stock using odin, but it gets stuck at system.img.md5 and wont move...is there any way to fix.. tried switching usb ports and no luck...please need help
alrigh... alrigh... alriiiight got it to work after almost 5 days with out a tablet....which i really missed... I finally fixed the god damn issues with this stupid thing.....
with odin constantly hanging on system.img i had to work around it...
first got odin far enough into system.img to were cwm would work
second i adb into the tablet and pushed rom file into sdcard
third i installed rom and finally got my tablet back
yessss
also learned how to open tablet and pull the battery out....which i didn't need to do at all
What is your recent history in terms of Rom & recoveries installed, other errors encountered... ?
Did you do any formats, wipes, factory resets, and if so, in what environment (android, recovery, adb, ...)
---------- Post added at 09:07 AM ---------- Previous post was at 09:06 AM ----------
Have you tried simple options like restarting the pc, reinstalling tab's drivers, ...
Apologies, not relevant to this post
whisperingforce said:
... reverted back to honeycombe 3.2. The problem i have is that it now will not let me access or set up my google account. I have been unable to go back to stock.
Kies is also not recognising my tablet.
Click to expand...
Click to collapse
This is completely unrelated! Pls create your own thread, or search for a topic that's actually similar to yours, instead of trampling over another...
sonko2k said:
Hi im trying to return galaxy 8.9 tablet back to stock using odin, but it gets stuck at system.img.md5 and wont move...is there any way to fix.. tried switching usb ports and no luck...please need help
Click to expand...
Click to collapse
I had the same issue after upgrade to US stock ICS and attempt to install CWM recovery resulted in a tablet that would not boot. Rebooted into recovery mode, rebooted from there to download mode and tried the Odin flash again using the US stock ICS. Each time I did this it got a bit further (as indicated by the download bar on the tablet screen) and eventually it succeeded. I am no expert so I completely fail to understand why this worked but it did.
fred_be9300 said:
What is your recent history in terms of Rom & recoveries installed, other errors encountered... ?
Did you do any formats, wipes, factory resets, and if so, in what environment (android, recovery, adb, ...)
---------- Post added at 09:07 AM ---------- Previous post was at 09:06 AM ----------
Have you tried simple options like restarting the pc, reinstalling tab's drivers, ...
Click to expand...
Click to collapse
okay so recent..... rom was ics 4.0.4 version 3 uploaded by safariking...had ClockworkMod Recovery v5.5.0.4.... and yes i formatted ,wiped, and factory restarted, all in clockwork recovery... i have restarted the pc and reinstalled drivers and got a little bit further but odin still gets stuck... tried to restore with backup but get E: cant mount /sdcard/
sonko2k said:
okay so recent..... rom was ics 4.0.4 version 3 uploaded by safariking...had ClockworkMod Recovery v5.5.0.4.... and yes i formatted ,wiped, and factory restarted, all in clockwork recovery... i have restarted the pc and reinstalled drivers and got a little bit further but odin still gets stuck... tried to restore with backup but get E: cant mount /sdcard/
Click to expand...
Click to collapse
Just like i said before.. In warning: Do not wipe or anything related to that if youre in ICS..
With stock kernel or stock recovery or One of them but you still in stock ICS boot.img wiping is risky..
if you use a safe recovery but your boot.img is not safe. ..or your boot.img is safe but recovery.img isnt. .
Your still have the emmc bug risk..
Stuck on system.img means odin not recognized your system partition.. Maybe corrupted or faulty..
Please read my warning in general section..
suwandiapr said:
Just like i said before.. In warning: Do not wipe or anything related to that if youre in ICS..
With stock kernel or stock recovery or One of them but you still in stock ICS boot.img wiping is risky..
if you use a safe recovery but your boot.img is not safe. ..or your boot.img is safe but recovery.img isnt. .
Your still have the emmc bug risk..
Stuck on system.img means odin not recognized your system partition.. Maybe corrupted or faulty..
Please read my warning in general section..
Click to expand...
Click to collapse
so is my tab bricked or is there any other way
fixed
sonko2k said:
fixed
Click to expand...
Click to collapse
For others who may have this problem in the future, how did you fix it?
boscorama said:
For others who may have this problem in the future, how did you fix it?
Click to expand...
Click to collapse
First post
How did you get the battery out?
orlandoxpolice said:
How did you get the battery out?
Click to expand...
Click to collapse
i took a thin box cutter blade and ran it around the edge of the screen while gently pushing out and pulling up... the screen easily separates from the back cover.... behind the screen is a white battery with small mutil colored wires...gently pull up the wires from the mainboard..... battery is now disconnected.... to put back just push those wires back down onto its connectors....
to completely remove there are screws running along the battery... and two ribbons...detach ribbons and unscrew battery
same problem
i have the same problem how do u use adb to install rom?
or what do u use to install rom,adb or odin? and what procedure do you do? please reply immediately..thanks
See my signature
This thread saved my ass. I too was stuck at the system.img.
Tried to restore using ADB but no joy. I was still able to access the download mode so kept trying ODIN.
It turned out to be my USB 3.0 ports on my laptop.
As soon as I used my USB 2.0 ports on my docking station ODIN worked fine!:laugh:
gutomlagi said:
i have the same problem how do u use adb to install rom?
or what do u use to install rom,adb or odin? and what procedure do you do? please reply immediately..thanks
Click to expand...
Click to collapse
if odin hangs up halfway through the process, what u have to do is install stock recovery through odin.... then go in to recovery and format data...go back to odin and install clockwork recovery.... go back into recovery and mount system and mount data... next download a app called quick adb pusher on to pc select the rom u want to push... under destination type /data/media/ press send and install ur rom
Failed with Odin 3.09, worked with Odin 3.07
I don't know if this will help.
I needed to re-flash my SM-T310 with the Kitkat 4.4.2 Stock ROM. I found a page suggesting I used Odin 3.09 and the stock ROM pointed to from the Samsung site. I started the load, and saw the same problem, my Odin Log looked just like the one posted earlier. Out of sheer desperation, I started again using the version of Odin (3.07) I had previously used to load TWRP.
And it worked perfectly. Loaded the various components, rebooted, came up with the initial screen ... Phew !!
Maybe I just had some sort of nasty glitch, maybe Odin 3.07 is a bit less picky (!) I have no idea. All I know is it worked for me !!
I had this same problem - got stuck on system.img very near the end, stayed there for hours. Finally fixed it by attaching the usb cable to a different port *d'oh*
same problem stuck in system.img
sonko2k said:
Hi im trying to return galaxy 8.9 tablet back to stock using odin, but it gets stuck at system.img.md5 and wont move...is there any way to fix.. tried switching usb ports and no luck...please need help
alrigh... alrigh... alriiiight got it to work after almost 5 days with out a tablet....which i really missed... I finally fixed the god damn issues with this stupid thing.....
with odin constantly hanging on system.img i had to work around it...
first got odin far enough into system.img to were cwm would work
second i adb into the tablet and pushed rom file into sdcard
third i installed rom and finally got my tablet back
yessss
also learned how to open tablet and pull the battery out....which i didn't need to do at all
Click to expand...
Click to collapse
i dont get it what you are talking about like cwm and adb without any logic my phone is bricked and i need your help my flash just stuck in system.img
did you have any idea then please give a reply
..............
Hey guys, i really need some help here, i would really like to just hard reset my phone back to stock, and then i can start from scratch on rooting and what not. My problem is , the phone just wont reset ahha.
like i go into TWRP, and using this post " http://www.droidforums.net/forum/droid-bionic-hacks/234845-factory-bionic-stock-rom-ics-4-0-4-a.html " try and restore my device. Ive so far encountered probably every problem possible...following that post i DL the file and go to past it onto the device storage but i couldn't find the 3. Copy or Move Folder to your Backups....(Ex). Sdcard-Ext/TWRP/Backup.... so i just paste it into the TWRP file directory.from there i go to boot the device, it automatically boots in to adb usb mode stating that ( flash failed) i then have to hold the volume buttons and power to bring it back to the main recovery menu to boot normally!? thats only one problem, next i have Safestrap installed, it shows the start up screen i can continue or boot into recovery. Now in recovery following the instruction in the link provided i go and i 5. Select Stock ROM slot (Activate) and go select 6. Select Restore but theres noting in it, so i just go to install and find my file that i put there. i then do step 7. Select Factory Bionic Folder and 8. Flash it ( Swipe ). TWRP says it was complete but it only shows it going into the flashing process of installing update... so i reboot the phone and same thing, i get automatically pushed to the ABD USB screen saying flash failed. ... last problem , i go to boot past and theres no OS installed ... just a black screen ... im totally lost i dont know what to do hahah , any help here people??
anyone have any ideas on how to just restore this baby straight to stock ICS? thanks
P.S sorry for the bad quality photos, that what u get for taking pics with a razr haha
Dose anyone have any ideas at all, please??
I'd suggest hooking up your Bionic to a computer and FXZ through RSDlite.
Else if phone is bricked use fastboot and use the FXZ version of the stock image.
If you need the official FXZ for 246 ICS, one place to get it from is here:
http://sbf.droid-developers.org/cdma_targa/list.php
Sent from my DROID BIONIC using Tapatalk 2
---------- Post added at 01:17 PM ---------- Previous post was at 01:13 PM ----------
Need further help?
Google this: fxz fastboot bionic
There should be a YouTube video called 'unbrick factory reset droid bionic with fast boot and fxz', near the top of the search results. Watch it
Sent from my DROID BIONIC using Tapatalk 2
collije said:
I'd suggest hooking up your Bionic to a computer and FXZ through RSDlite.
Else if phone is bricked use fastboot and use the FXZ version of the stock image.
If you need the official FXZ for 246 ICS, one place to get it from is here:
http://sbf.droid-developers.org/cdma_targa/list.php
Sent from my DROID BIONIC using Tapatalk 2
---------- Post added at 01:17 PM ---------- Previous post was at 01:13 PM ----------
Need further help?
Google this: fxz fastboot bionic
There should be a YouTube video called 'unbrick factory reset droid bionic with fast boot and fxz', near the top of the search results. Watch it
Sent from my DROID BIONIC using Tapatalk 2
Click to expand...
Click to collapse
errr, bump? Do you still need help?
Hello Bueller?
I have made an effort to see if the issue I am encountering is found elsewhere in the forums, but I have not seen a similar posting so I hope someone would be kind enough to assist me with this issue.
I was attempting to port my droid 4 over from verizon to page plus, following instructions in a different forum (verified by others) and I have completely killed my droid 4.
It will not boot, it is not recognized by my computer, holding the volume/power buttons does nothing, holding the power/home keys does nothing. I have the latest motorola drivers
I am guessing this is a hard brick where there is nothing left for me to do except sell the phone for parts (purchased from craigslist).
Is there anything that I can do? I really appreciate any help offered, thanks for your assistance!
If your phone needs fastbooted and your D4 is out of juice, you're really screwed.
The only way to give it enough power to flash it back to working condition is get a factory cable that allows flashing without a charged battery or look up a how-to on stripping a usb cable and manually charging the battery.
Otherwise it's a brick.
Sent from my XT894 using Tapatalk 2
The Magician Type 0 said:
If your phone needs fastbooted and your D4 is out of juice, you're really screwed.
The only way to give it enough power to flash it back to working condition is get a factory cable that allows flashing without a charged battery or look up a how-to on stripping a usb cable and manually charging the battery.
Otherwise it's a brick.
Sent from my XT894 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your response! The battery was fully charged and I have a factory cable attached to my computer. I have RSD Lite and a the latest droid file to flash - the problem I am having is that the Droid 4 will not connect to my computer. Am I dead in the water?
Definitely not. Keeping the battery alive is key. Install the latest usb drivers. There's a link in the first post of this thread:
http://www.droidforums.net/forum/showthread.php?t=206972
Sent from my XT894 using Tapatalk 2
Dead Droid 4
The Magician Type 0 said:
Definitely not. Keeping the battery alive is key. Install the latest usb drivers. There's a link in the first post of this thread:
Sent from my XT894 using Tapatalk 2
Click to expand...
Click to collapse
Ok - I have been to that forum post before and the issue I am having is that the phone is not bootable. I cannot do a factory reset, I can't get it to boot period. As such it is not recognizable to my laptop via usb and therefore isn't able to be found through RSD lite.
From what I read in the link you set, as well as many other forums, it seems that their phones will boot and get stuck at a particular boot location. My phone (I have no idea what happened to it) is just black, doesn't turn on, doesn't provide any indicators (such as a charging light or network - nothing).
I have not been able to find a forum that indicates if there is anything that can be done for a 'non-booting' droid 4, the only thing I found was for creating a Jig for a Samsung phone that was bricked and wouldn't boot.
I do appreciate your help and thanks for your posts!
Let me try and understand better. Can you turn the phone on at all? Splash screen? Boot logo? Fastboot screen? If you need to fastboot your device you only need it to boot into the fastboot screen by performing a button combo.
If you have absolutely no way of turning it on or getting it to a fastboot screen, you'll need a motorola factory cable...
Sent from my XT894 using Tapatalk 2
Dead Droid 4
The Magician Type 0 said:
Let me try and understand better. Can you turn the phone on at all? Splash screen? Boot logo? Fastboot screen? If you need to fastboot your device you only need it to boot into the fastboot screen by performing a button combo.
If you have absolutely no way of turning it on or getting it to a fastboot screen, you'll need a motorola factory cable...
Sent from my XT894 using Tapatalk 2
Click to expand...
Click to collapse
Hello Magician, I cannot turn on the phone at all - no splash screen, no logo - no nothing. I do have the motorola usb cable that came with the phone.
There's a difference between the cable that comes with the phone and a "factory cable." A factory cable is one that has been modified to be flashable without a well charged battery.
If your battery is dead and you don't have a working os that supports charging, you won't be able to turn the phone on without a modified cable or hijacking a cable to manually charge the battery.
If the phone does have a working battery, you should be able to access the fastboot screen
Sent from my XT894 using Tapatalk 2
Dead Droid 4
The Magician Type 0 said:
There's a difference between the cable that comes with the phone and a "factory cable." A factory cable is one that has been modified to be flashable without a well charged battery.
If your battery is dead and you don't have a working os that supports charging, you won't be able to turn the phone on without a modified cable or hijacking a cable to manually charge the battery.
If the phone does have a working battery, you should be able to access the fastboot screen
Sent from my XT894 using Tapatalk 2
Click to expand...
Click to collapse
Ok, I see - that was not very clear to me before and I thank you for your assistance! I will purchase one now from ebay and will give a whirl when the cable comes in.
You're great, thank you for your time and patience!
link to motorola factory adapter from team black hat
only $10, and when I ordered 1 it took 3 days to get
it by passes battery, so phone can be flashed back to stock with xlm recovery file
Power off your phone, hold volume down button and press power button, until you see AP Fastboot Flash Mode
---------- Post added at 08:01 PM ---------- Previous post was at 07:59 PM ----------
install moto drivers Motorola_End_User_Driver_Installation_5.9.0
---------- Post added at 08:03 PM ---------- Previous post was at 08:01 PM ----------
download your recovery firmware image .XML recovery Files for Motorola Droid 4 (XT894)
Try plugging it into the wall charger. I had same issue and that fixed it but then again maybe i got lucky
Sent from my DROID4 using xda app-developers app
that may work, but moto phones require software to charge
if the software is wrong it will not charge
Dead Droid 4
sd_shadow said:
link to motorola factory adapter from team black hat
only $10, and when I ordered 1 it took 3 days to get
it by passes battery, so phone can be flashed back to stock with xlm recovery file
Power off your phone, hold volume down button and press power button, until you see AP Fastboot Flash Mode
---------- Post added at 08:01 PM ---------- Previous post was at 07:59 PM ----------
install moto drivers Motorola_End_User_Driver_Installation_5.9.0
---------- Post added at 08:03 PM ---------- Previous post was at 08:01 PM ----------
download your recovery firmware image .XML recovery Files for Motorola Droid 4 (XT894)
Click to expand...
Click to collapse
Ok Shadow, I purchased and downloaded, great thanks for the links, it has been a challenge to find all of the downloads I have been needing. I am hoping persistence leads to victory.
that's why I started my list
sd_shadow's [Collection] of Links: FAQs, Guides, Rooting, SBFs, ROMs... - Google Docs
Dead Droid 4
rruleford said:
Try plugging it into the wall charger. I had same issue and that fixed it but then again maybe i got lucky
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
Hi rruleford, I gave it a shot a couple of times and it didn't work. thank you for the suggestion!!
there is also a
Droid 4 Utility ICS Only recovery/root/safestrap
Dead Droid 4
sd_shadow said:
there is also a
Droid 4 Utility ICS Only recovery/root/safestrap
Click to expand...
Click to collapse
I did use that utility when I was attempting to port over to page plus and this is where I started my trouble I think. the error was completely mine, I hit enter twice on my computer in the early stages of the sequence and the phone went black immediately after.
could you post link to the method you were using to flash phone to page plus
you may need to put spaces in link, because you do not have many posts
Dead Droid 4
sd_shadow said:
could you post link to the method you were using to flash phone to page plus
you may need to put spaces in link, because you do not have many posts
Click to expand...
Click to collapse
This is the post I followed:
www.howardforums.com/showthread.php...manual-activation-talk-text-mms-3g-and-rooted
I got stuck at the second screen.
Sorry it didnt help. Hope all turns out well for you...
Sent from my DROID4 using xda app-developers app
Okay, so I know there are a bunch of threads concerning boot loops, but I just do not know where to go next. So, I was trying to update to Cyanogen mod 10.1 from eclipse gingerbread with clock work mod. The flashing seemed successful, but the phone will only go to the red motorola screen. I cannot seem to find clockwork mod at all with numerous different button combinations. I am able to get into the boot menu and the android system recovery, but flashing any .zip file results in a whole value signature error. Please help me as I can not go long without a phone and thank you in advance. I've tried using Rsd lite 5.6 to flash back to stock, but there was a low battery warning that prevented it. Is there any way to accomplish charging without buying an external battery charger or cable?
Machete.jh said:
Okay, so I know there are a bunch of threads concerning boot loops, but I just do not know where to go next. So, I was trying to update to Cyanogen mod 10.1 from eclipse gingerbread with clock work mod. The flashing seemed successful, but the phone will only go to the red motorola screen. I cannot seem to find clockwork mod at all with numerous different button combinations. I am able to get into the boot menu and the android system recovery, but flashing any .zip file results in a whole value signature error. Please help me as I can not go long without a phone and thank you in advance. I've tried using Rsd lite 5.6 to flash back to stock, but there was a low battery warning that prevented it. Is there any way to accomplish charging without buying an external battery charger or cable?
Click to expand...
Click to collapse
Do you have a warranty still? best way to flash roms is through safestrap. That app is almost fool proof.
the only way to be able to reprogram the thing to stock with no battery life left would be to either purchase a motorolla factory cable (or make your own from a spare usb cable) which when used should automatically put your device into factory reprogramming mode.. if im not mistaken this will even work with no battery in there at all. then just RSD lite to FXZ back to stock.
I guess I should have closed this a while ago. The phone is fixed. Sorry for not updating.
Sent from my Galaxy Nexus using xda app-developers app
Machete.jh said:
I guess I should have closed this a while ago. The phone is fixed. Sorry for not updating.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Grats!