So I updated my rogers HTC One X with the OTA jellybean update. Then I decided I wanted to root. I did, TWRP (the older revision than the current one) didn't work because the touchscreen wouldn't work. Updated TWRP to the highest version (the one with the on screen keyboard?) and it worked. Flashed Jellybam, stuck on boot screen, flashing white and animation. Then I flashed the boot.img with adb, then flashed jellybam again. Worked, but no touch screen.
Is my solution just to wait for roms that support new hboot?
So what was the benefit to doing the ota again? You seem like you knew the risks I'm just wondering what the reward was?
Sent from my HTC One XL
Are you sure you are on the latest version (2.3.3.1)? Its supposed to fix the the touch screen issue.
http://forum.xda-developers.com/showthread.php?t=1677447
My reward was the chance to have a digital interaction with someone who offers no answer to a simple question, and instead thinks snark is worth their posting time. Obviously.
Twrp works fine as I said. It's the roms, once flashed, that don't respond to touchscreen swipes.
veemodz823 said:
Twrp works fine as I said. It's the roms, once flashed, that don't respond to touchscreen swipes.
Click to expand...
Click to collapse
The hboot screwed up both touchscreen response within TWRP and within the OS. I would have assumed that the new version of TWRP fixed both. I'm not personally on hboot 2.14, so hopefully some folks that are can chime in with some insight.
redpoint73 said:
The hboot screwed up both touchscreen response within TWRP and within the OS. I would have assumed that the new version of TWRP fixed both. I'm not personally on hboot 2.14, so hopefully some folks that are can chime in with some insight.
Click to expand...
Click to collapse
I didn't think that a recovery would actually fix something within an os when the two are two completely different things in my mind. I think that TWRP working on 2.14 means that something in TWRP has been changed from previous versions to accomodate 2.14. I guess the same just has to be done for the roms, but that's just my uneducated guessing and logic.
I too am having the same issues. Installed 5 different rom's, all of them had no touch screen capabilities. Still working on it, if I come across anything I will let you know. Were you able to backup your old rom with TWRP? If you did I would love if you could send me your recovery file since CWM happened to delete mine. I have Rogers evita if that's the same as yours.
Hey, no I didn't back up.
did you try this rom?
http://forum.xda-developers.com/showthread.php?t=2076361
veemodz823 said:
I didn't think that a recovery would actually fix something within an os when the two are two completely different things in my mind.
Click to expand...
Click to collapse
Yes, they are separate. But it's recovery that is installing the OS. So it seems logical to me it can cause a problem with the OS.
Sent from my HTC One X using xda app-developers app
veemodz823 said:
My reward was the chance to have a digital interaction with someone who offers no answer to a simple question, and instead thinks snark is worth their posting time. Obviously.
Click to expand...
Click to collapse
Sorry I didn't know you didn't have a backup. Now I feel terrible for joking with you before.
Sent from my HTC One XL
veemodz823 said:
Hey, no I didn't back up.
did you try this rom?
http://forum.xda-developers.com/showthread.php?t=2076361
Click to expand...
Click to collapse
I haven't tried that rom, it's an Australia one....don't know if that would work for us rogers guys. Might perm brick it
http://forum.xda-developers.com/showthread.php?t=2083314
It seems to have worked for this dude and I *believe* the Telstra is the same phone as ours and not an international version. But make sure. I would've flashed it but I'm at my volunteer.
Telstra is the same phone as Rogers (dual core S4 version of the One X/XL).
If it works, you'll need to manually enter the Rogers APN.
Sent from my HTC_Flyer_P512_NA using xda app-developers app
Does anybody think its possible that the new OTA firmware (flashing the entire OTA and not just the ROM) has some sort of difference compared to older ones.. surely a broken touch screen after the OTA can't be a coincidence. 2nd case.
Or its possible that the ROMs/recovery aren't compatible with some sort of change in firmware.. I wonder..
absolutelygrim said:
Does anybody think its possible that the new OTA firmware (flashing the entire OTA and not just the ROM) has some sort of difference compared to older ones.. surely a broken touch screen after the OTA can't be a coincidence. 2nd case.
Or its possible that the ROMs/recovery aren't compatible with some sort of change in firmware.. I wonder..
Click to expand...
Click to collapse
The weird thing is this: with older TWRP you can't get the touch screen to respond, but with newer TWRP it will respond to touch.
In the thread I posted above someone says this:
"Well known and posted about all over this forum.
HTC changed some firmware relating to the touchscreen in the 3.17 update. Roms require a kernel update to work. Twrp can cheat and just use htc's new kernel, cm10 build their kernel from source so could be hard to figure what changed until HTC release source."
veemodz823 said:
The weird thing is this: with older TWRP you can't get the touch screen to respond, but with newer TWRP it will respond to touch.
In the thread I posted above someone says this:
"Well known and posted about all over this forum.
HTC changed some firmware relating to the touchscreen in the 3.17 update. Roms require a kernel update to work. Twrp can cheat and just use htc's new kernel, cm10 build their kernel from source so could be hard to figure what changed until HTC release source."
Click to expand...
Click to collapse
typical HTC.. If you are still having issues, I may be able to help you RUU downgrade
Some already quoted me but to be clear.
Htc ship firmware updates with their official updates that customs rarely ever ship. Firmware relating to the touchscreen were updated and kernel changes are required to use it.
Twrp uses official sense kernel so just updated to latest. All kernels based on the kernel that shipped with 3.17 willbe fine.
Eg custom 3.17 jb roms and kernels will be fine.
But all things not based on 3.17 do not have the required kernel updates for the touchscreen.
It is unknown what changed so likely this won't get resolved until Htc release source for 3.17 kernel.
Downgrading from 3.17 has been reported to perma brick phones. Do so at your own risk, you have been warned..
---------- Post added at 05:07 AM ---------- Previous post was at 04:27 AM ----------
Also twrp does not install os/roms. Roms install themself. Roms include an update binary that has all the file operation apps like del, copy, move, read operation etc. And they include an update script that makes use of all the apps it ships with.
Twrp is a skeleton, it just starts the Rom and lets the rom do its own thing.
Twrp does not alter how a Rom installs, eg it can neither break nor fix things like this touchscreen problem.
All right, so to he clear, its just a matter of waiting for 3.17 compatible roms. Would that be far off considering Twrp is already updated to support 3.17 kernal roms? Or does HTC need to release source for custom 3.17 roms to be made? And what about that Telstra Rom that was mentioned? Why would that work, how was that made?
Twrp 2.3.3.1 works because it uses Htc sense 3.17 kernel (based on linux kernel 3.4.10). Twrp does not "support 3.17 kernel roms", twrp does not care what kernel a Rom has. Twrp simply has updated so it can function. If a Rom can function or not has nothing to do with twrp.
Telstra 3.17 Rom works because it is based on 3.17 Telstra Rom and uses the 3.17 kernel.
There is several 3.17 based roms. Based on the singtel 3.17.707.1 and Telstra 3.17.841.1 and I'm sure now there is loads of evita regions with 3.17 available more variations will show up.
Cm is not a sense rom. Same goes for aokp and such. Anything in "original development" is not based on sense. All those can not use sense kernels as they would need to add all the extra Htc stuff for it to work and you just end up with sense and not cm etc.
I can say again; only roms that can use the 3.17 kernel work and basically that just means only sense 3.17 roms. Anything else will not work. That is unlikely to change until 3.17 kernel source is released. There is several 3.17 based roms.
Kernel source could take up to 3 months. It has been 1 already. So could be another 2 months before this can be fixed in non sense roms.
Related
Hi,
First post (yay!) so I have a few questions:
1. Where is the 'thanks' button? There are loads of you I wanted to thank but it has not shown up on my forums where the help section said it would be. Has shown up now - guess I had to make a post before I could thanks people
2. I have the emmc chip that is prone to failure but after reading the forums it seems there may be a way to recover from it - is that right, and the chip is no longer a big problem? (Absolutely cannot afford to brick this phone as it's a present from a wife already angry that I rooted it)
3. Should I try to upgrade my HBOOT to 2.00.2002 and Radio (to what? the PCIMG88.zip from the Chinese website?) and install a new ROM, or try and revert everything back to s-on, unrooted stock rom and wait for the official update that is rolling out now in the UK? I'd prefer the option with the least chance of stress and bricking the phone.
4. After flashing a new ROM (if I do) I understand I should avoid updating/installing apps at the same time so my emmc chip isn't fried - can I reinstall 1 by 1 from Titanium backup, and won't Google start trying to download and install everything else at once? How do I avoid that?
I'm in the UK on T-Mobile PAYG with (I think) an unbranded Desire S
Android Version
2.3.3
HTC Version
2.1
Baseband Version
20.28b.30..0805u_38.03.02.11_M
Kernal Version
2.6.35.10-g13f6602
[email protected]#1
Build Number
1.28.401.1 CL24243 release-keys
Softawre Number
1.28.401.1
Saga PVT Ship S-off RL
hboot 6.98.1002
radio 38.03.02.11_Me
1.look at bottom right corner
4.if u restore all apps with titanium backup at once its ok, i think..
but when u setup your phone dont add google account to sync your app..
restore your apps and then add it..
take a look to ben_pyett signature for some useful links..
Theses are just my opinions
Thanks button to bottom right of each post next to edit button,
Don't bother upgrading you're hboot to 2.xx.xxxx (not yet any benefit)
Don't bother going back to s-on.
Don't pull battery.
I'd try to install the normal ENG bootloader over your revolutionary one if you can.
I'd also suggest installing the 4 EXT recovery instead of Cwm.
Don't do anything to you're device that you don't fully understand.
You've done the most difficult part making your device s-off now install some quality custom roms and enjoy it.
Always take full nandroid device backups prior to performing any steps on your device, so that you have a safe point to roll back to in case of problems.
When installing a new custom ROM don't enter your google account details until the last stage of the setup after the device had stopped all configuration, then go into the market app and check to see of it's installing any apps, if it is then cancel downloads, only some versions of market attempt the parallel download of several apps which has been linked to killing eMMC. Later one download one application at a time which seems ok..add suggested advice I also use titanium backup app to restore my apps after the new installation of a ROM rather than relying on market installs.
There is now more information on the eMMC issue, what was previously thought of a dead device can now be recovered but each instance is unique.
Enjoy
Swyped from my Desire S using XDA Premium
Guys,
Thanks for the replies - when I asked about the Thanks button it wasn't there, it only appeared after I posted so that is sorted now.
Ben, I do have 4EXT already installed and a backup, this isn't my first android phone but I would still class myself as a noob - I think I know what I'm doing generally but probably don't.
I think I might try for the ENG Hboot if I can find that post but I thought I would need the 2.00.2002 Hboot for sense 3.0 roms.
What is the advantage of the ENG Hboot over the revolutionary one?
Also, I'm wondering if I will receive an OTA option to update since I have s-off and rooted - I'm pretty sure I should not accept as it looks like some people have been experiencing problems trying to install the OTA over their non-stock phones/settings.
Can anyone confirm that:
1) my phone would see the update if it rolls out and
2) I should not install it unless I go back to stock rom and s-on?
Installing a new ROM will alert my wife to the fact I have rooted it so I'm in no hurry until I decide I can't live without some spectacular new features
Yep, DO NOT INSTALL THE OTA
^when you are rooted and s-off.
It will lead to problems.
I'd really suggest you try out Hyperion ROM/Saga 3D
They are like the stock ROMs with sense 3.0 (new OTA based)
They are optimised and better than the stock ota anyway
Sent from my HTC Desire S using xda premium
4myphone said:
Guys,
Thanks for the replies - when I asked about the Thanks button it wasn't there, it only appeared after I posted so that is sorted now.
Ben, I do have 4EXT already installed and a backup, this isn't my first android phone but I would still class myself as a noob - I think I know what I'm doing generally but probably don't.
I think I might try for the ENG Hboot if I can find that post but I thought I would need the 2.00.2002 Hboot for sense 3.0 roms.
What is the advantage of the ENG Hboot over the revolutionary one?
Also, I'm wondering if I will receive an OTA option to update since I have s-off and rooted - I'm pretty sure I should not accept as it looks like some people have been experiencing problems trying to install the OTA over their non-stock phones/settings.
Can anyone confirm that:
1) my phone would see the update if it rolls out and
2) I should not install it unless I go back to stock rom and s-on?
Installing a new ROM will alert my wife to the fact I have rooted it so I'm in no hurry until I decide I can't live without some spectacular new features
Click to expand...
Click to collapse
You shouldn't even consider OTA updates unless you're S-ON and STOCK....
certainly don't try it on a rooted device, just asking for trouble...I always simply disable the check for updates and Tell HTC features..
There are benefits to having ENG HBOOT (although I'm not 100% of all of them) I believe that you're able to downgrade easier, should you require the HBOOT number also doesn't stand out like a sore thumb......6.xx.xxxx should you want to return device!
All the new Sense 3.0 and Sense 3.5 ROMS work on old HBOOT, so just no point in upgrading, I did the upgrade before I released this and it's not worth going back.
EDIT: You also need to have a word with the misses! It's now your phone so you should be able to do what you want to it - whatever makes you happy!!
ben_pyett said:
You shouldn't even consider OTA updates unless you're S-ON and STOCK....
certainly don't try it on a rooted device, just asking for trouble...I always simply disable the check for updates and Tell HTC features..
There are benefits to having ENG HBOOT (although I'm not 100% of all of them) I believe that you're able to downgrade easier, should you require the HBOOT number also doesn't stand out like a sore thumb......6.xx.xxxx should you want to return device!
All the new Sense 3.0 and Sense 3.5 ROMS work on old HBOOT, so just no point in upgrading, I did the upgrade before I released this and it's not worth going back.
Click to expand...
Click to collapse
Was the hboot update 2.xxxx official, or was it from the Goapk forums?
Sent from my HTC Desire S using xda premium
olyloh6696 said:
Was the hboot update 2.xxxx official, or was it from the Goapk forums?
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Mine? think it was from the forums, but, same version number as OTA released HBOOT? why do you ask?
ben_pyett said:
Mine? think it was from the forums, but, same version number as OTA released HBOOT? why do you ask?
Click to expand...
Click to collapse
Oh, just wondering, as i never saw the update posted officially...
So if it is official, why does the official sense 3.0 rom not make full use of the new partitions?
Sent from my iPod touch using Tapatalk
olyloh6696 said:
Oh, just wondering, as i never saw the update posted officially...
So if it is official, why does the official sense 3.0 rom not make full use of the new partitions?
Click to expand...
Click to collapse
I believe this is because the cooks have made it this way.....My understanding is that the "official" S-On OTA upgrade installs the new version HBOOT and makes use of this new layout.
Someone correct me if this is wrong?
ben_pyett said:
I believe this is because the cooks have made it this way.....My understanding is that the "official" S-On OTA upgrade installs the new version HBOOT and makes use of this new layout.
Someone correct me if this is wrong?
Click to expand...
Click to collapse
Oh right !
How can a OTA install a new hboot, radio, and complete new UI, but the user doesn't lose any data ?!
It's strange .. when we want to upgrade, we have to do a full wipe
Sent from my HTC Desire S using xda premium
Can I get a census of people's model numbers?
If you pull the battery, the last string of numbers under the last bar code is what we are looking at.
I have two doubleshots, and I have two model numbers (part numbers):
99HML001-01 A
and
99HML001-00 A
What does everyone have?
Wondering if this has anything to do with the odd problems people are having with ICS Roms, and with the HTC unlock tool.
When you post your model number (part number) can you say if you've successfully flashed an ics ROM, and if you've used the HTC unlock tool successfully?
I have not flashed any ICS Roms yet, but am going to try soon - I have also not used the HTC unlock tool on either phone as they are both S-OFF now.
Thanks!
(any other observations on deviations between any model numbers would be great too)
I have "99HML001-00 A".
Unlocked S-ON, unable to flash ICS ROMs.
99HML001-00 A
revolutionary
flashed piroice once
99HML005-00 A
I used Rev Unlock Tools.
I've flashed 3 ICS Roms.
One based of the Sensation Leak.
Two Based of AOSP Soucre from Sensation
Sent from my MIUI.us Doubleshot using Tapatalk
The 00 A one.
No issues since the SOD fix was implemented.
Only really given "TBalden's" ROM a try as i found it most complete. As well as the fact that he helps out so much if you want something fixed.
Also: used Revolutionary
Just my spare change.
i told you this in the IRC but i'll document it here so you have it all in one place:
99HML005-00 A
haven't flashed anything ICS, or anything really for that matter, since updating to 1.55.531.3 by the OTA. i am kind of wondering if the people having problems with some ROMs are people who also updated by the OTA, and thus have the new radio and the other extra firmware bits that came with the OTA. it seems people who never did the OTA can flash anything at will..... is this correct?
edit: am also S-OFF by the Rev. method
Mine is 99HML001-00 hope this help also used the rev methed
99HML001-00 A here
didn't flash any ics rom btw, s-off'ed with revolutionary and such
I've got a 99HML005-00 A
P/N: 99HML001-00
all ics roms run fine
Recently received a warranty exchange
P/N: 99HML001-00 like all the others thus far
Revolutionary
Pyr-o-Ice ICS 1.0.2
99HML001-00 A
Rooted with newest H-Boot, so s-off.
Not able to flash any ROMs.
99HML001-00
Rev S-off
flashed all ics roms successfully
I've got P/N: 99HML005-00A
No problems with any ICS roms.
yogi2010 said:
...
haven't flashed anything ICS, or anything really for that matter, since updating to 1.55.531.3 by the OTA. i am kind of wondering if the people having problems with some ROMs are people who also updated by the OTA, and thus have the new radio and the other extra firmware bits that came with the OTA. it seems people who never did the OTA can flash anything at will..... is this correct?
...
Click to expand...
Click to collapse
That's a good thought and definitely worth pursuing.
(keep hitting thanks instead of quote -lmao o wells, )
I have a HTC one XL (s-on, hboot 1.14) with magio rom (4.2) installed. Suddenly my phone stopped getting a network signal. At first I thought its a hardware issue but then I found out it with the software plus its a common issue. Im not an experienced user.
So far I've found out the solutions are
1) Updating the firmware - I have no idea about this. Do I have to install the stock and root again? Is this installing the stock RUU? My CID is all ones, something like 1111111. Will I brick my phone? Do I have to install both th rom and firmware?
2) Beastmod - I feel dumb after reading this thread because it doesnt say what are the requirements to install this. Never installed a kernal before.
http://forum.xda-developers.com/showthread.php?t=2165880
3) Market app - network speed boost - I tried this, workd like a charm in the first.Sent a few texts but as soon as I made a call I lost the network
Due to my lack of knowledge on the subject I'm sacared to experiment because there is a chance of bricking the phone. I understand the issue is related with android 4.2 so a noob proof guide will help everyone who have the issue.
(example - http://forum.xda-developers.com/showthread.php?t=1787148)
kind regards
Whether you decide to update the firmware or install the Beastmode kernel, you will need s-off. You'll find the s-off thread here. You'll almost definitely need to change ROMs temporarily as it seems to be virtually impossible to achieve on a Sense 5 Android 4.2.2 ROM.
The kernel is s-on friendly but many people who are s-on have had trouble installing it. The 2.15 firmware can be found in the first post of this thread, along with instructions on how to flash it. It has nothing to do with returning to stock or RUUs and you don't need to modify your phone other than getting s-off first.
Sent from my Evita
dragz said:
So far I've found out the solutions are
1) Updating the firmware - I have no idea about this. Do I have to install the stock and root again? Is this installing the stock RUU? My CID is all ones, something like 1111111. Will I brick my phone? Do I have to install both th rom and firmware?
Click to expand...
Click to collapse
The firmware package being discussed (for resolving signal drop issues on Sense 5 ROMs) and linked by timmaaa above is not an RUU, but just the hboot, radio, boot.img, media and WiFi modules that came with the "official" Sense 5 OTA. It will only overwrite the modules I named, not the ROM. Nothing else needs to be done (you will still have your current ROM, root, etc.).
You must be s-off to install this.
timmaaa said:
Whether you decide to update the firmware or install the Beastmode kernel, you will need s-off. You'll find the s-off thread here. You'll almost definitely need to change ROMs temporarily as it seems to be virtually impossible to achieve on a Sense 5 Android 4.2.2 ROM.
The kernel is s-on friendly but many people who are s-on have had trouble installing it. The 2.15 firmware can be found in the first post of this thread, along with instructions on how to flash it. It has nothing to do with returning to stock or RUUs and you don't need to modify your phone other than getting s-off first.
Sent from my Evita
Click to expand...
Click to collapse
thank you, it worked
My request is very simple, but the story behind my phone might be lengthy. Here we go.
I bought a my HTC one x Evita on Amazon.com. The listing said it was new but it wasn't. How i got to know that when I tried to update the phone. I had considerable trouble doing so. Up to now I have not been able to do this.
I contacted xda- Developers.com and by providing details of the phone, they were able to identify that the phone wasn't new. The phone came with a h/boot of 0.08 very weird. I had extreme difficulty with flashing a custom ROM. But the good folks at xda got me thru again.
Here is my stress now. I tried to upgrade my phone using the latest RUU for it 3.18 after many tries. I will not install, kept failing saying cannot connect to phone try plugging phone back into PC, my but when I try it with RUU2.17 it works just fine so it's not the cable.
I got fed up with this, and decided to flash custom ROM.I flashed Viper XL with great success, then tried Cleanrom which is what I am currently on. By the way I have noticed something familiar with both Flashed Roms. They keep losing service and restarting the phone on its' own. Is this a h/boot issue or a Rom issue? Also I am thinking of installing the CM11 nightly ROM for my phone, please be reminded I am currently on H/Boot 1.14.
I tried flashing cm11 no success.
The signal drops and reboots (and the solution to those problems) have been mentioned literally dozens of times in both of those ROM threads. Please search properly before posting, it's rule #1 here on XDA.
The reason you can't flash cm11 is because your firmware is too old. I know you said the 3.18 RUU didn't work but that's what you need to do to flash any recent aosp ROM. The 4.4 ROMs also require a modify version of TWRP to flash.
Sent from my Evita.
timmaaa said:
The signal drops and reboots (and the solution to those problems) have been mentioned literally dozens of times in both of those ROM threads. Please search properly before posting, it's rule #1 here on XDA.
The reason you can't flash cm11 is because your firmware is too old. I know you said the 3.18 RUU didn't work but that's what you need to do to flash any recent aosp ROM. The 4.4 ROMs also require a modify version of TWRP to flash.
Sent from my Evita.
Click to expand...
Click to collapse
Thanks alot , great. Just one more question. I am supercid and s-off. Do I need to relock to boot-loader in order to run RUU3.18?
No you don't need to relock it.
Sent from my Evita.
Hi, please let me know if this should me moved to another section.
I am coming from Samsung phones, and building and installing ROMs for them. I got an HTC A9 a while back and I am having cyanogenmod withdrawals lol. I have the Sprint model so there doesn't seem to be any compatible builds, please let me know if I am wrong.
So basically I am breaking my dev shoes back out and going to attempt to build a CM ROM for the Sprint A9, but some things around still confuse me for HTC. I already have S-Off and unlocked bootloader, running a rooted stock image. But I am not sure I fully understand this RUU stuff? Also, if anyone else could fill in the blanks for me regarding differences between working with samsung vs htc. I already know you can't use Odin, that was one thing I really hated about samsung anyway, I am far more comfortable using fastboot lol. But any advice would be appreciated.
Thanks!
miked63017 said:
Hi, please let me know if this should me moved to another section.
I am coming from Samsung phones, and building and installing ROMs for them. I got an HTC A9 a while back and I am having cyanogenmod withdrawals lol. I have the Sprint model so there doesn't seem to be any compatible builds, please let me know if I am wrong.
So basically I am breaking my dev shoes back out and going to attempt to build a CM ROM for the Sprint A9, but some things around still confuse me for HTC. I already have S-Off and unlocked bootloader, running a rooted stock image. But I am not sure I fully understand this RUU stuff? Also, if anyone else could fill in the blanks for me regarding differences between working with samsung vs htc. I already know you can't use Odin, that was one thing I really hated about samsung anyway, I am far more comfortable using fastboot lol. But any advice would be appreciated.
Thanks!
Click to expand...
Click to collapse
I don't know much about the differences between dev'ing for HTC/Samsung, but an R.U.U is a Rom Update Utility, it includes 100% stock Rom, firmware, radios, etc. Flashing it will wipe ALL data on device (internal/SD card ) as well, so back Up any saved pics/data
Sent from my HTC One A9 using XDA Labs
So I got a flashable CM image, but it boot loops and I think I need to work on the kernel since I was using the one from hiaeul and I need hiaewhl. I pulled the sources from HTC and will start on that, but I have a question. Does anybody know what causes the "This build is for development purposes only" message?
I don't have the message on the stock rooted rom, but the message popped up after flashing CM, and coincidentally is where it bootloops at. I thought this pops up once you unlock the bootloader, but I haven't seen it until now.
miked63017 said:
So I got a flashable CM image, but it boot loops and I think I need to work on the kernel since I was using the one from hiaeul and I need hiaewhl. I pulled the sources from HTC and will start on that, but I have a question. Does anybody know what causes the "This build is for development purposes only" message?
I don't have the message on the stock rooted rom, but the message popped up after flashing CM, and coincidentally is where it bootloops at. I thought this pops up once you unlock the bootloader, but I haven't seen it until now.
Click to expand...
Click to collapse
It's built into the hboot/boot loader. Only way to change it is to hex edit the boot, which is risky. All HTC phones get that red msg after flashing (I forget exactly what causes it, I think custom boot.img, kernel, or something like that)
Sent from my HTC One A9 using XDA Labs
I could be wrong...but i remember only getting that red message about build being dev purposes only...when i was flashing or attempting to flash a different firmware meant originally for international handset versions after changing my CID/MID. It has been awhile since those days when i first got the A9 and nearly bricked it but i think that was the cause. If so, perhaps its the boot or kernel that is the issue? I also came from Samsung to HTC and it was quite the learning curve. ONly differences ive seen is...well...everything lol. Using RUUs, flashing via fastboot/adb sans odin, encryption of the internal memory, S-on/S-off and unlocking the bootloader. I am sure you know all these as well lol but just mean in general its a real b*tch working with this handset and it is picky on little things like specific order of events like flashing order......if you have several things to flash ive seen it mess up from just one part out of sequence when flashing. Anyhoo, still pretty new on a lot myself so I could be off but its what ive experienced so far. Good luck though and Ill be looking out your results for sure.
P.S - I also have sprint so I posted these elsewhere since no one else really looks out for our version much haha and you may need these for some reason later.
Sprint 1.60.651.4
http://www.mediafire.com/download/ki...1.60.651.4.exe
also
http://www.mediafire.com/download/d5...1/firmware.zip - for the Firmware zip to be flashed via RUU mode
System/recovery/boot images for stock are below:
http://www.mediafire.com/download/xe...zfh3x/boot.img
http://www.mediafire.com/download/oa...p/recovery.img
http://www.mediafire.com/download/48...g7j/system.img
mcbright80 said:
P.S - I also have sprint so I posted these elsewhere since no one else really looks out for our version much haha and you may need these for some reason later.
Sprint 1.60.651.4
http://www.mediafire.com/download/ki...1.60.651.4.exe
also
http://www.mediafire.com/download/d5...1/firmware.zip - for the Firmware zip to be flashed via RUU mode
System/recovery/boot images for stock are below:
http://www.mediafire.com/download/xe...zfh3x/boot.img
http://www.mediafire.com/download/oa...p/recovery.img
http://www.mediafire.com/download/48...g7j/system.img
Click to expand...
Click to collapse
Psst, none of your links are working. Looks like Mediafire deleted them.
help htc one a9
I recently updated my HTC One A9 to the new Marshmallow 6.01 version and now the wifi does not work at all (missing wifi module (8)) and the battery is at 4000%. My software number is 1.56.709.70, i believe this is the taiwan variant but it is unlocked. How do I fix this? Please help, do I flash an ruu or something? How do I know which ruu works for this phone?
JohnRogers23 said:
Psst, none of your links are working. Looks like Mediafire deleted them.
Click to expand...
Click to collapse
Ah damn! Ok ill upload them elsewhere...
JohnRogers23 said:
Psst, none of your links are working. Looks like Mediafire deleted them.
Click to expand...
Click to collapse
NEW LINK to Sprint 1.60.651.4
https://1drv.ms/f/s!AtVcVcbLOGTdgP9-e2NAN2fNHHIKVQ