Hey all,
I have this HTC EVO 3D that just, refuses to co-operate with me.
Story goes -
Got it on ICS and everything was working fine on it. I looked for updates available and it found a 28MB update that I installed and once the phone rebooted with the update, the camera fails to start and the touch screen just starts going crazy and opening everything, whereas before it fine.
So, I attempted to try and get it back to Gingerbread.
And googled and googled and googled.
Reason why I have opened a new thread is cause it's sort of everything going weird with it.
Of course, trying RUU files and trying to flash RUU in zip failed so on so forth.
I had unlocked the Bootloader and S-ON is on at this point. Also had CWM recovery installed and was able to boot into that.
With this in place, I read up on the wire trick and thought, yeah it seems a bit hard, I'll take it to a phone repair shop, where they had the phone for 2 weeks and told me that it was S-OFF and back to stock.
Since they had it and I got it back, it's now stuck in a boot loop and I can not get into any recovery etc (With the original SD Card in it). Can get to Bootloader and fastboot though.
Spent the last 3 hours with about 20 tabs in Chrome opened on how to exactly go from here and I am stuck.
Got a Linux Laptop here and tried to ControlBear and it comes up with ADB and Fastboot not found (Directory points to it being in tmp..no idea)
TL;DR
HTC Evo 3D (Australian Variant, was running ICS Telstra OEM)
Unlocked Bootloader
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.53.0007
eMMC-boot
Radio - 11.25.3504.16 M
Boot Loops, No Recovery, Fastboot commands work on windows.
So just wondering, where do I go from here. I don't know if the device is completely bricked now or if it can be saved.
(I tried a number of zip files on the SD Card (PG86IMG.zip) and nothing due to having S-ON.
Hoping someone can provide a procedure or point me in the right direction.
As reference, I used this thread mostly before it was taken to the Repair Shop and got stuffed.
Any help is appreciated.
Thanks so much.
skylirizm said:
Hey all,
I have this HTC EVO 3D that just, refuses to co-operate with me.
Story goes -
Got it on ICS and everything was working fine on it. I looked for updates available and it found a 28MB update that I installed and once the phone rebooted with the update, the camera fails to start and the touch screen just starts going crazy and opening everything, whereas before it fine.
So, I attempted to try and get it back to Gingerbread.
And googled and googled and googled.
Reason why I have opened a new thread is cause it's sort of everything going weird with it.
Of course, trying RUU files and trying to flash RUU in zip failed so on so forth.
I had unlocked the Bootloader and S-ON is on at this point. Also had CWM recovery installed and was able to boot into that.
With this in place, I read up on the wire trick and thought, yeah it seems a bit hard, I'll take it to a phone repair shop, where they had the phone for 2 weeks and told me that it was S-OFF and back to stock.
Since they had it and I got it back, it's now stuck in a boot loop and I can not get into any recovery etc (With the original SD Card in it). Can get to Bootloader and fastboot though.
Spent the last 3 hours with about 20 tabs in Chrome opened on how to exactly go from here and I am stuck.
Got a Linux Laptop here and tried to ControlBear and it comes up with ADB and Fastboot not found (Directory points to it being in tmp..no idea)
TL;DR
HTC Evo 3D (Australian Variant, was running ICS Telstra OEM)
Unlocked Bootloader
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.53.0007
eMMC-boot
Radio - 11.25.3504.16 M
Boot Loops, No Recovery, Fastboot commands work on windows.
So just wondering, where do I go from here. I don't know if the device is completely bricked now or if it can be saved.
(I tried a number of zip files on the SD Card (PG86IMG.zip) and nothing due to having S-ON.
Hoping someone can provide a procedure or point me in the right direction.
As reference, I used this thread mostly before it was taken to the Repair Shop and got stuffed.
Any help is appreciated.
Thanks so much.
Click to expand...
Click to collapse
Hello my friend, the reason you can't load the pg86img is because you have unlocked bootloader. The fastboot commands could help us a lot, did you follow the controlbear instructions in the correct order? I think there is a way through windows with exe files I don't remember well because I did S-OFF 3years+ before. If you want we can try together some time. If you want for start we can flash 4ext recovery and a custom rom so your phone can boot.
mhnx said:
Hello my friend, the reason you can't load the pg86img is because you have unlocked bootloader. The fastboot commands could help us a lot, did you follow the controlbear instructions in the correct order? I think there is a way through windows with exe files I don't remember well because I did S-OFF 3years+ before. If you want we can try together some time. If you want for start we can flash 4ext recovery and a custom rom so your phone can boot.
Click to expand...
Click to collapse
Hi there, I didn't know with having the bootloader unlocked that it would cause any issues, but there you go!
Yeah, if there's a guide to flashing the 4EXT Recovery and a custom rom that would be great!
I have a fair idea of how to do it, but don't want to try anything without having someone of greater knowledge point me in the right direction
Thanks!
Just an update, I did come across a thread to flash 4EXT Recovery onto my Evo 3D.
Put Recovery.img into my platform-tools folder, used the fastboot command, it said sending and OK.
Selected recovery and still boot loops. No idea where to go from here now
skylirizm said:
Just an update, I did come across a thread to flash 4EXT Recovery onto my Evo 3D.
Put Recovery.img into my platform-tools folder, used the fastboot command, it said sending and OK.
Selected recovery and still boot loops. No idea where to go from here now
Click to expand...
Click to collapse
Sorry for being late, I had some problems with my internet connection. Can you boot into recovery? Power button + Vol- and choose recovery, if you can boot tell me first which version you have and second what type of rom you want to have.
mhnx said:
Sorry for being late, I had some problems with my internet connection. Can you boot into recovery? Power button + Vol- and choose recovery, if you can boot tell me first which version you have and second what type of rom you want to have.
Click to expand...
Click to collapse
Hey there,
That's OK, I don't mind the wait, it's all good!
I can boot into Fastboot, but when I choose recovery/factory reset etc, it shows the HTC Logo and then goes into a bootloop.
As for the ROM, I want to get the original GB ROM for it because when I updated it to the latest ICS that's when the camera and touch started to get weird, whereas beforehand it was fine.
So thinking, if I go back down to GB Stock, that it should be all fine again, but I am not too sure on that one.
Thanks!
skylirizm said:
Hey there,
That's OK, I don't mind the wait, it's all good!
I can boot into Fastboot, but when I choose recovery/factory reset etc, it shows the HTC Logo and then goes into a bootloop.
As for the ROM, I want to get the original GB ROM for it because when I updated it to the latest ICS that's when the camera and touch started to get weird, whereas beforehand it was fine.
So thinking, if I go back down to GB Stock, that it should be all fine again, but I am not too sure on that one.
Thanks!
Click to expand...
Click to collapse
Well, we have to downgrade the hboot version first. Did you do the wire trick procedure right? You can download a pg86img and flash it first to fix the bootloops. First lock the bootloader. When you finish this report here. I have to sleep it's late here and I work early. I'll send you tomorrow. See you.
mhnx said:
Well, we have to downgrade the hboot version first. Did you do the wire trick procedure right? You can download a pg86img and flash it first to fix the bootloops. First lock the bootloader. When you finish this report here. I have to sleep it's late here and I work early. I'll send you tomorrow. See you.
Click to expand...
Click to collapse
Ok, the technician I took the phone to supposedly did the wire trick for S-OFF, but, it's still S-ON.
I have downloaded a lot of stock PG86IMG files before posting on here and none work, they scan when in bootloader and then nothing after that.
But that would be because I haven't locked the bootloader. So in saying this, I lock the bootloader following steps on many forum posts on here, then flash a .zip file that's correct and then it should all work?
I'll wait for your response, thanks!
skylirizm said:
Ok, the technician I took the phone to supposedly did the wire trick for S-OFF, but, it's still S-ON.
I have downloaded a lot of stock PG86IMG files before posting on here and none work, they scan when in bootloader and then nothing after that.
But that would be because I haven't locked the bootloader. So in saying this, I lock the bootloader following steps on many forum posts on here, then flash a .zip file that's correct and then it should all work?
I'll wait for your response, thanks!
Click to expand...
Click to collapse
I do not think that the wire trick procedure was correct because you are still s on. Lock the bootloader and try to load the zip.
mhnx said:
I do not think that the wire trick procedure was correct because you are still s on. Lock the bootloader and try to load the zip.
Click to expand...
Click to collapse
Hey, so I tried a P86IMG.zip from this thread here - http://forum.xda-developers.com/showthread.php?t=2274635
I couldn't find another one and with that I get an error "Main Version Fail" or "Main Version Check Fail".
I then tried RUU and RUU in zip format.
RUU comes back with wrong bootloader error. (I couldn't find an RUU that matched my radio version so I went with the nearest one)
RUU Zip comes back through fastboot with "remote 43 main version check fail"
Also I tried to do the Wire Trick and got stuck at the "ADB and Fastboot not found" even though the files are there and the phone is connected.
So still a little bit...stuck :\
Also relocked bootloader it just says relocked now.
If you need any other additional info I can send screenshots of what it's at.
Thanks!
skylirizm said:
Hey, so I tried a P86IMG.zip from this thread here - http://forum.xda-developers.com/showthread.php?t=2274635
I couldn't find another one and with that I get an error "Main Version Fail" or "Main Version Check Fail".
I then tried RUU and RUU in zip format.
RUU comes back with wrong bootloader error. (I couldn't find an RUU that matched my radio version so I went with the nearest one)
RUU Zip comes back through fastboot with "remote 43 main version check fail"
Also I tried to do the Wire Trick and got stuck at the "ADB and Fastboot not found" even though the files are there and the phone is connected.
So still a little bit...stuck :\
Also relocked bootloader it just says relocked now.
If you need any other additional info I can send screenshots of what it's at.
Thanks!
Click to expand...
Click to collapse
Did you try flashing the zip after the locking? You are doing the wire trick procedure on live linux cd?
mhnx said:
Did you try flashing the zip after the locking? You are doing the wire trick procedure on live linux cd?
Click to expand...
Click to collapse
Yes, tried flashing the zip after locking. Live CD is being used also. I will try again later. Thanks!
skylirizm said:
Yes, tried flashing the zip after locking. Live CD is being used also. I will try again later. Thanks!
Click to expand...
Click to collapse
If you want we can do the procedure together some time. Keep in mind that you have to unlock again. We can search for the windows version too.
mhnx said:
If you want we can do the procedure together some time. Keep in mind that you have to unlock again. We can search for the windows version too.
Click to expand...
Click to collapse
I have windows version of wire trick procedure. If you need it, I'll gladly share it via PM
donkeykong1 said:
I have windows version of wire trick procedure. If you need it, I'll gladly share it via PM
Click to expand...
Click to collapse
Oh that would be extremely helpful, I can use Linux, but prefer my Windows PC as it has all the files and it's just easier.
Thanks so much!
mhnx said:
If you want we can do the procedure together some time. Keep in mind that you have to unlock again. We can search for the windows version too.
Click to expand...
Click to collapse
donkeykong1 said:
I have windows version of wire trick procedure. If you need it, I'll gladly share it via PM
Click to expand...
Click to collapse
So update -
DK sent me the windows version of ControlBear via PM - thank you.
Have an unlocked bootloader.
I tried ControlBear, and because I can not boot into the OS, I start it at Fastboot USB, it reboots, then says "Connecting to Device", then "Testing ADB connection" then "Press Enter To Exit" and that's it, can't do anything else from there, and it gets stuck in the boot loop that it still has.
Tried again to google for methods for HBOOT 1.53, and am trying some of those methods, but it's not looking good at all.
I haven't even got to the stage where it asks me to do any sort of wire trick.
Also my battery in the EVO 3D has died so am using a battery out of a HTC MyTouch 4G with help from electrical tape :\
So now, any suggestions? I am trying to flash another RUU that's stock for my Radio (Well, it's close enough - RUUs are both 11.25.3504.06, mine is 11.25.3504.16)
EDIT: Tried all RUUs with relocked bootloader and comes back with bootloader error (ERROR 140). So, no idea.
Also it's scanning for PG86DIAG.img files on the SD Card - that's not normal is it.
Do you think we should give up on it, it's probably hard bricked and dead now
I think it's literally hard bricked and no way to bring it back from the dead.
As per my original post, all the details for the phone are there. And it sucks that I can't find a correct RUU for my phone (As it was Telstra AU - latest update of ICS)
AHH I don't know.
skylirizm said:
So update -
DK sent me the windows version of ControlBear via PM - thank you.
Have an unlocked bootloader.
I tried ControlBear, and because I can not boot into the OS, I start it at Fastboot USB, it reboots, then says "Connecting to Device", then "Testing ADB connection" then "Press Enter To Exit" and that's it, can't do anything else from there, and it gets stuck in the boot loop that it still has.
Tried again to google for methods for HBOOT 1.53, and am trying some of those methods, but it's not looking good at all.
I haven't even got to the stage where it asks me to do any sort of wire trick.
Also my battery in the EVO 3D has died so am using a battery out of a HTC MyTouch 4G with help from electrical tape :\
So now, any suggestions? I am trying to flash another RUU that's stock for my Radio (Well, it's close enough - RUUs are both 11.25.3504.06, mine is 11.25.3504.16)
EDIT: Tried all RUUs with relocked bootloader and comes back with bootloader error (ERROR 140). So, no idea.
Also it's scanning for PG86DIAG.img files on the SD Card - that's not normal is it.
Do you think we should give up on it, it's probably hard bricked and dead now
I think it's literally hard bricked and no way to bring it back from the dead.
As per my original post, all the details for the phone are there. And it sucks that I can't find a correct RUU for my phone (As it was Telstra AU - latest update of ICS)
AHH I don't know.
Click to expand...
Click to collapse
First of all you should be unlocked now with 1.53 hboot. Download from here the latest 4ext recovery (4EXT_Recovery_Touch_v1.0.0.6_RC3)
It's in my mega account don't worry about malicious software I downloaded it 5 minutes before doing this post. If you don't have unlocked your bootloader do it with the tokens HTC sent you in your email. Flash this recovery from fastboot (fastboot flash recovery "recoveryname".img). After that remove the battery and re-enter fastboot mode (Vol down+power button) and choose recovery. If you manage to boot into recovery from there tell me to send you a link for a rom to flash. I don't believe its a hard brick.
mhnx said:
First of all you should be unlocked now with 1.53 hboot. Download from here the latest 4ext recovery (4EXT_Recovery_Touch_v1.0.0.6_RC3)
It's in my mega account don't worry about malicious software I downloaded it 5 minutes before doing this post. If you don't have unlocked your bootloader do it with the tokens HTC sent you in your email. Flash this recovery from fastboot (fastboot flash recovery "recoveryname".img). After that remove the battery and re-enter fastboot mode (Vol down+power button) and choose recovery. If you manage to boot into recovery from there tell me to send you a link for a rom to flash. I don't believe its a hard brick.
Click to expand...
Click to collapse
Hey there, thanks for the help again, unfortunately, still didn't work.
I unlocked the bootloader again. Then tried to flash what you said, it said "writing" then "successful". I pulled the battery and tried to boot into recovery and just loops
skylirizm said:
Hey there, thanks for the help again, unfortunately, still didn't work.
I unlocked the bootloader again. Then tried to flash what you said, it said "writing" then "successful". I pulled the battery and tried to boot into recovery and just loops
Click to expand...
Click to collapse
Try doing:
fastboot erase recovery
fastboot flash recovery "recovery".img
fastboot format system
fastboot format boot
And if it still doesn't let me send you a boot.img in some minutes to try flashing it.
EDIT: And something last, you can still do the controlbear trick while not in OS, its easy if you wanna try let me know.
skylirizm said:
Hey all,
I have this HTC EVO 3D that just, refuses to co-operate with me.
Story goes -
Got it on ICS and everything was working fine on it. I looked for updates available and it found a 28MB update that I installed and once the phone rebooted with the update, the camera fails to start and the touch screen just starts going crazy and opening everything, whereas before it fine.
So, I attempted to try and get it back to Gingerbread.
And googled and googled and googled.
Reason why I have opened a new thread is cause it's sort of everything going weird with it.
Of course, trying RUU files and trying to flash RUU in zip failed so on so forth.
I had unlocked the Bootloader and S-ON is on at this point. Also had CWM recovery installed and was able to boot into that.
With this in place, I read up on the wire trick and thought, yeah it seems a bit hard, I'll take it to a phone repair shop, where they had the phone for 2 weeks and told me that it was S-OFF and back to stock.
Since they had it and I got it back, it's now stuck in a boot loop and I can not get into any recovery etc (With the original SD Card in it). Can get to Bootloader and fastboot though.
Spent the last 3 hours with about 20 tabs in Chrome opened on how to exactly go from here and I am stuck.
Got a Linux Laptop here and tried to ControlBear and it comes up with ADB and Fastboot not found (Directory points to it being in tmp..no idea)
TL;DR
HTC Evo 3D (Australian Variant, was running ICS Telstra OEM)
Unlocked Bootloader
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.53.0007
eMMC-boot
Radio - 11.25.3504.16 M
Boot Loops, No Recovery, Fastboot commands work on windows.
So just wondering, where do I go from here. I don't know if the device is completely bricked now or if it can be saved.
(I tried a number of zip files on the SD Card (PG86IMG.zip) and nothing due to having S-ON.
Hoping someone can provide a procedure or point me in the right direction.
As reference, I used this thread mostly before it was taken to the Repair Shop and got stuffed.
Any help is appreciated.
Thanks so much.
Click to expand...
Click to collapse
i have same problem plz give me GB rom link and flash method
---------- Post added at 07:56 AM ---------- Previous post was at 07:42 AM ----------
mhnx said:
First of all you should be unlocked now with 1.53 hboot. Download from here the latest 4ext recovery (4EXT_Recovery_Touch_v1.0.0.6_RC3)
It's in my mega account don't worry about malicious software I downloaded it 5 minutes before doing this post. If you don't have unlocked your bootloader do it with the tokens HTC sent you in your email. Flash this recovery from fastboot (fastboot flash recovery "recoveryname".img). After that remove the battery and re-enter fastboot mode (Vol down+power button) and choose recovery. If you manage to boot into recovery from there tell me to send you a link for a rom to flash. I don't believe its a hard brick.
Click to expand...
Click to collapse
plz help my htc evo 3d is bootloop no go to any recovery mode i flash all recovery
BOOTLOADER-UNLOCK
HBOOT-1.53.0007
RADIO-11.25.3504.06.M
i flash many ruu.exe but this
RUU_SHOOTER_U_ICS_35_S_hTC_Asia_WWE_3.28.707.1_Radio_11.77.3504.00U_11.25.3
flash seccussfully without any error but no booting only htc logo plz help
Related
Backstory: I tried flashing android revolution for the amaze once, and it didn't work (error 1) left it alone for a bit after recovering it, went back to bulletproof and flashed faux .009 kernel, then decided to try again...
Well I'll try to make this brief, sorry if I'm posting in the wrong subforum but here goes, I tried going from bulletproof 2.5.0 to Android Revolution HD and didn't flash the superwipe .zip (lazy me). The install failed with the same error 1, only this time I can't boot back into recovery. Booting to bootloader works but when I tried going into recovery I see it pop up for maybe a fraction of a second before the phone reboots.
I've tried reflashing clockwork mod but no dice
any sort of tips you folks can give me to steer me in the right direction?
Pulsewave said:
Backstory: I tried flashing android revolution for the amaze once, and it didn't work (error 1) left it alone for a bit after recovering it, went back to bulletproof and flashed faux .009 kernel, then decided to try again...
Well I'll try to make this brief, sorry if I'm posting in the wrong subforum but here goes, I tried going from bulletproof 2.5.0 to Android Revolution HD and didn't flash the superwipe .zip (lazy me). The install failed with the same error 1, only this time I can't boot back into recovery. Booting to bootloader works but when I tried going into recovery I see it pop up for maybe a fraction of a second before the phone reboots.
I've tried reflashing clockwork mod but no dice
any sort of tips you folks can give me to steer me in the right direction?
Click to expand...
Click to collapse
Not sure about the Amaze tbh, but if I had a failed flash on either of my HTC phones, I just re RUU'd.
D'oh! I forgot about that! Had to do that for my buddy's thunderbolt a few times. Lemme give that a shot and I'll report back
Edit: Worked
Edit:double post
im also having this problem, my phone keeps freezing at the startup screen when the htc logo pops up. i dont know much about this kind of stuff so i would really appreciated if anyone could guide me to what to do
the way that my phone froze like that was that i tried to flash a kernel for the Energy rom, i did installed the rom itself
http://forum.xda-developers.com/showthread.php?t=1362759 this is the rom that i wanted to use
and i flashed the kernel that was provided in the 4th post, i downloaded that file, extracted and ran the .bat file and thats how it happened
i would appreciate if anyone could help me with this
Bricked Htc Amaze 4g
I have a bricked HTC Amaze 4g. I had beastmod v2.20 on when i decided i wanted quick sense. After i finished it just froze on the htc startup logo. I played with it and got it into a bootloop. When i try to flash a ruu the blue bar loads up and comes back to the bootloader screen. I can get into recovery but it wont let me flash anything.Thanks to whoever replies I really appreciate it.
lmfaoomg said:
im also having this problem, my phone keeps freezing at the startup screen when the htc logo pops up. i dont know much about this kind of stuff so i would really appreciated if anyone could guide me to what to do
the way that my phone froze like that was that i tried to flash a kernel for the Energy rom, i did installed the rom itself
http://forum.xda-developers.com/showthread.php?t=1362759 this is the rom that i wanted to use
and i flashed the kernel that was provided in the 4th post, i downloaded that file, extracted and ran the .bat file and thats how it happened
i would appreciate if anyone could help me with this
Click to expand...
Click to collapse
You need to superwipe the phone and flash the ROM. After the ROM flashes, you have to flash the kernel twice.
samiaziz said:
I have a bricked HTC Amaze 4g. I had beastmod v2.20 on when i decided i wanted quick sense. After i finished it just froze on the htc startup logo. I played with it and got it into a bootloop. When i try to flash a ruu the blue bar loads up and comes back to the bootloader screen. I really appreciate it.
Click to expand...
Click to collapse
Same with you. You need to superwipe the phone and flash the ROM. After the ROM flashes, you have to flash the kernel twice.
Superwiping the phone removes all the data from the old ROM so you can install a fresh clean ROM.
If you want to install the RUU, you have to relock the bootloader first and then you can reflash the original RUU
Edit: i was misinformed
Sent from my NRGized Amaze...
via xda premium
aj_2423 said:
I dont believe u have to relock
Sent from my NRGized Amaze...
via xda premium
Click to expand...
Click to collapse
To flash an official RUU, you must relock it. I've done so plenty of times lol
Sent From My HTC Amaze 4G via Someone's Room
If the phone wont go into recovery, you have to use ADB and wipe the cache partition for it to go into recovery again. This is apparently a bug with some of recoveries posted by other devs in the development forum. You need to use fastboot.exe to wipe the cache via adb
And if... If the superwipe doesn't work due to recovery version you have try to boot in to your Bootloader run one of hasoon's tool and choose different recovery.. it did happen to me the bootloop before due to the fact the old roms like mike's rom. he doesn't update his script to support the newer recoveries and it doesn't support X's recovery, it will give you an error installation.. just try different recoveries and for sure your problem will be solved..
just make sure boot in your bootloader/H-boot then run hasoon's tool and have enough battery just to make sure...
hasoon2000 said:
To flash an official RUU, you must relock it. I've done so plenty of times lol
Sent From My HTC Amaze 4G via Someone's Room
Click to expand...
Click to collapse
Thanks for the good info Sir but i my HTC Amaze is bootloader locked and S-ON but i cannot find a RUU for T-mobile to unbrick it. Will a Ruu such as this one work?
RUU_Ruby_Videotron_CA_1.46.1530.1_R2_Radio_1.09.550L.17DC_30.68.550L.09_release_227343_signed.exe
My HTC Amaze scans all the versions of the PH85IMG i place on the sd card but goes back to the menu when its down
any advice that could help i will appreciate!
There's a thread in the dev section that has about a dozen RUUs. I don't see how one can miss it.
Thanks for your reply but i was a little unsure and did not want to make my phone any worst than it already is.
Can you explain 1 thing thing for me please - RUU always you to flash the phone via the computer? where as PH85img.zip allows you to flash the phone via sdcard? I hope i am correct here.
but i want to know how can i flash the phone when its connected via HBoot usb cause my pc recognizes it as "Android Composite ADB Interface"
Currently this is what is on my lcd
LOCKED
RUBY PVT SHIP S-ON RL
HBOOT-1.93.0002
EMMC BOOT
MAR 15 2012
i have tried several PH85img.zip files but the phone just scans them and goes back to the menu.
Some help will be appreciated extremely.
---------- Post added at 03:40 PM ---------- Previous post was at 03:33 PM ----------
I forgot to mention it connects to the pc but when i run command adb devices this is what i get
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\rquinlan.GOSL_DOM>adb devices
List of devices attached
C:\Documents and Settings\rquinlan.GOSL_DOM>
The latest ruu would be your best option, do not put the .zip part of the name since its already there, also a ruu may be an exe or zip file, since it is a complete stock file to restore the device, what would your carrier be to be exact? Just not up to reading through everything in this thread to see if you mentioned that piece of info, if its tmobile then the very first file in the stock ruu/ota thread would be the file you need.
Sent from my iPad using Tapatalk HD
thanks for your advice i managed to reboot the phone into recovery but heres whats strange to me the phone is in recovery with HTC on the screen thats it, the pc has recognized it as "MY HTC" in the device manager however, when i run the command adb devices this is what i get "SH218vp00163 offline". i ran the RUU file but i get error 170 usb connection.
so i am a bit lost as device manager can see the phone but the RUU file cannot and i am plugging the phone into the rear of the pc.
any ideas
Linkzz said:
thanks for your advice i managed to reboot the phone into recovery but heres whats strange to me the phone is in recovery with HTC on the screen thats it, the pc has recognized it as "MY HTC" in the device manager however, when i run the command adb devices this is what i get "SH218vp00163 offline". i ran the RUU file but i get error 170 usb connection.
so i am a bit lost as device manager can see the phone but the RUU file cannot and i am plugging the phone into the rear of the pc.
any ideas
Click to expand...
Click to collapse
Why are you using recovery exactly?
RUU's are to be flash via hboot, which is the very first screen you see when you go into the device's bootloader, in the case of exe files, you'll need to flash it via fastboot mode, which happens to be, correct me if I'm wrong, the very first or second option on the hboot menu.
yes you are correct cause i just tried it with an RUU from another carrier. i found out that the phone had 2.14.531 software installed. but the RUU i was using was 1.46 and so i got a signature error 132. now i need to find a way to remove the 2.14.531 software and replace it with a lower version. can you help me here
Linkzz said:
yes you are correct cause i just tried it with an RUU from another carrier. i found out that the phone had 2.14.531 software installed. but the RUU i was using was 1.46 and so i got a signature error 132. now i need to find a way to remove the 2.14.531 software and replace it with a lower version. can you help me here
Click to expand...
Click to collapse
What carrier are you on?
t-mobile
this is the RUU i tried and made a connection but the PH85img.zip are not working no matter how i try
RUU_Ruby_Videotron_CA_1.46.1530.1_R2_Radio_1.09.55 0L.17DC_30.68.550L.09_release_227343_signed.exe
Gave my Evo 3d to my borother a few months back, but hes come back to me today saying it was stuck in bootloop.
He booted into the bootloader and did a factory reset, but it was still stuck in bootloop.
I tried to get into recovery to flash a new rom, but when i select recovery from the bootloader, that also goes into a bootloop.
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Not sure if its important but the phone is s-off. Any ideas on whats going on or how to fix?
Apologies, supposed to put this in Q&A forum
While you're at bootloader, connect USB and then flash a stock RUU.
androidcdma said:
While you're at bootloader, connect USB and then flash a stock RUU.
Click to expand...
Click to collapse
Thanks for the reply. Will i lose s-off with this?
Tones1971 said:
Gave my Evo 3d to my borother a few months back, but hes come back to me today saying it was stuck in bootloop.
He booted into the bootloader and did a factory reset, but it was still stuck in bootloop.
I tried to get into recovery to flash a new rom, but when i select recovery from the bootloader, that also goes into a bootloop.
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Not sure if its important but the phone is s-off. Any ideas on whats going on or how to fix?
Apologies, supposed to put this in Q&A forum
Click to expand...
Click to collapse
You didn't say what version of the Evo 3D you have (CDMA or GSM) or what bootloader is installed, but if it's a Sprint CDMA model I would recommend flashing the Sprint ICS RUU.exe from Windows after putting the phone into fastboot mode in the bootloader. You may have to relock the bootloader with the "fastboot oem lock" command first if it shows "***UNLOCKED***" at the top of the screen.
That will fix a lot of problems, especially when the phone is in an indeterminate state. After flashing the RUU you can HTC unlock, flash a custom recovery and then root the stock ROM or flash a rooted ROM.
ramjet73
Sorry it is a UK GSM (Europe). I have revolutionary bootloader installed. Got an RUU to try now thanks.
androidcdma said:
While you're at bootloader, connect USB and then flash a stock RUU.
Click to expand...
Click to collapse
Tones1971 said:
Thanks for the reply. Will i lose s-off with this?
Click to expand...
Click to collapse
^^^^ He got it first with the short version.
No, you won't lose S-OFF and won't need to relock the bootloader first if that's your current status.
And if it's a GSM model everything still applies, you just need a different RUU, which you already have.
ramjet73
Thanks ramjet. Thought this was going to be straightforward but cant get ruu to install. Error 170. Ill keep plugging away / googling away, hopefully come up with something
Tones1971 said:
Thanks ramjet. Thought this was going to be straightforward but cant get ruu to install. Error 170. Ill keep plugging away / googling away, hopefully come up with something
Click to expand...
Click to collapse
Error 170 means that the RUU utility can't find the phone. There's a readme.doc for running the RUU here, and the error codes are towards the end of that.
Are you putting it into "fastboot" mode in the bootloader, which should change to "fastboot usb" when it is connected to a computer? You also need to have the HTC USB drivers active, which can be accomplished by installing HTC Sync.
ramjet73
Tones1971 said:
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Click to expand...
Click to collapse
adb push into a bootlooping phone?
do you have the drivers for the phone? (if not download and install HTC Sync as they come with it)
did you try flashing a custom recovery img through fastboot? (go to bootloader select fastboot, connect USB, type "fastboot flash recovery nameOfYourRecoveryImg.img")
Yeah have tried installing custom recovery through fast boot again, and im in fastboot ok when trying to run the RUU. Also have HTC Sync installed from when i had the phone.. Drivers seemed to be ok as i was able to install the custom recovery with adb, alhough i still got bootloop after that.
Ive a few other things to try when i get home from work. Im sure it shouldnt be too difficult to resolve. Hopefully anyway.
Well this isnt going smoothly at all. Used another PC and was able to get the RUU to run.
However it now comes up with Error 131 Customer ID problem. The RUU was for HTC Europe (non branded). The phone was sim free. When i posted months back my cid was HTC_001. I checked it here: http://forum.xda-developers.com/showpost.php?p=22394863&postcount=172
However now when i get my CID it is showing as CID0202. Any way i can get an RUU to install? Any idea how a CID could change?
EDIT: noticed i used a different command last time.
fastboot getvar cid shows CID0202
adb shell getprop ro.cid now shows device not found (previously showed CID_001)
Thats typing both commands in same window, one after the other. One gets CID0202, the other device not found???
There's a change cid command in fastboot, fastboot oem writecid or something along those lines... however i believe the cid check is in the updater scripts of the ruu in which case a fastboot flash of all the img files should avoid it entirely... i don't remember the procedure for extracting the img files from the ruu but i believe ur supposed to run it and then dig through your temp files...
dessolator666 said:
There's a change cid command in fastboot, fastboot oem writecid or something along those lines... however i believe the cid check is in the updater scripts of the ruu in which case a fastboot flash of all the img files should avoid it entirely... i don't remember the procedure for extracting the img files from the ruu but i believe ur supposed to run it and then dig through your temp files...
Click to expand...
Click to collapse
Thanks for this. Ill see if i can find anything else out about it. So saves running the RUU exe and no cid check done then?
Need to bump this as im not getting anywhere. No RUU's will install, error 31 customer error. Have flashed recovery via ADB and through PG86IMG.ZIP, but still cant get in to recovery as it just continually reboots.
S-OFF with revolutionary. Anybody any ideas please?
Got bigger problems than i thought. Finally got an RUU to install after 4 days of trying, by first using fastboot oem writecid 11111111. But when the phone rebooted it was back bootlooping again. Is there any hope for my phone?
Tones1971 said:
Got bigger problems than i thought. Finally got an RUU to install after 4 days of trying, by first using fastboot oem writecid 11111111. But when the phone rebooted it was back bootlooping again. Is there any hope for my phone?
Click to expand...
Click to collapse
You need to stop cross posting in the d3rp Q&A thread and your own thread if you want more help. Cross-posting is stongly discouraged on XDA and it's really confusing when you are asking for help in one thread while getting different advice in another.
It sounds to me like all the CID changes on your phone have left it in an indeterminate state and I'm not sure at this point what is the correct CID and RUU for your model. If you could detemine that, set the CID correctly and flash the right RUU the phone should work, but it might be too late if you have in fact been flashing firmware that doesn't match your phone because the right RUU may not back that out properly.
That's all I can offer at this point, but since I don't know the history of your phone and how it got the various CID's you have reported, you will probably be the one that needs to figure it out.
ramjet73
Hi folks,
I have a HTC Evo 3D from the UK bought sim free, rooted it with s-on and tried to install a rom with 4ext, got stuck in bootloop, tried clearing cache but it never worked, tried a few different roms (not the best idea) and failed loads, the back up I used successfully before stopped working and in a mad attempt to get anything working I managed to stop 4ext as the recovery and its now CWM Recovery v4.0.1.4. It doesnt boot loop it just stays on the HTC screen without doing anything else.
Is there anything I can do?
I have tried the shipped RRUs but run into an error each time, probably since I am just guessing at which I am supposed to be using, is there a way to figure it out? Or a rom/cwm way or a way of getting another backup/restore file?
Any help is very much appreciated, I shouldnt have been allowed the USB cable! lol
Thanks
Paul
ScottishPaul88 said:
Hi folks,
I have a HTC Evo 3D from the UK bought sim free, rooted it with s-on and tried to install a rom with 4ext, got stuck in bootloop, tried clearing cache but it never worked, tried a few different roms (not the best idea) and failed loads, the back up I used successfully before stopped working and in a mad attempt to get anything working I managed to stop 4ext as the recovery and its now CWM Recovery v4.0.1.4. It doesnt boot loop it just stays on the HTC screen without doing anything else.
Is there anything I can do?
I have tried the shipped RRUs but run into an error each time, probably since I am just guessing at which I am supposed to be using, is there a way to figure it out? Or a rom/cwm way or a way of getting another backup/restore file?
Any help is very much appreciated, I shouldnt have been allowed the USB cable! lol
4ext recovery is the choice for s-on users so using cwm is a bad idea. You maybe experiencing bootloops on 4ext because you may have not had smartflash enabled. S-on users cannot flash kernels through normal means through recovery like s-off users can. With smartflash this is possible. So my suggestion is to reflash 4ext through fastboot and enable it if you havn't done so and do a full wipe of your phone and reflash your rom and see if that work. As for the ruu's. You have to have your bootloader relocked to flash them. You can flash them through bootloader if they were signed by htc but if not, you will have to run the ruu exe on your pc which still ofcourse needs the bootloader to be relocked.
Click to expand...
Click to collapse
Thanks for the reply,
I'm trying to get 4ext running, I've tried fastboot flash recovery recovery.img and then boot recovery.img but all I get is the HTC screen with no recovery program now :S
Ta
Paul
Did you type the command with the exact name of your recovery file in your folder? Also do you have HTC sync installed? If so uninstall it. It will interfere with fastboot.
Jsparta26 said:
Did you type the command with the exact name of your recovery file in your folder? Also do you have HTC sync installed? If so uninstall it. It will interfere with fastboot.
Click to expand...
Click to collapse
Dont have HTC sync. I used the exact name, even using the TAB button to complete the filename
Thanks
Are you sure your bootloader is completely unlocked? Sometimes when you apply the unlock bin code the unlock screen doesn't show up with Ics. What kind of output do you get when you type the fastboot flash recovery command? There might be a clue. Well in any event I'm going to trouble shoot your problem. If you could copy and paste the input and output of your command that will help alot.
---------- Post added at 11:29 PM ---------- Previous post was at 11:15 PM ----------
Edit: let's try to get your phone back on stock and unlocking your bootloader instead. I read your post about how your having trouble flashing ruu. The first question is, is your phone branded or unbranded? Depending on either you will have to find an ruu exe file based on the region and carrier if branded. Just google it up. Next your phone will have to be in relocked state if your bootloader says unlocked. Type fastboot oem lock to relock it. Now you can run the file. Remember you must have the right on or it won't take. Remember after you unlock it again it will erase all your user data. Let me know if you succeed or not and then we can proceed from there. Oh yeah here's a link you might want to read up on about the whole ruu thing http://forum.xda-developers.com/showthread.php?t=1655832
Pretty sure its fully unlocked, I was able to run superSU, install 4ext and busybox etc.
I have got 4ext working again, the problem appears that the two recovery.img files I had tried were not the correct version for my phone, I've got the right one now and can boot into 4ext through the recovery option.
Okay, now try to flash a sense Rom like cool sense and let me know if it boots for you
Jsparta26 said:
Okay, now try to flash a sense Rom like cool sense and let me know if it boots for you
Click to expand...
Click to collapse
Yup its working I used KingCobra3D-ICS, such a great feeling to see it actually boot up for the first time in days! Thanks for all your help, not sure I will even attempt another rom, I think stick with this will be safe lol
Thanks
Paul
Hi,
I have a Sprint CDMA HTC EVO 3D. I tried root and get S-OFF for it. Unfortunately I failed and now the phone fail to boot.
Below is what I did from which you might be able to diagnose it and give me suggestions.
(1) The original status of mu phone is:
Stock rom, I never root it before.
HBOOT-1.58.0000
Android Version: 4.03
HTC Sense version: 3.6
Software version: 2.95.651.6.710RD
(2) My root procedures:
I followed this post: http://forum.xda-developers.com/showthread.php?t=1813818
I successfully unlocked phone with HTCDev, successfully Flashed 4EXT recovery, and successfully installed Superuser-3.1.3-arm-signed.zip. I also booted into sytem, everything worked well.
However I failed in next step of JuopunutBear's Wire Trick (S-OFF). When I ran ControlBear.exe, it finally hanged there.
Current status of my phone:
Unfortunately I did not make a backup to my original ROM, so there is no way to revert back by restoring backup.
Now the phone is in unlocked status, I was able to boot to HBOOT and also enter 4Ext recovery, however I am not able to boot into Android. If I try to boot into Android, it always hang at black screen.
I am able to boot to fastboot (USB) mode, I tried to flash some stock ROM (listed at http://forum.xda-developers.com/showpost.php?p=24268786&postcount=209), but I failed. For example, I ran a RUU of 2.89.exe, it detected my phone version is 2.95, and further update RUU failed.
Looks like my partition is ruined, but I might be wrong.
ANyone can help me to restore my phone to working status? At least I need the phone to be able to boo to Android.
Here are also some tries that I ever did:
(1) I ever put the PG86IMG.zip file (downloaded from http://forum.xda-developers.com/showpost.php?p=21593454&postcount=564) to my sdcard, still failed.
(2) I ever formatted all partition from 4EXT recovery
lsdyna said:
Here are also some tries that I ever did:
(1) I ever put the PG86IMG.zip file (downloaded from http://forum.xda-developers.com/showpost.php?p=21593454&postcount=564) to my sdcard, still failed.
(2) I ever formatted all partition from 4EXT recovery
Click to expand...
Click to collapse
EDIT:
Okay. I've got some questions.
1. You're stuck on some black screen as you said. It boots past the white HTC splash and then it's stuck on that black screen, right. Do you mean the juopunutbear "arrow screen" - juopunutbears boot.img?
2. I think if you had flashed the original boot img everything would have been fine.
3. The easiest way is to flash to stock, so lets try to figure out why it doesn't flash.
MrJyrks said:
Okay. So from what I understood, you are stuck on the black juopunutbear screen, right?
Click to expand...
Click to collapse
Yes, after I was stuck with black juopunutbear screen, I took battery out, reboot again, never was able to root to Android. I am only able to boot to HBoot.
lsdyna said:
Yes, after I was stuck with black juopunutbear screen, I took battery out, reboot again, never was able to root to Android. I am only able to boot to HBoot.
Click to expand...
Click to collapse
And you can boot to recovery, right?
EDIT:
One more thing. Which ruu were you trying to run
Edit2:
What's your CID? Use "fastboot getvar cid" or "fastboot oem readcid" (without quotes).
Edit3:
BTW, this was on the wire trick page... http://unlimited.io/jbtroubleshooting.htm - TROUBLESHOOTING There was everything you needed to know when you failed at something. Remember that page. You may need it the next time you try to do the wiretrick.
Q: Were you using a linux distro for the wire trick and did you use the appropriate files for wire trick since GB and ICS have separate tools?
If you want I may assist you in gaining s-off if we get this thing functional again.
Yes, I am able to boot to recovery.
I tried ROM's here
http://forum.xda-developers.com/showpost.php?p=24268786&postcount=209
and
http://forum.xda-developers.com/showthread.php?p=22519105#post22519105
I tried 2.17, 2.89, unfortunately none of them worked
My CID is SPCS_001
MrJyrks said:
And you can boot to recovery, right?
EDIT: One more thing. Which ruu were you trying to run
Edit2: What's your CID? Use "fastboot getvar cid" or "fastboot oem readcid" (without quotes).
Click to expand...
Click to collapse
lsdyna said:
Yes, I am able to boot to recovery.
I tried ROM's here
http://forum.xda-developers.com/showpost.php?p=24268786&postcount=209
and
http://forum.xda-developers.com/showthread.php?p=22519105#post22519105
I tried 2.17, 2.89, unfortunately none of them worked
My CID is SPCS_001
Click to expand...
Click to collapse
Aw man, I'm completely sorry I didn't see this: Software version: 2.95.651.6.710RD
That means, no RUU for you cause htc/sprint wasn't kind enough to provide the ruu. Also FYI you can't flash a ruu lower than your current one.
So your best bet is to flash the most stock 2.95 cdma rom you could find and right after, flash the stock cdma evo 3d kernel through fastboot or 4ext (I think 4ext smartflash does the same thing). Try to find something that's COMPLETELY STOCK - with no mods whatsoever or if you couldn't find any, try something that's almost* stock. That should get you booting and you can try s off again.
Edit: This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Now I only want to revert my phone to stock, not considering root at present time.
I searched 2.95 ROM, unfortunately the highest version that I can find is 2.89. Does this mean I have no way to revert my phone to live? Thanks a lot.
MrJyrks said:
Aw man, I'm completely sorry I didn't see this: Software version: 2.95.651.6.710RD
That means, no RUU for you cause htc/sprint wasn't kind enough to provide the ruu. Also FYI you can't flash a ruu lower than your current one.
So your best bet is to flash the most stock 2.95 cdma rom you could find and right after, flash the stock cdma evo 3d kernel through fastboot or 4ext (I think 4ext smartflash does the same thing). Try to find something that's COMPLETELY STOCK - with no mods whatsoever or if you couldn't find any, try something that's almost* stock. That should get you booting and you can try s off again.
Click to expand...
Click to collapse
I ever run a RUU 1.13...exe for mmy phone, it said my device is having 1.000, and it tried to update to 1.13. However, the update procedure always failed at some point, some at beginning, some failed at 'wring signature'...
MrJyrks said:
Aw man, I'm completely sorry I didn't see this: Software version: 2.95.651.6.710RD
That means, no RUU for you cause htc/sprint wasn't kind enough to provide the ruu. Also FYI you can't flash a ruu lower than your current one.
So your best bet is to flash the most stock 2.95 cdma rom you could find and right after, flash the stock cdma evo 3d kernel through fastboot or 4ext (I think 4ext smartflash does the same thing). Try to find something that's COMPLETELY STOCK - with no mods whatsoever or if you couldn't find any, try something that's almost* stock. That should get you booting and you can try s off again.
Click to expand...
Click to collapse
lsdyna said:
I ever run a RUU 1.13...exe for mmy phone, it said my device is having 1.000, and it tried to update to 1.13. However, the update procedure always failed at some point, some at beginning, some failed at 'wring signature'...
Click to expand...
Click to collapse
This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Flash like a normal rom and don't forget to flash the boot img because that's what's really causing you problems right now. I'd choose the deodexed one from there.
My HBoot screen shows below:
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.000
RADIO-1.09.00.0108
OpenADSP-v02.6.0.2226.00.0217
DO you think I still have chance to save my device? Thanks a lot.
lsdyna said:
I ever run a RUU 1.13...exe for mmy phone, it said my device is having 1.000, and it tried to update to 1.13. However, the update procedure always failed at some point, some at beginning, some failed at 'wring signature'...
Click to expand...
Click to collapse
lsdyna said:
My HBoot screen shows below:
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.000
RADIO-1.09.00.0108
OpenADSP-v02.6.0.2226.00.0217
DO you think I still have chance to save my device? Thanks a lot.
Click to expand...
Click to collapse
If you have access to the recovery, most likely, yes.
Hello MrJyrks,
Thank you so much for the link! I am eager to try that. Before I do that I think I shall ask two questions to avoid further mess up the device:
Question #1: To install the deodexed rom, which is the correct way:
(1) Rename the ZIP file to PG86IMG.ZIP, put to root of sdcard, then boot, letting the Bootloader to do the update.
(2) In 4EXT recovery, enable smartflash, enable script asserts, then install the zip from the root of sdcard.
Question #2: You said I shall flash boot image, can you tell me how to do this? I mean, where shall I get the boot image file? Flash it with 4EXT? SHall I do it before or after install ROM zip file?
Thank you very much for your helps!!!
MrJyrks said:
This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Flash like a normal rom and don't forget to flash the boot img because that's what's really causing you problems right now. I'd choose the deodexed one from there.
Click to expand...
Click to collapse
I tried install the stock ROM from your link (using 4EXT with smartflash enabled and script asserts enabled.) . Amazing that installation completed successfully (indeed this is the first ROM zip that I was able to install successfully since I mess up the device). When I exit After that, it did some further update which I guess is the boot.img that you mentioned.
4EXT it said 'a pending update for your boot partition is detected' and I think it was doing the boot image flash that you mentioned, right?
Unfortunately when I boo the device, I still got black screen.
Now I am unlocked and also rooted (since I successfully installed superuser in 4EXT). DO you think I shall lock the devioce before installing the stock ROM? If so, one possible issue is that if I relock the device, I found 4EXT is not available. In that case, how shall I install the ROM zip file?
Thanks.
MrJyrks said:
This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Flash like a normal rom and don't forget to flash the boot img because that's what's really causing you problems right now. I'd choose the deodexed one from there.
Click to expand...
Click to collapse
Further update:
I flashed boot image by: fastboot flash boot boot.img which is included in the stock ROM zip file.
The flash went successfully. However, I am still not able to boot to Android. WHat I have is the device hang there, alternatively displaying logo with white background, and black screen.
MrJyrks said:
This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Flash like a normal rom and don't forget to flash the boot img because that's what's really causing you problems right now. I'd choose the deodexed one from there.
Click to expand...
Click to collapse
I wiped cache and Dalvic, then re-flash the ROM, now I am able to boot as normal.
MrJyrks, you are my life save!!!
Your helps are sincerely appreciated !
lsdyna said:
I wiped cache and Dalvic, then re-flash the ROM, now I am able to boot as normal.
MrJyrks, you are my life save!!!
Your helps are sincerely appreciated !
Click to expand...
Click to collapse
You're welcome! I'm glad I could help!
---------- Post added at 12:02 PM ---------- Previous post was at 11:16 AM ----------
Oh, and if, in the future, you do try the wire trick and get stuck at some point you can revert the changes with ControlBear -r or ControlBear -f from command line. And you may also PM me if you need any help. Cheers!
MrJyrks, thank you so much!!!
MrJyrks said:
You're welcome! I'm glad I could help!
---------- Post added at 12:02 PM ---------- Previous post was at 11:16 AM ----------
Oh, and if, in the future, you do try the wire trick and get stuck at some point you can revert the changes with ControlBear -r or ControlBear -f from command line. And you may also PM me if you need any help. Cheers!
Click to expand...
Click to collapse
Similar problem, can't return to stock
I have a problem similar to lsdyna's, and am hoping that even though this post is old, MrJyrks or someone might be able to help me.
I am unsuccessfully trying to return my phone to stock. First a bit of history.
I had 2.95.651.6.710RD s-on hboot 1.58 Android Version: 4.03 HTC Sense version: 3.6 on my phone, and wanted root. I didn't need s-off, just wanted to root so could do some tweaking (stop some apps from autostarting, stop some form getting network access, etc.) so loaded 4EXT Recovery Touch, and got root (fastboot oem get_identifier_token method), got superuser in there, and happily began tweaking. Famous last words... I didn't make a backup right away (learned my lesson!) and suddenly found a 'overtweaked' sluggish phone on my hands.
Thought best thing would be to lose the root & return to stock & start over, carefully, making backups.
So I used Fastboot (fastboot oem lock) to lock it (worked) and proceeded to try to load RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe into it [via my computer], but didn't realize until reading MrJyrks post that a lower RUU couldn't be used.
I now am relocked (phone does boot up, but can tell the system tweaks are still slogging it), lost the recovery, and wondering what to do... do I try putting recovery back in & using the Negalite 2.95 stock deodex ROM MrJyrks mentioned? If so, how do I use that zip file method verses the exe one I tried thru my computer?
Thanks for the help
You had issues with the RUU because your main version is higher than that contained in the RUU.
Unlock, flash recovery again. Boot into recovery and flash this zip: https://copy.com/wlVvwssXXNN00Pe
That will lower your main version. Relock the bootloader, put the phone into fastboot USB mode, then run the RUU while in fastboot USB mode.
Should be back to stock after that.
hello every one, like alot of you guys i was stuck on white HTC Screen and only able to get to HBOOT and Fastboot, after a lot of Effing research over google and xda, almost a month an a thousand post with the same problem Finally Solved-it!!! im pretty sure it will work on your forgotten devices soooo. first of all i didnt uploaded the file just find it messing arround the web so all tanks go for those who uploadit.
an some months after a friend let me his phone with similar problems and got solved the same way.
booth phone were with lastest HBOOT 2.28.!! aln lastest radio.!
Attention.!! Im not responsable for any more DAMAGE or/if it can happen even if you have your phone already briked.. so play responsable..!!
ok. let me be a bit clear, i've got 2 diferent rezound with similar problems and booth got solved the same way
phone 1: Only showed white htc boot logo, and also onle let me acces hboot and fastboot, no recovery(custom or stock).NO BOOT.
phone 2: showed white htc logo,hboot,fastboot and also recovery but it was giving me emmc error an couldnt acces to any partition.
you will need some knowledge in FASTBOOT.!!! look for help over the web.!
STEP BY STEP GUIDE:
1)Fully Charge your Battery.!
2)Download this file-----> it have Hboot 2.28 and Radios 2.23 at: http://d-h.st/BIj http://d-h.st/BIj place it in your Fastboot folder.!
3)open CMD with Administrative Permitions(right click run as administrator)
4)cd to fastboot folder
5)put device in Fastboot mode(turn on pressing power + vol.down, then select fastboot).
5.1)if hboot unlocked relockit with fastboot oem lock, will reboot phone and show RELOKED.
6)run: fastboot oem rebootRUU. phone will reboot again and show Black Screen with HTC.
7)run: fastboot flash zip Firmware.zip (firmware.zip should be the file you downloaded in step 2!).
8)if everything goes well you will see a green bar moving on your phone and fastboot should start working and showing some files flashing i dont know hahaha.
9) wait it takes about 5 mins. when your cmd window shows that it finish, your phone will still have a green bar on it. just run
fastboot reboot
and the magic its done.!! wait other five mins for the phone to boot and start messing with it again.!!!
will attach a picture with my cmd windows if someone got lost.!try to figure them out hahah those are the things i saw all my files were on downloads but i already have fastboot preinstaled.
as i said before i hope this mini tutorial works for you guys. it will be cool if people in the forum put this as stickie.!! i've seen like a 1000 post with the same problem.!!
have fun.!!
Be VERY careful if you have custom recovery installed (TWRP/CWM/PhilZ/AmonRa), locking or re-locking the bootloader well S-ON can result in a hard brick situation.
acejavelin said:
Be VERY careful if you have custom recovery installed (TWRP/CWM/PhilZ/AmonRa), locking or re-locking the bootloader well S-ON can result in a hard brick situation.
Click to expand...
Click to collapse
In my situations one never entred in recovery and the other one didnt show any problem.
acejavelin said:
Be VERY careful if you have custom recovery installed (TWRP/CWM/PhilZ/AmonRa), locking or re-locking the bootloader well S-ON can result in a hard brick situation.
Click to expand...
Click to collapse
I know but this is the only solution ive founde wirh my two problems and i think theres nothing to loosenif your phone is already bricked trust me ive try everything with these phones
inchewazu said:
I know but this is the only solution ive founde wirh my two problems and i think theres nothing to loosenif your phone is already bricked trust me ive try everything with these phones
Click to expand...
Click to collapse
I'm not knocking your procedures or process... What I am saying is that if you have custom recovery installed and you relock, there is a definite potential for hard brick, if you are going to relock well S-on with custom recovery, there is a real possibility of bricking... One should flash stock recovery via fastboot prior to relocking.
Sent from my Nexus 4 using Tapatalk
acejavelin said:
I'm not knocking your procedures or process... What I am saying is that if you have custom recovery installed and you relock, there is a definite potential for hard brick, if you are going to relock well S-on with custom recovery, there is a real possibility of bricking... One should flash stock recovery via fastboot prior to relocking.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
well i guess you'r right so hope that doesnt happens to anyone around, well by the way probably no one uses this phone any more but tanks for pointing that important info.