So, this is a two-part question. First time asking a question here, so if I'm forgetting anything, lemme know.
Got a Droid X2 in November. Pretty awesome phone, all things considered. I did, however, notice a small bug: every rare once in a while when waking my phone, the phone would wake up without turning the screen on. I could still interact with the phone normally (unlocking the phone, pressing keyboard buttons with the vibration feedback, etc.), but I wouldn't be able to see anything.
I hazarded that maybe the ROM that I was already planning on installing would fix this. Maybe the horrible and evil Verizon bloatware was doing something silly with the software side of the phone. I went ahead and rooted the phone.
Weeelll, it didn't fix it. It still fails to wake up the screen sometimes, and now it's been doing it more frequently. Sometimes, it will even show a snow-crash-filled screen. I installed the 2.3.4 SBF and took it back to Verizon, and was able to show them the bug fairly quickly. They said that I could use the warranty to get it replaced. The thing that made me pause was that the man there told me that if I sent it back and they found out I rooted it, they'd charge me the full 500$ for a new one.
My questions:
1. Does anyone else have this bug, and is there a way to fix it? I poked around the forums, and haven't seen anything like this.
2. Would flashing an SBF erase any signs of rooting the device? If I did trade in the phone in that condition, would I get hit with that 500$ charge? How would Verizon tell if a phone's ever been rooted?
-Whistle
Remove your SD card and sbf they will not know. They can not tell if you sbf it maybe a factory reset would not hurt as well. Do not put any rooted apps on it. Why did he say that did you have a custom rom or rooted apps on it at the time?
SBF brings you to out of box state...nothing will show..
After you SBF be sure to do a system recovery and wipe data and cache...
There are great tutorials in the General section here...
To enter normal recovery, power off your x2, plug your phone in to a wall charger then hit volume down and power button until you see FASTBOOT... then use volume down until Android Recovery...then hit,, volume Up...then hit both volume up and down, you will see a triangle with an exclamation point, Again hit both volume up and down at the same time and it will bring you into recovery. From there you can wipe data and cache....
Note: after SBF it is a good idea to do this to eliminate anything left astray....
Good luck
PS.it takes about twenty minutes to complete.
Dee Ex Two - See Em Seven
Related
*EDIT* GOT A NEW PHONE SO THIS THREAD CAN BE CLOSED. THANKS.
So I pulled a stupid move and dropped my phone off of a deli counter. It's not the worst fall it's had so I don't really know what the deal is. I tried searching the site but didn't come up with anything like this(I will keep trying) Here's the chain of events to make it easier to read:
1) It was acting weird before when I tried to start Pocket Player, really slow. Then the screen went to sleep and I couldn't get it to wake up so I hit soft reset.
3) Went into the store thinking it's doing it's reset thing, then I knocked it off the counter when I went to pay.
Can't hard reset, tried all four ways on a page I found, or enter boot loader.
Not entirely sure what caused the freezing but I can't really see the soft reset doing it because I've done it so many times.
The next step is a repair place but the one I use(it's free) is a three hour round trip and I want to avoid it if I can. Any one know of any way to hard reset that isn't well known or have an idea what I should do? Thanks in advance.
have you pulled the battery and still failed at putting the phone into bootloader mode?
flashing the shipped ROM (.exe) to restore the phone should work, if you can get to the bootloader.
Couldn't get to boot loader, pulled the battery and what not. Actually got a new phone so this thread can be closed. Thanks for the reply, anyways.
Hello all -
My "bricked" situation appears to be unique as I've searched all over and have only found others with at least a phone that has a display.
Scenario:
Had SimplyHoney 4.0 installed (I believe Voodoo Lagfix was enabled). Decided it was time to go back to stock. ODIN'd back to stock (doesn't that wipe any VooDoo?). Re-rooted phone and connected to Kies for giggles to see if it would actually work this time for an "Official" update. (Last time I connected the phone it would not recognize the phone as the appropriate phone for an update) This time it saw it as a Vibrant and proceeded to do the Froyo update. Once it was completed, the Vibrant's screen never turned on.
It feels warm to the touch when you turn on the phone after a few minutes like it typically does, but I can't see anything on the screen.
Did this update do an extreme brick to my phone that it is now a lost cause?
I appreicate any advice you have.
BTW, tried the download button combos that are out here and none of those worked.
When I last had my phone open to fix the GPS contact, I see there is a small battery. Would popping that help reset anything?
It's the same scenario in this video on YouTube - "Video of hard bricked vibrant" by htcpro1212
Sorry can't post links yet.
I had a similar situation with a friends Vibrant this is what I did...pull out battery, plug phone to computer with usb, do the three button combo (volume up down &power) while holding replace battery and that should put phone in recovery mode... hope this helps good luck!
Sent from my Nexus One using XDA Premium App
no point rooting if you're going to update with kies, it wipes root
you could have just used whitehawkx stock 2.2 rom, kies has a history of hard bricks after you've been on a few custom roms
keep trying button combo's (vol + and power with the GB bootloades) but chances are its hard bricked, if it doesnt work phone samsung or t-mobile and say you tried updating with kies and it doesnt do anything now
Pm sent I can fix this for you...
You should always try ODIN back to stock. Its such an Relief.
I'm not sure if this will work in this case or not. When I thought I had bricked my Vibrant, I had a picture looking like a phone-triangle-computer on the screen, so it wasn't blacked out.
I got a "jig" (search the forums or google it.) They cost less than $10 and have saved me several times when I've messed up to get me to download mode so I can use odin.
so this guy came into my store who had a rezound, never once had a problem with it ever...then the battery died fully overnight because he forgot to charge it..
so when he woke up, it was dead obviously. he then plugged it in, and the orange light came on for 5 seconds...then shuts off. and nothing happens. this even happened when he brought it in for me to try. so i'm like, wtf, probably a bad battery maybe?
so i put in a good one we've got...same thing. so i ask if he's rooted or anything, he says no...but i did a search, and found some posts that when people had bad flashes of roms, it would stick at the white screen, and they had to restore a backup in CWM for it to work.
so i tried to see if maybe he was rooted...went into bootloader, hit recovery, and the phone just died. just shut off. so i was like, thats weird...so then i tried to do a factory reset....same thing, i hit factory reset, the white HTC screen came rgiht up, then the phone just died...and this was with a fully charged battery, too.
eventually we had to just call up and get him sent a refurb, but still, has anyone seen this problem? nothing i could do could get it to boot, and that's such a ****ty feeling especially if this guy said that he NEVER had a problem with any HTC phone, especially this rezound, until that battery died and it would'nt turn on again.
I've had that problem after a bad flash, but it still let me get into hboot and recovery without problems, so I doubt it was that. Don't have a clue what it could be though... at least you got him taken care of with a refurb. Maybe the inability to boot to recovery could be not having amon ra or cwm installed (never tried without one) and if he wiped /data or /system I don't know if factory reset would know what to reset to (again, never tried).
Edit: Also, with me, the phone never died. White HTC screen would stay up until I pulled the battery and it would still recognize the charger.
exactly! it's a problem after a bad flash. i wonder if this dude was lying and tried to flash something, his battery died, and it bricked it
I am currently experiencing the exact same problem; I was able to replicate everything you describe, including what happened when you tried to go into recovery or factory reset mode. I have NOT tried to root or do anything else untoward with the phone ... if anyone has any idea what I can do other than get a new phone and lose all my data, I would really appreciate it!
edit - there is one difference: my battery never died. I took my phone out of my pocket at 5:40 to look at it, and it was fine. I looked at it again at around 5:50 and I had the white htc screen. At this point I pulled the battery and started googling.
second edit - could the forced update have something to do with it??
nope, he brought his in before the update.
have you gotten anything to work? when we called customer service, they just replaced his phone for him..i hope it works out for you, man. maybe try to get into fastboot and wipe the phone, or something? i know i was able to get into the bootloader..maybe you can push a factory reset from the comp
avertist said:
I am currently experiencing the exact same problem; I was able to replicate everything you describe, including what happened when you tried to go into recovery or factory reset mode. I have NOT tried to root or do anything else untoward with the phone ... if anyone has any idea what I can do other than get a new phone and lose all my data, I would really appreciate it!
Click to expand...
Click to collapse
If you want to at least get the data off of it you can try using testdisk.
http://www.cgsecurity.org/wiki/TestDisk
I used it for my external sd card that wouldn't read in the phone or computer anymore and had all my nands and other backups on it. It seems like it won't work on Android but it will, but since I formatted it in the phone it didn't seem to have a volume name.
After you select the drive and it comes up with the partition table list, select [None].
Then select [Analyse]
I think that's when it will list all your directories.
You might be able to hook up your phone and get stuff off the internal card if you leave it at the white htc screen, not sure. But I have used testdisk successfully on a drive and the sd card that all systems said was unreadable and needed to be formatted. Anyway, it's worth a shot to see if you can get your stuff off it even if you have to return it.
jayochs said:
so this guy came into my store who had a rezound, never once had a problem with it ever...then the battery died fully overnight because he forgot to charge it..
so when he woke up, it was dead obviously. he then plugged it in, and the orange light came on for 5 seconds...then shuts off. and nothing happens. this even happened when he brought it in for me to try. so i'm like, wtf, probably a bad battery maybe?
so i put in a good one we've got...same thing. so i ask if he's rooted or anything, he says no...but i did a search, and found some posts that when people had bad flashes of roms, it would stick at the white screen, and they had to restore a backup in CWM for it to work.
so i tried to see if maybe he was rooted...went into bootloader, hit recovery, and the phone just died. just shut off. so i was like, thats weird...so then i tried to do a factory reset....same thing, i hit factory reset, the white HTC screen came rgiht up, then the phone just died...and this was with a fully charged battery, too.
eventually we had to just call up and get him sent a refurb, but still, has anyone seen this problem? nothing i could do could get it to boot, and that's such a ****ty feeling especially if this guy said that he NEVER had a problem with any HTC phone, especially this rezound, until that battery died and it would'nt turn on again.
Click to expand...
Click to collapse
Yeah I had a lot of white screen time when I had the Evo! A co-worker of mine had this happen on his Evo. It was from overheating. Now I realize this is the Rezound we're talking about but brilliant phones do think alike.
Sent from my ADR6425LVW using Tapatalk
happened to me when the kernel didn't flash but the rom did. Had to boot into fastboot and flash a kernel through a command prompt on my PC.
Just finished dealing with this after a bad flash. I couldn't boot, couldn't flash a new rom because of the Mainver error and couldn't get into recovery. Finally fixed it by deleting the PH98IMG.zip file. That let me get into recovery. Then had to flash back from ICS to Gingerbread. The I could follow the instructions to fix the Maiver error.
I had heard reports that people had data loss issues from the battery dying all the way in the rezound? Something tells me running the RUU on the phone would have fixed it.
Sent from my ADR6425LVW using XDA App
So yesterday I was in a call with low battery when it shut off. Normally not a problem, just plug it into the wall for a while. Well when I tried to turn it on, it wouldn't even boot up. It was stuck at the red M logo. The LED showed amber colored as well. I left it plugged in and the light remained amber until 90% battery, where it turned green.
I tried to turn it on and its been stuck on the red M logo. Its been stuck for more than 12 hours now.
I CAN access fastboot, android recovery, etc. I already tried wiping the cache and even did a factory reset. Still wont work.
What can I possibly do? I luckily have a backup phone, but I've had my photon for less than a month, no warranty, and I'm a novice Android user. Any help would be greatly appreciated.
MooseV2 said:
So yesterday I was in a call with low battery when it shut off. Normally not a problem, just plug it into the wall for a while. Well when I tried to turn it on, it wouldn't even boot up. It was stuck at the red M logo. The LED showed amber colored as well. I left it plugged in and the light remained amber until 90% battery, where it turned green.
I tried to turn it on and its been stuck on the red M logo. Its been stuck for more than 12 hours now.
I CAN access fastboot, android recovery, etc. I already tried wiping the cache and even did a factory reset. Still wont work.
What can I possibly do? I luckily have a backup phone, but I've had my photon for less than a month, no warranty, and I'm a novice Android user. Any help would be greatly appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1393519
Click on the software and tools link and use rsd lite to reflash the stock os onto the phone. If that doesn't work I would take it to the sprint store.
I assume you tried pulling the battery?
I'm downloading SBF now. Hopefully it works, because I live in Canada and we don't have Sprint stores.
And YES, I tried pulling the battery. Multiple times. With every combination (eg, plug in, turn on, then insert battery; put in battery, turn on, then plug in, etc)
the sbf should work but may i ask how you managed to brick your photon? when i just got mine i did everything wrong and i never got even a soft brick so i'm interested what i didn't mess up haha
Quick question: I should be downloading the most recent? Will it make a difference?
And damn, did I actually brick it?? I'm pretty new to this thing, this is my first Android and I've had it for less than a month...
And nothing should have triggered it. I added another line in build (ro.media.setting.1080p or something) and I added another setting in /system/etc/mediaprofiles.xml. I was trying to add 1080p to the camera (unsuccessfully). I didn't remove anything, and even after a reboot it was fine.
It wasn't until the battery died, where it stopped booting up. Just my luck :/
You should probably choose one of the newer ones, just becasue of bug fixes, etc. If you happen to know what version you were running before then I'd choose that. I cant stress enough, make sure the one you download is for the Photon and NOT Electrify! And technically yeah that is a brick lol but its extremely hard to legit brick beyond repair a photon due to the fact that we have RSD Lite and SBF files to bring it back.
Strangely, I found a thread depicting the same problem that I had, although with the electrify. http://forum.xda-developers.com/showthread.php?t=14813
Anyways, the problem is fixed, by reflashing the SBF using RSD Lite, everything is back to normal! Well, almost, just have to restore my backup
Thanks so much for your help guys, I wouldn't have been able to fix it without you all!
can you fix a bricked phone??
My Photon has done the same thing! I rooted her and did the Bootstrap Recovery thing. Everything was kosher until I tried to load that stupid Beats Audio. Something happened between me flashing it and the reboot where it locks the phone. I tried to do the Android recovery screen, I wiped, I did about everything I could find. No bueno.
I followed this forum and clicked the software and tools link as instructed. I tried with RSD 5.6, and tried several iterations of SBF's located here and here. I was using SBF - 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_MR-3-CM.
It lets me go into boot mode, and when I try to flash the SBF it appears to go through, but it always fails at the end. Which, the posts state it will do, but my phone will not reboot afterwords. After trying everything I could for a couple days, I decided to just take it to a Sprint store. Mind you I've had this under 30 days, but longer than 14 so they stated it would have to be replaced. They tried to flash, but said they were getting stuck too.
I know that a replacement is pretty much the answer, but just wanted to check one more time to see if anyone had any other ideas, or could point me to other forums maybe? Appears I've done what few have been able to accomplish...brick this joker.
All,
I've been following posts on XDA since my original droid incredible days. I've rooted and maintained two phones, never have any issues.
Recently I purchased a T-Mobile Springboard (got a crazy promotion price through my company) which ran stock TMo Honeycomb. Eager to get ICS and eager to get rid of the power-on tmobile jingle, I installed the latest S7-302u firmware update from Huawei's website. I am aware that my device is technically S7-303u, but the update worked fine and I had little-to-no bugs. I am very pleased with this tablet.
Now here where I get stupid.
A coworker of mine then tells me that he has a S7-303u update.zip file that he can give me, which I don't object to. I give him my micro SD, he places the file in the 'dload' folder with 'unlmt.cfg'. I then reconsider my predicament, and decide that I'm happy with my current firmware, even if it's not made specifically for my tablet hardware version. If it ain't broke, don't fix it.
By the evening, I forget that the update file is on my SD card.
Before going to bed, I extinguish the battery and let it power down. I then plug it in the the wall and fall asleep.
Around 3 am (3 hours later) I was woken up to my springboard rebooting. Confused, I pick it up and see that it's in some kind of boot-loop. The screen turns on, but stays black, and then immediately powers down, and restarts. This process repeats indefinitely. I hold the power button down, trying to do a hard-reboot, but it doesn't seem t work. Then, after about 5 "holding the power button down for 10 seconds", the device reboots and I am graced with the gracious Huawei MediaPad logo.
The device automatically goes into recovery mode and installs the forgotten update.zip....
Now I'm pissed, specifically because I've lost my high scores in Trainyard Express and just because I now how to re-install all my apps. It's annoying, but it's not the end of the world. Or so I thought.
I use my tablet 75% of the time for reading through the kindle app, and on this version of ICS the kindle app doesn't work! So immediately I decide to revert back to the old S7-302u update that I originally had installed, following the same steps I did to manually update the device previously.
I now cannot, for the life of me, get this thing to boot into recovery mode. The only thing I can get this device to do is get to the "Enter into fastboot mode" screen by holding the power button and the volume+ key (the one closest to the power button).
A few other symptoms:
1. The device is set to quickstart mode by default and I don't see any option to deactivate it. The only way to get the device to actually "turn off" is to choose restart to hold the power button down for a hard reboot.
2. If I hold down the power button for ten seconds, I expect the device to power down and stay down. This is not the case. It always reboots immediately. I have no way of actually fully powering this device down (not counting the quick-start power-down).
3. No charging indication. I'm not sure if this is a hardware or software issue. My device will charge, but it does not give any indication on the screen or the battery icon.
Now I'm stuck wondering what to do. Did I ruin this device? I wanted to avoid rooting it because of the loss of 4G data, but now I'm afraid that I might need root-permissions to fix whatever I messed up.
Thanks in advance for your help.
Daniel
PS. Just so you all know my experience, I've rooted and maintained a droid incredible and currently, my galaxy nexus. I however, have no programming experience what-so-ever. I'm just good at following directions (usually).
What happens if you pull the micro sd card out? It should stop the boot loop (in theory). If the install didn't go through it should boot up normally to the previous version. In settings you can turn off FastBoot.
You might have to look at the sd card on a computer and either get rid of the unlmt.cfg from the dload folder and it shouldn't try to boot to the dload folder.
eurobass said:
All,
I've been following posts on XDA since my original droid incredible days. I've rooted and maintained two phones, never have any issues.
Recently I purchased a T-Mobile Springboard (got a crazy promotion price through my company) which ran stock TMo Honeycomb. Eager to get ICS and eager to get rid of the power-on tmobile jingle, I installed the latest S7-302u firmware update from Huawei's website. I am aware that my device is technically S7-303u, but the update worked fine and I had little-to-no bugs. I am very pleased with this tablet.
Now here where I get stupid.
A coworker of mine then tells me that he has a S7-303u update.zip file that he can give me, which I don't object to. I give him my micro SD, he places the file in the 'dload' folder with 'unlmt.cfg'. I then reconsider my predicament, and decide that I'm happy with my current firmware, even if it's not made specifically for my tablet hardware version. If it ain't broke, don't fix it.
By the evening, I forget that the update file is on my SD card.
Before going to bed, I extinguish the battery and let it power down. I then plug it in the the wall and fall asleep.
Around 3 am (3 hours later) I was woken up to my springboard rebooting. Confused, I pick it up and see that it's in some kind of boot-loop. The screen turns on, but stays black, and then immediately powers down, and restarts. This process repeats indefinitely. I hold the power button down, trying to do a hard-reboot, but it doesn't seem t work. Then, after about 5 "holding the power button down for 10 seconds", the device reboots and I am graced with the gracious Huawei MediaPad logo.
The device automatically goes into recovery mode and installs the forgotten update.zip....
Now I'm pissed, specifically because I've lost my high scores in Trainyard Express and just because I now how to re-install all my apps. It's annoying, but it's not the end of the world. Or so I thought.
I use my tablet 75% of the time for reading through the kindle app, and on this version of ICS the kindle app doesn't work! So immediately I decide to revert back to the old S7-302u update that I originally had installed, following the same steps I did to manually update the device previously.
I now cannot, for the life of me, get this thing to boot into recovery mode. The only thing I can get this device to do is get to the "Enter into fastboot mode" screen by holding the power button and the volume+ key (the one closest to the power button).
A few other symptoms:
1. The device is set to quickstart mode by default and I don't see any option to deactivate it. The only way to get the device to actually "turn off" is to choose restart to hold the power button down for a hard reboot.
2. If I hold down the power button for ten seconds, I expect the device to power down and stay down. This is not the case. It always reboots immediately. I have no way of actually fully powering this device down (not counting the quick-start power-down).
3. No charging indication. I'm not sure if this is a hardware or software issue. My device will charge, but it does not give any indication on the screen or the battery icon.
Now I'm stuck wondering what to do. Did I ruin this device? I wanted to avoid rooting it because of the loss of 4G data, but now I'm afraid that I might need root-permissions to fix whatever I messed up.
Thanks in advance for your help.
Daniel
PS. Just so you all know my experience, I've rooted and maintained a droid incredible and currently, my galaxy nexus. I however, have no programming experience what-so-ever. I'm just good at following directions (usually).
Click to expand...
Click to collapse
Thanks
What is the firmware version of S7-302u are you installed in your S7-303u?
Hey, I have the springboard and did the exact thing you did, somehow the stock recovery was all messed up, best bet is to install twrp using fastbood and cm10. just follow after_silences instructions here,
http://forum.xda-developers.com/showthread.php?t=2045808
[Edit]once you change tmo stock firmware you'll lose your 4g option(there my be a fix for this now)but you will be able to text and make calls over 2g, edge2 and 3g"no need for WiFi or side app"[Edit]