Related
Hi guys. I have just recently bought this phone. This is my first HTC phone, ive always used samsung phones and wanted to try out the HTC. I managed to unlock the bootloader, root the phone and install twrp. My phone was bone stock so I downloaded the latest nightly for CM10 and gapps. Now for samsungs i didnt have to extract the boot.img and flash that via fastboot. so thinking the flashing process would be the same i flashed cm10, gapps and rebooted. And like clockwork the phone went into a boot loop. I found this little blurb in this thread http://forum.xda-developers.com/showthread.php?t=1957193
"5) Once your phone is in bootloader mode, type the following command fastboot flash boot boot.img ( If command prompt is closed then open command prompt in the folder where boot.img, adb, fastboot are present . For example: C:\android-sdk\platform-tools - Same folder used in step 3)
5) Then run the following command adb reboot recovery
6) Your phone is in TWRP recovery
7) Select mount from recovery ( See mount - image in the attachments for example)
8) Copy the ROM.zip which you downloaded earlier to the SD card ( For example cm-10-20121012-NIGHTLY-evita.zip) ( Not the extracted folder but the actual zip file which you downloaded)
4) Copy the gapps into sd card ( you need to download gapps if you using CM10 or ASOP roms )
5) Unmount, then select Wipe and select Factory reset ( it is recommended to do a factory reset before flashing the new ROM. ) (See wipe, wipe1 images below )
6) Select Install in recovery and flash the ROM.zip
7) You need flash gapps if you flashing CM10 or ASOP ROMS
so i re did the process. flashed boot img through fastboot, rebooted to recovery, flashed the rom that was already on the sd card, flashed the gapps package and rebooted phone. and i did do a factory reset when installing the rom. the phone rebooted, but this is where im stuck. the phone boots to the setup screen where you basically select the language. SCREEN is unresponsive, its not letting me click on start, its not registering my touch anywhere on the screen. I was thinking maybe it was the kernel so i made sure i was using the right kernel. i tried the whole process a few times but it didnt work. same problem. fone boots but doesnt register the touch. i even tried booting with flashing the gapps. so basically im stuck at the first screen. i had done a nandroid back up before and tried flashing that but that doesnt work either i guess because of the same reason.
Any help would be appreciated?
Thank you so much in advance
what hboot version do you have? There is an issue with the 2.14 hboot as HTC modified the firmware so the touchscreen drivers don't work for the older ICS or AOSP roms. If you have the 2.14 hboot, you'll need a JB sense ROM (like jokers or viperXL 3.1, or maybe Newts), check the forums themselves to see if they are compatible with the 2.14 hboot if you have it.\
If you don't have the newest hboot, maybe check the md5sum of the one you downloaded in case it is corrupted? If not try reflashing it, or flashing a different ROM and report back with results.
Good luck.
codeprimate said:
There is an issue with the 2.14 hboot
Click to expand...
Click to collapse
I hate that people are so hell bent on that this is a "2.14 hboot" issue.
2.14 hboot was just one of the many firmware updates pushed with 3.17 ROM's. I have not seen any knowledged person yet claim that the issue is actually in 2.14 hboot.
I believe if you revert your hboot with JET to 1.09 which you can do, the Touchscreen still does not work with incompatible kernels.
Which to me makes it pretty clear the issue is not in the hboot update at all but instead in one of the other updates.
twistedddx said:
I hate that people are so hell bent on that this is a "2.14 hboot" issue.
2.14 hboot was just one of the many firmware updates pushed with 3.17 ROM's. I have not seen any knowledged person yet claim that the issue is actually in 2.14 hboot.
I believe if you revert your hboot with JET to 1.09 which you can do, the Touchscreen still does not work with incompatible kernels.
Which to me makes it pretty clear the issue is not in the hboot update at all but instead in one of the other updates.
Click to expand...
Click to collapse
So in your opinion what is the solution i can try? Im not able to boot my phone so i cant really transfer any ROM zips to my phone. I have to use the bootloader or recovery to somehow get my phone back into workin order and then go from there. Thank you for your response
codeprimate said:
what hboot version do you have? There is an issue with the 2.14 hboot as HTC modified the firmware so the touchscreen drivers don't work for the older ICS or AOSP roms. If you have the 2.14 hboot, you'll need a JB sense ROM (like jokers or viperXL 3.1, or maybe Newts), check the forums themselves to see if they are compatible with the 2.14 hboot if you have it.\
If you don't have the newest hboot, maybe check the md5sum of the one you downloaded in case it is corrupted? If not try reflashing it, or flashing a different ROM and report back with results.
Good luck.
Click to expand...
Click to collapse
So i checked in the bootloader screen and i do have 2.14 hboot. so as the other person said i can downgrade my hboot using JET? and If im not mistaken you said that 2.14 may not be the latest hboot. If not where can i get the latest hboot. The other thing was since im not able to transfer any files to the phone.
Like twisted said you're going to have to flash a sense jb Rom right now go try viper.... Until the others update touch drivers to accommodate you people you have to use jb sense
marijuana king said:
Like twisted said you're going to have to flash a sense jb Rom right now go try viper.... Until the others update touch drivers to accommodate you people you have to use jb sense
Click to expand...
Click to collapse
ok so i downloaded jokers rom, and i was reading this link http://forum.xda-developers.com/showpost.php?p=32794132&postcount=7 to put the rom on my sd card. this link says they are using cwm recovery but i have read in many places that twrp should be used because it is officially supported for our devices. when i boot into recovery and try mount usb storage it doesnt show up on my computer as a flash drive. i have checked the drivers. im going to uninstall them and reinstall them, reboot my lappy and see if it recognizes the device. if you have any suggestions please throw them at me. at this time im looking for any straw that i can get to keep afloat.
anandsamuel said:
ok so i downloaded jokers rom, and i was reading this link http://forum.xda-developers.com/showpost.php?p=32794132&postcount=7 to put the rom on my sd card. this link says they are using cwm recovery but i have read in many places that twrp should be used because it is officially supported for our devices. when i boot into recovery and try mount usb storage it doesnt show up on my computer as a flash drive. i have checked the drivers. im going to uninstall them and reinstall them, reboot my lappy and see if it recognizes the device. if you have any suggestions please throw them at me. at this time im looking for any straw that i can get to keep afloat.
Click to expand...
Click to collapse
you should be able to flash that from TWRP instead of CWM without any dramas. if you can't see the device from your pc while it is booted into TWRP you can use "adb push C:\somepath\somefile /sdcard" to copy it onto your sdcard (you'll need the right version of the drivers and adb in your path). If you can't find the drivers or figure out anything let us know.
twistedddx said:
I hate that people are so hell bent on that this is a "2.14 hboot" issue.
2.14 hboot was just one of the many firmware updates pushed with 3.17 ROM's. I have not seen any knowledged person yet claim that the issue is actually in 2.14 hboot.
I believe if you revert your hboot with JET to 1.09 which you can do, the Touchscreen still does not work with incompatible kernels.
Which to me makes it pretty clear the issue is not in the hboot update at all but instead in one of the other updates.
Click to expand...
Click to collapse
You are right, it isn't the bootloader, it was the firmware upgrade pushed out alongside it, but it is a lot easier to check your hboot version from the bootloader than it is to check what software/firmware version you have, as the OP didn't list his software version, and had since blown it away with a new ROM, it seemed easier to check the firmware compatibility via the hboot version. I know strictly speaking the hboot isn't responsible for the touchscreen drivers, but they got the point quite quickly.
Update: so I was able to get my phone working I had to reinstall drivers on my computer restart the computer and then I was able to actually view my phone on my computer through TWRP and I transferred the ROM on to my phone and rebooted back into the bootloader flashed via boot image then went back to recovery and flash the ROM and everything is good to go now thank you all for your help this is an amazing phone
Sent from my HTC One XL using xda app-developers app
twistedddx said:
I hate that people are so hell bent on that this is a "2.14 hboot" issue.
2.14 hboot was just one of the many firmware updates pushed with 3.17 ROM's. I have not seen any knowledged person yet claim that the issue is actually in 2.14 hboot.
I believe if you revert your hboot with JET to 1.09 which you can do, the Touchscreen still does not work with incompatible kernels.
Which to me makes it pretty clear the issue is not in the hboot update at all but instead in one of the other updates.
Click to expand...
Click to collapse
Because it's the easiest way to identify that they are running the new firmware?
Yes. HTC went off and made some firmware updates to the touchscreen firmware.
We can't do anything about it until kernel source for the jellybean update is released.
Basically, if you took the new hboot EVER(since it updates the touchscreen firmware), that means you cant use AOSP Roms until we get source and can fix it in CM.
Aokp, pa, jellybam, kingkang, etc. All of those Roms use our kernel and device trees as a base. Once we get source and fix, they will update and everyone will be back in business.
The guys at TWRP were able to make recovery work because they just used the prebuilt stock kernel. On AOSP...we need source.
Sorry guys. Pester and scream at HTC to release JB source and that is the only way to help with this. Sorry to all of those that are affected....just know we are waiting impatiently as you are.
Sent from my Nexus 4 using xda app-developers app
h8rift said:
Yes. HTC went off and made some firmware updates to the touchscreen firmware.
We can't do anything about it until kernel source for the jellybean update is released.
Basically, if you took the new hboot EVER(since it updates the touchscreen firmware), that means you cant use AOSP Roms until we get source and can fix it in CM.
Aokp, pa, jellybam, kingkang, etc. All of those Roms use our kernel and device trees as a base. Once we get source and fix, they will update and everyone will be back in business.
The guys at TWRP were able to make recovery work because they just used the prebuilt stock kernel. On AOSP...we need source.
Sorry guys. Pester and scream at HTC to release JB source and that is the only way to help with this. Sorry to all of those that are affected....just know we are waiting impatiently as you are.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
lol, I've tried arguing with HTC's "support" for the source code, they are either extremely thick or deliberately obtuse. They kept telling me how to check if my carrier has released jellybean. I kept telling them that they are required under the GPL to release the source for the kernel along with any binaries.
I think the only way they'll release them in a timely fashion is if we get organised in a class action suit for violation of the GPL. It is for HTC's point blank refusal to meet it's legal requirement in a timely fashion that I refuse to ever buy another HTC device. I'll use this one for the term of my contract and then jump ship to a manufacturer that doesn't treat the open source community with contempt.
I don't mean to hijack this thread, but I'm facing a related issue.
I had rooted and unlocked my bootloader, hadn't yet installed any custom ROM. So today, without thinking, I install the OTA 4.1.1 update. Now of course I lost root, but even worse, when I boot in TWRP, my touchscreen is also unresponsive. I have the hboot 2.14.
I tried flashing TWRP again, but the same deal happens: the touchscreen won't register anything.
When you said that TWRP were able to make the recovery work, was this after the recent firmware update? Do I need a more recent version of TWRP (I'm using 2.3.3.1)?
I asked about this in the TWRP thread, but this seems closely related so I posted again here.
Edit- All is well, goo manager was installing 2.3.3.0 for some reason.
So as a n00b, I posted in the wrong forum earlier, lol
Anyways , long story short, htc one x evita, unlocked bootloader, tampered, rooted, will not flash past htc splash screen, when I try to restore, it does nothing, when going into folders there is NOTHING there, so random, I did clear my caches as instructed, maybe I am n00bish and deleted the wrong things, I can read the phone in adb, will go into teamwin screen,
REgardless, If I can get this fixed, I will not be messing with it again, lol(as all noobs say)
IS there anything I can do at this point before I throw my hands in the air and throw my phone at a wall?
Far from unique. It's possible that you've accidentally wiped the sd at some point, or did you possibly do a factory reset from the bootloader? Why haven't you just copied a ROM to the device to flash?
Sent from my Evita
timmaaa said:
Far from unique. It's possible that you've accidentally wiped the sd at some point, or did you possibly do a factory reset from the bootloader? Why haven't you just copied a ROM to the device to flash?
Sent from my Evita
Click to expand...
Click to collapse
HI, I may have wiped the sd, let's say sure to this..lol..
I have tried to copy a rom, I had Viper somewhat load, then it flashes back to htc splash, then to twrp,
Any insite to one that may possibly work?(the others will not load at all, they all fail install)
I need a bit more background on the device, please post your bootloader details (the first five lines). What TWRP version are you using? What had you done to the device directly before encountering this problem?
When you say you had Viper somewhat load what do you mean? Did it boot into the ROM at all? Or did it only boot as far as the Viper boot animation? Or did it only make it as far as the HTC splash screen?
I can't really say what's going to work until we figure out exactly what's wrong. Make sure you answer all the above questions with as much relevant detail as possible and we'll see if we can sort it out.
Sent from my Evita
timmaaa said:
I need a bit more background on the device, please post your bootloader details (the first five lines). What TWRP version are you using? What had you done to the device directly before encountering this problem?
When you say you had Viper somewhat load what do you mean? Did it boot into the ROM at all? Or did it only boot as far as the Viper boot animation? Or did it only make it as far as the HTC splash screen?
I can't really say what's going to work until we figure out exactly what's wrong. Make sure you answer all the above questions with as much relevant detail as possible and we'll see if we can sort it out.
Sent from my Evita
Click to expand...
Click to collapse
First off, thank you for your prompt replies
Venom loaded splash screen, then reboot to htc splash with the red developer on the bottom
twrp is the newest one
first 5 lines are you meaning?
*** TAMPERED ****
*** UNLOCKED ****
Evita put ship s-on rl
hboot-2.14.0000
radio-0.23a.32.09.29
??
Well I tried to load the stock RUU from rogers, (ota one)
then after rooting,unlocking bootloader, I tried to load a custom rom(slimkat IIRC)
then IT shut down, I left it for the night, and then nothing, so I tried to install slimkat again, nothing, so I tried venom, and I had the splash screen for the rom, now I am basically back at square one, nothing lol
Yes those are the bootloader details I needed. When you say the latest TWRP I'm assuming you mean 2.6.3.0? There are two versions of 2.6.3.0, the official version and the modified version.
Official version
Can flash any ROM except 4.4 ROMs. If you're using this one it is why SlimKat (plus any other 4.4 ROM) is failing to install.
Modified version
This is required to flash 4.4 ROMs. It does work on some pre 4.4 ROMs but it doesn't on others.
The most common cause for your current situation to happen is that you've forgotten to flash the boot.img with fastboot. Your phone is s-on, this means that the boot.img is unable to be flashed during the recovery install due to security restrictions on hboots equal to or greater than 1.14. So, make sure you're using the correct recovery for the ROM you want to flash (official 2.6.3.0 for Viper, modified 2.6.3.0 for 4.4 ROMs), and make sure you flash the boot.img with fastboot. I have detailed instructions on how to flash a boot.img in my How-To Guide For Beginners thread, link in my signature.
Do that and report back with how you go.
Sent from my Evita
timmaaa said:
Yes those are the bootloader details I needed. When you say the latest TWRP I'm assuming you mean 2.6.3.0? There are two versions of 2.6.3.0, the official version and the modified version.
Official version
Can flash any ROM except 4.4 ROMs. If you're using this one it is why SlimKat (plus any other 4.4 ROM) is failing to install.
Modified version
This is required to flash 4.4 ROMs. It does work on some pre 4.4 ROMs but it doesn't on others.
The most common cause for your current situation to happen is that you've forgotten to flash the boot.img with fastboot. Your phone is s-on, this means that the boot.img is unable to be flashed during the recovery install due to security restrictions on hboots equal to or greater than 1.14. So, make sure you're using the correct recovery for the ROM you want to flash (official 2.6.3.0 for Viper, modified 2.6.3.0 for 4.4 ROMs), and make sure you flash the boot.img with fastboot. I have detailed instructions on how to flash a boot.img in my How-To Guide For Beginners thread, link in my signature.
Do that and report back with how you go.
Sent from my Evita
Click to expand...
Click to collapse
Thank you so very much, once again with the quick replies and the "dumming" it down for me,
I will try in a little bit, to be honest, im not sure what twrp it is, I know its 2.3.6.0, it was the newest one,
in your instructions is there a way to boot just back to stock rom as well?(my pc is horrible, if I load more then one page it dies off lol) I will try this when I get home in a little bit herre.
I can almost positively say you're on the official version of TWRP, you'd need to go out of your way to find the modified one usually. With your phone in its current state you can't use an RUU to go back to stock. The latest Rogers RUU is older than your current firmware and you can't run an older RUU while s-on. If you made a TWRP backup of your stock ROM before wiping you could restore that backup though.
Your best and easiest option right now is to just flash a ROM. Once you've gotten a custom ROM booted up my guess is you won't want to go back to stock
Once you've gotten a ROM booted you can get s-off on your device which will make life a lot easier for you. It means no more flashing a boot.img, you'll be able to flash radios, you can run any Evita RUU (forwards or backwards, and from any carrier), and more benefits. But for now just concentrate on getting the ROM booting.
I'm assuming you have adb/fastboot installed on your PC already? If not you'll need to do that first, Google search "minimal adb and fastboot", the first result should take you to a thread that can get it done with very little effort.
Sent from my Evita
timmaaa said:
I can almost positively say you're on the official version of TWRP, you'd need to go out of your way to find the modified one usually. With your phone in its current state you can't use an RUU to go back to stock. The latest Rogers RUU is older than your current firmware and you can't run an older RUU while s-on. If you made a TWRP backup of your stock ROM before wiping you could restore that backup though.
Your best and easiest option right now is to just flash a ROM. Once you've gotten a custom ROM booted up my guess is you won't want to go back to stock
Once you've gotten a ROM booted you can get s-off on your device which will make life a lot easier for you. It means no more flashing a boot.img, you'll be able to flash radios, you can run any Evita RUU (forwards or backwards, and from any carrier), and more benefits. But for now just concentrate on getting the ROM booting.
I'm assuming you have adb/fastboot installed on your PC already? If not you'll need to do that first, Google search "minimal adb and fastboot", the first result should take you to a thread that can get it done with very little effort.
Sent from my Evita
Click to expand...
Click to collapse
Yes I have a basic Adb/fastboot setup already, is there a particular rom you recommend?(I will trust your best judgement here) I am home now, I will try and let you know
Thank you again
Asking for a ROM recommendation isn't allowed on XDA so I can't answer that question, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge.
Each user has different tastes anyway. Some people like Sense ROMs, some like aosp ROMs. Personally I'm an aosp guy, aosp ROMs are generally a bit snappier, plus you can run the latest version of Android (Sense ROMs are limited to 4.2.2 for our device). I'd suggest having a look at the ROMs on offer, check out their features and pick one to flash. If you don't end up liking it you can always just flash another, and that's half the fun.
As a side note, getting s-off via Rumrunner s-off seems to work better on Sense ROMs. I know someone very recently got s-off while on the Kickdroid ROM so if you do want to get s-off I'd suggest flashing that ROM purely for the s-off process. You might like it and want to stay on it, if not just flash away.
Sent from my Evita
timmaaa said:
Asking for a ROM recommendation isn't allowed on XDA so I can't answer that question, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge.
Each user has different tastes anyway. Some people like Sense ROMs, some like aosp ROMs. Personally I'm an aosp guy, aosp ROMs are generally a bit snappier, plus you can run the latest version of Android (Sense ROMs are limited to 4.2.2 for our device). I'd suggest having a look at the ROMs on offer, check out their features and pick one to flash. If you don't end up liking it you can always just flash another, and that's half the fun.
As a side note, getting s-off via Rumrunner s-off seems to work better on Sense ROMs. I know someone very recently got s-off while on the Kickdroid ROM so if you do want to get s-off I'd suggest flashing that ROM purely for the s-off process. You might like it and want to stay on it, if not just flash away.
Sent from my Evita
Click to expand...
Click to collapse
I understand and apologize, Never thought of it that way,
Anyways an update, I followed your tutorial, and I am not having much luck here, It still maintains to say NO OS installed (through twrp when rebooting after I do adb and such)
maybe I am missing something ?
Adb or fastboot?
Sent from my Evita
timmaaa said:
Adb or fastboot?
Sent from my Evita
Click to expand...
Click to collapse
Fastboot,
Small update I did manage to get a rootbox rom to load, but its not stable by anymeans...Ugh super frustrated with it
Are you wiping in TWRP before flashing? It's very important to wipe system/factory reset/cache/dalvik cache before installing a ROM. Just never do a factory reset in the bootloader, that'll corrupt your sd card.
Sent from my Evita
timmaaa said:
Are you wiping in TWRP before flashing? It's very important to wipe system/factory reset/cache/dalvik cache before installing a ROM. Just never do a factory reset in the bootloader, that'll corrupt your sd card.
Sent from my Evita
Click to expand...
Click to collapse
Yes to wiping before flashing in TWRP just those ones mentioned, (if you do sd you loose your flash right?), anyways the rom I flashed yesterday was super unstable, just trying a few diff. ones out and trying to find one that will continue to stay working lol!! Your tutorial in your signature is very helpful
thank you so much for all your help,and patience
Yeah you don't want to wipe sd card/internal storage or you'll lose all of your personal data like images, music, ROM zips, backups.
Sent from my Evita
timmaaa said:
Yeah you don't want to wipe sd card/internal storage or you'll lose all of your personal data like images, music, ROM zips, backups.
Sent from my Evita
Click to expand...
Click to collapse
Oh this is a clean phone, I already backed up on pc Before lol
Question though, I installed Viper again(just to try it) and it loads a menu showing ram, one of the memory sections shows -1? is this correct?
On a side note, I got Venom up and running and WOW!!!
once again, a super thank you for your patience and help all along Timmaaa,
I'm not sure what you're talking about, is that after booting into the ROM? Can you show me a screenshot?
Sent from my Evita
timmaaa said:
I'm not sure what you're talking about, is that after booting into the ROM? Can you show me a screenshot?
Sent from my Evita
Click to expand...
Click to collapse
it was while I was installing, everything seems fine, still no wifi(original issue)
im thinking the logic board may be buggered...sad day...lol
But, it is fast as heck now, running venom rom, I will try to get S-off and then maybe try to get it so I can load up the 4.4X roms
Thanks for all the help
Hi please could i ask for some help regarding what roms can be flashed after s-offing via the Revolutionary method.
I have searched to the point of falling asleep and waking with key imprints on my face! After my searching im still slightly unclear about what i can and cant do without further modding
Im pretty sure that i can flash any custom rom i want but nothing should ever be assumed when flashing phones, thats how paperweights are made!
I had to downdrade the H-boot And did so using zergrush and old stock rom - http://forum.xda-developers.com/showthread.php?t=1399331
my device was branded so i used a branded rom in the downgrade as stated and so still have branding.
im pretty sure that now im s-off unlcoked that removing branding before flashing custom is not a issue but again, never assume!
bootloader screen infor is now as follows-
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-38.03.02.15_M
eMMC-boot
Mar 10 2011,14:58:38
Revolutionary Clockwork Mod v4.0.1.4 is flashed to recovery,
I dont think at this stage the device is rooted, thats done with the Superuser-3.0.7-efgh-signed file i have i beleive but have to read more on how its installed, can root be also gained directly though custom roms?
Also, on ben_pyett's index page- http://forum.xda-developers.com/showthread.php?t=1146601 he suggests that a different h-boot is installed after doing the revolutionary mod to avoid probelms later on-
ben_pyett;15187889
[B said:
It is recommended that after unlocking your device with Revolutionary you install an ENG bootloader, so that you can easily upgrade and downgrade your bootloader if required in the future - not doing so can lead to difficulties.[/B]
:
Click to expand...
Click to collapse
is this importaint and can anyone explain why this should be done please?
with what i have told you please can someone let me know anything further i nedd to do before flashing a custom rom or can i go right ahead and flash?
the last question i have is theres a tonne of ICS roms out there but also a few jelly bean ones too, ICS seems to be more popular by far, is there a reason for this and should i avoid the newer Jellybean roms?
Thanks, thanks and thanks again in advance for your help,
Steve.
I would recommend you install the hboot from this thread :
http://forum.xda-developers.com/showthread.php?t=1679338
It has a new partition layout that is compatible with every rom out there. I use that version. There have also been reports of the revolutionary hboot having problems formatting partitions sometimes.
Almost all custom roms are rooted, so if you're planning to install one, you don't need to flash superuser first.
I would also update your recovery, to either the latest 4ext touch, or twrp. They support every rom out there including the kit-kat ones.
There are more ics roms there because of the age of the device and because HTC never released anything past ics for it. But if you look which threads are still active, you'll see that there's really only development still going on for the kit-kat roms (flinny's Andromadus and devil-kins builds). I'm using those and would recommend trying them (as long as you have a Sony panel, if not you'll have problems on any thing past ics).
Sent from my GT-P5110 using XDA Premium 4 mobile app
teadrinker said:
I would recommend you install the hboot from this thread :
http://forum.xda-developers.com/showthread.php?t=1679338
It has a new partition layout that is compatible with every rom out there. I use that version. There have also been reports of the revolutionary hboot having problems formatting partitions sometimes.
Almost all custom roms are rooted, so if you're planning to install one, you don't need to flash superuser first.
I would also update your recovery, to either the latest 4ext touch, or twrp. They support every rom out there including the kit-kat ones.
There are more ics roms there because of the age of the device and because HTC never released anything past ics for it. But if you look which threads are still active, you'll see that there's really only development still going on for the kit-kat roms (flinny's Andromadus and devil-kins builds). I'm using those and would recommend trying them (as long as you have a Sony panel, if not you'll have problems on any thing past ics).
Sent from my GT-P5110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thanks for your help, i will take your advice on the h-boot and recovery, ive flshed tonnes of win mob handsets and a couple of win phone 7's even with downgrading and rooting on the win phone handsets it was so much less complex and confuising than andriod!
what do you mean by sony panel? do you mean the display? is it some kind of driver issue or am i on the wrong path here?
thanks steve.
About the display panel type, check this thread :
http://forum.xda-developers.com/showthread.php?t=1943524
Sent from my GT-P5110 using XDA Premium 4 mobile app
teadrinker said:
About the display panel type, check this thread :
http://forum.xda-developers.com/showthread.php?t=1943524
Sent from my GT-P5110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the info, i have checked and its Sony!
I changed the Hboot to the version you suggested and i have changed the recovery to twrp, i was going to install 4ext but its £2 and annoyingly google play store does not accept paypal and i dont have a credit or debit card, only my wife and she does not want it linked to my play account grrr.
Anyway, now i have to choose a JB rom to install, flinny's Andromadus rom seems to be very much still in the alpha stage and i want a rom that is as stable as possible, i will have a look at the devil kins rom in a sec.
Anyway, thanks again for your help, i will hit the thanks button.
Steve.
steve_htc_wizard said:
Thanks for the info, i have checked and its Sony!
I changed the Hboot to the version you suggested and i have changed the recovery to twrp, i was going to install 4ext but its £2 and annoyingly google play store does not accept paypal and i dont have a credit or debit card, only my wife and she does not want it linked to my play account grrr.
Anyway, now i have to choose a JB rom to install, flinny's Andromadus rom seems to be very much still in the alpha stage and i want a rom that is as stable as possible, i will have a look at the devil kins rom in a sec.
Anyway, thanks again for your help, i will hit the thanks button.
Steve.
Click to expand...
Click to collapse
4ext recovery is free... Only the control app u have to pay for, has more option. Anyway Download the free updater app and use that to flash recovery. Link below.
http://4ext.net/
Or click link below, follow instructions. Or extract the zip file and flash recovery.img via fastboot commands
http://forum.xda-developers.com/showthread.php?t=2275946
jmcclue said:
4ext recovery is free... Only the control app u have to pay for, has more option. Anyway Download the free updater app and use that to flash recovery. Link below.
http://4ext.net/
Or click link below, follow instructions. Or extract the zip file and flash recovery.img via fastboot commands
http://forum.xda-developers.com/showthread.php?t=2275946
Click to expand...
Click to collapse
TWRP was miles better than the outdated revolutionary recovery but wow, the 4ext recovery you directed me too is tonnes better again, thanks!
One problem im having though and had it with the TWRP recovery too-
I managed to flash a ics rom to the phone, i did this as i found one i that looked very stable from the user comments in the topic and it granted me the root i needed to install the new recovery and various other bits via the o.s but now although the rom is showing now bugs i want to jump to JB as that was always my goal if it could be done.
but both the roms i have downloaded to try come up with a signing error in both TWRP and 4EXT recoverys, i don't know enough to brave turning off the signing check (guessing this may be the solution) and so can't install these roms at the moment. I really like the look of the carbon JB rom but almost every post talks about lag so im giving that one a miss.
please can you explain what is preventing me from installing these roms?
The ICS rom i installed flashed with no problems at all using the revolutionary recovery but i don't know if there was a setting that was not active or even a lack of it altogether in that particular recovery.
The other question is which flinny's Andromadus JB rom version is recomended? There's so many versions but all "test" roms and no official versions, do you know of a particular one that has the most functionality and stability?
Thanks again for pointing me to the 4ext link, its miles better.
Steve.
EDIT: I have just re-flashed the phone with the same "RTS" ICS rom using the new 4EXT recovery as having done a full wipe in preperation for the new rom i lost a lot of things that were backed up using the previous recovery and did not get the signing error so now im sure its a rom thing rather than a recovery setting
after installing maximus hd on m htc one s I have only 2gb of available space for my pictures/music etc. what Have I done and how do i fix it to give me more available space?
Thanks
arinb12 said:
after installing maximus hd on m htc one s I have only 2gb of available space for my pictures/music etc. what Have I done and how do i fix it to give me more available space?
Thanks
Click to expand...
Click to collapse
Or any other rom I can install without this problem. Im handing the phone over to my mum who doesnt care as long as there is space and it works
Or any other rom I can install without this problem. Im handing the phone over to my mum who doesnt care as long as there is space and it works.
Only interested in battery life and useablility not fussed by sense 5 etc
Did you flash the firmware and the modfied TWRP, that are required to run MaximusHD?
Flippy498 said:
Did you flash the firmware and the modfied TWRP, that are required to run MaximusHD?
Click to expand...
Click to collapse
cant recall, this was a while back - the phone went into storage since then.
how can i find out?
arinb12 said:
cant recall, this was a while back - the phone went into storage since then.
how can i find out?
Click to expand...
Click to collapse
twrp is installed though.
If you flashed the required firmware your hboot version should be 2.16. Just boot into bootloader to find out which version you're using.
And the correct TWRP version is either the modified version 2.6.1 you can download from the MaxismusHD thread or the modified version you can find in this thread. Look at post #3 to find what you're looking for.
2.15
all i want is my storage back and for it to remain unlocked for all sims,
can i just re install stock rom and keep the simlock unlocked
dont care for options or tweaks.
arinb12 said:
2.15
all i want is my storage back and for it to remain unlocked for all sims,
can i just re install stock rom and keep the simlock unlocked
dont care for options or tweaks.
Click to expand...
Click to collapse
If you want to install MaximusHD you will have to follow the install instructions in the OP of the thread and this will upgrade your hboot version to 2.16 and install TWRP 2.6.1.0. Then your phone will show the correct amount of storage. Word of warning, some people have had problems with in call quality on 4.2.2 sense rom's, it seems to affect some phones more than others. If you don't want to do this, you can install Viper which is also 4.2.2 and keep hboot 2.15. Or you can use and RUU to go back to stock, your phone will stay sim unlocked but the latest official version is android 4.1. The RUU files are here, you can also use this unofficial RUU based on 4.2.2.
thanks for everyones help.
installed viper and rectified storage.
Hi folks
REALLY hoping somoene can help.
I have an HTC ons S (S4) which ive is rooted, Bootloader off, s-off, superCID 11111111.
I used TWRP to wipe data/cache/dalvik and installed Maximus HD rom.
Everything seemed fine until I checked storage on phone and I only had 2gb (should be 16gb...minus OS ofc)
So went back to TWRP, wiped, reinstalled and it asked me if i wanted to wipe (i think it was storage) and since there was nothing I really
needed on the phone i chose yes this time hoping it would fix storage size encounted first time (and opting not to wipe)
It did actually fix storage...its now back to full, I can see phone storage on PC, add / remove files from it...BUT!! now when i go
into TWRP it says:
Storage: Internal Storage (0 MB)
and I cannot see my files....I just see an empty TWRP folder and if jump up a folder I get
and-sec
boot
cache
data
dev
devlog
etc
internal_sd
license
proc
recovery
res
root
sbin
supersu
sys
system
tmp
usb-otg
but ALL these folders appear to be empty (
Ive checked ive got latest version of TWRP, tried an older version, tried clockwork recovery instead, but none of the recoverys will show
my storage (yet its fine on PC)
If anyone maybe knows how to fix the storage issue, id be extremely grateful for any help )
(hopefully without having to go back to stock...I had major nutache getting s-off, supercid etc done lol)
Thanks,
CUS.
I had a problem like this. I had to re-install the stock recovery, then run it and it fixed my problem. Others say you need to reset factory from the stock recovery.
In any case check this out - it's probably the same issue:
http://forum.xda-developers.com/showthread.php?t=1630459
Thanks for the reply 808phone
I tried what you advised...Now in TWRP it is showing internal storage 48mb!.....better than zero but still not right.
Would you happen to have any other ideas?
Thanks,
CUS.
CUSXDA said:
Thanks for the reply 808phone
I tried what you advised...Now in TWRP it is showing internal storage 48mb!.....better than zero but still not right.
Would you happen to have any other ideas?
Thanks,
CUS.
Click to expand...
Click to collapse
That's because you used the wrong recovery for 2.16 hboot. You shouldn't use a 2.15 recovery with 2.16 hboot
All the official TWRP builds are for 2.15 hboot and Maximus is a ROM for 2.16.
Sent from nowhere over the air...
Oooh thanks for the reply Rapier!
I really like the maximus rom and would like to stick to it for the time being... if I were to re-install with a different custom recovery like clockwork
(could you suggest one please? ) , do you think this may fix the issue or have a screwed things up using TWRP to install maximus?
CUSXDA said:
Oooh thanks for the reply Rapier!
I really like the maximus rom and would like to stick to it for the time being... if I were to re-install with a different custom recovery like clockwork
(could you suggest one please? ) , do you think this may fix the issue or have a screwed things up using TWRP to install maximus?
Click to expand...
Click to collapse
Best way to do it is by using the recovery linked in MaximusHD thread (in OP). Most 2.16 ROMs have a link to the proper recovery in their OP
Edit: I've checked MaximusHD thread, if you follow the installation instructions closely you'll notice that is a "install_package.rar" mentioned. The one that contains the 2.16 firmware AND the recovery. Use that one. Alternatively you can use a 2.16 recovery from other ROMs built for 2.16 like the unofficial CM11 or the Liberty or SixthSense ROMs by bilal_liberty. Any of those should be good to go with MaximusHD as well
Sent from nowhere over the air...
Thanks for the reply Rapier
...Thats actually the recovery that I used...the package contains TWRP but it was an older version so I did replace it with the latest version.
I think the problem is this (I know, I messed up )
I followed install instructions on maximus page as instructed...during install it asked if i wanted to wipe storage
(it might of said SD card, i cant remember) so I chose NO.
On completion when I plugged phone into PC to transfer files onto it, it only had 2GB storage
So I did a complete install again following install procedure from beginning on Maximus page, but this time when it asked if I wanted to wipe storage I chose YES (I didnt have anything i needed on it)
Now when I plug into PC I see the full 16gb and can add/delete files, but if I boot into recovery (either using TWRP or clockwork) I only see 48mb
so I cant backup, install other roms or anything
Would you have any more suggestions buddy?
....OMG, fixed it!. :laugh:
The ONE thing that screwed the install was ME trying to be good and keep everything updated to the lastest version!
Turns out the TWRP in the install package is actually a MODIFIED version especially for Maximus HD!
and using the latest (or a different) version gives you either the 0mb or 48mb issue!.
Thank you so much for the help that put me on the right track....after reading post after post, i finally spotted one that mentioned
it is a "modified" recovery!.
CUSXDA said:
....OMG, fixed it!. :laugh:
The ONE thing that screwed the install was ME trying to be good and keep everything updated to the lastest version!
Turns out the TWRP in the install package is actually a MODIFIED version especially for Maximus HD!
and using the latest (or a different) version gives you either the 0mb or 48mb issue!.
Thank you so much for the help that put me on the right track....after reading post after post, i finally spotted one that mentioned
it is a "modified" recovery!.
Click to expand...
Click to collapse
Yes, this is exactly what I've told you in my first post...you're using the wrong recovery for 2.16 hboot. You can still have the latest, there's a thread called "Unofficial TWRP..." and there you can find TWRP 2.7.1.0a-dm that is used by many for 2.16 hboot. I used it myself with SixthSense Liberty ROM and it's working
Sent from nowhere over the air...
Yes I see now, I did mis-read your post, I do apologize...
"That's because you used the wrong recovery for 2.16 hboot. You shouldn't use a 2.15 recovery with 2.16 hboot
All the official TWRP builds are for 2.15 hboot and Maximus is a ROM for 2.16. "
I unfortunately read that as TWRP will not work, I need a recovery that is for 2.16 (my bad)
"Maybe" would of been a little clearer to mention "Install package has a modified TWRP, use that "
It doesn't take much to confuse me I'm afraid.....I'm a total newbie to all this so have a hell of a lot to learn hehe
and having been trying to sort this for 2 days & nights, my brain was TOTALLY fried!
...Updated to twrp-2.7.1.0a-ville-dm as suggested...all working great!
Many thanks for all your help Rapier!....I honestly do REALLY appreciate it :good: