Hello, I would like to talk about my Google Pixel 32GB (8.1) that bootloops. Here are the things I know about it:
1. I bought it a while ago off eBay saying it was a bootloop problem. It sounded like a software problem, so I thought, I could fix this. Turns out I was wrong.
2. I can get it into the bootloader screen
3. It occasionally boots up but then freezes and starts looping again. It normally turns on whenever I turn it off for an extended amount of time. When it did turn on the first time, the first thing I did was turn on OEM unlocking but it says "unavailable to carrier locked devices".
4. Also whenever I leave it off for a while, I can get it into recovery mode.
5. I've tried factory resetting the phone but no hope
6. I can't put a recovery OTA on it because Android Pie is waiting to be downloaded. If I try to download that, it takes too long and the phone loops again
I would really appreciate some help with this and thank you in advance for helping me with it. :good:
Related
The unit has been used for about 2 months and remains quite new. It was quite stable before. Yesterday night, about half an hour after plugged in for charging and with WiFi Hotspot turned on for sharing 3G data to another netbook, the unit suddenly rebooted itself. It then stopped at the start-up screen and remained there for several minutes. I kept holding the power button for a few seconds to turn it off but it then automatically reboot itself afterwards, and stopped at the start-up screen again. It means that even complete turning off is not possible.
Trying to enter into recovery mode showed the following few lines:
# MANUAL MODE #
-- Updating application...
Copying Common Apks.
Click to expand...
Click to collapse
and then it automatically rebooted again. It means that it can't enter into recovery mode normally.
It was possible to enter into download mode. And it was the first time this machine went into download mode. I run Odin Downloader and flashed the official stock ROM. After showing "Pass", the device rebooted itself. Unfortunately, it still stopped at the start-up screen, just showing "Samsung Galaxy Tab 7.0 plus". It is really troubesome. I have experience playing several Android devices before and it is the first time I face such troublesome problem.
The device is an official product. The biggest problem is that the original purchase invoice was lost and most likely that I couldn't get official support, repair service or replacement.
May I ask if anyone would kindly provide me some help or advice. Thanks!
Instead of going into download mode go into recovery mode and see if there are any errors. Your scenario is sounding very similar to the one I had in the past.
I just ran into a nasty snag at boot logo as well. nandroid, stock kernel and factory reset were no help. Try Odin back to Stock, it still may not get past boot logo, hold vol up and power to get into recovery and factory reset. Hope it works for you.
Unfortunately I was unable to get into recovery mode even after odin flashing stock ROM.
It rebooted itself a few seconds after displaying some lines of text. I can't see the normal recovery menu.
My Nexus 5 seems to get stuck at the update screen (the standing green android with the spinning polyhedron) after flashing to stock(+unroot) with softbrick/bootloop checked. The flash completed without error. I've left it at this screen for over an hour and not only does it not progress it doesn't even get to the progress bar at the bottom.
This afternoon my (unrooted, bootlocked, stock) N5 turned itself off 3 times while on the charger. Powered back on and then would find it turned off 20 or so minutes later when I checked it again. After the third time it booted to the "Google" screen and would go no further. I tried a hard reset but it gave an error. So I plugged it into my laptop and fired up Wug's NRT, unlocked the bootloader (at which point it got stuck at the same update screen described above for around an hour). I held power till it went off, booted back into bootloader (which showed as unlocked) and performed the flash to stock(+unroot) with softbrick/bootloop checked and ended up at the update animation again. Any thoughts other than RMA?
****Edit: Finally got the phone to boot after fastboot booting twrp. Was able to to wipe the phone (after multiple attemps blocked by can not mount storage/cache/etc/etc errors). Flashed 4.4 and the phone now boots to android BUT radio is non-functional (no signal despite being in my normal coverage area), any attempt to add an APN causes a hard reboot (had to go through all the setup screens again). Additionally, the phone won't turn off, even hard power downs (holding the button for 30 secs) lead to an immediate reboot. Still RMAing but I was able to relock the bootloader.
You really shouldn't RMA a phone after messing it up yourself by using a toolkit when you didn't know what you were doing.
Flash the factory images manually. That should get your phone up and running again.
Chromium_ said:
You really shouldn't RMA a phone after messing it up yourself by using a toolkit when you didn't know what you were doing.
Flash the factory images manually. That should get your phone up and running again.
Click to expand...
Click to collapse
Performed a manual flash with the exact same results. There is apparently something wrong with the hardware (which may explain why it was turning itself off and then wouldn't boot past the google logo.
gallahad2000 said:
Performed a manual flash with the exact same results. There is apparently something wrong with the hardware (which may explain why it was turning itself off and then wouldn't boot past the google logo.
Click to expand...
Click to collapse
Yep, I would agree.
I've had some previous experience with custom roms on my old Nexus 6P and thought I would try the same for my mate 9. Unfortunately I've discovered the Mate 9 is not as easy to install custom roms as I thought.
I've tried several things throughout the day and I feel I've accidently overwritten things I shouldn't have but can't remember everything I've done.
It is an Optus branded phone so I believe at the start of the day I had some version of L09C34. I currently have an unlocked boot loader and TWRP installed and would like to flash back to the stock firmware, but seem to be unable to do so. The boot loader is unlocked and when I try flashing extracted parts from fastboot, the phone will reboot, reboot again and sit at erecovery. Unfortunately while I can connect to wifi, no packages are found for recovery.
Additionally I now get this lovely colourful screen in lieu of the logo on initial boot.
Any help would be appreciated.
Okay, so I've managed to unbrick it and install a version of L09C432 and get it working again - thank you to various threads on XDA. I think what I noticed was that someone else had tried the C432 firmware on a C33 model and it worked. Without being able to get hold of the C34 firmware, I tried to flash nougat originally and it worked.
This morning, I've noticed I still have an issue where the touchscreen won't work when the phone is cold (i.e I can't click anything and can't turn alarms off). If I reboot the phone to recovery it's fine, so it leads me to believe its an OS thing. Also, if I give it a few minutes in my pocket, or holding my palm on the screen it then responds. This is the issue I tried to resolve by resetting and trying a different rom but seems I haven't been successful.
Finally, when I first turn the phone on and the screen lights up I see a green background with one blue and one red box. Any ideas what I have messed up there and how to fix it? I'm not too concerned, but it would be a nicety.
Just providing updates in case anyone comes a long with similar issues.
I have now fixed the strange coloured screen on initial power on. I've found the oeminfo for the C432 firmware on another XDA thread and took a backup of what was currently there, restored the C432 version and rebooted. I was presented with the eRecovery and no TWRP. Quick check in fastboot mode showed the phone relocked. I unlocked it again and it booted no issues, however was unsure if the custom rom was still installed as I was presented with the option of an OTA update. Initially my sim card was not recognised, so I had to remove and reinstall it but so far so good.
I've just reflashed my custom rom and will see how I go.
The only potential issue I have outstanding is my touchscreen not working either first thing in the morning, or when the phone is cold - i.e I've gone to the gym and left it sitting in the locker for 2 hours and I can't use the touchscreen when I come back. I can unlock it fine with the finger print reader and the phsyical buttons respond but touches on the screen won't. If the phone is left alone for a few minutes the screen shuts off and turns back on approx every 5 seconds until it becomes responsive. Has anyone seen anything like this before? My googling hasn't lead me to anything helpful.
Recently had issues with my G7 Power and it seems to be soft-bricked. I was using an app and the app in question usually has the occasional stutter but then things resume to normal a second later. This is what happened yet this time the phone froze and was completely unresponsive. I held the power button down, turned it off and back on and it seemed fine but for whatever reason it got stuck on the Verizon loading screen which never happens. Turned it off and on again and it got stuck on the Moto animation so I held the power button down again. The phone shut off and refused to turn on again.
Eventually I ended up getting into fast boot (initially tried getting into fast boot many times with no success, no idea why it suddenly worked that time) and reset the phone through there and it would still get stuck on the Verizon loading screen. Kept turning the phone off and returning it to fast boot to repeat the process which was probably a stupid mistake on my part as the phone proceeded to shut off like expected but this time I couldn't get into fast boot anymore at all, even when keeping it on the charger that came with the phone.
LMSA was looking like the perfect solution but my PC isn't recognizing the phone as a drive so I don't think any sort of software made for instances like this are going to work unless there's something I'm doing wrong here. I can't get into the phone to enable USB debugging either.
Any recommendations as to what I should do? It's looking like sending it back to get it fixed is my only option here. Never had any issues with the phone until now.
Re-flash Stock ROM.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP>
jwoegerbauer said:
Re-flash Stock ROM.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP>
Click to expand...
Click to collapse
My PC won't recognize the phone at all, would this still work? Would it also completely wipe the device's memory?
Hello
My phone has a strange problem.
My phone bootloader is locked. Developer option is also disabled. But in the last few days, when the charge on my phone was low (about 4-5%), the phone automatically rebooted.
This happened a few more times, but the last time the phone did not boot.
After passing the Poco logo, the full miui logo animation is played and stays on for about 20-30 seconds. Then reboot. Of course, I have to say that the sound of the animation is incomplete.
I tried to boot the phone with manual reboot or through recovery and safe mode, but I did not succeed.
Unfortunately, I have information in my phone that I did not back up and I need it. Can you suggest a way?
Thank you for your time and attention.
Respect.
Well you shouldn't be running it until low battery shutdown, just not a good practice.
Make sure the battery is good and charging...
If you can't get it to boot the outlook for data recovery is bleak.
I am not familiar with Xiaomi devices; in this situation I would generally recommend sideloading the OTA. Perhaps manually installing a system update might help?