The phone was rooted before and I had a few magisk modules installed.
After updating a few of them, the phone entered in a bootloop state. I waited 2 hours, hoping it will start, since a similar event happened a few weeks ago. After realising it will not start I tried to flash back to stock. It gave an error message and now I'm stuck. The phone does try to power on, holding the power button makes it vibrate. It also gets recognized by the PC as "Android". When I try to flash the stock img back on, I get "phone is locked" or something along those lines message. I did try going into recovery but it doesn't work, the screen is black (not dead, it is black color). What can I do?
Mi Flash Tool <<<<<<
I had the same problem with Magisk and version 10.07
---------- Post added at 05:17 PM ---------- Previous post was at 05:17 PM ----------
Mi Flash Tool <<<<<<
I had the same problem with Magisk and version 10.07
Related
Hello,
I am not new to rooting, made a mistake in installing cyanogemod 10.2.1 on my S3. I had the Status 6 error, saw some troubleshoot fix online and it told me to delete the first line from the Update Script inside the google folder. I went to recovery, installed the rom, it said restart, so i did. Now my S3 wont load into recovery or to download mode at all. Although i still see the qhsusb_dload in device manager when i plug it in my pc.
I have tried booting from an sd card but i got nothing, i kept on trying different debrick images from everywhere and i dont know if i have the right one. My phone was in 4.4.2 before all this happened. Please help because i just got this new phone and i really dont have money to jtag. My parents would kill me.
Thank you.
http://forum.xda-developers.com/showthread.php?t=2549068
---------- Post added at 12:00 PM ---------- Previous post was at 11:52 AM ----------
http://forum.xda-developers.com/showthread.php?t=2962626
Hello,
I really need your help and expertise.
I got the notification that I needed to update my N7 with the latest OTA security updates. I let it do its thing and noticed after some time that it was stuck on the Google logo. I tried restarting but nothing would work. I read what I could about some people tapping the back of their units and then working again but that unfortunately didn't work for me. I tried to start in recovery mode but that didn't work and then the power plus vol up. It tried to finish installing the update. But I soon got an error message with the Android guy laying on its back with a red arrow on its stomach saying only "Error" nothing more or less. Not sure what to do next, I tried to find info on suggestions but after about 5 minutes, it seemed to try to reboot and went right back to getting stuck on the Google logo.
I've never had any issues with this. It's stock (no root) and had the Marshmallow update on it running just fine. It's completely unusable now and I have no idea what to do to try to fix this. Any suggestions would be really helpful. Thanks so much!
Please post the output of:
fastboot format cache
but if the response is "FAILED (command write failed)" then let's discuss it in the thread linked in my signature.
use nrt, would solve your problem.
---------- Post added at 03:53 PM ---------- Previous post was at 03:52 PM ----------
download the stock firmware latest and flash it either on fastboot or use nrt instead.
I had TWRP 2.8.7.0 working fine, but tried upgrading to 3.0 -
That had a weird issue where twrp would show the splash screen, the screen would intermittently turn off and on, and keep showing the splash screen, but never entered recovery.
Decided to revert to 2.8.7.0 using flashify... Now when I try to create a nandroid backup in 2.8.7.0, it starts working and then shows the twrp splash screen, and as in 3.0 the screen intermittently turns on and off.
Anyone experienced something like this before? Kind of unsure how to proceed.
Update: now it does the screen intermittently flashing on and off, stuck on twrp flash screen just trying to enter twrp.
Also tried removing SD-Card with no luck
Update2: The behavior is pretty much identical to what's seen in this video https://www.youtube.com/watch?v=Kr46ugrpL6U , except it only happens in recovery (I can enter the os normally if i dont attempt to go into recovery)
This has been common problem with twrp from the looks of it. Right now when I boot to twrp 2.7.x.x I get stuck at the twrp splash. However my problem I can't find any info on your there looks to be two terminal commands you can run to fix it..... Seeing this post I wanted to ask about mine at the same time couldn't hurt do to its starting to look related to the recovery boot loop. But like I said I'm just stuck at it not looping.... very odd.
---------- Post added at 03:14 PM ---------- Previous post was at 03:02 PM ----------
OK mine was sad and simple.... I formatted my SD card back to portable storage and poof it now boots to recovery don't know if it could be related but it's worth a shot!
cmjester6421 said:
This has been common problem with twrp from the looks of it. Right now when I boot to twrp 2.7.x.x I get stuck at the twrp splash. However my problem I can't find any info on your there looks to be two terminal commands you can run to fix it..... Seeing this post I wanted to ask about mine at the same time couldn't hurt do to its starting to look related to the recovery boot loop. But like I said I'm just stuck at it not looping.... very odd.
---------- Post added at 03:14 PM ---------- Previous post was at 03:02 PM ----------
OK mine was sad and simple.... I formatted my SD card back to portable storage and poof it now boots to recovery don't know if it could be related but it's worth a shot!
Click to expand...
Click to collapse
Unfortunately I don't think it's the same, because I still have issues even with the SD card removed. Also, I'm on lollipop if that helps.
I remember that happened once to me in a Samsung device. But eve worst, my device was unable to boot into OS. What I did was put download mode and flashed any version that was easy to root. Then, root, flash recovery TWRP, and then used a nandroid backup. You can apply same procedure on this LG G3 and you'll be back on the game.
Enviado desde mi LG-D851 mediante Tapatalk
Hi,
I know this is a typical newbie has no idea what he's doing scenario, so I apologize. However, I feel like I've tried everything and am yielding no results.
I am trying to root a Verizon LG G3. Since I'm not entirely sure as to the technical details, I want to explain what I think I know. To my understanding, there are different versions of VS985? I haven't seen anything resembling 49A, 49B, or 49C, but the closest thing I found was the software version which said VS9854CA.
The first thing I tried was the One Click Root tool. The tool did not find any methods of rooting though. The next thing I tried was TowelRoot. I set my phone to stay awake while charging, and pressed the "Make it rain" button. It turned yellow as a response, but did not do anything else even after leaving the phone untouched for eight hours. I also tried to ADB tools but "adb reboot fastboot" only rebooted the phone back into the OS, and "adb reboot recovery" showed an android figure with the words "No Command" for a small duration before rebooting back into the OS. The final guide I tried was the KDZ and TOT methods. KDZ resulted in the message "Upgrade stopped due to an error," and TOT displayed "READY!" for the COM41 but did not attempt anything even after unplugging and plugging the phone back in.
Can anyone help me please? Could there be something I'm doing wrong in any of those methods?
I appreciate all the help I get. Thank you.
I'm in the same boat. I just got this phone from eBay, thought it would be easy to root as I used to have one and that was my experience at that time. Things have changed... There is no root for this latest software version 4CA. Totally sucks!
Any suggestions for a comparable phone that can be rooted when on the latest stock update? I'm on Verizon btw...
just use the LGFlash Tool 2014 and flash the 47A KDZ (6.0) file and then rooted using KingRoot 4.9.6 .. Now going to flash twrp and them fulmics rom.
I have tried everything else nothing worked for me. I was on VS985.... MRA58K (6.0.1).. Tot method didn't worked...flashing 10b KDZ also didn't worked.. They keep giving error.
---------- Post added at 04:33 PM ---------- Previous post was at 03:44 PM ----------
Twrp flash doesn't worked and i lost my stock recovery too. NOw just flash 10B Tot with 35B dll and m back to Kitkat. Hope so everything will work now
---------- Post added at 04:55 PM ---------- Previous post was at 04:33 PM ----------
got the red factory reset with status 2.. I had to flash kdz 24b now my phone is booting
So I got my brand new Xiaomi Redmi note 5 global version 2 days ago. Really happy, until I tried to turn it on...
Power (Normal boot) : the phone keeps bootlooping, never passes the Mi initial logo screen
Power + volume up (recovery) : gives an error saying "The system has been destroyed" and just turns off
Power + volume down (fastboot) : works fine
Bootloader it's locked obviously so I can't flash anything
Sometimes the "powered by Android" and the 3 dots blinking appear but they just keep loading and nothing happens (I've waited for 2 hours even) or it just freezes and restarts again. I managed to get into MiRecovery once, don't ask me how, it just got into it without me doing anything special. I tried to flash a new rom via "update.zip" but the phone wasn't recognized via MiAssistant. Never booted into MiRecovery ever since, just gives me the error now.
When I put the phone charging, it automaticaly keeps booting. It only appears the battery icon when the battery it's empty.
Activating warranty is what I'm supposed to do I know, but the problem is that it would take me at least a month to get the phone back since I'm from Portugal and I bought it in a Hong Kong warehouse.
I thing that's all, I really have nothing else to say, I would appreciate some help, thanks in advance!
EDIT : forgot to mention, did the "fastboot getvar anti" test and the result was "anti : 3"
I think you have a chinese variant phone and was flashed with global rom. The system has been destroyed error means you are using a rom not compatible with phone and the bootloader was locked. Only fix is to unlock bootloader OR do a testpoint and flash china rom with anti ver 3 bootloader http://bigota.d.miui.com/V9.5.16.0....EICNFA_20180531.0000.00_8.1_cn_e2d86ecd6b.tgz
---------- Post added at 07:30 AM ---------- Previous post was at 07:21 AM ----------
Also try mi assistant beta on my thread and flash china recovery rom
https://forum.xda-developers.com/redmi-note-5-pro/how-to/tut-flashing-official-recovery-rom-t3798165
devcon69 said:
I think you have a chinese variant phone and was flashed with global rom. The system has been destroyed error means you are using a rom not compatible with phone and the bootloader was locked. Only fix is to unlock bootloader OR do a testpoint and flash china rom with anti ver 3 bootloader http://bigota.d.miui.com/V9.5.16.0....EICNFA_20180531.0000.00_8.1_cn_e2d86ecd6b.tgz
---------- Post added at 07:30 AM ---------- Previous post was at 07:21 AM ----------
Also try mi assistant beta on my thread and flash china recovery rom
https://forum.xda-developers.com/redmi-note-5-pro/how-to/tut-flashing-official-recovery-rom-t3798165
Click to expand...
Click to collapse
Does deep flash/EDL cable works too? I really don't want to open my phone and void the warranty if I ever need it
I tried to boot recovery via fastboot "fastboot boot recovery.img" and it gives me a "Too many links" error