Database Develop

Oneplus 3 decryption Ultimate guide

Ok guys, this is a sureshot guide for
PROBLEM
* anyone wanting to decrypt their op3 but stuck at 1+ boot screen(Or not able to boot any custom ROMs.) and only able to restore twrp backups
* After using fastboot format userdata twrp and about phone shows only 32gb phone memory(where the hell is my rest of 32gb )
* Fastboot format userdata resulting in Stuck at boot screen or simply an unbrick trick to return to Stock OOS in unencrypted stage
SOLUTION
1. Use method 2 of Mega unbrick guide to restore your phone to stock partitions found here
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
2. After the flashing is complete do not reboot the phone instead reboot directly into bootloader.
3. In fastboot mode flash modded twrp 3.0.2.22 using command ''fastboot flash recovery recovery.img'' found here
http://forum.xda-developers.com/devdb/project/?id=15934#downloads
4. Reboot directly into twrp and using mtp mode copy latest elemental x kernel or bluspark kernel zip for OOS and SYSTEM supersu.zip into the internal storage. System supersu.zip here OR directly proceed to step 8
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.78-201609011115.zip
5. Now flash system supersu.zip and directly after that kernel.zip
6. Now again reboot to recovery directly and from twrp boot into system.
7. After boot up you system should be decrypted. You can check in security settings.
8.Reboot recovery and flash required firmware + modem zip found here
http://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
9.wipe data +cache +dalvik +system
10. Flash any rom of your choice and go flashoholic, use multirom or whatever you want.
Pheww. Thanks.

Man, Finally the SystemRoot (V4A, MultiROM etc) as we discussed a couple of weeks back with this hassle at the Mega Unbrick and Decrypt guides threads...:highfive:
I saw your post on MultiROM but maybe it got moved I guess...
So are you able to cross flash anything now ?
thanks.

Ashtrix said:
Man, Finally the SystemRoot (V4A, MultiROM etc) as we discussed a couple of weeks back with this hassle at the Mega Unbrick and Decrypt guides threads...:highfive:
I saw your post on MultiROM but maybe it got moved I guess...
So are you able to cross flash anything now ?
thanks.
Click to expand...
Click to collapse
anything... even multirom works flawless.

I will give this a try, Or will try to Flash the EX then perform parts of this since they support Kexec, to see what works, I have data and lot of apps working them again is a real pita with my schedule...

Thanks but, this is basically what i have done to decrypt my op3, i just used the CypherOs ROM instead OxygenOs, fastboot format userdata, reboot to recovery, flash rom, flash elementalx, and i didnt flash Supersu(dont know if thats causing my problem, i dont think so), i also did fastboot format userdata without being stuck at boot logo and still no 32gb, dont know whats the problem

ach3fck said:
Thanks but, this is basically what i have done to decrypt my op3, i just used the CypherOs ROM instead OxygenOs, fastboot format userdata, reboot to recovery, flash rom, flash elementalx, and i didnt flash Supersu(dont know if thats causing my problem, i dont think so), i also did fastboot format userdata without being stuck at boot logo and still no 32gb, dont know whats the problem
Click to expand...
Click to collapse
its different fastboot format userdata causes this Dont know why. I suggest method in the OP. Read carefully and follow it.

nikhilsnigam said:
its different fastboot format userdata causes this Dont know why. I suggest method in the OP. Read carefully and follow it.
Click to expand...
Click to collapse
Aham, so the format userdata causes it, thanks for that. i want to ask you something, after restoring completely with Msmdownloadtool(method2) can i directly reboot to recovery then sideload CB 3.5.5 and then reboot to fastboot and continue with the tutorial? What im saying is my device is decrypted as long it doesnt boot, am i right?

ach3fck said:
Aham, so the format userdata causes it, thanks for that. i want to ask you something, after restoring completely with Msmdownloadtool(method2) can i directly reboot to recovery then sideload CB 3.5.5 and then reboot to fastboot and continue with the tutorial? What im saying is my device is decrypted as long it doesnt boot, am i right?
Click to expand...
Click to collapse
Yes you can but you will be encrypted again. so after msm method reboot fastboot and flash modded twrp. reboot recovery flash CB or OOS. flash supersu flash kernel. Agin flash twrp.img from recovery itself and reboot recovery. After that reboot system and you are good to go. Make sure you have enough system space before flashing supersu and kernel. frow twrp file manager delete unneeded system apps 1st. DO NOT REBOOT in between.

nikhilsnigam said:
Yes you can but you will be encrypted again. so after msm method reboot fastboot and flash modded twrp. reboot recovery flash CB or OOS. flash supersu flash kernel. Agin flash twrp.img from recovery itself and reboot recovery. After that reboot system and you are good to go. Make sure you have enough system space before flashing supersu and kernel. frow twrp file manager delete unneeded system apps 1st. DO NOT REBOOT in between.
Click to expand...
Click to collapse
But i need unlocked bootloader to flash twrp, so i guess i need to unlock after i use Msmdownload tool right?

ach3fck said:
But i need unlocked bootloader to flash twrp, so i guess i need to unlock after i use Msmdownload tool right?
Click to expand...
Click to collapse
your bootloader doesn't get locked

nikhilsnigam said:
your bootloader doesn't get locked
Click to expand...
Click to collapse
Sorry to bother you, but i have one more question, i used Msmdownloadtool before, but only in Qualcomm download mode, can i use fastboot or i have to boot to EDL(qualcomm download mode)? And again sorry for taking your time.

ach3fck said:
Sorry to bother you, but i have one more question, i used Msmdownloadtool before, but only in Qualcomm download mode, can i use fastboot or i have to boot to EDL(qualcomm download mode)? And again sorry for taking your time.
Click to expand...
Click to collapse
you have to use qualcomm download mode by switching off your phone. pressing vol up button and connecting to usb.

nikhilsnigam said:
you have to use qualcomm download mode by switching off your phone. pressing vol up button and connecting to usb.
Click to expand...
Click to collapse
Yeah, i know that, thanks a lot, will try later all of this since i have no time now, will report how it went.Thanks!

Official TWRP 3.2.3-0 for Essential PH-1

I bought an Essential during one of Amazon's sales and I have finally produced a working, official TWRP for the device. I tested it on Essential's 9.0 official firmware with August security patches. Touch works and TWRP is able to decrypt your data even if you have a PIN / pattern / password set. MTP may or may not work, depending on what kernel you are using. The screen is still not using the right-most edge of the screen, but I've implemented a few dirty hacks that I will clean up later to make TWRP fit the screen better. It is NOT recommended to use custom themes at this time on this device due to the screen weirdness.
Since the Essential is an AB device that does not support fastboot boot, you will have to flash the initial TWRP image to the boot partition. You can either switch slots following the instructions on our website or download the latest factory image or make sure you have a recent copy of your current ROM so you can reflash the boot image. Take your pick. Especially for your first install, I recommend doing the install when you are close to computer so you can fix anything that may go wrong.
https://twrp.me/essential/essentialph1.html
#TWRPisEssential

Reserved.

Thank you more than you'll know man!!!!!

Fantastic! Thanks for the support

Sick! Thanks man!

Good deal, how does it handle September patches?

Forgive me if I'm missing something here, but does this mean it will always be on a slot?

hottcakes said:
Forgive me if I'm missing something here, but does this mean it will always be on a slot?
Click to expand...
Click to collapse
Edit
Proper thread with install instructions.
https://forum.xda-developers.com/essential-phone/how-to/guide-how-to-install-twrp-root-t3841922
edit end
how to install
fastboot getvar current-slot
say you get a
fastboot flash boot_b twrp.img
fastboot --set-active=b
now if you use volume rockers to go to recovery and then press power button to select you should boot into twrp.
Once in twrp, flash the twrp zip file.
then go to reboot. and change slot to a.
now reboot to system and you should boot into Android and you should also have twrp on both slots.
if you get current slot as b, then use "a" slot to flash twrp image.
video for those who need one. Also, has root instructions.
https://www.youtube.com/watch?v=7PYBYDbapho

@Dees_Troy thank you very much, this is greatly appreciated!
By the way, should the time zone work?
Thanks again!

If I have fingerprint/pattern protection, when I boot into twrp what will I see? Option to decrypt and continue without having to enter anything (I hope)? I don't want to be surprised and not know whether to continue or not.
Edit: Thanks for doing this!!!

Awesome!! Thank you so much!!
I am happy to report the touch screen in TWRP works fine with the September release.
NOTE: If you have MAGISK installed, you must install the stock boot image (to both slots), then install the TWRP patcher zip, and finally install Magisk LAST or the phone will continue rebooting into TWRP.
So once you are in TWRP, flash stock boot image, click reboot (don't actually reboot) and change to other slot, flash stock boot image, then flash TWRP installer zip, click reboot (don't actually reboot) and make sure you are on the slot your started with, now flash Magisk and reboot phone.
I only have one issue: if you have a pattern set for your lockscreen, TWRP will still prompt you for a password. So before booting into TWRP, change your pattern to a password (this way you don't lose all your stored fingerprints) and after getting back into Android, change back to your pattern. It decrypts perfectly fine with the lockscreen password; it just doesn't prompt for a pattern when a lockscreen pattern is set.
And a second very minor bug is the time and date shown in TWRP is incorrect.
Thank you again soooooo much!!!!
Edit: I found a fix for the issue with not being prompted for a pattern and being prompted for a password instead, even though you have a pattern set! The fix is if you have a lockscreen pattern, change it to a lockscreen password, boot into twrp, type your password (be very careful when you are typing because the screen and touch are sligly mis-aligned so look at the actual keys being pressed), reboot into Android, change your password back to a pattern, and now everytime you boot into TWRP, it will prompt you for your pattern. So, apparently, the pattern has to be set AFTER twrp is installed for twrp to recognize you have a pattern set and prompt you for it.

I had to remove Magisk before I could get twrp to stick. With Magisk I would just reboot back into recovery. Once the procedure is done with stock boot img you can reboot into recovery and flash kernel and magisk as you normally would with TWRP.
I should add that it also won't decrypt for me but not as big of a deal if you forget like it was when you had to flash a boot.img again with a PC.
Nice to have TWRP on a device again. Android doesn't feel right without it.

I know there is a thumbs up for the thanks but a it's also nice to hear. A sincere thanks to you and whoever might of helped along the way!

Ok so I'm going to ask is this permanent even if we flash a different rom or kernal to ethier slot

munchy_cool said:
how to install
fastboot getvar current-slot
say you get a
fastboot flash boot_b twrp.img
fastboot --setactive=b
now if you use volume rockers to go to recovery and then press power button to select you should boot into twrp.
Once in twrp, flash the twrp zip file.
then go to reboot. and change slot to a.
now reboot to system and you should boot into Android and you should also have twrp on both slots.
if you get current slot as b, then use a slot to flash twrp image.
Click to expand...
Click to collapse
Thanks this helped just one correction in the 2nd command fastboot --set-active=_b

gorm said:
Thanks this helped just one correction in the 2nd command fastboot --set-active=_b
Click to expand...
Click to collapse
Fastboot -ab accomplishes same thing. Use fastboot -aa for a slot.

Str0ntium said:
Fastboot -ab accomplishes same thing. Use fastboot -aa for a slot.
Click to expand...
Click to collapse
Good to know, thanks
Just nice to have a working TWRP .
Great day for future Essential Development:good:

galakanokis said:
I had to remove Magisk before I could get twrp to stick. With Magisk I would just reboot back into recovery. Once the procedure is done with stock boot img you can reboot into recovery and flash kernel and magisk as you normally would with TWRP.
I should add that it also won't decrypt for me but not as big of a deal if you forget like it was when you had to flash a boot.img again with a PC.
Nice to have TWRP on a device again. Android doesn't feel right without it.
Click to expand...
Click to collapse
I had a tough go at it also, having magisk already installed. Finally got it after a few trial and errors. And I have no decryption either... Something with magisk, perhaps? Either way, glad to have twrp back...

Wondering if this can now be modified to replace the ramdisk stock recovery for a permanent installation finally. Does this still rely on the Nougat kernel? I know building twrp on newer oreo kernel sources resulted in the touch driver not working at all.

Touch is not working for me, I'm on Sept security patch.

Nokia 8 won't boot to TWRP?

So, I wiped all data, system, cache, internal storage using TWRP and then I flash the system.img to System Image and boot.img to Boot into 2 slots (A & B). Consequently, I lose TWRP and root. I have gone back to May Security Patch Nokia 8 TA-1004. I have updated and updated up until October 2018 Patch.
Then, I tried to use "fastboot boot twrp.img", however it doesn't work. It is just stuck to POWERED BY ANDROID LOGO. Flashing twrp will break the wifi and I do not want that. Anybody has solutions for this? I can't get it to boot to TWRP. I use Android stock recovery and apply update in SD Card, not working as well.
I really want to have access root. All because of that stupid random restart occurs in this thread https://forum.xda-developers.com/nokia-8/help/nokia-8-sudden-restart-occurred-randomly-t3852357
Note: During flashing system.img which reverts back to stock one, I didn't use fastboot command. I use TWRP to revert back.

Download and extract this stock boot image and you can use it to root through Magisk's patch boot image option.
https://drive.google.com/file/d/11A8-jK0hm4j-ah3HwPpk8i_hwcoIwPBx/view?usp=drivesdk

ironman38102 said:
Download and extract this stock boot image and you can use it to root through Magisk's patch boot image option.
https://drive.google.com/file/d/11A8-jK0hm4j-ah3HwPpk8i_hwcoIwPBx/view?usp=drivesdk
Click to expand...
Click to collapse
Is this the latest stock boot image (october patch)?

For resolve a lower security than september can't boot to twrp try this method.
Boot to download mode. Then Use command.
Fastboot reboot bootloader => for enter again download mode
Fastboot boot twrp.... It will go to twrp well.

Topogigi said:
Is this the latest stock boot image (october patch)?
Click to expand...
Click to collapse
Um I think cuz Magisk took this backup right during the Install to Second Slot option

ironman38102 said:
Download and extract this stock boot image and you can use it to root through Magisk's patch boot image option.
https://drive.google.com/file/d/11A8-jK0hm4j-ah3HwPpk8i_hwcoIwPBx/view?usp=drivesdk
Click to expand...
Click to collapse
This is October patch? If it does, you are a lifesaver.
ValKyre said:
For resolve a lower security than september can't boot to twrp try this method.
Boot to download mode. Then Use command.
Fastboot boot bootloader => for enter again download mode
Fastboot boot twrp.... It will go to twrp well.
Click to expand...
Click to collapse
YOU SIR, ARE ROCK. This is very much working for me. I can boot already to twrp. No longer stuck in POWERED BY ANDROID LOGO.
Although you have mistyped the command. It should be "fastboot reboot bootloader". Anyway, thank you. I have given my thanks to you.

godofknife said:
This is October patch? If it does, you are a lifesaver.
YOU SIR, ARE ROCK. This is very much working for me. I can boot already to twrp. No longer stuck in POWERED BY ANDROID LOGO.
Although you have mistyped the command. It should be "fastboot reboot bootloader". Anyway, thank you. I have given my thanks to you.
Click to expand...
Click to collapse
Yup ... Sorry with my head not remember true command hehe

ironman38102 said:
Download and extract this stock boot image and you can use it to root through Magisk's patch boot image option.
Click to expand...
Click to collapse
So can i use this img to root with Magisk with patch boot image option? Is this October patch?
Edit: Stuck on Powered by Android logo => not October boot img

Mo4o293 said:
So can i use this img to root with Magisk with patch boot image option? Is this October patch?
Edit: Stuck on Powered by Android logo => not October boot img
Click to expand...
Click to collapse
My bad I guess

ironman38102 said:
Download and extract this stock boot image and you can use it to root through Magisk's patch boot image option.
https://drive.google.com/file/d/11A8-jK0hm4j-ah3HwPpk8i_hwcoIwPBx/view?usp=drivesdk
Click to expand...
Click to collapse
I wonder if some kind soul can offer some wisdom, I unlocked my bootloader and flashed twrp. All fine so far.
I then upgraded to Pie.
I then flashed Magisk.
I was getting some strange Magisk behaviour so uninstalled it but for some reason it did'nt restore stock boot and Play Store was misbehaving.
I then flashed this boot image ^^ and yes, very stupidly, I now have no wifi (my MAC address is screwed).
I can boot to OS but I have no File Manager, nor root and I don't really know what to try from here.
I cant get to recovery (twrp or stock), it just get stuck on the Powered by Android logo.
I have debugging enabled but adb just reports my device as offline.
I cant get in to fastboot mode either.
Really appreciate some help from a kind soul
Ta

Hello i unlocked bootloader and after working so hard i finally booted twrp img to my nokia 8 and from there i cant access to twrp it always opens stock recovery.pls help me.....
I tried 2 to 3 times but i cant access twrp the process was successful but cant access it

I would say if it does not boot to it, its not there. Just flash twrp again. Use the latest from their website to do it.

[MAGISK] [BOOT] Pre rooted Boot.img for Oneplus 6T Android 10 Open Beta 1

Hi Guys
UPDATE 2: (2/11/2019) Boot img now patched to Magisk V20.1 and added Google Drive as a mirror
UPDATE: It has come to my attention that some users are having issues with this version, please note this is still in beta and root isn't fully supported yet, also please make sure your running the latest magisk manager (version 7.3.5 at the time of this update) BEFORE flashing the patched boot IMG, those currently having issues, try flashing the stock IMG provided and installing the latest magisk manager then flashing the patched IMG
here is a working magisk patched boot img for you guys wanting root on your new android 10 open beta 1 software.
PLEASE BE AWARE THIS DOESNT COME WITH TWRP, THIS MAY ALSO BREAK THE ORIGINAL STOCK RECOVERY, BY FLASHING THIS BOOT IMG, YOU TAKE FULL RESPONSIBILITY FOR YOUR DEVICE AND NEITHER I OR XDA WILL BE HELD RESPONSIBLE
this DOESNT contain TWRP but is just rooted with magisk v20.0
simply flash the provided file in fastboot with the following command
Code:
fastboot flash boot magisk_patched.img
Code:
fastboot reboot
Please note this will ONLY work with the OnePlus 6T
i have also provided the stock android 10 boot img in case anything goes wrong
DOWNLOADS::
[CURRENT VERSION - Magisk V20.1]
Mega -> https://mega.nz/#!YI5BkICC!66fiUUdmg1EgGcTNExHZ52IoliVY4HBMBdwxErpI-co
Google Drive -> https://drive.google.com/file/d/1xyRPzsKh1kQXK0_RpdnesuR85vc6FvRf/view?usp=sharing
[OLD Versions]
[Magisk V20.0]
https://mega.nz/#!cQRFwA7b!R1yLz1ozFUTEOLXv-OREK-oF5YeUGN1PrWvSSh22vHw
Stock Boot img
https://mega.nz/#!1BAnRCoK!nu6UVAnR2yHnbaf54FEhc7U_3oEyP1q2BFMU0LK7XC4
Credits:
@oneplus for the phone and stock boot image
@topjohnwu for magisk and his boot image patcher

Trying now. Will report.
Update: Well, after a reboot, it is just sitting at the spinning animated boot logo...been like 10 minutes.
Also couldn't enter recovery after flashing the new patched boot img.
Update 2: Flashed back stock boot.img then recovery worked and phone booted fine.

Do i need a computer for this ?

techlogik said:
Trying now. Will report.
Update: Well, after a reboot, it is just sitting at the spinning animated boot logo...been like 10 minutes.
Also couldn't enter recovery after flashing the new patched boot img.
Update 2: Flashed back stock boot.img then recovery worked and phone booted fine.
Click to expand...
Click to collapse
Did you try this by chance? We have the A/B partitions I don't think "fastboot flash boot ... " flashes both partitions.
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img

charlie95113 said:
Do i need a computer for this ?
Click to expand...
Click to collapse
yes because fastboot command is needed, henced done using pc.

mywebslave said:
Did you try this by chance? We have the A/B partitions I don't think "fastboot flash boot ... " flashes both partitions.
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Click to expand...
Click to collapse
Only the active partition gets flashed by default that is booting...it does that fine. I don't think Magisk is compatible on the OP6T for rooting and patching the new boot.img.
Same thing even manually flashing both. It just sits with the spinning boot animation for eternity.
I also used the payload extractor and took the stock boot.img and patched it with Magisk myself. Same issue. So obviously Magisk just doesn't suppor this phone yet and Devs need to work on it.
Thx

techlogik said:
Did you try this by chance? We have the A/B partitions I don't think "fastboot flash boot ... " flashes both partitions.
Only the active partition gets flashed by default that is booting...it does that fine. I don't think Magisk is compatible on the OP6T for rooting and patching the new boot.img.
Same thing even manually flashing both. It just sits with the spinning boot animation for eternity.
I tried patching the stock boot.img myself as well, it ends up being the exact same size as the TS for this method...same problem.
Thx
Click to expand...
Click to collapse
Weird I was able to do the local update and install magisk to the inactive partition prior to reboot. On reboot worked fine just no recovery.
Maybe it just doesn't like this particular one. I used the latest canary version.
I'll try patching one when I get home and see how it goes. If it works out I'll post it here.

mywebslave said:
Weird I was able to do the local update and install magisk to the inactive partition prior to reboot. On reboot worked fine just no recovery.
Maybe it just doesn't like this particular one. I used the latest canary version.
I'll try patching one when I get home and see how it goes. If it works out I'll post it here.
Click to expand...
Click to collapse
Yes, I did the same thing. Also, as mentioned above, I used the payload extractor and grabbed the stock boot.img right from the Beta1 zip file.
Then, cppied over to the phone, used Magisk with Canary build as well, then flashed both boot_a and b directly with the patched file. Just sits at the animated boot spinning.
Flash stock images back, boots right up. I'm on a OP6T unlocked US phone on VZW. No problems with any other build beta or stable with twrp or magisk and custom kernels.
Thanks

techlogik said:
Yes, I did the same thing. Also, as mentioned above, I used the payload extractor and grabbed the stock boot.img right from the Beta1 zip file.
Then, cppied over to the phone, used Magisk with Canary build as well, then flashed both boot_a and b directly with the patched file. Just sits at the animated boot spinning.
Flash stock images back, boots right up. I'm on a OP6T unlocked US phone on VZW. No problems with any other build beta or stable with twrp or magisk and custom kernels.
Thanks
Click to expand...
Click to collapse
So weird. Same setup as mine op6t, unlocked, Verizon. Haven't had a single issue. I'm gonna give it a try in a few minutes. I'll see what happens
---------- Post added at 08:19 PM ---------- Previous post was at 07:43 PM ----------
I did a fresh payload dump. Flashed to both A/B partitions, reboot, booted up fast as hell.
Here's the one I patched
magisk_patched.img
boot.img
Not sure if it makes a difference but I did mine on linux with latest platform tools.

mywebslave said:
So weird. Same setup as mine op6t, unlocked, Verizon. Haven't had a single issue. I'm gonna give it a try in a few minutes. I'll see what happens
---------- Post added at 08:19 PM ---------- Previous post was at 07:43 PM ----------
I did a fresh payload dump. Flashed to both A/B partitions, reboot, booted up fast as hell.
Here's the one I patched
magisk_patched.img
boot.img
Not sure if it makes a difference but I did mine on linux with latest platform tools.
Click to expand...
Click to collapse
So should we be using this instead?
Sent from my ONEPLUS A6013 using Tapatalk

mywebslave said:
So weird. Same setup as mine op6t, unlocked, Verizon. Haven't had a single issue. I'm gonna give it a try in a few minutes. I'll see what happens
---------- Post added at 08:19 PM ---------- Previous post was at 07:43 PM ----------
I did a fresh payload dump. Flashed to both A/B partitions, reboot, booted up fast as hell.
Here's the one I patched
magisk_patched.img
boot.img
Not sure if it makes a difference but I did mine on linux with latest platform tools.
Click to expand...
Click to collapse
Gave this a try, no luck. Stuck in bootloop but as soon as I flashed back the stock boot, it booted up just fine

zhenliang1102 said:
Gave this a try, no luck. Stuck in bootloop but as soon as I flashed back the stock boot, it booted up just fine
Click to expand...
Click to collapse
And this one?
fastboot --set_active=a
fastboot flash boot magisk_patched.img
fastboot --set_active=b
fastboot flash boot magisk_patched.img
fastboot --set_active=a
fastboot reboot

when i flash the magisk_patched.img and my cellphone reboot my cellphone does not recognize my simcard and have no network, am back on the stock boot.img

cultofluna said:
And this one?
fastboot --set_active=a
fastboot flash boot magisk_patched.img
fastboot --set_active=b
fastboot flash boot magisk_patched.img
fastboot --set_active=a
fastboot reboot
Click to expand...
Click to collapse
I doubt this would work because the patched image is only 26mb while the stock boot image is 64mb. Someone mentioned this in the OB thread

Black screen after the update
[Solved] I am facing a serious issue. I was on Magisk v20.0 and Twrp 3.3.1-1
- I uninstalled Magisk
- Installed the OTA from local
- Installed Magisk on the second partition
- Reboot
Phone rebooted
But I am getting a totally blacked out screen. Calls work, vibration, Oneplus gestures work, just the screen is black (even in safe mode)
Can anyone please help me get this sorted (with data preserved if possible) I didn't back up the data cuz I wanted to do it after I updated to 10 (as downgrading wipes the system)
Problems:
ADB is not working (unauthorized) as I haven't turned on any developer options yet and can't due to black screen.
No way to unroot at this point without adb or twrp.
Thanks in advance.
UPDATE: Flashed boot.img and it worked. I guess magisk.img is not compatible or I am doing it wrong. My bet is on the latter.

Hy, do you have proximity sensor problem after update?! Thanks...is anything i can do?

jack5225 said:
[Solved] I am facing a serious issue. I was on Magisk v20.0 and Twrp 3.3.1-1
- I uninstalled Magisk
- Installed the OTA from local
- Installed Magisk on the second partition
- Reboot
Phone rebooted
But I am getting a totally blacked out screen. Calls work, vibration, Oneplus gestures work, just the screen is black (even in safe mode)
Can anyone please help me get this sorted (with data preserved if possible) I didn't back up the data cuz I wanted to do it after I updated to 10 (as downgrading wipes the system)
Problems:
ADB is not working (unauthorized) as I haven't turned on any developer options yet and can't due to black screen.
No way to unroot at this point without adb or twrp.
Thanks in advance.
UPDATE: Flashed boot.img and it worked. I guess magisk.img is not compatible or I am doing it wrong. My bet is on the latter.
Click to expand...
Click to collapse
Same happened to me
Phone boots to a Black screen
adb reboot bootloader -> works
fastboot flash boot boot.img -> works
Only Patched boot.img -> boots to black screen
Sent from my ONEPLUS A6010 using Tapatalk

Same for me. Softbrick and phone doesn't boot. It also encrypted my whole /data with diferent password i think and I had to wipe whole /data partition. System boots after wiping data storage but as soon as I install magisk it doesn't want to boot again. I guess I will wait for final image and TWRP support.

i couldnt flash it manually (via cmd), but all in one tool managed it well.
worked fine and quick,thank you

Crazy that some phones it is working and others it doesn't. Nothing we are doing wrong, OP has work to do still. I can imagine this official update to Q is going to cause a support fiasco...if you want to root that is. ROFL. All works fine with stock though upgrade. Understand it is Beta, but they claim a November official release
We are going to need some Dev help. Or going to need to sell this phone and upgrade to the 7t or Pro..haha

Question stuck at bootlogo after installing gsi

Hello everyone. i just want to install Gsi on an new unlocked tab a8, after flashing twrp, I use the fastbootd mode to flash the gsi and installed the multi-disable zip. when I want to reboot to os, it stucked at bootlogo. I don't know where I am wrong, so please help me, in appreciation

WolfHRB said:
Hello everyone. i just want to install Gsi on an new unlocked tab a8, after flashing twrp, I use the fastbootd mode to flash the gsi and installed the multi-disable zip. when I want to reboot to os, it stucked at bootlogo. I don't know where I am wrong, so please help me, in appreciation
Click to expand...
Click to collapse
We don't know where you went wrong either because you didn't list the steps you took or what GSI you flashed or what stock ROM you started from. Or where you are looping.

starting firmware: X200ZCU2CWD3
Steps: 1. Unlock BL
2. flash TWRP via Odin V3.14
3. Format data partition
4. flash dm-verity disabler (File name: Disable_Dm-Verity_ForceEncrypt)
5. reboot to fastbootd mode (using TWRP reboot menu)
6. fastboot erase system
7. fastboot flash system "img path"
8. fastboot -w
9. fastboot reboot

lewmur said:
We don't know where you went wrong either because you didn't list the steps you took or what GSI you flashed or what stock ROM you started from. Or where you are looping.
Click to expand...
Click to collapse
starting firmware: X200ZCU2CWD3
Steps: 1. Unlock BL
2. flash TWRP via Odin V3.14
3. Format data partition
4. flash dm-verity disabler (File name: Disable_Dm-Verity_ForceEncrypt)
5. reboot to fastbootd mode (using TWRP reboot menu)
6. fastboot erase system
7. fastboot flash system "img path"
8. fastboot -w
9. fastboot reboot

WolfHRB said:
starting firmware: X200ZCU2CWD3
Steps: 1. Unlock BL
2. flash TWRP via Odin V3.14
3. Format data partition
4. flash dm-verity disabler (File name: Disable_Dm-Verity_ForceEncrypt)
5. reboot to fastbootd mode (using TWRP reboot menu)
6. fastboot erase system
7. fastboot flash system "img path"
8. fastboot -w
9. fastboot reboot
Click to expand...
Click to collapse
Don't flash dm-verity disabler for this device and the GSI should boot as long as it's compatible

kevinco1 said:
Don't flash dm-verity disabler for this device and the GSI should boot as long as it's compatible
Click to expand...
Click to collapse
Without this alway bootloop logo too.
1. Extract the IMG to the adb folder and rename it system.img
2. Flash TWRP with ODIN
3. When booting into TWRP using the Volume up and Power key, select reboot and then fast boot.
4. When you get there, go on your PC and open cmd with the adb folder.
5. Now type fastboot devices just make sure you have the device connect properly. Type fastboot -w after.
6. Type "fastboot flash system system.img" press enter and wait for it to finish. The last line should be be where you can type other commands.
7. When its finished, type fastboot reboot fastboot.

stradfred said:
Without this alway bootloop logo too.
1. Extract the IMG to the adb folder and rename it system.img
2. Flash TWRP with ODIN
3. When booting into TWRP using the Volume up and Power key, select reboot and then fast boot.
4. When you get there, go on your PC and open cmd with the adb folder.
5. Now type fastboot devices just make sure you have the device connect properly. Type fastboot -w after.
6. Type "fastboot flash system system.img" press enter and wait for it to finish. The last line should be be where you can type other commands.
7. When its finished, type fastboot reboot fastboot.
Click to expand...
Click to collapse
What exact GSI and build are you trying to install? There are only a few that are compatible, otherwise you're not gonna have any other luck flashing

I tryed with on my X200XXU2CWC1 firmware:
lineage-19.1-20230418-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230325-UNOFFICIAL-a64_bgN.img
Old version too but the same result...
Which version we are sure that works?

stradfred said:
I tryed with on my X200XXU2CWC1 firmware:
lineage-19.1-20230418-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230325-UNOFFICIAL-a64_bgN.img
Old version too but the same result...
Which version we are sure that works?
Click to expand...
Click to collapse
Make sure you are only trying to flash arm64 builds for this device
Both 19.1-20230418 and 20.0-20230324 do install properly but there's certain bugs that make them unfit to be used as a daily driver.
If you're looking for the latest build where everything works (including bluetooth) flash 20.0-20230218

stradfred said:
Without this alway bootloop logo too.
1. Extract the IMG to the adb folder and rename it system.img
2. Flash TWRP with ODIN
3. When booting into TWRP using the Volume up and Power key, select reboot and then fast boot.
4. When you get there, go on your PC and open cmd with the adb folder.
5. Now type fastboot devices just make sure you have the device connect properly. Type fastboot -w after.
6. Type "fastboot flash system system.img" press enter and wait for it to finish. The last line should be be where you can type other commands.
7. When its finished, type fastboot reboot fastboot.
Click to expand...
Click to collapse
You left out the step to format data and factory wipe.

lewmur said:
You left out the step to format data and factory wipe.
Click to expand...
Click to collapse
That's right!
How is it normal to do this command after having flashed a ROM ???
Once done, I boot of course on lineage after a few moments on the Samsung logo.
Which version of lineage is the most stable, 19 (Android 12) or 20 (Android 13)?
Thank you both for your help.

kevinco1 said:
If you're looking for the latest build where everything works (including bluetooth) flash 20.0-20230218
Click to expand...
Click to collapse
https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/History/lineage-20.0-20230218-UNOFFICIAL-arm64_bgN.img.xz/download
I tried this.

stradfred said:
That's right!
How is it normal to do this command after having flashed a ROM ???
Once done, I boot of course on lineage after a few moments on the Samsung logo.
Which version of lineage is the most stable, 19 (Android 12) or 20 (Android 13)?
Thank you both for your help.
Click to expand...
Click to collapse
TWRP and fastboot can't handle the encrypted data partition. So you need to format it. Current versions of LOS re-encrypt it as soon as you boot to system. And you can't use dm-verity on this model, so you can't disable it.

stradfred said:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/History/lineage-20.0-20230218-UNOFFICIAL-arm64_bgN.img.xz/download
I tried this.
Click to expand...
Click to collapse
Did you try this build before or after the realization you had left out the steps to wipe and factory reset?

Has anyone managed to install a GSI on the SM-X200 with X200XXU2CWC1 firmware? I tried different LOS 20 and LOS 19 GSIs, with and without GAPPS, including the ones mentioned earlier from March and April, but did not succeed a single time. The tablet gets always stuck in a boot loop. I flashed via TWRP and wiped and formatted data every time.
Is it possibly the vendor firmware (SW rev. 2) that prevents the GSI from running? All guides from this forum seems to relate to a SW rev. 1 firmware like X200XXS1CWA3.

mrspeccy said:
Has anyone managed to install a GSI on the SM-X200 with X200XXU2CWC1 firmware? I tried different LOS 20 and LOS 19 GSIs, with and without GAPPS, including the ones mentioned earlier from March and April, but did not succeed a single time. The tablet gets always stuck in a boot loop. I flashed via TWRP and wiped and formatted data every time.
Is it possibly the vendor firmware (SW rev. 2) that prevents the GSI from running? All guides from this forum seems to relate to a SW rev. 1 firmware like X200XXS1CWA3.
Click to expand...
Click to collapse
If you mean you used the "Install" button in TWRP to flash, then that is your mistake. The "Install" button only has the option to flash the "Super" partition and not the "System". You need to use "Fastboot" to flash the system image. I flashed from CWD2 which is even later than CWC1, so that shouldn't be a problem. If it was, then TWRP wouldn't have worked. I'm running LOS 20 20300507 bgN.

No, I used TWRP to get into fastboot mode and said fastboot flash system ...img. I have no idea what I did wrong. Previously I flashed Lineage on a couple of Samsung Tablets (SM-T510, SM-T505).

mrspeccy said:
No, I used TWRP to get into fastboot mode and said fastboot flash system ...img. I have no idea what I did wrong. Previously I flashed Lineage on a couple of Samsung Tablets (SM-T510, SM-T505).
Click to expand...
Click to collapse
There are only certain LOS builds that work with this device, you're wasting your time if you are blindly flashing random ones.
Refer to earlier posts to confirm which ones do work. And like @lewmur just reported the newest build 20300507 bgN does flash successfully

The 20230507 bgN was actually the first build I tried before I went to older variants, including the 20220814 bgN that is mentioned in a different thread.
@lewmur : Did you do a clean flash and format data before you installed the 20230507 build on the CWD2 firmware? There might be some issues with format data and the TWRP 3.7.0-12.2 from this forum (https://forum.xda-developers.com/t/...-for-2021-galaxy-tab-a8-10-5-sm-x200.4488691/) on the latest kernel. After I format data in TWRP, the tablet is recognized as writable media in Windows, but I get reading and writing errors when I try to access the about 22 GB large partition.
I know that it is impossible to roll back the bootloader to revision 1, but may it be possible that I extract and flash a kernel from the X200XXS1CWA3 to further investigate this issue?

mrspeccy said:
The 20230507 bgN was actually the first build I tried before I went to older variants, including the 20220814 bgN that is mentioned in a different thread.
@lewmur : Did you do a clean flash and format data before you installed the 20230507 build on the CWD2 firmware? There might be some issues with format data and the TWRP 3.7.0-12.2 from this forum (https://forum.xda-developers.com/t/...-for-2021-galaxy-tab-a8-10-5-sm-x200.4488691/) on the latest kernel. After I format data in TWRP, the tablet is recognized as writable media in Windows, but I get reading and writing errors when I try to access the about 22 GB large partition.
I know that it is impossible to roll back the bootloader to revision 1, but may it be possible that I extract and flash a kernel from the X200XXS1CWA3 to further investigate this issue?
Click to expand...
Click to collapse
You must do a clean flash. The purpose of formatting the data partition is to get rid of the encryption. TWRP can't handle the encryption. And LOS will re-encrypt it the first time you boot to system. As to extracting the kernel from CWA3, I don't advise doing that. It could hard brick the tablet.