Problem returning to stock - HTC Amaze 4G

Hello Everyone,
I hope there is an obvious solution that I am just missing. I have the Amaze 4G on Wind Mobile, I rooted, then flashed the Energy rom. Then I wanted to return to stock. I have followed more tips, tricks, guides, suggestions, how-to's then I can count so here is where I am at.
I can still get into hboot/fastboot as well as whatever recovery I happen to flash with Hasoon2000's kit;
hboot version is 1.93.0002
I am still S-ON
I was running the official stock ICS; I rooted after that update; so I don't think that I need to return to GB then OTA update to ICS.
I have tried the three Wind mobile stock RUU's that are floating around; the first two fail because my hboot is a newer version.
I have downloaded the Wind ICS OTA file, extracted the stock boot and recovery .img files and flashed them over with the Hasoon2000 kit, renamed the un-extracted ICS OTA file to PH85IMG.zip (with only ONE .zip), copied to my external card, relocked the bootloader, removed the battery and rebooted. It finds the file, loads, checks, then sends me back to the hboot screen. I have tried then rebooting the phone and eventually it ends up at the white HTC boot screen and sits there. I have tried leaving it there for 30 + minutes and unless it might need days I don't think it is going anywhere.
I have managed to boot into the stock recovery which at times even gets a progress bar, reboots, and sits at the HTC screen; other times I get the red triangle.
I know other people have had issues similar to this as I have read an endless number of threads on the subject, none of the suggestions have worked thus far.
Any help is greatly appreciated. Thank you!
EDIT:
I can still install custom roms so not all is lost, but I would still like to get back to the stock rom and it still isn't working. I tried using the tool from this thread http://forum.xda-developers.com/showthread.php?t=1526316 to reset my version and then run the update wizard and it recognized that I was at version 1.00.0000 but still failed.
Also installing PH85IMG.zip from the sd card gets to the parsing stage and then goes back to hboot.
Any ideas?

Tried to delete this thread but couldn't figure out how so I'll just edit it again.
I finally found the following thread http://forum.xda-developers.com/showpost.php?p=27058110&postcount=44
It doesn't specifically state that this problem applies to Wind mobile users but given the issues I am having I assume it does.
So I need a nand backup file! I would have my own except the SD Card it was saved on has died. So if anyone out there is using the Amaze 4G on Wind Mobile and can send me their Nand backup I will be forever grateful!
Unless of course those reading this know of an alternative solution?
Thanks in advance!

Related

[Q] EVO 3D Constant Boot Loops; Trying to Flash Stock ROM

Hello,
I have flashed to Cyanogenmod successfully via fastboot USB method. Has worked for a week. Now my phone just reboots. Figured it was the ROM, so did fastboot USB method again to install Synergy ROM (latest). The GUI didn't even finish loading, and it rebooted. Flashed back to Cyanogenmod, same thing. I've wiped before EACH flash.
I am so lost and wish to revert back to stock ROM and do this all over again, HOWEVER, I've done RUU recovery method from Sprint and it doesn't work. Loading the PG86IMG.zip from the root of the SD card doesn't really render results.
I've checked forums, and really couldn't find a solid way of doing this. If I missed or overlooked something, please point me to it and I'll gladly read it.
I am running HBOOT 1.50, which has been widely been perceived as a royal pain. I bought the phone used and came like that.
How would I do this?
alucardromero said:
Hello,
I have flashed to Cyanogenmod successfully via fastboot USB method. Has worked for a week. Now my phone just reboots. Figured it was the ROM, so did fastboot USB method again to install Synergy ROM (latest). The GUI didn't even finish loading, and it rebooted. Flashed back to Cyanogenmod, same thing. I've wiped before EACH flash.
I am so lost and wish to revert back to stock ROM and do this all over again, HOWEVER, I've done RUU recovery method from Sprint and it doesn't work. Loading the PG86IMG.zip from the root of the SD card doesn't really render results.
I've checked forums, and really couldn't find a solid way of doing this. If I missed or overlooked something, please point me to it and I'll gladly read it.
I am running HBOOT 1.50, which has been widely been perceived as a royal pain. I bought the phone used and came like that.
How would I do this?
Click to expand...
Click to collapse
If you wish to revert back to stock, loading the RUU is the best method.
Can you elaborate on what error you received you tried loading the PG86IMG.zip through the bootloader?
RUU are found here: http://goo-inside.me/shooter/ruu
Yep, I used that one. I don't get an error. It reads it ( obviously by the progress bar ) but doesn't give me an option to update or anything. Just passes it by as if it wasn't there.
*slaps head* I shouldn't have messed with this phone at all.
Also, I did managed to lock up the phone again. I used Sprint RUU again, successful. However, I still have boot loops as the GUI loads in Android.

Rogers Evo 3D Failed Ruu Recovery

Hey everyone, pretty new to the forums. I have been tinkering with trying to root my new rogers evo 3d i got a few days ago. I ran into some issues, and thought i had soft bricked my phone, it seemed to the point of no return, so just wanted to share what i did to make it work. Ive read a few posts were others had a similar issue and didnt seem to be resolved. I used the Revoluntionary Method, at 1st i was having trouble with the HTC drivers, the program no matter how many i tried would crash on install. So i just skipped all the stpes and just ran the Revoluntinoary Program, it actualy did everything, including install the HTC drivers all automated, worked awesome. Then not realising that i couldnt do most roms on a rogers gsm phone, i tried and failed with many roms. The one and only rom that i was able to install, was leedroid. This rom worked perfect everytime......but only on the 1st boot, if i tried to restartt the phone it would hang on the HTC logo. At this point i just wanted to revert back to rogers stock rom......but of course i didnt back anything up! I downloaded the rogers Ruu listed on here, and figured hey this will do the trick. After runiing the rogers Ruu and failing many times, i was frustated. Not only did it fail the flash, but it also locked my boot and left me S Off. Now every time i tried to start my phone, i would get the HTC logo screen with the !!!! in each corner, unplugging the usb gave me the locked hboot screen, and of course the Ruu kept failing. From everthing i read in the forums, it seemed toast. Since the RUU kept failing on the extract part it seemed, i thought maybe try to free up some space on the sd card......then i decided to just do a quick format on the card(Used card reader). For whatever reason, after formatting my sd card and rebooting the phone....it just started right up in stock rom, like the day i got it. Didnt even have to try the Ruu again, it just worked. Sorry for the long winded post, just wanted to give a brief history on everything i had done. Hopfully this helps someone out there that was stuck at the same location i was.
I think your in the wrong section bud. But good to know.
Sent from my HTC EVO 3D X515m using XDA App
maxer420 said:
Hey everyone, pretty new to the forums. I have been tinkering with trying to root my new rogers evo 3d i got a few days ago. I ran into some issues, and thought i had soft bricked my phone, it seemed to the point of no return, so just wanted to share what i did to make it work. Ive read a few posts were others had a similar issue and didnt seem to be resolved. I used the Revoluntionary Method, at 1st i was having trouble with the HTC drivers, the program no matter how many i tried would crash on install. So i just skipped all the stpes and just ran the Revoluntinoary Program, it actualy did everything, including install the HTC drivers all automated, worked awesome. Then not realising that i couldnt do most roms on a rogers gsm phone, i tried and failed with many roms. The one and only rom that i was able to install, was leedroid. This rom worked perfect everytime......but only on the 1st boot, if i tried to restartt the phone it would hang on the HTC logo. At this point i just wanted to revert back to rogers stock rom......but of course i didnt back anything up! I downloaded the rogers Ruu listed on here, and figured hey this will do the trick. After runiing the rogers Ruu and failing many times, i was frustated. Not only did it fail the flash, but it also locked my boot and left me S Off. Now every time i tried to start my phone, i would get the HTC logo screen with the !!!! in each corner, unplugging the usb gave me the locked hboot screen, and of course the Ruu kept failing. From everthing i read in the forums, it seemed toast. Since the RUU kept failing on the extract part it seemed, i thought maybe try to free up some space on the sd card......then i decided to just do a quick format on the card(Used card reader). For whatever reason, after formatting my sd card and rebooting the phone....it just started right up in stock rom, like the day i got it. Didnt even have to try the Ruu again, it just worked. Sorry for the long winded post, just wanted to give a brief history on everything i had done. Hopfully this helps someone out there that was stuck at the same location i was.
Click to expand...
Click to collapse
Which Hboot version on your Device? S-Off already? my device with Hboot .11 unlocked bootloader, and S-on, after flash Shooter beats 1.5 rom + included kernel Kamma v0.7, and now i can't get back to stock rom via RUU, failed everytimes (relocked bootloader), there is a way to get back stock rom without Gold card????
ddeathmetal said:
Which Hboot version on your Device? S-Off already? my device with Hboot .11 unlocked bootloader, and S-on, after flash Shooter beats 1.5 rom + included kernel Kamma v0.7, and now i can't get back to stock rom via RUU, failed everytimes (relocked bootloader), there is a way to get back stock rom without Gold card????
Click to expand...
Click to collapse
My Phones a Rogers Evo 3D GSM, HBoot 1.48.0008. Yup it was SOFF.
I used the Revo method to get Unlocked, SOFF and CWM.
I started out with CDMA roms, not knowing any better, and got my phone stuck in a boot loop.
The only way for me to stop the bootloop was with LeeDroids rom found here on XDA, so maybe try downloading that and flashing it. I downloaded every GSM Rom listed, but only Leedroid for me would do anything. The rest just hung up on the HTC logo.
Then I realised that Leedroids rom was also hanging on the HTC logo after Initial boot so i wanted to just get back to stock. I downloaded the listed Rogers Ruu also from XDA. Flashed into Leedroids rom on initial boot, ran the Rogers Ruu......only to have it fail on the update.....did a few cycles of the built in recovery option in the Ruu to no avail. I would always end up and the screen with around 11 checks all ok, but under system in would be failed. There was some message about and extraction error, and this Ruu wasnt compatible with my phone do download and try a new one.
Now my phone was stuck at the HTC logo screen with the 4 !!!! in the corners, unplugging the usb brought up the Hboot screen, which now said ****Locked**** and SOFF still.
I did a few more trys at the RUU, after redownloading multiple copys from different sources, same results, even tried to get the revo tool to pick up my phone during one of the flashes but it couldnt detect it.
At this point i called rogers.....asked about getting a replacment they said come in but i knew once they saw SOFF they wouldnt go for it.
The extraction failing on the RUU was what got me thinking that maybe by some chance there wasnt enough room on the SD card to complete the update? Which didnt make sense cause i had over 2g free space. Just for the hell of it, i popped out the SD, put it in my laptop, did a basic quick reformat of it.....then put in back in my phone.
The plan was to try the Ruu one last time but as soon as i hit the power button my phone started with a normal HTC logo, with no !!!!....followed by the rogers splash screen and right into the set up of the phone. Everything was back like the very 1st day i had it, even had the spiderman game. Not sure exactly why it worked, but maybe if you try something similar you can get yours back as well, hope this helps a bit.
maxer420 said:
My Phones a Rogers Evo 3D GSM, HBoot 1.48.0008. Yup it was SOFF.
I used the Revo method to get Unlocked, SOFF and CWM.
I started out with CDMA roms, not knowing any better, and got my phone stuck in a boot loop.
The only way for me to stop the bootloop was with LeeDroids rom found here on XDA, so maybe try downloading that and flashing it. I downloaded every GSM Rom listed, but only Leedroid for me would do anything. The rest just hung up on the HTC logo.
Then I realised that Leedroids rom was also hanging on the HTC logo after Initial boot so i wanted to just get back to stock. I downloaded the listed Rogers Ruu also from XDA. Flashed into Leedroids rom on initial boot, ran the Rogers Ruu......only to have it fail on the update.....did a few cycles of the built in recovery option in the Ruu to no avail. I would always end up and the screen with around 11 checks all ok, but under system in would be failed. There was some message about and extraction error, and this Ruu wasnt compatible with my phone do download and try a new one.
Now my phone was stuck at the HTC logo screen with the 4 !!!! in the corners, unplugging the usb brought up the Hboot screen, which now said ****Locked**** and SOFF still.
I did a few more trys at the RUU, after redownloading multiple copys from different sources, same results, even tried to get the revo tool to pick up my phone during one of the flashes but it couldnt detect it.
At this point i called rogers.....asked about getting a replacment they said come in but i knew once they saw SOFF they wouldnt go for it.
The extraction failing on the RUU was what got me thinking that maybe by some chance there wasnt enough room on the SD card to complete the update? Which didnt make sense cause i had over 2g free space. Just for the hell of it, i popped out the SD, put it in my laptop, did a basic quick reformat of it.....then put in back in my phone.
The plan was to try the Ruu one last time but as soon as i hit the power button my phone started with a normal HTC logo, with no !!!!....followed by the rogers splash screen and right into the set up of the phone. Everything was back like the very 1st day i had it, even had the spiderman game. Not sure exactly why it worked, but maybe if you try something similar you can get yours back as well, hope this helps a bit.
Click to expand...
Click to collapse
thanks for your info... maybe i'll try todo same your experience... i'll tell you later, if it's work or not!!! cheers!

Boot loop *fixed*

So after unlocking the boot loader today and loading up the stock rooted OTA rom my phone started randomly boot looping. It was sitting on my desk then randomly rebooted and now its been doing the same thing despite my best tries to fix it.
I had Amon Ra recovery installed initially, then flashed CWM via Rom manager. At this point I can't boot into recovery (or factory reset). It all happens very quickly, but it looks like the recovery menu loads up then the phone reboots. I am able to get into fastboot and reflash any of the recovery img's. I've tried the Amon Ra newest, the CWM normal and touch recovery and none of them will let me in. I've tried to get into recover with the 4G sim out and with the SD card out.
The phone does boot into an OS but after about 10 seconds it reboots. I did some digging and thought it might be the older bootloop issue with the network type. It does it with the sim out and in airplane mode so I'm not all that confident that its that issue.
At this point I am looking at tried to re-stock via Hboot RUU's. I have the P98IMG-1.02.605.6.zip on an SD card and that does flash but at the end of the verification it tells me "the main version is older." So I'm either looking for another package that will let me re-stock and give it a try again... or open to any other suggestions?
Hoping the phone isn't totally hosed, though based on what I can still get into I think there may be hope yet.
Anyone?
thanks in advance!
Have you tried CleanFlash? Also you are getting the mainver because you updated with the OTA. Google ruu_vigor. You are looking for the one that starts with 2.01.
Sent from my VTAB1008 using xda premium
This may help...
Get the 2.____.11 RUU from the 'Vigor Shipped' post in development. Follow the directions in the word file in post 2 from here:
http://forum.xda-developers.com/showthread.php?t=1487981
And then flash that RUU in HBOOT.
I had 99 problems with the RUU exe and spent the last week trying to get it to take. That tip to extract the PH file finally got me there. It fixed all kinds of issues for me and got me to stock.
Don't forget to relock.
(I think if you ran the ICS leak RUU you may still have issues, but you could follow those steps with that RUU as well probably and it would hopefully get you cleaned up)
Thanks for the help so far.
I got the newer RUU and got it flashed via hboot after i relocked. *edit* after the second time flashing it it seems to be working.
You guys rock.

Evo3D HBoot 1.58 Constant Rebooting Loop -- Needs Help Please

I have an Evo3d through Sprint and about a month ago they started sending me notifications to upgrade to Ice cream sandwich. I did such and immediately my touchscreen started going crazy. If I used the keypad in either position it would just randomly add letters all over the place, the home row would just stop working, and the phone would occasionally appear to lock up. I took the phone into the Sprint repair center and they told me they would not do anything with it because there is a incredibly small dent along the bezel that happened when I dropped the phone over 1 year ago. It has worked for at least a year on Gingerbread with 0 issues. I was then left to my own devices and after looking at several guides finally decided on a guide video to use for flashing to a custom rom, which I was hoping would fix the problem.
I unlocked the phone, simple enough, and from what I could find came to the conclusion that the guide which was for HBOOT-1.50 S-ON was the same image and process for my phone which is HBOOT-1.58 S-ON. I then used the cwm-4.0.1.4-shooter image to load into a "revolution" menu which allowed me to select the ROM which I had previously loaded onto the phone in the sdcard root directory. I selected MeanROM-v45 as per the video's recommendation and it told me it installed. I then rebooted the phone and saw the fancy new loading animation, then I saw the phone background, then I saw the unlock ring, then the phone rebooted in a never ending cycle. After reading the countless threads on what could be wrong, I tired MeanRom-v4.1, and the stock rom which I was led to believe was "Kingdom_Sprint_WWE-0.81.651.0_Radio_1.05.00.0429_NV-SPCS_2.25_0429_PRL21078_test_188785" and it gave me an error when trying to install. I then did more reading and found a new boot image which is "recovery-clockwork-5.0.2.0-shooter" and another rom which claimed to be stock which was "Shooter_S_Sprint_WWE_2.17651.5_odex". This rom reset the boot animation to the stock Sprint one, but alas all my phone does is constantly reboot, except I did notice it says "Safe Mode" in the lower right hand corner of the background before it reboots. I then tried to use the "RUU_Shooter_ICS_35_S_Sprint_WWE_2.89...." application which I was linked to from one forum post or another, and it gives me an error 155, then gives me another error when it tries to recover. Does anyone know how to correct what I apparently messed up? Sometimes some of the instructions are filled with lingo that i don't quite understand, but i can follow directions if they are sufficiently given.
joebandli said:
I have an Evo3d through Sprint and about a month ago they started sending me notifications to upgrade to Ice cream sandwich. I did such and immediately my touchscreen started going crazy. If I used the keypad in either position it would just randomly add letters all over the place, the home row would just stop working, and the phone would occasionally appear to lock up. I took the phone into the Sprint repair center and they told me they would not do anything with it because there is a incredibly small dent along the bezel that happened when I dropped the phone over 1 year ago. It has worked for at least a year on Gingerbread with 0 issues. I was then left to my own devices and after looking at several guides finally decided on a guide video to use for flashing to a custom rom, which I was hoping would fix the problem.
I unlocked the phone, simple enough, and from what I could find came to the conclusion that the guide which was for HBOOT-1.50 S-ON was the same image and process for my phone which is HBOOT-1.58 S-ON. I then used the cwm-4.0.1.4-shooter image to load into a "revolution" menu which allowed me to select the ROM which I had previously loaded onto the phone in the sdcard root directory. I selected MeanROM-v45 as per the video's recommendation and it told me it installed. I then rebooted the phone and saw the fancy new loading animation, then I saw the phone background, then I saw the unlock ring, then the phone rebooted in a never ending cycle. After reading the countless threads on what could be wrong, I tired MeanRom-v4.1, and the stock rom which I was led to believe was "Kingdom_Sprint_WWE-0.81.651.0_Radio_1.05.00.0429_NV-SPCS_2.25_0429_PRL21078_test_188785" and it gave me an error when trying to install. I then did more reading and found a new boot image which is "recovery-clockwork-5.0.2.0-shooter" and another rom which claimed to be stock which was "Shooter_S_Sprint_WWE_2.17651.5_odex". This rom reset the boot animation to the stock Sprint one, but alas all my phone does is constantly reboot, except I did notice it says "Safe Mode" in the lower right hand corner of the background before it reboots. I then tried to use the "RUU_Shooter_ICS_35_S_Sprint_WWE_2.89...." application which I was linked to from one forum post or another, and it gives me an error 155, then gives me another error when it tries to recover. Does anyone know how to correct what I apparently messed up? Sometimes some of the instructions are filled with lingo that i don't quite understand, but i can follow directions if they are sufficiently given.
Click to expand...
Click to collapse
Well since you are S-on and unlocked you have to relock your bootloader to run ruu files. Fastboot oem lock is the command you run in fastboot. Also with older ruu files they only work with older roms and such. as for newer ones like the ics ruu, ics roms such as meanrom ics v2.6 works with only hboot 1.58 and newer firmware. I understand that sometimes these guides and tutorials are not clear enough. That's why you got to ask questions. We are here to help so you can get the best out of your experience with your evo 3d. I would not rely on sprint techs too much because sometimes they will just tell you to do a factory reset. Your phone should be fine. Just relock your bootloader and run the file from the bootloader screen and everything should be peachy. If you want to flash a custom rom after you do the update just unlock your bootloader again. Flash 4ext recovery for your device and do some research on what roms and kernels are compatible with S-on unlocked bootloaders. Fyi 4ext recovery has this thing called the smart flash option that allows you to flash kernels through their recovery without having to do through fastboot. Or try Joeykrims Flash Gui Image. All in all, gaining s-off is the best route to solve most of your problems and makes it easier to flash roms and kernels. There is a method for gaining s-off with the ics ota and hboot 1.58. Just do your research. Best of luck to you.
Oh yeah don't forget to hit the thanks button if I helped you out at all.
Jsparta26 said:
Your phone should be fine. Just relock your bootloader and run the file from the bootloader screen and everything should be peachy.
Click to expand...
Click to collapse
Which file are you reffering to from the bootloader screen?
When I Vol Down + Power On this is what I see
***RELOCKED***
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
eMMC-boot
May 17 2012,15:06:44
HBOOT
Now that I have relocked the phone it tries to load PG86DIAG.zip (No Image!), PG86DIAG.nbh (No Image!), PG86DIAG.zip (No Image or wrong image!), PG86IMG.zip, and then it does "Checking..[PG86IMG.zip]" and returns Main Version is Older! Update Fail! Press <Power> to reboot.
I know several of the tutorials and even the "How to Fix" guides I was trying to use to restore the phone has me copy PG86IMG.zip to the sdcard root, so I am guessing I need a different image. Now the only problem is that I have to re unlock the phone so I can "fastboot boot cwm-4.0.1.4-shooter.img" so that I can mount the phone and transfer files to and from it (unless there is another method I can use other than adb, because it does not see it as an attached device)
So what I should do is:
1, Unlock the phone again
2, fastboot boot cwm-4.0.1.4-shooter.img
3, Mount the phone, and copy a file named "PG86IMG.zip" (Which I need to obtain the correct one)
4, Unmount the phone and then relock it?
What would the next step be and do you know where I can get the correct file?
I appreciate the response, I am at my wits end and was about to go waste some cash buying a new phone.
joebandli said:
What would the next step be and do you know where I can get the correct file?
I appreciate the response, I am at my wits end and was about to go waste some cash buying a new phone.
Click to expand...
Click to collapse
Forget about PG86IMG.zip files. Since you are S-ON they have to be signed by HTC and there are very few of those around.
You need the 2.89 RUU.exe from one of the links in this post. Flash that from Windows, then HTC unlock again and follow the guides to flash a custom recovery and then root the stock ROM or a rooted custom ROM.
ramjet73
ramjet73 said:
Forget about PG86IMG.zip files. Since you are S-ON they have to be signed by HTC and there are very few of those around.
You need the 2.89 RUU.exe from one of the links in this post. Flash that from Windows, then HTC unlock again and follow the guides to flash a custom recovery and then root the stock ROM or a rooted custom ROM.
ramjet73
Click to expand...
Click to collapse
Thank a ton, that worked to put my phone back to "working" icecream sandwich.

Cannot re-load stock OS, please help!

Ok, I will try to give as much info as I can, please let me know if there is anything else I should provide. I really appreciate any help and advice as I've been pulling my hair out for the last 3 days, spending 10+ hours trying to get my Amaze back working.
Problem started a few days ago, phone shut off, when it powered back on it was stuck on the White HTC logo. That same day the phone died completely and would not power on at all, not even the amber light. Eventually the amber light would blink the but phone wouldn't charge. I fixed this first issue by jump starting the battery with a 9V battery, something someone suggested on a thread. Worked great to get the phone charging again... but that's it. So basically I have access to the HBOOT/Fastboot and EXT4 Recovery menu's, and there is no OS on the phone, I know for sure now because I wiped the system.
When I try (but fail) to install the RUU 1.41 exe, and it checks the phone, i comes back saying my "current" version on the phone is 2.14.661.2 even though there isn't any OS on there...
Bit more background info. I purchased this phone last year off someone, it was running 4.1.2 and the bootloader was unlocked. It *is S-ON though.
Whatever else this guy did, I'm not sure as this is what I can tell, however the CID pulls up as Telus001? which the guy did tell me it was a Telus phone.
So I'm trying to load the Telus stock rom and I've been getting nowhere and pulling my hair out. I'm 10hrs in and no further then I was. So first I downloaded the Telus RUU 1.41 exe from the stock rom but it gives an Error 43. I tried this with both the bootloader locked again, and unlocked. I then downloaded the OTA 2.14.661 zip from the stock roms, and renamed it to PH85IMG, stuck that on the Ext SD card. Problem is when it boots into the HBOOT it actually see's the file, loads it, then checks it, but then returns me to the main menu. I don't get promted to update. Now I've tried this too with the bootloader unlocked, and locked. So a third go, I extracted the Rom from the 1.41 RUU and made that PH85IMG, tossed it onto the SD card and again this time it actually went further but gave another error.
I have tried to Sideload the above Roms through recovery but they give error's.
In that All In One program there is an option to fix the Mainver error, however when I run that all I get is "Device not found". The phone IS loaded under device manager as HTC Phone as I had installed the drivers. I've tried to google this fix but I can't get anywhere.
Everyone has said on forums that sticking a PH85IMG.zip file on an Ex SD and having it boot into the HBOOT menu will rebuild the phone, but I'm out of idea's how to get there because it loads the rom's, checks them, and then boots me back to the menu. There is only 2 Rom's I can find for Telus, and that's the 1.41 EXE or the OTA 2.14.661.2. My HBOOT version is 1.93.0002, RUBY PVT SHIP S-ON RL.
Thanks in advance for any help/suggestions, desperately just want my phone working again. I feel like I've been to the 4 corner's of google trying to solve this problem.
Strange This should not happen.Also if your phone is running 4.1.2 which should be a custom then that means your phone was updated to ics so the ruu.exe will fail.if you have access to 4ext recovery then you can flash any custom rom to boot your phone.But if you want stock and both of the stock roms for your carrier is not working then the only thing you can do is s-off the phone then use supercid so you can flash any carrier's rom then flash t-mobile ics stock.Tell me if this worked for you.
darkshadow1997 said:
Strange This should not happen.Also if your phone is running 4.1.2 which should be a custom then that means your phone was updated to ics so the ruu.exe will fail.if you have access to 4ext recovery then you can flash any custom rom to boot your phone.But if you want stock and both of the stock roms for your carrier is not working then the only thing you can do is s-off the phone then use supercid so you can flash any carrier's rom then flash t-mobile ics stock.Tell me if this worked for you.
Click to expand...
Click to collapse
Got it going!! Thanks for the suggestions. What did it in the end was this thread --> http://forum.xda-developers.com/showpost.php?p=27058110
I had EXT4 Recovery already, so I used his Zip and just flashed that. Phone came back up and is running great now... if only I had found his thread before the hr's and hr's I've been googling and trying things.

Categories

Resources