[Stock ROM] A2017G TWRP flashable Images - ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve

Because meanwhile it's hard to find new A2017G images in Drakenfx TWRP thread I decided to open a new thread with the files from me.
Notes:
TWRP used 3.1.0.0
Coming from previous Stock Nougat System try to dirty flash the System and root with Supersu 2.79 (not sr3). After that wipe cache/dalvik.
If it isn't working this way, try formating system partition and flash system again. TWRP will tell you that there is no system installed and the system will for sure not boot if so. Restart into TWRP and flash the System and Supersu again. If this is still not working you have to factory reset your phone.
Keep care for Dragons. Its possible the update will change your data partition to f2fs. In combination with Supersu this is bad. If so you have to format data to ext4.
Using Supersu it's not necessary to install the no-verity patch, it's already included in Supersu.
Be carefull, next dragon ahead. Not installing Supersu after a virgin installation (data wiped/factory reset) will lead to a stock recovery instead of TWRP after the first boot.
[Nougat:]
B04:
I can't believe it. This ROM is up to now fully functional. ZTE finally did it. Cam is working, Dolby, Live Wallpaper also, no Tencent spyware, I wonder where the pittfall is!?!
Bootstack
https://www.androidfilehost.com/?fid=457095661767159296
System
https://www.androidfilehost.com/?fid=745425885120730040
Full Stock Reverter (If you like to revert Fastboot/Aboot/Recovery to Stock version)
https://www.androidfilehost.com/?fid=529152257862724933
B02:
Bootstack
https://www.androidfilehost.com/?fid=817550096634766076
System
https://www.androidfilehost.com/?fid=745425885120728390
Full Stock Reverter (If you like to revert Fastboot/Aboot/Recovery to Stock version)
https://www.androidfilehost.com/?fid=673368273298951352
B01:
Bootstack
https://www.androidfilehost.com/?fid=745425885120713802
System
https://www.androidfilehost.com/?fid=673368273298937254
[Marshmallow]
B09
Bootstack
https://www.androidfilehost.com/?fid=457095661767125769
System
https://www.androidfilehost.com/?fid=673368273298919671

@tron1 tried dirty flashing over b01 was stuck in ugly boot screen
same result after wiping and clean installing b02,
towards end of system.zip file to lines of red error line stating error log generated,and zip successfully flashed.

tuiyaan said:
@tron1 tried dirty flashing over b01 was stuck in ugly boot screen
same result after wiping and clean installing b02,
towards end of system.zip file to lines of red error line stating error log generated,and zip successfully flashed.
Click to expand...
Click to collapse
TWRP version?

tron1 said:
TWRP version?
Click to expand...
Click to collapse
twrp-3.0.3-1-ailsa_ii

tuiyaan said:
twrp-3.0.3-1-ailsa_ii
Click to expand...
Click to collapse
This is ancient. Try it with 3.1.0 or 3.0.4

Thanks alot.
Really handy to have all the files in one place.

Can I flash this ZTE_A2017GV1.2.0B02_Stock_System_by_tron1.zip on my A2017U variant with A2017U boot stack?

khangozzy said:
Can I flash this ZTE_A2017GV1.2.0B02_Stock_System_by_tron1.zip on my A2017U variant with A2017U boot stack?
Click to expand...
Click to collapse
I can only ask you to try and tell us if it is working. The other way it is working. I've been succesfully on BadBoys ROM with A2017G.

I'm on A2017G , LOS 14.1 from the 1st may. Can I dirty flash your B02 bootstack to get it up to date ?
Does the bootstack contains the latest baseband ?

tron1 said:
This is ancient. Try it with 3.1.0 or 3.0.4
Click to expand...
Click to collapse
tried it with 3.0.4 twrp no error but stuck in boot menu
tried with B01 and B02.
back to b10 with twrp zip

tuiyaan said:
tried it with 3.0.4 twrp no error but stuck in boot menu
tried with B01 and B02.
back to b10 with twrp zip
Click to expand...
Click to collapse
Tried flashing Supersu after flashing system? Also flashed Bootstack?

tron1 said:
Tried flashing Supersu after flashing system? Also flashed Bootstack?
Click to expand...
Click to collapse
Danke bro Danke
my device is alive and B02 updated
thank you for your patience
flashing SU did the job
i was missing this step

tron1 said:
I can only ask you to try and tell us if it is working. The other way it is working. I've been succesfully on BadBoys ROM with A2017G.
Click to expand...
Click to collapse
It works well with my lastest A2017U B25 bootstack.
Btw, how can I disable the Mi-POP notification when it turned on?
Sent from my ZTE A2017G using Tapatalk

khangozzy said:
It works well with my lastest A2017U B25 bootstack.
Btw, how can I disable the Mi-POP notification when it turned on?
Click to expand...
Click to collapse
Should be digged somewhere in the settings. Can't tell you exactly because I've removed this piece of crapware.

khangozzy said:
It works well with my lastest A2017U B25 bootstack.
Btw, how can I disable the Mi-POP notification when it turned on?
Sent from my ZTE A2017G using Tapatalk
Click to expand...
Click to collapse
It can't be removed while mipop is active. Hope it'll be fixed in next update

joaste said:
It can't be removed while mipop is active. Hope it'll be fixed in next update
Click to expand...
Click to collapse
It doesn't show on US B19 ROM.
Sent from my ZTE A2017G using Tapatalk

khangozzy said:
It doesn't show on US B19 ROM.
Sent from my ZTE A2017G using Tapatalk
Click to expand...
Click to collapse
Not even when you drag down the notification window?

joaste said:
Not even when you drag down the notification window?
Click to expand...
Click to collapse
Yes
Sent from my ZTE A2017G using Tapatalk

Update!!! B04 is up and running.

I'm on Marshmallow B09 unlocked and twrp. Can I just flash B04 Bootstack and after that B04 System for upgrading to nougat?
And which SuperSU version to flash for root?
and which partitions i need to wipe before/after flashing Nougat?
Thank you!

Related

{GUIDE} Jumping between 3.5.2/3.2.6 and New Released CM based Roms (Eg: RR 5.7.4)

Oneplus has Screwed a lot of things between 3.5.2 AND 3.2.6..!! I wanted to try newest version of RR released by Blackjubel. But had issues.
Took me 5 minutes figure out things and decided to share it here:
IMPORTANT POST..!!! READ..!!! Credit for firmware files to @davidxantos
For people coming from 3.5.2 or 3.2.6
I am making a very important post. This is meant for all those who are using latest community build of Oneplus 3 and want to try another rom. You will not be able to do so as the twrp you are using will not flash roms completely and the firmware of community build will not let you flash the latest build of twrp. So here is what you need to do.
READ CAREFULLY:
STEP 1 : Grab firmware for 3.2.6 from this link and flash. flashing this will BREAK your fingerprint sensor. WAIT read on.
https://drive.google.com/…/0ByD3oqJ_...0;/view…
STEP 2: Now flash latest twrp 3.0.2.1 . Now you are on the latest twrp.
STEP 3: Now Flash firmware for 3.2.4 from this link. YOU HAVE your finger print sensor back..!
https://drive.google.com/…/0ByD3oqJ_...0;/view…
Now you have the latest twrp again and also can flash anything you want to..!!
Thanks to Oneplus for screwing this..!
Thanks but 3. 2.6 files do not found
No link works!
Just go find another link if these here don't work ...
There is a thread with all official firmwares. Or just use Google.
Sent from my OnePlus 3 using Tapatalk
3.2.4 https://drive.google.com/file/d/0ByD3oqJ_uj0VWjVMbmZoZS1kejg/view
3.2.6 https://drive.google.com/file/d/0ByD3oqJ_uj0VZUFjblBSbEVNRGs/view?usp=sharing
XDA app screwed the links
I tried but i bricked the phone. I cani only restore with the Qualcomm tool but now im stuck on the oxygen 3.1.2 and every time that flash any rom or OTA i brick the phone
gelomc said:
I tried but i bricked the phone. I cani only restore with the Qualcomm tool but now im stuck on the oxygen 3.1.2 and every time that flash any rom or OTA i brick the phone
Click to expand...
Click to collapse
This is strange..
gelomc said:
I tried but i bricked the phone. I cani only restore with the Qualcomm tool but now im stuck on the oxygen 3.1.2 and every time that flash any rom or OTA i brick the phone
Click to expand...
Click to collapse
Could it be that your bootloader is now locked again after using the unbrick tool?
DavidXanatos said:
Could it be that your bootloader is now locked again after using the unbrick tool?
Click to expand...
Click to collapse
No it's unlocked i checked
---------- Post added at 08:39 PM ---------- Previous post was at 08:38 PM ----------
geekynoob said:
This is strange..
Click to expand...
Click to collapse
I know...
I was on 3.2.6 after the OTA. I installed TWRP 3.0.2.1 and re-rooted it. I then took a backup and proceeded to flash RR 5.7.4. Broken fingerprint scanner/home button.
First, does anyone know why this happens? Can it be fixed?
In the meantime, do we need to revert to 3.2.4 to be able to install other roms and not break the the fps/hb?
Can anyone point me to a TWRP flashable version of 3.2.4? <-- Got this, Thanks.
Thanks in advance.
Edit to add below
I did what was detailed in the OP from stock rooted 3.2.6. I flashed the 3.2.6 firmware from TWRP. Rebooted to bootloader. Flashed TWRP 3.0.2.1 via fastboot. Flashed 3.2.4 firmware from TWRP. FPS/HB broken.
Did I miss something?
Reflashed 3.2.6 firmware on a hunch. FPS/HB working again.
My goal is to get to RR 5.7.4 with a working FPS/HB. Any ideas?
Thanks again.
EdHicks said:
I was on 3.2.6 after the OTA. I installed TWRP 3.0.2.1 and re-rooted it. I then took a backup and proceeded to flash RR 5.7.4. Broken fingerprint scanner/home button.
First, does anyone know why this happens? Can it be fixed?
In the meantime, do we need to revert to 3.2.4 to be able to install other roms and not break the the fps/hb?
Can anyone point me to a TWRP flashable version of 3.2.4? <-- Got this, Thanks.
Thanks in advance.
Edit to add below
I did what was detailed in the OP from stock rooted 3.2.6. I flashed the 3.2.6 firmware from TWRP. Rebooted to bootloader. Flashed TWRP 3.0.2.1 via fastboot. Flashed 3.2.4 firmware from TWRP. FPS/HB broken.
Did I miss something?
Reflashed 3.2.6 firmware on a hunch. FPS/HB working again.
My goal is to get to RR 5.7.4 with a working FPS/HB. Any ideas?
Thanks again.
Click to expand...
Click to collapse
It's easy mate..
Flash rr and then flash the 3.2.4 fw.. As u have a good twrp now.. Simple..
geekynoob said:
Oneplus has Screwed a lot of things between 3.5.2 AND 3.2.6..!! I wanted to try newest version of RR released by Blackjubel. But had issues.
Took me 5 minutes figure out things and decided to share it here:
IMPORTANT POST..!!! READ..!!! Credit for firmware files to @davidxantos
For people coming from 3.5.2 or 3.2.6
I am making a very important post. This is meant for all those who are using latest community build of Oneplus 3 and want to try another rom. You will not be able to do so as the twrp you are using will not flash roms completely and the firmware of community build will not let you flash the latest build of twrp. So here is what you need to do.
READ CAREFULLY:
STEP 1 : Grab firmware for 3.2.6 from this link and flash. flashing this will BREAK your fingerprint sensor. WAIT read on.
https://drive.google.com/â?¦/0ByD3oqJ_...0;/viewâ?¦
STEP 2: Now flash latest twrp 3.0.2.1 . Now you are on the latest twrp.
STEP 3: Now Flash firmware for 3.2.4 from this link. YOU HAVE your finger print sensor back..!
https://drive.google.com/â?¦/0ByD3oqJ_...0;/viewâ?¦
Now you have the latest twrp again and also can flash anything you want to..!!
Thanks to Oneplus for screwing this..!
Click to expand...
Click to collapse
In short, we cannot flash official twrp via modified twrp? Can't we just flash 3.2.4 without flashing 3.2.6 firmware?
z31416 said:
In short, we cannot flash official twrp via modified twrp? Can't we just flash 3.2.4 without flashing 3.2.6 firmware?
Click to expand...
Click to collapse
Nice u will get a black screen..
geekynoob said:
Nice u will get a black screen..
Click to expand...
Click to collapse
Thanks for this. I'm about to flash 3.2.4 fw only.
Good thing I saw this thread.
So step by step procedure if we wamt to flash other roms are:
-reboot to recovery (modifoed twrp)
-wipe
-flash 3.2.6 fw via modified twrp
-flash/install official twrp.img
-flash 3.2.4 fw
-flash rom etc
-finally reboot?
i'm using multi rom with FOS 1.5.1 as primary and whenever i flash RR(Flashing 3.2.4 firmware before and after too) and custom rom, FPS/home button not recognised.
what am i doing wrong, although multirom does have individual space why cant the older firmware doesnt work. everything except the home button is working fine.
can anyone explain how it works.
z31416 said:
Thanks for this. I'm about to flash 3.2.4 fw only.
Good thing I saw this thread.
So step by step procedure if we wamt to flash other roms are:
-wipe
-flash 3.2.6 fw via modified twrp
-flash/install official twrp.img
-flash 3.2.4 fw
-flash rom etc
-finally reboot?
Click to expand...
Click to collapse
Modded twrp can be used to flash 3.2.6 or 3.5.2 oos.. Now if u want to go back.. Using the modded twrp flash the 3.2.4 files.. Just reboot recovery now flash non modded twrp as u have 3.2.4 files official twrp will work.. And then flash any rom u want..
green. said:
i'm using multi rom with FOS 1.5.1 as primary and whenever i flash RR(Flashing 3.2.4 firmware before and after too) and custom rom, FPS/home button not recognised.
what am i doing wrong, although multirom does have individual space why cant the older firmware doesnt work. everything except the home button is working fine.
can anyone explain how it works.
Click to expand...
Click to collapse
Multi rom cannot distinguish firmware files.. They are core files.. So fp won't work..
geekynoob said:
Multi rom cannot distinguish firmware files.. They are core files.. So fp won't work..
Click to expand...
Click to collapse
okay, so the developer have to include the firmware in their roms in future build, thats how it works, right?
and while experimenting i flashed OOS 3.2.4 firmware but FPS working fine in FOS 1.5.1. how come it is?
z31416 said:
Thanks for this. I'm about to flash 3.2.4 fw only.
Good thing I saw this thread.
So step by step procedure if we wamt to flash other roms are:
-reboot to recovery (modifoed twrp)
-wipe
-flash 3.2.6 fw via modified twrp
-flash/install official twrp.img
-flash 3.2.4 fw
-flash rom etc
-finally reboot?
Click to expand...
Click to collapse
This will do it. It's how I got going. I went from stock rooted 3.2.6 OOS to RR 5.7.4.
Thanks for putting to words for others.
green. said:
okay, so the developer have to include the firmware in their roms in future build, thats how it works, right?
and while experimenting i flashed OOS 3.2.4 firmware but FPS working fine in FOS 1.5.1. how come it is?
Click to expand...
Click to collapse
I've done a bit of Dev.. But i am not sure about ur statement.. .. And cm based roms don't have fw files.. Feel like a noob lol..

TWRP/Stock Recovery can´t install any Rom!

Hello i need help. I was on OOS 4.0. Like to update to 4.0.1 with clean System. So i boot to TWRP and make fullwipe(format:data/system/cache-dalvik cache)
After flash the 4.0.1 twrp says no os install. Ihave test another rom from this side https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015 but no way.
After that i flash stock recovery (fastboot) and stock rom via adb sideload but after 46% the installation failed (3 times).
Sorry for bad english and thanks for all
I read somewhere that TWRP is not compatible with the OSS 4.0 or higher and that's why you get errors when trying to install them. So, to make it work you gotta install the newest and beta version of TWRP...
Here you go, as I already said, it's a beta version, I'm not 100% sure if it'll work...
https://build.nethunter.com/test-builds/twrp/oneplus/twrp-3.0.3-1-beta1-oneplus3t.img
enzzo28 said:
I read somewhere that TWRP is not compatible with the OSS 4.0 or higher and that's why you get errors when trying to install them. So, to make it work you gotta install the newest and beta version of TWRP...
Here you go, as I already said, it's a beta version, I'm not 100% sure if it'll work...
https://build.nethunter.com/test-builds/twrp/oneplus/twrp-3.0.3-1-beta1-oneplus3t.img
Click to expand...
Click to collapse
I installed OSS 4.0 without issues on TWRP 3.0.3.
It sounds more like a bad download to me. Try to redownload the file and flash it again.
RL77LUC said:
I installed OSS 4.0 without issues on TWRP 3.0.3.
It sounds more like a bad download to me. Try to redownload the file and flash it again.
Click to expand...
Click to collapse
Could you install it?
There's a way to flash the 36MB OTA file in TWRP without downloading the full 4.0.1 zip.
I think the OTA fails and gets stuck because of SuperSU or Magisk modifies the boot.img
So, you could try this:
1. Dirty flash the full 4.0 zip
2. Flash 4.0.1
3. Flash SuperSU/Magisk
Sent from my OnePlus 3T using XDA Labs
enzzo28 said:
Could you install it?
There's a way to flash the 36MB OTA file in TWRP without downloading the full 4.0.1 zip.
I think the OTA fails and gets stuck because of SuperSU or Magisk modifies the boot.img
So, you could try this:
1. Dirty flash the full 4.0 zip
2. Flash 4.0.1
3. Flash SuperSU/Magisk
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
TWRP can't install partial OTA updates.
It can install full 4.0 ZIP, but AFAIK, it can't install partial updates.
RL77LUC said:
TWRP can't install partial OTA updates.
It can install full 4.0 ZIP, but AFAIK, it can't install partial updates.
Click to expand...
Click to collapse
Have you tried reading solutions about the last OTA on other XDA's posts?
I've been reading just to spend time and they have found a lot of solutions to some errors with TWRP
Sent from my OnePlus 3T using XDA Labs
enzzo28 said:
Have you tried reading solutions about the last OTA on other XDA's posts?
I've been reading just to spend time and they have found a lot of solutions to some errors with TWRP
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Not really, as I moved to LineageOS.
I just wanted to say that 4.0 worked fine for me , so his error shouldn't be because of that.
RL77LUC said:
Not really, as I moved to LineageOS.
I just wanted to say that 4.0 worked fine for me , so his error shouldn't be because of that.
Click to expand...
Click to collapse
Alright man, it's great that you've found a way to install another rom ✌?
Sent from my OnePlus 3T using XDA Labs
Hey
So my op3t is back in live.
OS is 3.5.4 bootloader unlock.
Twrp is installed but not working (is the beta for 4.0.1)...
First I will working Twrp for nano backup.
Then root on the last official os
What the best way for me I don't will brick my device second time
Gesendet von meinem ONEPLUS A3003 mit Tapatalk

Stuck in bootloop after Xposed install [Magisk][Exposed][Recovery]

Device is stuck in bootloop after I installed Xposed framework module from magisk manager .
I've tried uninstalling magisk , but the uninstall package terminates with error .
Then I flashed stock boot.img , it is booting but I cannot disable the module as magisk isn't installed.
Is there a way I can removed magisk's files / uninstall magisk modules manually from twrp .
Thanks !
(If there is some more relevant place for this thread , please let me know I'll post this there.)
Edit: Fixed it!
you will have to reflash entire system.img + boot.img again with proper wiping.
I never got xposed working on R6 stock.. (i got it magically working on GSI tho) I really want Xposed tho.. :/
TanRayCz said:
I never got xposed working on R6 stock.. (i got it magically working on GSI tho) I really want Xposed tho.. :/
Click to expand...
Click to collapse
which gsi image & twrp you are using? I flashed rr gsi-nosu-vanilla but it keeps bootloop.
abkdmn said:
which gsi image & twrp you are using? I flashed rr gsi-nosu-vanilla but it keeps bootloop.
Click to expand...
Click to collapse
LOS Treble. Call/SMS issues though. LR Team TWRP.
TanRayCz said:
LOS Treble. Call/SMS issues though. LR Team TWRP.
Click to expand...
Click to collapse
i tried flashing the los (15.1 arm A only) gsi image, stuck at bootloop.
how can u succeed?
Michaelw7 said:
i tried flashing the los (15.1 arm A only) gsi image, stuck at bootloop.
how can u succeed?
Click to expand...
Click to collapse
If youll get into bootloop i suggest you trying to wipe system and data partitions from fastboot (important), then flash stock ROM and then flash the GSI. This most of the time worked for me as clear GSI flash. So steps may not be necessary.
TanRayCz said:
If youll get into bootloop i suggest you trying to wipe system and data partitions from fastboot (important), then flash stock ROM and then flash the GSI. This most of the time worked for me as clear GSI flash. So steps may not be necessary.
Click to expand...
Click to collapse
thank u for the help. i will try it
TanRayCz said:
If youll get into bootloop i suggest you trying to wipe system and data partitions from fastboot (important), then flash stock ROM and then flash the GSI. This most of the time worked for me as clear GSI flash. So steps may not be necessary.
Click to expand...
Click to collapse
[official] miui 10 recovery & fastboot ROM
tried wipe system and data partition from fastboot.
and then flash stock rom (from [official] miui 10 recovery & fastboot ROM thread in kernel sub forum), and then instal the gsi image los 15.1.
still bootloop. idk what i did wrong. still no clue
Michaelw7 said:
[official] miui 10 recovery & fastboot ROM
tried wipe system and data partition from fastboot.
and then flash stock rom (from [official] miui 10 recovery & fastboot ROM thread in kernel sub forum), and then instal the gsi image los 15.1.
still bootloop. idk what i did wrong. still no clue
Click to expand...
Click to collapse
Try to flash stock kernel/boot.img or remove Magisk trough uninstaller. This magically helped me one time
TanRayCz said:
Try to flash stock kernel/boot.img or remove Magisk trough uninstaller. This magically helped me one time
Click to expand...
Click to collapse
where can ai get the stock kernel file?
Michaelw7 said:
where can ai get the stock kernel file?
Click to expand...
Click to collapse
You can restore boot.img by installing Magisk uninstaller update ( it's available on Magisk thread I think) , or download a fastboot update for your device to get stock boot.img
Michaelw7 said:
where can ai get the stock kernel file?
Click to expand...
Click to collapse
You can extract it from firmware ZIP
Michaelw7 said:
where can ai get the stock kernel file?
Click to expand...
Click to collapse
go to this site. (not promoting it or something) https://extract.me paste this link [ http://bigota.d.miui.com/V10.0.1.0....FH_20180919.0000.00_8.1_global_794ccbbe18.tgz ] wait a few second then you will see all files from this archive, download what you want from it. It will save you a lot of time to download entire archive. Trust me.

Oxygen OS Pie community build

Hey ppl, just installed it on my 3t, but when I try to install magisk, it says successful in TWRP, but when I boot up into system, it says not rooted. BUT the system partition is full and I can read it, but not write... There is some weird issue. Can anyone follow my problem?:silly:
Overall nice, what OnePlus did
Pic
svandasek said:
Pic
Click to expand...
Click to collapse
Reflashing the Magisk zip solves the issue I suppose. It fixed it for me on some other ROMs too.
Sent from my #FlagshipKiller3T using Tapatalk
DarkSJ1998 said:
Reflashing the Magisk zip solves the issue I suppose. It fixed it for me on some other ROMs too.
Sent from my #FlagshipKiller3T using Tapatalk
Click to expand...
Click to collapse
I was trying, even tried to flash oos in between so that boot.img is stock again... No chance, tried SuperSU , and it says root isn't installed correctly on device.
svandasek said:
I was trying, even tried to flash oos in between so that boot.img is stock again... No chance, tried SuperSU , and it says root isn't installed correctly on device.
Click to expand...
Click to collapse
You probably didn't have magisk manager installed, check it? If that's the case download apk from Magisk thread and installing should deal with the issue.

One UI 2 Beta - Rooting and installing working TWRP after Upgrade

Hi!
After flashing the One UI Beta to your S9/S9+ you can flash the latest TWRP on the same way through Odin jow you did it on Android Pie.
After flashing TWRP you need to wipe data.
Next step is to flash the latest magisk zip 20.1.
Than you have to flash the zip from here. This will modify the TWRP and make it fully working.
No more bootloop after flashing TWRP.
All credits goes to @Alucard for this great tweak.
g960u/u1?
rianplas said:
g960u/u1?
Click to expand...
Click to collapse
No idea on snapdragon.
Its for exynos.
Oel said:
Hi!
After flashing the One UI Beta to your S9/S9+ you can flash the latest TWRP on the same way through Odin jow you did it on Android Pie.
After flashing TWRP you need to wipe data.
Next step is to flash the latest magisk zip 20.1.
Than you have to flash the zip from here. This will modify the TWRP and make it fully working.
No more bootloop after flashing TWRP.
All credits goes to @Alucard for this great tweak.
Click to expand...
Click to collapse
After flashing the One UI Beta need waiting 7 days to enable oem unlock?
andylitias said:
After flashing the One UI Beta need waiting 7 days to enable oem unlock?
Click to expand...
Click to collapse
No problem.here
I had the OEM unlock before i changed to One Beta
Oel said:
No problem.here
I had the OEM unlock before i changed to One Beta
Click to expand...
Click to collapse
already flash zip and got error failed to unmount odm
and bootloop
andylitias said:
already flash zip and got error failed to unmount odm
and bootloop
Click to expand...
Click to collapse
The odm thing is not important.
Wich unit and wich steps you are going?
You deleted data first, than flashing magisk and after this the alucard2 zip?
Oel said:
The odm thing is not important.
Wich unit and wich steps you are going?
You deleted data first, than flashing magisk and after this the alucard2 zip?
Click to expand...
Click to collapse
G960F
already in one ui beta 2 android 10
flash twrp
format data
flash magisk 20.1 and flash alucard
still bootloop
andylitias said:
G960F
already in one ui beta 2 android 10
flash twrp
format data
flash magisk 20.1 and flash alucard
still bootloop
Click to expand...
Click to collapse
Ok, did you try to do download the zip again?
Please try this and flash again.
Wich version of twrp you are on?
Oel said:
Ok, did you try to do download the zip again?
Please try this and flash again.
Wich version of twrp you are on?
Click to expand...
Click to collapse
twrp-3.3.1-0
already download zip and flash again but still bootloop
andylitias said:
twrp-3.3.1-0
already download zip and flash again but still bootloop
Click to expand...
Click to collapse
Please try this older version. It works both on my G960F
twrp-3.3.1-0
already in beta 2android 10
flash twrp
format data
flash magisk 20.1
flash zip
And bootloop from Samsung logo
---------- Post added at 11:48 PM ---------- Previous post was at 11:30 PM ----------
Oel said:
Please try this older version. It works both on my G960F
Click to expand...
Click to collapse
Nope
This is the magisk patched kernel for the 960 Beta.
Flash it through twrp in "boot".
Flash the zip again and boot.
If it doesnt work than go back to twrp and flash the magisk uninstaller zip, than the patched kernel and it should boot.
IMPORTANT!
THE FIRST BOOT AFTER THE MILTI DISABLE ZIP NEEDS BETWEEN 3 TO 5 MINUTES!
https://we.tl/t-mB2vCFl51O
Yes, it works now!
RpRAUC said:
Yes, it works now!
Click to expand...
Click to collapse
method?
andylitias said:
twrp-3.3.1-0
already download zip and flash again but still bootloop
Click to expand...
Click to collapse
RpRAUC said:
Yes, it works now!
Click to expand...
Click to collapse
Great to hear!
What was the problem?
The long time on the first boot?
Oel said:
Great to hear!
What was the problem?
The long time on the first boot?
Click to expand...
Click to collapse
I will try tomorrow
already back to pie again
Thanks
andylitias said:
method?
Click to expand...
Click to collapse
This is the magisk patched kernel for the 960 Beta.
Flash it through twrp in "boot".
Flash the zip again and boot.
This metod works fo me
---------- Post added at 12:27 AM ---------- Previous post was at 12:25 AM ----------
Oel said:
Great to hear!
What was the problem?
The long time on the first boot?
Click to expand...
Click to collapse
2-3 min, then setup menu (account etc)
[email protected] and v2 doesn work,
I don't understand why
Here a better description wich steps you have to go:
Here is a instruction how to install OneUI beta with TWRP and root.
Flash Stock Rom CSK1 (XEU)
Let it boot (Welcome screen)
Flash update.zip (via abd or sd card)
Let it boot (welcome screen)
Flash twrp.tar
Boot in twrp
Format data
Reboot in recovery
Flash multi.disable.samsung
Reboot
Finish setup
Reboot twrp
Flash magisk
Reboot
Install magisk manager apk
Open magisk
Install the update (it ask you when you open magisk manager)
Let it reboot
Finish
Thanks to LONEsnoWolf
RpRAUC said:
2-3 min, then setup menu (account etc)
[email protected] and v2 doesn work,
I don't understand why
Click to expand...
Click to collapse
smartlock working?
cant add google account?

Categories

Resources