Related
Hello everyone, I am checking here to see if anyone might know. I used to have a Samsung Vibrant and was familiar with using it's ODIN tool that would allow you to return to 100% stock on your phone for everything except hard bricking the phone.
I was wondering if there is any tool like this for the EVO 3D. I know there are the RUU files which you can place on your SD card for flashing over, but I am on HBOOT 1.5 with the HTC Dev Unlock method so I have not yet found an RUU that I can flash back to 100% stock with.
If there is any information, I would surely appreciate it. I have spent the last 3 hours searching 3 different android forums as well as google for a way to do this either with or without a special tool like this. Even if someone knows of an RUU that I can flash back to stock with on HBOOT 1.5.
witemouse said:
Hello everyone, I am checking here to see if anyone might know. I used to have a Samsung Vibrant and was familiar with using it's ODIN tool that would allow you to return to 100% stock on your phone for everything except hard bricking the phone.
I was wondering if there is any tool like this for the EVO 3D. I know there are the RUU files which you can place on your SD card for flashing over, but I am on HBOOT 1.5 with the HTC Dev Unlock method so I have not yet found an RUU that I can flash back to 100% stock with.
If there is any information, I would surely appreciate it. I have spent the last 3 hours searching 3 different android forums as well as google for a way to do this either with or without a special tool like this. Even if someone knows of an RUU that I can flash back to stock with on HBOOT 1.5.
Click to expand...
Click to collapse
RUU is to HTC as Odin is to Samsung (for the most part!).
RUU is the correct method. RUU stands for ROM Update Utility. The RUU .exe file can be run from Windows (just like Odin) and connects to the device, sends over the payload (rom.zip/PG86IMG.zip) and allows it to flash all partitions with stock images.
Alternate Method: Extract the payload from the RUU .exe (rom.zip/PG86IMG.zip) push to root of sdcard, boot into bootloader and let the bootloader apply the payload.
In the end, both do the same thing, just start off slightly different.
For the Sprint EVO 3D RUU files - http://goo-inside.me/shooter/ruu
*might* also have the GSM RUU files under shooterru
Thanks a bunch for the info! I really appreciate it. +thanks
I was attempting to downgrade my hboot 1.50 to hboot 1.40 and followed directions here here. I intentionally bricked it and believe I did that correctly. I'm in Japan and downloaded the RUU for my phone and extracted the ROM from it. Everything was fine and I believe it was bricked according to directions, but the phone is not recognized when I connect to my linux machine or any machine. It's just totally bricked. At this point, could anyone point me to some tools or tips so I can attempt to unbrick it? It's a great phone and I'd like to revive it. Thanks!
gjash
gjash said:
I was attempting to downgrade my hboot 1.50 to hboot 1.40 and followed directions here here. I intentionally bricked it and believe I did that correctly. I'm in Japan and downloaded the RUU for my phone and extracted the ROM from it. Everything was fine and I believe it was bricked according to directions, but the phone is not recognized when I connect to my linux machine or any machine. It's just totally bricked. At this point, could anyone point me to some tools or tips so I can attempt to unbrick it? It's a great phone and I'd like to revive it. Thanks!
gjash
Click to expand...
Click to collapse
Hey man the phone isn't bricked if you have a pulsating dim red power light, alot of people came across the problem of actually killing batteries trying to brick their phones. If its pulsating just leave it charging on the wall socked for a while bit if it is a very very dim constant red light it is bricked and you would have to use a compatible computer that takes the drivers for your phone. Read through the thread you linked and search for your issue, it is a common one
****'ll Buff Out
gjash said:
I was attempting to downgrade my hboot 1.50 to hboot 1.40 and followed directions here here. I intentionally bricked it and believe I did that correctly. I'm in Japan and downloaded the RUU for my phone and extracted the ROM from it. Everything was fine and I believe it was bricked according to directions, but the phone is not recognized when I connect to my linux machine or any machine. It's just totally bricked. At this point, could anyone point me to some tools or tips so I can attempt to unbrick it? It's a great phone and I'd like to revive it. Thanks!
gjash
Click to expand...
Click to collapse
Hi there gjash. I'm sorry for the way some people are acting here. May I ask who your cell phone carrier is? Is it KDDI, or do you have a Sprint phone? Can you also link to the RUUs that you used for the phone?
Please let me know anything you can tell me about the phone. Don't post any numbers. Was your HBOOT version 1.50 before?
Also, if you put the battery back into the phone, does it power on at all? If it does, it's not bricked.
~co~
closeone said:
Hi there gjash. I'm sorry for the way some people are acting here. May I ask who your cell phone carrier is? Is it KDDI, or do you have a Sprint phone? Can you also link to the RUUs that you used for the phone?
Please let me know anything you can tell me about the phone. Don't post any numbers. Was your HBOOT version 1.50 before?
Also, if you put the battery back into the phone, does it power on at all? If it does, it's not bricked.
~co~
Click to expand...
Click to collapse
Thanks, it's just dead as can be. I did eventually get it recognized by linux on the live cd and it successfully went through it's routine to get to hboot 1.40. The next step should be to install RUU 1.13. It's a KDDI phone. I used this
RUU_Shooter_K_S_KDDI_JP_1.11.970.2_Radio_1.02.00.0906_NV_1.39_01C_release_246058_signed.exe
for initially bricking it. I extracted the ROM first. That part went smoothly . I think I did everything right and i'm where i should be now but it just doesn't do anything... nothing. I did try to mess with emmc_recover but no luck yet. When I do the RUU I just keep getting "error 170 usb connection error." I've tried uninstalling/re-installing/different versions of HTC drivers. I keep messing with it for a bit and hopefully something gives! Oh and battery, no battery, I can't get anything. If I could get it recognized on the PC I think I'd have a shot! Thanks again,
gjash
runcool said:
The evo3d was designed for americans. We don't support the Japan people do to over population of your race. Also if you used your head you'd notice that the computer you're using likely is in the crappy Japan language no one uses. Therefore, you need to try another computer and it'll work. We can't support every computer out there. The Drivers won't work for every type of computer on the planet.
To make this racist reply short, it's your computer. you gotta try another computer. Try using an older system. I'll have to open it up to figure out which drivers they put in there, but I know for a fact it won't work on my computer. I'd have to use it on another as well.
They should put that in the instructions. hmmm But after trying another computer, get back with us.
ps again, you said you "tried it on other computers" model numbers of those and what language are they in? It does make a difference. But I'm glad you speak english or I'd just laugh. I'm really mean today. so sorry. hahaha. Let me know if I'm right.
ps again. remember drivers drivers and drivers. drivers only work with certain types of hardware.
edit, you said linux machine, BUT DID YOU EVEN INSTALL the drivers on it? lmao!?
Click to expand...
Click to collapse
Your a complete douche bag! Its people like you that drag society down! If I met you in person I would ***** SLAP you so hard it would not be funny!
The last I checked we all bleed red.
@op I am glad you got it worked out unfortunately I can not help because I have no idea who your carrier is. What I do know is if you update to ruu 2.17.651.5 you will be back on Hboot 1.5 but with S-off.
Sorry that is all the info I can give you.
@gjash,
Sorry for the poor manners of some users here.
I thought the hboot 1.50 downgrade was just for EVO3D Cdma phones on Sprint USA, unless I missed something. Your phone/carrier has the same bootloader?
Sent from my PG86100 using Tapatalk
mpgrimm2 said:
@gjash,
Sorry for the poor manners of some users here.
I thought the hboot 1.50 downgrade was just for EVO3D Cdma phones on Sprint USA, unless I missed something. Your phone/carrier has the same bootloader?
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Hi, yeah it's an EVO 3d Cdma. It's the same as the Sprint one. I should be able to get up and going but there really seems to be a lack of resources, a wiki or anything. I guess I just haven't found where it's hiding. I kinda put it off to the side, but I hope to revive it one day. Do you know the purpose of flashing RUU 1.13 after overwriting the hboot? I'm at that point now and I'm looking for another route to where I wanna go. Thanks!!
gjash
gjash said:
Hi, yeah it's an EVO 3d Cdma. It's the same as the Sprint one. I should be able to get up and going but there really seems to be a lack of resources, a wiki or anything. I guess I just haven't found where it's hiding. I kinda put it off to the side, but I hope to revive it one day. Do you know the purpose of flashing RUU 1.13 after overwriting the hboot? I'm at that point now and I'm looking for another route to where I wanna go. Thanks!!
gjash
Click to expand...
Click to collapse
After downgrading/flashing Hboot 1.40, the goal of the RUU is to install an earlier fully working Stock Rom (S-On still) that came with the same Hboot 1.40 that is pushed to the phone with the downgrade tool/process. Hopefully you can find an early KDDI ruu with Hboot 1.40 for this part. This allows you to run " http://Revolutionary.io 's rooting/S-Off tool to gain "S-Off" and install a custom Recovery like Revolutionary CWM Recovery 4.0.1.4 (or 4Ext Recovery).
From there (make a nandroid backup) you can update the firmware/radio if needed (make sure hboot 1.50 isn't included) and flash a current rooted rom (stock or custom) that matches your radio/baseband as appropriate. Maybe there is a current rooted stock KDDI RUU (PG86IMG.zip) without the hboot 1.50 or someone (like Mr.Esp, freeza, or xhausx) can help you pull the stock rom apart for this step.
You can also flash the SuperUser zip (app & binary) from custom recovery to gain root on a currently installed stock rom once you have S-Off.
That's my LIMITED understanding, but I'm not 100% sure about your situation overseas since I thought all foreign carriers outside the U.S. used GSM devices.
closeone said:
Hi there gjash. I'm sorry for the way some people are acting here. May I ask who your cell phone carrier is? Is it KDDI, or do you have a Sprint phone? Can you also link to the RUUs that you used for the phone?
Please let me know anything you can tell me about the phone. Don't post any numbers. Was your HBOOT version 1.50 before?
Also, if you put the battery back into the phone, does it power on at all? If it does, it's not bricked.
~co~
Click to expand...
Click to collapse
Well, I've gotten to the step where I need need to install RUU 1.13. I'm hoping it would take that, but I keep getting an "Error 170 USB connection error" The phone is identical to the sprint one. I believe! I have no lights or anything. Seems dead. Thanks for any help!
gjash
Can't really do anything at the moment. I can't flash RUU 1.13 and I can't get it to be recognized on USB so I could use ADB and try pushing something to it. I have no idea! This is a learning thing at this point. I did root my Asus transformer before though! Thanks for any help!
gjash
gjash said:
Well, I've gotten to the step where I need need to install RUU 1.13. I'm hoping it would take that, but I keep getting an "Error 170 USB connection error" The phone is identical to the sprint one. I believe! I have no lights or anything. Seems dead. Thanks for any help!
gjash
Click to expand...
Click to collapse
First, I think your phone needs to be booted to the new bootloader and in "Fastboot USB" mode displayed on it for the .exe to work.
I am also willing to bet that this is where you need to run the earlier KDDI ruu.exe file that had hboot 1.40 included...
I'm not sure, but "RUU_Shooter_K_S_KDDI_JP_1.09.970.5_Radio_1.02.00.0906_NV_1.39_01C" is an earlier version than the one you bricked with in your previous post. It's listed in Football's CDMA Stock Rom Collection thread, but I don't know which Hboot is included in it.
Closeone or Unknownforce posted in their thread recently about starting the .exe and right before the flash running %temp% in "run" command or something to find the "ROM.zip" that the exe flashes to the phone (this is what gets named to PG86IMG.zip & manually flashed in bootloader sometimes).
- once you have the .zip, you can open it up with 7zip or similar and see what Hboot version is in there (see attached example).
Edit: Here is the post:
closeone said:
But take the RUU .EXE that you upgraded your phone with already and grab the ROM out of there.
To get to your temp directory: press the Windows key and R on your keyboard at the same time. Type in this exactly: %temp%
Rename the rom.zip to PG86IMG.zip and put it on your SD card.
Click to expand...
Click to collapse
I haven't made any progress. I'm assuming I need to use emmc_recover to overwrite the boot partition and maybe the misc partition. So can someone help me figure out identifying the partition, how I can get linux to recognize the device so I have a chance to recover? Also, at this point I settle for anything working, any Hboot, whatever... It would be nice if I could post in the original thread, hmmmm. moderator, can you help there?
thanks,
gjash
Keep an eye on Unknownforce's thread, starting at Post 1912. Looks like ZiT777 is in the same situation and able to provide info to Unknownforce about your phone's hardware.
mpgrimm2 said:
First, I think your phone needs to be booted to the new bootloader and in "Fastboot USB" mode displayed on it for the .exe to work.
I am also willing to bet that this is where you need to run the earlier KDDI ruu.exe file that had hboot 1.40 included...
I'm not sure, but "RUU_Shooter_K_S_KDDI_JP_1.09.970.5_Radio_1.02.00.0906_NV_1.39_01C" is an earlier version than the one you bricked with in your previous post. It's listed in Football's CDMA Stock Rom Collection thread, but I don't know which Hboot is included in it.
Closeone or Unknownforce posted in their thread recently about starting the .exe and right before the flash running %temp% in "run" command or something to find the "ROM.zip" that the exe flashes to the phone (this is what gets named to PG86IMG.zip & manually flashed in bootloader sometimes).
- once you have the .zip, you can open it up with 7zip or similar and see what Hboot version is in there (see attached example).
Edit: Here is the post:
Click to expand...
Click to collapse
You are right... both KDDI 1.09 and 1.11 have Hboot 1.50. I guess the trying Sprint 1.13 wouldn't be an option? That's the question and I can't really find out as the KDDI ones and the Sprint ones don't work because I always get USB 170 connection errors. So kinda stuck, but greatly appreciate the help!
gjash
mpgrimm2 said:
Keep an eye on Unknownforce's thread, starting at Post 1912. Looks like ZiT777 is in the same situation and able to provide info to Unknownforce about your phone's hardware.
Click to expand...
Click to collapse
I will start looking there... I was thinking that the KDDI Evo 3d is CDMA and it would have the same partition layout. I'd like to determine that and go from there. Can someone explain the sprint evo 3d partition layout? thanks!
gjash
I'm willing to mess with this phone so if any developers have something I can do, please let me know. Otherwise, I just try to get back to stock.
I extracted original hboot from latest KDDI RUU and renamed it hboot.img and then executed 'downgrade'
I got this error:
Waiting for device...
Found the Correct Device!
Writing image file!
dd: opening `/dev/sdf34': Permission denied
FAILED!!
Any ideas? Thanks!
gjash
I've got nothing on that error (may need to be named hboot_1.4.nb0 ), but if I recall correctly, the earlier version of the downgrade tool had the option in it to manually change misc_version to an earlier one so that you could flash an RUU. I think Closeone's LiveCD v3.4 had it.
mpgrimm2 said:
I've got nothing on that error (may need to be named hboot_1.4.nb0 ), but if I recall correctly, the earlier version of the downgrade tool had the option in it to manually change misc_version to an earlier one so that you could flash an RUU. I think Closeone's LiveCD v3.4 had it.
Click to expand...
Click to collapse
Getting closer I think... I just needed to do a sudo ./downgrade and it flashed fine. Now I have a red light on which is more than I had before. I will go to windows now and try to flash the KDDI RUU. thanks for the help.
gjash
Update:
I'm back up where I started. I used Unknownforce's hboot downgrade but renamed the original hboot from the KDDI RUU to hboot.img, according to Unknownforce's direction (thanks!). After I did that, the phone just booted up normally. I thought I would have to flash the RUU but wasn't necessary. I think with some changes this whole exploit could work with the japanese cdma version of the Evo 3D. If anyone can outline what I'd need to do, it might be fun. especially that I already ordered another phone, but I won't actually need it.
gjash
Does your device happen to be the KDDI ISW12HT?
(I assume it is from what you've said)
Do you know the exact model you have?
The current CDMA models that I'm aware of are the:
X515c: CDMA800, CDMA1900, ESMR800, WiMAX 2.5-2.7GHz (the sprint one)
X515d: CDMA800, CDMA1900 (I forget)
X515e: CDMA900, CDMA2100 (the HTC rider)
The ISW12HT is listed as having CDMA800, CDMA2100, which arnt any of those 3.
Do you happen to know what submodel you have? I have no idea how to check as I've never touched one.
I'm wondering if it's the X515b or a yet unknown one (by unknown I mean with regards to the model number)
I've already listed all the common and less-common models on the wiki: HTC Evo 3D - XDA wiki.
But I have no idea what the ISW12HT's model is, and a fair amount of googling turns up little.
If you could poke around your device/box/manual and find it I'd appreciate it
Hello,
I installed the AOKP "adrenalized" ROM yesterday (http://forum.xda-developers.com/showthread.php?t=1884085), and while I initially had a great experience with it, it seems several things have started to go wrong for me.
The most pressing issue is that I can no longer make any phone calls... within the first 12 hours or so of having the ROM, this was not an issue (I received a phone call), but all of a sudden, I no longer have any mobile signal (either 4g or 3g) whatsoever, and if I try to make a call, it says "Mobile network not available." I tried searching online for help with this, but I could not find anything.
The other two issues (these are not as pressing as my inability to make/receive calls) are a persistent error that I have a "Damaged SD card" and I can't access my internal storage when I hook up my phone to my PC. I did find someone else on another phone having an issue with AOKP/damaged sd card, but the fix suggested (editing a file called vold.fstab) did not work (the line to edit in the file was not present in my file).
Sorry for the long post - I am fairly inexperienced when it comes to this stuff, but any help is greatly appreciated.
rocketman13 said:
Hello,
I installed the AOKP "adrenalized" ROM yesterday (http://forum.xda-developers.com/showthread.php?t=1884085), and while I initially had a great experience with it, it seems several things have started to go wrong for me.
The most pressing issue is that I can no longer make any phone calls... within the first 12 hours or so of having the ROM, this was not an issue (I received a phone call), but all of a sudden, I no longer have any mobile signal (either 4g or 3g) whatsoever, and if I try to make a call, it says "Mobile network not available." I tried searching online for help with this, but I could not find anything.
The other two issues (these are not as pressing as my inability to make/receive calls) are a persistent error that I have a "Damaged SD card" and I can't access my internal storage when I hook up my phone to my PC. I did find someone else on another phone having an issue with AOKP/damaged sd card, but the fix suggested (editing a file called vold.fstab) did not work (the line to edit in the file was not present in my file).
Sorry for the long post - I am fairly inexperienced when it comes to this stuff, but any help is greatly appreciated.
Click to expand...
Click to collapse
Need a little bit more info for me to be helpful. S-on or off? Did you verify MD5 before installing? What rom did you come from? Latest firmware? Anything you can provide about your setup would be useful. TBH, it sounds like you had a bad download, so I'd try to re-download and verify MD5 before you install.
iamwalterwhite said:
Need a little bit more info for me to be helpful. S-on or off? Did you verify MD5 before installing? What rom did you come from? Latest firmware? Anything you can provide about your setup would be useful. TBH, it sounds like you had a bad download, so I'd try to re-download and verify MD5 before you install.
Click to expand...
Click to collapse
Thanks for your reply, iamwalterwhite. Here is the relevant information:
S-On
Previous ROM before AOKP: Scott's CleanROM Pro 4.5
Firmware: Android Version 4.0.4
Baseband version: 0.95.00.1118r, 0.95.00.1223r
Unfortunately, I did not check the MD5 before I installed because I thought the risk of not doing it would be low. Apparently, I was wrong! Given that information, do you think it is still worth verifying MD5 and re-installing AOKP? Thanks.
You are still on gb firmware. Flashing the old firmware patch may help.
Sent from my Kindle Fire using Tapatalk 2
pwned3 said:
You are still on gb firmware. Flashing the old firmware patch may help.
Sent from my Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
Wow, really? How can you tell? I thought Android version 4.0.4 was Ice Cream Sandwich, and I vaguely remember flashing a GB firmware patch when I first installed Scott's CleanROM 4.5, but my memory could be a bit fuzzy... should I just reboot to AmonRa recovery and flash it? Thanks for your help!
We can tell based off of your baseband version. Honestly, I think you should re-lock then flash the newest RUU. It will probably clear up your problem. If you'd still like, I can tell you how to check an MD5, but I think it's best if you flash that RUU. It's worth it, our radios have gone through multiple updates since the version that you have.
iamwalterwhite said:
We can tell based off of your baseband version. Honestly, I think you should re-lock then flash the newest RUU. It will probably clear up your problem. If you'd still like, I can tell you how to check an MD5, but I think it's best if you flash that RUU. It's worth it, our radios have gone through multiple updates since the version that you have.
Click to expand...
Click to collapse
Thanks, iamwalterwhite. I did some searching and found the latest RUU for the Rezound as 4.03.605.1 (I found it on Android Police, but I can't post the link since I'm a new user). However, it seems I am supposed to check the MD5 for that file as well.
Assuming that is the latest RUU though, then the steps I'd follow are: download the RUU/verify MD5, name it as PH98IMG.zip in my SDcard root, re-lock my bootloader, and finally reboot to AmonRa recovery to flash this RUU.
Are there any steps I am missing? Thanks again for your help... it is much appreciated.
You need to install in hboot not recovery. Running this will also write over your recovery. I suggest having the newest amon ra downloaded so you can unlock and flash it after the ruu
Sent from my Rezound using Xparent SkyBlue Tapatalk 2
rocketman13 said:
Thanks, iamwalterwhite. I did some searching and found the latest RUU for the Rezound as 4.03.605.1 (I found it on Android Police, but I can't post the link since I'm a new user). However, it seems I am supposed to check the MD5 for that file as well.
Assuming that is the latest RUU though, then the steps I'd follow are: download the RUU/verify MD5, name it as PH98IMG.zip in my SDcard root, re-lock my bootloader, and finally reboot to AmonRa recovery to flash this RUU.
Are there any steps I am missing? Thanks again for your help... it is much appreciated.
Click to expand...
Click to collapse
Have you set up an ADB folder? If so, place the RUU in your adb folder then execute this command in a command prompt:
cd c:\(your adb folder name)
You should then get a screen that looks like this:
c:\(your adb folder name)>
Then type: md5sums (ruu name).zip
Should look like this:
c:\(adb folder name)> md5sums (ruu name).zip
Your steps are mostly correct, however, you must flash the PH98IMG.zip via hboot. In fact, you won't be able to get to your recovery if you boot into your bootloader with the .zip on your sd card.
By the way, don't use the .1 RUU. Follow this link: http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/ This is the .2 (seems like a hopelessly miniscule difference), but it's the most current.
Edit: Since you are s-on, you will need to unlock via HTCDEV after the RUU. Then you can go about installing AR 3.15 the same way as you did before. If you plan on going s-off, you might want to consider doing that before running the RUU. I know it's a lot of information, and a lot to sift through (not to mention the many different ways to do do things) but going s-off makes it much more simple.
iamwalterwhite said:
Have you set up an ADB folder? If so, place the RUU in your adb folder then execute this command in a command prompt:
cd c:\(your adb folder name)
You should then get a screen that looks like this:
c:\(your adb folder name)>
Then type: md5sums (ruu name).zip
Should look like this:
c:\(adb folder name)> md5sums (ruu name).zip
Your steps are mostly correct, however, you must flash the PH98IMG.zip via hboot. In fact, you won't be able to get to your recovery if you boot into your bootloader with the .zip on your sd card.
By the way, don't use the .1 RUU. Follow this link: This is the .2 (seems like a hopelessly miniscule difference), but it's the most current.
Edit: Since you are s-on, you will need to unlock via HTCDEV after the RUU. Then you can go about installing AR 3.15 the same way as you did before. If you plan on going s-off, you might want to consider doing that before running the RUU. I know it's a lot of information, and a lot to sift through (not to mention the many different ways to do do things) but going s-off makes it much more simple.
Click to expand...
Click to collapse
A HUGE thank you to both of you!! I restored my phone to the .2 RUU, and I now have a working phone and proper access to my internal storage. Unfortunately iamwalterwhite, I didn't see your message until after I finished installing the RUU, so I am still on S-On, but I am rooted. Do you know if I could still get to S-Off from this point (i.e. after installing RUU on my phone)?
Also, do you think it is ok to try re-installing the AOKP ROM that previously gave me problems (I verified the MD5), or should I hold off/try another ROM?
Again, thanks to you both, iamwalterwhite and pwned3. I was pretty lost otherwise.
rocketman13 said:
A HUGE thank you to both of you!! I restored my phone to the .2 RUU, and I now have a working phone and proper access to my internal storage. Unfortunately iamwalterwhite, I didn't see your message until after I finished installing the RUU, so I am still on S-On, but I am rooted. Do you know if I could still get to S-Off from this point (i.e. after installing RUU on my phone)?
Also, do you think it is ok to try re-installing the AOKP ROM that previously gave me problems (I verified the MD5), or should I hold off/try another ROM?
Again, thanks to you both, iamwalterwhite and pwned3. I was pretty lost otherwise.
Click to expand...
Click to collapse
Sorry to post again, but I just had an issue arise that has been pestering me for a while. Anytime my GPS is on, my phone shuts off and reboots within a minute or so... I know Rezound folks had this problem a while back due to the Google Maps update, but I've been having this for a while, even when I was on Scott's CleanROM and with fixed Maps. Now that I am on RUU (rooted), I hoped this problem would go away because I use Navigation a lot... but unfortunately, it is still here. I currently have Maps 6.12.0.
Does anyone have any thoughts/suggestions? Thanks.
rocketman13 said:
A HUGE thank you to both of you!! I restored my phone to the .2 RUU, and I now have a working phone and proper access to my internal storage. Unfortunately iamwalterwhite, I didn't see your message until after I finished installing the RUU, so I am still on S-On, but I am rooted. Do you know if I could still get to S-Off from this point (i.e. after installing RUU on my phone)?
Also, do you think it is ok to try re-installing the AOKP ROM that previously gave me problems (I verified the MD5), or should I hold off/try another ROM?
Again, thanks to you both, iamwalterwhite and pwned3. I was pretty lost otherwise.
Click to expand...
Click to collapse
You're welcome, that's why they call this here a community. If I was you, I wouldn't try to s-off right now. The reason I say that is because the juopunutbear method to s-off uses a different hboot (I believe the jbear hboot is .25 while the RUU is .27). That hboot was compatible with the ICS ota pre-global. You may have to wait until they get an update do to it. At this point, you will only have to worry about extracting the boot.img for roms that aren't global based (aokp being an example), but that should be a small annoyance. Much smaller, than say, bricking your phone!
iamwalterwhite said:
You're welcome, that's why they call this here a community. If I was you, I wouldn't try to s-off right now. The reason I say that is because the juopunutbear method to s-off uses a different hboot (I believe the jbear hboot is .25 while the RUU is .27). That hboot was compatible with the ICS ota pre-global. You may have to wait until they get an update do to it. At this point, you will only have to worry about extracting the boot.img for roms that aren't global based (aokp being an example), but that should be a small annoyance. Much smaller, than say, bricking your phone!
Click to expand...
Click to collapse
A number of people have been successful with S-OFF on hboot 2.27 using the .5 ControlBear. There seem to be no issues with it at all.
shrike1978 said:
A number of people have been successful with S-OFF on hboot 2.27 using the .5 ControlBear. There seem to be no issues with it at all.
Click to expand...
Click to collapse
Just found this thread: http://forum.xda-developers.com/showthread.php?t=1883924&page=2 It looks like there have been a few successes wit s-off even after the .2 RUU. Thanks Shrike!
iamwalterwhite said:
Just found this thread: It looks like there have been a few successes wit s-off even after the .2 RUU. Thanks Shrike!
Click to expand...
Click to collapse
Oh man, I'm not sure I'm brave enough to do the infamous "wire trick" just yet... but I will keep that link as a reference once I feel more confident.
Also, sorry to bother you again, but did any of you happen to see my previous post about my GPS:
rocketman13 said:
Sorry to post again, but I just had an issue arise that has been pestering me for a while. Anytime my GPS is on, my phone shuts off and reboots within a minute or so... I know Rezound folks had this problem a while back due to the Google Maps update, but I've been having this for a while, even when I was on Scott's CleanROM and with fixed Maps. Now that I am on RUU (rooted), I hoped this problem would go away because I use Navigation a lot... but unfortunately, it is still here. I currently have Maps 6.12.0.
Does anyone have any thoughts/suggestions? Thanks.
Click to expand...
Click to collapse
As always, thank you very much!!
rocketman13 said:
Oh man, I'm not sure I'm brave enough to do the infamous "wire trick" just yet... but I will keep that link as a reference once I feel more confident.
Also, sorry to bother you again, but did any of you happen to see my previous post about my GPS:
As always, thank you very much!!
Click to expand...
Click to collapse
I saw that post abou GPS, but I'm not familiar with that at all. The only thing that I recall was the problem with the upgrade in google maps. Apophis has a thread over in General where he lists his g-talk (along with some other users). He might be able to help.
iamwalterwhite said:
I saw that post abou GPS, but I'm not familiar with that at all. The only thing that I recall was the problem with the upgrade in google maps. Apophis has a thread over in General where he lists his g-talk (along with some other users). He might be able to help.
Click to expand...
Click to collapse
Ok, great! I'll see if I can ask about the GPS. Thanks for your help!
Hello everyone Im hoping someone can help me with a problem I'm having :/ . I want to go back to stock but I can't find the right ruu. I got a refurbished phone from VM and it came with 1.58 and radio 1.09 and flashed the nega rom but I want to go back to stock but everytime it says error when trying to ruu the phone. Can someone help me find the right ruu or tell me what I'm doing wrong? Ohh and I'm s-on.
Anyone? im almost crying of how fed up trying to find the problem ! :/ i cant find the fastboot drivers for the phone either
fabyprado123 said:
Hello everyone Im hoping someone can help me with a problem I'm having :/ . I want to go back to stock but I can't find the right ruu. I got a refurbished phone from VM and it came with 1.58 and radio 1.09 and flashed the nega rom but I want to go back to stock but everytime it says error when trying to ruu the phone. Can someone help me find the right ruu or tell me what I'm doing wrong? Ohh and I'm s-on.
Click to expand...
Click to collapse
There is no RUU available yet that will work with the 2.95 update installed which is apparently how you go the phone. You can either get S-OFF and then flash the original RUU and take the two OTA updates, or try flashing one of the stock ROM's in this post. If you want to go back to almost 100% stock and unrooted you will need to flash the unrooted version of the stock ROM and then flash the stock recovery.
The one thing that won't be stock in that scenario is the bootloader since if you lock it the status will show "relocked" rhater than "locked".
ramjet73
I want to thank you for replying !!! ive seen many posts and you are like a god of the Htc evo 3d ! Im trying to get s off with jbear but i get the error message " connect device and install drivers" i think it might be the fastboot but not sure can you help me with that?
fabyprado123 said:
I want to thank you for replying !!! ive seen many posts and you are like a god of the Htc evo 3d ! Im trying to get s off with jbear but i get the error message " connect device and install drivers" i think it might be the fastboot but not sure can you help me with that?
Click to expand...
Click to collapse
You need to install the HTC drivers. Which version of Windows are you using?
Getting S-OFF with hboot 1.58 installed is still uncharted territory for VM users. I suggest you check out the related threads in this forum and post there for help since there are a lot of Evo V 4G users there that can help. They are actually looking for someone in your situation who is willing to try getting S-OFF so I'm sure you will get lots of help.
ramjet73
will do ive tried installing random drivers i find for the evo 3d but dont work :/ do you know where to put the folder for the drivers? thank you so much for your help btw
Dude !! I finally got s-off !!!
fabyprado123 said:
Dude !! I finally got s-off !!!
Click to expand...
Click to collapse
Great!
How did you do it?
ramjet73
I flashed viper Rom (don't remember which one) and that gave me stock kernel. Then, I downloaded a .zip file with the drivers to the phone and used the jbear program to s-off. Then , I put 1.04.200 hboot and used the ruu to bring me back to stock. Updated my phone and I am all good. If I get all the folders together might make a tutorial on how to get s-off even after taking the OTS updates on s-on. Or prob. You can hel0 me ramjet73?
Sent from my HTCEVOV4G using xda app-developers app
fabyprado123 said:
I flashed viper Rom (don't remember which one) and that gave me stock kernel. Then, I downloaded a .zip file with the drivers to the phone and used the jbear program to s-off. Then , I put 1.04.200 hboot and used the ruu to bring me back to stock. Updated my phone and I am all good. If I get all the folders together might make a tutorial on how to get s-off even after taking the OTS updates on s-on. Or prob. You can hel0 me ramjet73?
Click to expand...
Click to collapse
Well, we already have guides on both XDA and androidforums.com and the unlimited.io developers that created JuopunutBear have gotten very sensitive about having instructions posted in other places.
I'm curious how you did the wire trick since the Windows downloads are no longer on the unlimited.io website. Did you use an existing guide? At this point we are just trying to figure out what is the best version of JBear to use after VM users have installed the March OTA and have hboot 1.58.
ramjet73
I'm not sure ? I have the folder though , I can send it to you and you can take a look at it?
Sent from my HTCEVOV4G using xda app-developers app
fabyprado123 said:
I'm not sure ? I have the folder though , I can send it to you and you can take a look at it?
Click to expand...
Click to collapse
Yea, just for the jbear portion. I'd appreciate it if you can zip it up and upload it to dropbox or similar and PM the link to me.
As I said, at this point we are just trying to determine which jbear version works best with the Evo V updated to the March OTA and hboot 1.58. If the most effective process warrants a new guide I will be happy to work with you on that.
ramjet73
Program I used to S-OFF
I dont think its letting me send the link to the program i used. Can I post it here?
Hello. Never made a thread before and was really hoping I wouldn't have to or would find an answer elsewhere.
Since that didn't work out, here's my problem:
Background: Evo 3d, virgin mobile, unlocked bootloader, s-off, hboot was at 1.50, and I don't remember what the radio was at. I was running CM11 and was quite happy until two days ago when I stopped receiving texts! No clue why, just stopped. Hangouts, etc etc. Called VM and they had no idea why that was happening either. Tried switching roms, reinstalling backups, etc etc. Clean wipes and all. Then I saw someone said they had to [for some reason] reinstall everything stock and then they had messaging back. So that's what I set out to do.
In Between: Used the RUU that I'm fairly certain came with my phone. Everything was good, it erased everything, and "updated system" and signatures. It was almost finished when BAM, popped up with error 152 Image Update Error; right at the very end. Quite disappointing. Tried it multiple times again with the same result. Not sure what to do.
Current: Only screen I can see (looks like shortened bootloader screen) says "***locked***" at the top, hboot 1.57.0000, radio 1.06.00.126, then says openADSP-v02.6.0.2226.00.0217eMMc-boot
Also tried flashing the unlock_code.bin, and while it took it, it changed nothing. One screen I did see very briefly but cannot replicate said that everything was there except system. Not really sure how to take that or what to do. Any and all help would be helpful. As is it sits on the HTC screen with exclamation points in each corner. When unplugged from usb it gives me that above screen. Removing battering and restarting to bootloader still gives the same screen.
Did you run ruu through windows or pg86img.zip?
Sent from my Evo 3D CDMA using xda app-developers app
hossman said:
Did you run ruu through windows or pg86img.zip?
Sent from my Evo 3D CDMA using xda app-developers app
Click to expand...
Click to collapse
Through Windows; the RUU exe.
SammyMak said:
Through Windows; the RUU exe.
Click to expand...
Click to collapse
You can try this
https://www.dropbox.com/s/d4baafpgchgg4ef/ruu-PG86IMG.zip
Put that on the root of your SD card and rename to pg86img.zip
Make sure its the only one there
Boot to boot loader and accept updates
It may reboot itself to bootloader, if it asks to accept again then accept
When its done reboot your phone
Rename or remove the file when done
Hope that helps
Sent from my Evo 3D CDMA using xda app-developers app
So I have my phone working now. I think it was the RUU.exe that I was using. I downloaded a different one from here http://androidruu.com/Shooter/ after much googling. That finally restored it to original VM stock rom etc. I couldn't use your method of placing the zip onto the root of my SD because despite it being there, it wouldn't go through the normal search for the file. I would remove the battery, put it back in, use the button key combo to try and open to bootloader, and it would go but it would be the page with the status and then it would instantly go back to the black screen with HTC logo.
Thank you for your help though!
Also I'm not sure how useful exactly this will be for anyone else, but if you find yourself ruu'd and needing better files...
The hboot ENG 1.04 I got from here: http://forum.xda-developers.com/showthread.php?t=1817513
ALL other downloads of that hboot did not work AT ALL.
I got the updated radio from here: http://androidforums.com/cdma-evo-3d-all-things-root/648902-radios-hboot-firmware-all-downloads.html
The hboots on that site however are stock and most likely won't run the custom roms as well, if at all, as 1.04.
SammyMak said:
I got the updated radio from here: http://androidforums.com/cdma-evo-3d-all-things-root/648902-radios-hboot-firmware-all-downloads.html
But the hboots on the site aren't helpful fyi
Click to expand...
Click to collapse
Hey, that's my thread. Just curious what you mean by the hboots aren't helpful?
If there is a problem I'm unaware of, I'd be happy to know what it is so I can get it squared away.
hossman said:
You can try this
https://www.dropbox.com/s/d4baafpgchgg4ef/ruu-PG86IMG.zip
Put that on the root of your SD card and rename to pg86img.zip
Make sure its the only one there
Boot to boot loader and accept updates
It may reboot itself to bootloader, if it asks to accept again then accept
When its done reboot your phone
Rename or remove the file when done
Hope that helps
Sent from my Evo 3D CDMA using xda app-developers app
Click to expand...
Click to collapse
thank you!
Brian706 said:
Hey, that's my thread. Just curious what you mean by the hboots aren't helpful?
If there is a problem I'm unaware of, I'd be happy to know what it is so I can get it squared away.
Click to expand...
Click to collapse
I must apologize! I seem to have mis stated that; they are helpful with regards to them being the stock hboots. However in my particular case those stock hboots weren't for me. I'll edit that here in a sec, but if I was going back to full stock I'd definitely use your stock VM hboot and it would be helpful in that case. Hope that makes sense, no disrespect meant!
SammyMak said:
I must apologize! I seem to have mis stated that; they are helpful with regards to them being the stock hboots. However in my particular case those stock hboots weren't for me. I'll edit that here in a sec, but if I was going back to full stock I'd definitely use your stock VM hboot and it would be helpful in that case. Hope that makes sense, no disrespect meant!
Click to expand...
Click to collapse
Thanks for clarifying that! I see what you meant now.
No worries, I didn't take offense or think you were disrespectful; I just wanted to make sure the downloads were working properly!
And for the record, the stock hboots will work just fine with custom roms. Hboot 1.50 for example will be compatible with the same selection of roms as JuopunutBear 1.50.5050. The difference is that JuopunutBear is patched and will allow for extra fastboot commands and allow them to be run on a locked bootloader.
The eng 1.04 hboot allows for extra fastboot commands that the stock hboot cannot. But you can boot any rom out there on the stock hboots. I've used stock 1.50 forever on this device.