Related
So, got a problem with my m8
my m8 is the international unlocked version from amazon, 2 months old.
no root, no s-off, just stock with the last update from htc (4.4.3 i think)
last night, went to sleep, and charge my phone with 20% battery, then this morning when i woke up, the phone was in this screen:
replace the .
h.ttp://i.imgur.com/yYoTilH.jpg
Tried to reboot but with no luck, at the same menu i entered to hboot and some lines with "not found" (like 4-5 files) appeared on the screen, then in the new menu, i tried to enter the recovery menu, no luck and went back to fastboot menu, factory reset, no luck too.
After trying all of the menu options with no luck, i tried to use the fastboot to flash an stock image of the recovery, but always getting a signature verification failed.
Tried to flash the stock roms from here, but also the same error (signature verification failed)
So, if someone knows something to help me, please do
You cannot flash anything if boot loader is locked or you don't have s-off
Open on your pc where adb and fastboot files are a command window when the phone is connected to pc and type on fastboot erase cache...see if something happens and if it worked reboot it
One-M8-Master said:
You cannot flash anything if boot loader is locked or you don't have s-off
Open on your pc where adb and fastboot files are a command window when the phone is connected to pc and type on fastboot erase cache...see if something happens and if it worked reboot it
Click to expand...
Click to collapse
Code:
erasing 'cache'...
OKAY [ 0.003s]
finished. total time: 0.003s
worked (i think), but after reboot, stuck at fastboot again
guess ill have to take it to technical service
Hey guys !
So since i messed up with the recovery mode, i'm stucked in the fastboot with no Download mode (recovery doesnt work neither).
So after searching 3 days in the internet i found the acces to fast through adb by puting a new laf.img in order to restore the download mode and flash a stock firmware !
My problem is that when i try to enter the command on the cmd, i get severals errors, take a look :
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: device not found
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase laf
erasing 'laf'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.034s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash laf laf.img
target reported max download size of 2147483648 bytes
sending 'laf' (18432 KB)...
OKAY [ 0.581s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.615s
Also command : "fastboot boot laf.img" result to "Failed(remote: dtb not found) instead of flash write failure..
Of course i have my G3 855 32GB in download mode (but it goes into fastmode), so when i try a command, lines are added in the screen etc..
Does that mean that my laf.img don't work? I assumed that so i try several, but does it have to be the exact same one as the one who was in my phone before( v20a if i record correctly ) or could it be from any 855 32GB version ?
I also thought it could be a recognition problem as when i type "adb devices" or "adb shell" nothing is found..
If someone has any clue or a link to some guide i'll be more than joyful, thanks in advance !
Try adb fastboot when writing command hope it helps
Anik49 said:
Try adb fastboot when writing command hope it helps
Click to expand...
Click to collapse
Hey thank you so much for answering !
What do you mean by that, i already download the adb/fastboot driver and launch a cmd in the directory they are at, writing "adb fastboot" has no result neither, can you be more specific please ?
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again: http://open-freax.fr/guide-unbrick-your-lg-g3/
BigsyBiggins said:
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again:
Click to expand...
Click to collapse
Well i hope my problem can be solved in a safer way, i dont like much to go on the hardware part, so I'll use it as my last hope, but thanks
Altought i think my device is recognized by fastboot in someway because it responds when i type commands in fastboot, and also when i reboot it.
But i'm getting this error :
Code:
error : command never completed
error : auto CMD12 error
error : command completed with errors
error : command timeout error
failed to send stop command
failed writing block @ 1
in the screen of my phone. Does that stand for Cyanogen mode which i was trying to put on my phone ?
I mean when you enter command in cmd use adb before any command also use cmd which one available on android sdk folder....also you can use this method if adb not workinhg properly http://forum.xda-developers.com/lg-g...-9008-t3072091
BigsyBiggins said:
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again: http://open-freax.fr/guide-unbrick-your-lg-g3/
Click to expand...
Click to collapse
Like @BigsyBiggins said, this is the guide which could fix your phone. HW Part is not too hard!
Anik49 said:
I mean when you enter command in cmd use adb before any command also use cmd which one available on android sdk folder....also you can use this method if adb not workinhg properly
Click to expand...
Click to collapse
Oh ok ! Also your link is not working :s
I understand that the method can work but I think that the method i'm trying to use is really close to succeed, over my search on the internet, i saw lots of people who manage to succeed with it.
But i guess i must do something wrong. I downloaded the kdz file according to my IMEI.
Then I extracted the .dz file with LG Firmware Extract. Then I extracted the file named laf_393216.bin from the dz file. Changed his name into laf.img , put it into the fastboot directory.
Then i typed
Code:
fastboot format cache
fastboot erase laf
fastboot flash laf laf.img
in a cmd from the directory.
It all seemed to work, but then when i remove the battery and restart into download mode, it goes into fastboot after the download mode charging animation..
Also when i try to boot with fastboot boot laf.img i get the error (remote: dtb not found) on the cmd.
And ERROR: Unable to find suitable device tree for device(194/0x0001001/112/0) ERROR: getting device tree adress failed DTB offset is incorrect, kernel image does not have appended DTB)
Am I doing something wrong, should I changed more file than just laf ?
SisGG said:
Oh ok ! Also your link is not working :s
I understand that the method can work but I think that the method i'm trying to use is really close to succeed, over my search on the internet, i saw lots of people who manage to succeed with it.
But i guess i must do something wrong. I downloaded the kdz file according to my IMEI.
Then I extracted the .dz file with LG Firmware Extract. Then I extracted the file named laf_393216.bin from the dz file. Changed his name into laf.img , put it into the fastboot directory.
Then i typed
Code:
fastboot format cache
fastboot erase laf
fastboot flash laf laf.img
in a cmd from the directory.
It all seemed to work, but then when i remove the battery and restart into download mode, it goes into fastboot after the download mode charging animation..
Also when i try to boot with fastboot boot laf.img i get the error (remote: dtb not found) on the cmd.
And ERROR: Unable to find suitable device tree for device(194/0x0001001/112/0) ERROR: getting device tree adress failed DTB offset is incorrect, kernel image does not have appended DTB)
Am I doing something wrong, should I changed more file than just laf ?
Click to expand...
Click to collapse
I don´t know what exactly is the problem, maybe something with your win-driver, some crashed or drifted partitions or some broken files...
I just can repeat my advice: I was in the same situation with my phone after a failed cm13 update and i was trying and reading about 2 days how to solve it - after the above mentioned method, your phone would get out of this "coma".
Maybe somebody else here in this forum could help you with your mentioned method, sorry.
Ernesto0023 said:
I don´t know what exactly is the problem, maybe something with your win-driver, some crashed or drifted partitions or some broken files...
I just can repeat my advice: I was in the same situation with my phone after a failed cm13 update and i was trying and reading about 2 days how to solve it - after the above mentioned method, your phone would get out of this "coma".
Maybe somebody else here in this forum could help you with your mentioned method, sorry.
Click to expand...
Click to collapse
Well I think i'm still under warranty, so i dont wanna touch to much on the hardware.
So do you think, if i send it back without touching anything, saying i put it on charge one night and the next morning it was like this, the warranty could work?
If they found it's rooted or they understand you did something with your software your warrenty is void ?
SisGG said:
Well i hope my problem can be solved in a safer way, i dont like much to go on the hardware part, so I'll use it as my last hope, but thanks
Altought i think my device is recognized by fastboot in someway because it responds when i type commands in fastboot, and also when i reboot it.
But i'm getting this error :
Code:
error : command never completed
error : auto CMD12 error
error : command completed with errors
error : command timeout error
failed to send stop command
failed writing block @ 1
in the screen of my phone. Does that stand for Cyanogen mode which i was trying to put on my phone ?
Click to expand...
Click to collapse
Remove the battery, put it, press the volume + and connect to PC USB, if like entering download, what happens to us not to go, will leave the ****ing LoGo, Well, hold down the volume + and not let go, I think it is less for 2 minutes more. After a while, the computer tells us that something was connected, the phone will tell you who is in fastboot as I said before, if not let me fastboot flash boot files and the LAF, recovery ect, nothing happens, there is still a magic command.
fastboot boot laf.img
Keep it in the ****ing heart
miguexneox said:
Remove the battery, put it, press the volume + and connect to PC USB, if like entering download, what happens to us not to go, will leave the ****ing LoGo, Well, hold down the volume + and not let go, I think it is less for 2 minutes more. After a while, the computer tells us that something was connected, the phone will tell you who is in fastboot as I said before, if not let me fastboot flash boot files and the LAF, recovery ect, nothing happens, there is still a magic command.
fastboot boot laf.img
Keep it in the ****ing heart
Click to expand...
Click to collapse
I dont quite understand what u meant there :s
I already have acces on the fastboot, actually now, my phone goes instantly on fastboot whatever i do.. Though i cannot boot a laf.img downloaded and flashed .. :'(
SisGG said:
I dont quite understand what u meant there :s
I already have acces on the fastboot, actually now, my phone goes instantly on fastboot whatever i do.. Though i cannot boot a laf.img downloaded and flashed .. :'(
Click to expand...
Click to collapse
were u able to resolve this issue. I am in your shoes at the moment.
I have tried the qualcomm. The drivers doesnt seem to work for my phone .
I can't flash or the laf.img . the fastboot commands doesnt seem to work.
and I'm stuck in fastboot .
What can be done
datrmon said:
were u able to resolve this issue. I am in your shoes at the moment.
I have tried the qualcomm. The drivers doesnt seem to work for my phone .
I can't flash or the laf.img . the fastboot commands doesnt seem to work.
and I'm stuck in fastboot .
What can be done
Click to expand...
Click to collapse
You have several options:
- find your phone firmware, extract recovery.img and flash it back through fastboot(do exactly the same for the LAF partition to restore download mode)
- flash a custom recovery for your phone model, if it doesn't work try an older version of TWRP, also it can be that your phone is not d855 but d850 model, so try to flash a d850 custom recovery and see if it works(that was exactly my problem and why i got stuck in fastboot mode, because my phone is d850 model and in settings it says d855, so I flashed wrong TWRP)
Ghikya said:
You have several options:
- find your phone firmware, extract recovery.img and flash it back through fastboot(do exactly the same for the LAF partition to restore download mode)
- flash a custom recovery for your phone model, if it doesn't work try an older version of TWRP, also it can be that your phone is not d855 but d850 model, so try to flash a d850 custom recovery and see if it works(that was exactly my problem and why i got stuck in fastboot mode, because my phone is d850 model and in settings it says d855, so I flashed wrong TWRP)
Click to expand...
Click to collapse
Thanks for the response .
I am unable to flash files at all.
This is the error
D:\mfastboot-v2>fastboot flash laf laf.img
target max-download-size: 2048MB
sending 'laf' (18432 KB)...
OKAY [ 0.646s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.726s
D:\mfastboot-v2>
datrmon said:
Thanks for the response .
I am unable to flash files at all.
This is the error
D:\mfastboot-v2>fastboot flash laf laf.img
target max-download-size: 2048MB
sending 'laf' (18432 KB)...
OKAY [ 0.646s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.726s
D:\mfastboot-v2>
Click to expand...
Click to collapse
It seems that your phone's bootloader is locked, you can try to execute this command: "fastboot oem unlock", and then check state with "fastboot oem device-info". But some people says that it does nothing, so you can try and check for yourself.
You can also try to boot directly an image from fastboot for eaxmple:
Code:
fastboot boot laf.img
or
Code:
fastboot boot twrp.img
So if you could successfully boot a laf image you would be able to access download mode, and if you could boot a custom recowery then you could access ADB and to try to flash other partitions, or even flash a custom rom...
Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"
Fixed flashing error "remote: unsupported command" when flashing a Pixel C back to stock
I used TWRP and SuperSU to root and modify the buildprops to enable and get an early look at the windowing in Android N beta on my Pixel C release 5 ahead of time.
When Release 5 NPD90G was available I decided to flash back to stock from Developer Preview 4 NPD56N rooted with SuperSU and flashed with TWRP. I like root - I run Ubuntu and Win 7. I don't mind running a rooted device if it doesn't have all my work and financial data. When the final N release is out, the Pixel C will become my work machine. It's almost there.
I'm naturally paranoid. I change my long passwords frequently and use 2 factor authentication for everything. So if I can, I'll take a stock release. See my instructions for wiping Android devices: How to wipe an Android Phone: the paranoid editon
I could not flash the NPD90G stock bootloader because of an error "remote: unsupported command"
Here's how I fixed it.
Updated the SDK manager including SDK Tools and USB drivers.
With the Pixel C in recovery mode, {hold the power key and volume down}
In TWRP mount System and reboot to recovery
>ADB Shell.
From ADB Shell I ran
>fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable Fast boot.
Then I changed from TWRP to Fastboot mode {power button plus hold the volume up button}
>fastboot erase userdata
>fastboot erase boot
>fastboot erase cache
>fastboot erase recovery
>fastboot erase system
See Note 1. Below
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
Note 1.
The first time through I flashed the following line items which resulted in the resting robot Andi. I don't think I needed to do this, but if the above instructions don't work, run the following before continuing for {flash bootloader bootloader-dragon-google_smaug.7900.27.0.img}
>flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot reboot-bootloader
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
>fastboot flash cache cache.img
Twrp can't flash
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command
Tugio said:
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command
Click to expand...
Click to collapse
When in fastboot mode, use:
Code:
fastboot boot twrp-local-file-on-computer.img
DanBUK said:
When in fastboot mode, use:
Click to expand...
Click to collapse
It's nice of you to help a fellow XDA user. But I suspect he's already solved his problem of three months ago.....
Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards
lllopa said:
Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards
Click to expand...
Click to collapse
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Make sure you have the latest version of fastboot and adb. I get these errors almost every month if I don't update.
https://developer.android.com/studio/releases/platform-tools.html
@stevep2007, thank you so much! I've been dealing with this "remote: unsupported command" nonsense for days now after trying to revert back to an older Oreo version of Lineage. This did the trick!
How can I solve the problem when my Pixel C is not unlocked? My Pixel made an update and after installing the Update I got the green little man. Now I have no Chance to activate USB debugging etc. Its also not possible to install twrp.img
How can I go to ADB shell with locked bootloader? Or isn't it possible?
Fastboot devices shows me my tablet. ADB devices also show my tablet with "sideload".
But every try to flash my Pixel fails. I alway get the message .... remote: unknown command.......fastboot error: command failed
flash-all.bat showes that all "*.img are missing" error: command failed... unknown command etc.......
So any idea to get my Pixel working again? ADB shell would make it I think. But how with locked bootloader.
_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
This did it for me!! Thanks much. I also updated platform-tools at the same time, who knows which did it
_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions
bernardomarx said:
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions
Click to expand...
Click to collapse
Sorry replied incorrectly
I have struggled to fix my bootlooping problem , After install LOS rom/ other rom and flashing the Magisk. Everything installed fine, but for some reason, after restarting the system it will get to LOS loading screen and bootloop. I attempted to install a stock rom on it, but that load fine but it WIFI and Cellular Network doesn't work. The boot loader has been unlocked Any detail instruction will be highly appreciated. Thanks
Background info, I have spent more than 1 years using this awesome phone with Lineage OS 15.1 , I wake up one morning with the constantly boot looping. I have the T-Mobile version with the bootloader unlocked. I have also spent weeks going through and following other threads but haven't been able to resolved my issue.
sammd301 said:
I have struggled to fix my bootlooping problem , After install LOS rom/ other rom and flashing the Magisk. Everything installed fine, but for some reason, after restarting the system it will get to LOS loading screen and bootloop. I attempted to install a stock rom on it, but that load fine but it WIFI and Cellular Network doesn't work. The boot loader has been unlocked Any detail instruction will be highly appreciated. Thanks
Background info, I have spent more than 1 years using this awesome phone with Lineage OS 15.1 , I wake up one morning with the constantly boot looping. I have the T-Mobile version with the bootloader unlocked. I have also spent weeks going through and following other threads but haven't been able to resolved my issue.
Click to expand...
Click to collapse
Whenever you move from custom to stock and vice versa you should format user data. Easiest way is in bootloader mode, issue the command 'fastboot -w' w/o quotes.
41rw4lk said:
Whenever you move from custom to stock and vice versa you should format user data. Easiest way is in bootloader mode, issue the command 'fastboot -w' w/o quotes.
Click to expand...
Click to collapse
I applied the "fastboot -w" below is the output I got; Still no WIFI and Cellular network not working
-------------------------------------------------------------
PS C:\adb> fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type not supported.
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.005s
-------------------------------------------------
sammd301 said:
I applied the "fastboot -w" below is the output I got; Still no WIFI and Cellular network not working
-------------------------------------------------------------
PS C:\adb> fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type not supported.
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.005s
-------------------------------------------------
Click to expand...
Click to collapse
Do you have an imei number still? Is the bootloader still unlocked? Have you tried following the return to stock thread and doing a clean install of the latest TMO firmware?
41rw4lk said:
Do you have an imei number still? Is the bootloader still unlocked? Have you tried following the return to stock thread and doing a clean install of the latest TMO firmware?
Click to expand...
Click to collapse
The IMEI number is “Unknown” , Yes the bootloader is Unlocked because, I am able to flash TWRP image on the phone. Yes I spent close to a week following the return to stock thread, the first time I did it, the Cellular network come on about 30 minutes after the phone completed loading to the home screen. Thanks for the guidance
You need to blankflash, then flash the latest TMO firmware for your phone. Usually you lose baseband when you flash the wrong firmware, does it say XT1789-04 by the usb port?
sammd301 said:
The IMEI number is “Unknown” , Yes the bootloader is Unlocked because, I am able to flash TWRP image on the phone. Yes I spent close to a week following the return to stock thread, the first time I did it, the Cellular network come on about 30 minutes after the phone completed loading to the home screen. Thanks for the guidance
Click to expand...
Click to collapse
I would go through the unlock process again. Your bootloader shows flashing_locked
Uzephi said:
I would go through the unlock process again. Your bootloader shows flashing_locked
Click to expand...
Click to collapse
I follow the procedure to unlocked the bootloader again, it now shows "flashing_unlocked" as show in the photo below; I flashed another oem rom but still no wifi and network and Still Baseband /Baseline is < not found>
sammd301 said:
I follow the procedure to unlocked the bootloader again, it now shows "flashing_unlocked" as show in the photo below; I flashed another oem rom but still no wifi and network and Still Baseband /Baseline is < not found>
Click to expand...
Click to collapse
Can you link the flash all you used and how you flashed it?
Uzephi said:
Can you link the flash all you used and how you flashed it?
Click to expand...
Click to collapse
I have been following this tread on xda [ https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783 ]
Below is the steps
How to fix your phone:
Download the Utilities zip Link to the flash all https://www.androidfilehost.com/?fid=5862345805528053597
Extract the zip to it's own folder
Download the flash all for your device from the options below.
Extract the flash all zip into the same folder as the Utilities.
Run the Flashall.bat file
Watch windows command prompt put your phone back to stock!
sammd301 said:
I have been following this tread on xda [ https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783 ]
Below is the steps
How to fix your phone:
Download the Utilities zip Link to the flash all https://www.androidfilehost.com/?fid=5862345805528053597
Extract the zip to it's own folder
Download the flash all for your device from the options below.
Extract the flash all zip into the same folder as the Utilities.
Run the Flashall.bat file
Watch windows command prompt put your phone back to stock!
Click to expand...
Click to collapse
What zip did you use?
Edit: that thread uses AFH which has an older version bootloader than in your picture so something isn't going right. How long does it take to flash?
Edit 2: does your phone reboot after running the .bat file?
I used the T-Mobile Flash All zip the link was to google drive https://drive.google.com/file/d/1Bo_ry_38J6BHy4-A4fuhAnv94C5yV1TW/edit
sammd301 said:
I used the T-Mobile Flash All zip the link was to google drive https://drive.google.com/file/d/1Bo_ry_38J6BHy4-A4fuhAnv94C5yV1TW/edit
Click to expand...
Click to collapse
Yeah, that one is old. Try https://androidfilehost.com/?fid=11410963190603877456 just like the guide states, it should open command prompt and you should see it flashing. The process can take s minute or two. If it immediately closes within 30 seconds or hangs, it didn't flash
Uzephi said:
What zip did you use?
Edit: that thread uses AFH which has an older version bootloader than in your picture so something isn't going right. How long does it take to flash?
Edit 2: does your phone reboot after running the .bat file?[/QUOTE
Yes the phone does reboot by itself after running the .bat file, But it reboot back to bootloader screen.
Click to expand...
Click to collapse
Uzephi said:
Yeah, that one is old. Try https://androidfilehost.com/?fid=11410963190603877456 just like the guide states, it should open command prompt and you should see it flashing. The process can take s minute or two. If it immediately closes within 30 seconds or hangs, it didn't flash
Click to expand...
Click to collapse
I download the suggested rom [ https://androidfilehost.com/?fid=11410963190603877456 ] and flashed it to my phone running flashall.bat via Windows PowerShell,
It took approximately 6 minutes for the flashing to be complete, but with some minor error, Afterword the phone reboot back to the bootloader screen. After starting it still doesn't show the IMEI number and No cellular network or WIFI available.
The output of the flashing process is below along with the attach screenshot of the error;
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.803s]
finished. total time: 0.807s
sammd301 said:
I download the suggested rom [ https://androidfilehost.com/?fid=11410963190603877456 ] and flashed it to my phone running flashall.bat via Windows PowerShell,
It took approximately 6 minutes for the flashing to be complete, but with some minor error, Afterword the phone reboot back to the bootloader screen. After starting it still doesn't show the IMEI number and No cellular network or WIFI available.
The output of the flashing process is below along with the attach screenshot of the error;
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.803s]
finished. total time: 0.807s
Click to expand...
Click to collapse
Flash again, after it is done, type fastboot --set-active=other and then run it one last time. Then boot your phone.
Uzephi said:
Flash again, after it is done, type fastboot --set-active=other and then run it one last time. Then boot your phone.
Click to expand...
Click to collapse
After flashing the rom again, and getting the error " Erase successful, but not automatically formatting..." I input the fastboot command "fastboot --set-active=other" and I got back "unknown option -- set-active=other" as show in the image below. Was the syntax right?
I have been googling the errors I have received like "Erase successful, but not automatically formatting.
File system type raw not supported" to see if I can land on page that can help resolve the issue with the phone.
I have downloaded the latest adb and fastboot platform tools versions, after running the flashall.bat file, I still got the same error at the end. I follow up with the "fastboot --set-active=other" command and this time I got [ Setting current slot to '`' FAILED (remote: '') ] as show in the image below.
sammd301 said:
I have downloaded the latest adb and fastboot platform tools versions, after running the flashall.bat file, I still got the same error at the end. I follow up with the "fastboot --set-active=other" command and this time I got [ Setting current slot to '`' FAILED (remote: '') ] as show in the image below.
Click to expand...
Click to collapse
Seems it isn't recognizing other then, which it should. Do =_b then to see if you can swap to slot B
Uzephi said:
Seems it isn't recognizing other then, which it should. Do =_b then to see if you can swap to slot B
Click to expand...
Click to collapse
After inputting the command [ fastboot --set-active=_b ] the output I got back was [ Slot _b does not exist. supported slots are:
a
b ]
I proceed to input [ fastboot --set-active=b ] the output was [ Setting current slot to 'b' ]
So I the flashing again and input the [ fastboot --set-active=b ] again and got back [ Setting current slot to 'b' ]
I pressed the power button to start the phone from bootloader menu , the phone boot-loop with the Motorola logo as show, after 6 to 8 cycling of the boot looping with the Motorola logo the phone bootup again with T-Mobile logo. When it got home screen, I saw again that Network and cellular still not working and No IMEI number too.
Pixel 3 XL stuck in fasboot "error boot prepare" after rooting attempt with Magisk
Ok so I spent the morning rooting my phone with a Magisk_patched.img made with Magisk Canary.
Now, my phone will not exit fastboot mode no matter what I do and gives the error "error boot prepare".
I have even tried to flash the original boot image back to the phone but I still get the same error after doing so.
PLEASE, help?
EDIT
After doing more digging, it seems my phone is not being recognized by fastboot because when I run the adb devices command, I get an empty list of devices.
I'm guessing this is the problem, but how to I get fastboot/adb to recognize my phone?
catass said:
Ok so I spent the morning rooting my phone with a Magisk_patched.img made with Magisk Canary.
Now, my phone will not exit fastboot mode no matter what I do and gives the error "error boot prepare".
I have even tried to flash the original boot image back to the phone but I still get the same error after doing so.
PLEASE, help?
EDIT
After doing more digging, it seems my phone is not being recognized by fastboot because when I run the adb devices command, I get an empty list of devices.
I'm guessing this is the problem, but how to I get fastboot/adb to recognize my phone?
Click to expand...
Click to collapse
I responded to you in the other thread as well, but just in case:
You need to put the fastboot files in the platform tools folder and CMD cd to that folder.
Then ADB reboot bootloader
You can remove the -w from the flash all batch file so you don't have to wipe, then run it.
crixley said:
I responded to you in the other thread as well, but just in case:
You need to put the fastboot files in the platform tools folder and CMD cd to that folder.
Then ADB reboot bootloader
You can remove the -w from the flash all batch file so you don't have to wipe, then run it.
Click to expand...
Click to collapse
OK but when I input the adb reboot bootloader I get an error back saying there is no device/emulator found.
Also, do I put the whole OTA folder I unzipped into the platform-tools directory or just a few select files? Or any at all for that matter... pulling my hair out here lol. Thanks for your time and help, though.
Below is what happened when I ran the flash-all.bat file after moving it and everything else included in the OTA into the platform-tools directory.
I ran it just by double clicking it and choosing run:
Sending 'bootloader_b' (8361 KB) OKAY [ 0.369s]
Writing 'bootloader_b' (bootloader) Flashing Pack version b4s4-0.2-6066691
(bootloader) xbl signature verify fail
FAILED (remote: 'Validate packed image fail')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.051s
Sending 'radio_b' (73276 KB) OKAY [ 2.190s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g670-00036-200114-B-6134202
(bootloader) Flashing partition modem_b
OKAY [ 0.371s]
Finished. Total time: 2.791s
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.050s
--------------------------------------------
Bootloader Version...: b1c1-0.2-6085603
Baseband Version.....: g670-00036-200114-B-6134202
Serial Number........: 92CY17WPW
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' FAILED
Device product is 'crosshatch'.
Update requires 'bonito' or 'sargo'.
fastboot: error: requirements not met!
Press any key to exit...
PS- Also, I even tried downloading the ota for sargo and extracted the payload.bin file to get the boot.img for sargo and tried using that to boot back to stock ota but i still get stuck in fastboot after running the reboot command.
WTF.
Why would you try using things from a different device (are you sure your device is even a pixel 3 xl)? Seems your fastboot or drivers are not correct or you are using an incorrect image.
wangdaning said:
Why would you try using things from a different device (are you sure your device is even a pixel 3 xl)? Seems your fastboot or drivers are not correct or you are using an incorrect image.
Click to expand...
Click to collapse
Because when I tried flash-all.bat, at the bottom of the respond prompt it says something about current product is crosshatch and must be bonito or sargo(sp?). Take a look at my last post in this thread where i copy pasted what the command prompt returned me. It's near the bottom where it says it.
I interpreted that as having the wrong boot.img, so I downloaded bonito which is actually for the 3a XL hoping it would work but it didnt.
Also below is what the command prompt returns to me when I try adb reboot bootloader. I have a feeling if I can get things to where it recognizes a device when I run the adb reboot bootloader command, then my problems will be solved. I just have no idea on how to do so.
C:\Users\Dtbur\Downloads\platform-tools>adb reboot bootloader
error: no devices/emulators found
Update, new error.
So I downloaded the Pixel 3 XL OTA from FEB 2020 instead of the newest one from MARCH 2020.
Now, I can get out of fastboot for (for a second) to a screen that warns me about the bootloader being unlocked and not to store any sensitive data on the device, followed by the Google flash screen, BUT then back to fastboot mode.
The enter reason I got the first time after this happened was Enter reason: No valid boot slot.
SO... I tried fastboot flash boot_a boot.img to get the a slot flashed, as well.
That didn't work BUT now I get a new Enter reason: error booting boot.img.
Am I starting to get somewhere, or just making things worse?
If I were you I would connect, make sure device is recognized by fastboot, and try the crosshatch flash all again.
OK so I finally managed to get out of fastboot and flash a factory image.
I then patched with Magisk again to get root (worked this time). All I have done is flash the magisk_patched.img to my phone in fastboot and I seem to have gotten root after installing root checker.
Is this all that I need to do for root? On the root checker app it says: Superuser binary files not installed. What are Superuser binary files? Is this an issue? Everything else checks out in the root checker app.
can you advise how do you able to flash back to factory. I am having same issue.
Same issue on pixel 4
crixley said:
I responded to you in the other thread as well, but just in case:
You need to put the fastboot files in the platform tools folder and CMD cd to that folder.
Then ADB reboot bootloader
You can remove the -w from the flash all batch file so you don't have to wipe, then run it.
Click to expand...
Click to collapse
my pixel 4 is stuck on bootloader. "error boot prepare".
I did this on my Mac - > ./fastboot flash boot_a /Users/vladgolouschin/Downloads/Pixel/lineage-17.1-20201122-recovery-flame.img
Sending 'boot_a' (65536 KB) OKAY [ 1.550s]
Writing 'boot_a' OKAY [ 0.532s]
Finished. Total time: 2.372s
I tried also flashing boot without a. Also tried boot__a (this one returns error).
PLEASE HELP
Vlad_vog said:
my pixel 4 is stuck on bootloader. "error boot prepare".
I did this on my Mac - > ./fastboot flash boot_a /Users/vladgolouschin/Downloads/Pixel/lineage-17.1-20201122-recovery-flame.img
Sending 'boot_a' (65536 KB) OKAY [ 1.550s]
Writing 'boot_a' OKAY [ 0.532s]
Finished. Total time: 2.372s
I tried also flashing boot without a. Also tried boot__a (this one returns error).
PLEASE HELP
Click to expand...
Click to collapse
Try boot b as well that might help
Hi, I know this is a crazy old thread, but I'd like to share my fix for this:
First, this usually happens if you're playing around with Magisk and do "Reboot to EDL" without knowing what that does. Or any other tool to reboots your device in a silly manner and messes up the default partition it's living on. So, you then find yourself trapped in reboot/fastboot land. The bottom line is:
You get an error that says "error boot prepare" at the bottom of your screen.
To Fix:
1. Connect device to machine with adb/fastboot/etc
2. Type: fastboot set_active b (Or "a" - whatever the OPPOSITE is of what it's currently set to)
3. Type: fastboot reboot --slot b
*You will likely be brought to a broken loader window with the Android-Dude opened up, ignore it and type:
4. Type: adb reboot bootloader
5. Select Normal Start-Up after making sure your Boot slot is set to "b" (or "a")
6. After selecting Reboot to system and you should be set.
Key Take Aways:
If your phone ever gets stuck in a weird boot loop that all the sudden NOTHING works, including recovery mode, etc.. it's likely just looking on the wrong a/b partition and just needs a little guidance on where home is, via "set_active".
Thank You For Coming To My NED Talk.
Hope This Helps!
-DANNO
arfarfdan said:
Hi, I know this is a crazy old thread, but I'd like to share my fix for this:
First, this usually happens if you're playing around with Magisk and do "Reboot to EDL" without knowing what that does. Or any other tool to reboots your device in a silly manner and messes up the default partition it's living on. So, you then find yourself trapped in reboot/fastboot land. The bottom line is:
You get an error that says "error boot prepare" at the bottom of your screen.
To Fix:
1. Connect device to machine with adb/fastboot/etc
2. Type: fastboot set_active b (Or "a" - whatever the OPPOSITE is of what it's currently set to)
3. Type: fastboot reboot --slot b
*You will likely be brought to a broken loader window with the Android-Dude opened up, ignore it and type:
4. Type: adb reboot bootloader
5. Select Normal Start-Up after making sure your Boot slot is set to "b" (or "a")
6. After selecting Reboot to system and you should be set.
Key Take Aways:
If your phone ever gets stuck in a weird boot loop that all the sudden NOTHING works, including recovery mode, etc.. it's likely just looking on the wrong a/b partition and just needs a little guidance on where home is, via "set_active".
Thank You For Coming To My NED Talk.
Hope This Helps!
-DANNO
Click to expand...
Click to collapse
So I finished step 4, and I assumed for step five on my phone it said "reboot bootloader" instead of "error boot prepare" and hit "Start" on the power button. Now it is loading by showing the Google logo, will my phone restart normally once it finished or will it show the bootloader screen again? plus this is taking a long time so far 5=10 minutes will it be okay? My apologies in advance I am very new to this
arfarfdan said:
Hi, I know this is a crazy old thread, but I'd like to share my fix for this:
First, this usually happens if you're playing around with Magisk and do "Reboot to EDL" without knowing what that does. Or any other tool to reboots your device in a silly manner and messes up the default partition it's living on. So, you then find yourself trapped in reboot/fastboot land. The bottom line is:
You get an error that says "error boot prepare" at the bottom of your screen.
To Fix:
1. Connect device to machine with adb/fastboot/etc
2. Type: fastboot set_active b (Or "a" - whatever the OPPOSITE is of what it's currently set to)
3. Type: fastboot reboot --slot b
*You will likely be brought to a broken loader window with the Android-Dude opened up, ignore it and type:
4. Type: adb reboot bootloader
5. Select Normal Start-Up after making sure your Boot slot is set to "b" (or "a")
6. After selecting Reboot to system and you should be set.
Key Take Aways:
If your phone ever gets stuck in a weird boot loop that all the sudden NOTHING works, including recovery mode, etc.. it's likely just looking on the wrong a/b partition and just needs a little guidance on where home is, via "set_active".
Thank You For Coming To My NED Talk.
Hope This Helps!
-DANNO
Click to expand...
Click to collapse
Hi this is my problem, I have tried to downgrade the android system of my pixel 3aXL, from android 12 to android 11 by following this tutorial: https://9to5google.com/2021/10/21/how-to-downgrade-from- android-12-to-android-11-on-google-pixel /
Unfortunately I'm hopelessly stuck in the "Fastboot Mode" loop. I have downloaded the "platform-tools_r31.0.3-windows" tool, I have downloaded, unzipped and pasted the content of the latest android image for my 3aXL pixel "bonito-sp1a.210812.016.a1-factory-8a51e8a7" (android 12), In the folder "platform-tools", then I open the command window "cmd" and run the command "adb reboot bootloader", but it tells me the following: "* daemon not running; starting now at tcp: 5037 * daemon started successfully error: no devices / emulators found ", and when I execute the command" flash-all ", it keeps thinking:" <waiting for any device> ", while in the section of" Fastboot Mode "in the option" Enter reason " it says: "reboot bootloader" I have tried the factory reset, "adroid flash tool" and nothing works, I would greatly appreciate your help, please!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}