I have a 2015 shield pro that was stuck in a boot loop (not sure what happened exactly, it was my dads), so I was reflashing it according to the dev guidelines after unlocking the bootloader. When i rebooted after flashing boot.img, now the green light comes on for a few seconds and goes off for a while, then comes on again after a while and off quickly. I cant get it into the bootloader by the hardware method. any other ideas or is it trash?
Related
Hi all,
I got my Wileyfox storm running stock CMOS 13.0 in April and had no problems for about a month. Eventually, I got a pop-up notification with an "Incremental Update" for the phone. I downloaded it and when ready to install, I did so - or at least tried. The update finished and booted into recovery for some reason. At the time I didn't question it and just rebooted the phone from recovery. This led to a boot hang on the "Cyanogen Mod Ready" boot screen.
After searching around for a fix I eventually tried to flash over the stock ROM via Fastboot - which for some reason errored on emmc_appsboot and the phone rebooted itself - with a penguin instead of the Wileyfox boot logo and STILL hangs on the Cyanogen screen. I can also now not boot into fastboot and not boot to fastboot from recovery either (which I CAN still boot to).
Does anyone have any ideas on how to fix this ASAP??? Help would be greatly appreciated!
Many thanks.
I've finally found something that works, unplug the battery for a day or two, then plug in and charge and turn on and might boot properly. Frustrating having to do it every time you get into the bootloop hang and doesn't work every time but still probably salvageable.....I discovered after being bricked for 14 months.
When I bought and booted it there was no such lag, but when I tried a failed root with TWRP+SuperSU device bootloop'd
and I had to flash tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c on the device.
so now device is booting but I am noticing that boot logo of Mi is shown for 20sec . Has anyone faced this nuiance ? if yes is there a way out ?
Sounds like standard "pause"/warning due to unlocked bootloader which probably can't be skipped. Once you lock the bootloader, it should boot more quickly. Please keep in mind that you have to have fully stock system before relocking the bootloader.
yes. you can say that.
but only saw the warning once and then I accepted that delay could be due to that. and now even after full flash and lock all script the delay is bothering me. Should I contact mi support or exercise 30 day replacement.
Same here, all started when flashing the first rooted boot-image. But i can clearly remember that after a full flash with relock of the BL, the boot logo was lasting only 5-6 secs.
Now i have reflashed it all (without wiping data) and it is lasting 20 secs anyway
Hi,
I picked up a second hand XT1622 super cheap the other day. It didn't seem to want to boot at first, and stuck around on the blue Motorola logo for a while, but eventually after leaving it alone for an hour or so it sprang into action.
Trouble was I then made the mistake of downloading the December OTA update, and since rebooting from that installation it's been stuck on the blue screen again.
I thought maybe something went wrong with the OTA, and flashed the December firmware through Fastboot hoping that would resurrect it, but I'm still getting the same result.
The bootloader is locked unfortunately, and I can't boot into recovery mode either - same issue.
Does anybody have suggestions other than me breaking the phone in half (which is probably going to happen today anyway)?
Phone suddenly sprang to life, but for some reason wouldn’t let me press return after entering my PIN after prompting for it in setup - maybe it’s a hardware issue and the phone’s on its way to the great G4 graveyard in the sky?
The original G destroys this nonsense of a phone.
For and download the stock firmware, and then flash it through fastboot. After that, see if it boots. If it does, unlock the bootloader so you will have b easier time if this happens again.
Hi boys, i've done some mess on my cellphone! I flashed a preloader to root without have unlocked bootloader, now my cellphone hangs on asus screen with the following message:
Red State
Your device has failed verification and may not work properly
Your device will boot in 5s
After that, it reboots and goes to the same screen. I've tried turning it off but it won't, nor it goes to recovery screen, it keeps on booting loop on that screen.
Its a zenfone 3 max, ZC520TL.
nanhuto said:
Hi boys, i've done some mess on my cellphone! I flashed a preloader to root without have unlocked bootloader, now my cellphone hangs on asus screen with the following message:
Red State
Your device has failed verification and may not work properly
Your device will boot in 5s
After that, it reboots and goes to the same screen. I've tried turning it off but it won't, nor it goes to recovery screen, it keeps on booting loop on that screen.
Its a zenfone 3 max, ZC520TL.
Click to expand...
Click to collapse
Good day good sir,
I know the following may not be of much help, but I'm afraid you will need to return it to Asus for repairs, because:
1. Bootloader is locked (that means no flashing)
2. You can't boot into recovery (no install via adb or micro sd)
I'm sorry I wasn't able to help much, but that's all I can say after experimenting with Asus's software for a while.
Greetings,
Kevin
Hi,
I have the same issue but instead of a bootloop, I can still boot android up with my zenfone max 3 zc520tl phone but I noticed that I can't turn on my Wifi. I this issue related to Red state? How can I fix the red state error? Please, I'm in dire need of help.
I was trying to boot into recovery after I flashed TWRP but it gave me the "Your device cannot be checked for corruption, please lock the bootloader"
Which, like a complete idiot, I did.
Now my phone is stuck showing the ZTE logo, turning off, and repeating. It won't turn off either, so it's stuck in this loop? I tried using Tuliptool.
Impatient Kidd said:
I was trying to boot into recovery after I flashed TWRP but it gave me the "Your device cannot be checked for corruption, please lock the bootloader"
Which, like a complete idiot, I did.
Now my phone is stuck showing the ZTE logo, turning off, and repeating. It won't turn off either, so it's stuck in this loop? I tried using Tuliptool.
Click to expand...
Click to collapse
That's just a message warning you that the bootloader is unlocked. It would have disappeared in 5 seconds and booted recovery, so you should have let it continue. Nothing was wrong.
Your battery is probably dead by now due to all that bootlooping. I'd try unlocking the bootloader again, if possible.
JoeGatto said:
That's just a message warning you that the bootloader is unlocked. It would have disappeared in 5 seconds and booted recovery, so you should have let it continue. Nothing was wrong.
Your battery is probably dead by now due to all that bootlooping. I'd try unlocking the bootloader again, if possible.
Click to expand...
Click to collapse
All of my previous attempts to unlock the bootloader have failed, either not functioning or due to oem unlocking not being enable as its factory reset.
I'm not sure if it is possible to unlock the bootloader, so I'm here