Related
Hi, I have a VilleC2 version of HTC One S from Virgin Australia which I have rooted with a custom TWRP recovery. An OTA update came out today, but it would not update, instead booting into TWRP every time. Does anyone have the stock RUU or just the recovery image so I can flash it? I lost mine :crying:
Going to point out there's no version-main for some reason. Not sure what to do. I noticed the OTA update was called:
OTA_VILLEC2_U_JB_45_S_Optus_AU_3.19.980.101_16.22.20.03U_16.11.20.24_M_release_310845116mwbfmhbdc886n
(bootloader) version-main:
(bootloader) product: villec2
(bootloader) cidnum: OPTUS001
(bootloader) security: on
Android Version: 4.0.3
HTC Sense Version: 4.0
Software Number: 1.11.980.120
Got it, sorry lol.
someoneusedmyid said:
Hi, I have a VilleC2 version of HTC One S from Virgin Australia which I have rooted with a custom TWRP recovery. An OTA update came out today, but it would not update, instead booting into TWRP every time. Does anyone have the stock RUU or just the recovery image so I can flash it? I lost mine :crying:
Going to point out there's no version-main for some reason. Not sure what to do. I noticed the OTA update was called:
OTA_VILLEC2_U_JB_45_S_Optus_AU_3.19.980.101_16.22.20.03U_16.11.20.24_M_release_310845116mwbfmhbdc886n
(bootloader) version-main:
(bootloader) product: villec2
(bootloader) cidnum: OPTUS001
(bootloader) security: on
Android Version: 4.0.3
HTC Sense Version: 4.0
Software Number: 1.11.980.120
Click to expand...
Click to collapse
can u upload the ruu if pos or put up here about how u did it plz? thx in advance
Can you please give us a link to the optus RUU/OTA that you found,
Thanks
Ok, I'll start from the beginning.
I purchased my phone from Rogers at April 2012. So it was Rogers stock 4.0.x rom, everything was locked at that time. I FORGOT the stock hboot/ruu version number for Rogers ONE XL.
From the time being, I rooted it, superCID, unlocked via HTC DEV. After these, I flashed customer recovery, and successfully flashed several roms from time being. Finally I stayed with ViperXL.
Then, facepalm s-off is released, and I s-offed my phone. Everything worked just fine.
The problem occurred when I started to flash sense 5 roms about couple weeks ago. I did not upgrade my firmware and I flashed sense 5 based roms (this is my bad), so I'm experiencing random reboot and signal drops. Then I upgraded my firmware using the instruction in this tread: http://forum.xda-developers.com/showthread.php?t=2423735 . I verified my installtion with ./fastboot gervar all . At this time, there were two warnings on the top of my bootloader: "tampered" and "unlocked".
So, at this time, I tried several sense 5 roms. My recovery at this time was TWRP 2.6.3.0. All the roms have one common problem on my phone: after I locked the screen and left my phone for a while, if I wanna wake my phone/display, nothing happened by pressing the power button. I have to press the power button for 10+ seconds to restart my phone. If I just left my phone for a short time and wake it, it will work properly.
I was thinking are these sense 5 problems, so I tried to flash cm roms yesterday. I followed the instructions in http://forum.xda-developers.com/showthread.php?t=2382933 to upgrade my RUU to 3.18. I flashed TWRP 2.6.3.0, and tried to flash cm 10.1 and 10.2. For cm 10.2, there were a lot of force close when I boot my phone. For cm 10.1, it is so unstable with random reboots as well as did not respond when I try to wake up the phone. I am not questioning CM's roms, I am sure there were something wrong with my phone or what I've done to it.
So, I tried to flash viper rom again with ruu 3.18 installed. The rom won't even boot...... However I found something interesting when I am flashing the viper rom. The size of ViperXL is 700+ MB while the size of CM 10.1 or 10.2 is around 180MB. The time it took to flash ViperXL was shorter than the time it took to flash CM roms.
Then I re-installed the RUU 3.18 update on my phone. Right now, the AT&T stock rom also will not respond after I left my phone idle for a moment......
User timmaaa kindly reminds me about something. I am posting the original post I started in another tread.
Originally Posted by snake3276120 View Post
After I ran the RUU 3.18 upgrade in this tread: http://forum.xda-developers.com/show....php?t=2382933
I boot into bootloader, and ran fastboot getvar all, the result is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT246W304864
(bootloader) imei: 359691041684351
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4122mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
I'm assuming "(bootloader) version-main: 3.18.502.6" is the RUU version. I also flashed an hboot 2.14, it became 3.17.xxxxxxx. That'w why I am assuming this is the RUU number.
Ok, regardless of the build number or ruu...... I think there is something wrong with my bootloader. It doesn't matter which hboot I flash (hboot 2.14 with version-main 3.17/3.18, or hboot 2.15 with version-main 5.08), and I tried several twrp (2.4.4.0 and 2.6.3.0). The time it took to flash viper xl is really short while viper xl has 700MB. It is even shorter than the time I flash CM, which is around 180 MB. (Sorry for the bad English, I actually mean "The size of ViperXL is 700+ MB while the size of CM 10.1 or 10.2 is around 180MB. The time it took to flash ViperXL was shorter than the time it took to flash CM roms.")
I guess I'll start with the current AT&T stock rom (which still lose respond after I left the phone open for a while, and I have to press the power button for 10 secs to reset my phone)on hboot 2.14 and ruu 3.18. Root it, try to s-off again. Not sure if this will solve the problem.
Something interesting when I'm booting my phone, when the phone displays only the green HTC in the middle of the display, there is some text below it... saying something like "This is an internal build, do not distribute outside of HTC, failure may cause to law action". However, the AT&T stock rom I'm running right now does not have this.
timmaaa:
It's a bit hard to follow what you're saying there but here goes. It's not the RUU number it's the build number. An RUU is the program that updates your phone, the reason you see them referred to as the 3.18 RUU is because they're known by the build number that they update your phone to.
Did you check the md5 of the downloaded file as someone else suggested? It might be corrupt. Also, maybe you should try TWRP 2.6, versions 2.4.x and 2.5.x are well known as being very buggy, and I've seen people have issues with version 2.6.3 too. 2.6 is rock solid though.
The red text you see when the phone boots up is completely normal for a modified phone so you needn't worry about that. The reason the stock ROM doesn't have it is because the RUU has returned your phone to being completely stock, therefore not modified, therefore no red text.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
OK, I am wondering where I can get my RUU number......
Also, in this case, what I should do now? Install TWRP 2.6.0.0 and try to flash everything again?
Currently "tampered" is gone from my bootloader, only "unlocked" stays there.
Lol you've kinda mashed my quote in with your post there so it's hard for people to see where they begin and end.
What do you mean you want to get your RUU number? Like I said an RUU is a program, what exactly do you mean?
Sent from my Evita
timmaaa said:
Lol you've kinda mashed my quote in with your post there so it's hard for people to see where they begin and end.
What do you mean you want to get your RUU number? Like I said an RUU is a program, what exactly do you mean?
Sent from my Evita
Click to expand...
Click to collapse
Because some posts are saying RUU 3.17 or 3.18, so I got confused...... but as long as it's a program, I will assume they are talking about the firmware or bootloader after running RUU 3.17 or 3.18 upgrade.
timmaaa said:
Lol you've kinda mashed my quote in with your post there so it's hard for people to see where they begin and end.
What do you mean you want to get your RUU number? Like I said an RUU is a program, what exactly do you mean?
Sent from my Evita
Click to expand...
Click to collapse
I fixed the qoute
Just to be clear, after you ran the 3.18 RUU you booted the phone without making any modifications and the problem was still occurring, right? It seems to me that it might be some kind of hardware problem that's causing a sleep of death every time the phone goes into sleep mode.
Sent from my Evita
timmaaa said:
Just to be clear, after you ran the 3.18 RUU you booted the phone without making any modifications and the problem was still occurring, right? It seems to me that it might be some kind of hardware problem that's causing a sleep of death every time the phone goes into sleep mode.
Sent from my Evita
Click to expand...
Click to collapse
That's right, I didn't even flash recovery... Well, my stock rom just self-rebooted, and stuck at booting animation while adb is still able to recognize it, and I can issue a reboot from adb. This also applies to my sense 5 roms.
If it's hardware problem, looks like upgrading to hboot 2.15 ruined my hardware, which is hard to believe...... Everything works fine before I upgrade my hboot to 2.15
Unfortunately it isn't under warranty anymore either.
Sent from my Evita
timmaaa said:
Unfortunately it isn't under warranty anymore either.
Sent from my Evita
Click to expand...
Click to collapse
I know... it is unfortunate...
timmaaa said:
Unfortunately it isn't under warranty anymore either.
Sent from my Evita
Click to expand...
Click to collapse
I upgraded my hboot to 2.15 and I flashed MaginRom 4.0. At least it's booting...... looks like my recovery hates aroma installer.
snake3276120 said:
I upgraded my hboot to 2.15 and I flashed MaginRom 4.0. At least it's booting...... looks like my recovery hates aroma installer.
Click to expand...
Click to collapse
Confirm your hboot and baseband version and post here. You said it upgraded, but let's make sure it actually was completely successful.
Also, I think TWRP 2.6.3 has some bugs, not sure if AROMA is one of them. You might check the TWRP thread. But I believe other 2.6.x versions are very stable. I've been on 2.6.0 for a while, and everything seems to be working great, and don't remember any bug reports on that version.
Yeah I can confirm I've seen folks with bugs on 2.6.3 but I've been using 2.6 for months and not a single problem (and no reports of bugs from others).
Sent from my Evita
timmaaa said:
Yeah I can confirm I've seen folks with bugs on 2.6.3 but I've been using 2.6 for months and not a single problem (and no reports of bugs from others).
Sent from my Evita
Click to expand...
Click to collapse
I used 2.6.0.0 to flash my current magiorom 4..... well at least it is usable now, with app/sense/notification bar/wake phone do not respond sometimes... I'm not blaming the rom, I am blaming my phone... probably now it's the time to get a new one lol
redpoint73 said:
Confirm your hboot and baseband version and post here. You said it upgraded, but let's make sure it actually was completely successful.
Also, I think TWRP 2.6.3 has some bugs, not sure if AROMA is one of them. You might check the TWRP thread. But I believe other 2.6.x versions are very stable. I've been on 2.6.0 for a while, and everything seems to be working great, and don't remember any bug reports on that version.
Click to expand...
Click to collapse
Here you are, boss.
PS E:\Program Files (x86)> cd '.\Minimal ADB and Fastboot'
PS E:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3874mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
PS E:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
I think the result is the same in thread http://forum.xda-developers.com/showthread.php?t=2423735
Quoted from the thread:
Install:
Installing the rom:
Download the rom and copy to your sdcard
Reboot to Recovery
Flash rom
I recommend you wipe data before or after flashing the rom
For root access, flash this: Flash this in recovery for root access
Reboot
OPTIONAL: Installing the Firmware (Warning: You MUST be S-OFF and Super CID to flash this! Flash at own risk!)
Reboot to bootloader (adb reboot bootloader if "USB Debugging" is enabled in Android)
Run: fastboot oem rebootRUU
Run: fastboot flash zip <PathToFirmware.zip>
If the output ends with "FAILED (remote: 90 hboot pre-update! please flush image again immediately)", run the previous command AGAIN
If it ends with "INFO..... OK", reboot to the bootloader: fastboot reboot-bootloader
Verify everything was successful by running: fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4140mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Reboot into Android: fastboot reboot or into recovery: fastboot reboot-recovery
Click to expand...
Click to collapse
Please refer to the attachment for a photo of my bootloader
Will TWRP 2.3.3.0 solve my problem? It looks like most roms recommend this recovery.... btw I'm running 2.6.0.0 at the moment.
No, changing TWRP won't solve your problem. You said you're using TWRP 2.6 now and that version is fine. I'd suggest trying one more time to do a clean flash, so wipe cache/dalvik cache/factory reset/system and install the ROM. Hell, do the wipe two or three times to be sure before installing.
Sent from my Evita
timmaaa said:
No, changing TWRP won't solve your problem. You said you're using TWRP 2.6 now and that version is fine. I'd suggest trying one more time to do a clean flash, so wipe cache/dalvik cache/factory reset/system and install the ROM. Hell, do the wipe two or three times to be sure before installing.
Sent from my Evita
Click to expand...
Click to collapse
lol thanks... Every time before I flash a new rom, I just format everything...
I don't know what to tell you then. There's nothing wrong with the ROMs you're using so it's either a case of user error or hardware failure of some kind.
Sent from my Evita
timmaaa said:
I don't know what to tell you then. There's nothing wrong with the ROMs you're using so it's either a case of user error or hardware failure of some kind.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for all the help... I think it is hardware error... because I'm an electrical/computer engineer, I don't think I can't even handle flashing roms... Maybe I need to do more research lol
One XL is a nice phone, I don't wanna switch yet...
snake3276120 said:
Thanks for all the help... I think it is hardware error... because I'm an electrical/computer engineer, I don't think I can't even handle flashing roms... Maybe I need to do more research lol
One XL is a nice phone, I don't wanna switch yet...
Click to expand...
Click to collapse
Could you also try one last thing? Could you upgrade your twrp to latest release and try flashing cm 10.2 0310 nightly please.
Sent from my One X using Tapatalk 4
sandys1 said:
Could you also try one last thing? Could you upgrade your twrp to latest release and try flashing cm 10.2 0310 nightly please.
Sent from my One X using Tapatalk 4
Click to expand...
Click to collapse
Ok I'll do a backup and try tonight....latest twrp do u mean 2.6.3.0, or there is another new release?
Hey guys.
I wanted to root my HTC One S, and I read that the program SuperOneClick was the fastest way of doing it, so I went ahead and connected the HTC to my PC with the USB cable and clicked "root". After like 15 minutes however the program didn't do anything, it just froze and I had to close it. Root Checker Basic said something similiar to no valid root or something. Tried to click "unroot" now so I could start again with a different method, froze again, closed SuperOneClick again. What am I supposed to do now? Is rooting it again safe as I now probably have some half / corrupted root? And can someone link me to the best method? Thanks in advance.
CrackedHippo said:
Hey guys.
I wanted to root my HTC One S, and I read that the program SuperOneClick was the fastest way of doing it, so I went ahead and connected the HTC to my PC with the USB cable and clicked "root". After like 15 minutes however the program didn't do anything, it just froze and I had to close it. Root Checker Basic said something similiar to no valid root or something. Tried to click "unroot" now so I could start again with a different method, froze again, closed SuperOneClick again. What am I supposed to do now? Is rooting it again safe as I now probably have some half / corrupted root? And can someone link me to the best method? Thanks in advance.
Click to expand...
Click to collapse
One-click-roots are not suggested...
Did you unlock the bootloader?
Just unlocked the bootloader and flashed cwm, my own fault for using superoneclick. Thanks anyway ;p
Sorry for the double post. I may need some help as I probably bricked(?) my One S.
Didn't do anything root-related for a long time so I think I made a beginner's mistake.
What I did was unlock (htcDEV), and flash CWM recovery.
I tried installing liquid kitkat custom rom, but now it won't boot, not even in recovery.
Help?
EDIT: It's stuck in a boot loop :/
CrackedHippo said:
Sorry for the double post. I may need some help as I probably bricked(?) my One S.
Didn't do anything root-related for a long time so I think I made a beginner's mistake.
What I did was unlock (htcDEV), and flash CWM recovery.
I tried installing liquid kitkat custom rom, but now it won't boot, not even in recovery.
Help?
EDIT: It's stuck in a boot loop :/
Click to expand...
Click to collapse
Press Power button for 10secs+ to power off
Can you enter fastboot? Is your phone S4 ville or s3 villeC2?
LS.xD said:
Press Power button for 10secs+ to power off
Can you enter fastboot? Is your phone S4 ville or s3 villeC2?
Click to expand...
Click to collapse
I finally managed to enter recovery / fastboot.
Sorry for the foolish comment but I actually have no idea if it's S4 or S3, how do I find out?
Also what should I do right now? Flash stock rom on it or..?
CrackedHippo said:
I finally managed to enter recovery / fastboot.
Sorry for the foolish comment but I actually have no idea if it's S4 or S3, how do I find out?
Also what should I do right now? Flash stock rom on it or..?
Click to expand...
Click to collapse
FIRST you need to know which phone / firmware you got.
Enter fastboot, connect to pc, open CMD and type "fastboot getvar all"
Copy the log and post it here please. Delete IMEI/serial before you post the log. Then i can exactly tell you what you need to install
LS.xD said:
FIRST you need to know which phone / firmware you got.
Enter fastboot, connect to pc, open CMD and type "fastboot getvar all"
Copy the log and post it here please. Delete IMEI/serial before you post the log. Then i can exactly tell you what you need to install
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.15.50.05.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***
(bootloader) imei: ***
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 3810mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Here you go, thanks in advance!
CrackedHippo said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.15.50.05.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***
(bootloader) imei: ***
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 3810mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Here you go, thanks in advance!
Click to expand...
Click to collapse
HTC One S - S4 ville - generic dutch version
You will just need to flash the kernel contained in the rom (boot.img) via fastboot (S-ON means u need to flash kernel manually) to fix your installation
Generally I'd suggest
Flash this recovery via fastboot --> TWRP 2.7.0.8
(its compatible to the lastest CM11 versions 05/01/2014 and newer
And may be try PAC rom (I just love it)
LS.xD said:
HTC One S - S4 ville - generic dutch version
You will just need to flash the kernel contained in the rom (boot.img) via fastboot (S-ON means u need to flash kernel manually) to fix your installation
Generally I'd suggest
Flash this recovery via fastboot --> TWRP 2.7.0.8
(its compatible to the lastest CM11 versions 05/01/2014 and newer
And may be try PAC rom (I just love it)
Click to expand...
Click to collapse
I indeed just flashed the boot.img seperately which was in the rom, and now it works. It's a huge relief to see my phone work again, thanks a lot!!
One more thing so I avoid messing up in the future; When I decide to install another rom, do I always do a factory reset / clear cache, then flash the rom and flash the kernel via fasboot?
CrackedHippo said:
I indeed just flashed the boot.img seperately which was in the rom, and now it works. It's a huge relief to see my phone work again, thanks a lot!!
One more thing so I avoid messing up in the future; When I decide to install another rom, do I always do a factory reset / clear cache, then flash the rom and flash the kernel via fasboot?
Click to expand...
Click to collapse
FULL wipe --> format system, data, cache, dalvik --> flash rom --> immediately go to fastboot and flash the kernel --> reboot and done
Just try to get S-OFF, then the kernel get installed with the rom via recovery
LS.xD said:
FULL wipe --> format system, data, cache, dalvik --> flash rom --> immediately go to fastboot and flash the kernel --> reboot and done
Just try to get S-OFF, then the kernel get installed with the rom via recovery
Click to expand...
Click to collapse
Looks like I was cheering too early. Roughly 1 minute after launching my phone, .comSystemGUI or something along those lines stopped working, and whenever I pressed "ok" the message would instantly return. I can't connect my phone to my PC to put another ROM on it since the message won't disappear. Also I tried re-flashing the same ROM, but now it says can't mount storage/sdcard0.
Really frustrating!
http://forum.xda-developers.com/showthread.php?t=2206434
This topic guided me into getting the sdcard mountable again, but in the process I lost the rom .zip file.
And my phone won't boot anymore, it doesn't get past the HTC logo, so I can't put a new rom on it and flash it.
What is there left for me to do? Stock rom? How do I find the stock rom?
Thanks in advance.
I figured it out, thanks for your guidance LS.xD!
Basically what I did was mount the SD storage in CWM and transfer Pac-man rom onto the storage, then flash the .zip, flash Gapps and finally in bootloader fastboot the boot.img (because I'm S-ON). Maybe this will help anyone.
EDIT: Someone may wanna be careful with using TWRP, it corrupted my SD storage for a while.
CrackedHippo said:
I figured it out, thanks for your guidance LS.xD!
Basically what I did was mount the SD storage in CWM and transfer Pac-man rom onto the storage, then flash the .zip, flash Gapps and finally in bootloader fastboot the boot.img (because I'm S-ON). Maybe this will help anyone.
EDIT: Someone may wanna be careful with using TWRP, it corrupted my SD storage for a while.
Click to expand...
Click to collapse
SD card bug can also be caused by CWM or flashing a rom (Viper really loves to brick SD). I never had any issues with TWRP. The only SD card bug I had in over a year flashing roms to my One S was caused by flashing CWM
Sent from my beloved HTC One S using (most time buggy) Tapatalk
Hi guys, I'm new to installing custom roms. I've been reading for countless hours on the process before I attempt to install one. Here's where I'm at.
Phone: Verizon HTC One m8
1) Used Sunshine to get unlocked bootloader & S-OFF
2) I downloaded all OTA updates
3) Then flashed TWRP 3.0.2.0 and rooted with superSU
4) I immediately made a nandroid backup using TWRP
My phone's current state is working fine on stock rom.
Android 6.0
Sense 7.0
Here's my getvar all output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.14.20.0930
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.21.605.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXX
(bootloader) imei: XXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: XXXXXXXXXX
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
I want to install Android Revolution HD
I downloaded Android Revolution HD 53.1 which is Marshmallow (Android 6.0.0 + HTC Sense 7.0) according to their site.
I made one attempt to install that rom but it didn't work. Here's what I did:
1) Copied the rom zip to my sdcard
2) Entered recovery (TWRP)
3) Performed a Wipe in TWRP (default wipe settings)
4) Clicked Install, selected the Android Revolution zip.
The install screen came up, I went through the dialog and selected which apps I wanted to be installed in ARHD, and the install went through and eventually said Success. I rebooted the phone and was stuck in bootloop. So I restored to my nandroid backup and haven't tried again since.
I have read and re-read their instructions and am still not sure what I'm missing. Any help is greatly appreciated, and if you need any info just let me know. Thanks!
jdub55 said:
Hi guys, I'm new to installing custom roms. I've been reading for countless hours on the process before I attempt to install one. Here's where I'm at.
Phone: Verizon HTC One m8
1) Used Sunshine to get unlocked bootloader & S-OFF
2) I downloaded all OTA updates
3) Then flashed TWRP 3.0.2.0 and rooted with superSU
4) I immediately made a nandroid backup using TWRP
My phone's current state is working fine on stock rom.
Android 6.0
Sense 7.0
Here's my getvar all output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.14.20.0930
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.21.605.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXX
(bootloader) imei: XXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: XXXXXXXXXX
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I want to install Android Revolution HD
I downloaded Android Revolution HD 53.1 which is Marshmallow (Android 6.0.0 + HTC Sense 7.0) according to their site.
I made one attempt to install that rom but it didn't work. Here's what I did:
1) Copied the rom zip to my sdcard
2) Entered recovery (TWRP)
3) Performed a Wipe in TWRP (default wipe settings)
4) Clicked Install, selected the Android Revolution zip.
The install screen came up, I went through the dialog and selected which apps I wanted to be installed in ARHD, and the install went through and eventually said Success. I rebooted the phone and was stuck in bootloop. So I restored to my nandroid backup and haven't tried again since.
I have read and re-read their instructions and am still not sure what I'm missing. Any help is greatly appreciated, and if you need any info just let me know. Thanks!
Click to expand...
Click to collapse
If I'm reading the op correctly I don't think that rom is compatible with the Verizon m8
Sent from my HTC One M8 using XDA Labs
jurington said:
If I'm reading the op correctly I don't think that rom is compatible with the Verizon m8
Click to expand...
Click to collapse
Ah shoot. I must have overlooked that. Okay, then how about this Verizon Stock Rooted rom?
Here's the thing. I really want a debloated rom. I'm not picky. It would be nice to get a stable custom rom that supports ART and is debloated. But I'm a bit confused.
It seems most of the stable roms are running Lollipop. Does this mean I need to downgrade somehow? Can I flash firmware, or do I need to do a actual factory reset? Please clarify this part, I think this is where I'm most confused at the moment.
jdub55 said:
Ah shoot. I must have overlooked that. Okay, then how about this Verizon Stock Rooted rom?
Here's the thing. I really want a debloated rom. I'm not picky. It would be nice to get a stable custom rom that supports ART and is debloated. But I'm a bit confused.
It seems most of the stable roms are running Lollipop. Does this mean I need to downgrade somehow? Can I flash firmware, or do I need to do a actual factory reset? Please clarify this part, I think this is where I'm most confused at the moment.
Click to expand...
Click to collapse
So for the most part just stay on marshmallow firmware. Everything I believe is compatible with it. And I'm running viper rom right now and it's pretty amazing. But just look in the Verizon m8 development and original development and you'll find roms that are compatible with it.
Sent from my HTC One M8 using XDA Labs
jurington said:
So for the most part just stay on marshmallow firmware. Everything I believe is compatible with it. And I'm running viper rom right now and it's pretty amazing. But just look in the Verizon m8 development and original development and you'll find roms that are compatible with it.
Sent from my HTC One M8 using XDA Labs
Click to expand...
Click to collapse
Oh okay. I actually already downloaded ViperOneM8 6.0.0 from their website. Is it safe to say I can perform a Wipe in TWRP, and then install the Viper rom and I should be good?
Also, just to clarify: I don't need to flash any firmware.zip?
Thanks so much.
jdub55 said:
Oh okay. I actually already downloaded ViperOneM8 6.0.0 from their website. Is it safe to say I can perform a Wipe in TWRP, and then install the Viper rom and I should be good?
Also, just to clarify: I don't need to flash any firmware.zip?
Thanks so much.
Click to expand...
Click to collapse
If you're already on the latest ota then you're good to go. And it'll have you perform a wipe through the aroma installer so no need to wipe before hand. And it's pretty slick, I just flashed it this morning and I'm liking it so far.
Sent from my HTC One M8 using XDA Labs
jurington said:
If you're already on the latest ota then you're good to go. And it'll have you perform a wipe through the aroma installer so no need to wipe before hand. And it's pretty slick, I just flashed it this morning and I'm liking it so far.
Click to expand...
Click to collapse
Thanks, I'm now running ViperOne!
I'm noticing a couple issues though:
1) The HTC Calendar app won't sync with my Google account. And my Google account isn't showing in the "Accounts" setting in Calendar. (I opted to not install Google Calendar during the rom install, but opted to install HTC Calendar)
2) None of the photos I've taken after installing V1 work with uFocus. I don't know if it's an issue with uFocus, or the dual lens. But when I go to edit a photo I took, I go into uFocus, and it says "Tap anywhere to adjust focus", but it doesn't matter where I tap, it doesn't adjust anything. Also, when taking a photo it doesn't tell me if my finger is blocking the 2nd lens. It will take the shot anyway, and if the 2nd lens was blocked, it will simply deny going into uFocus for that shot.
3) Is there any way to hide the Boomsound notification when playing audio?
If I can resolve these issues I can see myself sticking with this rom for a long time
jdub55 said:
Thanks, I'm now running ViperOne!
I'm noticing a couple issues though:
1) The HTC Calendar app won't sync with my Google account. And my Google account isn't showing in the "Accounts" setting in Calendar. (I opted to not install Google Calendar during the rom install, but opted to install HTC Calendar)
2) None of the photos I've taken after installing V1 work with uFocus. I don't know if it's an issue with uFocus, or the dual lens. But when I go to edit a photo I took, I go into uFocus, and it says "Tap anywhere to adjust focus", but it doesn't matter where I tap, it doesn't adjust anything. Also, when taking a photo it doesn't tell me if my finger is blocking the 2nd lens. It will take the shot anyway, and if the 2nd lens was blocked, it will simply deny going into uFocus for that shot.
3) Is there any way to hide the Boomsound notification when playing audio?
If I can resolve these issues I can see myself sticking with this rom for a long time
Click to expand...
Click to collapse
The first two issues are known about, and I don't know if it can be fixed since its a port from the HTC 10 and it's a completely different base than the m8 and if you follow the main thread and the Verizon for viper you see if there can be a fix. And I haven't looked hard to see if I can hide that dialogue but if I do I will definitely let you know.
Sent from my HTC One M8 using XDA Labs
I have an A9 that I figure'd I'd root since my current phone is a Galaxy J7 and will never see root access ever (it's a tracfone).
Here's what's up. I went through several walk-throughs on trying to root the device with a one-click solutions on my phone and PC. 'OneClickRoot' won't open, KingRoot methods do nothing, and KingoRoot seemed a bit too shady to me. So maybe I'm getting ahead of myself. I do some reading and every guide that seemed worth it's weight in text, walked me through unlocking the bootloader first, then rooting. So I download the JavaDev and AndroidDev installers, and other HTC drivers/managers. I have access to adb + fastboot (+ htc_fastboot where applicable). I make an account over at HTCDev and officially unlock the phone. As I read further into this process, TWRP comes up. I download 3.2.1.0 (and eventually some other versions too). I ran 'fastboot flash recovery twrp.img' (also trying the .img with full version in name as downloaded, and changing it to recovery.img). Fastboot takes all of 6.x seconds to do it's work (which doesn't seem quite right for a 38MB file, but what to I know?), and everything seems to check out. If I try to cmd/adb reboot into recovery mode or manually enter it from the fastboot>bootloader>recovery menues, I get an htc logo, delayed black screen than a normal boot to the lockscreen. Clear the cache? Tried it via fastboot, since the stock recovery is gone. Still nothing. At this point I feel I'm missing something very small, or something just plain doens't work. I've checked XDA, and a few other forums to as for back as 2015 posts on rooting/bootloader issues, and tryed little variation in commands trying to make things work. So here I am, first post on XDA, pleaing for help. My head is spinning and if I have to hear the damn AT&T chime on boot after a hung up recovery boot one more time, I am going to destroy this phone.
Since you're going to ask, this is what I'm working with:
Code:
HTC One A9 (Model 2PQ9120)[AT&T]
Download Mode:
Code:
*** UNLOCKED ***
htc_hiaeul PVT S-ON
LK-1.0.0.0000
[email protected]
OpenDSP-6.8.5.00.190-8952_1013
OS-1.27.502.5
Nov 12 2015,15:40:38(656287)
While on Download Mode:
Code:
C:\adb>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_hiaeul
(bootloader) version: 1.0
(bootloader) imei: 352637070179992
(bootloader) version-main: 1.27.502.5
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PQ912000
(bootloader) cid: CWS__001
Bootloader Mode:
Code:
[COLOR="Gray"]*** Software status: Offical *** [/COLOR]
[COLOR="Magenta"]*** UNLOCKED ***[/COLOR]
[COLOR="Orange"]*** S-ON ***[/COLOR]
While on Bootloader Mode:
Code:
C:\adb>fastboot getvar all
(bootloader) version:0.5
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x625000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xd9000000
(bootloader) serialno:HT5APBE01249
I tried to find a stock recovery image, but I have no clue what I looking for quite honestly, and don't want to flash the wrong thing (though at this point I guess it doesn't matter). I don't need a long drawn-out 'well this is where you kerfuffled your device' speech, ask if I ran a command, and I'll try to elaborate on when and how I did. Or heck, just throw commands at me and I'll just try them out. It's no big deal If I lose the phone altogether, I'm just trying to make it a WiFi only, barbones, games-only device. Thanks ahead of time!
Magisks will root your device from twrp...You have an ATT variant... Which has not been updated to latest nougat software... 1.27.502.5... This means youll have to flash one of the earliest versions of twrp...
I tried 3.0.0-0 (didn't work), which is only a year older than the A9, and it's the oldest Team Win has on their site. How early we talking about?
EDIT:
Found an old guide from Dec2015 that cites 'twrp-2.8.7.0_CPTB-B9-hiae.img' as the versio to use, but frequently says 'only use for HTC A9 Tablet'. Is this something I can just try, since it's the recovery partition (is it a partition?) and is already dead. I can't make it go from not working to not working more can I?
I have the exact same phone, with the exact same setup (version#'s, s-on, etc) as Allodesh and I am having the same troubles. I tried following the guide in the Official Lineage OS 15.1 thread and got to the part to install the latest twrp. The latest version didn't take, and I was left without a boot recovery after trying. I tried several other versions and eventually 3.0.0-0 took. I tried flashing the rom from twrp 3.0.0-0, but I am unable to mount the drives and get "invalid argument".
Do you think an earlier version of twrp might help my case too?
My phone still boots up into the stock Android, but I can't do any OTA updates. So, I'm pretty much stuck. I've spent the last week googling, but this is the only thread I found that seems to have the same issues I'm having. So, any help you could offer both of us would be very much appreciated!
By the way, is s-off necessary or relevant to our problems?
Sorry if I'm hijacking this thread, but I think my problems are the same.
Well I've been toying with my phone and searching forums for the last couple of weeks for answers and I've figured out 2 things. For the AT&T US GSM phones we have, the latest version of TWRP that will work for it is 3.0.0-2. Once I flashed that, my mounting troubles stopped and I was able to successfully root my phone by flashing the SuperSU zip.
The 2nd thing I found out is that LineageOS won't work on this phone without getting S-Off and upgrading the firmware using one of the other carrier's RUU files which is way more work than I want to get into. I wish this information was in the How-To install Lineage guide for the HTC One A9, as I probably would have got a different phone, but oh well, at least it's rooted now and I can clear out the bloatware.
If you want to start over from square one, just find the correct RUU (I can't post the link apparently, too new to the forum) and run it from windows and it'll restore it to factory. It might take a couple of tries for it to install, but it works.
Hope that helps a little.