I have been passed a HTC Desire to try and fix after a friend of mine ran into issues trying to put Froyo on it. It was originally with Virgin (Virgin boot screen) but was not locked as other sims were usable.
I've tried various different methods to get it up and running but suspect something he has done with his attempts has caused serious issues - also he is not all that clued up and cannot remember exactly what he did - he did mention that RUU update failed, and also an image he had tried to flash from his sd card had got part way through and then locked up on the radio update.
With the original sim and memory card in, the phone will constantly reboot or just stick at the HTC logo. Take the memory and sim cards out, the phone will boot but system wont launch properly so cant get into settings to enable debugging so I can access the device via ADB. I can get to the fastboot screen, and to the Vol Down-Power screen on start, but if I select recovery it stays on HTC logo and goes nowhere.
I have managed to get HBOOT downgraded to 0.8, but when trying to put on original Virgin RUU it says the main version is older (probably because I'm trying to install an older version over a newer one). The stock Froyo RUU fails and tells me wrong HBOOT and sometimes gives a CID error. Although the phone is not locked, I suspect it will still need a goldcard, but cant create one as I cant get ADB access to the phone.
Sorry if this is a bit of a mess but at work and trying to take calls as well as write this and fix the darned phone. I;m not unfamiliar with methods used to get the phone rooted, but not well up on troubleshooting or working around these issues I have.
Any help would be appreciated.
You should be able to restore it by installing this RUU with a working goldcard:
http://shipped-roms.com/shipped/Bra...3.00.32U_5.09.00.20_release_140022_signed.exe
If you get a CID error your goldcard isn't working. There should be no version error with this.
Thanks for the reply....however how can I create a goldcard when I cant get the phone to a point where I can get my pc to recognise it? All the goldcard methods I have seen/tried involve having the usb plugged in and debugging enabled - cant get to that stage as phone wont boot - reboot loop most of the time and when I do occassionally get to the os it doesnt last, it will reboot after a few seconds. Anything else I could do? Or, could I use the card in other phone and create the goldcard in that and transfer over? I do have my own working Desire handset.
Don't know much about this but have read that a goldcard is unique to the SD card not the phone so you could create one on your phone and then use it in your mates. Also, from what I've read it would be worthwhile wiping your mates SD card (make sure he's not added a partition to it), copying a Rom to it, and try to install it using Rom manager (or whatever recovery program which was used to root the phone)
Ok, I used my own phone to sort out the goldcard and currently trying that out now...will keep you posted. Just started the RUU Stock Froyo and seems to have got further so far. Wish me luck!
Mmmmm....ok the RUU worked, but when it restarted (with original goldcard/memory card in, it kept rebooting. It did start once, got to initial setup then promptly rebooted. I swapped out the memory card (no sim in at all by the way at any point up to now) to my own card and after one final reboot it did start up. It doesnt seem stable at all with the original memory card, and still not entirely stable with my card. Could this be a phone fault? Im assuming if the RUU got through all its stages then all areas and files on the phone have been updated correctly and are all correct? Could past failures at updates etc have caused an issue elsewhere?
Have you wiped the various caches? As far as I can make out you need to make sure everything is wiped. I read a post on the OpenDesire thread which suggested that clockworkrom, if that is the recovery program you have installed, may not wipe one of the caches (possibly the dalvik cache) correctly. They recommended another recovery program called something like AmonRu. Although I can't really help you it might be worthwhile saying how the phone was rooted.
Ok, none of this was to root the phone. It was to debrand and put on the HTC Desire Froyo build. Not a custom rom, the standard RUU.
As far as I was aware, an RUU restore of the phone would wipe the appropiate caches, but correct me if I'm wrong. The phone now starts with the standard HTC startup and sound and for all intents and purposes is working, but just cant explain the random reboots. These seem to be worse with the 8GB card that my mate gave me with it. Although, after trying mine and putting the original one back in it seems to have stayed stable up to now. I'm beginning to wonder if there may be an issue with the memory card slot - another swap of the memory card again will probably trigger the reboots once more.
We will see how it goes anyway.
You've got a hardware fault. The RUU will completely reflash the phone, so if it flashed successfully but is still rebooting randomly, it can't be software.
Your probably right. Just started to try and do a downgrade, and after putting the PB99.IMG file on the gold card I made earlier, then starting the downgrade I noticed it stuck at about 98% on the radio update (second item in the list). I'm going to leave it a while to see if I get an error but I suspect it will not move or do anything.
Having gone through this process before on my own handset, I know it doesn't take anywhere near this long. Thing that confuses me though is that the RUU process I went through before went through with no issues - so why would that be able to successfully install a radio update and not this downgrade process? Anyone else had this happen to them?
Update: Ok, leaving this now as I've exhausted all avenues and its obvious the phone is not going to play ball. On another RUU flash it failed (and looking at the logs it was at the radio section and mentioned a partition update failure). A subsequent RUU flash was successful, so at least I've got it back to stock (although it doesnt stay booted long enough to even get the initial setup wizard done now). Passing it back to my friend tomorrow and hope he can get a warranty repair. Just a shame I couldn't get it back to the Virgin firmware. Thanks all those that helped anyway, much appreciated.
Related
i get a "can't connect to phone" error and a black screen with silver HTC letters on it on the screen of my phone when trying to flash the latest stock RUU. this is after the updater reboots the phone to try and flash.
i ran some root technique a couple days after i got my EVO (stood in line @ 5:30am to boot!). don't remember what it was though. toasts orig root i guess.
then it ran that sd card update (which didn't work for me). dunno if any of this matters, but wanted to provide back story.
why can't i flash??
Well depending on if you installed todays OTA update somehow changes my answer to your question.
For one if you did not install todays OTA update then the problem you are having is very commen and easily fixed. You'll notice that after it tells you there is no connection your phone should still be at the black screen with htc's logo. Without disconnecting or restarting your phone relaunch the RUU and go through it again. You should notice it will actually work the second time and eventually youll get a progress bar on your pc and eventually on the phone. This I am 90% certain should fix your problem. I've used the RUU numerous times and that has become standard procedure, although I don't understand why.
This will unroot your phone meaning you can then run unrooted or its now presentable if you have reason to take it in for replacement/warrenty issues.
But be warned! If you go back to stock in order to receive todays OTA update you will not be able to root your phone again using any current methods or files. Youll receive an error about the file being older than the new and wont be able to even partial root let alone get nand access.
On my end I unrooted today to test out the new features knowing full well I wouldn't be able to root again with the update installed. I figured I'd be able to use the RUU like you are because when it unroots a phone it takes it back to the default software from the day the phone was release but it was my luck that for whatever reason this new update effs up trying to use the RUU.
Is there a way to restore to factory settings that won't have the update installed or is it like how the 3GS was and once you upgrade thats it
Try flashing directly from the sd card, link is in my sig '(un)root'
-------------------------------------
Sent from my god phone.
aaaahhh. there it goes. thanks.
actually it was more i was having sd-card issues still. kept unmounting. rather happy w/ how the EVO works for now so rooting/modding isn't a priority. figured i'd reflash to see if it fixed the sd issue.
thanks!
Hello All,
My wife just recieved a refurbished phone through best buy. I tried to root her phone with unrevoked. When i went through with the process i got a error code through unreoked about firmware being too new. So after reading around I found out that it has the OTA FW and cannot be rooted yet. So after the root failed I cleared the storage on the phone. So now everytime she uses the phone it begins to boot loop when she begins to make a call. This is not my first time rooting I have done this plenty of times. Any Ideas?
Sounds like you've done what you can with the phone. Without s-off you cant flash the custom recovery to get more access to the file system so you're fairly stuck. You might try going into the phone settings and doing a full restore, just save any pics and whatnot she may have taken onto a computer so you can wipe the sd card for good measure as well. If that doesn't fix it then just take it to BB and tell them the refurb isn't working.
ok i will try erasing everything first and see what happens
How did everything work out?
A colleague of mine has an incredible that every few days reboots into a continuous boot loop. It takes removing the battery for it to boot normally, and then a few days later it does it again.
He has tried a reset, and it doesn't fix the problem. This is an unhacked unrooted stock Incredible with what ever updates came from Verizon/HTC over the air.
I'm wondering if it would help to reflash it to virgin stock in case something is corrupted. In fact its also possible that one of the HTC updates caused the problems, since it seems to have started about the time of an update.
I have a Samsung phone and am familiar with the procedure for Samsung (Kies, Odin, etc) but don't know what to tell him about HTC.
What is the procedure for reflashing to stock, and perhaps selecting a stock version older than the latest for HTC phones?
kmandel said:
A colleague of mine has an incredible that every few days reboots into a continuous boot loop. It takes removing the battery for it to boot normally, and then a few days later it does it again.
He has tried a reset, and it doesn't fix the problem. This is an unhacked unrooted stock Incredible with what ever updates came from Verizon/HTC over the air.
I'm wondering if it would help to reflash it to virgin stock in case something is corrupted. In fact its also possible that one of the HTC updates caused the problems, since it seems to have started about the time of an update.
I have a Samsung phone and am familiar with the procedure for Samsung (Kies, Odin, etc) but don't know what to tell him about HTC.
What is the procedure for reflashing to stock, and perhaps selecting a stock version older than the latest for HTC phones?
Click to expand...
Click to collapse
You can reflash the phone to stock with what incredible users call an ruu (rom update utility), however flashing older versions or downgrading the os is not allowed with s-on (security on). His best bet in my opinion would be to root and s-off the phone, and then flash a custom rom. However if hes not into all of that he can try to do an ruu and see if it fixes things. Doing so will wipe the phone compleetly and he will loose all of his apps and data. A pc running windows xp or newer is required.
1. Download the ruu http://dinc.does-it.net/Stock_Image...0_Incredible_C_hboot_1.02.0000_4.08.605.2.exe, and place it somewhere on your pc.
2. Download and install HTC Sync http://dinc.does-it.net/HTC-Sync/3.0.5606/setup_3.0.5606.exe.
3. On the phone go to menu - settings - applications, uncheck fastboot if it is checked and then select development, and make sure usb debugging is checked.
4. Connect the phone to the pc with the usb cable, and wait for any drivers to install on the pc. The phone should be in charge only mode.
5. On the pc run the ruu file and follow the instructions it gives you.
If all goes well the phone will be like it just came from the factory. If doing all of this is to technical for him he can take it into a verizon store and they will do it for him at little or no charge.
cmlusco said:
If all goes well the phone will be like it just came from the factory. If doing all of this is to technical for him he can take it into a verizon store and they will do it for him at little or no charge.
Click to expand...
Click to collapse
Well not like it came from the factory originally. That would be Froyo, and this procedure would presumably get the last official (and maybe problem some Gingerbread). Is that right?
Also, I'm surprised to hear that a Verizon store could do a flash. My only experience is with T-mobile and they can't do any better than use the "factory reset" menu that just clears settings.
kmandel said:
Well not like it came from the factory originally. That would be Froyo, and this procedure would presumably get the last official (and maybe problem some Gingerbread). Is that right?
Also, I'm surprised to hear that a Verizon store could do a flash. My only experience is with T-mobile and they can't do any better than use the "factory reset" menu that just clears settings.
Click to expand...
Click to collapse
Well not like it originally came from the factory 2 years ago (with froyo), but if they were still selling them today or you get a replacement, that is how it would come from the factory. The last update 4.08.605.2 fixed all the major issues and shouldnt give any major trouble. The only other option would be to root.
Verizion is pretty good with customer service, you may have to find a knowledgable employee but they can do it for you.
We tried the "ruu" approach without success. The drivers installed on the PC, the phone goes into debug mode, and we can even run "adb" manually and talk to the phone. However, when either "ruu" or "Ht Sync" try to talk to the phone they just say the phone is not connected.
If we run the task manager on windows we can actually see "ruu" invoking "adb" and there is no long timeout. It appears that ruu just doesn't like the answers.
Again running adb manually for example with the shell option seems to do all you expect adb to do. This is with both the versions linked above and the updates they end up offering.
Any ideas?
OK, found a mistake. I didn't realize that to do the ruu flash I needed to turn off the phone and vol-down/power it into htboot mode.
With that done the update program sees the phone notices it has lastest firmware and offers to update it to the same version. I say yes, and the phone reboots and the PC tells me it will take 10 minutes to flash, then 2 seconds later tells me it succeeded and the phone reboots.
Obviously it did not flash anything. Am I missing something?
Also any pointers on how to flash an earlier stock rom (and where to find it)?
Hey guys,
First off, I've searched far and wide for any help with my problem but it is such a peculiar situation that I have yet to find someone with a similar situation. I expect if I want to ever use my M8 again, I'll need to send it to HTC and pay a few hundred bucks to fix it. But maybe someone here will have an idea that I've missed.
Shortly after getting my M8, I unlocked my device, rooted it and installed a few roms. Everything was fine save for one major thing: no matter which PC I used (and I used MANY - 3 different windows destops, a windows desktop at the office and my Macbook Pro) the device was never able to mount and make the storage accessible. I knew at that point something at some point had gone wrong. I've long preferred to use a wireless file transfer app to send stuff to and from my phone so I wouldn't have to break out all my cables so I figured it wouldn't be a big deal. I'd make it work.
A few days ago, I decided to try a different rom than what I'd been using for months (HD Revolution - great rom!) and downloaded everything required. I booted to TWRP, wiped the usual stuff and flashed my rom. When I rebooted, I was continually met with a crash as soon as the phone started and was never able to get into the OS. No big deal - this has happened before with other devices, so I didn't sweat it. I simply powered down the phone and tried to get back to recovery. Here's where the problem really kicked in : when attempting to boot to recovery, my phone will bring up the Hboot screen but instantly try to select the first option, thus not allowing me to scroll down to "Recovery". No matter what I do, it brings up the white Hboot screen, automatically selects the first option, gives me some error (I'm at work so I don't have the device in front of me) and tries to boot to the OS. That takes us back to the automatic crash.
Now, I know usually the solution would involve USB and ADB, but like I mentioned at the start of my sad tale, connecting my phone to PC's results either in nothing (Mac) or a "the device has failed" message in Windows. I've tried removing all the phone drivers, reinstalling and using a few toolkit methods - the phone is just never ever detected.
So, that's it. I'm pretty much resigned to sending my phone in and the HTC folks quoted me about $200. I do have a functional phone at the moment so it isn't the worst situation in the world, but if I could fix this I'd be able to using it as my main device again or sell it for a good chunk of change - I just bought it in June.
Sorry for the long read!
As far as the storage issue, never seen that happen before so I'm not sure. When you plug it in to the computer does the phone ask if you want to connect it as a storage device etc?
The bootloader is a very peculiar problem. It almost sounds like you have an img file that its trying to read as soon as you boot into boot loader.
Try to install HTC sync. And make sure the computer has an internet connection when you plug it in via usb.
Try to flash stock recovery fw buddy
Maybe thats problem RUU
Cek mike blg to find all stock recovery fw
After that install custom recovery again
This sounds a little familiar.
In my experience I've found some firmware versions and ROMs very choppy.
I once had a problem with storage too, couldn't send anything over to my phone.
Fortunately I could access recovery, so used ADB sideload and installed another ROM. And went to another firmware and never looked back.
The last 401.6 firmware gave me all sorts of issue.
If you can access fastboot I'd also recommend new firmware 401.7 is working flawlessly for me with ARHD 21.
Sent from my HTC One_M8 using XDA Free mobile app
I would try putting one of the bootable ruus on your SD card so when it goes to your hboot, it'll read the RUU and install it
Awesome, some interesting suggestions here. Would I be able to somehow update the firmware via an SD card without any input from a computer? I managed to get into Recovery last night somehow (maybe letting the battery totally drain and charging it for a while did something) but plugging in my phone when in recovery still won't mount the storage or be recognized by ADB. Would I somehow be able update my firmware from recovery without the need of ADB'ing from my desktop? I've been looking at ROM threads and stuff and noticed that almost every rom requires new firmware or WiFI/radios other stuff won't work....
I'm at work right now so I'll definitely research this in depth when I get home, but if you guys could guide me in the right direction, I'd really appreciate it and maybe buy ya' a beer.
Xavierc123 said:
Awesome, some interesting suggestions here. Would I be able to somehow update the firmware via an SD card without any input from a computer? I managed to get into Recovery last night somehow (maybe letting the battery totally drain and charging it for a while did something) but plugging in my phone when in recovery still won't mount the storage or be recognized by ADB. Would I somehow be able update my firmware from recovery without the need of ADB'ing from my desktop? I've been looking at ROM threads and stuff and noticed that almost every rom requires new firmware or WiFI/radios other stuff won't work....
I'm at work right now so I'll definitely research this in depth when I get home, but if you guys could guide me in the right direction, I'd really appreciate it and maybe buy ya' a beer.
Click to expand...
Click to collapse
Download a rom that can use the 2.xx firmware. Look around and you should be able to find the roms. There's still plenty out there. Here's a little suggestion, reflash TWRP (or other recovery) through fastboot than grab a SD card and place the rom into the SD card and install the rom using through the use of a SD card. Just remember to do a full wipe before that
Hi, total noob to Android hacking and rooting here...
I'm in the US and have the HTC Desire 816 (710c) on Virgin Mobile. Really wishing I'd done better research about the Desire 816 and VM before buying this phone. It's a great phone except for the small HD. I didn't realize just how many headaches that small HD--and Virgin's tight-fisted grip regarding their unlock policy--would cause me!
Forgive the length of this, but I'm hoping more detail as to what I've done/tried will help find the right solution...
I was doing fine on KitKat and for some reason decided I wanted to upgrade to Lollipop--mistake number 1! I first installed the update over KitKat but had some issues. Nothing major, but I figured something was definitely wonky when I noticed the basic stock web browser was gone--not that I really use it, just wanted to test something with it. (I was having an issue in Habit Browser, didn't realize 'til later that it was because I had my download folder setting on external SD card. While that worked in KK, it didn't in LP.) So, I did a backup...or THOUGHT I did. HTC Backup app was supposed to have been backing up my phone every day to Drive...turns out, it wasn't, despite notifications that it was working. So, anyway... I went ahead and factory reset the phone and reinstalled Lollipop. UGH! An even bigger mistake. Over 6 GB of the HD gone, just from stock LP!
Then I thought maybe if I unlocked the phone, I could delete most of the junk, even still using the stock OS. I followed the directions on HTCDev and although the proper screen appeared on the phone and asked me if I wanted to unlock, and I replied yes, it didn't work at first. The phone rebooted and everything was the same. Reboot checker confirmed failure.
So, as I was ready to try to narrow down my list of previously installed apps to absolute essentials due to the reduced disk space, I thought to see if there was a a way to revert to KitKat. I followed the instructions here http://forum.xda-developers.com/desire-816/general/ruu-t2952058. I tried the RUU .exe first. It failed, telling me I needed to get the correct RUU and try again. However, HTC's website does NOT show any KK downloads for Virgin Mobile USA for this device. More on that in a moment...
I also tried the flashing via SD card method. It also failed. I thought, what the heck, I'll try steps 3 and 4 of the SD card method, flashing the stock recovery and lock the bootloader, even though I thought my device was locked. Well, I guess I didn't notice when I went into fastboot that the device indeed HAD at some point unlocked, after all.
After those steps, I now had the following show up:
*** Software Status: Modified ***
*** RELOCKED ***
SECURITY ALERT!
I tried flashing the ROM.zip from SD card method again. It failed spectacularly, saying something about about a large file (some of the text was beyond the edges of the screen, so I couldn't read all of it. There was also an instruction to press power to reboot. The phone went back into fast boot screen with red highlighted "!! Image Update FAIL !!" Mind you, this was with the SD card now removed. I did manage to get the phone to boot normally again, back to stock Lollipop.
Now I thought I would try flashing the WWE KK download from HTCDev. Well, I didn't get the large image fail message, but it did fail saying that it was not the right image.
I tried unlocking the phone again, via the instructions at HTCDev. Didn't work. Thought I would try the ROM.zip file from the thread here at XDA one more time. Same fail message as before, same behavior of phone getting stuck on flashboot screen with red error message on initial attempt to reboot the device. I do notice now that although phone status is still modified and relocked, the security alert message is gone.
Can anyone help? I just want KitKat back so I can reload all my previous apps! (or possibly a good KK equivalent non-stock ROM, once I get the phone unlocked again? I have no idea which one though, being a noob :/ )
Thanks!
witchywoman said:
So, as I was ready to try to narrow down my list of previously installed apps to absolute essentials due to the reduced disk space, I thought to see if there was a a way to revert to KitKat. I followed the instructions here http://forum.xda-developers.com/desire-816/general/ruu-t2952058. I tried the RUU .exe first. It failed, telling me I needed to get the correct RUU and try again. However, HTC's website does NOT show any KK downloads for Virgin Mobile USA for this device. More on that in a moment...
Click to expand...
Click to collapse
That ruu file should work it's the vm usa last kitkat version. You need to follow the directions unroot and relock phone. But depending on what you did to the phone that was non standard you might also need to wipe or format internal data before running the ruu.
I think you can:
1) unroot then boot into recovery(twrp)
2) wipe phone/format data.
3) Boot directly from twrp to bootloader so you can get to fastboot usb.
4) Flash stock recovery from your PC.
5) Relock bootloader then run the ruu.exe.
All the other stuff you did afterwards should not be necessary.
pcjunky: The phone is currently relocked. I'm not 100% sure about unrooted, but I think it is. Like I said, when it was unlocked before I didn't even realize it, and I didn't really do anything unusual with it. The phone still had stock Lollipop on it and I just changed some stock settings and preferences.
Also, as I said, I am a total noob. I don't know what you mean about twrp and booting into that to wipe the drive and then from that. I'm sure there is info about that on this site somewhere, but it might be quicker if you (or someone) could explain it briefly, or point me in the right direction.
Updating to answer my own question in this reply. You're telling me to use a custom recovery but I never installed one. So.... currently searching to see how to do that.
I don't know if it's worth you time to learn how to go back to Kitkat. There should be howto's in the general forum for most everything you need. But I think the free memory difference between Kitkat and Lollipop is almost 1GB. 4.04GB free versus 3.14GB free. If you make sure all your apps that support being moved to SD card are moved and your storage settings for supported items uses the SD card you might be able to save enough space to get by until you decide to switch phones.
Twrp is a custom recovery and backup/restore tool you can do a search to learn about it, but you might not need it. The HTC backup is OS specific and it only saves apps and data not system files. So your HTC backup under Kitkat won't restore over Lollipop. If you had installed Twrp and and made a backup of Kitkat before you installed Lollipop you could restore your kitkat backup over Lollipop.
If you still want to try to get back to kitkat you can try to reset your phone(In theory relocking your phone should do that but it wont hurt) before you run the ruu file.
pcjunky said:
I don't know if it's worth you time to learn how to go back to Kitkat. There should be howto's in the general forum for most everything you need. But I think the free memory difference between Kitkat and Lollipop is almost 1GB. 4.04GB free versus 3.14GB free.
Click to expand...
Click to collapse
Well, it's interesting to note that my phone used ~ 4.8 GB when it was new with KK installed. After the Lollipop upgrade, it was using well over 6 GB with just the stock OS, HTC apps and Virgin apps on it. Obviously, that was unacceptable, and it's what got me started on this whole quest. :silly: However, after flashing a custom recover image, rather than the stock recovery I used previously, the stock installation is using 4.97 GB, so I think I should be good to go with that.
If you make sure all your apps that support being moved to SD card are moved and your storage settings for supported items uses the SD card you might be able to save enough space to get by until you decide to switch phones.
Click to expand...
Click to collapse
I always have used the SD card as much as was supported. Switching phones is not an option for me as I have a rather limited income and the Desire was an investment. Thus another reason I embarked on trying to make these changes.
Twrp is a custom recovery and backup/restore tool you can do a search to learn about it, but you might not need it. The HTC backup is OS specific and it only saves apps and data not system files. So your HTC backup under Kitkat won't restore over Lollipop. If you had installed Twrp and and made a backup of Kitkat before you installed Lollipop you could restore your kitkat backup over Lollipop.
If you still want to try to get back to kitkat you can try to reset your phone(In theory relocking your phone should do that but it wont hurt) before you run the ruu file.
Click to expand...
Click to collapse
Well, as I said above, the stock/OME installation now, before uninstalling whatever junk it will let me, is using only 4.97 GB, so I should be fine with that.
Thanks for your efforts to help me out with this. :good:
I'm glad you got it to a workable point. It's possible to go back to Kitkat, but I personally wouldn't do it because it gives you better battery life.
From time to time you should check apps under settings and swipe left to see the apps on sd card. Sometimes new app updates will support being moved to sd card or an updated version of an app will need to be moved over to the sd card.