I installed clean rom about a year ago, so unsure what version it could be on the top of my head.
I have not updated my firmware or anything.
The only thing I did before I resetted my tablet was change a few settings.
1. I changed the resolution so it would help save me some battery.
2. It had an option to use 4.1 of android instead of 4.2, so I did that.
Other then that I read around the forum and came to the conclusion I might have soft bricked it but in the other forums they were messing with cache and was in the process of installing. So I was unsure if I should come to that conclusion, hence I started a thread.
Tried to PWR + vol down, but it vibrates and shows nothing on screen.
Shows the Logo then it increases in size (assuming at that time it was changing resolution) and then it just gets stuck.
Not sure what I could do from here on out.
Thanks ahead for your time.
xirosil said:
I installed clean rom about a year ago, so unsure what version it could be on the top of my head.
I have not updated my firmware or anything.
The only thing I did before I resetted my tablet was change a few settings.
1. I changed the resolution so it would help save me some battery.
2. It had an option to use 4.1 of android instead of 4.2, so I did that.
Other then that I read around the forum and came to the conclusion I might have soft bricked it but in the other forums they were messing with cache and was in the process of installing. So I was unsure if I should come to that conclusion, hence I started a thread.
Tried to PWR + vol down, but it vibrates and shows nothing on screen.
Shows the Logo then it increases in size (assuming at that time it was changing resolution) and then it just gets stuck.
Not sure what I could do from here on out.
Thanks ahead for your time.
Click to expand...
Click to collapse
How did you change the resolution?
Are you saying the tablet vibrates continously when trying to boot into the BL??
Did you wait long enough when trying to get to the bootloader?
You have to hold the buttons until the tablet vibrates twice, then you should see the bootloader menu.
If you can't get there, you may be in bad trouble unless you have nvflash blobs.
Related
So I have an lg g2x originally running gingerbread 2.3.3 and I went through this procedure -> http://forum.xda-developers.com/showthread.php?t=1259852&highlight=linux+g2x+root
Everything seemed to work as described except that the phone now will not boot. I get to the LG screen but then the buttons just blink and shuts down and tries to boot again.
I must have missed a step somewhere, though I am not sure where that might have happened. In any case, I would like to get this working or, at the very least, get the phone back and working.
I am running linux and do *not* have access to windows at all.
Which LG screen are you getting? The static one or the one with a moving green bar underneath it? Can you still boot into Clockworkmod Recovery or was that a no go? You need to give more detailed information so people can figure out at what point in the boot process your phone is rebooting.
I get that initial booting LG screen with the face and the letters LG, there is no green bar. It sits in that screen for 15 or 20 seconds then attempts to reboot. Well, thats what I assume happens. The screen goes black, the buttons along the bottom flash and then after a few seconds that white LG screen comes back and it does it all again. It never gets past that and never into CWM. I can still put it in the flash mode that allows nvflash to connect and do its thing, but thats about it.
If you have successfully nvflashed cwm. Then you should be able to get into cwm by holding volume down+power until it goes to a blueish LG screen. Then flash a rooted rom from there.
That is the easiest/safest way of rooting a g2x. If you haven't done this you can Google "nvflash g2x Linux" and find guides on how to do it.
Sent from my LG-P999 using xda premium
Right, thats exactly what should happen. Unfortunately, its not what actually happens. During bootup I a can hold power + volume down all day long and get the exact same behavior. Its a bit disconcerting.
[solved]
Guys, I found the problem and figured I would post it here for future folks.
I was unable to start my phone plugged into the charge (both to the computer and to the wall). I had to have the battery in for this to get to a good place. I guess initial startup just took too much power.
So if you do this, after using the restore script. Press the power button and volume down hold both, then *put in the battery*. Thats what worked for me.
thanks!
Hi all,
I have been given a tablet to try and recover by a friend who seems to have semi-bricked it. I heard that he ticked the wrong buttons in Odin and then it all went downhill from there...
See the attachment: This graphical screen is displayed all the time. I cant actually shut the tablet down, even if I boot into CWM and choose shutdown from there. It will turn the entire screen of for 2 seconds and then then go into the attached funky graphics screen and stay there.
There is no battery charge at the moment so the odd time I do get it to boot properly, it shuts down straight away. Im leaving it chargin as we speak to rule that out.
I've tried flashing a stock ROM and get an error7. I have wiped and reset the tablet and wiped both caches too.
My next move is to (after its charged) download and apply a ROM from the samsung website and see if I can return it to normal.
I really want to know why I cant shut it off and what's the deal with the weird graphics screen? Any step by step instruction on how to reset properly and what I should do would be SUPERB.
Good day to all. I'm here resorted to ask about my problem here because I really can't handle it. I been googling for days. I'm ran out of resources from both google and tablet. So, I hope you can help me here. Note I'm going to write this in FULL detail here, so expect this to be a extremely long post. (I been warning you) So here goes....
Anyone uses the brand Ramos?(kind of unpopular brand) I use Ramos W21, it's been using it around 1 year and a half, and it endured a lot of problems, but fixed by researching on online forums and apply various methods there. Now, I think it's finally gave up...
One time, when I opened it and play my usual apps and browsing, it caused the errors " unfortunately
google.process.gapps has stopped", unfortunately browser has stoped",and "unforturnately google play has stopped". Then, I tried to clear data the similar apps in settings as usual, and even disabling them. Then more errors exploded, and "unfortunately launcher has stopped" appears. The menu screen(where the usual wallpaper and shortcut apps are located) turns black, while my running apps are still there running. When I pressed the back key to exit the app, now only tons of errors from the launcher appears endlessly(while the screen is black.
The time I finally turned it off by hard reset it made its way to the main problem: the bootloop.
Okay, here's where the thing gets real. It opens with the usual ramos logo, but the next one is a silver flashing android logo instead of enlarged ramos logo with spinning fire from the letter o(which is NOT my usual boot up screen) When I turned it off, it reopens again up to flashing silver android logo and the cycle repeats, even with pin reset until battery dies out. No recovery mode, so I can't use it to fix this. USB connections can't be recognized when inserted to PC. And no, the tablet is not rooted, and I don't customized anything, no mods, and no fancy roms. Just using a stock rom.
So now what? All I have here is just a sd card slot, which I think there's hope in there. Right now it has two options, deal with it and fix with all of might, or repair it in the nearest repair shop(something that is pretty risky, a lot of fakes and robbers here)
Well, this is the first time I post here, so sorry for anything that goes wrong. Thanks in advance.
Hi, thank you for using XDA Assist. It sounds like a rouge app has replaced your boot animation. Rather than try to chase that down and try to fix it I'd flash the stock firmware and start all over. Unfortunately there is very little about your device on XDA. So you'll probably have to google that.
Solved!!!
Update: I FINALLY FIXED IT!!! IT WAS A MIRACLE!!! O.O
After I keep on wrecking it's power buttons and volume buttons, I discovered something decisive!
This tablet actually HAS RECOVERY MODE! Again, it has a recovery mode! However, the way how to input it is very unique compared to most devices, including other devices from the same brand!
Now having the power of recovery state, I first selected "wipe data cache". The old large Ramos logo with spinning fire appeared again! But it's still bootlooping. So I went back on recovery state, selected "factory reset" and boom, IT BOOTS LIKE BRAND NEW!!! (sacrificing my old data though)
Okay, I don't want this recovery mode powers to be kept only by me. So I'm going to share it to all Ramos users,especially the model W21, like right now!
1. To do this, you need power button and volume up button.
2. While bootlooping, hold the power button and volume button at the same time and it will turn it off(Then expect it to turn on back up again automatically)
3. When it opens up again to the small Ramos logo(no fire animation), now RELEASE the POWER BUTTON ONLY, and keep holding the volume up button. Note, this is important! If you do anymore than this, it will either black out, go bootlooping once again, or ultimately, nothing.
4. Keep holding the volume up button, then the ramos logo will disappear, and now it will enter to our holy grail, RECOVERY MODE! Congratz!
Now when you finally have a normal working Ramos tablet again, you may go there again by turning it off by "Power Off" (assuming that your tablet is open) then holding the power and volume up(then follow above!)
I hope this will help a ton for Ramos users! :laugh:
I'm glad you got it working. You should post your solution here, http://forum.xda-developers.com/general/general More people with your device will look there than in the Assist forum. Name the post something like [SOLVED] RAMOS Bootloop Problem
jd1639 said:
I'm glad you got it working. You should post your solution here, http://forum.xda-developers.com/general/general More people with your device will look there than in the Assist forum. Name the post something like [SOLVED] RAMOS Bootloop Problem
Click to expand...
Click to collapse
Well thank you then for the link. Gotta go there!
Thread closed.
Bought a Nexus 5 about 6 months ago USED. It has been amazing. I got the latest OTA a week ago or so, not sure if that has anything to do with current issues.
About 2 days ago started randomly restarting. Today, it shut down and has been in continuous loop restarting. I see "Google" and maybe even the boot dots loading, then it is off. Three seconds later, starts again and repeats. Never makes it all the way into Android system. I let it sit for a while and when I pick it up, without touching any buttons, it repeats all of this. I suppose it is probably dead in general, but I don't know. Do you guys have any ideas? Again, I bought it used and from a ma/pap store who said they buy 100 in bulk, which made me skeptical, but they also had a 60 day guarantee and it was amazing the first 60 days and even after. It has been error free for 6 months, so I don't know if this is just a random issue or if the previous owner dropped it in a lake and I got lucky, or what. FWIW the damn thing has been in a case and never dropped, so it isn't anything that I have done I don't think. Thanks for any help.
edit: never rooted, never messed with, always been stock
Another user reported some instability since the last OTA update.
Flashing the full factory images did the trick.
a friend of mine gave me his nexus 5 to repair and its doing something similar. He had ir rooted and on latest 5.1.1 (i think). Either way, he said it was randomly locking up and rebooting. When i got it it had the red blinking light when plugged so i got a new battery. That got fixed but then the constant bootloop showed itself. I flashed TWRP (many versions, 2.6.3.1; 2.7.1.1; 2.8.7.1; the one that worked best was 2.7.1.1). So, once in twrp wiped, pushed cm 12 snapshot, flashed it, pushed gapps, falshed, pushe supersu flashed. Started the system. That precise order of things (ie: pushing flashing, then pushing something new and flashing it) was what gave me best results to actually boot up at least once. Once booted up and logging in and everything to cm i had some sort of stability (even rebooting and powering off) but i think that everything went wrong when i plugged the phone to the computer and it was back to bootloops and not even getting to the recovery. Flashed everything again. Didnt work. Had to leave the phone sit for a while (without the back casing) before trying again, in order, before getting any success. Im starting to think of ovrheating but it doesnt even get that hot...
Dunno if you guys have any ideas on this. Or if i can give you mor details to help us out.
Regards!
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
WaxLarry said:
In my opinion your problems seems power button's related.
Click to expand...
Click to collapse
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Paul22000 said:
This morning my Nexus 5 was turned off all of a sudden after not having used it for 20-30 minutes. I held the power button and nothing. I plugged it into power and the "Google" screen appeared. It then went into a reboot loop on and off, on and off, on and off. I held the Volume Buttons and it went into fastboot, but then boot looped out again and again. Searching on Google yielded that this was indeed a common problem. [...]
Click to expand...
Click to collapse
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Ok @jeffsf keep going on this thread. I had the same damn experience, that ended with RMA. LG said that the problem is related to some tension change in the power button. After the RMA I used the phone totally stock and never had a problem. Two months ago I switched to blu_spark kernel and some weeks after i noticed some problem. When I pressed the button to lock the screen, phone locked itself and then screen turned on, sometimes showing the shutdown option. So i understood that something was happening to the power button. I tried to overvolt with a +5mV on general offset and since then i never had problem. If you can enter recovery or bootloader i suggest you to flash some kernel with volt change support and then overvolt the general offset... and keep finger crossed
jeffsf said:
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Click to expand...
Click to collapse
I got a notification for this post since you quoted me. I'm not sure if you're having the same problem but I'll tell you what happened to me, just in case. I called T-Mobile and they referred me to the nearest 3rd party phone repair shop. I went there and after an evaluation, the repairman told me the power button on my phone was indeed broken. They replaced it for $55.
The story doesn't end there though. I took my phone home and a few hours later I tried to use bluetooth and it didn't work. I took it back and found out that unfortunately, when the guy replaced the power button, he inadvertently broke the bluetooth. There's no way to fix bluetooth without replacing the motherboard entirely, which would cost $200. I'd rather buy a new phone at that point since my Nexus 5 was getting old. He refunded me, which was nice. At least the power button worked so I could use my phone. Bluetooth isn't as valuable as being able to you know, turn on the phone, so at least it was a net gain.
After that, I purchased a Nexus 6 and rooted it so I could use double-tap-to-wake (along with the automatic screen on when you pick up the Nexus 6). I also use the following app in order to turn off the screen by swiping up from the home button (I don't care about losing the shortcut to Google Now): Screen Off and Lock
I can now literally go weeks without using the power button on my Nexus 6. (I literally only use it when tap to wake sometimes becomes unresponsive which is rare.)
Bottom line: I will never buy another phone without tap to wake functionality! :good:
A local repair shop here indicated that one sometimes does changing the power switch resolve the issue. They have seen situations where the issue appears to be one of the power-management ICs. Just something to be aware of when examining the potential cost of a repair and who you would have do the work.
I'm a serial lurker here and hate to ask for help, but want to reach out (and finally start hitting thanks).
My N5 was on MMB29S 6.0.1, SuperSU version 2.65 for root, xposed v79 (gravitybox, APM+, snapprefs), and ran perfectly fine up until a few weeks ago when I started having issues. Apps would sometimes FC, and (not always right after) system would hang and then reset. Sometimes the screen would go black but notification light still would blink.
Upon reset, it would either (a) get stuck at google screen and bootloop or (b) get stuck at some point during the boot animation. If the phone did start, it would usually work for a variable amount of time - minutes, hours, but usually not more than a day. Other times, the phone simply would not start and required a slowly increasing amount of time to boot while holding down the power button, sometimes not even booting at all. The phone would sometimes be unresponsive to holding the power button for up to 12 hours before the phone booted up again. Not saying I help the power button that long, but tried frequently over that period of time.
Over the past few days I've taken to troubleshooting in the ways I could think of and what I've read here on xda (I can link to any of the threads if you are curious) and the rest of the web. I started by disabling xposed, restoring stock boot image and removing root, and have since flashed completely to stock MMB29V and have followed the advice of @audit13 to even flash the userdata.img file and perform a factory wipe before booting the phone for the first time.
Nothing works. Even after being bone stock now there are still random resets, with the power button having to be held down for quite some time to power back on (if at all). The only difference is that it hasn't been getting stuck on the boot animation when it does power on.
I'm a bit sad, and realizing that this is probably the end of the line for my venerable Nexus 5, but any help/suggestions are welcome. Thank you in advance!
Download the Nexus Root Toolkit for your computer to try to restore your Nexus.
Could be a power button issue that's causing the resets? Have you tried removing the motherboard and quickly pressing and releasing the power button several times in a row using more pressure than normal?
audit13 said:
Could be a power button issue that's causing the resets? Have you tried removing the motherboard and quickly pressing and releasing the power button several times in a row using more pressure than normal?
Click to expand...
Click to collapse
I have yet to try that, but will try that in the next couple days. Might not get to it tomorrow as I have an upcoming exam.
I'm not completely sure if that's it though since the system seems to hang/freeze before powering down, but I can give it a shot. Thank you for the idea!
FelipeRodrigo said:
Download the Nexus Root Toolkit for your computer to try to restore your Nexus.
Click to expand...
Click to collapse
As a last resort I could try that -- how do you think that would solve my issue? Thank you!
Maybe a battery problem? I'm just guessing at the different things that may cause a boot problem or resets.