Hi,
so i was trying root my Lenovo Yoga Tab 3 using Magisk. I followed multiple guides on how to do this as this tablet is pretty hard to root. I tried using the TWRP recovery method but i couldn't find a TWRP version that worked on the tablet. So i decided to use the Patched Stock Boot Image method instead. I searched everywhere but i couldn't find a stock boot image for the firmware version of the tablet. I found it on a few websites but non of the downloads were working. I found threads and discussions where people had the same problem, but none of the download links were working. So i decided to try using the stock boot image with the closest firmware version to mine that i could find. The image was called YT3-X50F_USR_S000022_1606061517_Q1241_ROW_QPST. I don't remember what firmware my tablet have, and i can't find out because the tablet is stuck in boot. When rooting the tablet i used multiple guides, but mainly this one. So anyways i used Magisk to patch the image file. Then i flashed the boot image to the tablet and rebooted and now it is constantly booting. It just shows the Lenovo logo. I can't power it off, holding the power butting just reboots. I can't access the bootloader or the recovery menu, when i hold the correct buttons it tries to boot in to the bootloader, but then the tablet reboots and goes back to being stuck in the boot sequence. I have searched the internet for answers and i found people with similar problems, but i didn't find any solutions to my problem. Have i bricked the device? I have rooted my phone before and i didn't encounter any problems. But when rooting this tablet however i found myself spending hours trying to find the proper files online. I couldn't even find anything on the Lenovo website! Is there anything i can do? Do you think it will help to let it run out of battery and recharge it again? Have i bricked it for good?
Related
Hey,
I've tried searching similar threads for this issue but haven't found a solution that works quite yet.
I have Samsung S Vibrant GT-I9000M on which I tried to originally flash CyanogenMod. At first I tried using Clockworkmod and discovered I couldn't actually get into it because of the Samsung 3e recovery utils. So I tried flashing to a different firmware (I've tried a lot now) to get to 2e but I am unable to get past the loading screen, which is flashing the samsung galaxy s logo. I've followed a lot of guides to try to get back to stock firmware but I haven't had any success at all.
I can't get into recovery mode anymore but I can get into download mode, and I've been trying to get back to stock firmware but whatever I try it just reboots and starts flashing a loading icon (if the usb is still plugged in, without it just flashes the samsung s galaxy screen). I've also noticed that the model number changed from GT-I9000M to GT-I9000.
I'm new to all of this, so if anyone can lend a helping hand I'd really appreciate it. So to summarize, I can get back into download mode but I cant' get into recovery. I've tried at least 5 or 6 times to reflash stock firmware (following the guides in this forum, I can link if needed) but its the same result each time. A cycling loading screen.
this guy is having the same problem.. see my posts in his thread.. do all the things i have told him to do..
http://forum.xda-developers.com/showthread.php?t=1022688
Hello
About three days ago I went to turn on my N8000 and it got stuck in the "Samsung GALAXY Note 10.1" logo. At first I thought it was updating something or just taking longer to start, but after one day I realized that it wasn't going to start at all. So I tried to do a factory reboot but found out that the tablet won't boot into the bootloader (Power + vol up), it just kept going into the galaxy logo. It can, however, boot into download mode, so I started checking on the page what could solve my problem. I tried installing the CWM recovery using ODIN 1.85, the flash was successfull but the device will still not boot into recovery mode. After that I read that installing a stock firmware could solve the issue, so I downloaded the Kit Kat version and flashed it, rebooted but nothing. I found some topic that a guy had to use a .pit file along the kit kat firmware, did that too and nothing.
So here I am stuck with my tablet bricked and without knowing what else to do, so I was hoping to get some help from you guys.
Thanks in advice!
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
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
Greetings everyone,
I decided to post my problem with my phone after searching the entire internet for similar problem but with no luck. Anyway I used to play around with my Samsung j7 pro for 2 years, I managed to flash twrp and thus many other custom roms, until last week when I recklessly flashed a sboot.img.tar file through Odin in order to fix cellular network in a rom I flashed earlier, this alone bricked my phone refusing to get past the Samsung logo, so like I do always, I tried to restore my phone by flashing the stock firmware (9.0) which I always keep on my PC, but surprise, the phone refuses to go through the process and gives me this error:
sw rev check fail bootloader device -1 binary 6
(same with 8.0 and 7.0 firmware)
I searched the internet for same error but with no luck, because I understand it's a mismatch between device bootloader current version and the firmware bootloader's, that they should be the same or higher, meaning you can't downgrade, I get that! but I never seen device with negative figure (-1) what that's supposed to mean? my device bootloader used to be on 6, how did it managed to jump to minus one ?
then I tried to flash TWRP to see if I could flash a rom and get around it, so I did, but when booting into recovery the screen goes black, I thought first the phone turned off, but not really, because TWRP seems to work with screen completely black, I knew that because I accidentally touch the screen and I sense vibration, I managed to reboot the phone via twrp just by guessing the buttons location (screen always black) in order to prove that TWRP is working with screen off. I tried to flash multiple TWRP versions but the same problem, no screen just touch, by the way there is nothing wrong with display hardware because it shows Samsung logo at start and also can boot into download mode just fine.
I hope someone could help me overcome this big of an issue, because I tried everything.