Hboot 2.09
I've unlocked the bootloader and rooted my phone. I'm using the TWRP recovery, and am S-ON. I successfully flashed ViperMOD, but when I got to the start up screen, the touch screen and the haptic buttons would not respond. Thinking it was the ROM, I flashed CM10 only to find that I had the exact same problem there. I'm flashing the ROM first in TWRP and then the boot.img through fastboot. I know it is something software related because the touch functionality works in TWRP but not in any ROM.
Thanks in advance
Sent from my Galaxy Nexus using xda app-developers app
Bastakks said:
Hboot 2.09
I've unlocked the bootloader and rooted my phone. I'm using the TWRP recovery, and am S-ON. I successfully flashed ViperMOD, but when I got to the start up screen, the touch screen and the haptic buttons would not respond. Thinking it was the ROM, I flashed CM10 only to find that I had the exact same problem there. I'm flashing the ROM first in TWRP and then the boot.img through fastboot. I know it is something software related because the touch functionality works in TWRP but not in any ROM.
Thanks in advance
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Did you flash the full 3.16 OTA with the tp.img? tp.img works with TWRP 2.4.1.0 and any 3.16 based ROM but not any 3.15 ROM or AOSP rom. If you did, you have two choices. Either you can only use 3.16 roms, or you can try flashing this: http://themikmik.com/showthread.php?13192-FIRMWARE-S-OFF-1-12-HBOOT-ONLY-Jewel-Firmware-Collection-Latest-Radio-1-12-11-1210&p=286650&viewfull=1#post286650 That is the tp.img from 3.15 firmware and some have reported that it fixes this problem. You must flash this by renaming it to PJ75IMG.zip, putting it in the root of your external SD card, and going to bootloader. Upon request, accept the flash. Make sure you don't have another PJ75IMG.zip file in your external SD card. I'm not sure personally if this works but it's worth trying.
grizzlywan said:
Did you flash the full 3.16 OTA with the tp.img? tp.img works with TWRP 2.4.1.0 and any 3.16 based ROM but not any 3.15 ROM or AOSP rom. If you did, you have two choices. Either you can only use 3.16 roms, or you can try flashing this: http://themikmik.com/showthread.php?13192-FIRMWARE-S-OFF-1-12-HBOOT-ONLY-Jewel-Firmware-Collection-Latest-Radio-1-12-11-1210&p=286650&viewfull=1#post286650 That is the tp.img from 3.15 firmware and some have reported that it fixes this problem. You must flash this by renaming it to PJ75IMG.zip, putting it in the root of your external SD card, and going to bootloader. Upon request, accept the flash. Make sure you don't have another PJ75IMG.zip file in your external SD card. I'm not sure personally if this works but it's worth trying.
Click to expand...
Click to collapse
You have to be S-OFF to flash PJ75IMG.zip files in bootloader
If you have no way of flashing the 3.15 tp firmware, your only option is to flash a 3.16 rom.
My recommendation is in my signature below.
Sent from my MeanBean optimized and supercharged ElteVO.
I have done all of that. As the next post states, it doesn't work on S-ON devices. Looks like I'll be mucking about with a Linux live CD since I have 64windows and dirtyracun won't run on it.
Sent from my Galaxy Nexus using xda app-developers app
I am having exactly the same issue. I have successfully flashed several different roms (Charmeleon, UR Evo, Viper) and once loaded, I have no touchscreen response at all. At this point, I want to relock it, but when I attempt the RUU, the program doesn't see the phone (all drivers are installed). I can't get the phone to work so I had to buy a cheap tracfone to use in the mean time. Any suggestions? (I wish I'd saved a copy of the stock rom after unlocking but I thought it would work so I didn't)
Also, I have tried flashing MeanBean (which fails outright) and CyanogenMod, Avatar, and Evervolv (all of which hang out on the loading screen and never progress). I just want my phone back.
brinnanza said:
I am having exactly the same issue. I have successfully flashed several different roms (Charmeleon, UR Evo, Viper) and once loaded, I have no touchscreen response at all. At this point, I want to relock it, but when I attempt the RUU, the program doesn't see the phone (all drivers are installed). I can't get the phone to work so I had to buy a cheap tracfone to use in the mean time. Any suggestions? (I wish I'd saved a copy of the stock rom after unlocking but I thought it would work so I didn't)
Click to expand...
Click to collapse
Try going back and flashing a 3.15 based ROM. What version of TWRP are you on?
Sent from my EVO using xda premium
Same here... very frustrating.
I've have flashed Viper ROM which installs "apparently fine" until its time to touch the screen. Mean bean fails right out the box and wont install. TWRP works perfect with the touch panel. Also flashed Miklatte and the phone booted to a non responsive touch panel.:silly: I don,t care about S- OFF right now. I need this phone working. Any help is appreciated. thanks.
Im on Hboot 2.09 / 3.15.651.6 / unlocked S-ON.
lg31376 said:
I've have flashed Viper ROM which installs "apparently fine" until its time to touch the screen. Mean bean fails right out the box and wont install. TWRP works perfect with the touch panel. Also flashed Miklatte and the phone booted to a non responsive touch panel.:silly: I don,t care about S- OFF right now. I need this phone working. Any help is appreciated. thanks.
Im on Hboot 2.09 / 3.15.651.6 / unlocked S-ON.
Click to expand...
Click to collapse
What baseband (radio) are you on? If you're on the baseband ending in 1210, you can only run ROM's based on software version 3.16 and you must use TWRP 2.4 or newer.
Here is some info that might be useful:
http://forum.xda-developers.com/showthread.php?t=2256478
Also keep in mind that being S-on you essentially have to flash MeanBean twice-once to install the ROM, then again to install the kernel.
Sent from my EVO using xda premium
Save yourself time and the headache, just get S-Off. It's too easy now.
http://moonshine.io/
Enjoy.
FinZ28 said:
What baseband (radio) are you on? If you're on the baseband ending in 1210, you can only run ROM's based on software version 3.16 and you must use TWRP 2.4 or newer.
Here is some info that might be useful:
http://forum.xda-developers.com/showthread.php?t=2256478
Also keep in mind that being S-on you essentially have to flash MeanBean twice-once to install the ROM, then again to install the kernel.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
My radio : 1. 12. 11. 1119
TWRP v2.5.0.0
HBOOT: 2.09
Open DSP- v31.1.0.45.0815
Sorry guys I should explain my case further. I bought this phone from ebay. It was stuck on a soft brick which Bigdady619 helped me get out of. (Thanks again Bro!). So this is my current problem. Phone is unlocked S-ON. It was already on current HBOOT 2.09 and v 3.15.651.6. Now I need S-OFF but tried to do dirtyracun (on UBUNTU live CD) several times and ended with a "failed connection test error " at step14. went to IRC channel and they said is USB related issue. I have USB 2 and Good USB cable. Dont have HTC original but I dont understand why it has to be that one. I'm an audio and electronics engineer and know how USB works. Anyways thats whats keeping me from the holy grail! On the other side I cant flash touchpanel firmware cause Im not S-OFF. I've spent ****less hours on this forums and havent found an answer to the touch screen problem, other than flashing the firmware, which some people with the same problem have done and still no fix. At the moment I have a what seems to be a perfectly working Viper 4G 3.1.5 installed. Its the only ROM that would install correctly anyways. Touch panel works only on TWRP. I will try dirtyracun one more time and lets see what happens. thanks for paying attention to this aggravating problem.
***Update*** I just finished doing dirtyracun process. Problem: Step 14. Enable USB Debugging on your device. Once I flash the RUU ( step 11) The phone reboots to ROM (Viper 4G) with USB Debugging disabled. Due to touch panel issue I cant enable it and finish up the process! Apparently after burning Google down theres no way to enable USB Debug through adb or fastboot. Im stuck!
Update
***Update*** I just finished doing dirtyracun process. Problem: Step 14. Enable USB Debugging on your device. Once I flash the RUU ( step 11) The phone reboots to ROM (Viper 4G) with USB Debugging disabled. Due to touch panel issue I cant enable it and finish up the process! Apparently after burning Google down theres no way to enable USB Debug through adb or fastboot. Im stuck!
Yessssss!!!!
FINALLY S-OFF ACHOEVED through Facepalm!!!! thanx XDA! Now to deal with this touchpanel issue.
---------- Post added at 10:02 PM ---------- Previous post was at 09:24 PM ----------
Wooohoooo!! flashed the touchpanel firmware and BAM!! Evo LTE on DECK!! Thanx XDA U guys Rock!
lg31376 said:
FINALLY S-OFF ACHOEVED through Facepalm!!!! thanx XDA! Now to deal with this touchpanel issue.
---------- Post added at 10:02 PM ---------- Previous post was at 09:24 PM ----------
Wooohoooo!! flashed the touchpanel firmware and BAM!! Evo LTE on DECK!! Thanx XDA U guys Rock!
Click to expand...
Click to collapse
Sweet good job :thumbup::beer:
Sent from my HTCONE using xda app-developers app
can i use the older tp firmware to run 3.16 based roms also? or just on 3.15, cm and aosp?
Had the same issues after s off had to downgrade firmware to 3.15 but everything is sweet now captain throwback has a img you can flash by putting on root of sd and starting bootloader
Sent from my EVO using xda app-developers app
generalmofo said:
can i use the older tp firmware to run 3.16 based roms also? or just on 3.15, cm and aosp?
Click to expand...
Click to collapse
Yes. Old tp works with new roms, but new tp doesn't work with old roms/recovery.
______________________________
HTC Evo 4G LTE
~Asking for the 'best rom' is just like asking who's the best Pokémon. When you get it, sometimes you realize that its not all that great in your opinion. Try to flash 'em all! ~
aarsyl said:
Yes. Old tp works with new roms, but new tp doesn't work with old roms/recovery.
______________________________
HTC Evo 4G LTE
~Asking for the 'best rom' is just like asking who's the best Pokémon. When you get it, sometimes you realize that its not all that great in your opinion. Try to flash 'em all! ~
Click to expand...
Click to collapse
Thank you.
Related
I've been (at least trying to) patiently wait for Deck to post full install instructions for CM10 but the CM10 op is still bare as bones. Has anyone else posted an install guide or instructions yet?
I'm currently rooted with RegawMod and running MeanRom 2.1 and it's really terribly laggy and frustrating, I can't wait any longer for CM10. Do I need S-off to install CM10 or do I just wipe, flash, and go?
Thanks for any help or links!
If you are on hboot 1.15 or higher you have to fast boot flash the kernel.
Other than that its just like a normal aosp install. Wipe flash rom flash gapps.
Its been my daily for 3 weeks.
Sent from my EVO using Tapatalk 2
You don't need s-off. You will however have to flash the boot IMG separately by using fastboot or the app flash image GUI and a full wipe is definitely required. There is a helpful thread in Q&A called "don't panic" that will answer all your questions
Good luck
Sent from my EVO using xda app-developers app
corcgaigh said:
You don't need s-off. You will however have to flash the boot IMG separately by using fastboot or the app flash image GUI and a full wipe is definitely required. There is a helpful thread in Q&A called "don't panic" that will answer all your questions
Good luck
Click to expand...
Click to collapse
Dont use flash image gui unless you know how to do it manually through fastboot. You are just asking for issues
Instructions:
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-a.html
Rxpert said:
If you are on hboot 1.15 or higher you have to fast boot flash the kernel.
Other than that its just like a normal aosp install. Wipe flash rom flash gapps.
Click to expand...
Click to collapse
I'm on hboot 1.12, so does that mean I can just flash normally?
edit - From what I can tell from reading, hboot 1.12 doesn't have the same restrictions that 1.15+ do, so I think I'm OK but I would like verification.
Thanks for the help everyone.
Yes hboot 1.12 allows for access to the boot partition
Also luuuuucckkyyyyyy...
EdhyMonker said:
I'm on hboot 1.12, so does that mean I can just flash normally?
edit - From what I can tell from reading, hboot 1.12 doesn't have the same restrictions that 1.15+ do, so I think I'm OK but I would like verification.
Thanks for the help everyone.
Click to expand...
Click to collapse
If you are on Hboot 1.12 I'd strongly suggest looking into getting S-OFF. Theres really no reason not to.
Up to you though, its not required
Bit off topic, anyone check to see if you can push a new splash, right now I'm too lazy to start my PC just to fastboot one measly splash
Rxpert said:
If you are on Hboot 1.12 I'd strongly suggest looking into getting S-OFF. Theres really no reason not to.
Up to you though, its not required
Click to expand...
Click to collapse
The S-OFF guide was way over my head so I just let it be. If there's not a real good reason for doing it, and I can still run CM10, then I'd rather not.
It allows you to directly flash new firmware like radios to fix any problems a device might be having. If you have Son and want the latest firmware you have to revert back to stock and accept ota, then unlock reflash recovery and reflash custom ROM or rooted stock, you could also just flash root installer if you want to just root stock
om4 said:
It allows you to directly flash new firmware like radios to fix any problems a device might be having. If you have Son and want the latest firmware you have to revert back to stock and accept ota, then unlock reflash recovery and reflash custom ROM or rooted stock, you could also just flash root installer if you want to just root stock
Click to expand...
Click to collapse
No, S-ON people with 1.12 H-boot can flash radios and firmware from recovery. They can do whatever they please in recovery just like S-OFF. S-OFF users can flash things from bootloader and even change the appearance of their h-boot to read S-ON and **locked** even though they are S-OFF
To the OP, this is the best rooting guide I've seen. It really explains everything step by step. http://androidforums.com/evo-4g-lte...panda-s-htc-dev-ltevo-root-dummies-guide.html Its recommended to have Linux at least bootable, because in the small chance the phone gets bricked... the unbricker program requires linux.
I ran it in windows before the unbricker was available, no issues here
You basically just hook the phone up to it and run the program like you do for most other root programs. All 1-click
Ah yeah forgot to mention that, most everyone is on 1.15 or 1.19 sorry
om4 said:
Ah yeah forgot to mention that, most everyone is on 1.15 or 1.19 sorry
Click to expand...
Click to collapse
Alright, I got S-Off using Lazy Panda and it went better than expected!
Do I need to flash updated firmware / radios separately from CM10, or does CM10 include latest firmware?
Sorry to ask dumb questions, but I do hope this thread will also be a good resource for others like me.
You don't have to flash any firmware updates. There are a few users with issues although they may be related to the ROM update and not necessarily the firmware included. I haven't really checked since I'm s on. If you want to update the radios there's an update zip here somewhere, be sure to read through everything carefully. Radios are more risky then every day flashing
Alright everyone now I need some help!
I flashed CM10 after s-off, was on stocked 1.13 rooted rom.
Now when CM10 boots up I am faced with a phone activation screen. It says something like "you will not be able to place calls or access the mobile network until the device is activated". I am unable to make calls or receive calls or access the internet. I have tried reflashing cm10 and the problem persists.
In the mean time, I will try flashing a nand backup and see where that gets me. I appreciate any and all help, and I have found no posts in the CM10 thread with a similar issue.
Update: I wiped and restored a back-up, MeanRom 2.1. Upon boot, hands-free activation ran and activated the phone and downloaded a PRL update. Everything is working fine now. Not sure if I should try CM10 again or what? Any advice?
EdhyMonker said:
Alright everyone now I need some help!
I flashed CM10 after s-off, was on stocked 1.13 rooted rom.
Now when CM10 boots up I am faced with a phone activation screen. It says something like "you will not be able to place calls or access the mobile network until the device is activated". I am unable to make calls or receive calls or access the internet. I have tried reflashing cm10 and the problem persists.
In the mean time, I will try flashing a nand backup and see where that gets me. I appreciate any and all help, and I have found no posts in the CM10 thread with a similar issue.
Update: I wiped and restored a back-up, MeanRom 2.1. Upon boot, hands-free activation ran and activated the phone and downloaded a PRL update. Everything is working fine now. Not sure if I should try CM10 again or what? Any advice?
Click to expand...
Click to collapse
ive only ever seen this issue with cyanogenmod and the old htc vogues, still great phones for what they were
EdhyMonker said:
Alright, I got S-Off using Lazy Panda and it went better than expected!
Do I need to flash updated firmware / radios separately from CM10, or does CM10 include latest firmware?
Sorry to ask dumb questions, but I do hope this thread will also be a good resource for others like me.
Click to expand...
Click to collapse
Yes, you should be flashing the upgraded firmware. You'll see the full firmware as the very first downloadable link. Flash that
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
Rename the file to "PJ75IMG.zip", place on root of SD card, and boot into HBOOT to flash. Check the md5 to make sure its right. With radios you want to make sure its the correct file.
Welcome to S-OFF my friend
Rxpert said:
Yes, you should be flashing the upgraded firmware. You'll see the full firmware as the very first downloadable link. Flash that
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
Rename the file to "PJ75IMG.zip", place on root of SD card, and boot into HBOOT to flash. Check the md5 to make sure its right. With radios you want to make sure its the correct file.
Welcome to S-OFF my friend
Click to expand...
Click to collapse
Thanks, but I tried this and it says "no image or wrong image" when trying to flash the PJ75IMG.zip file.
Did you type in PJ75IMG.zip or PJ75IMG and kept it a zip file...you should do the 2nd.
joebarkho said:
Did you type in PJ75IMG.zip or PJ75IMG and kept it a zip file...you should do the 2nd.
Click to expand...
Click to collapse
I thought that might've been the issue so I tried it both ways, didn't work either way. I'll take another shot at it tomorrow.
Just flashed my first ROM (newest CM 10.1 nightly) with TWRP and everything seemed to have gone well but when I hit "Reboot" the HTC logo flashed for a second and then the screen went black and it's not doing anything. Been like this for 10 minutes.
I already rebooted back into recovery and reset the phone and cleared the caches and flashed the ROM again. Same thing.
Anyone know what's going on?
rdtmk said:
Just flashed my first ROM (newest CM 10.1 nightly) with TWRP and everything seemed to have gone well but when I hit "Reboot" the HTC logo flashed for a second and then the screen went black and it's not doing anything. Been like this for 10 minutes.
I already rebooted back into recovery and reset the phone and cleared the caches and flashed the ROM again. Same thing.
Anyone know what's going on?
Click to expand...
Click to collapse
Are you S-OFF? If not, you need to flash the boot.img separately.
exSD said:
Are you S-OFF? If not, you need to flash the boot.img separately.
Click to expand...
Click to collapse
No i'm not. Are there instructions anywhere on how to do that? Thanks for the help :good:
rdtmk said:
No i'm not. Are there instructions anywhere on how to do that? Thanks for the help :good:
Click to expand...
Click to collapse
There are 2 S-off methods in the original development threads.
Sent from my EVO using Tapatalk 2
rdtmk said:
No i'm not. Are there instructions anywhere on how to do that? Thanks for the help :good:
Click to expand...
Click to collapse
Look in the thread. If the author has posted the boot.img you can do it fairly easily.
mulhiny said:
There are 2 S-off methods in the original development threads.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Figured it out. Flashed it manually with Fastboot method and it boots into CM10.1 now but my touchscreen appears to not be working
You most likely need newest firmware if I'm not mistaken. You really need to s-off your phone. Then you won't have all the difficulty your having. Otherwise, you need newest firm ware...
Sent from my EVO using Tapatalk 2
rdtmk said:
Figured it out. Flashed it manually with Fastboot method and it boots into CM10.1 now but my touchscreen appears to not be working
Click to expand...
Click to collapse
This is because you have the newest touch panel firmware. It only works with roms based off of 3.16...currently no aosp Rom will work for you unless you s-off and downgrade to the 3.15 panel firmware. This is my understanding anyway. Flash a 3.16 sense Rom (viper, meanbean, etc) and you'll be back in business.
Sent from my EVO using Tapatalk 2
mulhiny said:
This is because you have the newest touch panel firmware. It only works with roms based off of 3.16...currently no aosp Rom will work for you unless you s-off and downgrade to the 3.15 panel firmware. This is my understanding anyway. Flash a 3.16 sense Rom (viper, meanbean, etc) and you'll be back in business.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the help everyone. So without touch I wasn't able to turn on USB debugging mode so that I could get superCID so that I could S-Off so I tried to recover with the backup I made in TWRP but it just boot loops.
How can I copy a ROM onto my phone without actually being able to boot into a ROM?
rdtmk said:
Thanks for the help everyone. So without touch I wasn't able to turn on USB debugging mode so that I could get superCID so that I could S-Off so I tried to recover with the backup I made in TWRP but it just boot loops.
How can I copy a ROM onto my phone without actually being able to boot into a ROM?
Click to expand...
Click to collapse
Flash the ROM through fastboot.
fastboot flash zip nameofrom.zip
exSD said:
Flash the ROM through fastboot.
fastboot flash zip nameofrom.zip
Click to expand...
Click to collapse
says:
"writing 'zip' ... FAILED (remote: not allowed)"
Try getting a copy of cwm (not the touch version) and flash it via the fast boot method. Use the volume rockers to move, camera to select, power to go back.
It'd be easier to just ruu back to stock and start at square 1. Doesn't take that long to root and s-off anymore. Dirty racun would probably still work too.
Sent from my EVO using xda premium
Yeah, if you wanna run ANYTHING other than a sense 3.16 ROM, you're gonna HAVE TO S-off so you can downgrade that damn touch panel that came with the 3.16 update (thanks HTC :banghead
I thought the latest twrp was compatible with the updated TP now, though. What TWRP version you using? If not, as stated above, finding non-touch CWM recovery sounds like only/best solution. That was a good idea. Last I heard (long ago), CWM for this device breaks your /misc partition. Viperboy used to have it posted in the old viper thread so you could repair /misc. Not sure if it's still there.
Good luck.
From my Evo LTE, yup.
scottspa74 said:
Yeah, if you wanna run ANYTHING other than a sense 3.16 ROM, you're gonna HAVE TO S-off so you can downgrade that damn touch panel that came with the 3.16 update (thanks HTC :banghead
I thought the latest twrp was compatible with the updated TP now, though. What TWRP version you using? If not, as stated above, finding non-touch CWM recovery sounds like only/best solution. That was a good idea. Last I heard (long ago), CWM for this device breaks your /misc partition. Viperboy used to have it posted in the old viper thread so you could repair /misc. Not sure if it's still there.
Good luck.
From my Evo LTE, yup.
Click to expand...
Click to collapse
Twrp 2.4.x.x is compatible with 3.16 +TP
SOLVED!! Thanks to everyone, especially bigdaddy and FinZ! I will post something about what I did and what I used to get S-Off since it is actually really easy once put into easy to understands terms
Hey everyone,
Everything was going really as I was rooting my Evo 4G LTE this afternoon, until I realized I forgot to S-off. TWRP was installed and Superuser was flashed - Anyways, I got antsy and wiped the phone and flashed CM 10.1 and realized I forgot S-off - so of course, the phone wouldn't boot past the HTC screen.
I've been trying to flash stock roms to get into the superuser app, but none of them will load. They start to flash in TWRP, then the phone reboots to the HTC splash screen.
I am now unlocked, but still S-on. I can't flash any roms right now and was hoping someone might be able to help me out. I even tried the process all over again, but I get the same problem. So as of now, I can't get an OS on the phone.
Any ideas? Thanks.
Edit: I was running the latest OTA with HBOOT 2.09.
venkman21 said:
Hey everyone,
Everything was going really as I was rooting my Evo 4G LTE this afternoon, until I realized I forgot to S-off. TWRP was installed and Superuser was flashed - Anyways, I got antsy and wiped the phone and flashed CM 10.1 and realized I forgot S-off - so of course, the phone wouldn't boot past the HTC screen.
I've been trying to flash stock roms to get into the superuser app, but none of them will load. They start to flash in TWRP, then the phone reboots to the HTC splash screen.
I am now unlocked, but still S-on. I can't flash any roms right now and was hoping someone might be able to help me out. I even tried the process all over again, but I get the same problem. So as of now, I can't get an OS on the phone.
Any ideas? Thanks.
Edit: I was running the latest OTA with HBOOT 2.09.
Click to expand...
Click to collapse
Flash meanbean or viper rom, both have s-on kernel installer and you should be able to get s-off using dirty racun or moonshine... Sharkie rom is a stock rom too with a s-on installer... Good Luck!
Sent from my EVO using xda app-developers app
venkman21 said:
Hey everyone,
Everything was going really as I was rooting my Evo 4G LTE this afternoon, until I realized I forgot to S-off. TWRP was installed and Superuser was flashed - Anyways, I got antsy and wiped the phone and flashed CM 10.1 and realized I forgot S-off - so of course, the phone wouldn't boot past the HTC screen.
I've been trying to flash stock roms to get into the superuser app, but none of them will load. They start to flash in TWRP, then the phone reboots to the HTC splash screen.
I am now unlocked, but still S-on. I can't flash any roms right now and was hoping someone might be able to help me out. I even tried the process all over again, but I get the same problem. So as of now, I can't get an OS on the phone.
Any ideas? Thanks.
Edit: I was running the latest OTA with HBOOT 2.09.
Click to expand...
Click to collapse
Question... How did you install your recovery? Goo manager, pj75img.zip, or fastboot? I have had this same problem and the only solution was to fastboot flash a recovery... Dunno it was very weird and has only happened on my lte but it's been months.
Flowed from my Jewel using Tapatalk 2
gunfromsako said:
Question... How did you install your recovery? Goo manager, pj75img.zip, or fastboot? I have had this same problem and the only solution was to fastboot flash a recovery... Dunno it was very weird and has only happened on my lte but it's been months.
Flowed from my Jewel using Tapatalk 2
Click to expand...
Click to collapse
I installed it using fastboot. I'm going to try one of the ROMs suggested above and see if that works. I'll let you all know as soon as I do it.
I keep reading that Moonshine won't work with HBOOT 2.09 - and I haven't had any luck getting it to work; it still gives me connection issues saying it can't connect to the phone. It's weird... I can use the adb devices command in recovery mode and my device ID shows up, but when I go into fastboot USB and do adb devices, I can't get it to show up. If I could somehow get that to show up during fastboot, it would mean smooth sailing.
Update: I successfully installed Meanbean. However, I still cannot gain S-Off. Moonshine won't work and I do not know enough to use DirtyRacun since it must be used with Ubuntu. I'll post my Moonshine issues in that thread
Thanks for the help with this! It looks like it just needed a S-On ROM to be installed which I though I was doing before!
I've tried every single HTC driver available and I can't get anything to recognize the Evo when it's in fastboot. It only recognizes the device when the ROM is loaded and USB storage is enabled. Unfortunately, I can't get s-off (as far as I know) without being in the bootloader and using fastboot.
Anyone know how I can achieve this or how I can get everything to communicate with one another like they're supposed to?
Have you deleted all the HTC stuff on your PC rebooted it the plug you phone back in and it should load the drivers again
then boot into bootloader and it should load more drivers
also try updating your android-sdk
Make sure you have the most current HTC driver. At least one person that I know of had issues until he updated to the most recent driver, which can be found in the link below. Use the HTC driver from post #2.
http://forum.xda-developers.com/showthread.php?t=2179776
Also, like Bigdaddy said, make sure you have things like HTC Sync removed. Make sure you're using a USB 2.0 port, too. I don't know where you read Moonshine doesn't work with Hboot 2.09, because it does (specifically for the latest OTA).
Sent you a PM
Sent from my EVO using xda premium
Hello all, and thank you for taking your time to attempt to help me with my problem.
I could not find a solution even after hours of researching and trial and error, so please forgive me if this happens to be one of those problems that are seemingly impossible to solve, when the actual solution is really quite simple! I'm hoping it is at the very least...
A few days ago I received an HTC Evo 3d from a family member.
I'm certain that the phone was completely stock, never rooted, no custom ROMs ---- just an ordinary HTC 3vo.
So I decide that I'm going to go ahead and find the steps necessary in order to flash a custom ROM, and I believe I did with this:
http://forum.xda-developers.com/showthread.php?t=1889438
I followed the guide, and eventually got to "***Step3: Perform JuopunutBear (wire trick) to get S-OFF status" where I had a little difficulty with the timing of the taps on the SD card. At one point I removed the battery from my phone because I thought it was stuck on the screen with the green arrow pointing downward, and after trying to reboot I found that the same JuopunutBear screen with the green arrow was still there.
I removed the battery once more, but this time when booting I held the volume down button to initiate bootloader. That went successfully, and so after trying the methods I found at http://unlimited.io/jbtroubleshooting.htm to remove this screen, I figured that I might try and flash a ROM from recovery and maybe that would fix it?xD My logic proved only half correct because even after formatting data/cache/dalvik, and then flashing a few different ROMs (not in the order of course) to see if any of them would allow the phone to boot up completely into OS, the phone is now stuck in a bootloop :'(
If I didn't provide enough information in the above description then I'd be glad to give any more details.
My bootloader reads like this:
- Juopunutbear -
SHOOTER XC SHIP S-OFF RL
HBOOT-1.57.5757
eMMC-boot
Apr 20 2012, 17:39:22
^ Never noticed that the date is inaccurate before typing all of this out! Not sure that has anything to do with my problem here, but still interesting..
Thank you again for taking your time to help me.
This phone has given me trouble since it was first given to me lol.
The first issue before rooting or anything was with the inability to use wifi!
I ended up having to buy service for the phone to even register my Gmail account..
You're in good shape
With s off you can recover easily.
The question is what do you want to run?
If you're going to stay ics sense, then you'll just need to format all partitions except sd and flash a Rom
If you want to run a jb Rom, you need to downgrade your hboot to the jbear 1.50
Sent from my PG86100 using xda app-developers app
---------- Post added at 08:42 AM ---------- Previous post was at 08:40 AM ----------
I think the date is the release of the bootloader or something...shouldn't be today's date
Sent from my PG86100 using xda app-developers app
Thank you for the reply
I'll try flashing different sense ROMs specifically,
and see if it will boot all the way through to the home screen.
Have you installed a recovery?
I suggest 4ext
Sent from my PG86100 using xda app-developers app
I have installed a recovery, and it just happens to be 4ext!
I've been installing my ROMs by toggling usb storage in recovery, placing the ROM on the root of my microSD, and after disconnecting from usb storage I proceed to flash the chosen ROM, provided I've already wiped everything.
My trouble usually comes afterward when the ROM has completed it's installation and I go to reboot. Every time I've tried so far I've encountered a bootloop :/ But we'll see this time!
Gotcha
You'll get it sorted
What Rom are you trying now?
Sometimes you need to flash the boot.IMG after the Rom, but that usually only happens if youre s on.
If it still bootloops I would try this next:
Boot to recovery
Wipe all partitions
Reboot recovery
Wipe all partitions again
Flash Rom
Reboot phone
If all else fails you can run the ruu (will return u to stock Rom and recovery) and you will keep s off but will need to install recovery again.
Sent from my PG86100 using xda app-developers app
I chose Team d3rp - Lights Out just to see if it would work, and to my surprise it did!!!
I wiped everything but my sd manually once,
and after flashing the ROM, the aroma installer gave the option to wipe again so I did.
After a suspenseful minute or two during the reboot, I finally got everything set up!
I can't thank you enough..!!
I'm not sure if I should make another thread or not, but the only problem I see now is with the wifi.
I have it connected to my network, and it's showing full signal,
but I can't access the internet and 3g doesn't even pick up when wifi is on.
If needed I'll make another thread, but I figured I would ask just in case!
I appreciate all the help so far.
Try a reboot or different kernel...don't know why it doesn't work
Sent from my PG86100 using xda app-developers app
Hello, a couple of days ago I received an HTC Evo 3D, but I don't like the stock HTC rom, so I decided to use NonSense (http://forum.xda-developers.com/showthread.php?t=1507616). I updated firmware, and installed CWM 6.0, wiped partitions and installed that ROM. But now i got a bootloop :/ .
Bootloader is unlocked..
egerth said:
Hello, a couple of days ago I received an HTC Evo 3D, but I don't like the stock HTC rom, so I decided to use NonSense (http://forum.xda-developers.com/showthread.php?t=1507616). I updated firmware, and installed CWM 6.0, wiped partitions and installed that ROM. But now i got a bootloop :/ .
Bootloader is unlocked..
Click to expand...
Click to collapse
Again, more info please. What h-boot? S-on or s-off?
Sent from my Nokia 3310 using Tapatalk
donkeykong1 said:
Again, more info please. What h-boot? S-on or s-off?
Sent from my Nokia 3310 using Tapatalk
Click to expand...
Click to collapse
S-off, I think it has to be s-on, hboot 1.53.0007, i'm currently trying to use RUU get back to stock, RUU says :
from image version 3.28.401.1 to 3.28.631.1
But it fails because of model id.
Bootloader is currently relocked.
egerth said:
S-off, I think it has to be s-on, hboot 1.53.0007, i'm currently trying to use RUU get back to stock, RUU says :
from image version 3.28.401.1 to 3.28.631.1
But it fails because of model id.
Bootloader is currently relocked.
Click to expand...
Click to collapse
You can only flash sense based ROMs with that h-boot. Since you're s-off just downgrade your h-boot to 1.49.0007 or 1.49.1107 and you can flash anything you want
Sent from my Nokia 3310 using Tapatalk
Oh crap, made a mistake, I have s-on.
Then you can only flash sense based ROMs. Try Cool ICS, it's great. Or do s-off ?
Sent from my Nokia 3310 using Tapatalk
donkeykong1 said:
Then you can only flash sense based ROMs. Try Cool ICS, it's great. Or do s-off ?
Sent from my Nokia 3310 using Tapatalk
Click to expand...
Click to collapse
I was about to download that, hopefully it'll work. :fingers-crossed:
You need 4ext recovery and smartflash enabled because Cool uses custom kernel
Sent from my Nokia 3310 using Tapatalk
donkeykong1 said:
You need 4ext recovery and smartflash enabled because Cool uses custom kernel
Sent from my Nokia 3310 using Tapatalk
Click to expand...
Click to collapse
I tried with CWM, and after a successful flash and boot, I flashed boot.img via fastboot, seems to be working, thank you!
You're welcome
Sent from my Nokia 3310 using Tapatalk
Ok, I give up. I've tried everything I can think of, but I can't get 4G to stick on, and trying to run the 3.06 RUU gives me error 170.
Here's what happened. Yesterday I flashed Kickdroid 2.0 with the CDMA patch from: http://forum.xda-developers.com/showthread.php?t=2634126
- Everything seemed to install fine, and initially 4G was up. But within about a minute 4G disconnected and I no longer had any mobile data.
- So then I did a full complete wipe via TWRP - doing the factory reset, then using the advanced wipe on everything except internal storage - then restored my backup of BadSeed's Tranquil rom. It came up fine initially but then within about a minute 4G disconnected and I was put back at 3G.
- Re-wiped everything same as before, then flashed the Tranquil Rom from scratch. - Same problem. 4G connects initially then drops to 3G.
- Updated TWRP to the beta .6 version as suggested by the Kickdroid dev and re-flashed and did all those same steps again and still having same problem
- At one point last night I left the phone alone and after a long time with the kickdroid Rom re-flashed it asked me which carrier I had. I chose Verizon and then 4G stuck on for a while. Then, it lost it's connection again to 4G. This Rom never gave me any 'Service'. The lockscreen always said 'no service'
- This morning, I flashed the latest Viper and it too initially gives me 4G then about a minute later that drops and I'm stuck on 3G.
- I thought maybe it was my SIM card, so I put it in my rezound and it works just fine in that phone.
- I've been trying to RUU using the 3.06.605.4 RUU from: http://forum.xda-developers.com/showthread.php?t=2612740 but I keep getting error 170 saying that the device wasn't found and to plug in my usb cable.
I suspect that there is something in the CDMA patch that has done this. I say that in hopes to help narrow the problem down not to blame anyone, as I do accept the responsibility to what I have flashed on my phone, so please don't take it that way. I don't know what could remain after wiping and re-flashing but it seems as thought something has.
Anyhoo, I'm getting a little desperate at this point and hoping someone can help me out. Much appreciated...
Try flashing the recovery flashable radio?
Something could have borked the radio partition.
Sent from my DNA using my mind.
Uzephi said:
Try flashing the recovery flashable radio?
Something could have borked the radio partition.
Sent from my DNA using my mind.
Click to expand...
Click to collapse
Lol, of course the one thing I forgot to mention that I did. I flashed the radio from .torrented's thread as well.
I think at this point I'd like to just RUU it anyway. Could it be that my bootloader is still unlocked and I have TWPR as my recovery?
Thanks a lot guys...
badogg said:
Ok, I give up. I've tried everything I can think of, but I can't get 4G to stick on, and trying to run the 3.06 RUU gives me error 170.
Here's what happened. Yesterday I flashed Kickdroid 2.0 with the CDMA patch from: http://forum.xda-developers.com/showthread.php?t=2634126
- Everything seemed to install fine, and initially 4G was up. But within about a minute 4G disconnected and I no longer had any mobile data.
- So then I did a full complete wipe via TWRP - doing the factory reset, then using the advanced wipe on everything except internal storage - then restored my backup of BadSeed's Tranquil rom. It came up fine initially but then within about a minute 4G disconnected and I was put back at 3G.
- Re-wiped everything same as before, then flashed the Tranquil Rom from scratch. - Same problem. 4G connects initially then drops to 3G.
- Updated TWRP to the beta .6 version as suggested by the Kickdroid dev and re-flashed and did all those same steps again and still having same problem
- At one point last night I left the phone alone and after a long time with the kickdroid Rom re-flashed it asked me which carrier I had. I chose Verizon and then 4G stuck on for a while. Then, it lost it's connection again to 4G. This Rom never gave me any 'Service'. The lockscreen always said 'no service'
- This morning, I flashed the latest Viper and it too initially gives me 4G then about a minute later that drops and I'm stuck on 3G.
- I thought maybe it was my SIM card, so I put it in my rezound and it works just fine in that phone.
- I've been trying to RUU using the 3.06.605.4 RUU from: http://forum.xda-developers.com/showthread.php?t=2612740 but I keep getting error 170 saying that the device wasn't found and to plug in my usb cable.
I suspect that there is something in the CDMA patch that has done this. I say that in hopes to help narrow the problem down not to blame anyone, as I do accept the responsibility to what I have flashed on my phone, so please don't take it that way. I don't know what could remain after wiping and re-flashing but it seems as thought something has.
Anyhoo, I'm getting a little desperate at this point and hoping someone can help me out. Much appreciated...
Click to expand...
Click to collapse
Did you update HTC driver? then trying to RUU from bootloader, Fastboot usb, with the latest Hboot updated* (1.54.0000)= 3.06.605.4 version.
---------- Post added at 01:34 PM ---------- Previous post was at 01:23 PM ----------
badogg said:
Lol, of course the one thing I forgot to mention that I did. I flashed the radio from .torrented's thread as well.
I think at this point I'd like to just RUU it anyway. Could it be that my bootloader is still unlocked and I have TWPR as my recovery?
Thanks a lot guys...
Click to expand...
Click to collapse
Bootloader unlocked matter to RUU , TWRP nope.
finanandroid said:
Did you update HTC driver? then trying to RUU from bootloader, Fastboot usb, with the latest Hboot updated* (1.54.0000)= 3.06.605.4 version.
---------- Post added at 01:34 PM ---------- Previous post was at 01:23 PM ----------
Bootloader unlocked matter to RUU , TWRP nope.
Click to expand...
Click to collapse
I would expect a problem later on if it were the bootloader being locked still, not int he beginning and then saying that the device isn't found. Or am I totally wrong and should just re-lock the bootloader and try again?
badogg said:
I would expect a problem later on if it were the bootloader being locked still, not int he beginning and then saying that the device isn't found. Or am I totally wrong and should just re-lock the bootloader and try again?
Click to expand...
Click to collapse
Well you mention error 170, usually its HTC Driver outdated, thats the reason that I suggest Driver update.
thought first have a working ADB/fastboot to see your phone. usb 2
you need to lock the Bootloader in order to run Ruu 3.06.exe (no problem because after RUU is done, Rumrunner unlock and S-Off Thanks to beaups
you need to update the Stock Hboot version to 3.06. thanks to Torrented
Here the link updated thanks to Phaded http://forum.xda-developers.com/showthread.php?t=2293919&highlight=flash+radio
finanandroid said:
Well you mention error 170, usually its HTC Driver outdated, thats the reason that I suggest Driver update.
thought first have a working ADB/fastboot to see your phone. usb 2
you need to lock the Bootloader in order to run Ruu 3.06.exe (no problem because after RUU is done, Rumrunner unlock and S-Off
you need to update the Stock Hboot version to 3.06. thanks to Torrented
Here the link updated thanks to Phaded http://forum.xda-developers.com/showthread.php?t=2293919&highlight=flash+radio
Click to expand...
Click to collapse
I tried the updated drivers earlier and still get the error 170. I'm wondering if there is just something wonky with my work computer that isn't working right. I'll try locking bootloader and running RUU from a laptop and see what happens. Thanks for the assist! :highfive:
badogg said:
I tried the updated drivers earlier and still get the error 170. I'm wondering if there is just something wonky with my work computer that isn't working right. I'll try locking bootloader and running RUU from a laptop and see what happens. Thanks for the assist! :highfive:
Click to expand...
Click to collapse
a pleasure
Any other android devices hooked up to that PC? I had 170 error when having both Rezound and DNA plugged in. The program may be trying to look at the other device port instead of the DNA port.
Try with locked boot loader and stock recovery. After I got rid of error 170 I got an error in the 150's (not the one mentioned in the ruu thread). It was because of custom splash image and custom recovery.
Sent from my DNA using my mind.
Uzephi said:
Any other android devices hooked up to that PC? I had 170 error when having both Rezound and DNA plugged in. The program may be trying to look at the other device port instead of the DNA port.
Try with locked boot loader and stock recovery. After I got rid of error 170 I got an error in the 150's (not the one mentioned in the ruu thread). It was because of custom splash image and custom recovery.
Sent from my DNA using my mind.
Click to expand...
Click to collapse
Interesting, I don't have anything connected, but I'm sure I have drivers loaded for my nexus 7
Which drivers for HTC are you using? The ones from HTC sync or the ones from pdanet? I found the pdanet ones work better for everything but HTC sync (which, who honestly uses? Lol)
Sent from my DNA using my mind.
Well, I let htcsync update the usb drivers and now the RUU is updating the image now.
Ok, this persisted through the RUU. Rom booted up, got 4G initially, then went to 3G.
badogg said:
Ok, this persisted through the RUU. Rom booted up, got 4G initially, then went to 3G.
Click to expand...
Click to collapse
after Ruu you most do a factory reset* from stock recovery
All that is usually needed is to restore the NV partitions on the device.
To do this, flash a stock rom and stock recovery.
Perform a factory reset in stock recovery.
Your radio should then function normally again.
No need to RUU or any of that, just a stock rooted rom and stock recovery are sufficient.
The key factor is the factory reset in stock recovery.
So if you did the RUU already, and did not do the factory reset in stock recovery, then that's why you still have an issue.
finanandroid said:
after Ruu you most do a factory reset* from stock recovery
Click to expand...
Click to collapse
omg, duh!! I knew that, just forgot to do it.
That seems to have fixed it. +150,000 internets to you!!
badogg said:
omg, duh!! I knew that, just forgot to do it.
That seems to have fixed it. +150,000 internets to you!!
Click to expand...
Click to collapse
glad :good: you got it !
@santod040 which stock rom do I need to flash and what is stock recovery? Do I have to do this with adb comands or use twarp like normal flash so I can get my radio working correctly again and 4g back? Any one that can point me to what I need to do here is greatly appreciated. Thank you!
Sent from my HTC6435LVW using Tapatalk
Sutko82 said:
@santod040 which stock rom do I need to flash and what is stock recovery? Do I have to do this with adb comands or use twarp like normal flash so I can get my radio working correctly again and 4g back? Any one that can point me to what I need to do here is greatly appreciated. Thank you!
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
My full odex stock Rom in the dev section is sufficient.
If there isn't a stock recovery posted anywhere I'll locate one for you.
Then you flash the Rom in your current recovery.
After you boot, reboot to hboot.
Then fastboot flash recovery nameoffile.img.
Then either factory reset from Recovery or from the roms settings option.
Sent from my HTC6500LVW using Tapatalk
Pls locate stock recovery as I am not sure which one to use. I am downloading your odexed stock rom as we speak. I appreciate this very much! @santod040
Sent from my HTC6435LVW using Tapatalk
---------- Post added at 11:48 PM ---------- Previous post was at 11:43 PM ----------
After boot type in command prompt reboot to hboot or can I just type adb devices and then flash recovery
Sent from my HTC6435LVW using Tapatalk