Consistant Hot Reboots and loss of data signal "!" - Nexus 6 Q&A, Help & Troubleshooting

So it seems like since i updated everything to 5.1 (radio etc) ive been having issues with my phone hot rebooting and also losing data. Ill have lte for hours and then all of a sudden i still have full bars but there is a "!" instead of 3G or LTE. Currently im on Temaseks latest nightly but it was happening on chroma also. My Baseband says "MDM9625_104446.01.02.95R". Any idea what could be causing this? (Im also not flashing anything crazy when I flash these roms. I flashed Temaseks nightly about 2 hours ago with the recommended banks gapps, and I just got a hotboot and lost datasignal).

HaiKaiDo said:
So it seems like since i updated everything to 5.1 (radio etc) ive been having issues with my phone hot rebooting and also losing data. Ill have lte for hours and then all of a sudden i still have full bars but there is a "!" instead of 3G or LTE. Currently im on Temaseks latest nightly but it was happening on chroma also. My Baseband says "MDM9625_104446.01.02.95R". Any idea what could be causing this? (Im also not flashing anything crazy when I flash these roms. I flashed Temaseks nightly about 2 hours ago with the recommended banks gapps, and I just got a hotboot and lost datasignal).
Click to expand...
Click to collapse
Did you clear cache? Clean flash or dirty?

Evolution_Freak said:
Did you clear cache? Clean flash or dirty?
Click to expand...
Click to collapse
Hey There. I'm a fan of never dirty flashing. I always wipe a few times before I flash anything. I dont do any type of titanium backup or anything either. I even deleted everything on my storage except for the TWRP backup folder and my roms folder so theres nothing weird left behind. Other than the baseband there was nothing else I needed to flash right?

HaiKaiDo said:
Hey There. I'm a fan of never dirty flashing. I always wipe a few times before I flash anything. I dont do any type of titanium backup or anything either. I even deleted everything on my storage except for the TWRP backup folder and my roms folder so theres nothing weird left behind. Other than the baseband there was nothing else I needed to flash right?
Click to expand...
Click to collapse
Thanks for clarifying that for me. No, I don't think you've missed anything. Before trying anything too drastic, I'd suggest flashing the factory image, if you can, and see if it continues to happen. I know that can be a hassle but it also could fix whatever might be broken.

Evolution_Freak said:
Thanks for clarifying that for me. No, I don't think you've missed anything. Before trying anything too drastic, I'd suggest flashing the factory image, if you can, and see if it continues to happen. I know that can be a hassle but it also could fix whatever might be broken.
Click to expand...
Click to collapse
hmm ill give it a try. Seemslike googles dev site is having problems at the moment and the download is going really slow...of course heh. ill report back when im on stock.

HaiKaiDo said:
So it seems like since i updated everything to 5.1 (radio etc) ive been having issues with my phone hot rebooting and also losing data. Ill have lte for hours and then all of a sudden i still have full bars but there is a "!" instead of 3G or LTE. Currently im on Temaseks latest nightly but it was happening on chroma also. My Baseband says "MDM9625_104446.01.02.95R". Any idea what could be causing this? (Im also not flashing anything crazy when I flash these roms. I flashed Temaseks nightly about 2 hours ago with the recommended banks gapps, and I just got a hotboot and lost datasignal).
Click to expand...
Click to collapse
adjust your voltages so that its best for your device. raise or lower your voltages until the reboots stop.

simms22 said:
adjust your voltages so that its best for your device. raise or lower your voltages until the reboots stop.
Click to expand...
Click to collapse
Wouldnt that mean theres something wrong with my phone? I havnt messed (and really dont ever) mess with OC or Voltages.

HaiKaiDo said:
Wouldnt that mean theres something wrong with my phone? I havnt messed (and really dont ever) mess with OC or Voltages.
Click to expand...
Click to collapse
no. the nexus 6 has 15 different pvc bin numbers. that means 15 different voltage charts to follow, depending on your devices bin number. and for each bin number, each individual device will vary. so, it might be alright, but most likely you would have to adjust slightly for best voltage for your personal device.

Evolution_Freak said:
Thanks for clarifying that for me. No, I don't think you've missed anything. Before trying anything too drastic, I'd suggest flashing the factory image, if you can, and see if it continues to happen. I know that can be a hassle but it also could fix whatever might be broken.
Click to expand...
Click to collapse
+1! Fastboot factory image. That's what I'd do. :thumbup:

Related

[Q] How manytimes we can install rom in nexus one

I tried 5 different roms and i feel cyanogenmod 6 rc2 version is stable. but i am worrying if i try one more custom rom then will it break my phone?. Please tell me how many time we can install roms in the phone.
Will it create a bad sector on my phone.
dlcsboop said:
I tried 5 different roms and i feel cyanogenmod 6 rc2 version is stable. but i am worrying if i try one more custom rom then will it break my phone?. Please tell me how many time we can install roms in the phone.
Will it create a bad sector on my phone.
Click to expand...
Click to collapse
Well as long as you're wiping between different ROMs you should be fine. And even if you are there won't be any permanent damage. The only way you can brick your phone is by installing a bad/old radio.
Even if there's a limited number of "flashing" the phone you won't reach it before you get a new phone.
Likely in the millions of times.
Don't worry about it.
Its the same question like "how many times can you write data on a sd card", you already got a new one when you reach that number
Flash memory has a certain number of read write times until it fails. But that number is so high that it will be years from now.
how can i know if i have a bad sector??
Amritttt said:
how can i know if i have a bad sector??
Click to expand...
Click to collapse
You have to wipe/install a new rom and copy logs to sd card from either other or advanced menu, havent used amon_ra recovery in forever
So, how do we get to the answer of how many times one can flash their phone?
That is such an interesting question. The answer must be had!
androidcues said:
So, how do we get to the answer of how many times one can flash their phone?
That is such an interesting question. The answer must be had!
Click to expand...
Click to collapse
Lol, I may be able to tell you soon, flashing nightlies every day
How many stars are there in the Galaxy?
Flippy125 said:
Lol, I may be able to tell you soon, flashing nightlies every day
Click to expand...
Click to collapse
EVERY DAY ISN'T ENOUGH!!!!!!!1111oneeleven
Flippy125 said:
Lol, I may be able to tell you soon, flashing nightlies every day
Click to expand...
Click to collapse
Hey, I am a total newbie but I would like to flash the nightlies as well. I usually backup all my apps and settings using Titanium Backup, do a Nandroid backup, wipe and then flash the new ROM. However, backing up all apps and settings using Titanium Backup and restoring them after flashing the nightly is quite time consuming. Even worse is arranging the application short cuts / widgets on the desktops after a fresh install.
Nandroid will allow me to go back to backed up version after I have played around with the nightly for a few hours. But then I lose all the features of the nightly once I am back to my old ROM. As I am carrying only a single phone, it becomes mandatory for me to restored the Contacts, Messages, Applications and Settings after flashing a new ROM.
It may sound stupid but is there a better and faster way of doing things without having to restore all applications/settings from the backup so that I also could try out the nightlies? How do you manage this?
For the most part, you can flash nightlies without a wipe, if you're going from CM to CM. If you see weird behavior after flashing, then go back and wipe, and if that doesn't work do a complete wipe and flash.
If you're on another ROM, then I would definately wipe...
Sent from my Nexus One using XDA App
Exactly 6.3 times. That is all. But nobody mentions it.
danger-rat said:
For the most part, you can flash nightlies without a wipe, if you're going from CM to CM. If you see weird behavior after flashing, then go back and wipe, and if that doesn't work do a complete wipe and flash.
If you're on another ROM, then I would definately wipe...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Thanks, danger-rat! I'll give it a shot
meechto said:
Thanks, danger-rat! I'll give it a shot
Click to expand...
Click to collapse
I strongly suggest wiping cache and dalvik-cache prior to flashing a new nightly, it prevents **** and doesn't affect your settings/files
Haven't been on CM for awhile, but if you use Launcher Pro or ADW they have Homescreen backups. Have had good luck with MyBackUpPro too.
Ken
3 times. 1...2...crunch...3. Haven't you all seen the tootsie pop commercial?
androidcues said:
So, how do we get to the answer of how many times one can flash their phone?
That is such an interesting question. The answer must be had!
Click to expand...
Click to collapse
How many licks does it take to get to the Tootsie Roll center of a Tootsie Pop? LMAO, that's what I WANNA KNOW!

Can't turn off wifi toggle

has any one been having any trouble with their wifi on their nexus 6, randomly the wifi toggle will stop working the toggle will be off and it still says "Turning Wi-Fi on..." i've booted into recovery and cleared cache and rebooted the phone and it worked the first time and it's been acting up again and this time clearing the cache isn't working does anyone else have any ideas without doing a factory reset.
humpty123 said:
has any one been having any trouble with their wifi on their nexus 6, randomly the wifi toggle will stop working the toggle will be off and it still says "Turning Wi-Fi on..." i've booted into recovery and cleared cache and rebooted the phone and it worked the first time and it's been acting up again and this time clearing the cache isn't working does anyone else have any ideas without doing a factory reset.
Click to expand...
Click to collapse
maybe try just flashing the system img, then wipe cache's again before booting. if that doesnt work, its may be time for the dreaded fdr.
I've never been into flashing system img & fdr? It's just sad because I had the same issue before also losing signal with my device. Til I got a replacement and the replacement device is starting to act up also.
Sent from my Nexus 6 using XDA
bweN diorD said:
maybe try just flashing the system img, then wipe cache's again before booting. if that doesnt work, its may be time for the dreaded fdr.
Click to expand...
Click to collapse
okay so put the phone in recovery and did cache wipe and reset it from recovery also and got everything set up again and still it shows Wi-Fi toggled off and saying turning on Wi-Fi im not sure what todo at this point.
https://goo.gl/photos/bdHB8Nw2tbH71LMj6
humpty123 said:
okay so put the phone in recovery and did cache wipe and reset it from recovery also and got everything set up again and still it shows Wi-Fi toggled off and saying turning on Wi-Fi im not sure what todo at this point.
Click to expand...
Click to collapse
my only other suggestion would be to re-flash. you could try just the system partition, but if it were me i would just go all in for full clean flash.
im sure Simms will get on me for saying so, but you can just grab wugs toolkit and be done in 20min or so.
bweN diorD said:
my only other suggestion would be to re-flash. you could try just the system partition, but if it were me i would just go all in for full clean flash.
im sure Simms will get on me for saying so, but you can just grab wugs toolkit and be done in 20min or so.
Click to expand...
Click to collapse
I've never flashed before i know from what i hear its really easy for Nexus devices. but i'm just curious what would of caused this like from my first N6 since December and it acts up now in Sept and having the replacement N6 acting up the same way.
Is it rooted with mods or completely stock? If stock, try deleting the saved wireless networks..
danarama said:
Is it rooted with mods or completely stock? If stock, try deleting the saved wireless networks..
Click to expand...
Click to collapse
100% stock I can't get access to any saved networks at all
https://goo.gl/photos/34veZPQvW3pLiB5YA
humpty123 said:
I've never flashed before i know from what i hear its really easy for Nexus devices. but i'm just curious what would of caused this like from my first N6 since December and it acts up now in Sept and having the replacement N6 acting up the same way.
Click to expand...
Click to collapse
these random issues usually come from a corrupt file, either by an update or some other means. its hard to impossible to pinpoint the cause usually.
if you never flashed before, its best to read up on it a bit first. wugs walks you through the steps, from downloading the files, and drivers, to the flashing. its not foolproof, but if you follow the lead of the script, its not hard to figure out.
bweN diorD said:
these random issues usually come from a corrupt file, either by an update or some other means. its hard to impossible to pinpoint the cause usually.
if you never flashed before, its best to read up on it a bit first. wugs walks you through the steps, from downloading the files, and drivers, to the flashing. its not foolproof, but if you follow the lead of the script, its not hard to figure out.
Click to expand...
Click to collapse
well i have before but that was so long ago and that was for my MyTouch and HTC Sensation but that was years ago. Now I know things are easier but I've never really been into flashing and the only reason I did back then was for updates and different version of Sense UI but since I've been using Nexus Devices I didn't have a need or desire to actually flash. Pretty much I'm a NOOB! :laugh:
but I don't see why wouldn't a factory reset fix it. even if it was temp.
humpty123 said:
well i have before but that was so long ago and that was for my MyTouch and HTC Sensation but that was years ago. Now I know things are easier but I've never really been into flashing and the only reason I did back then was for updates and different version of Sense UI but since I've been using Nexus Devices I didn't have a need or desire to actually flash. Pretty much I'm a NOOB! :laugh:
but I don't see why wouldn't a factory reset fix it. even if it was temp.
Click to expand...
Click to collapse
a factory reset only deletes data, it does not restore any of the file system to its original state.
bweN diorD said:
a factory reset only deletes data, it does not restore any of the file system to its original state.
Click to expand...
Click to collapse
oh... so when I called Motorola they told me to wipe cache how did that help the first time ?
humpty123 said:
oh... so when I called Motorola they told me to wipe cache how did that help the first time ?
Click to expand...
Click to collapse
clearing the cache is always a good idea, i think i suggested that earlier.
i dont know how to explain well what cache is exactly, its not part of the file system, its more like temp data storage i believe.
bweN diorD said:
clearing the cache is always a good idea, i think i suggested that earlier.
i dont know how to explain well what cache is exactly, its not part of the file system, its more like temp data storage i believe.
Click to expand...
Click to collapse
yeah i tried that a few times today and it did nothing... i'm about to give up since i don't have a PC anymore i use a Chromebook
humpty123 said:
yeah i tried that a few times today and it did nothing... i'm about to give up since i don't have a PC anymore i use a Chromebook
Click to expand...
Click to collapse
def of cache from google
"In cell phones and networks, a cache usually refers to a memory storage area in the phone or network that stores copies of information that is likely to be needed in the near future, so it can be accessed faster."
i dont know how to flash with a chrome book, if possible. sorry
bweN diorD said:
def of cache from google
"In cell phones and networks, a cache usually refers to a memory storage area in the phone or network that stores copies of information that is likely to be needed in the near future, so it can be accessed faster."
i dont know how to flash with a chrome book, if possible. sorry
Click to expand...
Click to collapse
all i know it happened a day after i got the last update from T-Mobile. i should them back and tell them i'm having the same issues with my phone have them replace it for me again.
humpty123 said:
all i know it happened a day after i got the last update from T-Mobile. i should them back and tell them i'm having the same issues with my phone have them replace it for me again.
Click to expand...
Click to collapse
thats pretty consistent with what i said earlier. these type of issues frequently arise after updates. files dont update exactly right and something gets corrupted.
bweN diorD said:
thats pretty consistent with what i said earlier. these type of issues frequently arise after updates. files dont update exactly right and something gets corrupted.
Click to expand...
Click to collapse
i decided to call T-Moblie and talk to them they told me to take it to a store and get it dianogsed and they will call to get it replaced since it is the 64GB and stores don't have it.... I just want the Wi-Fi to work even though i don't use it all the time but still.

No service on virgin mobile Desire 510 suddenly

Hi all. I could use some help with this issue I've been having. Basically, about a week ago, I went on a trip to Colorado and at the same time had an issue with my data through VM. After talking to them, I had to change my service plan. Since then I haven't been able to maintain any kind of connection with VM; it reads no service a lot, even in places I've never had an issue (home, school, practically everywhere...). Before I deal with VMs customer service yet again, I wanted to see if there is any issues with my phone/rom/kernel and any updates to either I could use.
http://forum.xda-developers.com/desire-510/help/how-to-treat-sd-internal-storage-t3029186
I used this guide to root my phone and install all that stuff in order to use my sd card as my internal storage. So, could there be some issue with that wHich could cause me to not be able to get any service? Is there anything I could do on my side to determine if the problem is with my phone?
If the issue lies with VMs network, are there any updates to the kernel or roms with newer versions of Android that I could use and still use my sd card as my main storage? Side question: on any rooted device, could you do the ad card as main memory thing with the apps, Apparted and Link2sd?
Thanks anyone who can help me out.
Edit: I'm running Android 4.4.2
Kernel version
3.4.0-Missed-Kernel-v2.6.1
[email protected] #4
SMP PREEMPT
Build number
1.48.652.2 CL373881 release-keys
Umm, can think what else I should add. Thanks
Cypher5235 said:
Hi all. I could use some help with this issue I've been having. Basically, about a week ago, I went on a trip to Colorado and at the same time had an issue with my data through VM. After talking to them, I had to change my service plan. Since then I haven't been able to maintain any kind of connection with VM; it reads no service a lot, even in places I've never had an issue (home, school, practically everywhere...). Before I deal with VMs customer service yet again, I wanted to see if there is any issues with my phone/rom/kernel and any updates to either I could use.
http://forum.xda-developers.com/desire-510/help/how-to-treat-sd-internal-storage-t3029186
I used this guide to root my phone and install all that stuff in order to use my sd card as my internal storage. So, could there be some issue with that wHich could cause me to not be able to get any service? Is there anything I could do on my side to determine if the problem is with my phone?
If the issue lies with VMs network, are there any updates to the kernel or roms with newer versions of Android that I could use and still use my sd card as my main storage? Side question: on any rooted device, could you do the ad card as main memory thing with the apps, Apparted and Link2sd?
Thanks anyone who can help me out.
Edit: I'm running Android 4.4.2
Kernel version
3.4.0-Missed-Kernel-v2.6.1
[email protected] #4
SMP PREEMPT
Build number
1.48.652.2 CL373881 release-keys
Umm, can think what else I should add. Thanks
Click to expand...
Click to collapse
Tap settings and then scroll to the bottom and look for either software update or about phone and then look for the option to select PRL update, do that and then go back and do a profile update in the same spot as the PRL update and then reboot the phone.
MrMike2182 said:
Tap settings and then scroll to the bottom and look for either software update or about phone and then look for the option to select PRL update, do that and then go back and do a profile update in the same spot as the PRL update and then reboot the phone.
Click to expand...
Click to collapse
Yep, I've tried that one. But for the sake of thoroughness, I tried it twice more to no avail. Any other tips/tricks?
Cypher5235 said:
Yep, I've tried that one. But for the sake of thoroughness, I tried it twice more to no avail. Any other tips/tricks?
Click to expand...
Click to collapse
Flash this via twrp and let me know if it works.. After you flash this wipe the cache and dalvic cache too then reboot.
Edit: Are you running the stock rom or something else?
MrMike2182 said:
Flash this via twrp and let me know if it works.. After you flash this wipe the cache and dalvic cache too then reboot.
Edit: Are you running the stock rom or something else?
Click to expand...
Click to collapse
Alright, tried that, too, now. Still a no-go.
I'm not sure if I have a custom rom, but I don't think so. I just followed that guide, and I believe it only needed me to install a custom kernel. This thing acts weird. I'll pick it up and unlock it, and it will have 5 bars, but then quickly jump down to 1 then no service. As I'm driving to class, I'll have 4-5 bars but when I get to school, it's gone. It feels like whenever there are WiFi signals, I lose my service connection, if that helps.
Thank you so much, btw.
Cypher5235 said:
Alright, tried that, too, now. Still a no-go.
I'm not sure if I have a custom rom, but I don't think so. I just followed that guide, and I believe it only needed me to install a custom kernel. This thing acts weird. I'll pick it up and unlock it, and it will have 5 bars, but then quickly jump down to 1 then no service. As I'm driving to class, I'll have 4-5 bars but when I get to school, it's gone. It feels like whenever there are WiFi signals, I lose my service connection, if that helps.
Thank you so much, btw.
Click to expand...
Click to collapse
Install this and see what happens but first create a backup of your current system in recovery... http://forum.xda-developers.com/desire-510/orig-development/modded-cm11-32-bit-t3245291/post63749189
MrMike2182 said:
Install this and see what happens but first create a backup of your current system in recovery... http://forum.xda-developers.com/desire-510/orig-development/modded-cm11-32-bit-t3245291/post63749189
Click to expand...
Click to collapse
Hmm, definitely going to try this tonight. I've now tried to revert to my stock image, and things just haven't gone well since then. So, since I've already removed or backed up all data, should I just wipe everything (data, system, boot, cache, dalvik, etc), flash root, flash custom kernel, then restore this rom? That way, everything is fresh with no chance of interferences?
Cypher5235 said:
Hmm, definitely going to try this tonight. I've now tried to revert to my stock image, and things just haven't gone well since then. So, since I've already removed or backed up all data, should I just wipe everything (data, system, boot, cache, dalvik, etc), flash root, flash custom kernel, then restore this rom? That way, everything is fresh with no chance of interferences?
Click to expand...
Click to collapse
No flashing anything the boot/kernel is already in the folder just wipe and restore no using custom kernels there's already a custom kernel in it. It already has root access you do not even need a computer to do this just download extract and move the modded folder to twrps backup folder and restore. This is a full custom modified CyanogenMod 11.. Not stock rom at all.
MrMike2182 said:
No flashing anything the boot/kernel is already in the folder just wipe and restore no using custom kernels there's already a custom kernel in it. It already has root access you do not even need a computer to do this just download extract and move the modded folder to twrps backup folder and restore. This is a full custom modified CyanogenMod 11.. Not stock rom at all.
Click to expand...
Click to collapse
Okay, wow. I really like this, man. It's really slick. But, sadly, I'm still SOL. Sometimes there is a connection with VM, but it goes away quickly. I've really appreciated your help, but the problem seems to lay on VMs side, or there is a physical problem in my phone preventing it from maintaining a connection.
Im going to try to deal with their customer service and see if they can do anything. In the end, the phone only cost me $50, I guess. If I get it worked out, I'll post what it was about so you may be able to help the next guy with the issue, lol.
Cypher5235 said:
Okay, wow. I really like this, man. It's really slick. But, sadly, I'm still SOL. Sometimes there is a connection with VM, but it goes away quickly. I've really appreciated your help, but the problem seems to lay on VMs side, or there is a physical problem in my phone preventing it from maintaining a connection.
Im going to try to deal with their customer service and see if they can do anything. In the end, the phone only cost me $50, I guess. If I get it worked out, I'll post what it was about so you may be able to help the next guy with the issue, lol.
Click to expand...
Click to collapse
Lol that's definitely gotta be VM's side then.. I'm on VM to but let me ask you a question... Is that a pay as you go, like 1 monthly payment or is it prepaid? If it's the monthly payment then ask VM to reprovision the phone but restore back to your stock backup before calling.
MrMike2182 said:
Lol that's definitely gotta be VM's side then.. I'm on VM to but let me ask you a question... Is that a pay as you go, like 1 monthly payment or is it prepaid? If it's the monthly payment then ask VM to reprovision the phone but restore back to your stock backup before calling.
Click to expand...
Click to collapse
It's their $35/month unlimited plan. I just got off the phone with them after 1.5 hours, so not that long, lol. They claim there is a cell tower being worked on, and everything should clear up in 48-72 hours....and yet I can't get a stable signal 20 miles away at school, so it sounds like a rote answer when they have no clue. On the other hand, my wife's S2 barely gets a signal, too.
They are going to comp my for the 2 weeks it's been down, tho. If after this weekend there isn't any improvment....wwell, I'll figure something out, I guess.
Cypher5235 said:
It's their $35/month unlimited plan. I just got off the phone with them after 1.5 hours, so not that long, lol. They claim there is a cell tower being worked on, and everything should clear up in 48-72 hours....and yet I can't get a stable signal 20 miles away at school, so it sounds like a rote answer when they have no clue. On the other hand, my wife's S2 barely gets a signal, too.
They are going to comp my for the 2 weeks it's been down, tho. If after this weekend there isn't any improvment....wwell, I'll figure something out, I guess.
Click to expand...
Click to collapse
The "Cell tower being worked on" is just an incompetent fools answer because they in fact have no idea what the problem really is. What carrier does your wife have, VM to?
MrMike2182 said:
The "Cell tower being worked on" is just an incompetent fools answer because they in fact have no idea what the problem really is. What carrier does your wife have, VM to?
Click to expand...
Click to collapse
Lol, I've figured that one out when they told me that a couple months ago, I called back the next day and asked about the tower and they told me there was no record of any tower problems. Yeah, she's on VM also, with a Samsung S2, completely stock. When I check her signal, she has a connection, but it's low, around -100 to -120 dba.
Cypher5235 said:
Lol, I've figured that one out when they told me that a couple months ago, I called back the next day and asked about the tower and they told me there was no record of any tower problems. Yeah, she's on VM also, with a Samsung S2, completely stock. When I check her signal, she has a connection, but it's low, around -100 to -120 dba.
Click to expand...
Click to collapse
If it's both phones doing it then it's certainly not on your side.
MrMike2182 said:
If it's both phones doing it then it's certainly not on your side.
Click to expand...
Click to collapse
Hey Mike. I hate to bother you again, especially since I've been reading how much you've been dealing with other people, so I think I know how to do this, I just would like to run this by you to make sure I have it right.
I'm going to try to have VM replace my phone, so I need it back to looking clean.
1) So, I need to relock the bootloader first. I first "fastboot oem lock" in cmd, then.
2) I DL the RUU from HTC's site, specifically the VM 1.49.652.3 file.
3) While still in fastboot usb, I run the RUU repeatedly till it completes
4) Go back to hboot and do a factory reset.
Thanks man. I've tried to read things through, but I want to make sure it'll be clean if they do replace it.
Edit: Wait, I just saw someone said to input "fastboot oem rebootRUU" then run the RUU.
Cypher5235 said:
Hey Mike. I hate to bother you again, especially since I've been reading how much you've been dealing with other people, so I think I know how to do this, I just would like to run this by you to make sure I have it right.
I'm going to try to have VM replace my phone, so I need it back to looking clean.
1) So, I need to relock the bootloader first. I first "fastboot oem lock" in cmd, then.
2) I DL the RUU from HTC's site, specifically the VM 1.49.652.3 file.
3) While still in fastboot usb, I run the RUU repeatedly till it completes
4) Go back to hboot and do a factory reset.
Thanks man. I've tried to read things through, but I want to make sure it'll be clean if they do replace it.
Edit: Wait, I just saw someone said to input "fastboot oem rebootRUU" then run the RUU.
Click to expand...
Click to collapse
Just relock the bootloader then flash the stock recovery and then run the RUU from the PC but you don't need to factory reset after that because the RUU is the reset.

Strange issue.

Hey guys! So this is a very strange issue. When I power off my nexus, a lot of times I have to wait a good 30 seconds or so before I can power it back on or go into the bootloader. If I power it off, and try to turn it back on fast, it stays black screen almost as of it's frozen or just not responding. I noticed this issue begun when I flashed the radio from N preview 2, and didn't happen before that. My question here, is what could this be? Can the radio really cause odd things like this to happen? Or is there another cause? I am running the newest Android version MOB30I, and have multirom installed with about 4 or so secondaries.
H4X0R46 said:
Hey guys! So this is a very strange issue. When I power off my nexus, a lot of times I have to wait a good 30 seconds or so before I can power it back on or go into the bootloader. If I power it off, and try to turn it back on fast, it stays black screen almost as of it's frozen or just not responding. I noticed this issue begun when I flashed the radio from N preview 2, and didn't happen before that. My question here, is what could this be? Can the radio really cause odd things like this to happen? Or is there another cause? I am running the newest Android version MOB30I, and have multirom installed with about 4 or so secondaries.
Click to expand...
Click to collapse
You flashed Npreview radio on a marshmallow build?
Dead-neM said:
You flashed Npreview radio on a marshmallow build?
Click to expand...
Click to collapse
Yes! Yes I did. Could this be an issue?
H4X0R46 said:
Yes! Yes I did. Could this be an issue?
Click to expand...
Click to collapse
no. as im using the n preview radio on marshmallow, which is the same radio that came out with the last security update.
---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------
H4X0R46 said:
Hey guys! So this is a very strange issue. When I power off my nexus, a lot of times I have to wait a good 30 seconds or so before I can power it back on or go into the bootloader. If I power it off, and try to turn it back on fast, it stays black screen almost as of it's frozen or just not responding. I noticed this issue begun when I flashed the radio from N preview 2, and didn't happen before that. My question here, is what could this be? Can the radio really cause odd things like this to happen? Or is there another cause? I am running the newest Android version MOB30I, and have multirom installed with about 4 or so secondaries.
Click to expand...
Click to collapse
im going to guess, try a different kernel. as its the kernel that will boot up the device?
H4X0R46 said:
Yes! Yes I did. Could this be an issue?
Click to expand...
Click to collapse
Yes it can. Why did you do that?
Make a backup (android or titatium backup)
Then reflash stock n6 firmware (erase data so put your backup and important files into pc)
Dead-neM said:
Yes it can. Why did you do that?
Make a backup (android or titatium backup)
Then reflash stock n6 firmware (erase data so put your backup and important files into pc)
Click to expand...
Click to collapse
the N radio, is the same exact radio that google released for the may security patch. so the N radio, is the latest official radio for the nexus 6. so no, that wont be the problem.
simms22 said:
no. as im using the n preview radio on marshmallow, which is the same radio that came out with the last security update.
---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------
im going to guess, try a different kernel. as its the kernel that will boot up the device?
Click to expand...
Click to collapse
I wonder if it is. I'm using the newest Elite kernel for Marshmallow, it's always been my go to kernel. It's strange because after turning the device off, I can't turn it back on instantly, screen stays black as if it's not 100% shut down yet. I have to wait a bit before turning it back on, or entering the bootloader.
simms22 said:
im going to guess, try a different kernel. as its the kernel that will boot up the device?
Click to expand...
Click to collapse
No, it's the bootloader that boots the device.
If he's hitting the power button and unable to get to the "Google" splash screen or the bootloader, the kernel is very irrelevant.
I'd be more curious if he's trying to use the bootloader from the N-Preview 2 with MM. Even though I think it's supposed to be backwards compatible, the bootloader is the only thing that would cause that sort of issue.
*technically* I'm pretty sure that you could format /boot (where the kernel is stored) and still get to your bootloader for fastboot and such. So, the kernel is really irrelevant until after the bootloader does it's thing.
*edit*
also, there's a reason that these are known as "Developer Previews" not "End-User Previews"... If you don't know how to fix weird issues that pop up like that, you should probably avoid them.
Yoinx said:
No, it's the bootloader that boots the device.
If he's hitting the power button and unable to get to the "Google" splash screen or the bootloader, the kernel is very irrelevant.
I'd be more curious if he's trying to use the bootloader from the N-Preview 2 with MM. Even though I think it's supposed to be backwards compatible, the bootloader is the only thing that would cause that sort of issue.
*technically* I'm pretty sure that you could format /boot (where the kernel is stored) and still get to your bootloader for fastboot and such. So, the kernel is really irrelevant until after the bootloader does it's thing.
*edit*
also, there's a reason that these are known as "Developer Previews" not "End-User Previews"... If you don't know how to fix weird issues that pop up like that, you should probably avoid them.
Click to expand...
Click to collapse
Mmm yes after what said simms22 I've check the n preview and the bootloader is xxx.18 instead of last mm which is xxx.17 but a bootloader downgrade is risky right?
@H4X0R46 do you use the .sh file and update your bootloader and radio with n preview?
Dead-neM said:
Mmm yes after what said simms22 I've check the n preview and the bootloader is xxx.18 instead of last mm which is xxx.17 but a bootloader downgrade is risky right?
@H4X0R46 do you use the .sh file and update your bootloader and radio with n preview?
Click to expand...
Click to collapse
It can be. Normally, once you upgrade, you just stick with the new one as they're backwards compatible normally. But, the ones for the Previews aren't always 100%. The whole reason these previews come out is so that developers can start making their apps compatible prior to the official release. Ideally, this is supposed to be done in emulators not necessarily real devices.
If the 30 second delay in powering back on is *that* big of a deal (to him) to risk bricking the phone by downgrading the bootloader and having something go wrong... I say go for it.
Yoinx said:
It can be. Normally, once you upgrade, you just stick with the new one as they're backwards compatible normally. But, the ones for the Previews aren't always 100%. The whole reason these previews come out is so that developers can start making their apps compatible prior to the official release. Ideally, this is supposed to be done in emulators not necessarily real devices.
If the 30 second delay in powering back on is *that* big of a deal (to him) to risk bricking the phone by downgrading the bootloader and having something go wrong... I say go for it.
Click to expand...
Click to collapse
Is downgrading the bootloader really risky? I've done it before without issue and never knew this was risky! Are you supposed to just stay with the newest bootloader if you already flashed it? I always flash the bootloader for the image I'm flashing, even if I'm downgrading.
Dead-neM said:
Mmm yes after what said simms22 I've check the n preview and the bootloader is xxx.18 instead of last mm which is xxx.17 but a bootloader downgrade is risky right?
@H4X0R46 do you use the .sh file and update your bootloader and radio with n preview?
Click to expand...
Click to collapse
I flash each partition manually.
H4X0R46 said:
Is downgrading the bootloader really risky? I've done it before without issue and never knew this was risky! Are you supposed to just stay with the newest bootloader if you already flashed it? I always flash the bootloader for the image I'm flashing, even if I'm downgrading.
Click to expand...
Click to collapse
It's always risky when you're messing with essentially the lowest level software on the device. For instance, lets say that something happens while you're flashing the bootloader and it corrupts. What do you use to reflash it? You can't get to fastboot anymore...
As long as you know what you're doing, don't have corrupt images, and don't lose power or have lightning strike your computer while you're doing it, you would be fine.
The issue is that many/most people on XDA these days have no idea how to recover from problems or even what problems the things that they're doing might cause. So I tend to approach every situation under the assumption that the other poster may not have a full understanding.
No offense intended of course.
Yoinx said:
It's always risky when you're messing with essentially the lowest level software on the device. For instance, lets say that something happens while you're flashing the bootloader and it corrupts. What do you use to reflash it? You can't get to fastboot anymore...
As long as you know what you're doing, don't have corrupt images, and don't lose power or have lightning strike your computer while you're doing it, you would be fine.
The issue is that many/most people on XDA these days have no idea how to recover from problems or even what problems the things that they're doing might cause. So I tend to approach every situation under the assumption that the other poster may not have a full understanding.
No offense intended of course.
Click to expand...
Click to collapse
Alright so that's just to be safe then? My laptop sometimes freezes solid out of the blue, uncommon but does happen, and I always thought "what if I'm flashing stuff?" Scary thought. ESPECIALLY the bootloader! So the danger you're referring to is flashing a bootloader in general, not so much downgrading? Like I said, I always match the bootloader to the version I'm running. This is okay?
EDIT: I ALWAYS ALWAYS ALWAYS check the MD5 checksum for EVERYTHING before flashing. Can never be too safe
H4X0R46 said:
Alright so that's just to be safe then? My laptop sometimes freezes solid out of the blue, uncommon but does happen, and I always thought "what if I'm flashing stuff?" Scary thought. ESPECIALLY the bootloader! So the danger you're referring to is flashing a bootloader in general, not so much downgrading? Like I said, I always match the bootloader to the version I'm running. This is okay?
EDIT: I ALWAYS ALWAYS ALWAYS check the MD5 checksum for EVERYTHING before flashing. Can never be too safe
Click to expand...
Click to collapse
In general, the bootloader needs to match the highest version of android you intend to run. They're typically always backward compatible. On some phones, you can't downgrade the bootloader (at least not easily). This phone you should be fine doing so. However, there's not usually any reason to (backwards compatible afterall).
Yoinx said:
In general, the bootloader needs to match the highest version of android you intend to run. They're typically always backward compatible. On some phones, you can't downgrade the bootloader (at least not easily). This phone you should be fine doing so. However, there's not usually any reason to (backwards compatible afterall).
Click to expand...
Click to collapse
Cool! Thanks for your input on that! Much appreciated! Yea I'm always wary of the bootloader because like you said, it IS the lowest software on the device. Quick question, if that were to get corrupted, does the device just not boot resulting in permanent brick? Or does it boot just no fastboot access? Might be a noob question, but why not ask lol
H4X0R46 said:
Cool! Thanks for your input on that! Much appreciated! Yea I'm always wary of the bootloader because like you said, it IS the lowest software on the device. Quick question, if that were to get corrupted, does the device just not boot resulting in permanent brick? Or does it boot just no fastboot access? Might be a noob question, but why not ask lol
Click to expand...
Click to collapse
Depends, I've never really looked into unbricking this phone. Never had to yet.
Depending on the phone you can use tools like QHUSB and similar which let you reflash partitions just through the USB connection.
I know it's late but it could also be just the rom setup. I know a while ago there were commits that shut the device screen and buttons off before it was done shutting down (to make it appear faster) this made devices seem bricked for a short period. I don't know what ever happen to those commits, so I can't say for sure that it is them. But your issue fits perfectly.
So have I been flashing the bootloader wrong all along? I flashed in twrp a couple times but I try to flash them individually and wipe after flashing.
Sent from my Nexus 6 using XDA-Developers mobile app
Anybody able to find out why? I'm surprised to see I'm not the only one having this issue, it's annoying really.

Losing service after flashing ROM

I've recently tried flashing pixel experience and various other roms via twrp. However, Everytime I load the phone up, I either have no service, data, or sometimes 3g briefly. When I try to go to carrier settings I get a ".com.android.phone has stopped." Error message, any advice on how to fix this?
L4ndon said:
I've recently tried flashing pixel experience and various other roms via twrp. However, Everytime I load the phone up, I either have no service, data, or sometimes 3g briefly. When I try to go to carrier settings I get a ".com.android.phone has stopped." Error message, any advice on how to fix this?
Click to expand...
Click to collapse
Do a proper clean flash
Phazmos said:
Do a proper clean flash
Click to expand...
Click to collapse
I have done this. Still have the same problem. Wiped dalvik, system, data, cache. No luck, I've tried every rom on this forum.
L4ndon said:
I have done this. Still have the same problem. Wiped dalvik, system, data, cache. No luck, I've tried every rom on this forum.
Click to expand...
Click to collapse
Obviously you haven't done a proper clean flash. I've flashed every rom available and no fcs. Only time I've had signal trouble was with att(gsm). Never lost signal, would just go from 2 bars to none then back again, but never lost signal.
Oh, search pe thread for my name to see the correct way to flash.
Phazmos said:
Obviously you haven't done a proper clean flash. I've flashed every rom available and no fcs. Only time I've had signal trouble was with att(gsm). Never lost signal, would just go from 2 bars to none then back again, but never lost signal.
Oh, search pe thread for my name to see the correct way to flash.
Click to expand...
Click to collapse
I don't know what to say. I boot into twrp, wipe dalvik, cache, system, data and then I flash the rom. Once I boot, I have the service issue. Could it be not flashing gapps?
L4ndon said:
I don't know what to say. I boot into twrp, wipe dalvik, cache, system, data and then I flash the rom. Once I boot, I have the service issue. Could it be not flashing gapps?
Click to expand...
Click to collapse
1 - gapps has nothing to do with signal
2 - you seem to flash like most others here, I don't, and don't have issues they do.
3 - info was posted, follow it, or don't. Up to you.
4 - Best of luck!
Phazmos said:
1 - gapps has nothing to do with signal
2 - you seem to flash like most others here, I don't, and don't have issues they do.
3 - info was posted, follow it, or don't. Up to you.
4 - Best of luck!
Click to expand...
Click to collapse
Can you link the thread that you were talking about how to flash properly? I can't seem to find it. Sorry if I came off as brash, was just a little frustrated at my own mistakes.
L4ndon said:
Can you link the thread that you were talking about how to flash properly? I can't seem to find it. Sorry if I came off as brash, was just a little frustrated at my own mistakes.
Click to expand...
Click to collapse
Sorry man, but I'm not much of a spoon feeder - give a man a fish etc etc.
Get some sleep - relax - tackle it tomorrow - maybe without the frustrating you will find what you need to see (it is right there).
Riddle me this - a rom is a rom and as a rom a rom can be found in the ___ section. Simple isn't it.
Have a good night!
Phazmos said:
Sorry man, but I'm not much of a spoon feeder - give a man a fish etc etc.
Get some sleep - relax - tackle it tomorrow - maybe without the frustrating you will find what you need to see (it is right there).
Riddle me this - a rom is a rom and as a rom a rom can be found in the ___ section. Simple isn't it.
Have a good night!
Click to expand...
Click to collapse
Hey, after decrypting my phone and using the method you posted in the pe thread to flash roms, I am still getting service problems. I've also noticed that anytime I have tried to open carrier settings on the phone, I get a ".com.android.phone has stopped." So I cant update the prl at all. I've seen people post about modifying the APN settings but I thought that was irrelevant on sprint. I'm honestly out of ideas.
L4ndon said:
Hey, after decrypting my phone and using the method you posted in the pe thread to flash roms, I am still getting service problems. I've also noticed that anytime I have tried to open carrier settings on the phone, I get a ".com.android.phone has stopped." So I cant update the prl at all. I've seen people post about modifying the APN settings but I thought that was irrelevant on sprint. I'm honestly out of ideas.
Click to expand...
Click to collapse
Well, when nothing helps, it's time to go back to stock.
Get firmware for your location - different firmware (modem especially) for different markets.
Don't use any "tools" or .bat files you find here and flash with fastboot - do 1 command at a time and note results, (remove sim before flashing and reinsert after you've booted into stock once).
See what happens. Sometimes things get messed up enough to where flashing stock is the only thing to do. That'll really clean it out.
I had a real funky issue when going from att to vz. Spent hours with straight talk trying to sort it out (had 4g but no calls or texts). Flashed stock - popped sim in - bang - everything working, and has been ever since and I've flashed them all, some several times, still good.
L4ndon said:
Hey, after decrypting my phone and using the method you posted in the pe thread to flash roms, I am still getting service problems. I've also noticed that anytime I have tried to open carrier settings on the phone, I get a ".com.android.phone has stopped." So I cant update the prl at all. I've seen people post about modifying the APN settings but I thought that was irrelevant on sprint. I'm honestly out of ideas.
Click to expand...
Click to collapse
When I first got my xt1806 I didn't load a Sim card in it when I powered it up, I immediately unlocked the bootloader, installed recovery, flashed a ROM and just used WiFi for a few days with no issues. But once I did put a new Sim in it I noticed all I could get was 3g - and with every other ROM I installed all I could get was 3g no matter what I tried. The only solution was to fastboot flash back to stock, install the Sim, power it up, & let it "register"(send a text or make a call & also verify 4g works) with the network. I'm not saying you did the same thing I did, but the fix should be flashing back to stock.
*Copy your internal memory somewhwere before you reflash stock in case everything gets wiped.
*I'm on Verizon btw, so my experience may or may not apply to Sprint.
Sprint problems with 4g
I know this isn't my thread but I shall try anyway. I have the Sprint version of the g5 s plus. I have tried every way of flashing a rom that I can think of (all wipes rom then gapps magisk, magisk then gapps, rom and no gapps or magisk, etc.). I cannot manage to keep 4g after flashing. I have backed up my efs with twrp and tried restoring it. Nothing. I've used fastboot to flash nhlos erase modems1&2 flash fsg. I tried *#*#463whatever to turn it back on and nothing. I've checked all settings and tried all things I know of. Still nothing. The only way I can get/keep 4g is by using stock rooted which I hate. . Is this just a specific problem to my type of phone or is there something I'm missing? Is there a different firmware or modem I could use or something? Any thoughts or ideas would be great cause I'm stumped.

Categories

Resources