Related
My son brought me his Nexus S 4g and told me that it doesn't work anymore. He says that he didn't do anything and that it just started doing this on its own. Any help would be greatly appreciated.
When powered on, it quickly goes to the screen with the Google icon and a lock icon. It sits here for about 30 seconds, then reboots to the same thing. If I pull the battery and hold Vol Up and Power when inserting the battery I can get into Fastboot, but when I select Recovery or Reboot, I get the same Google screen.
When I gave him the phone, it was rooted with CWM recovery loaded and a ICS ROM running.
Any help would be greatly appreciated as I have been reading through threads all night long without finding much.
Sounds to me like you need to begin the rooting process again at the "fastboot oem unlock" part. Since you probably don't have anything on your SD card, you might have to push a new recovery via fastboot as well.
Look to this thread:
http://forum.xda-developers.com/showthread.php?t=1078213
for inspiration.
Once you get into the recovery loaded via fastboot, you can get whatever rom that you want onto the SD card by navigating to:
Mounts and Storage > Mount USB Storage
and leave it on that screen while you load the rom onto the SD card.
After that flash the new rom via CWM as normal.
Thanks for the reply. Since I was already unlocked, I followed the steps to return the phone to stock, including flashing boot, system, userdata, recovery and erasing cache. Now when I reboot, it just loops to the Google screen and reboots after 30 seconds. The only difference is that I don't see the lock icon at the bottom or the Google screen.
When I select Recovery, it just goes into the same Google loop. I am going to try to go through the root steps and see what happens. :-(
I was able to unlock the phone, but it will not boot into Recovery. I can get to Fastboot, but I am back to where I started.
When I gave the phone to my son, I had installed SetCPU and configured a profile to throttle the processor down when the screen was off to conserve battery. I am now wondering if he tried to overclock the processor and clicked "set at boot".
Any more suggestions? (please)
Did you successfully flash a recovery.img? Immediately after this you should hit Recovery, then mount the storage, copy a ROM over, do a Full Wipe and flash the ROM.
If all goes well, you'll boot fine. If not, it may be a hardware problem. Try to wipe most of it and lock the bootloader if you need to send it to samsung.
It looks like I successfully flashed a recovery image. I have tried version 5.x and version 3.x. Below is the result of the 5.x command. However when I select Recovery from Fastboot, I go to the Google screen loop.
C:\Program Files\Android\android-sdk\tools>fastboot flash recovery recovery-cloc
kwork-5.0.2.0-crespo4g.img
sending 'recovery' (4136 KB)... OKAY
writing 'recovery'... OKAY
C:\Program Files\Android\android-sdk\tools>
OK, go to http://wonderly.com/bb/CRESPO4G/OEM/GRJ22IMAGES.zip
That will download the GRJ22 stock images of your phone. Unzip them in your PC. Next, use fastboot like this.
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
After it finishes you can reboot your phone with "fastboot reboot". This will installed Stock GB 2.3.4 for NS4G. Setup your phone and you will get OTA to 2.3.5. After that you will get OTA again to 2.3.7. Good luck.
By the way, you must let it OTA all the way up to 2.3.7 to get the latest Radio and bootloader version.
Giving it a shot now. I'll let you know shortly how it goes.
Update: Same result. All commands completed successfully, but I end up in the Google logo boot loop. Is there a kernel .img file that I should flash, in case my son tried to flash an unsupported kernel?
C:\Program Files\Android\android-sdk\tools>fastboot flash bootloader bootloader
img
sending 'bootloader' (1536 KB)... OKAY
writing 'bootloader'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot reboot-bootloader
rebooting into bootloader... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot flash radio radio.img
sending 'radio' (15232 KB)... OKAY
writing 'radio'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot reboot-bootloader
rebooting into bootloader... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot flash system system.img
sending 'system' (174451 KB)... OKAY
writing 'system'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot flash userdata userdata.img
sending 'userdata' (18796 KB)... OKAY
writing 'userdata'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot flash boot boot.img
sending 'boot' (2904 KB)... OKAY
writing 'boot'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot flash recovery recovery.img
sending 'recovery' (3144 KB)... OKAY
writing 'recovery'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot erase cache
erasing 'cache'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot reboot
rebooting...
C:\Program Files\Android\android-sdk\tools>
That included stock kernel.
Man you might just want to fastboot oem lock and send the phone. Those were factory images... if they don't work it means hw issues.
Sent from my Nexus S 4G using XDA
rasengan82 said:
That included stock kernel.
Man you might just want to fastboot oem lock and send the phone. Those were factory images... if they don't work it means hw issues.
Sent from my Nexus S 4G using XDA
Click to expand...
Click to collapse
I agree. If this does not work, send the phone back to Sprint.
I really appreciate y'all trying to help. I will see if Sprint will be kind enough to exchange it. Thanks again.
trying to flash boot.img even stock boot or patched image but got failed as message partition does not exist. The device is in fastboot mode with unlocked bootloader and rooted.
Tried Flashify, but freeze when tapping on Boot image.
command: fastboot flash boot boot.img
Result:
c:\adb>fastboot flash boot patched_boot.img
sending 'boot' (16852 KB)...
OKAY [ 0.382s]
writing 'boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.387s
Any idea?
Did you solve the problem?
i think you can try https://forum.xda-developers.com/meizu-pro-5/how-to/tutorial-restore-hard-bricked-lost-t3838461
ISCYamil said:
Did you solve the problem?
Click to expand...
Click to collapse
Nope. The reason I want to flash stock boot image or patch boot image because of every time flash new flyme rom via TWRP, the phone always rooted and Magisk is not working to hide root. Now I just use as is. The banking app cannot be working with rooted phone.
hall060679 said:
trying to flash boot.img even stock boot or patched image but got failed as message partition does not exist. The device is in fastboot mode with unlocked bootloader and rooted.
Tried Flashify, but freeze when tapping on Boot image.
command: fastboot flash boot boot.img
Result:
c:\adb>fastboot flash boot patched_boot.img
sending 'boot' (16852 KB)...
OKAY [ 0.382s]
writing 'boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.387s
Any idea?
Click to expand...
Click to collapse
I had the same problem just earlier today. What did the trick for me was installing the ROM using TWRP recovery. Move the stock ROM (you need to zip it for the process) into phone's root directory using your computer and then in TWRP tap on "Install" and find the zipped stock ROM and confirm. Let us know.
try fastboot flash bootimg instead.
I was on MIUI Global 12.0.2 Stable. I tried to flash Pig's latest Lineage (2020.07.21) from TWRP. The flash failed with an "Error 7". When I tried to reboot, the device went to "fastboot" mode.
After that, every attempt of a reboot ended in fastboot mode. So I tried to flash TWRP.img. Flashing went OK. But "fastboot boot twrp.img" gave the error "FAILED (remote: Failed to load/authenticate boot image: Load Error)". The result was same with "fastboot oem reboot-recovery" command.
So I was stuck in fastboot mode with the risk of battery depletion. Below is the commands I ran to flash the TWRP.
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 805306368 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.016s]
writing 'recovery'...
OKAY [ 0.154s]
finished. total time: 2.179s
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 2.016s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 2.046s
C:\adb>
Click to expand...
Click to collapse
SOLUTION: One needs to flash the fastboot ROM in MiFlash.
My situation had an extra issue as there were no fastboot ROM for MIUI Global 12.0.2. So, I downloaded MIUI 11.0.5 Global Fastboot ROM and flashed it. One needs to keep in mind about the "Anti-Rollback Protection" (https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/) and take necessary steps to avoid an anti-rollback brick.
If anti-rollback compatible ROM not available, then just delete first lines in all .bat files (.bat for Windows; .sh for Linux) up to the first line that starts with "fastboot %* getvar product..." of the available fastboot ROM. Those lines are the anti-rollback check. After than you can flash it via MiFlash.
Stillness said:
So I try to flash TWRP.img. Flashing goes OK. But "fastboot boot twrp.img" gives this error "FAILED (remote: Failed to load/authenticate boot image: Load Error)"
Click to expand...
Click to collapse
There is a Fastboot command to reboot to recovery (TWRP if you previously flashed it):
>> fastboot oem reboot-recovery
zgfg said:
There is a Fastboot command to reboot to recovery (TWRP if you previously flashed it):
>> fastboot oem reboot-recovery
Click to expand...
Click to collapse
Thanks for the reply. I tried that command too, but ended with the same error.
Now, downloading the 11.0.5 Global Fastboot ROM since no 12.0.2 Fastboot available. My plan is to just delete first lines in .bat files of the ROM to avoid 'rollback protection' and flash via MiFlash before the battery goes zero. According to google, it seems flashing the full Fastboot ROM is the only solution
SOLVED
Solved. Edited the OP.
zgfg said:
There is a Fastboot command to reboot to recovery (TWRP if you previously flashed it):
>> fastboot oem reboot-recovery
Click to expand...
Click to collapse
Wow, thank you so much for pointing this out!
I just had a close to two hour journey through all emotions after trying to restart my phone and suddenly ending up in a seemingly inescapable fastboot hell...
I've tried booting different recoveries, all failing with
Code:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
and was already at the point of giving up getting my system back, just trying to save my data if possible. Flashing seemed to work, but
Code:
fastboot reboot recovery
just threw me back into fastboot, which I assumed to be due to the phone rejecting the flashed recoveries just as it was rejecting them when I tried to boot them directly.
When I saw this comment I wondered whether Xiaomi implemented rebooting directly to the recovery differently (as it turns out, it doesn't seem to be standardized) and
Code:
fastboot oem reboot-recovery
worked perfectly! After reflashing my ROM from TWRP I was booted back up into my system with everything intact, as if nothing has happened.
Hi All,
I just followed the instructions to root my h918 and then successfully updated to h91820h. I then used the TWRP app to flash twrp, and the Magisk app to update Magisk. After that I rebooted from the Magisk app, and now my phone is stuck in a bootloop. I cannot get into download mode, or recovery mode, or the system. I can get into fastboot mode by trying to go into download mode (holding the volume down and plugginto a USB port ot the laptop.
It seems that T-mobile removed any commands from fastboot that will help me. If I try to "fastboot reboot emergency", it just bootloops. If I try fastboot boot a twrp image, I get:
Code:
fastboot boot twrp-3.4.0-1-h918.img
downloading 'boot.img'...
OKAY [ 0.667s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.686s
The command "fastboot reboot bootloader" boots to fastboot. The bootloader is indeed unlocked, but it looks like I'm stuck, because the LG fastboot doesn't allow anything to fix the brick.
Code:
$ fastboot getvar unlocked
unlocked: yes
finished. total time: 0.020s
I'm not finding any hope or help on Google. It seems if I can't boot into twrp or download mode, I'm toast, and I can't figure out how to boot into anything but the bootloader.
Does anyone have any suggestions on how to bring this phone back from the dead?
Thanks,
Rob
frohro said:
Hi All,
I just followed the instructions to root my h918 and then successfully updated to h91820h. I then used the TWRP app to flash twrp, and the Magisk app to update Magisk. After that I rebooted from the Magisk app, and now my phone is stuck in a bootloop. I cannot get into download mode, or recovery mode, or the system. I can get into fastboot mode by trying to go into download mode (holding the volume down and plugginto a USB port ot the laptop.
It seems that T-mobile removed any commands from fastboot that will help me. If I try to "fastboot reboot emergency", it just bootloops. If I try fastboot boot a twrp image, I get:
Code:
fastboot boot twrp-3.4.0-1-h918.img
downloading 'boot.img'...
OKAY [ 0.667s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.686s
The command "fastboot reboot bootloader" boots to fastboot. The bootloader is indeed unlocked, but it looks like I'm stuck, because the LG fastboot doesn't allow anything to fix the brick.
Code:
$ fastboot getvar unlocked
unlocked: yes
finished. total time: 0.020s
I'm not finding any hope or help on Google. It seems if I can't boot into twrp or download mode, I'm toast, and I can't figure out how to boot into anything but the bootloader.
Does anyone have any suggestions on how to bring this phone back from the dead?
Thanks,
Rob
Click to expand...
Click to collapse
How are you trying to boot into download mode, are you trying to do it via fastboot or the hardware buttons?
frohro said:
Hi All,
I just followed the instructions to root my h918 and then successfully updated to h91820h. I then used the TWRP app to flash twrp, and the Magisk app to update Magisk. After that I rebooted from the Magisk app, and now my phone is stuck in a bootloop. I cannot get into download mode, or recovery mode, or the system. I can get into fastboot mode by trying to go into download mode (holding the volume down and plugginto a USB port ot the laptop.
It seems that T-mobile removed any commands from fastboot that will help me. If I try to "fastboot reboot emergency", it just bootloops. If I try fastboot boot a twrp image, I get:
Code:
fastboot boot twrp-3.4.0-1-h918.img
downloading 'boot.img'...
OKAY [ 0.667s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.686s
The command "fastboot reboot bootloader" boots to fastboot. The bootloader is indeed unlocked, but it looks like I'm stuck, because the LG fastboot doesn't allow anything to fix the brick.
Code:
$ fastboot getvar unlocked
unlocked: yes
finished. total time: 0.020s
I'm not finding any hope or help on Google. It seems if I can't boot into twrp or download mode, I'm toast, and I can't figure out how to boot into anything but the bootloader.
Does anyone have any suggestions on how to bring this phone back from the dead?
Thanks,
Rob
Click to expand...
Click to collapse
im having the same problem, i dont have download more or twrp now, all i have is fastboot
i am going to assume going into download mode through fastboot is the only option for the two people posting for help here. from what i see from the posts, both hardware buttons sequence , or the plug in & down volume are the ONLY way to get to fast boot.
and fast boot is the only thing available on the phone.
i have labeled that a soft brick .
i asume one of the two help seekers have used the magisk 20.2 trap?
the release proved to be a problem , there is a tutorial on how to fix it.
i will go look for that and try to edit it into my responce later.
for now, are the two seekers already acomplished in this procedure?
TWRP Installation Tutorial for Linux Mint and Ubuntu users ยป AndroidGuru.eu
TWRP (Team Win Recovery Project) is an open-source custom recovery image for Android devices. It is a replacement for the stock recovery mode that is installed on most Android devices by the manufacturer. TWRP provides various advanced features and options that are not available in the stock...
www.androidguru.eu
20.2 problem notes and fix
Magisk 20.2 Kills LG V20 (All variants) Boot partition. Reverting to 20.1 fixes issue
So over in the LG V20 forum a lot of people are finding out that installing Magisk 20.2 throws the phone into Fastboot mode. https://forum.xda-developers.com/v20/help/direct-installing-magisk-update-wiped-t4028705...
forum.xda-developers.com
frohro said:
Hi All,
I just followed the instructions to root my h918 and then successfully updated to h91820h. I then used the TWRP app to flash twrp, and the Magisk app to update Magisk. After that I rebooted from the Magisk app, and now my phone is stuck in a bootloop. I cannot get into download mode, or recovery mode, or the system. I can get into fastboot mode by trying to go into download mode (holding the volume down and plugginto a USB port ot the laptop.
It seems that T-mobile removed any commands from fastboot that will help me. If I try to "fastboot reboot emergency", it just bootloops. If I try fastboot boot a twrp image, I get:
Code:
fastboot boot twrp-3.4.0-1-h918.img
downloading 'boot.img'...
OKAY [ 0.667s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.686s
The command "fastboot reboot bootloader" boots to fastboot. The bootloader is indeed unlocked, but it looks like I'm stuck, because the LG fastboot doesn't allow anything to fix the brick.
Code:
$ fastboot getvar unlocked
unlocked: yes
finished. total time: 0.020s
I'm not finding any hope or help on Google. It seems if I can't boot into twrp or download mode, I'm toast, and I can't figure out how to boot into anything but the bootloader.
Does anyone have any suggestions on how to bring this phone back from the dead?
Thanks,
Rob
Click to expand...
Click to collapse
ok i found a way to get into twrp (if ever installed)
1- turn off your phone
2- hold Volume Down + Power button until you see the LG logo
3- When you see the Logo release the power button while still holding the volume down and immediately after release press power button 3 times.
4- you will see a factory reset screen, press yes twice and it will go to twrp.
NOW WE NEED TO FIND A WAY TO FLASH A WORKING ROM THRU TWRP
Hey guys, I need help with this Asus Zenfone 2 Laser that:
Cannot boot to any OS (asus logo pops up, freezes, and then a blue screen flashes for a really short period, before it powers off, see video here.)
Can't download the unlock app to unlock bootloader
Can't access ADB
Cannot access Recovery mode
Can't "factory reset", apply update over ADB, etc.
Bootloader is locked
Can't flash custom recovery, boot TWRP, or really anything...
See fastboot reference below for more info
Code:
$ fastboot boot twrp-3.7.0_9-0-Z00T.img
Sending 'boot.img' (31066 KB) OKAY [ 0.987s]
Booting FAILED (remote: 'unlock device to use this command')
fastboot: error: Command failed
$ fastboot flash recovery twrp-3.7.0_9-0-Z00T.img
Sending 'recovery' (31066 KB) OKAY [ 0.987s]
Writing 'recovery' FAILED (remote: 'Permission denied, phone is protected')
fastboot: error: Command failed
$ fastboot flash boot boot.img # (Original boot.img from factory image)
Warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 17980722).
Sending 'boot' (17559 KB) OKAY [ 1.478s]
Writing 'boot' FAILED (remote: 'Permission denied, phone is protected')
fastboot: error: Command failed
$ fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
$ fastboot oem device-info
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.003s]
Finished. Total time: 0.003s
As someone who has only worked with Google Pixel phones in the past, I'm very frustrated for a few reasons.
Firstly, why the hell is the ONLY WAY to unlock a bootloader through an app that was released in such a clandestine, under-the-table way?
Second, why is the manufacturer gatekeeping the recovery files? The only way I was able to find the stock recovery.img is through a comment on a Reddit post (ironically posted by an ASUS Employee).
Third, I've been scouring the internet for many, many days trying to find any kind of emergency recovery method, but every single tutorial acts on the assumption that the bootloader is unlocked, and that boot.img, recovery.img, etc. can be flashed.
Enough about the frustration. Now let's talk about what I've tried so far.
I tried ASUS Flash Tool (Finding ADB drivers was a whole different fiasco for this device), and came up empty handed, as it doesn't detect the device when in fastboot mode.
I tried using fastboot to flash boot, recovery, system, fastboot, and dnx/ifwi, to no avail.
I tried booting into recovery via `fastboot reboot recovery`, `fastboot reboot-recovery`, `fastboot oem reboot-recovery`, and by holding Vol Down while booting up. They all give the same result, which is just an instant (<1 second) reboot. My best guess is that recovery.img is either missing or badly corrupt, so the bootloader just gives up and exits immediately.
Please help. I don't want an expensive paperweight sitting in my drawer just because of a bootloop that wasn't my fault (seriously this device just bootlooped itself one day, I didn't flash a custom rom, root or anything like that).
Any help is appreciated,
Thanks in advance
you can flash on locked bootloader in EDL mode. search in the forum, don't hesitate to ask for clarity on search results. I give you a starting point.
(don't read the whole thread, it will only confuse you)
https://forum.xda-developers.com/t/...image-dump-file-raw-bin.4543217/post-88139417
alecxs said:
you can flash on locked bootloader in EDL mode. search in the forum, don't hesitate to ask for clarity on search results. I give you a starting point.
(don't read the whole thread, it will only confuse you)
https://forum.xda-developers.com/t/...image-dump-file-raw-bin.4543217/post-88139417
Click to expand...
Click to collapse
Probably a dumb question, but how can I put my device into EDL mode?
I've tried many key combinations in conjunction with plugging it into the computer, and I've tried connecting it without a battery.
if nothing else works you need to figure out test points
https://forum.xda-developers.com/t/...ed-to-unlock-bootloader.4531349/post-87944673
you still have fastboot? try this for EDL mode.
Code:
fastboot oem enter-dload
Good news and bad news. Good news is: I was able to enter EDL mode.
Bad news is, apparently my entire partition scheme was messed up, and upon running "edl w gpt gptboth0.bin", fastboot no longer works.
I have tried flashing aboot using edl ("edl w aboot emmc_appsboot.mbn") and it's not working.
Not to mention that it is almost impossible to find the firmware file with all the factory files such as "emmc_appsboot.mbn". The place where I got my file seemed very sketchy and I'm not surprised if the reason it's not working is because it's the wrong file.
Once again, this is a result of ASUS gatekeeping their recovery files to service centers to drive up repair sales.
If anyone has a link, or would like to provide a donor file, it would be VERY much appreciated.
what is inside official download?
https://www.asus.com/supportonly/asus zenfone 2 laser (ze551kl)/helpdesk_bios
alecxs said:
what is inside official download?
https://www.asus.com/supportonly/asus zenfone 2 laser (ze551kl)/helpdesk_bios
Click to expand...
Click to collapse
So yes, I was able to get fastboot back. However, I am now facing another issue.
In order to get fastboot back, I had to run this command
Bash:
edl qfil rawprogram0.xml patch0.xml image_dir
This seemed fine at first, but now, running "edl printgpt" returns nothing. Somehow, the phone is able to boot to fastboot without any GPT partitions visible.
However, when I try to flash gpt_main0, or gpt_both0, the phone now becomes unbootable.
This means, if I try to create a partition table to flash recovery onto, appsboot (and by extension, fastboot) no longer works.
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (18115 KB) OKAY [ 0.581s]
Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
fastboot: error: Command failed
"partition table doesn't exist"
If I try to create the partition table, the phone refuses to boot...
OS were
sj-dan said:
So yes, I was able to get fastboot back. However, I am now facing another issue.
In order to get fastboot back, I had to run this command
Bash:
edl qfil rawprogram0.xml patch0.xml image_dir
This seemed fine at first, but now, running "edl printgpt" returns nothing. Somehow, the phone is able to boot to fastboot without any GPT partitions visible.
However, when I try to flash gpt_main0, or gpt_both0, the phone now becomes unbootable.
This means, if I try to create a partition table to flash recovery onto, appsboot (and by extension, fastboot) no longer works.
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (18115 KB) OKAY [ 0.581s]
Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
fastboot: error: Command failed
"partition table doesn't exist"
If I try to create the partition table, the phone refuses to boot...
Click to expand...
Click to collapse
So we're you able to find a fix in any way? I find myself in just about the same situation tho for different reasons. I have a radiant max 5g att device i moronicaly tried to download a gsi using the dsu updater, but forgot to unlock bootloader or even enable USB debugging before attempt. So OS system is crashing an saying 'device corrupted' on boot attempt. Recovery mode gets the same result. Was able to use the bugjaegar app to connect ad run the bootloader but every repair attempt is blocked by the fact the USB debugging isn't on. To make matters worse I accidentky hit boot fastbootd command instead of normal and whatever that did wiped out my ability to even connect with bootloader so I'm kind of stuck.
faisaliteb said:
Mod. edit: spammer gone. alecxs
I found many tutorials about fixing bootloops on the Nexus but they all seem to require an unlocked bootloader.
The bootloader on the device is locked. I can see the device in fastboot devices but I can't unlock it.
Any idea how to repair this? Can I somehow flash a factory image onto the device even though OEM unlock is disabled? There is no data on the device that would need to be preserved. I'm ideally looking for a Linux-based solution. more info... ***
Click to expand...
Click to collapse
Yeah man I've been looking at this problem for over a week now and can't find much online at all to help. Except for this EDLmode some devices can boot into, and apparently you can flash a locked system using this emergency download mode. I dunno still researching.