Hi guys.
After two weeks without wifi, yesterday, my phone decide to update about 20 apps from market. When Beautiful Widgets were downloading, phone suddenly froze and I had to remove my battery after 10 minutes. When it booted again, Angry Birds started to update and phone froze again. So I removed my battery once again and when it booted up, I turned my net connection offline to prevent downloading. As soon as I did so, I canceled all market downloads and turned connection online again. Market started updating on its own and phone froze during night.
So I decided to removed battery once again this morning and when I put it back in, put it back in, phone froze after "Quietly Brilliant" logo with black screen.
It was suitable for factory reset from bootloader. So I did factory reset and same story repeated, except for this, it was a loading loop, HTC Quietly Brilliant and sound which comes with it over and over again.
So in the end, I tried to do the "recovery" option which did no good and again factory reset, but this time, bootloader froze and nothing happened. This is final state of my phone.
So after boring story, there is a question. Is there any way I can do software flash / reset without phone (via USB etc?) before I send it back to HTC for repair?
Device is S ON and never been rooted. I also removed SIM and memory card with no effect.
Thanks a lot!
You should take hope from the fact that you are able to still enter bootloader and perform full reset
Also the fact that you are still s-on means that you should still be covered under warranty
I believe that you should be able to re flash your original rom via your pc using RUU, check to see if your original is in the rom sticky thread within the dev section and if so start downloading
Sent from my HTC Desire S using XDA Premium App
You may well have a hardware problem, in which case I would advise you send it for repair rather than trying to root and invalidating your warranty.
Hey, thx for reply.
I have no experiences in this but I guess I only need to know this things:
RUU - Stands for ROM Upgrade Utility. What soft should I use?
Also, all I can see in bootloader is following:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
RADIO-38.03.02.11_M
eMMC-boot
Mar 10 2011,14:58:38 (<wtf?)
and then just classic boot menu with options like FASTBOOT etc.
Therefore I cant figure out, which ROM is mine in that thread. Also, is there any option to flash ROM from memory card? Does it have to be signed?
Only limitation is warranty which I dont wanna lose. Thx.
InfernalByte said:
You may well have a hardware problem, in which case I would advise you send it for repair rather than trying to root and invalidating your warranty.
Click to expand...
Click to collapse
See the statement above, I will not do anything to invalidate the warranty.
Yesterday, after attempting the "Update all" for the first time (well, not exactly) the phone froze just as yours did & started encountering the same issues. After coming here to seek assistance, this thread was the first I laid eyes upon.
My case in somewhat more detail, after freezing during the "Update all", I performed a soft reset by removing the battery as well, booted up fine, but as soon as everything was loaded the market tried to continue where it left off (which is updating Opera Mobile @ 98%) and the result was another freeze. I was quickly able to deduct that the update were to be the issue & turned off connectivity. Now, at the present state, Opera Mobile update is still under notifications (at 98% complete but "paused"), as soon as I re-enable either WiFi or 3G it continues & crashes. I cleared all caches & reset all Market applications & rebooted to no avail.
Hard reset was next on my list, but see-ing how the situation got worse for your device hereafter, I am holding it off for now. Is it possible to have market updates, that are ongoing, canceled? Bear in mind that I cant enter Market since it requires connectivity.
Weird stuff.
Yes, when your phone is turned on (connection on), open your Market app, press menu button and select "My apps". You should see all downloading apps now. Hold your finger on each and wait until menu pops up. Select cancel download. You have to be quick tho.
If I were you, I would not do any software reset, my phone is pretty much bricked now, as it freezes on nearly every bootloader option.
Numline1 said:
Yes, when your phone is turned on (connection on), open your Market app, press menu button and select "My apps". You should see all downloading apps now. Hold your finger on each and wait until menu pops up. Select cancel download. You have to be quick tho.
If I were you, I would not do any software reset, my phone is pretty much bricked now, as it freezes on nearly every bootloader option.
Click to expand...
Click to collapse
Thanks! That did the trick, was able to remove everything due to be updated.
Strangely, though, I wasn't able to finish loading the market before it resumed the Opera update. This time, however, instead of crashing it was able to complete it (contrary to the last 10+ attempts yesterday), thus there is a chance it wouldn't have crashed at all. In any case, keeping distance from the Market seems like a valid idea for now.
Reading your thread might've helped to avoid my device turning into a brick, I appreciate it.
Well, update to my current status:
Im still in hboot. Device was recognized as "Android 1.0" in my Windows, so I had to install ADB driver. It is now connected as Android Composite ADB Interface".
I can't get any further, since RUU says my phone is not connected to PC.
Any advices please?
PS: When I choose "Recovery" in hboot, it shows HTC logo for a while, then icon of mobile phone with green sign shows and after few secs, screen turns off and phone vibrate for a few times and disconnects from PC.
//When I connect it in Fastboot, it shows as "MyHTC" in Windows.
Numline1 said:
PS: When I choose "Recovery" in hboot, it shows HTC logo for a while, then icon of mobile phone with green sign shows and after few secs, screen turns off and phone vibrate for a few times and disconnects from PC.
Click to expand...
Click to collapse
Afraid, that I'm well out of my depth with all that, hopefully someone else with more knowledge will post...or else it's warranty return. best of luck
Np, thx for trying, maybe someone else will know
//Update: In Fastboot mode, my device is recognized by RUU!!! Trying to update right now!!!
As you've never been rooted or S-off, and the phone has developed its own fault. I'd return it!
Well, so far, no luck. RUU stuck at "Rebooting to bootloader" and phone is frozen.
InfernalByte said:
As you've never been rooted or S-off, and the phone has developed its own fault. I'd return it!
Click to expand...
Click to collapse
Im willing to do that first thing tommorow, but Im trying to fix it today, as it is sunday and I have day off.
Numline1 said:
Well, so far, no luck. RUU stuck at "Rebooting to bootloader" and phone is frozen.
Im willing to do that first thing tommorow, but Im trying to fix it today, as it is sunday and I have day off.
Click to expand...
Click to collapse
Good luck
(....10 Chars...)
Ok, update about my phone so far:
RUU was not sucessful, for some reason there's still freeze in certain HBOOT actions, like when I select "Factory reset" or when RUU is trying to get phone from fastboot to bootloader.
So I extracted rom.zip from my RUU and now I'm backing up my memory card using my old phone. I'm willing to rename it to update.zip and try to flash it.
Any advices about this?
Numline1 said:
Ok, update about my phone so far:
RUU was not sucessful, for some reason there's still freeze in certain HBOOT actions, like when I select "Factory reset" or when RUU is trying to get phone from fastboot to bootloader.
So I extracted rom.zip from my RUU and now I'm backing up my memory card using my old phone. I'm willing to rename it to update.zip and try to flash it.
Any advices about this?
Click to expand...
Click to collapse
Update.zip will not work, if your determined to try something push a new SPL via fastboot commander, even thought your not S-off if things aren't working maybe the CID check wont check either.
Below will only work if your phone is not branded or you have a goldcard.
Alternatively unzip your RUU on your PC in one of the files called {squigly brackets and a lot of numbers673652435364849483763} you'll find a .zip called rom.zip rename this PB99IMG and put the file into the root directory of your SD card, and boot into Hboot. Just answer yes to any questions. This is the way HTC Tech folk themselves serve an RUU.
Yea, I actually extracted it using advanced system monitor from microsoft, this file was in temp folder. That's where my rom.zip was. Anyway, isn't it PB88IMG.zip? I think DS is checking for this one. Thx.
//Edit: I mean PB88IMG.img
//Edit2: It's PG88IMG.zip It's now updating, don't know if it works yet, still at BOOTLOADER update with status "Updating".
Ok, I think this is my last post, since I no longer know what else to do. When Im trying to flash PG88IMG, it stops at [1]BOOTLOADER - Updating.
For more than one hour. There's something wrong with it and I will claim my warranty, which will be funny, since Im in Slovakia, phone was bought from Amazon with 3 year warranty from SquareTrade and they claim, they may just return money in some cases, which will result in buying a new phone = more than 2 weeks...
Numline1 said:
they may just return money in some cases, which will result in buying a new phone = more than 2 weeks...
Click to expand...
Click to collapse
O, bugger!
question is if they do give you the money, will you buy another DS? and if not what would you consider instead? Sensation?
Yea, can't say yet, since I don't know. I just discovered, there may be a chance they will cover my repair costs when I email them all the service documentation from service center.
But if they do, I'd like to stay with HTC, I paid something about 377L for the phone, so I may buy something better now.
Anyway, thanks a lot for help guys, if you come with some new ideas about how to fix it, do not hesitate to tell me I'll be sending it to them first thing tommorow.
Hi guys, sorry if there's some solution already available on the forum, but I didn't find it and am really afraid of what the fu** is happenning with my Desire S One day I have entered Android Market and clicked "Update All" in "My Applications" tab (there were about 14-15 updates available) and lied down my phone on the desk. After few minutes I looked at it and it was dead (blac screen with backlight on) - it was not responding at all, so I pull the battery out and in again. This time it was still able to turn on, but every time it got stuck in few minutes (when updates have resumed) - the only way to get it works was to canlcel every update. I was able to cancel one per reboot (before HTC got stuck), but after few reboots I have finally canceled all updates, and... my phone seemd to work properly again Yeah... 'seemd to' ;/ I have updated few apps manually (only one at a time) and then tried to download and install some new app (about 25MB) - then my phone has finally broke down;/ At the beginig I was able to enter a bootloader, but after trying to enter recovery (it has failed because there were no backup in sd/recovery dir) it has died at all - not reacting for any key pressed After plugging it to PC it has started to blink with it's LED, but that's all And later it didn't even want to blink with this diode
Has anybody any idea, what the hell is going on?? I have never flashed that phone etc. so what could happen? Please help me, because I want to avoid hard resteing my phone to save some data on it if it'll be still possible...
Oh, and sorry for my english
This has been mentioned before and the 'update all' option seems to have been a contributing factor to fried eMMC along with pulling the battery and putting it back in again to quickly
Read the posts in the end of the index thread, eMMC issue section (see last link in my sig)
Swyped from my Desire S using XDA Premium
Thanks for replies, now I see that it truly can be an eMMC issue :/ I have read littlebit about it now, but unfortunatelly I can't even check if my eMMc is fired, cause I haven't got debugging mode on And now ADB works correctly on my PC, but it doesn't see my device
BTW. Can you tell me how to execute instructions given by amidabuddha (about checking eMMC)? He writes to execute "dmesg | grep mmc0" comand, but this command is not recognized by my command prompt (paths are set correctly and so on) so I'm not able to try it even on a working phone (Wildfire connected and recognized by ADB correctly)... :/
EDIT:
I have read somewhere, that if my bootloader is unlocked, than I can flash a new recovery image and do a nandroid backup. Does it mean "if my phone is S-OFF"? Is there any way to retrieve some data from my phone if it's not? I'm still able to get into bootloader, so it should be easy to reset to factory defaults (if my eMMC isn't fried, which I can't check ), but I still got hope to save some data... Can anybody help?
mrkaczor said:
Thanks for replies, now I see that it truly can be an eMMC issue :/ I have read littlebit about it now, but unfortunatelly I can't even check if my eMMc is fired, cause I haven't got debugging mode on And now ADB works correctly on my PC, but it doesn't see my device
BTW. Can you tell me how to execute instructions given by amidabuddha (about checking eMMC)? He writes to execute "dmesg | grep mmc0" comand, but this command is not recognized by my command prompt (paths are set correctly and so on) so I'm not able to try it even on a working phone (Wildfire connected and recognized by ADB correctly)... :/
EDIT:
I have read somewhere, that if my bootloader is unlocked, than I can flash a new recovery image and do a nandroid backup. Does it mean "if my phone is S-OFF"? Is there any way to retrieve some data from my phone if it's not? I'm still able to get into bootloader, so it should be easy to reset to factory defaults (if my eMMC isn't fried, which I can't check ), but I still got hope to save some data... Can anybody help?
Click to expand...
Click to collapse
What is your bootloader version? If you are S-OFF then you can install a Recovery and in the better case formatting cache will do the trick. If your bootloader is locked (Stock) just give your device for a repair. This is a well known problem to the HTC guys and it will be covered by your warranty.
All the data on your SDcard is still there (pictures, etc). The contacts and calendar items can be restored via your Google account later if you had a sync previously. Probably you will lose your SMS.
Unfortunatelly my phone is S-ON, the informations given in bootloader are as follows:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 30 2011,17:29:31
So it seems that the only solution is to send my phone for eMMC replacement And to say 'goodbye' to all my data... Anyway thanks for help guys...
Downloaded Advanced ACE Hack Kit (30042012)
Disabled apple drivers, shutdown extraneous applications, disabled firewall and antivirus, and did all the other prep steps recommended in the Effen manual.
Yes, I read the Effen manual
Never had HTC drivers installed or sync software. Installed drivers bundled with AAHK.
Plugged phone into laptop USB port - device was detected, drivers installed. Launched AAHK, selected 1 for the automated flash process.
Things seemed to go fine, however I saw a few errors (a few of which seemed to be anticipated by the script and were reported as expected and normal), and the phone rebooted a number of times.
Ended up on a white screen, with the phone totally locked up and unresponsive. Pulled the battery and rebooted holding power and volume down to boot into CMR (white screen with old school pixelated text?).
All appears not to be well though. I can't get the phone to boot and have yet to try installing any kind of ROM. Have tried to repeat the process, but the laptop will not install the drivers for the device this time when I plug it in - Android 1.0 device shows up, but the machine can't find the right drivers (maybe the device ID changed during flash?). Device manager lists the device as not working (missing a driver)
Device Instance ID: USB\VID_0BB4&PID_0C94\HT11NT206202
In looking at the summary screen on the phone, I see the following:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.03.02.26_M
eMMC-boot
Apr 12 2011,00:55:45
After trying a few different options, my current status is:
HBOOT USB PLUG
I downloaded Ubuntu 12.04 LTS and tried re-running the flash, but the AAHK doesn't see the phone - says 'waiting for the phone to be connected' or something similar.
Given that I REALLY don't want to brick the phone, I am cautious about trying to work out the next step myself. Had wondered about:
1. Trying to get the (Win XP Pro SP3) drivers installed correctly for that device - then I could try re-running the flash process again.
2. Why did the flash process fail. I didn't have anything in the PD98IMG folder as I understood that was optional, yet the hack kit complained about the file being missing when it started running - red herring?
3. Do I need to put a rom on the SD card and use CMR to load that? If so, I am not sure I have a microSD to SD adapter handy right now?
Am on IRC looking for assistance - this post is to summarize my circumstances and hopefully help anyone in the same position later on.
Thank you in advance!
Solved
Thanks to @PaxtonCamaro91 on IRC for this:
Booted to livecd
- tried to run AAHK, but it errored saying it could not find the device
- rebooted phone in fastboot mode, still did not work
- booted to white HTC screen (not bootloader)
- AAHK then detected phone - selected T from AAHK menu selected fastboot RUU
- selected 1 to reflash.
The flash succeeded this time, but only took about 45 seconds to complete.
Rebooted phone, saw AT$T Rethink possible screen, which didn't appear before, and eventually came all the way to the desktop.
Confirmed adb reboot recovery and adb reboot bootloader worked from a terminal window
Confirmed S-OFF now showing under bootloader screen.
Carried out factory reset and am now moving on to AOSPX ICS 4.0.4 !!
Thanks to all who made this possible - awesome tool, awesome support!
im having the same issue, constantly fails downgrade and now doesnt even aknowledge attempts in bootloader.
im stuck here and have even tried onther pc, with the same outcome
jw2k_fr said:
Thanks to @PaxtonCamaro91 on IRC for this:
Booted to livecd
- tried to run AAHK, but it errored saying it could not find the device
- rebooted phone in fastboot mode, still did not work
- booted to white HTC screen (not bootloader)
- AAHK then detected phone - selected T from AAHK menu selected fastboot RUU
- selected 1 to reflash.
The flash succeeded this time, but only took about 45 seconds to complete.
Rebooted phone, saw AT$T Rethink possible screen, which didn't appear before, and eventually came all the way to the desktop.
Confirmed adb reboot recovery and adb reboot bootloader worked from a terminal window
Confirmed S-OFF now showing under bootloader screen.
Carried out factory reset and am now moving on to AOSPX ICS 4.0.4 !!
Thanks to all who made this possible - awesome tool, awesome support!
Click to expand...
Click to collapse
THANK YOU!!! My phone is back from the dead! , oh btw I was running AAHK on Windows 7 Home Premium 64bit
This is why I have been advocating using the Ubuntu Live CD method for many months. I've never seen anyone have problems going that route.
Hi,
I have my HTC Desire S for about 6 month and it worked fine. About three weeks ago I installed the official ICS upgrade for this phone. The phone was rooted (by me) so I re-locked it in order to apply the update (sorry if I'm not using the right terms, I a bit new for this..).
A week ago, while in visiting in Rome, I tried to open my phone after the flight and it started a reboot loop. After a while it somehow recovered, and from the HTC recovery log I saw there was some "radio failure".
During the last week it would reboot from time to time, and I thought I would check it out when coming back home.
Now, trying to open it after the flight home - it won't even get beyond the HTC logo, just stuck in endless reboot loop.
I read some posts on this problem, but because my phone is re-locked I don't know what I can do: any thread about this problem requires the phone to be rooted. And I'm not sure how to root it because any thread about performing a root requires to open the phone and set up some settings, like 'enable debugging' for the USB connection (which I cannot do because phone keeps rebooting..).
Here is what I see at the HBOOT screen, hope it helps:
*** RELOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.02.0002
RADIO-3831. 19.00.110
eMMC-boot
Jul 31 2012, 15:41:32
Trying to select FACTORY RESET will not help.
Trying to select RECOVERY ends with an error (I get a screen with a nice picture of the phone and red exclamation mark near it).
PLZ HELP!!
Thanks
Update: I've unlocked my phone again using the HTC site, so now the HBOOT screen shows *** UNLOCKED *** as the first line, other lines are the same (if this helps...)
UPDATE: I've used some very good guide (unfortunately I cannot post the link because I'm a new user..) for rooting and flashing a new ROM to my phone (downgraded to Gingerbread ROM), BUT the phone keeps rebooting..
Help plz....
As it did work until you opened the phone, either you made a physical problem, and now need a new board because it is defective, torn, cracked or something...
Or you made a mistake by removing the battery while the phone was still (partially) powered. This may cause some partition damage like on a pc. As there is no chkdsk available, the easiest solution is to repartition and reformat.
I read you already have reformatted the data partition by factory reset, and tried to repartition by installing that old update.
That would not work, as a normal flashing of a (custom or original) rom will / can not repartition the emmc chip. The only way to do that is to execute the RUU again what made phone get the ICS Update.
If that doesn't solve your problem, your phone seems to be defective.
The last option that remains then is to replace the emmc chip.
Verstuurd van mijn Nexus 7 met Tapatalk
Thanks for the reply.
Can you explain how should I reformat and repartition? I have now the ClockworkMod Recovery (V5.8.1.5)
I cannot run RUU because the exe file tries to connect to the phone and gets an connection error. It only worked when the phone completed its upload and now (because of the reboot-loop) I can't get to this state.
Ok, It took me some time to understand that when in fastboot the PC has communication with the phone and I can install RUU..
So I re-install the HTC official ICS RUU for my device and it seems PROBLEM SOLVED!
Phone has started, I could play with it a bit... and no reboots yet.
Let's see if it keeps like that for several hours / days... I hope it is not an hardware problem and only software...
Thanks!
Just as a quick intro, hello everyone. I'm new to the forum, but I've been reading from this site for a couple years now. Now that that's out of the way...to the real question.
So, my DNA committed suicide the other day and I received an HTC One M7 from a friend of mine who switched to apple. Yeah...he's stupid. But it's my gain. ANYHOW! It's a sprint HTC One m7 with the 1.57 hboot. I've come across an issue with trying to break this system open. Unlock went great along with TWRP recovery flash and superSU. No issues with any of that. HOWEVER! Somewhere down the line I believe my baseband and IMEI has been lost internally. I only come to this conclusion through research and finding a somewhat similar situation.
Currently, this is what's happening. I can enter bootloader and recovery just fine. The phone boots up just fine. But, once the phone is booted and I unlock the screen, all I get is a white screen with an HTC logo. Touch works, vibration works, it registers everything I do including the pull down (just to display header. it never actually pulls down), usb debugging icon, sounds, screenshot, PC recognizes device and everything. But it stays like this for about a minute or two and then restarts. It does this over and over.
I've been trying to s-off using rumrunner just to see if by chance it'd have success, but the phone won't recognize ADB. It will recognize fastboot commands perfectly, but not ADB. And yes...I use ADB commands in recovery I've tried every driver I could think of and every version of recovery and adb.exe I could find compatible. Because the computer won't recognize the phone in ADB, I can't get anywhere in rumrunner and because I can't access the main screen after unlocking the screen, I can't even use sunshine.
I'm at a total loss and I don't have any money for another phone. I really need some advice to get this fixed so I can flash a baseband and/or RUU and get this thing working with ViperONE. Please halp!
- Charles
You need to flash a stock ruu with fastboot and the imei will restore .
To see if the imei is still in the partition but the software doesn´t recognize it go in fastboot mode and type fastboot getvar all and the imei should be there.