Hi, I have a Verizon variant of the OG Pixel, and decided to try to unlock the bootloader when I found this guide recently.
https://www.xda-developers.com/how-to-unlock-bootloader-verizon-google-pixel-xl-running-android-10/
So my phone was working properly before I did anything following this guide, it did not bootloop or had any problem whatsoever.
I'm not sure what version of the OS I had before I wipe/factory reset and sideload ota image, but when I did the first factory reset, it boot into the system and through all the setup process without any problem, so I decided to factory reset again through the settings menu.
This time I did not let it boot into system but going straight into recovery, factory reset through recovery, sideload OTA image, then factory reset again through recovery like the guide said, then reboot.
Now I got a constantly bootloop device. It stuck in Google logo for longer then I think it needs, then reboot; sometimes it get to the G logo but freezes then reboot; sometimes it couldn't finish the G logo animation and freezes there then reboot; sometimes it goes through Google logo, G logo animation, Android logo on the bottom, then freezes and reboot; the furthest it make so far was the progress bar animation under the G logo but freezes after all and reboot with no luck.
Since this is a locked devices, I could not:
-Wipe anything through fastboot
-Flash anything through fastboot
-Boot into a custom recovery image through fastboot
-Downgrade through adb sideload
-Push files through adb (I have no usable system or custom recovery, no listed adb devices in recovery, push command in adb sideload mode was not permitted.)
Things I've tried:
-Factory reset through recovery
-Sideload OTA image with different USB cables or computers (It only allows me to sideload the latest OTA image, no downgrade premitted, and the result was always success with status 0 without any error message using any combination.)
-Smashed the power button to make sure it is not the case that my power button was stucked
-Make sure it has enough power in the battery (Charge while powered off did shows the charging animation though.)
-Tap on the phone/massage the phone like some Youtube video siad
-Put it into a freezer like some article said
I think I've done anything I could. I thought it was software problem since I had a properly working device just not a long time ago, and have no problem booting into bootloader or recovery, had no error message when I sideload OTA image and factory reset, but now I begin thinking that this could be caused by faulty hardware maybe a non-wetting joint or something (similar symptom did happened on my Nexus 7 2013 which will not boot unless I apply some pressure on the back where motherboard underlies.) But before I did all these factory reset and OTA thing it has no problem at all, so I still not fully convinced that my beloved phone becomes a paperweight just because the hardware suddenly decides to loose a solder point or something.
Did this happened to you guys? Is there something I can do that I missed? Or any way I can get my phone back alive again?
Related
Hello.
Today my oneplus one was suddenly stuck in bootloop. This happened in the middle of the day when I rebooted my phone. My phone was running the latest update that came OTA (stock lollipop). Whenever I boot my phone it starts loading and suddenly a Chrome (browser) window appears for 1 second and tries to load a website. Afterwards my lock screen pop ups for 1 seconds and it starts to reboot. During the lockscreen I tried to unlock my phone as soon as possible, but it just reboots. (Any ideas about this weird problem?)
I CAN boot it in recovery mode by holding volume-down button and power button.
I CAN boot it in fastboot mode by holding volume-up button and power button.
Perhaps a factory reset will do the trick, but I don't have a backup of my files (because this happened so suddenly without me trying to flash/customize my phone). My first priority is recovering my files, because most solutions will end up in me losing every file. Unfortunately I've found little possibility to do this during the bootloop problem. I've tried to flash TWRP because it could make backups of my phone. I tried it through ADB/Fastboot, but it failed because my device is not unlocked (I can't go to settings and put my phone in developer mode and debugging mode). So I've read somewhere that unlocking my phone (bootloader?) through ADB will wipe my phone, which is exactly what I don't want.
Also I've tried this: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
But It also failed because my device was not unlocked.
Did I miss some steps somewhere or did I read something wrong?
Hopefully anybody has an idea to either fix the bootloop without losing my data, or finding a way to recover my files before wiping the phone.
Thank you.
RightHanded said:
Hello.
Today my oneplus one was suddenly stuck in bootloop. This happened in the middle of the day when I rebooted my phone. My phone was running the latest update that came OTA (stock lollipop). Whenever I boot my phone it starts loading and suddenly a Chrome (browser) window appears for 1 second and tries to load a website. Afterwards my lock screen pop ups for 1 seconds and it starts to reboot. During the lockscreen I tried to unlock my phone as soon as possible, but it just reboots. (Any ideas about this weird problem?)
I CAN boot it in recovery mode by holding volume-down button and power button.
I CAN boot it in fastboot mode by holding volume-up button and power button.
Perhaps a factory reset will do the trick, but I don't have a backup of my files (because this happened so suddenly without me trying to flash/customize my phone). My first priority is recovering my files, because most solutions will end up in me losing every file. Unfortunately I've found little possibility to do this during the bootloop problem. I've tried to flash TWRP because it could make backups of my phone. I tried it through ADB/Fastboot, but it failed because my device is not unlocked (I can't go to settings and put my phone in developer mode and debugging mode). So I've read somewhere that unlocking my phone (bootloader?) through ADB will wipe my phone, which is exactly what I don't want.
Also I've tried this: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
But It also failed because my device was not unlocked.
Did I miss some steps somewhere or did I read something wrong?
Hopefully anybody has an idea to either fix the bootloop without losing my data, or finding a way to recover my files before wiping the phone.
Thank you.
Click to expand...
Click to collapse
Unfortunately you might be stuck in a catch-22 situation here. In order to access the files you'd need to unlock the bootloader, but in doing so you'd lose those files. Without usb debugging already enabled I can't see a way out of this.
Decided to unlock the bootloader through ADB. (bye bye data)
After I've unlocked it, I've tried installing TWRP.
Some minor problems occured but I can finally boot into TWRP through volume-down button + power button.
I've decided to download the stock ROM i've found on the OPO forums.
Couldn't acces my phone through normal methods, so I had to use ADB to push the files into my phone.
Installing the file through TWRP, wiped cache/dalvik and installed super user before rebooting.
After rebooting my phone is stuck on the boot screen now. (This also happened before I installed TWRP on my phone)
I've also tried this method: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Also no succes. I'm stuck in the bootscreen where it says 'cyanogen'.
EDIT: Managed to fix it eventually through: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061 (part 2) writing the command in TWRP.
Phone finally boots normally again.
RightHanded said:
Decided to unlock the bootloader through ADB. (bye bye data)
After I've unlocked it, I've tried installing TWRP.
Some minor problems occured but I can finally boot into TWRP through volume-down button + power button.
I've decided to download the stock ROM i've found on the OPO forums.
Couldn't acces my phone through normal methods, so I had to use ADB to push the files into my phone.
Installing the file through TWRP, wiped cache/dalvik and installed super user before rebooting.
After rebooting my phone is stuck on the boot screen now. (This also happened before I installed TWRP on my phone)
I've also tried this method: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Also no succes. I'm stuck in the bootscreen where it says 'cyanogen'.
Any other way to fix this problem?
Click to expand...
Click to collapse
Exactly what did you flash? Full filename please. No errors occurred?
Heisenberg said:
Exactly what did you flash? Full filename please. No errors occurred?
Click to expand...
Click to collapse
Hopefully the stock cyanogen OS.
First I've tried to flash cyanogenmod 12 through TWRP (file is found here: https://forums.oneplus.net/threads/cm12s-yng1tas17l-installation-guide-review-change-log.304615/)
Afterwards I was still stuck in bootscreen, so I've looked for another solution.
Which made me find this guide: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
After flashing this file (probably the same thing) the problem still remained.
Eventually after multiple wipes/factory resets (which did not solve the problem) I've entered the command in TWRP and after reboot it finally worked again.
So I basically flashed my phone twice, once through TWRPS and the other through the batch file (perhaps ADB?).
Also no errors occured which stopped the flashing and commands. Did have to reinstall TWRP and reboot instantly in it by holding the volume down button multiple times. This doesnt happen anymore though.
Only had to install google apps for CM12 (gapps), for which I used TWRP in recovery mode.
Currently reinstalling most apps on my phone and no problems yet.
Hi there, having just the old casual phone crisis. I was running cyanogenmod 12.1 for awhile and decided to finally upgrade to a nougat 7.1 build.
I tried using this one https://forum.xda-developers.com/google-nexus-5/development/rom-dark-rom-t3492150 using adb sideload as I had tried a earlier one and the gapps messed up so I wasn't able to put twrp back on the phone. The rom said it had installed successfully but I wasn't able to sideload gapps, I kept getting an error status 255. I went ahead and just tried to load the rom without gapps and see if I could install it slowly through APKs. I managed to get past the initial android load and the services started up, and it got in an endless crash loop because the phone service wouldn't start. So I went to try and flash another rom and was going to delete the cache. When I went to delete the cache the phone hung for about an hour so I tried to just reset it into recovery mode again.
Now when I hold the power button and volume down key to into fastboot mode I can. I have access to the initial screen with the four options, but when I try to start recovery mode or start the phone my screen goes black, and it'll flash the dead android symbol with the error saying unable to mount cache, it only flashes it for like half a second then goes black and repeats every 10-15 seconds.
I tried holding power down, doing volume up, and letting go to do a hard factory reset but it does nothing. I also can't seem to access the adb sideloading anymore, I'm very scared that it's hard bricked, is there anything I can do at all to fix this.
Flash a new version of the recovery via fastboot. Then do a full wipe. After that install the ROM only! Reboot recovery (not system but recovery) then reflash the ROM (no wipe) and add everything else. Hope this helps you out.
The phone may not boot the ROM without wiping data if installing a 7.1 ROM over a 5.1.1 ROM.
Ok, let me explain the situation, i'll try to cover up everything i've done, So, please read my whole post first.
The situation of the device is it able to go through bootloader and recovery, it load the animation and logo, but after it the screen is blank (i can see the "android is upgrading", strange it just only 2 apps then nothing)
no sign of life in the blank state, i've tried to press the power up quite times, no sound. Blank state = slightly bright black.
First, i tried to "factory" within the bootloader. it failed, result is blank screen.
Second, i tried the wipe data/factory reset in the recovery, it throws errors.
Third, i tried to flash TWRP. The procedure is finished successfully (complete), but when i tried to boot to the recovery it enter the stock recovery.
Fourth, i tried [5.0.2][Restore to Stock][XT1033] Asia Retail [Dual Sim][4.4.2/4.4.2][LockBootloader] method, i tried the manual one to make sure everything is done supposedly. The only thing that failed is when i tried the last step, mfastboot.exe oem lock. Still then I reboot the phone, blank screen.
Fifth, i tried [HOW TO] Unbrick Moto G 2013! [Falcon, Peregrine] [Lollipop guide], but i'm stuck at step 7 where my phone only detected as "Android Android USB Device"
Another info that might needed is my bootloader is unlocked.
i've also tried the latest KK rom and L rom, and tried flashing under win7 and win10. Both result in blank screen.
Any idea before i jump intio a dead emmc conclusion?
Not sure it'll help, but maybe try updating to the latest adb/fastboot. Mfastboot isn't really necessary anymore, latest fastboot should be ok for heavy loads
just boot into recovery using following cmd
fastboot boot (ur recovery name)
without brackets it will boot ur device in recovery then wipe and install the custom ROMs.
My relatives have gotten this watch gifted to them a while back but it was in chinese so to get it to English I had to unlock bootloader and flash the room. But while doing so I by mistake flashed twrp instead of booting into it on the Recovery Partition right after unlocking bootloader and after rebooting, it was stuck in a horrible bootloop. Why is it horrible?
So the problem is, it keeps booting into twrp, fails to mount data cache and everything, shuts down and reboots again, shows a warning that it can't detect an operating system and continues to boot into the same twrp recovery and so on. When I try to boot into bootloader, it says to go to g.co/ABH and read instructions to proceed, but after holding down the button to continue to boot, it goes back to the same bootloop.
I cannot boot it into bootloader or get it into fastboot, I can't do anything in twrp and I can't boot into os (cause of course, there is none). Does anyone know how I can fix this? I've been struggling for 4 hours with this today. I'm really scared that I've completely bricked it and can't restore it .
I can see it in adb devices while it's in twrp and twrp is freaking out then shutting down, but I can't even side load a rom to even install something I can boot into.
Link me a thread if there is one where this problem gets fixed or help me please. Thank you!
So on my OnePlus Nord CE 2 Lite I was trying to root it. So I did everything extracted the boot image, patched it, flashed it and when my phone starts up it shows this boot animation and then it asks me for my pin. But when i try to input it the nothing happens the touch screen is not recognizing my touches. It can't be a hardware issue because I got the phone today and it worked like an hour ago before doing the rooting. When i boot into the pin screen and try to use adb to reboot it says: error: insufficient permissions for device. Then after a while the phone reboots so this is practically a boot loop. When i try booting up the phone it is really weird it starts the boot up process after a while and it shows the android and OnePlus booting screen then it has the red dot with the white dots going around it and then a black screen and then it either restarts again or it shows the pin screen.
I followed this guide: https://forum.xda-developers.com/t/rooting-oneplus-nord-2-ce-lite.4500297/
...download the correct firmware version for your device (EU / India), bring up fastboot, change slot, flash firmware and done ...the only thinkable reason is, you didn't wait until the phone downloaded the OTA update after unpacking it "one hour" before
I tried to wipe data but then I got stuck on a screen that requires a verification code that I obviously can't enter. And I can't reboot I have tried everything. When I hold the power button and nothing happens at all. I guess I have to wait for the battery to run out.
Okay, so now I got out of that using vol+ and power. But now I realized that the problem is that I had a different version of the boot image compared to other partitions. For example the boot image is like version 3.27 but everything else is version 2.85 (Those aren't actual versions just an example) But when I try to flash the system, vendor and product image it says: remote: '(system_a) No such partition'
or whatever image I'm trying to flash like product_a or vendor_a
Everything else works just those don't and the phone boots into recovery mode but I still can't use touch controls.
use "OppoRealme-OFP-Flash_1.0-x64_Windows" it will flash every thing.
//edit : one time it worked.
After i bricked in again. It's not working. Boot loops