Related
Hello this is my first HTC device and I just learnt about Hboot, Firewater, S-off, and RUU terms.
These are my AT&T HTC M8 with 4.4.2 OS on it, Just had it S-off and Unlocked bootloader.
Can I know the following things...before flashing anything onto this
1-> Can I SIM unlock it using the Config.dat method as the device was not at all updated ?
2-> Changing CID to SuperCID grants me access to all RUUs but that's not needed as I will use customROMs based on Sense and AOSP right ?
3-> In order to flash and all I must be S-off I did it So now I can use ViperROM 4.4.4 but before that the viperrom page says need for an updated firmware >3 mines on 1.5, So if I flash any will the S-off goes away ?? & found this thread here for firmware updates but it says red text, can I know whats that ??
4-> How can I convert this device to a fully unlocked device like dev edition/ international version ?
5-> Most important of all what makes this device go hardbrick and S-on again (Firmware flashing, RUU etc, Like to know what will cause this since the device is S-off can I assume this device won't brick like Nexus phones).
Sorry for this lengthy post, never used a HTC device wanted to make sure all is well.
Thanks :fingers-crossed: !!
S-OFF allows you to do all sorts
I used the Sim unlock method after i S-OFF my At&t device just because and really couldn't tell you if worked cause I actually like At&t .
Supercid does allow for flashing other gsm firmware/ruu
Yes you would want to be as close in firmware to gain the best running experience when flashing Roms above your current firmware
S-OFF only changes if you do it the way you gained it
Being S-OFF you could flash the wrong ruu and hard brick your device ( CDMA device hardware I believe could brick your device along with the wrong device kernel could also brick it )
Nexus is pretty solid but can be bricked
Thanks for the quick post :good:
So I will go ahead and update the firmware w.o redtext (just noticed it's the one that says "This build blah blah" when bootup) then I'm good to go for the flashing all stuff ??
I can also flash a non sense based rom after using sense based Viper ROM / ARHD / etc without any issues, now is my device basically a Dev Edition plus the RUU & CID editing is only needed If I ever need going back to stock (though it wont happen) or flash regional firmwares or converting to GPE, DEV, WWE editions rt ?
Lastly my device ID it says M8_UL_CA will it change after I flash a ROM or Radio or Firmware ?
Ashtrix said:
Thanks for the quick post :good:
So I will go ahead and update the firmware w.o redtext (just noticed it's the one that says "This build blah blah" when bootup) then I'm good to go for the flashing all stuff ??
I can also flash a non sense based rom after using sense based Viper ROM / ARHD / etc without any issues, now is my device basically a Dev Edition plus the RUU & CID editing is only needed If I ever need going back to stock (though it wont happen) or flash regional firmwares or converting to GPE, DEV, WWE editions rt ?
Lastly my device ID it says M8_UL_CA will it change after I flash a ROM or Radio or Firmware ?
Click to expand...
Click to collapse
Yes, you can flash any ROM. If you plan on running GPE, you will need to convert back using a WWE RUU as GPE uses different sized partitions making the system partition too small to run Sense based ROMs.
Your device ID will change to M8_UL after flashing WWE firmware, but it isn't anything to worry about.
xunholyx said:
Yes, you can flash any ROM. If you plan on running GPE, you will need to convert back using a WWE RUU as GPE uses different sized partitions making the system partition too small to run Sense based ROMs.
Your device ID will change to M8_UL after flashing WWE firmware, but it isn't anything to worry about.
Click to expand...
Click to collapse
Thanks a lot !!
While GPE is a trade off for only AOSP, with DEV/WWE I can run any ROM based on Sense/AOSP i.e GPE & including the Lollipop right ?
So before proceeding I will update the Firmware first to a 2.xx or 3.xx then run an RUU based on DEV/WWE for conversion
Sorry for so many doubts, slowly learning about HTCs devices
Ashtrix said:
Thanks a lot !!
While GPE is a trade off for only AOSP, with DEV/WWE I can run any ROM correct ?
So before proceeding I will update the Firmware first then run an RUU based on DEV/WWE for conversion & for the last If I need to run Lollipop I should flash firmware again for v5 base or the WWE/DEV RUU (I think the Dev edition had got the lollipop Update) has the Firmware, Radio packed with it ?
Click to expand...
Click to collapse
The RUU contains the firmware. No need to flash it twice. You could just flash the WWE firmware if you are on Sense right now. Mostly RUUs are used to fix devices that are experiencing issues, or for converting GPE/Sense.
Running the RUU wipes EVERYTHING, so flashing the firmware is preferable. The WWE 5.0.1 firmware should be out soon, but DevEd is out now. If you wanted to convert to DevEd, there are plenty of tutorials on XDA. I'm really not up to speed on running DevEd firmware.
Found this page for all stuff & this thread for conversion.
& what's this .401 stuff in the first thread ?
I'm ok with full wipe anyways so I can use the RUU or the other recovery way for the conversion right ?
Ashtrix said:
Found this page for all stuff & this thread for conversion.
& what's this .401 stuff in the first thread ?
I'm ok with full wipe anyways so I can use the RUU or the other recovery way for the conversion right ?
Click to expand...
Click to collapse
401 is International WWE firmware. For example, my firmware version is 3.28.401.9 Verizon's latest firmware is 3.28.605.4
If you are okay with the full wipe, the RUU is probably the best way to convert, but the recovery method with stock recovery and stock nandroid would work too.
xunholyx said:
401 is International WWE firmware. For example, my firmware version is 3.28.401.9 Verizon's latest firmware is 3.28.605.4
If you are okay with the full wipe, the RUU is probably the best way to convert, but the recovery method with stock recovery and stock nandroid would work too.
Click to expand...
Click to collapse
Thank you verymuch for clarification !!!
Will do the work tmrw, its 2AM here
I've been fully converted GPE and back twice and after successfully converting back to Sense this last time I chose the Dev edition backup and stock recovery method followed by the proper CID&MID to take the OTA update witch is now lollipop
So basically I now have a lollipop firmware to run with the stock GPE lollipop ROM and you bet it runs great
Hi everyone!
I've been far from Rom changing, etc for a period. I've done this with HTC Desire HD and Samsung S4, but these two are very simpler than M8. Now I wnat to do this with my M8. These are my phone's details:
HTC One M8x
Android 5.0.2
Build number 4.24.709.2
I want to Root, S-OFF, Install a new Recovery (The best in your opinion). Also I don't think about restore it once again to factory defaults as Custom Roms (Like Android Revolution, Venom Viper, etc) update too! These are my questions:
1. Can I Root and S-OFF Android 5?! Is there any problem with this?
2. What Recovery do you suggest for me?
3. May you give me a link for this? I've searched a lot, but I can't find it, There is no straight way!
4. What is SuperCID?! Should I do this?! How?
5. As you see my phone's build number shows it's not Europe version. It's for Korea I think. How can I find original Rom if there's a problem?
Sorry if I'm wrong by making a thread for this questions.
Finally, Thank you very very much!
M8x is the Taiwan variant. Its identical to other "GSM" M8 versions in hardware, but its CPU is clocked higher.
Most mods for the other "GSM" versions will work (root, custom ROMs, and many more). However it has been found some things are not cross-compatible, such as firmware (in particular radio) from other M8 versions will not work on the M8x.
salah_erosennin said:
1. Can I Root and S-OFF Android 5?! Is there any problem with this?
2. What Recovery do you suggest for me?
3. May you give me a link for this? I've searched a lot, but I can't find it, There is no straight way!
4. What is SuperCID?! Should I do this?! How?
5. As you see my phone's build number shows it's not Europe version. It's for Korea I think. How can I find original Rom if there's a problem?
Click to expand...
Click to collapse
1) Unlock the bootloader, and root should be fine.
You should be able to s-off by sunshine. The sunshine app will check first to see if your phone is compatible, and you won't be charged ($25) if your version is not compatible. So no harm in checking first. But according to the following thread, sunshine should work (see near the end of thread): http://forum.xda-developers.com/showthread.php?t=2738509
Although it should be noted that s-off is not strictly needed for root, custom ROMs, and many other things. And the usefulness of s-off is likely limited for your version, anyway; as some of the main reasons for s-off would be to flash another versions radio or other firmware (and as mentioned previously, this won't work for the M8x).
2) TWRP is the only currently updated custom recovery for this device. Use version 2.8.4 or later based on the thread linked it Item 1 above. Older versions are likely to cause issues.
3) Here you go: https://twrp.me/devices/htconem8gsm.html
4) SuperCID will "pass" any CID check for HTC software updates or other "official" HTC files. But seeing as the main reason for changing the CID would be to install another versions firmware or RUU (and as previously discussed, this won't work on your M8x), I would say you don't need it.
Once the phone is s-off, you can make the phone SuperCID with a single fastboot command.
5) Not Korean, as mentioned the M8x is from Taiwan. I can't find the stock nandroid for your version. But after you unlock the bootloader, you backup the stock recovery and stock ROM with TWRP.
redpoint73 said:
M8x is the Taiwan variant. Its identical to other "GSM" M8 versions in hardware, but its CPU is clocked higher.
Most mods for the other "GSM" versions will work (root, custom ROMs, and many more). However it has been found some things are not cross-compatible, such as firmware (in particular radio) from other M8 versions will not work on the M8x.
1) Unlock the bootloader, and root should be fine.
You should be able to s-off by sunshine. The sunshine app will check first to see if your phone is compatible, and you won't be charged ($25) if your version is not compatible. So no harm in checking first. But according to the following thread, sunshine should work (see near the end of thread): http://forum.xda-developers.com/showthread.php?t=2738509
Although it should be noted that s-off is not strictly needed for root, custom ROMs, and many other things. And the usefulness of s-off is likely limited for your version, anyway; as some of the main reasons for s-off would be to flash another versions radio or other firmware (and as mentioned previously, this won't work for the M8x).
2) TWRP is the only currently updated custom recovery for this device. Use version 2.8.4 or later based on the thread linked it Item 1 above. Older versions are likely to cause issues.
3) Here you go: https://twrp.me/devices/htconem8gsm.html
4) SuperCID will "pass" any CID check for HTC software updates or other "official" HTC files. But seeing as the main reason for changing the CID would be to install another versions firmware or RUU (and as previously discussed, this won't work on your M8x), I would say you don't need it.
Once the phone is s-off, you can make the phone SuperCID with a single fastboot command.
5) Not Korean, as mentioned the M8x is from Taiwan. I can't find the stock nandroid for your version. But after you unlock the bootloader, you backup the stock recovery and stock ROM with TWRP.
Click to expand...
Click to collapse
Thank you very very much for your help. That's a complete guide.
So long story short, I messed up and wiped my OS off my phone via TRWP. After reinstalling and looking/asking around on the forums, I managed to reinstall it, but the WiFi is no longer working. Then after some more looking/asking, I gave up and sent in to a store for repairs. It came back and the guy said he couldn't do anything to fix it.
So... now I'm here asking again. Does anyone have any idea how to fix this?
Here's an image of my bootloader
http://imgur.com/SswEXd2
As you can see, the OS- is blank. I'm not sure if that's normal or not, but I'm 99% sure that there's supposed to be some code following OS-
You likely flashed a ROM that is a different version from what you had before, and does not match your firmware (hboot, radio, WiFi, etc. - modules that do NOT get updated when you flash a ROM).
Your hboot goes with Android 4.4.3, or software number 2.x. So flash a stock or custom ROM based on software 2.x, and WiFi should work again.
You likely flashed a ROM based on Android 4.4.4 or 5.0, and therefore no WiFi.
And no OS number listed on hboot screen is a common bug found on older TWRP versions.
Which ROM do you recommend?
Xenosaki said:
Which ROM do you recommend?
Click to expand...
Click to collapse
Most custom Sense ROMs based on software 2.xx should work.
You might also be able to use 1.xx software based ROMs, as well. Firmware is usually "backwards compatible" (with older ROMs) but never forwards compatible.
Also, next time make a backup of your stock ROM. One of the great things you can do once you have TWRP installed.
redpoint73 said:
Most custom Sense ROMs based on software 2.xx should work.
You might also be able to use 1.xx software based ROMs, as well. Firmware is usually "backwards compatible" (with older ROMs) but never forwards compatible.
Also, next time make a backup of your stock ROM. One of the great things you can do once you have TWRP installed.
Click to expand...
Click to collapse
I'm looking for a 2.xx rom right now.
Also, another question, could I update the firmware without flashing the ROM first? Or do I need to do that prior to updating the firmware?
EDIT: I'm unable to find a sense 2.xx for the HTC ONE M8. Or does the phone type not matter as long as it's a sense 2.xx?
What's your device CID & MID ?
ckpv5 said:
What's your device CID & MID ?
Click to expand...
Click to collapse
How would I go about finding it?
Xenosaki said:
I'm looking for a 2.xx rom right now.
Also, another question, could I update the firmware without flashing the ROM first? Or do I need to do that prior to updating the firmware?
EDIT: I'm unable to find a sense 2.xx for the HTC ONE M8. Or does the phone type not matter as long as it's a sense 2.xx?
Click to expand...
Click to collapse
No. You want to update the firmware first. You should also update your recovery before flashing the new firmware. Then your OS won't be blank anymore (after you flash new firmware).
If you want a 2.xx based ROM,. you could try ViperOneM8 2.5.0
It's a solid Sense based ROM with a lot of customization options.
---------- Post added at 05:12 PM ---------- Previous post was at 05:08 PM ----------
Xenosaki said:
How would I go about finding it?
Click to expand...
Click to collapse
Find it by hooking up to your PC, getting into ADB/fastboot and entering fastboot getvar all
The CID is listed as CID
The MID is listed as modelid
Xenosaki said:
I'm looking for a 2.xx rom right now.
Also, another question, could I update the firmware without flashing the ROM first? Or do I need to do that prior to updating the firmware?
Click to expand...
Click to collapse
You're talking about 2 different approaches now. You can either:
1) Flash a ROM that is supported by your (2.xx) firmware.
2) Update the firmware that matches your current ROM (but not sure what version that would be).
You don't need to do both (flash new firmware and flash a 2.xx ROM). Although you can, as long the ROM is supported by the firmware (otherwise you will still have broken WiFi and possibly other severe bugs).
Also, keep in mind that if you are s-on, you can only flash a firmware that is signed and corresponds with your CID.
Xenosaki said:
I'm looking for a 2.xx rom right now.
EDIT: I'm unable to find a sense 2.xx for the HTC ONE M8. Or does the phone type not matter as long as it's a sense 2.xx?
Click to expand...
Click to collapse
It absolutely matters. NEVER EVER EVER flash a ROM meant for another device. If you are s-on, it probably won't flash anyway. But if it does, it either won't work, or may even brick your device.
You likely just didn't browse back far enough (or didn't use the proper search string, if you used the XDA search function) to find a 2.xx based ROM for the M8. ROM base 2.xx is pretty old, so I see a couple started on Page 5 of 7 in the M8 Development section. What I see are:
http://forum.xda-developers.com/showthread.php?t=2702765
http://forum.xda-developers.com/showthread.php?t=2794008
redpoint73 said:
You're talking about 2 different approaches now. You can either:
1) Flash a ROM that is supported by your (2.xx) firmware.
2) Update the firmware that matches your current ROM (but not sure what version that would be).
You don't need to do both (flash new firmware and flash a 2.xx ROM). Although you can, as long the ROM is supported by the firmware (otherwise you will still have broken WiFi and possibly other severe bugs).
Also, keep in mind that if you are s-on, you can only flash a firmware that is signed and corresponds with your CID.
It absolutely matters. NEVER EVER EVER flash a ROM meant for another device. If you are s-on, it probably won't flash anyway. But if it does, it either won't work, or may even brick your device.
You likely just didn't browse back far enough (or didn't use the proper search string, if you used the XDA search function) to find a 2.xx based ROM for the M8. ROM base 2.xx is pretty old, so I see a couple started on Page 5 of 7 in the M8 Development section. What I see are:
http://forum.xda-developers.com/showthread.php?t=2702765
http://forum.xda-developers.com/showthread.php?t=2794008
Click to expand...
Click to collapse
Sorry if I'm asking too many questions. If I go with the updating the firmware route first, do I have to do anything specific? Like for example update from 2.x.x -> 5.0. Or does it not matter what version I'm currently on to update to 5.0. Also, I'm seeing a lot of issues concerning which carrier the phone is from. Is there a way to check that? I *think* mine might be some asian branded version, but I'm unsure.
Also, I'm checking the phone's firmware and it's saying that it's 4.4.4. http://imgur.com/rbLpjl1
All the pic info you provided not really can give proper help.
I'm asking again, maybe for the last time .. what's your device CID & MID ?
Xenosaki said:
Sorry if I'm asking too many questions. If I go with the updating the firmware route first, do I have to do anything specific? Like for example update from 2.x.x -> 5.0. Or does it not matter what version I'm currently on to update to 5.0. Also, I'm seeing a lot of issues concerning which carrier the phone is from. Is there a way to check that? I *think* mine might be some asian branded version, but I'm unsure.
Click to expand...
Click to collapse
It absolutely matters what firmware you pick and whether or not it corresponds to your CID. For one thing, with s-on, you can only flash the firmware for your CID, plus the firmware has to be signed.
Another thing, the firmware will update your radio baseband version. So if you flash firmware for a different CID, you may change the band support, and find you no longer have 3G or 4G connection (depending on what firmware you flash, what bands used by your local carrier, etc.).
Also, don't confuse software version with Android version (you've mixed the 2 together above). The Android version is Google's numbering scheme. Software number is HTC's numbering scheme.
Software version 2.xx corresponds to Android version 4.4.3.
Android version 5.0 (Lollipop) corresponds to software version 4.xx.
Its been requested a couple times now that you do adb getvar all to determine your CID and MID. We can't help if you are guessing or don't know the carrier version.
Xenosaki said:
Also, I'm checking the phone's firmware and it's saying that it's 4.4.4. http://imgur.com/rbLpjl1
Click to expand...
Click to collapse
The photo has nothing to do with your firmware number. The firmware number is best determined with adb getvar all, and is displayed as "main version".
What your picture shows simply means the ROM you flashed is based on Android 4.4.4, and software 3.28.401. The software number of the ROM is completely different from your present firmware number; and the very reason why your WiFi is broken.
I've already determined from the pic in your first post that your firmware is 2.xx (corresponding to Android 4.4.3). To get the more specific numbers (after the "2") you need to do adb getvar all.
Also, if you post the getvar output, be sure to delete your IMEI and serial number, as these are private info.
ckpv5 said:
All the pic info you provided not really can give proper help.
I'm asking again, maybe for the last time .. what's your device CID & MID ?
Click to expand...
Click to collapse
redpoint73 said:
It absolutely matters what firmware you pick and whether or not it corresponds to your CID. For one thing, with s-on, you can only flash the firmware for your CID, plus the firmware has to be signed.
Another thing, the firmware will update your radio baseband version. So if you flash firmware for a different CID, you may change the band support, and find you no longer have 3G or 4G connection (depending on what firmware you flash, what bands used by your local carrier, etc.).
Also, don't confuse software version with Android version (you've mixed the 2 together above). The Android version is Google's numbering scheme. Software number is HTC's numbering scheme.
Software version 2.xx corresponds to Android version 4.4.3.
Android version 5.0 (Lollipop) corresponds to software version 4.xx.
Its been requested a couple times now that you do adb getvar all to determine your CID and MID. We can't help if you are guessing or don't know the carrier version.
The photo has nothing to do with your firmware number. The firmware number is best determined with adb getvar all, and is displayed as "main version".
What your picture shows simply means the ROM you flashed is based on Android 4.4.4, and software 3.28.401. The software number of the ROM is completely different from your present firmware number; and the very reason why your WiFi is broken.
I've already determined from the pic in your first post that your firmware is 2.xx (corresponding to Android 4.4.3). To get the more specific numbers (after the "2") you need to do adb getvar all.
Also, if you post the getvar output, be sure to delete your IMEI and serial number, as these are private info.
Click to expand...
Click to collapse
Not sure if I got the right ones, but here you go. Let me know if I didn't do it right.
http://imgur.com/a/C8hcK#0
The first picture is getting the CID and MID by following some guide off of google, so I don't know if that's right or not.
The second and third picture are the adb getvar all that you suggested me doing.
See ... you're on T-Mobile network but your device is not a TMOB and not a EU but a TW device.
CID HTC__621
MID 0P6B11000
This is my suggestion to fix whatever problem you have currently (without S-Off).
1. Restore 2.22.709.3 TWRP backup as your device hboot is 3.18.0000
2. install 2.22.709.3 stock recovery after restore
3. do multiple OTA to the latest lollipop version : 2.22.709.3 --> 3.28.709.6 --> 4.16.709.9 --> 4.24.709.2
4. Then if you like to install custom ROM, install TWRP again and install any custom ROM that you like - now you should not have any wifi problem
All the needed files / how-to is here : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You guys are absolutely amazing. Thank you so much for the help and patience. I followed all the steps (except for the multiple OTA updates, which I'm in the process of right now) and the wifi problem seems to be fixed.
On an off note, does it matter that in the bootloader, it says
*** Software status: Modified ***
*** UNLOCKED ***
?
And should I go through the process of S-Off-ing my phone? Does it benefit me to do it?
Again, thank you so much
Xenosaki said:
I followed all the steps (except for the multiple OTA updates, which I'm in the process of right now) and the wifi problem seems to be fixed.
On an off note, does it matter that in the bootloader, it says
*** Software status: Modified ***
*** UNLOCKED ***
?
Click to expand...
Click to collapse
UNLOCKED is fine. OTAs will install whether its locked or not. Better to leave it as-is (relocking only needed and recommended to run RUU or signed firmware zip).
The software modified flag is a bit puzzling. It usually indicated the ROM has been modified. If you installed the stock TWRP backup for your CID, it shouldn't say this. And software modified will prevent OTA from installing.
Are you sure you installed the stock TWRP backup (exactly correct software number) that ckpv5 indicated?
Xenosaki said:
And should I go through the process of S-Off-ing my phone? Does it benefit me to do it?
Click to expand...
Click to collapse
It depends on what you want to do with the phone. For most things (root, flashing custom ROMs, kernels, etc.), s-off is not needed. But it can be handy if you want to flash radios, modified hboots, convert to another CID or MID, and some other things.
---------- Post added at 10:22 AM ---------- Previous post was at 10:18 AM ----------
Xenosaki said:
The second and third picture are the adb getvar all that you suggested me doing.
Click to expand...
Click to collapse
The pics do not show the expected output for adb getvar all.
My guess is that you tried to run the commands same as the other (fastboot) commands, while in fastboot mode. adb commands can only be run while booted into OS (and with Debugging enabled in phone settings) or in recovery. Only fastboot commands work in fastboot mode.
redpoint73 said:
The software modified flag is a bit puzzling. It usually indicated the ROM has been modified. If you installed the stock TWRP backup for your CID, it shouldn't say this. And software modified will prevent OTA from installing.
Are you sure you installed the stock TWRP backup (exactly correct software number) that ckpv5 indicated?
Click to expand...
Click to collapse
That's the same as "TAMPERED" on hboot 3.18.0000 as seen on his first screenshot.
MODIFIED is on hboot 3.19.0000
That usually come after the bootloader is unlocked.
That can be change on S-Off device.
I installed the Venom ROM so that's probably the reason why it's showing that then. Thanks for everything guys
Morning guys,
I have had many Android phones and loved that I was able to flash custom ROMs and tweak bits. I got rid of my LG G2 some time ago for the HTC One M8 and I feel a little lost. I can't flash a custom ROM because it has S-OFF and there's no way I'm paying a third party to remove this.
Is there any way around this so I can keep playing? Otherwise, I might as well have got a darn iPhone.
Kind regards,
Chris
There is no need to S-Off to flash custom ROMs.
What you need :
Bootloader unlocked using HTCDev unlock_code.bin
latest firmware of your M8 region that read 4.xx.xxx.x
latest TWRP
That's all then you're good to install custom ROMs.
Ahh I have done all of that. But I was under the impression that I need to be S-OFF'ed?
You need S-Off if you want to change firmware of other M8 region to your device (which is not necessary) or to update yours without going HTC way i.e doing OTA.
Another important note, your device is not a China M8 like M8_TL but a M8_UL or M8_UL_CA to flash the Intl GSM Custom ROMs that you can find here : http://forum.xda-developers.com/htc-one-m8/development
Good luck ... it's not comfortable to use this forum format ..
No. Mine is the standard UK HTC One M8. I would just like to try out CyanogenMod and clear out some of the pre-installed HTC apps that I don't use.
Your firmware must be on 4.16.401.10 or 4.16.401.13 then you're good.
To remove some pre-installed HTC apps you need root which comes pre-installed with custom ROMs and custom kernel which usually has write protection disabled.
Gotta go now ... give any custom ROM a try .. you'll understand better
Nope, my firmware is on 4.20.771.2. Does that matter sorry?
That's H3G and that's good enough.
Thank you for all your help!!!
Hi,good afternoon,my friend brought me his HTC one m9,because i have experience with these things, i have flashed many devices of different brands but this is my first HTC device.
Well the problem is this:
He unlocked the botloader,installed TWRP ,super SU.zip (via twrp) and a custom rom with s-on,after that he lost signal,the phone does not have imei and baseband is uknown.
I've searched trough xda ,before posting this,so i came across with a thread that said that the phone can recover signal flashing a custom rom and a kernel,did that with no success. And also i've read that returning the bootloader to locked status,will allow me to flash a RUU file in order to get back to stock.
So, i relocked the bootloader,using CMD, but now the phone just boots into bootloader ,i can enter download mode aswell,but its stucked there.
Phone is recognized by windows,via fastboot.
So,the phone status is bootloader relocked,and s-on.
i´ve tried flashing the RUU via sdcard on download mode and gives me error,also i tried using fastboot commands and the result is the same,i can not flash the RUU file.
Any suggestions are very apreciated. Thanks fot your time.
kalel29 said:
Hi,good afternoon,my friend brought me his HTC one m9,because i have experience with these things, i have flashed many devices of different brands but this is my first HTC device.
Well the problem is this:
He unlocked the botloader,installed TWRP ,super SU.zip (via twrp) and a custom rom with s-on,after that he lost signal,the phone does not have imei and baseband is uknown.
I've searched trough xda ,before posting this,so i came across with a thread that said that the phone can recover signal flashing a custom rom and a kernel,did that with no success. And also i've read that returning the bootloader to locked status,will allow me to flash a RUU file in order to get back to stock.
So, i relocked the bootloader,using CMD, but now the phone just boots into bootloader ,i can enter download mode aswell,but its stucked there.
Phone is recognized by windows,via fastboot.
So,the phone status is bootloader relocked,and s-on.
i´ve tried flashing the RUU via sdcard on download mode and gives me error,also i tried using fastboot commands and the result is the same,i can not flash the RUU file.
Any suggestions are very apreciated. Thanks fot your time.
Click to expand...
Click to collapse
For download mode SD card method:
Make sure you're using an external SD card, not internal storage.
Make sure SD card is formatted properly.
Make sure file is named 100% correctly and is meant for that specific carrier /model.
No reason it shouldn't work.
Sent from my HTC6545LVW using Tapatalk
kalel29 said:
i´ve tried flashing the RUU via sdcard on download mode and gives me error,also i tried using fastboot commands and the result is the same,i can not flash the RUU file.
Click to expand...
Click to collapse
Are you sure you flashed the correct one? Some basic information about firmware versions, RUUs and instructions how to flash them can be found in my sticky thread in the general section.
Concerning the reception problem: It's important whether you tried to use a sense-based custom rom or a non-sense-based one. The mono-kernel only works with non-sense roms like CM or Candysix. Moreover the reception problem has been covered in this thread some days ago. If you want to use a sense-based rom the re-flash boot.img "trick" might be working for you, too.
Sidenote: There is absolutely no need for flashing SuperSU if you are going to erase the system and to flash a custom com. It doesn't harm the device but it's a waste of time.
Flippy498 said:
Are you sure you flashed the correct one? Some basic information about firmware versions, RUUs and instructions how to flash them can be found in my sticky thread in the general section.
Concerning the reception problem: It's important whether you tried to use a sense-based custom rom or a non-sense-based one. The mono-kernel only works with non-sense roms like CM or Candysix. Moreover the reception problem has been covered in this thread some days ago. If you want to use a sense-based rom the re-flash boot.img "trick" might be working for you, too.
Sidenote: There is absolutely no need for flashing SuperSU if you are going to erase the system and to flash a custom com. It doesn't harm the device but it's a waste of time.
Click to expand...
Click to collapse
Yes I flashed the one for my operator. Can I flash another RUU?
About your links, I'll check them when I get back from work. Thanks.
Is your phone branded by your carrier? (Can be checked by looking at the SKU of the currently installed firmware.) If not then it's the wrong RUU. Is the RUU made for the same firmware version as the one that is currently installed on the phone or does the RUU even have a newer version? If not then it's the wrong RUU.
Flippy498 said:
Is your phone branded by your carrier? (Can be checked by looking at the SKU of the currently installed firmware.) If not then it's the wrong RUU. Is the RUU made for the same firmware version as the one that is currently installed on the phone or does the RUU even have a newer version? If not then it's the wrong RUU.
Click to expand...
Click to collapse
Hi again, the phone is giving me this error :
im still lost ,hope this helps to point me in the right direction.
Code:
D:\Francisco\Desktop\HTC\fastboot_adb\fastboot_adb>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 3.44.600.1
(bootloader) boot-mode: RUU
(bootloader) version-baseband: 01.01_U11440801_97.04.60111G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: HTC__332
all:
finished. total time: 0.033s
Thanks
You still didn't mention the name of the RUU you wanted to flash. However a quick search for your SKU (Telcel Mexico) showed me that there is no RUU available you could use. The only one I could find is linked in my thread and that one is too old for your phone since you can't downgrade the firmware with S-ON. You either need to re-unlock the bootloader, flash a sense-based custom rom and buy the sunshine app or try to find someone who has a java card. Both solutions would set the phone S-OFF so that you would be able to use that old RUU. Alternatively you could contact Llabtoofer (a link can be found in my thread and in my google sheet). He has a RUU service with RUUs that are not available publicly*. Neither the sunshine app, nor a java nor the RUU service are for free. Llabtoofer and the sunshine app cost nearly the same. I don't know how much you need to pay for java card services. Be aware that even if it's OK if the phone is running a custom right now** and you don't want to use any of these solutions that you still lack a way back to stock if a new OTA (like the one for Android N) gets distributed and therefore you won't be able to install it.
If you use the old RUU all OTAs that got installed on your phone will need to get re-installed.
However you choose you should read the tab "make your own backup" of my sheet after the phone got recovered and all available OTAs got installed but before anyone starts flashing anything, again. This way you will learn how to create a backup that will help you out if you face such a situation, again. Instructions how to restore such a backup correctly can be found in the tab "twrp backups".You'll always need to create a new backup when a new OTA got installed on your phone and you want to re-root it. Besides if you're willing you could upload the backup (and any upcoming ones) and share it(/them) with the xda community by posting the download link(s) in my thread.
* He wants to know the hboot version of your phone of you request his help. Since the One M9 has no hboot but an aboot and that one never got updated you can enter version 1.0.0.0000. That's the current aboot version.
** Possible solutions for recovering the reception can be found in my first post in this thread. There is no need to flash a RUU since your IMEI and your baseband are still intact but the boot.img of the rom you tried to use was/is incompatible.
Flippy498 said:
You still didn't mention the name of the RUU you wanted to flash. However a quick search for your SKU (Telcel Mexico) showed me that there is no RUU available you could use. The only one I could find is linked in my thread and that one is too old for your phone since you can't downgrade the firmware with S-ON. You either need to re-unlock the bootloader, flash a sense-based custom rom and buy the sunshine app or try to find someone who has a java card. Both solutions would set the phone S-OFF so that you would be able to use that old RUU. Alternatively you could contact Llabtoofer (a link can be found in my thread and in my google sheet). He has a RUU service with RUUs that are not available publicly*. Neither the sunshine app, nor a java nor the RUU service are for free. Llabtoofer and the sunshine app cost nearly the same. I don't know how much you need to pay for java card services. Be aware that even if it's OK if the phone is running a custom right now** and you don't want to use any of these solutions that you still lack a way back to stock if a new OTA (like the one for Android N) gets distributed and therefore you won't be able to install it.
If you use the old RUU all OTAs that got installed on your phone will need to get re-installed.
However you choose you should read the tab "make your own backup" of my sheet after the phone got recovered and all available OTAs got installed but before anyone starts flashing anything, again. This way you will learn how to create a backup that will help you out if you face such a situation, again. Instructions how to restore such a backup correctly can be found in the tab "twrp backups".You'll always need to create a new backup when a new OTA got installed on your phone and you want to re-root it. Besides if you're willing you could upload the backup (and any upcoming ones) and share it(/them) with the xda community by posting the download link(s) in my thread.
* He wants to know the hboot version of your phone of you request his help. Since the One M9 has no hboot but an aboot and that one never got updated you can enter version 1.0.0.0000. That's the current aboot version.
** Possible solutions for recovering the reception can be found in my first post in this thread. There is no need to flash a RUU since your IMEI and your baseband are still intact but the boot.img of the rom you tried to use was/is incompatible.
Click to expand...
Click to collapse
Ok,thanks, and yes,the RUU I was trying to flash I the telcel one.
I'm going to tell my fiend that he needs to pay in order to get his phone working.
Thanks again for everything. Have a nice day.
Update
I managed to unlock the bootloader again, the phone boots, but it has no signal.
Do I need sunshine and then flash any ruu?
Or what can I do? BTW my friend agreed to pay for sunshine.
kalel29 said:
Update
I managed to unlock the bootloader again, the phone boots, but it has no signal.
Do I need sunshine and then flash any ruu?
Or what can I do? BTW my friend agreed to pay for sunshine.
Click to expand...
Click to collapse
Is it a sense-based rom? If yes, did you reflash the stock boot.img? Or is it a non-sense-based rom? In that case the mono kernel which is linked above needs to be flashed for recovering the reception.
If you're currently using a sense-based rom (which is not an HTC 10 port - e.g. Viper one m9 4.3) then you can install the sunshine app and start it. The app will explain the rest of the procedure. Just google "sunshine s-off" and you'll find it. After your phone got S-OFF you simply need to try reflashing the RUU.
Flippy498 said:
Is it a sense-based rom? If yes, did you reflash the stock boot.img? Or is it a non-sense-based rom? In that case the mono kernel which is linked above needs to be flashed for recovering the reception.
If you're currently using a sense-based rom (which is not an HTC 10 port - e.g. Viper one m9 4.3) then you can install the sunshine app and start it. The app will explain the rest of the procedure. Just google "sunshine s-off" and you'll find it. After your phone got S-OFF you simply need to try reflashing the RUU.
Click to expand...
Click to collapse
The phone has the ICE rom,Twrp and superSU,I think it's a sense-based rom, sorry I can't give you more info, as I said I'm new in flashing HTC, but I'm learning thanks to you.
ICE is sense-based. It's using HTCs own launcher and framework which is called Sense. Examples for non-sense-based roms are CM, CandySix or other AOSP roms.
Depending on the version of ICE that got flashed on the phone you might need to revert back to an older version*. The newest ICE rom is based on an HTC 10 port and I've read several posts of users reporting that they couldn't use sunshine with an HTC 10 port.
* I don't know which version that would be. I've never used ICE so you would need to figure that out on your own.
Flippy498 said:
ICE is sense-based. It's using HTCs own launcher and framework which is called Sense. Examples for non-sense-based roms are CM, CandySix or other AOSP roms.
Depending on the version of ICE that got flashed on the phone you might need to revert back to an older version*. The newest ICE rom is based on an HTC 10 port and I've read several posts of users reporting that they couldn't use sunshine with an HTC 10 port.
* I don't know which version that would be. I've never used ICE so you would need to figure that out on your own.
Click to expand...
Click to collapse
So basically, no matter what rom I flash,sense or no sense based, I will need sunshine in order to have a working baseband?
No. Sunshine is needed for getting back to stock for installing upcoming OTAs. And in case you want to use a sense-based roms it's needed for being able to backup the stock boot.img. As explained before, you need to re-flash that one after you flashed the custom rom. The boot.img of 3.35.y (y is a placeholder for any possible number) custom roms isn't compatible with 3.x firmware if x is not equal to 35 (as in your case). At the moment your only option for not having to use sunshine would be flashing a non-sense-based rom and the kernel I linked in an earlier post. But as explained before you wouldn't be able to install upcoming updates like the one for Android N if you choose not to use sunshine.
Flippy498 said:
No. Sunshine is needed for getting back to stock for installing upcoming OTAs. And in case you want to use a sense-based roms it's needed for being able to backup the stock boot.img. As explained before, you need to re-flash that one after you flashed the custom rom. The boot.img of 3.35.y (y is a placeholder for any possible number) custom roms isn't compatible with 3.x firmware if x is not equal to 35 (as in your case). At the moment your only option for not having to use sunshine would be flashing a non-sense-based rom and the kernel I linked in an earlier post. But as explained before you wouldn't be able to install upcoming updates like the one for Android N if you choose not to use sunshine.
Click to expand...
Click to collapse
Finally i have signal again,flashed slim 6 and monokernel. Thank you so much,i've learned something new about HTC now im going to return the phone to my friend,also i explained what you told me in order to have a sense based rom.