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
Related
I'm a bit of a newb and seem to have f'd my phone up a bit. I was able to unlock via HTCdev prior to them taking it away and have been on ViperLTE 1.0 from the beginning. Before flashing ViperLTE 2.0 I wanted to flash the new RUU so I grabbed the RUU files from http://forum.xda-developers.com/showthread.php?t=1770978 and proceeded to flash Stock boot (kernel) and Stock Recovery (2.17.605.2). Needless to say I'm unable to get into recovery and noticed wifi doesn't work any more... What can I do to rectify this and get me back to the path of flashing ViperLTE 2.0
Thanks for the help!
gdemore said:
I'm a bit of a newb and seem to have f'd my phone up a bit. I was able to unlock via HTCdev prior to them taking it away and have been on ViperLTE 1.0 from the beginning. Before flashing ViperLTE 2.0 I wanted to flash the new RUU so I grabbed the RUU files from http://forum.xda-developers.com/showthread.php?t=1770978 and proceeded to flash Stock boot (kernel) and Stock Recovery (2.17.605.2). Needless to say I'm unable to get into recovery and noticed wifi doesn't work any more... What can I do to rectify this and get me back to the path of flashing ViperLTE 2.0
Thanks for the help!
Click to expand...
Click to collapse
You need a custom recovery like twrp or cwm I think. If you were on viper 1.0 all you needed was the hboot. Try pushing the recovery in fastboot. I think it'll fix everything.
Sent from my ADR6410LVW using xda app-developers app
spazmcghee said:
You need a custom recovery like twrp or cwm I think. If you were on viper 1.0 all you needed was the hboot. Try pushing the recovery in fastboot. I think it'll fix everything.
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
Thanks for the response. I had TWRP before the incident. I tried reflashing TWRP through HBOOT (1.02) and if failed with "Main Version is older! Update Fail!"
gdemore said:
Thanks for the response. I had TWRP before the incident. I tried reflashing TWRP through HBOOT (1.02) and if failed with "Main Version is older! Update Fail!"
Click to expand...
Click to collapse
I had that problem also. I followed the instructions under post #2 and it worked like a charm.
http://forum.xda-developers.com/showthread.php?p=33987199
canpitt27 said:
I had that problem also. I followed the instructions under post #2 and it worked like a charm.
http://forum.xda-developers.com/showthread.php?p=33987199
Click to expand...
Click to collapse
That did the trick! Thanks!
Can someone please direct me on the proper way to update RUU?
gdemore said:
That did the trick! Thanks!
Can someone please direct me on the proper way to update RUU?
Click to expand...
Click to collapse
If you are just looking to run a stock Rom I'd use
http://forum.xda-developers.com/showthread.php?p=32708425
sent from my ADR6410LVW using xda app-developers app
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.
I think I've done it this time. I was able to unlock the bootloader and also able to put TWRP recovery onto the phone. The mistake I made was trying to flash MIUI to the phone without backing anything up, so here I am and have been for the last 4 hours trying to figure out how to get my phone to boot into a ROM of any sort to try and S-OFF using the FacePalm method.
I honestly don't know what I should do at this point. I can still enter recovery and flash ROMs. Just, none of them actually load. The only time I can get any of them to load is when I flash it via recovery, then flash the boot.img via fastboot. However, when I do it this way, my touch screen within the ROM no longer works. So I can't press or do anything, to give my phone super user permissions. I'm really frustrated and just want to fix my phone. Can anyone offer some help or advice so I can try and fix this sometime between now and my death?
Thank you in advance.
cdboss said:
I think I've done it this time. I was able to unlock the bootloader and also able to put TWRP recovery onto the phone. The mistake I made was trying to flash MIUI to the phone without backing anything up, so here I am and have been for the last 4 hours trying to figure out how to get my phone to boot into a ROM of any sort to try and S-OFF using the FacePalm method.
I honestly don't know what I should do at this point. I can still enter recovery and flash ROMs. Just, none of them actually load. The only time I can get any of them to load is when I flash it via recovery, then flash the boot.img via fastboot. However, when I do it this way, my touch screen within the ROM no longer works. So I can't press or do anything, to give my phone super user permissions. I'm really frustrated and just want to fix my phone. Can anyone offer some help or advice so I can try and fix this sometime between now and my death?
Thank you in advance.
Click to expand...
Click to collapse
Relax
Check the link in my sig. Should answer most of your questions regarding your issues.
You are S-on, most likely on Hboot 1.15 or newer. You have to flash the kernel separately from the ROM for the ROM to boot when you are S-on. This is why fastboot flashing the kernel (boot.img) worked.
Regarding your other issue, it sounds like you have the updated touch panel driver that came with the most recent OTA. You need to use TWRP 2.4+ and you can only run ROM's that are software version 3.16. Once you get S-off you can downgrade the driver and run whatever ROM you want
Sent from my EVO using xda premium
certain putesbi
FinZ28 said:
Relax
Check the link in my sig. Should answer most of your questions regarding your issues.
You are S-on, most likely on Hboot 1.15 or newer. You have to flash the kernel separately from the ROM for the ROM to boot when you are S-on. This is why fastboot flashing the kernel (boot.img) worked.
Regarding your other issue, it sounds like you have the updated touch panel driver that came with the most recent OTA. You need to use TWRP 2.4+ and you can only run ROM's that are software version 3.16. Once you get S-off you can downgrade the driver and run whatever ROM you want
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Thank you for your reply and help.
I'm running HBOOT 2.09 to be exact. I'm also running TWRP 2.5, so I'm good there as well. Right now I can't boot into a ROM appropriately to achieve S-OFF. I tried creating a Ubuntu Live CD and the Kernel got messed up I guess when putting it on the disc. That was another frustration of mine, lol. I can't achieve the FacePalm method because I can't boot into a ROM to adb shell as super user, since it physically needs to be accepted on the phone.
I'm going to read what you suggested, though, perhaps that will give me the answer.
Edit: I'm going to go with your suggestion of flashing a ROM that's made for 3.16, and see if my touch panel works so I can S-OFF and flash whatever I want. I'll let you know how that goes.
cdboss said:
Thank you for your reply and help.
I'm running HBOOT 2.09 to be exact. I'm also running TWRP 2.5, so I'm good there as well. Right now I can't boot into a ROM appropriately to achieve S-OFF. I tried creating a Ubuntu Live CD and the Kernel got messed up I guess when putting it on the disc. That was another frustration of mine, lol. I can't achieve the FacePalm method because I can't boot into a ROM to adb shell as super user, since it physically needs to be accepted on the phone.
I'm going to read what you suggested, though, perhaps that will give me the answer.
Click to expand...
Click to collapse
What ROM are you trying to run? If it isn't based on software version 3.16 it WON'T WORK.
Sent from my EVO using xda premium
FinZ28 said:
What ROM are you trying to run? If it isn't based on software version 3.16 it WON'T WORK.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Just edited my post. I'm an idiot and didn't completely read your post. My apologies. I'm in the process of getting Viper4G at the moment, to try and achieve S-OFF.
cdboss said:
Just edited my post. I'm an idiot and didn't completely read your post. My apologies. I'm in the process of getting Viper4G at the moment, to try and achieve S-OFF.
Click to expand...
Click to collapse
I was able to get into Viper, tried doing the FacePalm S-OFF and it wasn't successful, for whatever reason. However, at least I'm better off than I was before. Any suggestions from here? I really want to get MIUI on this and not really feeling up to installing Ubuntu tonight.
If not, I really want to thank you. At least I'm able to use my phone again, lol.
cdboss said:
I was able to get into Viper, tried doing the FacePalm S-OFF and it wasn't successful, for whatever reason. However, at least I'm better off than I was before. Any suggestions from here? I really want to get MIUI on this and not really feeling up to installing Ubuntu tonight.
If not, I really want to thank you. At least I'm able to use my phone again, lol.
Click to expand...
Click to collapse
You're going to have to go the Dirty Racun route, unfortunately
Sent from my EVO using xda premium
FinZ28 said:
You're going to have to go the Dirty Racun route, unfortunately
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Guess I'll have to try and make another Live CD. I have no interest in dual booting a copy of Ubuntu at the moment, lol.
Thanks for the help.
FinZ28 said:
Relax
Check the link in my sig. Should answer most of your questions regarding your issues.
You are S-on, most likely on Hboot 1.15 or newer. You have to flash the kernel separately from the ROM for the ROM to boot when you are S-on. This is why fastboot flashing the kernel (boot.img) worked.
Regarding your other issue, it sounds like you have the updated touch panel driver that came with the most recent OTA. You need to use TWRP 2.4+ and you can only run ROM's that are software version 3.16. Once you get S-off you can downgrade the driver and run whatever ROM you want
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I now was able to get S-OFF. What exactly do I do to downgrade those drivers and flash a ROM that I want?
cdboss said:
I now was able to get S-OFF. What exactly do I do to downgrade those drivers and flash a ROM that I want?
Click to expand...
Click to collapse
If you want to downgrade your touch panel, check out this thread:
http://forum.xda-developers.com/showthread.php?t=1704612
The above thread links to here:
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
The touch panel you want to downgrade to is located under the 3.15 firmware, so just follow the directions posted in order to downgrade.
Sent from my EVO using xda premium
FinZ28 said:
If you want to downgrade your touch panel, check out this thread:
http://forum.xda-developers.com/showthread.php?t=1704612
The above thread links to here:
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
The touch panel you want to downgrade to is located under the 3.15 firmware, so just follow the directions posted in order to downgrade.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Awesome, thank you. I was able to get the ROM I wanted on here and looks like everything is good to go. Appreciate the help, FinZ28.
cdboss said:
Awesome, thank you. I was able to get the ROM I wanted on here and looks like everything is good to go. Appreciate the help, FinZ28.
Click to expand...
Click to collapse
You're welcome
Sent from my EVO using xda premium
Hey folks, this is urgend!
Why? Well, I wanted to do my girlfriend a favour and root her device and did so successfully, but it seems I cannot boot into any real ROM. The only ROM that successfully booted was the unofficial port of CM9. I uninstalled it because I would like to flash a daily driver for her. And that was when I tried fulmix.ROM as well as mySENSEdx+ v3. Here is my setup:
* TWRP 2.5 (official release)
* Formatted with SuperWipe JB
* Unlocked bootloader
Issues; When having flashed the ROM and installed boot.img through fastboot, all I get is a blackish screen, the device reboots every 5 minutes. Strange: I seem to not be able to perform a factory reset through TWRP. It always tells me that either cache or another smaller partition is inaccessible. Did I miss something while rooting? Any recommendations as how to solve this freaking issue will be REWARDED!
You are using the wrong recovery for your hboot. Your hboot version seems to be 1.25, but you are using a recovery made for hboot 1.24 and below. So go in Android Development Section and download TWRP for JB, flash that via fastboot and ROM installing as well as factory reset should work again.
1. Your main problem is the recovery. Don't use the official release but use the one for JB hboot from this thread : http://forum.xda-developers.com/showpost.php?p=36714573&postcount=2
2. In order to make sure that recovery is correct for your device, make sure you do have a 1.25 hboot (boot to bootloader and recheck that)
ckpv5 said:
1. Your main problem is the recovery. Don't use the official release but use the one for JB hboot from this thread : http://forum.xda-developers.com/showpost.php?p=36714573&postcount=2
2. In order to make sure that recovery is correct for your device, make sure you do have a 1.25 hboot (boot to bootloader and recheck that)
Click to expand...
Click to collapse
Thank you so much! To anwer your questions:
1. Will flash it ASAP after work. Is SuperWipe JB correct if want to flash your ROM?
2. It definately is. Would you Please tell me why the official TWRP will not work? Just curious..
SecUpwN said:
Thank you so much! To anwer your questions:
1. Will flash it ASAP after work. Is SuperWipe JB correct if want to flash your ROM?
2. It definately is. Would you Please tell me why the official TWRP will not work? Just curious..
Click to expand...
Click to collapse
1. Superwipe is not necessary. Just select wipe and do swipe to factory reset in TWRP is enough.
2. The official one is based on old files before JB is released to DX (e.g official TWRP for One X for the latest JB 4.2.2 hboot 1.73, touch is not working because it is based on old files)
ckpv5 said:
1. Superwipe is not necessary. Just select wipe and do swipe to factory reset in TWRP is enough.
2. The official one is based on old files before JB is released to DX (e.g official TWRP for One X for the latest JB 4.2.2 hboot 1.73, touch is not working because it is based on old files)
Click to expand...
Click to collapse
Everything is working good now. Any chance of an updated TWRP or 4EXT?
SecUpwN said:
Everything is working good now. Any chance of an updated TWRP or 4EXT?
Click to expand...
Click to collapse
Latest we have is TWRP 2.6.3.0, and it will probably be the latest for a while
GtrCraft said:
Latest we have is TWRP 2.6.3.0, and it will probably be the latest for a while
Click to expand...
Click to collapse
Does it work with Desire X without any issues?
SecUpwN said:
Does it work with Desire X without any issues?
Click to expand...
Click to collapse
No problems at all
GtrCraft said:
No problems at all
Click to expand...
Click to collapse
Can you help me here, please?
SecUpwN said:
Can you help me here, please?
Click to expand...
Click to collapse
Why don't you just flash a recovery and install rom from there.
Because flashing a recovery results in a "signature error" - means no recovery is flashable. This phone is not even able to get S-OFF yet, guess this is since the ROM itself is "corrupt" due to the HBOOT downgrade. Or am I getting this wrong?
Maybe... If I recall it correctly, the revolutionary scripts first interaction with the phone requires adb which isn't possible through bootloader. Do you have the stock recovery installed and can you boot into it? If yes, maybe adb can access your phone from there. If this is possible, try to run revolutionary from within the recovery...
dansou901 said:
Maybe... If I recall it correctly, the revolutionary scripts first interaction with the phone requires adb which isn't possible through bootloader. Do you have the stock recovery installed and can you boot into it? If yes, maybe adb can access your phone from there. If this is possible, try to run revolutionary from within the recovery...
Click to expand...
Click to collapse
That's the point: This phone doesn't have a recovery and flashing one is not possible. That's why flashing a complete RUU is trivial here. Are you able to find the adequate 1.22 RUU as a ZIP zo be flashed through fastboot?
Do you have the download link for the appropriate RUU? I can then extract it for you and load it up again, but I don't know which file you need exactly, as there are many RUUs on AndroidRuu...
dansou901 said:
Do you have the download link for the appropriate RUU? I can then extract it for you and load it up again, but I don't know which file you need exactly, as there are many RUUs on AndroidRuu...
Click to expand...
Click to collapse
Thank you so much! You'll find it here.
SecUpwN said:
Can you help me here, please?
Click to expand...
Click to collapse
I've got you covered friend
Sent from my C525c using Xparent Skyblue Tapatalk 2
I need help, not sure which I have done wrong. Last night I rooted and put TWRP on my phone. Tried to flash a rom and it just errored out. Tried multiple roms. So I got it s-off. Same issue.
I have tried last 2 versions of TWRP. Then I put latest Philz on and still can't install. I ended up wiping everything to test but now i'm stuck with a phone and no OS. I've been able to use the adb sideload method but can't get them to install.
Tried 3 roms. Phone was latest OTA before I tried anything. I saw something about it having a separate partition but the latest Philz was supposed to account for that. HBoot is 2.09
Is there a certain version of recover I am supposed to be on? Or any other suggestions? Thank you
jasin said:
I need help, not sure which I have done wrong. Last night I rooted and put TWRP on my phone. Tried to flash a rom and it just errored out. Tried multiple roms. So I got it s-off. Same issue.
I have tried last 2 versions of TWRP. Then I put latest Philz on and still can't install. I ended up wiping everything to test but now i'm stuck with a phone and no OS. I've been able to use the adb sideload method but can't get them to install.
Tried 3 roms. Phone was latest OTA before I tried anything. I saw something about it having a separate partition but the latest Philz was supposed to account for that. HBoot is 2.09
Is there a certain version of recover I am supposed to be on? Or any other suggestions? Thank you
Click to expand...
Click to collapse
First, you should be a bit more specific about which Roms you're trying to flash and which version of TWRP you are trying. If your hboot is 2.09, you can't flash any Roms built for the new partition. But without more specific information, I doubt anyone can offer much help.
Evolution_Freak said:
First, you should be a bit more specific about which Roms you're trying to flash and which version of TWRP you are trying. If your hboot is 2.09, you can't flash any Roms built for the new partition. But without more specific information, I doubt anyone can offer much help.
Click to expand...
Click to collapse
You most likely answered my issue. I thought I was on latest but I did see there is an hboot 2.10. So I am downloading the latest RUU to update me. It was the latest PAC. I thought since the phone said no updates available i was good to go.
jasin said:
You most likely answered my issue. I thought I was on latest but I did see there is an hboot 2.10. So I am downloading the latest RUU to update me. It was the latest PAC. I thought since the phone said no updates available i was good to go.
Click to expand...
Click to collapse
Good luck. To run the RUU, your bootloader must be relocked. You will remain S-off. Just unlock your bootloader afterwards at htcdev.com and install the TWRP built for the new partition. [emoji3]
Sent from my LGLS990 using Tapatalk
jasin said:
You most likely answered my issue. I thought I was on latest but I did see there is an hboot 2.10. So I am downloading the latest RUU to update me. It was the latest PAC. I thought since the phone said no updates available i was good to go.
Click to expand...
Click to collapse
The latest update wasn't released as a over-the-air update, hence the lack of a notification. Make sure you back up your internal storage, as the RUU will wipe it clean. Make sure you use Captain Throwbacks's TWRP 2.7.1.0b. Other versions of TWRP will not work properly with the new partition layout. Might want to look over the first few posts in the thread below for more info.
http://forum.xda-developers.com/showthread.php?t=2639180
Evolution_Freak said:
Good luck. To run the RUU, your bootloader must be relocked. You will remain S-off. Just unlock your bootloader afterwards at htcdev.com and install the TWRP built for the new partition. [emoji3]
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
No need to relock if S-off. Only applicable for devices that are S-on.
Magnum_Enforcer said:
No need to relock if S-off. Only applicable for devices that are S-on.
Click to expand...
Click to collapse
Sorry, its been a while. [emoji45]
Sent from my LGLS990 using Tapatalk
Evolution_Freak said:
Sorry, its been a while. [emoji45]
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
No it hasn't You just forgot everything when you bought your G3.
Thanks guy. I am up and running with latest cm11. I could not get adb side load to work with that twrp. Finally found an old SD card. Could have been the Roms I was trying but it was latest PAC nightly. Anyways it's perfect now.
Sent from my Nexus 7 using Tapatalk
jasin said:
Thanks guy. I am up and running with latest cm11. I could not get adb side load to work with that twrp. Finally found an old SD card. Could have been the Roms I was trying but it was latest PAC nightly. Anyways it's perfect now.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Glad to hear you're up and running.
Can anybody help me?I installed InsertCoin Sense 6 Rom(i have TWRP v2.7.1.0b and unlock throught HTCdev.com)and i cant get throught boot image(which says HTC One and beatsaudio).That can I do?
If you're S-on you may need to fastboot flash the kernel. Hit the top link in my sig & scroll down to the section about S-on kernel flashing.