i remember the nexus 6 had a nasty habit of loading att crap when you flash and reboot with a sim installed. to get around it you removed the sim prior to rebooting, then when everything is loaded up you can re-install the sim. now i've had the 6P since launch and have been happily flashing away by removing the sim prior to reboot and it dawned on me that maybe the 6p doesn't have this issue. i'll give it a try at the next flashing, but in the meantime, any experience?
indianajonze said:
i remember the nexus 6 had a nasty habit of loading att crap when you flash and reboot with a sim installed. to get around it you removed the sim prior to rebooting, then when everything is loaded up you can re-install the sim. now i've had the 6P since launch and have been happily flashing away by removing the sim prior to reboot and it dawned on me that maybe the 6p doesn't have this issue. i'll give it a try at the next flashing, but in the meantime, any experience?
Click to expand...
Click to collapse
As far as I know you don't need to worry about this.
Related
So, I have read a lot about TWRP sometimes bugging out and randomly encrypting phones and adding a password to which the user either never set it up or that TWRP doesn't accept it. This has recently happened to me and I cannot use my phone and I don't know what to do.
I have had the bootloader of my phone unlocked since day 1 when I bought my phone (release date last year) and have been running PA ever since. I have never had any problems with it, until about 5 days ago, when I grabbed my phone and everything started crashing and the camera was apparently not available. I didn't know what was the deal with it, so I rebooted the phone and it entered a bootloop (it hangs on the Google logo for about 5 minutes and then it hangs on the PA logo screen forever). I went on to the bootloader and started TWRP to see what was the deal. I originally wanted to grab certain files off the phone in case I had to do a system format, but when I got to TWRP, it asked me for a password which I have never set up and I tried every combination I could think of but it always failed. Everything was encrypted and without the password I couldn't get to it. I tried wiping everything including a factory reset before resorting to a system format (which I read about it and apparently is meant to be the solution). Everything failed because it couldn't access the /cache, /data, nothing. I went on to do a system format and although that is meant to wipe the phone and remove encryptions, it also failed to wipe the /cache and although TWRP says that the wipe is successful, the phone is still encrypted, the password is still around and it bootloops. I have tried the system format like 50 times and always the same.
Can anyone help me out with this? I am currently travelling around but am at a hostel where there is great internet and pcs, so I can install drivers, toolkits and such. I actually started looking around for new phones, since I cannot for the life of me get the phone to start again.
Note: The phone was working perfectly fine, I put it down to have dinner and once I finished, I tried to use it and it started to bug out. I also read around about this, and everyone's issue gets fixed after a system format.
Any help, would be greatly appreciated, that phone is the only net device I have on this trip and it sucks to not have any way to contact anyone.
Thanks.
Bump
Don't blame TWRP for something it doesn't do.
Looks like your device have an EMMC failure, sorry.
You can try installing factory image, or last resort restoring by download mode, but I think the flash memory in your phone is gone.
http://forum.xda-developers.com/showthread.php?t=2347060
sent from nexus 4
eksasol said:
Don't blame TWRP for something it doesn't do.
Looks like your device have an EMMC failure, sorry.
You can try installing factory image, or last resort restoring by download mode, but I think the flash memory in your phone is gone.
http://forum.xda-developers.com/showthread.php?t=2347060
sent from nexus 4
Click to expand...
Click to collapse
I didn't mean to blame TWRP. It is just that it was when I am on it that I get asked for the password and I was under the impression that it was TWRP that did the encrypting (I am in no way a developer or even very knowledgeable when it comes to the under the hood stuff, I usually only follow the tutorials). But thanks for the reply and the link, I will try that and hopefully get the phone back working.
Also, I did read in a thread that apparently this can occur due to hardware failure, I was just hoping this wasn't the case.
This happened to me on an old phone. Not sure why. Factory image fixed it. Could be a different issue but its worth a shot.
Sent from my Nexus 4 using XDA Premium 4 mobile app
It's happening to me now too
Sent using T-Mobile S4 4.3 MK2
LEGEND94 said:
It's happening to me now too
Sent using T-Mobile S4 4.3 MK2
Click to expand...
Click to collapse
Did it suddenly happen or did you change ROMs?
I tried a new rom for the first time and then went back to wicked 9.1, I'm thinking that triggered something.
I think I got a fix though, look here: http://forum.xda-developers.com/showthread.php?t=2588377
Sent using T-Mobile S4 4.3 MK2
I recently had some issues with my GPS so I used Odin to go back to stock firmware, everything was still ok after this and my GPS was back to working order. Then I used CF auto root to root my device again/use TWRP recovery. Then I flashed the latest PAC nightly and gapps with seemingly no problems. The phone worked fine for 2-3 days until one day when it was in my pocket I got a warning saying something along the likes of "SIM card has been removed. Reboot required." Rebooting would make the sim come back online momentarily until it would randomly come back up. There didn't seem to be any correlation with any new apps I had installed or things I did on my phone to cause this error. I thought perhaps it was the ROM so I tried reflashing (complete with factory wipe) and the problem still happened. I also tried wiping factory->system->cache&dalvik before reflashing..again it worked but only briefly. I tried going back to stock but it still happens. Right now I'm running task650s aokp and it still comes up..the sim works in other phones no problem. Any ideas on what might be going on/how to fix this issue?
Sent from my SGH-I337 using XDA Premium 4 mobile app
Around a week ago everything was force closing on my N4 so I decided to reboot it, when I did it got stuck in boot loops. Because of this I went to wipe the data and cache so I could flash a Rom but when I did all my data from my SD partition had disappeared. This has happened to me before and the way I solved it last time was to unroot and flash back to stock using the Nexus 4 toolkit. However when I went to do that this time it said my boot loader was locked so I couldn't complete the task. So then I unlocked the bootloader which apparently is successful but when I refresh the bootloader it seems to be locked again. Over the last week I have tried sideloading zips, force flashing, unrooting, unlocking the bootloader and all this on both a mac and windows toolkit.
When researching this problem I only could find one thread which resembled my problem on xda however it was about the Nexus 7 and the person ended up sending it back to Asus. Would be great if someone good respond, thanks!
(Also my device is a Rooted UK 16gb if that helps)
It sounds like your emmc flash memory is bad. Not being able to lock or unlock the bootloader is a sign of that. You should warranty the device.
I agree. I faced a similar problem on my Optimus 2X. It started with occasional bootloops, and last week it got to the point where it was boot-looping after every boot w/ force closes, missing data, and e2fsck did nothing, because the fixed errors came back within hours. Definitely sounds like your memory chip has called it quits.
Hello everyone,
So here's my story: I got a 6P short after release and it's been amazing. After switching from a S6 I couldn't be happier until 3 days ago.
I was playing around with my phone (checking for updates on the play store if I recall correctly) and I was going to switch from 4g to wifi. I went ahead and pulled down my notification shade and went to press WiFi but misclicked and hit Hotspot which was below it. My phone suddenly froze big time and this is for the first time ever since purchase.
At first I thought I'd wait it out since the device was completely unresponsive, home button didn't work and neither did anything on screen. Buttons didn't make a difference either. 10 minutes went by and I ended up force restarting by holding down power + volume up. First part of my bootup went fine but when it got to the android boot animation after I put in my pin to allow the device to start it dropped from the smooth usual framerate down to 1 frame every 10-15 seconds and it slowed down further until it came to a complete halt around the time the android letters appear.
My first thought was corrupt rom so I went ahead and wiped data from the stock recovery. I was running completely stock with no modifications whatsoever. That didn't do anything. Phone still froze in the same boot phase. Desperate I unlocked bootloader to flash a clean fresh image to try to fix it and to my surprise that didn't change a thing.
As I was getting pretty desperate already I had one more idea and that was to flash up to the Dev preview. To my huge surprise it booted and I jumped from excitement. So I started setting up my phone again. I got past the prompt to insert sim card and I was now at the screen to choose a wifi network. As soon as I clicked into that the phone froze up again and at that point I lost all hope.
I wiped data in stock recovery and shut the phone down for the night. On day 3, today I woke up and tried starting the phone and it worked as if nothing had happened. I went through the setup and set up my phone on the N preview. At a certain point I was planning to go back to the latest official build but for now I was happy my phone was back from the dead. Later today I tried to restart my phone to clear all running apps etc and it froze up on boot.
I'm losing all hope that I'll be resolving this myself so I'm reaching out to the community to see if anyone's had this happen to them before and hopefuly for a solution. It's still under warranty so I can eventually send it back to the retailer but I'd rather not have a phone for 3 weeks.
Any and all help is appreciated.
Thank you for reading through my long and probably pretty boring story!
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
To the OP, is there any reason you did not flash to release version 6 instead of Dev preview ?
Also, any reason you can not simply do the "unenroll" from https://www.google.com/android/beta ?
It will require you to setup certain settings again as you will be back to a "factory reset".
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
DJBhardwaj, i haven't specifically erased those partitions. I was under the impression wipe userdata along with reflashing did that. I will try that tonight when I get home!
Xdafly, I only updated up to N as a last resort because at first I had a locked BL. I was planning to unenrol but that would've been too late as it self bricked after a restart.
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
Well I just did the erase thingy and my phone booted but wifi won't turn on. Enabling hotspot doesn't brick anymore but I now suspect WiFi might've been the issue. Any tips on how to find out what it could be and possibly fix it?
Edit: 2 restarts and a factory reset later I'm back to bricked same way as before.
try safe mode
mr.dj26 said:
try safe mode
Click to expand...
Click to collapse
That was my first thought, that was the restart that bricked it again. Safe mode shouldn't have made a difference since I hadn't even logged into Google account for apps.
After reading the very first post; sounds like bad WiFi hardware.
All the hanging has been related to WiFi or Hotspot.
I think you should get a replacement
Sent from my Purified NexusixP
If Someone Helped You Then Dont Just say Thanks...Hit The Thanks Button!
Is your phone rooted and did you install Xposed?
Over the weekend I shutdown my 6p (stock rooted with April security patch, Xposed v80) and charged it. When it turned it back up I kept getting "Unfortunately, nfc service has stopped". Long story short: I ended up factory reset my phone and reinstalled EVERYTHING and I still got into bootloop. Then I came across
https://github.com/rovo89/Xposed/issues/113
https://github.com/rovo89/android_art/issues/28
At the end of the second post rovo89 (developer of Xposed) fixed the bug in V83. I wiped my 6p once more and installed everything with v83. Problem solved.
Good luck!
Out of the most random occurrence today I'm all of a sudden having modem issues or something. It on't stop saying roaming indicator on and boots up reading as a missing sim for the first couple seconds. Thought maybe my sim card died, Swapped with another one, did the same thing. Thought maybe for some reason it was my rom (which was TruPure X), flashed to CM13 now to try and see if that was maybe it, still the same. Hoping someone can help me avoid having to do a restore back to stock and re-rooting, flashing all over, etc.
I don't know what's going on, but I am having the same issue as of this morning. I did go back and reflash stock, which fixed it but seems to have corrupted my sd card. I backed up the contents, so it isn't a disaster, but I can't get stock or custom ROMs to reformat it for use as internal storage.
If anyone has any ideas, I'd welcome the suggestions.
Neez333 said:
Out of the most random occurrence today I'm all of a sudden having modem issues or something. It on't stop saying roaming indicator on and boots up reading as a missing sim for the first couple seconds. Thought maybe my sim card died, Swapped with another one, did the same thing. Thought maybe for some reason it was my rom (which was TruPure X), flashed to CM13 now to try and see if that was maybe it, still the same. Hoping someone can help me avoid having to do a restore back to stock and re-rooting, flashing all over, etc.
Click to expand...
Click to collapse
hannahlin said:
I don't know what's going on, but I am having the same issue as of this morning. I did go back and reflash stock, which fixed it but seems to have corrupted my sd card. I backed up the contents, so it isn't a disaster, but I can't get stock or custom ROMs to reformat it for use as internal storage.
If anyone has any ideas, I'd welcome the suggestions.
Click to expand...
Click to collapse
You can try dialing *#*#9636#*#* and change preferred network.
[email protected] said:
You can try dialing *#*#9636#*#* and change preferred network.
Click to expand...
Click to collapse
I figured it out in the service menu... Which btw its *#*#4636#*#* ... Lolz. Somehow the network type within phone info got changed.. How idk, cuz I only use service menu when absolutely needed and actually think that was my first time on the moto.