Related
So I just got done configuring chompSMS. Disabled notifications on the built in SMS app. Did a battery pull and got this screen and haven't been able to get out of it. Held down home & power and got a user memory wipe screen. Figure I'd give that a shot. Still stuck on the FASTBOOT screen and now have to redo the whole thing if I manage to get out of this screen.
Anyone else see this? Not much out there about Sprint's Hero, but there's a bit about Orange's Hero, rooting, flashing rom's and all that fun stuff. Nothing about getting it back to normal though.
and to add....after letting it sit connected to usb for a bit, the screen finally went dark but now won't turn back on. Really odd.
hmm im kinda new to android, but if your stuck in fastboot cant you use the devkit to push a new recovery image like RA 1.2.3 and flash ?
i might be wrong tough
I'm brand spanking new to Android. Haven't dealt with sdk's andn loading rom's in ages and don't have the time to figure it out. Thought there might be some hard reset button combo that I was missing or something. Just heading to the Sprint store now with box in hand to have them switch it out or activate my Treo Pro again. Kinda need the phone for work and don't have a home phone so downtime is not a good thing.
darkenergy said:
hmm im kinda new to android, but if your stuck in fastboot cant you use the devkit to push a new recovery image like RA 1.2.3 and flash ?
i might be wrong tough
Click to expand...
Click to collapse
he won't be able to push that to do ADB tricks, nor do fastboot flashing with img files
Goldcard doesn't help as well
I hv got a G1 in same situation after pulling out the battery.
Stucked at first splash screen on next boot.
I assume that is a rom / system problem so I tried to boot into recovery but still freeze on 1st splash screen.
I tried to figure out the problem and I'd try to connect by usb and tried adb logcat but only waiting device return. And yep the screen goes black ( but still on ) likely in this situation.
And yea SPL enter was successful but can't connect to fastboot so no recovery can flash.
I notify the phone (seemingly) won't be able to charge as the notification do not turn on, or it does charge but problem with notification light (?), probably it is more likely a hardware problem due to removing the battery. Recently I take the G1 to a shop to figure out is that a hardware failure.
I'm all for troubleshooting and playing around with ROMs, but there's times when I just need to be up and running and have opted not to screw around with something I depend on for work. There's other toys to "play" with.
So after a way too long stay at the Sprint store I have a new Hero that's up and running just fine.
Wanted to say it was something I installed, but everything seemed to be approved by the masses as working well. Maybe it was something with the battery pull. I'm surprised no one has made a soft reset widget. Seems kinda basic coming from 13yrs of PalmOS and a bit of winMob.
dbpaddler said:
So I just got done configuring chompSMS. Disabled notifications on the built in SMS app. Did a battery pull and got this screen and haven't been able to get out of it. Held down home & power and got a user memory wipe screen. Figure I'd give that a shot. Still stuck on the FASTBOOT screen and now have to redo the whole thing if I manage to get out of this screen.
Anyone else see this? Not much out there about Sprint's Hero, but there's a bit about Orange's Hero, rooting, flashing rom's and all that fun stuff. Nothing about getting it back to normal though.
and to add....after letting it sit connected to usb for a bit, the screen finally went dark but now won't turn back on. Really odd.
Click to expand...
Click to collapse
download htc sync and install it.
http://www.htc.com/us/supportdownloadlist.aspx?p_id=300&act=sd&cat=all
download sprint RUU and run it, it will wipe your phone, but it will work agian
ftp://xda:[email protected]_Hero_C_Sprint_1.29.651.1_signed_release.exe
thanks for that. Will keep that handy for next time or if I ever play around with it. I think I'm going to the Moment though when it hits next month. Better screen, processor and keyboard will be doing it for me.
fixing any android stuck in fastboot
If your stuck in fast boot this is what you do.
1. Remove the micro sd card and somehow connect it to your computer.
2. Download a rom that is made for your phone and put it in a easily accessible folder on the micro sd.
3. Reinsert the sd card in the phone and reboot, once in fast boot go to hboot.
4. After going into hboot select recovery.
5. After this is done you must go to "install zip from sd card" and choose the rom that you have downloaded, select install and wait until the installation is complete, if unsuccessful redownload and try the whole process again, if unsuccessful the second time try downloading another rom.
If you have any questions please personal message me so i can help you.
Download: cyanogenmod.com
Btw i had a HTC hero and had this problem many times and this had worked every time.
I have a similar situation
when i power on the phone it goes straight to fastboot mode.
I Checked volume keys and are not stuck.
If I connect phone via usb and run:
fastboot reboot
the phone will load normally the android OS and will work just fine until you power it off again.
\
I dismantled the phone just to be sure there is no hardware issues, I tried to power on the phone without the home button connected to the board and the phone will load the android OS without any issue.
I dismantled the button itself, it has some sort of touch IC inside and a normal key button downside.
I could not notice any dust or water tracks in the button, so
at this point and dont know where to go...
I dont have another button just to be sure if it is the button itself or a board issue.
dbpaddler said:
So I just got done configuring chompSMS. Disabled notifications on the built in SMS app. Did a battery pull and got this screen and haven't been able to get out of it. Held down home & power and got a user memory wipe screen. Figure I'd give that a shot. Still stuck on the FASTBOOT screen and now have to redo the whole thing if I manage to get out of this screen.
Anyone else see this? Not much out there about Sprint's Hero, but there's a bit about Orange's Hero, rooting, flashing rom's and all that fun stuff. Nothing about getting it back to normal though.
and to add....after letting it sit connected to usb for a bit, the screen finally went dark but now won't turn back on. Really odd.
Click to expand...
Click to collapse
yurais said:
I have a similar situation
when i power on the phone it goes straight to fastboot mode.
I Checked volume keys and are not stuck.
If I connect phone via usb and run:
fastboot reboot
the phone will load normally the android OS and will work just fine until you power it off again.
\
I dismantled the phone just to be sure there is no hardware issues, I tried to power on the phone without the home button connected to the board and the phone will load the android OS without any issue.
I dismantled the button itself, it has some sort of touch IC inside and a normal key button downside.
I could not notice any dust or water tracks in the button, so
at this point and dont know where to go...
I dont have another button just to be sure if it is the button itself or a board issue.
Click to expand...
Click to collapse
People still use the Hero? There are so many better phones you can buy for dirt cheap. Heck, I got the Evo LTE for $80 on Craigslist. Even the Evo Shift, Design and 3D can be had cheap. I'd dump the Hero without blinking.
Last night I bought a brand new Streak 5 from a local guy. Box was sealed, no mention of refurb, inner contents were sealed.
I didn't have time to test it and the guy I bought it from said he had gotten it a while back from a work raffle and that it had been sitting in a drawer in his house - I have no reason not to trust that he was lying to me.
When I actually got time to unbox it, I popped the battery in and tried to turn it on. The menu buttons lit up briefly and then when out. The screen never came on. Since then, it has been completely unresponsive.
I've tried to charge it with the wall charger, as well as my PC. Neither seem to be doing anything and my PC doesn't recognize it - even with Dell's software installed.
I've tried to take out the battery and hook it up to the wall charger and my PC to get it to turn on.
I've removed the Micro SD.
There is no SIM card in it currently.
I ordered another battery and an external battery charger. They should be here in a few days. I have the current battery rigged up and charging with a spliced USB cord.
What else can I do? I feel like I've done everything "simple" thus far and I'm a little nervous when it comes to utilities like Streakflash.
I'm coming over from the iPhone world and my Android use has been limited at best. Any help is appreciated.
What happens on the device itself after having had a chance to charge?
Does it light up when you press the power button, or nothing at all?
Thanks for the response.
There is no indication that it's charging. The screen doesn't come on, or even flash. The buttons do not light up. However, I don't believe it's the cable or the connector since my PC responds with an unrecognized device -- "Qualcomm CDMA Technologies MSM" prompt. I also managed to get my PC to tell me that the device "wasn't plugged in."
I've tried to get some response out of it in every possible combination regarding the buttons, battery, back cover, microSD, and where it's plugged in. It just sits there. No lit screen, no lit menu buttons, nothing.
If it helps, I'm running Windows 7 64 bit. I've installed every possible thing I could find regarding the Dell drivers and my OS.
It sounds like your device somehow got shipped without having all the software installed onto it.
Can you provide more information about the device itself, such as it's manufacture date or any other info on the box/device labels? Devices getting shipped half baked like that isnt exactly common.
This sounds like a legitamate time to use QDL tool to reflash it, but I cant provide any help with that as I've never used it.
Can you use QDLTool if your computer doesn't even recognize it?
The date on the label is 10/12/2010.
If it's displaying as "Qualcomm CDMA Technologies MSM" that's a sign that it should be able to get into upload mode as that's what the driver qdl tool uses I believe.
It's likely out of warrentee already, so you prob have to fix it on your own if at all.
I can't get it to respond to anything I do. It's very disheartening. I really, really wanted this phone, too.
I'm downloading the latest version of Ubuntu. I'm going to see if I can make any headway through Linux.
I can't get QDLTool to pick-up the device, either. I get an error message when I try to use it and scanning for it does nothing.
Did you install the driver bundled with it properly?
If it still doesnt detect it after that it's likely a dud
use qdltool, you can download it from here
http://www.box.com/s/rj9xd5tl7v5amimbm3youll need to make sure you have all drivers installed though, info is on this forum somewhere,
once installed run the software on pc you should see a big box with "run" on it, click run then connect phone by holding volume up and connecting usb then qdltool will do rest from there
when i got my both my dell streak it was the same deal. first one came exactly as how you described it. I put in the battery, made SURE THAT THE CONNECTORS ARE lined up on the back case, and then tried to power it on. NOTHING.
It seems even if the battery was fully charged, the only real way to turn it on was to connect the streak to the power adapter and then press hold down the on button. WHen the device finally gave me the dell logo, it would just sit there stuck. So i took out the battery, and redid it. Then went into fastboot mode (hold camera and power) and it wouldnt detect the touch screen. It seems that the touch scree was faulty and hence it would remain stuck on the dell logo. I tried to calibrate the touch screen a few times, all failed. Then finally for one time it worked, and the touch screen came back to life. Shortly after though upon booting into the old stage 1.6, it restarted and the touch screen failed again.
So i sent it back to rogers and they gave me a replacement phone. Same deal, when you first put in the battery and the case it wouldnt start no matter what. Only upon plugging it into the power adapter then it starts up. However this new one had a functional touch screen.
1) check out the touch screen by using the fastboot, or stock recovery. If you get error messages, it means your screen is toast most likely and then you might have to open her up and see if all the connections are lined up
2) if it doesnt boot at all, try connecting it to the power adapter first and then after about 30 seconds power it on. You should be able to see the dell logo unless as the guys stated before the software is hosed.
3) if the software is totally hosed, tried to get it into fastboot mode or recovery and see if you can reflash the device.
something like that...
Thanks for the comments, guys.
As of now, it's still in the same position it was in. It doesn't respond to any combinations of buttons, battery in/or, or plugged into the wall/pc.
I'm assuming that the situation it's in currently is what's preventing any sort of legitimate connection between the phone and my PC.
My last shot is a battery and external charger that should be here next week.
I've read through a number of other threads but can't sem to get a definitive answer to my particular problem.
Some weeks ago my daughter dropped my Streak and caused the LCD to leak. I ordered a replacement screen from eBay, it arrived earlier this week and I fitted it and it worked. On a side note I have now upgraded to a Galaxy Note but am keeping my Streak as its such a great phone. This means however that it doesn't currently have a SIM card or an SD Card.
Once i'd fitted the new screen i decided to do a fresh install and booted into fastboot, however I then realised that I didn't have an SD card in, so whilst it was still plugged in, I took the battery out. The screen flashed in a strange way, went blank, but remained backlit until I removed the data cable.
Since then the screen has just backlit but nothing else. I have used Streakflash, QDL tool, both successfully, but to no avail.
I have checked and double checked the connections from the new screen to the motherboard. Unfortunately i disposed of my old screen before this happened so cannot test it on my broken screen.
When I remove insert a blank, freshly formatted SD Card, a 'LOST.DIR' folder and occasionally an 'ANDROID' folder appear if I leave it to run for a while after powering on.
My question is this: Do you think it might just be the screen that is malfunctioning, or might the phone be kaput?
Any help would be appreciated.
No i don't think it is bricked,
since the folders are automatically created (lostdata and .android), i think your phone is still running. If your phone is a factory unlocked i suggest you to flash ROM using fastboot.
You can find lots of thread on how to flash, just search the forum and hope you will have your streak back
Hope it helps.
PS:"From my experience i would like to warn you not to use "fastboot -w" option in fastboot mode never ever(coz that can really brick your phone)"
Good day everyone,
My problem started a month and a half ago, but in a different form. The battery of my Motorola Razr (Non-US) went too low, and it only showed the bright white light whenever I tried to charge it. This is an error code that means that the battery ran so low that it is now in a protective mode that you can only get it out with higher amounts of amperage, using a cable that I don't have myself. I returned it to the store, they sent it to the motorola factory, and I got it back yesterday. Now, it might be important for me to note that I live in the Netherlands; the nearest Motorola factory was the one in Germany. It took a solid 5 weeks for me to get my phone back.
Right, so today/yesterday I tried to turn on my phone, excited to have it back after such a long time. It got stuck in a bootloop. All it does is show the red/white M, with dual core below it. This is the first screen you normally see when you boot the phone. After a second or 5, the screen goes black, only to be replaced by the red/white M, this time without the dual core text. After a while ripples start to show around the M, but without vibrations. The menu buttons also do not light up. Normally the same happens, but it vibrates rather violently and the menu buttons do light it; it means that the phone is booting the firmware.
The phone keeps this up for a few minutes, after which it starts all over again, from the red/white M with the dual core text. It does does indefinitely, until the battery runs out. It doesn't shut down in between, so this takes quite a while. I tried forcing it to reboot with the volume down + power button (which is a hardware reboot), but that just makes the cycle start over again. Very, very rarely (usually after looping for about an hour), the phone DOES go on. However, it soon crashes again, being on between 10 seconds and 5 minutes.
Now here is what I think happened. Before I sent the phone to the factory, I was running an old version of android, still in Gingerbread. I don't know exactly what firmware it used, but it was rather old, maybe half a year at least. However, now that I have it back, I appear to have been updated to ICS 4.0.4. The firmware running on the phone is also new (obviously), version 672.180.41.XT910.NonEFIGSRetail.en.EU (EU for Europe obviously, and NonEFIGS for non English, French, Italian, German and Spanish) as I live in the Netherlands. Now what I figure has happened is that the factory tried to flash my phone to the new firmware after they had fixed the issue, and the update didn't take.
Now, I could obviously return the phone to the store again and have them repair it, but that will take another month. Also, the store is very disappointing to say the least; they will not give me a replacement phone in the meantime, which is very bothersome. So I'd rather try and solve the problem myself.
However, I don't know how to flash 672.180.41.XT910.NonEFIGSRetail.en.EU again. All the instructions or guides that I have found so far only refer to the American version of the phone, or require me to be able to access the phone (turn it on). I can however access the boot menu with volume + volume - power held together, which lets me access the AP Fastboot menu.
Could anyone give me instructions what to do from there? I already did a factory reset, which did nothing to fix the situation.
I did find this link
http://forum.xda-developers.com/showthread.php?t=1837971
But I'm not sure how to proceed with that.
Note: If I'm on the wrong path with trying to fix it all, please do say so! By no means do I want to screw up the situation any further, as I could still have it repaired for free, it just takes a long time and I'd rather not.
Note2: If I am missing any crucial info, please let me know too!
Edit/Delete Message
Alright, so maybe I should modify the title.. I tried using the method in
http://forum.xda-developers.com/showthread.php?t=1837971
But I'm afraid that only made the situation worse. My phone now automatically boots into AP Fastboot, giving the message that the flash has failed.
Now I understand that I should be able to just re-flash it, but I would be very thankful if someone could point me to the right files/procedure, as almost everything I can find is for the US version, and I'd rather keep the EU version with my language pack and all.
Thanks in advance
Resolved Bootloop problem
Hi Dazm;
I had the exactly the same problem and i resolved it yesterday. You need to flash a custom ROM for in order for it to work again, but you battery is to low to do this e.g. if you hold both volume+ - down and keep power button for 10sec and go to fastboot ap, it would indicate this.
So what i did was the extreme lol, i created my own factory cable, I bought a usb data cable cut of the one end (micro usb) stripped the red and black coded wires, removed the back cover of the Motorola Razr XT910, and you will notice at the bottom corner of the phone is a positive + negative - with screws. I connected the red wire to the positive + and the black wire to the negative - and the other end of the usb to my computer. This will charge for 1 hour 15min, once this is done, you will need to download RSD lite 5.7 and install on pc, download stock ROM and flash the ROM with RSD lite and there you go. Mine work 100%, sorry if im not to clear, was in a rush.
arendshp said:
Hi Dazm;
I had the exactly the same problem and i resolved it yesterday. You need to flash a custom ROM for in order for it to work again, but you battery is to low to do this e.g. if you hold both volume+ - down and keep power button for 10sec and go to fastboot ap, it would indicate this.
So what i did was the extreme lol, i created my own factory cable, I bought a usb data cable cut of the one end (micro usb) stripped the red and black coded wires, removed the back cover of the Motorola Razr XT910, and you will notice at the bottom corner of the phone is a positive + negative - with screws. I connected the red wire to the positive + and the black wire to the negative - and the other end of the usb to my computer. This will charge for 1 hour 15min, once this is done, you will need to download RSD lite 5.7 and install on pc, download stock ROM and flash the ROM with RSD lite and there you go. Mine work 100%, sorry if im not to clear, was in a rush.
Click to expand...
Click to collapse
Thanks for the reply! I'm not sure this is the issue though, I can still charge my phone (It's at 100% now), and it says Battery OK in the fastboot menu. However, exactly which custom ROM I need to flash is the main part of my problem, I think.
Interesting, I'm going to have to keep my eye on this thread.
I am experiencing the same thing, after an OTA update to 672.180.41.XT910.Retail.en.FR from GB. I also experiencing a rebooting loop with the occasional boot that last about 5 minutes. Clueless about what to do at this time. Maybe flashing with a fastboot file found here.
Hopefully you can resolve your problem and help me solve mine in the process. Unlike you, it's improbable at this time to have my phone service by Motorola; Moto US won't touch because it has French software, Moto FR would fix the phone (after I cover the service and postage) but will not sent it back to me because I have an American address.
All
While flashing my LS990 back to stock (was rooted/TWRP) my dog hit my laptop and the USB cable unplugged and the battery popped out right in the middle of the process. Now when I try to enter download mode it simply reboots to the LG logo and when trying to enter recovery I get the same (says Entering Recovery then just reboots). Am I screwed/bricked? Is there any way to recover from this or am I buying a new phone? UGH UGH UGH.
Any help would be greatly appreciated - I work in technology so being without a phone, even for a few hours won't fly so I may be driving to Sprint here in a few minutes...
-Ross
When you have it plugged in is it not recognizing or what is it doing? The reason I am asking is because, depending on how your dog pulled out/ stepped on the wire may tell you if the adapter in the phone is broken. When your in flashtool and it is searching try moving the wire in phone up and down till you find a "Sweet spot" then just hold it like that till it is done. Also change the usb on the computer you are using like try a different usb port. Not on the software on the sides
If you need any more help like really fast just PM me or else I wont check this till like tomorrow
First thanks for taking the time to help. It's never recognized by my Windows 8 box as it never gets into recovery or download mode. When I try download mode it simple reboots back to the LG screen and with recovery it says its entering recovery then reboots. So the PC never ever sees it in device manager at all as it won't boot that far. Honestly I think it's toast and I'm just gonna have to replace it. Ugh.
-Ross
Since your phone is in that little area you maybe able to run the command: adb reboot bootloader
defiantly try the wire jiggle thing that maybe the reason I had a similar problem with a nexus 4 my dog stepped on the wire while it was charging and the bottom adapter messed up and I had to hold a wire for like a half hour to get it to flashback then I just had to return it to t-mobile.
All change usb port use another one that you know works.
It's not a physical connection issue now - that works fine. it's that since it got cut off mid flash I think the boot loader is only half written or something. So it never shows in ADB since it just reboots over and over and over. Nothing can get it to stop/settle down.
I assume I'll be taking it to Sprint tomorrow to see if they'll be nice to me...