You've probably seen this problem before, a boot loop so that when you turn the phone on, it loops in the Google start screen. So, I did not have USB debugging enabled, but I still have an idea that might work. It might be crazy, but I would plan to COMPLETELY wipe the phone. Not just factory reset it, but wipe it completely of all traces of the old Android software, and then install a new bootloader and then ROM. The problem is, I can't find this anywhere. Ideas?
bebeto0304 said:
You've probably seen this problem before, a boot loop so that when you turn the phone on, it loops in the Google start screen. So, I did not have USB debugging enabled, but I still have an idea that might work. It might be crazy, but I would plan to COMPLETELY wipe the phone. Not just factory reset it, but wipe it completely of all traces of the old Android software, and then install a new bootloader and then ROM. The problem is, I can't find this anywhere. Ideas?
Click to expand...
Click to collapse
Problem is you still won't have debugging set to OK even custom Roms you still have to check debugging and most likely you have a hardware issue not software unfortunately
Related
So today I was minding my own business, riding the subway and listening to some music when my Galaxy Nexus decides to reboot itself. After this, it gets into a reboot loop (never getting past the Google logo).
I tried restarting the phone into fastboot mode and using the recovery option, but I end up getting the icon of the android on its back, chest plate open and a red exclamation triangle thing coming out of it. I assume this is bad
A little back story... this is the GSM/Euro Galaxy Nexus. I've been using it for close to 6 months most likely and have never rooted/unlocked it. In actuality, I don't think I've ever done anything with it out of the ordinary (like I have in the past with other android devices). In fact, I don't know if I ever even plugged it into my PC via USB before (thus no drivers, may have never set it to USB debugging enabled).
Is there anything I can do here? I tried looking at a few options (Such as the WugFresh Galaxy Nexus Root Toolkit, which has a Stock resetting option), but since I never enabled USB debugging and installed drivers before the phone decided to go and brick itself, I don't know if I'm actually stuck...
What do you think? Is there an option I have not yet considered? Or am I going to try and convince Samsung to honor my warranty or something?
Moved to Q&A, please pay attention next time where you are opening a new discussion
When you see the android on its back you have to hold vol. up + power to enter the options.
There you can wipe data and reboot to see if it will boot up again.
If that doesn't work you can try flashing the stock images. Those will require you setting up fastboot on your computer. There are many guides on how to do all of that.
Good luck.
If you can get into Fastboot mode just fine, then hook it up to your computer and flash the stock images. It'll revert you back to stock fresh and you can go from there.
We also need to teach people how to debug at basic level at least. If we just teach them how to solve it without caring about what went wrong... they've got the phone might as well learn a few things more.
And yea, i know most couldn't care less. Also, this is no brick - this word very much starts to annoy me when it is incorrectly used and that seems to be getting typical around here. Most likely wiping data/factory reset from stock recovery will allow op to boot up again.
i had the same happening to me under stock. after quite some time it went into a bootloop out of the blue.
this:
bk201doesntexist said:
Most likely wiping data/factory reset from stock recovery will allow op to boot up again.
Click to expand...
Click to collapse
solved it. my data was gone, but at least the phone worked.
then i decided to root and use a custom rom and it never ever happened again.
bk201doesntexist said:
We also need to teach people how to debug at basic level at least. If we just teach them how to solve it without caring about what went wrong... they've got the phone might as well learn a few things more.
And yea, i know most couldn't care less. Also, this is no brick - this word very much starts to annoy me when it is incorrectly used and that seems to be getting typical around here. Most likely wiping data/factory reset from stock recovery will allow op to boot up again.
Click to expand...
Click to collapse
Sure we do but as long as :
1. people start threads that suggest they bricked their phone and
2. all they had to do is Google some around to discover that what they see is a stock recovery and
3. discover what they can do to solve their problems (like most of us do to solve our problems)
I think they couldn't care less about debugging... How sad as it may be.
If you discover problems with a device that is sold as much as the GN it is highly unlikely that you were the first to have that problem. If you are: just post away.
OK,
So a friend of mine asked me to help him fix his Nexus 7 2013 FLO (WiFi only).
According to him he hasn't even unlocked the bootloader (and the info displayed while in fastboot mode confirms this). Apparently what happened, a few months ago, he downloaded an OFFICIAL KitKat OTA, clicked OK to upgrade, and since then, the tablet will not get past the screen that says Google. I can get it into fastboot mode but cannot flash anything, and when I attempted to use The Nexus Root Toolkit by WugFresh to unlock the bootloader at the very least, I can get it to display the screen that says "please use the arrow key to navigate Yes or No. Unlocking your bootloader allows you to load a custom OS, but may void your warranty, etc. etc. etc."
I tried using CMD to erase the cache and userdata and after giving it upwards of 20 minutes, during which the window (in CMD) simply said "erasing cache" and never actually made any progress whatsoever...
Any idea what (if anything) can be done?
Sound off in the comments!
Thanks a million!
Stephen Spigelman
I can't help... but am in the same boat as of last night with the 5.0 update.
Were you able to unlock the bootloader? You did say that you were able to get to the screen to unlock it. If not, i dont think much of anything can be done.
Bricked
Virgin N7 2013... No hacking... Bootloader locked... started acting weird and I attempted a system restore. It now gets stuck at the Google screen. Fastboot gets stuck at erasing userdata. I have tried multiple USB cables on Win7, OSX, and Ubuntu. Help!!!
im wondering how this happens?, I already unlocked my bootloader just cause of this.. maybe the chip just dies?
When my 2013 was stuck at the Google screen, I RMAed and they had to replace the motherboard. Unfortunately, I think this is a hardware issue.
ariesgodofwar said:
When my 2013 was stuck at the Google screen, I RMAed and they had to replace the motherboard. Unfortunately, I think this is a hardware issue.
Click to expand...
Click to collapse
Too many of us with the exact same problem after trying to to flash Lollipop. Cant believe we re all having hardware problems at the same time.
tigerdim said:
Too many of us with the exact same problem after trying to to flash Lollipop. Cant believe we re all having hardware problems at the same time.
Click to expand...
Click to collapse
Mine did not occur after flashing any firmware, but the symptom was the same in that I could get into the bootloader, attempt to flash new system images, appear as if all would be well, and then on reboot would stick at the Google screen. Not sure if folks are seeing the same thing here, but when I tried to get into Recovery from the Bootloader menu, it would reboot as if going there, but still never make it past the Google screen. It happened within 18 hours of unboxing a remanufactured N7 G2. Asus advised on the packing slip that is was a LED (Indicator) Error (whatever that is), and they they subsequently had to replace the board to fix it.
I hope it is a software issue, but not sure to tell you how to go about correcting it if you cannot flash new images via ADB or the bootloader and get it to boot successfully.
When i boot to recovery i get the TWRP startup screen but stays stuck.
Bump
bump.. any ideas?
i have the same :/
kobi_shalom said:
i have the same :/
Click to expand...
Click to collapse
Its driving me nuts.
I have found though that if I try a "Erase Boot" or similar and pull the cable after a second or so I do get a "OK" instead of being stuck with "Erasing boot..." Seems to work for Boot, Cache etc..
The problem is that when I try OEM Unlock it needs to perform 5 different erases, so pulling the cable wont work for this. I just stay stuck on "Erasing userdata...r..."
tigerdim said:
Its driving me nuts.
I have found though that if I try a "Erase Boot" or similar and pull the cable after a second or so I do get a "OK" instead of being stuck with "Erasing boot..." Seems to work for Boot, Cache etc..
The problem is that when I try OEM Unlock it needs to perform 5 different erases, so pulling the cable wont work for this. I just stay stuck on "Erasing userdata...r..."
Click to expand...
Click to collapse
So you success?
NO success because I cannot unlock the bootloader.
My mom's pixel 2 xl all of a sudden wont boot. It said cant find valid operation system. The device will not start. She said it might have updated overnight or something like that. I tried to download the factory image from google to restore the OS but it wont flash without bootloader being unlock. It odd that the phone was working and now it doesnt have an OS.
Any help is appreciated. Thanks.
sumasage said:
My mom's pixel 2 xl all of a sudden wont boot. It said cant find valid operation system. The device will not start. She said it might have updated overnight or something like that. I tried to download the factory image from google to restore the OS but it wont flash without bootloader being unlock. It odd that the phone was working and now it doesnt have an OS.
Any help is appreciated. Thanks.
Click to expand...
Click to collapse
Can you get to stock recovery for a factory reset?
It doesn't even let me get to recover. Picking recovery from the bootloader screen just make the phone restart like it try to go to recovery but then it come back to the same screen saying it can't find valid operating system.
Same happend to me on my first unit when I relocated the bootloader.
Unit resetted and then can no longer find an operating system..
Only option was to call Google and RMA it. I've seen it happen to others on the web as well
trim81 said:
Same happend to me on my first unit when I relocated the bootloader.
Unit resetted and then can no longer find an operating system..
Only option was to call Google and RMA it. I've seen it happen to others on the web as well
Click to expand...
Click to collapse
What did you say Google? Did you tell them it happened while re-locking boot loader? I am on same boat....I tried to relock bootloader and getting Can't find valid operating system
I rma the unit as well.
sumasage said:
I rma the unit as well.
Click to expand...
Click to collapse
Did they accept the RMA? Was the issue after an update or did you try to flash the update using adb or fastboot?
ram4ufriends said:
Did they accept the RMA? Was the issue after an update or did you try to flash the update using adb or fastboot?
Click to expand...
Click to collapse
Tell them exactly that. It no longer boots
As soon as I said there was no valid os the rep proceeded to rma. Seem like it a know issue so they didn't bother to transfer me to tech support.
Not sure if you want to try any of these solutions before you RMA, but here's another thread on the same "No OS ....." with several options, might be worth a try?
I ran into the same issue, however I found a solution, perhaps universal perhaps not.
When I enter fastboot mode, my phone shows (until I release the power/vol buttons) the "Start" option that is part of the boot mode. After releasing, I get the "no rom detected." So I used the script at the top of https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761. I used the script by running it WHILE pressing the Power/Vol keys.
This worked for me.
Note: I let go of power/vol after starting script.
megernic said:
I ran into the same issue, however I found a solution, perhaps universal perhaps not.
When I enter fastboot mode, my phone shows (until I release the power/vol buttons) the "Start" option that is part of the boot mode. After releasing, I get the "no rom detected." So I used the script at the top of https://forum.xda-developers.com/pi...l-deuces-bootloop-recovery-flashing-t3704761. I used the script by running it WHILE pressing the Power/Vol keys.
This worked for me.
Note: I let go of power/vol after starting script.
Click to expand...
Click to collapse
Did you check or uncheck OEM unlocking in Developer Options before doing this?
Device is fine and can be used via bluetooth mouse / keyboard - however, touchscreen went completly dead
formatted it - changed image, same result
anyone have any idea how to fix it , like a link to a video - part needed - or even a UK store
thanks
I have a similar issue.
I've had my Pixel C for around 11 Months, purchased direct from the google store in November 2017.
Last week I opened the tablet and the screen was totally unresponsive. The physical buttons were working so after several forced reboots which did not help I went for the Nuclear option and restored the device to factory defaults. This didn't work either and I was still unable to interact with the screen so logged a call with Google. I was about to invoke the warranty when suddenly the device responded again after a further reboot. I agreed with the support person that I would keep it for the time being, hoping it was just a glitch
Unfortunately the problem has recurred twice again and the only way to recover seems to be to power the device off, leave it for a "while" and power on.. not exactly scientific.
Has anyone else experienced similar issues? The device received a security update mid last week so I wonder if this is more than coincidence.
Any road, in this state the device is completely unreliable so I'll be looking to return it. I'm assuming google will not have any new replacements so I need to find an alternative android tablet
touch screen pixel c unreliable
owens2000 said:
I have a similar issue.
Has anyone else experienced similar issues? The device received a security update mid last week so I wonder if this is more than coincidence.
Any road, in this state the device is completely unreliable so I'll be looking to return it. I'm assuming google will not have any new replacements so I need to find an alternative android tablet
Click to expand...
Click to collapse
Same for me. The touchscreen is unresponsive, thought it would be hardware damaged, but did a couple of restarts, and all of a sudden I was able to type ten letters, then unresponsive again. Were you able to resolve this issue? Thanks!
after the last few updates the screen would respond less and less. This last update last night killed the screen completely. Zero response! I honestly think this is an error on their part but even if they fixed it in an update I cant get in to install the update!
I wanted to root and install a custom rom to see if that would fix it but honestly Ive been out of the loop for so long and without going into dev mode Im not sure I can at all.
tevil said:
I wanted to root and install a custom rom to see if that would fix it but honestly Ive been out of the loop for so long and without going into dev mode Im not sure I can at all.
Click to expand...
Click to collapse
I know how you feel. Same here, touchscreen became unresponsive before I could do any settings to flash anything else e.g twrp. Please share your next steps. Thanks
milgrave said:
I know how you feel. Same here, touchscreen became unresponsive before I could do any settings to flash anything else e.g twrp. Please share your next steps. Thanks
Click to expand...
Click to collapse
Im working on trying to unlock the bootloader right now. I tried the toolkit but its giving me a syntax error on trying to flash in fastboot since thats the only thing I can get to. Whats crazy is even the android recovery option is corrupt and this is a stock tablet. I really think google did this to these devices on purpose or unintentionally but has no intention on fixing them. I couldnt even run the update any since there is no way for me to get to anything.
Im looking for instructions on how to do everything from fastboot and ADB but everything is so outdated.
milgrave said:
I know how you feel. Same here, touchscreen became unresponsive before I could do any settings to flash anything else e.g twrp. Please share your next steps. Thanks
Click to expand...
Click to collapse
Hey sorry to post twice but try these. I just tried these steps and got my tablet fully wiped (do caches first) and working. Im enabling USB debugging and bootloader unlock and doing it all now. This was proven to be a google update issue to me.
Perform a master reset
https://thedroidguy.com/2019/08/how...3-xl-touchscreen-not-responding-issue-1094388
To factory reset your Google Pixel 3 XL:
Turn off your Google Pixel 3 XL.
Press and hold the Power+Volume Down buttons until bootloader mode (image of an Android with Start above it) appears, then release.
Select Recovery mode. You can use the Volume buttons to cycle through the available options and the Power button to select. The device will flash the Google start screen momentarily and then restarts in Recovery mode.
If presented with an image of a broken Android with “No Command” printed on the screen, press and hold the Power button. Press the Volume Up button once. Then release the Power button.
From the Android Recovery screen, select Wipe data/factory reset.
Select Yes. Wait for several minutes for the factory data reset process to complete.
Select Reboot system now. Allow several minutes for the factory data reset and reboot processes to complete.
Set the phone up again.
from there I just now used wugfreshs tool kit to unlock the bootloader and Im going to install TWRP and probably a custom rom to avoid updating again.
Update: def a software issue. I worked fine with this tablet for a few hours. Installed 1 app then it locked again. Opera browser. I've had my suspicions of the app for a while which is why I tested this app first. I'm using those same steps again to wipe and seeing if the touchscreen works again. I had trouble getting twrp and a room loaded due to encryption. There is apparently a decrypt file you need to install recovery and root. I can't seem to locate the correct one but wugs toolbox sees the device fine once the drivers are installed.
Ill keep this running and updated with results.
Full wipe and reset again and the screens not working again. What stinks is I once again can't get it into dev mode. I guess maybe it is a hardware issue. Sad, this thing has always been in a case and babied. I still think tho it's a bug with newer releases and the hardware in certain C's. It's beyond warranty though so what can we say to Google at this point. It's not even an old tablet and was pretty pricey. My Nexus 9 still runs perfectly!
Hi all;
I writing to ask if I can get support from you in order to recover data from my phone. This is the situation I have a Xiaomi 10T 5G device that 4 days ago suddenly reboot and get stuck on MI logo screen. I have try entering in Recovery mode and test Reboot, Safe Mode and Repair Mode with no luck. I have try also to connect it to MIPC suit but the phone get not detected, only if I put it in fastboot mode I got a message from PC suite telling that I should change to Normal mode and reconnect.
I have installed ADB drivers and my usb drivers of my device.
The issue and before sending it back for reparation I want to backup the photos, all the other data is not relevant. The phone is with the fabric ROM. Is there any way that I can recover the data??
Thanks in advance for your support.
locked bootloader? unlocked?
GizmoTheGreen said:
locked bootloader? unlocked?
Click to expand...
Click to collapse
I assume is blocked as nothing g has been done to it since the purchase.
That happened to me twice. I was pushing it to recovery, fastboot, safemode for over and hour untill it turned on. It was after update last spring. Never happened again. I cant remember what happened (i know i realized it than, but i was on a business trip and pissed, just remember that prior to that it was a problem with unlocking it/power button/sensor, maybe not the same thing as you have, since it was looping),i think it was some bug
Hi thanks for the reply but I assume is not the same case as I have try to fastboot, safe mode and repair mode a lot of times and nothing happened.
Hope to find a way to get the data from the device.
zepo88 said:
Hi thanks for the reply but I assume is not the same case as I have try to fastboot, safe mode and repair mode a lot of times and nothing happened.
Hope to find a way to get the data from the device.
Click to expand...
Click to collapse
it may be stuck in some kind of recovery loop because it crashed and think it couldn't boot. like windows does.
try turn it completely off then start it.
I'm sorry if you did not unlock before hand, there is nothing you can do.
flashing rom requires unlocked bootloader. running TWRP requires unlocked bootloader.
flashing stock rom/ recovery rom from SD will I think wipe your data
unlock bootloader will wipe your data.
if you can't get it to boot you are SoL for the data friend :/
Thanks Sir. Seen that there is no option I have wipe all the data and the phone has come back again to normal operation. Now I will try to root to use some data recovery tool to see what I can get. Any recomendations??