I'm trying to root my OnePlus 6T, and i've got to the point of trying to fastboot with the twrp img file. when i type ./fastboot boot twrp-3.2.3-x_blu_spark_v9.91_op6.img into powershell, while the device is the unlocked bootloader, the device disconnects from my pc and just sits on the "Fastboot Mode" screen with the OnePlus logo. if i try to enter ./adb sideload twrp-3.2.3-x_blu_spark_v9.91_op6.zip, powershell gives me the following error message: "adb: sideload connection failed: no devices/emulators found". i've tried all sorts of different combinations but nothing works. i even added the zip file to my devices root folder to try and manually update it, but the file doesn't show in the update screen, only saying "please add the update file to the root folder". what does the "Advance, ADB sideload" part of this article mean: https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ this is what i've been following, but i have clearly done something wrong, but i can't tell what that is.
Hmm... Now I have never used blu_spark but as you said your using the version for the 6 on a 6t is it compatible.. have you tried https://forum.xda-developers.com/on...ficial-twrp-touch-recovery-t3861482?nocache=1
@ikako
I use the themed TWRP from here https://forum.xda-developers.com/on...covery-theme-blacked-twrp-acuicultor-t3847752
But I suggest booting twrp using fastboot from your pc then flashing the twrp installer zip and magisk. That's how I've always installed recovery on my 6t and never an issue.
I did see an xda thread a few days ago specifically for installing Blu Spark TWRP. Let me see if I can find a link real quick ..brb
Related
Hey guys, I'm at a lost here. I don't think I'm that stupid but I am following all steps from the guides to install TWRP without luck. I already managed to unlock my bootloader with Axon7Toolkit. I already certified that QUSB_Bulk driver is installed, I did it with Zadig, but when in EDL mode, even after killing adb, the axon7tool can't find it. I tried installing a zip with the toolkit but when I choose the package, the toolkit simply closes. Is that me? My phone?
Thank you!
gibawatts said:
Hey guys, I'm at a lost here. I don't think I'm that stupid but I am following all steps from the guides to install TWRP without luck. I already managed to unlock my bootloader with Axon7Toolkit. I already certified that QUSB_Bulk driver is installed, I did it with Zadig, but when in EDL mode, even after killing adb, the axon7tool can't find it. I tried installing a zip with the toolkit but when I choose the package, the toolkit simply closes. Is that me? My phone?
Thank you!
Click to expand...
Click to collapse
What software version are you on?
I was at latest nougat but I downgraded to B10
Doing it via fastboot never fails for me.
Get to fastboot put two img in adb folder (I rename it for ease of typing since I suck) rename to recovery.img
Type this cmd in adb
Fastboot flash recovery recovery.img
Reboot to recovery and root. Done deal
download 3.1.0.0 twrp into your download folder on your desktop enter fastboot into your phone open up your command prmt type fastboot devices, your phone should appear then type fastboot flash recovery then go to the twrp right click drag it into the command prmt air page and place it there. you should see the file then hit enter. It'll take like 5 seconds it's really fast then reboot t recovery. when in twrp it'll ask you to install it again say no and uncheck the to options. DONE.
After loads of stress and bangs on the table I managed to unlock, install TWRP, LOS and root. I removed every driver related to my cell phone, deleted everything I download from it and started from scratch. I installed TWRP via fastboot but wasn't able to enter recovery mode, than I mase the stupidity to lock the bootloader back and got stuck in that password screen. Then I gave another go with the toolkit, unlocked it again and, I don't know how or why, it finally booted TWRP. Now everything is OK. Glad to be back to "Nexus mode" after so many time.
Thank you!
Hi guys,
Unable to boot after c*cking up a manual upgrade from B10 to B11 on my A2017G and would love your input. I feel like if I can just install TWRP again it should be an easy fix. Here's some specifics:
1. my phone is unlocked, rooted and running stock firmware.
2. I was trying to install stock recovery to install the B11 update. I did so but also tried to install another zip (B10 bootloader?) which I seem to have flashed wrong. Now just get the screen as shown on attachment and cannot boot.
3. Stock recovery seems to have been flashed and I can boot to this. From here I can boot to bootloader but can't seem to do anything from there.
4. I try update via ADB with the sideload command, but get the message "E:footer is wrong. E: Signature verification failed. Installation aborted".
5. I try to Update from SD as have the firmware zip file and TWRP on the root of my external SD card, but get the message "Couldn't Mound /sdcard, aborted."
6. The only time my phone shows as a connected device in ADB is when I try to sideload files. No other ADB code seems to work, only get the message "error: closed" on the terminal.
Assuming I've got all the firmware files (and full backups on my external SD) I feel like if I can just install TWRP again it should be an easy fix. So, any ideas on how I install TWRP given situation above?
Best,
Neil
nstirton said:
Hi guys,
Unable to boot after c*cking up a manual upgrade from B10 to B11 on my A2017G and would love your input. I feel like if I can just install TWRP again it should be an easy fix. Here's some specifics:
1. my phone is unlocked, rooted and running stock firmware.
2. I was trying to install stock recovery to install the B11 update. I did so but also tried to install another zip (B10 bootloader?) which I seem to have flashed wrong. Now just get the screen as shown on attachment and cannot boot.
3. Stock recovery seems to have been flashed and I can boot to this. From here I can boot to bootloader but can't seem to do anything from there.
4. I try update via ADB with the sideload command, but get the message "E:footer is wrong. E: Signature verification failed. Installation aborted".
5. I try to Update from SD as have the firmware zip file and TWRP on the root of my external SD card, but get the message "Couldn't Mound /sdcard, aborted."
6. The only time my phone shows as a connected device in ADB is when I try to sideload files. No other ADB code seems to work, only get the message "error: closed" on the terminal.
Assuming I've got all the firmware files (and full backups on my external SD) I feel like if I can just install TWRP again it should be an easy fix. So, any ideas on how I install TWRP given situation above?
Best,
Neil
Click to expand...
Click to collapse
Are you able to boot into EDL mode by typing ADB reboot edl ?
If so you can flash desired recovery with axon7tool
marcus.linkenbach said:
Are you able to boot into EDL mode by typing ADB reboot edl ?
If so you can flash desired recovery with axon7tool
Click to expand...
Click to collapse
Hi, thanks for your reply. Unfortunately not, just get the message "error: closed" in the terminal. Is there a button combination I could press in order to get into EDL?
nstirton said:
Hi, thanks for your reply. Unfortunately not, just get the message "error: closed" in the terminal. Is there a button combination I could press in order to get into EDL?
Click to expand...
Click to collapse
Try vol+ + vol- + power
it seems that the only time my device will show as connected in ADB is when I navigate through Recovery and select the "Apply Update from ADB" option. But even then, whilst it shows as connected, it only seems to allow the "sideload" command. Please see screenshot of Terminal. So at no other time will it show as a connected device.
Similarly, to have it show up in Device Manager, it'll only show when I switch the phone off, hold down Vol+ & Vol- and attached the power cable.
You are still on MM. So you are able to boot into bootloader.
adb reboot bootloader
fastboot devices
Now it should show your device as fastboot
If so you can now flash recovery with “fastboot flash recovery recovery.img“
marcus.linkenbach said:
You are still on MM. So you are able to boot into bootloader.
adb reboot bootloader
fastboot devices
Now it should show your device as fastboot
If so you can now flash recovery with “fastboot flash recovery recovery.img“
Click to expand...
Click to collapse
Thanks for your reply. Unfortunately as mentioned the only time my device shows as connected in Terminal is when I select "Update via ADB" whilst in recovery. Otherwise the device never shows as connected in adb.
So unfortunately fastboot doesn't seem to be an option for me.
Perhaps my drivers are out of whack but assuming what I've done to my phone hasn't changed that, it must be something PC - side.
nstirton said:
Thanks for your reply. Unfortunately as mentioned the only time my device shows as connected in Terminal is when I select "Update via ADB" whilst in recovery. Otherwise the device never shows as connected in adb.
So unfortunately fastboot doesn't seem to be an option for me.
Perhaps my drivers are out of whack but assuming what I've done to my phone hasn't changed that, it must be something PC - side.
Click to expand...
Click to collapse
But what if it shows your device as sideload? Can't you there reboot into fastboot?
No, it doesn't accept the command. Only one accepts is sideload. You can see from my screenshot a few posts back that the device is connected but shows different to how it normally would.
Breakthrough!
I seemed to follow the steps I've tried 100 times today and I now have TWRP installed again!
Thanks again to those who helped
I am attempting to put lineageos on my new Mi A1, following the installation guide here https://wiki.lineageos.org/devices/tissot/install
I have previously installed lineage on my old Moto G LTE and a Samsung Galaxy S4 and have not run into issues.
I have unlocked the bootloader and all that but I can't get twrp to boot.
I boot into fastboot with
Code:
adb reboot bootloader
that works fine, then I
Code:
fastboot boot twrp-3.2.2-0-tissot.img
This seems to have no effect, other than my phone 'disconnecting' from the PC.
I get the following terminal output
Code:
./fastboot boot .\twrp-3.2.2-0-tissot.img
Downloading 'boot.img' OKAY [ 0.682s]
booting OKAY [ 0.623s]
Finished. Total time: 1.336s
However nothing happens on the phone, it still just has the fastboot logo on it.
At this point if I manually reboot (long-press power) it will reboot into stock rom.
If I manually reboot into recovery (long-press power+volume up) it will reboot into stock recovery
I have ensured my sytem tools are up to date, and tried the previous version of twrp, and there is no change.
I WAS able to get twrp to boot using the "Mi A1 Tool" i found here https://forum.xda-developers.com/mi-a1/how-to/tool-xiaomi-mi-a1-tool-drivers-unlock-t3742857
However I was not able to install lineage due to an error.
I did not copy the exact output but it was something along the lines of
error 7, kInstallDeviceOpenError
After this attempt, I reflashed the stock rom using Xiaomi tools, and am back to the beginning.
The phone is fully up-to-date with stock updates, Android 8.1, July security update.
Once again went through the bootloader unlocking, and everything, but have arrived at the same result.
Anyone have any ideas?
any help would be greatly appreciated!
Thanks!
Hey, could you try this TWRP made for Oreo? https://www.androidfilehost.com/?fid=818070582850498337 (thread: https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472)
I've also had some issues booting TWRP, but running
Code:
fastboot oem unlock
was enough to boot it successfully (
Code:
fastboot boot recovery-3.2.1-2-oreo.img
)
Thank you!
dgadelha said:
Hey, could you try this TWRP made for Oreo? https://www.androidfilehost.com/?fid=818070582850498337 (thread: https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472)
I've also had some issues booting TWRP, but running
Code:
fastboot oem unlock
was enough to boot it successfully (
Code:
fastboot boot recovery-3.2.1-2-oreo.img
)
Click to expand...
Click to collapse
This recovery image worked great, AND installed lineage, thank you very much.
However, I am now unable to get gapps working.
I was pointed to this changelog here https://lineageos.org/Changelog-19/ by a user in the lineage subreddit.
I rebooted from twrp into the lineage recovery, chose Apply Update -> Apply from ADB
On my PC I run
Code:
./adb sideload .\MindTheGapps-8.1.0-arm64-20180610_024023
.zip
and after a pause I get the output
Code:
serving: '.\MindTheGapps-8.1.0-arm64-20180610_024023.zip' (~0%) adb: failed to read command: No error
and sometimes I get
Code:
serving: '.\MindTheGapps-8.1.0-arm64-20180610_024023.zip' (~0%) adb: failed to read command: Connection reset by peer
What happens on the phone has been a little different each time I have attempted this.
It either pops up on screen that it is unable to verify the file, install anyway?, doing so doesn't work.
OR it is hung up on a progress bar screen, with the following log output, or a slight variation of it
Code:
Stopping adbd...
Now send the package you want to apply to the device with "adb sideload <filename>"...
Finding update package...
Opening update package...
Verifying update package...
E: Signature verification failed
E:error: 21 Restarting dbd... Installation aborted.
After many attempts of this, reflashing lineage, and trying again, it did miraculously start doing the transfer at one point. It got to 47% then failed again.
Can't you just install from recovery?
https://forum.xda-developers.com/mi-a1/development/rom-lineageos-15-1-t3757938
pidermin said:
This recovery image worked great, AND installed lineage, thank you very much.
However, I am now unable to get gapps working.
I was pointed to this changelog here https://lineageos.org/Changelog-19/ by a user in the lineage subreddit.
I rebooted from twrp into the lineage recovery, chose Apply Update -> Apply from ADB
On my PC I run
Code:
./adb sideload .\MindTheGapps-8.1.0-arm64-20180610_024023
.zip
and after a pause I get the output
Code:
serving: '.\MindTheGapps-8.1.0-arm64-20180610_024023.zip' (~0%) adb: failed to read command: No error
and sometimes I get
Code:
serving: '.\MindTheGapps-8.1.0-arm64-20180610_024023.zip' (~0%) adb: failed to read command: Connection reset by peer
What happens on the phone has been a little different each time I have attempted this.
It either pops up on screen that it is unable to verify the file, install anyway?, doing so doesn't work.
OR it is hung up on a progress bar screen, with the following log output, or a slight variation of it
Code:
Stopping adbd...
Now send the package you want to apply to the device with "adb sideload <filename>"...
Finding update package...
Opening update package...
Verifying update package...
E: Signature verification failed
E:error: 21 Restarting dbd... Installation aborted.
After many attempts of this, reflashing lineage, and trying again, it did miraculously start doing the transfer at one point. It got to 47% then failed again.
Click to expand...
Click to collapse
Hey,
Install GApps also at TWRP. Signature verification is failing most probably because the Lineage Recovery should be accepting only Lineage-signed ZIP files.
You can install TWRP in your current boot image (so you don't need to boot TWRP everytime through fastboot) with this ZIP: https://www.androidfilehost.com/?fid=746010030569959456 (yet, you need to boot to TWRP through fastboot so you can flash it, but no need to boot it manually after installing it). Notice that after every system update you may need to install TWRP again (same for Magisk), as boot images get replaced.
Also, if sideload fails, you can just do a
Code:
adb push filename.zip /sdcard/
then install the ZIP directly from the "Install" section on TWRP.
Thanks!
Thanks a lot!
I found and was able to follow this guide
https://forum.xda-developers.com/mi-a1/how-to/lineageos-gapps-magisk-twrp-dolbyatmos-t3762939
instead of the one on the lineageOS website, and I am up and running.
Thank you very much for your time!
Can't boot to recovery or fastboot
I'm totally not getting the problem, i am having network issues on my Mi A1 on both Oreo and pie. So I decided to install a custom ROM but I can't boot my device to fastboot or recovery, it simply reboots . I tried the hard keys as well as through the PC using command prompt it just reboots normally. Any suggestions on what should I do Please?
Azan Qazi said:
I'm totally not getting the problem, i am having network issues on my Mi A1 on both Oreo and and pie. So I decided to install a custom ROM but I can't boot my device to fastboot or recovery, it simply reboots . I tried the hard keys as well as through the PC using command prompt. Any suggestions on what should I do.
Click to expand...
Click to collapse
Have you tried doing reboot in the OS and choosing Recovery option?
Azan Qazi said:
I'm totally not getting the problem, i am having network issues on my Mi A1 on both Oreo and pie. So I decided to install a custom ROM but I can't boot my device to fastboot or recovery, it simply reboots . I tried the hard keys as well as through the PC using command prompt it just reboots normally. Any suggestions on what should I do Please?
Click to expand...
Click to collapse
TrueMS said:
Have you tried doing reboot in the OS and choosing Recovery option?
Click to expand...
Click to collapse
yes sir I did tried several times. But as I said above it simply reboots the system.
I am following this guide here to root oneplus 6t (european variant), 9.0.5 Android:
https://www.xda-developers.com/onepl...otloader-root/
bootloader is unlocked and I can see there is a positive connection between phone and PC by checking the output on adb devices and fastboot devices. both work as intended.
the problem is that when I try to adb sideload, it says that I need version 1.0.32. so this means I cannot flash the custom recovery.
any tips? been looking online for quite some time now and cannot figure out what to do anymore. where can I find this 1.0.32 adb version?
I am a long time user on nexus 5 and just bought this phone, want to root it aswell. (note: this does not mean I have high level of knowledge on these types of hacks, just wanted to have this clear.)
Are you trying to boot or to flash the recovery from adb ? If you're trying to install the recovery from adb it wont work, on a/b devices the recovery is part of the boot image wich needs to be patched, boot twrp.img and then get the bluespark twrp zip and flash it.
nikexv2 said:
Are you trying to boot or to flash the recovery from adb ? If you're trying to install the recovery from adb it wont work, on a/b devices the recovery is part of the boot image wich needs to be patched, boot twrp.img and then get the bluespark twrp zip and flash it.
Click to expand...
Click to collapse
I can start the twrp, the problem is when I go into adb sideload and try to flash it. on pc is says "error" and on the phone it says I need to get adb 1.0.32. I am trying to flash that bluespark recovery with no luck.
cesar.maranhao said:
I can start the twrp, the problem is when I go into adb sideload and try to flash it. on pc is says "error" and on the phone it says I need to get adb 1.0.32. I am trying to flash that bluespark recovery with no luck.
Click to expand...
Click to collapse
You need to flash the zip from within the recovery that you booted using adb, not sideload it.
I already tried that, copied the files to the phone but when I try to access them through the bootable trwp, I cannot access them.
cesar.maranhao said:
I already tried that, copied the files to the phone but when I try to access them through the bootable trwp, I cannot access them.
Click to expand...
Click to collapse
wrong twrp used. you correct twrp and it will work. like this twrp https://forum.xda-developers.com/on...covery-theme-blacked-twrp-acuicultor-t3847752 or https://forum.xda-developers.com/devdb/project/?id=27466#downloads the choice is yours alone to make.
you are asking for help with 6t in the 6 form. whats wrong with this? you should be at this link https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Can't flash via TWRP, "failed mount system", twrp sideload not working either.. stuck
I need my phone for work tomorrow so any help would be greatly appreciated.
I'm on TWRP 3.2.3-1 and was using the latest stock oreo rom from here: https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
My phone suddenly didn't have a reception today, after rebooting I regained reception but couldn't make calls. I rebooted to recovery and tried to dirty flash the same stock twrp flashable oreo rom that I was using and it failed. Apparently the OS got corrupted. I tried repeatedly to flash the ROM and then noticed I was getting an error : failed to mount system , invalid argument. I couldn't mount system via the Mount tab in TWRP and I couldn't find anything helpful to resolve this error.
I did some more research downloaded the fastboot flashable ROM from here : https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433 and tried to flash the rom via adb using adb sideload in twrp but twrp doesn't seem to load that function correctly. In the elevated command prompt in the adb directory I type adb sideload filename.zip and it just freezes up my PC. My device does show up with the adb devices command and shows " *Serial Number* RECOVERY ".
I don't understand what to do with the instructions in the fastboot flash stock thread I posted above and I'm at the limit of my knowledge. No idea how to proceed... any help is greatly appreciated.
I tried extracting the xml.zip into the adb folder and rebooted to bootloader/AP Fastboot Flash Mode and was going to try the commands in the fastboot Rom thread but my device only shows up in adb devices when I load twrp. uhhhhgggghhhhhh guess I'll have to buy a backup phone tomorrow while I try to get this one working
Holy hell.... I didn't realize since I was in the fastboot/bootloader I had to use "fastboot devices" command to see the device. Tried that and saw the device listed, so I created a .bat file using the commands in the fastboot roms thread above and I have a functional device again. Whohoooooo!
Did you try to format /System/ as EXT4?