I'm not an expert but I'm not new to this either. I just don't have enough technical experience to figure this out. I had the Phone working and everything was amazing!
A few Days ago due to flashing the phone came up with a message 'No service' and i cannot get the phone to connect to my network at all. The phone cannot make emergency calls yet it cannot connect to any of the networks. When i turn off the Airplane mode it just get stuck on it and it never gets off even if you leave it for a day.(Check screenshot attached) When i dial this code *#*#4636#*#* nothing happens. I don't get the information although The code just vanish away from the dialing screen.
So far, Ive checked both covers on the back ensuring the pins connect properly for the aerial and there is no damage to either panel.
Hard reset did nothing to help, it booted straight up with the same limited service message.
I have tried my SIM card in another phone and it works perfectly, so i know its a problem with the phone.
I've had the IMEI number checked and the phone is not blocked.
The SIM card appears to be detected as you can see in the screenshot i attatched.
If the phone had been dropped, gotten wet or experienced any other form of potential damage, then I would assume it was a hardware repair issue. But because nothing has happened to obviously explain the issue I am experiencing, I am unsure.
Any thoughts would be greatly appreciated!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
shysoul64 said:
A few Days ago due to flashing the phone came up with a message 'No service' and i cannot get the phone to connect to my network at all.
Click to expand...
Click to collapse
What exactly did you flash (include file name, any version number, etc.)?
If the "no service" occurred right after flashing something, than that is mostly likely the cause, and the road you should pursue. Not things like checking IMEI, etc.
Tell us exactly what you did, exact sequence of events, etc.
First of all i want to Thank you for replying. Actually one of my friend Flashed it i have no idea what he has done even though he don't get it but he flashed it somehow and made my device in this Position.
redpoint73 said:
What exactly did you flash (include file name, any version number, etc.)?
If the "no service" occurred right after flashing something, than that is mostly likely the cause, and the road you should pursue. Not things like checking IMEI, etc.
Tell us exactly what you did, exact sequence of events, etc.
Click to expand...
Click to collapse
shysoul64 said:
First of all i want to Thank you for replying. Actually one of my friend Flashed it i have no idea what he has done even though he don't get it but he flashed it somehow and made my device in this Position.
Click to expand...
Click to collapse
You need to ask your friend what he flashed. It's extremely important. Ask him what file, with the exact file name, version number, and source (whatever of those he can give you, all of them if possible).
It sounds like he doesn't really know what he is doing? Why did he even flash anything at all? What was he trying to do? He shouldn't be doing anything to your phone, unless he intend on buying you a new one when he messes up (and it looks like he did).
Seeing as the phone is s-off, it's very possible he flashing the wrong file, and damaged the radio. The damage might be permanent (we've seen it happen before).
Also, we need more info about the phone. If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
redpoint73 said:
You need to ask your friend what he flashed. It's extremely important. Ask him what file, with the exact file name, version number, and source (whatever of those he can give you, all of them if possible).
It sounds like he doesn't really know what he is doing? Why did he even flash anything at all? What was he trying to do? He shouldn't be doing anything to your phone, unless he intend on buying you a new one when he messes up (and it looks like he did).
Seeing as the phone is s-off, it's very possible he flashing the wrong file, and damaged the radio. The damage might be permanent (we've seen it happen before).
Also, we need more info about the phone. If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
He is a complete noob but act like if he is a Pro ( I came to know after he did this to my phone and when i forwarded him the Questions you asked)
Actually my Phone was a bit laggy which made me pissed off and my bad luck was that he was sitting right next to me. He told me to leave my Phone for a day and he would fix it up at the end result is in front of you.
He have no idea what he has flashed i.e. (exact file name, version number, and source). He said i downloaded from a random site by searching it from google. LOL!
I will give you the info whatever you want to know.
How to fastboot getvar all?
I'm kind of new to these Android Flashing so i might sound stupid.
redpoint73 said:
You need to ask your friend what he flashed. It's extremely important. Ask him what file, with the exact file name, version number, and source (whatever of those he can give you, all of them if possible).
It sounds like he doesn't really know what he is doing? Why did he even flash anything at all? What was he trying to do? He shouldn't be doing anything to your phone, unless he intend on buying you a new one when he messes up (and it looks like he did).
Seeing as the phone is s-off, it's very possible he flashing the wrong file, and damaged the radio. The damage might be permanent (we've seen it happen before).
Also, we need more info about the phone. If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
shysoul64 said:
He have no idea what he has flashed i.e. (exact file name, version number, and source). He said i downloaded from a random site by searching it from google. LOL!
Click to expand...
Click to collapse
That type of behavior is extremely careless, and my opinion, that person should not be messing with yours or anyone else's phone.
If he had truly "no idea" what he was flashing, then he had no business flashing it! Him having "no idea" what he flashed to me says he had little or no understanding of what he was doing. And best practice is to fully understand what you are installing to the phone, and also keep track of exactly what those files were, steps performed, etc.
The file (or files) that he flashed still aren't on his computer in a folder somewhere, or even in the PC's recycle bin? Another best practice, I always keep files (I've flashed) on my PC for a while "just in case" I need to use them again or reference them.
Really hard to troubleshoot the problem, without knowing what he did. One thing I can suggest, is to flash the RUU, which is a complete factory image, and will hopefully clear up the "no network" problem. See the following post for files and instructions:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
redpoint73 said:
That type of behavior is extremely careless, and my opinion, that person should not be messing with yours or anyone else's phone.
If he had truly "no idea" what he was flashing, then he had no business flashing it! Him having "no idea" what he flashed to me says he had little or no understanding of what he was doing. And best practice is to not only fully understand what you are installing to the phone, but also keep track of exactly what those files were, steps performed, etc.
The file (or files) that he flashed still aren't on his computer in a folder somewhere, or even in the PC's recycle bin? Another best practice, I always keep files (I've flashed) on my PC for a while "just in case" I need to use them again or reference them.
Click to expand...
Click to collapse
I'm forwarding all of your Messages to him. He is ignoring them he ain't answering my calls either. I cannot contact him right now. I don't think whether he have the files anymore.
Anyways, apart from that is there any other way to Flash it back to the normal state?
redpoint73 said:
That type of behavior is extremely careless, and my opinion, that person should not be messing with yours or anyone else's phone.
If he had truly "no idea" what he was flashing, then he had no business flashing it! Him having "no idea" what he flashed to me says he had little or no understanding of what he was doing. And best practice is to fully understand what you are installing to the phone, and also keep track of exactly what those files were, steps performed, etc.
The file (or files) that he flashed still aren't on his computer in a folder somewhere, or even in the PC's recycle bin? Another best practice, I always keep files (I've flashed) on my PC for a while "just in case" I need to use them again or reference them.
Really hard to troubleshoot the problem, without knowing what he did. One thing I can suggest, is to flash the RUU, which is a complete factory image, and will hopefully clear up the "no network" problem. See the following post for files and instructions:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
Should i leave the S-Off or Turn it ON?!
shysoul64 said:
Should i leave the S-Off or Turn it ON?!
Click to expand...
Click to collapse
Have you tried manually entering an APN into your phone?
Sent from my HTC One M9 using Tapatalk
shysoul64 said:
Should i leave the S-Off or Turn it ON?!
Click to expand...
Click to collapse
Leave it S-Off till (if) you get it up and running. Then its entirely up to you.
Looking at the bootloader screen. It appears as though it is a faux bootloader as the status is official.. Cid is 11111111 which is supercid, so be careful.
shysoul64 said:
I'm not an expert but I'm not new to this either. I just don't have enough technical experience to figure this out. I had the Phone working and everything was amazing!
A few Days ago due to flashing the phone came up with a message 'No service' and i cannot get the phone to connect to my network at all. The phone cannot make emergency calls yet it cannot connect to any of the networks. When i turn off the Airplane mode it just get stuck on it and it never gets off even if you leave it for a day.(Check screenshot attached) When i dial this code *#*#4636#*#* nothing happens. I don't get the information although The code just vanish away from the dialing screen.
So far, Ive checked both covers on the back ensuring the pins connect properly for the aerial and there is no damage to either panel.
Hard reset did nothing to help, it booted straight up with the same limited service message.
I have tried my SIM card in another phone and it works perfectly, so i know its a problem with the phone.
I've had the IMEI number checked and the phone is not blocked.
The SIM card appears to be detected as you can see in the screenshot i attatched.
If the phone had been dropped, gotten wet or experienced any other form of potential damage, then I would assume it was a hardware repair issue. But because nothing has happened to obviously explain the issue I am experiencing, I am unsure.
Any thoughts would be greatly appreciated!
Click to expand...
Click to collapse
cool bro..... jst flash the stock rom for htc one m8
miffymiffy said:
Leave it S-Off till (if) you get it up and running. Then its entirely up to you.
Looking at the bootloader screen. It appears as though it is a faux bootloader as the status is official.. Cid is 11111111 which is supercid, so be careful.
Click to expand...
Click to collapse
I flashed the Stock software but it didn't worked for me. I'm still having the same issue as i mentioned. Any other way?
redpoint73 said:
That type of behavior is extremely careless, and my opinion, that person should not be messing with yours or anyone else's phone.
Really hard to troubleshoot the problem, without knowing what he did. One thing I can suggest, is to flash the RUU, which is a complete factory image, and will hopefully clear up the "no network" problem. See the following post for files and instructions:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
I did exactly what you said last night but my Phone is still in the same state. Do you have any other way to suggest?
shysoul64 said:
I did exactly what you said last night but my Phone is still in the same state. Do you have any other way to suggest?
Click to expand...
Click to collapse
Which ruu did you try?
maultasche said:
Which ruu did you try?
Click to expand...
Click to collapse
This RUU https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Suggested by redpoint73
shysoul64 said:
This RUU https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Suggested by redpoint73
Click to expand...
Click to collapse
That's the correct RUU for your phone. But since we don't know what was flashed it's hard to help. Seems like radio is bricked permanently. I'm sorry but I think your issue can't be fixed by just flashing software.
maultasche said:
That's the correct RUU for your phone. But since we don't know what was flashed it's hard to help. Seems like radio is bricked permanently. I'm sorry but I think your issue can't be fixed by just flashing software.
Click to expand...
Click to collapse
Awwww! RIP M8
maultasche said:
That's the correct RUU for your phone. But since we don't know what was flashed it's hard to help. Seems like radio is bricked permanently. I'm sorry but I think your issue can't be fixed by just flashing software.
Click to expand...
Click to collapse
Just another thought by a Noob. LOL!
If flashing can damage M8 radio files then there might be a file that can fix it also. What do you say?
shysoul64 said:
Just another thought by a Noob. LOL!
If flashing can damage M8 radio files then there might be a file that can fix it also. What do you say?
Click to expand...
Click to collapse
If there was such a file maybe. But such a file does not exist (not that I know of) or it's not available for the general public.
Related
Hello
My phone's screen is stuck at opening htc logo. I never rooted it - shall I just flash it with standard stock rom? Would you please be so kind to point me in the right direction? Bless...
My kindest regards
Pete
Try booting without the sd card.
How old is the phone? What happened / did you do (if such is the case) for it to get like that? Etc.....
Sent from a dream.
Teichopsia said:
Try booting without the sd card.
How old is the phone? What happened / did you do (if such is the case) for it to get like that? Etc.....
Sent from a dream.
Click to expand...
Click to collapse
Tried that before without result...also did a factory reset but to no avail. Phone was just over a year old when it happened, got it from my insurance policy so it's possibly a refurbished one. I can't remember doing anything to cause this...
phosphen said:
Tried that before without result...also did a factory reset but to no avail. Phone was just over a year old when it happened, got it from my insurance policy so it's possibly a refurbished one. I can't remember doing anything to cause this...
Click to expand...
Click to collapse
You Need to provide the Cid number and the Main Version. Do You know how to Get that?
glevitan said:
You Need to provide the Cid number and the Main Version. Do You know how to Get that?
Click to expand...
Click to collapse
Sorry, no idea...
phosphen said:
Sorry, no idea...
Click to expand...
Click to collapse
Ok, enable USB debugging, plug the phone to the PC and then open a CMD ON the PC and type adb reboot-bootloader and once in bootloader type fastboot getvar all. You Need to post the INFOcidnum and INFOmain
How old is your phone? Isn't there still any warranty? If so you may try to contact your reseller, service provider or the manufacturer. If not glevitan may be your hero
glevitan said:
Ok, enable USB debugging, plug the phone to the PC and then open a CMD ON the PC and type adb reboot-bootloader and once in bootloader type fastboot getvar all. You Need to post the INFOcidnum and INFOmain
Click to expand...
Click to collapse
Sorry mate, I was offline for a whole day, just managed to get back on it
How can I enable USB debugging if I can get onto HBOOT menu only? Is it possible to switch it on from there? Saludos
phosphen said:
Sorry mate, I was offline for a whole day, just managed to get back on it
How can I enable USB debugging if I can get onto HBOOT menu only? Is it possible to switch it on from there? Saludos
Click to expand...
Click to collapse
Yes, from fastboot, plug the phone (You will see fastboot USB in red) type: fastboot getvar all
sounds like a boot loop?
try removing the battery, once you have done that re boot into boot loader from there you should see an option for recovery.you may want to do a full wipe and re flash the rom.:silly: keep in mind the initial flash normally will take the longest,best to leave it be for a few minutes while the phone adjust to the new settings,that sometimes will seem like you may have an issue, but patience most times is all that is needed.hope this helps.
rdub504 said:
try removing the battery, once you have done that re boot into boot loader from there you should see an option for recovery.you may want to do a full wipe and re flash the rom.:silly: keep in mind the initial flash normally will take the longest,best to leave it be for a few minutes while the phone adjust to the new settings,that sometimes will seem like you may have an issue, but patience most times is all that is needed.hope this helps.
Click to expand...
Click to collapse
It's not rooted, so I don't think that will work.
bananagranola said:
It's not rooted, so I don't think that will work.
Click to expand...
Click to collapse
excellent point,but if that's true what is he flashing?
rooted phone=flash capable non rooted =stock rom with no admin access. am i mistaken,if so slap me and call me susan,if not box that thing up and bring it back,and if that's not an option then warranty time.because that device is chap.
rdub504 said:
excellent point,but if that's true what is he flashing?
rooted phone=flash capable non rooted =stock rom with no admin access. am i mistaken,if so slap me and call me susan,if not box that thing up and bring it back,and if that's not an option then warranty time.because that device is chap.
Click to expand...
Click to collapse
Hello susan
Sent from a dream.
Teichopsia said:
Hello susan
Sent from a dream.
Click to expand...
Click to collapse
LOL,I guess i'm susan and my face now hurt.can you please elaborate a bit so i can also understand what i am missing.
rdub504 said:
LOL,I guess i'm susan and my face now hurt.can you please elaborate a bit so i can also understand what i am missing.
Click to expand...
Click to collapse
Well....
1- over a year old bought refurbished.
2- he never rooted. We could assume that it is s-off from the previous owner but all of us failed to ask that question making another assumption that he isn't s-off.
3- he did a factory reset which didn't work (whatever that means with an s-on device / with an s-off device it really messes things up).
4- glevitan is here. If he doesn't know how to fix it (and from the few active members that tend to lend a hand in these type of posts) there may be just a handful who could help out. Hence, the OP is in good hands.
5- when someone messes up their phone without knowing what happened nor how to fix it, you need to give more detailed instructions on how to get it done.
6- I'm guessing that the info glevitan asked for is to find the correct ruu for the member to flash and to get his phone back to working conditions. If that doesn't work, chances are it's a hardware problem.
Sent from a dream.
Teichopsia said:
Well....
1- over a year old bought refurbished.
2- he never rooted. We could assume that it is s-off from the previous owner but all of us failed to ask that question making another assumption that he isn't s-off.
3- he did a factory reset which didn't work (whatever that means with an s-on device / with an s-off device it really messes things up).
4- glevitan is here. If he doesn't know how to fix it (and from the few active members that tend to lend a hand in these type of posts) there may be just a handful who could help out. Hence, the OP is in good hands.
5- when someone messes up their phone without knowing what happened nor how to fix it, you need to give more detailed instructions on how to get it done.
6- I'm guessing that the info glevitan asked for is to find the correct ruu for the member to flash and to get his phone back to working conditions. If that doesn't work, chances are it's a hardware problem.
Bullet point,impressive. now a refurb with s off would mean a root from a previous owner?
"S-ON, which means it blocks you from flashing radio images — the code that manages your data, Wi-Fi and GPS connections. Switching your phone to S-OFF lets you flash new radios. Rooting doesn’t require S-OFF, but many rooting tools will give you S-OFF in addition to root access" So hince my question if attempting to flash a rom ,it would be a safe bet he would be rooted,because without it he would have no admin access,recovery or superser access and would not be able to complete the flash process.a factory reset would normally on a stock rom not result in a loss of the entire stock rom but only a loss off data i.e contacts apps etc. and with these things in mind it would seem to be a safe to assume its a hardware issue or a rooted refurb phone from a previous owner in a bootloop becauce a factory reset there would wipe everything?
Click to expand...
Click to collapse
Factory reset resets the phone to it's "as fabricated"-condition, wich means it wipes user data and cache on the phone. With or without root the procedure is the same and should usally not affect /system or /boot.
So we have to find out, if the phone is S-On/S-Off (phosphen, more information on the topic can be read for example here, second post).
Teichopsia said:
Well....
1- over a year old bought refurbished.
2- he never rooted. We could assume that it is s-off from the previous owner but all of us failed to ask that question making another assumption that he isn't s-off.
3- he did a factory reset which didn't work (whatever that means with an s-on device / with an s-off device it really messes things up).
4- glevitan is here. If he doesn't know how to fix it (and from the few active members that tend to lend a hand in these type of posts) there may be just a handful who could help out. Hence, the OP is in good hands.
5- when someone messes up their phone without knowing what happened nor how to fix it, you need to give more detailed instructions on how to get it done.
6- I'm guessing that the info glevitan asked for is to find the correct ruu for the member to flash and to get his phone back to working conditions. If that doesn't work, chances are it's a hardware problem.
Sent from a dream.
Click to expand...
Click to collapse
rdub504 said:
Teichopsia said:
Well....
1- over a year old bought refurbished.
2- he never rooted. We could assume that it is s-off from the previous owner but all of us failed to ask that question making another assumption that he isn't s-off.
3- he did a factory reset which didn't work (whatever that means with an s-on device / with an s-off device it really messes things up).
4- glevitan is here. If he doesn't know how to fix it (and from the few active members that tend to lend a hand in these type of posts) there may be just a handful who could help out. Hence, the OP is in good hands.
5- when someone messes up their phone without knowing what happened nor how to fix it, you need to give more detailed instructions on how to get it done.
6- I'm guessing that the info glevitan asked for is to find the correct ruu for the member to flash and to get his phone back to working conditions. If that doesn't work, chances are it's a hardware problem.
Bullet point,impressive. now a refurb with s off would mean a root from a previous owner?
"S-ON, which means it blocks you from flashing radio images — the code that manages your data, Wi-Fi and GPS connections. Switching your phone to S-OFF lets you flash new radios. Rooting doesn’t require S-OFF, but many rooting tools will give you S-OFF in addition to root access" So hince my question if attempting to flash a rom ,it would be a safe bet he would be rooted,because without it he would have no admin access,recovery or superser access and would not be able to complete the flash process.a factory reset would normally on a stock rom not result in a loss of the entire stock rom but only a loss off data i.e contacts apps etc. and with these things in mind it would seem to be a safe to assume its a hardware issue or a rooted refurb phone from a previous owner in a bootloop becauce a factory reset there would wipe everything?
Click to expand...
Click to collapse
Cfhappy said:
Factory reset resets the phone to it's "as fabricated"-condition, wich means it wipes user data and cache on the phone. With or without root the procedure is the same and should usally not affect /system or /boot.
So we have to find out, if the phone is S-On/S-Off (phosphen, more information on the topic can be read for example here, second post).
Click to expand...
Click to collapse
Sorry guys, but before hijacking this thread maybe you can go and follow the discussion in the off topic thread. The idea here is to lend a hand to someone that is stuck and a noob and this for certain not helping him. Let's keep it clean....
BTW, the only solution in his case is to flash the OEM RUU or make a goldcard and flash an unbranded rom. With no s-off there´s no other way.
Click to expand...
Click to collapse
I couldn't resist.
Maybe it's good practice for him to read through all to learn to discern right info from wrong.
Sent from a dream.
Teichopsia said:
I couldn't resist.
Maybe it's good practice for him to read through all to learn to discern right info from wrong.
Sent from a dream.
Click to expand...
Click to collapse
Yeah, that is right, but with the phone stuck in the splash I don´t think is a good time to think about learning. This experience will definitely be worth for him in the future. :victory:
Okay my phone has been working fine till now.
My IMEI is intact still displays *#06# the correct no. It has been unlocked. I have rooted installed a custom ROM all was working okay till yesterday. When I turn the phone on emergency calls only is displayed. When I try to make a call it pops up with not registered on network. My data works okay though so I know am not blacklisted. Has anybody got a fix. Been searching but can seem to find a solution. Please help.
you have a backup of your efs folder?
Try a data clear.
Make sure you already have a backup of efs.
Sent from my GT-N7100 using xda premium
UtkarshGupta said:
Try a data clear.
Make sure you already have a backup of efs.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
I have tried it already. It's seems like my phine has locked itself in emergency mode and doesnt want to come out of it
Sent from my GT-I9305 using xda app-developers app
MrCeez said:
I have tried it already. It's seems like my phine has locked itself in emergency mode and doesnt want to come out of it
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Gonna have to bump this, since I have the same issue.
Phone was working fine until I tried this rom. Now every rom I try, including flashing stock using odin, leaves the phone as "emergency calls only". I've tried different modems etc, nothing.
Current baseband N71000NEDLK1.
Even flashing the proper UK 3 network stock rom, nothing.
Have you tried with another sim card? Maybe you have a damage sim.
zabumba said:
Have you tried with another sim card? Maybe you have a damage sim.
Click to expand...
Click to collapse
Ive tried my mrs' o2 card, same issue there.
It feels like a rom has changed everything, my modem even. I've tried to flash one recommended for Three UK, but it didn't seem to stick in recovery.
X82X said:
Ive tried my mrs' o2 card, same issue there.
It feels like a rom has changed everything, my modem even. I've tried to flash one recommended for Three UK, but it didn't seem to stick in recovery.
Click to expand...
Click to collapse
Try to restore the stock Firmware or a different custom rom
aukhan said:
Try to restore the stock Firmware or a different custom rom
Click to expand...
Click to collapse
I fear for the worst. I've read a few entries from people saying when this happened to them (some never rooted or on any custom rom) they had a paperweight.
I've tried about 6 different stock roms, many custom. Many modems. Nothing will get it working.
The phone has full signal, can scan for networks, but will not allow calls or connect to data.
I've tried the sim elsewhere and it's fine.
Since this is my only means of communication, I'm extra worried.
Any help on this matter, is greatly appreciated!
X82X said:
I fear for the worst. I've read a few entries from people saying when this happened to them (some never rooted or on any custom rom) they had a paperweight.
I've tried about 6 different stock roms, many custom. Many modems. Nothing will get it working.
The phone has full signal, can scan for networks, but will not allow calls or connect to data.
I've tried the sim elsewhere and it's fine.
Since this is my only means of communication, I'm extra worried.
Any help on this matter, is greatly appreciated!
Click to expand...
Click to collapse
Is your IMEI number intact as shown on the box ?
Which device is this i mean model ?
N7100 or N7105 or some other is this a Carrier specific device ?.
aukhan said:
Is your IMEI number intact as shown on the box ?
Which device is this i mean model ?
N7100 or N7105 or some other is this a Carrier specific device ?.
Click to expand...
Click to collapse
The IMEI is 004XXX010640000 / 01
Model N7100.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
X82X said:
The IMEI is 004XXX010640000 / 01
Model N7100.
Click to expand...
Click to collapse
Is IMEI matching on the box ?
aukhan said:
Is IMEI matching on the box ?
Click to expand...
Click to collapse
Sorry, I never had a box. My dad has been using it great for 6 months, I have it a day, stick a rom on it and boom. But I'm smelling something with the kernel. I changed the kernel and now there is no signal at all. I need to find the right one for this UK model.
I've got the same exact problem as well, my N7100 bought it from china ( not copy) and after install Hong Kong version of stock rom via Odin,I have the same exact problem.
1. I can search for all the available network.
2. Under settings-about-status, it shows my phone number, my carrier, HSDPA mode...all looks normal except "emergency call"
3. I tried calling the sim that was in the N7100 and text message, the line works,text message shows as delivered, but nothing turns up on the N7100.
I've tried custom,stock,per-rooted from many versions of the world but the problem is still there.
X82X said:
Sorry, I never had a box. My dad has been using it great for 6 months, I have it a day, stick a rom on it and boom. But I'm smelling something with the kernel. I changed the kernel and now there is no signal at all. I need to find the right one for this UK model.
Click to expand...
Click to collapse
i think your the victim of IMEI corrupt or EFS Folder corrupted
as the IMEI 004XXX010640000 / 01 this is what you posted it looks suspcious to me
pull the battery there is sticker match the IMEI showing on the sticker and from phone see it they matches if they dont they your in deep trouble where you may have to get it serviced
---------- Post added at 02:37 PM ---------- Previous post was at 02:36 PM ----------
pixellized said:
I've got the same exact problem as well, my N7100 bought it from china ( not copy) and after install Hong Kong version of stock rom via Odin,I have the same exact problem.
1. I can search for all the available network.
2. Under settings-about-status, it shows my phone number, my carrier, HSDPA mode...all looks normal except "emergency call"
3. I tried calling the sim that was in the N7100 and text message, the line works,text message shows as delivered, but nothing turns up on the N7100.
I've tried custom,stock,per-rooted from many versions of the world but the problem is still there.
Click to expand...
Click to collapse
suggest you to try this and check #15
aukhan said:
i think your the victim of IMEI corrupt or EFS Folder corrupted
as the IMEI 004XXX010640000 / 01 this is what you posted it looks suspcious to me
pull the battery there is sticker match the IMEI showing on the sticker and from phone see it they matches if they dont they your in deep trouble where you may have to get it serviced
Click to expand...
Click to collapse
Correct. The IMEI is totally different. But as I said, I am not going to fix it. I'll just sell it on cheap for someone else to. It's a shame and annoying that something like this can go wrong and potentially brick a phone. I know theres risks to all rooting/custom roms, which I accept, but it still doesn't stop it stinging when it does go wrong, which to my knowledge, wasn't my fault.
X82X said:
Correct. The IMEI is totally different. But as I said, I am not going to fix it. I'll just sell it on cheap for someone else to. It's a shame and annoying that something like this can go wrong and potentially brick a phone. I know theres risks to all rooting/custom roms, which I accept, but it still doesn't stop it stinging when it does go wrong, which to my knowledge, wasn't my fault.
Click to expand...
Click to collapse
always remember option number when rooting device always make a backup of Efs folder or backup you rom
aukhan said:
always remember option number when rooting device always make a backup of Efs folder or backup you rom
Click to expand...
Click to collapse
But, for me, the IMEI number is still the same as my original number,from the back of the phone sticker & also the box, could my phone's problem be any different?
pixellized said:
But, for me, the IMEI number is still the same as my original number,from the back of the phone sticker & also the box, could my phone's problem be any different?
Click to expand...
Click to collapse
First thing before you try anything else make a backup of EFS folder search for the thread you will find specific to Note 2.
then try to make a ROM backup
then Flash the stock Firmware see if this works.
X82X said:
Correct. The IMEI is totally different. But as I said, I am not going to fix it. I'll just sell it on cheap for someone else to. It's a shame and annoying that something like this can go wrong and potentially brick a phone. I know theres risks to all rooting/custom roms, which I accept, but it still doesn't stop it stinging when it does go wrong, which to my knowledge, wasn't my fault.
Click to expand...
Click to collapse
Don't be paniced mate. The problem is easy to solve. With a root explorer find the folder efs_Backup, location of the folder varies from rom to rom. If you are in a custom stock rom, you'll find it under sd card. It also may locate on root/media. Every time you flash a new rom the efs backed up automatically in zip. After finding the folder, open it, you'll find many zip files mentioned dates. Extract the one you remember when your phone was fine. Then copy the whole content of the extracted folder and paste to the root/efs.
Before pasting, erase the existing contents of the efs folder.
DONE!
Sent from my GT-N7100 using xda premium
I bought a HTC One M8 AT&T phone from eBay that was rooted. I'm not a fan of being rooted, and I've rooted and unrooted in the past, so I THOUGHT i was familiar with the process. I am just about ready to pull my hair out. I've spend a good 5-6 hours trying all sorts of methods. Maybe someone can help me. Here's the scoop:
I have S-on. I have TWRP recovery. I have HTC sync drivers installed on my computer. I have NO OS installed (I didn't back anything up not realizing I deleted the back up). I have tried flashing a boot img from CMD of my computer directly onto the phone but NOTHING i attempt to flash will work. I have zip files from a 1.158.502.1, I have been attempting to flash from the "install" folder on TWRP with NO avail. The CMD prompt: Fastboot Devices DOES recognize my device in my PC. Please help me.
Did you put the .zip on your SD card, internal? Where is the .zip located? Really, make sure CID matches ATT, relock bootloader, and run from here: http://www.htc.com/us/support/htc-one-m8-att/news/
You can't screw this phone up, you just can't.
"Did you put the .zip on your SD card, internal? Where is the .zip located? Really, make sure CID matches ATT, relock bootloader, and run from here: URL
You can't screw this phone up, you just can't."
The .zip is on my sd card. THe CID matches ATT. I do not know how to relock the bootloader. That's something I haven't tried. I'm trying NOT to screw the phone up, I don't think I am, it's just that nothing is working.
1st off, don't panic! You didn't screw up your phone.
I'm not sure what you're trying to say the problem is, but:
If your zip file is a twrp backup, then you need to put it in the corresponding twrp backups folder (sd_ext/twrp/backups/serialnumber/backupfoldername/). Otherwise, if your zip file is an RUU then you'll need to place it at the root of your sd and rename it to 0P6BIMG.zip then flash it from bootloader.
You need to flash an OS before you flash the corresponding firmware and boot image.
Anyhow, do provide more details!
cami0488 said:
I bought a HTC One M8 AT&T phone from eBay that was rooted. I'm not a fan of being rooted, and I've rooted and unrooted in the past, so I THOUGHT i was familiar with the process. I am just about ready to pull my hair out. I've spend a good 5-6 hours trying all sorts of methods.
Click to expand...
Click to collapse
Every Android phone is different, and has its own learning curve. You should also not apply methods meant for other phones, only for the M8.
cami0488 said:
I have S-on. I have TWRP recovery. I have HTC sync drivers installed on my computer. I have NO OS installed (I didn't back anything up not realizing I deleted the back up).
Click to expand...
Click to collapse
Did you delete all the partitions in the TWRP "Advanced wipe" option?
cami0488 said:
I have tried flashing a boot img from CMD of my computer directly onto the phone but NOTHING i attempt to flash will work. I have zip files from a 1.158.502.1, I have been attempting to flash from the "install" folder on TWRP with NO avail.
Click to expand...
Click to collapse
What do you mean it "nothing I attempt will work"? If you aren't specific about what you attempted, this doesn't tell us anything!!!
What was your command syntax? Where did you get the file? What is the outcome (error message, or just no boot into OS)?
Also, this is never going to get your phone running in itself, anyway. You realize boot.img is just a kernel (and a few other small things) and not the whole ROM? If you deleted the system partition, you need to restore an entire ROM (over 1GB for a Sense ROM) not just boot.img, which is about 13 MB?
---------- Post added at 09:54 AM ---------- Previous post was at 09:51 AM ----------
shirreer said:
Anyhow, do provide more details!
Click to expand...
Click to collapse
Agreed, the OP hasn't provided nearly enough info.
Its not remotely clear what the OP has even tried flashing.
Saying he "tried a bunch of stuff" is not helpful. OP needs to describe every step, what files used, and the outcomes with error messages or other results.
Need to do fastboot getvar all, and post the output (be sure to delete IMEI and serial numbers before posting the output, as these are personal data).
---------- Post added at 09:56 AM ---------- Previous post was at 09:54 AM ----------
hack14u said:
Really, make sure CID matches ATT, relock bootloader, and run from here: http://www.htc.com/us/support/htc-one-m8-att/news/
Click to expand...
Click to collapse
Agree that the OP probably just need to relock the bootloader and run the Lollipop RUU.
Not only will this get the phone up and running again in (nearly) stock condition, but will also update it to the most current Android LP version.
redpoint73 said:
Every Android phone is different, and has its own learning curve. You should also not apply methods meant for other phones, only for the M8.
Click to expand...
Click to collapse
Yeah, I certainly learned that the hard way.
Did you delete all the partitions in the TWRP "Advanced wipe" option?
Click to expand...
Click to collapse
Yes unfortunately I did. No TWRP back ups exsist.
What do you mean it "nothing I attempt will work"? If you aren't specific about what you attempted, this doesn't tell us anything!!!
Click to expand...
Click to collapse
I attemped to flash the rom 155.502.18 via a zip file to the phone. Nothing. I attempted loading up a boot.img from some YouTube view I watched that I can't link because I don't have 10 posts on here yet.
What was your command syntax? Where did you get the file? What is the outcome (error message, or just no boot into OS)?
Click to expand...
Click to collapse
I'm sorry, I don't know what a command syntax is. I got the file right off here in XDA Forums in the ROM's folder for AT&T stock rom. The error just says "failed" and will not write. It seems to keep missing an "MD5" file. The error in CMD prompt is that it just doesn't go anywhere after I type in >Flashboot Flash Boot boot.img
Also, this is never going to get your phone running in itself, anyway. You realize boot.img is just a kernel (and a few other small things) and not the whole ROM? If you deleted the system partition, you need to restore an entire ROM (over 1GB for a Sense ROM) not just boot.img, which is about 13 MB?
Click to expand...
Click to collapse
I did not know that. I was just trying to figure out how to get this to work again. Yes, I did delete the system partition, so I guess I will have to restore an entire ROM (1gb of space for a Sense ROM). The problem is, I don't know which files from these .zip files on XDA are the correct files, and I can't seem to find any videos on YouTube that show the problems I'm having.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Agreed, the OP hasn't provided nearly enough info.
Its not remotely clear what the OP has even tried flashing.
Saying he "tried a bunch of stuff" is not helpful. OP needs to describe every step, what files used, and the outcomes with error messages or other results.
Need to do fastboot getvar all, and post the output (be sure to delete IMEI and serial numbers before posting the output, as these are personal data).
Click to expand...
Click to collapse
I apologize for the lack of information. I have some screenshots of the errors and what the TWRP recovery bootloader looks like, but I can't attach my image files to this post because It says I need 10 more posts. Otherwise I would have tried to post more information. "he said". I am a woman*. I did try a fastboot getvar all before, so I'm aware what that is, but I'll have to post short messages around here to reach my 10 post mark so i can start including some screenshot images.
Agree that the OP probably just need to relock the bootloader and run the Lollipop RUU.
Click to expand...
Click to collapse
Relative question. What is the difference between manually flashing a ROM through the CMD prompt on my comptuper vs "RUU". I don't have any current operating system on the phone so I can no longer go into the settings and turn off USB debugging and whatever else I've seen instructions on using RUUs. Which all seem to indicate I need an OS before even doing that option.
Not only will this get the phone up and running again in (nearly) stock condition, but will also update it to the most current Android LP version.
Click to expand...
Click to collapse
THAT IS THE GOAL! I would be SOoooooooooooooooooooooooo happy if and when that can finally happen. Annnnnd I"ll never be buying anymore phones that are rooted again, because I don't want to go through this annoying process of unrooting. Now I know why the seller didn't unroot!, lolAnd THANK YOU to all for your replies. I shall post more information
shirreer said:
1st off, don't panic! You didn't screw up your phone.
I'm not sure what you're trying to say the problem is, but:
If your zip file is a twrp backup, then you need to put it in the corresponding twrp backups folder (sd_ext/twrp/backups/serialnumber/backupfoldername/). Otherwise, if your zip file is an RUU then you'll need to place it at the root of your sd and rename it to 0P6BIMG.zip then flash it from bootloader.
You need to flash an OS before you flash the corresponding firmware and boot image.
Anyhow, do provide more details!
Click to expand...
Click to collapse
I got this .zip file from the XDA ROMs folder off here. I'm not sure if it's an RUU file. However it is not a backup, or so it wasn't labled that way. It was labled as the "stock ROM"
Try what I said. Before, run the command fastboot OEM lock. That will relock the bootloader so you don't throw an error when you run the RUU. The RUU will wipe everything and bring it back to ATT stock. From there you can learn more commands, and how to "fix" things. An RUU is the stock files packaged as a .exe file, you actually run it from your PC like you were installing a piece of software, but it goes to your phone. Don't worry about not having this, or that, it will fix it for you, unless something else is not set right. Give it a shot, you have nothing to lose, literally. Oh, and I always run RUU's from fastboot USB so it detects it pretty quick.
hack14u said:
Try what I said. Before, run the command fastboot OEM lock. That will relock the bootloader so you don't throw an error when you run the RUU. The RUU will wipe everything and bring it back to ATT stock. From there you can learn more commands, and how to "fix" things. An RUU is the stock files packaged as a .exe file, you actually run it from your PC like you were installing a piece of software, but it goes to your phone. Don't worry about not having this, or that, it will fix it for you, unless something else is not set right. Give it a shot, you have nothing to lose, literally. Oh, and I always run RUU's from fastboot USB so it detects it pretty quick.
Click to expand...
Click to collapse
See, I read about using RUU, but I also read that if you have "S-on" you can't flash anything on the device unless you do it through the cmd prompt. That's what caused my problems to begin with, I didn't know where to start after having accidentally wiped my OS, backups, and damn near everything. So it can still work via the RUU method with my S-On? I shall try it tomorrow after work.
From CMD, type:
fastboot getvar all
Take a picture and post it, so we can find you a rom that's suitable for your CID! From then on its really simple.
cami0488 said:
Yes unfortunately I did. No TWRP back ups exsist.
Click to expand...
Click to collapse
Forgive me while I rant, but I see this all too often (wiping partitions when you don't know what they are). Quite frankly, if you don't know what you are wiping, or what the result will be, then don't wipe it. It doesn't take much research to find out what each wipe option (partition) is. There are far too many post on here to the effect "I wiped system and now I have no OS". Well, seeing as system and OS are the same thing, that is an obvious outcome. Plus, these options are called "Advanced" for a reason. If you don't have advanced knowledge (or at least research what the options mean), don't mess with them.
Further, wiping everything in TWRP Advanced Wipe options means you wiped your internal storage and removable SD (if you have one), both of which are the possible locations for TWRP backups (internal storage is the default backup location). So again, since you wiped everything, of course you wiped your TWRP backups.
cami0488 said:
I attemped to flash the rom 155.502.18 via a zip file to the phone. Nothing. I attempted loading up a boot.img from some YouTube view I watched that I can't link because I don't have 10 posts on here yet.
Click to expand...
Click to collapse
First of all, that is not a valid OS number for the M8, and the likely reason is that you typed it incorrectly. You really need to post specifically and correctly, otherwise we can't know what you are doing. It might seem unimportant or nitpicky to you, but tiny differences in these numbers can have big implications, so you really need to try harder to get it right.
Your description is still far to vague to mean anything. "a boot.img from some YouTube" Do you seriously think that is going to help us help you at all? There are thousands (if not millions) of videos on YouTube. We can't have any idea what that means. You really do need to give the exact steps you've tried and the exact files, if you want proper help.
While you can't use the link function to post links, if needed you can post the text. If the forum still won't allow it, just obfuscate the URL with "dotcom" at the end or something similar.
cami0488 said:
I'm sorry, I don't know what a command syntax is. I got the file right off here in XDA Forums in the ROM's folder for AT&T stock rom. The error just says "failed" and will not write. It seems to keep missing an "MD5" file. The error in CMD prompt is that it just doesn't go anywhere after I type in >Flashboot Flash Boot boot.img
Click to expand...
Click to collapse
Syntax is just the exact command as you typed it (order of the typed words, spelling, etc.). This is extremely important, as a single typo such as a wrong character, improper order, etc. will cause the command to fail.
For instance (and I'm not sure if what you posted above is the exact syntax you actually used or not) for the above command, there is no such thing as "Flashboot", it should be fastboot. And fastboot/adb commands typically don't have the command words capitalized like you have it. Exception is if a directory or filename has caps, in which case it needs to match exactly.
cami0488 said:
"he said". I am a woman*.
Click to expand...
Click to collapse
My apologies there. Pesky pronouns! Of course, on the internet, unless we know beforehand, we can only guess at the proper pronoun; as it often gets impractical to type "he/she" or non-gender specific "they". I'll try to get it right in this thread, moving forward.
cami0488 said:
I did try a fastboot getvar all before, so I'm aware what that is, but I'll have to post short messages around here to reach my 10 post mark so i can start including some screenshot images.
Click to expand...
Click to collapse
Just cut and paste the getvar data. In Windows command prompt, you can right mouse click, select "mark" to highlight the desired getvar text; then Ctrl-C to copy (then just right click Paste or Ctrl-V to paste into an XDA forum message).
---------- Post added at 10:22 AM ---------- Previous post was at 10:15 AM ----------
cami0488 said:
Relative question. What is the difference between manually flashing a ROM through the CMD prompt on my comptuper vs "RUU". I don't have any current operating system on the phone so I can no longer go into the settings and turn off USB debugging and whatever else I've seen instructions on using RUUs. Which all seem to indicate I need an OS before even doing that option.
Click to expand...
Click to collapse
USB debugging only affects adb use while the phone is running. It doesn't affect fastboot, and fastboot will work even when no OS. Further, RUU only requires fastboot, and even then only to reboot into RUU mode.
---------- Post added at 10:24 AM ---------- Previous post was at 10:22 AM ----------
cami0488 said:
I got this .zip file from the XDA ROMs folder off here. I'm not sure if it's an RUU file. However it is not a backup, or so it wasn't labled that way. It was labled as the "stock ROM"
Click to expand...
Click to collapse
If you don't understand what it is, you shouldn't be flashing it. You haven't sufficiently described what it is (or linked the location) so we can't possibly know what it is, or properly help with it, either.
Honestly, no offense intended, it seems like your understanding and knowledge of what you are doing is pretty shaky. I'd suggest reading up for an hour or so of the basic tutorials, guides, Index threads, etc. before doing anything more with the phone (aside from RUU, which is what I am about to recommend for you).
---------- Post added at 10:32 AM ---------- Previous post was at 10:24 AM ----------
cami0488 said:
See, I read about using RUU, but I also read that if you have "S-on" you can't flash anything on the device unless you do it through the cmd prompt.
Click to expand...
Click to collapse
This is completely false.
You only need s-off to flash hboot, radio, change CID/MID, and a few other things. You can flash M8 ROMs, kernels, and a good number of other things from TWRP with s-on. Just find the proper desire ROM, and put it on removable SD or adb push to internal storage; then boot into TWRP and flash the ROM to get OS back.
But RUU is the best option for you.
cami0488 said:
So it can still work via the RUU method with my S-On?
Click to expand...
Click to collapse
Absolutely.
You will need to relock the bootloader with the command: fastboot oem lock
After that, verify in bootloader that it says RELOCKED near the top of the screen.
Then just run the following RUU to get the phone running, and also updated to AT&T Lollipop: http://dl3.htc.com/application/RUU_M8[email protected]50319A_40.45.C33065.00_F_release_426617_signed_2.exe
Rant away, I thought I was pretty clear on the first page Just don't confuse anyone with M_7 in the link, lol...
hack14u said:
Just don't confuse anyone with M_7 in the link, lol...
Click to expand...
Click to collapse
Yeah, the "M" and the "7" has nothing to do with the M7. Its just truncated from: RUU_M8[email protected]50319A_40.45.C33065.00_F_release_426617_signed_2
redpoint73 said:
The above message and rant
Click to expand...
Click to collapse
Thank you for your response. It is much appreciated. However there is no need for the reprimand. What has happen has happen, and I have already decided that I will never again buy a rooted phone with the intention of unrooting it myself. What worked for me on my Xperia Z2, Galaxy Note 2, Galaxy S2, and HTC Evo is obviously nothing similar to what is going on here with the HTC M8. Therefore I will avoid a situation like this entirely by never attempting to unroot phones again. (I'm not personally a fan of flashing ROMs anyways)
Anyways, I'm going to try locking the bootloader as you instructed now, and then downloading the RUU file from HTC. Thanks again. I'll keep this updated.
shirreer said:
From CMD, type:
fastboot getvar all
Take a picture and post it, so we can find you a rom that's suitable for your CID! From then on its really simple.
Click to expand...
Click to collapse
Thank you sir -
hack14u said:
Try what I said. Before, run the command fastboot OEM lock. That will relock the bootloader so you don't throw an error when you run the RUU. The RUU will wipe everything and bring it back to ATT stock. From there you can learn more commands, and how to "fix" things. An RUU is the stock files packaged as a .exe file, you actually run it from your PC like you were installing a piece of software, but it goes to your phone. Don't worry about not having this, or that, it will fix it for you, unless something else is not set right. Give it a shot, you have nothing to lose, literally. Oh, and I always run RUU's from fastboot USB so it detects it pretty quick.
Click to expand...
Click to collapse
Just relocked the bootloader as you instructed
Downloading the RUU that RedPoint73 provided in his last post. Once that is downloaded, All I have to do is run the .exe program like normal and it should prompt me to a location where I can flash the information to the phone?
While i'm sitting here waiting for the RUU to download. I had yet another question. The rooted ROM that the phone was originally flashed with was Android High Definition Mike1986. For whatever reason, it would not ever let us connect to Google Play. Anytime we reboot, hard reset, factory data reset, or format the whole thing back to default settings we would always get the same message "google play services are not available". Now that was a problem of the ROM I stated, but is that related to the ROM that is flashed, or the phone itself?
Ugh oh. So I decided to run the RUU. The phone looked like what seemed to be installing. But the installation estimates it take 10 mins. I's been 20 minutes and is still 0/6 completed. I think something is wrong.
cami0488 said:
While i'm sitting here waiting for the RUU to download. I had yet another question. The rooted ROM that the phone was originally flashed with was Android High Definition Mike1986. For whatever reason, it would not ever let us connect to Google Play. Anytime we reboot, hard reset, factory data reset, or format the whole thing back to default settings we would always get the same message "google play services are not available". Now that was a problem of the ROM I stated, but is that related to the ROM that is flashed, or the phone itself?
Click to expand...
Click to collapse
It probably didn't have any gapps package installed.
---------- Post added at 07:01 PM ---------- Previous post was at 07:00 PM ----------
cami0488 said:
Ugh oh. So I decided to run the RUU. The phone looked like what seemed to be installing. But the installation estimates it take 10 mins. I's been 20 minutes and is still 0/6 completed. I think something is wrong.
Click to expand...
Click to collapse
It looks like it connected, let us know if it worked, like I said before, if it doesn't, there is something else wrong.
---------- Post added at 07:04 PM ---------- Previous post was at 07:01 PM ----------
I don't think I have ever seen any of that after fastboot oem lock. Has anyone else seen anything like that? Something looks very strange, like all of it.
---------- Post added at 07:10 PM ---------- Previous post was at 07:04 PM ----------
Oh ya, ARHD is the ROM you are referring to, some of the best folks out there, great work.
hack14u said:
It probably didn't have any gapps package installed.
Click to expand...
Click to collapse
I found this site - http://www.droidviews.com/restore-att-htc-one-m8-stock-firmware/ that seems to also to have directions to do the exact thing i"m doing now. But the very first part of the instruction yet again says "S-OFF is REQUIRED. It connected, and found the phone, but it stays stuck on that screen right there. I have tried retrying this 3 times. Waiting 20 mins a piece with no progress.
$20 to the dev who gets AOSP to work on Sprint's latest 1.80.651.30, WITHOUT using foreign firmware.
We're about a year into this device, and apparently we have no developers on the Sprint side working on this.
Not sure if that price is worth it to anyone, but I'm a man of my word.
mcwups1 said:
$20 to the dev who gets AOSP to work on Sprint's latest 1.80.651.30, WITHOUT using foreign firmware.
We're about a year into this device, and apparently we have no developers on the Sprint side working on this.
Not sure if that price is worth it to anyone, but I'm a man of my word.
Click to expand...
Click to collapse
You contacted me multiple times about editing the Verizon guide for Sprint.. I took my free time to respond.. and now you post this.. A bit of a slap in the face, no? :silly:
I would contact the Devs working on AOSP personally, however with N already here (and coming soon to the rest of the carriers), I personally don't see anyone taking their time on MM (just an opinion).
I do hope you get it working. :good:
andybones said:
You contacted me multiple times about editing the Verizon guide for Sprint.. I took my free time to respond.. and now you post this.. A bit of a slap in the face, no? :silly:
I would contact the Devs working on AOSP personally, however with N already here (and coming soon to the rest of the carriers), I personally don't see anyone taking their time on MM (just an opinion).
I do hope you get it working. :good:
Click to expand...
Click to collapse
No, you never got back with my question!
I have your zip, but haven't flashed it, because I'm not sure if it needs "modified" for Sprint.
Plus, I am looking for it to work with Sprint firmware first.
mcwups1 said:
No, you never got back with my question!
I have your zip, but haven't flashed it, because I'm not sure if it needs "modified" for Sprint.
Plus, I am looking for it to work with Sprint firmware first.
Click to expand...
Click to collapse
"No, you never got back with my question!"
I responded last night, and I quoted you so you'd get a notification to see it.
http://forum.xda-developers.com/showpost.php?p=70256059&postcount=15
The whole point of this method is to get back to stock Verizon/Sprint.
If you do my method you will be back on 100% Sprint (Since you are flashing the Sprint RUU AFTER the modified firmware) AND AOSP ROMs working. I don't know why, but it works. It's been confirmed on a number of Verizon users AND Sprint.
"Plus, I am looking for it to work with Sprint firmware first"
Then why did you contact me multiple times? I am not going to apologize for taking longer than you'd like to respond.. I wrote the guide for Verizon, so excuse me for not wanting to brick your device with rushed info..
Like I said, I hope you get it working.. I did respond in the thread, and as I said if you need help editing the android.info.txt, let me know. :good:
I didn't get it. Responded to the linked thread /post.
Thank you.
I understood your instructions for the firmware and RUU, but didn't think your zip would work with my Sprint device. Thank you so much for the deeper explanation.
Will report back here....
mcwups1 said:
I didn't get it. Responded to the linked thread /post.
Thank you.
I understood your instructions for the firmware and RUU, but didn't think your zip would work with my Sprint device. Thank you so much for the deeper explanation.
Will report back here....
Click to expand...
Click to collapse
You are very welcome my friend!
AOSP/CM ROMs are a great way to change up the device so I understand the want to use them, hence how this method was found.
andybones said:
You are very welcome my friend!
AOSP/CM ROMs are a great way to change up the device so I understand the want to use them, hence how this method was found.
Click to expand...
Click to collapse
@andybones
Just to make sure (on both threads, sorry), my CID is 11111111.
I don't use the Sprint CID, I change the android text to the Super CID number, right?
Okay.
Everything done and I didn't brick.
New problem.
I only have 3G, even after the RUU.
Something tells me I shouldn't have GSM options?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mcwups1 said:
Okay.
Everything done and I didn't brick.
New problem.
I only have 3G, even after the RUU.
Something tells me I shouldn't have GSM options?
Click to expand...
Click to collapse
In bootloader run these cmds
fastboot erase modemst1
fastboot erase modemst2
Okay. It appears I have LTE, but now I can't make calls.
Edit: Now, since I woke up this morning, I have no data. I can boot up, but I cannot make calls or message anyone.
Says my device is not activated, and I need to call customer service.
Or, you are not authorized to call this account (calling my wife), if you would like more services, contact customer service.
Showing all zeros for a phone number.
000-000-0000
@andybones
Check your Gmail.
mcwups1 said:
@andybones
Check your Gmail.
Click to expand...
Click to collapse
Thank you kindly my friend! Very much appreciated.
andybones said:
Thank you kindly my friend! Very much appreciated.
Click to expand...
Click to collapse
I can flash CM, but I can't use it.
I cannot make calls or message anyone.
If I restore my Sense backup, then I have no data. I have to erase modems again, just to get messaging back and to get my Sprint ID to return and give me my phone number again.
This has been a major headache, and I don't think this will actually work fully on my device.
Curious to know if you know why I had to input a PIN after flashing that modified firmware zip after reboot?
mcwups1 said:
I can flash CM, but I can't use it.
I cannot make calls or message anyone.
If I restore my Sense backup, then I have no data. I have to erase modems again, just to get messaging back and to get my Sprint ID to return and give me my phone number again.
This has been a major headache, and I don't think this will actually work fully on my device.
Curious to know if you know why I had to input a PIN after flashing that modified firmware zip after reboot?
Click to expand...
Click to collapse
Can't say about Sprint usage and AOSP ROMs or sprint anything really so can't comment on that.
After flashing the firmware it wiped my system so it had no ROM to boot to, so I had to hold volume buttons and power to get into bootloader and then ran the VZW RUU.
I have been using multirom personally since this method as well.
I still wish someone would find a way to get AOSP working on Sprint firmware.
After wiping modems, updating PRL and Profile, I have a working phone again on Sense.
I'm not sure what flashing that zip did, but I'm thinking it changes the internal partitions of firmware, and that Sprint either blocks partitions or doesn't have them, and the zip modded them, or added them.
But WTF do I know?
mcwups1 said:
I still wish someone would find a way to get AOSP working on Sprint firmware.
After wiping modems, updating PRL and Profile, I have a working phone again on Sense.
I'm not sure what flashing that zip did, but I'm thinking it changes the internal partitions of firmware, and that Sprint either blocks partitions or doesn't have them, and the zip modded them, or added them.
But WTF do I know?
Click to expand...
Click to collapse
As I. It seems once/if theres a fix for Sprint, it should also hopefully be the same for Verizon.
Your input is as good as the rest of us.
I've gotten CM/Lineage to work on my Sprint HTC 10. I did have to flash an international firmware zip to get it to get past the boot logo but now it's fine. Note though that I did delete the modems, radio, cache and recovery out of the firmware package before I flashed it. This is likely why you have issues with data now if you didn't do so.
That said, data is still iffy at times on AOSP without toggling some settings after rebooting so it might be worth it for some people to wait until that's fixed before proceeding.
ssmercurys said:
I've gotten CM/Lineage to work on my Sprint HTC 10. I did have to flash an international firmware zip to get it to get past the boot logo but now it's fine. Note though that I did delete the modems, radio, cache and recovery out of the firmware package before I flashed it. This is likely why you have issues with data now if you didn't do so.
That said, data is still iffy at times on AOSP without toggling some settings after rebooting so it might be worth it for some people to wait until that's fixed before proceeding.
Click to expand...
Click to collapse
You should do a write up on the Sprint forums for others.
Their are builds that are out now for sprint that doesn't require a custom firmware
trev23sks said:
Their are builds that are out now for sprint that doesn't require a custom firmware
Click to expand...
Click to collapse
How?
This is the first carrier unlocked phone I've purchased. It's brand new and I bought it because I'm an M8 fanboy and my first M8 is dying. I'm on AT&T. I just got the phone and installed my SIM and setup my google accounts and all that stuff. I want to update Android but when I go to setting/about/software updates all it says is "checking". It's been checking for over an hour. Did I do something wrong? Is there a way to get the latest OTA Android for an AT&T M8?
My plan is to get to MM then unlock the bootloader and flash TWRP so I can start flashing custom ROM's. I never did anything to my original M8 but have done rooting etc on my old HTC Vivid and both my ASUS tablets.
Thanks in advance for your help.
Post fastboot getvar all result (remove serial & imei no.)
If it is a EU variant, then you can install RUU to update it to Marshmallow.
ckpv5 said:
Post fastboot getvar all result (remove serial & imei no.)
If it is a EU variant, then you can install RUU to update it to Marshmallow.
Click to expand...
Click to collapse
First, thanks for your reply ckpv5.
Second, not sure I'm following you. I can connect via ADB and it show this when I use the devices command:
device product:htc_europe model:HTC_One_M8 device:htc_m8
Is that the correct ADB command or am I just doing it wrong. Could you please provide more information. I'd really appreciate it. This is my first carrier unlocked phone so I'm a noob at this.
theandies said:
First, thanks for your reply ckpv5.
Second, not sure I'm following you. I can connect via ADB and it show this when I use the devices command:
device product:htc_europe model:HTC_One_M8 device:htc_m8
Is that the correct ADB command or am I just doing it wrong. Could you please provide more information. I'd really appreciate it. This is my first carrier unlocked phone so I'm a noob at this.
Click to expand...
Click to collapse
adb reboot bootloader
fastboot getvar all
Thanks for everyone's replies so far.
Here is what I get when doing the adb commands suggested.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now help me continue with getting this phone updated to at least MM.
:good:
theandies said:
Thanks for everyone's replies so far.
Here is what I get when doing the adb commands suggested.
Now help me continue with getting this phone updated to at least MM.
:good:
Click to expand...
Click to collapse
Download this RUU.zip
Rename it by deleting everything in name of the .zip except for 0P6BIMG (and .zip of course)
Place the renamed .zip onto your extSD card and put it into your phone. (the card must be formatted to FAT32 for this, and if it is 32gb or less, it probably already is)
Boot to bootloader and follow the prompts (vol up to confirm the flash ~ power button to reboot after it's flashed)
And that's it, super easy.
Make sure to delete the renamed .zip after the flash, or every time you boot to bootloader it'll try to update again
Good luck!
Awesome. Trying it now.
Can you school me on the information that I posted? I'm used to messing with WiFi only tablets and this is my first time messing this deep into a phone. I don't want to brick my brand new M8 so I'm going real slow.
Here is some more info if needed. I see it says s-off, is that correct? Also, once I update can I then proceed to flash TWRP and custom ROM's?
Thanks. Updated to Android 6!!! Now beware I'll have a lot more questions.
theandies said:
Thanks. Updated to Android 6!!! Now beware I'll have a lot more questions.
Click to expand...
Click to collapse
Cool! glad I could help.
A little info: since you are S-Off you shouldn't need to unlock the bootloader before you flash TWRP and ROMs, S-Off is all you'll need.
So it IS s-off! Cool. Any way you could tell me how you knew what RUU to use? Just trying to learn.
theandies said:
So it IS s-off! Cool. Any way you could tell me how you knew what RUU to use? Just trying to learn.
Click to expand...
Click to collapse
Your version-main in your getvar/ OS in your bootloader is your current firmware version. To find what you need for updating, the third series of numbers is what is important to match. In your case that was 401 which = WWE/Interanational
But that won't matter with your M8, only if you get a newer HTC device. The RUU I linked you to is not only the latest, but also the last firmware/ROM update for the M8. It won't be updated anymore and hasn't been for almost a year. In general, manufacturers and carriers will only update a device for two years.
xunholyx said:
Your version-main in your getvar/ OS in your bootloader is your current firmware version. To find what you need for updating, the third series of numbers is what is important to match. In your case that was 401 which = WWE/Interanational
But that won't matter with your M8, only if you get a newer HTC device. The RUU I linked you to is not only the latest, but also the last firmware/ROM update for the M8. It won't be updated anymore and hasn't been for almost a year. In general, manufacturers and carriers will only update a device for two years.
Click to expand...
Click to collapse
Understood. I have one more problem. My mobile data is not working. I checked all the APN settings and all of them are grayed out. Any ideas on what to do? I'll post a screenshot in a while. Just got to work.
I also tried *#*#4636#*#* but I really don't want to do anything with that yet as I really don't know what to do there and don't want to make things worse.
Texting and phone calls are working just fine.
Well snooping around the internet at work tonight I was able to figure out that I need to set my APN setting. More snooping and I found an APN setting that works......kind of. It will not go 4G LTE only HSPA. Here is a screen shot and the APN settings that get me HSPA.
I will try and duplicate the APN settings from my old phone in the mean time does anyone have a known good 4G (or 4G LTE) AT&T APN that will work with this phone? Hopefully I've posted enough information for the experts to help me get back up to speed.
Either of those APNs should work fine. Literally, the grayed out one (nextgenphone) is the one I'm on now, and it works flawlessly for me (3G, LTE, MMS, etc.). The one you entered (ATT Phone) I believe is actually the new/current one being used as default on most newer ATT phones, and should work fine as well. Your problem isn't APN, I think it's the RUU you used.
I would suggest using the AT&T RUU 6.20.502.5 from here (see RUU section): https://forum.xda-developers.com/showthread.php?t=2751432
Note the red text below the RUU. If you get Error 155 installing the RUU, you'll need to fastboot flash the firmware, before the RUU will install properly (peculiarity of US Marshmallow RUUs).
Reason you need the AT&T RUU, is that by flashing the Euro RUU, you installed the Euro radio, which is only intended to support LTE bands 3, 7, 8, 20. AT&T uses LTE bands 2, 4, 5, and 17. Therefore, you are missing support for every LTE band used by AT&T (the band or bands used by AT&T in you local area being the most important), and explains why everything works but LTE.
Great information redpoint73. I'll flash the other RUU this weekend.
Please bear with me, when you say flash via. fastboot you mean using ADB and pushing it though USB from my computer? Forgive me but as I said this is my first phone I've messed with this deep. My experience has been on ASUS tablets and most of the custom stuff done on them is usually flashed via SD card (or internal storage) 99% of the time. I can do it with the help of XDA I just don't want to render my new M8 inoperable.
theandies said:
when you say flash via. fastboot you mean using ADB and pushing it though USB from my computer?
Click to expand...
Click to collapse
If you read the red colored note regarding Error 155, under the RUUs in my Index thread (which I linked) you will see another link there, to a separate post/thread that will tell you exactly how to flash the firmware (if needed). Follow those instructions, and you will be good.
Flash via fastboot uses your computer and USB. But keep in mind that adb and fastboot are similar, but not exactly the same.
I see the RUU you suggested is an .exe file. Just connect via ADB and run that file? Also I downloaded the firmware you suggested as well. To avoid any issues should I flash that first before the RUU?
Thanks
theandies said:
I see the RUU you suggested is an .exe file. Just connect via ADB and run that file? Also I downloaded the firmware you suggested as well. To avoid any issues should I flash that first before the RUU?
Thanks
Click to expand...
Click to collapse
Just hook up your phone and double click on the download. The .exe will install a lot like software for your PC
If it fails to install booting to bootloader first before starting the RUU.exe sometimes helps.
On HTC's US website, there are both manual update instructions and a download for the RUU
I'm not sure if you'll need to flash the firmware first since you are already on Android 6, but it couldn't hurt to do so, and you might actually need to.
Awesome, this place is full of great people willing to help. I just wish I could reciprocate more.
theandies said:
Also I downloaded the firmware you suggested as well. To avoid any issues should I flash that first before the RUU?
Click to expand...
Click to collapse
It wouldn't hurt to flash firmware first. Only reason I would suggest folks to run the RUU first (and see if it works) is because not everyone is comfortable using fastboot commands to flash the firmware (and therefore may avoid having to learn how to do that). But if you are comfortable with the process to flash the firmware (it's not hard), then go ahead and do so before running the RUU.
Like xunholyx, I'm not sure if you need to flash the firmware first, or not. If you were coming from Lollipop, you definitely would need to. I have a feeling that you will indeed need to flash the US firmware before the RUU will install. Even though you are on Marshmallow firmware, it's the Euro one, so I think (but not sure) the RUU will still fail until you flash the US MM firmware.
EDIT - Forget it I found it........duh.
Thanks redpoint73. I'm going to flash the firmware first because of what you said (Euro phone vs. US).
I can't seem to find your post on how to do that again in the sea of posts. I thought I bookmarked it but it's not there. Can you be so kind as to link it up.
:good: