Unknown Imei and basebandm, and find a way to get back to stock. - AT&T HTC One (M7)

So here's a little bit of context first:
1-This is a friend's phone
2-The data partion corrupted on its own
3-I unlocked the bootloader
4-Flashed twrp
5-Formatted data partition through adb
6-Flashed cm11 normally
Now the phone network doesnt want to work and both the imei and baseband show up as unknown even though they show up normally with the command "fastboot getvar all" .
I've tried restoring to this backup http://forum.xda-developers.com/showthread.php?t=2775650 but it kept crashing and rebooting and it had the same imei and baseband problem so i went back to cm11.
Any ideas?

tinclan said:
So here's a little bit of context first:
1-This is a friend's phone
2-The data partion corrupted on its own
3-I unlocked the bootloader
4-Flashed twrp
5-Formatted data partition through adb
6-Flashed cm11 normally
Now the phone network doesnt want to work and both the imei and baseband show up as unknown even though they show up normally with the command "fastboot getvar all" .
I've tried restoring to this backup http://forum.xda-developers.com/showthread.php?t=2775650 but it kept crashing and rebooting and it had the same imei and baseband problem so i went back to cm11.
Any ideas?
Click to expand...
Click to collapse
If imei and baseband are missing in Settings it is a sign that it is a hardware issue and will cause a host of problems. If under warranty you can return to carrier or HTC for repair. However, since you unlocked the bootloader and I would guess it is S-ON you will not be able to return it to 100% stock for a warranty repair. You can still return it but will have to pay for the repair.

majmoz said:
If imei and baseband are missing in Settings it is a sign that it is a hardware issue and will cause a host of problems. If under warranty you can return to carrier or HTC for repair. However, since you unlocked the bootloader and I would guess it is S-ON you will not be able to return it to 100% stock for a warranty repair. You can still return it but will have to pay for the repair.
Click to expand...
Click to collapse
Omg man that's totally not the response I wanted to hear. What about the fact that the iemi and baseband show up fine using the "fastboot getvar all" command? And BTW I only unlocked the bootloader when the data partition corrupted, before I tried to unlock the bootloader HTC had already told my friend that they're gonna charge him $200 bucks to fix that issue and that wasn't really an option for him. Also, do you think the issue maybe because of corrupted firmware. I though that maybe if we werent able to fix the issue then I works just get s-off and run an ruu then try to remove the tampered banner and get back the bootloader states to "locked", what do you think?

tinclan said:
Omg man that's totally not the response I wanted to hear. What about the fact that the iemi and baseband show up fine using the "fastboot getvar all" command? And BTW I only unlocked the bootloader when the data partition corrupted, before I tried to unlock the bootloader HTC had already told my friend that they're gonna charge him $200 bucks to fix that issue and that wasn't really an option for him. Also, do you think the issue maybe because of corrupted firmware. I though that maybe if we werent able to fix the issue then I works just get s-off and run an ruu then try to remove the tampered banner and get back the bootloader states to "locked", what do you think?
Click to expand...
Click to collapse
It is worth a try to see if the firmware or RUU will fix the issue, however, if it is hardware then it will not.

majmoz said:
It is worth a try to see if the firmware or RUU will fix the issue, however, if it is hardware then it will not.
Click to expand...
Click to collapse
Thanks for replying! I will definitely try flashing the firmware and RUU before concluding that it's a hardware problem, but btw do you know if i need s-off to flash firmware for the same os version and same cid/mid or will it just check that it's compatible and overwrite the one already there?

tinclan said:
Thanks for replying! I will definitely try flashing the firmware and RUU before concluding that it's a hardware problem, but btw do you know if i need s-off to flash firmware for the same os version and same cid/mid or will it just check that it's compatible and overwrite the one already there?
Click to expand...
Click to collapse
If you are S-ON then RUU & firmware must be the same version or higher and signed. When you flash the firmware or RUU it will overwrite the partitions and it may wipe all of your data as well. So, if you can you will want to copy all of your data/files off of the phone prior to flashing the firmware or RUU.

majmoz said:
If you are S-ON then RUU & firmware must be the same version or higher and signed. When you flash the firmware or RUU it will overwrite the partitions and it may wipe all of your data as well. So, if you can you will want to copy all of your data/files off of the phone prior to flashing the firmware or RUU.
Click to expand...
Click to collapse
I really appreciate your help, I have one final question. If i extract the firmware from the official ota update then it's signed, right? Also, do i have to lock the bootloader, flash the stock recovery and have the stock sense ROM or if having the relocked bootloader and/or stock recovery enough?

tinclan said:
I really appreciate your help, I have one final question. If i extract the firmware from the official ota update then it's signed, right? Also, do i have to lock the bootloader, flash the stock recovery and have the stock sense ROM or if having the relocked bootloader and/or stock recovery enough?
Click to expand...
Click to collapse
Yes, the firmware in the OTA is signed.
Yes, you must lock your bootloader prior to flashing firmware or RUU if S-ON
If you flash the stock firmware it will include the stock recovery

majmoz said:
Yes, the firmware in the OTA is signed.
Yes, you must lock your bootloader prior to flashing firmware or RUU if S-ON
If you flash the stock firmware it will include the stock recovery
Click to expand...
Click to collapse
Thanks a lot for your help

Hi im Nissanka from srilankan
my phone is HTC One m7
my problem is IME Unknown
this problem is solution tell me please
Phone name
HTC One
IMEI
Unknown
IMEI SV
Unknown
Device serial number
FA42KWM01166
Phone number
Unknown
IMSI
Unavailable
IP address
Unavailable
Wi-Fi MAC address
e8.99.c4.86.72.45

Related

[Q] Help to unroot htconex+

Hi everyone, i 'm going to be concise. I own an HTC onex+ international version (it should be no brand) and i would like to unroot it and reset to factory for a warranty issue. I'm extremely noob so i would like, if it's possibile, the fastest, easyest and safest way to do so.
On internet i found several guides about it as http://onexroot.com/one-x-unroot/how-to-unroot-rooted-htc-one-x/ or http://theunlockr.com/2012/12/28/how-to-unroot-the-htc-one-x-2/ BUT i found also an xda tool http://forum.xda-developers.com/showthread.php?t=1870652&nocache=1 that sounds appropriate to me; i read on other forum that i need some kind of extra instrument like boot.img
There are some things to take note of. The boot.img and HBoot image flashing requires users to get their own files as those are device specific and aren’t included
Click to expand...
Click to collapse
actually i have no idea where get it and how use it. I would be very gratefull if some of you could explain to me step by step how to do the unroot.
ps. i just rooted and put inside the cmw under the instruction of friend of mine but i don't really understand how i did it.
thank you in advance.
relock bootloader and install RUU and you are back on Stock
but would you be back on stock for a warranty issue, you didn't must do that.
warranty has nothing to do with your firmware or root or bootloader unlock.
they would be erase all at your phone and flash the RUU
skdubg said:
relock bootloader and install RUU and you are back on Stock
Click to expand...
Click to collapse
thank you for your reply but the problem is that actually i don't know how to relock booloader and what RUU is; that's why i was lokking for a step by step guide. I may follow and understand a little the guide of before but i'm not safe that it works with htc onec+ too.
but would you be back on stock for a warranty issue, you didn't must do that.
warranty has nothing to do with your firmware or root or bootloader unlock.
Click to expand...
Click to collapse
really? i belived that an "unlocked" phone was an enough reason to invalidate the warranty isn't it?
kadakar said:
really? i belived that an "unlocked" phone was an enough reason to invalidate the warranty isn't it?
Click to expand...
Click to collapse
if you dont touch the bootloader it says: LOCKED
if you unlocked bootloader it says: UNLOCKED
if you relocked bootloader it says: RELOCKED
we can never go back to LOCKED (RELOCKED is technical the same like LOCKED, but it shows as RELOCKED) all people can see that the bootloader was touched by the user
so it cant the reason for that
to relock:
boot into bootloader
and execute this command in fastboot:
fastboot oem lock
now you can install your latest RUU (RUU is the Stock Firmware from HTC as *.exe to install from Windows [depends on your CID])

HELP How to return to stock rom

I need to know how to return to stock rom because after installing custom one my device reboots without any reason
Please how can I do to come back to stock one
Thanks
moudja said:
I need to know how to return to stock rom because after installing custom one my device reboots without any reason
Please how can I do to come back to stock one
Thanks
Click to expand...
Click to collapse
flash the stock using odin
odin is for samsung devices
moudja said:
I need to know how to return to stock rom because after installing custom one my device reboots without any reason
Please how can I do to come back to stock one
Thanks
Click to expand...
Click to collapse
You must find a RUU specific for your CID device (China, Europe, Asia/India, etc ... I don't know all), and then there is here http://forum.xda-developers.com/showthread.php?t=1706070 a guide how to do the rest - is for other device but the procedure is the same. Pay attention, your RUU have to start with these letters RUU_PRIMO_DS_ICS_40A..... and end with .....signed.exe
Only one thing: if you updated your radio and hboot before via OTA, I don't know if you can find a RUU with those versions and it may experience an error - it hapened to me. In that case you have to find a HTC service to revert to stock, and it will cost you because your warranty is void after bootloader unlock.
thanks
carliv said:
You must find a RUU specific for your CID device (China, Europe, Asia/India, etc ... I don't know all), and then there is here http://forum.xda-developers.com/showthread.php?t=1706070 a guide how to do the rest - is for other device but the procedure is the same. Pay attention, your RUU have to start with these letters RUU_PRIMO_DS_ICS_40A..... and end with .....signed.exe
Only one thing: if you updated your radio and hboot before via OTA, I don't know if you can find a RUU with those versions and it may experience an error - it hapened to me. In that case you have to find a HTC service to revert to stock, and it will cost you because your warranty is void after bootloader unlock.
Click to expand...
Click to collapse
thanks for the help:good:

Set Device to original firmware

Hello everyone
I hope someone can help me with this.
I have signal issues with my device, htc one x+, and thinking of sending it back as is still under warranty.
I have the revolution firmware on it and want to know how I can effectively set the original firmware on it so that I can then send it back.
Thank you
cpu2007 said:
Hello everyone
I hope someone can help me with this.
I have signal issues with my device, htc one x+, and thinking of sending it back as is still under warranty.
I have the revolution firmware on it and want to know how I can effectively set the original firmware on it so that I can then send it back.
Thank you
Click to expand...
Click to collapse
Depending on your devices bootloader (HBOOT) version and CID, you may be able to use an RUU to get back stock easily. If there's no matching RUU for your phone, you will have to search for stock backups and recovery matching your CID in order to apply stock HTC rom/firmware/recovery.
What is your bootloader version and CID?
reaper90 said:
Depending on your devices bootloader (HBOOT) version and CID, you may be able to use an RUU to get back stock easily. If there's no matching RUU for your phone, you will have to search for stock backups and recovery matching your CID in order to apply stock HTC rom/firmware/recovery.
What is your bootloader version and CID?
Click to expand...
Click to collapse
I don't know how to find the bootloader.
I found the CID using CID getter from the play store.
it shows it as : HTC__001
cpu2007 said:
I don't know how to find the bootloader.
I found the CID using CID getter from the play store.
it shows it as : HTC__001
Click to expand...
Click to collapse
reboot into bootloader (power off your phone and then press and hold power & volumedown button) there you can see your version number. If i remember right you need version 1.35 or lower to use a RUU, or your phone has to be S-OFF.
reaper90 said:
reboot into bootloader (power off your phone and then press and hold power & volumedown button) there you can see your version number. If i remember right you need version 1.35 or lower to use a RUU, or your phone has to be S-OFF.
Click to expand...
Click to collapse
This is what I see in the screen
Unlocked
ENRC2B_U PVT SHIP S-ON RL
HBOOT-1.30.0000
CPLD-None
MICROP-None
RADIO-3.1204.167.31
eMMC-bootmode:disabled
CPU-bootmode: disabled
HW secure boot:enabled
MODEM PATH: OFF
I've tried the following commands
adb bugreport | find "bootloader"
and I got this
6 un.ofs=362 androidboot.engid=0x
[ro.boot.bootloader]: [1.30.0000]
[ro.bootloader]: [1.30.0000]
http://www.androidruu.com/index.php?developer=ENRC2B
download the 1.17.401.1 RUU, it should work on your device. Make sure you backup all your stuff before using it, this will erase everything on your phone!!
reaper90 said:
http://www.androidruu.com/index.php?developer=ENRC2B
download the 1.17.401.1 RUU, it should work on your device. Make sure you backup all your stuff before using it, this will erase everything on your phone!!
Click to expand...
Click to collapse
Thank you, what information you've used to decide what RUU to use?
is that because 1.17 is the latest version and because they bootloeader and cid I've given you tell you that my phone is european and factory unlocked?
In addition:
I'm aware of a few methods that can be used to backup: Titanium,through adb,clockworld twrp but none of these does a full complete backup.
What's the best way to back up all the date so that all my messages,contacts,apps settings and messages(viber,skype logs and chats) can be restored once I have installed the stock firmware.
Can you also point out a simple guide that shows me how to install the stock firmware?
Thank you
cpu2007 said:
Thank you, what information you've used to decide what RUU to use?
is that because 1.17 is the latest version and because they bootloeader and cid I've given you tell you that my phone is european and factory unlocked?
In addition:
I'm aware of a few methods that can be used to backup: Titanium,through adb,clockworld twrp but none of these does a full complete backup.
What's the best way to back up all the date so that all my messages,contacts,apps settings and messages(viber,skype logs and chats) can be restored once I have installed the stock firmware.
Can you also point out a simple guide that shows me how to install the stock firmware?
Thank you
Click to expand...
Click to collapse
HTC__001 is a so called WWE (world wide edition) cid and i mostly read about people in europe having this, don't know what country exactly. and RUU is bound to certain cid and we only have those few RUUs for this device, so if someone does not have a matching cid for those RUUs you aren't able to use them. Also (as you've seen) your phone's bootloader is S-ON (Security-ON) like most people here have it, which means we're not allowed to do everything with our phones, for example we can't flash boot.img in recovery and we can't downgrade our bootloader version. This is the reason why i needed to know your bootloader version because the latest RUU we have is this 1.17.401.1 which includes bootloader 1.35 if i remember right. So if you had version 1.40 you wouldn't be able to use it because you can't downgrade bootloader version.
As for backup: I use titanium backup for all my user apps and app data (settings, savegames, chats, ...) and SMS Backup & Restore for sms backup.
But you also will need root to restore those backups.
To use the RUU, simply connect your phone to your computer and execute it. It should guide you to the process.
reaper90 said:
HTC__001 is a so called WWE (world wide edition) cid and i mostly read about people in europe having this, don't know what country exactly. and RUU is bound to certain cid and we only have those few RUUs for this device, so if someone does not have a matching cid for those RUUs you aren't able to use them. Also (as you've seen) your phone's bootloader is S-ON (Security-ON) like most people here have it, which means we're not allowed to do everything with our phones, for example we can't flash boot.img in recovery and we can't downgrade our bootloader version. This is the reason why i needed to know your bootloader version because the latest RUU we have is this 1.17.401.1 which includes bootloader 1.35 if i remember right. So if you had version 1.40 you wouldn't be able to use it because you can't downgrade bootloader version.
As for backup: I use titanium backup for all my user apps and app data (settings, savegames, chats, ...) and SMS Backup & Restore for sms backup.
But you also will need root to restore those backups.
To use the RUU, simply connect your phone to your computer and execute it. It should guide you to the process.
Click to expand...
Click to collapse
Thank you for explaining.
So I understand that if there's no a compatible RUU, it will not be possible to downgrade to the stock firmware, does this mean that after using custom rom, if I endup with a higher bootloader, I can't get back to my stock firmware but only change from one custom to another custom rom?
Where do these RUU come from? aren't they supplied by HTC, I mean if someone has a device with stock firmware but want's to flash his/her phone again, how would they do it? (for example in iphones you can get stock firmware for every phone)
Is it there a way to create a RUU when I have a stock firmware so that in case I need to revert back I can use that?
I'm on version 4.1.1 i guess, which i think isn't the latest version, after going stock firmware, if I upgrade, will i get my bootloader upgraded too?
sorry for too many questions
cpu2007 said:
Thank you for explaining.
So I understand that if there's no a compatible RUU, it will not be possible to downgrade to the stock firmware, does this mean that after using custom rom, if I endup with a higher bootloader, I can't get back to my stock firmware but only change from one custom to another custom rom?
Where do these RUU come from? aren't they supplied by HTC, I mean if someone has a device with stock firmware but want's to flash his/her phone again, how would they do it? (for example in iphones you can get stock firmware for every phone)
Is it there a way to create a RUU when I have a stock firmware so that in case I need to revert back I can use that?
I'm on version 4.1.1 i guess, which i think isn't the latest version, after going stock firmware, if I upgrade, will i get my bootloader upgraded too?
sorry for too many questions
Click to expand...
Click to collapse
Bootloader version is not rom version, custom roms won't update your bootloader. There's a difference between "firmware" and custom rom. you can update your phones firmware (bootloader etc.) with a cid matching "firmware.zip" from an OTA or RUU or on stock this is done automatically when applying OTA updates that include new versions of those. So if your bootloader version was too high, you can't use the RUU anymore and you have to get back to stock by using a stock TWRP/CWM backup and additionally flash stock recovery and boot.img and then relock your bootloader.
and yes RUUs are made by HTC, but there are no RUUs for latest software updates yet. either they don't exist or they're not leaked...
Your bootloader will probably be updatet to 1.35 if i remember right, but as long as the RUU includes the same version or a higher one, you're able to use it, so you can still use this RUU when used once.
just don't do OTA update to Sense 5/Android 4.2.2 or your bootloader will be upgraded to 1.72 and you won't be able to use any of those ruu again.
I just forgot one thing, I have linux at home, it's not possible to update through linux as it's an exe file.
is it there an alternative?
cpu2007 said:
I just forgot one thing, I have linux at home, it's not possible to update through linux as it's an exe file.
is it there an alternative?
Click to expand...
Click to collapse
I'm sry, as far as i know there's no way for RUU on linux. But i think i remember seeing a guide (either here at some xda forum or somewhere else on the internet) with a description on how to extract the stock rom and firmware.zip (which includes stock boot.img and recovery) from a RUU. So you could flash stock rom, boot.img and recovery and then relock bootloader, which should have the same effect. But i think you will need windows here too...
After running the RUU, it asked me to update the image, however it fails and it stays on the HTC black screen.
I've searched around and the way to install the RUU is to run it until the wizard windows open, search the temp folder and and a file in it called rom.zip.
extract the recovery or recovery_signed file from it and use fastboot command on the phone.
However when I try to extract the recovery_signed file, winrar says it's corrupt
how can I solve this or is it there another way to install the stock firmware?
my bad I had to fastboot oem lock
back to stock ,thank you!
is it there anything else I need to do in order to make sure that my phone is in the warranty guideline( i mean softwarewise)
Now I have got the phone fixed hopefully.
The phone details are as [email protected]
HTC ONE X+
android v: 4.2.2
htc sense version: 5.0
software num: 2.18.401.2
htc sdk api level: 5.41
How can I make a full backup of this stock firmware so if I decide to go back after using some custom firmwares, I can do so by restoring it back.
THank you
cpu2007 said:
Now I have got the phone fixed hopefully.
The phone details are as [email protected]
HTC ONE X+
android v: 4.2.2
htc sense version: 5.0
software num: 2.18.401.2
htc sdk api level: 5.41
How can I make a full backup of this stock firmware so if I decide to go back after using some custom firmwares, I can do so by restoring it back.
THank you
Click to expand...
Click to collapse
- unlock bootloader
- install custom recovery (CWM/TWRP)
- nandroid backup (all partitions)
You can restore this any time you need. Don't forget, you have to flash the boot/kernel backup separately in fastboot from your pc, so copy that backup to your computer once you have it.
BUT: if you want to go completely back to stock (relocked bootloader) you also need to flash stock recovery. i don't know how to dump stock recovery... maybe you can find some stock recovery.img for your version number here on xda or via google.
reaper90 said:
- unlock bootloader
- install custom recovery (CWM/TWRP)
- nandroid backup (all partitions)
You can restore this any time you need. Don't forget, you have to flash the boot/kernel backup separately in fastboot from your pc, so copy that backup to your computer once you have it.
BUT: if you want to go completely back to stock (relocked bootloader) you also need to flash stock recovery. i don't know how to dump stock recovery... maybe you can find some stock recovery.img for your version number here on xda or via google.
Click to expand...
Click to collapse
I have done all the steps but the one in bold is confusing me.
when you say flash boot/kernel separately ,you mean for the custom rom? how do I get the boot/kernel file to flash for my stock firmware?
I used TWRP to do a full backup, is nandroid backup necessary and what's the difference between that and TWRP backup?
cpu2007 said:
I have done all the steps but the one in bold is confusing me.
when you say flash boot/kernel separately ,you mean for the custom rom? how do I get the boot/kernel file to flash for my stock firmware?
I used TWRP to do a full backup, is nandroid backup necessary and what's the difference between that and TWRP backup?
Click to expand...
Click to collapse
nandroid backup = backup in custom recovery.
i mean if you want to restore your stock backup, you also have to flash the stock boot.img/kernel in fastboot because with S-ON phones we're not allowed to flash boot.img/kernel in recovery, hence we can't restore it using recovery restore function.
HTC ONE X+ RUU needed
Hi guys, i used to have a custom rom on my htc one x+ but now i want to put the stock RUU but i relocked and dicovered that my hboot is 1.40.0000 and my version-main is 1.17.401.3. So what can i do now?

"Unfortunately, AT&T Ready2Go has stopped." Is stuck looping on my phone.

"Unfortunately, AT&T Ready2Go has stopped." Is stuck looping on my phone.
About a year ago I rooted my phone, following these directions. (I can't yet post a link, but the first option on google when searching "how to root m8" is the site, htconeroot.com, that I used.)
This morning I noticed that my phone was not vibrating anymore no matter if I restarted the phone or what settings were applied. So I checked online to see if there was a fix, and a factory reset was recommended.
So when I got back from work today, I thought I had successfully uninstalled the root using SuperSU. Then I performed a factory reset. My phone then went into TWRP recovery which was alarming. So I rebooted the system from TWRP , then the message in the title kept popping up over and over again, so I am in a bit of a pickle. I can message and call at the moment but that is about it.
I'm thinking the problem is similar to this one someone had on a note 3, except I was trying to factory reset rather than update. http://forum.xda-developers.com/showthread.php?t=2663120
Has this happened to anyone else, and do you have any suggested fixes for resetting this phone???
Thanks in advance.
I've seen a number of cases on the M8 forums of various processes stopping with message "XXX has stopped" after a factory reset. Not sure what is causing this. But there are a variety of ways to recover.
Since you have TWRP, you can try to restore a TWRP backup of your own (if you made one) or install a stockish ROM. Those methods may be helpful if you want to retain or retrieve any personal data.
Otherwise, relock the bootloader and RUU back to full stock (RUU will wipe the phone).
redpoint73 said:
Otherwise, relock the bootloader and RUU back to full stock (RUU will wipe the phone).
Click to expand...
Click to collapse
Honestly I'd be fine returning to full stock, at least for the time being, to see if the vibration problem would fix itself. But do I need to be S-OFF for RUU?
eaflook said:
But do I need to be S-OFF for RUU?
Click to expand...
Click to collapse
No, and I wish folks would stop saying you need s-off to RUU (not you, but I assume you got this notion from another post/thread).
You can run the an RUU made for the AT&T M8, as long as you aren't "downgrading" to a previous version (such as Lollipop to Kitkat). For that, you need s-off; or to change the CID and run another carrier version RUU.
You do need to relock the bootloader to run RUU while s-on, with command: fastboot oem lock
Are you currently on LP or MM (what does it say for OS number on the bootloader screen)?
redpoint73 said:
No, and I wish folks would stop saying you need s-off to RUU (not you, but I assume you got this notion from another post/thread).
You can run the an RUU made for the AT&T M8, as long as you aren't "downgrading" to a previous version (such as Lollipop to Kitkat). For that, you need s-off; or to change the CID and run another carrier version RUU.
You do need to relock the bootloader to run RUU while s-on, with command: fastboot oem lock
Are you currently on LP or MM (what does it say for OS number on the bootloader screen)?
Click to expand...
Click to collapse
Um... the OS line on the bootloader screen looks blank, unless I'm looking in the wrong place.
Should I do this? http://forum.xda-developers.com/htc-one-m8/help/guide-how-to-solve-soft-brick-phone-t2824193
eaflook said:
Um... the OS line on the bootloader screen looks blank, unless I'm looking in the wrong place.
Click to expand...
Click to collapse
No, you're looking in the right place. Its somewhat common for OS number to be blank, its a known bug in older TWRP versions that it deletes the OS number.
What does it say for hboot number and radio number?
If the phone still on the stock ROM you originally rooted on? If so, is it Lollipop, Kitkat, etc.?
eaflook said:
U
Should I do this? http://forum.xda-developers.com/htc-one-m8/help/guide-how-to-solve-soft-brick-phone-t2824193
Click to expand...
Click to collapse
You can do that. All that "guide" describes is one way to get a ROM on an SD and flash it, which is one of the options I already suggested in Post #2 above.
But what ROM will work, somewhat depends on the info I requested above.
redpoint73 said:
What does it say for hboot number and radio number?
Click to expand...
Click to collapse
hboot number-3.19.0.0000
radio [email protected]
redpoint73 said:
If the phone still on the stock ROM you originally rooted on? If so, is it Lollipop, Kitkat, etc.?
Click to expand...
Click to collapse
Yes it is still on the stock root ROM. I am running Lollipop 5.0.2.
eaflook said:
hboot number-3.19.0.0000
radio [email protected]
Yes it is still on the stock root ROM. I am running Lollipop 5.0.2.
Click to expand...
Click to collapse
You should be fine flashing most any ROM on the AT&T or "international" M8 development forums. Just avoid other dev sections for variants, such as the Sprint or Verizon dev sections.
Before flashing a ROM, you may want to update your TWRP version to 3.0.whatever.
Although I have to admit, I'm still on TWRP 2.8.4, and its worked fine flashing LP and MM custom ROMs. Any older than 2.8.something may cause issues.
Alternately, relock bootloader and run RUU 4.28.502.2 (Lollipop). If you want to run the Marshmallow RUU (6.20.502.5), you'll need to flash the MM firmware first, then RUU. Link that describes that process, as well as all ATT RUUs is on my Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
redpoint73 said:
You should be fine flashing most any ROM on the AT&T or "international" M8 development forums. Just avoid other dev sections for variants, such as the Sprint or Verizon dev sections.
Before flashing a ROM, you may want to update your TWRP version to 3.0.whatever.
Although I have to admit, I'm still on TWRP 2.8.4, and its worked fine flashing LP and MM custom ROMs. Any older than 2.8.something may cause issues.
Alternately, relock bootloader and run RUU 4.28.502.2 (Lollipop). If you want to run the Marshmallow RUU (6.20.502.5), you'll need to flash the MM firmware first, then RUU. Link that describes that process, as well as all ATT RUUs is on my Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
Click to expand...
Click to collapse
Do you know how I might update TWRP from 2.7.0.2?-----Nevermind, I got it.
eaflook said:
Do you know how I might update TWRP from 2.7.0.2?-----Nevermind, I got it.
Click to expand...
Click to collapse
Good practice is to post what you did (or going to do) for the benefit of others that may have the same question; or so we can verify you are on the right track.
In case others may have the same question (or you get stuck again), all TWRP versions, and instructions (recommend install with fastboot method) are here: https://twrp.me/devices/htconem8gsm.html

Upgrading Software Issue.

Software up to date issue
HI all, just got this M8 and it is an ATT Version. but I believe it is unlocked because I am using it with cricket.
When trying to update Android Tells me software is up to date ?
Android version 5.0.2
HTC Sense Version 6.0
Software Number 4.28.502.1
HTC SDK API Level
I am pretty sure that ATT has updated to Marshmallow by now / So why can't I update? I am on wifi and 4G/LTE Could it be because I am using a Cricket Sim Card in the Phone ?
I have downloaded the RUU for Marshmallow software version 6.20.502.5. Should I continue with the Manual update ?
I believe this phone was originally purchased from ATT on May of 2016 if it makes any difference , figured I post it. since it could be a newer version of HTC M8.
Also is there a way to back up my current stock rom, without Rooting phone ? Thanks for all your help.
As I cannot root my phone, because when I go into developer option and search for S-off That option is not there and I can't Continue.
My responses below in red font:
ELEVO said:
HI all, just got this M8 and it is an ATT Version. but I believe it is unlocked because I am using it with cricket.
When trying to update Android Tells me software is up to date ?
I am pretty sure that ATT has updated to Marshmallow by now / So why can't I update? I am on wifi and 4G/LTE Could it be because I am using a Cricket Sim Card in the Phone ?
That is correct, the AT&t version (and most US versions) can only OTA update if connected to the proper branded carrier (AT&T in this case). Therefore, the RUU is your best option to update.
I have downloaded the RUU for Marshmallow software version 6.20.502.5. Should I continue with the Manual update ?
You can. But you need to flash the 6.20.502.5 firmware first, before you can flash the RUU. See instructions to flash the firmware here: https://forum.xda-developers.com/showpost.php?p=67123738&postcount=7
Then run the RUU. Keep in mind, that RUU will wipe the phone. So backup your data to an off-phone location (cloud, computer, etc.) before RUU.
Also is there a way to back up my current stock rom, without Rooting phone ? The current Lollipop ROM? No, there will be no way to revert to LP by official means, once you RUU to Marshmallow. I doubt you will find the need or desire to "downgrade" to obsolete LP version. If for some reason you did want to, there are options, but would require unlocking the bootloader (to install custom recovery and flash a Lollipop ROM), or s-off (which would allow you to "downgrade" by RUU - which is not allowed with s-on).
As I cannot root my phone, because when I go into developer option and search for S-off That option is not there and I can't Continue.
You are misunderstanding a couple things:
1) s-off is not a setting in Developer Options. s-off can only be obtained with sunshine app ($25)
2) You don't need s-off to root this device. Simply unlock the bootloader, install TWRP, and flash SuperSU to root
Click to expand...
Click to collapse
Detailed
redpoint73 said:
My responses below in red font:
Click to expand...
Click to collapse
Thanks for the detailed reply, really helpful and greatly appreciated :good:
Two more Questions, Can I upgrade to an official DEV Edition RUU on this ATT Device? or would I have to use a Custom Dev ROM ? as I am trying to Tether with my phone, just like my official Developer HTC M8 I purchased in 2014 , Seems AT&T phone wont allow me to Tether ?
Also once I flash firmware and upgrade to official RUU will need to Unlock and Root Loader? Will doing upgrading to official Marshmallow Relock bootloader and Un Root Phone ? Back to Stock ? Thanks again, I will be attempting this pretty soon. Thanks again
For the Record, I have made a back up of my Lollipop via TWRK. I also backed it up using Titanium back up, just in case.
Again, my responses in red font:
ELEVO said:
Thanks for the detailed reply, really helpful and greatly appreciated :good:
You're welcome. Always happy to help!
Two more Questions, Can I upgrade to an official DEV Edition RUU on this ATT Device?
You can't flash the Dev Edition RUU with s-on. Even though the versions are very similar (same model ID - MID) the two versions have different carrier ID (CID). Wrong carrier ID will make the Dev Ed RUU fail, by definition. And the only way to change CID is with s-off. Further, its not really necessary to flash the Dev Ed RUU (and not worth spending money of s-off) to accomplish what you want (see more below)
or would I have to use a Custom Dev ROM ? as I am trying to Tether with my phone, just like my official Developer HTC M8 I purchased in 2014 , Seems AT&T phone wont allow me to Tether ?
Its correct that the AT&T stock ROM disables tethering. Flashing most custom ROMs (or the Dev Ed ROM) will enable tethering - as well as remove annoying AT&T branding and bloat apps. Flashing the Dev Ed RUU is not necessary to accomplish this.
Also once I flash firmware and upgrade to official RUU will need to Unlock and Root Loader? Will doing upgrading to official Marshmallow Relock bootloader and Un Root Phone ? Back to Stock ? Thanks again, I will be attempting this pretty soon. Thanks again
You need to relock the bootloader in order to flash firmware and RUU (command: fastboot oem lock). Once the RUU is complete, the phone will be on a fully stock "factory" image. So you will be unrooted. You will also be back to stock recovery (no longer have TWRP installed). From there, what you want to do:
1) Unlock the bootloader again. Either use the same unlock bin code you used to unlock BL before. Or get a new code from HTCDev.com
2) Flash TWRP back to the phone with fastboot. TWRP 3.0.2 is recommended for compatibility with MM firmware.
3) Flash the desired custom ROM. The custom ROM will be rooted (if you flash the Dev Ed ROM, you can select root in the AROMA installer).
For the Record, I have made a back up of my Lollipop via TWRK. I also backed it up using Titanium back up, just in case.
Always good to make backups. Although be aware, that RUU will wipe the phone, including internal storage. So if you picked internal storage as your backup location, you'll want to move/copy to another location (removable SD is okay, otherwise to computer or cloud).
Also note that restoring app data (as well as call logs, SMS) using Titanium, after RUU or ROM flash should be okay. But don't restore any system data, as this can cause problems.
Click to expand...
Click to collapse
redpoint73 said:
Again, my responses in red font:
Click to expand...
Click to collapse
Ok i came back to this old post. I forgot all about it, it really is helping me alot.
My questioin is after i Relock the bootloader can i do a factory wipe? will this remove everything from my phone and bring it back to stock?
I relocked my phone, but all my apps and contacts are their.
Bricked ?
ELEVO said:
Ok i came back to this old post. I forgot all about it, it really is helping me alot.
My questioin is after i Relock the bootloader can i do a factory wipe? will this remove everything from my phone and bring it back to stock?
I relocked my phone, but all my apps and contacts are their.
Click to expand...
Click to collapse
I think i may have bricked my phone? I went and installed an RUU firmware file for Marshmallow as most instruct to do via Fastboot. All went well, installation completed and i was able to send command to phone to reboot. when it tried to reboot. white screen with HTC Comes on and then goes almost black with a very light dark grey background.
Phone would not reboot into anything but dark screen. even when i restarted it with power button. the only thing that worked for me, was Holding Down Power/Volume and quickly hit the volume down button before device would vibrate to reboot, that took me into recovery. Below is what i see in Recovery.
Phone now has new software
***RELOCKED***
m8_UL_CA PVT SHIP S-ON
HBOOT-3.1.0.0000
RADIO-4.0 [email protected]
OpenDSP-V56.2.2-00593-M8974_FO.0126
0S-6.20.502.5
eMMC-boot 2048MB
APR 14 2016,19:39:46.0
HBOOT
<Vol UP> to previous item
<Vol Down> to next item
<Power> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
I was able to run and "IMAGE CRC" via boot loader. it gave me alot of numbers after calculating. not sure if that is a good sign ?
Things I've tried in Recovery.
1. Recovery goes back to black screen.
2. SHOW BARCODE Works- 3 bar codes showed up.
3. Fastboot works. but when i try command "adb devices" it says list of devices attached. but nothing shows up
4. Tried to do a factory reset and tries to do it, then a black phone pops up on screen with green arrow sgoing in circles for like 10 seconds. then reboots to dark screen.
Please Help :crying: Thanks
Can anyone help me with this? I bought the phone with me on vacation and now using an HTC Developer Edition that the button down doesn't work and Volume down button us sunk in But at least i have my phone with all my contacts and apps , For now ?
I would like to know if i can unbrick my other HTC . Thanks.
Late in responding, as I was on work travel myself, and not on XDA for over a week.
ELEVO said:
I think i may have bricked my phone?
Click to expand...
Click to collapse
It's basically impossible for you to do anything with an s-on M8 that will actually brick it. That is the good thing about s-on.
ELEVO said:
I went and installed an RUU firmware file for Marshmallow as most instruct to do via Fastboot. All went well, installation completed and i was able to send command to phone to reboot. when it tried to reboot. white screen with HTC Comes on and then goes almost black with a very light dark grey background.
Click to expand...
Click to collapse
I think you only flashed the firmware.zip and not the RUU. Based on the condition here, and your other thread you created here: https://forum.xda-developers.com/htc-one-m8/help/htc-one-e-m8-fastboot-issues-t3757628
I clearly described above to flash the firmware.zip then the RUU. They are 2 completely different things. Firmware is about 80 MB and only contains hboot, radio, and a few other things. RUU is a full image that is 1.5 GB.
No boot after flashing signed firmware is normal, as it expects the RUU to be run afterwards.
ELEVO said:
Fastboot works. but when i try command "adb devices" it says list of devices attached. but nothing shows up
Click to expand...
Click to collapse
adb doesn't work in fastboot mode. Only fastboot commands will work in fastboot mode. You can only use adb when booted to OS (not an option for you, obviously) or alternately in custom recovery TWRP. So what you describe (adb not working) is normal and expected.
However, fastboot is enough to get the phone working from the described condition.

Categories

Resources