• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root *****10/4/13*****New OTA DO NOT DOWNLOAD IF YOU'RE ROOTED

Come to think of it, I may have downloaded the earlier version of the firmware. I knkw I had to wait a few days before I had time to sit down and flash. By then I had the newest TWRP. I bet my firmware has the touchscreen update in it.
 
Just sharing my experiences, since the process *should* be pretty simple and straight forward. Having read through *everything*, I was starting to get insecure...haha. Anyway, if any other noobs like myself get the nervies...it can be *this* simple:

Currently running PAC MAN ROM - I am current on firmware updates [I previously flashed the 3.15.651.6 OTA with radio/baseband 1.12.11.1119].

So, earlier today...

  • I ran a NANDROID backup, because it's easy - when I was a kid, we had to take our devices down to the river to back them up!
  • I downloaded the PJ75IMG...zip [latest firmware] from Cap'n's firmware thread and renamed it "PJ75IMG" on my external sd card.
  • I ran an MD5 check - all clear!
  • Rebooted into bootloader. The PJ75IMG file was detected and everything updated fine...and fast.
  • Rebooted.
  • After PAC MAN loaded back up, I deleted the PJ75IMG file from my card.
  • Unicorns flew from my device signaling I was upgraded.

The process takes a few minutes, and nothing was lost. Radio/baseband is now 1.12.11.1210. I'll report back if my device spontaneously bricks. :)

[I know he's around, so thanks again, Cap'n...where ever you are...]
 
NeoteriX said:
I'm reading some of the XDA posts on this -- do you know what version of TWRP you're running? There is some suggestion there that if you updated to 2.4.1 like me (latest version has the touchscreen fix for people that might have been impacted by the earlier version of the firmware update) that might be a cause of the problems.
Click to expand...

I'm running 2.4.1. Should i downgrade and worry about touchscreen issues, out wait fit TWRP to correct the issuer in a new version?





EarlyMon said:
Nandroids back up boot (the kernel), system and data, but not radio partitions.

I just updated to 2.4.1.0, it restores fine, I'll try an install later.
Click to expand...

Restoring has been fine for me, it's flashing that has been an issue.
 
CYNICALifornia said:
I'm running 2.4.1. Should i downgrade and worry about touchscreen issues, out wait fit TWRP to correct the issuer in a new version?


Restoring has been fine for me, it's flashing that has been an issue.
Click to expand...

I'm going to downgrade in a little while to see if it fixes my issues.

I haven't had any issues restoring or flashing, except for the weird install bug. Everything else worked just fine.
 
CYNICALifornia said:
I'm running 2.4.1. Should i downgrade and worry about touchscreen issues, out wait fit TWRP to correct the issuer in a new version?
Click to expand...

Can't hurt to downgrade TWRP and give it a try. If you get no touchscreen, you can come back to 2.4.1 and wait.

EarlyMon said:
If anyone wants just 2.4.0.0 (without the touchscreen fix for the latest OTA), here's the link from Team Win -

Techerrata Downloads - Downloading openrecovery-twrp-2.4.0.0-jewel.img

Flash with -

fastboot flash recovery openrecovery-twrp-2.4.0.0-jewel.img

Ask for Mac/Linux command version if needed. :)
Click to expand...

I had no trouble doing installs with 2.4, but that's my case, I never had the touchscreen bits in there.
 
I also upgraded my firmware after the Captain took the touchscreen bits out and have been using the 2.4.0 twrp to fix permissions, back up, restore and wipe and flash fresh roms w/o any issues.
 
I just got this phone (i know all late) :p, but once i got it it was already updated to the latest update 3.16.651.3 710RD, and i want to root it to get CM 10.2 :D does anyone know when that will be possible?
 
CYNICALifornia said:
I'm running 2.4.1. Should i downgrade and worry about touchscreen issues, out wait fit TWRP to correct the issuer in a new version?







Restoring has been fine for me, it's flashing that has been an issue.
Click to expand...
So this is how I understand the TWRP situation --

If you've flashed the 3.16 firmware, and your phone isn't bricked, you fall into one of two categories:
1) You're one of the early adopters and flashed the firmware before it was known that there are some touchscreen bits that are incompatible with other ROMs and TWRP.
2) You're one of the later adopters that flashed the firmware after (1) was discovered and Cap'n removed the offending bits.

If you fall into group (1) you probably need/needed the updated TWRP 4.2.1 in order to use it since prior versions (might) be incompatible. I'm not sure what to do here, you might be able to maybe flash the corrected version over it? I don't know, and I don't know what the consequences could be.

If you fall into group (2), that's me. I just did this all starting last night so everything had been fixed, but not really knowing any better I went ahead and updated to TWRP 4.2.1 just in case. Well it looks like 4.2.1 was affecting the install of the 3.16 Rooted OTA ROM. Because the version of the firmware I had was the more recent one without the touchscreen problem, I was able to downgrade to TWRP 3.2.1 without any loss of functionality and then flash the ROM.

I hope that helps--
 
fearstealth said:
I just got this phone (i know all late) :p, but once i got it it was already updated to the latest update 3.16.651.3 710RD, and i want to root it to get CM 10.2 :D does anyone know when that will be possible?
Click to expand...
i commented on your other post in the dummies guide.....lets keep the conversation there;)
fearstealth said:
thanks but my Evo isn't even rooted nor do i have recovery on it.:(
Click to expand...
and i think neo was commenting on cynical and not about your thread;)
 
Hopefully I can clarify the issues for everyone with the whole TWRP and touch panel driver situation.

There shouldn't be any "early adopters" of my firmware zip left that flashed the version with the touch panel image included. Only 4 people downloaded it before I pulled it (and those people downloaded it before I even announced it in the thread). So there shouldn't be anyone that's S-OFF that has the tp.img installed because of me.

That being said, when I found that TWRP was unresponsive due to the new tp.img, I was working with Dees_Troy on getting it working, which he was able to do, producing the 2.4.1.0 version of TWRP. The problem with the latest version of TWRP is that it will not flash any 3.16 based ROMs successfully, apparently due to the kernel modifications.

The real issue is for people that were UNLOCKED S-ON. In order to upgrade their firmware, they would have to flash stock recovery, relock and take the OTA. Then they'd have to unlock and flash the latest TWRP. Unfortunately, they would not be able to use any custom AOSP ROMs, since we don't have kernel source from HTC, and 3.15 base ROMs can only be run if the 3.16 boot.img/kernel is flashed.

After typing that all out, it probably doesn't make anything clearer after all :confused:.
 
CapThrowback said:
Hopefully I can clarify the issues for everyone with the whole TWRP and touch panel driver situation.

The real issue is for people that were UNLOCKED S-ON. In order to upgrade their firmware, they would have to flash stock recovery, relock and take the OTA. Then they'd have to unlock and flash the latest TWRP. Unfortunately, they would not be able to use any custom AOSP ROMs, since we don't have kernel source from HTC, and 3.15 base ROMs can only be run if the 3.16 boot.img/kernel is flashed.

After typing that all out, it probably doesn't make anything clearer after all :confused:.
Click to expand...

so this is a kernel issue? can those with unlocked and latest ota just fastboot the boot.img of aosp roms? can't they do the same thing with 3.15 or 3.16 roms? sorry you are right i'm just a little confused.:o:(
 
ocnbrze said:
so this is a kernel issue? can those with unlocked and latest ota just fastboot the boot.img of aosp roms? can't they do the same thing with 3.15 or 3.16 roms? sorry you are right i'm just a little confused.:o:(
Click to expand...
Basically it's the new 3.16 kernel that's breaking the latest TWRP, yes (or so it seems).

But 3.16-based ROMs won't even flash in the latest version, thus the need to downgrade. Fastbooting the kernel won't help if the ROM never installed. Those are the only ROMs affected, to my knowledge.
 
CapThrowback said:
Basically it's the new 3.16 kernel that's breaking the latest TWRP, yes (or so it seems).

But 3.16-based ROMs won't even flash in the latest version, thus the need to downgrade. Fastbooting the kernel won't help if the ROM never installed. Those are the only ROMs affected, to my knowledge.
Click to expand...

ok so aosp roms then? still feasible with the latest twrp with the latest ota?

so what you are saying is unlock the bootloader>install the latest twrp 2.4.1>flash a 3.15 rom>downgrade twrp>and you should be good to go after that? or is there no need to downgrade twrp?

you just have to be careful flashing 3.15 and 3.16 roms?
 
I seem to have been successful. I started at hboot 1.2.222, s-off, 2.13 software and firmware.

Here are the steps I followed:
- nandroid
- flash 3.15 firmware
- flash 3.16 firmware
- nandroid
- flash TWRP 2.1.3
- flash 3.16 ROM

Thanks for the help in determining the problem and finding a solution.
 
ocnbrze said:
ok so aosp roms then? still feasible with the latest twrp with the latest ota?

so what you are saying is unlock the bootloader>install the latest twrp 2.4.1>flash a 3.15 rom>downgrade twrp>and you should be good to go after that? or is there no need to downgrade twrp?

you just have to be careful flashing 3.15 and 3.16 roms?
Click to expand...
No, if you took the latest OTA, you CANNOT run any AOSP ROMs right now.

You'll be able to flash them (latest TWRP will allow that), but once booted, touch screen will be unresponsive.

I'm basically just saying the same thing we've been saying throughout the thread: do NOT take the OTA. S-OFF as soon as possible.

Otherwise you're stuck on JellyBean Sense until kernel source (for 3.16, likely) is released.
 
CapThrowback said:
No, if you took the latest OTA, you CANNOT run any AOSP ROMs right now.

You'll be able to flash them (latest TWRP will allow that), but once booted, touch screen will be unresponsive.

I'm basically just saying the same thing we've been saying throughout the thread: do NOT take the OTA. S-OFF as soon as possible.

Otherwise you're stuck on JellyBean Sense until kernel source (for 3.16, likely) is released.
Click to expand...

got it, thanx capt for clearing that up.

so basically 3.16=unlock only=can't flash aosp roms, only JB sense roms

thanx captn you are the man!!!!!:adore:
 
So I'm not going to take this update, but how in heck do I get rid of the notification of the update in the update bar?
 
Already did Settings --> System Updates --> HTC software update --> and unchecked. But that doesn't make the notification disappear. It's still there like a wart on Kate Beckinsale's face.
 
emerilnut said:
Already did Settings --> System Updates --> HTC software update --> and unchecked. But that doesn't make the notification disappear. It's still there like a wart on Kate Beckinsale's face.
Click to expand...

LMAO!!!!! that is funny:rofl:

what rom are you on? there should be a clear option in the notification bar to clear it.
 
emerilnut said:
Already did Settings --> System Updates --> HTC software update --> and unchecked. But that doesn't make the notification disappear. It's still there like a wart on Kate Beckinsale's face.
Click to expand...
After you disable the autoupdate, if you click on the notification itself, it will give you the option to download the update or snooze the notification--you know what to do.
 
Thanks, Neo.

I was afraid to tap it because I didn't want the download to auto start and take me into the update loop. Appreciate it guys.

ocnbrze, I'm on Viperboy's deodex ROM of the 3.15.651.17 710RD build that came out in December. It wasn't that clear to me. The notification said tap to update. Hence, my fear that it would auto-start the update without any chance for me to stop it.
 
You must log in or register to reply here.
Back
Top Bottom