Related
okay guys here's my issue. I was flashing over to liberty and I forgot to wipe everything so as liberty was going through its stuff through bootstrap I pulled the battery hoping to stop the process.
HOWEVER, I am not stuck at the "liberty" logo. I have tried to sbf and I am getting....
failed flashing process: Phone (0000): Phone did not re-enumerate after RAM-downloader was sent. (0x703E) phone was disconnected.
Can someone please help me?
I've seen people have sucess with SBF errors by renaming the SBF file, trying a diff comp, and if ya vista or win7 ya have to be running as Admin. Give any of those a try that ya can while I'm looking over google to see if I can find anything more directly relevant to the errors you are getting.
Luckily I still have my x sitting around. I'm using macbook pro with vmware running windows 7. I have sbfed successfully on my x using the same setup.
Sent from my DROIDX using Tapatalk
I should also note that I tried booting into recovery and wiping data and cache still didn't help.
I do have a backup of stock from that I made. However, I just don't think its possible for me to access that backup to restore?
Sent from my DROIDX using Tapatalk
I'm not sure then. I've looked over quite a few different articles were people have had this problem, and have had it solved, and everytime it was some type of comp issue that was causing it. Some people fixed by changing USB ports, some by reinstalling the Moto RSD software (Also, with RSD, make sure you are using version 4.8 or 4.9), or using a completely different computer or OS. Past that the only other thing I can suggest is make sure you have the correct SBF file, and maybe try re-downloading it incase it somehow got corrupted during the download.
EDIT: Which recovery are you using? The stock recovery, or Clockwork? If ya using stock, then as far as I am aware you don't have the ability to backup/restore.
-Gilgamesh- said:
I'm not sure then. I've looked over quite a few different articles were people have had this problem, and have had it solved, and everytime it was some type of comp issue that was causing it. Some people fixed by changing USB ports, some by reinstalling the Moto RSD software (Also, with RSD, make sure you are using version 4.8 or 4.9), or using a completely different computer or OS. Past that the only other thing I can suggest is make sure you have the correct SBF file, and maybe try re-downloading it incase it somehow got corrupted during the download.
EDIT: Which recovery are you using? The stock recovery, or Clockwork? If ya using stock, then as far as I am aware you don't have the ability to backup/restore.
Click to expand...
Click to collapse
I am using rsd 4.9. I tried everything you stated except a new computer.
I have droid 2 bootstrapper installed and clockwork. However, whenever I boot into recovery it keeps bringing me to the stock one so I can't restore. If I can figure out how to restore maybe I would be good?
Sent from my DROIDX using Tapatalk
Likely you got far enough into SBF to erase clockwork. Though you can try pulling you battery during boot while its on the moto logo, and if clockwork is still installed it will then boot directly to it.
Yupp nothing. Stuck at the liberty boot logo where it says "liberty"
Sent from my DROIDX using Tapatalk
I donno then. I would try a diff comp and see if that helps. Or maybe someone else will see this thread and have some other ideas. You may could also try posting directly in the SBF thread, maybe someone with more experance with it will see it there? Just a thought.
Thanks for the help.
If anyone else can help I am all ears!
Sent from my DROIDX using Tapatalk
Ok, the bad news...
The first thing Liberty does when installing is format the /system directory. I dont know at what point you pulled the battery but, while you did at one time have bootstrapper and clockwork mod installed, you no longer do. Your only option at this point is to SBF.
I have had, as have others, lots of issues with getting it to go through on Windows 7. It will get to a point where it tries to switch modes (unfortunately I don't recall the name of that mode right now), then it wont find the driver fast enough and fail. If you can get that driver installed when it tries to switch modes, it should work, and cause no problems in the future. The problem for you though, may be even greater given that Windows 7 is bad enough and being run in VMware probably will just compound those issues.
If at all possible, try from a windows XP machine.
OK so im not sure about the Liberty ROM however I have had to SBF when I tried installing Fission 2.4.3 on my D2G.
My process was turning the phone on boot mode. This is done but holding the +- Volume button and then hitting the power button.
Next I got RSDLite 4.9 and lastest drivers from motorola. Next is restart computer! This was important as RSD wasn't finding my phone until I did. Once I restarted ran RSD hooked up the phone in boot mode found the sbf file and hit start. Took about 15 min to finish.
Not sure if this helps.
Rsd is finding my phone no problem right away. I suppose I should try it on a different computer though, one that's running xp.
Sent from my DROIDX using Tapatalk
buryboi said:
Ok, the bad news...
The first thing Liberty does when installing is format the /system directory. I dont know at what point you pulled the battery but, while you did at one time have bootstrapper and clockwork mod installed, you no longer do. Your only option at this point is to SBF.
I have had, as have others, lots of issues with getting it to go through on Windows 7. It will get to a point where it tries to switch modes (unfortunately I don't recall the name of that mode right now), then it wont find the driver fast enough and fail. If you can get that driver installed when it tries to switch modes, it should work, and cause no problems in the future. The problem for you though, may be even greater given that Windows 7 is bad enough and being run in VMware probably will just compound those issues.
If at all possible, try from a windows XP machine.
Click to expand...
Click to collapse
Do you know what driver your talking about or where to find it?
Okay guys I tried doing it on Windows XP and I am still getting the same exact message it wont' re-enumerate.
I am scared beyond belief right now and don't know what to do. If someone can suggest something I would really appreciate it.
Not sure if this helps, but this is what "my device" info says while in rsd lite...
IMEI/ESN/MEID:
N / A
Technology:
N / A
Software Version:
N / A
Flex Version:
N / A
Bootloader Version:
v0x00D011
DRM Version:
N / A
AP Die ID:
14b0001391953a0a0000d8ff0100
BP Die ID:
0000000000000000cd6932890485
AP Public ID:
6df40c77da38d6f01bc27cc2f40c041ee4491ae2
BP Public ID:
040000000500000002000000ffff0000ed153289
If you are on Win7 64 then try the drivers in the attached zip file.
It is the BP passthrough mode that fails at the end of the flash because it needs to load a separate interface to flash the baseband radio partition.
That interface is a Motorola Flash device MDM6600 and not the S-Flash OMAP3460 device.
If you are having trouble with the drivers loading during the flash cycle re enumeration then you can try this trick to get them to load.
Turn off the phone and then power on holding the Volume Up + Power.
The phone will boot to the M Logo and just stay there like it is hung.
It is now in BP passthrough mode and will enumerate as a Motorola MDM6600 flash device and Windows will attempt to load those drivers when you connect the USB cable. Point the New Hardware Found wizard to the folder where you extracted the zip and it should load them. If not, you may have to manually force it to load them in the Have Disk dialog.
Now pull the battery and reboot the phone normally and try flashing in RSD Lite again. You will already have the BP passthrough interface drivers loaded now and it should re enumerate and complete the flash of the baseband(CG5) and reboot the phone at the end. Wait at least a minute after it reboots for all the post boot initializations to complete and RSD Lite should eventually say Pass and allow you to disconnect without the error warning about damaging the attached device.
If none of this works, get an XP box and it will all work without any issues 99% of the time.
Good luck!
Okay... So I downloaded the drivers, connected via USB and it did show up as what you said it would. However, I then ran the sbf and it says "The Motorola AP flash interface could not be found and kept failing.
What do I do?
Also, another thing it now says my battery is low. If I just plug it into the wall, will it charge or do I need to USB it? I can't tell if its charging or not
nickb2005 said:
Also, another thing it now says my battery is low. If I just plug it into the wall, will it charge or do I need to USB it? I can't tell if its charging or not
Click to expand...
Click to collapse
It won't charge in the bootloader until you have software on your phone you need to use another D1 or D2 to charge. Or use an external charger.
If windows isn't working there are ways to flash in linux that usually yield better results.
Sent from my DROID2 using XDA App
Ok guys, here I am - finally.
This forum is my last chance as I am going mental trying to find a solution to this issue searching the internet.
My Defy won't charge!!!
It won't charge from a socket, not form the PC via USB.
And It's not the hardware failure, 100% sure.
Now,
Imagine you have a rooted defy with original stock rom.
Everything is fine and you never experienced any real problems with the phone apart from freezing maybe but this is nothing (just uninstall all the unnecessary crap and you'll be fine).
Anyway you decided to play with custom roms, and as this is you first time you do two very important things: back up you current rom and back up all you apps using Titanium Backup.
You also have clockworkmod recovery.
Now,
Here where the problem started - I download new ROM using Rom Manager but when I tried to install it I was given a message: The phone will be turned off and instalation will continue in recovery mode. And when I pressed yes nothing happened.
Next I did the most stupidest thing ever - I installed 2ndinit recovery and THAT'S IT - after reboot - no sign of life whatsoever. I am still asking myself why on Earth I did that.
Oh no, I can get to bootloader but it is saying that battery low cannot program.
I can also get to android recovery mode but this is not clockworkmod recovery and there is no option for restore. I only can wipe cache and restore to factory state but it does not help.
I was trying to get into RSD solution but PHONE IS DEAD, CAN'T DO THAT!
ANY SUGGESTION, I do not want to believe that this is the end for the great handset.
Anything anybody......???????????????????????
Can you see the device when it's connected to a computer? Then you should be able to flash clockwork recovery again using adb. Follow the 'Installing bootmenu & the ClockworkMod Recovery' instructions on the Cyanogenmod wiki / Defy full update guide.
Then you can restore your backed up ROM.
Actually It's not detected by PC just because battery is dead.
So when I get it charged somehow I certainly will try that. Thanks
It won't charge even when the phone is powered off? Have you tried a different USB cable? Maybe you know someone else with a Defy that you can swap batteries with. Or get one of those external battery chargers. It's starting to sound more like a hardware problem, then a software problem with your ROM.
I recently picked up a Pantech Burst phone from At&t, and upgraded to ICS. I then proceeded to root the phone using the prestoroot.img method and it worked. Everything was running dandy until I got the VM Heap tool app and(stupidly) set the vm heap to 52m and attempted to reboot... It failed and all I got was a loop of boot up animations. I tried several times to reboot, and then tried to boot to recovery mode and factory reset. That worked, but it STILL didnt reboot..! I dont have a backup, and whenever i try to " Install update from external storage", it just fails over and over again. I found thestock firmware and downloaded it to my external sd card and install(still to no success). Im only 13 and cant afford a new phone! PLEASE SOMEONE HEEEELLLLPPPPPP!!!!!!!!!!!!!
Use P9070_Download_Tool_v3.3.zip and flash PRESTO_BIN_JUUS09032012_TP20_user using this method http://forum.xda-developers.com/showthread.php?p=28602800#post28602800. You might find other answers in that same thread Pantech Burst Essentials.
I love you!!!!!!!
dvinelord said:
use p9070_download_tool_v3.3.zip and flash presto_bin_juus09032012_tp20_user using this method http://forum.xda-developers.com/showthread.php?p=28602800#post28602800. You might find other answers in that same thread pantech burst essentials.
Click to expand...
Click to collapse
it workkeed!!!!!:d
DvineLord said:
Use P9070_Download_Tool_v3.3.zip and flash PRESTO_BIN_JUUS09032012_TP20_user using this method http://forum.xda-developers.com/showthread.php?p=28602800#post28602800. You might find other answers in that same thread Pantech Burst Essentials.
Click to expand...
Click to collapse
I bricked my phone few days back doing restore from CWM 6 downloeded online from ROM manager,
I wiped cache dalvik etc & rebooted, I could see the Tap the android screen then suddenly blank now it wont start
I get QHSUSB_dload in PC device manager any way out
I tried this method but I dont get the download button to click it remains greyed out.
Is there any driver for QHSUSB_dload?
Or do I have no hope at the moment or in near future?
just don`t use ROM manager for installing recovery . usually the result is bricked phone
Yah, i remember a fastboot brick i got from rom manager (LG Optimud ME)
Sent from a 2.8 inch screen
I also just bricked my Pantech Burst the same way...using ROM Manager. Is there a way to fix this or am I out of luck? I did try the method posted at the top of this thread. It just gets locked in the S/W Upgrading screen. Any help will be greatly appreciated.
I'm too in same situation.....i tried it updating via Pantech OS Upgrade tool......it updates successfully but doesnot bootup....
and now it shows some S/W Upgrading with red colour background
plz help me out:crying::crying::crying::crying::crying:
coolamjadkhan said:
I'm too in same situation.....i tried it updating via Pantech OS Upgrade tool......it updates successfully but doesnot bootup....
and now it shows some S/W Upgrading with red colour background
plz help me out:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Mine did not upgrade successfully, but I have the exact same problem. On day three of waiting for a callback from Pantech on the issue. They are supposedly talking to the techs in Korea about it.
Maybe solved!
tajlund said:
Mine did not upgrade successfully, but I have the exact same problem. On day three of waiting for a callback from Pantech on the issue. They are supposedly talking to the techs in Korea about it.
Click to expand...
Click to collapse
Don't know if this is going to help, but I had the problem (as I described) red S/W Upgrading and couldn't do anything. Well, after about two weeks of sitting with the battery out, I decided to redownload and rerun the Pantech update app, and lo and behold, it fixed my phone. It also installed a more up to date version of Android 4.0, I went from 4.01 to 4.04.
This is after running the updater a good 30 or so times the past two weeks hoping for anything to work, now today, bam, it works fine.
I would recommend anyone in this situation give the most recent updater a try, it may solve your problem.
need help with my burst!!!!!
Hey! i have a pantech burst and i love it! but i had to reset it and now it wont work. my exhusband root it a few months ago....and he deleted the keyboard and the launcher..... so.... when i turn it on i cant do anything cause i cant write .... and if i skip the android start menu i cant see anything cause i dont have a launcher.... please someone help! what can i do?
:crying: Bricked my phone total unable start. any hardware diagnostic tool or manual reset button.
please help urgently
needhelppantech said:
Hey! i have a pantech burst and i love it! but i had to reset it and now it wont work. my exhusband root it a few months ago....and he deleted the keyboard and the launcher..... so.... when i turn it on i cant do anything cause i cant write .... and if i skip the android start menu i cant see anything cause i dont have a launcher.... please someone help! what can i do?
Click to expand...
Click to collapse
would you like to sell it cheaper rate???
Bricked Pantech Burst Stuck in S/W Downloading Mode and completely wiped ...
Ok I am having a similar issue guys. Last night I had to wipe my phone because it was overly full and I switched providers and the phone had become unusable. I tried using clockworkmod to do this and it wiped everything ( including clockworkmod. ) Now I only get a S/W Upgrading screen with a red box. I tried using the pantech download tool and the PANTECH_PRESTO_BIN_JUUS03122012.pdl file. It did appear that it was installing it but then it became stuck at the very very very end of things. I basically had to take the battery out to do anything at all as I had left the phone on all night to download the pdl file but without any luck.
When I reboot the phone it had the S/W Upgrading mode with the red screen. I've tried all of the different key combinations on the pantech burst etc volume up + volume down and power, volume down + power, volume up + power. None of these things will reboot the phone.
I am hoping I can use the pantech download tool to install a different pdl instead and possibly get it working that way. I know that when the phone is off if I plug it into usb then the screen lights up on it with the S/W Upgrading screen and the red box. If I press the power button or any other combinations of buttons + the power button it also does this. It literally will not do anything else.
I cannot use pantech pc suite because the phone originally was so unusable I could not put the android apk file on the phone even though I have it on my laptop.
I tried using adb and fastboot and it will not even find my device through ANY usb port on the laptop. I've tried deleting and reinstalling the drivers over and over. The only thing I know to do is reboot afterward and hopefully it will find my phone on usb with adb. If I can just get to a bootloader or flash functional firmware onto this phone I think I could get it working but I do not know enough about the pantech burst to try physically jumping anything on it in order to hard reset it.
So my only options right now look like maybe get a different pdl, possibly reboot and the drivers may find my phone, or JTAG this thing.
I can't put it in usb debugging mode because it won't boot. Since adb does not even find the device as being attached it seems as if this phone should be operating in a different port mode or something to make it visible. I could be wrong but I am hoping that rebooting fixes the driver issue and makes the phone visible.
I tried PDAnet also and once again it does not work because it cannot find the device. This could be a usb cable issue I suppose but I only have this particular cable I am pretty sure
I might try another cable as well...
Any other ideas ? Am I going to have to JTAG this thing or should it be fixable using the download tool and a different pdl ? Or do I need to find another way to completely wipe the phone first and THEN use the download tool with the pdl file ?
It does get a bit confusing with so many mods, roms, and methods to recover android phones. If I can get the phone to boot then I can reload my backups and all should be well. I do need this phone for business purposes also. Any ideas guys ?
PS> I am also pretty decent with linux distros like arch or ubuntu so I would like to also know if it would just be better to do this in linux and possibly use linux to manually switch the phone to a different device mode to make it visible in the instance of there being nothing wrong with the drivers.
Thanks for any ideas or suggestions ...
UPDATE - progress ???
dsull1981 said:
Ok I am having a similar issue guys. Last night I had to wipe my phone because it was overly full and I switched providers and the phone had become unusable. I tried using clockworkmod to do this and it wiped everything ( including clockworkmod. ) Now I only get a S/W Upgrading screen with a red box. I tried using the pantech download tool and the PANTECH_PRESTO_BIN_JUUS03122012.pdl file. It did appear that it was installing it but then it became stuck at the very very very end of things. I basically had to take the battery out to do anything at all as I had left the phone on all night to download the pdl file but without any luck.
When I reboot the phone it had the S/W Upgrading mode with the red screen. I've tried all of the different key combinations on the pantech burst etc volume up + volume down and power, volume down + power, volume up + power. None of these things will reboot the phone.
I am hoping I can use the pantech download tool to install a different pdl instead and possibly get it working that way. I know that when the phone is off if I plug it into usb then the screen lights up on it with the S/W Upgrading screen and the red box. If I press the power button or any other combinations of buttons + the power button it also does this. It literally will not do anything else.
I cannot use pantech pc suite because the phone originally was so unusable I could not put the android apk file on the phone even though I have it on my laptop.
I tried using adb and fastboot and it will not even find my device through ANY usb port on the laptop. I've tried deleting and reinstalling the drivers over and over. The only thing I know to do is reboot afterward and hopefully it will find my phone on usb with adb. If I can just get to a bootloader or flash functional firmware onto this phone I think I could get it working but I do not know enough about the pantech burst to try physically jumping anything on it in order to hard reset it.
So my only options right now look like maybe get a different pdl, possibly reboot and the drivers may find my phone, or JTAG this thing.
I can't put it in usb debugging mode because it won't boot. Since adb does not even find the device as being attached it seems as if this phone should be operating in a different port mode or something to make it visible. I could be wrong but I am hoping that rebooting fixes the driver issue and makes the phone visible.
I tried PDAnet also and once again it does not work because it cannot find the device. This could be a usb cable issue I suppose but I only have this particular cable I am pretty sure
I might try another cable as well...
Any other ideas ? Am I going to have to JTAG this thing or should it be fixable using the download tool and a different pdl ? Or do I need to find another way to completely wipe the phone first and THEN use the download tool with the pdl file ?
It does get a bit confusing with so many mods, roms, and methods to recover android phones. If I can get the phone to boot then I can reload my backups and all should be well. I do need this phone for business purposes also. Any ideas guys ?
PS> I am also pretty decent with linux distros like arch or ubuntu so I would like to also know if it would just be better to do this in linux and possibly use linux to manually switch the phone to a different device mode to make it visible in the instance of there being nothing wrong with the drivers.
Thanks for any ideas or suggestions ...
Click to expand...
Click to collapse
--------------------------------------------------------------------------
OK quick update, I found the pantech burst upgrade tool and the burst-hack.cmd script
I managed to successfully find my phone with the upgrade tool and it completely ran its course and I am guessing it installed Ice Cream Sandwich.
My new problem is that the phone goes to the pantech logo boot screen if I plug the phone into usb but that is all it will do. If I unplug the phone and try to get into S/W Upgrade mode again or power it on it will not do anything at all. Basically the display only comes on when plugged in at this point so I am wondering if the battery is even charged or if it will charge. I read somewhere ( in the gizmolord forum ) that a guy had the same issue as me and he ran this tool for his pantech burst and then left the battery out for 2 weeks and tried to power it back on and it worked for him.
Is it possible that I just need to power the device down completely and let it completely discharge before it will reboot or is this thing bricked ?
I am thinking that either the battery needs to charge, or the phone needs to discharge and power down completely, or the phone could be bricked. I have a feeling it is not bricked because the update tool said everything was successful and no errors or anything.
I will try leaving the battery out for awhile and letting the phone discharge on its own and see what kind of results I get. I would think that 16 - 24 hours would be sufficient. Any ideas ?
---------------------------------------------------------------------------------------------------------------------
Ok so I did a bit more digging and research and found out that the culprit is most likely the poorly designed charging circuit in the pantech phones. I found a tech blog called Mikes Techblog where he shows how to solve this on a pantech jest phone with the same issue. The problem is that the battery is 3.7v and is currently reading 2.8v on the volt meter. The phone will not even attempt to charge until 3.7v is available on the battery because of how the charge circuit is designed. I am going to try the usb cable trick and usb adapter and see if I can monitor its progress with the voltmeter and get it back up to 3.7 volts. After this it should allow me to charge it normally and should boot just fine. It is showing the pantech logo which tells me that the firmware is there and isn't buzzing or doing anything else weird so more than likely this is related to the battery and not having enough of a charge when running the official upgrade tool. This problem probably had already existed prior running the update tool and is why the S/W Upgrading screen only would come up AFTER being plugged into a power source and would disappear immediately. If the battery had any charge whatsoever and if the phone could see it then I would see a screen that tells me to plug my phone in and charge it. I am thinking this is solved but will only know after I charge the battery. From what I've been reading in comments from others the battery issue is prevalent on many different pantech phones including the burst model. Other people with the pantech burst have said in comments on Mike's blog that this made their phone boot right up and said that this was EXACTLY the issue. Perhaps the best way to use these pantech phones is to never ever let them fully discharge the battery.
I am on a Verizon Razr Maxx HD (xt926). This all started when I decided to cleanly flash the newest version of CM10.2. I had been running it before. I wanted to start from a blank slate, so I went into TWRP and did the format wipe. Installed the newest CM10.2 nightly and gapps. This went fine and I booted into the ROM and started recovering all of my stuff. I installed F-droid and AdAway, and rebooted for that. The phone never got past the Bootloader Unlocked warning screen. I turned it off and went into TWRP to try some things. I tried to fix permissions, but it failed, referencing something to do with fdroid. I wiped again and reinstalled CM, but I still couldn't get past the Bootloader Unlocked warning.
I booted into TWRP again and wiped what I could, and accidentally wiped my external SD, and I had no card readers lying around to get the ROM zips back onto it. I downloaded the Razr HD utility, used the batch file, and tried to flash the stock rom through fastboot, but it got stuck in some kind of loop and would not flash correctly. I then tried to do it manually, but got some sort of buffer error. I tried again, and it started ok but I never saw it actually finish flashing.
By this time I finagled the ROM zips onto the SD card and stopped the fastboot and booted into TWRP. I did another set of wipes, and rebooted into TWRP again. I flashed the CM and Gapps. The ROM booted fine from TWRP and I was able to start setting up my account again. I tried rebooting after the initial setup just to see if it was working correctly, and was met with the fastboot screen with fastboot reason: Flash failed. I rebooted into TWRP from there, and tried to boot normally, but it still brought me to the fastboot. I went to the boot menu and tried the normal boot selection, and now my phone is stuck on the Bootloader Warning screen and now it won't even turn off when I hold the power button.
I have no idea what is going on, or why I could get to the working ROM once but not again. Does anyone know anything that could help me?
Kopiok said:
I am on a Verizon Razr Maxx HD (xt926). This all started when I decided to cleanly flash the newest version of CM10.2. I had been running it before. I wanted to start from a blank slate, so I went into TWRP and did the format wipe. Installed the newest CM10.2 nightly and gapps. This went fine and I booted into the ROM and started recovering all of my stuff. I installed F-droid and AdAway, and rebooted for that. The phone never got past the Bootloader Unlocked warning screen. I turned it off and went into TWRP to try some things. I tried to fix permissions, but it failed, referencing something to do with fdroid. I wiped again and reinstalled CM, but I still couldn't get past the Bootloader Unlocked warning.
I booted into TWRP again and wiped what I could, and accidentally wiped my external SD, and I had no card readers lying around to get the ROM zips back onto it. I downloaded the Razr HD utility, used the batch file, and tried to flash the stock rom through fastboot, but it got stuck in some kind of loop and would not flash correctly. I then tried to do it manually, but got some sort of buffer error. I tried again, and it started ok but I never saw it actually finish flashing.
By this time I finagled the ROM zips onto the SD card and stopped the fastboot and booted into TWRP. I did another set of wipes, and rebooted into TWRP again. I flashed the CM and Gapps. The ROM booted fine from TWRP and I was able to start setting up my account again. I tried rebooting after the initial setup just to see if it was working correctly, and was met with the fastboot screen with fastboot reason: Flash failed. I rebooted into TWRP from there, and tried to boot normally, but it still brought me to the fastboot. I went to the boot menu and tried the normal boot selection, and now my phone is stuck on the Bootloader Warning screen and now it won't even turn off when I hold the power button.
I have no idea what is going on, or why I could get to the working ROM once but not again. Does anyone know anything that could help me?
Click to expand...
Click to collapse
Try the solution in the last few posts on this thread. http://forum.xda-developers.com/showthread.php?t=2465695
I hope you get more knowledgeable advice than mine but, were I in your situation, my primary goal would be to get back to STOCK. Forget CM and modding for now. Either through TWRP or through the recovery settings on the phone itself I'd get to where I could do a factory reset. If you're continuously able to boot into TWRP I don't see how your phone could be bricked. My experience is, if I can get a phone to do ANYTHING I've got a shot at figuring out how to get out of whatever mess I've created. I don't know if this could be a factor but I'd put in a different micro SD card too, in case there's something on the card you've got in there.
Just an update. So, I got it to go back to fastboot this morning and I tried using the Razr Utility to flash back stock and stock recovery, but I got a "Failed" line with the reason "Remote Failure". Not sure what that's about. When it reset it got back to the Cyanogenmod boot graphic, but it never started. I left it there for a good 12 minutes.
Right now it's sitting in TWRP. I'm going to let it charge to 100% (it was a little less when I tried all of this) and attempt it again at 100% battery. Thanks for the help so far!
So, I tried using the Razr Utility to flash the system, kernel, radio and for system it was unsuccessful (something about too many threads or strings, something to that effect), but the rest said OK. Now my phone doesn't seem to turn on. My computer still makes the device plugged in sound when it's plugged/unplugged, but I cannot get the screen to show anything or seem to turn on the phone.
Is this it? Is it... bricked!? ;-;
Edit: I ordered the Factory Adapter as a last resort sort of thing. This is lame.
Edit Edit: I've seen the boot logo since my last edit! But... it's not coming back and I still can't even bring up the bootloader. I don't know why it will sometimes turn on or sometimes not. In any case, I'm now hopeful that not ALL is lost.
Bottom line, the adapter will allow you to fix your phone and flash the stock FXZ in RSD Lite or fastboot and get back to a clean slate and start over.
That's why we went to the trouble of making them!
cellzealot said:
Bottom line, the adapter will allow you to fix your phone and flash the stock FXZ in RSD Lite or fastboot and get back to a clean slate and start over.
That's why we went to the trouble of making them!
Click to expand...
Click to collapse
That's the plan! One odd thing happening now... My phone's screen isn't showing anything, so I assumed it was off. I left it unplugged and went to see a movie..... and the phone is still warm. This leads me to believe the phone is still drawing power, for some reason... God this is weird. I'll wait for the adapter and try again. Thanks for the help!
cellzealot said:
Bottom line, the adapter will allow you to fix your phone and flash the stock FXZ in RSD Lite or fastboot and get back to a clean slate and start over.
That's why we went to the trouble of making them!
Click to expand...
Click to collapse
according to the packaging on mine from tbh a chinaman made it, just sayin
Yes, we designed them and contracted through our US supplier who produced all of our cables who, in turn, had them produced in China according to our specifications. There is no longer any injection molded plastic production done in the US that can work at this small scale for affordable rates.
Sorry...that's the way the world works these days.
cellzealot said:
Yes, we designed them and contracted through our US supplier who produced all of our cables who, in turn, had them produced in China according to our specifications. There is no longer any injection molded plastic production done in the US that can work at this small scale for affordable rates.
Sorry...that's the way the world works these days.
Click to expand...
Click to collapse
thanks for making it either way, better to have and not need.
havent had to use it so far
bweN diorD said:
thanks for making it either way, better to have and not need.
havent had to use it so far
Click to expand...
Click to collapse
You're welcome! They are definitely the best $10 investment you can make in any Motorola phone.
Next time you want to invest many thousands of dollars of your own money in a wild, hairbrained scheme to help a bunch of anonymous people on the internet fix their phones that they recently finished destroying themselves, let us know...we have just the plan!
cellzealot said:
You're welcome! They are definitely the best $10 investment you can make in any Motorola phone.
Next time you want to invest many thousands of dollars of your own money in a wild, hairbrained scheme to help a bunch of anonymous people on the internet fix their phones that they recently finished destroying themselves, let us know...we have just the plan!
Click to expand...
Click to collapse
how many thousands, and whats the plan?
I got the Factory Adapter and used RSD Lite to flash stock. And it works! Yay! It's starting up reliably and everything.
Except... it won't start up without the cable attached, and the battery icon has a big question mark on it. It also won't connect to the cell network (but does connect to WiFi). What do I do now?
Edit: So I noticed that while the battery status said "Unknown", it did go from 2% to 3% charge level when I plugged it in normally for a little. My plan at the moment is to try leaving it plugged in for a while and then try taking the OTA update to see if that fixes everything. Good plan?
Edit Edit: Never mind! I just had to let it charge for a bit. It seems to be back in working order, now! Thank you so much for all the help everyone!
That is exactly what is supposed to happen. Congrats on fixing your phone!
The factory cable/adapter does not charge the device but powers it directly, allowing it to boot no matter what state the battery is in or even without a battery at all.
You cannot charge in bootloader, which is why the cable/adapter is so valuable. Once the device can boot/charge normally then you are all set.
I'm stumped with this issue of my Motorola Razr HD LTE XT925 Rogers version 4.1.2 being in a boot loop. It started when I did a factory reset to try and fix some camera issues that I was having it started up with the Motorola red M icon then went to proceed with the factory reset with the android icon with the spinning blue object then restarts and just does a loop I have tried some steps that I found that I will list but all are unsuccessful and I did try them several times. It is stock firmware but was rooted with one click rooting program can't remember the name I did nothing else to the firmware.
Power + volume down for 10 seconds (simulates a battery pull)
Stock recovery tried wiping data and cache and then rebooting
Tried to use the boot menu normal start up and factory options
I did however get it to boot to the Rogers logo screen once but it just froze and had to restart it
I am currently trying get ADB tool to installed and get it working to see my phone as well as RDS Lite 6.1.6 it wont show any info about the phone but when in fastboot mode RDS Lite see it as connected in fastboot but no info about the phone shows up in the top left box as it has shown before also tried Super ADB Tool it show nothing at all I will continue to try and get the tools working.
Any help in getting the phone to boot normally is greatly appreciated.
I was also wondering if any body knows a good way to completely wipe the razr XT925 and restore the stock firmware that would also help.
OK so I have ADB installed and working I think put my XT925 in fast boot mode then I put in code adb devices in to the windows command console but show nothing listed and my phone says it is in fastboot mode and usb is connected and windows sees it as well but not ADB. There is no errors ether I am so confused as to why ADB and RSD show no info about my phone? I will see if its any of my drivers that are missing.
I went ahead and tried to flash my phone with RSD lite 6.1.6 with no luck the boot loop is preventing it from proceeding with the flash is this just a lost cause and there is no fix for it. The only thing I can think of is that I have to unlock the boot loader is that even an option when I can't even get boot into android? Any one got any ideas?
I was messing a round with my phone and try to get it working with any of the tools and had turned of the phone to stop it from constantly showing the red M icon and the android icon with the blue spinning object over and over but still had the phone plugged in to the computer and was looking in device manger in windows and seen this QHUSB_DLOAD with no drivers for it and looked at the VID & PID ids (USB\VID_05C6&PID_9008
) and searched for drivers thinking that is what is missing for my phone as I have never see it before and it is Qualcomm modem flashing port I don't know what to do did really mess up my phone by just doing a factory restore?
Some help or clarification would help a lot now as it is a bit troubling that I am unable to fix the Motorola Razr XT925 and might be bricked just by doing a factory restore. :silly:
OK I am getting desperate here I will do anything to stop it from looping I have even tried house of motos way just the same thing still if I can stop it from looping I can get it to work but does anyone knows a way to wipe the phone completely or stop it from this infuriating loop???
Just as a side note I found that forcing it in to normal start up with the wall charger plugged in it will charge when done then it will show the rogers logo like its booting but does nothing.
I have searched the forms and google now for 2 days about any way to fix the boot loop but all just say to do things that I have tried many different ways many times and the tools don't work or will work like RDS but it is unable to continue do to the loop of it doing a factory restore then restarts.
If any body has any ideas at all or can at least point me in the right direction would be a life saver I will even jtag the phone if i have to, if even that's possible
Have you booted into fastboot mode?
Have tried to rsd to stock from fastboot?
Darbness said:
Have you booted into fastboot mode?
Have tried to rsd to stock from fastboot?
Click to expand...
Click to collapse
Thanks for the reply, I have gone into fastboot mode and used RSD to try and flash the stock rom but when it restarts the phone its unable to countiue becuse it is uable to get past the bootloop
If your phone is bootloader locked you can always take it back to the carrier, that's it if you have guarantee. I suggest you try a earlier version of RSD lite, 6.1.4 for example, and see how it goes.
Sent from my RAZR HD using xda app-developers app
Hydr0id said:
If your phone is bootloader locked you can always take it back to the carrier, that's it if you have guarantee. I suggest you try a earlier version of RSD lite, 6.1.4 for example, and see how it goes.
Sent from my RAZR HD using xda app-developers app
Click to expand...
Click to collapse
OK, not able to take it to Rogers some issues with doing that but will try RSD lite 6.1.4 besides that no other ways?
I had the same issue yesterday. Received a phone call and my phone shut off and started looping on the red M logo, but no further. I did everything in my power to get RSD Lite and ADB to recognize my phone in fastboot mode. Nothing. Then, I moved the USB port to another port on my laptop, and viola, RSD Lite picked it up, but ADB never did. Using the stock firmware available for my 926, I was able to revert back to the latest version of JB for my phone. I did also have to run RSD Lite in *administrator mode* in order to get success. Hope any of these tips helps you out.
Also, even though I was successful in flashing, I was still in loop mode until... I had to wait for the battery to die and the phone to shut all the way off. Then after powering up, it came up. I tried the volume down + power key, but it would only reset the phone, it would not completely power it off like it needed. This is not something I have seen on any forum anywhere, so hopefully it helps.
xaneth said:
I had the same issue yesterday. Received a phone call and my phone shut off and started looping on the red M logo, but no further. I did everything in my power to get RSD Lite and ADB to recognize my phone in fastboot mode. Nothing. Then, I moved the USB port to another port on my laptop, and viola, RSD Lite picked it up, but ADB never did. Using the stock firmware available for my 926, I was able to revert back to the latest version of JB for my phone. I did also have to run RSD Lite in *administrator mode* in order to get success. Hope any of these tips helps you out.
Also, even though I was successful in flashing, I was still in loop mode until... I had to wait for the battery to die and the phone to shut all the way off. Then after powering up, it came up. I tried the volume down + power key, but it would only reset the phone, it would not completely power it off like it needed. This is not something I have seen on any forum anywhere, so hopefully it helps.
Click to expand...
Click to collapse
Thanks for the reply, I was thinking along the same lines as that but trying it on a freshly installed windows plus on different computer and just have RSD lite 6.0 and my Motorola drivers for my phone installed. I was thinking that it was my current motherboard that has a Intel usb 3.0 controller on it and my old motherboard did not as I manually updated my phone from 4.0.4 to 4.1.2 before on my old motherboard and had no issues and will fallow the instructions to the letter and will triple check as well. I will see how this goes and hope it works as its my last option to get it working.
OK so trying to reflash the phone from a different computer with a fresh install of windows buy did not work.
I was looking though the options in the android system recovery menu and two options stood out are:
apply update from external storage
and
apply update from ADB (wont work as ADB does not see the phone)
would doing an update with an SD card with the firmware on it work or is it for some other purpose?
osalot said:
OK so trying to reflash the phone from a different computer with a fresh install of windows buy did not work.
I was looking though the options in the android system recovery menu and two options stood out are:
apply update from external storage
and
apply update from ADB (wont work as ADB does not see the phone)
would doing an update with an SD card with the firmware on it work or is it for some other purpose?
Click to expand...
Click to collapse
I'm not sure, never flashed that way. If it isn't too much to ask, can you tell me the process you are following to flash the stock rom step by step?, to see if I can somehow help you out, it's really odd It doesn't work.
Sent from my RAZR HD using Tapatalk
Hydr0id said:
I'm not sure, never flashed that way. If it isn't too much to ask, can you tell me the process you are following to flash the stock rom step by step?, to see if I can somehow help you out, it's really odd It doesn't work.
Sent from my RAZR HD using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply, The steps I take to flash my phone is to first put my phone in to fast boot mode then connect my phone to the back of my pc then start up RSD Lite and add the latest firmware for my XT925 in RSD then let it load the firmware and it restarts the phone. it starts up to the non animated red M icon then the android with the spinning blue object in its chest comes up but then shuts off and restarts and have left it for several hours until it died and had to recharge it up.If I can I will post a video of how I flash it and what the phone does.
also is it normal for RSD Lite not to show the imei number of the phone or any thing about it in the top left box (Device properties) when you click on the modal?, all I get is N/A in Device properties box.
Yes, that is completely normal, that only appears when the flash is succesful and you get past the "select language" screen, but seeing that you're stuck in the M logo means that you haven't got there yet, in the mean time it will still appear no imei and no info.
Sent from my RAZR HD using xda app-developers app
---------- Post added at 04:08 PM ---------- Previous post was at 04:01 PM ----------
Here, try this: http://www.android.gs/unroot-droid-razr-hd-xt926-downgrade-stock-firmware/
The RSD process following the exact same instructions found there on a Windows with USB 2.0, and it is preferred you use RSD 6.1.4 (if you don't have it I can post it here if you want)
Your build to flash is found here: http://sbf.droid-developers.org/
Search for the one the phone brought when it was just bought, it has to be from your carrier.
Btw: did the flashing gives you any errors at all or not? Also, do you have bootloader unlocked? Just some details I'm curious, but seeing your phone does finish the process and restarts means it probably doesn't get any errors, anyway I'm just curious.
Sent from my RAZR HD using xda app-developers app
Hydr0id said:
Yes, that is completely normal, that only appears when the flash is succesful and you get past the "select language" screen, but seeing that you're stuck in the M logo means that you haven't got there yet, in the mean time it will still appear no imei and no info.
Sent from my RAZR HD using xda app-developers app
---------- Post added at 04:08 PM ---------- Previous post was at 04:01 PM ----------
Here, try this: http://www.android.gs/unroot-droid-razr-hd-xt926-downgrade-stock-firmware/
The RSD process following the exact same instructions found there on a Windows with USB 2.0, and it is preferred you use RSD 6.1.4 (if you don't have it I can post it here if you want)
Your build to flash is found here: http://sbf.droid-developers.org/
Search for the one the phone brought when it was just bought, it has to be from your carrier.
Btw: did the flashing gives you any errors at all or not? Also, do you have bootloader unlocked? Just some details I'm curious, but seeing your phone does finish the process and restarts means it probably doesn't get any errors, anyway I'm just curious.
Sent from my RAZR HD using xda app-developers app
Click to expand...
Click to collapse
thanks for the reply, I have just tried the the steps in the link you provided and I used RSD lite 6.1.4 and got the 4.0.4 Rogers firmware for my XT925 that it originally came with and waited an hour but just did the same thing, I don't get any errors when flashing although RSD displays to start the phone up manually and I have a locked boot loader (Device is LOCKED: Status Code: 0) I can how ever get it to go to the animated red M icon and then the rogers logo by selecting normal power up from the boot menu but doesn't boot in to android.
osalot said:
I was also wondering if any body knows a good way to completely wipe the razr XT925 and restore the stock firmware that would also help.
Click to expand...
Click to collapse
http://theunlockr.com/2012/01/24/how-to-restore-the-motorola-droid-razr-using-fastboot-files/
Ok, so I think I maybe doing something incorrectly so I will put all the steps I did to reflash my phone and will add some pics and a video if possible.It took me a few days to get another phone to use for vids and pics the phone I used to for video and pics Samsung Captivate, unbrickable ya can't kill it.
1. I have installed RSD Lite 6.1.4
2. Installed the latest Motorola drivers by down loading the Motorola Device Manager
3. Down loaded the firmware for my phone android 4.1.2 full file name ---> 9.8.2Q-8-XT925_VQL-12.2_CANADA_VANQJBLTEFRCI_P004_CFC_fb.xml.zip
4. Put my phone in fast boot mode then connected my phone to my netbook on the side or on the back usb 2.0 port on the PC with the original Motorola usb phone cable tried both to be sure
5. Started up RSD Lite 6.1.4 and load the firmware and selected Decompress only
6. Checked RSD Lite to make sure my phone is connected and showing up and RSD Lite shows (Fastboot VQUISH_U S USB N/A Connected)
7. I then selected start button on RSD Lite and it flashed the firmware with out issues or errors
8. phone restarts fine from fastboot left it for 1:30 RSD displays to reboot the phone manually but the phone does not do anything else but reboot constantly left the phone doing that until it ran out of battery
Pic of XT925 in fastboot mode not connected
Pic of RSD with phone connected in fastboot mode ready to be flashed
Video of phone restarting after being flashed and looping (click the link below)
http://s1295.photobucket.com/user/Osalot-Ruin/media/RSDandphonevideoCapture_zpsff85211b.mp4.html
Pic of RSD after leaving the phone for 1 hour and 30 minutes
In the steps I don't see the XML file editing, did you deleted the getvar line in the XML file?
Sent from my RAZR HD using XDA Free mobile app