Related
I have read the guide and searched for 5 hours and still can't find an answer.
I have a windows 7 computer with the SDK and all drivers installed properly and have both the factory images downloaded from Google. The extracted factory image has been placed in my SDK folder platform-tools. I have been trying to flash the bootloader via fastboot commands. The computer recognizes the nexus 7 and gives me the proper serial number when I do "fastboot devices". I then run through all the commands in the "Guide flashing a factory image", fastboot erase boot, fastboot erase cache, fastboot erase recovery, fastboot erase system, fastboot erase userdata and see that all the commands finish. When I get to fastboot flash bootloader bootloader-grouper-4.13.img the command prompt just hangs and does nothing. In the upper left corner of the Nexus 7 I see signature match but the command line reads sending 'bootloader' <2096 KB>...
OKAY [ 0.265s]
writing 'bootloader'....
I am lost as to what to do. Should I try the command fastboot reboot-bootloader even though I may not have properly flashed the bootloader.img????
Thanks for any help, I have been playing with this since yesterday.
Why did you erase cache, system, recovery etc? Weren't you just updating your hboot?
Usualy not wise to loose power while updating firmware, but if you've been at it for a day you soon will as I don't believe you can charge through bootloader mode.
When flashing through fastboot the update won't take effect until you reboot, if its hung for a while (I mean a real long while as this may not be safe) why not unplug usb, replug, then fastboot flash a recovery quick.
Now get a new download of whatever spl you can find with md5sums. Download and make sure the md5 matches
Now flash that hboot and see what happens
Sent from my HTC Vision using xda premium
I read a lot about problems with that 4.xx bootloader.
Try flashing one of the 3.xx bootloaders from 4.1.x factory images.
Hello,
So I decided to unlock and root my Pure today. Originally I was going to flash Lineage, but I later decided not to. Anyway, I was following the instructions here.
So I unlocked and installed TWRP succesfully. Then I decided to root. And that's where I screwed up.
Following these instructions, I now have a phone that won't boot past the "M" logo. Apparently my mistake was not using the current SU version.
I have been Googling for an hour now, but almost every solution I've come across has involved plugging the phone into the computer. My issue is that my computer isn't recognizing the phone when I plug it in, so my knowledge of how to fix this is limited (and my expertise in this topic was minimal to begin with...). I can get to recovery mode, and have tried a factory reset. No dice. I also put the latest official factory image from Motorola on the SD card, but when I went to install it, it wouldn't show up.
As you can tell I am quite stuck here. I haven't tried to root a phone since my Incredible back in the day. Any help would be greatly appreciated.
Thanks!
Did you use TWRP to make a nandroid backup before attempting to root? If so, just restore it.
If not, you're going to have to either fastboot flash it back to stock. More info in the firmware thread.
Or you could give a custom rom, or this TWRP flashable stock rom a try. I've never used the TWRP flashable stock rom, but it might be an easy way out of your predicament if you aren't comfortable and familiar with fastboot and want to stay stock.
For future rooting attempts of the stock rom I'd recommend Magisk. It always works systemless, so there's no need to force it to install systemless like SuperSU. Just flash the zip in recovery and install the Magisk manager from the Play Store and you're rooted. No more soft bricks.
jason2678 said:
Did you use TWRP to make a nandroid backup before attempting to root? If so, just restore it.
If not, you're going to have to either fastboot flash it back to stock. More info in the firmware thread.
Or you could give a custom rom, or this TWRP flashable stock rom a try. I've never used the TWRP flashable stock rom, but it might be an easy way out of your predicament if you aren't comfortable and familiar with fastboot and want to stay stock.
For future rooting attempts of the stock rom I'd recommend Magisk. It always works systemless, so there's no need to force it to install systemless like SuperSU. Just flash the zip in recovery and install the Magisk manager from the Play Store and you're rooted. No more soft bricks.
Click to expand...
Click to collapse
Ok, first, thanks for the response.
I think somehow I didn't actually install TWRP. Not sure how.
I followed that thread link and tried everything, but to no avail. Maybe I was doing it wrong? I did this:
- Downloaded everything under "6.0 MPH24.49-18 FIRMWARE"
- Put it on my SD card
- Booted into recovery
- Selected Install from SD Card
And there was nothing listed. I tried the same with the "6.0 MPH24.49-18-3 FIRMWARE".
I also did the "AutoFlashFirmwareScript", but I'm assuming that didn't work since I can't turn on USB Debugging. Is there a possibility I somehow wiped the entire OS and there isn't anything to boot into?
bootloopohgod said:
Ok, first, thanks for the response.
I think somehow I didn't actually install TWRP. Not sure how.
I followed that thread link and tried everything, but to no avail. Maybe I was doing it wrong? I did this:
- Downloaded everything under "6.0 MPH24.49-18 FIRMWARE"
- Put it on my SD card
- Booted into recovery
- Selected Install from SD Card
And there was nothing listed. I tried the same with the "6.0 MPH24.49-18-3 FIRMWARE".
I also did the "AutoFlashFirmwareScript", but I'm assuming that didn't work since I can't turn on USB Debugging. Is there a possibility I somehow wiped the entire OS and there isn't anything to boot into?
Click to expand...
Click to collapse
okay so you are wrong here..
firmware needs to be flashed via fastboot they are not available in flashable zips they are .xml file.. you need to follow the instructions given here
https://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
or if you want latest firmware of any version of style or pure
download from here
https://firmware.center/firmware/Motorola/
and follow the same instructions given in the first link
hope this helps
Sagar_1401 said:
okay so you are wrong here..
firmware needs to be flashed via fastboot they are not available in flashable zips they are .xml file.. you need to follow the instructions given here
https://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
or if you want latest firmware of any version of style or pure
download from here
https://firmware.center/firmware/Motorola/
and follow the same instructions given in the first link
hope this helps
Click to expand...
Click to collapse
This definitely seems helpful, but when I tried it gave me a bunch of Failures.
For "fastboot flash partition gpt.bin":
Code:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.382s
And then a Failure for every command from "fastboot flash boot boot.img" to "fastboot flash system system.img_sparsechunk.8" (the build I used doesn't have sparsechunk 9 or else I'd assume that would have been a failure as well). It is encouraging to know I can at least somewhat communicate with the phone, for some reason yesterday I couldn't even do that.
bootloopohgod said:
This definitely seems helpful, but when I tried it gave me a bunch of Failures.
For "fastboot flash partition gpt.bin":
Code:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.382s
And then a Failure for every command from "fastboot flash boot boot.img" to "fastboot flash system system.img_sparsechunk.8" (the build I used doesn't have sparsechunk 9 or else I'd assume that would have been a failure as well). It is encouraging to know I can at least somewhat communicate with the phone, for some reason yesterday I couldn't even do that.
Click to expand...
Click to collapse
ignore that partition error
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
make sure
while flashing NON-HLOS.bin you might get error
dont worry
when you reach that step do type it again when you see that error and it'll successful flash the NON-HLOS.bin which is your main step for your modem
im sure this will 100% work
edit: all the files have different no of system system.img_sparsechunk
if you are flashin sept patch it should have 8 i assume but if you just type system system.img_sparsechunk.9 it'll say file not found u won't encounter any error by that
hello friends I have the motorola g5 plus xt1680 by telcel. I have the bootloader blocked and I also have many files in memory that I do not want to lose.
I got a security patch which I downloaded and installed correctly, after updating my mistake I let the cell phone completely discharge, reaching the battery at 0%, after this I can not turn on the device stays in the motorola logo.
I have already tried to flash firmwares using adb but I can not mark me error, errors similar to this one:
fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ -0.000s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling
gpt.default.xml
FAILED (remote failure)
finished. total time: 0.066s
for more than download firmware images, all of them make me the same error and I can not find the solution on the internet.
I have been several days and can not find a solution, it is very important not to lose my files that I have on my cell phone.
Would any of you help me please?
Have u tried using the Moto Smart Assist to reflash the phone? It should automatically detect the correct firmware for you.
But if you want to flash one of the firmwares you have, leave out the "fastboot flash partition gpt.bin" and "fastboot flash bootloader bootloader.img" commands and the flash should work fine. Apparently the update you took updated the partition tables on your device so you either have to flash without downgrading or flash using the exact firmware that the gpt.bin file is using.
If you need to get your files off first, download TWRP here, and then copy it into the directory where you have fastboot and run
"fastboot flash recovery twrp-3.2.3-1-potter.img" and then scroll down with the vol keys until you get reboot to recovery. (If it doesn't flash correctly you may have to push vol key down to reboot bootloader and try flash again) After inside TWRP, you should be able to use your password to decrypt your data and then use a USB cable to get your things off the phone or take a TWRP backup of your data / internal storage partitions and restore those after a fresh flash.
Drkmatr1984 said:
Have u tried using the Moto Smart Assist to reflash the phone? It should automatically detect the correct firmware for you.
But if you want to flash one of the firmwares you have, leave out the "fastboot flash partition gpt.bin" and "fastboot flash bootloader bootloader.img" commands and the flash should work fine. Apparently the update you took updated the partition tables on your device so you either have to flash without downgrading or flash using the exact firmware that the gpt.bin file is using.
If you need to get your files off first, download TWRP here, and then copy it into the directory where you have fastboot and run
"fastboot flash recovery twrp-3.2.3-1-potter.img" and then scroll down with the vol keys until you get reboot to recovery. (If it doesn't flash correctly you may have to push vol key down to reboot bootloader and try flash again) After inside TWRP, you should be able to use your password to decrypt your data and then use a USB cable to get your things off the phone or take a TWRP backup of your data / internal storage partitions and restore those after a fresh flash.
Click to expand...
Click to collapse
thanks, I had already tried to revive my phone with moto smart assist but the software tells me that my phone is not compatible.
I can install twrp if I have the bootloader blocked or I need to open the bootloader to use twrp? but when I open the bootloader my phone restarts from the factory that will erase all my files
I think I've already got the most recent security patch that is updated, apparently this is:
https://mega.nz/#!jxUEXazJ!TVU8n458ZZwd5TfP12I_uEvslYgGc5vakyUaOeSqMOs
can I install that version on my cellphone without any risk ?
then I can flash it without losing my data by omitting the command fastboot erase userdata or is it more advisable to use the ocpion of twrp to recover my data as you explain my friend?
Thank you very much for the help
Well, if the bootloader is locked, then you can't flash TWRP until you unlock it, which you can't do because you can't get into the system to enable OEM unlocking from developer options. So you're pretty limited to what you can do...
I believe fastboot flashing everything using the exact same firmware as your most recent update, but omitting the gpt.bin, bootloader, and userdata commands would work.
I tried to flash the last ota for the motorola g5 plus and now I can install almost everything but when it comes time to flash the following commands it marks me error:
fastboot erase customize
fastboot erase logo
and now how do I fix that I reboot the device and it keeps giving me boot on the motorola logo
c:\Herramientas ADB\platform-tools>fastboot erase customize
erasing 'customize'...
bootloader Permission denied
FAILED remote failure
finished. total time: 0.006s
c:\Herramientas ADB\platform-tools>fastboot erase clogo
erasing 'clogo'...
bootloader Permission denied
FAILED remote failure
finished. total time: 0.005s
and now how can I solve that someone help me
july48 said:
I tried to flash the last ota for the motorola g5 plus and now I can install almost everything but when it comes time to flash the following commands it marks me error:
fastboot erase customize
fastboot erase logo
and now how do I fix that I reboot the device and it keeps giving me boot on the motorola logo
c:\Herramientas ADB\platform-tools>fastboot erase customize
erasing 'customize'...
bootloader Permission denied
FAILED remote failure
finished. total time: 0.006s
c:\Herramientas ADB\platform-tools>fastboot erase clogo
erasing 'clogo'...
bootloader Permission denied
FAILED remote failure
finished. total time: 0.005s
and now how can I solve that someone help me
Click to expand...
Click to collapse
Why don't use ADB pull command to pull the data from device and run the all command of flashing except bootloader and gpt.
riyan65 said:
Why don't use ADB pull command to pull the data from device and run the all command of flashing except bootloader and gpt.
Click to expand...
Click to collapse
I think the problem is he can't get past bootloader so no ADB commands for him to have access to, and his bootloader is locked and since his system won't boot he can't turn on OEM unlocking to unlock it to flash TWRP or something similar to give him ADB commands.
july48 said:
I tried to flash the last ota for the motorola g5 plus and now I can install almost everything but when it comes time to flash the following commands it marks me error:
fastboot erase customize
fastboot erase logo
and now how do I fix that I reboot the device and it keeps giving me boot on the motorola logo
c:\Herramientas ADB\platform-tools>fastboot erase customize
erasing 'customize'...
bootloader Permission denied
FAILED remote failure
finished. total time: 0.006s
c:\Herramientas ADB\platform-tools>fastboot erase clogo
erasing 'clogo'...
bootloader Permission denied
FAILED remote failure
finished. total time: 0.005s
and now how can I solve that someone help me
Click to expand...
Click to collapse
Your problems are not related to the errors for "customize" and "clogo". These entries are for customazions made by Moto Maker and it's normal that they fail if you don't have any of these.
If your device doesn't boot you may have downgraded your bootloader in the past.
I have already tried to omit the bootloader and gpt commands, and I still have the same problems only in that part of the code, having the bootloader blocked limits me a lot, I do not know if I have to wait for the firmware of my phone company Telcel to flash it by adb and see if only so I retrieve the phone.
I do not know what else to try if there is any other solution
july48 said:
I have already tried to omit the bootloader and gpt commands, and I still have the same problems only in that part of the code, having the bootloader blocked limits me a lot, I do not know if I have to wait for the firmware of my phone company Telcel to flash it by adb and see if only so I retrieve the phone.
I do not know what else to try if there is any other solution
Click to expand...
Click to collapse
If you have the most recent firmware you don't need to omit the bootloader and gpt commands, and the clogo and customize commands almost always fail, you don't even really need them.
If it's still not booting I'm not sure what else to tell you to try. Someone in another one of my posts suggested trying to boot with "fastboot boot boot.img" and then possibly you could switch on OEM unlocking from the developer options, then reboot, unlock bootloader, and flash again or flash TWRP and use recovery to recover from there.
But I'm not guaranteeing that will do anything other than be stuck at boot logo.
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.
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.