Z551ML 2GB version.
Put a temp root on the phone (has been restarted since), and went to update today and it bootlooped on me. I tried to fix it numerous ways and it has only gotten worse.
Bootloader and HW Ver show nothing on Fastboot screen.
Tried to fastboot new img files, but now it just goes to the dying android with a red triangle.
Tried to do Un-Tethered TWRP and flash a new ROM, same thing.
I have no access to ADB, only fastboot.
Nothing but dying little android with red triangle no matter what I do.
I was tinkering with the notion that maybe the bootloader is locked, and that's why it won't take the flashed ROMs?
IDK. Seriously need help, please?
Related
So I am the proud owner of a shiny, new Galaxy Nexus (GSM). Unlocked the bootloader and installed CWM recovery and was doing great. Today I decided to install the volume fix. Installed the zip through recovery, completed and rebooted. The phone got stuck in a bootloop over and over and over and over and would not boot Android at all. Did a ton of research here and everywhere and, in a panic, I booted into CWM recovery, reset the cache & did a full factory reset. NOW, the phone will not go past the Google bootscreen with the unlock symbol, no matter what I do. AND, I can't even flash the original google image because I can't get in to set USB debugging so my computer won't even recognize the phone (FYI, I'm on a Mac). I am at a complete loss and don't know what to do. If I could only get the computer to recognize the phone I could flash the original google image through Terminal, but alas, I can't. Any ideas? If I can somehow get this phone back up and running I would be eternally grateful. For now, I think I may be SOL. Thanks....
This happened to me, I was not able to solve the issue, even though I could push and pull data to and from the device via ADB. I could still not get past the google logo. I decided to lock the boot loader again and return to the store for a new device.
http://groups.google.com/group/android-building/msg/2cd2b16ed56a7e84
Sent from my Galaxy Nexus using XDA App
hartford said:
So I am the proud owner of a shiny, new Galaxy Nexus (GSM). Unlocked the bootloader and installed CWM recovery and was doing great. Today I decided to install the volume fix. Installed the zip through recovery, completed and rebooted. The phone got stuck in a bootloop over and over and over and over and would not boot Android at all. Did a ton of research here and everywhere and, in a panic, I booted into CWM recovery, reset the cache & did a full factory reset. NOW, the phone will not go past the Google bootscreen with the unlock symbol, no matter what I do. AND, I can't even flash the original google image because I can't get in to set USB debugging so my computer won't even recognize the phone (FYI, I'm on a Mac). I am at a complete loss and don't know what to do. If I could only get the computer to recognize the phone I could flash the original google image through Terminal, but alas, I can't. Any ideas? If I can somehow get this phone back up and running I would be eternally grateful. For now, I think I may be SOL. Thanks....
Click to expand...
Click to collapse
One more post like this in Dev section and you'll be banned for 3 weeks
hi everyone
after an afternoon of googling I decided I need more help
so this is what happened (at that moment I was running on PureNexus and TWRP:
at some point I noticed that my phone was off, I tried to reboot it, it showed the google logo for a moment, but then the screen went black.
after a while I tried to reboot again, with the same effect...and again
so I decided, hm maybe a factory reset helps and tried to boot into TWRP. tried to boot into recovery, but with the same result as before: google logo appears then screen turns black
next I booted into bootloader and flashed TWRP through adb. but this didnt help either. still everything just as before.
at that point I got a little nervous. then I deleted cache and userdata through fastboot, still nothing.
after some googling I stumbled over a thread which suggested to use the Nexus Root Toolkit for reflashing Stock.
I followed all the instructions in NRT and according to the log (and fastboot), all the images were successfully flashed, but when I booted the screen turned black after the google logo again.
since I was able to boot into bootloader, I decided to lock and unlock the bootloader (at that point I was just trying to see some effect), but nothing worked
any suggestions on what else I could try?
thanks! cheers
trier09 said:
hi everyone
after an afternoon of googling I decided I need more help
so this is what happened (at that moment I was running on PureNexus and TWRP:
at some point I noticed that my phone was off, I tried to reboot it, it showed the google logo for a moment, but then the screen went black.
after a while I tried to reboot again, with the same effect...and again
so I decided, hm maybe a factory reset helps and tried to boot into TWRP. tried to boot into recovery, but with the same result as before: google logo appears then screen turns black
next I booted into bootloader and flashed TWRP through adb. but this didnt help either. still everything just as before.
at that point I got a little nervous. then I deleted cache and userdata through fastboot, still nothing.
after some googling I stumbled over a thread which suggested to use the Nexus Root Toolkit for reflashing Stock.
I followed all the instructions in NRT and according to the log (and fastboot), all the images were successfully flashed, but when I booted the screen turned black after the google logo again.
since I was able to boot into bootloader, I decided to lock and unlock the bootloader (at that point I was just trying to see some effect), but nothing worked
any suggestions on what else I could try?
thanks! cheers
Click to expand...
Click to collapse
If this is not the dreaded bootloop, unlock the bootloader and flash factory image manually.
That should help.
indian84 said:
If this is not the dreaded bootloop, unlock the bootloader and flash factory image manually.
That should help.
Click to expand...
Click to collapse
thanks, I was afraid it might be....
I flashed the factory image first with the sh_all option and then manually. both methods didnt work and I couldnt get past the google logo.
Right now Im not even able to boot into the bootloader.
Im assuming theres nothing else the try besides contacting LG support?
Maybe its time to say goodbye to a good friend
trier09 said:
thanks, I was afraid it might be....
I flashed the factory image first with the sh_all option and then manually. both methods didnt work and I couldnt get past the google logo.
Right now Im not even able to boot into the bootloader.
Im assuming theres nothing else the try besides contacting LG support?
Maybe its time to say goodbye to a good friend
Click to expand...
Click to collapse
LG Support it is for you. They have know to replace units that have passed the warranty period by one or two months. Give it a shot
So after 2 hours of searching, trying and failing, I just decided to post here and see what help I can get.
Situation is exactly like the title. Had Lineage 14.1 installed, and decided to update the phone. Rebooted the phone and went to TWRP recovery. For whatever reason, I decided to reboot the phone, which ended up in it coming back to TWRP. This repeated until I got the stock recovery, which put me into bootloader instead. Bootloader is now locked, I can no longer get into recovery, and I'm stuck in bootloader for as long as this continues.
So far I have tried:
--------BEFORE TWRP RECOVERY FAILURE AND BOOTLOADER LOCK---------
Factory Resetting
Formatted and flashed ROM
A couple of ADB commands
--------AFTER TWRP RECOVERY FAILURE AND BOOTLOADER LOCK---------
Replaced recovery image file with stock
Idiotically replaced bootloader image file with stock (Locked, can tell since Android N is no longer bugging me with preboot notification which was present before when bootloader was unlocked)
Idiotically replaced the system image file with stock
A slew of fastboot commands (You can comment and I can see if I have attempted them)
Attempted to continue the fastboot process
Attempted to use an automatic rootkit. Did not like my device, so it did nothing at all.
Manually unplugging the battery
Haven't tried:
Placing rom in sd card, like I've seen people say elsewhere. (No SD card available)
Anything else you tell me that I haven't done
I'm not really interested in keeping any files that I've had before, if that is not already made clear.
Anyone that can help me, I really want this to end. :crying: :crying:
BillJake said:
So after 2 hours of searching, trying and failing, I just decided to post here and see what help I can get.
Situation is exactly like the title. Had Lineage 14.1 installed, and decided to update the phone. Rebooted the phone and went to TWRP recovery. For whatever reason, I decided to reboot the phone, which ended up in it coming back to TWRP. This repeated until I got the stock recovery, which put me into bootloader instead. Bootloader is now locked, I can no longer get into recovery, and I'm stuck in bootloader for as long as this continues.
So far I have tried:
--------BEFORE TWRP RECOVERY FAILURE AND BOOTLOADER LOCK---------
Factory Resetting
Formatted and flashed ROM
A couple of ADB commands
--------AFTER TWRP RECOVERY FAILURE AND BOOTLOADER LOCK---------
Replaced recovery image file with stock
Idiotically replaced bootloader image file with stock (Locked, can tell since Android N is no longer bugging me with preboot notification which was present before when bootloader was unlocked)
Idiotically replaced the system image file with stock
A slew of fastboot commands (You can comment and I can see if I have attempted them)
Attempted to continue the fastboot process
Attempted to use an automatic rootkit. Did not like my device, so it did nothing at all.
Manually unplugging the battery
Haven't tried:
Placing rom in sd card, like I've seen people say elsewhere. (No SD card available)
Anything else you tell me that I haven't done
I'm not really interested in keeping any files that I've had before, if that is not already made clear.
Anyone that can help me, I really want this to end. :crying: :crying:
Click to expand...
Click to collapse
What is your IFWI version number in bootloader ?
IFWI Version: 0094.0183
BillJake said:
IFWI Version: 0094.0183
Click to expand...
Click to collapse
Flash raw 4.21.40.184 M with AFT in bootloader
https://forum.xda-developers.com/zenfone2/general/z008-z00a-z00d-z00x-raw-fw-collection-t3448966
Thank you so much. Fixed my phone.
BillJake said:
Thank you so much. Fixed my phone.
Click to expand...
Click to collapse
Marvelous , drop a thank you to realyoti in the link , hit his thanks button too.:good::highfive:
Long story short my V521 is bricked, as far as I can tell.
Here’s what happens:
Turn on.
Shows ‘can’t detect corruption’ unlocked boot loader screen.
Shows LG screen.
Reboots.
If I attempt factory reset via hardware buttons, I get a Nougat circle that says ‘Erasing...’, then reboots into the above loop.
Download mode seems to be nonexistent, as it just never works. My PC does not recognize it as the right device for LG support tool or Uppercut to find it, despite all drivers being installed.
ADB was working until stock recovery flashing (which I thought was gonna be a fix...)
And now I don’t know what to do.
Basically, the only thing I have is an unlocked bootloader.
Someone. Please.
Help me.
:crying:
Long story short, I ended up with a classic bootloop (shows boot animation continuously) from messing around with Magisk modules, so I did a wipe from recovery, still bootloop, so I tried reverting completely to stock with the OEM downloads. I tried flash_all_except_storage.bat, and flash_all.bat, but this time it was a different bootloop. The phone shows the Android One logo, the screen flickers like it's going to the boot animation, but then it just goes back to the Unlocked Bootloader Warning Screen, then the Android One logo, and loops like that. I dumbly thought locking the bootloader, reflashing everything, and starting over like it were a new phone would fix the issue, so I did flash_all_lock.bat, but now I'm just stuck with this weird bootloop and a locked bootloader. Trying to unlock the bootloader with fastboot just gives me "oem unlock is not allowed", so I'm at a loss here.
Does anyone know of anything else I could do, or is this a hard brick?
With a locked bootloader EDL flash probably is your last chance.
Maybe this thread helps:
https://forum.xda-developers.com/mi-a2-lite/help/hard-bricked-mi-a2-lite-help-to-enter-t3862648
thorin0815 said:
With a locked bootloader EDL flash probably is your last chance.
Maybe this thread helps:
https://forum.xda-developers.com/mi-a2-lite/help/hard-bricked-mi-a2-lite-help-to-enter-t3862648
Click to expand...
Click to collapse
I got stuck with a similar problem and that was the only option, to boot into EDL mode you will need to partially dissasemble your device and flash the image via fastboot or via MiFlash (download the latest version as I had problems with an older one). Since that incident I kept the bootloader unlocked just in case something happens.
I had the phone booted into EDL mode and attempted to flash the stock ROM (10.0.3.0) with MiFlash, but it errored out with an ERROR_UNSUPPORTED_TYPE. I tried with the previous version, 10.0.2.0 and it worked for some reason. That fixed it though, so thanks! I've been lightly tinkering with rooting android phones a few years now, but until encountering this issue, I'd never heard of EDL mode. You learn something new every day? ?
I have the same issue with my nephew 's mi a2 lite which has the bootloader locked.
It only shows the android one logo.
I cannot go to recovery mode, but I can go in fastboot.
Changing from "a" to "b" doesn't solve anything and being the bootloader locked is not possible to flash anything from fastboot.
So I've opened the device and I've short circuited the edl pinpoint to be able to flash with MiTool (I've used an old version since more recent ones gave errors when flashing).
I was able to flash both the latest official ROM and the oldest one which I've found ( daisy_global_images_V11.0.14.0.QDLMIXM_10.0 and daisy_global_images_V9.6.4.0.ODLMIFF_8.1 respectively).
In both cases the device still is "frozen" with the android one logo when I've tried to turn it on after the flashing procedures gave me a successful status.
What else can I do?