Related
THIS DOWNLOAD CENTER IS THE RESULT OF DAYS WORK UPLOADING STUFF. IT TOOK A LOT OF EFFORT TO RESUME ALL THINGS TOGETHER. SO.....E N J O Y
NOTE : use all files with caution. Read threads before use, learn and use them carefully. I am not responsible for damaging/bricking your phone or other related stuff…
NOTE 2 : When having questions : DO ASK THEM IN THE "QUESTION&ANSWERS" forum or THE RELATED THREAD ! THNX !
Now, since I am using this A2017G phone from the first release day on and therefore following all stuff regarding stock rom, root etc. (except custom ROM department) , I thought it would be useful to share all my own files, tools and other stuff that I used since day 1.
There are different threads posting about files for all variant phones together (and not always up to date) and IMO also not bundle some major specific threads for A2017G which are ,again IMO, the most useful since I bought this splendid phone.
Therefore I want this a place for the A2017G model alone and keep it up-to-date where possible.
I do not pretend this will be a one of a kind but definitely sure it will bundle some things together that new users and others can use to (re-)find directly some specific file or thread.
All credits of course goes to those who spend their time to make things work!
I will update stuff if needed.
FACTORY IMAGES DIVISION : A2017G
Since day 1 ZTE released updates/stock factory image files. Most of the files are scattered all over the place or not existing anymore.
Therefore I took ‘some’ :cyclops: time to upload all my ORIGINAL stock files from ZTE otherwise they’re only wasted data on my harddrives.
These files could be useful to go back to whatever factory image you want or extract the necessary data from it.
The files are just renamed. Rename back (f.e. “update.zip”, "recovery.img"...) where necessary or if needed in a particularly thread or flash method :
note : Like i said these files are genuine, original downloads from ZTE. So, if you're not able to update as usual through settings (put file in root of extrernal SD) or via stock recovery (either with update from SD or ADB sideload (putting file in ADB folder on your PC)) or whatever...you're doing something wrong or...you've bad luck. Anyway, try harder :fingers-crossed:
note2 : the zip files are ready to use. There are no zips in zips. So extracting or whatever is not needed.
A2017G-MM-B03 : https://www.androidfilehost.com/?fid=889764386195898861
A2017G-MM-B03 stock recovery : https://www.androidfilehost.com/?fid=889764386195898860
A2017G-MM-B03 boot : https://www.androidfilehost.com/?fid=673368273298958442
A2017G-MM-B06 : https://www.androidfilehost.com/?fid=673368273298954543
A2017G-MM-B08 : https://www.androidfilehost.com/?fid=745425885120731436
A2017G-MM-B08 stock recovery : https://www.androidfilehost.com/?fid=745425885120731415
A2017G-MM-B08 boot : https://www.androidfilehost.com/?fid=817550096634772937
A2017G-MM-B09 : https://www.androidfilehost.com/?fid=673368273298955140
A2017G-MM-B10 : https://www.androidfilehost.com/?fid=817550096634769190
A2017G-MM-B10 stock recovery : https://www.androidfilehost.com/?fid=889764386195899093
A2017G-MM-B10 boot : https://www.androidfilehost.com/?fid=673368273298958443
A2017G-MM-B11 : https://www.androidfilehost.com/?fid=529152257862726439
A2017G-MM-B11 stock recovery : https://www.androidfilehost.com/?fid=889764386195899089
A2017G-MM-B11 boot : https://www.androidfilehost.com/?fid=817550096634772938
A2017G-N-B01 : https://www.androidfilehost.com/?fid=817550096634768963
A2017G-N-B01 stock recovery : https://www.androidfilehost.com/?fid=745425885120725539
A2017G-N-B01 boot : https://www.androidfilehost.com/?fid=889764386195902947
A2017G-N-B02 : https://www.androidfilehost.com/?fid=529152257862727042
A2017G-N-B02 stock recovery : https://www.androidfilehost.com/?fid=673368273298958444
A2017G-N-B02 boot : https://www.androidfilehost.com/?fid=817550096634772939
A2017G-N-FOTA-B01 to B02 : https://www.androidfilehost.com/?fid=529152257862723162
A2017G-N-FOTA-B02 to B04 : https://www.androidfilehost.com/?fid=817550096634768949
A2017G-N-B04 (australian) : https://www.androidfilehost.com/?fid=889764386195899120
(also flashable with trons bootstack+system / IMO the most stable version @ the moment)
According to ZTE the australian version is the same as used for the OTA B04 on german devices and on new sold phones for that region
A2017G-N-B04 stock recovery : https://www.androidfilehost.com/?fid=673368273298958445
A2017G-N-B04 boot : https://www.androidfilehost.com/?fid=889764386195902948
A2017G-N-B05 (spain) : https://www.androidfilehost.com/?fid=889764386195912222
A2017G-N-B05 stock recovery : https://www.androidfilehost.com/?fid=745425885120744960
A2017G-N-B05 boot : https://www.androidfilehost.com/?fid=817550096634782427
A2017G-N-FOTA-B04 to B05 : https://www.androidfilehost.com/?fid=889764386195919032
A2017G-N-B06 (turkey) : https://www.androidfilehost.com/?fid=817550096634795481
A2017G-N-B06 stock recovery : https://www.androidfilehost.com/?fid=889764386195927517
A2017G-N-B06 boot : https://www.androidfilehost.com/?fid=961840155545593447
A2017G-N-FOTA-B05 to B08 : https://androidfilehost.com/?fid=962021903579488106
A2017G-N-B08 (germany) : https://androidfilehost.com/?fid=673791459329058532
A2017G-N-B08 boot : https://androidfilehost.com/?fid=962021903579488691
A2017G-N-B08 stock recovery : https://androidfilehost.com/?fid=817906626617942655
A2017G-N-B09 (sweden) : https://androidfilehost.com/?fid=673791459329072549
A2017G-N-B09 boot : https://androidfilehost.com/?fid=817906626617951591
A2017G-N-B09 stock recovery : https://androidfilehost.com/?fid=745849072291693720
A2017G-N-FOTA-B08 to B10 : https://androidfilehost.com/?fid=962187416754466305
A2017G-N-FOTA-B09 to B10 : https://androidfilehost.com/?fid=890129502657590984
A2017G-N-B10 : https://androidfilehost.com/?fid=746010030569960734
A2017G-N-B10 boot : https://androidfilehost.com/?fid=818070582850499639
A2017G-N-B10 stock recovery : https://androidfilehost.com/?fid=962187416754467268
A2017G-N-FOTA-B10 to B12 : https://androidfilehost.com/?fid=1322778262903993524
A2017G-N-B12 : https://dl1.ztems.com/zxmdmp/downlo...K/ZTE/ZTE A2017G/452783/fota_B15_MR_B17_MR.up
A2017G-N-B12 boot : https://www.androidfilehost.com/?fid=1322778262904001038
A2017G-N-B12 stock recovery : https://www.androidfilehost.com/?fid=1322778262904001082
A2017G-O-B02 : https://forum.xda-developers.com/showpost.php?p=78045733&postcount=35
A2017G-O-B02 boot : https://androidfilehost.com/?fid=11410932744536994029
A2017G-O-B02 stock recovery : https://androidfilehost.com/?fid=11410932744536994031
A2017G-O-B03 : http://download.ztedevices.com/support/product/548/201812051059748/sd/20181212113602035.zip
A2017G-O-B03 boot : https://androidfilehost.com/?fid=11410963190603885505
A2017G-O-B03 stock recovery : https://androidfilehost.com/?fid=11410963190603883442
TWRP flashable Bootstack/Stocksystem Images
Previous version ( MM-B09 / N-B01 / N-B02 / N-B04 ) : https://forum.xda-developers.com/axon-7/development/stock-rom-a2017g-twrp-flashable-images-t3599069
A2017G-N-B05-bootstack : https://www.androidfilehost.com/?fid=889764386195912453
A2017G-N-B05-stocksystem : https://www.androidfilehost.com/?fid=961840155545578497
(Bootstack/Stocksystem (based on B05(spain)/ remind to flash SU2.79 after flashed both files !)
A2017G-N-B06-bootstack : https://www.androidfilehost.com/?fid=673368273298981646
A2017G-N-B06-stocksystem : https://www.androidfilehost.com/?fid=817550096634795513
(Bootstack/Stocksystem (based on B06(turkey)/ remind to flash SU2.79 after flashed both files !)
A2017G-N-B08-bootstack : https://androidfilehost.com/?fid=745849072291684863
A2017G-N-B08-stocksystem : https://androidfilehost.com/?fid=962021903579488675
(Bootstack/Stocksystem (based on B08(germany)/ remind to flash SU2.79 after flashed both files !)
A2017G-N-B09-bootstack : https://androidfilehost.com/?fid=673791459329066133
A2017G-N-B09-stocksystem : https://androidfilehost.com/?fid=962021903579497339
(Bootstack/Stocksystem (based on B09(??)/ remind to flash SU2.79 after flashed both files !)
A2017G-N-B10-bootstack : https://androidfilehost.com/?fid=673956719939825932
A2017G-N-B10-stocksystem : https://androidfilehost.com/?fid=890129502657589263
(Bootstack/Stocksystem (based on B10/ remind to flash SU2.79/magisk after flashed both files !)
A2017G-N-B10-FULL EDL : https://androidfilehost.com/?fid=746010030569960045
A2017G-N-B12-bootstack : https://androidfilehost.com/?fid=1322778262903993157
A2017G-N-B12-stocksystem : https://androidfilehost.com/?fid=1322778262903993549
(Bootstack/Stocksystem (based on B12/ remind to flash SU2.79/magisk after flashed both files !)
A2017G-N-B12-FULL EDL : https://androidfilehost.com/?fid=1322778262903993129
A2017G-O-B02-bootstack : https://androidfilehost.com/?fid=11410932744536994154
A2017G-O-B02-stocksystem : https://androidfilehost.com/?fid=11410932744536994370
A2017G-O-B02-FULL EDL : https://androidfilehost.com/?fid=11410932744536993760
A2017G-O-B03-bootstack : https://androidfilehost.com/?fid=11410963190603885509
A2017G-O-B03-stocksystem : https://androidfilehost.com/?fid=11410963190603892464
A2017G-O-B03-FULL EDL : https://androidfilehost.com/?fid=11410963190603874726
ROOT DIVISION : A2017G
IMO these are the most used recurring files and threads to start from scratch and use to root, unlock your phone and play around with :
Minimal ADB FASTBOOT tool : https://www.androidfilehost.com/?fid=529152257862726185
Axon7tool : https://www.androidfilehost.com/?fid=673368273298954280 thnx @tennear
Axon7toolkit v1.2.0 : https://www.androidfilehost.com/?fid=673368273298961049 thnx @bkores
Zadig driver tool v2.2 : https://www.androidfilehost.com/?fid=529152257862726183
Zadig driver tool v2.3 : https://www.androidfilehost.com/?fid=817550096634786647
SU2.65 (MM) : https://www.androidfilehost.com/?fid=529152257862726221
SU2.79 (N) : https://www.androidfilehost.com/?fid=529152257862726223
SU2.81 (N) : https://www.androidfilehost.com/?fid=745425885120734872
SU2.82 (N) : https://www.androidfilehost.com/?fid=961840155545568721
TWRP : Most important, i repeat most important :
!!! do NOT use TWRP 3.0.2.2 version to backup/restore - you will be most unhappy with your BRICKED phone (read threads about that) !!!
!!! so do update to lastest version TWRP 3.1.0.0 or newer as soon a you can !!!
OFFICIAL
TWRP 3.0.2.2 (tenfar) : https://www.androidfilehost.com/?fid=529152257862720446
TWRP 3.1.0.0 : https://www.androidfilehost.com/?fid=529152257862720448
TWRP 3.1.1.0 : https://www.androidfilehost.com/?fid=889764386195900705
(TWRP 3.2.0.0 : https://androidfilehost.com/?fid=889964283620771093)
TWRP 3.2.1.0 : https://androidfilehost.com/?fid=673791459329066789
TWRP 3.2.2.0 : https://androidfilehost.com/?fid=5862345805528041048
TWRP 3.2.3.0 : https://androidfilehost.com/?fid=5862345805528069068
TWRP 3.3.0.0 : https://androidfilehost.com/?fid=1395089523397944924
CUSTOM thnx @NFound
TWRP 3.2.1.5 : https://androidfilehost.com/?fid=746010030569951007
TWRP 3.2.1.6 : https://androidfilehost.com/?fid=890129502657585390
TWRP 3.2.1.7 : https://androidfilehost.com/?fid=673956719939822011
TWRP 3.2.1.8 : https://androidfilehost.com/?fid=962339331458997156
MiFlash tool : https://www.androidfilehost.com/?fid=673368273298954241
EDL TOOL : https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759 thnx @djkuz
THE 1 MINUTE ULTIMATE DFU UNBRICK TOOL (no more opening of device/no EDL cable needed anymore) : https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229
MISCELLANEOUS :
1. JoJoc System Tuning Battery Tweak by @nfsmw_gr :
V3.2 :
*script : https://forum.xda-developers.com/axon-7/how-to/tweak-jojoc-tuning-battery-focused-t3704831
*Magiskmodule V3.2
*SuperSU zip
V2.1 :
*script : https://forum.xda-developers.com/axon-7/how-to/tweak-jojoc-tuning-battery-focused-t3704831
*Magiskmodule V2.1
*SuperSU zip
2. Lockscreen PIN, Pattern & Password remover : https://androidfilehost.com/?fid=818222786056030640
3. Universal Bootloader B15 (7.1.1) : https://androidfilehost.com/?fid=673368273298930589 thnx @Unjustified Dev
4. Remove Bootloader Unlock Warning : https://androidfilehost.com/?fid=745849072291698596
info : https://forum.xda-developers.com/axon-7/how-to/guide-remove-unlocked-bootloader-screen-t3727493
SOME THREADS to ROOT and UPDATE A2017G :
Root,unlockBL…imo the place to be ! thnx @Controllerboy
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
TWRP flashable bootstack/stocksystems thnx @tron1
https://forum.xda-developers.com/axon-7/development/stock-rom-a2017g-twrp-flashable-images-t3599069
Root, fastboot, twrp after Nougat update thnx @Choose an username...
https://forum.xda-developers.com/axon-7/how-to/guide-reinstall-twrp-root-update-to-t3578552
....
ON REQUEST :
1. MODEMS : by @Choose an username... : modem flasher for N-B01, N-B02 and N-B04 thnx @sToRm1nG
https://www.androidfilehost.com/?w=files&flid=172381
As a matter of fact the N-B02, N-B04 and N-B05 are the same.
So different nougat modems are :
N-B01 : https://www.androidfilehost.com/?fid=745425885120724885
N-B02,4 and 5 : https://www.androidfilehost.com/?fid=961840155545591899
N-B06 : basicly the same as N-B02,4 ,5 but a very small difference in size. Therefore the upload : https://www.androidfilehost.com/?fid=817550096634795810
N-B08 : https://androidfilehost.com/?fid=889964283620762049
N-B09 : https://androidfilehost.com/?fid=962021903579497257
N-B10 : https://androidfilehost.com/?fid=890129502657589880
N-B12 : https://www.androidfilehost.com/?fid=1322778262904001054
Oreo Modem:
O-B02 : https://androidfilehost.com/?fid=11410932744536994030
O-B03 : https://androidfilehost.com/?fid=11410963190603883450
2. Initial MM-B03 system stock sounds : https://androidfilehost.com/?fid=889964283620762508 ( thnx @Kenziner )
(old upload version)https://www.androidfilehost.com/?fid=673368273298967887
3. LOS14 sounds : https://androidfilehost.com/?fid=817906626617942936
If you feel the need for a specific file to post here, just PM me or comment. Thnx !
ENJOY !
ps : report when a link is down
This thread should be pinned, as there are a lot of important links to download, for our device. Thanks for this topic!
raystef66 said:
TWRP : Most important :
TWRP 3.0.2.2 (tenfar) : https://www.androidfilehost.com/?fid=529152257862720446
TWRP 3.1.0.0 : https://www.androidfilehost.com/?fid=529152257862720448
TWRP : Useful :
TWRP 3.0.3.0 : https://www.androidfilehost.com/?fid=817550096634769206
TWRP 3.0.3.1 : https://www.androidfilehost.com/?fid=529152257862726447
TWRP 3.0.4.0 : https://www.androidfilehost.com/?fid=889764386195899070
Click to expand...
Click to collapse
I think you should only leave TWRP 3.1 here, or at least leave 3.1.0-0 and 3.0.2-2 by tenfar and a huge flashy disclaimer that says not to backup anything, and update it as fast as possible
Nice thread anyways
Strange but mine (A2017G B02) do not want to update automatically via system updater. It do not want to see B02 to B04 file. Yes, I renamed it do update.zip also I was trying A2017GV1.2.0B04.zip and also I was trying all SD location eg. FOTA folder and update folder - doesn't work.
PS. I just pointed FOTA and update folders on ss.
MrMD69 said:
Strange but mine (A2017G B02) do not want to update automatically via system updater. It do not want to see B02 to B04 file. Yes, I renamed it do update.zip also I was trying A2017GV1.2.0B04.zip and also I was trying all SD location eg. FOTA folder and update folder - doesn't work.
PS. I just pointed FOTA and update folders on ss.
Click to expand...
Click to collapse
You have to throw the update to the root of the storage. No idea if it doesn't work...
One more thing - I assume you checked it wasn't compressed again?? As in, when you open the ZIP, does a bunch of random crap appear or one ZIP inside? If there's only a ZIP then decompress it and try again
MrMD69 said:
Strange but mine (A2017G B02) do not want to update automatically via system updater. It do not want to see B02 to B04 file. Yes, I renamed it do update.zip also I was trying A2017GV1.2.0B04.zip and also I was trying all SD location eg. FOTA folder and update folder - doesn't work.
PS. I just pointed FOTA and update folders on ss.
Click to expand...
Click to collapse
All files are ready to use. There are no zips in zips.
If your phone is stock you can use the B02 to B04 fota. It should work as it is an original. Perhaps wipe cache first in stock recovery.
MrMD69 said:
Strange but mine (A2017G B02) do not want to update automatically via system updater. It do not want to see B02 to B04 file. Yes, I renamed it do update.zip also I was trying A2017GV1.2.0B04.zip and also I was trying all SD location eg. FOTA folder and update folder - doesn't work.
PS. I just pointed FOTA and update folders on ss.
Click to expand...
Click to collapse
Experienced the same issue. If you can't get the system updater to detect it, just install via the stock recovery. That worked perfectly for me.
1. It isn't compressed that's a ready to go zip.
2. Was trying all possible location especially few times root location of my SD card.
3. When I trying to update via stock recovery after clicking "apply SD update" it said "you are unable to apply SD update" - that one I also was trying with different locations.
When I was updating to B02 everything worked at the first try idk what happened to my phone
EDT. Wipe cache do not resolve the trouble. Also factory reset.
MrMD69 said:
1. It isn't compressed that's a ready to go zip.
2. Was trying all possible location especially few times root location of my SD card.
3. When I trying to update via stock recovery after clicking "apply SD update" it said "you are unable to apply SD update" - that one I also was trying with different locations.
When I was updating to B02 everything worked at the first try idk what happened to my phone
EDT. Wipe cache do not resolve the trouble. Also factory reset.
Click to expand...
Click to collapse
You can try also adb sideload in recovery. Put the update.zip in the adb folder and try with the specific adb command : adb sideload update.zip
I did that once.
You can also rename the .zip to .up in all cases and try again.
MrMD69 said:
1. It isn't compressed that's a ready to go zip.
2. Was trying all possible location especially few times root location of my SD card.
3. When I trying to update via stock recovery after clicking "apply SD update" it said "you are unable to apply SD update" - that one I also was trying with different locations.
When I was updating to B02 everything worked at the first try idk what happened to my phone
EDT. Wipe cache do not resolve the trouble. Also factory reset.
Click to expand...
Click to collapse
Ha. Experienced that too ?. All you gotta do is go into settings > advanced settings > developer options and then enable OEM unlocking. Then you should have no issues in recovery.
All factory images are uploaded and ready to use :cyclops:
Managed it to update via ADB - works flawlessly - thx for helping me !
@ raystef66
Thank you for your useful post. Just to mention that TWRP just has newer version 3.1.1-0 :
https://eu.dl.twrp.me/ailsa_ii/
dnlilas said:
@ raystef66
Thank you for your useful post. Just to mention that TWRP just has newer version 3.1.1-0 :
https://eu.dl.twrp.me/ailsa_ii/
Click to expand...
Click to collapse
Thnx. Good find ! Updated thread with download link:good:
Just flash img in your TWRP
Had contact with ZTE Germany and they confirmed me today that the Australian Full B04 Nougat zip (20170505161441337.zip) is also the firmware which is distributed on new sold phones in Germany and also the OTA B04 update is based on it. So no differences as ZTE said.
Uploaded the lastest flashable SuperSU 2.81 zip
Flashed it without any issues
Damn, can someone do this for the U.S. version, I'm looking for the B29 mm official zip from ZTE's website which isn't there anymore.
Latest SuperSU 2.82
For those who feel the urgent need to update their SuperSU (again )
version 2.82 (27.05.2017) available:good:tested OK:good:
@raystef66
I suggest you to add download link to stock boot.img to all places where currently you mention stock recovery download,
for coherent and practical reasons. recovery.img and boot.img could of course be extracted from ROM zip,
but it is not easy to download the ROM (about 2.4GB) to just get recovery or boot image.
Stock boot.img are important to install SuperSU or Magisk since the utilities need to patch it.
Also to add recovery.img + boot.img for A2017G-N-B02 and A2017G-N-B04:
A2017G-N-B02 : A2017GV1.2.0B02_boot.img, A2017GV1.2.0B02_recovery.img
A2017G-N-B04 : A2017GV1.2.0B04_boot.img, A2017GV1.2.0B04_recovery.img
Thank you.
dnlilas said:
@raystef66
I suggest you to add download link to stock boot.img to all places where currently you mention stock recovery download,
for coherent and practical reasons. recovery.img and boot.img could of course be extracted from ROM zip,
but it is not easy to download the ROM (about 2.4GB) to just get recovery or boot image.
Stock boot.img are important to install SuperSU or Magisk since the utilities need to patch it.
Also to add recovery.img + boot.img for A2017G-N-B02 and A2017G-N-B04:
A2017G-N-B02 : A2017GV1.2.0B02_boot.img, A2017GV1.2.0B02_recovery.img
A2017G-N-B04 : A2017GV1.2.0B04_boot.img, A2017GV1.2.0B04_recovery.img
Thank you.
Click to expand...
Click to collapse
As most of the time recovery will do the trick i uploaded them earlier. Rest could be extracted out of rom zip.
But as i do have them all, i will look into it on your request and add them where needed. Thnx!
EDIT : UPDATED !
Ulefone Armor X6 - mt6580, 720x1280 5-inch, 2/16 ram/rom Android 9. There is a full rom, ulefone site (Support > Software Download). I use EU version.
Rom is with "-sign.img"s, system/build.prop: "ro.treble.enabled=true", "ro.expect.recovery_id=0xb4248...", boot-sign.img without ramdisk.
Used tools: Linux - IMG-SIGN Extractor (signimg2img), simg2img/img2simg, mount, SP Flash Tool, Carliv Image Kitchen, Windows - Miracle.
Tests for modification:
Fastoboot flashing unlock - ok.
SPFT - before connection - hold volume down - is possible to flash full rom. Single img - error.
Patching recovery-sign.img in magisk, recovery mode. Fastboot flash recovery magisk_patched.img = bootloop.
System-sign.img - unsign, unsparse, mount, remove bootanimation.zip and apps (Duo, YTMusic), edit build.prop: "ro.treble.enabled=false", remove "ro.expect.recovery_id=0xb4248...". Umount, sparse, flash system via fastboot. Fastboot say "ok". After start - stil stock system, without modification.
For the upper rom exist update ~400mb. Update, dump with Miracle - img's are unsigned.
System.img - unsparse, mount, remove bootanimation.zip and apps (Duo, YTMusic), edit build.prop: "ro.treble.enabled=false", remove "ro.expect.recovery_id=0xb4248...". Umount, sparse, flash system via Miracle = bootloop.
Also, I make a few ports of TWRP via Carliv Image Kitchen. Always bootloop (I never had trouble with a previous ports, for other phones, especially for this cpu)
Any other ideas? Or links to the right treads. This is my first rom with treble / "-sign.img"s.
Root
Tested on "GQ3085DH1_KSP2E_Ulefone_EEA_20200312_V01（Eu）" (Baseband version MOLY.WR8.W1449.MD.WG.MP.V237.4,2019/10/28 09:26, Kernel version 4.9.117 #2 Mon Oct 28 09:48:24 CST 2019)
Unlocking bootloader and disable verification (fastboot - min. version 1.8, vbmeta.img from stock rom):
fastboot flashing unlock
(volume up)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot
On Android - Mtk-easy-su-v1.1.3.apk & MagiskManager-v7.5.1.apk.
Mtk-easy-su:
1. Run on boot
2. Magisk.v20.4.zip (assets-r22) - install
3. "Activate bootless root"
Restart phone. After start, wait to see "Success" on screen (bottom). Magisk work.
After root, if adb is needed:
adb shell
su
mount -o rw,remount /
Do you have made any progress?
Im sitting here on my armor x6 and have the same problems.
ahaff said:
Ulefone Armor X6 - mt6580, 720x1280 5-inch, 2/16 ram/rom Android 9. There is a full rom, ulefone site (Support > Software Download). I use EU version.
Rom is with "-sign.img"s, system/build.prop: "ro.treble.enabled=true", "ro.expect.recovery_id=0xb4248...", boot-sign.img without ramdisk.
Used tools: Linux - IMG-SIGN Extractor (signimg2img), simg2img/img2simg, mount, SP Flash Tool, Carliv Image Kitchen, Windows - Miracle.
Tests for modification:
Fastoboot flashing unlock - ok.
SPFT - before connection - hold volume down - is possible to flash full rom. Single img - error.
Patching recovery-sign.img in magisk, recovery mode. Fastboot flash recovery magisk_patched.img = bootloop.
System-sign.img - unsign, unsparse, mount, remove bootanimation.zip and apps (Duo, YTMusic), edit build.prop: "ro.treble.enabled=false", remove "ro.expect.recovery_id=0xb4248...". Umount, sparse, flash system via fastboot. Fastboot say "ok". After start - stil stock system, without modification.
For the upper rom exist update ~400mb. Update, dump with Miracle - img's are unsigned.
System.img - unsparse, mount, remove bootanimation.zip and apps (Duo, YTMusic), edit build.prop: "ro.treble.enabled=false", remove "ro.expect.recovery_id=0xb4248...". Umount, sparse, flash system via Miracle = bootloop.
Also, I make a few ports of TWRP via Carliv Image Kitchen. Always bootloop (I never had trouble with a previous ports, for other phones, especially for this cpu)
Any other ideas? Or links to the right treads. This is my first rom with treble / "-sign.img"s.
Click to expand...
Click to collapse
Yo, can you send me the port of TWRP for this phone please?
64-bit Base Package For GSI Redmi 7A
Flashing instructions ?
• Boot to recovery
• Flash given zip file (Downloads section)
• Wipe system
• Flash any arm64 GSI of your choice to system image
• Format data, wipe cache
• Flash gapps, magisk, etc...
• Boot to system, congrats you're on arm64.
Changelog:
- Fixed camera service crashing.
- Gcams can now run on Enforcing mode.
- Swap is disabled by default in favor of ZRAM.
- Fixed more services crashing that just filled up the logcat.
- Changed to Global for better overlay compatibility
- ViperFX now works in Enforcing mode where as before it would be unstable.
- Camera doesn't take as long to launch now.
Old Changes (from previous vendor/post):
• Fix bt audio, cleanup audio configs
• Add exfat fix
• Fix headphones
• Fix video recording
• Enable pseudo-gyro (emulated gyroscope from miui)
Downloads :
Base
mirror link
Bugs ?
• VoLTE doesn't work (fix: https://t.me/Redmi7AUpdates/98)
Things to point out:
- As mentioned on the previous release, Pie and Amber/Erfan based GSIs can't boot on Enforcing mode, in which case the Permissiver v5 zip from #permissiver is necessary.
- The FM Radio fix found in notes doesn't work anymore, use this instead (http://www.mediafire.com/file/wgnysvjo362yuco/FM_Radio-Fix.zip/file) and flash through Magisk.
- If you are having any camera related issues then switch to Permissive mode.
-Fixed some stuff and made a new one.
-Sadly, upgrading directly from the old one isn't possible and formatting data is required, I tried to make it upgradable but with no success.
*Currently using Havoc os 3.8"
And credits to telegram redmi 7a team and for the developers who work so hard for this project I do not own this work
Join here need telegram app on windows and android and dont forget to like my post https://t.me/PineOfficial
just flash permissiver to make wired headphone work
for me blissrom arm64 is smooth with face unlock unless u use android 9 as base firmware to have encryption or else u cant add password
daizu said:
just flash permissiver to make wired headphone work
for me blissrom arm64 is smooth with face unlock unless u use android 9 as base firmware to have encryption or else u cant add password
Click to expand...
Click to collapse
True, use MIUI A9 base to get encryption working on TWRP.
No chance to get this working on MIUI?
iagm12 said:
No chance to get this working on MIUI?
Click to expand...
Click to collapse
theres no way and also memeUI sucks
Custom Roms GSIs are better
edit:
there is new a update bluetooth already fix and other bugs..
iagm12 said:
No chance to get this working on MIUI?
Click to expand...
Click to collapse
You could try to use this on a MIUI GSI ported from the Redmi 8 maybe, but I don't know if it would work completely.
Maybe Erfan's GSI builds? https://mirrors.lolinet.com/firmware/gsi/MIUI/
---------- Post added at 03:24 PM ---------- Previous post was at 03:22 PM ----------
Also, not to nitpick, but my username is different in XDA.
https://forum.xda-developers.com/redmi-7a/how-to/redmi-7a-arm64-kernel-t4134381
I'm the kernel dev.
---------- Post added at 03:29 PM ---------- Previous post was at 03:24 PM ----------
Also, I'm going to try out Ubports if I can. It would be interesing to see if it would work because of the Q vendor.
Great Work, congrats <3
i have ask helios developer (maintainer of helios gsi) to resize the gsi of redmi 8 (redmi 8 has 3.5 gb raw image that cant be flash easy to our phone which has only 3gb)
"Flash any arm64 GSI of your choice to system image" i dont know what is this, but can u give me yours?
all using just twrp to flash?
How did you root your device? Im currently on MIUI 11.0.3 Q and there's no TWRP or any magisk rooting files/guide that is updated.
Good work btw. If you can share your rooting method and TWRP this can be an ALL IN ONE guide. Many thanks!
EDIT: Its working right now, but thing is I cant flash anything from internal storage, it shows weird letters (encrypted). Its Pitch Black Recovery 3.0. How did you solve this?
regularfanb0y said:
EDIT: Its working right now, but thing is I cant flash anything from internal storage, it shows weird letters (encrypted). Its Pitch Black Recovery 3.0. How did you solve this?
Click to expand...
Click to collapse
Had the same situation here on my 7A with TWRP, i also couldn't transfer the files via file Explorer from Windows to the 7A
because of the encryption (the copy and paste window doesn't do anything and disapears after a while).
Solution to this is:
Format Data > Yes
[Warning - outdated - OP has replaced the fw+vendor file 11.0.3 to 11.0.11]
Explaning some stuff about GSI basics
If this GSI stuff is also new to you like it is to me:
When working with GSI it's important to understand that the version which is currently running on your device, lets say V10.2.5 for example,
has the same version of your patched boot image (actually the boot image is build to fit for the currently running version i guess)
In this Thread the Base (11.0.3 Q FW) must have the same Version as the currently running version.
At the beginning i didn't know how this should work out because in all the other GSI Rom guides there is a patched boot image file in use
but if you want to use this Base (11.0.3 Q FW) there is no V11.0.3 GLOBAL patched boot image file to use?, just russia.
(see https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305 link in download section)
but then i read somewhere that the boot img also/always is part of the stock image and then i saw that the actual stock image from c. mi. com homepage is V11.0.3.
the second thing that doesn't made sense to me was: does Base (11.0.3 Q FW) mean you only can run Android 10 on it and why are there "higher versions" like Base (11.0.7 P FW) for the older Android P?
but anyway i had all the needed files to give it a try.
Instructions how to get from some sort of a corrupt status xy --> StockRom
Because i did some testing with Rom's i needed a "starting point" = this means unlocked Bootloader, Stock Rom V11.0.3, recovery installed
This was necessary for me to find out what step causes problems and also to "reset" the boot.img if i used a patched one
So this was my loop i did everytime to get from some sort of a corrupt status "xy" back to "starting point":
Enter Fastboot mode (Vol-Down & Power)
Install Stock Rom "pine_global_images_V11.0.3.0.QCMMIXM_20200717.0000.00_10.0_global" from c .mi .com homepage by using the software "MiFlash 2020.3.14.0"
(if you use MiFlash for the first time go to Driver --> install & wait for weird message.)
(it's important to use the V11.0.3.0. if you want to run the "64-bit Base Package For GSI Redmi 7A")
if your bootloader is unlocked at this moment choose "clean all" at the bottom of MiFlash instead of "clean all and lock".
("clean all" always ends with the error "error: Not catch checkpoint (\$fastboot -s .*lock), flash is not done" but you can ignore this one)
After install Stock Rom is finished let the device boot to system
if you already have a unlocked bootloader and you used "clean all" option you can now shut down the device and then enter Fastboot mode (Vol-Down & Power)
if you used "clean all and lock" with a previous unlocked bootloader you can quickly unlock it again by entering Fastboot mode and using the "Mi Unlock" software for Windows.
if your bootloader was never unlocked before you now have to do the complete process:
enable the developer options, go to "Mi unlock status" and register/LOGIN ON YOUR DEVICE into Mi-Account, install "Mi Unlock" software on PC and then you can unlock it.
anyways, if your bootloader is unlocked - shut down the device and then enter Fastboot mode (Vol-Down & Power)
[not flashing boot.img, already mentioned why not ]
use fastboot to flash vbmeta.img
vbmeta file
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
use fastboot to flash recovery.img
TWRP recovery
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
go to recovery by holding Vol-Up & Power
-->my starting point to testing different settings...
Wipe Dalvik / ART cache, System, Data, Cache.
Format Data > Yes
Do not wipe Internal Storage!
copy the following files to the devices sdcard:
Base (11.0.3 Q FW) - fw_vendor_pine_64bit-rel_11.0.3MI.zip File from download section [Warning - outdated - OP has removed this file]
"lineage-17.1-20200808-UNOFFICIAL-treble_arm64_bvN.img" (thats the one i've used but any arm64 GSI of your choice should work)
link in Download section at: https://forum.xda-developers.com/pr...lopment/gsi-lineageos-17-0-gsi-archs-t4004673
Permissiver v5:
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
FM Radio fix: [EDIT: dont use this because LOS bootscreen will stuck in a flickering loop]
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
use FM-Radio_(GSI).zip instead [EDIT: app doesnt work because of errormessage]
https://forum.xda-developers.com/attachment.php?attachmentid=4937895&d=1580288989
worked for me, thanks @dmitrypershin2015
Flash fw_vendor_pine_64bit-rel_11.0.3MI.zip aka "Base (11.0.3 Q FW)"
Wipe system
Flash any arm64 GSI of your choice to system image
Reboot to Recovery
Flash Magisk (optional) (not tested here)
Flash Permissiver v5
Flash GApps (optional) (not tested here)
If you get 'insufficient space' error, first resize System partition.
Flash FM-Radio_(GSI).zip
Reboot system and enjoy.
As already mentioned the FM Radio fix doesn't work, if you skip it LOS boots perfectly
another bug: No other color of the Notification LED than white
Somewhere in the Forum there is a link to Permissiver v4 instead of v5, cant say if v4 works fine but v5 does
mYXiao said:
I had some troubles getting this running, but finally i made it
If this GSI stuff is also new to you like it is to me:
When working with GSI it's important to understand that the version which is currently running on your device, lets say V10.2.5 for example,
has the same version of your patched boot image (actually the boot image is build to fit for the currently running version i guess)
In this Thread the Base (11.0.3 Q FW) must have the same Version as the currently running version.
At the beginning i didn't know how this should work out because in all the other GSI Rom guides there is a patched boot image file in use
but if you want to use this Base (11.0.3 Q FW) there is no V11.0.3 GLOBAL patched boot image file to use?, just russia.
(see https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305 link in download section)
but then i read somewhere that the boot img also/always is part of the stock image and then i saw that the actual stock image from c. mi. com homepage is V11.0.3.
the second thing that doesn't made sense to me was: does Base (11.0.3 Q FW) mean you only can run Android 10 on it and why are there "higher versions" like Base (11.0.7 P FW) for the older Android P?
but anyway i theoretically had all the files to give it a try.
But i had to flash Stock Rom for many times because i wanted to start from the same starting point so i could find out what step causes the problem
and also to "reset" the boot.img if i had used a patched one
So this was my loop i did everytime to get from some sort of a corrupt status back to "my starting point" = this means unlocked Bootloader, Stock Rom V11.0.3 and recovery installed
[ beginning of loop
Enter Fastboot mode (Vol-Down & Power)
Install Stock Rom "pine_global_images_V11.0.3.0.QCMMIXM_20200717.0000.00_10.0_global" from c .mi .com homepage by using the software "MiFlash 2020.3.14.0"
(if you use MiFlash for the first time go to Driver --> install & wait for weird message.)
(it's important to use the V11.0.3.0. if you want to run the "64-bit Base Package For GSI Redmi 7A")
if your bootloader is unlocked at this moment choose "clean all" at the bottom of MiFlash instead of "clean all and lock".
("clean all" always ends with the error "error: Not catch checkpoint (\$fastboot -s .*lock), flash is not done" but you can ignore this one)
After install Stock Rom is finished let the device boot to system
if you already have a unlocked bootloader and you used "clean all" option you can now shut down the device and then enter Fastboot mode (Vol-Down & Power)
if you used "clean all and lock" with a previous unlocked bootloader you can quickly unlock it again by entering Fastboot mode and using the "Mi Unlock" software for Windows.
if your bootloader was never unlocked before you now have to do the complete process:
enable the developer options, go to "Mi unlock status" and register/LOGIN ON YOUR DEVICE into Mi-Account, install "Mi Unlock" software on PC and then you can unlock it.
anyways, if your bootloader is unlocked - shut down the device and then enter Fastboot mode (Vol-Down & Power)
[not flashing boot.img, already mentioned why not ]
use fastboot to flash vbmeta.img
vbmeta file
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
use fastboot to flash recovery.img
TWRP recovery
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
] end of loop -> my starting point to testing different settings...
go to recovery by holding Vol-Up & Power
Wipe Dalvik / ART cache, System, Data, Cache.
Format Data > Yes
Do not wipe Internal Storage!
copy the following files to the devices sdcard:
Base (11.0.3 Q FW) - fw_vendor_pine_64bit-rel_11.0.3MI.zip File from download section
"lineage-17.1-20200808-UNOFFICIAL-treble_arm64_bvN.img" (thats the one i've used but any arm64 GSI of your choice should work)
link in Download section at: https://forum.xda-developers.com/pr...lopment/gsi-lineageos-17-0-gsi-archs-t4004673
Permissiver v5:
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
FM Radio fix: [EDIT: dont use this because LOS bootscreen will stuck in a flickering loop]
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
use FM-Radio_(GSI).zip instead
https://forum.xda-developers.com/attachment.php?attachmentid=4937895&d=1580288989
worked for me, thanks @dmitrypershin2015
Flash fw_vendor_pine_64bit-rel_11.0.3MI.zip aka "Base (11.0.3 Q FW)"
Wipe system
Flash any arm64 GSI of your choice to system image
Reboot to Recovery
Flash Magisk (optional) (not tested here)
Flash Permissiver v5
Flash GApps (optional) (not tested here)
If you get 'insufficient space' error, first resize System partition.
Flash FM-Radio_(GSI).zip
Reboot system and enjoy.
I found out that the FM Radio fix doesn't work here, if you skip it LOS boots perfectly
Somewhere in the Forum there is a link to Permissiver v4 instead of v5, cant say if v4 works fine but v5 does
Click to expand...
Click to collapse
Whats the FM radio GSI zip for?
List of GSIs I've tried on 11.0.3 64 bit
Boots:
Havoc OS (Camera and Screenrecording bug)
Bliss Q (Camera and Weird cutted corners)
Bootleggers (Camera, Weird cutted corners and Brightness cant adjust)
Evolution X (Camera and Brightness cant adjust)
LOS 17 (Camera)
Dont boot:
N/A
Anyone here have a fix for camera, Brightness, Screenrecording and weird cut corners?
regularfanb0y said:
Whats the FM radio GSI zip for?
Click to expand...
Click to collapse
If i boot LOS 17 without the FM radio GSI zip the default FM Radio App which should be preinstalled isn't. flashing the zip fixed that.
regularfanb0y said:
Anyone here have a fix for camera, Brightness, Screenrecording and weird cut corners?
Click to expand...
Click to collapse
All i can say is that i tested Camera, Weird cutted corners and Brightness and Screenrecording on LOS 17 based on 11.0.3 64 bit . Everything works so far
PS: Can you please edit your quote so only the lines you refer to getting repeated? thx
does it work with the feature ： wireless fm radio？
so you can play sky children of light with this or games 64 bit based?
mYXiao said:
I had some troubles getting this running, but finally i made it
If this GSI stuff is also new to you like it is to me:
When working with GSI it's important to understand that the version which is currently running on your device, lets say V10.2.5 for example,
has the same version of your patched boot image (actually the boot image is build to fit for the currently running version i guess)
In this Thread the Base (11.0.3 Q FW) must have the same Version as the currently running version.
At the beginning i didn't know how this should work out because in all the other GSI Rom guides there is a patched boot image file in use
but if you want to use this Base (11.0.3 Q FW) there is no V11.0.3 GLOBAL patched boot image file to use?, just russia.
(see https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305 link in download section)
but then i read somewhere that the boot img also/always is part of the stock image and then i saw that the actual stock image from c. mi. com homepage is V11.0.3.
the second thing that doesn't made sense to me was: does Base (11.0.3 Q FW) mean you only can run Android 10 on it and why are there "higher versions" like Base (11.0.7 P FW) for the older Android P?
but anyway i theoretically had all the files to give it a try.
But i had to flash Stock Rom for many times because i wanted to start from the same starting point so i could find out what step causes the problem
and also to "reset" the boot.img if i had used a patched one
So this was my loop i did everytime to get from some sort of a corrupt status back to "my starting point" = this means unlocked Bootloader, Stock Rom V11.0.3 and recovery installed
[ beginning of loop
Enter Fastboot mode (Vol-Down & Power)
Install Stock Rom "pine_global_images_V11.0.3.0.QCMMIXM_20200717.0000.00_10.0_global" from c .mi .com homepage by using the software "MiFlash 2020.3.14.0"
(if you use MiFlash for the first time go to Driver --> install & wait for weird message.)
(it's important to use the V11.0.3.0. if you want to run the "64-bit Base Package For GSI Redmi 7A")
if your bootloader is unlocked at this moment choose "clean all" at the bottom of MiFlash instead of "clean all and lock".
("clean all" always ends with the error "error: Not catch checkpoint (\$fastboot -s .*lock), flash is not done" but you can ignore this one)
After install Stock Rom is finished let the device boot to system
if you already have a unlocked bootloader and you used "clean all" option you can now shut down the device and then enter Fastboot mode (Vol-Down & Power)
if you used "clean all and lock" with a previous unlocked bootloader you can quickly unlock it again by entering Fastboot mode and using the "Mi Unlock" software for Windows.
if your bootloader was never unlocked before you now have to do the complete process:
enable the developer options, go to "Mi unlock status" and register/LOGIN ON YOUR DEVICE into Mi-Account, install "Mi Unlock" software on PC and then you can unlock it.
anyways, if your bootloader is unlocked - shut down the device and then enter Fastboot mode (Vol-Down & Power)
[not flashing boot.img, already mentioned why not ]
use fastboot to flash vbmeta.img
vbmeta file
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
use fastboot to flash recovery.img
TWRP recovery
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305] end of loop -> my starting point to testing different settings...
go to recovery by holding Vol-Up & Power
Wipe Dalvik / ART cache, System, Data, Cache.
Format Data > Yes
Do not wipe Internal Storage!
copy the following files to the devices sdcard:
Base (11.0.3 Q FW) - fw_vendor_pine_64bit-rel_11.0.3MI.zip File from download section
"lineage-17.1-20200808-UNOFFICIAL-treble_arm64_bvN.img" (thats the one i've used but any arm64 GSI of your choice should work)
link in Download section at: https://forum.xda-developers.com/pr...lopment/gsi-lineageos-17-0-gsi-archs-t4004673
Permissiver v5:
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
FM Radio fix: [EDIT: dont use this because LOS bootscreen will stuck in a flickering loop]
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
use FM-Radio_(GSI).zip instead
https://forum.xda-developers.com/attachment.php?attachmentid=4937895&d=1580288989
worked for me, thanks @dmitrypershin2015
Flash fw_vendor_pine_64bit-rel_11.0.3MI.zip aka "Base (11.0.3 Q FW)"
Wipe system
Flash any arm64 GSI of your choice to system image
Reboot to Recovery
Flash Magisk (optional) (not tested here)
Flash Permissiver v5
Flash GApps (optional) (not tested here)
If you get 'insufficient space' error, first resize System partition.
Flash FM-Radio_(GSI).zip
Reboot system and enjoy.
I found out that the FM Radio fix doesn't work here, if you skip it LOS boots perfectly
Somewhere in the Forum there is a link to Permissiver v4 instead of v5, cant say if v4 works fine but v5 does
Click to expand...
Click to collapse
I have two redmi 7a phones, and I tried both. The first one worked the first try, but the second one does not let me install the gapps, I get error code 70 don't have enough space, I tried to resize system but I get an error and if I try again it works but when starting the phone it stuck in the logo (I already installed FM radio gsi). I don't understand why that happens
Jak08 said:
so you can play sky children of light with this or games 64 bit based?
Click to expand...
Click to collapse
I would also wish to know this, will this allow arm64 apps to run? this is a new one to me ? didn't know this was even possible
This is my first post of this kind so bear with me, please
Info for Galaxy A8 Star:
CPU : SDM660 ( A only, 64bit )Support Project TrebleSupport System as root
※WARNING※
You will have to have OEM unlocked and this will void your warranty!!!
※also, I'm not responsible for the accident about you bricking your device※Step. 1
First of all, you will need to download two custom recoveries (TWRP, OrangeFox)
OrangeFox: https://forum.xda-developers.com/t/orange-fox-recovery-galaxy-a8-star-sm-g885f.4301055/
TWRP: https://github.com/sabpprook/android_device_samsung_astarqlte (test3 file does not work for me but you can try)
I want to finish it only using TWRP but the only TWRP that was working does NOT support flashing the system.img files
and also Orange Fox recovery has a bug that while in recovery you can't connect with the computer and push the files to the phone
so it was required to use two bootloader
Step. 2
Odin: https://odindownload.com/
I also recommend downloading the stock ROM for backup
1. after downloading the TWRP from the link (for Odin we will use the .tar file)
put your phone into download mode
Code:
adb reboot download
or just turn off the phone and press the power button, volume up, Bixby button at the same time
and use the volume button to boot into download mode
2. after the phone went to the download mode, go to Odin and at the ap section add the TWRP file then flash it
3. press the volume down, power button to turn off the device, and right after that press the power button, volume up, Bixby button at the same time
4. you will now see the TWRP recovery, press wipe, and format data
5. now we will download some files we needed
makemesar.zip: (at the attachment) or you can download it from https://drive.google.com/u/0/uc?export=download&confirm=P1-1&id=1F_f_tL4sEYFx5fa6AnwR0x1tlYhqarcT ( when you unzip it there is the zip file )Permissiver_5.zip: https://androidfilehost.com/?fid=6006931924117940902Disable_Dm-Verity_ForceEncrypt: https://drive.google.com/file/d/166texWJQhR1RgRoXiRSH_M2Q2mAyS2gC/viewCertification_Patch.zip: (at the attachment)Havoc Rom (you can use any rom you want but this is the one that I've managed to work) http://download.havoc-os.com/?dir=arm64-ab (download arm64 ab with gapps)most rooms with AB partition will be supportedMagisk: https://magiskmanager.com/ (download the apk and make it a zip file) - you could need for the phone to get the boot (makemesar will unroot it so don't worry)6. after downloading all the files that we need, we will push the files to our device using
Code:
adb push 'file dir' sdcard
※ also push TWRP .img file and the OrangeFox .img too!!
7. after pushing all the files we need to our phone, press install from the TWRP recovery and press flash from image
and select the Orange Fox .img as a recovery image, and reboot to bootloader
8. now you will boot to the Orange Fox recovery, (locate to data/media to find the files)
at the Orange Fox recovery wipe System, Dalvlk / ART Cache, Cache, Data
9. after wiping now install the os.img file and reboot to the bootloader (before reboot you will see the warning that OS is not installed), go to the menu and mount system, vendor, and install Dm Verity.zip, Permissiver_5.zip, makemesar.zip then reboot to the bootloader again, (now we will not see the OS is not installed) and now install the Certification Patch.zip
10. reboot to the system and you will see the new os setup process (sometimes you have to install the Certification Patch after setup the os )
10-1. if your device keeps going to download mode, reinstall the magisk and then reboot the phone, then it will work.
(after it boots, gently turns off the phone and install makemesar.zip first and install Dm-Verity to unroot) - some of you will be forced to use magisk but doing some wiping or reflashing the system.img sometimes makes the unrooted state work (or flash the stock system.img (extract from the stockrom) and flash the gsi ROM without wiping )
Screenshots: At Below
Currently, MTP does not work but I think this is the problem with the Havoc os, if you use another rom it could work
face unlock, fingerprint unlock works, the camera works.
if I manage to get other ROMs workingI will update the post
also at the first time I have made mine to boot without magisk but while doing again for this post I'm having trouble without magisk, if I found a way that works always I will add that to the post
[UPDATE#2]
you can download the Pixel 3 gsi rom from
(Thanks for Santa Duck providing this information!!!!)
with this files you can install the android 12 gsi rom in a usable state!!
and also ADB is working with this rom
there is still a bootlooping bug so do it with caution
[Update#1]
Today I have managed to install the Android Beta 3.1 [ is beta software and I don't recommend using it as your daily os]
https://sourceforge.net/projects/nippongsi/files/Pixel%20-%20Pixel4a_SBeta3.1%20-%20TBO42ZZ8IF/Pixel4a_SBeta3.1-AB-12-20210727-nippongsi.img.gz/download
you can download the ROM file from Nippon's Sourceforge
every step is the same and you just have to change the rom as this
there's a bug that developer setting crash the settings app and it is working but it does have some lots of bugs, and screen lock is not working but I'll try to fix it and upload the method
if your device get boot looped, press Bixby + power + vol down to boot into download mode and flash the stock AP file using Odin
[I was supposed to edit the upper one but accidentally created as a reply ]
Just go to UPDATE#2
Skuld Norniern said:
Havoc Rom (you can use any rom you want but this is the one that I've managed to work) http://download.havoc-os.com/?dir=arm64-ab (download arm64 ab with gapps)
Click to expand...
Click to collapse
Hey I thought that A8 star is an A-only device. Does flashing A/B roms cause any problems?
thongass000 said:
Hey I thought that A8 star is an A-only device. Does flashing A/B roms cause any problems?
Click to expand...
Click to collapse
thanks for the makemesar.zip we can install the A/B partition roms without any problems on the A only device and for me the A only roms won’t work on my phone
Skuld Norniern said:
thanks for the makemesar.zip we can install the A/B partition roms without any problems on the A only device and for me the A only roms won’t work on my phone
Click to expand...
Click to collapse
Hi I'm back. Do you have any issue with wired audio? I have a A9 2018 (same chipset) and audio still goes through speaker while headphones are plugged in.
If anything in Phh Treble Settings helps you, please tell me. Or if you don't need any settings for wired audio, can you send me a zip file containing any files that have the name "audio_policy" in /vendor/etc? Thanks.
thongass000 said:
Hi I'm back. Do you have any issue with wired audio? I have a A9 2018 (same chipset) and audio still goes through speaker while headphones are plugged in.
If anything in Phh Treble Settings helps you, please tell me. Or if you don't need any settings for wired audio, can you send me a zip file containing any files that have the name "audio_policy" in /vendor/etc? Thanks.
Click to expand...
Click to collapse
Sorry for being late!!
for me, I do have the same issue with wired audio and I have not been able to find a way to fix it yet
if I manage to fix the issue I will fix the main article
Skuld Norniern said:
Skuld Norniern said:
This is my first post of this kind so bear with me, please
Info for Galaxy A8 Star:
CPU : SDM660 ( A only, 64bit )Support Project TrebleSupport System as root
※WARNING※
You will have to have OEM unlocked and this will void your warranty!!!
※also, I'm not responsible for the accident about you bricking your device※Step. 1
First of all, you will need to download two custom recoveries (TWRP, OrangeFox)
OrangeFox: https://forum.xda-developers.com/t/orange-fox-recovery-galaxy-a8-star-sm-g885f.4301055/
TWRP: https://github.com/sabpprook/android_device_samsung_astarqlte (test3 file does not work for me but you can try)
I want to finish it only using TWRP but the only TWRP that was working does NOT support flashing the system.img files
and also Orange Fox recovery has a bug that while in recovery you can't connect with the computer and push the files to the phone
so it was required to use two bootloader
Step. 2
Odin: https://odindownload.com/
I also recommend downloading the stock ROM for backup
1. after downloading the TWRP from the link (for Odin we will use the .tar file)
put your phone into download mode
Code:
adb reboot download
or just turn off the phone and press the power button, volume up, Bixby button at the same time
and use the volume button to boot into download mode
2. after the phone went to the download mode, go to Odin and at the ap section add the TWRP file then flash it
3. press the volume down, power button to turn off the device, and right after that press the power button, volume up, Bixby button at the same time
4. you will now see the TWRP recovery, press wipe, and format data
5. now we will download some files we needed
makemesar.zip: (at the attachment) or you can download it from https://drive.google.com/u/0/uc?export=download&confirm=P1-1&id=1F_f_tL4sEYFx5fa6AnwR0x1tlYhqarcT ( when you unzip it there is the zip file )Permissiver_5.zip: https://androidfilehost.com/?fid=6006931924117940902Disable_Dm-Verity_ForceEncrypt: https://drive.google.com/file/d/166texWJQhR1RgRoXiRSH_M2Q2mAyS2gC/viewCertification_Patch.zip: (at the attachment)Havoc Rom (you can use any rom you want but this is the one that I've managed to work) http://download.havoc-os.com/?dir=arm64-ab (download arm64 ab with gapps)most rooms with AB partition will be supportedMagisk: https://magiskmanager.com/ (download the apk and make it a zip file) - you could need for the phone to get the boot (makemesar will unroot it so don't worry)6. after downloading all the files that we need, we will push the files to our device using
Code:
adb push 'file dir' sdcard
※ also push TWRP .img file and the OrangeFox .img too!!
7. after pushing all the files we need to our phone, press install from the TWRP recovery and press flash from image
and select the Orange Fox .img as a recovery image, and reboot to bootloader
8. now you will boot to the Orange Fox recovery, (locate to data/media to find the files)
at the Orange Fox recovery wipe System, Dalvlk / ART Cache, Cache, Data
9. after wiping now install the os.img file and reboot to the bootloader (before reboot you will see the warning that OS is not installed), go to the menu and mount system, vendor, and install Dm Verity.zip, Permissiver_5.zip, makemesar.zip then reboot to the bootloader again, (now we will not see the OS is not installed) and now install the Certification Patch.zip
10. reboot to the system and you will see the new os setup process (sometimes you have to install the Certification Patch after setup the os )
10-1. if your device keeps going to download mode, reinstall the magisk and then reboot the phone, then it will work.
(after it boots, gently turns off the phone and install makemesar.zip first and install Dm-Verity to unroot) - some of you will be forced to use magisk but doing some wiping or reflashing the system.img sometimes makes the unrooted state work (or flash the stock system.img (extract from the stockrom) and flash the gsi ROM without wiping )
Screenshots: At Below
Currently, MTP does not work but I think this is the problem with the Havoc os, if you use another rom it could work
face unlock, fingerprint unlock works, the camera works.
if I manage to get other ROMs workingI will update the post
also at the first time I have made mine to boot without magisk but while doing again for this post I'm having trouble without magisk, if I found a way that works always I will add that to the post
[UPDATE#2]
you can download the Pixel 3 gsi rom from
(Thanks for Santa Duck providing this information!!!!)
with this files you can install the android 12 gsi rom in a usable state!!
and also ADB is working with this rom
there is still a bootlooping bug so do it with caution
Click to expand...
Click to collapse
Hello sir i can't find havoc os 4.5 in:https://download.havoc-os.com/?dir=arm64-ab
Click to expand...
Click to collapse
After flashing twrp on my sm g885f, cant get into terp,
mine shows volume down + power to restart, not to enter turn off
how can i enter into twrp
Skuld Norniern said:
9. after wiping now install the os.img file and reboot to the bootloader (before reboot you will see the warning that OS is not installed), go to the menu and mount system, vendor, and install Dm Verity.zip, Permissiver_5.zip, makemesar.zip then reboot to the bootloader again, (now we will not see the OS is not installed) and now install the Certification Patch.zip
Click to expand...
Click to collapse
'os.img file' where
, guess i fixed it
when installing Certification_Patch.zip, it shows command error
what i found- this patch is for G885FDXS5CUL1, mine is
G885FDXU5CUG1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Official TWRP 3.6.1-* For Galaxy Note 20 & Note 20 UltraOnly for exynos variants - N980F / N981B / N985F / N986B (Europe - Global, Single/Dual-SIM)
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Kernel Features:
N986BXXU3FVC5 kernel source (OneUI 4.1 / March 2022 sourcecode)
disabled uh/defex/proca/knox/rkp/rooting protection/logging/audit/useless features
Recovery Features:
Android 11 tree
built in full 64 mode
toybox/busybox support
compatible with Android 12.0 and above
Downloads:
Galaxy Note 20 (c1s / N980F / N981B)
Galaxy Note 20 Ultra (c2s / N985F / N986B)
AVB disabled vbmeta
* official TWRP builds are not up yet, you can find latest test builds in post #2, below
Instructions:
Odin (Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .tar file according to your device
Download AVB disabled vbmeta .tar
Open Odin v3.14.1 and place the downloaded TWRP .tar file in AP tab, downloaded vbmeta .tar file in CP tab and click Start - once you press start grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Heimdall (Linux)
Install heimdall & additional required packages:
Code:
sudo apt-get update
sudo apt-get install heimdall-flash android-tools-fastboot android-tools-adb libusb-0.1-4 libusb-1.0-0 libusb-1.0-0-dev
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .img file according to your device
Download AVB disabled vbmeta .img
Open your preferred terminal in linux and type (replace red lines with the path of downloaded img files):
Code:
sudo heimdall flash --RECOVERY /path/to/recovery.img --VBMETA /path/to/vbmeta.img
and press enter - once you press enter grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
TWRP
Download .img file for your device and install from your current TWRP with Install image - browse to image location and select - Recovery
dd (Requires root)
Download .img file for your device, place it in the root of your /sdcard folder, rename it to twrp.img then run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/13100000.ufs/by-name/recovery
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Sources:
Device trees - c1s / c2s
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal9830/tree/android-11.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, geiti94, jesec, dyneteve, ianmacd, testers, donors and anyone else involved in making this possible
As always, if you like what i do, you can always send me some pizza/coffee/drugs/drinks or anything else via paypal.me/corsicanu
Compatibility and changelog:
06.05.2022 - Initial TWRP 3.6.1 release
Compatibility: Android 12 (OneUI 4.0 & 4.1)
Security patch: N/A
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary
Further reading:
Full guide of how to unlock/root your device
Background on Android Verified Boot
Rollback protection
FAQ
Q: Can i use this recovery with other firmware then mentioned in compatibility?
A: Only with same Android version or Rollback protection might kick in and you won't be able to pass the lockscreen.
Q: Where do i get vbmeta.img?
A: From here, download the one you need according to install instructions.
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you flashed multidisabler zip / formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware. If you still don't succeed, post here some details about your device and previous firmware and we might be able to help.
Q: Why do i need to format data partition?
A: Because old firmware encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
Thanks for this. Where is twrp.img for Note 20 Ultra 5G / N986B
Updated first post with official pages from twrp.me, but since the builds are not up yet, i posted latest test builds in post #2.
Regards
Thanks, for this I'll keep for more year Note 20 Ultra. Time to wait or maybe make GSI for Note.
Yaayyyy
I m newbie to note 20 ultra...i want to flash root and twrp... What steps shld i follow.... Currently i m on stock non rooted.. Confused what to flash via odin..
@corsicanu
Many thanks for the latest update mate. It's working perfectly, as everything from you does
corsicanu said:
Compatibility and changelog:
06.05.2022 - Initial TWRP 3.6.1 release
Compatibility: Android 12 (OneUI 4.0 & 4.1)
Security patch: N/A
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary
Further reading:
Full guide of how to unlock/root your device
Background on Android Verified Boot
Rollback protection
Click to expand...
Click to collapse
I notice I have bootloder on my device that I didn't install my self. I'm just a average user and have no clue how this was put on my phone. Also all of my apps are older versions an I'm unable to update them. I need help figuring out what's going on. Anyone please help!!!
@corsicanu
Many thanks for the latest update mate
1. Can I use this TWRP version with any custom ROM (e.g. Dr. Ketan ROM)?
2. Do I have to flash vbmeta.img, even when I have that custom ROM?
3. Is there a twrp.img for N986B that supports Android encryption, since right now encryption is somehow disabled after installing Dr. Ketan ROM: the lockscreen password has no effect and I can access and read all files on all partitions with the TWRP file manager !
monicaONxda said:
1. Can I use this TWRP version with any custom ROM (e.g. Dr. Ketan ROM)?
2. Do I have to flash vbmeta.img, even when I have that custom ROM?
3. Is there a twrp.img for N986B that supports Android encryption, since right now encryption is somehow disabled after installing Dr. Ketan ROM: the lockscreen password has no effect and I can access and read all files on all partitions with the TWRP file manager !
Click to expand...
Click to collapse
1. Yes as long as the rom dev doesn't have other instructions regarding the recovery used (i.e. LineageOs)
2. No, you already have some nulled vbmeta flashed since you are running a custom rom.
3. Nope, since samsung uses proprietary encryption. You can however preserve data encryption in the rom (talk that with the dev of your rom), but this will make it unreadable by twrp in any conditions. Please keep in mind that Samsung fw may not like it and it can trigger a data wipe without warnings.
Regards.
corsicanu said:
1. Yes as long as the rom dev doesn't have other instructions regarding the recovery used (i.e. LineageOs)
2. No, you already have some nulled vbmeta flashed since you are running a custom rom.
3. Nope, since samsung uses proprietary encryption. You can however preserve data encryption in the rom (talk that with the dev of your rom), but this will make it unreadable by twrp in any conditions. Please keep in mind that Samsung fw may not like it and it can trigger a data wipe without warnings.
Regards.
Click to expand...
Click to collapse
Where's 2.8
corsicanu said:
1. Yes as long as the rom dev doesn't have other instructions regarding the recovery used (i.e. LineageOs)
2. No, you already have some nulled vbmeta flashed since you are running a custom rom.
3. Nope, since samsung uses proprietary encryption. You can however preserve data encryption in the rom (talk that with the dev of your rom), but this will make it unreadable by twrp in any conditions. Please keep in mind that Samsung fw may not like it and it can trigger a data wipe without warnings.
Regards.
Click to expand...
Click to collapse
Many Thanks!
Re. 3.: With "fw" you meant FRP? But when I have root I can simply erase FRP and most Knox and other unwanted bloatware apks on /system, /product, /prism etc. ?
Btw. do you know if there is there a possibility to completely remove the Samsung ROM and replace it with a plain Android? You may lose one hardware driver for the "Sasmung Pen" but everthying else should work..?
monicaONxda said:
Many Thanks!
Re. 3.: With "fw" you meant FRP? But when I have root I can simply erase FRP and most Knox and other unwanted bloatware apks on /system, /product, /prism etc. ?
Btw. do you know if there is there a possibility to completely remove the Samsung ROM and replace it with a plain Android? You may lose one hardware driver for the "Sasmung Pen" but everthying else should work..?
Click to expand...
Click to collapse
Fw as in firmware. Regarding plain android - search for AOSP based projects, i'm not aware of the active developement so i can't properly advice you in this matter.
Regards
corsicanu said:
Official TWRP 3.6.1-* For Galaxy Note 20 & Note 20 UltraOnly for exynos variants - N980F / N981B / N985F / N986B (Europe - Global, Single/Dual-SIM)
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Kernel Features:
N986BXXU3FVC5 kernel source (OneUI 4.1 / March 2022 sourcecode)
disabled uh/defex/proca/knox/rkp/rooting protection/logging/audit/useless features
Recovery Features:
Android 11 tree
built in full 64 mode
toybox/busybox support
compatible with Android 12.0 and above
Downloads:
Galaxy Note 20 (c1s / N980F / N981B)
Galaxy Note 20 Ultra (c2s / N985F / N986B)
AVB disabled vbmeta
* official TWRP builds are not up yet, you can find latest test builds in post #2, below
Instructions:
Odin (Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .tar file according to your device
Download AVB disabled vbmeta .tar
Open Odin v3.14.1 and place the downloaded TWRP .tar file in AP tab, downloaded vbmeta .tar file in CP tab and click Start - once you press start grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Heimdall (Linux)
Install heimdall & additional required packages:
Code:
sudo apt-get update
sudo apt-get install heimdall-flash android-tools-fastboot android-tools-adb libusb-0.1-4 libusb-1.0-0 libusb-1.0-0-dev
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .img file according to your device
Download AVB disabled vbmeta .img
Open your preferred terminal in linux and type (replace red lines with the path of downloaded img files):
Code:
sudo heimdall flash --RECOVERY /path/to/recovery.img --VBMETA /path/to/vbmeta.img
and press enter - once you press enter grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
TWRP
Download .img file for your device and install from your current TWRP with Install image - browse to image location and select - Recovery
dd (Requires root)
Download .img file for your device, place it in the root of your /sdcard folder, rename it to twrp.img then run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/13100000.ufs/by-name/recovery
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Sources:
Device trees - c1s / c2s
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal9830/tree/android-11.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, geiti94, jesec, dyneteve, ianmacd, testers, donors and anyone else involved in making this possible
As always, if you like what i do, you can always send me some pizza/coffee/drugs/drinks or anything else via paypal.me/corsicanu
Click to expand...
Click to collapse
i am trying to root my note 20 u device. when all succesfully start from magisk module and twrp, i find the screen flicker for a second every 15 seconds. I'm trying to figure out which app the problem is from. looked in screen recorder and found the problem. apparently from system ui. then start again from the initial step one by one. and the cause of the problem is after installing twrp. I'm on Ui5.1 N986B exyns. i feel twrp has a bug
Now im use back stock recovery and problem has gone
Hi it's been a while since I last install TWRP on SS phone, it got complicated now I have few question, can you help answering?
Open Odin v3.14.1 and place the downloaded TWRP .tar file in AP tab, downloaded vbmeta .tar file in CP tab and click Start - once you press start grab the phone and press vol up + power to force it boot straight in TWRP after flashing
Click to expand...
Click to collapse
- For this, do I have to press the key combo 1 time only after clicking Start Odin or I have to hold till the progress done?
2.
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Click to expand...
Click to collapse
- I never install TWRP on my phone, do I have to follow this step?
-If yes, do I have to install that file right after TWRP first boot (when odin completed flashing)
And finally, does it support android 13?
Thank you so much