[RECOVERY][UNOFFICIAL]PitchBlackRecoveryProject 3.0.0 [m30lte] - Samsung Galaxy M30 ROMs, Kernels, Recoveries, & Ot

I would like to thank PBRP, Teamwin for their amazing work!
As usual, I am not responsible for damage to your device, you, the user is choosing to make these modifications.
Your device's warranty is VOID if this procedure is followed, Proceed at your own caution!
With the new update of Android 10 for our device SM-M305[F] / M305[M], Samsung reimplemented RMM and called it KG(KnoxGuard), there is confusion in the device community on how to install TWRP and root device.
Follow these updated instructions to get PBRP working with Latest Stock Firmware.
This thread will be updated regularly.
STRONGLY ADVICE TO BACKUP DATA.
Steps to get PBRP working with stock firmware
First of all flash completely stock firmware, you can always root with Magisk later.
If you are rooted and have PBRP installed already and you are not on Latest Firmware mentioned above then flash latest firmware.
Select BL, AP, CP, CSC (Use HOME_CSC).
Never only flash AP, will cause your /data to shrink.
Once you're updated to latest firmware mentioned above, make sure you unlock your bootloader.
Go into Settings>Software Info>Tap build number seven times.
Go into Settings>Developer Options>OEM Unlock & enable it.
It will prompt you with password/pin confirming to unlock bootloader. Device will reboot and wipe itself.
Setup device once it reboots and again enable developer options and see OEM unlock to be enabled and togglable.
Next enable USB debugging in Settings>Developer Options>USB Debugging.
Open up ADB/FASTBOOT Utility on your computer and connect your device with USB C cable.
Type in following commands without the quotations.
1."adb reboot download" ; reboots your device into Download mode, can flash device via Odin Downloader(Windows) or Heimdall Utility(Linux)
2.Download the attached PBRP.tar if you're using Odin or PBRP.img if you're using Heimdall to flash.
3.Flash the TWRP recovery by
ODIN:-
Clicking AP in Odin and make sure the Repartition and Auto Reboot boxes are UNTICKED/NOT SELECTED.
Click Start at bottom.
Heimdall:-
Open up a terminal window in the directory where twrp.img is downloaded.
Type in heimdall flash --RECOVERY pbrp.img --no-reboot
4.Once flash is complete, press Volume Down+Power Button to shutdown and as soon as screen is black IMMEDIATELY PRESS AND HOLD VOLUME UP+POWER Button and let go of Power button when you see samsung logo, continue holding Volume Up until device boots into TWRP.
5.Once device boots into PBRP, swipe to allow modifications and then Click Wipe>Format Data>type in "yes". This will format everything and reset the device.
6.Go into Wipe>Advanced Wipe>Tick only Cache and swipe to wipe it.
7.Reboot back into recovery by Reboot>Recovery>Do not Install.
8.Once rebooted back into PBRP, transfer the attached zip to phone Internal or SDcard, DO NOT RENAME THE ZIP.
9.Flash the zip by, Install > Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip, swipe to flash it.
10.Wipe cache and dalvik cache, reboot into system by, Reboot > System > Do not install.
11.Device will boot into Android, wait patiently for about 15mins.
12.Once device boots, setup as usual, you will need internet.
13.Voila! You have successfully installed PBRP alongside Stock firmware.
Thanks to @MiyamuraNEET for his persistent testing and timely directions that helped me to bring you this guide.
Thanks to @SahilSonar for bringing TWRP to our device initially
Thanks to @Akhil99 (me) for fixing MTP/ADB in TWRP recovery and bringing you this guide.
HIT THANKS IF WE HELPED YOU.
Downloads:
PBRP:
1. https://www.mediafire.com/file/gtjj6p0ou3hikz9/PBRP-m30lte-3.0.0-20201222-1227-UNOFFICIAL.img/file
2. https://www.mediafire.com/file/wi9v33cr8mkjyay/PBRP-m30lte-3.0.0-20201222-1227-UNOFFICIAL.zip/file
Disable DM_Verity_ForceEncrypt : https://androidfilehost.com/?fid=8889791610682882483
XDAevDB Information
[RECOVERY][UNOFFICIAL]PitchBlackRecoveryProject 3.0.0 [m30lte], Tool/Utility for the Samsung Galaxy M30
Contributors
Akhil99
Source Code: https://github.com/akhil1999/pbrp_device_samsung_m30lte
Version Information
Status: Stable
Stable Release Date: 2020-12-22
Created 2020-12-22
Last Updated 2020-12-22

awesome!

Only dev constantly releasing new to builds/mods to give us great experience,
Appreciate you bro,

Akhil 99 said:
Only dev constantly releasing new to builds/mods to give us great experience,
Appreciate you bro,
Click to expand...
Click to collapse
Thanks for your kind words. A new Port is incoming watch out for that!

Akhil99 said:
Thanks for your kind words. A new Port is incoming watch out for that!
Click to expand...
Click to collapse
It's me Zan,
A51 port tester...

hi, does this work with September 2021 patch.?
I have rooted my phone and interested to replace this with already flashed twrp since someone said PBRP has disable dm-verity feature?

Related

[GUIDE] Unlock Bootloader without wiping data after CM11s 30O

This is what I have done this afternoon.
Use at your own risk, I'm not responsible for any data losing.
Environment: Oneplus One with stock CM11s XNPH30O
Steps:
1. Apply cm-11.0-XNPH25R-bacon-signed.zip from stock recovery.
2. DO NOT BOOT TO OS when update is finished. After updated, press power button until screen off.
3. Boot to fastboot mode by holding 'Power' button & 'Vol UP(+)'.
4. In fastboot mode, boot to custom recovery by
Code:
fastboot boot openrecovery-twrp-2.7.1.1-bacon.img
http://techerrata.com/browse/twrp2/bacon
5. Make a nandroid backup for data partition. (Optional)
6. Sideload OnePlusOne-BootUnlocker.zip http://forum.xda-developers.com/showpost.php?p=54251992&postcount=1
7. Reboot to bootloader(fastboot mode)
8. Extract cm-11.0-XNPH30O-bacon-signed-fastboot.zip and execute 'flash-radio.sh' to update radio and other binaries.
9. Flash 30O system partition only by
Code:
fastboot flash system system.img
(Don't flash userdata.img or userdata_64G.img or you'll lose all your data.)
10. Reboot. The Bootloader is unlocked.
Sorry for my bad english.
Sick man, gonna try this when i get home
I am running on 33R will this work ???
Or connect to PC.. Adb backup, root, then adb restore
Cool write-up! I re-wrote the guide for use over on the OnePlus forums: https://forums.oneplus.net/threads/...ck-the-bootloader-without-losing-data.103642/
ifg said:
This is what I have done this afternoon.
Use at your own risk, I'm not responsible for any data losing.
Environment: Oneplus One with stock CM11s XNPH30O
Steps:
1. Apply cm-11.0-XNPH25R-bacon-signed.zip from stock recovery.
2. DO NOT BOOT TO OS when update is finished. After updated, press power button until screen off.
3. Boot to fastboot mode by holding 'Power' button & 'Vol UP(+)'.
4. In fastboot mode, boot to custom recovery by
Code:
fastboot boot openrecovery-twrp-2.7.1.1-bacon.img
http://techerrata.com/browse/twrp2/bacon
5. Make a nandroid backup for data partition. (Optional)
6. Sideload OnePlusOne-BootUnlocker.zip http://forum.xda-developers.com/showpost.php?p=54251992&postcount=1
7. Reboot to bootloader(fastboot mode)
8. Extract cm-11.0-XNPH30O-bacon-signed-fastboot.zip and execute 'flash-radio.sh' to update radio and other binaries.
9. Flash 30O system partition only by
Code:
fastboot flash system system.img
(Don't flash userdata.img or userdata_64G.img or you'll lose all your data.)
10. Reboot. The Bootloader is unlocked.
Sorry for my bad english.
Click to expand...
Click to collapse
Big thanks for this guide. You saved my life. And thanks also to developers for this MOD :good:
---------- Post added at 04:11 PM ---------- Previous post was at 04:05 PM ----------
Dibbyo123 said:
I am running on 33R will this work ???
Click to expand...
Click to collapse
Be sure to read the steps.
philicibine said:
Or connect to PC.. Adb backup, root, then adb restore
Click to expand...
Click to collapse
How would this be done by steps? I'm somewhat familiar with adb {I have the SDK installed and use it for fastboot) but coming from rooting and modding mostly Samsung devices I don't have experience with this method. Could you elaborate in another thread plz? Just the back up and restore part. I can manage the unlock and root.
erad1 said:
How would this be done by steps? I'm somewhat familiar with adb {I have the SDK installed and use it for fastboot) but coming from rooting and modding mostly Samsung devices I don't have experience with this method. Could you elaborate in another thread plz? Just the back up and restore part. I can manage the unlock and root.
Click to expand...
Click to collapse
i used the steps posted here. although they needed adapting for the one.
the bones of it is there though, so if you understand it, its easy to do.
Kind of went a different route but used this as a base and got it done. It was tricky but I'm unlocked, rooted, stock recovery and got most of my data back! Thanks for heads up philicibine and OP.
someone running on 33R succeeded with this MOD ???
Medosofts said:
someone running on 33R succeeded with this MOD ???
Click to expand...
Click to collapse
Yes. I was on 33R. Went to stock recovery and flashed 25R. Booted to fastboot and remotely ran twrp recovery and did a backup (in case) then flashed Bootloader unlock zip. While still in recovery, flashed 33R zip and SuperSU. I didn't extract any fastboot files, just used the flashable stock signed zip. All said and done, I had unlocked bootloader and root and back on 33R.
Now I was able to use Flashify app if I wanted a permanent custom recovery.
ralphwiggum1 said:
Yes. I was on 33R. Went to stock recovery and flashed 25R. Booted to fastboot and remotely ran twrp recovery and did a backup (in case) then flashed Bootloader unlock zip. While still in recovery, flashed 33R zip and SuperSU. I didn't extract any fastboot files, just used the flashable stock signed zip. All said and done, I had unlocked bootloader and root and back on 33R.
Now I was able to use Flashify app if I wanted a permanent custom recovery.
Click to expand...
Click to collapse
Hello did this wipe the device???
also were did you download the 33R from can you please provide me the link.
Thanks
Hilmesh said:
Hello did this wipe the device???
also were did you download the 33R from can you please provide me the link.
Thanks
Click to expand...
Click to collapse
This did NOT wipe my device. Look for the flashable (NOT fastboot) images in this thread.
http://forum.xda-developers.com/showthread.php?t=2857110
ralphwiggum1 said:
This did NOT wipe my device. Look for the flashable (NOT fastboot) images in this thread.
http://forum.xda-developers.com/showthread.php?t=2857110
Click to expand...
Click to collapse
Hello ,
I am on 33 R and downloading the flash-able zip from the thread you gave. The rest of items i have already downloaded (Please see attachment). Request you to please confirm that once my 33R download is complete am i ready to proceed??? (I also have the Complete SDK Package with me)
Also can you please list me the procedure step by step. This is my very first time doing it this way as i am used to rooting my S2 and that is a totally different method using ODIN.
Hope to receive your positive reply.
Ok. Done. It worked flawlessly on 33R. Followed all the steps as mentioned by @ralphwiggum1 (Thanks a lot mate . Also Thanks to @ifg for making the basic post to be followed. See attached Rootchecker image for proof.
Please note that this procedure worked for me on a totally unrooted & never before tried rooting device with 33R. Also my device info showed Tampered bit as True & unlock bit as False. You can check it by following this http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912. Thanks to @Mnt-XDA.
Hilmesh said:
Ok. Done. It worked flawlessly on 33R. Followed all the steps as mentioned by @ralphwiggum1 (Thanks a lot mate . Also Thanks to @ifg for making the basic post to be followed. See attached Rootchecker image for proof.
Please note that this procedure worked for me on a totally unrooted & never before tried rooting device with 33R. Also my device info showed Tampered bit as True & unlock bit as False. You can check it by following this http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912. Thanks to @Mnt-XDA.
Click to expand...
Click to collapse
Good job!
"As every guide is written with a Foreword so is this. Please try at your own risk. I am not responsible."
Next this is neither my guide nor my work. I went through all the threads as mentioned in the various links given below. All I did was follow procedure from whichever thread / post was related with my condition. Once I even got confused with too much information but then again as they if we don’t try we never know whether we would have failed or succeeded. 
So I was able to do this only due the works of other people. All the credit & Thanks goes to them. I have tried and remembered and mentioned all the names. In case I have missed anyone please forgive me and point me the name and I will thank them too.
My Step by step procedure to root the device without wipe for devices who have never tried rooting their Oneplus One and are currently on 33R using the method mentioned in this thread,
Download the Recovery flashable zips of the complete ROMz - XNPH25R, XNPH33R
Follow the ADB & Fastboot Installation Procedure listed HERE(Also if you can then do read the complete post as it is very informative for Noobs like me )
Download the Oneplusone-bootunlocker.zip from HERE (Again if possible please read this complete thread too as it is also very informative)
Download the Supersu file from HERE
Download the custom recovery file from HERE
Copy both the Flashable zips, Bootunlocker, supersu files to your device
Switch off your device. And Then boot into STOCK RECOVERY by pressing the VOL DOWN & POWER key
Apply update – XNPH25R and then keep the power key pressed until the screen turns off. DO NOT REBOOT
Now boot to fastboot mode by holding the POWER button & VOL UP Key. Connect it to the PC and let it install all the drivers
Go to the SDK Installation in your PC, and within that go to the folder PLATFORM-TOOLS. Copy the “openrecovery-twrp-2.8.0.1-bacon.img” or latest file which you must have downloaded from the TWRP site
Within the directory Press the Shift Key and right click and you will get an option “Open command Prompt here” – Do it. Type in the command
Code:
Fastboot boot openrecovery-twrp-2.8.0.1-bacon.img
. Wait for 30 Seconds your device will enter into TWRP Custom recovery
Make a Nandroid backup (Optional)
Go to the install option within the recovery and select the Bootunlocker.zip. make sure the signature verification check box in unchecked. Apply the zip.
Now once again go into install option and select the XNPH33R zip and apply
I rebooted the device after Step 14 as I forgot to apply the supersu
Once again followed the same procedure to enter fastboot mode (Step 9) and loaded the custom recovery as mentioned in Step 11 and then applied the supersu zip as mentioned in Step 13. Again rebooted and device was successfully rooted with SuperSU
Next I wanted to flash Franco’s latest Kernel (franco.Kernel-nightly-r20.zip). Downloaded from HERE
Again put device in Fastboot mode (Step 9) and loaded Custom recovery (Step 11) and installed zip file using same procedure as Step 13
Wiped Cache & Dalvik Cache & Rebooted the device. No Issues. Franco Kernel was installed
Credits - I would like to thank everyone for helping me out. Full Thanks & Credits to @ifg (Guide for XNPH300), @Mnt-XDA (Bootunlocker.zip & a great thread about Reset Unlocker & Tamper Bit), @MICa.fighter (CM11S official & untouched image collection), @franciscofranco (Kernel for Oneplus One), Chromium (From Oneplus One Forum for a great guide on Everything Rooting for Oneplus One), @Chainfire (SuperSU), @ralphwiggum1 (for already trying it and clearing my doubts and giving me confidence to proceed)
Worked like a charm. Thanks!
Yeah, I really wish I found this post before I wiped my OPO, and lost another day reinstalling and configuring apps.
Hilmesh said:
"As every guide is written with a Foreword so is this. Please try at your own risk. I am not responsible."
Next this is neither my guide nor my work. I went through all the threads as mentioned in the various links given below. All I did was follow procedure from whichever thread / post was related with my condition. Once I even got confused with too much information but then again as they if we don’t try we never know whether we would have failed or succeeded. 
So I was able to do this only due the works of other people. All the credit & Thanks goes to them. I have tried and remembered and mentioned all the names. In case I have missed anyone please forgive me and point me the name and I will thank them too.
My Step by step procedure to root the device without wipe for devices who have never tried rooting their Oneplus One and are currently on 33R using the method mentioned in this thread,
Download the Recovery flashable zips of the complete ROMz - XNPH25R, XNPH33R
Follow the ADB & Fastboot Installation Procedure listed HERE(Also if you can then do read the complete post as it is very informative for Noobs like me )
Download the Oneplusone-bootunlocker.zip from HERE (Again if possible please read this complete thread too as it is also very informative)
Download the Supersu file from HERE
Download the custom recovery file from HERE
Copy both the Flashable zips, Bootunlocker, supersu files to your device
Switch off your device. And Then boot into STOCK RECOVERY by pressing the VOL DOWN & POWER key
Apply update – XNPH25R and then keep the power key pressed until the screen turns off. DO NOT REBOOT
Now boot to fastboot mode by holding the POWER button & VOL UP Key. Connect it to the PC and let it install all the drivers
Go to the SDK Installation in your PC, and within that go to the folder PLATFORM-TOOLS. Copy the “openrecovery-twrp-2.8.0.1-bacon.img” or latest file which you must have downloaded from the TWRP site
Within the directory Press the Shift Key and right click and you will get an option “Open command Prompt here” – Do it. Type in the command
Code:
Fastboot boot openrecovery-twrp-2.8.0.1-bacon.img
. Wait for 30 Seconds your device will enter into TWRP Custom recovery
Make a Nandroid backup (Optional)
Go to the install option within the recovery and select the Bootunlocker.zip. make sure the signature verification check box in unchecked. Apply the zip.
Now once again go into install option and select the XNPH33R zip and apply
I rebooted the device after Step 14 as I forgot to apply the supersu
Once again followed the same procedure to enter fastboot mode (Step 9) and loaded the custom recovery as mentioned in Step 11 and then applied the supersu zip as mentioned in Step 13. Again rebooted and device was successfully rooted with SuperSU
Next I wanted to flash Franco’s latest Kernel (franco.Kernel-nightly-r20.zip). Downloaded from HERE
Again put device in Fastboot mode (Step 9) and loaded Custom recovery (Step 11) and installed zip file using same procedure as Step 13
Wiped Cache & Dalvik Cache & Rebooted the device. No Issues. Franco Kernel was installed
Credits - I would like to thank everyone for helping me out. Full Thanks & Credits to @ifg (Guide for XNPH300), @Mnt-XDA (Bootunlocker.zip & a great thread about Reset Unlocker & Tamper Bit), @MICa.fighter (CM11S official & untouched image collection), @franciscofranco (Kernel for Oneplus One), Chromium (From Oneplus One Forum for a great guide on Everything Rooting for Oneplus One), @Chainfire (SuperSU), @ralphwiggum1 (for already trying it and clearing my doubts and giving me confidence to proceed)
Click to expand...
Click to collapse
Excellent...well done and will help many!

5S/5G Roms and Root Mega thread [Updated November 2022]

Nubia Red Magic 5G and 5S Roms and Root support Thread
Second post for TWRP and Magisk installation. Mirror for all roms and tools at end of post
Latest Official Rom updates
Android 11
US/Asia - V8.70 Nubia Link MD%: will update soon
EU - V7.70 Nubia Link MD5: will update soon
China - V9.50 Nubia Link MD5: 361AC13CA52AB83C239783FBAB088CEA
Android 10
US/Asia - V8.12 Nubia Link MD5: 6e930fc2431b3daeae2d94145926a6c1
EU - V7.15 Nubia Link MD5: bb9e3153716851e87f196ae6b4f44a2e
China - V6.23 Nubia Link MD5: BD447840ACA4D48F9443B94D2EAD890F
Change Log - 8.70 / 7.70 Android 11
- Security Patch October 2022
- Game Space enhancements
- Game space Gyro sensitivity menu
- game space touch sample rate improvement
- Fixed: corner of screen non-touchable in some cases
- Fixed: issue where game would fail to close
- Fixed: location of caller display
-Fixed: screen tearing when using 144hz
-
Bugs -
in Testing
- Always on display notification not showing
- memory leak in nubia launcher (requires forced close often to stop phone from lagging)
- small window mode for telegram and discord have wrong zoom/ aspect levels.
_____________________________________________________________________________________________________________
UNBRICK TOOL for 5S - Courtesy of @johnny886
Use this tool, with directions on the thread to restore your device to USA/Asia 8.07
you can then install TWRP and after flash any region rom after creating a somewhat universal unbrick tool for those in different regions.
Follow directions on the thread. but here is a link to the Thread. A Mirror for the tool is in my Personal Mirror at the bottom of this thread post.
Link to Thread
Confirmed working with 5G devices - but its recommended to update as soon as you unbrick.
_____________________________________________________________________________________________________________
For unlocked bootloader
Fix your fingerprint sensor.
here Link
--------------------------------
Update Instructions.
Note
for Android 11 do not flash through TWRP you will softbrick.
____________________________________________________________________
For Stock devices without root
- disable security. No pin, no face unlock, no finger print, no pattern. remove all security.
-download zip file
-go to system update tap three dots and select local update
-Navigate to update.zip and select.
-your phone will reboot and install new rom
- you phone will reboot once more and you will be greeted with your lock screen
- setup Phone with security options as before flash.
For devices with "LOCKED bootloader" Root / TWRP (not tested on A11)
- take backup of vbmeta and recovery partitions in TWRP
- change the name of both files to vbmeta.img and recovery.img
(VBmeta is often 64kb big and Recovery is often 90+mb big.)
- copy and paste these new img files into the update zip.
- flash through TWRP
- go back to main menu, select advanced, then select option
"disable replace TWRP" to keep TWRP as your recovery.
for devices with "Unlocked bootloader" (not tested on A11)
-make full backup
-download zip
-install zip through TWRP
-reboot
__________________________________________________________________________________
Custom Roms and Kernels
Kernel
Mattofthedead's Redmagic 5S kernel for LOS and Stock roms LINK
Roms
Rom Builder Ra's Custom Roms - Please post any bugs or issues in the related threads.
Pixel Experience Plus
Ressurection Remix
NOTE : to boot any Custom rom on the 5S device. Flash the Rom following the directions. then flash Matts LOS kernel Version 3
__________________________________________________________________________________
------------------------------
Old roms
Android 11
V8.65 Nubia Link MD5: 3d52e18c66366d3d23744184425d3926
V8.64 Nubia Link MD5: a7e61f5e2f7c377a6850cf6ac3a62aa7
V7.65 Nubia Link MD5: 746dad5b6145dfba1108355095a6ad46
V7.64 Nubia Link MD5: 55371ee8e5728aee2bc7df5b3a7d6585
V9.42 Nubia Link MD5: D492B92DD83B366508CDD74DE7D152A3
V9.40 Nubia Link MD5: D28F26289A9B75F771EF4F623F0BB367
V8.57 Nubia Link MD5: 266819d4b09c2c52aadb39e948dc84bc
V8.59 Nubia Link MD5: d7e32b7a3e833adc57fcf734aa47f5a3
V7.57 Nubia Link MD5: 81ee71869f660a28b631d871ffb59524
V7.60 Nubia Link MD5:
V9.26 Nubia Link MD5: 8997375CD97D8F7F261F21121FC8EFAA
Android 10
v6.18 Link MD5: 9AC5EA5F64835C1995E4A81D4973FB71
V6.13 Link MD5: F38ED2D7CB58252D308B29D1D4517DB9
V7.07 Link MD5: ffc3fdaf4afc522aa3a084d9275f2cb6
V7.14 Link MD5: 0f879160fbf8b556de5303207b93d0d1
V8.07 Link MD5: b30dab221be73292c5da7884afc0363f
V8.11 Link MD5: 85d9366a3017112cb68d66041e725ce6
________________________________________________________
Personal Mirror - Located in Eastern Canada
________________________________________________________
TWRP and root guide for 5S and 5G on Android 10 only - (these steps will NOT unlock your bootloader) - these steps use a bypass method to install a recovery without unlocking bootloader. the command below is to allow flashing of partitions. bootloader status is still locked during and after process is complete.
Note. if you already have ADB and fastboot drivers installed, this folder will work as is. if not I put an installer in the folder too to install a mini adb fastboot setup. which needs windows driver signing turned off (windows 8-10) this can be done by going to advanced startup and choosing to boot without driver signing.
1. Download zip file found at the end of this post
2. Extract to root of C: drive
3. open CMD prompt with admin privileges
4. CD to the ADB folder you extracted. (CD = Change Directory)
5. Connect your device in Fastboot mode (power off. hold volume down +Power until it vibrates. then release power but continue to hold volume down)
6. Once in fastboot mode, with cable connected to the computer run these commands
7. fastboot oem nubia_unlock NUBIA_NX659J (this allows you to flash the device partitions)
8. fastboot flash recovery TWRP-xxx.img (xxx being the version number of the TWRP image you choose to install)
9. fastboot flash vbmeta vbmeta_skip.img
10. reboot to recovery (from the fastboot menu) it should load TWRP
11. if TWRP does not ask you to keep recovery from being over written, go to advanced and choose disable replace TWRP. to keep TWRP as your recovery, and stop the system from re writing the stock recovery.
12. Reboot to system for the first time and complete the initial setup. this is to create the user space partitions data/media ( preferably do not make a pin or pattern at this stage)
13. once in the rom, connect to PC and copy over the Magisk zip to the internal memory. then reboot holding Volume up
14. once back into TWRP (if you created a pin during setup TWRP will ask you for your pin to access data) go into install and flash the Magisk.zip you moved in step 13 then reboot. once back into the rom, you will see a Magisk app, tap it and allow to update, the APK will install latest version of the manager.
More NOTES.
this must be done on a clean system. you need to wipe all data partitions to boot to system. re writing VBMETA causes encryption to break. until you reboot. so you lose everything Make a backup of your data partition on to your PC before doing anything.
its also recommended to have an update.zip of your current rom (which you can download from the post above), incase you need to reinstall the rom after flashing the new recovery or VBmeta.
OEM unlocking in the developer options is NOT needed. since you are not unlocking your bootloader. this step can be ignored.
I'll update this tutorial with newer steps if needed.
Thanks to those that created all these great tools.
@wzsx150 - for their version of TWRP
John Wu - for Magisk
@mslezak vbmeta_skip
If i've helped you root your device, please hit thanks.
Link ADBmini - zip updated with Magisk 21.4 zip
MD5 for ADBfastbootmini.zip: 0ad97a9ae1539b26ef78c849b169e807
I'm working on a process that will update to Android 11, through TWRP and root, without losing data. Much like a stock update.
I will update the thread once my tests are complete.
Hello. I can not flash (i cant even copy) the zip via TWRP. I see the storage device on my windows laptop. I have wipe data cache and dalvik, but it does not copy it and i can not restore my device. Help will be appreciated
josehdx said:
Hello. I can not flash (i cant even copy) the zip via TWRP. I see the storage device on my windows laptop. I have wipe data cache and dalvik, but it does not copy it and i can not restore my device. Help will be appreciated
Click to expand...
Click to collapse
Try putting update zip on a USB key and connect via OTG and flash this way. Moving files with TWRP for some reason corrupts or does not complete transfer.
Make sure to factory reset. If you're coming from a used update, backup your data partition and wipe everything. Then check to see if the partition is in fact empty. ( I noticed sometime my data partition did not erase)
Patrick Morgan said:
Try putting update zip on a USB key and connect via OTG and flash this way. Moving files with TWRP for some reason corrupts or does not complete transfer.
Make sure to factory reset. If you're coming from a used update, backup your data partition and wipe everything. Then check to see if the partition is in fact empty. ( I noticed sometime my data partition did not erase)
Click to expand...
Click to collapse
Thanks
Working fine after full data partition wipe.
I have an additioal question regarding further updates, and i would not want to open a new topic. so, after flashing the zip, i "lost" TWRP but i already have root access. I wonder if is possible to flash upcoming updates with the default recovery built in on the phone, if not, i would assume i need to install TWRP again.in any case, will side loading update make any problem with the current system? i hope my question and context is clear
As these are official ROMs, they will replace the recovery and remove root from the phone.
If you do not have root, flashing these zips from the system menu local update should work. But if you have root or TWRP it's better to flash through TWRP.
You could just flash TWRP again after flash, but I personally modify the zip and add the recovery to it to save me going into fastboot after each update.
Is it possible to install the US rom on a device with EU rom?
in the EU version I can't set the frame rate to 144 hz.
Darkvenum79 said:
Is it possible to install the US rom on a device with EU rom?
in the EU version I can't set the frame rate to 144 hz.
Click to expand...
Click to collapse
I've spoken with another EU rom user, that has the same issue before. it seems it was an error in the stock rom.
reinstalling 7.07 from the links above should fix your problem.
both 7.07 (the EU rom) and 8.07 (the US rom) are exactly the same. the only difference is the languages from what I can tell.
I have a silly question. Unfortunately i unlocked bootloader and i lost the fingerprint capability. I have tried many times to do the calibration without success. I wonder if a factory flash (EDM or any nubia tool) can restore the capability and then use this guide to do the rooting? Thanks
josehdx said:
I have a silly question. Unfortunately i unlocked bootloader and i lost the fingerprint capability. I have tried many times to do the calibration without success. I wonder if a factory flash (EDM or any nubia tool) can restore the capability and then use this guide to do the rooting? Thanks
Click to expand...
Click to collapse
No it wont.
There is a specific step by step that is required to get it functioning again. And it only survives until your next full wipe, which i assume you will do more often flashing non official roms.
I can grab the steps and edit this post for you.
Edit -
Prep.
have a black / very dark brown leather. (belt, wallet, etc)
a soft gel plaster / Bandaid
(something skin textured and in a pink / light beige colour) texture and colour are important.
First step is clear data in the infingerprint app in app info and remove permissionfor data memory - (you need to show system apps to find it)
- digit in call phone code:
*#9959#
(android 11 use Activity launcher (playstore) to enter fingerprint menu)
- uncheck performance checkbox , check only calibration checkbox
Steps -
1. Press start then wait.
2.Press next and with plaster / bandaid press on circle
3.Press next and use wallet / belt ( the display becomes black for black calibration)
4.Press next and use gel plaster / bandaid again but pinch it in so only the part with your finger touches the circle.
If you are lucky see success alert in green color
In system app in setting In-Display-Fingerprint allow access to data memory then reboot device.
Enjoy your Finger Print once more!
P.S. = do this procedure in a very dark room to improve the chances of it succeeding.
Thanks to qtr1st (Salem) and mikekrunk (Mike) for the steps and information.
josehdx said:
I have a silly question. Unfortunately i unlocked bootloader and i lost the fingerprint capability. I have tried many times to do the calibration without success. I wonder if a factory flash (EDM or any nubia tool) can restore the capability and then use this guide to do the rooting? Thanks
Click to expand...
Click to collapse
esy re-lock bootloader fingrperint work fine without calibration
---------- Post added at 12:13 PM ---------- Previous post was at 12:08 PM ----------
Patrick Morgan said:
TWRP and root guide for 5S - (these steps will NOT unlock your bootloader) - these steps use a bypass method to install a recovery without unlocking bootloader. the command below is to allow flashing of partitions. bootloader status is still locked after process is complete.
Pretty short step by step to get twrp and Magisk if you want, on your phone. (Red Magic 5S)
Note. if you already have ADB and fastboot drivers installed, this folder will work as is. if not I put a installer in the folder too to install a mini adb fastboot setup. which needs windows driver signing turned off (windows 8-10) this can be done by going to advanced startup and choosing to boot without driver signing.
1. Download zip file attached or mirrored
2. Extract to root of C: drive
3. open CMD prompt with admin privileges
4. CD to the ADB folder you extracted.
5. Connect your device in Fastboot mode (power off. hold volume down +Power until it vibrates. then release power but continue to hold volume down)
6. Once in fastboot mode, with cable connected to the computer run these commands
7. fastboot oem nubia_unlock NUBIA_NX659J (this allows you to flash the device partitions)
8. fastboot flash recovery TWRP-xxx.img (xxx being the version number of the TWRP image you choose to install)
9. fastboot flash vbmeta vbmeta_skip.img
10. reboot to recovery (from the fastboot menu) it should load TWRP
11. if TWRP does not ask you to keep recovery from being over written, go to advanced and choose disable overwrite TWRP. to keep TWRP as your recovery, and stop the system from re writing the stock recovery.
12. Magisk zips files are in the folder. copy to device and flash through twrp. and install the apk after boot. done twrp and root.
More NOTES.
this must be done on a clean system. you need to wipe all data partitions to boot to system. re writing VBMETA causes encryption to break. until you reboot. so you lose everything Make a backup of your data partition on to your PC before doing anything.
its also recommended to have a update.zip of your current rom (which you can download from the post above), incase you need to reinstall the rom after flashing the new recovery or VBmeta.
OEM unlocking in the developer options is NOT needed. since you are not unlocking your bootloader. this step can be ignored.
I'll update this tutorial with newer steps if needed.
Thanks to those that created all these great tools.
@wzsx150 - for their version of TWRP
John Wu - for Magisk
@mslezak vbmeta_skip
If i've helped you root your device, please hit thanks.
Link ADBmini
MD5 for ADBfastbootmini.zip: e49f162080c6a2124c243716546ad710
Click to expand...
Click to collapse
where is the link of twrp.img
sansha1211 said:
where is the link of twrp.img
Click to expand...
Click to collapse
Patrick Morgan said:
Link ADBmini
MD5 for ADBfastbootmini.zip: e49f162080c6a2124c243716546ad710
Click to expand...
Click to collapse
that file called Link ADBmini has all you need
Is it ok to flash Eu rom to my NA/asia rom?
After reboot it ask me for verify pin and now I can't load the TWRP.img Partition volume Full error help me please
Rai972 said:
After reboot it ask me for verify pin and now I can't load the TWRP.img Partition volume Full error help me please
Click to expand...
Click to collapse
reboot to bootloader by... power off device -> press and hold volume down and power button until you see the logo -> connect device to your computer then do the steps 7 to 12
also once you are in TWRP make sure you ... this must be done on a clean system. you need to wipe all data partitions to boot to system. re writing VBMETA causes encryption to break. until you reboot. so you lose everything Make a backup of your data partition on to your PC before doing anything.
7. fastboot oem nubia_unlock NUBIA_NX659J (this allows you to flash the device partitions)
8. fastboot flash recovery TWRP-xxx.img (xxx being the version number of the TWRP image you choose to install)
9. fastboot flash vbmeta vbmeta_skip.img
10. reboot to recovery (from the fastboot menu) it should load TWRP
11. if TWRP does not ask you to keep recovery from being over written, go to advanced and choose disable overwrite TWRP. to keep TWRP as your recovery, and stop the system from re writing the stock recovery.
12. Magisk zips files are in the folder. copy to device and flash through twrp. and install the apk after boot. done twrp and root.
Rai972 said:
After reboot it ask me for verify pin and now I can't load the TWRP.img Partition volume Full error help me please
Click to expand...
Click to collapse
if you have not removed your pin before flashing any of the roms. it asks you for YOUR own pin that you made when you setup the phone. so use your own pin.
the process of rooting your device, clears a security partition. (the VBmeta partiton)
this deletes the encryption you had on your phone. so the devices partitions are unaccessable and need to be wiped before you can boot to system.
you need to clear data. all data. then check in TWRP file browser if your data partition is clear. .. if you see folders with random letters its not been formatted correctly.
so, in the wipe menu on TWRP you should go into advanced and change the partition type to ext4 then back to f2fs to clear the partition of data.
once your phone is clear you should be able to wipe cache and davik then reboot to system for it to start like a factory reset.
sansha1211 said:
esy re-lock bootloader fingrperint work fine without calibration
---------- Post added at 12:13 PM ---------- Previous post was at 12:08 PM ----------
where is the link of twrp.img
Click to expand...
Click to collapse
How should i relock the bootloader? Via cmd, command doesn't work. Should i lock also via developer options?
josehdx said:
How should i relock the bootloader? Via cmd, command doesn't work. Should i lock also via developer options?
Click to expand...
Click to collapse
adb devices
adb reboot bootloader
fastboot devices
fastboot flashing lock
josehdx said:
How should i relock the bootloader? Via cmd, command doesn't work. Should i lock also via developer options?
Click to expand...
Click to collapse
via cmd -- fastboot flashing lock
After i reboot in TWRP and disable replace TWRP, i install magisk from a USB otg, and then i wipe all data, then i reboot system but it keeps opening TWRP in every reboot, i had to install Stock Rom to have my phone back but without root, what im doing wrong?? thanks
Edit: now it worked, tried a few times and worked don't know what failed

Unable to Boot TWRP in Recovery mode, bootloop issues

Hello guys, I'm a beginner in this flashing stuff. I have watched youtube over a guy flashing Android 10 on his Samsung note 3. I carefully took his steps and i make sure that my model is compatible with said ROM, Mine is Samsung note 3 lte (N9005), Snapdragon. The issues that i am currently having is on flashing TWRP on my Samsung Note 3, because it won't boot on recovery mode despite i press the exact button as the Video describe, it just boots in recovery and then restarted on the same logo boot repeatedly. I have tried flashing LineAgeOs using the tutorial provided by LineAgeOs team and again, i make sure that the rom is fully compatible and still end up same result. Please help me on this issue. Thank you very much for giving your time reading my problems
Please describe your issue again with more details.
From you're post, it seems as though you are having issues with TWRP. Below I will give you a full tutorial on how to get TWRP up and running for your specific device. Do give this a go, as I have done the research for your specific model, and it should work just fine.
First things first, unlock your devices bootloader. You may not have done this correctly, so if it is possbile to boot into android, then try this:
How to unlock Bootloader on Samsung Galaxy Note 3 | Softstribe
Unlocking bootloader in Samsung Note 3 made easy and you can simply enable developers mode where you can perform OEM unlock.
softstribe.com
If you're bootloader is already unlocked, then proceed.
Now that the bootloader in unlocked, we need to install TWRP for your specific device. Your device is the N9005, which is the international snapdragon model. It's codename is hlte, or hlte*. For TWRP, it is also categorised as the Europe/American model (hltexx).
For flashing TWRP correctly to a samsung device, we will need odin. Odin is a flashing software for samsung devices.
Download Odin.zip from here:
Samsung Odin - Root Android download page for one click root
Samsung odin download - Root android and oneclickroot for flash / install custom ROM with one click root method
odindownload.com
(Download the latest version (v13.4.1 at the time of writing this)
Now, extract Odin.
Once we have Odin downloaded, we will need to install the correct usb drivers for Samsung phones.
Download the file below, then extract the zip and run the installer:
Samsung_USB_Driver_v1.7.31.0
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Now that odin and the drivers are ready, we need the actual twrp image which we need to flash to our device.
Here is the link, download the latest .img.tar file (3.6.1_9-0 at the time of writing):
Download TWRP for hlte
Download TWRP Open Recovery for hlte
dl.twrp.me
Do not download the normal .img file, as that cannot be flashed via odin.
Now that we're past the prerequisites, we need to actually flash twrp to your device. To begin, we must put your note 3 into download mode. To enter download mode, power off your phone completely and then press Power+Home+Vol Down at the same time and keep these three buttons pressed until your phone shows a "download mode, do not power off target!!!" screen, you can follow this video tutorial below:
Now that we are in download mode on the device, we need to get back to our computer and configure odin to flash twrp. First things first, open odin. Now, connect your phone to the computer. You should see a little "COM-" show up in one of the empty boxes in the top row under the word "ID:COM". This is good, it means that your pc successfully recognises your device.
Now, go to the options tab on the left side, makse sure that repartition is UNCHECKED. Now, click on the "AP" button, and navigate to and select the TWRP.img.tar file that you downloaded earlier. After you have selected it, click on start at the bottom right. Now it will begin to flash twrp, which should not take long. Make sure that you do not disconnect the device while flashing, wait for the phone to complete. Once it is done, the phone will reboot.
Now, just remove the battery, then put it back in. To enter TWRP recovery, keep Power+Home+Vol Up pressed, then once you see the samsung boot logo upon the phone powering on, let go of power, but keep home and volume up pressed.
Congrats! You've just flashed TWRP to your device, amazing!
Now you can go and look for custom roms to flash to your device. Since your model is the N9005, look for hlte/hlte* roms, don't use any roms if they don't support the hlte/hlte* variant.
Alright, now since you have mentioned that you want to use lineage os, here's a guide for that too.
So currently, it is recommended to use android 11 lineage os nightly builds as they are stable and official, so they should not have any bugs. So unfortunately, I cannot recommend installing lineage os android 10, as you had originally wanted, though the installation process for that will be somewhat similar. It is still not recommended to use old or unofficial builds due to bugs and lack of security updates.
First, we need to download lineage os for this device onto our pc, here's the link to the latest nightly build:
https://mirrorbits.lineageos.org/full/hlte/20220319/lineage-18.1-20220319-nightly-hlte-signed.zip
Next we need to download a GApps package for google play functionality. OpenGApps is recommended as it is open source, secure and reliable, usually with no bugs. I recommend using the nano package instead of pico if your device can handle it (your's can handle it just fine), as it contains google play functionality, and some extra google features which cannot be downloaded from google play. Here is the link to the nano package for your device (only for android 11 roms):
https://sourceforge.net/projects/opengapps/files/arm/20220215/open_gapps-arm-11.0-nano-20220215.zip/download?use_mirror=udomain&r=&use_mirror=autoselect
Now, if you want to get your device play protect certified, you will also need to download magisk for rooting, and magisk modules (so that you can download netflix and use banking apps etc.), but that is something you can do later on, and you can find any tutorial online for this.
Once the download is complete, move the lineage and opengapps .zip files to an sd card and insert it into the phone. Enter TWRP, go to wipe and click on Advanced. From here, wipe System+Data+Cache+Dalvik/ART Cache. Your files such as photos and media will not be wiped.
Next, go back to the TWRP main menu and select install. Click the select storage button at the bottom left and click on Micro SD Card. Now, click on the lineage os zip file, then click on the Add Zips to Queue button and select the opengapps zip file, then click install. This will take some time, do not interrupt it. Once it is complete, you can reboot the phone. The first reboot will take some time, and the first boot may be slow, after setting up your device, make sure to reboot it at least once.
Congrats, you've just installed a custom rom with google play functionality via TWRP!
Unfortunately, sometimes there are issues. If you still cannot get into lineage os despite waiting at least 10 minutes on the boot screen, then follow these steps below:
The lineage team says that booting issues may be due to incompatible recoveries, this means that we will have to use lineageos's own recovery to flash the rom.
For this, download the lineage os recovery.img from here:
https://mirrorbits.lineageos.org/recovery/hlte/20220319/lineage-18.1-20220319-recovery-hlte.img
Now copy this image file to your sd card and insert it into the phone.
Enter TWRP. First of all, click on wipe, then click on advanced and select System+Data+Cache+Dalvik/ART Cache and wipe. Now, go back to the main menu and click install. At the bottom right or left, there will be a button to "Install Image". Click on that button, and select the lineage recovery zip file and install it. Now go back to the main menu and click on the reboot button, then click on reboot to recovery.
Now you will boot into the lineage os recovery, from here you can install lineage os and the gapps zip files. Here is a tutorial:
This tutorial is for a oneplus phone, but it will be the same process on your samsung device.
Once it is complete, you can restart the device. If you would like TWRP back after flashing, just follow the steps from my first post and use odin to flash the twrp file again. I recommend that after installing lineage os, flash twrp again, as twrp recovery is much better than lineage recovery, and you dont need lineage recovery after installing lineage os.
If I helped you out, please mark my post as the solution, Thanks!
PhotonIce said:
If I helped you out, please mark my post as the solution, Thanks!
Click to expand...
Click to collapse
I did exactly with all your instructions. The end result is still the same that it won't boot TWRP after flashing, I don't really understand what the heck is wrong with my Samsung Note 3 Hlte. However i did try again with Lineageos Recovery, heck same thing too! This is really frustracting man, it just restarted itself and goes into normal boot.
LeEpic69 said:
I did exactly with all your instructions. The end result is still the same that it won't boot TWRP after flashing, I don't really understand what the heck is wrong with my Samsung Note 3 Hlte. However i did try again with Lineageos Recovery, heck same thing too! This is really frustracting man, it just restarted itself and goes into normal boot.
Click to expand...
Click to collapse
Did you follow my instructions from the beginning, using the files I linked, instead of your own?
How did you even try lineage recovery if you can't boot into TWRP? You need to boot into TWRP to flash lineage recovery..
HECK, how did you even flash lineage os if you can't boot into twrp???
Please answer these questions, as it is literally impossbile to do what your doing without entering twrp.
Just follow my instructions step by step, using only the files I linked, then tell us what happens.
I think your problem is that you aren't even entering recovery mode. You need to keep Power+Home+Volume Up pressed, then once the samsung logo appears, wait for 2 seconds and let go of power, without letting go of home or volume up. Now keep home and volume up pressed, eventually you will boot into twrp.
If you can't get into twrp, it means that you didn't flash it correctly, in which case make sure that your bootloader is unlocked.
It is also possible that your devices buttons or broken or something, in that case, download platform tools from here:
https://magiskupdate.com/wp-content/uploads/2021/12/platform-tools_r31.0.3-windows.zip/
Next, download and install adb and fastboot drivers from here:
Download in progress... - My USB Drivers
Preparing your download... Please wait...! Facing issues downloading the file or the download link is broken? You can report us here.
myusbdrivers.com
Install the drivers, then reboot. After that, extract platform tools and open the folder. Note the location of the folder (e.g. C:\Users\Name\Downloads\platform-tools). Now open a command prompt window (cmd), then type:
cd location of platform tools folder here
e.g.
cd C:\Users\Name\Downloads\platform-tools
Now, boot your phone into download mode (power+home+vol down), then connect it to the pc. Type:
adb reboot recovery
and
fastboot reboot recovery
This will force your device to boot into recovery, if your device still doesn't boot into twrp, then you have incorrectly flashed twrp to your device. If that's the case, please carefully follow my instructions from the first post, using my linked files only.
PhotonIce said:
Did you follow my instructions from the beginning, using the files I linked, instead of your own?
How did you even try lineage recovery if you can't boot into TWRP? You need to boot into TWRP to flash lineage recovery..
HECK, how did you even flash lineage os if you can't boot into twrp???
Please answer these questions, as it is literally impossbile to do what your doing without entering twrp.
Just follow my instructions step by step, using only the files I linked, then tell us what happens.
I think your problem is that you aren't even entering recovery mode. You need to keep Power+Home+Volume Up pressed, then once the samsung logo appears, wait for 2 seconds and let go of power, without letting go of home or volume up. Now keep home and volume up pressed, eventually you will boot into twrp.
If you can't get into twrp, it means that you didn't flash it correctly, in which case make sure that your bootloader is unlocked.
It is also possible that your devices buttons or broken or something, in that case, download platform tools from here:
https://magiskupdate.com/wp-content/uploads/2021/12/platform-tools_r31.0.3-windows.zip/
Next, download and install adb and fastboot drivers from here:
Download in progress... - My USB Drivers
Preparing your download... Please wait...! Facing issues downloading the file or the download link is broken? You can report us here.
myusbdrivers.com
Install the drivers, then reboot. After that, extract platform tools and open the folder. Note the location of the folder (e.g. C:\Users\Name\Downloads\platform-tools). Now open a command prompt window (cmd), then type:
cd location of platform tools folder here
e.g.
cd C:\Users\Name\Downloads\platform-tools
Now, boot your phone into download mode (power+home+vol down), then connect it to the pc. Type:
adb reboot recovery
and
fastboot reboot recovery
This will force your device to boot into recovery, if your device still doesn't boot into twrp, then you have incorrectly flashed twrp to your device. If that's the case, please carefully follow my instructions from the first post, using my linked files only.
Click to expand...
Click to collapse
I did follow your instructions using your own files that you provided for me. I did press Power + Home + volume up exactly as you told me to and let go of power button and keep pressing Volume up and Home, It just won't boot correctly into Twrp and restarted itself. There is alternative than using TWRP which is Lineageos Recovery os, i flashed that on my Samsung Note 3 HLTE, but it also don't work as well. However the link you sent to me right now is broken. Mind sending new one?
i forgot to mention one thing, i already unlocked the bootloader on Devs setting by turning on USB Debugging. There is no saying about bootloader option. I'm 100% sure i am doing it correctly. I downloaded literally everything from you and did as the instruction told. Even when i keep pressing Home + Volume up, it goes into bootloop without any successful attempt into booting twrp correctly and once i let go of Home + volume up button will boot my Samsung note 3 hlte into Normal boot and work as normal.
there should be an oem unlocking option in developer options. you need to select that, then reboot into downlaod mode and confirm to unlock your bootloader. To check it if it is unlocked, boot into download mode and send a picture of the text which it shows at the top right here on this forum and ill be able to confirm it for you.
N9005 does not have a locked bootloader .
Check its actually a N9005
PhotonIce said:
there should be an oem unlocking option in developer options. you need to select that, then reboot into downlaod mode and confirm to unlock your bootloader. To check it if it is unlocked, boot into download mode and send a picture of the text which it shows at the top right here on this forum and ill be able to confirm it for you.
Click to expand...
Click to collapse
You can see the video for the devs option, there is only usb debugging, i turn it off so that you can notice it and turn it back on in the video. You can try look at the download mode picture too. Let me know if i am doing anything wrong. Anyways the SDK Platform tool link you sent me is broken bro, i haven't try that solution yet.
JJEgan said:
N9005 does not have a locked bootloader .
Check its actually a N9005
Click to expand...
Click to collapse
It is N9005 my bro, I checked the spec with CPUZ and also reFlashed with Stock ROM N9005 with same Country region just for sure and it works fine. After i flash the stock rom, it can boot into recovery mode with no issues. However, with TWRP... It just won't work... I don't know why...
Will an older TWRP 2.8.70 etc flash , it could then upgrade TWRP .
JJEgan said:
Will an older TWRP 2.8.70 etc flash , it could then upgrade TWRP .
Click to expand...
Click to collapse
I'll try flashing Old twrp version and soon update about it.
Okay. it seem to be work out. But i realised that my Samsung note 3 hlte lcd screen is not original... So is this the reason why i can't flash custom rom? Or is there any alternative that may help me flash any good custom rom other than stock?
LeEpic69 said:
Okay. it seem to be work out. But i realised that my Samsung note 3 hlte lcd screen is not original... So is this the reason why i can't flash custom rom? Or is there any alternative that may help me flash any good custom rom other than stock?
Click to expand...
Click to collapse
Changed parts doesnt affect the installation of a custom rom. What issue are you encountering, you said that it worked out..? Just use twrp to wipe system+data+cache+dalvik, then flash acustom rom which is compatible with the hlte
PhotonIce said:
Changed parts doesnt affect the installation of a custom rom. What issue are you encountering, you said that it worked out..? Just use twrp to wipe system+data+cache+dalvik, then flash acustom rom which is compatible with the hlte
Click to expand...
Click to collapse
Twrp 2.8.70 is too old to read modern custom rom, it seem that i can't flash Lineageos 18.1 at all. That's what i mean, although Android 7.1 Lineageos seem to work out on my samsung note 3 hlte
flash 2.8.70, then install a 3.3x image via twrp's "install image" option in the install menu

[HOWTO]/[ROM] [UNOFFCIAL] How to Flash Lineage OS 19.0

Here is a quick how-to guide to flash LineageOS 19.0 to the A51​
Disclaimer: I am not the maintainer of any of the files I link to here. I just wanted to share my experience to make the process of Flashing los19 to the a51 easier for others.
Prerequisites:
1. Unlocked Bootloader
This step is crucial. You need to unlock the bootloader of the A51 before trying any of this. If not, you are likely to brick your device.​1.1. Unlock developer mode by standard procedure: Settings > Info > Tab 7 times on build number​1.2. Enable USB debugging in Developer Options​1.3. Enable OEM unlocking in Developer Options -> To see OEM unlock option I needed to connect to my WIFI, then set the phone date manually to March 7th 2019. Only then the OEM unlock option became visible in Developer Options. Yes, this is super dumb and inconvenient...​1.4 After triggering OEM unlock option shutdown your phone.​1.5 Enter Download mode by: Pressing Volume+ and Volume - while at the same time plugging in the USB cable that is already in your PC.​1.6. To finally unlock bootloader, you will see a green screen on which you need to press Vol + for some time. THIS WILL VOID YOUR WARRANTY. It will also erase all data on your phone!​1.7 After reboot repeat steps 1.1. - 1.5. again. This time you can actually enter download mode by pressing Vol + shortly on the green screen.​
2. Flash Twrp
You can now flash TWRP via Odin. The TWRP img I used is here: https://www.mediafire.com/file/0h14t0263oujhna/TWRP-11-3.6.1-a51-20220321-1406-hotfix.tar/file. I flashed it as AP. Make sure to uncheck Auto reboot before flashing.​When flashing is complete hold Vol - and Power until reboot.​Immediately when rebooting hold Vol + and Power until Samsung logo appears, then let Power go but hold Vol + to enter TWRP.​
3. Actual Flashing:
3.1. Necessary Files:​Make sure to load all files necessary to your SD before flashing:​ChonDoe_Flasher, Disable_Dm_Verity, Multidisabler, LOS-Imagefile, Magisk(optional)​​As for the LOS Image I used this file here, which already includes gapps:​lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img​​If you don't want gapps pick an image that says "BvS" instead of "bgs"​​3.2. You need to move your LOS-Image to the same folder as ChonDoe_Flasher and rename the file to "system.img"​
3.3 Flashing Sequence:
In TWRP Follow this sequence:
3.3.1. Wipe data, dalvik, cache​3.3.2. flash disable_dm_verity​3.3.3. flash multidisabler​3.3.4. Wipe internal storage (Backup might be advisable, if you didn't format data anyways)​3.3.5. reboot recovery​3.3.6. flash chondone with lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img in the same folder renamed to system.mg​3.3.7. Wipe data​3.3.8. Reboot​
That should be it. First startup takes some time, your phone should boot to LOS 19.
4. Anger Management
If you softbrick your device you can try to go back to stock rom by accessing download mode and flashing it via Odin. Will take some fiddling around with the button combinations.
If you hardbrick your device don't hold me responsible and good luck to you!
Thanks to
Kyau Sana, Vadim Kupriyanov, Knoyan GTR-X and Sara Lins and other, from the telegram-group, who helped me figure out the process.
Reserved 1
Reserved 2
Lineage 19 flash worked but after flashing my TWRP recovery bootloops (flashing twrp logo).
TWRP that loops is twrp-a51-3.5.0_10-1_ianmacd.
Do you have a working TWRP for this version of Lineage ?
Tried TWRP v3.6.1 A51 tree but it doesn't work and boots into download mode with "DT Entry not found / DT Load Failed / VB Meta sign errors"
exault said:
Lineage 19 flash worked but after flashing my TWRP recovery bootloops (flashing twrp logo).
TWRP that loops is twrp-a51-3.5.0_10-1_ianmacd.
Do you have a working TWRP for this version of Lineage ?
Tried TWRP v3.6.1 A51 tree but it doesn't work and boots into download mode with "DT Entry not found / DT Load Failed / VB Meta sign errors"
Click to expand...
Click to collapse
I added a download link to the TWRP img I used to my initial post. Let me know if it works.
cheers
DerTopher said:
I added a download link to the TWRP img I used to my initial post. Let me know if it works.
cheers
Click to expand...
Click to collapse
Nope TWRP does not work. When using the one you linked (as all other 3.6.1 ones) it just jumps back to download mode with DT Entry not found & VBMeta not signed errors.
ALL sensors ok ?
Fingerprint ok ? In this ROM
exault said:
Nope TWRP does not work. When using the one you linked (as all other 3.6.1 ones) it just jumps back to download mode with DT Entry not found & VBMeta not signed errors.
Click to expand...
Click to collapse
Sorry to hear mate. Unfortunately I cannot hell you solve this issue. There is a telegram channel for custom roms on the A51 with many motivated people. One of them might have the answer you need!
See: https://t.me/samsunga51
If you find it, please post it, so others can profit from it. With your agreement I would also like to add info about the solution - should you find it - to my initial post.
hacker812c said:
ALL sensors ok ?
Fingerprint ok ? In this ROM
Click to expand...
Click to collapse
Don't know about fingerprint as I do not want to provide biometric data to my phone. Maybe someone else using the ROM can answer this; Or you, if you decide to flash it post your results.
Apart from that I have not had any problems with the ROM apart from the following:
-The resulotion of the native lineage camera app is not satisfactory. When I find an app that works better, I'll let you know.
- Restarting the phone after empty battery requires a soft reset sometimes (power+vol -)
-> A solution to this problem might be given in this post. Will try it later.
Thank you, @DerTopher , but unfortunately the link to your LOS file does not work any more. How do I get the file now?
THIS GUIDE ONLY WORKS ON ANDROID 12!!!
sunnyy15 said:
I have concluded all my experiments, and now I can confirm that the "twrp-a51-3.5.0_10-1_ianmacd.tar" on this website only works for Android 10 as instructed by Admin. This does not for Android 11. For Android 11 you have to flash a different file called "Twrp+vbmeta_A11.tar". Details are given in the following link: https://forum.xda-developers.com/t/...-sm-a515f-one-ui-3-0-dub1-android-11.4231543/
Click to expand...
Click to collapse
@DerTopher , please change your OP to specify that this guide ONLY works for Android 12. I just bootlooped my device when trying this on Android 10 stock firmware
See this excelent post for more info: https://forum.xda-developers.com/t/...-ui-2-5-ctj1-android-10.4213443/post-84750027
Anyone knows how to remove the native SU, so that magisk doesn't complain about "abnormal state" su file ?
when i flash something in twrp i have an error failed to mount '/odm4 no such file or directory Can some help me please i am stuck here
DerTopher said:
Here is a quick how-to guide to flash LineageOS 19.0 to the A51​
Disclaimer: I am not the maintainer of any of the files I link to here. I just wanted to share my experience to make the process of Flashing los19 to the a51 easier for others.
Prerequisites:
1. Unlocked Bootloader
This step is crucial. You need to unlock the bootloader of the A51 before trying any of this. If not, you are likely to brick your device.​1.1. Unlock developer mode by standard procedure: Settings > Info > Tab 7 times on build number​1.2. Enable USB debugging in Developer Options​1.3. Enable OEM unlocking in Developer Options -> To see OEM unlock option I needed to connect to my WIFI, then set the phone date manually to March 7th 2019. Only then the OEM unlock option became visible in Developer Options. Yes, this is super dumb and inconvenient...​1.4 After triggering OEM unlock option shutdown your phone.​1.5 Enter Download mode by: Pressing Volume+ and Volume - while at the same time plugging in the USB cable that is already in your PC.​1.6. To finally unlock bootloader, you will see a green screen on which you need to press Vol + for some time. THIS WILL VOID YOUR WARRANTY. It will also erase all data on your phone!​1.7 After reboot repeat steps 1.1. - 1.5. again. This time you can actually enter download mode by pressing Vol + shortly on the green screen.​
2. Flash Twrp
You can now flash TWRP via Odin. The TWRP img I used is here: https://www.mediafire.com/file/0h14t0263oujhna/TWRP-11-3.6.1-a51-20220321-1406-hotfix.tar/file. I flashed it as AP. Make sure to uncheck Auto reboot before flashing.​When flashing is complete hold Vol - and Power until reboot.​Immediately when rebooting hold Vol + and Power until Samsung logo appears, then let Power go but hold Vol + to enter TWRP.​
3. Actual Flashing:
3.1. Necessary Files:​Make sure to load all files necessary to your SD before flashing:​ChonDoe_Flasher, Disable_Dm_Verity, Multidisabler, LOS-Imagefile, Magisk(optional)​​As for the LOS Image I used this file here, which already includes gapps:​lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img​​If you don't want gapps pick an image that says "BvS" instead of "bgs"​​3.2. You need to move your LOS-Image to the same folder as ChonDoe_Flasher and rename the file to "system.img"​
3.3 Flashing Sequence:
In TWRP Follow this sequence:
3.3.1. Wipe data, dalvik, cache​3.3.2. flash disable_dm_verity​3.3.3. flash multidisabler​3.3.4. Wipe internal storage (Backup might be advisable, if you didn't format data anyways)​3.3.5. reboot recovery​3.3.6. flash chondone with lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img in the same folder renamed to system.mg​3.3.7. Wipe data​3.3.8. Reboot​
That should be it. First startup takes some time, your phone should boot to LOS 19.
4. Anger Management
If you softbrick your device you can try to go back to stock rom by accessing download mode and flashing it via Odin. Will take some fiddling around with the button combinations.
If you hardbrick your device don't hold me responsible and good luck to you!
Thanks to
Kyau Sana, Vadim Kupriyanov, Knoyan GTR-X and Sara Lins and other, from the telegram-group, who helped me figure out the process.
Click to expand...
Click to collapse
Hello friends, how are you? Could someone post the ROM link again, the link is broken.
lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS
dmudo said:
Hello friends, how are you? Could someone post the ROM link again, the link is broken.
lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS
Click to expand...
Click to collapse
Andy Yan's personal builds // GSI
Download Andy Yan's personal builds // GSI for free. None
sourceforge.net
i have a question
in step 3.3.6. flash chondone with lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img in the same folder renamed to system.mg
i try to flash chondoe and i tried to add de system.img, and it prompt me to what partition
This are the partitions that apears to me
- Boot
- DTBO Image
- Optics Image
- Prism Image
- Recovery
- Param
- VBmeta Samsung
- VBMeta Samsung
- Super (system vendor product odm)
Does anyone know where ?
DerTopher said:
Here is a quick how-to guide to flash LineageOS 19.0 to the A51​
Disclaimer: I am not the maintainer of any of the files I link to here. I just wanted to share my experience to make the process of Flashing los19 to the a51 easier for others.
Prerequisites:
1. Unlocked Bootloader
This step is crucial. You need to unlock the bootloader of the A51 before trying any of this. If not, you are likely to brick your device.​1.1. Unlock developer mode by standard procedure: Settings > Info > Tab 7 times on build number​1.2. Enable USB debugging in Developer Options​1.3. Enable OEM unlocking in Developer Options -> To see OEM unlock option I needed to connect to my WIFI, then set the phone date manually to March 7th 2019. Only then the OEM unlock option became visible in Developer Options. Yes, this is super dumb and inconvenient...​1.4 After triggering OEM unlock option shutdown your phone.​1.5 Enter Download mode by: Pressing Volume+ and Volume - while at the same time plugging in the USB cable that is already in your PC.​1.6. To finally unlock bootloader, you will see a green screen on which you need to press Vol + for some time. THIS WILL VOID YOUR WARRANTY. It will also erase all data on your phone!​1.7 After reboot repeat steps 1.1. - 1.5. again. This time you can actually enter download mode by pressing Vol + shortly on the green screen.​
2. Flash Twrp
You can now flash TWRP via Odin. The TWRP img I used is here: https://www.mediafire.com/file/0h14t0263oujhna/TWRP-11-3.6.1-a51-20220321-1406-hotfix.tar/file. I flashed it as AP. Make sure to uncheck Auto reboot before flashing.​When flashing is complete hold Vol - and Power until reboot.​Immediately when rebooting hold Vol + and Power until Samsung logo appears, then let Power go but hold Vol + to enter TWRP.​
3. Actual Flashing:
3.1. Necessary Files:​Make sure to load all files necessary to your SD before flashing:​ChonDoe_Flasher, Disable_Dm_Verity, Multidisabler, LOS-Imagefile, Magisk(optional)​​As for the LOS Image I used this file here, which already includes gapps:​lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img​​If you don't want gapps pick an image that says "BvS" instead of "bgs"​​3.2. You need to move your LOS-Image to the same folder as ChonDoe_Flasher and rename the file to "system.img"​
3.3 Flashing Sequence:
In TWRP Follow this sequence:
3.3.1. Wipe data, dalvik, cache​3.3.2. flash disable_dm_verity​3.3.3. flash multidisabler​3.3.4. Wipe internal storage (Backup might be advisable, if you didn't format data anyways)​3.3.5. reboot recovery​3.3.6. flash chondone with lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img in the same folder renamed to system.mg​3.3.7. Wipe data​3.3.8. Reboot​
That should be it. First startup takes some time, your phone should boot to LOS 19.
4. Anger Management
If you softbrick your device you can try to go back to stock rom by accessing download mode and flashing it via Odin. Will take some fiddling around with the button combinations.
If you hardbrick your device don't hold me responsible and good luck to you!
Thanks to
Kyau Sana, Vadim Kupriyanov, Knoyan GTR-X and Sara Lins and other, from the telegram-group, who helped me figure out the process.
Click to expand...
Click to collapse
3.3.7 format data or wipe?

General Questions, how to flash the SM-T585

hello, I need your help please.
since I use the pixel smartphones, I have no longer flashed. now I got the SM-T585 gift and wanted to flash the https://forum.xda-developers.com/t/unofficial-rom-t585-lineageos-18-x-11-0-64-bit-treble.4511073/ on it. but I'm a bit rusty now and would need your help.
Where do I get latest bootloader and modem?
How do I flash them to the tablet?
When do I flash the repartition script?
How do I get TWRP on the tablet?
How to backup all partitions (it least efs) and store somewhere?
I appreciate any support.
Thanks, Markus from Germany
bavmouse said:
hello, I need your help please.
since I use the pixel smartphones, I have no longer flashed. now I got the SM-T585 gift and wanted to flash the https://forum.xda-developers.com/t/unofficial-rom-t585-lineageos-18-x-11-0-64-bit-treble.4511073/ on it. but I'm a bit rusty now and would need your help.
Where do I get latest bootloader and modem?
Click to expand...
Click to collapse
These are part of the firmware package for your device. You can use programs such as Frija, or websites such as Sammobile to download the latest firmware.
bavmouse said:
How do I flash them to the tablet?
Click to expand...
Click to collapse
Put the tablet in download mode, and use Odin to flash the files. Make sure the bootloader is unlocked. You most likely cannot immediately flash custom binaries after you unlock the bootloader; skip through initial setup, connect to the Internet, ensure OEM Unlocking is still visible in Developer Options.
When in download mode, there should be a line that reads KG STATUS. If this is CHECKING or COMPLETED, you should be OK. If it says PRENORMAL, you need to boot the OEM firmware and ensure OEM Unlocking is visible. This is due to Vaultkeeper - even after the bootloader is unlocked, Samsung throws a few wrenches into the mix to make things tricky.
bavmouse said:
When do I flash the repartition script?
Click to expand...
Click to collapse
After you've installed TWRP.
bavmouse said:
How do I get TWRP on the tablet?
Click to expand...
Click to collapse
The TWRP image for your tablet should be available as an AP.tar file. Once you've ensured Vaultkeeper has unleashed your bootloader, you can flash this using Odin in download mode to the AP slot.
bavmouse said:
How to backup all partitions (it least efs) and store somewhere?
Click to expand...
Click to collapse
You can use TWRP to create a backup.
bavmouse said:
I appreciate any support.
Thanks, Markus from Germany
Click to expand...
Click to collapse
Here to help.
V0latyle said:
These are part of the firmware package for your device. You can use programs such as Frija, or websites such as Sammobile to download the latest firmware.
Put the tablet in download mode, and use Odin to flash the files. Make sure the bootloader is unlocked. You most likely cannot immediately flash custom binaries after you unlock the bootloader; skip through initial setup, connect to the Internet, ensure OEM Unlocking is still visible in Developer Options.
When in download mode, there should be a line that reads KG STATUS. If this is CHECKING or COMPLETED, you should be OK. If it says PRENORMAL, you need to boot the OEM firmware and ensure OEM Unlocking is visible. This is due to Vaultkeeper - even after the bootloader is unlocked, Samsung throws a few wrenches into the mix to make things tricky.
After you've installed TWRP.
The TWRP image for your tablet should be available as an AP.tar file. Once you've ensured Vaultkeeper has unleashed your bootloader, you can flash this using Odin in download mode to the AP slot.
You can use TWRP to create a backup.
Here to help.
Click to expand...
Click to collapse
thank you very much for your detailed answer.
I have now collected all the programs and files.
but could you please give me a brief list of the exact order of procedure in bullet points, that would be very helpful.
and when and how do i unlock the bootloader?
thank you, markus
bavmouse said:
thank you very much for your detailed answer.
I have now collected all the programs and files.
but could you please give me a brief list of the exact order of procedure in bullet points, that would be very helpful.
and when and how do i unlock the bootloader?
thank you, markus
Click to expand...
Click to collapse
Unlock bootloader:
Enable developer options
Toggle OEM Unlocking to ON
Power off device completely (disconnect USB cable)
Start device in download mode: hold both Volume buttons, do not press Power, plug in USB cable from PC, device should start in download mode
Unlock bootloader; hold Volume Up until bootloader unlock screen appears, select Continue. This will wipe data
Disable Vaultkeeper:
Boot device and skip through initial setup. Connect to Internet. Enable Developer Options and ensure OEM Unlocking toggle is still visible. If it is not, Vaultkeeper is still enabled and you won't be able to flash custom binaries.
If OEM Unlocking is visible (should read "Bootloader is already unlocked"), power off device and start in download mode. Look for KG STATUS: If this says COMPLETED or CHECKING, you should be OK. If it says PRENORMAL or BROKEN, you won't be able to flash custom binaries, and you need to go back to step 1 to ensure Vaultkeeper is disabled.
Flash firmware:
Put device in download mode and leave connected to PC
Start Odin, device should appear: blue box under ID: COM, "Added!" in log
Flash firmware - BL goes in BL slot, AP goes in AP slot, etc. There are two CSC files - CSC and HOME_CSC. CSC is for factory reset, HOME_CSC keeps user data. Keep in mind for future update.
Flash TWRP:
Download TWRP for your device
Put device in download mode
Start Odin and flash TWRP .tar in AP slot
When device reboots, hold Volume Up to start in recovery mode
Disable encryption:
Download Multidisabler, transfer to device, flash in TWRP
Format data (Wipe > Format data > type YES)
Install LineageOS:
With device in TWRP mode and connected to computer, download desired LineageOS image
Note: should be arm64, be aware that some of the bvN/bgN "secure" builds may boot loop. VNDKlite not required. bvS/bgS builds have built in root, just need PHH SuperSU app. bvN/bvS builds do not have Gapps, will need to flash a Gapps package such as MindtheGapps (make sure you select the appropriate version)
Transfer LineageOS image to device storage (MTP should work in TWRP)
Install LineageOS (Install > Select Storage> select storage you uploaded the image to > Install Image > select System (DO NOT flash image to /boot, /recovery, or any other partition)
If necessary, install Gapps
Note: if this fails, you may need to resize /system. After flashing LineageOS, go to Wipe > Advanced Wipe > select System > Repair or Change File System > Resize File System
Reboot to system

Categories

Resources