Related
Hi
I've downloaded an HTC Europe 1.15 RRU that I used before and worked.
Now, however, it wont flash. I just get to the "waiting for bootloader" and then a "connection error". I tried rebooting into bootloader but then the RRU just counts upto 100 and then tells me there is a connection error.
The difference between now and last time is that I've updated my bootloader to Alpha-Rev bootloader and Clockwork Mod Recovery is installed. The phone is rooted and S-OFF as well.
I'm trying to restore the phone to factory condition in preparation for a return to HTC for repair.
I guess I need to resintall some bootloader and recovery mod?? or is that in the RUU?
Any ideas/advice?
Android version 2.2
Baseband 32.47.00.32U_5.10.05.23
Kernel 2.6.32.15-gf5a401c
Build 2.29.405.2 CL263770 release-keys
Software: DJ Droid v1.8 (but also tried latest MoDaco, Pinky, CM6 and LeeDroid)
Browser: WebKit 3.1
HBOOT 0.93.0001
BRAVO PVT3 SHIP S-OFF
MICROP-051d
TOUCH PANEL-SYNW0101
Clockwork Recovery v2.5.0.7
Why do you want to put the FIRST ever RUU back onto your device? Just download the latest RUU (2.29.405.2) by clicking on my signature. This is assuming your phone in unbranded from the start, if not you'll need to get the RUU for your operator
Er, because I said ...
"I'm trying to restore the phone to factory condition in preparation for a return to HTC for repair"
Factory condition means ANY ROM that was meant for the unit - you don't need to go back to the first!!! So long as you're on an x.xx.405.x ROM you'll be fine!!! LMAO!!!
If you just flash the 2.29.405.2 RUU then you're back to stock so the factory will accept it
bloody hell.
saved me a ****ty weekend there pal.
nice1
cheers
will do this tonight and report back.
My HBOOT is 0.93.001 (flashed using alpha-rev clockword mod install utility). Some older RUUs refuse to load (waiting for bootloader and a reboot to bootloader whilst the RRU is still running - doesnt fix the problem). Appears to be waiting for a special signature from the bootloader. Is your link (RRU) likely to work do youo know ??
If you're currently S-OFF, which I assume you are, then get this file instead:
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.zip
It's the same RUU but in ZIP form. Once downloaded remove everything from the name except PB99IMG (so the file is effectively called PB99IMG.zip) and copy it to the root of your SD card. Then boot into HBOOT and it will read the ZIP and ask you to continue. Say yes and once done reboot and you'll be back to stock. Then just remove the ZIP from the SD card and away you go!
Word of advice: I was S-OFF and using the N1Table and the first time I ran this it failed on the System partition and got stuck on the white HTC screen. I left it an hour, ran the PB99IMG again and it completed so if you are on anything other than the stock table I'd go back to that first using the file from AlphaRev before running the ZIP
Either way you should be fine
Yeah S-OFF.
I'm okay with the PB99 - used that when creating gold card and downgrading.
The N1Table stuf is new to me. I'll google that now.
Thanks for the tip and link.
Cheers pal.
**EDIT:
Okay, so N1table is the partition table for sram/nvram chips.
I have not knowingly modified these, but in any event will grab
the stock HTC table just in case. I can only assume the hangup
is generated because the partition table is hardcoded in the RRU
rather than being read in by the RRU - or something like that.
Anyway, thanks once again pal.
[Q] The phone was purchased on the UK Orange network although no branding on the phone (orange square logo and orange applications). The phone was locked to the Orange network and the settings SLIGHTLY different than the unbranded phone my bro has. Will I need to get hold of the Orange RRU before sending to HTC for repair (as in will the IMEI number be registered to Orange or something)?
If it had the Orange ROM on it then you will need that before sending it back...now, an Orange RUU has never surfaced BUT I might know someone getting one today so if I hear anything I'll post back on here.
If you needed a gold card to flash the stock RUU then you will need the Orange RUU
With regards to S-OFF, unless you downloaded and flashed a new table you will still be on the stock Desire one
I used alpha-rev' s-off utility (cant recall the link and didnt save it) but unsure whether the table has been modified. I'll just download the HTC one. Simples.
DAMM. I thought I may need the Orange RUU. Yes, the stock RRU wouldnt install I recall; required a gold card and a bootloader downgrade as I remember. ****!
I've been searching for Orange RUU for months to no avail.
As I said, hold out a day or so as I think someone might be getting it from Orange
Leave it with me...
Acknowledged
My gracious thanks in advance.
Good luck!
Eddy if you get a stock Orange RUU you will be god . Hope you get it.
Sent from my HTC Desire using XDA App
It won't be me but apparently someone is getting an Orange techie to debrand his phone and he's getting the RUU in case he needs to go back to stock...as soon as I hear something I'll update
ste1164 said:
Eddy if you get a stock Orange RUU you will be god . Hope you get it.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
+1 for Eddy being God
EddyOS said:
It won't be me but apparently someone is getting an Orange techie to debrand his phone and he's getting the RUU in case he needs to go back to stock...as soon as I hear something I'll update
Click to expand...
Click to collapse
Hang on; dya mean its possible to create an RUU or backup of a branded Orange phone - as indeed I had before I rooted et.al. ? Oh no, could I have created one - surely not ?
EddyOS said:
If you're currently S-OFF, which I assume you are, then get this file instead:
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.zip
It's the same RUU but in ZIP form. Once downloaded remove everything from the name except PB99IMG (so the file is effectively called PB99IMG.zip) and copy it to the root of your SD card. Then boot into HBOOT and it will read the ZIP and ask you to continue. Say yes and once done reboot and you'll be back to stock. Then just remove the ZIP from the SD card and away you go!
Word of advice: I was S-OFF and using the N1Table and the first time I ran this it failed on the System partition and got stuck on the white HTC screen. I left it an hour, ran the PB99IMG again and it completed so if you are on anything other than the stock table I'd go back to that first using the file from AlphaRev before running the ZIP
Either way you should be fine
Click to expand...
Click to collapse
Nice1 Eddy. The ZIP did the trick. The RRU method didnt work but I expected that as it was looking for an original HBOOT signature.
So, back to HTC stock. Not sure whether they would accept it for repair though given that it was sold as a branded Orange handset. Can they check?
Well, I will give this a go. The reason for the repair is that I've installed god knows how many custom ROMs and:
1. wifi doesnt always work.
2. Data connection errors.
3. Random reboots.
4. 90% reboot when navigating in the car.
5. Failure to answer some incoming calls.
6. Sometimes outgoing calls carry no voice modulation (they cant hear me)
different problems depending on ROMs.
So, lets see how the stock does before I decide to send back/or not.
Thanks again Eddy.
No, the bloke at Orange is going to give the guy getting it debranded the Orange RUU so he can go back to stock if he needs to...
HTC can tell, and my still fix it and put the Orange ROM back on it, but they may also turn around and refuse to fix it due to having a different ROM to the original
You can get to stock Orange with a very complicated method. After debranding you would root the phone. Then apply the backup on my thread. You then remove the superuser.apk with adb. You then flash the two updates orange released this unroots your phone back to stock.
Sent from my HTC Desire using XDA App
Nice1 Ste, however, mine is SLCD not Amoled. The nandroid is from an Amoled handset. Wont work with mine. Nice idea tho.
Anyone have a nandroid from an Orange set??
After breaking my previous desire i got a new one from insurance past friday. I s-off and rooted it with revolutionary and ran the alpharev cm7 r2 partition table. All went fine and i installed the CM 7.2 RC rom and started downloading all my apps and stuff.
All seemed fine untill i shutdown my phone last night and when booting it up this morning it doesn't boot up into anything. I can only get into Hboot and fastboot. I've tried booting into recovery but it gets stuck on the boot screen again.
Now i've read the Q&A troubleshooter posted above here and i have already tried reflashing recovery, which sadly still didn't boot after the reflash.
Now i'm completely stuck on what to do and have been searching for over an hour now.
I've read i could do a RUU for my phone, but seeing as alpharev has protection against that i'm not certain that would even help. What would be the best solution here to get my phone working again. (and if possible with the current data on it , i hadn't made a backup of the full install yet)
Edit: some extra info
Hboot 6.93.1002
Bravo PVT3 S-off
radio 5.11.05.27
CM 7.2 RC
clockwork, not sure newest version for desire afaik
Did you try to remove battery?
yes, seeing as that is the only option right now to turn my phone off .
I also ran fastboot oem gencheckpt to force boot into recovery. The phone got stuck at htc splashscreen. I posted the cmd image information in this post.
when i pulled the battery to shut down the phone, the cmd gave and "error, to many links"
edit:
i ran the alpharev downgrade image to overwrite my hboot and see if i could get into recovery after reflashing that aswell. Sadly this didn't work and after flashing both it still gets stuck at the htc splash screen
i ran the downgrade hboot again and will not try to fix it with a RUU
hmm, the phone is still recognized by the pc, but i have a black screen and can't get it to display anything. did i use a bad ruu or? I"m really confused now :|
after looking in the troubleshoot again i tried to flash the bravo stock from alpha rev, but i'm getting a FAILED <remote: signature verify fail>
well seeing as i most likelly need a goldcard now and don't have another android device laying around i will have to continue this tomorrow or tonight.
if ANYBODY has any advice everything is really appriciated!
what RUU did you flash?
if it was under 2.xx that means you did slcd brick have look here
flash bravo stock from alpharev, then run (if you have a goldcard) the 2.2 WWE RUU, or your carriers RUU (make sure it's the latest one)
Check shipped-roms.com
i think i ran this RUU
RUU_Bravo_HTC_Europe_1.15.405.3_Radio_32.30.00.28U _4.05.00.11_release_121865.exe
which i got from this post, which i now see is terribly out-dated xD.
I got my phone from vodafone in Holland, and i just saw an RUU for bravo that was shipped by vodafone UK which also supports the same radio as mine. Is it a safe bet to use that one for the recovery process?
I wasn't able to run any images right now from fastboot for some reason so i will indeed need to make a goldcard. Will do so tomorrow and report back if i've had any succes.
Thanks for the advise!
OK, so i'm a bit confused by that guide i'm afraid...
I've noticed that in step 4 that i'm unable to enter recovery (no surprise seeing as i was unable before the RUU).
I can boot in to fastboot and hboot i think seeing as i get the "device connected sound" in windows. When i then enter ADB devices or fastboot oem gencheckpt it gives me some information, which can be seen in the screenshot.
What i'm now confused about is, do i still need to make a goldcard, and if so how? I tried running that goldcard creater software but it couldn't pull a CID. Should i create a goldcard by just using a phone of my friend (desire s :|)? Or is it possible to just run the right RUU straight away seeing as i can connect to hboot and fastboot, let that run and when that is finished use revolutionary to root my phone agian.
Attached is the cmd for fastboot oem gencheckpt and adb devices, although normally the fastboot oem gencheckpt finished with a "FAILED <status read failed<too many links>>
Gimme bootloader information, also what state is the phone in now, and what have you tried so far. (quick summary)
My bad just read you last posts.
Try the Vodafone RUU, it should work, don't see why it shouldn't. If that fails, make a goldcard with your friends Desire S, and flash the 2.2 WWE RUU.
If that fails then use the 2.3 RUU.
Ah great!!! I ran the vodafone ruu and atleast now i'm getting fastboot and hboot displayed again.
I'll see how far i can get on my own now. Thanks alot for all your help
Darn, aren't there yet...
I can now get into fastboot and hboot WITH it being displayed so that is already a big plus. However i'm still on a off partition format so i need to flash that back to the original partition format.
I'm S-ON right now so i can't do it through fastboot.
So i made the goldcard through my friends phone and place a PB99IMG.zip containing the alpharev bravostock on the goldcard.
When i then boot into HBOOT it gives me the reading PB99IMG.zip but doesn't give me an option to run the update afterwards. I then checked with the RUU i ran from my pc and created an PB99IMG.zip of that and let it run from HBOOT thus checking if the goldcard was functional. This worked perfectly apart from the partition table being screwed.
How can i now either install recovery from my goldcard while being S-ON or how can i succesfully run the bravo_stock image from my goldcard?
edit: I know i could use the old s-off trick from alpharev but i would prefer to use revolutionary instead seeing as it's more up to date...
k i think i know what to do.
i'll just create a bootable USB with the 1.8 hboot from alpharev on it. S-off my device and restore the partitions to stock.
Then run the RUU again so that my phone returns to stock sense and S-on.
After that i should be the basic root process all over again by running revolutionary etc right?
If you're S-ON. You DO NOT need to touch the hboot, and you can't anyway.
If you've got a goldcard just try the WWE RUU. And if that doesn't fix it then the 2.3 RUU.
That's all you need to do. NOTHING else.
The 2.3 RUU (the vodafone one i downloaded) doesn't work.
I don't think any RUU will work for my seeing as i'm still on the CM 7 r2 partition layout instead of the original sense layout (a little mistake i made when running the first faulty RUU). I'll try to run the WWE RUU first, but i don't think it'll achieve anything.
If i would now run the alpharev 1.8 hboot from a bootable USB it shouldn't put my device at risk right? :|
Edit:
i'm actually getting CID incorrect from the WWE RUU from the troubleshoot thread and from another WWE RUU i downloaded from shipped-roms.com
edit2:
alright, i tried 2 WWE RUUs, which when ran from my PC give me ERROR[131]: customer-ID error and a CID incorrect when done from my goldcard... i also tried alpharev hboot 1.8 but that didn't work either for the obvious reason that you need to boot into android and enable usb debugging and the WWE RUUs for i do not know what reason .
Damn i thought i had figured it out before going to college but aparently i was wrong >.<
i don't know if it's relevant but when i try to boot normally i get the HTC splash screen and it vibrates 7 times in a row...
So i think my goldcard might not be as golden as it should be. Should i try it with my other microSD, the one that i actually use in my phone, an 16 gb kingston?
If so can i use the same goldcard.img or should i create a new one?
bortak said:
If you're S-ON. You DO NOT need to touch the hboot, and you can't anyway.
If you've got a goldcard just try the WWE RUU. And if that doesn't fix it then the 2.3 RUU.
That's all you need to do. NOTHING else.
Click to expand...
Click to collapse
Dear god how many times do I just need to repeat myself.
Just download http://www.htcdev.com/process/legal_download/152 , boot into fastboot mode, then run RUU.exe
There is no vodafone 2.3 RUU, there is only one, and it is unbranded.
Elightos said:
So i think my goldcard might not be as golden as it should be. Should i try it with my other microSD, the one that i actually use in my phone, an 16 gb kingston?
If so can i use the same goldcard.img or should i create a new one?
Click to expand...
Click to collapse
If you still get CID error - you do not have a goldcard. Simple as that.
Elightos said:
The 2.3 RUU (the vodafone one i downloaded) doesn't work.
Click to expand...
Click to collapse
The 2.3 RUU always does something, if not for better than for worse.
ah right i'm sorry, i was a bit confused about that ruu because of some of the information displayed on shipped-rom.com. Prolly read it wrong or something.
Anyway the 2.3 RUU did indeed fix it! quite surprised after all this really didn't expect it! Thanks out a load and i'm sorry for touching a nerve there, it's just the first time doing anything like this so it was all a tad bit confusing!
Elightos said:
ah right i'm sorry, i was a bit confused about that ruu because of some of the information displayed on shipped-rom.com. Prolly read it wrong or something.
Anyway the 2.3 RUU did indeed fix it! quite surprised after all this really didn't expect it! Thanks out a load and i'm sorry for touching a nerve there, it's just the first time doing anything like this so it was all a tad bit confusing!
Click to expand...
Click to collapse
Lol don't worry about it, everyone starts of a newb I remember posting some scare stories of mine a while back of when I first started messing with my phone
I need an Obi-wan here. I'm a noob -- though I've gotten a solid four day education
hacking at this problem.
My wife's Android Desire Z - Stock ROM, S-ON, got stuck looping with a failed
android.process.acore message and after trying a cache clear that didn't help
I set out to factory reset it. Figured the nuclear option would be dead simple. Nope.
Factory Reset from the Hboot menu simply froze the phone
at the HTC menu for an hour. Not good.
From there dozens of resets and reboots and fastboots would sometimes successfully boot
to my wife's setup (so nothing was reset at all), only to get stuck in the acore loop again.
I was once quick enough to put it into
airplane mode and that stopped the error message loops. YAY! I could try a reset
via software! But when I attempted
Settings > SD & phone storage > Factory data reset it rebooted to HTC screen, Vodafone
screen, HTC screen, vodafone screen. ANOTHER loop.
OK, next try was to flash the ROM with an original shipped version.
Couple forums in Dutch said the shipped ROM for the Vodafone Desire z in NL was Bravo/Froyo World Wide English
so I located this file:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_
signed.exe
and attempted reset by running that on a pc.
But the USB connection failed after the unit reset: Error 171, Error 170.
Tried installing HTC Sync AND the Universal boot drivers
and the Android Booloader Driver, as per the helpful advice from Bob Denny at Phandroid. (As a noob, I can't post links here, sorry)
And yep, I disabled anti-virus, had a fully charged phone (I'm hoping you get
the picture here -- I've done my due dilligence and googling before asking for help.) but
nada. RUU rebooted the phone, waited for the bootoader, and either the phone never pings the USB
port to say it's there or the PC doesn't see it.
FINE. I can put a PC10IMG.ZIP on the SD card and dispense with the frustration of messing with windows, right? Well, no.
I extracted ROM.ZIP from the RUU renamed it PC10IMG.ZIP and slapped it in the root
directory of the SD card. I booted to Hboot with the volume down and power buttons, chose
Fastboot and watched the the Zip load (blue verticle progress bar upper right of screen),
check it (brown progress bar upper right), then NOTHING -- back to the Hboot menu.
No error message, and no invitation to
update. Reboot takes me back to screen loop. Normal power-on does the same.
Further searches make me question if this is the right shipped ROM.
The RUU reports that I'm running version 2.42.161.22
(of what? Vision Gingerbread?) and the Bravo/Froyo WWE Rom reported itself to be version 1.59 something.
As this is an S-ON phone, I know I can't roll back to earlier ROMS, and can only install
the exact version as shipped.
So the questions I THINK I need answered:
1. Does anyone know for certain, or know where I can find out, which ROM
shipped with the Vodafone NL Desire-Z in 2010? I can get Kernel source for it at the HTCDev site,
but I see no compiled ROM there -- anything I can do with kernel source?
2. Anyone know where can I get the right PC10IMG.ZIP file to flash the unit from the SD Card? (I tried Shipped-Roms.com and
dozens of google permutations)
3. Is my methodology for flashing the SD Card right or is there anything in the
description above that lends anyone to believe my problem or solution is anything
other than the one I'm obsessing over?
Any help deeply appreciated.
Info from Hboot screen:
VISION PVT SHIP S-ON
HBOOT-0.05.0013
MICROP-0425
RADIO-26.10.51.26
eMMC-BOOT
Apr 11 2011, 23:36:27
Image CRC:
osbl: 0x1B4C7A4C
amss: 0xEF10821B
hboot: 0xCCCC4C36
recovery: 0x9627D8E8
system: 0xB6CE69CE
Please tell me I'm a stupid Noob and I've missed something so obvious I'll leave a
facepalm scar on my forehead, then tell me what it is so I can fix this dang phone and
get my life back. I'd be one appreciative noob.
-b
Try again with the PC10IMG.zip, this time don't extract the rom image, flash the entire zip. If this doesn't work you may need to make a goldcard. This means you will need to boot the phone and get into setting to turn debugging on and will will also need to get the proper window drivers up and running in order to use adb. (Try holding the s key on the key pad while powering on, this may keep the bootloop away)
Sent from my MyTouch 4G Slide using xda premium
demkantor said:
Try again with the PC10IMG.zip, this time don't extract the rom image, flash the entire zip.
Click to expand...
Click to collapse
Yeah, sorry wasn't clear I extracted the zip from the RUU, not the rom itself, so I've tried this one already.
Safe boot doesn't boot -- gets me the HTC screen and freezes there. I'll keep trying, as I think gettting debugging on and going gold card may be my only hope if the problem isn't incorrect ROM (or if there's no finding the correct one).
Here's a simpler question: If in my hboot screen I see
VISION PVT SHIP S-ON
Does that mean the shipped ROM was vision gingerbread and that's the only one to try,
or could my wife's "system updates" upgraded the phone from a Bravo shipped ROM?
And when I get a CID Incorrect error on a Vision Gingerbread ROM, does that mean the WWE Vision Gingerbread ROM I tried to install isn't good because it's not Vodafone, or because it's not the shipped ROM?
Any help will be thankfully appreciated!
Sorry it took so long to get back,
ship s-on is referring to you have a shipped bootloader and your security flags are on, that line is not specific to any version of the desire z
You won't be able to flash any ROM like that unless it is an upgrade from current version. I believe if you go to HTC website the latest ruu was not released as an ota and may work for you as its probably newer. If it doesn't work then you will need to get super cid in order to flash something older, which means you need to get adb working
Sent from my Nexus 7 using xda premium
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.
Let me start by saying this forum has provided me with a ton of support in the past. There is so much information available here that I rarely have to start my own thread. Unfortunately, I have spent the past 18 hours looking for a solution to my current problem and have come up empty handed. I'm hoping some of you are savvy enough to help me out. I will try to provide as much information as possible to help diagnose the issue.
Device
HTC One M8
Carrier: AT&T
CID: CWS_001
Unlocked HTC Bootloader
S-On
I was previously running the stock ROM rooted (based on the above) simply to disable the AT&T bloatware. As of last week, AT&T began pushing the 4.4.4 update and I made the mistake of trying to install it not realizing my custom recovery (TWRP 2.7.1.0) would prevent it. Ever since this occurred, my phone has been doing strange things, i.e. random reboots and the "AT&T" logo in the upper left corner of the task bar would flash and disappear. It eventually got to the point where my phone was stuck in a constant boot loop and the only thing that would fix it was a factory reset from TWRP recovery. The phone would then act normal for about 24 hours and then the boot loop would start again.
I decided to try solving the issue by installing the GPE 4.4.3 ROM. I performed a complete wipe in TWRP (including system) and installed the GPE ROM via ADB/Fastboot. Everything was fine from this point and all apps/data synced after I logged into my Google account. Shortly after the phone booted, I was asked to install the GPE 4.4.4 update. It was at this point that I decided to load the stock recovery image so I could simply install the OTA update. Once again, no problems. Stock recovery flashed fine and I downloaded the 4.4.4 OTA update and rebooted the phone. The phone appeared to finish the install, but failed to boot. Now I cannot get past the HTC splash screen and I do not have a custom recovery.
The factory reset option from stock recovery does not help (still gets stuck at the splash screen) and for some reason my device is no longer recognized in Fastboot which prevents me from flashing a custom recovery. I thought it may have been a driver issue so I uninstalled and reinstalled HTC Sync Manager. I also tried manually uninstalling the drivers from the USB Root Hub, pulled the battery on my laptop, and allowed Windows 7 to auto update the drivers automatically. In each case, the drivers were successfully installed, but the phone is still not recognized in Fastboot (no devices listed). I even did a system restore on my laptop to a few days before the issue and the phone still isn't recognized by HTC Sync Manager or Fastboot.
The stock recovery bootloader displays the following information:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-INVALID_VER_INFO
OpenDSP-INVALID_VER_INFO
OS- (2.12..1700.1)
eMMC-boot 2048MB
Based on all of this, do I have any options or is my phone bricked?
1. Is there anything I can do so my device is recognized by ADB/Fastboot so I can flash a custom recovery?
2. Can I install a ROM from the SD card with the stock recovery? I currently have the GPE 4.4.3 ROM on my SD card, but the zip is not recognized by the stock recovery. Can I rename it to something else so it can be recognized and installed?
3. Because the phone is not recognized by Windows, I cannot use the RUU method. Are there any other ways to return my phone to stock without RUU?
Any help is greatly appreciated.
Swazi Samurai said:
Let me start by saying this forum has provided me with a ton of support in the past. There is so much information available here that I rarely have to start my own thread. Unfortunately, I have spent the past 18 hours looking for a solution to my current problem and have come up empty handed. I'm hoping some of you are savvy enough to help me out. I will try to provide as much information as possible to help diagnose the issue.
Device
HTC One M8
Carrier: AT&T
CID: CWS_001
Unlocked HTC Bootloader
S-On
I was previously running the stock ROM rooted (based on the above) simply to disable the AT&T bloatware. As of last week, AT&T began pushing the 4.4.4 update and I made the mistake of trying to install it not realizing my custom recovery (TWRP 2.7.1.0) would prevent it. Ever since this occurred, my phone has been doing strange things, i.e. random reboots and the "AT&T" logo in the upper left corner of the task bar would flash and disappear. It eventually got to the point where my phone was stuck in a constant boot loop and the only thing that would fix it was a factory reset from TWRP recovery. The phone would then act normal for about 24 hours and then the boot loop would start again.
I decided to try solving the issue by installing the GPE 4.4.3 ROM. I performed a complete wipe in TWRP (including system) and installed the GPE ROM via ADB/Fastboot. Everything was fine from this point and all apps/data synced after I logged into my Google account. Shortly after the phone booted, I was asked to install the GPE 4.4.4 update. It was at this point that I decided to load the stock recovery image so I could simply install the OTA update. Once again, no problems. Stock recovery flashed fine and I downloaded the 4.4.4 OTA update and rebooted the phone. The phone appeared to finish the install, but failed to boot. Now I cannot get past the HTC splash screen and I do not have a custom recovery.
The factory reset option from stock recovery does not help (still gets stuck at the splash screen) and for some reason my device is no longer recognized in Fastboot which prevents me from flashing a custom recovery. I thought it may have been a driver issue so I uninstalled and reinstalled HTC Sync Manager. I also tried manually uninstalling the drivers from the USB Root Hub, pulled the battery on my laptop, and allowed Windows 7 to auto update the drivers automatically. In each case, the drivers were successfully installed, but the phone is still not recognized in Fastboot (no devices listed). I even did a system restore on my laptop to a few days before the issue and the phone still isn't recognized by HTC Sync Manager or Fastboot.
The stock recovery bootloader displays the following information:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-INVALID_VER_INFO
OpenDSP-INVALID_VER_INFO
OS- (2.12..1700.1)
eMMC-boot 2048MB
Based on all of this, do I have any options or is my phone bricked?
1. Is there anything I can do so my device is recognized by ADB/Fastboot so I can flash a custom recovery?
2. Can I install a ROM from the SD card with the stock recovery? I currently have the GPE 4.4.3 ROM on my SD card, but the zip is not recognized by the stock recovery. Can I rename it to something else so it can be recognized and installed?
3. Because the phone is not recognized by Windows, I cannot use the RUU method. Are there any other ways to return my phone to stock without RUU?
Any help is greatly appreciated.
Click to expand...
Click to collapse
There is 2 methods to do an RUU. one is by putting the RUU on your sdcard and booting into the bootloader and waiting a few minutes then accepting the prompt to do it and 2 is the fastboot method. Since you have an SD card you could attempt the first one I listed. Make sure you don't change the name of the RUU and make sure you get the proper one for your phone.
S1L3nTShaDoWz said:
There is 2 methods to do an RUU. one is by putting the RUU on your sdcard and booting into the bootloader and waiting a few minutes then accepting the prompt to do it and 2 is the fastboot method. Since you have an SD card you could attempt the first one I listed. Make sure you don't change the name of the RUU and make sure you get the proper one for your phone.
Click to expand...
Click to collapse
Don't you have to be S-OFF or have a locked bootloader to run a RUU? I am unable to achieve either of those since my phone is not recognized by by ADB/Fastboot.
Also, because my most recent functioning ROM was GPE 4.4.3, would I still be able to run the stock AT&T RUU? I thought the partitions were different? I have the GPE RUU as well, but I don't think I can run that either without changing my CID and locking my bootloader.
Swazi Samurai said:
Don't you have to be S-OFF or have a locked bootloader to run a RUU? I am unable to achieve either of those since my phone is not recognized by by ADB/Fastboot.
Also, because my most recent functioning ROM was GPE 4.4.3, would I still be able to run the stock AT&T RUU? I thought the partitions were different? I have the GPE RUU as well, but I don't think I can run that either without changing my CID and locking my bootloader.
Click to expand...
Click to collapse
S-OFF not so sure about, locked bootloader, no you can have it unlocked. But you can try it anyways, the SD card method.
Yes you would be able to run it, I'm quite sure all you did was flash a GPE ROM. I believe all flashing the ROM does is give you a GPE ROM where as the GPE RUU would change all that and give you GPE phones firmware too.
On the off hand you did do a GPE RUU then I'm not sure.
S1L3nTShaDoWz said:
S-OFF not so sure about, locked bootloader, no you can have it unlocked. But you can try it anyways, the SD card method.
Yes you would be able to run it, I'm quite sure all you did was flash a GPE ROM. I believe all flashing the ROM does is give you a GPE ROM where as the GPE RUU would change all that and give you GPE phones firmware too.
On the off hand you did do a GPE RUU then I'm not sure.
Click to expand...
Click to collapse
I have heard it has to be one or the other. If S-OFF, the bootloader can be unlocked. If S-ON, the bootloader has to be locked.
I did not run the GPE RUU originally; I installed the ROM through custom recovery. I'm assuming that is a good thing based on your feedback.
Regardless, I haven't been able to try the SD method because the zip file I extracted from the RUU exe will not transfer to my SD card. I also tried downloading another user's bootable version and it won't transfer either. I have copied many other files to and from my SD card (even larger file sizes) without any issues. I have no clue what is going on now...
Swazi Samurai said:
I have heard it has to be one or the other. If S-OFF, the bootloader can be unlocked. If S-ON, the bootloader has to be locked.
I did not run the GPE RUU originally; I installed the ROM through custom recovery. I'm assuming that is a good thing based on your feedback.
Regardless, I haven't been able to try the SD method because the zip file I extracted from the RUU exe will not transfer to my SD card. I also tried downloading another user's bootable version and it won't transfer either. I have copied many other files to and from my SD card (even larger file sizes) without any issues. I have no clue what is going on now...
Click to expand...
Click to collapse
I formatted my SD card and was finally able to transfer the RUU. The bootloader begins to run the 0P6BIMG file, but it fails right after it starts parsing. I tried running it several times and the results were the same.
I really wish I could get ADB to recognize my phone so I can flash a custom recovery... When I plug my phone into a USB port, my computer makes a noise, the phone says "USB" next to Fastboot, and HTC Sync Manager begins to load. When HTC Sync Manager comes up, it says "HTC Sync Manager couldn't connect to your phone." Windows Device Manager also does not have anything listed for an Android device.
I've noticed when the phone is not powered on and simply charging from the USB port, an "HTC MTP Device" driver tries to install, but fails. Could this be the problem? I've tried plugging the phone into 3 different computers and they all get the MTP failure.
If you are coming from a GSM variant things get a little bit more complicated to install a GPE RUU, as the GPE HBoot is different from the GSM one and partition sizes are as well.
You have to be S-Off to install the proper firmware and prior to doing this, change the CID as well as the MID to a GPE one.
There is a full guide on this forum to convert your M8 from GSM to GPE, bit as I'm on the train at the moment I can't provide you the link right away.
Sent from my HTC One_M8 using XDA Free mobile app
HTCNerdYoda said:
If you are coming from a GSM variant things get a little bit more complicated to install a GPE RUU, as the GPE HBoot is different from the GSM one and partition sizes are as well.
You have to be S-Off to install the proper firmware and prior to doing this, change the CID as well as the MID to a GPE one.
There is a full guide on this forum to convert your M8 from GSM to GPE, bit as I'm on the train at the moment I can't provide you the link right away.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I'm not specifically trying to install the GPE RUU at the moment. I had the stock GSM recovery installed based on my original CID and I'm trying to load the associated RUU.
I originally loaded GPE 4.4.3 with TWRP and downloaded the 4.4.4 update OTA from Google. Before restarting my phone and installing the update, I flashed the stock GSM recovery for CID CWS_001. This may have been what caused the issue initially when the phone tried to apply the update if it was looking for a GPE recovery.
I know I cannot install the GPE RUU because I'm S-ON and ADB does not recognize my device so I cannot change the MID or CID. At this point, I'm really just trying to get back to stock so I can start fresh.
Is it possible that when the 4.4.4 update tried to run, it associated my recovery with GPE and now that's why it will not install the stock RUU due to a mismatch? I'm really just guessing at this point.
Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.
3484jacks said:
Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.
Click to expand...
Click to collapse
I'll give that a try and report back. Thanks for the input.
3484jacks said:
Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.
Click to expand...
Click to collapse
You are the freakin man!!! I edited the template from the post you suggested, added my MID/CID, and packaged it with the TWRP image. Booted right from the SD and I now have custom recovery! I wish I could buy you a beer!
No problem mate. Glad I could help. :thumbup::thumbup::beer:
Sent from my HTC One_M8 using XDA Free mobile app