Hey everyone,
Earlier today I was able to successfully root my Essential Ph-1 running Oreo 8.1, using Magisk and twrp-mata_11.img . Later on I tried to install Xposed framework, but found myself caught in a bootloop, when the flashed TWRP did not recognized my phone PIN and I tried to reboot the system and take the PIN out. I am able to access the bootloader and use the TWRP when I flash it, and that's it.
I do realize that it fixing it is not really a complex process, but I have been having trouble with flashing with fastboot. Every command I try to run ends up in failure, except the "fastboot devices" one. For example, when I tried to run the "fastboot -w" command, I received the following:
"wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (No error))
erasing 'userdata'...
FAILED (command write failed (No error))".
And all others commands showed the "FAILED (command write failed (No error))" message, including when I tried to run the "flash all" file as system admin.
Also, I have only tried to do it in Windows, to no avail, while I am still inexperienced with Linux and cannot connect fastboot to my device.
This is not the first time that I have rooted the device, I did it twice a couple months ago but lost the root because of updates. The difference is that I used my Nintendo Switch Pro Controller cable, which for some reason was the cable that worked the best, instead of the phone's factory cable with a Syntech USB - C to USB adaptor. this time. I found out later on that this cable had issues with this kind of process.
Also, when flashing TWRP in my oldest attempt at rooting, I got the message "system mount fail" when installing the magisk zip, but it never progressed beyond that and my at-the-time rooted phone worked perfectly.
This is my first Android phone after years of Apple(also my first thread here), and I have been excited and experimenting with it a lot, though I've only had it for less than 3 months. I would be really grateful if you guys could help me.
Thank you for the collaboration.
Do not turn it off. Seems that ends in instant brick. Try flashing the return to stock zip
crixley said:
Do not turn it off. Seems that ends in instant brick. Try flashing the return to stock zip
Click to expand...
Click to collapse
All right, will try. Thanks for the tip
Make sure you have a good cable and good fastboot in your computer
Sent from my PH-1 using XDA Labs
So I was able to pass through some problems from before, but one still persists. When I run the command "fastboot flash-all" on my command prompt, it shows all the options for fastboot, while only "flash-all" shows that there is no such command. I have also tried "fastboot flashall", but that shows the message:
error: neither -p product specified nor ANDROID_PRODUCT_OUT set.
Sorry, I know this is not the fastboot thread, but I'm really lost here.
Shiro744760 said:
So I was able to pass through some problems from before, but one still persists. When I run the command "fastboot flash-all" on my command prompt, it shows all the options for fastboot, while only "flash-all" shows that there is no such command. I have also tried "fastboot flashall", but that shows the message:
error: neither -p product specified nor ANDROID_PRODUCT_OUT set.
Sorry, I know this is not the fastboot thread, but I'm really lost here.
Click to expand...
Click to collapse
flash-all is a batch/script file, its not a fastboot command. You simply need to run on Windows
Code:
.\flash-all.bat
or Linux/MacOS
Code:
./flash-all.sh
Just open up a terminal/command prompt, type flash and then hit tab and it will autocomplete the full path.
It worked!
Thought it was already gone for good, I can barely believe it
Thank you very much for all of you, it really meant a lot your help!
Related
I've followed all the guides to a T. and my SDK is able to run nicely. However, once I've made contact w/ my device in 'usb debugging mode', tested the connection w/ "adb devices" in command prompt, and set the device to bootloader w/ the "adb reboot bootloader" command, and finally I give it the command to "fastboot oem unlock", I get an unknown error!! Please help. I have all the path variables set, and my SDK is running good, and has all the newest updates.
This is a link to a video I made of the problem. Please watch. It'll help if you can see the problem! just copy paste into search bar - youtube.com/watch?v=2bROUZh7GRI
Thanks for your responses. I hope they come quickly!
V0nice said:
I've followed all the guides to a T. and my SDK is able to run nicely. However, once I've made contact w/ my device in 'usb debugging mode', tested the connection w/ "adb devices" in command prompt, and set the device to bootloader w/ the "adb reboot bootloader" command, and finally I give it the command to "fastboot oem unlock", I get an unknown error!! Please help. I have all the path variables set, and my SDK is running good, and has all the newest updates.
This is a link to a video I made of the problem. Please watch. It'll help if you can see the problem! just copy paste into search bar - youtube.com/watch?v=2bROUZh7GRI
Thanks for your responses. I hope they come quickly!
Click to expand...
Click to collapse
OK, I will first say that I'm not an expert, but have gone through this process and have had to use ADB a number of times, so
1) why did you copy all the platform tools into tools folder? It should be otherway around, but clearly you have it working, so OK with that,
2) do you have all the files you need in your tools folder (since that's what you are using)?
3) are you using the proper syntax? No additional spaces where they don't belong, and so on?
4) are you getting any messages at all on the Xoom itself when you enter these commands?
5) Review all of your steps. Start over. If no luck, why not try to chat with experts on Xoom Channel on IRC? Maybe they can help you pinpoint the problem.
It doesn't seem serious but I think you've maybe missed a step in your prep work or have something simple turned around.
Good luck.
-copied to tools folder, because that's what I was directed to do... Guess it works either way.
-I do have all the files needed.
-How do I know if I'm using proper Syntax or not? that might be where I went wrong. But idk...
-No messages AT ALL on the xoom screen. (actually, 1 time out of the hundreds of times, Below the 'fastboot' words, I got red words that said cannot process command, or something like that.)
okantomi said:
OK, I will first say that I'm not an expert, but have gone through this process and have had to use ADB a number of times, so
1) why did you copy all the platform tools into tools folder? It should be otherway around, but clearly you have it working, so OK with that,
2) do you have all the files you need in your tools folder (since that's what you are using)?
3) are you using the proper syntax? No additional spaces where they don't belong, and so on?
4) are you getting any messages at all on the Xoom itself when you enter these commands?
5) Review all of your steps. Start over. If no luck, why not try to chat with experts on Xoom Channel on IRC? Maybe they can help you pinpoint the problem.
It doesn't seem serious but I think you've maybe missed a step in your prep work or have something simple turned around.
Good luck.
Click to expand...
Click to collapse
-copied to tools folder, because that's what I was directed to do... Guess it works either way.
-I do have all the files needed.
-How do I know if I'm using proper Syntax or not? that might be where I went wrong. But idk...
-No messages AT ALL on the xoom screen. (actually, 1 time out of the hundreds of times, Below the 'fastboot' words, I got red words that said cannot process command, or something like that.)
Ok. I'm unlocked now. New problem... >.< There's always something!! now when I try to flash the recovery image, I get an unknown error.
"C:\AndroidSDK\tools>fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.
img
sending 'recovery' (3998 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\AndroidSDK\tools>"
Anyone recognize why it would do this?
V0nice said:
Ok. I'm unlocked now. New problem... >.< There's always something!! now when I try to flash the recovery image, I get an unknown error.
"C:\AndroidSDK\tools>fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.
img
sending 'recovery' (3998 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\AndroidSDK\tools>"
Anyone recognize why it would do this?
Click to expand...
Click to collapse
Do you know what you did to be able to unlock? I think you really have to be careful to type commands EXACTLY as shown. No extra spaces, but don't leave anything out either. Looks like commands aren't typed in correctly. Take your time. You'll do it.
V0nice said:
Ok. I'm unlocked now. New problem... >.< There's always something!! now when I try to flash the recovery image, I get an unknown error.
"C:\AndroidSDK\tools>fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.
img
sending 'recovery' (3998 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\AndroidSDK\tools>"
Anyone recognize why it would do this?
Click to expand...
Click to collapse
I had this error followed by "unknown partition". When I tried fastboot boot recovery.img, it would say it could not access recovery. I deleted every partition and sent the device the stock imgs. Recovery would still fail.
STRANGELY ENOUGH, I rebooted my PC, unplugged the cable from the Xoom, let the device boot, changed USB debugging to on (stock unchecked it when imaged), and it took the recovery flash that time. I can't explain why, but it worked for me.
eqppwqqep said:
I had this error followed by "unknown partition". When I tried fastboot boot recovery.img, it would say it could not access recovery. I deleted every partition and sent the device the stock imgs. Recovery would still fail.
STRANGELY ENOUGH, I rebooted my PC, unplugged the cable from the Xoom, let the device boot, changed USB debugging to on (stock unchecked it when imaged), and it took the recovery flash that time. I can't explain why, but it worked for me.
Click to expand...
Click to collapse
So is everything ok now?
okantomi said:
So is everything ok now?
Click to expand...
Click to collapse
Yes. I am not rooted. am I supposed to change the thread to solved or something?
different error on trying to flash this recovery
I get a strange error when trying to "fastboot flash recovery-Tiamat-R4c-100611-1150-cwm.img I get:
error: cannot determine image filename for 'recovery-Tiamat-R4c-100611-1150-cwm.img
The file is there. In fact I have used this file before. Am I really hosed. Any ideas.
jesmitty said:
I get a strange error when trying to "fastboot flash recovery-Tiamat-R4c-100611-1150-cwm.img I get:
error: cannot determine image filename for 'recovery-Tiamat-R4c-100611-1150-cwm.img
The file is there. In fact I have used this file before. Am I really hosed. Any ideas.
Click to expand...
Click to collapse
If you haven't already. Delete the .img file. and reinstall it. try the process again.
make sure you're inputting the full command prompt from the beginning. That was my problem. Hope that helps.
jesmitty said:
I get a strange error when trying to "fastboot flash recovery-Tiamat-R4c-100611-1150-cwm.img I get:
error: cannot determine image filename for 'recovery-Tiamat-R4c-100611-1150-cwm.img
The file is there. In fact I have used this file before. Am I really hosed. Any ideas.
Click to expand...
Click to collapse
fastboot flash recovery(you missed this) recovery-Tiamat-R4c-100611-1150-cwm.im
Hello everyone.
I need a bit of help repairing my partitions on my Kindle.
To try and sum it up quickly, I am rooted, have FFF and TWRP installed. I decided to repartition my Kindle (using FireParted) to allow for more apps space. I did and everything went smooth. After installing some apps, I got a message saying my storage space was getting low. When I looked at the settings, I noticed that I had partioned my Kindle the wrong way. (Had more space for videos, music, pictures).
Sooo I decided to again repartition my Kindle once again using FireParted. Created a backup and let it do its thing. After 10 minutes I noticed the program still wasn't done and then it just stopped. Of course when I restarted it said that the partition couldn't be found. I tried restoring back up but it didn't find any. (wtf)
I then decided to try out the Unbrick utility but when I clicked on OTHER to see what other options were available, it immediately rebooted my Kindle and then I was stuck on the yellow triangle. I lost TWRP because I couldn't even boot into that. So I proceeded to uninstall/reinstall the drivers again. I ran the Kindle Fire Utility, it shows that I'm still rooted. Installed TWRP again and now I'm able to mount/unmount etc. but because my partion is all messed up. I'm unable to install a new ROM.
This is where I need help. I read about going into FASTBOOT mode with the KFU and then typing "fastboot oem format" but when I boot in FASTBOOT, I lose the TWRP and my computer/kfu/adb no longer recognizes the device. I tried entering the command through adb but I get a "'fastboot' is not recognized as a internal or external command".
So at this point I have no clue what to do or where to go. Any help would be appreciated.
Btw, I did look at this thread but it didn't help:
http://forum.xda-developers.com/showthread.php?t=1388996
sounds like you dont have fastboot.exe - issue the commands from the tools folder of kfu - there is fastboot.exe and all other commands you'll ever need
When I click on fastboot.exe from the tools folder of kfu, all it does is open and close right away nothing else. If I use the KFU to boot into fastboot it just gets stuck at activating fastboot but nothing happens.
to click it will not help you !
open an (elevated) command prompt and cd to the tools folder of kfu (ie "cd c:\kfu\tools")
now you can issue the suggested commands - ie "fastboot oem format"
if your drivers are ok the command should succeeed
b63 said:
to click it will not help you !
open an (elevated) command prompt and cd to the tools folder of kfu (ie "cd c:\kfu\tools")
now you can issue the suggested commands - ie "fastboot oem format"
if your drivers are ok the command should succeeed
Click to expand...
Click to collapse
Thanks for the help b63, I appreciate it.
I did what you said, elevated command prompt etc. Fastboot.exe worked correctly now. When I put "fastboot oem format" it just hangs on "waiting for device" but nothing ever happens. How long does this process normally take? It's been like 10 minutes now and no change. I don't know if the kindle is supposed to reboot or what. Right now it's on TWRP recovery...
ANDROID 3G said:
Thanks for the help b63, I appreciate it.
I did what you said, elevated command prompt etc. Fastboot.exe worked correctly now. When I put "fastboot oem format" it just hangs on "waiting for device" but nothing ever happens. How long does this process normally take? It's been like 10 minutes now and no change. I don't know if the kindle is supposed to reboot or what. Right now it's on TWRP recovery...
Click to expand...
Click to collapse
check your device manger - it's a driver issue
update the driver - the right one is "android adb interface"
if your driver is right there is another trick to try:
issue the command and let it sit on <waiting for device>
power down the kf by holding pwr button ~20sec - prw on again
the command should be picked up and finished
I had this problem when using FireParted as well. It causes problems on a stock ROM erasing partition 10 and 11. I was able to recover using the post you sent and have also my own instruction as well. http://forum.xda-developers.com/showthread.php?t=1453816
Hope this helps.
Hello,
Tried to update to lollipop like the rest of the world..well, i should have waited
At first i just ran the flash-all.bat (edited so it didn't include erase userdata and the -w option)
fastboot threw all sorts of errors, too many links, invalid argument
then i tried to run manually the commands, same thing. Not all of them "worked" at once.
Unfortunately I don't have a log.
So now i have a N7 that won't boot past the Google screen
I can get to bootloader but it shows on device manager as Unknown USB device, Device Descriptor Request Failed, so fastboot doesnt help.
I can also get to stock recovery and use adb just fine.
Is there anyway to fix this? sideloading anything?
So my dad went out and bought a nakasig/tilapia it's running Android 4.2.1 and bootloader is 4.13. Having just updated my razor/flo via fastboot everything was setup and working. "adb reboot bootloader" reboots the nakasig/tilapia into fastboot mode and "fastboot devices" shows the nakasig/tilapia serial number. Every other fastboot command just hangs there and does nothing. "fastboot oem unlock" does not prompt me to unlock bootloader. "fastboot reboot" doesn't even reboot the tablet. I use Linux so I figured I would try Windows following the thread sticky'd in this forum http://forum.xda-developers.com/showthread.php?t=2175086 same problem adb works fastboot will list the device but can't do anything with it. "fastboot getvar all" did give me an error however "FAILED (command write failed (Unknown error))" all the other commands just hang there doing nothing saying nothing. Having tried Windows and Linux setups which I have used on my other Nexus devices without issue I am starting to think its an issue with the bootloader maybe I need some older version of fastboot.
Is there a way to flash bootloader from inside Android or Recovery? I can use Towelroot to root the tablet then flash TWRP from Android and boot into TWRP but I don't think you can flash a bootloader from there or unlock the bootloader can you?
Edit: according to http://forum.xda-developers.com/showthread.php?t=2068207 the nakasig/tilapia bootloader is encrypted so you can't flash or unlock it without fastboot.
OK so you have a 2013 N7 that does not have this problem, but your dad's 2012 does. Two different pieces of hardware.
Could it be a driver issue? Sometimes when the drivers are not talking to it correctly you get these flaky results. Different USB cable/port?
Theoretically there is a flash all command you can use to flash an update of the whole thing including the bootloader without it being unlocked. However if you are getting write errors then you should really be cautious because that could just fry it instead of fixing it.
dextroamphetamine said:
So my dad went out and bought a nakasig/tilapia it's running Android 4.2.1 and bootloader is 4.13. Having just updated my razor/flo via fastboot everything was setup and working. "adb reboot bootloader" reboots the nakasig/tilapia into fastboot mode and "fastboot devices" shows the nakasig/tilapia serial number. Every other fastboot command just hangs there and does nothing. "fastboot oem unlock" does not prompt me to unlock bootloader. "fastboot reboot" doesn't even reboot the tablet. I use Linux so I figured I would try Windows following the thread sticky'd in this forum http://forum.xda-developers.com/showthread.php?t=2175086 same problem adb works fastboot will list the device but can't do anything with it. "fastboot getvar all" did give me an error however "FAILED (command write failed (Unknown error))" all the other commands just hang there doing nothing saying nothing. Having tried Windows and Linux setups which I have used on my other Nexus devices without issue I am starting to think its an issue with the bootloader maybe I need some older version of fastboot.
Is there a way to flash bootloader from inside Android or Recovery? I can use Towelroot to root the tablet then flash TWRP from Android and boot into TWRP but I don't think you can flash a bootloader from there or unlock the bootloader can you?
Edit: according to http://forum.xda-developers.com/showthread.php?t=2068207 the nakasig/tilapia bootloader is encrypted so you can't flash or unlock it without fastboot.
Click to expand...
Click to collapse
cmstlist said:
OK so you have a 2013 N7 that does not have this problem, but your dad's 2012 does. Two different pieces of hardware.
Click to expand...
Click to collapse
Correct.
cmstlist said:
Could it be a driver issue? Sometimes when the drivers are not talking to it correctly you get these flaky results.
Click to expand...
Click to collapse
ADB and fasboot use the same drivers don't they? While in Anroid adb works fine I can adb shell I can adb push/get I can adb reboot.
cmstlist said:
Different USB cable/port?
Click to expand...
Click to collapse
Tried every cable and port I have. Different computers even.
cmstlist said:
Theoretically there is a flash all command you can use to flash an update of the whole thing including the bootloader without it being unlocked. However if you are getting write errors then you should really be cautious because that could just fry it instead of fixing it.
Click to expand...
Click to collapse
NONE of the fastboot commands work except "fastboot devices"
dextroamphetamine said:
Correct.
ADB and fasboot use the same drivers don't they? While in Anroid adb works fine I can adb shell I can adb push/get I can adb reboot.
Click to expand...
Click to collapse
No, AFAIK they're different drivers, and different devices often require a distinct driver install too.
cmstlist said:
No, AFAIK they're different drivers, and different devices often require a distinct driver install too.
Click to expand...
Click to collapse
Got any sources on that info?
WOW
weird! really weird!
I really don't know what the issue, the fact that it happens on Linux and on Windows makes me think to an hardware realted issue, unfortunately..
As long as I know adb and fastboot do not use exactly the same drivers, but you download and install them together, so it should n not be a problem, this one..
The only think I can suggest you atm is to try with Linux by logging in as superuser (su). On my slackware with my "normal" user adb works as usual, but if I try to use fastboot the terminal says me No permissions..
I hope someway your distro has the same issue, even if your fastboot devices success!
So login as superuser and try to use fastboot. If you do not install it in /bin partition you should have to locate its directory and then use
./fastboot devices
or any other command but with ./fastboot instead of fastboot..
hope it helps.. I really hope!!
For that matter, on a whim... when you open a command prompt in Windows to adb to your device, try running Command Prompt as an Administrator. Sometimes Windows is weird like that.
Please keep questions in the Q&A section. Development sections are for development only.
Thread moved to Q&A.
Thanks,
Darth
Forum Moderator
EDIT: Fixed, see below.
Hello all, I have a Pixel 4 running the July build of Android (QQ3A.200705.002). I previously had it rooted with Magisk, but I have reset the phone and it's not longer rooted (verified; originally it was still rooted after a factory reset) .When I attempt to relock the bootloader, I type the command
Code:
fastboot flashing lock
However, fastboot just shows me the help message, as if I were to type 'fastboot help'.
When I try to manually flash an image using flash-all.bat (QQ3A.200705.002 for example), I get the following error:
Code:
error: failed to load 'image-flame-qq3a.200705.002.zip': Not enough space
If I try to manually flash individual images, I get various errors. For the boot image, I get an error that says no partition exists (like my boot_a slot isn't there. I can flash it into boot_b just fine). If I try to flash system, it tells me I need to be in fastbootd; I haven't looked up how to do that yet. I am a bit lost here, I've never had anything like this happen before, and the system is completely wiped from a factory reset, so there is plenty of available storage.
I figured out that I was able to update to the August build (QQ3A.200805.001) by sideloading the OTA update, but I still cannot lock the bootloader. This is what happens when I run the command (reference Fastboot 1.png).
I also tried it in Powershell ISE, and I'm getting this error (reference Fastboot 2.png)
Code:
+ FullyQualifiedErrorId : NativeCommandError
Almost like fastboot itself isn't recognizing the 'flashing' command.
Thoughts?
I was able to fix it by downloading the latest platform-tools from here: https://developer.android.com/studio/releases/platform-tools
However, I am pretty sure I was already on the latest platform-tools (I had flashed the phone numerous times on Android 10 already), but I digress.