Hi All,
Currently im on DU, the latest updated non-trebble rom that got google update in august(?) published bij nfound.
I dont have fastboot (bootstack?) and no adb in recovery. (Nfounds TWRP)
it seems that there is no non-trebble rom (oreo or pie) being maintained right now regarding google security patches. Right?
OK for this i have to switch to trebble based images.
How to get back fastboot and TWRP with adb? I hate going to trebble without being able to fallback to adb in TWRP or fastboot in case some things dont work out during this process.
Whats the way to go?
I appreciate a guide!
thanx
You could try the Axon 7 tool kit.
It will do most things, that should help.
Read carefully any instructions regarding treble etc, in some instances you need a vendor partition.
I'm still reading all the different options.
Syberclone said:
You could try the Axon 7 tool kit.
It will do most things, that should help.
Read carefully any instructions regarding treble etc, in some instances you need a vendor partition.
I'm still reading all the different options.
Click to expand...
Click to collapse
I should have mentioned i dont have a windowscomputer.
edit: never mind i flashed oki's TWRP and I therefore have all the tools needed in TWRP!
I am asking myself what these 2 options in TWRP are for,and when they should be executed?
The first option disables/enables dm-verity for the system partition, the 2nd option disables/enable EMMC write protection for the system partition. That's my understanding of it. You are using @Oki's TWRP, correct?
AnonVendetta said:
The first option disables/enables dm-verity for the system partition, the 2nd option disables/enable EMMC write protection for the system partition. That's my understanding of it. You are using @Oki's TWRP, correct?
Click to expand...
Click to collapse
Yes,correct,But i dont understand when we should execute these commands.
I followed oki s guide for flashing los15 with his EDL kit,and he mentioned these steps in his guide...but previous i never used these command
Don't use @Oki's guide, it is better to do everything by hand and get a learning experience/understanding of everything that is going on. Like for instance, view everything as a separate step unto itself (unlocking bootloader, flashing TWRP, flashing a ROM/modem, etc.). I tried both of his EDL packages and had various issues (ROM sometimes not booting, etc). You can still use his TWRP and vendor Party tool, just avoid his EDLs. I had posted in his thread once for help but never got an answer, so I moved on and started from scratch with a clean EDL flash.
Short answer: you can run them whenever you want
AnonVendetta said:
Don't use @Oki's guide, it is better to do everything by hand and get a learning experience/understanding of everything that is going on. Like for instance, view everything as a separate step unto itself (unlocking bootloader, flashing TWRP, flashing a ROM/modem, etc.). I tried both of his EDL packages and had various issues (ROM sometimes not booting, etc). You can still use his TWRP and vendor Party tool, just avoid his EDLs. I had posted in his thread once for help but never got an answer, so I moved on and started from scratch with a clean EDL flash.
Short answer: you can run them whenever you want
Click to expand...
Click to collapse
i always did.
I like to know what it does,not when i can run them whenever i want.
Because whent i have excetue this,my system partition is suddenly smaller,but my battery holds longer %
@Predatorhaze: I tried to explain to the best of my understanding. You are free to flash anything on your phone that you want. @Oki is a good dev and s/he tries to be helpful, but my experience with his/her ROM EDL zips hasn't been good, which is why I recommended to avoid them. The issues you mention seem quite weird, they should not be happening, are you certain?
I can only suggest that you post in the relevant thread for help.
i have just found (twrp-installer-3.3.0-2-tissot.zip) file on TWRP's official website i just want to know is it same recovery installer as CosmicDan's ( TWRP-Installer-3.2.1-with-Tissot-Manager-2.5) recovery installer or is it something else and what if i flash it with TWRP
can any one tried this recovery installer. i want to try it but i don't have a PC now so i'm afraid of losing my already installed recovery
reply if anyone tried it.
You can always fastboot into CosmicDan's boot-recovery.img image from TWRP-fastboot_boot_only-3.2.1-with-Tissot-Manager-2.5.zip. It does not alter anything. From there you can install twrp-installer-3.3.0-2-tissot.zip to try. If you do not like it flash back TWRP-Installer-3.2.1-with-Tissot-Manager-2.5.zip from same fastboot-ed boot-recovery.img.
The differences between official and CosmicDan's are that official is newer and CosmicDan's has tissot manager to repartition for Treble. But that usually only needs to be done once.
Myself I have fastbooted boot-recovery.img image from TWRP-fastboot_boot_only-3.2.1-with-Tissot-Manager-2.5.zip some time because I was not comfortable with flashing TWRP-Installer-3.2.1-with-Tissot-Manager-2.5.zip in all sorts of Pie Treble experiments.
But once I knew twrp-installer-3.3.0-2-tissot.zip was Treble aware, I flashed it and it does what it needs to do (for me).
thanks bro but after posting this thread i flashed it in cosmicdan's twrp and got latest 3.3.0.2 version of twrp because its my habbit to do testing and experimental things with my phone and i can't wait for someone to test and post result so i did it.
actually i had a little bit doubt before flashing it and i have some important data on my phone so i just want to be sure coz i don't want to loose my data
you won't believe how much times i bricked my phones and bring back them to working
Hello!
Just unlocked my mi 9t and installed magisk. So far it's working great but I really want to try a custom rom because I don't really like miui.
Now I came from a oneplus 3t that has simple zip files to install roms. Now I see for this device you have gsi roms. My question is do I need to flash vbmeta and how would I go about doing that? Is it device specific? Or is the one in the xda tutorial universal?
Thanks!
They are different.
GSI are for all (or most) of devices (treble-enabled).
Zipped ROMs are device specific.
We still don't have "normal" roms because developers haven't get this phone. So, for now, we have to use GSI.
Some people think vbmeta is specific, but actually, at least for GSI roms, it's universal.
You can flash it using fastboot mode and CMD/Terminal or if TWRP allow it, flash from there.
I tried rooting my OP6T on Android 10, and was up half the night. Recovered from a hard brick twice, using the Qualcomm serial flash tool thing. I was trying to flash Majisk, and read that it had to be done via a custom recovery like TWRP. All the guides said that it to boot TWRP, then basically flash TWRP using itself so that it says. Fastboot kept saying "Remote Unknown Command" when using "fastboot boot" like all the guides said. Then someone told me to run "fastboot flash boot twrp.img". This caused the first hard brick. I guess because I wrote the recovery over the boot partition. I then found a post somewhere where someone said that Oneplus Devs removed the boot command from Fastboot for some reason. No idea why!! But no one else in the OP6T TWRP thread reported issues. Maybe they were all installing TWRP on an Android 9.x build that diden't have this issue? Eventually after recovering and flashing several layers on OTA updates through the local upgrade option, I was back on A10 OB2. But I still wanted root and hadn't got TWRP working yet. Then I found a random post buried in a random thread somewhere saying that custom recoveries on A10 are useless at this point period because TWRP can't flash the system partition, as it's read only. Not sure if this only applies to OP devices?
I am now back to where I started. I would still like twrp for backups, but since it's not cooperating, I try the alternative option for Masisk, involving the patched boot.img file. I download the patched the patched boot file in this thread. Flashed it with "fastboot flash boot boot.img", and got my 2nd hard brick. It would get stuck at the bootloader warning screen and no fastboot.
Now i've lost my data, 6+ hour of time, and no closer than I was before.
I am going to take a break now, cause I need an operational phone this week. Word of advice: If you're not a developer that knows exactly what they are doing, don't even attempt to get root on an Android 10 build!
You can install Magisk,manager,extract the boot img from the OOS zip file using payload_dumper,copy that boot img. to your phone,patch the image with magisk,copy to your PC then fastboot the patched image to your phone .And yes,you cannot have twrp yet.
I'm on the open beta 2 of Android 10 and I have root and TWRP. It's possible.
It's not that hard, you don't even need twrp to install magisk. in android 10.
download open beta 2 Android 10. Extract payload.bin from it. Use payload_dumper to extract boot
install magisk apk, and patch boot.
go to fastboot use the
"Fastboot flash boot_a patched_boot.img "
and you are done.
Sh4d0wk1ng said:
It's not that hard, you don't even need twrp to install magisk. in android 10.
download open beta 2 Android 10. Extract payload.bin from it. Use payload_dumper to extract boot
install magisk apk, and patch boot.
go to fastboot use the
"Fastboot flash boot_a patched_boot.img "
and you are done.
Click to expand...
Click to collapse
I think I see what I did! I need to use "fastboot flash boot_a" (or b), and not just "fastboot flash boot". Not sure how you know whether to use a or b without a custom recovery though? Because AFAIK, the fastboot command for that is broken.
Not sure what payload dumper is, but I should be able to use the the same patched boot image that everyone else used since it's for that same ROM, now that I known exactly where to flash it to (besides A or B).
When I flashed to "boot" before, I must have overwritten some kind of low-level pre-bootloader, lol.
Thank you
Bhamilton0347 said:
I'm on the open beta 2 of Android 10 and I have root and TWRP. It's possible.
Click to expand...
Click to collapse
How did you achieve this? Do you have to start with A9 with TWRP, and then somehow upgrade to A10 without overwriting it with stock recovery?
I found this guide, but step 2 does not make sense to me. How could you flash TWRP inside of the Masisk Manager app?
I imagine you still can't flash system with TWRP, but everything else works?
Thank you
roman gabriel said:
You can install Magisk,manager,extract the boot img from the OOS zip file using payload_dumper,copy that boot img. to your phone,patch the image with magisk,copy to your PC then fastboot the patched image to your phone .And yes,you cannot have twrp yet.
Click to expand...
Click to collapse
I think the issue was that I flashed to the wrong place. See above. Thank you.
I'm feeling extremely lazy rn and I don't feel like explaining all of the trouble I went through to get it working, but you should be able to just fastboot flash these images to their respective partitions and you should have both TWRP and Magisk. It's got Magisk 20.1, the modified one so that EdXposed will work. But they're functionally the same.
https://drive.google.com/file/d/149TqVLqKr7Rc8xygMDoUyY_SLoATQrRq/view?usp=drivesdk
Let me know if it works.
Note: this is the boot.img for the second open beta of Android 10 for the OnePlus 6T. This may also work on the stable and first beta release as well as even on the 6, but I do not know. Also, your SIM card may not be showing up, but this problem disappeared for me a minute or two after boot.
Bhamilton0347 said:
I'm feeling extremely lazy rn and I don't feel like explaining all of the trouble I went through to get it working, but you should be able to just fastboot flash these images to their respective partitions and you should have both TWRP and Magisk. It's got Magisk 20.1, the modified one so that EdXposed will work. But they're functionally the same.
https://drive.google.com/file/d/149TqVLqKr7Rc8xygMDoUyY_SLoATQrRq/view?usp=drivesdk
Let me know if it works.
Note: this is the boot.img for the second open beta of Android 10 for the OnePlus 6T. This may also work on the stable and first beta release as well as even on the 6, but I do not know. Also, your SIM card may not be showing up, but this problem disappeared for me a minute or two after boot.
Click to expand...
Click to collapse
Thank you. I can't risk it right now. But i'll try sometime. Anyone wanna be the guinea pig?
If it works well, it should be very useful to the community.
I am brand new to Majisk by the way. It's been a couple years since I was rooted.
flyoffacliff said:
Thank you. I can't risk it right now. But i'll try sometime. Anyone wanna be the guinea pig?
If it works well, it should be very useful to the community.
I am brand new to Majisk by the way. It's been a couple years since I was rooted.
Click to expand...
Click to collapse
It's 100% safe and I can guarantee it'll boot as long as you're on an international OP6T on the Android 10 open beta 2. I reuploaded and included the stock boot.img as well so just in case you do have any problems, you can just fastboot flash it and you'll be able to boot right up (no hard brick or anything)
Bhamilton0347 said:
It's 100% safe and I can guarantee it'll boot as long as you're on an international OP6T on the Android 10 open beta 2. I reuploaded and included the stock boot.img as well so just in case you do have any problems, you can just fastboot flash it and you'll be able to boot right up (no hard brick or anything)
Click to expand...
Click to collapse
Great. Thank you. I might wait for the next stable build though. It just came out on H2OS, so shouldn't be too long now.
Man it just worked smooth for me. I was already on OB2 and I followed this below link. Half way down, I realised it was for OP6 and not 6T. However I had proper twrp and I just followed the procedure.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213
EDIT: I faced problems with wifi connectivity. So I had rebooted to TWRP and reflashed OB2, TWRP and Magisk again to get it working. An issue with
"fastboot flash boot" command I guess.
flyoffacliff said:
I think I see what I did! I need to use "fastboot flash boot_a" (or b), and not just "fastboot flash boot". Not sure how you know whether to use a or b without a custom recovery though? Because AFAIK, the fastboot command for that is broken.
Not sure what payload dumper is, but I should be able to use the the same patched boot image that everyone else used since it's for that same ROM, now that I known exactly where to flash it to (besides A or B).
When I flashed to "boot" before, I must have overwritten some kind of low-level pre-bootloader, lol.
Thank you
I wasn't sure either but I know that the boot on the oneplus 6t android 10 it has two partitions. I just flashed it on boot_a and it works. I could attempt to install twrp on the other partition but I don't really needed it. good luck and let us know how it went.
Click to expand...
Click to collapse
I had a bit more luck with the adventure this time! Successfully flashed TWRP and Magisk, but then Emojis were completely broken at the OS level. Apparently this is caused by a partition issue, but not sure how this happened. I tried a script to fix it that someone posted and it did not work. So I took this as an opportunity to flash the latest ROM to fix it.
I went into TWRP, ran the full update ZIP, then the TWRP installer, then the Magisk installer (all without rebooting). Apparently it does not switch slots automatically when you run it from recovery instead of the "local update" option? TWRP was fine after the update, but Masisk was not, despite me flashing the ZIP. No idea why! But I switched back to the other slot that was still rooted, used Magisk Manager to flash it to inactive slot, and switched slot back to one with new OS. Success! Funny how different methods work/fail with different people. Thanks for the help everyone. I just noticed 10.3.1 is no longer posted on the OnePlus website download page, hope it didn't get pulled again!
EDIT: Does each slot just have its own system and cache partition? Everything else is like data and modem is combined, right?
https://forum.xda-developers.com/oneplus-6t/how-to/root-oneplus-6t-loosing-data-android-10-t4041865
follow this guide.. work 100%. Tested.