Hello guys.
I apologize for making yet another "my phone is soft-bricked" thread, but I have been through at least 20-25 of the other threads, seemingly tried everything, and I can't get past my problem. Also, most of the other threads I saw are pretty old and not really active anymore. A few of the tools there can't even be downloaded anymore because the links are dead.
Anyway, here's my story.
I have a 16 GB US retail XT1032 that I bought mostly to give tech support to my parents, whom I also bought a 8GB each. Theirs, I left untouched. Mine, I unlocked bootloader and rooted right away. All went well for a long time.
My parents kept receiving OTA's and it took them all the way to Lollipop. Me being rooted, I got stuck in KitKat somewhere (I'm not 100% sure whether that was in 4.4.2 or 4.4.4), but since it wasn't my daily driver, I let it lie as stock rooted KitKat. Recently I wanted to go to Lollipop in order to keep seeing "the same things" as my parents, and I installed TWRP in preparation to flash a "stock enhanced" version of Lollipop. TWRP flashed fine but there was something funny all along: I could use ADB or a root app to boot into recovery from the ROM, but I could never manage to get the phone to go into recovery by booting into fastboot (vol down+power) and then choosing recovery. Screen would go black and recovery would never load.
So I copied a "stock" Lollipop image and booted into TWRP from the ROM and wiped everything and tried flashing the Lollipop ROM. It got stuck somewhere part way, and a few hours later there was no more progress.
Ever since then, I am stuck in fastboot. Fastboot seemingly works correctly, recently I was able to flash an OG animation to get rid of the nasty "your bootloader is unlocked" warning. I can flash recoveries (TWRP and/or CWM) without error on the phone or the computer, but when I try to then boot into recovery using the bootloader, I get stuck on the black screen and go nowhere.
As others in the various threads have commented, when I try to boot "normally", I get the boot animation and a vibration and then it gets stuck.
I have tried so many things by reading different threads I couldn't tell you anymore what all of them were. I've gotten errors about downgrading, I've gotten stuck in fastboot reason: "failed flash", I've gotten flashing errors about the size of recovery or boot or gpt. What I've never managed to do again is to boot into anything other than bootloader. No recovery and no ROM.
Could someone with a bit of experience please point me to some working links and/or when you have the time, help me look at a couple of logs or something that can help me figure out where my problem lies and how to get out of it? my daily driver phablet died a gruesome death and I wanted to go back to my trusty moto g, to no avail.
Thank you very much to whomever can help.
Ruben.
Try to reflash full stock firmware for your device according to your bootloader version. Hope it helps....
Try typing in fastboot devices
Related
Ok, so I gave my wife my old TF101 when I got the 701. I reflashed it with a fresh install of timduru's KatKiss ROM. It's been running reasonably well aside from random reboots. all of a sudden, yesterday it stopped booting up at all. It shows the normal Asus flash screen, but then when it shows the OS specific one (in this case, the weird little picture of timduru's meerkat thing...) it's just flashing random little bits of tha tpitcure all over different parts of the screen an some sort of random flickering and never going past it. I can still boot to the recovery normally, so I wiped it and tried reflashing the same ROM and ended up with the same thing. Tonight I plan to try to download the newer version of the ROM and try, but I fear I may be SOL. Any other suggestions?
Have you tried wiping everything 100% in TWRP Recovery?
Including Data etc ?
*Detection* said:
Have you tried wiping everything 100% in TWRP Recovery?
Including Data etc ?
Click to expand...
Click to collapse
Yes, I did that. Still no good. I'm pretty much screwed, aren't I?
If your TF serial number starts B6O or lower, some B7Os too, then it is SBK1, which means you can use NVFLASHable ROMs - they delete and remake every partition on the TF and reinstall stock ROM - you could try that in case the sdcard is corrupt
stuck at TWRP screen, failed to flash bootloader
Hello everyone,
Not to thread jack but I have a similar problem and instead of opening a new thread I decided to revive this one.
I have a similar problem that my TF101 has been working flawlessly for many years. It is rooted and was running 4.3 ROM. As of yesterday, it just won't boot at all. It has been stuck at the NVidia screen and just sits there. I tried to enter recovery mode by using volume(-) + power and the unit presents the TWRP logo and just loops as well by showing the TWRP screen (3 seconds) then going blank for a second then showing TWRP screen again in a cycle. I downloaded and tried Easyflasher and Brks toolkit and nothing can complete the flash. I can enter MTP mode which the computer can see the device but the manufacturer name and model are not-recognized. I can also enter APX mode but while trying to flash anything I get an error message (error, cannot flash bootloader) and the computer dings (device disconnects).
I have been trying for a day now and have run out of ideas.
Has the unit finally bit the dust? Does any one out there have any more ideas or suggestions on what to try next?
TIA for any help provided.
I need help. I've had my old TF101 for a couple of years now. I was running KatKiss 4.3 when one day, I plugged it into an old soundboard to sound test some speakers. For some reason this sent it into a bootloop (it did the same to my G2, but I got it out easily). I figured it was not a big deal since I get into bootloops all the time, but I was shocked when I booted into TWRP and the touchscreen wouldn't work! So I rebooted it over and over but it still wouldn't boot regularly and TWRP wouldn't accept touches. I reflashed TWRP through adb (which worked in TWRP) and still nothing. Then I downloaded some TF101 unbrick tool that utilized nvflash, but it kept getting errors because it was missing files. After I used that, my tablet screen seemingly wouldn't turn on! I tried EasyFlasher with sbk2 (cause mine's a b70) but that did nothing. I was about ready to give up, when I stumbled across a thread here where a guy's tablet was stuck booting into apx mode. I guessed that that might explain the screen not turning on, so I tried the solution there, which involved another nvflash tool that was designed just to flash the base boot stuff, no ROM. This worked. After this I tried EasyFlasher again (with sbk1 this time) to get the Asus stock ROM, and it seemed to work, but the tablet wouldn't finish booting (I let it boot for over a half an hour). I flashed TWRP and some custom touchscreen enabled CWM with it, but the touchscreen still wouldn't work. I flashed regular CWM with it and tried to install KatKiss, but it wouldn't boot either. I tried multiple times wiping and flashing, but the touchscreen still won't work, and no rom will boot.
So now, I have given up, and for the first time in many years of rooting, roming, flashing and wiping, I have found a problem I can't figure out on my own or through Google or previous threads here, and I'm stumped. I'm actually quite surprised its taken me so long to get here. Anyway, Thanks in advance for the help!
Folks, I have seen some threads on here so I will understand that you will probably hate me but seriously none of those did well for me. So that's why I am creating mine. As an owner of LG G2 mini I had been closely focusing on CM12 progress re lollipop that InvaderJohn was working on. There was a camera overexposure issue so I tried to use some working lib files and vendor/lib files and created a flashable file for TWRP recovery. I screwed it up as upong the flash my phone with CM12 didn't boot up. I wasn't able to get into recover thru adb so I pressed volume down and middle button and got myself into factory mode. I did factory reset and was in TWRP recovery again. Good. Then I reflashed the phone and there was an error saying that secure booting unsuccessful. I have LG Flashtools and tot file with dll for my LG D620fr on my laptop. This method I used once when getting the phone bricked and it worked and I was able to install stock 4.4.2 ROM. But this time... not sure why but the tot flash got stuck with 94% and while the phone was supposed to get restarted it didn't and the message above of the secure etc. popped up. I am able to get into my TWRP recovery (weird) but nothing else. I suspect I got my bootloader locked. Is there any way how to figure this out, please? I was trying the fastboot method but my phone is unrecognizeable. Any help is much appreciated.
enzo_cz said:
Folks, I have seen some threads on here so I will understand that you will probably hate me but seriously none of those did well for me. So that's why I am creating mine. As an owner of LG G2 mini I had been closely focusing on CM12 progress re lollipop that InvaderJohn was working on. There was a camera overexposure issue so I tried to use some working lib files and vendor/lib files and created a flashable file for TWRP recovery. I screwed it up as upong the flash my phone with CM12 didn't boot up. I wasn't able to get into recover thru adb so I pressed volume down and middle button and got myself into factory mode. I did factory reset and was in TWRP recovery again. Good. Then I reflashed the phone and there was an error saying that secure booting unsuccessful. I have LG Flashtools and tot file with dll for my LG D620fr on my laptop. This method I used once when getting the phone bricked and it worked and I was able to install stock 4.4.2 ROM. But this time... not sure why but the tot flash got stuck with 94% and while the phone was supposed to get restarted it didn't and the message above of the secure etc. popped up. I am able to get into my TWRP recovery (weird) but nothing else. I suspect I got my bootloader locked. Is there any way how to figure this out, please? I was trying the fastboot method but my phone is unrecognizeable. Any help is much appreciated.
Click to expand...
Click to collapse
Sounds like the bootloader is locked.
Check this thread: How to check for locked bootloader? ... but it's for the LG G3.
Best place to ask is the G2 Mini Q&A, Help & Troubleshooting.
Thread closed and thank you.
I have looked at multiple guides on this and other sites, googled and tried stuff and I cannot resolve this problem. Hopefully I am posting in the right place.
I took the jump and unlocked the bootloader on my Moto G first generation, XT1034 successfully. I flashed TWRP 2.8.60.xt1034.zip with adb and this was successful. Then I flashed Super SU 4.6 Update and that was successful. I got into trouble I guess when I tried to flash Cyanogenmod 12.1 nightly. I used TWRP to flash via install. The flash had an error, which unfortunately I didn't write down. I believe it was something to do with a partition. However, it looked like the flash failed. At this point and for hours I have been trying to fix the "Warning Bootloader Unlocked Loop I am stuck in.
I have been able to get into the phone and flash via adb commands. I've tried several commands suggest to fix this that I have found in forums. I have tried flashing several recoveries including an older TWRP per the method in this thread, a clockworkmod - and the original 2.8.6.0.xt1034. When I get into the phone bootloader which is available, I have not been able to access any options in recovery. Pushing the power button on recovery leads to a blank screen sometimes followed by a recovery starting or a Motorola Logo starting up and a couple times a recovery. TWRP has started a couple times, but never gets past the intro screen, where it locks up. clockworkmod (clockworkmod-6.0.4.7-falcon.img started once after flashing through adb and gave me flash options. I tried to sideload, didn't understand, went back and the recovery locked up. These recoveries no longer load at all.
Through all of this the "Warning Bootloader Unlocked" logo screen comes up after plugging into the computer (Windows 8.1).
Example, I open the phone bootloader by waiting for the phone screen to go from the "Warning Bootloader Unlocked" screen to blank - it cycles from logo to blank. If I'm quick the phone and hard boot the phone will boot into bootloader. I connect to the laptop through USB. When I toggle to recovery and hit the power button the screen goes blank, the Motorola Logo pops up, goes blank and then the "Warning Bootloader Unlocked" appears. The Laptop then seems to connect and disconnect as the Warning screen comes on and turns off.
The factory selection just goes to a blank screen.
I would really appreciate some advice on how to get the phone back to a state in which I can work with it and try again. It is very difficult wading through all of the information out there. I've learned a lot through this issue, but can't take it any further.
Thanks, Jeff
Solved - Stuck in "Warning Bootloader Is Unlocked" Loop
This resolution took many hours to figure out, but I finally got there with this guide - http://forum.xda-developers.com/showthread.php?t=2542219, this thread - http://forum.xda-developers.com/showthread.php?p=54855457#post54855457 and this thread - http://forum.xda-developers.com/gen...e-firmware-t3042687/post59139823#post59139823.
I tried RSD Lite on different computers and USB cables I could not get the device recognized. So I ended up with the MfastbootV2 method to reload stock firmware, which I found on the firmware thread above - this was big, as my phone is with Wind Mobile in Canada and the link is the right one. The only thing I picked up from a different website was to use a computer with USB 2 ports. This is what I did, but I don't know one way or the other if USB 2 was needed. .
Can't thank you hard working guys enough for the time you take to put these threads together. I'm back up and running. As a bonus, after a big clean up in the process, my phone is running fast again.
Thanks everyone.
Hello.
First of all, i'm sorry if this question have been asked before. Believe me, i've tried searching even through Google's 2nd page but still no luck in finding answer.
I had a OPO 64GB version. It was working fine until i decided to do ROM update. My previous working ROM is "CM13-20160812-somethingsomething-SNAPSHOT.zip". It is rooted with Xposed installed
I tried to update it using TWRP. the update is "CM13-20161216-somethingsomething-SNAPSHOT.zip". It got stuck at "Patching system image unconditianally"(probably wrong spelling there) for more than one hour. So, i decided to force reboot it and it is now stuck at boot logo(not bootanimation)
Thing is, i cant get it into fastboot, nor recovery. it just stuck there and i've tried to Power Cycle but still no result. I tried to plug it into my computer and it does detect it in "Device Manager" under "Portable Devices" with name "A0001".
I wonder if it soft brick or hard brick. I'm asking brilliant mind in here, if there's a way to restore it. I just revived it from broken screen since 2016(talk about bad luck) and i don't want to completely replace as the device is still in good condition.
Also, if there's no other choice then i had no other way than to follow this guide here, which completely unbrick my phone(also losing me 30+ apps)
http://www.androidbrick.com/unbrick-oneplus-one-two-3-3t-qualcomm-hs-usb-qdloader-9008/
or
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Nevermind. i got it to work by installing QPST driver. for some reason it enable adb at boot logo(yes at boot logo). got into recovery and recover my system partition(which is broken).
I ask the mod to delete this thread. Thank you