So this began happening on my phone today.
https://youtu.be/gKUyPtlIHss
Can`t access recovery, adb or fastboot.
Is there any hope?
Related
Hi,
I rooted using:
OneclickrecoveryV0.4.2
Didn't backup my original stock OS, and couldn't book into an OS.
It was stuck in a loop, used OneclickrecoveryV0.4.2 to fix the loop.
Then it still did not boot into an OS. I put cm-10-20130929-NIGHTLY-tf101.
Worked fine. Wanted to try Katkiss 6.0. Did not seem to work with TWRP 2.5.
Download signed_twrp-2.8.1.1_tf101.zip. Installed it after booting into TWRP 2.5.
It looked successful and rebooted into OS fine. However, after I rebooted it, it is stuck now.
I can't boot into TWRP. It gets stuck at "booting recovery kernel image".
Help...please! I am not tech savvy at all... it took me hours researching to even get to this point...
Did I brick it?
My girlfriend will be throwing pots and pans at me if I can't fix this
Thanks in advance...
i have exactly the same problem, i used easyflasher to flash twrp and tablet says ok, but dont enter in twrp. only says "booting recovery kernel image".
anybody? U_U,
Same issue here, any help?
please help us sombody!
Anybody have a solution? My tablet is still dead in the water.
you guys didn't look hard enough, the solution was on the thread for the twrp that you were trying to use. (2.8.1.1 unofficial thread) read the post
Originally Posted by sidneyk
OK, try this. If you are still in boot loop or regular reboot takes you back to boot looping then hold volume down and power button until white text appears and then release buttons and allow OS to cold boot. That should get you back to Android. If so, then either from a terminal or through adb shell with USB connected to pc, type:
Code:
su
dd if=/dev/zero of=/dev/block/mmcblk0p3
Then reboot normally. That should get you out of boot looping. Then download this blob:
And move it to the root of /sdcard. Then, either from a terminal or adb shell type:
Code:
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot normally. You should see the blue-green flashing bar and then Android should boot. Then reboot to recovery to see if it took. I've had to do the same thing with experimental builds that didn't work out and it works like a charm.
http://forum.xda-developers.com/showthread.php?t=2434422&page=70
this solution has been there since may I just ran into this problem today and had it fixed in a few hours after finding that post, i knew it was an issue with the unofficial twrp but i was just trying to find a way to manually flash an older recovery since flashify didn't work and twrp manager didn't work, i ran into this solution by searching for the partition name of the recovery partition which is mmcblk0p4 and tf101.
Thank you for the information but that has not solved my issues. When I attempt to get to recovery the screen goes black and I can't see the menu...when I boot I get android error and the screen will go black so I can barley see the menu...I can't get the computer drivers to recognize in apx mode..basically stuck.
Hi guys,
I have a OPO bricked in a very weird way... It's booting straight to TWRP (v3.0.2-0) and nothing else. It is impossible to boot into bootloader (Vol. Up + Power), it still goes to TWRP. And when it is plugged on a computer, it's also booting straight to TWRP...
First a little recap :
- The OPO has (had) an unlocked bootloader and was updated from COS13 to Oxygen OS a while ago.
- The screen was smashed, touch screen not working anymore, and I had it replaced
- Then this problem occured (before screen change, it was booting to Android without a problem)
What I tried :
- Tried to reboot into bootloader, from TWRP via the reboot menu, nope.
- Tried to reboot into bootloader, from TWRP with "adb reboot bootloader", nope.
- Hard Reset from TWRP, nothing.
- Flash latest COS from TWRP (cm-13.1.2-ZNH2KAS3P0-bacon-signed.zip) found here, nothing.
- I wanted to try this last chance unbrick "OnePlus Recovery Tool", but for that the OPO has to be OFF while plugged on a computer, and mine automatically boots on TWRP when plugged , so it's not bricked enough to use it, f***!
Since I can't access the bootlader, I can't do a proper clean/flash
I'm really out of ideas here. I'm starting to think that the problem isn't software but hardware...
Has anyone ever encountered such a brick, or has another idea?
Thanks in advance for your help.
fully shutdown your device and then press the volume up while connecting your phone to pc and see if it can boot into fastboot or not...
just.befa said:
Hi guys,
I have a OPO bricked in a very weird way... It's booting straight to TWRP (v3.0.2-0) and nothing else. It is impossible to boot into bootloader (Vol. Up + Power), it still goes to TWRP. And when it is plugged on a computer, it's also booting straight to TWRP...
First a little recap :
- The OPO has (had) an unlocked bootloader and was updated from COS13 to Oxygen OS a while ago.
- The screen was smashed, touch screen not working anymore, and I had it replaced
- Then this problem occured (before screen change, it was booting to Android without a problem)
What I tried :
- Tried to reboot into bootloader, from TWRP via the reboot menu, nope.
- Tried to reboot into bootloader, from TWRP with "adb reboot bootloader", nope.
- Hard Reset from TWRP, nothing.
- Flash latest COS from TWRP (cm-13.1.2-ZNH2KAS3P0-bacon-signed.zip) found here, nothing.
- I wanted to try this last chance unbrick "OnePlus Recovery Tool", but for that the OPO has to be OFF while plugged on a computer, and mine automatically boots on TWRP when plugged , so it's not bricked enough to use it, f***!
Since I can't access the bootlader, I can't do a proper clean/flash
I'm really out of ideas here. I'm starting to think that the problem isn't software but hardware...
Has anyone ever encountered such a brick, or has another idea?
Thanks in advance for your help.
Click to expand...
Click to collapse
Open the back panel of your device and clean it properly with isopropyl alcohol and microfiber cloth.Also clean the power and volume buttons strips.
Reattach it correctly and then try booting into system or fastboot.
Thank you guys for your help.
So, what happened is that the volume buttons connector was dead, and that the volume down signal was "permanent", that is why the device was systematically booting in recovery mode, no matter what I tried.
Replacing it worked just fine
The phone keep bootloopis while I was charging earlier now I cant boot properly,
I can access fastboot mode but I cant access twrp bcs after the twrp logo, i reboot back to os and loop forever.
I have replaced the battery and I still cant boot into it. any ideas?
Update: I flashed twrp while connecting to a charger now it boots, but im using the old battery, will update further
I recently changed my OS from stock android to resurrection remix 2 a few months ago for better battery backup, everything was working well until today when it went into fastboot on its own and is stuck there. The buttons don't work, pressing the power button reboots to fastboot. I also tried using adb commands, specifically "fastboot reboot/ fastboot reboot bootloader " and again it reboots to fastboot, still stuck. I also found this application called reiboot for android in an article online and tried that too but to no avail. I can't shutdown the device let alone boot to twrp.
Maybe I can try flashing a new rom again but I really don't want to go through it again and lose my data, I haven't backed up anything because I had no idea this would happen.
Any insight regarding this situation would be greatly appreciated.
Thanks!
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?