Question Anyone had problems rooting OOS13 final - OnePlus 9 Pro

I'm on the EU final, bootloader was already unlocked.
Usually I'm on my Windows 11 PC but I'm stuck on my linux laptop for now (ZorinOS).
Downloaded the platform tools but the fastboot command isn't recognised, even with ./ :
:~/ADB$ ./fastboot
fastboot: usage: no command
./adb works ok
Both ADB and Fastboot show executable permissions
So I downloaded and installed ADB and Fastboot with APT
Also, finally, got the payload_dumper to install correctly and extract the payload.bin
Magisk 25.2 is installed, copied the extracted boot.img over and rooted it, copied it to my computer
Used ADB REBOOT BOOTLOADER, that worked fine
Used fastboot with the rooted image, which seemed to work fine:
~/ADB$ fastboot boot magisk_patched-25200_2FxQP.img
downloading 'boot.img'...
OKAY [ 6.735s]
booting...
OKAY [ 0.448s]
finished. total time: 7.183s
Then I just get stuck on the fastboot logo, I know sometimes it's slow to boot but I left it for ages and no boot, nothing's destroyed though, the phone will boot back normally, albeit with that new ugly orange mode message.
Tried it a second time too, same result.
Any ideas? I was wondering if the fastboot installed via APT might be out of date but the one in the google platform tools doesn't seem to want to play

djsubterrain said:
I'm on the EU final, bootloader was already unlocked.
Usually I'm on my Windows 11 PC but I'm stuck on my linux laptop for now (ZorinOS).
Downloaded the platform tools but the fastboot command isn't recognised, even with ./ :
:~/ADB$ ./fastboot
fastboot: usage: no command
./adb works ok
Both ADB and Fastboot show executable permissions
So I downloaded and installed ADB and Fastboot with APT
Also, finally, got the payload_dumper to install correctly and extract the payload.bin
Magisk 25.2 is installed, copied the extracted boot.img over and rooted it, copied it to my computer
Used ADB REBOOT BOOTLOADER, that worked fine
Used fastboot with the rooted image, which seemed to work fine:
~/ADB$ fastboot boot magisk_patched-25200_2FxQP.img
downloading 'boot.img'...
OKAY [ 6.735s]
booting...
OKAY [ 0.448s]
finished. total time: 7.183s
Then I just get stuck on the fastboot logo, I know sometimes it's slow to boot but I left it for ages and no boot, nothing's destroyed though, the phone will boot back normally, albeit with that new ugly orange mode message.
Tried it a second time too, same result.
Any ideas? I was wondering if the fastboot installed via APT might be out of date but the one in the google platform tools doesn't seem to want to play
Click to expand...
Click to collapse
I also had issues booting the boot.img. I took the risk of flashing it and it worked.

Airwolf79 said:
I also had issues booting the boot.img. I took the risk of flashing it and it worked.
Click to expand...
Click to collapse
Using what command? Just fastboot flash boot rootedimage.img?
Kind of reticent to do that cos there's no linux MSM tool

djsubterrain said:
I'm on the EU final, bootloader was already unlocked.
Usually I'm on my Windows 11 PC but I'm stuck on my linux laptop for now (ZorinOS).
Downloaded the platform tools but the fastboot command isn't recognised, even with ./ :
:~/ADB$ ./fastboot
fastboot: usage: no command
./adb works ok
Both ADB and Fastboot show executable permissions
So I downloaded and installed ADB and Fastboot with APT
Also, finally, got the payload_dumper to install correctly and extract the payload.bin
Magisk 25.2 is installed, copied the extracted boot.img over and rooted it, copied it to my computer
Used ADB REBOOT BOOTLOADER, that worked fine
Used fastboot with the rooted image, which seemed to work fine:
~/ADB$ fastboot boot magisk_patched-25200_2FxQP.img
downloading 'boot.img'...
OKAY [ 6.735s]
booting...
OKAY [ 0.448s]
finished. total time: 7.183s
Then I just get stuck on the fastboot logo, I know sometimes it's slow to boot but I left it for ages and no boot, nothing's destroyed though, the phone will boot back normally, albeit with that new ugly orange mode message.
Tried it a second time too, same result.
Any ideas? I was wondering if the fastboot installed via APT might be out of date but the one in the google platform tools doesn't seem to want to play
Click to expand...
Click to collapse
Also having that issue on the NA varient. So f-ing annoying.

djsubterrain said:
I'm on the EU final, bootloader was already unlocked.
Usually I'm on my Windows 11 PC but I'm stuck on my linux laptop for now (ZorinOS).
Downloaded the platform tools but the fastboot command isn't recognised, even with ./ :
:~/ADB$ ./fastboot
fastboot: usage: no command
./adb works ok
Both ADB and Fastboot show executable permissions
So I downloaded and installed ADB and Fastboot with APT
Also, finally, got the payload_dumper to install correctly and extract the payload.bin
Magisk 25.2 is installed, copied the extracted boot.img over and rooted it, copied it to my computer
Used ADB REBOOT BOOTLOADER, that worked fine
Used fastboot with the rooted image, which seemed to work fine:
~/ADB$ fastboot boot magisk_patched-25200_2FxQP.img
downloading 'boot.img'...
OKAY [ 6.735s]
booting...
OKAY [ 0.448s]
finished. total time: 7.183s
Then I just get stuck on the fastboot logo, I know sometimes it's slow to boot but I left it for ages and no boot, nothing's destroyed though, the phone will boot back normally, albeit with that new ugly orange mode message.
Tried it a second time too, same result.
Any ideas? I was wondering if the fastboot installed via APT might be out of date but the one in the google platform tools doesn't seem to want to play
Click to expand...
Click to collapse
Go into recovery and factory reset. That happen to me once when flashing in fastboot from bootloader.

djsubterrain said:
Using what command? Just fastboot flash boot rootedimage.img?
Kind of reticent to do that cos there's no linux MSM tool
Click to expand...
Click to collapse
Yeah, I know. I'm on a Mac, so, same boat. Yes, I flashed with "fastboot flash boot boot.img", specifically renaming the patched img to boot.img. This used to be the standard way of doing it, although I realize it's safer to boot the img.

My mistake, you are trying to get root, correct?

TheGhost1951 said:
My mistake, you are trying to get root, correct?
Click to expand...
Click to collapse
Try fastboot enhanced maybe? Nope, sorry, that is for windows only I believe.

TheGhost1951 said:
Try fastboot enhanced maybe? Nope, sorry, that is for windows only I believe.
Click to expand...
Click to collapse
Being on a MAC, I really don't have a clue bud..

Actually found the linux version of MSM tool (It's really just a Qualcomm tool) so I might try flashing directly, will need to grab the appropriate MSM image just in case.
Made a guide here for anyone else in Linux but I haven't tested yet

djsubterrain said:
Actually found the linux version of MSM tool (It's really just a Qualcomm tool) so I might try flashing directly, will need to grab the appropriate MSM image just in case.
Made a guide here for anyone else in Linux but I haven't tested yet
Click to expand...
Click to collapse
Did root work?

If you're trying to root, just run the command "fastboot boot magisk_patched boot.img" Don't use the command "fastboot flash boot magisk_patched boot.img" You only want to boot the patched img, once it boots, then use the magisk apk to direct install.

mustangtim49 said:
If you're trying to root, just run the command "fastboot boot magisk_patched boot.img" Don't use the command "fastboot flash boot magisk_patched boot.img" You only want to boot the patched img, once it boots, then use the magisk apk to direct install.
Click to expand...
Click to collapse
You did actually read my post, right?

mustangtim49 said:
If you're trying to root, just run the command "fastboot boot magisk_patched boot.img" Don't use the command "fastboot flash boot magisk_patched boot.img" You only want to boot the patched img, once it boots, then use the magisk apk to direct install.
Click to expand...
Click to collapse
I'm still getting a bootloop

LuckyTheCoder said:
I'm still getting a bootloop
Click to expand...
Click to collapse
Of course, once it goes wrong, it stays wrong. Did you use the fastboot flash boot command? Either way, msn tool and start from scratch.

mustangtim49 said:
Of course, once it goes wrong, it stays wrong. Did you use the fastboot flash boot command? Either way, msn tool and start from scratch.
Click to expand...
Click to collapse
I did, yes. MSN tool? Like fully reset?

LuckyTheCoder said:
I did, yes. MSN tool? Like fully reset?
Click to expand...
Click to collapse
It will!

TheGhost1951 said:
It will!
Click to expand...
Click to collapse
:/

LuckyTheCoder said:
:/
Click to expand...
Click to collapse
I can't count the number of times I have started from scratch just from trying different things and crashing!

TheGhost1951 said:
I can't count the number of times I have started from scratch just from trying different things and crashing!
Click to expand...
Click to collapse
How in the world am I supposed to back it up?

Related

[Q] Nexus 7 2013 Problems...

A couple days ago, I was browsing the internet, then my Nexus 7 2013 suddenly froze. I did a reboot, but it got stuck on the boot animation. So, since it wasn't booting back up, I tried to load from one of my old backups. I managed to get the back up to work, however I needed to download the 4.4.2 update OTA through TWRP. It never officially said it finished, but I restarted the tablet and it's been stuck on the Google screen. I've went to fastboot, but it wont let me into TWRP recovery since it only loads the Google screen. I've also tried this ( http://www.androidbeat.com/2013/11/flash-factory-image-nexus-device/#.U0o0z3nn_0x ) and it didn't work.
When I try to reset through WugFresh, I've flashed KRT16S 4.4 and KOT49H 4.4.2, and and I get
Code:
sending 'bootloader' (3911 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.638s
archive does not contain 'boot.sig'
error: out of memory
I've also tried a few other ways of restoring to factory settings but nothing has worked :crying:
Any help is much appreciated!
I deleted my OS on my nexus... Oops? what I did is I did a ADB Sideload custom rom but if you can't get into twrp you are screwed. Maybe send it to Asus or return it if it is under warranty and get a new one. Just remember don't listen to me, in just a child on a tablet at night trying to unpack full posting privileges.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Any other suggestions..?
Couldn't you go into your bootloader, erase your recovery using ADB, and then flash it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
codemonkey98 said:
Couldn't you go into your bootloader, erase your recovery using ADB, and then flash it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I don't think I've tried that yet. Do you have a link on how to do it? I'm not all that experienced...
PieceofSlice said:
I don't think I've tried that yet. Do you have a link on how to do it? I'm not all that experienced...
Click to expand...
Click to collapse
A tutorial can be found here. The tutorial guides you to get the Nexus 7 (2012) original files, please get the actual Nexus 7 (2013) files.
codemonkey98 said:
A tutorial can be found here. The tutorial guides you to get the Nexus 7 (2012) original files, please get the actual Nexus 7 (2013) files.
Click to expand...
Click to collapse
Alright, thanks I'll try this as soon as I get home. Though, when it says to type "fastboot flash bootloader bootloader-grouper-3.34.img" will I just be able to substitute the new 4.4.2 factory image stuff instead of the older? Also, does it matter that I can't set my Nexus into debugging mode?
PieceofSlice said:
Alright, thanks I'll try this as soon as I get home. Though, when it says to type "fastboot flash bootloader bootloader-grouper-3.34.img" will I just be able to substitute the new 4.4.2 factory image stuff instead of the older? Also, does it matter that I can't set my Nexus into debugging mode?
Click to expand...
Click to collapse
Yes you will need to replace by the "bootloader-grouper-3.34.img" by the name of the img in your device archive.
For my Razorg / deb (The LTE version) it will be :
Code:
fastboot flash bootloader bootloader-deb-04.02.img
and
Code:
fastboot -w update image-razorg-kot49h.zip
And for the Razor / flo (Wifi version) it will be :
Code:
fastboot flash bootloader bootloader-flo-flo-04.02.img
and
Code:
fastboot -w update image-razor-kot49h.zip
For reminder, factory images can be found there : https://developers.google.com/android/nexus/images?hl=FR#razor
Debugging mode / ADB is not nessesary until you write the bootloader in fastboot mode
But don't forget to install drivers, except if you already do this step
I hope i helped you.
PieceofSlice said:
Alright, thanks I'll try this as soon as I get home. Though, when it says to type "fastboot flash bootloader bootloader-grouper-3.34.img" will I just be able to substitute the new 4.4.2 factory image stuff instead of the older? Also, does it matter that I can't set my Nexus into debugging mode?
Click to expand...
Click to collapse
You mustn't flash grouper bootloader on flo/deb!
Only the bootloader that belongs to your firmware.
Yet I'm not sure if your USB driver is installed properly.
Are you 100% sure it is?
that link is great!...
Don't worry you are not screwed...just follow the link the person above posted about how to hard reset your nexus device. Since you have a 2013 nexus just make sure that you download the correct nexus image and make sure you flash the correct files and you will be fine. I have used that same tutorial on my nexus 7 2013 flo and deb to fix issues.
Trust me it will work...
-droidshadow
codemonkey98 said:
A tutorial can be found here. The tutorial guides you to get the Nexus 7 (2012) original files, please get the actual Nexus 7 (2013) files.
Click to expand...
Click to collapse
When following the tutorial, I type in "fastboot erase boot." However, when I do that it gives me this error...
Code:
C:\android-sdk\platform-tools>fastboot devices
04988e98 fastboot
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
I have the SDK installed correctly and everything in the correct spot, right?
PieceofSlice said:
When following the tutorial, I type in "fastboot erase boot." However, when I do that it gives me this error...
Code:
C:\android-sdk\platform-tools>fastboot devices
04988e98 fastboot
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
I have the SDK installed correctly and everything in the correct spot, right?
Click to expand...
Click to collapse
The files in folder look fine now
Did you update your SDK manager to the newest version? (Especially sources regarding API 18 and 19 are important). Move the firmware files elsewhere before, because by major updates whole platform-tools folder will be replaced.
Try to use different USB port on your PC. Once when you are in fastboot mode, does this command work?
Code:
fastboot reboot-bootloader
tetakpatalked from Nexus 7
Well, just my 2 cents... I read somewhere else on this forum from someone having the same issue that replacing the cable he used actually did the trick for him. You might try that. Won't hurt..
tetakpatak said:
The files in folder look fine now
Did you update your SDK manager to the newest version? (Especially sources regarding API 18 and 19 are important). Move the firmware files elsewhere before, because by major updates whole platform-tools folder will be replaced.
Try to use different USB port on your PC. Once when you are in fastboot mode, does this command work?
Code:
fastboot reboot-bootloader
tetakpatalked from Nexus 7
Click to expand...
Click to collapse
I haven't updated the SDK. So when I do, just be sure to move the image files and whatnot, and then put them back after the update, correct?
I'll be doing this later
PieceofSlice said:
I haven't updated the SDK. So when I do, just be sure to move the image files and whatnot, and then put them back after the update, correct?
I'll be doing this later
Click to expand...
Click to collapse
Yes just move your firmware files (bootloader and image.zip) out of the folder.
Updating is easy, double-click SDK manager application (you will see it as soon as you open SDK folder) and there you can choose what to update. You just need an internet connection.
tetakpatalked from Nexus 7
i am intrigued to see if this person was able to fix his tablet...
I think that all the suggestions above are very good ones. Making sure he has the most updated software...
Make sure he tries another usb cable or make sure you are using the stock usb cable.
And trying another usb port...
However from this fastboot devices output it did show that his device was connected which i don't think would happen with a default usb cable.
Okay so here is what i think may be causing the problem.
I think you need to unlock your bootloader before you can erase it. Try following this tutorial -> http://forum.xda-developers.com/showthread.php?t=1907796
You have to unlock it before you can erase the bootloader. So you need to do:
command 1: adb reboot-bootloader
command 2: fastboot oem unlock
then you can do:
command 3: fastboot erase boot
try that and see if that helps....
If that does not work then try flashing the new bootloader over the old one.
I hope this has been helpful.
Don't give up...
-droidshadow
LOL, good point @droidshadow!
Hey, @PieceofSlice, is your bootloader possibly still locked? Please make photo of the text in bootloader mode on bottom left and post screenshot of it.
tetakpatalked from Nexus 7
droidshadow said:
i am intrigued to see if this person was able to fix his tablet...
I think you need to unlock your bootloader before you can erase it. Try following this tutorial -> http://forum.xda-developers.com/showthread.php?t=1907796
You have to unlock it before you can erase the bootloader. So you need to do:
command 1: adb reboot-bootloader
command 2: fastboot oem unlock
then you can do:
command 3: fastboot erase boot
try that and see if that helps....
-droidshadow
Click to expand...
Click to collapse
I'm pretty sure my bootloader is unlocked, my tablet has the unlocked padlock at the Google screen. I'll take your advice and try a new cord too
droidshadow said:
i am intrigued to see if this person was able to fix his tablet...
You have to unlock it before you can erase the bootloader. So you need to do:
command 1: adb reboot-bootloader
command 2: fastboot oem unlock
then you can do:
command 3: fastboot erase boot
try that and see if that helps....
If that does not work then try flashing the new bootloader over the old one.
-droidshadow
Click to expand...
Click to collapse
So I actually tried to do this because, even though I updated the Android SDK, when I typed in "fastboot erase boot", it basically froze on "erasing bootloader." When I tried the first command, "adb reboot-bootloader", it said
Code:
C:\android-sdk\platform-tools>adb reboot-bootloader
error: device not found
So I take it I have a problem with ADB or something?
There are two generally different modes by using Android Debugging Bridge:
1. ADB (device booted in OS or recovery)
2. FASTBOOT (device in bootloader mode)
When I tried the first command, "adb reboot-bootloader", it said
Code:
C:\android-sdk\platform-tools>adb reboot-bootloader
error: device not found
So I take it I have a problem with ADB or something?
Click to expand...
Click to collapse
So, if you have tried this command above when your device was in bootloader mode, it was wrong command, as the command should have started with "fastboot...." instead of "adb..."
If the device was booted in OS, this command would have been correct and such response could have two reasons:
* USB debugging was not enabled
* drivers are not installed properly
After updating SDK manager, it is always highly recommended to check if the driver still works.
PieceofSlice said:
when I typed in "fastboot erase boot", it basically froze on "erasing bootloader."
Click to expand...
Click to collapse
Careful, mate, I hope you didn't try to erase your bootloader? That would have fatal results. Actually "boot" means kernel! As long as your bootloader is there = your tab will be fine.
By flashing a factory image the order of doing things is
* erase all (kernel, system, userdata etc)
* flash new bootloader
* reboot bootloader
* flashing whole factory image zip file
tetakpatalked from Nexus 7

Stuck in Fastboot/No Download Mode

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...

Pixel C - fastboot unsupported command

Hi everyone ! (I apologyze for my english)
I cant flash anything on my Pixel C because of this:
C:\Users\ykant\Desktop\Minimal ADB and Fastboot>fastboot flash recovery TWRP_dragon_3.0.2-23.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
FAILED (remote: unsupported command)
finished. total time: -0.000s
Click to expand...
Click to collapse
No system to boot on and my TWRP is wiped !!
--> Cant do this:
fwtool vbnv write dev_boot_fastboot_full_cap 1
Click to expand...
Click to collapse
Is my pixel C bricked now ?
regards !
Did you unlock your device first with "fastboot oem unlock"?
redukt said:
Did you unlock your device first with "fastboot oem unlock"?
Click to expand...
Click to collapse
Yes i did this before, i was running on Remix OS
I don't know if this is of relevance but there were new fastboot commands introduced from Android M (?) and I have recollection about "partial unlock" - two flags required to be set and if only one was set it could be reported that the bootloader was unlocked but fastboot saw it as locked. Above may be totally wrong.
Here's the difference between old and current fastboot commands. Note the new lock/unlock commands
Code:
************************ OLD **************************************
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
************************ NEW **************************************
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> Reflash device from update.zip.
Sets the flashed slot as active.
flashall Flash boot, system, vendor, and --
if found -- recovery. If the device
supports slots, the slot that has
been flashed to is set as active.
Secondary images may be flashed to
an inactive slot.
flash <partition> [ <filename> ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
flashing lock_critical Prevents flashing bootloader-related
partitions.
flashing unlock_critical Enables flashing bootloader-related
partitions.
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
erase <partition> Erase a flash partition.
format[:[<fs type>][:[<size>]] <partition>
Format a flash partition. Can
override the fs type and/or size
the bootloader reports.
getvar <variable> Display a bootloader variable.
set_active <slot> Sets the active slot. If slots are
not supported, this does nothing.
boot <kernel> [ <ramdisk> [ <second> ] ] Download and boot kernel.
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ]
Create bootimage and flash it.
devices [-l] List all connected devices [with
device paths].
continue Continue with autoboot.
reboot [bootloader] Reboot device [into bootloader].
reboot-bootloader Reboot device into bootloader.
help Show this help message.
-Yazh- said:
Hi everyone ! (I apologyze for my english)
I cant flash anything on my Pixel C because of this:
C:\Users\ykant\Desktop\Minimal ADB and Fastboot>fastboot flash recovery TWRP_dragon_3.0.2-23.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
FAILED (remote: unsupported command)
finished. total time: -0.000s
Click to expand...
Click to collapse
No system to boot on and my TWRP is wiped !!
--> Cant do this:
fwtool vbnv write dev_boot_fastboot_full_cap 1
Click to expand...
Click to collapse
Is my pixel C bricked now ?
regards !
Click to expand...
Click to collapse
Hi, I'm just wondering if you were able to fix your tablet. I ran into the same problem as you here and am not able to find a solution to it.
Hi !!
Sorry for bad news, but i didn't found any solution since my Pixel C was bricked. Maybe there is a solution, but I dropped it before finding it.
I hope you find something to fix it !
@viii_xvi Are you using "Minimal ADB and Fastboot" as shown in the post you quoted by -Yazh- ? The current (?) version that I can find is 1.4.3 and that looks to be "2015".
For the current versions of adb and fastboot and the revision history, 12 since October 2016, see https://developer.android.com/studio/releases/platform-tools.html
peterk-1 said:
Are you using "Minimal ADB and Fastboot" as shown in the post you quoted by -Yazh- ? The current (?) version that I can find is 1.4.3 and that looks to be "2015".
Click to expand...
Click to collapse
No. I used the 15 second ADB and Fastboot installer. I'm pretty sure it works fine as I can use fastboot commands.
peterk-1 said:
For the current versions of adb and fastboot and the revision history, 12 since October 2016, see https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
I don't really know what to do with the files found in the zip. If I'm doing it wrong, can you tell me what I should be doing?
viii_xvi said:
No. I used the 15 second ADB and Fastboot installer. I'm pretty sure it works fine as I can use fastboot commands.
I don't really know what to do with the files found in the zip. If I'm doing it wrong, can you tell me what I should be doing?
Click to expand...
Click to collapse
There are Youtube videos on installing Android Platform Tools and a web search for installing Android Platform Tools with your o/s will find many hits. You need to know you are installing just the platform tools - some of the guides assume you are installing or have installed the full Android Software Development Kit (SDK).
Assuming you are using Windows then the simplest method is to copy the contents of the zip file into the current location of your "15 second" files. This ensures that you can run the new version of fastboot with the folder path you have used previously. In file manager "find" fastboot.exe and that will give you the folder to unzip ALL of the platform tools files. You will know if you have done it correctly if you get requests to overwrite existing files when you unzip the files.
peterk-1 said:
There are Youtube videos on installing Android Platform Tools and a web search for installing Android Platform Tools with your o/s will find many hits. You need to know you are installing just the platform tools - some of the guides assume you are installing or have installed the full Android Software Development Kit (SDK).
Assuming you are using Windows then the simplest method is to copy the contents of the zip file into the current location of your "15 second" files. This ensures that you can run the new version of fastboot with the folder path you have used previously. In file manager "find" fastboot.exe and that will give you the folder to unzip ALL of the platform tools files. You will know if you have done it correctly if you get requests to overwrite existing files when you unzip the files.
Click to expand...
Click to collapse
I've followed the instructions so I'm confident I did it correctly. Despite this, nothing has improved. I still can't flash the stock ROM or a custom recovery in fastboot.
What I've noticed from updating the fastboot version are some new commands I found when I entered "fastboot -h"
Code:
fastboot -h
commands:
reboot [bootloader|emergency]
stage <infile>
get_staged <outfile>
options:
--skip-secondary
--skip-reboot
--disable-verity
--disable-verification
--unbuffered
--version
From what I've tried, all the commands in options returns
fastboot: usage: no command
Click to expand...
Click to collapse
viii_xvi said:
I've followed the instructions so I'm confident I did it correctly. Despite this, nothing has improved. I still can't flash the stock ROM or a custom recovery in fastboot.
What I've noticed from updating the fastboot version are some new commands I found when I entered "fastboot -h"
Code:
fastboot -h
commands:
reboot [bootloader|emergency]
stage <infile>
get_staged <outfile>
options:
--skip-secondary
--skip-reboot
--disable-verity
--disable-verification
--unbuffered
--version
From what I've tried, all the commands in options returns
Click to expand...
Click to collapse
Hi, Did you tried to flash with the oldest stock rom of the pixel C ? Because it uses older version of fastboot so maybe it will work. I has also the same problem as you but hopefully twrp still worked so i could flash another system image.
rhmanoa said:
Hi, Did you tried to flash with the oldest stock rom of the pixel C ? Because it uses older version of fastboot so maybe it will work. I has also the same problem as you but hopefully twrp still worked so i could flash another system image.
Click to expand...
Click to collapse
I have now tried to flash the earliest factory image and am disappointed to say the bootloader did not flash and so I wasn't able to complete the flashing.
I don't think the problem is the fastboot version. It may be the bootloader itself. I've read someone describe this problem as "Broken fastboot (bootloader) security." I think the problem is that, when unlocked, the bootloader would return the same messages as if it was locked. The security of the bootloader still thinks it's locked and not allow flashing of any images. Also that locking and reunlocking does not improve the situation. This would explain why, when bootloader is unlocked, I get "remote: unsupported command" and "remote: image verification failed", the same as when I try the same commands when the bootloader is locked.
viii_xvi said:
I have now tried to flash the earliest factory image and am disappointed to say the bootloader did not flash and so I wasn't able to complete the flashing.
I don't think the problem is the fastboot version. It may be the bootloader itself. I've read someone describe this problem as "Broken fastboot (bootloader) security." I think the problem is that, when unlocked, the bootloader would return the same messages as if it was locked. The security of the bootloader still thinks it's locked and not allow flashing of any images. Also that locking and reunlocking does not improve the situation. This would explain why, when bootloader is unlocked, I get "remote: unsupported command" and "remote: image verification failed", the same as when I try the same commands when the bootloader is locked.
Click to expand...
Click to collapse
Just bought today, same issue, have you solved it?
mansonstein said:
Just bought today, same issue, have you solved it?
Click to expand...
Click to collapse
No, I didn't manage to fix it.
did you found a solution yet?
I got a same problem,cant flash anything but ordinary using.
I got the problem caused by flashed twrp3.2.3,cant get into system,just always get into twrp.
cant flash any official firmware with "flash-all.bat",no matter which platform tool or firmware.but the twrp were installed before can flash anything.
finally,I flashed newest OTA firmware,then device can be booted. but got the unsupported command
richardwia said:
did you found a solution yet?
I got a same problem,cant flash anything but ordinary using.
I got the problem caused by flashed twrp3.2.3,cant get into system,just always get into twrp.
cant flash any official firmware with "flash-all.bat",no matter which platform tool or firmware.but the twrp were installed before can flash anything.
finally,I flashed newest OTA firmware,then device can be booted. but got the unsupported command
Click to expand...
Click to collapse
I'm assuming you have the latest version of TWRP installed. IIRC, there should be "Fix Fastboot" in advanced options. If indeed you have the same problem I had, pressing this should fix the problem. I don't know anything beyond this as I never got to find out what happens afterwards.
viii_xvi said:
I'm assuming you have the latest version of TWRP installed. IIRC, there should be "Fix Fastboot" in advanced options. If indeed you have the same problem I had, pressing this should fix the problem. I don't know anything beyond this as I never got to find out what happens afterwards.
Click to expand...
Click to collapse
really?where I can find the“fix fastboot in advanced options”?
richardwia said:
really?where I can find the“fix fastboot in advanced options”?
Click to expand...
Click to collapse
I believe I'm not qualified to help you as I disposed of my tablet months ago. All the advice I've given is off of memory and may not be accurate. That being said, I won't help you anymore in fear of giving inaccurate information that may lead to bricking of your tablet.
I have a pixel C, flashed with latest 3-rd pixel experience before, someday i tried to flash back to factory image, hit the same trouble like this topic, i came here several times before, no solution, today, i found another article about this , it's solved my trouble.
sorry i am new here, i couldn't share the outside article link.
would like to share what i did on my pixel c.
1. root your pixel c
2. adb shell //this command could be executed under recovery mode too.
3. su
4. fwtool vbnv write dev_boot_fastboot_full_cap 1
5. adb reboot fastboot
then you could flash anything you want.
I had this just now - I finally got fed up of my Pixel C being so laggy and also chrome opening up as blank pages (I switched to brace to fix this, but it's abit crashy).
Anyhow I found that after
adb reboot bootloader
that
fastboot flash recovery twrp.img
was failing for me in the "Writing" stage
I discovered that the fix was to use
adb flashing unlock
then it will ask you a question (power button to confirm and one of teh volume keys to cancel).
after this it spins with erasing for a while and then comes back to fastboot after which
fastboot flash recovery twrp.img
Worked, after this you get an annoying 30s delay for each restart, I think that can be fixed by
adb flashing lock
I'll verify this when I've finished flashing a usable ROM to my Pixel C...

Stuck in bootloader - no recovery - no system

Hi all,
unfortunatelly I can't get my pixel c working again. I'm stuck in bootloader and only fastboot commands work but with no success.
fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
FAILED (remote: unsupported command)
Click to expand...
Click to collapse
fastboot boot twrp.img
creating boot image...
creating boot image - 13133824 bytes
downloading 'boot.img'...
OKAY [ 0.442s]
booting...
FAILED (remote: image verification failed)
Click to expand...
Click to collapse
All drivers (ADB, Fastboot, Google etc.) are installed and are up-to-date. Bootloader is unlocked and it seems BL reacts the same way like BL is locked.
System is not booting and recovery won't boot too. Is there any way to get an adb shell in another way?
Bolemichel said:
Hi all,
unfortunatelly I can't get my pixel c working again. I'm stuck in bootloader and only fastboot commands work but with no success.
fastboot flash recovery twrp.img
fastboot boot twrp.img
All drivers (ADB, Fastboot, Google etc.) are installed and are up-to-date. Bootloader is unlocked and it seems BL reacts the same way like BL is locked.
System is not booting and recovery won't boot too. Is there any way to get an adb shell in another way?
Click to expand...
Click to collapse
Have you tried flashing stock?
Bolemichel said:
Hi all,
unfortunatelly I can't get my pixel c working again. I'm stuck in bootloader and only fastboot commands work but with no success.
fastboot flash recovery twrp.img
fastboot boot twrp.img
All drivers (ADB, Fastboot, Google etc.) are installed and are up-to-date. Bootloader is unlocked and it seems BL reacts the same way like BL is locked.
System is not booting and recovery won't boot too. Is there any way to get an adb shell in another way?
Click to expand...
Click to collapse
Were you able to solve that?
FWIW, the state you're describing is not unheard of and requires to use the fwtool (reference, for example, here). But that, in turn, requires you can have TWRP installed... because with the bootloader in this limbo state, it also refuses to load TWRP on the fly using "fastboot boot ..."
xrad said:
Were you able to solve that?
FWIW, the state you're describing is not unheard of and requires to use the fwtool (reference, for example, here). But that, in turn, requires you can have TWRP installed... because with the bootloader in this limbo state, it also refuses to load TWRP on the fly using "fastboot boot ..."
Click to expand...
Click to collapse
No, meanwhile I returned it to google and got a new one. But thank you for help!

Cannot flash anything except flashall via fastboot mode

Having a weird issue I've never run into. Used to be on Invitrix rom, returned to stock via latest oreo flashall and wanted to get onto Lineage 15.1. While flashall works, I cannot boot from TWRP. I've attempted on both Windows 10, Ubuntu 18.04 LTS and Ubuntu 18.10 and ensured all drivers are installed. I've tried with and without sudo privilege just in case. I've tried renaming the .img to recovery.img, boot.img, etc.. Yet, I keep getting a simple failed message. Bootloader is still unlocked and I've tried multiple cables including the stock one, USB 2.0 and 3.0 ports on both my desktop and and laptop. Is my phone simply corrupted or am I missing something?
sudo fastboot boot twrp-3.2.3-0-nash.img
downloading 'boot.img'...
FAILED (remote: unknown command)
finished. total time: 0.001s
Put the phone in bootloader mode and verify connection.
PHP:
fastboot devices
If it is recognized then...
PHP:
fastboot boot <path/to/twrp-3.2.3-2-nash.img>
*Note - In win you can drag n' drop the recovery img in the command prompt and it will auto fill the full path.
41rw4lk said:
Put the phone in bootloader mode and verify connection.
PHP:
fastboot devices
If it is recognized then...
PHP:
fastboot boot <path/to/twrp-3.2.3-2-nash.img>
*Note - In win you can drag n' drop the recovery img in the command prompt and it will auto fill the full path.
Click to expand...
Click to collapse
I did. Device shows up like normal. I verified by typing
fastboot devices

Categories

Resources