Related
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
I am the cause of this problem, and hope someone can help to extricate me.
I bought my Rezound in April, excited that ICS was coming. I soon found the leaked ICS 4.0.3/Sense 3.6 and installed the leak, and have been (largely) happily enjoying it. There have been some small issues, and when I read that Verizon was finally sending ICS out to the Rezound, I checked and found that I couldn't get it unless my phone was put back to GB. That's when the problem started.
I've tried numerous ROMs, but really don't know what I'm doing, and after almost 20 hours of reading the various posts and searches, am no farther to a resolution than where I started yesterday.
The phone, no matter what I try to load, boots fine until it hits the 4G LTE screen and then freezes. Here's the HBOOT/FASTBOOT screen:
*** LOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP--v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012,19:24:37
I would love to get it whole enough to receive OTAs, but would be happy to get back where I started. Can someone help me please?
gandroid2 said:
I am the cause of this problem, and hope someone can help to extricate me.
I bought my Rezound in April, excited that ICS was coming. I soon found the leaked ICS 4.0.3/Sense 3.6 and installed the leak, and have been (largely) happily enjoying it. There have been some small issues, and when I read that Verizon was finally sending ICS out to the Rezound, I checked and found that I couldn't get it unless my phone was put back to GB. That's when the problem started.
I've tried numerous ROMs, but really don't know what I'm doing, and after almost 20 hours of reading the various posts and searches, am no farther to a resolution than where I started yesterday.
The phone, no matter what I try to load, boots fine until it hits the 4G LTE screen and then freezes. Here's the HBOOT/FASTBOOT screen:
*** LOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP--v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012,19:24:37
I would love to get it whole enough to receive OTAs, but would be happy to get back where I started. Can someone help me please?
Click to expand...
Click to collapse
Someone more knowledgeable may correct me, but HBOOT 2.27 & 2.22 radios are the newest version. So you're already upgraded to the newest stuff. Try installing an AOSP or ICS ROM and see if that works.
I made progress?
d.kozzer said:
Someone more knowledgeable may correct me, but HBOOT 2.27 & 2.22 radios are the newest version. So you're already upgraded to the newest stuff. Try installing an AOSP or ICS ROM and see if that works.
Click to expand...
Click to collapse
Thank you, that's actually more good news than I expected!
I have lost total confidence in any knowledge I thought I had. If someone could give me 1st grader level guidance toward installing an AOSP or ICS ROM, I would be most appreciative.
gandroid2 said:
Thank you, that's actually more good news than I expected!
I have lost total confidence in any knowledge I thought I had. If someone could give me 1st grader level guidance toward installing an AOSP or ICS ROM, I would be most appreciative.
Click to expand...
Click to collapse
It's easy.... if you like AOSP/CM9, I'd recommend the "le n00b" ROM in the dev section. If you like Sense 3.6, try Vigor360. If you like Sense 4, I really liked ViperRom. Just go to the OP of any thread for those, download the newest version to a PC or onto your SD card.
Then, go check out Scotty's noob friendly guide to rooting on AndroidForums (there might be an equivelent thread here, but I used this guide). I recommend using Amon Ra as your recovery, which is linked toward the top of the first post.
gandroid2 said:
Thank you, that's actually more good news than I expected!
I have lost total confidence in any knowledge I thought I had. If someone could give me 1st grader level guidance toward installing an AOSP or ICS ROM, I would be most appreciative.
Click to expand...
Click to collapse
if you want to go aosp you will need to s-off the phone to get there.
but you are on the latest update. you can only run roms built off the global ruu such as:
http://forum.xda-developers.com/showthread.php?t=1852119
http://forum.xda-developers.com/showthread.php?t=1860632
http://forum.xda-developers.com/showthread.php?t=1855605
to flash said roms you will need to htc dev unlock and then flash a recovery and then you can do any of the three roms above. if you want to be on a rom that is build off an older release you will need to s-off the phone.
d.kozzer said:
It's easy.... if you like AOSP/CM9, I'd recommend the "le n00b" ROM in the dev section. If you like Sense 3.6, try Vigor360. If you like Sense 4, I really liked ViperRom. Just go to the OP of any thread for those, download the newest version to a PC or onto your SD card.
Then, go check out...QUOTE]
Thanks a bunch. I've opened Scotty's guide to read next, and have downloaded Amon Ra (recovery-ra-vigor-3.15-gnm.img.zip). I've looked up some comparisons between Sense 3 & 4, which should help me make an informed decision. Thanks again for the guidance and suggestions.
Click to expand...
Click to collapse
synisterwolf said:
if you want to go aosp you will need to s-off the phone to get there.
but you are on the latest update. you can only run roms built off the global ruu such as:
to flash said roms you will need to htc dev unlock and then flash a recovery and then you can do any of the three roms above. if you want to be on a rom that is build off an older release you will need to s-off the phone.
Click to expand...
Click to collapse
Thanks synisterwolf.
I'll look at the roms you recommended and appreciate the information and wisdom you shared.
I'll also check out the organizations listed in your signature.
Thanks again.
I would use hasoons toolkit to unlock and install amon ra. The 4.03.605.2 RUU runs smooth and quick.
gandroid2 said:
d.kozzer said:
It's easy.... if you like AOSP/CM9, I'd recommend the "le n00b" ROM in the dev section. If you like Sense 3.6, try Vigor360. If you like Sense 4, I really liked ViperRom. Just go to the OP of any thread for those, download the newest version to a PC or onto your SD card.
Then, go check out...QUOTE]
Thanks a bunch. I've opened Scotty's guide to read next, and have downloaded Amon Ra (recovery-ra-vigor-3.15-gnm.img.zip). I've looked up some comparisons between Sense 3 & 4, which should help me make an informed decision. Thanks again for the guidance and suggestions.
Click to expand...
Click to collapse
Unfortunately, Scotty's guide won't work for me, as its unlock with htcdev section requires the Rezound to connect to my PC via usb, but the phone's somewhat bricked, locking up at the 4G LTE screen and won't connect.
I would surely appreciate other suggestions. Plemelin recommended hasoons toolkit, and I will look at it now.
Thanks again.
Click to expand...
Click to collapse
plemelin said:
I would use hasoons toolkit to unlock and install amon ra. The 4.03.605.2 RUU runs smooth and quick.
Click to expand...
Click to collapse
Thank you. I'm looking at it next.
plemelin said:
I would use hasoons toolkit to unlock and install amon ra. The 4.03.605.2 RUU runs smooth and quick.
Click to expand...
Click to collapse
Yeah, this is a good tool too.
gandroid2 said:
Thank you. I'm looking at it next.
Click to expand...
Click to collapse
For Scotty's guide, you're clearly on the HTC Unlock stage,maybe you should find the latest RUU and flash that? It'll have all parts of the phone's system (ROM, bootloader, recovery, radios, etc), so you'll have a clean phone (meaning all data will be wiped), and all the different pieces will work together and you should be able to boot into the stock ROM, then follow the guide from there starting with the HTC unlock. I think where you were at in post #1, you had all the ICS/global firmware but were trying to boot a gingerbread ROM which will fail every time. If you use an RUU, everything will be in sync.
d.kozzer said:
Yeah, this is a good tool too.
For Scotty's guide, you're clearly on the HTC Unlock stage,maybe you should find the latest RUU and flash that? It'll have all parts of the phone's system (ROM, bootloader, recovery, radios, etc), so you'll have a clean phone (meaning all data will be wiped), and all the different pieces will work together and you should be able to boot into the stock ROM, then follow the guide from there starting with the HTC unlock. I think where you were at in post #1, you had all the ICS/global firmware but were trying to boot a gingerbread ROM which will fail every time. If you use an RUU, everything will be in sync.
Click to expand...
Click to collapse
Nice,that's the original version which started this journey. I had downloaded it prior to starting all this, and messed up my Rezound by not doing it correctly. Now it's the one which (finally) worked. I don't know how it worked, unfortunately, as it didn't work exactly like Scotty told me it would, and the first few times I tried to install it were unsuccessful also.
Thanks again.
It's alive!
Thank you all for your help. Your replies encouraged me and directed me toward the solution.
Scotty's guide worked, although not exactly like it said it would. I now have the version I originally wanted, and it all works, except for the SU.
I installed CWM-SuperSU-v0.96.zip per Scotty, but I have don't have the SU ability. Undoubtedly did something wrong.
Thanks again.
gandroid2 said:
Thank you all for your help. Your replies encouraged me and directed me toward the solution.
Scotty's guide worked, although not exactly like it said it would. I now have the version I originally wanted, and it all works, except for the SU.
I installed CWM-SuperSU-v0.96.zip per Scotty, but I have don't have the SU ability. Undoubtedly did something wrong.
Thanks again.
Click to expand...
Click to collapse
Glad to help!
If you're using SU, then open up the app by going into the app drawer and see if there's a way for you to "update the binary". The binary is the meat and bones of the superuser app, and for some reason it's not working well out of the box on some roms, and you need to update it to get it working.
d.kozzer said:
Glad to help!
If you're using SU, then open up the app by going into the app drawer and see if there's a way for you to "update the binary". The binary is the meat and bones of the superuser app, and for some reason it's not working well out of the box on some roms, and you need to update it to get it working.
Click to expand...
Click to collapse
Apparently I'm not using SU after all.I tried to update with superuser and it "Failed to find currently installed su binary". I also opened Titanium Backup and it couldn't acquire root privileges. I missed something...
Hello i need help unrooting my evo lte.I used zedomax method to get super su.I didnt know or should i say i didnt read that it doesnt unlock the booloader.the process is to complicated for me.Iam now trying to unroot and return to stock.I know if you go into super su you can undo the changes to go back to your prevthat were made.my bootloader is locked.I have s-on.I have been trying to install the ruu that matches my phones software settings.i downloaded the drivers for the evo.I downloaded microsoft framework 4.0.my problem is this every time i go to install the ruu it fails because my drivers go back to saying android 1.0 and when i try to update drivers it does not let me.i am running on windows 7 64bit.this is really getting annoying.Is there any way to install the ruu through the bootloader?One more thing i tried putting the phone in fastboot on the bootloader but i still get the android 1.0 and i cant update the drivers on my pc..I am running software version 1.12.651.1 710rd.If anyone can help i would really appreciate it thanks.P.S pardon my poor grammer.
http://forum.xda-developers.com/showthread.php?t=1671577
How to Root/Unroot HTC Evo 4G LTE! [Windows/Mac/Linux][One-Click][<=1.22.651.1]
A quick peek at the android development section would have been quick and painless
not working
I did check out the thread.Im following the intructions.Like i said before when installing the ruu and my phone try s to reboot into the bootloader i get a error code 171.Thats because i cant update the drivers during the process.I go from my htc to android 1.0 and i cant update the drivers.Also one more thing my software version is displayed as 1.13.651.1_r2.But the ruu i downloaded only say 1.13.651.1.Can i still use that ruu?I cant seem to find a ruu thast has the _r2 at the end.Im sorry that im being a pain in the butt.
No its not that you are being a pain it's just that there's been a rash of people trying to revert to stock to take the ota. They all ask the same question and then they don't follow the directions or they don't read them correctly and end up back here with more issues. Try flashing a stock recovery and take the ota
A couple days ago I felt the same exact way thinking if anything happens to my phone I can't return it to sprint or anyone I rooted the same exact method that you did but I did my research and eventually gave up on trying to flash a ruu over being rooted with the boot loader unlocked has way more perks then having stock sense 4.0 if you ever need to update radios or anything upgrade the android software later on all you do is flash it there's so many people on xda to help you along the way as well believe me I thought I messed up my phone several times but like I said thanks to the good people at xda I'm enjoying my phone a lot better then the day I bought it brand new
Sent from my EVO using xda app-developers app
om4 said:
No its not that you are being a pain it's just that there's been a rash of people trying to revert to stock to take the ota. They all ask the same question and then they don't follow the directions or they don't read them correctly and end up back here with more issues. Try flashing a stock recovery and take the ota
Click to expand...
Click to collapse
Question, how do I flash back to stock recovery?
fastboot the recovery image
Hey gang -
Working with my EVO 3D (Virgin Mobile) - and I'm stuck in a world of S-ON. The pre-requisites state that for the S-OFF Wire trick to work you must be on Windows 7 or less and be using specific version of HTC drivers. I'm running Windows 8, the specific version of HTC drivers recommended (HTC Driver 3.0.0.007) will not work in Windows 8. Needless to say I've not been able to get the wire trick to work and I'm "still sober". I've had very little success trying roms that will work and be happy with an S-ON phone. Until I decide to downgrade a machine back to Windows 7... what roms should I look for that I'll actually be able to use without bootlooping? So far the Midnight rom worked but is incredibly battery hungry (10 minutes of facebooking drops the battery 20-25%) - and today I installed MeanRom which seems to be doing better in the battery department.
Just looking for friendly advice... I've kinda given up on the wire trick for now.
Midnight1970 said:
Hey gang -
Working with my EVO 3D (Virgin Mobile) - and I'm stuck in a world of S-ON. The pre-requisites state that for the S-OFF Wire trick to work you must be on Windows 7 or less and be using specific version of HTC drivers. I'm running Windows 8, the specific version of HTC drivers recommended (HTC Driver 3.0.0.007) will not work in Windows 8. Needless to say I've not been able to get the wire trick to work and I'm "still sober". I've had very little success trying roms that will work and be happy with an S-ON phone. Until I decide to downgrade a machine back to Windows 7... what roms should I look for that I'll actually be able to use without bootlooping? So far the Midnight rom worked but is incredibly battery hungry (10 minutes of facebooking drops the battery 20-25%) - and today I installed MeanRom which seems to be doing better in the battery department.
Just looking for friendly advice... I've kinda given up on the wire trick for now.
Click to expand...
Click to collapse
CyanogenMod 10.1 - WILD FOR THE NIGHT Works like a dream! http://forum.xda-developers.com/showthread.php?t=2098121&nocache=1 Also compatible with Virgin (It says you need S-Off but I have S-On on my Evo 3D, just need to use Flash Image GUI)
jsls said:
CyanogenMod 10.1 - WILD FOR THE NIGHT Works like a dream! http://forum.xda-developers.com/showthread.php?t=2098121&nocache=1 Also compatible with Virgin (It says you need S-Off but I have S-On on my Evo 3D, just need to use Flash Image GUI)
Click to expand...
Click to collapse
Are you on the Sprint 1.5 hboot?
WFTN is not going to boot with the stock 1.57 VM hboot.
ramjet73
Yes, sadly I'm on 1.57 hboot. This has been quite the thorn in my side.
Only one i know is Harmonia from andriodforums evo v 4g sections.
Not sure if you can run Wild for the night, but its my rom of choice but im s-off.
Looking at Harmonia now - thanks for the suggestion - I'm running MeanRom since last night.
MeanRom's battery performance is better than the last one I was using, MidnightRom.
Being stuck in the world of S-ON sucks... I want so much to try the AOKP/AOSP roms.... ugh!
Midnight1970 said:
Looking at Harmonia now - thanks for the suggestion - I'm running MeanRom since last night.
MeanRom's battery performance is better than the last one I was using, MidnightRom.
Being stuck in the world of S-ON sucks... I want so much to try the AOKP/AOSP roms.... ugh!
Click to expand...
Click to collapse
The requirements for the JuopuntBear wire trick have been changed to Ubuntu Linux and they no longer support Windows at all. There's a live CD linked from the unlimited.io website that can be booted without having to actually install Linux so you might want to give that a try.
I have a guide here for root/S-OFF that might work with Windows 8 if you use this guide to install the drivers.
ramjet73
Thanks ramjet - I'm looking at that info now. It sure is a lot to consume.
Most guides all say "click this post" for reference, that has a link within to click another post, which links to another post... lol, gets to where I've got 10 tabs open in no time... not complaining at all, just a bit time consuming to ensure all the info has been digested...
I'm having fits!
I followed the guide... got the RUU installed and configured.... unlocked the bootloader (again)... flashed the SU.... now when I try to run ControlBear it won't complete, saying it can't transfer the backups - looking at the JuopunutBear website it says that error is due to a custom rom or htc sync installed.... I don't have htc sync and the rom is the RUU.... I'm really confused now...
Midnight1970 said:
I'm having fits!
I followed the guide... got the RUU installed and configured.... unlocked the bootloader (again)... flashed the SU.... now when I try to run ControlBear it won't complete, saying it can't transfer the backups - looking at the JuopunutBear website it says that error is due to a custom rom or htc sync installed.... I don't have htc sync and the rom is the RUU.... I'm really confused now...
Click to expand...
Click to collapse
If you are using my guide, restart controlbear.exe and check the screen for superuser access prompts that need to approved. That's usually why the secondary backup fails.
ramjet73
Well I'll be........
Guess it would help if I actually looked at the screen, huh?
Well... I'm happy to report that after following your guide, ramjet, that I'm officially S-OFF!!! (after only the 2nd try) - I'm a happy man tonight!! Thank you sir...
I'm also refreshed that I was able to ask my questions and receive the answers and help I needed without a "xda smackdown" that tends to follow such newbie questions. For this I'm grateful.
Installed my first AOKP rom, TeamDIRT_DirtyUnicorns_V1.2, and its bootlooping after the install... never made it to the setup screen.
Ugh....
Have you installed another hboot? 1.50 and below to boot aosp based ROMs. Either do the PG86IMG.zip method, or my new favorite, search XDA for fastboot commander. I had to use it for my gfs evo v 4g because I couldn't get the pg86img to work because of the cid. I recommend 1.50.5050 jbear or 1.04 eng.
Sent from my PG86100 using xda premium
Its on JuopunutBear hboot but its still 1.57 ... guess I need to figure out how to get to 1.50.5050.... argh.
Ready to start screaming, lol ... really thought I had it with the wire trick... double argh...
Found the thread for the PG86IMG_JBear_1.50.5050_hboot_GB -
Rename this to just PG86IMG.zip and let the bootloader flash it?
Midnight1970 said:
Found the thread for the PG86IMG_JBear_1.50.5050_hboot_GB -
Rename this to just PG86IMG.zip and let the bootloader flash it?
Click to expand...
Click to collapse
That's it.
Congratulations on getting S-OFF.
ramjet73
I think I screwed up.... after going back to the RUU - I forgot to install the OTA update while on the stock RUU... now I'm having troubles sending and receiving texts.... do I have to start over from scratch?
I was getting the Radio Interface Resource Shortage error msg - I rebooted the phone and all seems well now... hmm.
Midnight1970 said:
I think I screwed up.... after going back to the RUU - I forgot to install the OTA update while on the stock RUU... now I'm having troubles sending and receiving texts.... do I have to start over from scratch?
Click to expand...
Click to collapse
No problem.
Since you are S-OFF now you can just flash the firmware only updates from both the VM OTA's (November and March). The November update is in this post and the March update is in this post. Just flash them in sequence from the bootloader.
ramjet73
If I use fastboot commands to push those updates, can I rename them or do they have to remain named PG86IMG.zip?
I created a similar thread the other day but it got so overwhelming and it was just confusing me more so I deleted it. I'm starting a fresh one so I can maybe explain myself better, not confuse anyone else and get better answers.
I just got a replacement Rezound in the mail today. My phone is currently on 4.05.605.14 710RD, LOCKED, HBOOT is 2.28.0000 & radios are 2.23.10.0123r/2.23.10.0124r.
That last time I was able to S-OFF I used the wire method and ControlBear for Windows. I went to the website Unlimited.IO and they no longer support Windows so I have no idea on how to S-OFF since I did it months ago. However, I did find ControlBear v0.1 for Windows here on the forums: http://forum.xda-developers.com/showpost.php?p=27764982&postcount=2079 My first question is will this version work for me? If you download it and open it you can see the zips contents. I wasn't sure If had to RUU back down to an earlier version for it to work? And last time I ended up being on a Juopunutbear HBOOT somehow.
So basically I want to be able to get back onto CyanogenMod 10.1 properly this time. I haven't done anything to my phone yet, still unrooted, on stock, etc.. I know my first step is too unlock it using the htcdev website but from there I'm confused, I can't remember the steps its been too long.
I need someone to please explain how I can get back to CM 10.1 and remain on the latest firmware/drivers/hboot etc. So I need help with rooting, s-off, how to get TWRP recovery back on, which to do first, etc.
I appreciate the help and I'll make sure I save this in case it ever happens again. Also, my apologies again for the previous thread, it was just too much going on, I just need simple steps.
Am not positive but i think u will need Ubuntu as that one wont work on the new 2.28 hboot. So lets start with u installing ubuntu on a drive or live cd
Sent from my Infected Rezound using xda app-developers app
xanda143 said:
Am not positive but i think u will need Ubuntu as that one wont work on the new 2.28 hboot. So lets start with u installing ubuntu on a drive or live cd
Sent from my Infected Rezound using xda app-developers app
Click to expand...
Click to collapse
ControlBear 0.1 worked for me on Windows, took a few tries but it finally pulled through. These where my steps:
1. unlocked
2. flashed recovery
3. flashed [ROM] OTA-Global-Stock-4.05.605.14 710RD-Rooted 5/1/13
4. flashed boot.img from the rom
5. did wired trick with CB 0.1
so i think im good now? just have a couple questions.
- my phone now says tampered/locked/s-off? last time i s-off it didnt have that tamper there, is this normal?
- im still on hboot 2.28.0000 & radio 2.23.10.0123r/2.23.10.0124r. is this latest hboot/firmware/radio?
- im still on that rom that i linked above. im good to go ahead and flash and jb rom now?
- last, is there anything else i need to do with my phone? fixing the mainver, etc.
xXezmacXx said:
- my phone now says tampered/locked/s-off? last time i s-off it didnt have that tamper there, is this normal?
- im still on hboot 2.28.0000 & radio 2.23.10.0123r/2.23.10.0124r. is this latest hboot/firmware/radio?
Click to expand...
Click to collapse
That's normal if you're still using an unpatched hboot. If you will still use some fastboot commands (I use fastboot boot zImage/fastboot flash zimage zImage alot) then look into vynlfreak's 2.27 patched hboot. DO NOT UNLOCK flash patched hboot instead.
xXezmacXx said:
- im still on that rom that i linked above. im good to go ahead and flash and jb rom now?
- last, is there anything else i need to do with my phone? fixing the mainver, etc.
Click to expand...
Click to collapse
Flash your rom and don't worry about mainver.
Just wanted to thank you two. I have always been hesitant about s-offing my phone. But seeing it here in a few simple steps gave me the courage to finally pull the trigger. I know I am super late to the S-Off party, but am thrilled to finally have arrived!