Related
Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.
This is the hspa version.
svntsvn said:
Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.
Click to expand...
Click to collapse
The android icon you're referring to sounds like the stock recovery. In order to flash a ROM (even stock) from recovery mode, you'll need to load a custom recovery. This requires the device to be unlocked.
Not very often a stock setup needs to be restored. Generally, with the stock setup, only the /data partition is wiped (revert to factory default) and the issues are cleared. Not sure why a stock setup would need to be restore.
If you're still going to pursue reloading the system, without access to the normal android mode, the best route will be using fastboot. This can be done on a mac and the fastboot commands should be the same.
Hope that helps get a start!
This happened me earlier. I was able to factory reset it, which, unfortunately really annoyed me because I hadn't saved a backup..
Before the "Google" logo shows up, press and hold the power button and the volume up and down buttons.
Then go into recovery mode using the volume buttons.
When it reboots, you get that Droid with the hazard sign (which I know you're at, but just for the sake of others who need help) all you have to do is hold down the power button and WHILE it's held, press the volume up or down button and move to "Factory Reset". When you hold down the power button and press the volume rocker, a little menu will appear. It should only take a few minutes then.
Hope this helps. Apparently this is a WiFi issue. I'll definitely be keeping backups as of now..
I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.
svntsvn said:
I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.
Click to expand...
Click to collapse
I had the exact same problem happen last night with UI crashing and then the getting stuck at the boot animation. I was desperately searching online, looking to find a solution that didn't involve rebooting to factory setting and came across this post and did exactly what you did and it WORKED, very strange, I really wanna know what caused that!!!!
I've had the same problem with my Galaxy Nexus. I received it on December 21st, with stock 4.0.1 build. No root or unlock attempt at any time. On January 2nd I experienced this problems (UI process crash, screen not responding, reboot and stuck in boot animation).
The only solution was to do a factory reset and start over.
On January 10th same problem, same solution. Second factory reset.
I got the 4.0.2 OTA just two days after that. I thought that would resolve the problem. The phone seemed more stable, with less FC's and no trace of the UI crash. Indeed it lasted long...
Exactly until January 24th when I picked up the phone and seemed in the sleep of dead. Removed the battery, restarted the phone... and stuck in the boot animation.
Do you have any advice? Should I return the phone? Aside from those specific problems I am quite happy with the SGN and Android 4 in general. And I use it quite a lot (I have a very long train commute) without other problems.
Again...
It happened again!!
I don't know what to do anymore, this is not a usable phone when I have to reinstall and reconfigure every 3 weeks.
I may have found the problem
Well, not me exactly, but this bug report seems to fit the problem and the charging workaround. Seems to be a problem the file used to store the battery stats and draw the charge graph.
It also fits my usage (I try not to charge it up until 100%).
I can't post links to the forum, the issue is id number 24518 which you can find in code.google.com/p/android/
After an entirely random error saying my phone is somehow Encrypted, I went ahead and did a factory reset which didn't help. The phone was still booting into the same screen asking me for a code to Decrypt the data. So after some "quick" reading on these forums I've decided to RUU to stock. But the file I've chosen, even though it matched my version it was a Firmware, while the phone was S-ON. The device had never been Rooted or tampered with previously.
So now the phone does not boot at all. I've tried every button combination, but nothing seems to work. If I plug in the phone to charge the orange light flashes, endlessly. Even after I've left the device to charge for 6hours, the orange light still flashes.
When I plug in the phone to my PC, all I get it seems is this new device: QHSUSB_BULK, which shows with an exclamation mark next to it. I've read similar threads for different phones where they've unbricked devices while they were in this mode, is that even possible? I can hear Windows recognizing a device was plugged in, and if I press Power+VolumeUP, it will disconnect the phone and reconnect it, at least based on the sounds Windows is playing. The screen is Black at all times.
How badly have I bricked this device and is there any hope to revive it? Thanks to everyone who chimes in on this.
arrayy said:
After an entirely random error saying my phone is somehow Encrypted, I went ahead and did a factory reset which didn't help. The phone was still booting into the same screen asking me for a code to Decrypt the data. So after some "quick" reading on these forums I've decided to RUU to stock. But the file I've chosen, even though it matched my version it was a Firmware, while the phone was S-ON.
Click to expand...
Click to collapse
Most likely it's a soft break. So you can fix it. First of all get yourself a working usb cable. Your's maybe broken.
Your phone's data partition had been encrypted. It never boots up completely without lux password. You could've format the data partition with a custom recovery such as TWRP. Instead you tried the reflash firmware but obviously it didn't finish and failed. All you need is reflash again but doing it correct way so it can finish. Your old data is gone atm. You will have factory reset phone at the end. Before giving you any instructions, you need to answer a few questions so anyone can help.
Have you ever updated your phone to marshmallow which is android 6? If no: You can recover it with voidzero's wonderful answer titled back to stock. Follow that exactly. If yes you can't flash old versions since they are using different bootloaders. Also you will have to reflash it manually. It's long and difficult for anyone who is new. If you don't know if it was updated. Just boot into bootloader then Fastboot mode, connect usb. Then use htc's Fastboot. Run htc_fastboot getvar all command. Paste output here.
Thanks for replying, risyasin.
Yes, I did update to Android 6. The problem is I'm not able to boot into the bootloader using the Power+VolumeUP keys, or any other combination.
Instead of flashing the RUU, or maybe turning to S-OFF(I still don't know if this would've made a difference), I flashed a firmware, one that matched my version. This is the exact filename: 0PKVIM[email protected]60201_20.05_018_F_release_479349_combined_signed
I've renamed it to 0PKVIMG.zip and booted using the Power+VolumeUP keys. For whatever reason, everything went OK, no errors whatsoever. In the end it told me to press Power to reboot the phone. I've pressed Power and nothing happened since.
If anyone can help me figure this out, I'd be forever grateful.
arrayy said:
Thanks for replying, risyasin.
Yes, I did update to Android 6. The problem is I'm not able to boot into the bootloader
Click to expand...
Click to collapse
That is a big problem. I assume you never tried to go S-OFF (which is dangereous). While phone was S-ON. You could always boot into bootloader. That's one of the purpose of staying S-ON.
Combination is Power + Volume down. But if your phone is up & somehow can not continue to boot. eg: stuck at reading system or kernel etc. You can do a hard reset which is pressing Volume up + volume down + power for at least 15 seconds. phone will shut down. then you can try bootlader combination. Make sure it's has power on with light at screen edges you must look at carefully. After trying this if you still can not see bootloader. That's a problem beyond my experiences, so I don't have any idea to fix it.
I have never tried the firmware you have used. Maybe that firmware is not usable, broken or even dangerous.
We need to confirm that here. if anyone else tried and brick their phone with that.
tl;dr summary:
- Replaced screen, worked for 1 week
- Randomly switches between hard-brick no response, and soft-brick boot loop
- Boot loops on loading TWRP as well as OS
- Running latest 7.0.0 NBD90W
- Phone is H790 variant
- Flashed Android 7 in the bootloader, not through OTA. This was as soon as Nougat came out, and it worked great for weeks.
- Bootloader unlocked (for temp-booting twrp only, "fastboot boot twrp.img" otherwise kept stock)
- Phone NEVER rooted
- No charging indicator when plugged in
- Battery bent during previous removal, maybe causing issues a week later?
Replaced screen with genuine LG front frame assembly after a running accident cracked my screen/digitizer. Phone worked fine for about a week, then randomly shut off and went into a boot loop.
Now it randomly switches between a boot loop and a hard brick. When it's acting like a hard brick, sometimes it goes back into boot loop temporarily if I disconnect and reconnect the battery. It eventually returns to hard brick.
Hard brick mode:
-- Doesn't respond to any power button presses. Does not indicate charging when plugged in. Entirely unresponsive.
Soft brick mode:
-- Normal boot: normally gets to Google logo and restarts. Rarely makes it to the flashing dot animation. Twice has booted into Android, past the lock screen, and works perfectly for ~10-15 seconds before rebooting.
-- Boot into bootloader: On occasion will reboot itself from bootloader, but rare. Usually works correctly including all adb commands.
-- Boot into stock recovery: Same as bootloader, usually works, sometimes reboots.
-- Boot into TWRP 3.0.2-2 bullhead: boots for a few seconds and then locks up. Has never made it through decryption - will either a) freeze and reboot right after I draw my pattern, throwing an error that it could not mount storage right before restarting or b) freeze and reboot anyway if I take too long before drawing my pattern. It seems to be more time-based than a function of anything I do.
Things I've tried:
Since my bootloader is unlocked, I've re-flashed these partitions with no fix:
bootloader.img
boot.img
recovery.img (stock)
radio.img
vendor.img
I've cleared cache through stock recovery, can't remember if I tried flashing cache.img
I have yet to flash system.img or userdata.img as I have a few files I'm trying to recover... The fact that I can't boot into TWRP, and the sporadic hard-brick behavior, doesn't give me enough confidence that wiping my data will help.
Phone tends to live in hard-brick mode unless I disconnect and reconnect the battery, then it sometimes goes into soft-brick boot loop for a while before once again hard-bricking itself. When hard bricked, no charging indicator appears when plugged in. When soft-bricked and turned off, will sometimes display the battery status after short-tapping the power button. No change when plugged in except only once it displayed the battery with lightning bolt icon for about 2 minutes, before returning to the icon without the lightning bolt.
My best guess is that I damaged the battery during removal.
- The adhesive was really strong, and while I didn't puncture the case, I did bend it somewhere between 30-45 degrees in the process. If I damaged the Li-Po foil, would that make sense for the phone to work, only to go belly-up a week later? I ordered an OEM LG battery for $13 because it's worth a shot at that price point. Arriving next week.
- The reboots sound in-line with it crashing when it tries to draw too much power? Bootloader and stock recovery usually run okay and I assume have a low power draw. The OS and TWRP probably draw more power and that's where it fails? The reboots seem to be more time-dependent than depending on anything in particular that I do, such as rebooting before OR after drawing my pattern on TWRP. And that it sometimes boots into full Android for a few seconds implies to me that the OS is working on at least some level.
Does anyone have any better ideas for when the new battery inevitably doesn't fix it, or things to try in the meantime? Could the common Nexus 5X boot loop under Nougat be causing issues booting into TWRP too? It feels hardware-related to me. I took it all apart and looked for loose/oxidized/bent contacts on all the connections but couldn't spot anything.
My Pixel isn't arriving until Nov 23-25, and to make matters worse I switched to Google Fi 3 days ago and I have no compatible phones to use in the meantime. Oops, lesson learned.
Hoping for some help or alternatives to fix my fiancee's Pixel XL. Last night the phone just kept flashing the 'G' logo on for 10 seconds, off for 10 seconds. She said the phone was close to dying before it happened, and I imagine it probably ended up draining the battery afterwards with the constant bootloop. Plugged it in all night but the charging screen didn't come up and would just stay in the bootloop. I could get it into the boot loader (power button and volume down), but it wouldn't go into recovery mode and instead would go right back to the boot loop.
So I tried a battery pack to charge it and it still didn't show charging, but I was able to get it into recovery mode eventually, but still boot loop afterwards. At one point, after leaving it on boot loader menu while attempting to charge, it eventually just tried to start itself and made its way to the second Google splash screen after the main G logo. Looked like it froze there though and I couldn't get it to that point again.
On my way to work this morning I tried plugging it into my car's USB port after powering off from the boot loader, and this time I kept flashing that it was charging (looked like it was 3/4 charged but not sure how accurate that is). So I got into recovery again and tried 3 factory resets consecutively. Still bootloop after attempting a startup afterwards. There was a similar issue a couple weeks ago where it looked like it was stuck in a bootloop, but it turned out the phone actually was dead that time and the charger wasn't working. Once we switched chargers it booted right up.
Any other suggestions or possibilities? I don't have much troubleshooting experience otherwise. Phone is fully stock, Google Fi. Any other info I can provide please let me know!
well, i'm not sure if it makes a difference, but now for some reason i can't get into recovery mode again. just goes into the boot loop. It also goes into the boot loop as soon as I plug the phone in to charge.
cgibsong002 said:
well, i'm not sure if it makes a difference, but now for some reason i can't get into recovery mode again. just goes into the boot loop. It also goes into the boot loop as soon as I plug the phone in to charge.
Click to expand...
Click to collapse
I assume you can't get into the bootloader using power and volume down buttons?
I have always been about to get into the boot loader. Actually i can get into recovery again as well. Seems if i let it sit for a while it'll go to recovery again. Maybe heat related.
My OG Pixel did the same thing to me one morning. I tried everything to revive my pixel but nothing worked. I did some digging and it turns out there is an issue with the storage on the phone. It's just a old fancy paper weight.
cgibsong002 said:
I have always been about to get into the boot loader. Actually i can get into recovery again as well. Seems if i let it sit for a while it'll go to recovery again. Maybe heat related.
Click to expand...
Click to collapse
If you can get into recovery, have you tried to sideload a full ota.zip (not an update)?
mozhno said:
If you can get into recovery, have you tried to sideload a full ota.zip (not an update)?
Click to expand...
Click to collapse
I haven't. I see that Google has all the ota's on their site. Is there a specific one that i might want to try? The same one? Go back a few? Will i even be able to sideload if my phone is fully stock?
Edit: sideload adb successfully but no change. I loaded the 6-5 ota which was what i already had.
cgibsong002 said:
I haven't. I see that Google has all the ota's on their site. Is there a specific one that i might want to try? The same one? Go back a few? Will i even be able to sideload if my phone is fully stock?
Edit: sideload adb successfully but no change. I loaded the 6-5 ota which was what i already had.
Click to expand...
Click to collapse
Sounds as if it's time to just try stuff and see what sticks. Regarding using an ota, it works if you are stock, and I sideload it even if I have installed majisk or installed another kernel. It typically works for me with fewer chances of blowing things up than flashing a stock image. Regarding what to try next, you may have already gone into recovery to check the install function to see if your storage still appears and try to flash anything that worked in the past; if you have a backup in twrp you could try to restore it; you could wipe cache and dahlvik; or even sideload an earlier ota version that worked. Since the 6-5 ota did not work nothing really jumps out to me as obvious. One final caveat, I once had to reboot a sideloaded ota a second time before my pixel booted properly. If I think of something else I'll post again.
I took it to ubreakifix and they told me that this is indeed a known issue with pixel xl's that they all suffered from a faulty motherboard and that is indeed the cause here. Said he thought there was actually a class action about it so I'll have to look into it. Really pisses me off that Google repeatedly told me it's not a known issue when their authorized repair center says it is.
Anyway i have a warranty with Upsie that I'm hoping to get this replaced with. We'll see.
cgibsong002 said:
I took it to ubreakifix and they told me that this is indeed a known issue with pixel xl's that they all suffered from a faulty motherboard and that is indeed the cause here. Said he thought there was actually a class action about it so I'll have to look into it. Really pisses me off that Google repeatedly told me it's not a known issue when their authorized repair center says it is.
Anyway i have a warranty with Upsie that I'm hoping to get this replaced with. We'll see.
Click to expand...
Click to collapse
Good luck
I'm assuming you tried booting into twrp recovery, going to reboot, and picked slot A ( or B if already in A) to reboot to and then rebooted system? A lot of the times simply switching slots from recovery and then rebooting is the fix. At least for me.
手机早期经历的情况得说明一下。root没有？Twrp是谁的？
Also, for anyone else having this issue, try rebooting into the bootloader. Connect to PC, and try fastboot --set-active=a
If this doesn't work, try booting back into your recovery image using fastboot boot *whatever you named your TWRP recovery image* and then flashing your twrp.zip again in recovery, and when rebooting if you're in slot B choose slot A in recovery to boot into.
Also keep in mind in Windows 10, it uses Powershell, so commands have to be typed in .\fastboot not just fastboot or it won't take it.
So I updated to Android 11 on Tuesday, and all seemed fine. Last night my phone was trying to install an app, and seemed to freeze.
After a few minutes, I forced it to shut-down (power + vol down) and it started to reboot. It got to the G logo with the small bottom bar animation for a number of minutes and eventually kicked back into Recovery mode.
I decided to try rebooting, and it started to reboot, got to the Google logo (the full word, not the "G"), and then kicked back into rebooting.
The phone now constantly reboots and even if I get into fastboot mode, it only stays in fastboot until I hit a key (vol up/down or power) and it then reboots into constant bootloops described above.
If I don't push a button on fastboot mode, it will just start booting anyways after about 3-5 seconds.
Does anybody know of what I could do? Not sure if replacing the battery would help (e.g. a power issue) or if it may be a corruption of the flash memory and that the system and underlying partitions are corrupt leading to nothing I could do to repair the phone.
I have really enjoyed this phone, but I am afraid that this phone is all-but-dead and unusable.
Any assistance is greatly appreciated.
Cheers,
B.D.
You can try flashing the stock rom from recovery or from fastboot.
Had something similar on an og Pixel... Turned out to be a broken power switch.
I had a weird issue last week. Phone would freeze after a couple of minutes and would reboot. It would also boot loop while connected for charging (wireless and corded.). The battery would not charge. I would shut down the phone and when I plugged in the charger, it would boot loop. The battery finally discharged to 0% and shut off. I plugged the charger in and it remained off. I let it charge to 100% and it's been working for the past week without issue. I'm not sure what happened.
I would suggest letting the battery drain to 0% and go from there. HTH
I updated my 3XL to Android 11 two days ago and since then I have caught it rebooting at seemingly random times, though only when it is on the wireless charger. I guess it's back to Android 10 for now. Hopefully reverting a Pixel is as easy as it was on the Nexus. Thanks Google.
BostonDan said:
So I updated to Android 11 on Tuesday, and all seemed fine. Last night my phone was trying to install an app, and seemed to freeze.
After a few minutes, I forced it to shut-down (power + vol down) and it started to reboot. It got to the G logo with the small bottom bar animation for a number of minutes and eventually kicked back into Recovery mode.
I decided to try rebooting, and it started to reboot, got to the Google logo (the full word, not the "G"), and then kicked back into rebooting.
The phone now constantly reboots and even if I get into fastboot mode, it only stays in fastboot until I hit a key (vol up/down or power) and it then reboots into constant bootloops described above.
If I don't push a button on fastboot mode, it will just start booting anyways after about 3-5 seconds.
Does anybody know of what I could do? Not sure if replacing the battery would help (e.g. a power issue) or if it may be a corruption of the flash memory and that the system and underlying partitions are corrupt leading to nothing I could do to repair the phone.
I have really enjoyed this phone, but I am afraid that this phone is all-but-dead and unusable.
Any assistance is greatly appreciated.
Cheers,
B.D.
Click to expand...
Click to collapse
Are you familiar with how to use commands in platform-tools to flash stock images? How did you upgrade? OTA? Are you rooted? Is it unlocked or Verizon variant? If unlocked, do you know how to unlock the bootloader?
jjlane86 said:
Are you familiar with how to use commands in platform-tools to flash stock images? How did you upgrade? OTA? Are you rooted? Is it unlocked or Verizon variant? If unlocked, do you know how to unlock the bootloader?
Click to expand...
Click to collapse
I am proficient in using the bootloader. Phone has been bootloader unlocked since day one.
I upgraded to Android 11 with ota and all was good for a day (rooted with Magisk canary). Then the phone started acting up, first not booting system and then bootlooping.
I can get into the bootloader (fastboot) but only for maximum 3-5 seconds before the phone reboots, or if I hit any button (vol up/down) the phone reboots. Also, if connected to my computer the USB does not recognize fastboot anymore (before it reboots anyways)
I think it's dead, Jim.
Cheers,
B.D.