Here's my situation. Got this new phone yesterday. I am (was) bootloader unlocked, s-on with htcdev method. Also am (was) using twrp for recovery. Then went looking for some roms... found one, moved it to the phone, wipe, blah, blah, done this before plenty on my old evo shift. Well, there was some problem, rom couldn't be installed, which is no problem for people who do regular nand backups. That was not me. So... stuck at htc screen.
Bottom line, after many hours of different ideas and methods, I've relocked the bootloader, downloaded an ruu, and I'm stuck. In hindsight I sort of backed myself into a corner, because though I supposedly needed to relock to run an ruu, now I can't get at twrp recovery. So I need help running the ruu from fastboot. In my searches, this seems possible, but it's not working for me. The phone is recognized, because when I enter into command "fastboot find devices" or whatever that was, a phone shows up. The .exe itself just won't open though. Tried running as administrator, tried compatibility mode, tried running it from the command line, each time it will give me the blue circley thing for about 5 or 10 seconds and then just do nothing.
I'm just out of ideas, feeling like I'm stuck here.
Remember: currently my screen reads TAMPERED RELOCKED Security Warning I'm in fastboot usb mode. Oh, and I tried to find the ruu to match my Hboot, but it currently shows 1.15.0000, and there is of course no ruu with that code, so I downloaded the newest one (2 point something)
Any help is appreciated
admsteff said:
Here's my situation. Got this new phone yesterday. I am (was) bootloader unlocked, s-on with htcdev method. Also am (was) using twrp for recovery. Then went looking for some roms... found one, moved it to the phone, wipe, blah, blah, done this before plenty on my old evo shift. Well, there was some problem, rom couldn't be installed, which is no problem for people who do regular nand backups. That was not me. So... stuck at htc screen.
Bottom line, after many hours of different ideas and methods, I've relocked the bootloader, downloaded an ruu, and I'm stuck. In hindsight I sort of backed myself into a corner, because though I supposedly needed to relock to run an ruu, now I can't get at twrp recovery. So I need help running the ruu from fastboot. In my searches, this seems possible, but it's not working for me. The phone is recognized, because when I enter into command "fastboot find devices" or whatever that was, a phone shows up. The .exe itself just won't open though. Tried running as administrator, tried compatibility mode, tried running it from the command line, each time it will give me the blue circley thing for about 5 or 10 seconds and then just do nothing.
I'm just out of ideas, feeling like I'm stuck here.
Remember: currently my screen reads TAMPERED RELOCKED Security Warning I'm in fastboot usb mode. Oh, and I tried to find the ruu to match my Hboot, but it currently shows 1.15.0000, and there is of course no ruu with that code, so I downloaded the newest one (2 point something)
Any help is appreciated
Click to expand...
Click to collapse
You can get the RUU here
This will help you get twrp and SuperSU back
It's really just an incompatible ruu? I'm about halfway through downloading the 1.22 version already, I thought I would try. I'll give it a shot, but wouldn't it give an error or something instead of just not responding on my pc?
admsteff said:
It's really just an incompatible ruu? I'm about halfway through downloading the 1.22 version already, I thought I would try. I'll give it a shot, but wouldn't it give an error or something instead of just not responding on my pc?
Click to expand...
Click to collapse
To be honest I have never flashed an RUU but I would think if you flashed the wrong one it could potentially brick your phone.
Thanks, these ruu files are so damn big, it's gonna be a few minutes. We'll see how it goes.
admsteff said:
Thanks, these ruu files are so damn big, it's gonna be a few minutes. We'll see how it goes.
Click to expand...
Click to collapse
You should try uploading them haha good luck.
Wait a minute, I noticed that the link you gave me is for a .zip file, while the one I'm downloading is for a .exe file? Isn't it supposed to be a self-installing program from windows? Do I need to be entering like a fastboot flash command for a zip instead because my phone is in fastboot and not fully booted? I can't believe I forgot the nand backup, this is like a whole wasted day of my life now...
admsteff said:
Wait a minute, I noticed that the link you gave me is for a .zip file, while the one I'm downloading is for a .exe file? Isn't it supposed to be a self-installing program from windows? Do I need to be entering like a fastboot flash command for a zip instead because my phone is in fastboot and not fully booted? I can't believe I forgot the nand backup, this is like a whole wasted day of my life now...
Click to expand...
Click to collapse
Like I said I have never ran an RUU so I'm not sure how it works you could PM om4 or read Don't Panic in the Q&A section
Yeah, problem is the same with the 1.22 ruu. It just wont execcute the program from my pc. Does anybody else have any ideas?
You only had to flash the kernel or bootimg. Seperately since your s-on...look for om4 guide " don't panic"...it should answer all of your questions...as far as the ruu make sure you're on the bootloader fastboot screen when you run it.
Sent from my EVO using xda premium
---------- Post added at 02:40 PM ---------- Previous post was at 02:37 PM ----------
http://forum.xda-developers.com/showthread.php?p=31102864
mrlakadaddy said:
You only had to flash the kernel or bootimg. Seperately since your s-on...look for om4 guide " don't panic"...it should answer all of your questions...as far as the ruu make sure you're on the bootloader fastboot screen when you run it.
Sent from my EVO using xda premium
---------- Post added at 02:40 PM ---------- Previous post was at 02:37 PM ----------
http://forum.xda-developers.com/showthread.php?p=31102864
Click to expand...
Click to collapse
Yes, I realize I dug myself into a hole by relocking. I just didn't want to learn how to put a new img on my phone (of course it was wiped, with a bad rom flashed) without having the thing mounted as a media device in the gui method. I'm sure it would have been quite easy, and that's kind of how the whole thing went, I wasn't scared enough and I just kept doing what I thought was the "easiest" way to get the phone back, and just was a dumbass overall. I read the "don't panic" guide. Maybe I missed something, but I don't think it would have got me out of the specific problem I made, once I was already in it. And I was certainly on fastboot usb when trying to run the ruu, and I had it in the right folder with fastboot.exe, etc.
Anyway, I never got it to work, but I ended up just returning the device to the retailer, and no questions were asked. It was cheating, I know. It could have been done, I was far from bricked, but when the phone is 1.5 days old and I can return it to a person who has no idea why my phone is "stuck", it was just too easy.
Thanks to everyone who tried to help
Related
Hey Guys, fairly new to posting here, but was hoping this could help some of you.
#####################################################################
# If you are running a stock ROM you can ignore this, there are better threads for you out there.
#####################################################################
When the OTA came out I knew I wanted the new radios, but have had nothing but problems putting them on.
I have spent the last couple of hours reading and generally just being frustrated. I eventually got to the conclusion I wanted and I thought having all of this OTA update junk in one place might be helpful for others.
History:
- I was running Ineffabilis 12/29. (great ROM)
- Went to Senseless ICS (great ROM, bluetooth problems, persistent with all current ICS's, was insurmountable for me)
- Went to Team BAMF Rezound Cubed ROM, used this ROM to get out of the ICS trap because it flashes a kernel after it flashes the ROM.
Coming From ICS, Team BAMF Cubed or the New clean GB rom:
If you have installed a ROM that updated the Main Ver (all ICS roms or Team BAMF rom, or the new clean GB rom, then you will need to reset the main ver to 1.00.000.00 to run the RUU.
To do that go to this thread: http://forum.xda-developers.com/showpost.php?p=21875151&postcount=1
Next:
Once you have your main ver set to 1.00.000.00. You will need to follow these instructions:
http://forum.xda-developers.com/showthread.php?t=1466474 (summary below)
1) You will need to reflash the stock recovery (a great way to do that is using Cleanflash, get it here: http://www.scottsroms.com/downloads.php?do=file&id=57) -- You can find the stock flash recovery image in the thread above.
2) Reboot to Fastboot and run "fastboot oem lock" from your DOS command line. This will reboot your phone back into fastboot/hboot.
3) Run the RUU.exe from Windows using the download from scottsroms here: http://www.scottsroms.com/downloads.php?do=cat&id=11
4) Go through and install the OTA updates. Go to settings, and software update.
5) Go back to HTCDev.com and unlock the bootloader as you have in the past.
6) Flash a new recovery.img, such as amonRa, (fastboot flash recovery nameofrecovery.img)
7) The world is now yours! Install ICS if you would like or any other ROM or install su if you prefer.
Credits:
!! mrbracht for the mainver fixed (saved my bacon)
!! FlyHalf205 for the rest of this
!! scrosler for generally being awesome and all the great tool's, roms, ruu, etc.
I've downloaded the recovery and unziped it. Then I moved it to fastboot but when I type fastboot flash recovery recovery_sign.img I get a error cannot load.
FlagAZ said:
I've downloaded the recovery and unziped it. Then I moved it to fastboot but when I type fastboot flash recovery recovery_sign.img I get a error cannot load.
Click to expand...
Click to collapse
The stock recovery? What mainversion are you?
I checked today it was something like 1.0.6. I know that it was not updated.
---------- Post added at 10:27 PM ---------- Previous post was at 10:24 PM ----------
I've been trying all day with no like...... I'm lost with all the post about how to do this (flash this, unload this, do it this way)......
okay so what is the text of the error?
i keep getting hung up in the RUU... my MainVer is the same version as the RUU, or was, but now i can't reboot my phone, just tuck in bootloader/fastboot, and with the stock recovery lol...
my ADB won't open either
---------- Post added at 09:26 PM ---------- Previous post was at 08:39 PM ----------
platinumrims said:
i keep getting hung up in the RUU... my MainVer is the same version as the RUU, or was, but now i can't reboot my phone, just tuck in bootloader/fastboot, and with the stock recovery lol...
my ADB won't open either
Click to expand...
Click to collapse
pah, gave up. unlocked reflashed amon ra, and restored my nandroid... :'(
Maybe this reply is too late. Sorry...
But, was it locked and having the stock recovery when you were trying the RUU? Also you run the RUU from windows while the phone is in hboot mode.
pngwyn said:
Also you run the RUU from windows while the phone is in hboot mode.
Click to expand...
Click to collapse
Yes, that is how I always do it.
Wow. I'm impressed with the details you provided. I was debating flashing ICS and had questions about going back. You answered all my questions. Thanks for posting your findings. I really appreciate it.
Updated
So by resetting the mainver, will I be able to flash ICS then say Ineffabilis 12/29 without worrying about updating any kernels? Also, just to confirm, once I flash ICS, I'd have to reset the mainver before going back to Ineffabilis 12/29.
Sent from my ADR6425LVW using xda premium
I go back and forth between ics and gb roms without any issues, never got a mainver error.
Sent from my HTC Rezound using XDA Premium
raider3bravo said:
Wow. I'm impressed with the details you provided. I was debating flashing ICS and had questions about going back. You answered all my questions. Thanks for posting your findings. I really appreciate it.
Updated
So by resetting the mainver, will I be able to flash ICS then say Ineffabilis 12/29 without worrying about updating any kernels? Also, just to confirm, once I flash ICS, I'd have to reset the mainver before going back to Ineffabilis 12/29.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Glad you found the post useful.
As far as I understand, you won't have any issues switching between GB and ICS and back to GB (other than needing to make sure you are running a compatible kernel). If you go back to ineffabilis after ICS you will need to find a way to get the kernel on the system (probably through fastboot or adb) and then flash ineffabilis, for me it was easiest to go back to GB using team bamf because it included the kernel and then you could flash ineffabilis and all should have been well.
The real reason to worry about main ver (as far as I know) is so that you can flash the ruu and return to stock. I guess there are also some other problems with kernels and them checking what mainver you have before flashing, but I am not familiar with those issues.
The nice thing is with the mainver hack above you won't ever have to worry by resetting the mainver, pushing the stock recovery, relocking and then flashing using the RUU utility it is possible to get completely back to factory condition.
Best Regards!
pngwyn said:
Maybe this reply is too late. Sorry...
But, was it locked and having the stock recovery when you were trying the RUU? Also you run the RUU from windows while the phone is in hboot mode.
Click to expand...
Click to collapse
I was using the ruu on Windows and had my phone in Hboot.
I relocked it, via an app someone made here on the forums because I couldn't get ADB to run at all. It would flash up in a window and close immediately. And I re installed SDK 10 Times and couldn't ever get adb to re instal or update.
Also had the stock recovery flashed...
When I used the app to relock the phone I had a "security warning" message under the relock status in fastboot, dunno if that's normal.
Then when trying to run the ruu I got a 155 error, but it wasn't the same one as listed in the report, or it didn't say the same thing at least. Then I kept getting battery lower than 30% errors so it wouldn't let me redo it after the 3rd try. Even though my phone was at like 85% when I got frustrated and decided booted it back up...
I'd like to try it again some other time but idk what else to do to get my ADB functioning ATM so I can check or change my MainVer (which was the same version as the ruu, also dunno if that mattered, I just though as long as it wasn't higher the ruu would work)
Any info would be mucho appreciated lol. :banghead:
platinumrims said:
I was using the ruu on Windows and had my phone in Hboot.
I relocked it, via an app someone made here on the forums because I couldn't get ADB to run at all. It would flash up in a window and close immediately. And I re installed SDK 10 Times and couldn't ever get adb to re instal or update.
Also had the stock recovery flashed...
When I used the app to relock the phone I had a "security warning" message under the relock status in fastboot, dunno if that's normal.
Then when trying to run the ruu I got a 155 error, but it wasn't the same one as listed in the report, or it didn't say the same thing at least. Then I kept getting battery lower than 30% errors so it wouldn't let me redo it after the 3rd try. Even though my phone was at like 85% when I got frustrated and decided booted it back up...
I'd like to try it again some other time but idk what else to do to get my ADB functioning ATM so I can check or change my MainVer (which was the same version as the ruu, also dunno if that mattered, I just though as long as it wasn't higher the ruu would work)
Any info would be mucho appreciated lol. :banghead:
Click to expand...
Click to collapse
I am not familiar with anything you experienced.
You shouldn't need adb for anything you are trying to do. It doesn't sound like you are getting the mainver error (if you were you would be getting the error after trying to go through the RUU wizard and it actually tells you your mainver is 2.00.###.## for whatever it is. If you are sure you haven't done anything to update your main ver than chances are your mainver is not the problem.
I am just guessing but this is what I am imagining could be solutions.
- Use 'fastboot oem lock' from the hboot prompt when in fastboot usb mode (ie your usb cable is plugged in.
- Make sure you are using the .exe version of the RUU. If you are not using the .exe version then that definitely could be the problem, if you are using the .exe version then perhaps the file got corrupted when you downloaded it. Try deleting and redownloading.
- You have said that you are running the stock recovery which sounds correct. But make sure you aren't using the stock recovery from one of your own backups use the one that is provided in the thread from my link above.
... In conclusion you shouldn't need ADB if your main version is the stock mainver. Flash the stock recovery first of all, then use the command 'fastboot oem lock' it will tell you it is locked it will reboot the phone (I think it even gives you an error in the dos prompt.) But then when it reboots it reboots to hboot and will say relocked at the top in the bright purple. Then be sure to run the RUU version .exe. If the RUU you have still isn't working download another (this is the one that worked for me: http://www.scottsroms.com/downloads.php?do=file&id=37)
Sorry wish I could be more helpful but I don't have relevant experience for what is happening for you but I do know what worked for me and I do believe it will work for you.
Good luck!
I doubt seriously that its my mainver. I'm wondering if it had something to do with that,weird security thing I had showing up in my fastboot. I will try it again maybe tomorrow night or something. Thank for your help
THANKS
I had to do the main ver fix and everything, great guide made everything super easy
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
So here is the short of it:
Was having some issues with Sprint on my EvOLtE rooted with unlocked bootloader on fresh 5.1.1 rom. They were unable to use any of the ##blablabla# commands on my phone to refresh my data connection. So I wiped and restored the stock ROM back up I had made. Still no go for the ##blablabla# commands so I was going to do a full factory reset and go from there. Well in the process, It seems I wipe out everything (system partition) as well as any backups that were saved to the internal sd card. So I read up and watched some vids posted and was going to try the full RUU to get it back to stock. I used ADB to relock the bootloader, and went to run the RUU. Well it will not see the phone as connected since there is no system files and no OS on the phone. And now that the bootloader is locked I have no access to recovery to try to flash anything, and can't run RegawMOD to re-unlock bootloader for the same reason as unable to to run RUU, no OS on phone to see connection. Can anyone please help?
Solution found:
per a responce from regaw_leinad The RUU does work from fastboot usb and is recognized and will run.
PhenixInk said:
So here is the short of it:
Was having some issues with Sprint on my EvOLtE rooted with unlocked bootloader on fresh 5.1.1 rom. They were unable to use any of the ##blablabla# commands on my phone to refresh my data connection. So I wiped and restored the stock ROM back up I had made. Still no go for the ##blablabla# commands so I was going to do a full factory reset and go from there. Well in the process, It seems I wipe out everything (system partition) as well as any backups that were saved to the internal sd card. So I read up and watched some vids posted and was going to try the full RUU to get it back to stock. I used ADB to relock the bootloader, and went to run the RUU. Well it will not see the phone as connected since there is no system files and no OS on the phone. And now that the bootloader is locked I have no access to recovery to try to flash anything, and can't run RegawMOD to re-unlock bootloader for the same reason as unable to to run RUU, no OS on phone to see conection. Can anyone please help?
Click to expand...
Click to collapse
power off your phone and then hold power+vol down to get into the bootloader. from there click fastboot and then once there click fastboot usb and it should come up as a disk drive. drag and drop an ruu on there and flash from the bootloader
edit: nvm i lied thats how it worked on the original evo 4g. idk how to do it on this phone. sorry... :/
---------- Post added at 11:56 PM ---------- Previous post was at 11:50 PM ----------
wait a minute..... if your able to get into the bootloader or fastboot i believe your able to run an ruu using an ruu.exe on your computer and having the phone pluged in via usb. i remember because i did it like 40 times when trying to fix my og evo after the twrp 2.0 bricked it...
Yea, No fastboot usb on this device. If Is there is some how I can get PJ75DIAG.zip extracted from the RUU, then maybe then I could flash the PJ75DIAG.zip through the bootloader.
PhenixInk said:
Yea, No fastboot usb on this device. If Is there is some how I can get PJ75DIAG.zip extracted from the RUU, then maybe then I could flash the PJ75DIAG.zip through the bootloader.
Click to expand...
Click to collapse
you might be able to get one of the developers such as regaw_leinad to try to help you with that. im not exactly sure how you would extract it but even harder would be making it flashable via bootloader.
Yea, I was gonna try to send him a pm but I don't think I have enough post to allow me to. When I tried, it just showed my sent box as empty. Any idea how may one needs to get that privilege? Or could you hit him up and send him my way. Thanks for addressing my op and giving your feed back, I appreciate it.
PhenixInk said:
Yea, I was gonna try to send him a pm but I don't think I have enough post to allow me to. When I tried, it just showed my sent box as empty. Any idea how may one needs to get that privilege? Or could you hit him up and send him my way. Thanks for addressing my op and giving your feed back, I appreciate it.
Click to expand...
Click to collapse
no problem. and i have no idea but ill send him over here to see if he can help
edit: i sent him a message about perhaps making a hboot flashable ruu. ill let you know what he says
Cool.
Thanks a lot man.
Hey guys,
I was running the latest Viper rom. Every great once in a while the phone would just turn off. I could get it back fine and this happened about 5-6 times. Today the phone got stuck in a boot loop. I figured something went wrong.
I attempted to restore the phone to stock using the RUU thread found here: http://forum.xda-developers.com/showthread.php?t=2152993
I restored it once fine, said it was good. Phone only rebooted over and over. The HTC logo came up 3-4 times then screen went blank. So I flashed again. Same thing, nothing.
Now I had been playing around and think I updated my radio. Now the RUU from that thread above says it cannot upgrade my phone. I can get to fastbook and lock and unlock the bootloader. I did install latest TWRP but it never enters recovery. I had hoped to just install a basic rom from the 2.04 update and be done. But I cannot get into recovery.
I'm stuck and don't know what else to do. Is there and RUU file like the one above for the new 2.04?
I still think something else is wrong with this phone. Somehow doubt VZW will take it back and exchange.
S-ON
Phone displays HBOOT-1.33.0001
RADIO-1.01.01.0110
Any ideas what I can do next please?
I think the radio got updated when I tried to do S-OFF. Instead of an error at step 3 it flashed. Now I've gone back and tried it again and though I get the proper errors is still shows S-ON. Maybe this isn't even needed. I think my days of tinkering with Android should be over. I can follow guides and such
When I try to enter recovery for TWRP I get a lot of colored lines. Going to try reflashing that and see what gives. I feel that if I could get into TWRP and get a rom file on the phone since I cannot get into Android I might have a chance.
Tersanyus said:
I think the radio got updated when I tried to do S-OFF. Instead of an error at step 3 it flashed. Now I've gone back and tried it again and though I get the proper errors is still shows S-ON. Maybe this isn't even needed. I think my days of tinkering with Android should be over. I can follow guides and such
When I try to enter recovery for TWRP I get a lot of colored lines. Going to try reflashing that and see what gives. I feel that if I could get into TWRP and get a rom file on the phone since I cannot get into Android I might have a chance.
Click to expand...
Click to collapse
Did you take the verizon update as you mentioned 2.04? If you did you will have to wait a bit yet to root again. Your only option would be stock verizon. Their software update basically closed the previously open window. If not...You HAVE updated radio per the # you posted, not sure if that really matters with regard to recovery. It seems like you have compounded many issues. I would try relocking bootloader and flash stock RUU again. Try to get back to stock verizon. If that's a no go, would try reflashing old radio and try stock ruu. How are you getting to try bootloader/recovery, turning on phone holding down vol button? Last ditch if it's says s-on and locked, I think you would be ok to try for a new phone.
I did not take the OTA from Verizon. I never got any prompt for an update. I did the updates for Viper that turned I think just turned that off.
Getting to bootloader is fine. I can lock it and unlock it fine. I know the RUU only loads if locked. I know recovery can only be installed if unlocked I believe. And yes I do that from vol down plus power button.
If I use newest TWRP recovery just gives a whole bunch of colored lines. If I try 2.4.0.0 I can see TWRP come up briefly then the phone reboots again.
The RUU exe file just now gives error 158. Basically it thinks it is not the correct ROM
I found the 1.15 radio but it won't flash. http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19
Just gives error of FAILED remote: 92 supercid
Tersanyus said:
The RUU exe file just now gives error 158. Basically it thinks it is not the correct ROM
I found the 1.15 radio but it won't flash. http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19
Just gives error of FAILED remote: 92 supercid
Click to expand...
Click to collapse
Is there a boot.img for the ruu? Maybe the previous boot image is still directing the process, a thought at least. Also that error 92 cid MAY be the issue, Do you have the newest one on (cid)? I had a lot of issues getting s-off and had to run supercid again to run the process after several error 92 messages. I would look at the whole s-off thread in original dev section maybe some answers in there or a direction to head in.
---------- Post added at 10:39 AM ---------- Previous post was at 09:48 AM ----------
rootntootn said:
Is there a boot.img for the ruu? Maybe the previous boot image is still directing the process, a thought at least. Also that error 92 cid MAY be the issue, Do you have the newest one on (cid)? I had a lot of issues getting s-off and had to run supercid again to run the process after several error 92 messages. I would look at the whole s-off thread in original dev section maybe some answers in there or a direction to head in.
Click to expand...
Click to collapse
Can you get to fastboot? adb can communicate with the phone? Says in red fastboot usb? Also how are you doing RUU, assuming your using executable from your pc? Forgot to ask..
Yes I can get to fastboot fine. I do a "fastboot devices" and it is read. adb doesn't seem to do anything though. The RUU is the .exe I found.
For the cid I did the old one so mine reads all 1's. I didn't think I could so the new cid as I cannot boot into Android at all.
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Tersanyus said:
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Click to expand...
Click to collapse
Not sure how you got there s-off should have all 2's....but it sounds like progress. If you are back to recovery and have a rom to flash in your phone that's great...but you'll need adb working to flash the image file that's associated with it, that will likely fix your wifi issue as well. Even with S-off most of the roms still need to have their respective image files flashed but I am unsure about stock RUU, someone with more experience may know that answer and can maybe steer you in the right direction...
Tersanyus said:
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Click to expand...
Click to collapse
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
rootntootn said:
Not sure how you got there s-off should have all 2's....but it sounds like progress. If you are back to recovery and have a rom to flash in your phone that's great...but you'll need adb working to flash the image file that's associated with it, that will likely fix your wifi issue as well. Even with S-off most of the roms still need to have their respective image files flashed but I am unsure about stock RUU, someone with more experience may know that answer and can maybe steer you in the right direction...
Click to expand...
Click to collapse
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
BTW There was nothing wrong with your phone, it's just that when you restored, you needed to flash the boot.img from your rom that you restored. It was most likely a kernel issue that we could correct with viper.
It sounds like you just need to install the matching rom and boot.img. If you're s off, just fastboot flash the boot.img for whatever rom you currently have installed. For the OTA update, you can install the radios without an RUU if you're s off.
I ran for several hours and several reboots on the RUU .exe file. When I downloaded a custom rom from http://forum.xda-developers.com/showthread.php?t=2150262 - That fan fine for an hour or so. Then boot loop over and over again. Thankfully I made a backup in twrp. I restored that and all is well.
I can't stand this factory rom, the part that really annoys me, besides the VZW bloat, is the recent apps button. For over a year with other HTC's I am used to making that the menu button. Had that in the custom rom.
So it looks like that rebooting loop just means I need to fastboot the boot.img?
I go back to the rom I linked about and fastboot the boot.img. I really liked viper rom but am going to stick to stock that is rooted and debloated.
My cid is all 1's since I did that before all this OTA came out. I did that about 3 weeks ago the day I got the phone.
Thanks for the tips. I'll let you know what happens when I go back to the rom above.
Bigandrewgold said:
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Sorry about the 2's info but read that the older cid apk would no longer work (from thread below) and myself put on the new one which yields the all 2's. Bottom line, glad you made progress, hopefully problem resolved
http://forum.xda-developers.com/showthread.php?t=2109862
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