Database Info

Stuck on BOOT!!!

So i unlocked the bootloader and rooted the phone, and after that im stuck on boot and nothing seems to get it back to work.
When i use the restore function on the tool i get "fastboot" is not recognized as an internal or external or external command...
Help Please? got the phone like 20 mins ago and have not even use it (((

Will anyone be kind enough to help me? its not even funny :'(

first off... it generally might take a little bit to get a response to a thread, especially with almost no information provided. Expecting a reply within 17 minutes under such circumstances is expecting quite a lot.
Now... when you say "Stuck at boot"......... what? do you see anything on the screen? If so, what? Android on its back with a red triangle? Android standing with a thing spinning by its chest and a bar below it? Does it at least turn on at all? Need details.
And fastboot is only recognized if you actually have the phone in fastboot mode... i.e. holding power and "volume down" down when powering the device on.

elementaldragon said:
first off... it generally might take a little bit to get a response to a thread, especially with almost no information provided. Expecting a reply within 17 minutes under such circumstances is expecting quite a lot.
Now... when you say "Stuck at boot"......... what? do you see anything on the screen? If so, what? Android on its back with a red triangle? Android standing with a thing spinning by its chest and a bar below it? Does it at least turn on at all? Need details.
And fastboot is only recognized if you actually have the phone in fastboot mode... i.e. holding power and "volume down" down when powering the device on.
Click to expand...
Click to collapse
The phone turns on, and it gets stuck on the boot where the circles are spinning, if I go to fastboot the android is laying down with the chest open and blue inside.
Where im stuck is at the spinning nexus logo.... :'(

I'm starting to get the feeling that you may have jumped the gun on modding your phone... ESPECIALLY unlocking the bootloader. Probably why a lot of people suggest going the manual route for things rather than relying on a tool to make it just a series of keystrokes. Less likely to potentially miss a step if you're constantly reading what has to be done next, rather than just typing number and/or hitting the Enter key.
After unlocking the bootloader, did the phone reboot, and did you see the one thing i mentioned on the screen, the android standing with his chest open and the thing spinning in front of it, with the tiny progress bar of sorts below him?

elementaldragon said:
I'm starting to get the feeling that you may have jumped the gun on modding your phone... ESPECIALLY unlocking the bootloader. Probably why a lot of people suggest going the manual route for things rather than relying on a tool to make it just a series of keystrokes. Less likely to potentially miss a step if you're constantly reading what has to be done next, rather than just typing number and/or hitting the Enter key.
After unlocking the bootloader, did the phone reboot, and did you see the one thing i mentioned on the screen, the android standing with his chest open and the thing spinning in front of it, with the tiny progress bar of sorts below him?
Click to expand...
Click to collapse
I dont believe i saw that :/
Im trying to flash factory image now.
:/

http://www.xda-developers.com/android/how-to-root-and-unlock-the-google-nexus-5-xda-developer-tv/
May want to watch the video there. The thing i speak of is at the 4:20 mark. When the bootloader is unlocked, a factory reset is automatically performed by the phone. If you're seeing the android on his back, with the blue lights inside, and text above and below him, chances are that's fastboot mode... but it could be something different that you're talking about.
It's getting quite late, and i have to get some sleep. Hopefully someone else might be able to pick this up from here...

elementaldragon said:
http://www.xda-developers.com/android/how-to-root-and-unlock-the-google-nexus-5-xda-developer-tv/
May want to watch the video there. The thing i speak of is at the 4:20 mark. When the bootloader is unlocked, a factory reset is automatically performed by the phone. If you're seeing the android on his back, with the blue lights inside, and text above and below him, chances are that's fastboot mode... but it could be something different that you're talking about.
It's getting quite late, and i have to get some sleep. Hopefully someone else might be able to pick this up from here...
Click to expand...
Click to collapse
Yes y did saw that, my problem is that when i try to do anything i get this "fastboot" is not recognized as an internal or external or external command

I had the same problem. Jumped the gun from unlocking the bootloader to immediately installing TWRP without a reboot. I was stuck in a boot loop for hours. Power down the phone by holding in the power button. Boot into the bootloader by holding down volume and the power button. From here you can use fastboot. I wiped the data and cache. "fastboot erase userdata" and "fastboot erase cache".
The error you mention above with fastboot is your computer not finding the path to fastboot. On linux, browse to the directory fastboot is in and use ./fastboot erase userdata
Once the data and cache were cleared I could boot just fine.

http://forum.xda-developers.com/showthread.php?t=2512534
Sent from my Nexus 5 using Tapatalk

orphan22 said:
Yes y did saw that, my problem is that when i try to do anything i get this "fastboot" is not recognized as an internal or external or external command
Click to expand...
Click to collapse
It seems you didn't install Fastboot on your computer... Check the requirements.

[Q] Phone Keeps Rebooting After It Dropped

My girlfriend dropped her phone yesterday and despite that it's encased in a bulky Ballistics case it appears that the power button is broken now. When I plug the phone into my laptop using her USB cable the phone automatically boots up the Google screen with the lock icon, vibrates and then shuts off and reboots again resulting in a boot loop. Unfortunately she's out of warranty. She opened the phone and the iron nub of the power button appears to be unmovable. She also tried going into recovery, but the phone continues to reboot.
Is there any way we can fix this? I read that some people can get theirs repaired at a repair shop, but I'm not sure how viable that is in Canada. Please advise.

Getting the power button fixed isn't too expensive. Hopefully that's all you need. ?

whyareallusernamestaken said:
My girlfriend dropped her phone yesterday and despite that it's encased in a bulky Ballistics case it appears that the power button is broken now. When I plug the phone into my laptop using her USB cable the phone automatically boots up the Google screen with the lock icon, vibrates and then shuts off and reboots again resulting in a boot loop. Unfortunately she's out of warranty. She opened the phone and the iron nub of the power button appears to be unmovable. She also tried going into recovery, but the phone continues to reboot.
Is there any way we can fix this? I read that some people can get theirs repaired at a repair shop, but I'm not sure how viable that is in Canada. Please advise.
Click to expand...
Click to collapse
I have had this issue for the past 4 days. After many attempts of trying to bang the phone a lil onto my hand (for where the power button is located at), sometimes the phone will boot fine, for as long as you do not click the power button again it won't act up.
(I am pretty sure I didn't drop my phone when I was napping in the car, it just started out of nowhere after I have been using lollipop 5.0 with franco kernel for like 2 months without any problem).
Same sypmtoms, bootloop (looked like the power button defective / boot IC on mobo defective), can't even stay on recovery/bootloader screen/system for longer than 5 sec.
Try these :
- spam click power button, until it is able to boot into system, you will have to keep clicking, for every click you either screen on/off you will realize Power Off options may pop up, it looks like the power button has been holded for few sec to trigger the power off, but all you do was spamming the click to keep the button active, you have to click until you feel that certain point the power off doesn't pop up, then stop clicking ( remember never to touch that power button again for NOW), if after a few sec of using the phone and it doesn't force shut down (result from power button defective where it sense its being clicked and hold for like 8-15 sec). Then you are good to carry on whatever I am to tell here.
- go to about phone, click the build number for 5-10 times until you get the unlocked developer mode
- back, click on developer options, enable usb debugging mode (this will pop another message asking you if you want the device to memorise your pc's mac address) that way it is synced with your pc.
- before you proceed with any other thing, go to playstore, download power button to volume button, enable volume power, check start volume power on bootup, check screen off. This will help you greatly for not touching the power button to unlock the screen when you are working on your pc.
- if you have all the correct nexus usb driver installed onto your pc, you need to get Minimal ADB and Fastboot installed onto pc. After installing, run Minimal adb and fastboot, a command prompt windows will pop out and is automatically redirected to the minimal adb folder. key in this command
"adb devices" to see if it detects your device or not. There should be at least a device listed if you have the usb driver installed correctly
- now you can make use of adb commands to reboot into bootloader/recovery to do any flashing of system, backup all your data that you needed to PC. Download official 5.0.1 nexus 5 image and extract it into the Minimal ADB folder.
- is your bootloader unlocked? if not do adb reboot-bootloader
- fastboot oem unlock (this will wipe all your data on the phone)
- fastboot reboot after the wipe is done
After that you can actually carry on with flashing back to stock images. Look at this link http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 for flashing to stock factory image.
I am not sure which step has actually solved my problem, because on my first flashing of factory image, booting into system as a brand new device (no extra softwares, yet to recover any of my data). the problem persists as long as I clicked on power button once, it'll act up again random power off and bootloop.
I actually was on a follow-up cases with google play support team from Aus as my device was bought from Aus. After the last step of factory image setting, doesn't help, I intended to ship it back for RMA as my device is still under warranty and I suspected it was the hardware issues from power button too. They will send me another refurbished device. After ending the call, they sent me link to proceed with warranty claims where I need to fill in several forms and ship the device back to them.
I decided to give it one more try, due to my phone was previously unlocked, rooted, changed to franco kernel.
By restoring to stock images made my device unroot, I was afraid of google will accuse me for unlocking bootloader voided the warranty and not willing to replace another unit for me. I locked back the bootloader, then I remembered in bootloader, fastboot oem device-info shows that a record of a phone if it has been unlocked, it will show Tampered status as True, google probably can use that to track if a device has been unlocked before. So I unlocked my bootloader again (which causing another wipe for whatever data is in the device).
So I looked up on google again and found source for changing that tampered status to False in addition to locking the bootloader again, but to change that tampered status, I need to use TWRP to run the scripted zip file, so I used fastboot boot path (it is stated in the link I gave you above) to boot into TWRP images temporarily from my desktop and ran the zip file, I always practice wiping data, cache and everything before I boot the device back into a brand new factory image.
So I went to wipe dalvik cache. Rebooted the system - it was running the Optimizing x numbers of Applications.
Upon finished with that. I was surprised that, after a few clicks of power button, the random power off issues is no longer there. I even test clicking on the power button for entire day. The symptom isn't coming back. So I emailed google play support team to cancel my warranty ticket and close the case for now.
Should there be any problem again I will probably then claim the warranty for replacement.
Its been more than 24 hours now that I am using the device without any problem of random power off and on or stuck in bootloop due to power button defective.
I suspect it is either the 5.01/5.0 lollipop with ART that is causing something wrong with the boot IC / power button defective in a long run.
Or maybe it was some settings I have changed in franco kernel ? but it was running fine for 2 months which made me doubt that it is franco kernel
Or it could be some of the apps I used to tweak my phone settings - LLama and tactile player (which I have set something condition and actions for power button) but I doubt it is caused by these either.
I will observe and see if the problem comes back after some time of using the 5.0.1 stock image now.
Oh I am also back to using franco kernel, unlocked bootloader and rooted again. Haha...
Hopefully you are able to solve the problem by trying some factory reset method + wiping cache, partition and dalvik.
If not, you probably may have the hardware issues, I have seen some other forum/websites with n5 users upon replacing the mobo, no longer encounter such problem.
Regards,
Kean

Thanks for the replies. My girlfriend was able to get the power button repaired for $80 and replaced the external button for $7 + tax, she paid $98. At least it's cheaper than a new phone.

Question Z flip 3 bootloop

The problem I have is with the galaxy z flip 3, it worked just fine inthe morning but after it ran outta juice and I charged it to a certain percentage, it stopped working properly, and got into an infinite boot loop, I tried forcing it to restart by long pressing volume down+power , but it didn't work, then I tried opening the recovery by long pressing on volume up+power and yet it also didn't work (I think that maybe it's because it was trying to boot at the time), so have you guys any solutions , please do help me cuz this phone really is important and with all honestly, isn't even mine XD, I'll be waiting for an answer

Your failsafe options are contact Samsung or do a factory reset (and then potentially contact Samsung).
If you can't boot it to anything, the only real option you have is to flash firmware, which likely won't help without wiping.
Unfortunately, not booting doesn't have a whole lot of options that don't wipe data without being rooted. Even then, you'd need recovery.

I see, then I may consider giving it to samsung, as long as they won't reset it, cuz the only reason why the phone is so important is because of the data, altough, isn't there any other way to acess recovery? Cuz I had this problem with the s10 before and I fixed it somehow (a certain Bixby key combination), but this time it seems there isn't any hidden combination.

Samsung is going to reset it. It's a required first step for them to do any work on it, even if the work has nothing to do with the software. What may help find a way to recover the data is starting with how it got to this point. Did you install anything new, change any important settings, or anything else that could have been a part of the issue? If not and it is an unexplained hardware failure, the data is likely gone already.
If it's something you might have installed or changed, it's possible that putting the phone in safe mode and undoing it may solve the issue and let you boot normally.
Booting into Safe Mode:
Make sure the device is powered off (charging is ok, as long as it is not currently trying to boot)
Hold the side key to power on and continue holding until "SAMSUNG" appears and the device vibrates
Immediately release the side key and begin holding volume down until boot completes
If the device has booted into safe mode, you will see a translucent "Safe Mode" in the bottom left

twistedumbrella said:
Samsung is going to reset it. It's a required first step for them to do any work on it, even if the work has nothing to do with the software. What may help find a way to recover the data is starting with how it got to this point. Did you install anything new, change any important settings, or anything else that could have been a part of the issue? If not and it is an unexplained hardware failure, the data is likely gone already.
If it's something you might have installed or changed, it's possible that putting the phone in safe mode and undoing it may solve the issue and let you boot normally.
Booting into Safe Mode:
Make sure the device is powered off (charging is ok, as long as it is not currently trying to boot)
Hold the side key to power on and continue holding until "SAMSUNG" appears and the device vibrates
Immediately release the side key and begin holding volume down until boot completes
If the device has booted into safe mode, you will see a translucent "Safe Mode" in the bottom left
Click to expand...
Click to collapse
Well I just asked the original owner (my mother), and apparently she doesn't remember downloading anything new into it, and it just went crazy by itself, also something else I wanna note, I tried charging it and it booted into recovery all by itself, I taught it was weird but Still went and wiped the cache and then when I tried restarting it it suddenly ran out of juice once again, also, it's second display shows some weird curruption/bug or glitch-like lines. So based off of this, can you really find the origin of this problem and if there is really any hope of saving it's data XD. Thank you btw, and once again, I'll be waiting for an answer

There are hundreds of reasons it could do that, including a faulty board. Thanks to the removal of physical sdcard support, you'd need to get it to boot into something with at least adb support to pull anything off it. Stock recovery doesn't provide any ways to perform a decent backup, but it sounds like the only option that wouldn't wipe the device didn't work.

I see, alright, thanks a lot, I'll consider resetting it

It may be worth trying to flash firmware first. Go into it knowing it may reset the device or leave you needing to reset it, but it doesn't hurt to try if you run out of safer options.

Same here, same symptoms, happened in front of my wife's and eyes face. We are fairly techy and understand our way around our devices. We also noticed the device crashed then would make it all the way to the home screen launcher and before catching signal the crash would cause a restart at that point I went in and did a cash swipe rebooted right back into recovery by itself then I unplugged the cable and it was acting as if it has a dead battery but when the cable was last plugged in during a couple of crash and then restarts all the way to the home screen I know the battery was at 70 something percent. My next step is going to probably be flashed the current firmware that just released on top of it as a dirty flash and see if I can get it to boot. If not then I'm going to do a hard reset and see if that works. When plugged in it automatically starts exhibiting symptoms as if the buttons are stuck. The devices in the OtterBox and it's fairly brand new I would say mint. Not dirty or any smudges either. all I'm saying is I'm one of those type of technicians that say yeah right when people say it just happened I don't know where but this actually happened I don't know when I was able to witness it. I'll come back and let you guys know what works and what doesn't. (By the way excuse my grammar I was voice typing while driving )

ariveraiv said:
Same here, same symptoms, happened in front of my wife's and eyes face. We are fairly techy and understand our way around our devices. We also noticed the device crashed then would make it all the way to the home screen launcher and before catching signal the crash would cause a restart at that point I went in and did a cash swipe rebooted right back into recovery by itself then I unplugged the cable and it was acting as if it has a dead battery but when the cable was last plugged in during a couple of crash and then restarts all the way to the home screen I know the battery was at 70 something percent. My next step is going to probably be flashed the current firmware that just released on top of it as a dirty flash and see if I can get it to boot. If not then I'm going to do a hard reset and see if that works. When plugged in it automatically starts exhibiting symptoms as if the buttons are stuck. The devices in the OtterBox and it's fairly brand new I would say mint. Not dirty or any smudges either. all I'm saying is I'm one of those type of technicians that say yeah right when people say it just happened I don't know where but this actually happened I don't know when I was able to witness it. I'll come back and let you guys know what works and what doesn't. (By the way excuse my grammar I was voice typing while driving )
Click to expand...
Click to collapse
Hello everyone just a quick update. Once I got home I plugged the device into a Samsung fast charger and Samsung OEM USB type-c cable and realize the device booted all the way to the home screen but register the same battery level as I mentioned above. Device was working as if nothing happened to it. So I updated all the apps on the Galaxy store then updated all the apps left over from the Google Play store, I then proceeded to check for a firmware update because I know the April update just released and installed the update with no issues. Updated the apps that needed to be updated again somehow there's always something and unplug the device from the power cable. Everything was working if no issues about half hour later the device cuts off and does not want to power on. FYI I already had my wife contact T-Mobile and get a warranty replacement we only paid $5.00 so my thoughts and conclusion on what's going on something happened to the battery or it's defective. Btw we only use Samsung OEM cables and equipment at home and in the car while connected through Android auto. it's only working while being plugged in it's not charging all the way even though it's registering it's charge level while the device is on.

Motorola XT1542 Weird brick, (Please help)

Due to some finantial plot twists in my life I've been forced to dust out my old Motorola G 3rd gen and use it as my main phone. A couple of days ago I followed a guide in how to unlock the bootloader and installed Lineage OS, everything was decently smooth, except by the fact that it didn't recognize my SIM card.
So as a troubleshooting step (And since I still didn't had anything important on my phone) I decided to reload a recovery image I had made with the original ROM.
And here is where the troube started. TWRP finished the restoration of the image and I told it to reboot the phone, now it has been stuck on the "Warning Bootloader Unlocked" Warning screen for the past hour or two. When I try to turn it off I hold the power button and 10 second later the screen goes off, but a few seconds later it turns back on and goes back into the warning screen.
When I plug it into my computer it isn't recognized and for some reason it doesn't allow me to enter the Bootloader (It might be worth noting that the volume down button hasn't worked very well for some years.)
So, it's not completely unresponsive, I have a screen and it recognizes button presses to some extent, but I can't do anything with it...
Is there any way I could fix it? I'll appreciate any help. (I don't care if I have to format the phone, I just need to fix it)

martiagosantinez said:
Due to some finantial plot twists in my life I've been forced to dust out my old Motorola G 3rd gen and use it as my main phone. A couple of days ago I followed a guide in how to unlock the bootloader and installed Lineage OS, everything was decently smooth, except by the fact that it didn't recognize my SIM card.
So as a troubleshooting step (And since I still didn't had anything important on my phone) I decided to reload a recovery image I had made with the original ROM.
And here is where the troube started. TWRP finished the restoration of the image and I told it to reboot the phone, now it has been stuck on the "Warning Bootloader Unlocked" Warning screen for the past hour or two. When I try to turn it off I hold the power button and 10 second later the screen goes off, but a few seconds later it turns back on and goes back into the warning screen.
When I plug it into my computer it isn't recognized and for some reason it doesn't allow me to enter the Bootloader (It might be worth noting that the volume down button hasn't worked very well for some years.)
So, it's not completely unresponsive, I have a screen and it recognizes button presses to some extent, but I can't do anything with it...
Is there any way I could fix it? I'll appreciate any help. (I don't care if I have to format the phone, I just need to fix it)
Click to expand...
Click to collapse
So I don't know if this is helpful in anyway, but I'll wait for it to run out of battery and then I'll try to plug it into the computer again, maybe that helps in any way?

I found this reddit thread
https://www.reddit.com/r/MotoG/comments/5iz8fz
Someone had the same issue (Or a very similar one) I had, but I don't know if OP figured out a way to fix it, or if he was able to get into the bootloader.

Update, the phone ran out of battery and it's shows the low battery screen when I try to turn it on, or when I try to enter Bootloader, it's still not recognized by my PC

Samsung J7 Prime (2017) SM-G610Y Boot Looping Problem

Good day, this would be a pretty lengthy post. I'd like to describe my experience clearly since I don't know what I possibly skipped over as I am very positive that my efforts have been correct basing on prior XDA forums. I even made this account solely for posting this to ask for help formally along with archiving this problem I'm having for those having a similar experience.
I've been working on my mom's phone this whole day and there are fruits of my current hard work. I am immensely stressed and despairing with my situation.
The Problems
Infinite boot looping
Can't access the recovery menu (power, volume+, even with home button)
Can access the ODIN / Download menu
Can't turn off either (holding down power button has no effect)
What I've done so far
I read XDA forums about similar experiences. Can't really access the recovery menu so I've factory reset.
We live in the Philippines and this phone is open line, so I went with those requirements while searching stock ROMs.
I downloaded the stock ROMs of the phone model via galaxyfirmware.com which was positively shared in the forums.
Did trial and error with it and eventually got the right one. I have formed a level of understanding with the filenames and eventually knew which is compatible.
Used Odin3 to Flash the BL, AP, CP, CSC, and even go Nand Erase and got the PIT file inside the CSC (Opened it using winrar)
The flashing is actually successful and quite fast to be honest.
The phone reboots itself and shows that it is still sadly boot looping.
Also, despite the several files used for the Flash, still can't access the Recovery Menu.
With that said, I have also tried using Frija which automatically downloaded the stock ROMs based on the model name and CSC type. Placed it in ODIN again and no changes, still boot looping.
I also can't put the TWRP I got here because of the FRP Lock, which can be undone via the settings of the phone. But since it's boot looping, I can't really do much about installing a custom ROM.
Currently, my dad is letting the phone drain its battery, since we can't really turn it off. The phone model doesn't have easily detachable battery as well, unlike the old days.
For some additional notes of what happened prior to this incident
My mom was just playing with her phone as her usual days went on. That day, she installed a new hotel-themed game she saw on Google Play. As I assume that it's from the app itself and not on some shady apk website, I saw no problem with it and didn't think it was the cause of all this. I went with the theory anyway and with the flashing, using CSC instead of HOME_CSC (which apparently saves the existing data on the phone from wiping), and even used the Nand Erase in the end. It's still stuck at boot looping.
I would appreciate anyone's reply to this discussion. I am truly desperate to fix this for my mom. If worse comes to it, I'll save money to buy her a brand-new phone.

You don't have a working android, so you won't remove the RFP. TWRP will not help you with this.
The symptoms you describe indicate a defective power button.
You manage to enter download mode because the power button is constantly on.
Because of the constantly on power button, you have no way to turn off the phone. Bootloop can also be the result of a constantly on power button.
To sum up, you should fix the power button.
1. The easiest way is to blow with compressed air and press the edge of the button with your fingernail, rapidly releasing the pressure. Perhaps the fuzz has blocked the button. Unfortunately, this rarely works.
2. Take the phone to a local service center.

Hi ze7zez! Me and my dad greatly appreciates your insight and we were definitely enlightened on this angle.
We didn't really think that the power button was stucked pressed on because you can clicking sounds when you press on it. The phone never had problems with the buttons along the 6 years it accompanied us, perhaps its age does start to show.
We're going to look into it tomorrow. Thank you very much! You gave us the idea that it may be shorted inside or some sort. Thank you again!

A bit of update.
I pried open only the back case of the phone so I can see and clean up the power button. I used tools specifically for it and made no damage on the phone during the process.
We couldn't really see anything busted from there. The buttons on the circuit still do the neat clicking sounds on it. Battery still looks the same.
Testing out the theory that the power button was stuck on:
We tried to only press and hold the volume down and power button. It didn't go to the download menu. We needed to press down all three together to access it. It is confusing since we believe it would be a power button issue too, as the phone instantly turns on by itself when plugged to a power source (it's completely drained by now and we still can't turn it off manually)
Perhaps it's an internal circuit problem with the power button? It's confusing with the fact we still have to press on it to access the ODIN menu if it was like "on" the entire time it's looping.
Thank you in advance for further insights.

Try restarting by pressing home, power and volume up all at once.

Hi Pranav2406,
I have tried that as well in order to access the Recovery menu to factory reset, but no luck.
We have given up on repairing the phone and went out yesterday to buy a new one in a rush.
We will still send this broken phone to a repairman.
If he fixes it, I'd ask what he did on it so I can post an update on this problem as well.
It's better to let the expert troubleshoot it.
I do suspect the problem in the phone's hardware. I'm pretty confident with all the stock ROM flashing I've done so it's not a software problem.
Thank again for everyone's insights.
Perhaps this case is too much for an amateur to fix.