When i am in twrp the touch screen doesnt work. So i try to flash using the bootloader with pj75img and after it it loads then reboots the phone nothing is happening. can anyone help?
NOTE TO ALL USERS: WHEN POSTING QUESTIONS ABOUT WHY YOUR DEVICE IS ACTING UP DUE TO A CERTAIN ROM, RECOVERY, ETC... YOU WILL NEED TO POST INFORMATION ABOUT YOUR DEVICE. THERE'S NO WAY WE CAN JUST GIVE YOU AN ANSWER WITHOUT KNOWING WHAT YOU HAVE. EXAMPLE: HBOOT, BASEBAND, ROOT, S-ON/S-OFF, ROM, ETC...
Pr0Ducer said:
When i am in twrp the touch screen doesnt work. So i try to flash using the bootloader with pj75img and after it it loads then reboots the phone nothing is happening. can anyone help?
Click to expand...
Click to collapse
With the limited amount of information you provided I have to assume you are on the latest firmware with the latest touchpanel and are flashing a version of TWRP that doesn't support that particular touchpanel. You will need to flash a later version of TWRP (2.4.4.0+) in order to use the touchscreen with the latest touchpanel firmware. In most cases: when first flashing TWRP and booting into the recovery the phone will reboot the system and you will then need to get into the bootloader and maneuver to the recovery again.
I have twrp 2.2.0, and and a basband form when i first got the phone which was last September, and have not done an update since then. Being a newb and not paying attention i installed the newest hatk rom and after that it flashed that one rom but every zip after that after flashing didnt do anything and now my touchscreen does not work when i am in recovey. So all i can think of is to bootload flash back but nothing works. it will flash after the phone reboots nothing has changed. Where do i go from here?
If this helps at all.
Jewel pvt s-pff RL
CID-SPCS_001
HBOOT-1.12.1111
Radio-1.12.11.1210
openDSP-v31.1.0.45.0815
Try flashing TWRP 2.4. or newer and see if that fixes the problem.
Sent from my EVO using xda premium
Did you install the latest firmware and touch? Maybe that's the problem.
If you don't want to mess with that, you could install cwm. Works with the volume keys and power button. If the touchscreen works with the ROM but not recovery, try a newer recovery (latest twrp, maybe?).
Sent from my Evo 4G LTE using xda premium
When I go to flash with the bootlader. It will load but no changes after I reboot.
Sent from my EVO using xda app-developers app
And yes I have tried to flash the new twrp. I'm just stuck with no touch screen in recovery. And buttons don't work either. Is there another way I can flash other than using the bootlader.?
Sent from my EVO using xda app-developers app
Pr0Ducer said:
And yes I have tried to flash the new twrp. I'm just stuck with no touch screen in recovery. And buttons don't work either. Is there another way I can flash other than using the bootlader.?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Need to use fastboot, images, or FlashGUI. Try TWRP 2.3. If you have no touch input with any recovery or ROM then you're going to need a new phone.
Sent from my EVO using xda app-developers app
Dont you need TWRP 2.4+ if you have the 3.16 ouch panel?
Sent from my EVO using xda premium
scottspa74 said:
Dont you need TWRP 2.4+ if you have the 3.16 ouch panel?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
2.3.3.0+ I thought. Otherwise 2.4+. Can't remember for sure but I used 2.4.4.0 when I got my replacement with all of the updates. I'm thinking I'm mixing those version numbers up a bit. Lol.
Sent from my EVO using xda app-developers app
Haha I see I typo'd and wrote ouch panel. Lol. Ouch panel is more appropriate dealing with 3.16
Sent from my EVO using xda premium
Related
I just got a used, white HTC EVO 3D off of eBay, and it already been rooted and flashed with a custom ROM (no s-off though, as its hboot 1.5).
I flashed clockworkmod using the fastboot method, but it never goes into recovery. The Rom boots fine, its just when it goes into recovery, I get the white HTC screen, and then it reboots and goes into android. I've turned off fast boot in the settings, so I'm not sure what the issue is.
Sent from my PG86100 using xda app-developers app
thomasca said:
I just got a used, white HTC EVO 3D off of eBay, and it already been rooted and flashed with a custom ROM (no s-off though, as its hboot 1.5).
I flashed clockworkmod using the fastboot method, but it never goes into recovery. The Rom boots fine, its just when it goes into recovery, I get the white HTC screen, and then it reboots and goes into android. I've turned off fast boot in the settings, so I'm not sure what the issue is.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
If you pull the battery and put it back, then go to hboot and select recovery and it doesn't go to recovery, then your recovery is corrupt or something, no biggie. Get flash image GUI and flash a recovery with it, or flash cwm with rom manager.
I used to have issues with certain recoveries when I had s-on, I think cwm version 4.0.1.4 was the one that worked for me.
Have you tried 4ext recovery? Link is in my Sig.
Well I have ROM manager and tried cwm 4.1.0.15 and got the same results.
Would 4ext work with any of the ics roms for the HTC EVO 3d?
Sent from my PG86100 using xda app-developers app
Yes it will. I use 4ext and am running ZREDX ICS.
Alright, that worked. Thanks for the help!
Sent from my PG86100 using xda app-developers app
I got my Evo 3d off Craigslist this morning and i love it. Traded my Evo 4g plus cash for it and i couldnt be happier. I was very successful in rooting the 4g amd never had any problems that i can think of and im hoping the same goes for the 3d.
Anyways ive been reading and reading on how to root it, get s-off so i can install a recovery and them flash a rom and kernel. Ive managed to confuse myself because it seems that if you root it one way, you may not be able tp fash custom kernels and if you use another method to root it, your more than like to have all sorts of problems.
Basicall i need help and if someone could post a link to show me best method on how to root, s-off, install custom recovery, and install a rom on the 3d it would be greatly appreciated.
I have Sprint (cdma) Android 2.3.4. Software # 2.08.651.2 hboot 1.5, baseband 0.97.10.0808
Here you go: http://forum.xda-developers.com/showthread.php?t=1585846
Sent from my ICS 3VO with Tapatalk 2
I ended up goin a different route by using the HTC unlcock bootloader and that was suscessful. I still have s on and I think I'm gonna keep it that way for now but I need to install a custom recovery.
I've tried setting up sdk all morning and can't get the cmd to recognize adbas an interal or external command. Not sure what exactly it is that in doing wrong.
I wanting to know if there'sa way to install my first custom recovery thru the bootloader in my phone without using my computer so I can flash the su.zip and get this thing rooted. Thanks
Sent from my PG86100 using xda app-developers app
The twrp recovery has a method to flash that recovery without a computer by downloading it as a zip and naming it properly. See their site for detail.
I still recommend s-off since it is easier to flash Roms and the ics Roms tend to bootloop with s-on.
Sent from my ICS 3VO with Tapatalk 2
I dowloaded and renamed it to PC86100IMG.zip then went to bootloader, it read the zip but said "update fail, main version older!" Have any idea as to why its saying that?
Sent from my PG86100 using xda app-developers app
I was finally able to get adb recognized but when I type adb reboot bootloader it gets into the bootloader just fine but when i type fastboot flash recovery recovery.img it "fastboot is not recognized as an internal or external demand"
I'm using jtniggles unlock hboot 1.5, twrp recovery, root ,flash
Sent from my PG86100 using xda app-developers app
scottypeterson said:
I dowloaded and renamed it to PC86100IMG.zip then went to bootloader, it read the zip but said "update fail, main version older!" Have any idea as to why its saying that?
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
It looks like you renamed it to the wrong thing. If you downloaded TWRP 2.2.0 zip, it must be renamed PG86IMG.zip on the root of the sd card. Then when you update in bootloader, it should work.
coal686 said:
It looks like you renamed it to the wrong thing. If you downloaded TWRP 2.2.0 zip, it must be renamed PG86IMG.zip on the root of the sd card. Then when you update in bootloader, it should work.
Click to expand...
Click to collapse
Sorry thats what i renamed it too. Got my numbers mixed up lol. Tried it again but says the same thing
Sent from my PG86100 using xda app-developers app
scottypeterson said:
Sorry thats what i renamed it too. Got my numbers mixed up lol. Tried it again but says the same thing
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Hmmm... Does your phone boot? If so, you could download 4ext (see my signature) and install their app. Then it will push the custom recovery for you. I use 4ext myself anyway.
I tried using their app already and it won't let me since I don't have root
Sent from my PG86100 using xda app-developers app
Just wanted to give you a thanks again for all your help. I was finally able to figure out why adb wasn't working. Once thaat was fixed, I installed twrp recovery and flashed Su.then did the wire trick which me VERY nervous but it worked and got S-Off after a couple tries and I then installed 4ext recovery from which I understand is the best recovery available. Thanks again!
Sent from my PG86100 using xda app-developers app
scottypeterson said:
Just wanted to give you a thanks again for all your help. I was finally able to figure out why adb wasn't working. Once thaat was fixed, I installed twrp recovery and flashed Su.then did the wire trick which me VERY nervous but it worked and got S-Off after a couple tries and I then installed 4ext recovery from which I understand is the best recovery available. Thanks again!
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Your welcome. Glad you figured it out. I personally have never had an issue with the 4ext recovery.
OK so I used the bootloader to flash the 3 option in Haus's thread and every thing is working. But....
Now on the bootloader screen it says locked tampered then S-off.
I was told the locked was just wat it was saying and didn't matter.
So do I have a locked boot loader? And does that even matter for anything or was it just required to get root plus S-off?
Did I mess up getting the newest hboot from the firmware? I was told I needed it to run meanbean.
Sent from my EVO using xda app-developers app
I'm not sure what u flashed but it sounds like you flashed the whole thing which means you have stock recovery now. Either fastboot flash recovery image or download thru goo manager.
Once you have a custom recovery installed your all set. Don't worry about the locked on your bootloader
Sent from my EVO using xda premium
mainstang said:
OK so I used the bootloader to flash the 3 option in Haus's thread and every thing is working. But....
Now on the bootloader screen it says locked tampered then S-off.
I was told the locked was just wat it was saying and didn't matter.
So do I have a locked boot loader? And does that even matter for anything or was it just required to get root plus S-off?
Did I mess up getting the newest hboot from the firmware? I was told I needed it to run meanbean.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
You should have flashed the first file the one with no kernel,hboot, or stock recovery that would have updated everything you needed to be updated
So did I mess anything up? I was able to flash mean bean without any issues.
Sent from my EVO using xda app-developers app
mainstang said:
So did I mess anything up? I was able to flash mean bean without any issues.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
No you just did the same as taking the OTA as far as I can tell. As long as everything is working you should be fine
Hey all,
so I've come into a bit of a conundrum. I was playing with the MaximusHD Jellybean 4.3 ROM. It was alright, but not for me. So I decided to flash back to stock. After a bit of finagling, I got a Stock Rooted 4.1.2 ROM for my phone, and was able to flash it. But now, I can't RUU my phone back to complete stock. Relocking the bootloader produces a **Security warning**, which prevents booting. Now, with an unlocked bootloader the stock ROM boots fine -- but locked, it doesn't boot and goes directly to bootloader. Can someone please walk me through getting my phone back to normal? I've used the RUU before to return to complete stock once before, except I'm not sure what I've done wrong this time around. Any help is appreciated. Also, I have TWRP recovery (latest version), unfortunately without a Nandroid backup
My phone works fine right now -- albeit rooted. Thank you!
Try flashing a stock recovery before relocking.
Sent from my HTC One using xda app-developers app
Are you s off?
Sent from my HTC One using XDA Premium 4 mobile app
Exact same problem here
Hi,
I have the exact same problem here, i've had my HTC One with a 2-year plan @t-mobile but with the stock rom i haven't had any t-mobile bloatware/splash screen. Is that normal?
Also if i flash a stock t-mobile rom it hangs at the bootloader.
nanobutter said:
Are you s off?
Click to expand...
Click to collapse
I don't have S-OFF, but I can get it if necessary. Will that help me any?
Yes it will help. I am no dev. Once your s off you won't need to lock your device and can run ruu
Sent from my HTC One using XDA Premium 4 mobile app
lampel said:
Try flashing a stock recovery before relocking.
Click to expand...
Click to collapse
Will this allow booting to my rooted ROM / will it remove the **Security warning** that prevents booting?
crashfocus said:
Will this allow booting to my rooted ROM / will it remove the **Security warning** that prevents booting?
Click to expand...
Click to collapse
It should.
Sent from my HTC One using XDA Premium 4 mobile app
nanobutter said:
It should.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunately, flashing a stock recovery just prevented my device from booting normally. I had to reflash TWRP to get it to boot properly... unless I just didn't give the boot process enough time on the stock recovery.
You can put any recovery on your phone, lock it, and run fastboot rebootRUU from hboot to run the RUU.
Sent from my HTC One using XDA Premium 4 mobile app
ofdsmen from
zerolgk5 said:
You can put any recovery on your phone, lock it, and run fastboot rebootRUU from hboot to run the RUU.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wonderful! I'll try this after school today. Will report back...
word, let me know if you have any trouble. :good:
Hello, I just bought a used AT&T M8 and am trying to convert it back to sense. Im not familiar with messing with HTCs. I see in hboot that it is unlocked and s-off. It looks like they put pure google on it. Ive been looking and seeing different instructionson gett phone back to stock but they seem scattered. I saw and tried running official ruu for 1.58 found in another thread but only get to the point where it tries to reboot into boot loader and then it says it cant and to find a ruu compatible with my device. I cant tell what custom recovery it has. Everytime in hboot when i choose recovery it just hangs and says bad command. Can somebody tell me instructions on how to run this ruu?
Sent from my LG-D950 using XDA Premium 4 mobile app
Okay, making some progress. Pushed latest TWRP via fastboot. I'm assuming if I flash stock ROM and then push stock recovery via fastboot, then you I should be able to run ruu?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
ILuvRice said:
Okay, making some progress. Pushed latest TWRP via fastboot. I'm assuming if I flash stock ROM and then push stock recovery via fastboot, then you I should be able to run ruu?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
In your boot loader, what os does it say you have? We need to know if they did a true gpe conversion or just a rom. Does it have 3 android guys on skateboards or something else?
On the boot loader, it just says os-. I have attached a pic of my boot loader. Thanks for responding.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
ILuvRice said:
On the boot loader, it just says os-. I have attached a pic of my boot loader. Thanks for responding.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You are on an gpe conversion and cannot flash sense roms. You need to follow this guide to get back to sense
http://forum.xda-developers.com/showthread.php?t=2733523
Make sure you change your cid to 11111111 before doing anything, it says to do this in the guide, but just saying
Update if anyone is interested, was able to flash a stock rooted Rom after following steps from thread posted above.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
ILuvRice said:
Okay, making some progress. Pushed latest TWRP via fastboot. I'm assuming if I flash stock ROM and then push stock recovery via fastboot, then you I should be able to run ruu?
Click to expand...
Click to collapse
I know you solved your issue another way. But just so you know (and others, too) an RUU does not typically require stock recovery; while OTA does require stock recovery (probably the reason for the confusion).
Thanks. I ended up just flashing the RUU yesterday with stock rooted Rom and TWRP. This is why I love XDA. I was able to buy a M8 pretty cheap and thanks to people here, I was able to get it going.?
Sent from my HTC One_M8 using XDA Premium 4 mobile app