I'm having a problem fastbooting a boot.img on my phone, I got the right room and have the bootloader unlocked and everything, but it keeps saying a command error from the phones side...... At least I think so.
Reinstall ADB drivers.
JJay666 said:
Reinstall ADB drivers.
Click to expand...
Click to collapse
That was the adb drivers, the same ones that I used to originally unlock the phone, you can't tell me that they weren't working, because they were working
I was trying to use them off of my windows 10 pc, but couldn't figure where the stupid folder went
Like, why would my adb drivers be not working even though it would work normally for unlocking the bootloader, and does it matter that I'm using the T-Mobile variant of the software?
youngherobrine1 said:
Like, why would my adb drivers be not working even though it would work normally for unlocking the bootloader, and does it matter that I'm using the T-Mobile variant of the software?
Click to expand...
Click to collapse
No it wouldn't. Try removing screen locks if any. Shouldn't be an issue if you can connect though. Easiest way is to use the AllinOne tool available here in this forum .
I had the same issue. I was trying to boot to the latest unofficial TWRP (fastboot boot twrp.img) and install it. I tried different USB ports, cables, etc... and even downloaded the official Google SDK (tools only) and replaced every binary on my laptop with them. Same thing (just slightly differently formatted output, but same "unknown command" error).
Fortunately, I realized that I only needed that to boot the phone prior to installing TWRP, which I already had (it was late!). I booted into the older installed TWRP and flashed the TWRP installer, then magisk.
I would still like to know what is happening, though. Like you said, this is the same Minimal ADB and Fastboot that I used to setup the phone in the first place.
Flapjack said:
I had the same issue. I was trying to boot to the latest unofficial TWRP (fastboot boot twrp.img) and install it. I tried different USB ports, cables, etc... and even downloaded the official Google SDK (tools only) and replaced every binary on my laptop with them. Same thing (just slightly differently formatted output, but same "unknown command" error).
Fortunately, I realized that I only needed that to boot the phone prior to installing TWRP, which I already had (it was late!). I booted into the older installed TWRP and flashed the TWRP installer, then magisk.
I would still like to know what is happening, though. Like you said, this is the same Minimal ADB and Fastboot that I used to setup the phone in the first place.
Click to expand...
Click to collapse
aparently I was using a chommand that wasnt working with the system, or was incomplete, heres the chommand I ended up using to get my phone rooted finally
fastboot flash boot magisk_patched.img
youngherobrine1 said:
aparently I was using a chommand that wasnt working with the system, or was incomplete, heres the chommand I ended up using to get my phone rooted finally
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
That command actually flashes recovery. I thought the proper method was to fastboot boot to the recovery, then run the installer.
Related
I tried to install the android revolution hd one 71.1 on my phone and it went out good so far into the installation but after the installation, i rebooted my phone and it went to a boot logo then went to the TWRP recovery mode. i tried deleting the cache and doing a reset but nothing is happening. please help me.
patrickgrantm said:
I tried to install the android revolution hd one 71.1 on my phone and it went out good so far into the installation but after the installation, i rebooted my phone and it went to a boot logo then went to the TWRP recovery mode. i tried deleting the cache and doing a reset but nothing is happening. please help me.
Click to expand...
Click to collapse
Having the same problem. The phone only reboots into twrp recovery mode, yet shows no errors when re-flashing device with most recent version of sense ui.
I'd really like to be able to use my phone.
lurkeratthegate said:
Having the same problem. The phone only reboots into twrp recovery mode, yet shows no errors when re-flashing device with most recent version of sense ui.
I'd really like to be able to use my phone.
Click to expand...
Click to collapse
Flash latest stock RUU. Once phone is fixed you can go for a custom rom again
LS.xD said:
Flash latest stock RUU. Once phone is fixed you can go for a custom rom again
Click to expand...
Click to collapse
I tried that. My computer is no longer recognizing the device at all. I thought I was making progress through the first part of the day, but for some reason, usb recognition seems to fluctuate.
I'm normally pretty alright working with this type of thing, but this phone has me completely baffled.
lurkeratthegate said:
I tried that. My computer is no longer recognizing the device at all. I thought I was making progress through the first part of the day, but for some reason, usb recognition seems to fluctuate.
I'm normally pretty alright working with this type of thing, but this phone has me completely baffled.
Click to expand...
Click to collapse
Really weird. So you have no chance to get into fastboot mode, not even by selection reboot to bootloader in twrp?!
LS.xD said:
Really weird. So you have no chance to get into fastboot mode, not even by selection reboot to bootloader in twrp?!
Click to expand...
Click to collapse
I supposed I should have been more clear. Fastboot will work, but all of the adb commands fail as the "device not found". I have tried restarting everything multiple times, updated all of the drivers, deleted the drivers, re-installed them, and while it makes the chime noise when I plug the phone in, all I can do is look at it in device manager. I'm running windows 8.1 and twrp 2.8.5.0, by the way.
lurkeratthegate said:
I supposed I should have been more clear. Fastboot will work, but all of the adb commands fail as the "device not found". I have tried restarting everything multiple times, updated all of the drivers, deleted the drivers, re-installed them, and while it makes the chime noise when I plug the phone in, all I can do is look at it in device manager. I'm running windows 8.1 and twrp 2.8.5.0, by the way.
Click to expand...
Click to collapse
RUU flashing is fastboot based I suppose. So you won't need adb at all.
LS.xD said:
RUU flashing is fastboot based I suppose. So you won't need adb at all.
Click to expand...
Click to collapse
Wait, what? I can flash images like twrp to my phone via fastboot, but the only ruu's I've found either have executable wizard files, or are self extracting. How can I flash a rom or update utility using fastboot?
lurkeratthegate said:
Wait, what? I can flash images like twrp to my phone via fastboot, but the only ruu's I've found either have executable wizard files, or are self extracting. How can I flash a rom or update utility using fastboot?
Click to expand...
Click to collapse
Connect phone in fastboot mode, run RUU, click next plenty of times, and done
If your phone is S-ON, flash stock recovery first and relock the bootloader before running the RUU
I had a bit of a problem with CM and it kept saying trebuchet had stopped working. (This is after the phone had been running fine for a whole year with CM. Then the phone kept restarting and saying trebuchet had stopped working and it would constantly restart until it calmed down. I decided to install and alternative launcher but the problem didn't totally go.
Thereafter I decided to delete trebuchet from root and boom the phone never calmed down and kept restarting. Eventually I tried restoring factor settings and it says now that there's no OS.
I had TWRP installed before but now when I've tried to install the latest one, it doesn't show any files on the OTG. I've put twrp on the SD along with a rom as well but nothing shows at all.
Can someone help in simple terms?
emmpii said:
I had a bit of a problem with CM and it kept saying trebuchet had stopped working. (This is after the phone had been running fine for a whole year with CM. Then the phone kept restarting and saying trebuchet had stopped working and it would constantly restart until it calmed down. I decided to install and alternative launcher but the problem didn't totally go.
Thereafter I decided to delete trebuchet from root and boom the phone never calmed down and kept restarting. Eventually I tried restoring factor settings and it says now that there's no OS.
I had TWRP installed before but now when I've tried to install the latest one, it doesn't show any files on the OTG. I've put twrp on the SD along with a rom as well but nothing shows at all.
Can someone help in simple terms?
Click to expand...
Click to collapse
Use adb commands to flash TWRP (Put your TWRP image in the same folder on your pc as your adb and enter each command separately):
adb reboot bootloader
fastboot flash recovery twrp.img (latest version is 3.1.1-0-peregrine, remame it to twrp.img - if that doesn't work rename twrp to recovery.img and try that).
fastboot reboot
If that works, restore you last known good working backup or try re-installing your stock rom.
sdembiske said:
Use adb commands to flash TWRP (Put your TWRP image in the same folder on your pc as your adb and enter each command separately):
adb reboot bootloader
fastboot flash recovery twrp.img (latest version is 3.1.1-0-peregrine, remame it to twrp.img - if that doesn't work rename twrp to recovery.img and try that).
fastboot reboot
If that works, restore you last known good working backup or try re-installing your stock rom.
Click to expand...
Click to collapse
I've installed fastboot onto my PC. Now i'm trying the adb commands but my phone isn't showing up
Tried a new cable.. so far it's started to recognise. I'll update this if theres news.
*adb command doesn't work... says no devices. Fastboot seems to work
ive managed to get the latest twrp on.. now I cant seem to adb sideload the rom nor does it show via otg.. ADB sideload disconnects and says invalid zip file
emmpii said:
I've installed fastboot onto my PC. Now i'm trying the adb commands but my phone isn't showing up
Tried a new cable.. so far it's started to recognise. I'll update this if theres news.
*adb command doesn't work... says no devices. Fastboot seems to work
Click to expand...
Click to collapse
Install or re-install your Motorola Device Manager on your pc from this link: https://mobilesupport.lenovo.com/us/en/solution/MS88481
Check in your pc Device Manager to see if your device is connected and recognized properly when you plug in the USB cable.
In the folder where your adb and fastboot files are, open a command prompt and enter adb devices to see if the phone is recognized now in adb. If it is, proceed as suggested earlier.
sdembiske said:
Install or re-install your Motorola Device Manager on your pc from this link: https://mobilesupport.lenovo.com/us/en/solution/MS88481
Check in your pc Device Manager to see if your device is connected and recognized properly when you plug in the USB cable.
In the folder where your adb and fastboot files are, open a command prompt and enter adb devices to see if the phone is recognized now in adb. If it is, proceed as suggested earlier.
Click to expand...
Click to collapse
shows up in device manager as android usb device, Still not showing on adb
I managed to get the device to finally track on with adb. It tracks fine now. However I can't seem to flash a rom on regardless of whether its OTG or sideload...
emmpii said:
shows up in device manager as android usb device, Still not showing on adb
Click to expand...
Click to collapse
Go to this link (https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816) and download the correct untouched rom for your phone model and transfer it to your sd card or internal memory.
Then try this command: fastboot boot recovery.img or fastboot boot twrp.img
and follow the directions exactly in the op in that thread to flash the rom.
sdembiske said:
Try this command: fastboot boot recovery.img or fastboot boot twrp.img
Go to this link (https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816) and download the correct untouched rom for your phone model and transfer it to your sd card or internal memory.
Then try this command: fastboot boot recovery.img or fastboot boot twrp.img
and follow the directions exactly in the op in that thread to flash the rom.
Click to expand...
Click to collapse
Absolutely no idea how but I managed to get one of the CM roms sideloaded and even though when i chose to reboot it said no OS. I've got it going, however I've forgotten to put gapps on so I'll try that now. Later on I'll try sideload stock rom or something and see how that goes. Thanks for the help so far! :good:
emmpii said:
Absolutely no idea how but I managed to get one of the CM roms sideloaded and even though when i chose to reboot it said no OS. I've got it going, however I've forgotten to put gapps on so I'll try that now. Later on I'll try sideload stock rom or something and see how that goes. Thanks for the help so far! :good:
Click to expand...
Click to collapse
The problem with CM roms is they're not really being updated anymore - just one of the problems I have with a lot of custom roms besides the bugs, etc., etc.
If you're hell bent on a custom rom, I would check out this one: [ROM][OFFICIAL][Peregrine][7.X] LineageOS 14.1 at https://forum.xda-developers.com/moto-g/4g-development/rom-cyanogenmod-14-0-t3469103
Lineage is the new go-to from CM. I personally would go back to stock first, however, to ensure everything is restored properly before installing it.
It's being updated regularly currently.
I just had a old CM rom downloaded from before hence I went to that lol. I'm trying lineage for now but I've also downloads the stock ROM. Whatever will keep the phone going
Maybe it's me not understanding what's new, I've "rooted" quite a few phones going back to the OG Droid - Motorola, Samsung, HTC. Never had any significant issue following directions and getting it done. Maybe things have changed over time. OG Pixel, 128GB, with sailfish-opr3.170623.008 (8.0.0). Auto-update disabled, USB debugging enabled, bootloader unlocked.
Setup: twrp-3.2.1-2-sailfish.img in platform-tools with adb and fastboot (latest versions). twrp-pixel-installer-sailfish-3.2.1-2.zip and Magisk-v16.0.zip at root of "Pixel/Internal Shared Storage". I also extracted a fresh boot.img from a factory image.
Just to make sure I'm starting fresh:
Code:
adb reboot bootloader
fastboot flash boot boot.img
fastboot --slot other flash boot boot.img
So far so good.
Code:
fastboot boot twrp-3.2.1-2-sailfish.img
TWRP comes up, I give it my PIN, it says decrypt OK, I tell it to install twrp-pixel-installer-sailfish-3.2.1-2.zip. Install seems fine, no errors reported. Back up a couple of levels, and "reboot recovery." It tries, eventually goes to a black screen for a few seconds, then does another reboot to system. No TWRP. Am I wrong in thinking I should be in TWRP at this point?
I can do the above, but flash Magisk-v16.0.zip instead, and I do end up with root, so that works. Just no way to get to TWRP except by fastbooting an external image.
I've also tried installing VerifiedBootSigner-v8.zip after installing twrp.zip, but that fails at the end with an "unable to verify..." or similar message. I'm not sure if that's supposed to be required or not currently, the TWRP install instructions don't mention it, but other guides do.
What am I doing wrong?
All I've ever done was boot to fastboot, adb boot <path-to-twrp>.img, and flash twrp. No need to use the boot signer anymore.
Sent from my Pixel using Tapatalk
Well, I can only guess that twrp-pixel-installer-sailfish-3.2.1-2.zip isn't compatible with the boot image in sailfish-opr3.170623.008.
I installed sailfish-opm1.171019.021-factory-68d3b69a.zip, then the twrp (and Majesk) install worked, just as expected.
So today my new One Plus 6 arrived. I tested it out for a bit made sure everything seemed to be working ok.
Then I unlocked bootloader, flashed twrp, magisk, all without issue. (I followed a guide I found on google) While setting everything up, I noticed that there was an update avaliable. So I installed that and got a message that the update will remove root. I thought "ok, i'll just have to do that again after. Update installed, rebooted device to recovery and realize TWRP is also gone after the update. So then I rebooted again to the bootloader and do fastboot devices command on my pc. Phone is there. Next I do the fastboot flash boot twrp.img command.
Sending.. Writing.. Finished... But I was still on the bootloader on the phone. I tried it a couple more times with no result. Restarted the phone only to boot into TWRP now. I thought to myself "hmm I'm not sure that's what's supposed to happen" but I continued to flash twrp.zip anyway. Rebooted the device.. TWRP booted again. Tried rebooting a couple more times with the same result.
Now, maybe this is where I messed things up more seriously. I'll also mention I foolishly didn't perform a backup on TWRP before doing all this. Not sure what to do, I flashed magisk as well. And I tried rebooting system, then when that didn't work I think I rebooted "slot B' for some reason.... After that it would only show the oneplus boot animation for a seemingly indefinite period of time.
I found I could get int the bootloader menu by holding vol up and power. Tried flashing TWRP, seemed to work on my computer's end but didn't boot recovery on phone. I rebooted into recovery from bootloader menu, brought me to endless oneplus boot animation again. Selecting start on the boot loader booted to TWRP. From there I rebooted back to slot A. Now it boots straight into TWRP.
I'm not sure what went wrong. I've rooted, installed various roms, etc on previous devices. Never had any issues before. But as I'm sure you can tell I don't really know what I'm doing. Does anyone have any advice? Thanks.
Your not supposed to fastboot flash the twrp, youre supposed to fastboot boot it. Just reflash stock boot.img and you'll be good
usernameisausername said:
I'm not sure what went wrong. I've rooted, installed various roms, etc on previous devices. Never had any issues before. But as I'm sure you can tell I don't really know what I'm doing. Does anyone have any advice? Thanks.
Click to expand...
Click to collapse
A number of things work differently on this phone. Don't assume any of your previous knowledge transfers over. There is a steep learning curve.
Stay away from random guides on Google. There are reliable guides here that, if you follow them to the letter, will keep you out of trouble.
fastboot flash boot [.IMG]
Is the issue. Should be
fastboot boot [.IMG]
On www.twrp.me/Devices you'll find the OnePlus 6 plus a corresponding how-to, directly from the source.
Your best bet:
1. Download the full ROM zip from either OnePlus directly or one of the links here on XDA.
2. Download latest TWRP files from twrp.me
3. fastboot boot [.IMG]
4. If in TWRP, connect to your PC and send the ROM over to your phone (MTP should work I think. Else, just ADB push it)
5. Flash the ROM in TWRP as you would flash any other ROM.
6. Should work, your system is now back to stock (also recovery). Let it boot once to be sure and then retry magisk but with the right fastboot commands.
To flash TWRP permanently, move the installer.zip you find on TWRP.me to your phone, fastboot boot the .IMG and flash the installer.zip in recovery.
Let me know if it worked
schwarzerfleck said:
4. If in TWRP, connect to your PC and send the ROM over to your phone (MTP should work I think. Else, just ADB push it))
Click to expand...
Click to collapse
MTP is disabled on most versions of twrp including official. There is an unofficial version with MTP working though it's a bit wonky.
iElvis said:
MTP is disabled on most versions of twrp including official. There is an unofficial version with MTP working though it's a bit wonky.
Click to expand...
Click to collapse
Yeah that's why I suggested the ADB push
schwarzerfleck said:
Yeah that's why I suggested the ADB push
Click to expand...
Click to collapse
So I'm having the same issue as OP currently and am somewhat a noob to this. I'm stuck booting into recovery, how do I adb push to the phone? its not showing up in adb devices at all
Eilermoon said:
So I'm having the same issue as OP currently and am somewhat a noob to this. I'm stuck booting into recovery, how do I adb push to the phone? its not showing up in adb devices at all
Click to expand...
Click to collapse
If you have USB debugging enabled, it's probably a driver problem. Windows 10 has issue with driver signatures and there's a setting that needs to be disabled. Do a search as it's been discussed (I use a Mac so I'm not certain what).
iElvis said:
If you have USB debugging enabled, it's probably a driver problem. Windows 10 has issue with driver signatures and there's a setting that needs to be disabled. Do a search as it's been discussed (I use a Mac so I'm not certain what).
Click to expand...
Click to collapse
Thanks for the info! If anyone has a source for this, that'd be awesome
So i recently decided to update my Oneplus 7 Pro from the public stable release to the OxygenOS 11 Open Beta 3 on a whim. Tried to go back to the old stable release by flashing fastboot roms from Tool All In One and it somehow broke everything, even though I did it multiple times before.
Phone can't boot into anything -- even with stock roms installed. Simply shows the bootloader is unlocked screen and nothing after. I can get into recovery and edl and fastboot, but nothing else. I think I flashed an older version from TAIO's fastboot rom flasher, making it impossible (!) for my computer to interact with my phone.
MSM Tool also doesn't work. Param preload, even though I have the QC and OP drivers installed.
Anything I can do?
You could try, moving the 10 stable on to a usb drive you could plug into the phone, then fastboot boot twrp.img via fastboot . Once in, format and install A10 from usb drive, done it many times
@soka said:
You could try, moving the 10 stable on to a usb drive you could plug into the phone, then fastboot boot twrp.img via fastboot . Once in, format and install A10 from usb drive, done it many times
Click to expand...
Click to collapse
That's just it -- I can't fastboot anything. Be it roms or TWRP.
Besides, my phone doesn't really interact with my computer so no adb. Only edl (i think).
VictimOfMagic said:
That's just it -- I can't fastboot anything. Be it roms or TWRP.
Besides, my phone doesn't really interact with my computer so no adb. Only edl (i think).
Thanks for replying
Click to expand...
Click to collapse
Sorry about that bud, sounds like your drivers are not installed properly. Maybe start there. I used the tool in one app to install the needed drivers. Worth a shot.
Try this post
Fastboot waiting for any device
Hello everybody, I was trying to update my Magisk and that process failed. I thought nothing of it put it off. Tried to restart my phone a few days later and now it's stuck in a fastboot loop. Cannot even go into recovery. So I'm like okay...
forum.xda-developers.com
@soka said:
Sorry about that bud, sounds like your drivers are not installed properly. Maybe start there. I used the tool in one app to install the needed drivers. Worth a shot.
Try this post
Fastboot waiting for any device
Hello everybody, I was trying to update my Magisk and that process failed. I thought nothing of it put it off. Tried to restart my phone a few days later and now it's stuck in a fastboot loop. Cannot even go into recovery. So I'm like okay...
forum.xda-developers.com
Click to expand...
Click to collapse
Well, TIAO only installs google's WinUSB. I already had that installed. I just don't know why I keep getting stuck on the param preload, even with all the drivers that could be needed being installed. Maybe it has something to do with the OOS version? I have GM1915, fastboot flashed to 10.0.4 Global.
Also, I think i messed up my msm tool since now it always says connected lmao
VictimOfMagic said:
Well, TIAO only installs google's WinUSB. I already had that installed. I just don't know why I keep getting stuck on the param preload, even with all the drivers that could be needed being installed. Maybe it has something to do with the OOS version? I have GM1915, fastboot flashed to 10.0.4 Global.
Also, I think i messed up my msm tool since now it always says connected lmao
Thanks for replying.
Click to expand...
Click to collapse
I had the same problem with drivers. (I tried the ones that come with the device (in an .iso image I think?) and then I tried with the patched L2 drivers.)
What worked for me: installing the ALL IN ONE tool (on windows) then runing it as administrator*, then installing the drivers from within the All In One Tool program.
md5hasher said:
I had the same problem with drivers. (I tried the ones that come with the device (in an .iso image I think?) and then I tried with the patched L2 drivers.)
What worked for me: installing the ALL IN ONE tool (on windows) then runing it as administrator*, then installing the drivers from within the All In One Tool program.
Click to expand...
Click to collapse
Running TAIO as an admin? That still only downloads WinUSB.
Can you expand on what you mean?
Under windows 10 open CMD as admin and enter bcdedit /set testsigning on
now reboot. This resolved for me the driver issue and phone was then correctly seen by msm unbrick tool