Hello First post here so hopefully in the right place! I've got a nexus 5, UK model purchased around January time. I had rooted, running stock with SuperSU installed and a few apps installed with xposed mod.
It was running perfectly fine, until a few days back where I was required to reboot, it then got stuck at the Google screen and wouldn't go past that, I turned the phone off for a while and eventually could get into it.. Great, until it happened again.. I spoke to a friend who said perhaps it was the xposed which was causing it, so I flashed back to factory, ran it for a while and it was fine, so went back to root and tested it, was stable so I reinstalled xposed.. It then got stuck in the bootloop again, so flashed to factory certain that it was xposed causing issues. I'm now running factory, however the phone will still get stuck in bootloop but will also randomly reboot itself now.. Has anyone experienced this? After scanning the forums I can't find anything so hopefully someone can help!! My boot loader is still unlocked.
Thank you, Jordan.
arsenaljordan said:
Hello First post here so hopefully in the right place! I've got a nexus 5, UK model purchased around January time. I had rooted, running stock with SuperSU installed and a few apps installed with xposed mod.
It was running perfectly fine, until a few days back where I was required to reboot, it then got stuck at the Google screen and wouldn't go past that, I turned the phone off for a while and eventually could get into it.. Great, until it happened again.. I spoke to a friend who said perhaps it was the xposed which was causing it, so I flashed back to factory, ran it for a while and it was fine, so went back to root and tested it, was stable so I reinstalled xposed.. It then got stuck in the bootloop again, so flashed to factory certain that it was xposed causing issues. I'm now running factory, however the phone will still get stuck in bootloop but will also randomly reboot itself now.. Has anyone experienced this? After scanning the forums I can't find anything so hopefully someone can help!! My boot loader is still unlocked.
Thank you, Jordan.
Click to expand...
Click to collapse
Are you able to flash a custom recovery? like TWRP, PHILZ, CWM? try it.
if successful, flash a custom Rom. just to discard the possibility of emmc failure.
GUGUITOMTG4 said:
Are you able to flash a custom recovery? like TWRP, PHILZ, CWM? try it.
if successful, flash a custom Rom. just to discard the possibility of emmc failure.
Click to expand...
Click to collapse
I am able to flash a custom recovery and so forth, so wouldn't think it to be emmc failure.
arsenaljordan said:
I am able to flash a custom recovery and so forth, so wouldn't think it to be emmc failure.
Click to expand...
Click to collapse
It doesn't really exonerates emmc from being bad yet. now, wipe and flash a Rom, a stock/aosp based one
GUGUITOMTG4 said:
It doesn't really exonerates emmc from being bad yet. now, wipe and flash a Rom, a stock/aosp based one
Click to expand...
Click to collapse
I have already flashed the stock recovery and ROM back to the device
Related
I was running slim 4.2.1 for quite some time with no problems, i loved it. I flashed 4.2.2 and my phone got stuck in NV and my phone number would come up as 000-000-3370. On first boot everything seems to be fine except that i get an error when i try to open up the play store. On my next boot is when I would see these problems. I tried everything from dirty flashing from a working 4.2.1 rom to completely formatting everything, even my external sd, and the same thing happens. This happens with every 4.2.2 rom out there. When i reboot i get stuck on the activating screen and my phone will get stuck in NV and ruim/sim wont stick no matter what i do. i don't know what else to do. someone please help!
It isn't a rom issue it is an S 3 issue that randomly occurs when flashing ROMs. You will have to flash the stock rom and reprovision your phone. I know because it has happened to me twice and both times it was with a Touchwiz ROM. You should have backed up your IMEI just in case this happens.
my imei is backed up. but why is it only 4.2.2 roms that do this?
I was able to flash back to a 4.2.1 Rom, namely pure Google for now, with no problems. but when I flash any 4.2.2 Rom the same thing happens.
All 4.2 ROMs used to do this to me.
However.
Only also happened when I flashed miui.
Now I run liquid smooth and haven't had the problem since.
sent from that young galaxy.
God bless the American people!
do u guys think I should Odin back to stock, then root, unlock, and try to flash 4.2.2?
Actually, there is an easier way
I have had this happen numerous times and it lef me to mess with my phone a little bit. I originally thought that setting it to CDMA/SIM and then rebooting would fix the problem, but I found a simpler solution to that. The last time I encountered the problem I simply set the phone to RUIM/SIM under mobile networks and then Turned on airplane mode for a few seconds then turned it off and I found my number under phone settings and everything. Try that and let me know how it goes.
Edit: Sorry, the term is RUIM/SIM, not CDMA/SIM. My bad.
hmmm, I'll definitely give that a shot later on tonight.
well I tried it, it works. but only temporarily. once I reboot it reverts back to how it was. any other thoughts?
anyone?
Chitala383 said:
anyone?
Click to expand...
Click to collapse
try this. i had the same problem. http://forum.xda-developers.com/showpost.php?p=35600769&postcount=2
nope, none of that works either. no matter what I do ruim/sim will not stick on a reboot on any 4.2.2 Rom. I'm really getting frustrated with this.
no one has any other solutions for me?
Chitala383 said:
anyone?
Click to expand...
Click to collapse
Does your phone display an IMEI number?
Settings->About->Status
Don't need the number, just to know if you have it there....
Also do you still have Root/Unlocked bootloader?
yes, i have an imei. i lost it once before so now its backed up, i'll never make that mistake again. it was a nightmare trying to get it back. and yes, i am rooted and unlocked.
Chitala383 said:
yes, i have an imei. i lost it once before so now its backed up, i'll never make that mistake again. it was a nightmare trying to get it back. and yes, i am rooted and unlocked.
Click to expand...
Click to collapse
Have you done a complete factory restore through Odin? You would lose root and unlocked bootloader, but it may be faster to restore to stock, and reroot/mod than to try to find an "easy" fix. I was having some issues the other day in between a few ROM's, but I just factory restored, and restarted from "scratch". Now I am running perfect.
You may have already tried, but on page 1 you asked if you should, and I did not see a confirmation you did so.
Had the same problem... And yes, the phone must be reprovisioned. Although sometimes you can just adjust the network settings and change it from NV. That worked for me also.
Sent from my SCH-I535 using Tapatalk 2
I flashed root 66 via Odin, bootloop. flashed the ma2 stock image, bootloop. then flashed the lk3 stock image with success. but still with the same results as before.
tomorrow I'll try flashing g1 and start from scratch there. what do u guys think?
well, I odin'd back to bone stock G1, rooted with rootdebugfs, flashed cwm with ez recovery, unlocked my bootloader with ez unlock, flashed liquidsmooth 4.2.2 rc2 and guess what. same ****!!!!!!!!!!!!! i'm really getting fed up with this. someone has to have a solution to this cuz this is really pissing me off.
Hi folks, this is my first thread in this section of the forum, because i was using my old device LG p500 and now i moved to this wonderful smartphone. So, i'd like to solve this problem which is happening now. Basically, the phone unexpectedly stops, and reboot. It happens a couple of times, i guess 3 times in a week. It wasn't happening in ICS, just now that i upload from OTA to Jelly Bean. Note that this was happened while my phone was Unrooted and with Locked Bootloader, the same occured with root and unlocked bootloader. So, any clue? Maybe i should just change the rom, or clean everything as fast as i can.
Thank you.
ermito said:
Hi folks, this is my first thread in this section of the forum, because i was using my old device LG p500 and now i moved to this wonderful smartphone. So, i'd like to solve this problem which is happening now. Basically, the phone unexpectedly stops, and reboot. It happens a couple of times, i guess 3 times in a week. It wasn't happening in ICS, just now that i upload from OTA to Jelly Bean. Note that this was happened while my phone was Unrooted and with Locked Bootloader, the same occured with root and unlocked bootloader. So, any clue? Maybe i should just change the rom, or clean everything as fast as i can.
Thank you.
Click to expand...
Click to collapse
If you took the OTA then you are sol and will not be able to unlock your bootloader to flash a custom recovery or a rom the traditional way. There is safestrap but thats less than optimal for flashing. As far as the reboots go, it is probably an app that is causing the issues. I would do a factory reset and be selective about the apps I re-installed.
mentose457 said:
If you took the OTA then you are sol and will not be able to unlock your bootloader to flash a custom recovery or a rom the traditional way. There is safestrap but thats less than optimal for flashing. As far as the reboots go, it is probably an app that is causing the issues. I would do a factory reset and be selective about the apps I re-installed.
Click to expand...
Click to collapse
What are you saying? I'm already unlocked bootloader and flashed a custom recovery and it's been working normally.
ermito said:
What are you saying? I'm already unlocked bootloader and flashed a custom recovery and it's been working normally.
Click to expand...
Click to collapse
Sorry I must have glazed over the part about you having your bootloader unlocked.
Hi, i changed to the SlimRom since then and the reboots still happen, i'm very frustrated. It freezes, then reboot into the bootloader screen and stays there for ever until i press the power button for a while and the phone vibrate 3 times and after that it boot normally.
Hi,
I have a rooted VZW S3 and have been running Jelly Beans build 20 for a while now. Wanting to give a 4.3 rom a try I loaded up MOAR 7.1. Wiped everything, I possibly could without wiping my SD card. Flashed the rom, no problems. Booted it up, no problems. Then if I do a reboot, even after it has sat for a while without me doing anything to it, I get stuck on the Samsung SIII screen. I can do a battery pull and go to TWRP then wipe and get back to my Jelly Beans, but I'd like to give MOAR 7.1 a try. Any help would be appreciated.
Thanks.
powerkatwedel said:
Hi,
I have a rooted VZW S3 and have been running Jelly Beans build 20 for a while now. Wanting to give a 4.3 rom a try I loaded up MOAR 7.1. Wiped everything, I possibly could without wiping my SD card. Flashed the rom, no problems. Booted it up, no problems. Then if I do a reboot, even after it has sat for a while without me doing anything to it, I get stuck on the Samsung SIII screen. I can do a battery pull and go to TWRP then wipe and get back to my Jelly Beans, but I'd like to give MOAR 7.1 a try. Any help would be appreciated.
Thanks.
Click to expand...
Click to collapse
Make sure to use the latest TWRP and did you install ML1 modem like instructed so?
buhohitr said:
Make sure to use the latest TWRP and did you install ML1 modem like instructed so?
Click to expand...
Click to collapse
Yeah I have the latest build if twrp and I think I already has the correct Mode from a prior rom. I didn't even check to verify guess I got too excited. I'll check and report back. Thanks.
buhohitr said:
Make sure to use the latest TWRP and did you install ML1 modem like instructed so?
Click to expand...
Click to collapse
Well I didn't have the ML1 modem so I wiped everything clean, installed the modem, then the rom. Got the same result.
powerkatwedel said:
Well I didn't have the ML1 modem so I wiped everything clean, installed the modem, then the rom. Got the same result.
Click to expand...
Click to collapse
Any other ideas that may be causing this?
powerkatwedel said:
Any other ideas that may be causing this?
Click to expand...
Click to collapse
Here is another user solved the issue, take from the thread:
"What I did was upgrade my recovery with Goo, I removed the SD card, I wiped the internal memory (not sure if this is necessary but what the hell), factory wiped, installed 7.1, once the phone booted up I logged in to gmail, let it sync, didn't install anything else and rebooted just to make sure it reboots fine, and it worked. Then I installed all my apps with TB without data, just the apps. That is what I did. I had the same problem as you for two days and was frustrated but then I read that if you upgrade your recovery it would work fine. I am assuming you are trying to wipe cache and it is telling you that it can't be mounted, that is another problem I was having, so I am assuming that by wiping the internal memory it cleared that problem up. I hope this helps you out. Hopefully someone here can either back up what I am saying or call me crazy and help you out. Good luck."
What kernel are you installing? I had similar problem trying to install with LK. But that is just my phone not playing nice with it unfortunately (nothing wrong with LK) try DKP or KT.
Sent from my SCH-I535 using xda app-developers app
Lehocki said:
What kernel are you installing? I had similar problem trying to install with LK. But that is just my phone not playing nice with it unfortunately (nothing wrong with LK) try DKP or KT.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I have tried LK and the Stock and was still getting it. I was able to get it to install last night finally and work, but now my WiFi isn't working.
powerkatwedel said:
I have tried LK and the Stock and was still getting it. I was able to get it to install last night finally and work, but now my WiFi isn't working.
Click to expand...
Click to collapse
I was never able to get the WiFi to work, so I switched roms and was able to get everything working on Wicked. Thanks for all the help.
im sure this question has been answered for different handsets etc before but i wanted to ask here.
I decided today to root my oneplus one. I had installed the CM12 update before hand and thought that it would not cause any issues. unfortunately after i installed the custom recovery i tried TWRP and clockwork mod and then rooted it. when i booted into the cm12 the root binary was not present and the recovery had reverted to the stock cyanogen recovery.
eventually after many attempts i decided to wipe the phone entirely and install cm11s onto the phone and wouldnt you know, the root and recovery all worked perfectly. i even installed titanium backup just to make sure. everything checked out 100%.
Then I proceeded to install cm12s again, thinking all was good but then it all reverted again. I really do not know what I am doing wrong. I am using the root toolbox that was shown on the root video in the root tab of this forum.
Before you ask, yes i have unlocked the bootloader. i followed the video to the word
I really do appreciate all help and advice given
Jamesr1292 said:
im sure this question has been answered for different handsets etc before but i wanted to ask here.
I decided today to root my oneplus one. I had installed the CM12 update before hand and thought that it would not cause any issues. unfortunately after i installed the custom recovery i tried TWRP and clockwork mod and then rooted it. when i booted into the cm12 the root binary was not present and the recovery had reverted to the stock cyanogen recovery.
eventually after many attempts i decided to wipe the phone entirely and install cm11s onto the phone and wouldnt you know, the root and recovery all worked perfectly. i even installed titanium backup just to make sure. everything checked out 100%.
Then I proceeded to install cm12s again, thinking all was good but then it all reverted again. I really do not know what I am doing wrong. I am using the root toolbox that was shown on the root video in the root tab of this forum.
Before you ask, yes i have unlocked the bootloader. i followed the video to the word
I really do appreciate all help and advice given
Click to expand...
Click to collapse
I am having the same issue I hope someone can help shed some light on what to do here. I found out when I tried to install Xposed.
Ohh_Zone said:
I am having the same issue I hope someone can help shed some light on what to do here. I found out when I tried to install Xposed.
Click to expand...
Click to collapse
i almost had it working but its after happening again. supersu has stayed installed now, the binary needs to be updated. but when i go to update it, it fails :/
Jamesr1292 said:
i almost had it working but its after happening again. supersu has stayed installed now, the binary needs to be updated. but when i go to update it, it fails :/
Click to expand...
Click to collapse
I can't even get TWRP to come back up, have you found a thread for this?
Ohh_Zone said:
I can't even get TWRP to come back up, have you found a thread for this?
Click to expand...
Click to collapse
no, nothing. iv even tried changing to an updated version of supersu to try and fix it and still the same. my recovery keeps reverting too
So I've been trying to go from Slimkat (Slim-4.4.4.build.7.0-Official-5979) to Cyanogenmod 12.1 (cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2vzw) for a few weeks now. I've tried like 4 different guides, which were all pretty similar, but every time I get to the same point. I'm able to get to my recovery (CWM), clear all my cache, etc, install CM12.1 and Gapp5.11, reboot, it optimizes all my apps, finishes the boot, and then goes into what seems like a boot loop. I've let it sit there and reboot for like 5-10 minutes before and it just keeps rebooting. I even redid the flashing of the aboot and bootloader as shown in the official CM install guide to get the recovery on there and also tried the latest TWRP recovery with the same results. Also, once it enters this bootloop, from the time I turn it on, it shows the Samsung logo with the blue Android man below it, then goes to the screen with the pulsing Android head, it vibrates then goes do a dark screen with a blue pulsing indicator light and then starts the sequence over after a few seconds.
I tried to remove my MicroSD card and boot without that with no success. Is it possible I need to format my internal storage as well? The guides usually don't mention what you're coming from, so I have no idea what starting point they expect me to be at.
Files used:
cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2vzw
gapps-511-base-20151205-1-signed
I did NOT use the below CM Recovery, however. I was afraid to do that and lose my ability to recover my old image.
cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2vzw-recovery
I'm able to recover back to my original ROM, but any help to upgrade is greatly appreciated. I'm tired of messing with this....
hypercoyote said:
So I've been trying to go from Slimkat (Slim-4.4.4.build.7.0-Official-5979) to Cyanogenmod 12.1 (cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2vzw) for a few weeks now. I've tried like 4 different guides, which were all pretty similar, but every time I get to the same point. I'm able to get to my recovery (CWM), clear all my cache, etc, install CM12.1 and Gapp5.11, reboot, it optimizes all my apps, finishes the boot, and then goes into what seems like a boot loop. I've let it sit there and reboot for like 5-10 minutes before and it just keeps rebooting. I even redid the flashing of the aboot and bootloader as shown in the official CM install guide to get the recovery on there and also tried the latest TWRP recovery with the same results. Also, once it enters this bootloop, from the time I turn it on, it shows the Samsung logo with the blue Android man below it, then goes to the screen with the pulsing Android head, it vibrates then goes do a dark screen with a blue pulsing indicator light and then starts the sequence over after a few seconds.
I tried to remove my MicroSD card and boot without that with no success. Is it possible I need to format my internal storage as well? The guides usually don't mention what you're coming from, so I have no idea what starting point they expect me to be at.
Files used:
cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2vzw
gapps-511-base-20151205-1-signed
I did NOT use the below CM Recovery, however. I was afraid to do that and lose my ability to recover my old image.
cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2vzw-recovery
I'm able to recover back to my original ROM, but any help to upgrade is greatly appreciated. I'm tired of messing with this....
Click to expand...
Click to collapse
I'd suggest maybe switching your recovery. I'm also running the same version of slimkat on my old S3.
Nexus 6 via SSHD/Cataclysm
ShapesBlue said:
I'd suggest maybe switching your recovery. I'm also running the same version of slimkat on my old S3.
Nexus 6 via SSHD/Cataclysm
Click to expand...
Click to collapse
yea, I tried using Clockwork Mod recovery as well. CM12.1 includes a recovery as well, but I'm hesitant to use it....
Also, how did you patch the Stagefright exploit on that?
hypercoyote said:
yea, I tried using Clockwork Mod recovery as well. CM12.1 includes a recovery as well, but I'm hesitant to use it....
Also, how did you patch the Stagefright exploit on that?
Click to expand...
Click to collapse
I mean change the recovery to something else like twrp. Honestly I didn't. I personally think the stagefright exploit wasn't anything to worry about
Nexus 6 via SSHD/Cataclysm
ShapesBlue said:
I mean change the recovery to something else like twrp. Honestly I didn't. I personally think the stagefright exploit wasn't anything to worry about
Nexus 6 via SSHD/Cataclysm
Click to expand...
Click to collapse
Yea, you might've missed that part or I worded it weird, but I tried both TWRP and ClockworkMod and they both produced the same result.
hypercoyote said:
Yea, you might've missed that part or I worded it weird, but I tried both TWRP and ClockworkMod and they both produced the same result.
Click to expand...
Click to collapse
That's weird. I've been using twrp on nearly all my devices and the only issue I've ever had is to update it
Nexus 6 via SSHD/Cataclysm
ShapesBlue said:
That's weird. I've been using twrp on nearly all my devices and the only issue I've ever had is to update it
Nexus 6 via SSHD/Cataclysm
Click to expand...
Click to collapse
Well, I don't think it's a recovery issue. My guess is it's got something to do with the Bootloader, some files on my phone. I really don't know. Doing the whole custom ROM thing isn't really that hard or complicated once you know what you're doing, but I've run out of things to check on. I don't recall doing anything odd before when I upgraded to Slimkat, but even if I did, it should've been undone in the install process of CM12.1.
hypercoyote said:
Well, I don't think it's a recovery issue. My guess is it's got something to do with the Bootloader, some files on my phone. I really don't know. Doing the whole custom ROM thing isn't really that hard or complicated once you know what you're doing, but I've run out of things to check on. I don't recall doing anything odd before when I upgraded to Slimkat, but even if I did, it should've been undone in the install process of CM12.1.
Click to expand...
Click to collapse
Very possible. I wish I knew what to do or how to help with this issue
Nexus 6 via SSHD/Cataclysm
ShapesBlue said:
Very possible. I wish I knew what to do or how to help with this issue
Nexus 6 via SSHD/Cataclysm
Click to expand...
Click to collapse
Me too! lol
Hehehe