Related
Hi all. I am new to the xda developers forums, as well as new to the process of rooting an Android phone and installing a custom ROM. So please forgive me if I am posting in the wrong area, etc. If so, I am happy to take direction and go to the proper areas/forums.
I have a HTC One X from T-Mobile.
I have been following instructions to root the phone, flash a custom recovery, and then install a custom ROM. Unlocking the phone was no problem. Flashing the custom recovery *seemed* to be no problem (the commands ran fine and the phone appeared to write the file), but when I try to boot into recovery mode, I get a warning screen from HTC ("This image is for internal development only, blah, blah, blah), but then I just get a black screen. I can't do anything other than hard reset the phone. Any time I try to boot into recovery, all I ever get is a black screen.
The recovery image that I've been trying to use is recovery-clockwork-touch-6.0.4.8-endeavoru.img.
I'm just wondering if this is a known issue and if you can point me in the right direction. Am I simply using the wrong recovery image? Is there a different recovery image recommended for One-X's from T-Mobile (does the carrier even matter?)?
Sorry for the noob question. Any guidance you can provide would be sincerely appreciated.
TIA
Hawkser said:
Hi all. I am new to the xda developers forums, as well as new to the process of rooting an Android phone and installing a custom ROM. So please forgive me if I am posting in the wrong area, etc. If so, I am happy to take direction and go to the proper areas/forums.
I have a HTC One X from T-Mobile.
I have been following instructions to root the phone, flash a custom recovery, and then install a custom ROM. Unlocking the phone was no problem. Flashing the custom recovery *seemed* to be no problem (the commands ran fine and the phone appeared to write the file), but when I try to boot into recovery mode, I get a warning screen from HTC ("This image is for internal development only, blah, blah, blah), but then I just get a black screen. I can't do anything other than hard reset the phone. Any time I try to boot into recovery, all I ever get is a black screen.
The recovery image that I've been trying to use is recovery-clockwork-touch-6.0.4.8-endeavoru.img.
I'm just wondering if this is a known issue and if you can point me in the right direction. Am I simply using the wrong recovery image? Is there a different recovery image recommended for One-X's from T-Mobile (does the carrier even matter?)?
Sorry for the noob question. Any guidance you can provide would be sincerely appreciated.
TIA
Click to expand...
Click to collapse
UPDATE:
For what it's worth, I have the following information from the fastboot screen ...
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.13.50.05.31
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10:57:-1
Not sure if any of that helps in determining the issue or the right recovery image.
TIA
Hawkser said:
UPDATE:
For what it's worth, I have the following information from the fastboot screen ...
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.13.50.05.31
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10:57:-1
Not sure if any of that helps in determining the issue or the right recovery image.
TIA
Click to expand...
Click to collapse
Wow. /sigh. Apparently I have a HTC One S, not a One X. Been so long since I've had this phone that I forgot the part number. I'm just going to crawl away now.
For the record. All is well now. It's amazing how quickly and easily everything installs when you use the right files for the right phone. Now my only issue is that Google Play Store won't install any apps. The Play store runs fine...it just won't install any apps. Off to more searches for that.
Thanks anyway. I'm glad to at least have CyanogenMod running now. First time for me.
My ATT HTC One M8 was rooted using the 'official HTC' method soon after purchase and I was able to get CyanogenMod installed via their windows install tool back in the day so I didn't have to really understand what I was doing. It still runs CM11 quite well, but I'd really like to upgrade to CM12 if for no other reasons then the security updates. When I try to upgrade to CM12 though I get this error:
This package supports bootloader(s): 3.18.0.0000, 3.19.0.00000; this device has bootloader 3.16.0.00000, Installation aborted.
My recovery is ClockworkMod Recovery v6.0.4.8
Here's my bootloader screen:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.16.0.0.0000
RADIO-1.16.21331931.LA11G
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.58.502.1
eMMC-boot 2048MB
Apr 18 2014,16:06:33.0
I don't know what I'm doing.
After six months of occasionally messing with this I still haven't figured out how to upload the boatloader. I only barely understand the stuff I read on this site. Most things have pointed me to do this:
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
But I'm not s-off, there is a ton of downloads and steps and 150 pages of comments (!) so if there is something burried in there that will help me I can't find it. I tried blindly applying one of the firmware downloads but it didn't work. and it was probably the wrong one anyway.
Everything else pointed me to return to stock and accept the OTA update with this thread:
http://forum.xda-developers.com/showthread.php?t=2696282
But I again got lost, and never got this working. Once I got brave and spent the better part of a day trying to return everything to stock, but I couldn't figure out how to do it in the end and was super-happy to get back where I started and have a working phone again. I don't recall the exact problem I had, but I remember trying several RUUs - not being sure which one was the right one - and they wouldn't apply and that was after changing recovery versions and types several times and following random forum advice and thinking I bricked the thing a dozen times.
My question is: Is there a simple way to upgrade my bootloader ? Simple meaning exact steps to follow to just upgrade the bootloader without doing a bunch of other stuff that could brick me and I don't understand? I'm not really sure where to begin, even though I've tried a bunch of stuff, this stuff is so confusing.
Is there any help for noob like me?
You have AT&T - those threads are not for you.
You need to see this - http://forum.xda-developers.com/showthread.php?t=2751432
1. Download RUU 4.28.502.2 RUU
2. Boot your device to bootloader/fastboot and connect to PC
2. relock bootloader - command fastboot oem lock
3. Install RUU
4. re-unlock your bootloader with the unlock_code.bin that you got from HTCDev
5. reinstall custom recovery
6. install your preferred custom ROM
To run a RUU .. you need USB2.0 and latest HTC USB driver installed. If not sure, download HTC Sync Manager - http://www.htc.com/us/support/software/htc-sync-manager.aspx
install it as it will install the latest HTC USB driver then uninstall the HTC Sync Manager but leave the driver.
This will wipe everything on internal storage - backup your photos, musics & etc to PC first.
Wow, thanks for taking the time with specific steps and links! I'll try again this weekend and let you know!
thanks!
This worked perfect! I think the key was the ATT RUU, which I definitly wasn't using it before. Once done getting back to CM was a snap and I'm now in great shape! Thanks so much!
You're welcome.
Correct RUU for correct device always fix things
Phone originally on Android 4 - probably KitKat, it was bought in late 2014.
It's had two OTA upgrades, first to Lollipop, which I used without any problems until Marshmallow came along, and then I did the OTA upgrade to that, and used it without any problems for a while.
I've never done any backups, mainly because I could never get HTC Sync Manager to see my phone when I connected it to the laptop, and because I'm lazy, and a friend told me that means there's probably unwanted bits of the old operating systems still on the phone.
I recently tried to "Restart" it when I had an unresponsive app, and it went into a bootloop. At that point I managed to get it started again (in safe mode maybe? not sure, but it started working, so I ignored the problem) and used it for a few days.
Same thing happened again - bootloop. Couldn't get out of it at all. Have tried a factory reset/restore without any success (I've resigned myself to losing any data left on it).
I can still get into recovery mode, but it still won't go any further. I asked about it on this forum a few days ago and was told that the OS is probably corrupted and will need to be restored.
The bootloader screen shows:
*** Software status: Official ***
*** locked ***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.29.214500021.12G
OpenDSP-v51.2.2-00593-M8974_FO.1015
OS-6.12.401.4
eMMC-boot 2048MB
Dec 17 2015,14:15:48.0
My question is this:
In Recovery mode, there's a menu option to "Apply update from SD card".
Can I use this by copying OS 6.12.401.4 to the root directory of an SD card, slotting that into the phone, and selecting that option?
If I can, then what format should this be in, and what format does its name need to be in?
If I can't just do that, what's the idiot's guide to what I need to do to get the phone working again? I don't have any great desire to root it, I was quite happy just using the phone as it was, when it was working.
Any help would be appreciated!
see this post: http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
you'll find this rom file of the official STOCK Sense ROM (ATTACHED HERE IS THE DIRECT LINK, which is also present in the post above): http://forum.xda-developers.com/devdb/project/dl/?id=15489&task=get
You'll need TWRP to just install it like any other ROM, follow the installation through AROMA and that's about it.
good luck.
DL55 said:
I don't have any great desire to root it, I was quite happy just using the phone as it was, when it was working.
Click to expand...
Click to collapse
First : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
Second : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
---------- Post added at 08:22 PM ---------- Previous post was at 08:17 PM ----------
ushabuntu said:
You'll need TWRP to just install it like any other ROM, follow the installation through AROMA and that's about it.
Click to expand...
Click to collapse
He said he doesn't want to root his device. To install TWRP he needs to unlock the bootloader (a process to root a device)
DL55 said:
Phone originally on Android 4 - probably KitKat, it was bought in late 2014.
It's had two OTA upgrades, first to Lollipop, which I used without any problems until Marshmallow came along, and then I did the OTA upgrade to that, and used it without any problems for a while.
I've never done any backups, mainly because I could never get HTC Sync Manager to see my phone when I connected it to the laptop, and because I'm lazy, and a friend told me that means there's probably unwanted bits of the old operating systems still on the phone.
I recently tried to "Restart" it when I had an unresponsive app, and it went into a bootloop. At that point I managed to get it started again (in safe mode maybe? not sure, but it started working, so I ignored the problem) and used it for a few days.
Same thing happened again - bootloop. Couldn't get out of it at all. Have tried a factory reset/restore without any success (I've resigned myself to losing any data left on it).
I can still get into recovery mode, but it still won't go any further. I asked about it on this forum a few days ago and was told that the OS is probably corrupted and will need to be restored.
The bootloader screen shows:
*** Software status: Official ***
*** locked ***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.29.214500021.12G
OpenDSP-v51.2.2-00593-M8974_FO.1015
OS-6.12.401.4
eMMC-boot 2048MB
Dec 17 2015,14:15:48.0
My question is this:
In Recovery mode, there's a menu option to "Apply update from SD card".
Can I use this by copying OS 6.12.401.4 to the root directory of an SD card, slotting that into the phone, and selecting that option?
If I can, then what format should this be in, and what format does its name need to be in?
If I can't just do that, what's the idiot's guide to what I need to do to get the phone working again? I don't have any great desire to root it, I was quite happy just using the phone as it was, when it was working.
Any help would be appreciated!
Click to expand...
Click to collapse
You're funny.
Following is a link to HTC's official stock RUU, and instructions to flash it. This will install your phone's current firmware/software from scratch.
https://www.androidfilehost.com/?fid=24369303960687057
To flash the RUU zip file:
A. You need to put it at the root of your SD CARD and rename it to 0P6BIMG.zip (first character is a zero, and careful not to rename it to 0P6BIMG.zip.zip)
B. Turn your phone off, then start it into bootloader. It will recognize the 0P6BIMG.zip file and give you instructions in RED for proceeding forward.
C. Follow the instructions in RED to flash. You will lose all data as the RUU will format all partitions.
Cheers
shirreer said:
You're funny.
Following is a link to HTC's official stock RUU, and instructions to flash it. This will install your phone's current firmware/software from scratch.
*(link removed because I'm new)*
To flash the RUU zip file:
A. You need to put it at the root of your SD CARD and rename it to 0P6BIMG.zip (first character is a zero, and careful not to rename it to 0P6BIMG.zip.zip)
B. Turn your phone off, then start it into bootloader. It will recognize the 0P6BIMG.zip file and give you instructions in RED for proceeding forward.
C. Follow the instructions in RED to flash. You will lose all data as the RUU will format all partitions.
Cheers
Click to expand...
Click to collapse
Many before you have a similar opinion of me. Sometimes it's in a good way, but I don't like to ask, in case it isn't.
But thanks, that was an impressively quick response, and I think you've recognised how much of an idiot I am. Downloading the zip file now, and I'll report on my success/failure (delete as and when obvious) later.
Cheers!
DL55 said:
Many before you have a similar opinion of me. Sometimes it's in a good way, but I don't like to ask, in case it isn't.
But thanks, that was an impressively quick response, and I think you've recognised how much of an idiot I am. Downloading the zip file now, and I'll report on my success/failure (delete as and when obvious) later.
Cheers!
Click to expand...
Click to collapse
Well, just so we're clear, you're funny in a good good way. Keeping your sense of humor while having phone problems is hard. Also, having phone problems does not an idiot make; that makes you a welcomed member of the XDA community
Do let us know how things go on your end.
shirreer said:
Well, just so we're clear, you're funny in a good good way. Keeping your sense of humor while having phone problems is hard. Also, having phone problems does not an idiot make; that makes you a welcomed member of the XDA community
Do let us know how things go on your end.
Click to expand...
Click to collapse
Thanks, that's kind of you to say as much.
My "idiot" comment was primarily because of my utter failure to be bothered about doing any form of backup.
I blame HTC Sync Manager**, which doesn't do either sync-ing OR managing...
If it wasn't for the fact that all but the most recent of my contacts were synced to Gmail, I'd have been a lot worse off!
I fully intend to report on what happens. I can't be the only one who'd benefit from knowing a straightforward solution to this, and if it helps others too, then that has to be a good thing.
** Yes, it IS the latest version. It can't see either my M8 or my One X, which is only on Jellybean...
shirreer said:
Well, just so we're clear, you're funny in a good good way. Keeping your sense of humor while having phone problems is hard. Also, having phone problems does not an idiot make; that makes you a welcomed member of the XDA community
Do let us know how things go on your end.
Click to expand...
Click to collapse
Oh look, a working M8!
Thanks for your help, it's good to find someone who could understand my level of incompetence.
And it's also good to have a 4G phone back again. I've spent the last couple of weeks swearing at a One X with a comprehensively cracked screen. It's been hell, I tell you...
I wish to do similar, Except my CID is H3G_001, i dont seem to be able to find a version higher than 5.0 anywhere, sd card flashing method that is, does anyone know if theres a copy anywhere, i do know that 3uk is currently on MM, i just cant find it, HEEELLLPPPP, pwetty pleeaasssee
gazza35 said:
I wish to do similar, Except my CID is H3G_001, i dont seem to be able to find a version higher than 5.0 anywhere, sd card flashing method that is, does anyone know if theres a copy anywhere, i do know that 3uk is currently on MM, i just cant find it, HEEELLLPPPP, pwetty pleeaasssee
Click to expand...
Click to collapse
Well, I wouldn't be able to tell you what to do, I don't even know what a CID is when it's not being used to fight crime...
...but you might stand a better chance of attracting attention to your problem by starting a new thread about it. Make the title specific to your problem, then the problem gets seen by more people.
DL55 said:
Well, I wouldn't be able to tell you what to do, I don't even know what a CID is when it's not being used to fight crime...
...but you might stand a better chance of attracting attention to your problem by starting a new thread about it. Make the title specific to your problem, then the problem gets seen by more people.
Click to expand...
Click to collapse
Yep, and that will get me the answers i want.....
DL55 said:
Oh look, a working M8!
Thanks for your help, it's good to find someone who could understand my level of incompetence.
And it's also good to have a 4G phone back again. I've spent the last couple of weeks swearing at a One X with a comprehensively cracked screen. It's been hell, I tell you...
Click to expand...
Click to collapse
I'm glad you're all set. Enjoy your M8, you've earned it.
Hi,
I have bought a used HTC M9 on Kijiji (I'm in Québec, Canada)
It must be faulty because it kept randomly restarting (sometimes once, sometimes for periods of 20 minutes, which made it hardly usable)
After clearing the cache partition and factory resetting it a couple times, I decided to flash it.
What I did:
- enabled the developer mode and USB debugging
- unlocked the bootloader
- flashed TWRP
- flashed SuperSU v2.74-2
Now, Android won't boot. When I start the phone, I see the green HTC logo on a white background with a red text saying it's a development build, then after about 10 seconds it restarts to the same screen. Over and over again.
In download mode, I am able to see the device with fastboot, but adb does not show anything.
In recovery mode, it's the opposite.
The phone is still S-ON so I have tried S-OFF methods (moonshine and firewater), but the fact of not having fastboot AND adb working at the same time made them fail.
Here's my phone info:
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei: ************
(bootloader) version-main: 3.38.666.2
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440801_96.01.51207G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: BM___001
Any help would be greatly appreciated...
Thanks in advance!
youre flashing the wrong superuser. Try 2.64. And btw, moonshine and firewater wont work. The only way to s off is sunshine
Roobwz said:
youre flashing the wrong superuser. Try 2.64. And btw, moonshine and firewater wont work. The only way to s off is sunshine
Click to expand...
Click to collapse
Thanks for your reply.
I used Squabbi's HTC one M9 Toolkit to flash
It does not offer 2.64, but 2.52 and 2.66 are the closest ones. Both in BETA as well.
Should I try one of them?
zzzer51 said:
Thanks for your reply.
I used Squabbi's HTC one M9 Toolkit to flash
It does not offer 2.64, but 2.52 and 2.66 are the closest ones. Both in BETA as well.
Should I try one of them?
Click to expand...
Click to collapse
You shouldnt use toolkits imo, no offence squabbi. You should just download the 2.64 file from chainfires thread and flash it in twrp. It isnt harder than that. Btw 2.64 was the only superSu that worked for me
Ok, I have been able to find a zip for 2.64 and will install it with TWRP when my phone's battery is drained out (it tried to boot on the OS and is currently stuck on the HTC logo...)
I have also tried installing files directly from the microSD
downloaded from:
https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml
http://androidruu.com/index.php?developer=M9
using fastboot flash zip zipfile.zip
but I get errors like
9 RU_SECURITY_FAIL
android-version information is missing
I'm not sure I'm trying to flash the right file anymore...
EDIT:
I have tried to flash both 0PJAIMG_HIMA_UL_L50_SENSE70_ATT_BM_1.32.666.30 and 0PJAIMG_HIMA_UL_L50_SENSE70_ATT_BM_1.32.666.6 files by going to TWRP -> Install but I get the error message 'zip file is corrupt!' every time...
And when I try to flash with fastboot, I get "Invalid sparse file format at header magi"
EDIT2:
Ok, I have made some progress!
What I did:
1/ Downloaded the image from this page http://forum.xda-developers.com/one-m9/general/guide-return-to-stock-canadian-htc-one-t3108236
2/ Formated my 8GB microSD card to exFAT (because the system image file is over 4GB)
3/ Extracted the system.emmc.win and boot.emmc.win files to the microSD card in path: E:\TWRP\BACKUPS\<myPhoneIDThatFastbootCanGiveYouIfYouTypeFastbootDevices>\Stock Bell
4/ Started the phone in recovery mode (TWRP)
5/ Tapped on Restore
6/ Selected the two files and hit Restore
7/ Performed a Factory reset (through TWRP, by tapping Wipe)
8/ Rebooted the phone in System mode
And Android started!
I'm not 100% sure it fully works as I haven't been able to finish the configuration yet (I don't have access to a wifi network where I am) so I will do that when I get home tonight.
But it looks a lot better than these past few days.
In the meantime, a quick question:
My bootloader is still unlocked. Can I leave it like that or should I re-lock it?
Thanks
No need to relock it unless you plan on updating. There is conflicting information on whether a locked bootloader is absolutely necessary.. Maybe someone could chime in?.
Otherwise it's safe to leave it and probably best to.
Beamed in by telepathy.
shivadow said:
No need to relock it unless you plan on updating. There is conflicting information on whether a locked bootloader is absolutely necessary.. Maybe someone could chime in?.
Otherwise it's safe to leave it and probably best to.
Beamed in by telepathy.
Click to expand...
Click to collapse
You can OTA with an unlocked bootloader but you need to be 100 % stock. It's always best to not relock bootloaders as if you get into problems, you'll not be able to flash stuff. The only time a locked bootloader is needed is when running RUU.exe while S-On. The SD card method works with an unlocked bootloader. I'd recommend to leave it unlocked
Thanks for the advice!
Ok so I have been able to boot the phone and set it up with my GMail account using wifi.
However, now:
1/ I have a red text mentioning that the build the phone is running is meant for development purposes only. It does not really matter to me, I just thought I'd mention it.
2/ There is no network service. I have tried my girlfriend's SIM card as well, but nothing happens. It doesn't say it can't register the SIM card nor say that the SIM card is not detected. Just nothing.
I tried changing the radio mode to GSM auto using *#*#4636#*#*, but when the phone reboots, it's back to WCDMA
3/ No IMEI (*#06# shows an empty window)
4/ It still randomly reboots as before. I was able to save a 'system crash' error report that popped up after a reboot. Please find it here: https://docs.google.com/document/d/13QBaeA1_Vo-b9mndffvbulG8epMq42Pnguawa2GcQTA/edit?usp=sharing
5/ When I press the physical button to lock the screen, it makes it go black then reboot, 50% of the time
zzzer51 said:
Thanks for the advice!
Ok so I have been able to boot the phone and set it up with my GMail account using wifi.
However, now:
1/ I have a red text mentioning that the build the phone is running is meant for development purposes only. It does not really matter to me, I just thought I'd mention it.
2/ There is no network service. I have tried my girlfriend's SIM card as well, but nothing happens. It doesn't say it can't register the SIM card nor say that the SIM card is not detected. Just nothing.
I tried changing the radio mode to GSM auto using *#*#4636#*#*, but when the phone reboots, it's back to WCDMA
3/ No IMEI (*#06# shows an empty window)
4/ It still randomly reboots as before. I was able to save a 'system crash' error report that popped up after a reboot. Please find it here: https://docs.google.com/document/d/13QBaeA1_Vo-b9mndffvbulG8epMq42Pnguawa2GcQTA/edit?usp=sharing
5/ When I press the physical button to lock the screen, it makes it go black then reboot, 50% of the time
Click to expand...
Click to collapse
did you restore the correct backup for your firmware?? ex 3.35,401.12 needs 3.35.401.12 and not 3.35.701.12. Everything needs to match. This might also solve your issues.
Roobwz said:
did you restore the correct backup for your firmware?? ex 3.35,401.12 needs 3.35.401.12 and not 3.35.701.12. Everything needs to match. This might also solve your issues.
Click to expand...
Click to collapse
I don't think I did...
The main-version that shows in download mode is 3.38.666.2 ... whereas the version of the backup I restored is 1.32.666.30.
I have been searching for a while, but have no idea where to find the right rom... Should I send an email to Bell?
zzzer51 said:
I don't think I did...
The main-version that shows in download mode is 3.38.666.2 ... whereas the version of the backup I restored is 1.32.666.30.
I have been searching for a while, but have no idea where to find the right rom... Should I send an email to Bell?
Click to expand...
Click to collapse
That's why you are getting these issues. You can try out the RUU service. Keep in mind that it costs around 20$, but at least you'll get a phone that's 100 % stock again. Either that or getting s off and downgrade firmware with a RUU
Skickat från min HTC One M9 via Tapatalk
Roobwz said:
That's why you are getting these issues. You can try out the RUU service. Keep in mind that it costs around 20$, but at least you'll get a phone that's 100 % stock again. Either that or getting s off and downgrade firmware with a RUU
Click to expand...
Click to collapse
Thanks for the suggestion, I did not know that service.
I always prefer doing things on my own, but I might have to use them because I have already spent around 20 hours trying to fix my phone...
That is, if we are sure there is absolutely no other way to find the RUU for free?
zzzer51 said:
Thanks for the suggestion, I did not know that service.
I always prefer doing things on my own, but I might have to use them because I have already spent around 20 hours trying to fix my phone...
That is, if we are sure there is absolutely no other way to find the RUU for free?
Click to expand...
Click to collapse
The service is remotely done over the computer, so you'll see everything that happens.
Well, if you find a RUU that matches everything (cid, mid and firmware), you'll be able to do it for free. Either that or s off (25$ as well), and you'll be able to convert your phone into a world wide edition model or dev edition. S off opens up a whole new world for you. Ex - you can flash exactly what you want (no need for Canadian firmware) and you're able to downgrade etc. The rest is up to you.
Roobwz said:
Well, if you find a RUU that matches everything (cid, mid and firmware), you'll be able to do it for free.
Click to expand...
Click to collapse
I found the version I was looking for from this link: http://www.htcdev.com/devcenter/downloads/P100
However, it's only 206MB, so I'm guessing it's not a firmware... what do I need to do with it?
EDIT: It's .tar.gz files. apparently source code
zzzer51 said:
I found the version I was looking for from this link: http://www.htcdev.com/devcenter/downloads/P100
However, it's only 206MB, so I'm guessing it's not a firmware... what do I need to do with it?
EDIT: It's .tar.gz files. apparently source code
Click to expand...
Click to collapse
That's kernel source I believe. Your only luck would be flippys thread in the general section
Skickat från min HTC One M9 via Tapatalk
The latest news:
I went S-OFF yesterday with Sunshine.
I was able to install Cyanogenmod, which looked cool, but I still did not have any network service.
So, I flashed an Bell stock firmware, version 1.xxx
Still did not have network.
I let Android download and install the update for version 2.xxx
When it finished, I got my network back!
Now, I would like, but am afraid to, update firmware to version 3.xxx or try Cyanogenmod again.
But, obviously, I'm afraid that I won't have any service anymore...
Anyways, thanks a lot guys for your help!
zzzer51 said:
The latest news:
I went S-OFF yesterday with Sunshine.
I was able to install Cyanogenmod, which looked cool, but I still did not have any network service.
So, I flashed an Bell stock firmware, version 1.xxx
Still did not have network.
I let Android download and install the update for version 2.xxx
When it finished, I got my network back!
Now, I would like, but am afraid to, update firmware to version 3.xxx or try Cyanogenmod again.
But, obviously, I'm afraid that I won't have any service anymore...
Anyways, thanks a lot guys for your help!
Click to expand...
Click to collapse
I would recommend upgrading to 3.xx for several reasons like doze, custom ROMs that are up to date etc. If you did the OTA from 1.x to 2.x, you shouldn't have any problems with the OTA to 3.x. in the worst case, just re flash the RUU or just convert the device to an European version.
Heyyy, it's me again
So, Android downloaded the update, but when I try to install it, it reboots to download mode.
Also, I cannot access the Recovery Mode.
I tried flashing TWRP 3.0.2.0 with fastboot a couple times, but when I try to access the Recovery Mode from the bootloader, I get :
Code:
Failed to boot to recovery mode
Press volume up or down to back to menu
Anyone knows why?
I am S-OFF and my bootloader is UNLOCKED
Thanks
zzzer51 said:
Heyyy, it's me again
So, Android downloaded the update, but when I try to install it, it reboots to download mode.
Also, I cannot access the Recovery Mode.
I tried flashing TWRP 3.0.2.0 with fastboot a couple times, but when I try to access the Recovery Mode from the bootloader, I get :
Code:
Failed to boot to recovery mode
Press volume up or down to back to menu
Anyone knows why?
I am S-OFF and my bootloader is UNLOCKED
Thanks
Click to expand...
Click to collapse
what was flashed prior to the OTA? OTAs fail if you arent 100% stock.
Roobwz said:
what was flashed prior to the OTA? OTAs fail if you arent 100% stock.
Click to expand...
Click to collapse
A looooot of stuff!
But even after flashing the original HTC recovery again, I get the same message.
And I can't access the recovery menu either.
Thanks
So roughly two years ago I decided to root my phone. I flashed TWRP, got S-OFF, and root. Well somebody hacked my phone and I freaked out. They were remotely downloading and inventorying all my devices' files, serial numbers, hardware info, accessing my camera, I mean everything, it was truly frightening the level of which whomever was doing this was able to to do it. I freaked out, went into TWRP, and started deleting everything that looked suspicious. I deleted my OS and probably a bunch of other things I shouldn't have on accident through TWRP. My device still has TWRP recovery functioning. I tried using ADB on my Windows 10 PC but I have no idea what I'm doing. I kept getting errors to the effect of "wrong version" etc. Being unable to use ADB I resorted to copying Viper OS to a flash card and I used TWRP to install it from flash. Once installed it "ran" but my Wifi radio did not work at all. When I tried to enable it in settings it stayed grey. Figuring I screwed up royally again, I decided to copy and paste a folder I created in 2014 with a TWRP recovery. It had the OS, cache, etc backed up. After using TWRP recovery it said I had no OS again. I'm freaking out, my phone is trashed, and I don't want to do anything else without a babysitter. I just want my original phone back, no custom roms, nothing. I don't want to turn S-ON because I know there is a possibility of bricking and quite frankly, I'm an idiot. Somebody just please walk me through what I need to do to get a fully functioning OS back on my phone. SD card methods preferred, as I can't get ADB to work or I'm too stupid to use it. I saw something mentioned that the firmware may need updating and that may have been the cause for the WiFi issue, since all I did was install Viper through a .zip through TWRP.
I just have no clue what I'm doing, the forums were no use. I don't understand any of it. To be honest, I don't know how I managed to root my device in the first place without bricking it. I need someone to baby me through the reinstallation of an OS. I mean every moot detail.
My "POWER ON + VOL DWN" Menu:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT: 3.16.0.0000
RADIO: 1.16.21331931.LA11G
OpenDSP v38.2.2-005420M8974.0311
OS: N/A
eMMC-boot: 2048MB
Apr 18 2014,16:06:33.0
TWRP version is 2.7.0.2
lgally80 said:
I just have no clue what I'm doing, the forums were no use. I don't understand any of it. To be honest, I don't know how I managed to root my device in the first place without bricking it. I need someone to baby me through the reinstallation of an OS. I mean every moot detail.
My "POWER ON + VOL DWN" Menu:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT: 3.16.0.0000
RADIO: 1.16.21331931.LA11G
OpenDSP v38.2.2-005420M8974.0311
OS: N/A
eMMC-boot: 2048MB
Apr 18 2014,16:06:33.0
TWRP version is 2.7.0.2
Click to expand...
Click to collapse
First things first.
Yes, you need to update your firmware, but you also really need to update your recovery as well.
Download this version of ViperOneM8 and flash it from your extSD. That will get you an OS that works.
Next, update your recovery. I would suggest 2.8.7.0 or newer. You can find the downloads for that here and instructions on how to flash the recovery here. ( I usually use the fastboot method myself )
After that you can update your firmware. You can find downloads for your firmware and instructions on how to flash it in this thread.
After you have the new recovery and new firmware, you will be able to flash a ROM built for the newer Android versions with working wifi.
You could also update via RUU from HTC's official US website, but you didn't give enough information for that. An RUU will return your phone to stock.
If you want to RUU your phone, plug into your PC and get into fastboot, enter fastboot getvar all and post the results here minus your IMEI and serial#. Either me or someone else here will be able to direct you to the proper RUU.
I'm guessing from your profile that you are on AT&T? If so, you can find the RUU for your device and instructions to update manually here.
Good luck!
xunholyx said:
First things first.
Yes, you need to update your firmware, but you also really need to update your recovery as well.
Download this version of ViperOneM8 and flash it from your extSD. That will get you an OS that works.
Next, update your recovery. I would suggest 2.8.7.0 or newer. You can find the downloads for that here and instructions on how to flash the recovery here. ( I usually use the fastboot method myself )
After that you can update your firmware. You can find downloads for your firmware and instructions on how to flash it in this thread.
After you have the new recovery and new firmware, you will be able to flash a ROM built for the newer Android versions with working wifi.
You could also update via RUU from HTC's official US website, but you didn't give enough information for that. An RUU will return your phone to stock.
If you want to RUU your phone, plug into your PC and get into fastboot, enter fastboot getvar all and post the results here minus your IMEI and serial#. Either me or someone else here will be able to direct you to the proper RUU.
I'm guessing from your profile that you are on AT&T? If so, you can find the RUU for your device and instructions to update manually here.
Good luck!
Click to expand...
Click to collapse
So, I first flashed the latest TWRP, and it did not work. Upon boot, I got the HTC on white background, with red "development purposes" warning, and it stayed there. I reflashed openrecovery-twrp-2.7.0.2-m8.img over the twrp-3.0.2-0-m8.img and got my recovery back using "flash recovery *.img" through ADB. thank god. Was this due to S-ON?
Next step, going to try flashing the OS/Rom you suggested. Will update in a sec...
Update 1:
Crap, that .zip has a bunch of stuff in it... Do I need to "build" an image to flash manually? Going to use the OS *.img by itself instead of leaving it as a whole .zip and trying to flash the whole .zip. There is a boot.img file and I don't want to mess with boot, so I will extract the zip and use only the OS in TWRP and see how that goes...
Update 2:
Opened the original OS Viper I flashed, it was a .zip with boot also, so going to leave this new one alone and go ahead and flash as a whole...
Update 3:
Flashed as whole, last screen on install said successful, rebooted. On HTC screen, waiting to see what happens... 3 minutes into waiting...
Update 4:
Holy mother of gaben, booted into setup, and my WiFi radio is detecting my networks, that's all I needed. You deserve just as many blowjobs as you do internets. Don't know what was wrong with that last Viper ROM but this did it. Many thanks. Not even going to bother with the new TWRP and everything else, my phone works as is and that's that. +1 for you mate.
lgally80 said:
So, I first flashed the latest TWRP, and it did not work. Upon boot, I got the HTC on white background, with red "development purposes" warning, and it stayed there. I reflashed openrecovery-twrp-2.7.0.2-m8.img over the twrp-3.0.2-0-m8.img and got my recovery back using "flash recovery *.img" through ADB. thank god. Was this due to S-ON?
Next step, going to try flashing the OS/Rom you suggested. Will update in a sec...
Click to expand...
Click to collapse
I did say to flash the ROM first to get back your OS, so.....
Anyway, that recovery version won't work until you update your firmware. Try 2.8.7.0 first, update your firmware, then you can use the 3.x.x.x recovery
I should have been clearer in my instructions
lgally80 said:
Crap, that .zip has a bunch of stuff in it... Do I need to "build" an image to flash manually? Going to use the OS *.img by itself instead of leaving it as a whole .zip and trying to flash the whole .zip. There is a boot.img file and I don't want to mess with boot, so I will extract the zip and use only the OS in TWRP and see how that goes...
Click to expand...
Click to collapse
You don't need to mess with or open a custom ROM zip to flash it. You just flash the whole zip. Yes, there is a lot in there, the OS (particularly a Sense one) is big, about 1.5 GB.
Mess with taking things out of the zip, and it probably won't flash. Or even if it does, it won't boot.
lgally80 said:
Holy mother of gaben, booted into setup, and my WiFi radio is detecting my networks, that's all I needed.
Don't know what was wrong with that last Viper ROM but this did it.
Click to expand...
Click to collapse
There is nothing wrong with the current Viper ROM.
The problem is your firmware is ancient (release KitKat firmware). Firmware meaning a number of modules needed for the OS to work, but are not contained in a ROM, which include hboot, radio, and a number of other modules including . . . WiFi.
Using your outdated KitKat firmware with almost any later ROMs (Lollipop or Marshmallow) will result in the same issue of WiFi broken, and also possibly extreme long boot time or no boot.
If you want to flash any remotely updated ROMs, you will need to update firmware as xunholyx already directed.
redpoint73 said:
You don't need to mess with or open a custom ROM zip to flash it. You just flash the whole zip. Yes, there is a lot in there, the OS (particularly a Sense one) is big, about 1.5 GB.
Mess with taking things out of the zip, and it probably won't flash. Or even if it does, it won't boot.
There is nothing wrong with the current Viper ROM.
The problem is your firmware is ancient (release KitKat firmware). Firmware meaning a number of modules needed for the OS to work, but are not contained in a ROM, which include hboot, radio, and a number of other modules including . . . WiFi.
Using your outdated KitKat firmware with almost any later ROMs (Lollipop or Marshmallow) will result in the same issue of WiFi broken, and also possibly extreme long boot time or no boot.
If you want to flash any remotely updated ROMs, you will need to update firmware as xunholyx already directed.
Click to expand...
Click to collapse
Yes I probably "should" update TWRP and my firmware, buuuut....
If it ain't broke, don't fix it.
Also in reply to your comments:
1. Flashing ViperOneM8_6.1.0.zip caused WiFi loss. Maybe Bluetooth also, don't remember. Flashing ViperOneM8_2.5.0.zip and now my phone is 100% functioning.
2. That "Old" firmware works fine now that it matches the ROM requirements, all radios functioning stable for several days now. I don't mind staying on older releases.
3. Nah I'm good, I use this M8 as a tool or entertainment device at home, and nothing else. It has no service, no AT&T signal here. Hasn't had service since 3 years after public release.
Anyway, thank you everyone who contributed. Anyone who's just showing up:
The Lesson of the Day - If your Hardware Radios do not function, the solution is your ROM probably requires a different Firmware revision than the one installed.
Cheers.