Hello, today i've successfully rooted my Pixel 3 with magisk and everything seems to be working fine except, i cant install TWRP.
i get the following upon doing fastboot boot twrp.img
Sending 'boot.img' (65536 KB) OKAY [ 2.169s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
i've tried mulitple USB A to USB C cables, and even usb-c to usb-c because my laptop has that port. Someone Please help
AmberKat said:
Hello, today i've successfully rooted my Pixel 3 with magisk and everything seems to be working fine except, i cant install TWRP.
i get the following upon doing fastboot boot twrp.img
Sending 'boot.img' (65536 KB) OKAY [ 2.169s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
i've tried mulitple USB A to USB C cables, and even usb-c to usb-c because my laptop has that port. Someone Please help
Click to expand...
Click to collapse
If you're on Android 10, twrp doesn't work. You really don't need it now anyway.
jd1639 said:
If you're on Android 10, twrp doesn't work. You really don't need it now anyway.
Click to expand...
Click to collapse
So downgrading back to Pie will solve the issue?
AmberKat said:
So downgrading back to Pie will solve the issue?
Click to expand...
Click to collapse
If you're adamant about having twrp, yes.
Xdevillived666 said:
If you're adamant about having twrp, yes.
Click to expand...
Click to collapse
I have the same issue, how can i flash a custom kernel and magisk without twrp in Android 10 please?
luizffgarcia said:
I have the same issue, how can i flash a custom kernel and magisk without twrp in Android 10 please?
Click to expand...
Click to collapse
For a custom kernel, you will need to use a kernel manager (EX kernel manager or FK kernel manager). Both are a small amount of money that is of course well worth it to support the devs. As for Magisk, you need to install the Magisk Manager canary APK and then patch boot to root.
sliding_billy said:
For a custom kernel, you will need to use a kernel manager (EX kernel manager or FK kernel manager). Both are a small amount of money that is of course well worth it to support the devs. As for Magisk, you need to install the Magisk Manager canary APK and then patch boot to root.
Click to expand...
Click to collapse
Thanks, i already have EX manager, and i have just rooted with canary. Cheer
luizffgarcia said:
Thanks, i already have EX manager, and i have just rooted with canary. Cheer
Click to expand...
Click to collapse
Easy peasy!
jd1639 said:
If you're on Android 10, twrp doesn't work. You really don't need it now anyway.
Click to expand...
Click to collapse
Why is TWRP not needed in Android 10? I have the same issue as the OP with fastboot boot hanging at sending boot.img, but a different reason for wanting TWRP to boot, namely to make a nandroid backup. I do not want to flash twrp, just boot as I have done for years pre OS10. I have no interest in backing up on Google servers, just wish to do a nandroid. Is there some other way to do this in OS10 without root?
Thanks, John
John Markley said:
Why is TWRP not needed in Android 10? I have the same issue as the OP with fastboot boot hanging at sending boot.img, but a different reason for wanting TWRP to boot, namely to make a nandroid backup. I do not want to flash twrp, just boot as I have done for years pre OS10. I have no interest in backing up on Google servers, just wish to do a nandroid. Is there some other way to do this in OS10 without root?
Thanks, John
Click to expand...
Click to collapse
Android 10's file structure is different so you won't be able to boot or flash twrp. Teamwin may figure out how to get twrp to work on it someday but for now it doesn't. So no nandriod, you'll need to find another way to backup if that's what you're looking to do.
jd1639 said:
Android 10's file structure is different so you won't be able to boot or flash twrp. Teamwin may figure out how to get twrp to work on it someday but for now it doesn't. So no nandriod, you'll need to find another way to backup if that's what you're looking to do.
Click to expand...
Click to collapse
Thank you. I'll just do adb backups then, unless Teamwin solves it. Until now I've always done both adb and nandroid.
I am currently on Android 9 and going to upgrade to the latest 10.
Is there anything chance for me to do a full image backup of the phone in advance before upgrading.
In case that the Android 10 doesn't fit me very well, I can roll back to Android 9 without losing any files.
Appreciate your comments and thank you in advance for the assistance.
jd1639 said:
Android 10's file structure is different so you won't be able to boot or flash twrp. Teamwin may figure out how to get twrp to work on it someday but for now it doesn't. So no nandriod, you'll need to find another way to backup if that's what you're looking to do.
Click to expand...
Click to collapse
Related
Hi guys
I was trying some of custom rom on my OP6 and I wanted to go back to Oxygen OS. So i did a clean installation with system wipe and i flashed the last full OTA update. But since i can't boot to system anymore, TWRP always displays that there is no OS installed despite the fact that I've tried several rom . Is this the first time it's done this to me how can I fix it?
raptax said:
Hi guys
I was trying some of custom rom on my OP6 and I wanted to go back to Oxygen OS. So i did a clean installation with system wipe and i flashed the last full OTA update. But since i can't boot to system anymore, TWRP always displays that there is no OS installed despite the fact that I've tried several rom . Is this the first time it's done this to me how can I fix it?
Click to expand...
Click to collapse
The best suggestion I can give you is to flash stock oos with TWRP, reboot to stock recovery, without flashing anything else, wipe data from stock recovery and startup system.. if it is working you can flash back TWRP and magisk if you need it
Just be careful because at your point is easy to lose all of your stored data
Hitman478™ said:
The best suggestion I can give you is to flash stock oos with TWRP, reboot to stock recovery, without flashing anything else, wipe data from stock recovery and startup system.. if it is working you can flash back TWRP and magisk if you need it
Just be careful because at your point is easy to lose all of your stored data
Click to expand...
Click to collapse
I tried your solution ..... and it worked thx man
I don't know why there was a problem with TWRP but the important thing is that my phone is alive again
raptax said:
I tried your solution ..... and it worked thx man
I don't know why there was a problem with TWRP but the important thing is that my phone is alive again
Click to expand...
Click to collapse
Exactly! I'm glad to had help you sometimes if something is done wrong TWRP is dangerous
raptax said:
I tried your solution ..... and it worked thx man
I don't know why there was a problem with TWRP but the important thing is that my phone is alive again
Click to expand...
Click to collapse
If you wipe system, then flash oos ROM, TWRP will think there is no os. You can just ignore and boot.
Wiping system then flashing any time will make twrp display "no os installed" it does this because it hasn't created files for twrp to check if you have a ton installed. Flashing twrp then rebooting to twrp fixes it.
Reboot to stock recovery?
Hitman478™ said:
The best suggestion I can give you is to flash stock oos with TWRP, reboot to stock recovery, without flashing anything else, wipe data from stock recovery and startup system.. if it is working you can flash back TWRP and magisk if you need it
Just be careful because at your point is easy to lose all of your stored data
Click to expand...
Click to collapse
Hi, need a little bit of support, since I'm new to this as well. I was in a working OOS open beta 25/28, but then I think I flashed the wrong zip (OOS 9.0.9?), and I was not able to boot to system. It kept going to "bootloader unlocked" screen and custom recovery. Currently in TWRP blu_spark 3.3.1-x v. 9.109, and it's showing me no OS installed when I attempt to reboot. I haven't rebooted to system yet.
All the folders in my /sdcard is gibberish... if I try to push a file to it, it says "Required key not available." I did remove all security/passwords from my phone before doing any updates/backups.
I completed a wipe cache/dalvik/system via TWRP, and flashed the OOS OTA stable Android 10 zip downloaded directly from OnePlus Support. Considering this situation, do you still think it's safe for me to reboot to system? Then how do I get to stock recovery from there--is that by holding down the buttons?
5xonlineage said:
Hi, need a little bit of support, since I'm new to this as well. I was in a working OOS open beta 25/28, but then I think I flashed the wrong zip (OOS 9.0.9?), and I was not able to boot to system. It kept going to "bootloader unlocked" screen and custom recovery. Currently in TWRP blu_spark 3.3.1-x v. 9.109, and it's showing me no OS installed when I attempt to reboot. I haven't rebooted to system yet.
All the folders in my /sdcard is gibberish... if I try to push a file to it, it says "Required key not available." I did remove all security/passwords from my phone before doing any updates/backups.
I completed a wipe cache/dalvik/system via TWRP, and flashed the OOS OTA stable Android 10 zip downloaded directly from OnePlus Support. Considering this situation, do you still think it's safe for me to reboot to system? Then how do I get to stock recovery from there--is that by holding down the buttons?
Click to expand...
Click to collapse
No, your internal storage Is like trash cause the last rom you flashed has older security patch than oos10. Your device Is now encrypted and wont boot to system. I Guess you have to erase all via MSN tool or fastboot signed rom. Even if you wiped what mentioned above, your problem still be the data.
Fastboot method?
°Washy said:
No, your internal storage Is like trash cause the last rom you flashed has older security patch than oos10. Your device Is now encrypted and wont boot to system. I Guess you have to erase all via MSN tool or fastboot signed rom. Even if you wiped what mentioned above, your problem still be the data.
Click to expand...
Click to collapse
Thank you for replying. I'm relieved that you know of a couple methods to try.
Is using "Format Data" in TWRP an option for dealing with the encryption??
For the MSN tool, can I use this one? Tried looking around, but it's unclear. "[TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" https://forum.xda-developers.com/on...wnloadtool-v4-0-international-t3798892/page10
I would be more comfortable with using fastboot, but am I at any risk of having lost fastboot, or can I just turn off my device from TWRP right now and hold down the buttons to get there? Afraid to move out of TWRP right now, in case I can't get back. I do have twrp-3.3.1-18-enchilada-Q-mauronofrio.img that I can run from fastboot if needed.
By "signed rom," do you mean I can simply flash one of the zips here from fastboot? "[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates" https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Thanks again.
5xonlineage said:
Thank you for replying. I'm relieved that you know of a couple methods to try.
Is using "Format Data" in TWRP an option for dealing with the encryption??
For the MSN tool, can I use this one? Tried looking around, but it's unclear. "[TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" https://forum.xda-developers.com/on...wnloadtool-v4-0-international-t3798892/page10
I would be more comfortable with using fastboot, but am I at any risk of having lost fastboot, or can I just turn off my device from TWRP right now and hold down the buttons to get there? Afraid to move out of TWRP right now, in case I can't get back. I do have twrp-3.3.1-18-enchilada-Q-mauronofrio.img that I can run from fastboot if needed.
By "signed rom," do you mean I can simply flash one of the zips here from fastboot? "[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates" https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Thanks again.
Click to expand...
Click to collapse
I hardbricked my device about 10 times and i was able to recovery It even from a blank screen. Btw format data Will erase all your data but also the internal storage. About fastboot dont be afraid, go under twrp reboot section and reboot to bootloader. Then go under xda op6 guide section and search for mirrors for fastboot rom guide by Mauronofrio. He pushed my ass out the **** a lot of time.
P.s. Sorry but I dunno how to paste a link via xda app. Yes, ik! It's a vert newbie thing.
5xonlineage said:
Thank you for replying. I'm relieved that you know of a couple methods to try.
Is using "Format Data" in TWRP an option for dealing with the encryption??
For the MSN tool, can I use this one? Tried looking around, but it's unclear. "[TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" https://forum.xda-developers.com/on...wnloadtool-v4-0-international-t3798892/page10
I would be more comfortable with using fastboot, but am I at any risk of having lost fastboot, or can I just turn off my device from TWRP right now and hold down the buttons to get there? Afraid to move out of TWRP right now, in case I can't get back. I do have twrp-3.3.1-18-enchilada-Q-mauronofrio.img that I can run from fastboot if needed.
By "signed rom," do you mean I can simply flash one of the zips here from fastboot? "[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates" https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Thanks again.
Click to expand...
Click to collapse
Do you solve, man?
Fastboot ROM
°Washy said:
I hardbricked my device about 10 times and i was able to recovery It even from a blank screen. Btw format data Will erase all your data but also the internal storage. About fastboot dont be afraid, go under twrp reboot section and reboot to bootloader. Then go under xda op6 guide section and search for mirrors for fastboot rom guide by Mauronofrio. He pushed my ass out the **** a lot of time.
P.s. Sorry but I dunno how to paste a link via xda app. Yes, ik! It's a vert newbie thing.
Click to expand...
Click to collapse
That's awesome, I'm starting to grasp how much of a genius Mauronofrio is, after so many people referencing his work.
In his guide, he says, "These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie." This may be a dumb question, but how do I know which zip/OOS version to flash, when I don't have a functioning OS on my phone?
5xonlineage said:
That's awesome, I'm starting to grasp how much of a genius Mauronofrio is, after so many people referencing his work.
In his guide, he says, "These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie." This may be a dumb question, but how do I know which zip/OOS version to flash, when I don't have a functioning OS on my phone?
Click to expand...
Click to collapse
I talked with Mauronofrio in pm and he said me that you could solve your issue simply flash the ROM you want and format data after flash that one. Remember that your internal will be wiped but it would happen in any scenario we talked.
Magisk, boot img?
°Washy said:
I talked with Mauronofrio in pm and he said me that you could solve your issue simply flash the ROM you want and format data after flash that one. Remember that your internal will be wiped but it would happen in any scenario we talked.
Click to expand...
Click to collapse
That worked! And starstruck that you were able to check that with him. I flashed Mauronofrio's fastboot ROM for 10.3.2 and it rebooted (WOW). I clicked through the Google setup pages and checked that my data and wifi worked.
I then went back into fastboot, booted M's twrp img, fomatted data, and then installed twrp-3.3.1-x_blu_spark_v9.109_op6.zip, rebooted into recovery.
Then I think I made a mistake, because I installed Magisk-v20.4.zip. It succeeded, but now I can't boot into system anymore. Is it too late to flash the 10.3.2 boot.img?
5xonlineage said:
That worked! And starstruck that you were able to check that with him. I flashed Mauronofrio's fastboot ROM for 10.3.2 and it rebooted (WOW). I clicked through the Google setup pages and checked that my data and wifi worked.
I then went back into fastboot, booted M's twrp img, fomatted data, and then installed twrp-3.3.1-x_blu_spark_v9.109_op6.zip, rebooted into recovery.
Then I think I made a mistake, because I installed Magisk-v20.4.zip. It succeeded, but now I can't boot into system anymore. Is it too late to flash the 10.3.2 boot.img?
Click to expand...
Click to collapse
No. Just flash stock boot image if magisk broke something.
Rooted
°Washy said:
No. Just flash stock boot image if magisk broke something.
Click to expand...
Click to collapse
I ended up following the guide to Magisk Root without TWRP for OnePlus 6 Oxygen OS https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853 since it was referenced by Mauronofrio's post for having issues getting his TWRP to work with latest Magisk.
Someone posted a patched boot.img for 10.3.2, so now I'm rooted without TWRP. Priorities. Now all I need is for special characters and emojis to work Will keep an eye on other threads.
I'm learning a lot, thanks so much for all your help. You pointed me in the right direction when I was not sure what the hell to do!
5xonlineage said:
I ended up following the guide to Magisk Root without TWRP for OnePlus 6 Oxygen OS https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853 since it was referenced by Mauronofrio's post for having issues getting his TWRP to work with latest Magisk.
Someone posted a patched boot.img for 10.3.2, so now I'm rooted without TWRP. Priorities. Now all I need is for special characters and emojis to work Will keep an eye on other threads.
I'm learning a lot, thanks so much for all your help. You pointed me in the right direction when I was not sure what the hell to do!
Click to expand...
Click to collapse
I followed that thread for the first A10 release cause there wasn't a worked twrp yet. You are welcome man, when I feel myself usefull I always try to help.
"System update installation failed" while trying to install Q dp3, what did I miss?
I am currently on oxygenOS 9.0.8, both slots completely stock. I have unlocked the bootloader and enabled USB debugging.
I am trying to install Q dp3, but everytime I select Q dp3 zip file and press ok, update manager immediately says "System update installation failed" with no specific error code or any leads.
I have tried:
-Redownloading the Q dp3 file from here (https://oxygenos.oneplus.net/OnePlus6Oxygen_22_OTA_003_all_1907120020_wipe_ae2a3b38959345b1.zip)
-Rebooting and trying again
-Relock and unlock the bootloader
-factory reset within the settings
The strange thing is, I can normally install oxygenos 9.0.8 full update file. So I suspected problem of the dp3 file. But redownloading didn't solve the problem.
Is there something I have missed out? Some settings I have to do? Specific conditions?
Searching haven't helped me much(I searched everywhere, but I think nobody has my problem).
If someone can help me, I will be grateful. Thanks!
Since your bootloader is unlocked anyway, you can flash Android Q DP3 zip using TWRP. Flash it on both slots. Haven't tried blu_spark, but mauronofrio's TWRP works with Q. Don't forget to format data.
remewer said:
Since your bootloader is unlocked anyway, you can flash Android Q DP3 zip using TWRP. Flash it on both slots. Haven't tried blu_spark, but mauronofrio's TWRP works with Q. Don't forget to format data.
Click to expand...
Click to collapse
Thanks! Will try that!
Can I ask you one more question? What is the best and convenient way to go back to stock? I used nexus 4 and mi a1 before, and both devices just had to use
fastboot roms to go back to complete stock. Is it same with OP6? Or do I have to use MSM tool or other things?
ddaggebi said:
Thanks! Will try that!
Can I ask you one more question? What is the best and convenient way to go back to stock? I used nexus 4 and mi a1 before, and both devices just had to use
fastboot roms to go back to complete stock. Is it same with OP6? Or do I have to use MSM tool or other things?
Click to expand...
Click to collapse
I think it's down to your preference. I prefer the fastboot ROMs simply because I haven't tried MSM download tool yet. But yeah, both fastboot ROMs and MSM download tool are available for OP6.
remewer said:
I think it's down to your preference. I prefer the fastboot ROMs simply because I haven't tried MSM download tool yet. But yeah, both fastboot ROMs and MSM download tool are available for OP6.
Click to expand...
Click to collapse
Thanks you! Now I can flash away~
remewer said:
I think it's down to your preference. I prefer the fastboot ROMs simply because I haven't tried MSM download tool yet. But yeah, both fastboot ROMs and MSM download tool are available for OP6.
Click to expand...
Click to collapse
I successfully flashed Q dp3 thanks to you.
However, I can't boot TWRP with fastboot boot twrp.img method. Before updating to Q, it worked. Now, cmd line shows FAILED (remote: 'unknown command').
I have tested with newer versions of Fastboot, but the results were the same. Anybody knows how to solve this problem?
ddaggebi said:
I successfully flashed Q dp3 thanks to you.
However, I can't boot TWRP with fastboot boot twrp.img method. Before updating to Q, it worked. Now, cmd line shows FAILED (remote: 'unknown command').
I have tested with newer versions of Fastboot, but the results were the same. Anybody knows how to solve this problem?
Click to expand...
Click to collapse
Yep, it's a known issue with DP3 (or possibly earlier builds). Anyway, every time you flash a ROM, may it be stock or custom, you should always flash TWRP next. For now, you could try downgrading to Pie using fastboot ROMs.
remewer said:
Yep, it's a known issue with DP3 (or possibly earlier builds). Anyway, every time you flash a ROM, may it be stock or custom, you should always flash TWRP next. For now, you could try downgrading to Pie using fastboot ROMs.
Click to expand...
Click to collapse
Thank you so much. I don't know what I could've done without you. I'll try to downgrading. Still not accoustomed to how roms work in OP6. Guess I'll study more.
Again, thank you for kindly answering my noobish questions! It means a lot to me
ddaggebi said:
Thank you so much. I don't know what I could've done without you. I'll try to downgrading. Still not accoustomed to how roms work in OP6. Guess I'll study more.
Again, thank you for kindly answering my noobish questions! It means a lot to me
Click to expand...
Click to collapse
No problem. Read more about A/B partitions. It's actually just as easy to mod our phone once you know how A/B partitions work.
Greetings to anyone that may see this - I am new to the android root thingy, so I apologize in advance if I have a stupid question. I have only rooted an old tablet with Kingoroot which used SuperSU as the root manager. First off, I want to address TWRP. What is the difference between the OP7Pro "guacamole" and "guacamoleb" (the "b" is very important and intentional.) I tried the regular guacamole image, but the phone didn't seem to want to boot the image. I am going to try guacamoleb. If I flash TWRP, can I boot my device normally? Some sources say yes some no. Thanks for all your help in advance!
UrAverageNerd said:
First off, I want to address TWRP. What is the difference between the OP7Pro "guacamole" and "guacamoleb" (the "b" is very important and intentional.)
Click to expand...
Click to collapse
Haven't seen guacomoleb (different code name to me implies a different device, but I'm not sure in this case). Just use the file from the dev's TWRP thread: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Unofficial version -75 is the current version. Use the version ( Q versus Pie) for your current Android/OOS version. Might be obvious, but some folks have asked about that.
UrAverageNerd said:
If I flash TWRP, can I boot my device normally? Some sources say yes some no. Thanks for all your help in advance!
Click to expand...
Click to collapse
Per the developer in his thread I linked above, for a stock device, if you flash TWRP, you should root (with Magisk) or the phone might not boot. Some folks have reported that they can flash TWRP and not Magisk and still boot. But there is not point in risking it, since your intent is to root anyway. Fastboot boot TWRP img, then flash TWRP installer zip, and just flash Magisk right away at the same time, then reboot. It's pretty easy.
Also note that installing TWRP is somewhat optional. You can just fastboot boot TWRP img, then flash Magisk to root. It is a matter of preference whether to have TWRP installed or not, and folks are pretty split on this. My opinion, TWRP installed (while not required) does give some potentially useful features if things ever go wrong. I personally don't see much advantage to not installing TWRP, but just my opinion.
Hi there. I ran into similar problems when I was a Root noobie (which I still am). Try the All In One Tool that can be found in this forum. That will help you flash TWRP. It got me there when I was struggling to Flash TWRP.
redpoint73 said:
Haven't seen guacomoleb (different code name to me implies a different device, but I'm not sure in this case). Just use the file from the dev's TWRP thread: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Unofficial version -75 is the current version. Use the version ( Q versus Pie) for your current Android/OOS version. Might be obvious, but some folks have asked about that.
Per the developer in his thread I linked above, for a stock device, if you flash TWRP, you should root (with Magisk) or the phone might not boot. Some folks have reported that they can flash TWRP and not Magisk and still boot. But there is not point in risking it, since your intent is to root anyway. Fastboot boot TWRP img, then flash TWRP installer zip, and just flash Magisk right away at the same time, then reboot. It's pretty easy.
Also note that installing TWRP is somewhat optional. You can just fastboot boot TWRP img, then flash Magisk to root. It is a matter of preference whether to have TWRP installed or not, and folks are pretty split on this. My opinion, TWRP installed (while not required) does give some potentially useful features if things ever go wrong. I personally don't see much advantage to not installing TWRP, but just my opinion.
Click to expand...
Click to collapse
Thanks for your help. Apparently the Android Q unofficial build -75 doesn't have any mirrors. It's still searching. I like using TWRP because it's convenient if I wan't to flash something else without a PC or Mac.:laugh:
UrAverageNerd said:
Apparently the Android Q unofficial build -75 doesn't have any mirrors. It's still searching.
Click to expand...
Click to collapse
Something wrong with the "main" download link (androidfilehost)?
UrAverageNerd said:
Greetings to anyone that may see this - I am new to the android root thingy, so I apologize in advance if I have a stupid question. I have only rooted an old tablet with Kingoroot which used SuperSU as the root manager. First off, I want to address TWRP. What is the difference between the OP7Pro "guacamole" and "guacamoleb" (the "b" is very important and intentional.) I tried the regular guacamole image, but the phone didn't seem to want to boot the image. I am going to try guacamoleb. If I flash TWRP, can I boot my device normally? Some sources say yes some no. Thanks for all your help in advance!
Click to expand...
Click to collapse
Use adb & fastboot via powershell
Get the adb files in a folder
Copy the twrp.img to the adb folder and on phone /storage/emulated/0/
Get a copy of the twrp installer on your phone anywhere works
Open adb folder
Hold shift and right click a empty space
Open powershell & type
Adb boot bootloader
Fastboot boot twrp.img (you can drag and drop the file into powershell if your lazy like me)
Flash the twrp installer on your phone
Done?
Reboot and go back into recovery to see if it works
Tip for updates:
After you get the update
Flash via twrp
Then flash twrp (so you don't need your computer)
Flash magisk if you want superuser
Reboot
Reboot recovery
Flash magisk again (seems it takes two flashes)
None of the tools work for my devices anymore just powershell
All in one doesn't read my fastboot
Cmd has a remote error after attempting to boot it.
UrAverageNerd said:
First off, I want to address TWRP. What is the difference between the OP7Pro "guacamole" and "guacamoleb" (the "b" is very important and intentional.)
Click to expand...
Click to collapse
Just noticed that the TWRP "guacomoleb" is the "unified" version that works with both the OnePlus 7 and the 7 Pro. Shouldn't make a difference whether you use the "unified" version or the 7 Pro specific TWRP.
Just a reminder for people who only read the oneplus 9 forum and not oneplus 9 pro one:
[RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
I tested it and flashed it on my oneplus 9 LE2110 and it works.
Again, as i always have to write to people.
Be careful, only do something you can undo.
Before you "Flash Current TWRP" do a full BACKUP!
Does said recovery perform full back-ups of partitions and restore features ?
Edit
I booted it up . Decrypts perfectly. Backed up modem just to see for myself. Rebooted back onto system . Booted twrp again and it found saved partition to restore. This makes life so much easier. Time to go get a full system backup !! Cool
Exactly. I'm super happy. Now the OnePlus 9 Is finally a good phone. Without TWRP it's just risky.
Im sure some bugs are still there but it looks very promising.
noname122414 said:
Exactly. I'm super happy. Now the OnePlus 9 Is finally a good phone. Without TWRP it's just risky.
Im sure some bugs are still there but it looks very promising.
Click to expand...
Click to collapse
And this is huge for many people roaming around here on carrier variants . Now super easy to restore modems to make switch to global.or eu or whatever.
Hi there, I have a question:
When you have a new device, would the following work:
1. Unlock bootloader
In fastboot mode:
2.
Code:
fastboot boot c:\twrp.img
In TWRP
3. Install TWRP
4. Install Magisk
5. Reboot - then you have Root, TWRP?
6. Upgrades can than be done in TWRP by installing the files and than intalling again TWRP and afterwards Magisk?
Best
Axel
It appears you are asking. If I am incorrect, my apologies. With the 6t (also a a/b OP device)
The process I always used was
1) reboot to bootloader
2) boot twrp.img
3) install twro zip
4) reboot recovery
5) upon TWRP reboot, install magisk
6) profit.
Anytime I tried to go ahead and install Magisk in the same round as installing TWRP, it would install to the opposite slot making me have to do the whole process over again. Ymmv
XDA is Great, and, yet, at the same time: XDA is very challenging.
With so many able to contribute, and the lack of external editing capacity ( unlike SO ),
it's difficult to distill the information.
Okay, Great! There's a TWRP for the OnePlus 9 !
I used TWRP 3.5 and Magisk to root a Lenovo Tab M10, without any need for external input.
The Answer I'm looking for here is: Am I able to install / root / whatever my T-Mo OP 9 with TWRP ?
Does anyone have any definitive solutions ?
Thank You, in Advance, for any assistance !
barguybrady said:
XDA is Great, and, yet, at the same time: XDA is very challenging.
With so many able to contribute, and the lack of external editing capacity ( unlike SO ),
it's difficult to distill the information.
Okay, Great! There's a TWRP for the OnePlus 9 !
I used TWRP 3.5 and Magisk to root a Lenovo Tab M10, without any need for external input.
The Answer I'm looking for here is: Am I able to install / root / whatever my T-Mo OP 9 with TWRP ?
Does anyone have any definitive solutions ?
Thank You, in Advance, for any assistance !
Click to expand...
Click to collapse
Is your bootloader unlocked? If yes then you could boot to fastboot and fastboot boot twrp.img. You will have your answer then.
MrSteelX said:
Is your bootloader unlocked? If yes then you could boot to fastboot and fastboot boot twrp.img. You will have your answer then.
Click to expand...
Click to collapse
Sadly, No, boot-loader is locked. Never encountered this on both previous OP 6t's.
Hence my confusion. When I walked out of the t-Mo store with my 6t, I had No issues.
I used the wonderful mauronofios tool, to do it All with no troubles.
crash my 6t, forced to take a "9 5g" from t-Mo, and now I am regretting it.
Wondering what has changed, and by whom..? t-Mo change policies, or OnePlus ?
Actually, I've been a t-Mo customer for 16 Years ! First time I've ever had to "Ask Permission" to have my phone, or my SIM unlocked...
barguybrady said:
Sadly, No, boot-loader is locked. Never encountered this on both previous OP 6t's.
Hence my confusion. When I walked out of the t-Mo store with my 6t, I had No issues.
I used the wonderful mauronofios tool, to do it All with no troubles.
crash my 6t, forced to take a "9 5g" from t-Mo, and now I am regretting it.
Wondering what has changed, and by whom..? t-Mo change policies, or OnePlus ?
Actually, I've been a t-Mo customer for 16 Years ! First time I've ever had to "Ask Permission" to have my phone, or my SIM unlocked...
Click to expand...
Click to collapse
You should start a separate thread for all that. Kinda want to keep on topic to make it less confusing for everyone
Has anyone been able to mount a usb drive? ive tried everything and it just looks to not be functional.
strangely enough, i heard TWRP backups are iffy right now but have already restored from one using this release in the past week. happy that works
mattie_49 said:
And this is huge for many people roaming around here on carrier variants . Now super easy to restore modems to make switch to global.or eu or whatever.
Click to expand...
Click to collapse
Just installed it - thanks OP.
Does anyone know if I can jdirtyflash the global rom 11.2.7.7 over the EU rom which is currently on 11.2.7.7 in twrp?
I was originally on global (le2110) but flashed EU via update. Now I want to go back to global.
applyscience said:
Has anyone been able to mount a usb drive? ive tried everything and it just looks to not be functional.
strangely enough, i heard TWRP backups are iffy right now but have already restored from one using this release in the past week. happy that works
Click to expand...
Click to collapse
Full system everything. User data. ? Did it work
mattie_49 said:
Full system everything. User data. ? Did it work
Click to expand...
Click to collapse
i dont know i have been bricked for 5 days ever since i attempted the lineage release
applyscience said:
i dont know i have been bricked for 5 days ever since i attempted the lineage release
Click to expand...
Click to collapse
Just lineage no kernel no special cam?
mattie_49 said:
Just lineage no kernel no special cam?
Click to expand...
Click to collapse
nah. just lineage. pretty sure i deal with support again tomorrow. fun...
Need help...
I typed Fastboot boot twrp.img instead of fastboot flash boot twrp.img
And that was to boot_a
So then i tried fastboot flash boot_b twrp.img
It wont load the recovery now. Phone wont boot up unless i
fastboot boot patched11.2.7.7DA.img
I even try to install Magisk directly and it fails.
Can I get some help. Dont even wanna restart my phone.
Thank you
All Good Now..... I Figured It Out!
How to fix this
id avoid TWRP if on 11.2.8.8 already. it can boot from fastboot and even install itself as your recovery but it will not mount data. i tried the refresh sizes trick in backup and then the default_password for password to decrypt and nothing. pretty sure twrp mishaps are what bricked my phone last too . thankfully it still boots, just the recovry section is effected
ill try and flash the OTA zip tomorrow. sick of messing with it for now lol
Are we still avoiding twrp
Hey,
I screwed up when patching the boot image for magisk on the latest stock rom update. I've attempted to reinstall the factory image but experience two different errors depending on which version of platform tools im using:
When I use 33.0.3 i get this error: fastboot: error: device requires partition vendor kernel boot which is not known to this version of fastboot
When i use 34.0.1 i get this error: Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)
I'm at a loss on how to correct the problem at this point. I've tried Pixelflasher but that fails also (I'm assuming from the same errors).
Any help is greatly appreciated as I'm without a phone until I fix this
Thanks in advance!!!!!
stslimited84 said:
Hey,
I screwed up when patching the boot image for magisk on the latest stock rom update. I've attempted to reinstall the factory image but experience two different errors depending on which version of platform tools im using:
When I use 33.0.3 i get this error: fastboot: error: device requires partition vendor kernel boot which is not known to this version of fastboot
When i use 34.0.1 i get this error: Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)
I'm at a loss on how to correct the problem at this point. I've tried Pixelflash but that fails also (I'm assuming from the same errors).
Any help is greatly appreciated as I'm without a phone until I fix this
Thanks in advance!!!!!
Click to expand...
Click to collapse
I would suggest using PixelFlasher (from this sub-forum) with 33.0.3, you should be able to revive your phone.
stslimited84 said:
Hey,
I screwed up when patching the boot image for magisk on the latest stock rom update. I've attempted to reinstall the factory image but experience two different errors depending on which version of platform tools im using:
When I use 33.0.3 i get this error: fastboot: error: device requires partition vendor kernel boot which is not known to this version of fastboot
When i use 34.0.1 i get this error: Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)
I'm at a loss on how to correct the problem at this point. I've tried Pixelflash but that fails also (I'm assuming from the same errors).
Any help is greatly appreciated as I'm without a phone until I fix this
Thanks in advance!!!!!
Click to expand...
Click to collapse
I would go with Pixel Flasher. pretty simple program with a lot of options. Patching Magisk and a few clicks to install firmware.
Fishawy said:
I would suggest using PixelFlasher (from this sub-forum) with 33.0.3, you should be able to revive your phone.
Click to expand...
Click to collapse
Thanks for the response.
As i mentioned in the OP, I tried pixelflasher and it does not work. I believe its experiencing the same issues since its just UI executing the commands essentially.
schmeggy929 said:
I would go with Pixel Flasher. pretty simple program with a lot of options. Patching Magisk and a few clicks to install firmware.
Click to expand...
Click to collapse
I tried pixel flasher with no success
stslimited84 said:
I tried pixel flasher with no success
Click to expand...
Click to collapse
Where are you getting your platform tools? Please tell me it's not a minimal adb thing and/or not from the android developers site...?
simplepinoi177 said:
Where are you getting your platform tools? Please tell me it's not a minimal adb thing and/or not from the android developers site...?
Click to expand...
Click to collapse
using the standard kit from https://developer.android.com/tools/releases/platform-tools
stslimited84 said:
using the standard kit from https://developer.android.com/tools/releases/platform-tools
Click to expand...
Click to collapse
weirdly enough, I've seen "sparse" or "partition" errors happen to members who ended up getting it working by changing the USB cord!
I might re-download platform tools (r33.0.3 of course), place it in a different location, and try there again. And/or re-download the factory firmware image but make sure to compare the checksums and make sure you're not trying to flash corrupted images...
*don't forget to remove the "-w" or your device will be wiped...
stslimited84 said:
Hey,
I screwed up when patching the boot image for magisk on the latest stock rom update. I've attempted to reinstall the factory image but experience two different errors depending on which version of platform tools im using:
When I use 33.0.3 i get this error: fastboot: error: device requires partition vendor kernel boot which is not known to this version of fastboot
When i use 34.0.1 i get this error: Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)
I'm at a loss on how to correct the problem at this point. I've tried Pixelflasher but that fails also (I'm assuming from the same errors).
Any help is greatly appreciated as I'm without a phone until I fix this
Thanks in advance!!!!!
Click to expand...
Click to collapse
Go over to the Pixel Flasher thread and submit a support.zip. Maybe badabing can help diagnose.
simplepinoi177 said:
weirdly enough, I've seen "sparse" or "partition" errors happen to members who ended up getting it working by changing the USB cord!
I might re-download platform tools (r33.0.3 of course), place it in a different location, and try there again. And/or re-download the factory firmware image but make sure to compare the checksums and make sure you're not trying to flash corrupted images...
*don't forget to remove the "-w" or your device will be wiped...
Click to expand...
Click to collapse
I've downloaded both several times but ill try a new location. At this point, I dont care if the device is wiped, I just need it working. i can restore the apps from backups.
I was able to fix it by using the android flash tool in chrome. It was the only thing that would overcome the errors. Phone is up and running again.
stslimited84 said:
I was able to fix it by using the android flash tool in chrome. It was the only thing that would overcome the errors. Phone is up and running again.
Click to expand...
Click to collapse
Glad you got it sorted.
stslimited84 said:
I was able to fix it by using the android flash tool in chrome. It was the only thing that would overcome the errors. Phone is up and running again.
Click to expand...
Click to collapse
that's always a good option to think on...I was gonna suggest it after checking on USB cord issues...glad you got it fixed...
Glad for your!
Is it the tool at https://flash.android.com/ ?
Did you patch boot.img and flash that?
As init_boot.img needs to be patched in Magisk and installed, for Pixel 7 series.
krakout said:
Glad for your!
Is it the tool at https://flash.android.com/ ?
Click to expand...
Click to collapse
Yep. I tried using the beta build first without success. Then I used the latest public build and it worked
I had something similar happen when flashing the latest QPR beta last week. I fixed it by sideloading the ota.zip instead, then booting to bootloader to flash the patched image after.