Not sure if anyone else has seen this?
A collegue of mine woke up to find his gnex not booting. I've got into the bootloader and it shows as no baseband and he also has no recovery.
I've tried flashing CWM via fastboot, which succeeds, however if you try to boot into recovery, it goes back to the bootloader stating that no recovery or boot is available.
I then tried to flash a radio, however had the same issue. Fastboot says a success but the bootloader says no baseband still.
Also, when rebooting bootloader, instead of powering off, the screen effectively dies/greys out.
Any ideas? I've tried reverting to stock using the Google images with no luck. Also tried to relock the bootloader - it succeeds, says so on bootoader, however on reboot it still says its unlocked
Sounds like there might be an issue with the flash memory?
Possibily. Seems a little odd that even the bootloader won't remember if its locked or unlocked. He's managed to get a replacement (even though the bootloader clearly states that it is unlocked)
The settings/changes made in the bootloader not sticking is (to me, at least) indicative of a hardware issue.
One last thing to consider - have you tried reflashing/updating the bootloader? There are instructions and links to the files needed in this thread: http://forum.xda-developers.com/showthread.php?t=1391881&highlight=flash+bootloader
codesplice said:
The settings/changes made in the bootloader not sticking is (to me, at least) indicative of a hardware issue.
One last thing to consider - have you tried reflashing/updating the bootloader? There are instructions and links to the files needed in this thread: http://forum.xda-developers.com/showthread.php?t=1391881&highlight=flash+bootloader
Click to expand...
Click to collapse
Yep, flashed the bootloader several times using all 3 sources from Google to see if it made any difference. Same story - success but on reboots it never seems to remember
Related
I need help, When I turn on my Nexus the screen stays stuck on the Google start up screen. My phone is rooted with JellyBean. I have the Verizon version of the phone. I was also wondering how can I unroot my phone back to stock ICS?
http://forum.xda-developers.com/showthread.php?t=1626895
Follow that to return to stock.
biscuitownz said:
http://forum.xda-developers.com/showthread.php?t=1626895
Follow that to return to stock.
Click to expand...
Click to collapse
Thanks.
Right now I'm still stuck at the google start-up screen which still won't load up. I don't know if I messed up my phone.
I'm not really tech savvy with the entire flashing and fixing, but I'll help you best as I can.
You're not in trouble even if the phone hangs on the google logo upon a boot up. If you can hold the volume up and then the power, you should have access to bootloader. You can boot cwm to install stock rom, which I believe will remove root (superuser) and return to stock ics or jelly bean depending on which stock rom you install. If you've unlocked the phone (which I assume you did), you can lock it again by using the command "fastboot oem lock," which will lock the device back to factory settings.
I've basically surmised the linked thread above. If you're still confused, look at this thread here. Cheers!
biscuitownz said:
http://forum.xda-developers.com/showthread.php?t=1626895
Follow that to return to stock.
Click to expand...
Click to collapse
My phone is facing same problem, but with a twist and need help.
I did not unlock, root, or install any bootloader before, no CWM.
But my phone is now in bootloop, after a hang for unknown reasons.
I tried recovery, reboot, even fectory reset, but it just goes into a continous loop of google word logo, flashing trapezoids, and then a glitchy stop, then loop.
Sometimes it will just loop at the google word logo.
So I thought my original ROM must be damaged, and wanted to flash a new rom, hoping to fix things.
Problem is, I managed to unlock, but cant get through to rooting as whenever I try to root, it will attempt to run, but will end up saying :
FAILED <status read failed<too many links>>
Also i did not have USB debug before my phone went into bootloop. So now during rooting and attempts to install CWM, there is supposed to be a reboot and a change of USB debug setting required, which can't happen in my case as it couldn't even reboot to stock android.
So I am stuck with a bricked phone currently, when I didn't do anything in the first place...
details of my phone when in fastboot mode:
Product name - tuna
Variant - maguro
HW Version - 9
BOOTLOADER VERSION - PRIMEKK15
BASEBAND VERSION - I9250XXLA2
CARRIER INFO - NONE
SERIAL NUMBER - sorry not disclosed
SIGNING - production
Please let me know what i should do next... Hope to recover my phone
Thanks.
Make sure before you start, you have the correct drivers for your phone. Use this for your driver, and put the phone on bootloader. Make sure when you type fastboot devices, it shows the device. You can then unlock, boot cwm, flash either stock or other roms from there.
My Nexus 5X just corrupted itself a couple days ago and unfortunately I did not enable OEM unlocking before that happened. I was running stock, un-rooted and from looking online the past couple days I see no way to unlock the bootloader so I can wipe everything and re-flash. I can get into fastboot, but not recovery mode. Recovery mode just says "No Command" with the little android on its side. I have tried all the fastboot commands that one would normally try and they all return some version of "device is locked" error messages. Is there any way at all to unlock the bootloader or flash stock, or otherwise get into recovery without checking that OEM unlocking option in the Developer Options of the OS? I don't care about my data, I just want to get my phone working again. It's out of warranty so I am willing to try anything to get it working again.
I'm in the same situation
This is why I always enable Oem unlocking on all devices I own regardless of security for things like this .
_Ghost said:
This is why I always enable Oem unlocking on all devices I own regardless of security for things like this .
Click to expand...
Click to collapse
Yeah, im going to be doing that from now on. I am pretty sure it was an OTA update that did it. It had just updated a day or two before. I was able to get into Recovery and sideload a different OTA update. The update failed and the phone rebooted, but it rebooted into Android. I was able to get my data off and all seems stable for now.
How did you fix it?!
coryrwest said:
Yeah, im going to be doing that from now on. I am pretty sure it was an OTA update that did it. It had just updated a day or two before. I was able to get into Recovery and sideload a different OTA update. The update failed and the phone rebooted, but it rebooted into Android. I was able to get my data off and all seems stable for now.
Click to expand...
Click to collapse
I am in this exact situation. Phone out of warranty, just want to get it back on, don't care about the data on it.. but the "device state" is locked. I can get it into recovery but the sideload fails, I think because the device is locked. How did you get your phone to work again??
I've tried following these instructions (I'm new and can't post a URL: [ttps://drive.google.com/file/d/0Bz6x7k-VkpUJam5Mc1hKa09PVGc/view) and it fails during step 19.
I've also tried these instructions (I can't post the URL but if you google this exact phrase, it's the first link: Nexus 5X Bootloop Fix - The Step-by-step DIY Guide - TechBii) but the phone is locked so I can't do it.
Help!
See this post please: https://forum.xda-developers.com/nexus-5x/general/petition-google-release-official-t3672987
Thanks
So did you ever get it to work or just thre the phone in the garbage, @coryrwest
See my latest post in the thread: https://forum.xda-developers.com/showpost.php?p=71241965&postcount=4
How?
coryrwest said:
Yeah, im going to be doing that from now on. I am pretty sure it was an OTA update that did it. It had just updated a day or two before. I was able to get into Recovery and sideload a different OTA update. The update failed and the phone rebooted, but it rebooted into Android. I was able to get my data off and all seems stable for now.
Click to expand...
Click to collapse
I'm having a similar issue, how did you exactly get it into recovery? Cause mine will simply keep rebooting if I select recovery mode from bootloader
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, 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?
Hello everyone,
Few weeks ago, I broke the screen of my MiA2 Lite. The touchscreen was still working perfectly, but nevertheless, I decided to change the whole display.
And... The touchscreen of the new display was not responsive also. So I've switched back to the old one. Same issue.
I've read somewhere, that a reflash could help to fix this issue.
So, I've installed TWRP and flashed a first rom: miui_DAISYGlobal_V11.0.21.0.QDLMIXM_c6721a4b58_10.0.
I tried then to boot, the phone boots correctly, but the new touchscreen was still not responsive. I tried then with the old one. Same issue.
Then I tried 5 other roms:
- lineage-19.1-20220329-UNOFFICIAL-daisy
- OctaviOS-v3.0-daisy-20211023-2257-GAPPS-Official
- syberia_daisy-v5.4-20220420-1948-OFFICIAL
- miui_DAISYGlobal_V11.0.5.0.QDLMIXM_4e152f6600_10.0
- crDroidAndroid-12.1-20220510-daisy-v8.4 --> Current installed rom.
Still the same issue... So I've started thinking that I've damaged the already broken screen during the disassembly process and that I've received a defective new one. But the odds are poor...
One more thing. When I boot my phone, I've a following message: "Your device software can't be checked for corruption. Please lock the bootloader."
So I've lock the phone, and then it cannot boot anymore. If I unlock it, the phone is able to boot correctly.
This is the first time I'm encountering this kind of issue. I've already done multiple reflashes on a OnePlus One with screen replacements also, and everything was always working perfectly.
What do you think about this issue?
Is it hardware or software issue?
What could I do to continue to troubleshoot and see what is causing the problem?
Thanks for your help!
I mean you could try locking the bootloader and then flashing the stock rom.
I think it's a hardware problem, but don't quote me on that.
Ezement said:
Hello everyone,
Few weeks ago, I broke the screen of my MiA2 Lite. The touchscreen was still working perfectly, but nevertheless, I decided to change the whole display.
And... The touchscreen of the new display was not responsive also. So I've switched back to the old one. Same issue.
I've read somewhere, that a reflash could help to fix this issue.
So, I've installed TWRP and flashed a first rom: miui_DAISYGlobal_V11.0.21.0.QDLMIXM_c6721a4b58_10.0.
I tried then to boot, the phone boots correctly, but the new touchscreen was still not responsive. I tried then with the old one. Same issue.
Then I tried 5 other roms:
- lineage-19.1-20220329-UNOFFICIAL-daisy
- OctaviOS-v3.0-daisy-20211023-2257-GAPPS-Official
- syberia_daisy-v5.4-20220420-1948-OFFICIAL
- miui_DAISYGlobal_V11.0.5.0.QDLMIXM_4e152f6600_10.0
- crDroidAndroid-12.1-20220510-daisy-v8.4 --> Current installed rom.
Still the same issue... So I've started thinking that I've damaged the already broken screen during the disassembly process and that I've received a defective new one. But the odds are poor...
One more thing. When I boot my phone, I've a following message: "Your device software can't be checked for corruption. Please lock the bootloader."
So I've lock the phone, and then it cannot boot anymore. If I unlock it, the phone is able to boot correctly.
This is the first time I'm encountering this kind of issue. I've already done multiple reflashes on a OnePlus One with screen replacements also, and everything was always working perfectly.
What do you think about this issue?
Is it hardware or software issue?
What could I do to continue to troubleshoot and see what is causing the problem?
Thanks for your help!
Click to expand...
Click to collapse
how did you use twrp without a touchscreen?
Thank you for your reply.
So, I first I've locked the bootloader.
And here is the first issue, I was no more able to boot TWRP.
When I lock the bootloader, I cannot use "fastboot boot twrp.img" and I cannot press Volume Up + Power to boot it.
So then I tried to unlock the bootloader. I first tried to flash 2 stock roms, but I've always "Invalid zip file format !".
Then I've downloaded a custom rom (Lineage). And the system boot correctly (but touchscreen still not working).
After this test, I've relocked the bootloader, and when I reboot, I've the following message: "The system has been destroyed". If I unlock again the bootloader, the system starts normally, but the touchscreen is still not responsive.
jons99 said:
how did you use twrp without a touchscreen?
Click to expand...
Click to collapse
I use a mouse plugged in the micro-usb port.
PhotonIce said:
I mean you could try locking the bootloader and then flashing the stock rom.
I think it's a hardware problem, but don't quote me on that.
Click to expand...
Click to collapse
Have you tried this?
Obviously neither twrp/custom roms will work with a locked bootloader, as they aren't signed images which the locked bootloader is supposed to boot.
Hello PhotonIce, sorry for very late answer.
Ezement said:
Thank you for your reply.
So, I first I've locked the bootloader.
And here is the first issue, I was no more able to boot TWRP.
When I lock the bootloader, I cannot use "fastboot boot twrp.img" and I cannot press Volume Up + Power to boot it.
So then I tried to unlock the bootloader. I first tried to flash 2 stock roms, but I've always "Invalid zip file format !".
Then I've downloaded a custom rom (Lineage). And the system boot correctly (but touchscreen still not working).
After this test, I've relocked the bootloader, and when I reboot, I've the following message: "The system has been destroyed". If I unlock again the bootloader, the system starts normally, but the touchscreen is still not responsive.
Click to expand...
Click to collapse
Like I've explained here, the problem is that I do not succeed to lock the bootloader and then flash a stock rom.
In fact I don't know how to flash with a locked bootloader.
lock the bootlaoder and flash the signed stock rom using mi flash tool (the official flashing tool)