Related
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
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
Hello,
My amaze 4g is currently running GB with the bullet proof custom rom i found here a couple years ago.
The boot loader is unlocked, and it is S-ON.
I wanted to try and update my phone to an ICS rom such as NRGZ28's energy Rom found here: http://forum.xda-developers.com/showthread.php?t=1362759.
First attempt, I factory reset the phone, cleared cache and cleared dalvik cache and flashed the rom. I chose the option to install it using the stock HTC kernel. The installation went smooth without errors until the final reboot to finalize the installation. The phone gets stuck in the white screen with the green htc logo on it. I recover using Clock Work Mod and everything is back to the old GB setting.
I assume it is because i have an outdated kernel so I go to NRGZ28's thread and download the stock kernel he has posted there. I flashed the kernel using Flash Image GUI apk. This is where the problem happens. After flashing the kernel, the phone is stuck on infinite loop at the above mentioned htc screen.
I flash the energy rom with the newly flashed stock kernel and the phone finally gets past the htc logo screen, but freezes shortly after during the blue animated splash screen and proceeds to repeat this. I can get into boot loader just fine, but am unable to get my phone working again even after a Clock work mod recovery.
please help!!
There is a special process you have to follow when going from GB to ICS, you can't just flash the latest kernel and expect it to work with ICS.
I would do a full wipe/factory reset, then follow the instructions here to upgrade to ICS stock, then you can install whatever ICS ROM you want:
http://forum.xda-developers.com/showpost.php?p=26865752&postcount=27
---------- Post added at 11:33 AM ---------- Previous post was at 11:27 AM ----------
Here is another, possibly more helpful link. It gives step by step instructions, make sure to follow the ones for S=On users (assuming you are S=On).
http://forum.xda-developers.com/showpost.php?p=25215207&postcount=2
I see. Thank you. I will try that right now. I will post an update soon.
o_jake said:
There is a special process you have to follow when going from GB to ICS, you can't just flash the latest kernel and expect it to work with ICS.
I would do a full wipe/factory reset, then follow the instructions here to upgrade to ICS stock, then you can install whatever ICS ROM you want:
http://forum.xda-developers.com/showpost.php?p=26865752&postcount=27
---------- Post added at 11:33 AM ---------- Previous post was at 11:27 AM ----------
Here is another, possibly more helpful link. It gives step by step instructions, make sure to follow the ones for S=On users (assuming you are S=On).
http://forum.xda-developers.com/showpost.php?p=25215207&postcount=2
Click to expand...
Click to collapse
Alright now I'm having a completely unrelated trouble trying to re-lock my bootloader. Yes, I am S-on. I've tried to factory reset but the phone still ends up looping on the htc logo screen. I type in "fastboot oem lock" on sdk but it just hangs at "waiting for device".
DougieJK said:
Alright now I'm having a completely unrelated trouble trying to re-lock my bootloader. Yes, I am S-on. I've tried to factory reset but the phone still ends up looping on the htc logo screen. I type in "fastboot oem lock" on sdk but it just hangs at "waiting for device".
Click to expand...
Click to collapse
Are you able to get into the bootloader, fastboot, or recovery? I'm unsure of which HTC screen you are talking about, if it is the one before trying to boot into Android then I would just ignore it for now. If you're having trouble relocking the bootloader, you might try this toolkit, which includes a tool to relock the bootloader: http://forum.xda-developers.com/showthread.php?t=1493905
All this stuff can probably be found in the HTC Amaze Bible, which you should probably familiarize yourself with before messing around and potentially bricking your phone. http://forum.xda-developers.com/showthread.php?t=1679486
o_jake said:
Are you able to get into the bootloader, fastboot, or recovery? I'm unsure of which HTC screen you are talking about, if it is the one before trying to boot into Android then I would just ignore it for now. If you're having trouble relocking the bootloader, you might try this toolkit, which includes a tool to relock the bootloader: http://forum.xda-developers.com/showthread.php?t=1493905
All this stuff can probably be found in the HTC Amaze Bible, which you should probably familiarize yourself with before messing around and potentially bricking your phone. http://forum.xda-developers.com/showthread.php?t=1679486
Click to expand...
Click to collapse
Yes, it is the screen right before it boots onto your phone's lock screen or main screen. Yes, I can get into the bootloader, fastboot, and the recovery without any problems.
DougieJK said:
Yes, it is the screen right before it boots onto your phone's lock screen or main screen. Yes, I can get into the bootloader, fastboot, and the recovery without any problems.
Click to expand...
Click to collapse
If you can get into the bootloader, fastboot, and recovery, then you should be able to continue the steps and get it working again. Try the Toolkit method of relocking bootloader and continue upgrade to ICS.
o_jake said:
If you can get into the bootloader, fastboot, and recovery, then you should be able to continue the steps and get it working again. Try the Toolkit method of relocking bootloader and continue upgrade to ICS.
Click to expand...
Click to collapse
The all-in-one toolkit is not recognizing my device. Not sure if it's a problem with windows or the toolkit.
Also, it seems the toolkit only works if you are able to actually get to your phone's home screen, which I am unable to do.
So frustrating.....
DougieJK said:
The all-in-one toolkit is not recognizing my device. Not sure if it's a problem with windows or the toolkit.
Also, it seems the toolkit only works if you are able to actually get to your phone's home screen, which I am unable to do.
So frustrating.....
Click to expand...
Click to collapse
Here are some more instructions: http://forum.xda-developers.com/showthread.php?t=1575550&highlight=relock+bootloader
It seems as though the problem is with ADB communicating with your phone. Type in "ADB devices" to see if it is detecting your phone.
Also make sure the file "fastboot.exe" is in the same folder as your ADB file that your command prompt is using.
---------- Post added at 03:12 PM ---------- Previous post was at 03:03 PM ----------
Also are you in bootloader or fastboot when you are trying to do this? I believe you should be in fastboot.
To enter fastboot: Boot into bootloader (hold power and volume down button), scroll down to fastboot, hit the power button.
Now try executing the fastboot command using adb. (remember to make sure fastboot.exe is in same folder as adb)
Alright, so I got it relocked by hooking it up to an old tower. It seems it was an issue with windows not recognizing my phone for some reason.
NOW, there's a new problem. On the bootloader menu, on the top it says "RELOCKED". I choose the recovery option, and it immediately takes me back to the bootloader menu displaying a "Security Warning" message under "RELOCKED".
I am going to cry.:crying:
DougieJK said:
Alright, so I got it relocked by hooking it up to an old tower. It seems it was an issue with windows not recognizing my phone for some reason.
NOW, there's a new problem. On the bootloader menu, on the top it says "RELOCKED". I choose the recovery option, and it immediately takes me back to the bootloader menu displaying a "Security Warning" message under "RELOCKED".
I am going to cry.:crying:
Click to expand...
Click to collapse
This is good... I think. You can now move on to the next step in these instructions: http://forum.xda-developers.com/showthread.php?t=1575550&highlight=relock+bootloader
You have to rename the RUU to what is says in that link, place it on an external SD card, then reboot into bootloader. Then it should automatically install the update (there might be a prompt, just hit yes).
o_jake said:
This is good... I think. You can now move on to the next step in these instructions: http://forum.xda-developers.com/showthread.php?t=1575550&highlight=relock+bootloader
You have to rename the RUU to what is says in that link, place it on an external SD card, then reboot into bootloader. Then it should automatically install the update (there might be a prompt, just hit yes).
Click to expand...
Click to collapse
Yes!!! I finally got it to work! Oh my god thank you so much. Thanks for being so patient with me. I dont know what more i can do do express my gratitude. It just felt amazing to see everything working and falling into place after hours and hours of hopelessness.
So from here on, I assume I just get back onto the boot loader menu, Unlock the boot loader again, then flash the rom I want.
Thank you again.
DougieJK said:
Yes!!! I finally got it to work! Oh my god thank you so much. Thanks for being so patient with me. I dont know what more i can do do express my gratitude. It just felt amazing to see everything working and falling into place after hours and hours of hopelessness.
So from here on, I assume I just get back onto the boot loader menu, Unlock the boot loader again, then flash the rom I want.
Thank you again.
Click to expand...
Click to collapse
You can flash any *ICS* ROM you want. There's another process if you want to go back to GB (though I'm not sure why you would want to).
You should be able to use the Toolkit to unlock the bootloader again, and I would recommend flashing the 4ext recovery while you're at it. From there you should be good!
o_jake said:
You can flash any *ICS* ROM you want. There's another process if you want to go back to GB (though I'm not sure why you would want to).
You should be able to use the Toolkit to unlock the bootloader again, and I would recommend flashing the 4ext recovery while you're at it. From there you should be good!
Click to expand...
Click to collapse
is the 4ext recovery preferred over Clockwork?
DougieJK said:
Alright, so I got it relocked by hooking it up to an old tower. It seems it was an issue with windows not recognizing my phone for some reason.
NOW, there's a new problem. On the bootloader menu, on the top it says "RELOCKED". I choose the recovery option, and it immediately takes me back to the bootloader menu displaying a "Security Warning" message under "RELOCKED".
I am going to cry.:crying:
Click to expand...
Click to collapse
Thats fine now since you are locked you can download the ruu file pertaining to your phone/carrier and put it in the root of your external sd card and boot into the bootloader and it will automatically detect the ruu and start updating. however you must rename the ruu appropriately (depending on which carrier your phone is) for T-Mobile you rename the ruu file ph85img and it detects it automatically. Good luck
Sent from my HTC_Amaze_4G using xda app-developers app
DougieJK said:
is the 4ext recovery preferred over Clockwork?
Click to expand...
Click to collapse
Yeah. You might like it better too.
hatlesssandman said:
Thats fine now since you are locked you can download the ruu file pertaining to your phone/carrier and put it in the root of your external sd card and boot into the bootloader and it will automatically detect the ruu and start updating. however you must rename the ruu appropriately (depending on which carrier your phone is) for T-Mobile you rename the ruu file ph85img and it detects it automatically. Good luck
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Yep I was just overreacting. After I renamed the ruu file, everything fell into place and my phone is now functioning with ICS.
So apparently, my phone isn't rooted anymore? is this normal?
Flashed 4ext using the all-in-one tool kit. Nothing happened. Can't run any apps that require root. I'm confused.
Yeah, that's totally normal after flashing an RUU and relocking the bootloader. Just re-root, here's a really easy tool for it: http://theunlockr.com/2012/05/01/how-to-root-htc-amaze-4g/
o_jake said:
Yeah, that's totally normal after flashing an RUU and relocking the bootloader. Just re-root, here's a really easy tool for it: http://theunlockr.com/2012/05/01/how-to-root-htc-amaze-4g/
Click to expand...
Click to collapse
That tool doesn't work for some reason, even though its the tool I used when I first rooted my phone. I just went and did the fastboot flash unlock_code.bin to unlock my phone again.
But for some reason, I can't get 4ext to flash... I went through the steps in the link you provided but my phone doesn't show the app nor am i able to access it through the recovery option from the boot loader menu.
I had already had my phone's bootloader unlocked and rooted and had a GPe ROM installed and worked perfectly. THEN I saw that you could literally make it a Google Play edition phone complete with OTA and worked on trying to achieve that. Getting my phone S-Off wasn't working because I believe of my HBOOT version (1.55) so I was told to download this stock ROM that would downgrade me to reach a version that I could then run revone to achieve S-OFF.
POST: http://forum.xda-developers.com/showpost.php?p=45487258&postcount=55
I ran a backup through TWRP first and then flahsed this ROM, which has kept my HTC One at the HTC One splash screen. I connected it to my computer/ADB and got it into the bootloader to go into custome recovery BUT the recovery takes me to a black screen with a phone and red triangle, so it's like my recovery isn't there anymore. Fine.
I download the latest TWRP for my phone(triple checked) and ran the fastboot flash recovery command through ADB but it says
"(bootloader) signature checking...FAILED (remote: signature verify fail)"
is there some sort of way to disable the signature check using ADB or am I actually going about this the wrong way?
I'll admit, I don't do this stuff oftem, so ask as many questions as needed as I probably left out details you may need
I may be wrong but you may have to re-lock the bootloader and run the ruu back to stock.
nandroid backup restore won't change the hboot so I don't think you'll have any luck there.
I'm running ARHD 40 just till we can find a way to run s-off on our AT&T devices.
noobsquared said:
I may be wrong but you may have to re-lock the bootloader and run the ruu back to stock.
nandroid backup restore won't change the hboot so I don't think you'll have any luck there.
I'm running ARHD 40 just till we can find a way to run s-off on our AT&T devices.
Click to expand...
Click to collapse
Not to sound n00b-ish, but what would be the best way of doing this?
EDIT: Actually it is relocked already! Duh! On the bootloader screen it says "TAMPERED" and then "RELOCKED" below that
That's alright, we were all noobs at some point in time.
Sounds like you re-locked the bootloader without stock recovery.
Here is the link:
http://forum.xda-developers.com/showthread.php?t=2158151
Download the cingular:
RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2.exe 1134.6MB 2013-10-07 16:47:53
Run the RUU from a windows based computer that has HTC drivers and it should restore it back to stock.
noobsquared said:
That's alright, we were all noobs at some point in time.
Sounds like you re-locked the bootloader without stock recovery.
Here is the link:
http://forum.xda-developers.com/showthread.php?t=2158151
Download the cingular:
RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2.exe 1134.6MB 2013-10-07 16:47:53
Run the RUU from a windows based computer that has HTC drivers and it should restore it back to stock.
Click to expand...
Click to collapse
I actually had that downloaded but I was just concerned if that was the right move since it wipes the phone.
noobsquared said:
That's alright, we were all noobs at some point in time.
Sounds like you re-locked the bootloader without stock recovery.
Here is the link:
http://forum.xda-developers.com/showthread.php?t=2158151
Download the cingular:
RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2.exe 1134.6MB 2013-10-07 16:47:53
Run the RUU from a windows based computer that has HTC drivers and it should restore it back to stock.
Click to expand...
Click to collapse
I hate to say this actually, but I can't find that .exe in the link. I don't know exactly what I'm looking for in it.
h_smith said:
I hate to say this actually, but I can't find that .exe in the link. I don't know exactly what I'm looking for in it.
Click to expand...
Click to collapse
Here you go:
http://www.androidruu.com/getdownlo...13_10.38j.1157.04_release_334235_signed_2.exe
You can always unlock the bootloader again, install twrp and try to boot and see if that works.
Install the nandroid backup matching your system and you can then get to your data.
noobsquared said:
You can always unlock the bootloader again, install twrp and try to boot and see if that works.
Install the nandroid backup matching your system and you can then get to your data.
Click to expand...
Click to collapse
But how would I do that if I can't even boot up the phone past the splash screen? I did all of the unlocking and TRWP installing via the phone
Downloading and installing the file right now. It's going slow as hell but I'll run when I get the chance
THANK YOU FOR STICKING WITH ME!
h_smith said:
But how would I do that if I can't even boot up the phone past the splash screen? I did all of the unlocking and TRWP installing via the phone
Downloading and installing the file right now. It's going slow as hell but I'll run when I get the chance
THANK YOU FOR STICKING WITH ME!
Click to expand...
Click to collapse
Sure thing man. It's stuck at that screen because when your phone is unlocked, it allows custom recovery but when it's locked, it won't boot unless it finds the stock recovery. I am not 100% sure but I've had that issue as well. I had to run the RUU to get back to stock since you can't lock the bootloader with custom recovery and expect it to boot. It may vary from device to device but I've always had to RUU back to stock or fastboot flash stock recovery to get past that screen before you lock the bootloader. You can try again, there is stock recovery posted by someone in forums. Download that, try to go in fastboot mode and try fastboot flash recovery recovery_name.img. I think once you've locked the bootloader it may not work but worth a shot.
noobsquared said:
Sure thing man. It's stuck at that screen because when your phone is unlocked, it allows custom recovery but when it's locked, it won't boot unless it finds the stock recovery. I am not 100% sure but I've had that issue as well. I had to run the RUU to get back to stock since you can't lock the bootloader with custom recovery and expect it to boot. It may vary from device to device but I've always had to RUU back to stock or fastboot flash stock recovery to get past that screen before you lock the bootloader. You can try again, there is stock recovery posted by someone in forums. Download that, try to go in fastboot mode and try fastboot flash recovery recovery_name.img. I think once you've locked the bootloader it may not work but worth a shot.
Click to expand...
Click to collapse
Thank you. I'm downloading the .exe and will post the results. But it looks like that might take a few hours :/
hey is there another link? that one is so slow and keeps timing out :/
You can either use download manager or chrome browser is pretty good at managing that.
Try this: http://d-h.st/VWf
---------- Post added at 06:31 PM ---------- Previous post was at 06:30 PM ----------
I just did a google search for the term RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_R and gave you the second result I got. Just search for the name of the file and you will find plenty of links.
Hope that helps.
This sounds like the exact same problem I had. The RUU and directions solved that one for me too...
Link to RUU: http://www.htc.com/us/support/news.aspx?p_id=628&p_name=htc-one-att
Other thread: http://forum.xda-developers.com/showthread.php?t=2492266
THANK YOU NOOB!!
I managed to get it fixed. Turns out HTC hosted that exact file so I downloaded it and it fixed my phone. Good times..
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