To start off, I have been running the pure nexus rom on marshmellow 6.0.1, and twrp 3.0.2-0 for months now, and loving my mxp. Today, my phone randomly froze (which happens often, due to me maxing out my ram with too many things running), no big deal right? We'll just hold the power button to hard reboot phone like normal Wrong. My phone now does not boot at all. I cannot get passed the "warning bootloader unlocked" screen. I cannot boot into twrp either, as it freezes at the teamwin start up screen (so unable to flash via recovery). None of my 3 computers recognize my phone as being plugged in (so unable to use adb/fastboot to flash), and fastboot flash mode is "Secure". Have I bricked my phone? I have not made any changes to it in months (aka I haven't flashed ANYTHING to my mxp in months, hence why I am so dumbfounded). I am willing to go back to stock (preferably keeping twrp) if need be. Any help is appreciated. Thanks
Have you tried a simple wipe? Open TWRP and go to Wipes, Advanced, and select caches and user data (NOT system or boot) and reboot... if not, you need to reflash your ROM.
And BTW, "Today, my phone randomly froze (which happens often, due to me maxing out my ram with too many things running), no big deal right?" Yes, actually that is a big deal... it is not normal and shouldn't be happening, you should have been troubleshooting that issue. Android usually doesn't just "max out RAM" and freeze up unless something is wrong.
Related
Nexus 7 (2012)
4.4.4 Stock
KTU84P
HW Version - ER3
Bootloader Version - 4.23
Locked Bootloader
Not Rooted
I have a Nexus 7 sitting in front of me that was dropped off by my aunt in hopes that I could repair it for her. It doesn't look too promising, but I thought I'd consult the mighty fine people here on XDA before I give her the bad news. Here's what she says happened. Yesterday, while preforming day to day activities on it (browsing internet, Skyping, Facebook, etc), the device completely froze. After holding down the Power Button and forcing it to shutdown, she booted it back up. Everything seemed to functioned properly for about 30s - 1min when, at that time, the device turned off and rebooted on its own. After booting back up, it started to repeat this cycle. Basically getting stuck in a bootloop. I personally have never witnessed a bootloop like this before, where the device successfully boots up completely into the OS before turning off and repeating. I'm more used to dealing with ones where it might go as far as the manufacturer logo and then repeats. So anway, as I stated, I only have a 30s - 1min window where I can make changes in order to troubleshoot. The first thing I figured I should do was to go into "About Device", turn Developer Mode on and get USB Debugging enabled. I was able to do this and used "adb devices" to confirm its connection to my computer before it looped again. After its next bootloop I headed back into settings because I wanted to take note of the Android version she was running. As I was navigating there, I noticed that the Developer Options were no longer active. Basically as if I hadn't enabled them yet. This made me start thinking that changes being made on the device weren't sticking. I decided to make a few visual changes to the home screen and see if they were still there after the next bootloop. I uninstalled an app, rearranged icon placement, and changed the wallpaper. Once it shutdown and booted back up again, everything was back to the way it was before the changes had been made. The app I had uninstalled was still there, the wallpaper reverted back, and the icons were back in their original location. At this point I decided to see if I could reboot into Safe Mode. Unfortunately, this doesn't work. I am able to get the reboot to Safe Mode confirmation box and tap "Ok" but it remains in Normal mode when it boots back up. I eventually tried to boot into recovery and preform a Factory Reset. I was able to get into recovery and reset the Nexus. Or so I thought. Instead of seeing a Device Setup screen after it wiped, like I assumed I would, it booted up and still had all the data on it. There were no errors during the wipe and it was confirmed with "Data wipe complete." afterwards.
I am absolutely lost. I've never dealt with such an unusual issue before. Especially with it not even reacting to a complete data wipe. So, just to recap . . . I only have 30s - 1min available to interact with the OS before it reboots itself, any changes made during that time don't stick, Device is successful booting into Stock Recovery, and I can successfully get a Fastboot connection when booting to the Bootloader.
Luckily she has come to terms that this might not get fixed and has decided to go a head an order a newer 2013 model. I'd still like to try any solutions that you all might have. Just in case there is a slight glimmer of hope.
Oh, and one last thing I should mention. I tried to see if I could get the bootloader unlocked but it didn't work. This is the first Nexus I've ever had in my possesion, so I'm not really familiar with the tools available for it. I found WugFresh's Root Toolkit and attempted to Unlock with it. The process seemed to go as it should and I didn't receive any errors on the tablet or in the software. However, in the end, it didn't make any changes to the bootloader.
same problem
I have the same problem as you.
Did you find a solution?
Can anybody help us?
Thanks.
I have a similar problem, but I think mine is related to the bootloader.
I'm stuck on 3.34 and that's where it fails ever time I try Wug's Nexus Tool Kit.
Have you tried Nexus Tool Kit yet?
eawooten said:
I have a similar problem, but I think mine is related to the bootloader.
I'm stuck on 3.34 and that's where it fails ever time I try Wug's Nexus Tool Kit.
Have you tried Nexus Tool Kit yet?
Click to expand...
Click to collapse
I have tried factory reset from recovery, no errors while wiping but when device restarts nothing has happened: I only have a 30s-1min of old system with all my data and apps or directly bootloop.
Also I have tried flash factory images with Nexus Tool Kit and directly from bootloader. No errors while flashing, apparently has flashed new image system. When device restarts nothing has happened: bootloop or my old system with data and apps for 30s before restart.
Myself and a few others are having the same problem... please keep us updated if you find anything out.
http://forum.xda-developers.com/showthread.php?t=2588911
First, thank you to the mods for putting my last post in the right place (and now I know where the right place is).
Anyhoo, my previous problem was a hardware issue that I've had repaired.
Now, this is no longer critical since I bought a replacement phone (Xperia Z if anyone cares) that is happily rooted and running CM. However, I'd still like the S4 rooted with CM and ready to go in an emergency.
The downside of the repair was that the shop I took it too re-flashed it back to stock (I wasn't happy, but hell, it gives me something to do, practically risk free now). Having soft bricked the I9505 three times, I've brought it back to life. However, I'd like to get twrp on there (Honestly, CWM is stepping backwards rather than forwards IMHO, dumbing down to the lowest common denominator). I have the flash files, and for good measure, I have a stock G4 recovery.
Now my problem,. whilst the phone will boot normally without an issue (I said I brought it back from dead), I can't boot to any recovery, either from the phone itself with HW keys, or via adb. It simply sits there at the Samsung logo pretending to boot. This is with both TWRP and stock, so I'm stumped.
I get the Samsung logo, with the little blue too tiny to read text top left, and there it stays. Normal reboot works just peachy with both. Not rooted as best as I can tell (though it should be). i.e. In developer options, none of the root stuff (enhanced reboot, root options etc.) are missing.
So, whilst not critical (it will still be a handy backup phone), any ideas?
you wouldn't have any advanced reboot options unless they were in the rom, and you can't have TWRP without root. maybe the phone shop left you with nothing as a recovery because they forgot ???
In Odin, uncheck everything except f.reset time, flash the tar version of TWRP in Odin, when you see the word "reset" in the status window, remove USB cable from the phone, remove battery, wait 5 seconds, replace battery, use buttons to get into recovery.
Getting into recovery.
*Press the three button combo of vol.up+home+power button
*As soon as Samsung appears relase the combo and in a jiffy press only the volume up+home button.
Hurray! :')
In order:
I've reflashed TWRP, stock, and CWM - all the successful, but same result
No Odin,. Linux user exclusively - so Heimdall
Three button combo starts recovery reboot (the giveaway is the too small to read blue text top left), but there it hangs. Using abd results in the same.
It simply hangs on booting recovery, whichever recovery, but will boot normally without a problem. Tried with and without SIM/SDCard/both/neither.
Probably worth adding, I'm not new to rooting (done it with my last 7 phones, including the one I'm currently using (Xperia Z)), and the S4 was rooted with CM13 before the shop got their hands on it.
After flashing twrp, are you letting the phone auto reboot from Odin?
How many times. Linux user - no Odin (that's Windows) - Heimdall, and it's not just TWRP, it's stock, TWRP and CWM
Personally, recommend trying to flash with Odin. I use Mac OSX myself.
I only have two options for Odin, either via a VM or using wine, and neither lets it detect the phone in download mode.
However, heimdall has always worked well (previously on this phone) so I'm not convinced that's the problem.
Don't know why, but it's finally worked.
How do I mark solved?
All,
I have had my Nexus bootloader unlocked and even rooted it before.
However, I friend needed a phone so I let her use my phone...about a month later she said the battery was bad because the phone keeps cutting off.
Long story short I got the phone back and I think she picked up some type of virus or something got corrupted because I forgot to lock the bootloader when I gave her the phone.
Here's what I have found and done:
Found out:
1. The phone will turn on while plugged in after a couple of tries.
2.If the phone is not plugged in, it gets to the 4 dots and either re-boots or shuts off
3.If I turn it on while plugged in and then unplug it and set the display to turn off after 30 minutes...the phone will stay on, until the display shuts off then the phone shuts off.
Here's what I tried:
1. sideloaded Android 8.1 using TWRP (about 5 times)
2. Wipe cache and the other cached (several times)
3. Tried rooted it again...using SuperSu BUT during the re-boot it will stay on the "Google" screen for 30 minutes and not do anything...will not re-boot or nothing...phone get's really hot. (tried this several times)
4. Using TWRP recovery and if I leave the phone unplugged (while in recovery mode) the phone never cuts off.
So I am thinking one of these partitions is bad, corrupted or missing which is causing the phone to think the battery is low and cuts the phone off. Just guessing here. Maybe some malware is installed on a partitions and flashing is not during the trick.
Any suggestions???
I really wanted to keep this phone as a rooted phone I can play with and try different things.
Thanks,
Real
realkewl said:
All,
I have had my Nexus bootloader unlocked and even rooted it before.
However, I friend needed a phone so I let her use my phone...about a month later she said the battery was bad because the phone keeps cutting off.
Long story short I got the phone back and I think she picked up some type of virus or something got corrupted because I forgot to lock the bootloader when I gave her the phone.
Here's what I have found and done:
Found out:
1. The phone will turn on while plugged in after a couple of tries.
2.If the phone is not plugged in, it gets to the 4 dots and either re-boots or shuts off
3.If I turn it on while plugged in and then unplug it and set the display to turn off after 30 minutes...the phone will stay on, until the display shuts off then the phone shuts off.
Here's what I tried:
1. sideloaded Android 8.1 using TWRP (about 5 times)
2. Wipe cache and the other cached (several times)
3. Tried rooted it again...using SuperSu BUT during the re-boot it will stay on the "Google" screen for 30 minutes and not do anything...will not re-boot or nothing...phone get's really hot. (tried this several times)
4. Using TWRP recovery and if I leave the phone unplugged (while in recovery mode) the phone never cuts off.
So I am thinking one of these partitions is bad, corrupted or missing which is causing the phone to think the battery is low and cuts the phone off. Just guessing here. Maybe some malware is installed on a partitions and flashing is not during the trick.
Any suggestions???
I really wanted to keep this phone as a rooted phone I can play with and try different things.
Thanks,
Real
Click to expand...
Click to collapse
Not an expert but i suggest you do the following:
Backup the boot image, download the modified boot image for 4 cores. Try to boot, if it boots normally, your problem is BLOD and it will be solved. If that is not the case, use the 1 click flash bat from the modified fastboot folder that you can find doing some search, that bat will recreate partitions and reflash everything and also flash the rom you provide it then try to boot again. Shutdown the phone, give a charge until 90ish, let it cool and then boot it up.
xxJMarian said:
Not an expert but i suggest you do the following:
Backup the boot image, download the modified boot image for 4 cores. Try to boot, if it boots normally, your problem is BLOD and it will be solved. If that is not the case, use the 1 click flash bat from the modified fastboot folder that you can find doing some search, that bat will recreate partitions and reflash everything and also flash the rom you provide it then try to boot again. Shutdown the phone, give a charge until 90ish, let it cool and then boot it up.
Click to expand...
Click to collapse
Thank you for taking the time to reply...and thanks for your suggestions. I tried both and was very hopefuly...but did not work. The phone still will not boot unless the usb is connected and powered. However, not sure if I did the 4core correctly because I could not tell if it worked or not. I found a twrp 4core for bullhead and that is what I used. However, when you first flash it and it does an auto reboot it boots into TWRP not Android. So within TWRP I just click on reboot system...but same outcome.
I think maybe this phone's hardware is dead or something got burned out...but it is not the battery.
Thanks,
real
realkewl said:
Thank you for taking the time to reply...and thanks for your suggestions. I tried both and was very hopefuly...but did not work. The phone still will not boot unless the usb is connected and powered. However, not sure if I did the 4core correctly because I could not tell if it worked or not. I found a twrp 4core for bullhead and that is what I used. However, when you first flash it and it does an auto reboot it boots into TWRP not Android. So within TWRP I just click on reboot system...but same outcome.
I think maybe this phone's hardware is dead or something got burned out...but it is not the battery.
Thanks,
real
Click to expand...
Click to collapse
You did it wrong. You have to flash the boot.img that disables 2 of your cores. Search it here on the forum you'll find it
A couple of days ago. I wanted to check my phone in the morning and it started boot looping when I pressed the power button. Then, after a couple of boots it went into the TWRP recovery. I wiped cache/dalvik in hopes of a quick fix but still boots into recovery.
I can also go into the bootloader but the bootloader is completely unresponsive. It just gets stuck on the "barcodes" option, the volume keys do nothing and adb doesn't see my device when it's in the bootloader. I also tried re-flashing the same ROM I'm using(within recovery) to no avail.
I still intended on using this thing for a couple more years (I have a couple of spare OEM batteries and a spare chasis). Really appreciate any help.
Recovery.log from TWRP
Any flash drive can become corrupted.
Boot loops are commonly caused by poorly coded apps like launchers and power management apps.
Rootkits are always suspect with abnormal boot ups and unstable operation when no other cause can be found.
On a stock Android a factory reset or in extreme cases a firmware reflash will resolve it unless it's a hardware failure which is rare*. Be careful what you flash, install and download... always.
*a drop, water exposure or a ESD event when repairing a phone can cause this... sometimes not immediately.
blackhawk said:
On a stock Android a factory reset or in extreme cases a firmware reflash will resolve it unless it's a hardware failure which is rare*. Be careful what you flash, install and download... always.
Click to expand...
Click to collapse
Can I reflash firmware without the download mode working properly?
Sorry, way beyond my skillset...
Hi!
I used my S7 Edge for a couple of years and now I am afraid it may have died on me. As always, backups of f.e. pictures are not up to date.
During the night, it lay on my Qi charger. When I took it in hand, the screen was extremely dark and stuck in the "loading Lineage" screen. I tried to reboot. It was stuck on the "Samsung Galaxy" screen.
I wanted to boot into recovery and wipe the cache and see if it works again. But I can't boot into recovery mode. No matter if I connect it to a USB cable, the button command does not work.
Switching the device off also isn't possible. The only way to switch it off is disconnecting the battery (I have opened it to do so).
The only thing I can do is booting into download mode (so I know my volume up button works...).
Several times the screen was stuck on the "empty battery" symbol - which did not change no matter how long I had it in the charger. I can't really replicate how I got to the battery screen. I installed another battery just to see if if by some magic this would change something, but nothing changed about my issue. No boot possible and no booting into recovery.
I thought to myself: Well, maybe if I reinstall TWRP I can get into Recovery again. But when I try Odin I get the error message: "there is no PIT partition"
I know you will want additional info:
sadly, I cant' say which version of lineage I had running. I would have to look into my phone - which I can't.
I installed Lineage a couple of years ago, the phone was rooted and had TWRP recovery. I changed my USB port and Audio port several months ago.
But everything was running fine - I did not change or do anything recently. It happened overnight.
Do you have any ideas what I can do? I am brooding for two days now over this issue and I am at the end of the line here.
Did my memory just die on me? Is it an unfixable hardware issue?
Or software-related and potentially salvageable?
thanks in advance for anybody that bothers with my problem.
PinkElf said:
Hi!
I used my S7 Edge for a couple of years and now I am afraid it may have died on me. As always, backups of f.e. pictures are not up to date.
During the night, it lay on my Qi charger. When I took it in hand, the screen was extremely dark and stuck in the "loading Lineage" screen. I tried to reboot. It was stuck on the "Samsung Galaxy" screen.
I wanted to boot into recovery and wipe the cache and see if it works again. But I can't boot into recovery mode. No matter if I connect it to a USB cable, the button command does not work.
Switching the device off also isn't possible. The only way to switch it off is disconnecting the battery (I have opened it to do so).
The only thing I can do is booting into download mode (so I know my volume up button works...).
Several times the screen was stuck on the "empty battery" symbol - which did not change no matter how long I had it in the charger. I can't really replicate how I got to the battery screen. I installed another battery just to see if if by some magic this would change something, but nothing changed about my issue. No boot possible and no booting into recovery.
I thought to myself: Well, maybe if I reinstall TWRP I can get into Recovery again. But when I try Odin I get the error message: "there is no PIT partition"
I know you will want additional info:
sadly, I cant' say which version of lineage I had running. I would have to look into my phone - which I can't.
I installed Lineage a couple of years ago, the phone was rooted and had TWRP recovery. I changed my USB port and Audio port several months ago.
But everything was running fine - I did not change or do anything recently. It happened overnight.
Do you have any ideas what I can do? I am brooding for two days now over this issue and I am at the end of the line here.
Did my memory just die on me? Is it an unfixable hardware issue?
Or software-related and potentially salvageable?
thanks in advance for anybody that bothers with my problem.
Click to expand...
Click to collapse
Hi, try to flash the stock firmware otherwise I really don't know :/
I guess I will lose my data when I install stock firmware, don't I?
What I ask myself is: Is the reason for not being able to boot into recovery that my device always thinks my battery is empty?
Is the fact that I can boot into download mode a sign that my memory and/or motherboard is still intact?
PinkElf said:
I guess I will lose my data when I install stock firmware, don't I?
What I ask myself is: Is the reason for not being able to boot into recovery that my device always thinks my battery is empty?
Is the fact that I can boot into download mode a sign that my memory and/or motherboard is still intact?
Click to expand...
Click to collapse
Are you using Lineage OS? If yes, then definitely yes. On my Xiaomi, I couldn't get into fastboot mode or into recovery, I don't know why and somehow I got there, I don't even know how I think I held the power mode for a long time and when the phone turned on I held the volume up button to get into recovery finally succeeded on the umpteenth attempt and from recovery I restarted the phone in fastboot mode and flashed the stock firmware. And yes, being able to boot your phone into fastboot is a good sign. It would be worse if it wasn't possible.
I am still stuck with the problem. I can boot into download mode. I can't find a way to boot into recovery.
Is there anything I can do in download mode?
If I find the lineage version I originally installed on my device, could I install it via ODIN and get my phone back without data loss? I have only ever installed ROMs via TWRP.
Just an idea, but as of now I get the error "could not find PIT partition" anyway while trying to reinstall TWRP.
PinkElf said:
I am still stuck with the problem. I can boot into download mode. I can't find a way to boot into recovery.
Is there anything I can do in download mode?
If I find the lineage version I originally installed on my device, could I install it via ODIN and get my phone back without data loss? I have only ever installed ROMs via TWRP.
Just an idea, but as of now I get the error "could not find PIT partition" anyway while trying to reinstall TWRP.
Click to expand...
Click to collapse
Yes, you can use download mode to install the firmware via Odin. Look
That means giving up hope for my personal data...
But even if I want to do this, I run into the problem, that I can't install anything due to "could not find PIT partition"...