Related
Hi guys,
I own a Fastweb branded desire and back key isn't working anymore.
So I'm tring to restore the branded official rom for warranty.
I got s-off and root and my gold card is in.
I've flashed the old modaco r6 rom to avoid main version is older and flashed downgrade hboot(alpharev) too.
When I start the ruu hboot 0.75 and old radio are flashed properly, but I still have custom splash and cwm recovery also system is untouched.
Ruu stops with error 140 bootloader problem.
I'm still able to flash custom roms and I can s-off again, but I really don't know what to do.
Any help?
Thanks.
Best regards.
Jus
You're in the wrong section dude, read the rules.. all questions go to q&a section
This sections is set aside for development only
Sent from my HTC Desire using XDA App
Sorry mate, is there a way to change section?
jussy,
I had exactly the same problem so I'll answer even tho this is the wrong thread. You have to start first by extracting the zip file from the RUU. Run the RUU until it gets to the first screen then leave it there (don't close it).
Go to Start -> Run and type %temp%.
Find the temporary folder folder that's just been created (sort based on date) and find a file called 'rom.zip'. Copy this file into another location and close the RUU.
FreshNClean said:
jussy,
I had exactly the same problem so I'll answer even tho this is the wrong thread. You have to start first by extracting the zip file from the RUU. Run the RUU until it gets to the first screen then leave it there (don't close it).
Go to Start -> Run and type %temp%.
Find the temporary folder folder that's just been created (sort based on date) and find a file called 'rom.zip'. Copy this file into another location and close the RUU.
Click to expand...
Click to collapse
Thanks for replay.
I've extracted rom.zip and renamed to PB99IMG.zip. tried to flash it in fastboot.
Flash process start but stops before finishing leave me in the same situation as before. If I want to flash it again gives me main version is older.
I've s-off it 10 times today and made many try.
EDIT: I've also tried to flash via fastboot commander the .img files in rom.zip but after that I could only access fastboot.
Now I've flash a generic ruu to make it boot.
Tbh mate I'm not sure how to change it lol.. mayb delete and repost in q&a..
Just beware of flames coming your way lol
Sent from my HTC Desire using XDA App
jussy said:
Thanks for replay.
I've extracted rom.zip and renamed to PB99IMG.zip. tried to flash it in fastboot.
Flash process start but stops before finishing leave me in the same situation as before. If I want to flash it again gives me main version is older.
I've s-off it 10 times today and made many try.
EDIT: I've also tried to flash via fastboot commander the .img files in rom.zip but after that I could only access fastboot.
Now I've flash a generic ruu to make it boot.
Click to expand...
Click to collapse
Dude, don't flash the zip, just put it in the root of your SD, then switch phone off, hold vol down button and reboot into recovery, your phone will recognize the pb99img.zip and some options should come up. Follow the on screen instructions and you should be unrooted in 15 mins max.
Traced from a Reflex S Desire
3f1f37 said:
Dude, don't flash the zip, just put it in the root of your SD, then switch phone off, hold vol down button and reboot into recovery, your phone will recognize the pb99img.zip and some options should come up. Follow the on screen instructions and you should be unrooted in 15 mins max.
Traced from a Reflex S Desire
Click to expand...
Click to collapse
Sorry for my bad english but what you said is what I've done.
1-root and s-off.
2-flash downgrade hboot(alpharev).
3-put PB99IMG.zip (extract as said from my branded ruu) on sd card root.
4-boot power + vol down.
5-It starts, step 1 goes well then at the end of step 2 screen became black and came back with 0.75 hboot s-on and if I try again it gives me main version is older.
So I can only reboot, reflash a rom and s-off it again.
Never ending loop...
Thanks anyway.
You are using wrong RUU.use the RUU with 5.11.05.27 , I am on mobile so can't give you the exect link.I will post it tomorrow for you, if you can't find.
And it is better to create a goldcard if you havent yet
Sent from my HTC Desire using Tapatalk
jhonybravo4u said:
You are using wrong RUU.use the RUU with 5.11.05.27 , I am on mobile so can't give you the exect link.I will post it tomorrow for you, if you can't find.
And it is better to create a goldcard if you havent yet
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
I've got my gold card already in.
Sadly there's only one ruu for my carrier.
I can flash a generic froyo ruu but it's not good for warranty.
I can't really help in terms of your issue.
If I remember right, I booted into the bootloader and switched on fastboot, then ran the RUU EXE making sure my phone was connected to my pc.
It eventually came right.
Saying that, after I got the stock ROM back on, my phone went ape (and to this day I have no idea why). Random restarts. Freezing. It was crazy. I had to upgrade the RUU for it to stay on properly. Was really weird.
There are so many threads about rooting for warrantee purposes, perhaps search them or go through thier instructions, cause I'm sure someone may have had the same issue.
Wish I could help you though.
mr_norris said:
I can't really help in terms of your issue.
If I remember right, I booted into the bootloader and switched on fastboot, then ran the RUU EXE making sure my phone was connected to my pc.
It eventually came right.
Saying that, after I got the stock ROM back on, my phone went ape (and to this day I have no idea why). Random restarts. Freezing. It was crazy. I had to upgrade the RUU for it to stay on properly. Was really weird.
There are so many threads about rooting for warrantee purposes, perhaps search them or go through thier instructions, cause I'm sure someone may have had the same issue.
Wish I could help you though.
Click to expand...
Click to collapse
It seems you didn't got the problem.
Thanks anyway.
I did it!!!!
Thanks to this guide http://forum.xda-developers.com/showthread.php?t=821809
and all of you.
So many thanks.
Sorry guys I got an other problem...
Now this is the second time I bring it to assistence (last time was for vol down) and when they give it back to me it was updated to froyo.
I'm facing problem with 1.15=>1.21 OTA, installation is aborted due to status 7 (if some one can help I'll post the full error message).
Unfortunetly the ruu I've used is the only one from my carrier.
Will they know that my phone was updated by them and I'll lose my warranty?
Any idea about fixing status 7?
Many thanks.
Best regads,
Jussy
I have a unique problem, and I think I will need someone with some patience to help if its even possible to get my phone back to stock. Recently my EVO screen backlight completely stopped working yet when I turn on the phone I know that it still boots up because i still get notification sounds and alarms and in direct sunlight i can still use the phone. My phone has a custom flash screen unrevoked, and it has an old stock rom 3.70 and hboot 2.10 with custom boot animation not to mention a custom kernal. What I need to know, is it possible to do a push or something to flash the radio to s-on and reset it all back to "stock"? I only have until 8-18-2011 to return my phone to sprint and to
get this done so please someone that knows what they are doing please reply. Thank you so much in advance. I have tried to flash the unrevoked s-on tool but it does not work with hboot 2.10 it seems and there must not be a recovery cause I get the triangle ! when i try to goto it. Please help!
Is your screen blank the entire time, from when you first turn on the phone? If so, then it is a hardware problem and I don't think Sprint will know the difference anyway until they've taken it apart and repaired it, and you'll have shiny new refurb by that time. But, still, if the phone really is booting up, it might be possible to run an RUU (the latest one) if you have usb debugging enabled already, or to flash a stock image. However, neither of those things will set the phone back to S-On. You would have to blindly go into the recovery and flash the S-On tool, which would be really hard. And I don't think it's necessary. I'll post some links to the RUU and/or PC36IMG instructions in a minute, but if you do some searching, you can find them.
Edit: Here's the link to a number of RUU's and PC36IMG files to flash back to stock. I would use the 3.70 version, because the 4.24 version installs an hboot which is locked down (although you would still have s-off). The RUU needs to be run with the HTC drivers installed, USB debugging on, and the phone actually booted up and running and connected to your computer. The PC36IMG file would need to be placed on the root of the SD card and named PC36IMG.zip. The bootloader would automatically recognize that file and after about 1-2 minutes of checking it, it would give you the option to hit volume-up to start the update (even though you can't see it). Good luck...
http://forum.xda-developers.com/showthread.php?t=884060
soldierforchrist2 said:
Is your screen blank the entire time, from when you first turn on the phone? If so, then it is a hardware problem and I don't think Sprint will know the difference anyway until they've taken it apart and repaired it, and you'll have shiny new refurb by that time. But, still, if the phone really is booting up, it might be possible to run an RUU (the latest one) if you have usb debugging enabled already, or to flash a stock image. However, neither of those things will set the phone back to S-On. You would have to blindly go into the recovery and flash the S-On tool, which would be really hard. And I don't think it's necessary. I'll post some links to the RUU and/or PC36IMG instructions in a minute, but if you do some searching, you can find them.
Click to expand...
Click to collapse
Yes the screen is just black when you turn it on, yet the phone will still vibrate and gives sound notifications of texts/email/alarms ect. I know the RUU will flash the rom back to stock but will flashing the latest RUU replace my kernal or is it possible to put that back to stock and what can i do about the splash screen/boot animation? Thank you for your time in this matter. I just want to do everything that is possible to get it back to stock before I send it off to avoid getting charged for my refurb.
z143 said:
Yes the screen is just black when you turn it on, yet the phone will still vibrate and gives sound notifications of texts/email/alarms ect. I know the RUU will flash the rom back to stock but will flashing the latest RUU replace my kernal or is it possible to put that back to stock and what can i do about the splash screen/boot animation? Thank you for your time in this matter. I just want to do everything that is possible to get it back to stock before I send it off to avoid getting charged for my refurb.
Click to expand...
Click to collapse
I understand. I don't know all of that for sure, but I'm pretty sure the RUU will replace your ROM, splash screen/boot animation, radio, hboot, recovery, etc. It wipes everything out and sets it back to stock. I think the only thing it won't do is set it back to S-ON. If you know what kind of recovery you have and how to use it, you can try to blindly flash the S-On tool from Unrevoked.... But I really don't think Sprint will know the difference, or even care when your screen is totally shot.
Edit: If you really really want to try to flash the S-On tool, do that first before you run the RUU. It will wipe out your custom recovery.
soldierforchrist2 said:
I understand. I don't know all of that for sure, but I'm pretty sure the RUU will replace your ROM, splash screen/boot animation, radio, hboot, recovery, etc. It wipes everything out and sets it back to stock. I think the only thing it won't do is set it back to S-ON. If you know what kind of recovery you have and how to use it, you can try to blindly flash the S-On tool from Unrevoked.... But I really don't think Sprint will know the difference, or even care when your screen is totally shot.
Edit: If you really really want to try to flash the S-On tool, do that first before you run the RUU. It will wipe out your custom recovery.
Click to expand...
Click to collapse
I have been looking for a video that might show me how to flash the s-on tool with clockworkmod 3.0.0.5 so i can try and follow the video blindly before i flash the RUU. Would you happen to know of a video that I can follow along with to maybe get s-on back? I would rather try and do it blindly than just sending it in.
z143 said:
I have been looking for a video that might show me how to flash the s-on tool with clockworkmod 3.0.0.5 so i can try and follow the video blindly before i flash the RUU. Would you happen to know of a video that I can follow along with to maybe get s-on back? I would rather try and do it blindly than just sending it in.
Click to expand...
Click to collapse
Makes sense. I don't know of a video off hand but I bet it's out there. I'll help you look. The hardest part is going to be finding the s-on zip on the SD card blindly. I think you can name it "update.zip" and select the option "flash update.zip".
http://www.youtube.com/watch?v=RyulgnaVW_w
Not the best video, but I think it will show you how to get there. You would need to select "apply update from sd card" instead of choose zip from sd card like they did. Pay careful attention to the parts that say "no, no, no.... yes - .... no, no" I don't know for sure if it's the same on every phone and version . Hopefully it is. You might find a better video, but this is the best I can do for you.
I'm not 100% sure what happens after you press "apply update from sd card" I think it will give you the "no no no... yes... no no no" option again.
Actually, I just realized something. Since there are videos that show you specifically how to flash an arbitrarily named zip file. You could just wipe your SD card clean and put the zip on there so that it is the only thing on the card. That might work too...
So, that being said. Here's a much better video that will show you how to flash the S-On tool. Hope this works for you.
http://www.youtube.com/watch?v=guHo_FbSy8Y
ok so i wanted to get a custom rom my desire hd 2.3.5
at start i have tryed the old way thats in the sticky but that was for 2.3.4 so that didnt work.
what did work was unlocking the bootloader via htc dev site. after that i was clueless.
I've found AAK to root my phone and downgrade so i had used that, but i forgot that the phone was unlocked and it said it had to be locked.
and now the phone is bricked i've tried all possible ways with wiping data and cache but it doesnt work.
i wanted to relock the bootloader with fastboot.
i had entered this command:
fastboot oem lock
but that gave this error
FAILED (status malformed (1 bytes))
so my phone hangs on the boot screen and i cant do anything?
can you guys please help me?
The fact you can get to the bootloader is a great sign, so don't worry! The only time you need to properly panic is when you can't get anything on the screen or even a charge light.
---Double check with someone else that this is correct, but I think this is what you need to do ---
Do you have a custom recovery (i.e clockworkmod)? Can you boot into recovery? Use the volume keys to select recovery, then press the power button. If you get options like "reboot now" and "install zip from sd card" then flash a rom like Android Revolution HD.
If you get a red triangle, find a zip you want to flash and name it "PD98IMG.zip" then put it on the root of the SD card. Reboot to bootloader and it should flash.
If you truly want to relock the bootloader, flash an RUU and it will restore you to stock.
Tamen said:
If you get a red triangle, find a zip you want to flash and name it "PD98IMG.zip" then put it on the root of the SD card. Reboot to bootloader and it should flash.
If you truly want to relock the bootloader, flash an RUU and it will restore you to stock.
Click to expand...
Click to collapse
Simply renaming a ROM PD98IMG.zip wont work it needs to be formatted in a certain way, but if the phone is S-OFF, which wasn't mentioned there are certainly PD98IMG's about for a variety of ROMs. But I suspect Tamens suggestion of flashing the appropriate RUU and starting from scratch is going to be quickest way to get sorted
I had this same problem with mine it got stuck trying to boot up but I had no boot loader or I couldn't get into recovery.so download a took called ANDROID FLASHER and reflash the radio ect.my desire hd is now fine.
Sent from my HTC Sensation XL with Beats Audio X315e using XDA App
well i have tried to flash the ruu but without succes.
ive loaded the PD98IMG.zip on the sd and let the bootloader use it. nothing happened.
also my phone is s-on and could not find a way to go to s-off in recovery mode or boatloader.
Down load the tool above Android flasher.from the tool u can enable fast boot ect from your PC and loads of other stuff.it is a very simple to use and it has loads of folders for recovery, boot loader ect let it do every thing for u.that was the only thing that worked for me
Sent from my HTC Sensation XL
I've tried it but it doesn't work because my phone is s-on...
the description of that utility said that s-off is essential
i am really running out of options..
in short my phone has a unlocked bootloader and after that i've used AAK.
the result is bricked phone with s-on and unlocked bootloader
Hi all. Have not been to this site in a while.
I have an 8181 Desire (Australia - Telstra). Presently running CM7 and Runnymede ROM, with 4EXT recovery.
Before I go too far...yes, I know I should use SEARCH, but honestly I have forgotten so much about modding, I really have no idea what I'm doing anymore...
I want to return to stock and pass the phone on to a friend. I have so far installed Telstra RUU to my PC and I have run Alpharev downgrade. I have now moved to reboot and run the RUU, but I keep booting straight to Bootloader screen, not progressing to main screen. I know this means I have missed a step or forgotten something, but have nfi what that might have been.
I never really learned to flash with Fastboot, so am I able to avoid that and continue the way I am a little more familiar with?
Thanks heaps for any help. In the meantime I will continue to SEARCH and see what I can see. Cheers.
Use the troubleshooting guide stickied to the top of q&a
Search for and then run the 2.3.3 GB RUU
I've found the 2.3.3 GB Telstra RUU and renamed to PB99IMG.zip, placed on SD card. I see a blue progress bar and then "would you like to reboot now?" Each time I reboot, I am straight back to Bootloader screen (not stuck in bootloop, as such).
Working my way thru the TS Guide, but I'm pretty sure I have missed a step or forgotten something along the way... Wondering if phone won't boot properly because I am now running the Downgrade HBoot, which is obviously not compatible with Runnymede.
Am I able to uninstall 4EXT touch? Would like to simplify things as much as I can and would be happy with standard CWM for flashing purposes...
Will keep playing today. I know the phone isn't bricked, so I'm not panicking. Yet.
Try flashing the stock hboot, then RUU
Currently if only flashed the downgrade.img, it's just in a blank state with no actual hboot I believe.
(Make sure you're flashing these hboots thru fastboot, not recovery)
777ace said:
I've found the 2.3.3 GB Telstra RUU and renamed to PB99IMG.zip, placed on SD card. I see a blue progress bar and then "would you like to reboot now?" Each time I reboot, I am straight back to Bootloader screen (not stuck in bootloop, as such).
Working my way thru the TS Guide, but I'm pretty sure I have missed a step or forgotten something along the way... Wondering if phone won't boot properly because I am now running the Downgrade HBoot, which is obviously not compatible with Runnymede.
Am I able to uninstall 4EXT touch? Would like to simplify things as much as I can and would be happy with standard CWM for flashing purposes...
Will keep playing today. I know the phone isn't bricked, so I'm not panicking. Yet.
Click to expand...
Click to collapse
Dont rename the ruu to PB99IMG... It wont work as u found out. So.... On ur pc, run the ruu.exe file that u downloaded, then (if using windows) when it gets to the screen with pic of phone asking to axcept stuff, click start on ur computer, then in search box type "run" then click on run then in that search box type %temp% and search then find the first or second newest folder there will be a file there called rom.zip... Rename that to PB99IMG then put it on the root of ur sdcard and boot into bootloader
---------- Post added at 02:24 AM ---------- Previous post was at 02:22 AM ----------
eddiehk6 said:
Try flashing the stock hboot, then RUU
Currently if only flashed the downgrade.img, it's just in a blank state with no actual hboot I believe.
(Make sure you're flashing these hboots thru fastboot, not recovery)
Click to expand...
Click to collapse
I was typing as u were posting
jmcclue said:
Dont rename the ruu to PB99IMG... It wont work as u found out. So.... On ur pc, run the ruu.exe file that u downloaded, then (if using windows) when it gets to the screen with pic of phone asking to axcept stuff, click start on ur computer, then in search box type "run" then click on run then in that search box type %temp% and search then find the first or second newest folder there will be a file there called rom.zip... Rename that to PB99IMG then put it on the root of ur sdcard and boot into bootloader
---------- Post added at 02:24 AM ---------- Previous post was at 02:22 AM ----------
I was typing as u were posting
Click to expand...
Click to collapse
Nice! Thank you!! I was following the TS Guide and couldn't figure why I couldn't find that rom.zip file... Now I get it.
A bit busy for a while, but will try again as soon as I get home and report back.
Cheers.
777ace said:
Nice! Thank you!! I was following the TS Guide and couldn't figure why I couldn't find that rom.zip file... Now I get it.
A bit busy for a while, but will try again as soon as I get home and report back.
Cheers.
Click to expand...
Click to collapse
If u get stuck just google search "how to extract rom.zip from ruu xda" im sure ul get a few guides.
Well, as it happened, impatience got the better of me and I did find the rom.zip and placed onto SD. Update worked fine, but now stuck at Telstra splash screen.
I really do have to head out, but I'll check back again later on.
Would having the SD card partitioned to SD-Ext/FAT32 effect the operation??
Thanks again for the help, feeling like a real n00b here!
Partition won't affect it. RUU doesn't see or care about it
Have you flashed stock hboot yet? It should say alpharev stock in the top of the bootloader screen.
If that RUU won't work, find the 2.3.3 WWE GB RUU
I have --- AlphaRev --- at top of screen. Definitely have flashed stock HBoot.
Just flashing WWE RUU now. I notice in the tutes I've found I should be seeing
Parsing...[SD ZIP]
[1]Bootloader - OK
[2]Radio_V2 - OK
[3] Radio_Cust - OK
etc...
I have the "OK" on all points except the [1] Bootloader, which has "Bypassed" after it...
WWE RUU now flashed, rebooted and still stuck at splash. Trying to recall if I had flashed a custom Kernel to this phone, back when I was using/playing with it. Blah, too many variables! Should have returned to stock two years ago!!
Still stuck at splash...and speaking of splash, phone might need to take a dip my swimming pool, I think.........................
777ace said:
I have --- AlphaRev --- at top of screen. Definitely have flashed stock HBoot.
Just flashing WWE RUU now. I notice in the tutes I've found I should be seeing
Parsing...[SD ZIP]
[1]Bootloader - OK
[2]Radio_V2 - OK
[3] Radio_Cust - OK
etc...
I have the "OK" on all points except the [1] Bootloader, which has "Bypassed" after it...
WWE RUU now flashed, rebooted and still stuck at splash. Trying to recall if I had flashed a custom Kernel to this phone, back when I was using/playing with it. Blah, too many variables! Should have returned to stock two years ago!!
Still stuck at splash...and speaking of splash, phone might need to take a dip my swimming pool, I think.........................
Click to expand...
Click to collapse
Not sure why it's skipping the bootloader part.
Custom kernel doesn't make a difference either. Everything except your sd card gets wiped when you run an RUU.
I had a read of the troubleshooting guide again, Part 8, it said to flash the downgrader, then RUU, sorry for my bad advice. Try that.
Else try runnnig the 2.3.3 RUU using PB99IMG.zip method in the same guide.
You should eventually be able to get it to boot. You don't have the RadioV2 fail which is a good thing
eddiehk6 said:
Not sure why it's skipping the bootloader part.
Custom kernel doesn't make a difference either. Everything except your sd card gets wiped when you run an RUU.
I had a read of the troubleshooting guide again, Part 8, it said to flash the downgrader, then RUU, sorry for my bad advice. Try that.
Else try runnnig the 2.3.3 RUU using PB99IMG.zip method in the same guide.
You should eventually be able to get it to boot. You don't have the RadioV2 fail which is a good thing
Click to expand...
Click to collapse
Well, I am now S-On, so progress is occurring... Also back to 0.75 HBoot.
Still booting straight to Fastboot though. For sh.ts and giggles, I just attempted to enter Recovery, but got the dreaded red triangle. All good, phone does still boot, just not in the way I want...
Anyhoo, still ticking away. Am relearning a heap of stuff. Maybe I could re-root and S-Off again, once I get this sorted??
777ace said:
Well, I am now S-On, so progress is occurring... Also back to 0.75 HBoot.
Still booting straight to Fastboot though. For sh.ts and giggles, I just attempted to enter Recovery, but got the dreaded red triangle. All good, phone does still boot, just not in the way I want...
Anyhoo, still ticking away. Am relearning a heap of stuff. Maybe I could re-root and S-Off again, once I get this sorted??
Click to expand...
Click to collapse
You can't enter recovery because the custom recovery gets overwritten by RUU as well. Like I said, everything should go back to stock.
Try the 2.3.3. GB RUU (I assume you used the Telus one as you only have 0.75 hboot?), get it booting first before trying anything else.
The latest RUU should have 1.02 hboot, at which point you could s-off with revolutionary as it's only compatible with 0.93 or 1.02 hboot as far as I know..
My suggestion of trying to enter recovery, or re-rooting was just me playing silly buggers. I swear once this thing is sorted, I am never touching it again!!
So I just tried to re-flash the Telstra RUU and got message "Main Version is older! Update Fail!". Probably due to the 0.75 HBoot, I am guessing. Would like to find a copy of Telstra FroYo RUU and see if that works. If it does get things moving, I could then OTA update once full-boot has been achieved.
Still pretty sure I missed a step somewhere... I did full wipe before starting (cache/dalvic, system, data, SD-Ext), but not factory reset. As I said, am now back to S-On, but I assume I am still rooted, so starting to think I should go back, gain S-Off, CWM and start all over again.
You people must be about ready to reach thru your monitor and choke me! Lol!!
777ace said:
My suggestion of trying to enter recovery, or re-rooting was just me playing silly buggers. I swear once this thing is sorted, I am never touching it again!!
So I just tried to re-flash the Telstra RUU and got message "Main Version is older! Update Fail!". Probably due to the 0.75 HBoot, I am guessing. Would like to find a copy of Telstra FroYo RUU and see if that works. If it does get things moving, I could then OTA update once full-boot has been achieved.
Still pretty sure I missed a step somewhere... I did full wipe before starting (cache/dalvic, system, data, SD-Ext), but not factory reset. As I said, am now back to S-On, but I assume I am still rooted, so starting to think I should go back, gain S-Off, CWM and start all over again.
You people must be about ready to reach thru your monitor and choke me! Lol!!
Click to expand...
Click to collapse
- Please use the 2.3.3 WWE RUU...
- Ignore anything and everything to do with Telstra...
- You are not rooted. You have run an RUU but it's not booting. This has overwritten everything, so your factory reset was unnecessary...
eddiehk6 said:
- Please use the 2.3.3 WWE RUU...
- Ignore anything and everything to do with Telstra...
- You are not rooted. You have run an RUU but it's not booting. This has overwritten everything, so your factory reset was unnecessary...
Click to expand...
Click to collapse
Yep, that's what I'm experiencing.
I have flashed RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4.05.00.11_release_122704 from here previously, but still had the boot issues when I ran it.
Gave it another try just now, but now have message "Model ID incorrect! Update Fail!"
- That is not the 2.3.3 GB RUU, I think it's an ancient Eclair RUU, yes android 2.1....
- If you can't find the 2.3.3 GB RUU, at least try the Froyo RUU from that thread, version 2.29.405.5 I think. This should give you hboot 0.93 which revolutionary also works on.
http://www.htcdev.com/process/legal_download/152
Or do it the PB99IMG method
http://d-h.st/d44
KA-CHING!!
I swear, if I could hit the THANKS button a million times, I would do so in a heart beat. Using mcclue's PB99IMG link, phone is now up and running like new!
But the thanks must also go eddiehk, for your patience and taking the time to check back each day to see how I am going. I swear I had no idea that RUU was Eclair/2.1... Just ASSUMED the updates were still relevant. Was getting close to just "Meh!" and tossing it in the trash.
So, going forward from here, is it worth me checking for OTA updates to bring the phone back completely to stock (Telstra) specs...or just leave it alone??
Anyway, again a million thanks to you guys for your help. Very much appreciated!! :good::good::good::good:
777ace said:
KA-CHING!!
I swear, if I could hit the THANKS button a million times, I would do so in a heart beat. Using mcclue's PB99IMG link, phone is now up and running like new!
But the thanks must also go eddiehk, for your patience and taking the time to check back each day to see how I am going. I swear I had no idea that RUU was Eclair/2.1... Just ASSUMED the updates were still relevant. Was getting close to just "Meh!" and tossing it in the trash.
So, going forward from here, is it worth me checking for OTA updates to bring the phone back completely to stock (Telstra) specs...or just leave it alone??
Anyway, again a million thanks to you guys for your help. Very much appreciated!! :good::good::good::good:
Click to expand...
Click to collapse
The 2.3 gb upgrade is the latest for this phone so just leave it as is. And if u want custom roms again, use revolutionary to s-off.
I have an M8 that I unlocked, rooted and installed a custom rom on. It was my brothers phone and have not touched it in quite a while but I tried to enter recovery on it and it just hangs at loading recover. I am able to get in to the bootloader, so I used fastboot to install the latest TWRP recovery image. No change, it just sits there loading recovery and then reboots and loads the rom.
My next step was to try updating the bootloader as it is on 3.16 and I need to get atleast to 3.19 for the latest CM12.1 roms. It is a CWS__001 device and with all the RUU's out there, I am totally confused and cannot find the one that I should be using.
I would appreciate anyone that can get my past the hanging recovery and pointing me to the proper RUU would be awesome!!!
Thanks!!!!
Flash an older twrp like the 2.7 series. The newer ones don't work on old hboots.
Thanks Mr Hofs!!!! That did it. I installed 2.7.1.0 and it works now. I appreciate the help.
Now to find the latest ruu for this phone and I will be all set!
bluecobras09 said:
Thanks Mr Hofs!!!! That did it. I installed 2.7.1.0 and it works now. I appreciate the help.
Now to find the latest ruu for this phone and I will be all set!
Click to expand...
Click to collapse
Here is the latest AT&T RUU direct from HTC's US website. Read the Manual System Update instructions (if you need them). The RUU download is at the end of the instructions.
Well, I finally found the RUU I used to update the bootloader on my original M8. It was the same model and a CWS__001, I followed the instructions I used before and first install failed as it said was usual and ran it a second time and it said it was successful. But after the fastboot reboot, it makes it to the white HTC screen and no further. Can't get it to go in to the bootloader or nothing so I think it may be bricked.
But thanks for the pointer.
bluecobras09 said:
Well, I finally found the RUU I used to update the bootloader on my original M8. It was the same model and a CWS__001, I followed the instructions I used before and first install failed as it said was usual and ran it a second time and it said it was successful. But after the fastboot reboot, it makes it to the white HTC screen and no further. Can't get it to go in to the bootloader or nothing so I think it may be bricked.
But thanks for the pointer.
Click to expand...
Click to collapse
Found the RUU that you used on your old phone? Did the RUU you ran contain the same or newer firmware than what was already on your new phone? If you aren't S-Off you can not flash an older firmware.
Your phone turns on, so it isn't bricked. Hold power + vol up to force a reboot (it could take up to 20 seconds). AS SOON AS THE SCREEN GOES BLACK slide your finger from vol up to vol down and hold it till it boots. That'll take you to bootloader.
Click the link I provided and download the newest RUU available for the AT&T M8 directly from HTC. Run that and hopefully your issues will be solved.
Good luck.
EDIT: I now see from your original post that you are still on the older bootloader, so the RUU you used should be newer that what you have (3.16 bootloader)
Still, give it another go. I'm not sure what RUU you have now, but downloading it again can't hurt.
Don't give up. You can fix this. Even if the RUU doesn't work (it should) there is always a way.
Thanks xunholyx, I will give it another try. The RUU I have gives me 3.19. It is the one I used on my personal M8 and it went without a hitch. I will follow you directions and report back.
Thanks!!
xunholyx said:
Found the RUU that you used on your old phone? Did the RUU you ran contain the same or newer firmware than what was already on your new phone? If you aren't S-Off you can not flash an older firmware.
Your phone turns on, so it isn't bricked. Hold power + vol up to force a reboot (it could take up to 20 seconds). AS SOON AS THE SCREEN GOES BLACK slide your finger from vol up to vol down and hold it till it boots. That'll take you to bootloader.
Click the link I provided and download the newest RUU available for the AT&T M8 directly from HTC. Run that and hopefully your issues will be solved.
Good luck.
EDIT: I now see from your original post that you are still on the older bootloader, so the RUU you used should be newer that what you have (3.16 bootloader)
Still, give it another go. I'm not sure what RUU you have now, but downloading it again can't hurt.
Don't give up. You can fix this. Even if the RUU doesn't work (it should) there is always a way.
Click to expand...
Click to collapse
bluecobras09 said:
Thanks xunholyx, I will give it another try. The RUU I have gives me 3.19. It is the one I used on my personal M8 and it went without a hitch. I will follow you directions and report back.
Thanks!!
Click to expand...
Click to collapse
And you will have to run it twice. The first time will update your bootloader. After you get a fail, don't disconnect or reboot, run the RUU a second time. (you'll get a message saying "flush" it again) This is normal with the older hboot.
Awesome, it is back online. Turns out the reason it would not boot was the complete lack of software on it. I do not remember that from my phone last year when I did it. The RUU update actually completed fine. I didn't know about the volume-up+power, slide to volume-down at black screen. That got me back into fastboot, unlocked bootloader, installed latest TWRP and rom and now all is well with the world again!!!.
I thank you for your time and knowledge xunholyx!!!
xunholyx said:
And you will have to run it twice. The first time will update your bootloader. After you get a fail, don't disconnect or reboot, run the RUU a second time. (you'll get a message saying "flush" it again) This is normal with the older hboot.
Click to expand...
Click to collapse