ok so last week i was on here saying that i was having problems flashing roms to my phone. found out that because im s-on (also my hboot is 2.09) most roms i have to flash the kernal. so i was told to get the app flash image gui. i got it, flashed the kernal, it worked, but...... after the rom loaded my touch didnt work. i couldnt unlock the phone at all. so i went back to the previous rom. i tried another rom using the flash image gui and it did the same thing. it was as if the touch imput was gone. any reason why this happened? something i did wrong? thanks
What ROM did you flash and what version of TWRP are you on? If you took the latest OTA to software version 3.16 then you also got an update to the touch panel. Unless you get S-off and downgrade the touch panel, you have to use 3.16 ROM's and TWRP 2.4+.
Sent from my EVO using xda premium
FinZ28 said:
What ROM did you flash and what version of TWRP are you on? If you took the latest OTA to software version 3.16 then you also got an update to the touch panel. Unless you get S-off and downgrade the touch panel, you have to use 3.16 ROM's and TWRP 2.4+.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
the rom is jewel_PAC_JB_4.2.2-v22.0.1_20130401-180210.zip im using the TWRP 2.4 but flashing to 2.5 now
Like fin said, if you had the 3.16 ota on your device, the new touch panel drivers won't allow you to use PAC, you can't use anything but 3.16 based sense ROMs. You really will need to get s-off to enjoy your device. Good luck.
Sent from my EVO using xda premium
Related
Okay, So I've got s-off, unlocked, rooted, all of that stuff going on right now. I've been reading through and I'm so confused on how to upgrade from stock GB to ICS. I see so many methods for different roms, Can someone point me in the direction in I need to go? I'm currently running software number 2.01.605.11 w/ PRI 1.13_002, 1.88_002
Depends what you want to do....
If you dont care for new radios and such, flash an ics Rom of your choosing and then flash the old firmware patch.
If you want new radios run an ics ruu (2 times, 1st time only updates some stuff and you'll have issues unless you do it 2 times) then flash an ics Rom of your choosing.
Also upgrade to amon ra 3.15 if you are on an older version. 3.15 is updated for the changes in ics
Sent from my Rezound
Ok, I would like the latest RUU, but do I flash through recovery, or rename and flash through hboot or something?
EDIT: I currently am running Ra 3.15
Flash through hboot as a ph98IMG
Run it twice then you'll need to put amon ra 3.15 again.
I'll attach a copy of amon ra 3.15..... You can rename it to ph98img and flash it in bootloader the same way. Or you can use whatever way you prefer.
Edit: here's the link
http://db.tt/UuiVjcrb
from my Rezound
Thanks, That's what I thought. I use to be familiar with this when I was using my thunderbolt. But "upgraded" to the LG spectrum and there was absolutely no development for that phone for the 4 months I had it. So I lost touch. BTW never get that phone. I honestly hated it more than any apple product...which to me is a lot of hate
Ok, so I flashed the 3.14.605.5 Ice Cream Sandwich ZIP RUU, I'm still s-off, unlocked and running RA 3.15 . but now it saying I'm not rooted.
Can't you root it again through AmonRa??
I believe there is an issue with ICS. Just flash a rooted stock ROM.
Sent from my ADR6425LVW using Tapatalk 2
LunaticSerenade said:
I believe there is an issue with ICS. Just flash a rooted stock ROM.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
That's what ended up doing after updating to the 3.14 firmware. Just installed the stock rooted 3.14 ROM.
Sent from my S-OFF Rezound using Tapatalk 2.
thanks for the speedy replies people. I'm downloading the stock rooted 3.14 now. so I will let you know if that fixes it
Ok, downloaded stock rooted deodex rom and everything is good. it's recognizing root again
Jlluna87 said:
Ok, downloaded stock rooted deodex rom and everything is good. it's recognizing root again
Click to expand...
Click to collapse
Excellent. An easy fix is always welcome.
Sent from my Sense 4 Rezound.
I'm currently running an unlocked, S-On rezound with HBoot 2.11 and I'm currently running ViperRez with Kernel 3.0.16.GD0048F1. I'm obviously using the GB firmware patch whenever possible but the GB Firmware patch doesn't work with AOSP roms, and i CAN install the AOSP roms without it, but it won't recognize the SD Card and i can't mount the internal one either.
So what's the best way to get to HBoot Firmware 2.27 so i can start installing newer JB roms?
You'll have to re lock the bootloader and run an RUU to update your firmware
This will bring you to the ics ota official
http://forum.xda-developers.com/showthread.php?t=1810931
Sent from my ADR6425LVW using xda app-developers app
Squirrel1620 said:
You'll have to re lock the bootloader and run an RUU to update your firmware
This will bring you to the ics ota official
http://forum.xda-developers.com/showthread.php?t=1810931
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
1) None of those download links work, and any that do point to a camera fix, not anything about the rom itself.
2) What about the mention of being fully stocked? I'm running a custom rom and the last time i tried
epy0nkaru said:
1) None of those download links work, and any that do point to a camera fix, not anything about the rom itself.
2) What about the mention of being fully stocked? I'm running a custom rom and the last time i tried
Click to expand...
Click to collapse
Here this one points to the global ics leak, the dl link works and it doesn't matter what rom you are on, it will be overwritten with the stock one. Once your firmware is updated you will need to unlock, flash a recovery, then flash a rom of your choice
http://forum.xda-developers.com/showthread.php?t=1835039
Sent from my ADR6425LVW using xda app-developers app
I actually wished the links worked because I think the global leak is what's causing my cpu issues with aosp and kernel's with perflock off/mpdecision used
Squirrel1620 said:
Here this one points to the global ics leak, the dl link works and it doesn't matter what rom you are on, it will be overwritten with the stock one. Once your firmware is updated you will need to unlock, flash a recovery, then flash a rom of your choice
http://forum.xda-developers.com/showthread.php?t=1835039
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
dyetheskin said:
I actually wished the links worked because I think the global leak is what's causing my cpu issues with aosp and kernel's with perflock off/mpdecision used
Click to expand...
Click to collapse
Actually through more rooting I found the right updates VERY DEEP in some other thread.
the post here it here in case anybody comes upon this thread and has the same question:
After upgrading my TP firmware - I am no longer able to run any non 3.16 roms.
I have flashed the 3.15ver. TouchPanel firmware back to phone - but if I install any non 3.16 rom - my screen/touchpanel is dead.
It works in TWRP 2.4.1 only.
Is there any way to once again run CM or AOKP?
Thanks, Jack
Sent from my MeanBean optimized and supercharged ElteVO.
midmadn said:
After upgrading my TP firmware - I am no longer able to run any non 3.16 roms.
I have flashed the 3.15ver. TouchPanel firmware back to phone - but if I install any non 3.16 rom - my screen/touchpanel is dead.
It works in TWRP 2.4.1 only.
Is there any way to once again run CM or AOKP?
Thanks, Jack
Sent from my MeanBean optimized and supercharged ElteVO.
Click to expand...
Click to collapse
Nope, you msut use the 3.15 tp driver for 3.15 roms and aokp, cm etc
Sent from my EVO using Tapatalk 2
You say driver. I believe that is part of the rom. I did flash the 3.15 touch panel firmware back to the phone.
I tried the pac-man cm 10.1 rom as well as miui 4.12.
My touchscreen is dead once the phone boots into the rom. It only works in recovery or meanbean 3.2 (3.16) rom.
Sent from my MeanBean optimized and supercharged ElteVO.
Here try this. It is the old touch panel driver, which, according to the meanbean thread, allows you to use non 3.16 roms.
Just flash the PJ75IMG.zip thru bootloader
Credit to mikeyxda and capt. Throwback
http://themikmik.com/showthread.php...o-1-12-11-1210&p=286650&viewfull=1#post286650
Sent from my EVO using Tapatalk 2
bennyboy78 said:
Here try this. It is the old touch panel driver, which, according to the meanbean thread, allows you to use non 3.16 roms.
Just flash the PJ75IMG.zip thru bootloader
Credit to mikeyxda and capt. Throwback
http://themikmik.com/showthread.php...o-1-12-11-1210&p=286650&viewfull=1#post286650
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Thank you very much for trying to help - but I already have that file and have flashed it through bootloader. That's what I was doing. From what was written in the meanbean thread - I should have been good to go. But no luck.
Anyone that flashed the new touchpanel firmware can not run any rom other than meanbean 3.? on or the stock 3.16 rom.
Sent from my MeanBean optimized and supercharged ElteVO.
On reverting the touchpanel - I was being a retard. (No offense meant to any MR persons)
You have to install the rom first and then run the 3.15 touchpanel firmware file.
Case solved. You must flash from the bootloader AFTER any non 3.16 rom install the 3.15 touchpanel firmware/driver.
Thanks to anyone that tried to help.
Jack
Sent from my MeanBean optimized and supercharged ElteVO.
midmadn said:
On reverting the touchpanel - I was being a retard. (No offense meant to any MR persons)
You have to install the rom first and then run the 3.15 touchpanel firmware file.
Case solved. You must flash from the bootloader AFTER any non 3.16 rom install the 3.15 touchpanel firmware/driver.
Thanks to anyone that tried to help.
Jack
Sent from my MeanBean optimized and supercharged ElteVO.
Click to expand...
Click to collapse
Ahh, glad you got the problem solved. Thanks for sharing that info as im sure other people will run into the same problem.
Sent from my EVO using Tapatalk 2
bennyboy78 said:
Here try this. It is the old touch panel driver, which, according to the meanbean thread, allows you to use non 3.16 roms.
Just flash the PJ75IMG.zip thru bootloader
Credit to mikeyxda and capt. Throwback
http://themikmik.com/showthread.php...o-1-12-11-1210&p=286650&viewfull=1#post286650
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
How do you flash from bootloader? i place the file on my phone but i go to bootloader and nothing happens
Edit: NVM im s-on
I had been running CM10.1(deck's build) on my phone as my daily driver for a while. At some point I was unable to get 4g anymore and wanted to update my PRL (from 25010 to 25012) thus needed to switch to a Sense ROM.
I followed instructions on the MeanBean ROM thread for S-OFF users and upgraded my firmware from 3.15.651.16 to 3.16.651.3 using Captain_Throwback's firmware from here
Now that my PRL and profile are updated, I want to go back to my nandroid backup of the DD CM10.1 ROM and am wondering if I need to downgrade my firmware back to 3.15.651.6 to get the AOSP ROM to work, or if downgrading would brick my phone.
I am S-OFF, hboot 2.09.4444 and did not install the latest tp firwmare.
As long as you did not do the tp firmware then no need to downgrade.
Sent from my EVO using Tapatalk 2
thicklizard said:
As long as you did not do the tp firmware then no need to downgrade.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Thanks a bunch thicklizard for the encouragement!! Restored my aosp nandroid and no issues.
My wife's Evo kept failing the 3.17 OTA so I moonshined it this week to allow her to get on latest firmware and software. She is stock other than S-off and root. I am fully aware that the firmware/radio and software are two different things. After getting S-off I flashed the current 3.17 bootloader firmware from Captain's thread and all went well and she is now on 1.13.11.0830 radio. Now I want to get her the software updates to move her from 3.16.651.xx to 3.17.651.4. My question is how to best do this. My thought is to flash the stock rooted deodexed rom but I didn't know if there was an alternative better way. Also, considering that an OTA upgrade of software is a dirty flash sort of, can I dirty flash stock rooted 3.17 over her current 3.16 without doing full wipe. Yes, I realize full wipe would be best and I am willing to do that if dirty flash is a mess. But, for time saving, is there any real danger in dirty flashing stock rooted 3.17 over her current stock rom with s-off and root? It just seems to me to be the rooted equivalalent of taking the OTA update.
Thanks for any advice.
evoimevo said:
My wife's Evo kept failing the 3.17 OTA so I moonshined it this week to allow her to get on latest firmware and software. She is stock other than S-off and root. I am fully aware that the firmware/radio and software are two different things. After getting S-off I flashed the current 3.17 bootloader firmware from Captain's thread and all went well and she is now on 1.13.11.0830 radio. Now I want to get her the software updates to move her from 3.16.651.xx to 3.17.651.4. My question is how to best do this. My thought is to flash the stock rooted deodexed rom but I didn't know if there was an alternative better way. Also, considering that an OTA upgrade of software is a dirty flash sort of, can I dirty flash stock rooted 3.17 over her current 3.16 without doing full wipe. Yes, I realize full wipe would be best and I am willing to do that if dirty flash is a mess. But, for time saving, is there any real danger in dirty flashing stock rooted 3.17 over her current stock rom with s-off and root? It just seems to me to be the rooted equivalalent of taking the OTA update.
Thanks for any advice.
Click to expand...
Click to collapse
Your firmware is updated.
Software is based on the rom you are running if you flash a 3.17 rom you will be updated in that area also.
As for dirty flashing it's not a good idea to dirty flash when going to a new base
thanks bigdaddy, I appreciate the response. Is there any downside to being on older software and newer firmware? I thought Captain TB or someone had said that the firmware and software are optimized to work together and shouldn't be out of sync. If that is the case I probably need to bite the bullet and go ahead and wipe and flash the stock rooted deodexed rom to get her the software update.
bigdaddy619 said:
Your firmware is updated.
Software is based on the rom you are running if you flash a 3.17 rom you will be updated in that area also.
As for dirty flashing it's not a good idea to dirty flash when going to a new base
Click to expand...
Click to collapse
Is it just me... Other than stock rooted 3.17, I'm not seeing any custom roms for this base. Im still using mean bean.
Sent from my EVO using xda app-developers app
lanewhit said:
Is it just me... Other than stock rooted 3.17, I'm not seeing any custom roms for this base. Im still using mean bean.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I think it is kind of what bigdaddy was saying and what CTB has said...3.17 is the software update that brought the firmware update if done OTA. I believe what CTB did was extract the firmware so people could update the radio/firmware without installing the OTA or stock 3.17 ROM. So, you can have latest radio/firmware with CM10.2 for instance. In my case, my wife wants to keep stock as much as possible so I was trying to figure out best way to get her to most recent stock software without taking it OTA. I think the way to do that is going to be to flash 3.17 stock rooted rom. As you mentioned I haven't seen many/any roms built from 3.17 source if it has even been released at all yet. I moved to CM roms long ago and haven't used any Sense roms since meanbean 3.09 which last I checked hadn't been updated in months. There are plenty of CM10.2 based ROMs available that have tons of updates and fixes. I left my wife's stock because otherwise I get blamed every time Sprint or htc messes something up. This way I can say I didn't touch her phone. By s-off and rooting it and installing stock rooted deodexed I am opening myself back up to her wrath but so be it. It's better than her telling me 4 times a day that her phones says an update is ready but fails every time she tries to install it OTA. It's all about path of least pain. LOL.
I would flash the new rooted base. As I mentioned before, I'm on mean bean 3.09 with the updated firmware from the Captains thread and all has been working great.
Sent from my EVO using xda app-developers app
lanewhit said:
I would flash the new rooted base. As I mentioned before, I'm on mean bean 3.09 with the updated firmware from the Captains thread and all has been working great.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Cool. Thanks for that info. I think I am going to do a twrp backup and a dirty flash of stock rooted first. I know that's not the best and most advisable route but dirty flashing is underrated. If things are wonky I will wipe and factory reset and flash again. Dirty flashing a new base on top of the old isn't THAT much different than getting the software update OTA. I trust dirty flashing more than I trust Sprint to be able to seamlessly deliver it. Probably do it tonight while she's asleep and see if she notices anything different tomorrow. I'll just blame Halloween spooks and goblins if things go wrong.