So I wanted CM 10 on my phone and did all the reading as was following a guide. I got as far as installing CM 10 and on the initial start-up it says it can take up to five minutes.. Well, it sits there forever and goes there every time I reboot.
Now, when I hold the volume and power buttons it goes into Android system recovery <3e> I know I had to boot into bootstrap recovery to be able to load the file off my external drive - otherwise you get the failed signature and it won't load.
Can I do anything here to fix my phone? I don't don't care what I loose, I need this working.
Thanks-
Kyle
Ok - so I'm trying to fastboot VRZ_XT912_6.5.1-73_DHD-11_TA-3_1FF_02 onto my phone bia FlashME as RSD Lite will no longer work and its telling me battery low.
I've had this plugged into a Motorola branded wall charger for nearly 4 hours and it still says battery low. Im switching to the dual usb black square charger and a Motorola branded usb cable and trying again - after this I'm not sure how I'm going to be able to charge it...
holding volume and power and going to bp tools to get the battery meter to show does nothing, sits at moto screen forever... I dont want to claim this on my insurance - but I may have to. Help?
KyleQ said:
Ok - so I'm trying to fastboot VRZ_XT912_6.5.1-73_DHD-11_TA-3_1FF_02 onto my phone bia FlashME as RSD Lite will no longer work and its telling me battery low.
I've had this plugged into a Motorola branded wall charger for nearly 4 hours and it still says battery low. Im switching to the dual usb black square charger and a Motorola branded usb cable and trying again - after this I'm not sure how I'm going to be able to charge it...
holding volume and power and going to bp tools to get the battery meter to show does nothing, sits at moto screen forever... I dont want to claim this on my insurance - but I may have to. Help?
Click to expand...
Click to collapse
To charge the phone, you will now need the Motorola factory Charging Cable that bridges pin 4 with pin 1...anyways this will allow the phone to charge now that it is stuck in bootloop. The bridging of the pins allows the phone to think it is in the factory programming mode, allowing it to charge.
I would include a link to the post, but I am a new member...can't post links...but Google the below search term, and there is a few sites on how to make the cable, or where to buy it.
Now, I believe this will solve your charging issue. I don't know about flashing back to stock or making the ROM work, and I would look around a little more on the subject of this cable because I just stumbled across a thread about this a few days ago. A quick Google/XDA search on "Motorola Factory Charge Cable Razr" Should be sufficient.
---EDIT---
After looking through the forums again, I found a thread that may help you...it is in the middle of this forum, and it is called Low Battery charge in Ap Fastboot Fix. Take a look at that and it may help you.
Its toast - wont charge. took it all apart, hacked a cable and put the leads on the battery and gave up. put it back together - calling asurian to get a replacement. **** this thing
Thanks in advance for any help...
Recently my phone bricked, out of the blue. I rooted it and flashed the most recent release of TWRP (I don't remember the utility I used) and tried (and failed) to gain S-OFF with lazypanda and moonshine. After flashing the stable CM10 release and realizing the touch screen did not work, I found a ParanoidAndroid release that I wanted to try (http://forum.xda-developers.com/showthread.php?t=2373565). I flashed it from recovery and it worked great for around a week, then one morning it just bricked. Before that, I had rebooted it many times each into recovery and bootloader and did a couple full reboots. I had also fully powered down and back up a couple of times as well. However, that morning I powered down the phone and it has not powered up since. I began the power down on the AC charger, and removed the charger a few seconds after the screen went black; the buttons were still lit up. It does not respond to any button combination other than having a PC recognize it as a QHSUSB_DLOAD device. I have tried the LazyPanda unbrick method, PblClear, and (against all hope) an RUU, none successful. At this point, I am forced to concede that I must take my phone to Sprint and have it replaced under TEP...unless someone has a solution?
Again, quick details - brick occurred after a week of full and non-buggy operation. Not the result of a botched S-OFF attempt as far as I know, though I did try to gain S-OFF with 2 different utilities, failing both times. Removed power cord (AC Charger) while powering down; LED does not light up, will not respond to any button combination. Mounts as QHSUSB_DLOAD device.
Thanks again for taking your precious time to help me! :laugh:
dadrumajor said:
Thanks in advance for any help...
Recently my phone bricked, out of the blue. I rooted it and flashed the most recent release of TWRP (I don't remember the utility I used) and tried (and failed) to gain S-OFF with lazypanda and moonshine. After flashing the stable CM10 release and realizing the touch screen did not work, I found a ParanoidAndroid release that I wanted to try (http://forum.xda-developers.com/showthread.php?t=2373565). I flashed it from recovery and it worked great for around a week, then one morning it just bricked. Before that, I had rebooted it many times each into recovery and bootloader and did a couple full reboots. I had also fully powered down and back up a couple of times as well. However, that morning I powered down the phone and it has not powered up since. I began the power down on the AC charger, and removed the charger a few seconds after the screen went black; the buttons were still lit up. It does not respond to any button combination other than having a PC recognize it as a QHSUSB_DLOAD device. I have tried the LazyPanda unbrick method, PblClear, and (against all hope) an RUU, none successful. At this point, I am forced to concede that I must take my phone to Sprint and have it replaced under TEP...unless someone has a solution?
Again, quick details - brick occurred after a week of full and non-buggy operation. Not the result of a botched S-OFF attempt as far as I know, though I did try to gain S-OFF with 2 different utilities, failing both times. Removed power cord (AC Charger) while powering down; LED does not light up, will not respond to any button combination. Mounts as QHSUSB_DLOAD device.
Thanks again for taking your precious time to help me! :laugh:
Click to expand...
Click to collapse
PM XDA member Zarboz regarding JTAG, which may be just what you need to resurrect your phone.
Sent from my EVO using xda premium
FinZ28 said:
PM XDA member Zarboz regarding JTAG, which may be just what you need to resurrect your phone.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Thanks! What exactly would a JTAG do? I did some research but couldn't find a good answer. Is there an advantage to that over just bringing it to Sprint to replace it, or do you think they might not take it?
EDIT: I went through my research again; I guess I just didn't understand it the first time. So, a JTAG can access and write to any memory on the phone, especially the memory that is now unavailable due to messing up the low-level boot software?
I've run into a similar situation on a completely different phone. I have a nexus 4 on AT&T that's been running ParanoidAndroid without problems for many months (most recent update flashed about 3 day earlier) that just wouldn't turn on one morning. The only indication it's alive at all is that it shows up as QHSUB_DLOAD / QDL mode when connected to the computer, and if I hold down the power button long enough to force it to restart the indicator light will briefly turn red for about a second. Your post caught my attention because almost no one else runs into this situation other than when they're flashing something wrong to the phone. Perhaps there's a bug in ParanoidAndroid that's responsible? (It's the only common element I see so far.)
Anyway, most every unbrick tool I can find expects you at least can access the storage to rewrite bootloaders, etc. The only thing I've found so far that will talk to the Qualcom chip in this mode is a perl script that still doesn't manage to get me out of this mode and to a state where the other tools can take over. JTAG may be my last resort. If you're considering a JTAG service, you should be aware that it involves taking apart the phone and in some cases soldering temporary leads to the circuit board. If you have any warranty style replacement options, you'll likely have to choose between those or the JTAG route.
iconoclastnet said:
I've run into a similar situation on a completely different phone. I have a nexus 4 on AT&T that's been running ParanoidAndroid without problems for many months (most recent update flashed about 3 day earlier) that just wouldn't turn on one morning. The only indication it's alive at all is that it shows up as QHSUB_DLOAD / QDL mode when connected to the computer, and if I hold down the power button long enough to force it to restart the indicator light will briefly turn red for about a second. Your post caught my attention because almost no one else runs into this situation other than when they're flashing something wrong to the phone. Perhaps there's a bug in ParanoidAndroid that's responsible? (It's the only common element I see so far.)
Anyway, most every unbrick tool I can find expects you at least can access the storage to rewrite bootloaders, etc. The only thing I've found so far that will talk to the Qualcom chip in this mode is a perl script that still doesn't manage to get me out of this mode and to a state where the other tools can take over. JTAG may be my last resort. If you're considering a JTAG service, you should be aware that it involves taking apart the phone and in some cases soldering temporary leads to the circuit board. If you have any warranty style replacement options, you'll likely have to choose between those or the JTAG route.
Click to expand...
Click to collapse
Just an update - I went to Sprint, and they agreed to replace the phone...waiting on it at the time of writing, but I will be starting from scratch. I plan to unlock the bootloader and root but not try for S-OFF as TWRP does have a way around it...and I WILL be staying away from ParanoidAndroid, although I love their ROM. Too bad...I just don't want another paperweight on my hands!
-EDIT- iconoclastnet: do you remember what circumstance the phone was in when it bricked? Like, on the charger, off the charger, turning on or off as it was plugged in/unplugged? Because I was unplugging mine just as it was powering down (not a reboot) and that's when it would not turn back on.
dadrumajor said:
-EDIT- iconoclastnet: do you remember what circumstance the phone was in when it bricked? Like, on the charger, off the charger, turning on or off as it was plugged in/unplugged? Because I was unplugging mine just as it was powering down (not a reboot) and that's when it would not turn back on.
Click to expand...
Click to collapse
Sorry for the delayed response, I was out of town for a couple of weeks and didn't notice your reply until now. Anyway, just for the record...
The notification led was indicating that the battery was about to run out (yes, I set a custom notification color for very low battery). It appeared to finally give up and shut off just moments before I reached the charger. So, I plugged it in and let it charge over night like usual, except the next morning it wouldn't turn on or respond to anything. At first I thought that the battery might not have charged for some reason, so I switched to a wireless charger because it has a charging/full indicator led on the charger itself, and confirmed a fully charged battery. Plugging it into the computer revealed the QHSUB_DLOAD / QDL mode status. I still haven't been able to get it out of that mode. At this point I'm really more interested in recovering the data from it than whether or not the hardware works normally anymore.
As for Paranoid Android, I've been using it successfully on a couple of other devices (both before and since the brick incident) and haven't had any problems with it, so it may be a complete coincidence. I'm at a loss for a good explanation though.
The issue was with TRIM not being removed from some early 4.3 ROM builds, which caused the bricks. It was discussed in some of the ROM threads. Had nothing to do with whether a phone was S-on or S-off.
Sent from my HTC EVO 4G LTE
I woke up few days before while I was keeping my Galaxy S3 in the charger and found out no electricity, however, I found out that the green LED is blinking too fast. I pushed the power button to get it unlocked but it didn't respond. I had to hold the power button to force it restarting (as usual in such cases) after unplugging it from the charger (for any expected power return back to source), however, the phone turned dead. It is no more powering on, I replaced the battery with another one, I used the charger when power is back, another charger and connected the USB to PC and nothing happened! I left the battery off the phone for several hours but it didn't work, though.
The phone is now hard bricked but would this case be a system board failure (high voltage) or just the bootloader became malfunctioning? Since the phone is out of warranty, I opened up the case, removed the battery and opened it and removed the system board carefully (I'm a Computer Engineer and took my precautions). Then I used a multimeter continuity check to make sure there are any charges. I applied it to the power button and the multimeter read 1 with high sound while any other part to read very high value with no sound.
I had to send it to the official Samsung repair shop for checkup and they told me it might be a system board or software issue (they didn't explain but I understand something regarding the bootloader/EFS...etc) and a system board would cost about 330 USD!! I should know what happened by tomorrow and decided I won't replace the board at all in such a price but I'm assuming it's a hard-brick.
1- The LED was blinking before I had to force hold power button to get the phone restarted, hence I think it didn't get high voltage from power source.
2- Would force holding power button to get the phone restarted to cause a power damage to the motherboard?
3- Would force holding power button to get the bootloader malfunction?
4- The multimeter's continuity test I performed has any sign/meaning?
5- Since I have a custom ROM with root (I did installed tens of custom ROMs before with tens of root/unroot) and I didn't suffer a problem, my local stock Samsung firmware yet before MG4, would this be a problem if it's a bootloader issue for them to use JTAG or whatever to copy bootloader information? (Modems after MG4 has another store location for EFS rather than earlier once)
Any tips / feedback would be most appreciated.
all key combinations have failed to produce boot and screen but the vibration responds quickly to the sequenced key combinations. no password issue always seemed to need a reset and extra attention but worked fine until left in partial sun through draped window and was powered on without a cool down. I heard a hiss and though the battery was discharging itself, tried when cool nothing so I put new battery in got a battery icon with low level and would not progress in power from there would not accept the charge . I charged with a new cube led usb charger and data cable overnight got the right results noted above but this time no icon just black screen I dont know what the power level is. I have tried three days charging nothing computer and wall. Tried to make phone vibrate and plug back in no. Windows phone one after mango, have lumia 710 zero problems removed battery twice to reboot phone twice in three years no biggie. Mango 7.5 on 710. want to use 800 as a data phone only would not trust it (mine anyway) for communication. Paid good price for it would like it to work again. Should I try powering it up for a few days? Oh phone always put on a surge protector as all my phones are. I once put phone under my pillow and a few hours later it booted screen came on. Have read people putting hair dryers on them I dont think thats the way to go got me here in the first place. very wonky phone it will and then it wont. I thought maybe usb connection damaged but obviously it is accepting some power and phone responding normally and readily to various key combo prompts but no boot and screen. How might this phone be repaired I would like to know what specifically could be the problem a base power or temp for reboot, what parts I could purchase (out of warranty) all parts inside were connected and looked pristine. No evidence of any heat damage. Used another Nokia battery for this phone new. This phone was let to totally power drain and what I have read that is not good for this phone. Maybe it is only accepting minimal power as before dont know but will try to charge another day to see if any activity occurs but would appreciate any help in zeroing in on what the problem or problems maybe, no software updates if no boot and it should do that if anything.
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Register an account on XDA forums for more questions or replies.
Stand by
Good luck
Please help! My dear friend asked me to fix her broken 610 from what I couldn't even restore to the original ROM. I've tried to download some roms that were as close as to the device that I have (a Polish PLAY.pl 610) but unfortunately couldn't load it through fastboot, adb or recovery. But that's not the subject right now.
All was ok (I could boot it up to fastboot), but one night I sat it down, and the next day it was dead.
- The orange diode doesn't light up when plugged to PC/socket charging
- Power, Power+VolUp, Power+VolDown, none of the combination work, the screen doesnt even flicker
ALL that shows that it is there, is a QHSUSB_BULK unknown device in Windows Device Manager...
Is there a way to fix it? I didn't manage to flash the ROM I just rooted it with HTCs tools, the next day it was like this.
Thanks!
Enstriel said:
Please help! My dear friend asked me to fix her broken 610 from what I couldn't even restore to the original ROM. I've tried to download some roms that were as close as to the device that I have (a Polish PLAY.pl 610) but unfortunately couldn't load it through fastboot, adb or recovery. But that's not the subject right now.
All was ok (I could boot it up to fastboot), but one night I sat it down, and the next day it was dead.
- The orange diode doesn't light up when plugged to PC/socket charging
- Power, Power+VolUp, Power+VolDown, none of the combination work, the screen doesnt even flicker
ALL that shows that it is there, is a QHSUSB_BULK unknown device in Windows Device Manager...
Is there a way to fix it? I didn't manage to flash the ROM I just rooted it with HTCs tools, the next day it was like this.
Thanks!
Click to expand...
Click to collapse
Sounds like a dead flat battery. Take it to a phone repairer and get them to give the battery a boost charge . You can do this your self if you know what your doing but these battery's can explode if you don't know what you doing and you'll need the right equipment, so if YOU DECIDE to try this be very careful (I am not responsible for any damage that may occur if YOU DECIDE to attempt these repairs yourself).
- remove the phones back cover
- disconnect the battery
- connect the battery (with correct polarity) to a bench top power supply with the voltage set to 3.5 volts DC and current limit set to 150 mA (this is very important, incorrect polarity or power supply settings may result in flames or explosions) and monitor the battery voltage. Once it is above 3 volts you are done.(if the battery seems to be getting hot at all during this process stop immediately)
- reconnect the battery and and give it a full charge as per normal in the phone.