Short version: Nexus 4 is stuck on bootloop but it's as good as new with the stock ROM.
Long version: My nexus 4 has stock kernel, stock ROM of Lollipop that was updated when google rolled it out few months back. I did have my bootloader unlocked via Nexus Root Toolkit few months back while i still had KitKat, but apart from that, i have NEVER ROOTED, NEVER INSTALLED A CUSTOM RECOVERY, NEVER CHANGED KERNEL, NEVER INSTALLED ANY OTHER CUSTOM ROMs. The only tampering i did was unlock the bootloader and never bothered anything else. But suddenly, my phone got stock on bootloop last night. I powered it off normally, full charged the phone, and when i turned it on, it got stuck ever since. It did happen once when the phone updated to lollipop for the first time, but a simple restart solved it that time. I have tried wiping cache, factory resetting and wiping cache again, but no luck so far.
All posts related to stuck bootloop in XDA are because of tampering the phone, installing a custom ROM, going back to stock etc. I didn't find a relevant post if this happens while still in stock with never tampered phone. If there is a post like that, please kindly redirect me there. I am left without a clue here with very less experience outside stock stuff.
PLEASE HELP !
cart00nist said:
Short version: Nexus 4 is stuck on bootloop but it's as good as new with the stock ROM.
Long version: My nexus 4 has stock kernel, stock ROM of Lollipop that was updated when google rolled it out few months back. I did have my bootloader unlocked via Nexus Root Toolkit few months back while i still had KitKat, but apart from that, i have NEVER ROOTED, NEVER INSTALLED A CUSTOM RECOVERY, NEVER CHANGED KERNEL, NEVER INSTALLED ANY OTHER CUSTOM ROMs. The only tampering i did was unlock the bootloader and never bothered anything else. But suddenly, my phone got stock on bootloop last night. I powered it off normally, full charged the phone, and when i turned it on, it got stuck ever since. It did happen once when the phone updated to lollipop for the first time, but a simple restart solved it that time. I have tried wiping cache, factory resetting and wiping cache again, but no luck so far.
All posts related to stuck bootloop in XDA are because of tampering the phone, installing a custom ROM, going back to stock etc. I didn't find a relevant post if this happens while still in stock with never tampered phone. If there is a post like that, please kindly redirect me there. I am left without a clue here with very less experience outside stock stuff.
PLEASE HELP !
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
Sorry to hear about your trouble but fortunately there is an XDA area dedicated to the LG/Google Nexus 4 at http://forum.xda-developers.com/nexus-4 which would be a good starting place. I suggest you post your question with all relevant details in the friendly Q&A forum there at http://forum.xda-developers.com/nexus-4/help where the experts familiar with your device will be best able to guide you.
Good luck!
EDIT: Member has now posted in the suggested area. Thread closed.
Related
Hey all, I am looking for a little help with my phone. As the title says, I don't have enough posts to ask my question in the development section, so I have to post here and hope someone can help me figure this out.
I'm running the latest release 5 of Jellywiz with incubus' ICS theme and the VRLG7 modem on my unlocked rooted with cwm 6.0.1.2 Verizon Galaxy S3. I'm not a developer, but I'm not a noob either, so I have all the bases covered for generic troubleshooting.
Last night my phone died at a party, when I got home I plugged it in and went to sleep. This morning it was fully charged so I unplugged it and booted it up. pretty much as soon as it was booted up (before i even unlocked the device) i saw a toast notification that "system has been granted superuser permission" then 5-10 seconds later I felt 4 or so vibrations and then the device reboots itself.. Once it reboots, it does again what I just described and will continue doing it until I take out the battery.
One time I managed to get into superuser and delete the system entry, then once it asked permission I denied its request. Didn't change the end result at all. Now it says "system has been DENIED superuser permission" and still reboots, following the same pattern.
Also, this isn't the first time this has happened. A few days ago when release 5 first came out I updated from release 3 and lost GPS, restored to an earlier backup that had GPS (i think release 1) and dirty flashed 5 again which kept my GPS working. Then I debloated some stuff and when I rebooted I experienced this problem. I eventually odin'd back to stock and did the whole reunlocking rerooting and all that fun stuff and then loaded up release 5 to have a fresh and clean install and it worked flawlessly for about 2 days until now.
So I guess my questions are; is there something i can do now to fix this "system root access" leading to reboots other than using odin to go back to stock, AND since I've been through odin once and it just came back on its own, what might i be doing to cause this problem in the first place. (nobody that i could find in the Jellywiz thread or on a simple google search had this problem)(I had hardly restored any apps or data just before the most recent occurrence so i dont think it has anything to do with other apps)
Thanks in advance for any help or advice, I believe you all with be able to help me get to the bottom of this!
Ok, first off, its a good thing that this wasnt posted in development, as it would have been promptly moved. You have not developed anything ( other than a problem )
Have you done any overclocking? More specifically, overclocking where your custom freq. profiles are applied at boot?
preusstang said:
Ok, first off, its a good thing that this wasnt posted in development, as it would have been promptly moved. You have not developed anything ( other than a problem )
Have you done any overclocking? More specifically, overclocking where your custom freq. profiles are applied at boot?
Click to expand...
Click to collapse
I agree a new thread about this wouldnt belong in development, but i can't even post in the thread relating to the ROM until i have 10 posts.
I have not overclocked or undervolted or really edited anything about the rom in any way... I odin'd to stock, unlocked, rooted, loaded custom recovery, factory reset, wiped data, cache, dalvik, all that stuff, loaded release 5, rebooted, then back to recovery to fix permissions, then rebooted, then recovery to flash rom developers theme, then rebooted... worked well for 2 days, then this morning i keep getting "system granted superuser permissions" leading to multiple vibrations, freezing, and a reboot.
Hey everyone.
So, this started happening to my Nexus (stock, unrooted, locked) after the 5.0.1 OTA update: youtube.com/watch?v=BolnMQx3LGs
It started in the first days of January, after receiving the 5.0.1. update. The phone randomly restarts and gets in a boot loop. For the last month it happened once or twice every week, often making the phone useless for several hours. I posted on the Nexus help forums, noticed a lot of people with the same problem as me, but no solutions.
Today I had enough and sideloaded Kitkat again. So far so good, but I don't want to celebrate just yet.
Has this happened to anyone here. Is there a reason for this to be happening or a solution?
I wish I had the answer. My wifes' stock rooted N5 did this 2 weeks ago and I could not keep it booted into recovery long enough to flash any images. I bought myself an N6 then I wiped my CM11 N5 and loaded stock 5.0.1. for her and put in her sim. She was fine for the last two weeks. Now today she says it is doing it to this phone. The first phones' issue looked exactly like your youtube video. Not your standard bootloop. Wiping cache and dalvik did not fix. A couple other threads mention they suspect kernel. Assuming I can get it to stay on the bootloader I will probably flash elementalX and see if that solves it.
thionylx said:
I wish I had the answer. My wifes' stock rooted N5 did this 2 weeks ago and I could not keep it booted into recovery long enough to flash any images. I bought myself an N6 then I wiped my CM11 N5 and loaded stock 5.0.1. for her and put in her sim. She was fine for the last two weeks. Now today she says it is doing it to this phone. The first phones' issue looked exactly like your youtube video. Not your standard bootloop. Wiping cache and dalvik did not fix. A couple other threads mention they suspect kernel. Assuming I can get it to stay on the bootloader I will probably flash elementalX and see if that solves it.
Click to expand...
Click to collapse
Sounds like a stuck power button to me.
Sent from my Nexus 5 using XDA Free mobile app
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
Hi, thank you for using XDA Assist. To update to 5.x you need to be 100% stock. That means no custom recovery, no root,etc. It would be best to ask your question here,http://forum.xda-developers.com/moto-g/help where the experts on your device reside. And you may need this,http://forum.xda-developers.com/showthread.php?t=2542219
Good luck!
Thread closed.
Hey, so basically I'm in a situation where I have no idea what to do.
I recently just got a new phone, and am going to give my Samsung Galaxy S3, SGH-T999V model - from Wind Mobile to my Dad. Basically, when I first got the phone - a couple months after, I decided to try Rooting it, and I did, successfully. Since I didn't really know what to do with my rooted phone, I decided to unroot it - then tried rooting it again some months later, but it didn't work successfully. Basically my phone wasn't rooted, but I had the "Team-Win" recovery on it.
I wanted to bring my phone back to it's original state - and have the stock recovery on it. After some Googling, my solution seemed to be to flash the stock rom for the SGH-T999V model onto my phone using Odin. And I did that - and it worked successfully. But I still couldn't check for OTA updates or anything, it said my phone had still been modified in an unauthorized way.
Now that I need to give the phone to my Dad, I have to format the device and erase everything. This is where my problem starts. When I try to format it (using the Stock recovery), I see a bunch of error messages, with the Android logo falling down in a kind of dead way. I reboot my device, and nothing changes.
It still has all my data, and everything on it.
Sorry if this is the wrong area to post this (I'm relatively new to the forum), and if my problem doesn't make much sense - I've tried being as detailed as possible. Could anyone help?
Hi, thank you for using XDA Assist. Flashing the stock firmware should show you to get ota's. This should have everything you need,http://forum.xda-developers.com/galaxy-s3/general/samsung-galaxy-s3-sticky-roll-thread-t2344125. Also, you can ask further questions here,http://forum.xda-developers.com/galaxy-s3/help/help-thread-galaxy-s3-question-t2690307
Thread closed
Please could someone help ! I'm trying to unlock my XT1032. I have the correct Sim-Unlock (network unlock) code from my old telco, but... it won't work because the phone is rooted, bootloader unlocked (S-ON) running CM13.
I figured that returning it to a stock build would allow me to unlock the phone, then I could re-root and return to CM13 on my new network.
However..... there are about a dozen guides on returning a Moto G to stock and the first one I tried left the phone stuck on the 'Warning: Bootloader is unlocked' message. Since then, I've tried several other guides and have got nowhere fast. I've been on this for four hours now and the only thing I seem to be able achieve is to get TWRP or CWM recovery on there by flashing from fastboot. Every other image I try either gives 'preflash validation failed' messages, sticks on the Bootloader Unlocked screen or gets it stuck in a bootloop!
I just want to switch networks... Why is this so bloody difficult ?
What Firmware did your XT1032 originally come with? or which Carrier?
Kitkat I think, and it's Tesco (UK).
I subsequently did the OTA update to Lollipop and then.... WHOAAAAA.... hold on... it's booting !!!
I don't know how, or what I've done to get this far, but the only thing I can think of that's changed is that the battery is now at 100% charge. It appears as though it's successfully flashed the 5.1 untouched ROM from http://forum.xda-developers.com/devdb/project/?id=7981#downloads
But, I've tried flashing that loads of times this evening and it's failed everytime.
Having said that it's booting, it's sitting here on the Motorola logo - and it hasn't got that far in the last five hours.... I'll be back shortly !
Update: It worked ! It completed the boot, I put the new SIM in, it asked for the unlock code and this time it worked OK. Now I'm tackling putting CM13 back on it. I think I'll stick with TWRP rather than CWM recovery, as long as TWRP can handle the automatic updating for the CM nightlies.
I have no idea what went wrong there - maybe it was just that the battery had to be at 100% ?? Who knows... Thankfully I doubt I'll be tackling that again !
I don't know if things have changed, but I would be careful with OTA Updates in CM. People have hard-bricked (phone is effectively destroyed) applying updates in this way. I also suggest you avoid official Motorola updates, rather use the factory firmware images available here: (which already include the content of OTA Updates)
[INDEX] Moto G [Falcon][Peregrine] Factory Firmware Images​
Thanks for replying anyway mate. In the end, it's all good now. Unlocked and back on CM13 and on my new network !
Ahhh... not so good after all. The phone reboots every time you try to uninstall an app. I've tried flashing back to CM12.1, the latest stable release, and it does the same, so I've obviously screwed something up along the way.
Could someone help me flatten this thing completely and get it working normally please?
I've tried reflashing loads of times, even tried Cyanogen Recovery instead of TWRP but nothing I do gets rid of this reboot problem.
Can anyone assist please?
OK, so I've followed the procedure detailed here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 and flashed the Untouched 5.0.2. EU Stock ROM successfully, but it still reboots when you try to uninstall any app.
Whatever it is that's causing this is not getting overwritten by the flashing procedures I'm using is it ?
HELP !!!!!
@aneng64 - You have not done what I told you to do. Read my post again.
Yes I did... and I still had the same problem. It was only once I stopped trying to flash zips from TWRP and used mfastboot to flash the whole set individually (non-hlos, motoboot etc) that I got it to behave. The issue, incidentally, seemed to be the same one mentioned elsewhere here that also causes settings to crash when you try to go into settings, security.
Once it was stable with a stock ROM, I was able to flash CM13 again and it's now sorted. Thanks for your help anyway.