[Q] What firmware will i get back from warranty? - Desire Q&A, Help & Troubleshooting

Ok, my phone finally decided it didnt like being rooted etc..
It wasnt bricked but the amount of random reboots was becoming a joke! After reinstalling the RUU for about the 7th time - it got to the stage it would always reboot at some point on the setup screens of the stock ROM. I could not get to the homescreen without it rebooting
I have no idea why - formatted sd card/booted without sd card in it/flashed stock ROM! - all still the same. The phone was totally unstable and unuseable..
I got so annoyed i walked straight into my local o2 shop and got it sent away for repair. Its running stock ROM and i couldnt get anywhere near to re-rooting so i am happy on that part that they will be happy warranty wise(never did s-off either)..
Question is - what firmware am i likely to get back??.. Anything remotely rootable or not??

Was it branded from o2 when you got it? Chances are it'll come back with their FroYo ROM on it...and ALL ROMs are rootable

Yes it was branded - Cheers. You helped me the first time mate to get the phone working after it hung at the splash screen... Well this was the end result!
Phone was hanging where i would have to reflash the RUU when using 3g network. Then the reboots...
I am still clinging to some hope that it was the phone and not me!!!!

Related

[Q] Stuck in a boot loop

Hello All
I purchased a phone from a friend of a friend so I don't have all the history of the phone. It looks like they attempted to root it and failed.
I only got it to boot op fully one time. (and I can't get it to boot up fully again) It goes to the htc incredible logo and starts over.) So here's what I know. I didn't see a superuser apk the one time I got it to boot. It has the radio that ends in 07.28. It has s-on. It has a recovery but not one that I'm used to (like on ogdroid)
Its says android system recovery <3e>
reboot
apply update.zip
wipe/factory
wipe cache partition
and at the bottom
E: Can't open /cache/recovery/command
I've tried the unroot method to try to get it going, but no luck. I'm stuck. Any thoughts? Thanks for any help.
You can follow this thread, part 2
http://forum.xda-developers.com/showthread.php?t=786436
Basically, download this file
http://www.fourty.net/~berzerker/stockstuff/PB31IMG_3.26.605.1_RUU.zip
Rename it to PB31IMG.zip, put it on the root of your SD card, boot the phone into the bootloader (hold vol + & pwr when turning on) and let it update. It should return it to a completely stock 2.2 with no root. From there you can go root it or do whatever you would like.
Ok I tried that. The update goes through successfully but I'm still stuck in the loop.
Is there a way to root or get s-off with out booting the phone? (I'm using a mac)
this happened to me recently - I reloaded RUU - hard reset - removed sd - left battery out for a while - used my wifes battery - power plugged in - Wiped everything possible in cwr (before ruu)
The phone is completely stock and wont stay on for more than 5 seconds if it even gets to the lock screen at all. In the end I had to put s-on and request a replacement
one thing I did notice though (hope this helps) I left my battery out of the phone overnight and in the morning without power connected it did boot all the way and I popped on to the market and used the browser for about 15 minutes - then fell back in to a boot loop and I wasn't able to reproduce that working state again.
Incredible
Try looking for a Ruu to return it stock,
make sure you wipe all.
Sometimes it helps to be patient and watch out for heat issues.
Not sure if this is related but My Hd2 on 2.3 and Mytouch 4g on 2.3 would boot loop when it got a little warm Remove the batter and let it sit for 10 minutes.
Ok
It's back to stock. I still have the same issue. It is the same problem that h0x90 had. This phone isn't activated and I'm not sure if it has a warranty or not. I would rather try to fix it if I can. Can I root it with adb or otherwise in its current state? I wonder if a rom would fix the problem. It seems to be software and not hardware, correct?
Before I was desperate enough to wipe everything (ruu) I loaded several different roms and loaded my backups - so in my case it was a hardware issue.
Verizon told me they cover the phone for 12 months from purchase date - and they're overnighting a refurb to me for free which is nice. Maybe if nothing else you can get a hold of the previous owner and attempt to get a replacement.
Best of luck though either way!
nothing0 said:
Ok
It's back to stock. I still have the same issue. It is the same problem that h0x90 had. This phone isn't activated and I'm not sure if it has a warranty or not. I would rather try to fix it if I can. Can I root it with adb or otherwise in its current state? I wonder if a rom would fix the problem. It seems to be software and not hardware, correct?
Click to expand...
Click to collapse
As the Incredible hasn't been on the market for a year yet, it's assuredly still within the warranty period.. As for trying to fix it yourself, I can all but guarantee that you cannot since what you're experiencing seems to be a relatively common hardware failure.
I finally gave up. I did find out that PCD at 1.800.229.1235 does warranty work for HTC. Maybe that information will help others. Thanks to all that helped.

[Q] Lost recovery, White screen boot loop.

Ok I'm lost. I'm working today and my phone tries to reboot for no apparent reason and is put into a boot loop that I cannot get out of no matter what. In boot loader I have no recovery. Downloaded amon ra recovery's PC36IMG.zip. Booted into bootloader it said it updated the recovery but after I've rebooted I still have no recovery. I don't think this is very good.
Bootloader asked you to update and reboot and it went through completely?
Yeah, it said update was succesful. Thats why I'm so confused.
So when you go into recovery from the bootloader, do you see the triangle?
Nope just back to white screen boot loop. Trying to flash sprint lovers with the pcm36img over it maybe that will bring me back to stock rooted stat.
Edit: Back to white screen boot loop.
this same thing happened to me a week ago. were u running a cm7 rom?
yeah ex10 i was going to switch last night guess its too late
Damn I feel bad for you
I had that same problem when i first rooted and flashed my evo. I suddenly got into an infinite boot loop where i no longer had a recovery. Sorry man i had to take it to a sprint store after i tried flashing a different bootloader and then retry flashing a different recovery from clockwork to amon. and then even tried to flash the stock rom none work. if none of those work then you most likely is going to have to go to a sprint store.
Well, you could try running an RUU. This will leave you unrooted and completely stock so you will need to root again.
Here's a how-to over on Android Central.
http://forum.androidcentral.com/htc-evo-4g-rooting-roms-hacks/19278-how-unroot-return-stock.html
when this happened to me last friday i looked around xda and i found a couple other people who had this problem as well. everyone i found (myself included) was running a cm7 rom. i still cannot get any farther than bootloader without a white screen loop. sprint sent me a replacement on warranty because i live too far from the sprint store for them to make me drive there but i have to send my old one back. its still s-off tho and even running the stock ruu does nothing to fix that. anyone know of how to get s-on without the ability to enter recovery or anything else? or a way to brick it completely so it wont boot to bootloader where they can see s-off?
Threw mine out of the window of my car and called sprint and told them I lost it. Cost me $100 to get a replacement and now I'm going to have to spend forever getting back to root and eng boot ect... sucks.
Has this only happened with the magnus cm7 or is the happening with the official cyanogen rc1 and nightlies? Because I'm really wanting to go to the CM7 nightlies but not if the chance this is going to happen again.
ChacocII said:
when this happened to me last friday i looked around xda and i found a couple other people who had this problem as well. everyone i found (myself included) was running a cm7 rom. i still cannot get any farther than bootloader without a white screen loop. sprint sent me a replacement on warranty because i live too far from the sprint store for them to make me drive there but i have to send my old one back. its still s-off tho and even running the stock ruu does nothing to fix that. anyone know of how to get s-on without the ability to enter recovery or anything else? or a way to brick it completely so it wont boot to bootloader where they can see s-off?
Click to expand...
Click to collapse
Does the bootloader let you run a PC36IMG.zip? If so, try running one (of a factory unrooted ROM), and when it goes to reboot and shows the green arrow facing down (if it gets that far) yank the battery at that point. I think that is when it's writing the radio image. If you can get it to that point, and then pull the battery, I'm pretty sure you'll have a brick. Aside from a battery pull during the radio flash, I'm not sure how to make a brick, without it being obvious of what you've done. You could rig your phone charger up to a 230 volt outlet from a drier or something, and plug it in. haha. maybe that would fry it, tell sprint you got a power surge when it was charging, and then it wouldnt turn on. (only 1/8 serious on that last part )
Has this only happened with the magnus cm7 or is the happening with the official cyanogen rc1 and nightlies?
Happened to me with official cm7 rc1
Does the bootloader let you run a PC36IMG.zip?
yes, but it doesn't actually do anything. it will go thru the whole update process but still goes back to a white screen loop and no recovery. tried a battery pull during the radio update a couple hours ago (i thought the same thing) but it did nothing. i think its because its not actually doing anything when u run the pc36img other than going thru the motions on the screen.
maybe i can microwave it hahaha
edit: after a couple battery pulls during the radio update in the pc36img im using, it will no longer go thru the full radio update when running the zip so i definately screwed up the phone. it still gets to bootloader no problem tho so ive accomplished nothing.
ChacocII said:
Has this only happened with the magnus cm7 or is the happening with the official cyanogen rc1 and nightlies?
Happened to me with official cm7 rc1
Does the bootloader let you run a PC36IMG.zip?
yes, but it doesn't actually do anything. it will go thru the whole update process but still goes back to a white screen loop and no recovery. tried a battery pull during the radio update a couple hours ago (i thought the same thing) but it did nothing. i think its because its not actually doing anything when u run the pc36img other than going thru the motions on the screen.
maybe i can microwave it hahaha
edit: after a couple battery pulls during the radio update in the pc36img im using, it will no longer go thru the full radio update when running the zip so i definately screwed up the phone. it still gets to bootloader no problem tho so ive accomplished nothing.
Click to expand...
Click to collapse
Damn, so you can still see s off? I have no clue how to get it to s on then, or make it so you can't even get to the bootloader. Yea, if you microwaved it (haha) i'm sure it wouldnt ever turn on again. However, whoever looks at it would be able to tell that something went very, very wrong, and it wasn't the phone's fault. ha. Maybe it won't even matter that it's s off. I've heard of people having luck with sprint looking at a phone that is s off, but I've also heard the oppositte (more often).
i actually told the sprint tech on the phone that i had rooted it and he still warranty replaced mine. im just hoping they dont change their minds when they get it back and see s-off and try to charge me 500 bucks for my new one.
Wow. Yeah, if it won't even run a PC36.img from bootloader, you're kinda SOL. That's pretty much a last resort. Granted, you should try a few different img's (different d/l sources) before assuming it's screwed. Sometimes, you can get a bad download. I had a stock Evo that wouldn't go into recovery, so I flashed a RUU from bootloader, and everything was fine. Best of luck with your replacement though, brother.
well i have 14 more days before i have to send it back. there must be some way to get it to not turn on at all without physical damage, just gotta figure it out.

[Q] HTC Desire Serious Issue!!

Ok i did searched a lot of sites before writing this, i just wanted to let you guys know the complete detail from where it started all the way down..
- I tried rooting the device through revoked, it failed and my phone got stuck at HTC logo.
- i install one of the ROM from shipped rom website and it start working again but had issue of random reboots.
- After few weeks my desire got heatup restarted and again stuck at HTC logo.
- This time i installed the official Gingerbread from HTC website, it works fine for few days but then again, when i used the phone for games or movies it get too hot and went reboot loop, unless i remove the battery and let it cool for few minutes.
- Last week i left for some work, got back home and my phone was on reboot loop for about an hour.
and this time reinstalling ROM doesn't solved the issue, any ROM which i install stuck on HTC screen and if i do install the Gingerbread it gets the reboot loop.
I gave up and try some local repair shop as i dont have any HTC center here in my country, the guy tried for 3 days now he said its Dead or bricked whatever you called it.
Everything is working fine from installing of ROM through either USB or SD Card, Fast boot is working good but its not booting at all, should i lose all hope for this phone and trashed it or there is still some hope?
Kindly Help
Mady4Real said:
Ok i did searched a lot of sites before writing this, i just wanted to let you guys know the complete detail from where it started all the way down..
- I tried rooting the device through revoked, it failed and my phone got stuck at HTC logo.
- i install one of the ROM from shipped rom website and it start working again but had issue of random reboots.
- After few weeks my desire got heatup restarted and again stuck at HTC logo.
- This time i installed the official Gingerbread from HTC website, it works fine for few days but then again, when i used the phone for games or movies it get too hot and went reboot loop, unless i remove the battery and let it cool for few minutes.
- Last week i left for some work, got back home and my phone was on reboot loop for about an hour.
and this time reinstalling ROM doesn't solved the issue, any ROM which i install stuck on HTC screen and if i do install the Gingerbread it gets the reboot loop.
I gave up and try some local repair shop as i dont have any HTC center here in my country, the guy tried for 3 days now he said its Dead or bricked whatever you called it.
Everything is working fine from installing of ROM through either USB or SD Card, Fast boot is working good but its not booting at all, should i lose all hope for this phone and trashed it or there is still some hope?
Kindly Help
Click to expand...
Click to collapse
Did you ever obtain root? If not, I have found that Revolutionary has better luck on the Desire than Unrevoked.
Cool story bro. Can you please post technical details about your phone? Hboot version would be a good place to start.
When you allowed your local repairman to touch it, you more or less sealed its fate. Everything points to board issues.
stankyou said:
Cool story bro. Can you please post technical details about your phone? Hboot version would be a good place to start.
Click to expand...
Click to collapse
bravo pvt1 SHIP S-OFF
Hboot-1.02.0001
Radio 5.17.05.23
just got it back for one day, before i give him back for mobo replaced..
Btw will try the gold card method..

stuck on LG boot screen not rooted

Hey guys my verizon g4 is stuck in bootloop and im not rooted, i cant get the past the lg boot screen, it stays on their for around 20 seconds goes black and back to lg screen.
I can get into recovery but none of the options do anything ive tried safe mode, usb debug mode i even tried factory reset they all just go back to the lg screen.
I was just watching a video on facebook when it froze restarted and now im stuck, ive been restarting it all day and i was able to get it to boot up twice but it froze again within seconds any help is appreciated
it might be the defective motherboard issue that people are having. you could try reflashing the system, but if that doesn't work you probably need a new motherboard/phone
Not an answer, but an experience.
I have an HTC ONE M8, VZW. I s-offed it and rooted it right when I got it. I began adding some of my google apps and it did what your G4 is doing, stuck on VZW screen.
Since I was s-off I was able to get a recovery in and ready. I was able to get a custom rom onto the phones external sd. I flashed it with the recovery and the flash took, no more vzw screen lock up.
Your experience makes me wonder what VZW is doing to force bootloops on unlocked or rooted phones with their retail products. Paranoid maybe, but I can see VZW deliberately adding code to stick it to rooted users.....................................I say this still knowing that many have rooted the current run of devices without issues...........................
luck
i read about the problems with the motherboard going bad, im assuming thats what happened to mine. Lg sent me a replacement under warranty
Update!
i called verizon they sending me a replacement. just to let you know i flashed 13B KDZ but the bootloop was still there i let my phone on and finally turned on quickly i did a factory reset and booted up normal and its working again. still im gonna send it back. just sharing my experience maybe for other people might work too.
killa408shark said:
Update!
i called verizon they sending me a replacement. just to let you know i flashed 13B KDZ but the bootloop was still there i let my phone on and finally turned on quickly i did a factory reset and booted up normal and its working again. still im gonna send it back. just sharing my experience maybe for other people might work too.
Click to expand...
Click to collapse
What is the 13B KDZ and how did you flash it? Im having same exact issue.
My G4 tanked over the weekend. I was browsing news and the phone locked up, then it shut off and turned back on. It just bootloops now. If I stick it in the freeze for a few minutes, sometimes it will boot to the OS where it starts to optimize the apps. It will get through about 20 before it shuts off and starts the bootloop process again. I haven't even been able to get the download mode to stay on, and when it does enter download mode, it is not detected by the computer. I think my problem is the motherboard. I'm just hoping that they aren't able to figure out I had it rooted!
I'm still waiting to hear back from Verizon about a replacement.
Does anyone have any ideas on how I can flash a stock rom back on this thing to try to save my tail? I am betting not since the phone won't stay on long enough to even flash the rom.
b3y0ndd34th said:
My G4 tanked over the weekend. I was browsing news and the phone locked up, then it shut off and turned back on. It just bootloops now. If I stick it in the freeze for a few minutes, sometimes it will boot to the OS where it starts to optimize the apps. It will get through about 20 before it shuts off and starts the bootloop process again. I haven't even been able to get the download mode to stay on, and when it does enter download mode, it is not detected by the computer. I think my problem is the motherboard. I'm just hoping that they aren't able to figure out I had it rooted!
I'm still waiting to hear back from Verizon about a replacement.
Does anyone have any ideas on how I can flash a stock rom back on this thing to try to save my tail? I am betting not since the phone won't stay on long enough to even flash the rom.
Click to expand...
Click to collapse
+
My phone was rooted and got into the bootloop also and I sent it in as is and nothing happened. So I think it would be fine to send it without the stock rom.
mainlygreen said:
+
My phone was rooted and got into the bootloop also and I sent it in as is and nothing happened. So I think it would be fine to send it without the stock rom.
Click to expand...
Click to collapse
Thank you for this information, this makes me feel a little better!
The replacement is already in the mail!
same issue of mine I was out then it cut off & wouldn't come back on but now it charges up & makes it to the boot screen
b3y0ndd34th said:
Thank you for this information, this makes me feel a little better!
The replacement is already in the mail!
Click to expand...
Click to collapse
did you send the faulty unit first or they are sending it on your complaint. I am outside US and my G4 got bootloop issue n i was wondering how to get the replacement through somebody as i wont be coming for another year.
thanks
bhuvesh89 said:
did you send the faulty unit first or they are sending it on your complaint. I am outside US and my G4 got bootloop issue n i was wondering how to get the replacement through somebody as i wont be coming for another year.
thanks
Click to expand...
Click to collapse
They mailed me a new one, no battery, no back. I put my battery, sim card, sd card, and back on the new phone, fired it up. Rolled it back, rooted it, then I mailed the old one back.
Personally, I love this phone, but I think I will be getting a nexus next.

Completely messed up ROM

Heya folks,
So my HTC 10 just randomly crapped out on me a few weeks ago. Been trying a few things to try to flash a new ROM on there, but I'm not having much luck and need advice. I was using my phone like I would any other time and all of a sudden the phone froze and restarted, but when it restarted it was taking forever to load back up (was just stuck at the HTC logo). I tried turning it off and on again and realized the thing was bootlooping on me. It wouldn't boot into system, download, recovery, nothing.
Now, here's the issue. My phone's S-ON and the bootloader is Locked. I've never done anything to the software on it before (but for some reason the software status is "Modified", which is weird. I did buy this phone used, so that could mean something, but I've never seen a modified software status on a bootloader that was not unlocked). The symptoms are pretty weird. I tried flashing the ROM using an official HTC RUU EXE, but the thing keeps saying that my phone is below 30%, and when I charge the phone it always starts charging at 22% (all the more reason I think the software is just completely kaputs). I found this thread where people were talking about the SD Card solution, but I'm quite sure the only way this would work is if my bootloader is unlocked.
So what do you guys think? Am I in a catch 22? Am I missing something? Any and all replies or questions would definitely help.

Categories

Resources