Related
The story begins when I had twrp. i flashed the oneplus_x_oxygenos_3.1.1_community_build usb debugging turned on, and oem unlocking. I was successful, I had stock oxygen OS but I lost twrp in doing so.
retried to install twrp, it did not work, when i tried going to recovery it's stuck on oneplus logo. i tried to fix it with this , did't notice it was for Oneplus 2, so.... hard bricked my phone, i was able to recover with this but i could not install twrp. so i installed the stock recovery MM which works now. OS does not work anymore. for some reason when i try to flash the oxygenos_3.1.1 with stock recovery, it still fails. even when i tried installing a lower version rom.
Can anybody help me? this is my daily driver phone. currently using my nokia feature phone for calls and texts......
what I have:
Stock recovery
nandroid backup that i cannot use because i don't have twrp,
usb debugging turned off,
and oem unlocking off.
can access fastboot, sideload.
no access to OS.
Hatred for Pokemon Go
yay it's alive!!
this worked for me! http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
moderator kindly delete my post. Thanks!
Don't know why people are still flashing community build with twrp. So much information on this. Yes we have a working twrp for 3.1.1 but that's for after its installed.
Exodusche said:
Don't know why people are still flashing community build with twrp. So much information on this. Yes we have a working twrp for 3.1.1 but that's for after its installed.
Click to expand...
Click to collapse
I guess some confusion might have been caused when it was posted on the OnePlus forums (and apparently a quote from a OnePlus rep) that the new build was "compatible" with TWRP. This was later clarified (by a poster, not OnePlus) to mean V41 of the blu-spark TWRP.
Chat with support confirms.
Kashaila said:
Sorry to keep you waiting. I apologize for the confusion. I have just confirmed from the specialist that TWRP is compatible with the new rollout.
Click to expand...
Click to collapse
https://forums.oneplus.net/threads/...nity-beta-for-oneplus-x.464812/#post-15231909
Perhaps the mistake arises because it is not clear was that whilst TWRP is compatible, you couldn't actually flash the new community build with it! TWRP is only compatible (like you say) AFTER the flash!!
https://tapatalk.com/shareLink?url=...share_tid=3464987&share_fid=3793&share_type=t
[guide] unbrick device
This should help...
The solution for OPX hardbrick is similar to OPO and OP2 - you just need a Qualcomm driver and a recover package.
So,here we go !!
Step 1 :- DOWNLOADS :-
1.) Drivers :- https://www.androidfilehost.com/?fid=24052804347799753 (Extract these files to a folder on desktop.)
2.) Recovery Tool :- https://drive.google.com/folderview?...XM&usp=sharing (Download all files inside this folder and put them in a folder on desktop.)
Step 2 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 3 :- Press the power button for 40 seconds to turn off the phone.
Step 4 :- Press only volume up button for 10 sec and then power button. While keeping them pressed,connect OPX to PC.Hold volume up until your PC finds a new hardware .
Step 5 :- Go to device manager in your PC, find the new "QUALCOMM-HS USB Diagnostics xxxx" device or something like this (It must be Unknown Devices as QHUSB_BULK or under COMs and Ports as Qualcomm xxxx). Update its driver in property page using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder).
Step 6 :- After installing the drivers,"Run As Administrator" the MSMDownloadToolV2.0 in the recovery tools folder.
Step 7 :- Click start at top left corner and wait for it to finish (Download Complete will come)
Step 8 :- Disconnect phone from PC and boot into system.
Now you can again do anything you wish to (unlock bootloader,etc).To unlock bootloader,go to developer options and tick "Enable OEM Unlock" first.
When you will need this guide ? :-
1.) If your phone is totally black (no racism)
2.) When you have locked the bootloader by mistake . (This happens when you flash a rom without having oem unlocking enabled.)
PS:- This method will wipe all data and restore your phone to OxygenOS and English Bootloader.
Thanks.
Hi, i can' get the qualcomm driver installed. It says like the hash isn't in the catalog and that it is damaged or messed with.
The Driver Signature is turned off in W10, so do you know something?
Also there is no communication with fastboot, i can boot to it, to the fb logo on the opx, but no way to get contact.
Thanks
tjeus said:
Hi, i can' get the qualcomm driver installed. It says like the hash isn't in the catalog and that it is damaged or messed with.
The Driver Signature is turned off in W10, so do you know something?
Also there is no communication with fastboot, i can boot to it, to the fb logo on the opx, but no way to get contact.
Thanks
Click to expand...
Click to collapse
Change computer.
Try with an old windows 7.
Or, try this: http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
Iirc, it's the same for Windows 10.
Sent from my ONE E1003 using Tapatalk
Himanshu Gusai said:
The solution for OPX hardbrick is similar to OPO and OP2 - you just need a Qualcomm driver and a recover package.
So,here we go !!
Step 1 :- DOWNLOADS :-
1.) Drivers :- https://www.androidfilehost.com/?fid=24052804347799753 (Extract these files to a folder on desktop.)
2.) Recovery Tool :- https://drive.google.com/folderview?...XM&usp=sharing (Download all files inside this folder and put them in a folder on desktop.)
Step 2 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 3 :- Press the power button for 40 seconds to turn off the phone.
Step 4 :- Press only volume up button for 10 sec and then power button. While keeping them pressed,connect OPX to PC.Hold volume up until your PC finds a new hardware .
Step 5 :- Go to device manager in your PC, find the new "QUALCOMM-HS USB Diagnostics xxxx" device or something like this (It must be Unknown Devices as QHUSB_BULK or under COMs and Ports as Qualcomm xxxx). Update its driver in property page using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder).
Step 6 :- After installing the drivers,"Run As Administrator" the MSMDownloadToolV2.0 in the recovery tools folder.
Step 7 :- Click start at top left corner and wait for it to finish (Download Complete will come)
Step 8 :- Disconnect phone from PC and boot into system.
Now you can again do anything you wish to (unlock bootloader,etc).To unlock bootloader,go to developer options and tick "Enable OEM Unlock" first.
When you will need this guide ? :-
1.) If your phone is totally black (no racism)
2.) When you have locked the bootloader by mistake . (This happens when you flash a rom without having oem unlocking enabled.)
PS:- This method will wipe all data and restore your phone to OxygenOS and English Bootloader.
Thanks.
Click to expand...
Click to collapse
Hello, i have similar problem.
I tried to flash sultan rom on top of cm13 nightly, but before flashing i wiped everything, system,data, cache etc.
Then i went to flash sultan(with twrp, can't remember the version but i think it was new one), i had to change update script in .zip file to ONE before i could flash it.
Then when it flashed i tried to restart but it said no system.
I decided not to restart and flash OOS 3.1.3, it flashed and restarted...but it was constantly restarting, logo would show and 1 sec after it would restart, and it stuck in a loop. No recovery, no fastboot...
With a guide above i managed to get it to install recovery and rom, but when booting, after loading android apps, it would just say finishing boot and restart again...
So i had recovery and tried to flash a new recovery but bootloader is locked, and cannot be unlocked because, oem unlock is disabled....
I tried to flash OOS 3.1.3 with stock recovery but after clicking YES for flashing phone turned off. When i tried to turn it on it only shows logo, nothing booting....
And now when i try to use MSM Download tool everything is done but phone still doesn't boot anything at all......now it won't even get to the part with loading android apps.....
Can anyone help?? Could someone please upload recovery.img and system.img that i could put in MSM folder, maybe if it would flash that files it would work?
Is there any other way to set oem unlock to enabled without developer options???
help help help
Ovakisan said:
Hello, i have similar problem.
I tried to flash sultan rom on top of cm13 nightly, but before flashing i wiped everything, system,data, cache work?
Is there any other way to set oem unlock to enabled without developer options???
help help help
Click to expand...
Click to collapse
The part when it said no system you would of been fine if you just let it boot. Did you wipe before flashing 3.1.3 after Sultan? You need to get old stock recovery to flash 3.1.3. Whether that be thru fastboot or using the unbrick guide.
Once you have booted 3.1.3 you can continue with fastboor flashing one of the updated twrp's (Sultans,blu sparksv41,Nachets.)
Exodusche said:
The part when it said no system you would of been fine if you just let it boot. Did you wipe before flashing 3.1.3 after Sultan? You need to get old stock recovery to flash 3.1.3. Whether that be thru fastboot or using the unbrick guide.
Once you have booted 3.1.3 you can continue with fastboor flashing one of the updated twrp's (Sultans,blu sparksv41,Nachets.)
Click to expand...
Click to collapse
I did wipe yes, but within twrp not stock recovery, so that is what f**ed it up :/
Thru fastboot i can't do anything because bootloader is locked and cannot be unlocked. unbrick guide just boots, updates and starts android applications and then restarts.
A few minutes ago it managed to get into setup wizard, and i went skip skip skip just to get into settings and before i got in freaking thing restarted and now is again starting aplications in a loop......
Could i use different img files with MSM downloader? Where can i read more about msm downloader app and what it does?
Ovakisan said:
I did wipe yes, but within twrp not stock recovery, so that is what f**ed it up :/
Thru fastboot i can't do anything because bootloader is locked and cannot be unlocked. unbrick guide just boots, updates and starts android applications and then restarts.
A few minutes ago it managed to get into setup wizard, and i went skip skip skip just to get into settings and before i got in freaking thing restarted and now is again starting aplications in a loop......
Could i use different img files with MSM downloader? Where can i read more about msm downloader app and what it does?
Click to expand...
Click to collapse
Can't you go through the steps to unlock bootloader now that you've done the hard brick guide? I'm not sure bro someone will help you.
Exodusche said:
Can't you go through the steps to unlock bootloader now that you've done the hard brick guide? I'm not sure bro someone will help you.
Click to expand...
Click to collapse
The problem is that after going through guide, MSM downloader would say that its done, and it wouldn't boot in android, sou you can't get into developers options to enable OEM unlocking. And throught fastboot you can't do anything because its not enabled...
anyway if anyone is reading this that has same issue, just don't stop restarting, this little fu**** just managed to boot into android and i managed to get into dev options(after 3-4 restart, and 1 wipe cache data in stock recovery). after setting OEM unlock to enabled i tried to shut down phone through normal shutdown procedure but it got stuck, but force shut down with button worked and it saved OEM unlocking option on enabled. so i managed to unlock bootloader with fastboot.
So im with stock recovery now, lollipop ROM, should i try to flash OOS 3.1.3 now, or do i have to do something else prior to flashing????
I'm kind of scared now to do anything :'D
EDIT: ok, i ran into problem again -.-
twrp is flashed, latest. now when i try to flash cm13 or sultans cm13 i get this error.
http://imgur.com/a/BSpK1
Hi,this is the beginners guide in rooting the Galaxy J5 Pro.
First I want you to know that J5 Pro is the same as J5 2017.
You will need some files:
Opt verity Encrypt - http://download.highonandroid.com/file/Tools/Root/Samsung/no-verity-opt-encrypt-6.0-star.zip
RMM State Bypass Mesa - http://download.highonandroid.com/file/Tools/Root/Samsung/RMM-State_Bypass_Mesa.zip
Magisk 19.1 - https://github.com/topjohnwu/magisk_files/raw/master/canary_builds/magisk-release.zip
Magisk Manager 7.1.2 - https://github.com/topjohnwu/magisk_files/raw/master/canary_builds/app-release.apk
(Optional)(For Pie) Helios Pie Kernel - https://androidfilehost.com/?fid=1395089523397966358
(Optional)(For Oreo) Helios Pro Kernel - https://androidfilehost.com/?fid=1395089523397913077
(Optional) Promotheus One UI (Pie ROM) -https://androidfilehost.com/?fid=1395089523397940329
(Optional) Promotheus Lite (Oreo ROM) -https://androidfilehost.com/?fid=1395089523397887684
TWRP 3.3.0-0 - https://github.com/ananjaser1211/an...3.3_J7Y17LTE/TWRP-3.3.0-j7y17lte-20190417.tar
Odin - https://odindownload.com/download/Odin3_v3.13.1.zip
Stock ROM (In case of Soft bricking you can save your device) - https://s3.wasabisys.com/updatofw/GALAXYJ5/SM-J530F/BTU/SM-J530F_1_20190405203714_44wceovclw_fac.zip
Samsung USB Drivers - https://developer.samsung.com/common/download/check.do?actId=698
Copy the No Verity OPT Encrypt file,RMM State Bypass,What kernel u need,The rom u need,Magisk and Magisk Manager APK to ur SD Card.
Enable Developer options(Go into About phone,Software information,Tap several times on Build number until it says you are a developer.
Then go to Settings > Developer options > Check Oem UNLOCK and USB Debugging.
If you broke your device go to last lines(down)
If you already downloaded the files lets begin!
1.Turn off your phone and boot into download mode (Hold Volume Down,Home and Power and them press Volume UP)
2.Install Samsung USB DRIVERS on PC
3.Connect your Phone to your PC by USB Cable.
4.Open odin and load the twrp tar in AP slot.
5.Go to options and uncheck Auto Reboot
6.Click start
7.When in ODIN it shows PASS,Hold Volume Up,Home and power until the screen turns black then immiediately release and Hold Volume UP,Home and Power until the TWRP Screen Appears.
8.Tap on Keep Read Only and then Wipe and Format Data.Type "yes" without ".
9.Tap on Reboot and then Recovery
10.Tap on install then on Select Storage And Micro SDCard.
11.Press on No verity Opt Encrypt and swipe.
12.Press back button and Install RMM State Bypass Mesa.
13.Press back button and Install Magisk.
14.Tap on Wipe Cache and Dalvik and Then Swipe
15.Press the middle button(Home) and Tap on Reboot and then System.
16.Wait for the phone to boot and configure it.
17.Enable Developer options again and enable OEM Unlock and USB Debugging.
18.Disconnect Your Phone from the PC.
If you just wanted Root, You are Done.
Install Helios Pro Kernel to Stock ROM -
1.Go into recovery
2.Install > Select Storage > Helios Pro Kernel file
3.Swipe
4.Wipe Cache and Dalvik and Reboot to System.
If you dont pass SafetyNet :Go to Magisk > Modules > And disable BusyBox for Android NDK.
Install Custom Rom -
1.Boot Into TWRP (When powered OFF Hold Volume UP,Home and Power)
2.Go to Wipe and Select System,Data,Cache,Internal Storage and swipe.
3.Then click on Wipe and Format Data. (Recommended)
4.Go to Install and select what ROM you want to Install:
-Promotheus One UI (Pie ROM)
-Promotheus Lite (OREO ROM)
Click on First "Click to show content" for Promotheus One UI
Click on Second "Click to show content" Promotheus Lite
1.In Aroma Installer Click next and agree to the terms and conditions
2.Then click Full Wipe.
3.Select What Mods you want
4.Select what BloatWare you want.
5.Click Install.
6.After its done Reboot.
7.After ~15 seconds of the Samsung Logo Hold Volume Down,Home and Power then release when the screen turns black.
8.After it boots it will be laggy.Complete the setup and connect to Google and Samsung Account and update everything first ftom Galaxy Store then from Play store.Then reboot and it will not be laggy.
9.You will see that you dont have root, to fix this Reboot into Recovery (You know the procedure) and go to Install > Select Storage > MicroSD Card > HeliosPie Kernel 3.1 and swipe.
10.Wipe Cache and Dalvik and reboot.
11.After it boots you will have Root and a Pie Custom Rom!
12.If you do not pass Safety Net,Go to Magisk > Modules > And disable BusyBox for Android NDK.
You are Done! Now install your favorite apps!
1.Boot into Recovery
2.Install > Promotheus Lite A8+
3.In Arome click Next and Agree to the Terms and Conditions.
4.Select your Mods
5.Select your BloatWare
6.Tap on Install and Reboot to System.
7.After ~15 seconds of The Samsung LOGO and then Hold Volume Down,Home and Power and Release when the screen turns black.
8.After the phone boots it will be very laggy.Complete the setup and connect to Google and Samsung Account and update everything From Galaxy Store and Play Store.
9.You will see you dont have root.Boot into Recovery and Tap on Install > Select Storage > Micro SDCard > Helios Pro Kernel.
10.Reboot to System.
11.You are done
If you dont pass SafetyNet :Go to Magisk > Modules > And disable BusyBox for Android NDK.
If you Soft Brickes your device, open odin. Hold Volume Down,Home and Power until you are in download mode.
In odin select BL in BL box
AP in AP box
CP in CP box
CSC in CSC box (Important select CSC not Home_CSC)
Click Start and wait.
Your device will boot.
Finish the setup and enable developer option blah blah blah (Try Again)
If you dont see Oem unlock,You need to wait 7 days.
So thats it! If you have any problem reply!
victorAndrie said:
Hi,this is the beginners guide in rooting the Galaxy J5 Pro.
First I want you to know that J5 Pro is the same as J5 2017.
Click to expand...
Click to collapse
Samsung website on the j5 pro. Notice the model number
https://www.samsung.com/au/smartphones/galaxy-j5-pro-j530y/SM-J530YZKEXSA/
Gsm arena page on j5 (2017). Notice the model number.
https://www.google.com/amp/s/m.gsmarena.com/samsung_galaxy_j5_(2017)-ampp-8705.php
That info was readily available to anyone for about 2 yrs Also, you guys on the j5 2017 already have guides to do what you created a thread to do?
https://forum.xda-developers.com/galaxy-j5/how-to/samsung-j5-2017-sm-j530f-root-oreo-8-1-t3911794
palmbeach05 said:
Samsung website on the j5 pro. Notice the model number
https://www.samsung.com/au/smartphones/galaxy-j5-pro-j530y/SM-J530YZKEXSA/
Gsm arena page on j5 (2017). Notice the model number.
https://www.google.com/amp/s/m.gsmarena.com/samsung_galaxy_j5_(2017)-ampp-8705.php
That info was readily available to anyone for about 2 yrs Also, you guys on the j5 2017 already have guides to do what you created a thread to do?
https://forum.xda-developers.com/galaxy-j5/how-to/samsung-j5-2017-sm-j530f-root-oreo-8-1-t3911794
Click to expand...
Click to collapse
That is only root.
victorAndrie said:
That is only root.
Click to expand...
Click to collapse
Straight from post #1 of that thread. Notice the starred parts below.
After updating my J5 2017 J530F to the latest Oreo 8.1 I was having trouble getting root and all things working again.
Hours of waiting for installs then something going wrong after applying the CF-Auto-root or trying to install Magisk or something and having to install again, Hours spent waiting..
Trying to install the auto-root would cause a verification error and force a system erase but not work again.
Thought i'd found the solution with the EDOs rom but then realised I had no bluetooth and had problems with mobile data.
After many efforts i found a way by simply installing the excellent Helios PRO kernel and manually installing Magisk after.
So I offer you the way i found to root my phone with Stock Oreo 8.1
A step by step breakdown of the method I used to fully root the fresh stock rom install.
First download the needed stuff
Latest Samsung Odin software. (3.13)
https://samsungodin.com/download
Download Link:
https://samsungodin.com/download/Odin3_v3.13.1.zip
USB Drivers.
https://samsungodin.com/SamsungUSBDriver/USB_Drivers_1.5.27.0.rar
New Oreo 8.1 Stock ROM
https://www.sammobile.com/firmwares/galaxy-j5/SM-J530F/BTU/
Download Link: https://www.sammobile.com/firmwares/galaxy-j5/SM-J530F/BTU/download/J530FXXU3BRL1/252803
***************************************************
*************TWRP
*******************************
https://github.com/TwrpBuilder/andr...s/tag/TWRP-3.2.3-TwrpBuilder-2018-09-13_15-34
Download Link: https://github.com/TwrpBuilder/andr...2.3-TwrpBuilder-j5y17lte-2018-09-13_15-34.tar
**************************************************
The Helios Pro Kernel
https://forum.xda-developers.com/ga...velopment/kernel-refined-kernel-v1-0-t3675500
Note if you are not installing from fresh stock roms Helios kernel says...
If you have flashed Root through any means other than magisk, Please uninstall it (SuperSU>Full unroot)
Magisk , (All J5 roms kernels i installed that said they had magisk pre-installed never actually worked on my phone)
so I downloaded the files to manually install Magisk.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
I used the main zip file and the manager apk
https://github.com/topjohnwu/Magisk/releases/download/v18.1/Magisk-v18.1.zip
https://github.com/topjohnwu/Magisk/releases/download/manager-v7.0.0/MagiskManager-v7.0.0.apk
Note: developer mode and OEM unlocking need to be enabled for most of these steps but many of the steps undo the settings so will need to be reapllied at various stages.
enable developer mode on phone by going to Settings/About phone/Software settings and keep pressing "Build Number" till developer mode activates then go back to main settings page and select "Developer Options" and make sure developer mode is enabled and USB debugging (i guess) and "OEM Unlock"
Method...
1. unpack Odin software and right click Launcher icon and select properties
Go to Compatibility settings and select Vista (service pack 2) compatibility.
Click okay and launch the Odin program.
2. Install stock ROM
Unpack the Oreo 8.1 files and use the buttons in Odin to load the BL , AP, CP and CSC files into each slot
Put phone into "Download Mode" by powering off and holding volume down - , home, and power buttons together till the screen pops up telling you to now press volume up to go to download mode.
Then plug in USB to computer.
Odin should report "Added" if you have correct samsung drivers on PC.
Then press "Start" in Odin.
Stock roms should all download to phone then it reboots.
***************************************************
3. Flash TWRP
Boot up phone, log into an account and get it all running then enable developer mode again.
Once set copy the Helios pro kernel zip file and the magisk zip and apk files to the phones SD card.
Now power down the phone and put it in download mode again.
Load Odin again and now put only the TWRP installer .tar file into the "AP" slot then select the "Options" tab in Odin and uncheck the auto reboot option. then hit start and flash twrp.
***************************************************
Load TWRP an install helios kernel
After flashing TWRP hold down the phones volume-down, home and power buttons and as soon as the screen goes blank immediately change volume down for volume up while still holding home and power.
then TWRP should load
Go to Wipe and select "Format Data" type yes to proceed , then back to wipe, select advanced wipe and wipe internal storage.
then back to TWRP main page and select "Install", select micro-sd card and point installer to the Helios Kernel zip file and install.
Install Magisk Manager app:
After booting up i still had no root so i installed the Magisk Manager apk using the "My files" app and launching it confirmed still no Magisk installed.
(I cannot recall if i had to go through the "Enable developer mode" again at this point but check if you need to or not)
Last Step, Manually Install Magisk.
Lastly I powered down the phone and held volume up, home and power key to launch TWRP
There i selected Install and installed the Magisk.zip file from SD card.
Finally the system booted, everything was working and i had root via an installed and working Magisk
Hope this helps someone..
palmbeach05 said:
Straight from post #1 of that thread. Notice the starred parts below.
After updating my J5 2017 J530F to the latest Oreo 8.1 I was having trouble getting root and all things working again.
Hours of waiting for installs then something going wrong after applying the CF-Auto-root or trying to install Magisk or something and having to install again, Hours spent waiting..
Trying to install the auto-root would cause a verification error and force a system erase but not work again.
Thought i'd found the solution with the EDOs rom but then realised I had no bluetooth and had problems with mobile data.
After many efforts i found a way by simply installing the excellent Helios PRO kernel and manually installing Magisk after.
So I offer you the way i found to root my phone with Stock Oreo 8.1
A step by step breakdown of the method I used to fully root the fresh stock rom install.
First download the needed stuff
Latest Samsung Odin software. (3.13)
https://samsungodin.com/download
Download Link:
https://samsungodin.com/download/Odin3_v3.13.1.zip
USB Drivers.
https://samsungodin.com/SamsungUSBDriver/USB_Drivers_1.5.27.0.rar
New Oreo 8.1 Stock ROM
https://www.sammobile.com/firmwares/galaxy-j5/SM-J530F/BTU/
Download Link: https://www.sammobile.com/firmwares/galaxy-j5/SM-J530F/BTU/download/J530FXXU3BRL1/252803
***************************************************
*************TWRP
*******************************
https://github.com/TwrpBuilder/andr...s/tag/TWRP-3.2.3-TwrpBuilder-2018-09-13_15-34
Download Link: https://github.com/TwrpBuilder/andr...2.3-TwrpBuilder-j5y17lte-2018-09-13_15-34.tar
**************************************************
The Helios Pro Kernel
https://forum.xda-developers.com/ga...velopment/kernel-refined-kernel-v1-0-t3675500
Note if you are not installing from fresh stock roms Helios kernel says...
If you have flashed Root through any means other than magisk, Please uninstall it (SuperSU>Full unroot)
Magisk , (All J5 roms kernels i installed that said they had magisk pre-installed never actually worked on my phone)
so I downloaded the files to manually install Magisk.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
I used the main zip file and the manager apk
https://github.com/topjohnwu/Magisk/releases/download/v18.1/Magisk-v18.1.zip
https://github.com/topjohnwu/Magisk/releases/download/manager-v7.0.0/MagiskManager-v7.0.0.apk
Note: developer mode and OEM unlocking need to be enabled for most of these steps but many of the steps undo the settings so will need to be reapllied at various stages.
enable developer mode on phone by going to Settings/About phone/Software settings and keep pressing "Build Number" till developer mode activates then go back to main settings page and select "Developer Options" and make sure developer mode is enabled and USB debugging (i guess) and "OEM Unlock"
Method...
1. unpack Odin software and right click Launcher icon and select properties
Go to Compatibility settings and select Vista (service pack 2) compatibility.
Click okay and launch the Odin program.
2. Install stock ROM
Unpack the Oreo 8.1 files and use the buttons in Odin to load the BL , AP, CP and CSC files into each slot
Put phone into "Download Mode" by powering off and holding volume down - , home, and power buttons together till the screen pops up telling you to now press volume up to go to download mode.
Then plug in USB to computer.
Odin should report "Added" if you have correct samsung drivers on PC.
Then press "Start" in Odin.
Stock roms should all download to phone then it reboots.
***************************************************
3. Flash TWRP
Boot up phone, log into an account and get it all running then enable developer mode again.
Once set copy the Helios pro kernel zip file and the magisk zip and apk files to the phones SD card.
Now power down the phone and put it in download mode again.
Load Odin again and now put only the TWRP installer .tar file into the "AP" slot then select the "Options" tab in Odin and uncheck the auto reboot option. then hit start and flash twrp.
***************************************************
Load TWRP an install helios kernel
After flashing TWRP hold down the phones volume-down, home and power buttons and as soon as the screen goes blank immediately change volume down for volume up while still holding home and power.
then TWRP should load
Go to Wipe and select "Format Data" type yes to proceed , then back to wipe, select advanced wipe and wipe internal storage.
then back to TWRP main page and select "Install", select micro-sd card and point installer to the Helios Kernel zip file and install.
Install Magisk Manager app:
After booting up i still had no root so i installed the Magisk Manager apk using the "My files" app and launching it confirmed still no Magisk installed.
(I cannot recall if i had to go through the "Enable developer mode" again at this point but check if you need to or not)
Last Step, Manually Install Magisk.
Lastly I powered down the phone and held volume up, home and power key to launch TWRP
There i selected Install and installed the Magisk.zip file from SD card.
Finally the system booted, everything was working and i had root via an installed and working Magisk
Hope this helps someone..
Click to expand...
Click to collapse
Hi,I see you forgot to install no verity encrypt,rmm state bypass. I would not recommend this method in any way to beginners(coming from an intermediarre or how that word is i am not native english) because you will then have RMM prenormal and you cant remove encryption ( most magisk modules dont work)
j5
hello, please i need any md5 rom for j5 because i have a problem on my system everything has stopped and my power button not working i cant delete wipe and cache and when i download twrp from odin to my phone its fail and its blocked by frp please im really need help
Does not remove the DM-verity problem
ExtremeGrief said:
Hi,this is the beginners guide in rooting the Galaxy J5 Pro.
First I want you to know that J5 Pro is the same as J5 2017.
You will need some files:
Opt verity Encrypt - http://download.highonandroid.com/file/Tools/Root/Samsung/no-verity-opt-encrypt-6.0-star.zip
RMM State Bypass Mesa - http://download.highonandroid.com/file/Tools/Root/Samsung/RMM-State_Bypass_Mesa.zip
Magisk 19.1 - https://github.com/topjohnwu/magisk_files/raw/master/canary_builds/magisk-release.zip
Magisk Manager 7.1.2 - https://github.com/topjohnwu/magisk_files/raw/master/canary_builds/app-release.apk
(Optional)(For Pie) Helios Pie Kernel - https://androidfilehost.com/?fid=1395089523397966358
(Optional)(For Oreo) Helios Pro Kernel - https://androidfilehost.com/?fid=1395089523397913077
(Optional) Promotheus One UI (Pie ROM) -https://androidfilehost.com/?fid=1395089523397940329
(Optional) Promotheus Lite (Oreo ROM) -https://androidfilehost.com/?fid=1395089523397887684
TWRP 3.3.0-0 - https://github.com/ananjaser1211/an...3.3_J7Y17LTE/TWRP-3.3.0-j7y17lte-20190417.tar
Odin - https://odindownload.com/download/Odin3_v3.13.1.zip
Stock ROM (In case of Soft bricking you can save your device) - https://s3.wasabisys.com/updatofw/GALAXYJ5/SM-J530F/BTU/SM-J530F_1_20190405203714_44wceovclw_fac.zip
Samsung USB Drivers - https://developer.samsung.com/common/download/check.do?actId=698
Copy the No Verity OPT Encrypt file,RMM State Bypass,What kernel u need,The rom u need,Magisk and Magisk Manager APK to ur SD Card.
Enable Developer options(Go into About phone,Software information,Tap several times on Build number until it says you are a developer.
Then go to Settings > Developer options > Check Oem UNLOCK and USB Debugging.
If you broke your device go to last lines(down)
If you already downloaded the files lets begin!
1.Turn off your phone and boot into download mode (Hold Volume Down,Home and Power and them press Volume UP)
2.Install Samsung USB DRIVERS on PC
3.Connect your Phone to your PC by USB Cable.
4.Open odin and load the twrp tar in AP slot.
5.Go to options and uncheck Auto Reboot
6.Click start
7.When in ODIN it shows PASS,Hold Volume Up,Home and power until the screen turns black then immiediately release and Hold Volume UP,Home and Power until the TWRP Screen Appears.
8.Tap on Keep Read Only and then Wipe and Format Data.Type "yes" without ".
9.Tap on Reboot and then Recovery
10.Tap on install then on Select Storage And Micro SDCard.
11.Press on No verity Opt Encrypt and swipe.
12.Press back button and Install RMM State Bypass Mesa.
13.Press back button and Install Magisk.
14.Tap on Wipe Cache and Dalvik and Then Swipe
15.Press the middle button(Home) and Tap on Reboot and then System.
16.Wait for the phone to boot and configure it.
17.Enable Developer options again and enable OEM Unlock and USB Debugging.
18.Disconnect Your Phone from the PC.
If you just wanted Root, You are Done.
Install Helios Pro Kernel to Stock ROM -
1.Go into recovery
2.Install > Select Storage > Helios Pro Kernel file
3.Swipe
4.Wipe Cache and Dalvik and Reboot to System.
If you dont pass SafetyNet :Go to Magisk > Modules > And disable BusyBox for Android NDK.
Install Custom Rom -
1.Boot Into TWRP (When powered OFF Hold Volume UP,Home and Power)
2.Go to Wipe and Select System,Data,Cache,Internal Storage and swipe.
3.Then click on Wipe and Format Data. (Recommended)
4.Go to Install and select what ROM you want to Install:
-Promotheus One UI (Pie ROM)
-Promotheus Lite (OREO ROM)
Click on First "Click to show content" for Promotheus One UI
Click on Second "Click to show content" Promotheus Lite
1.In Aroma Installer Click next and agree to the terms and conditions
2.Then click Full Wipe.
3.Select What Mods you want
4.Select what BloatWare you want.
5.Click Install.
6.After its done Reboot.
7.After ~15 seconds of the Samsung Logo Hold Volume Down,Home and Power then release when the screen turns black.
8.After it boots it will be laggy.Complete the setup and connect to Google and Samsung Account and update everything first ftom Galaxy Store then from Play store.Then reboot and it will not be laggy.
9.You will see that you dont have root, to fix this Reboot into Recovery (You know the procedure) and go to Install > Select Storage > MicroSD Card > HeliosPie Kernel 3.1 and swipe.
10.Wipe Cache and Dalvik and reboot.
11.After it boots you will have Root and a Pie Custom Rom!
12.If you do not pass Safety Net,Go to Magisk > Modules > And disable BusyBox for Android NDK.
You are Done! Now install your favorite apps!
1.Boot into Recovery
2.Install > Promotheus Lite A8+
3.In Arome click Next and Agree to the Terms and Conditions.
4.Select your Mods
5.Select your BloatWare
6.Tap on Install and Reboot to System.
7.After ~15 seconds of The Samsung LOGO and then Hold Volume Down,Home and Power and Release when the screen turns black.
8.After the phone boots it will be very laggy.Complete the setup and connect to Google and Samsung Account and update everything From Galaxy Store and Play Store.
9.You will see you dont have root.Boot into Recovery and Tap on Install > Select Storage > Micro SDCard > Helios Pro Kernel.
10.Reboot to System.
11.You are done
If you dont pass SafetyNet :Go to Magisk > Modules > And disable BusyBox for Android NDK.
If you Soft Brickes your device, open odin. Hold Volume Down,Home and Power until you are in download mode.
In odin select BL in BL box
AP in AP box
CP in CP box
CSC in CSC box (Important select CSC not Home_CSC)
Click Start and wait.
Your device will boot.
Finish the setup and enable developer option blah blah blah (Try Again)
If you dont see Oem unlock,You need to wait 7 days.
So thats it! If you have any problem reply!
Click to expand...
Click to collapse
The TWRP recovery does not stay there.
When flashing the "No verity Opt Encrypt", it fails with an error message in red. Only genuine binaries can be flashed.
Is there a simple answer to this ?
I've re-installed my stock ROM for now, no Root or TWRP.
Thank you.
Nice custom roms
I want to install TWRP on my Umidigi F1 so I can root it and install custom roms and all that
I am using the latest version of SP Flash Tool from here and the most recent stock rom from here to flash this TWRP 3.2.3 Image.
Everything works fine, but after flashing, if I try to boot into recovery (which I think is Power + Volume Up) it says
Code:
Red State
Your device has failed verification and may not work properly
Please download recovery image with verified signature or disable verified boot
Rebooting in 5 seconds....
And then it just reboots into normal Android.
From there on, it acts as if I hadn´t done anything and booting into recovery again just shows me the Android thingy and says
Code:
No Command
Booting with Volume Down always brings me to some chinese things I don´t understand but that very much looks like some kind of recovery to me as well.
Note that I have enabled USB Debugging and OEM unlocking in the settings and that SP Flash Tool states "Download OK" like it does after successfully flashing.
Now can someone help me installing TWRP on my F1?:angel:
Thank you for any help
Oh btw I just noticed this somehow didn´t end up in the Umidigi F1 section and I can´t figure out how to put it there either
So if you could tell me how, that´d be awsome
PHH aosp gsi confirmed to boot on BOLD-N1.
Need to be fully stock
--boot
--vendor
--recovery
Restoring device to factory condition , see this thread
Download PHH-AOSP 10
Download will be a compressed file *.gz , ectract the *.img file from inside
.
Code:
fastboot flash system **extracted-GSI.IMG**
fastboot oem reboot recovery
Perform factory reset inside stock recovery.
my tests trying to complete these steps with twrp all end with unknown imei.
V203 boots with only found issue is the fingerprint sensor Not working. For me i feel mtk devices are not secure anyway, the fingerprint sensor is more of a gimmick, so if it is not working, i do not care.
Current version v215 tested by and boots fine.
https://github.com/phhusson/treble_experimentations/releases
Things to consider
WHAT WORKS:
audio -music and speaker phone
camera-front and back (yes pop-up camera works)
video-camera front and back
video playback --(tested youtube in browser) - recorded video playback
Phone calls
messages
auto rotate
brightness
wifi tethering
mtp
flashlight
lift to wake (needed to turn off then on to activate it)
adaptive brightness
dark theme
gps
WHAT DOESN'T:
--Fingerprint
--phone works/ but dialer app has message that device is unsupported
--off-mode charging -- when charging with phone off, bootloader logo screen stays on, instead of battery icon
--screen recording-- after enable dev option // feature flag // settings_screenrecord_long_press .. you can access
screen record from long press power menu, long press screenshot menu, but recording will not save or stop
recording.-- setting option to on does not survive reboot
-- screen shot -- taking screen shot forces a bug report creation. (maybe this is not an issue, only a setting)
.
So I actually have to go back to stock since I'm running magisk? Is that why when I try flashboot flash vbmeta vbmeta.img it comes back as unknown file/directory?
Sergeantslaughter said:
So I actually have to go back to stock since I'm running magisk? Is that why when I try flashboot flash vbmeta vbmeta.img it comes back as unknown file/directory?
Click to expand...
Click to collapse
our device does not have VBmeta
the directions that say flash VBMETA, say use the stock meta file from stock firmware. so because that file is not used here, this is why you get the error message, ......
actually from your command you did not tell fastboot the location of the file you are trying to flash Unless you have a file called "vbmeta.img" in the current command terminal location. But again back to my original statement, our device does not have this file, so IF you do have the file, it is from other device anyway.
I guess I see how to flash the gsi but how do I get twrp installed?
mrmazak said:
PHH aosp gsi confirmed to boot on BOLD-N1.
only one permission file needed to be added. This is also expected to be included in the next release anyway.
Need to be fully stock
--boot
--vendor
--recovery
fastboot flash system **GSI.IMG**
fastboot oem reboot recovery
perform factory reset inside stock recovery.
my tests trying to complete these steps with twrp all end with unknown imei.
tested version was AOSP 10.0 v201
V203 boots without having to add the extra permission XML file.
Current version v204 not tested yet.
https://github.com/phhusson/treble_experimentations/releases
additional step to get version lower than v203 to boot
Download the additional permission file from
https://github.com/phhusson/device_...0.0/privapp-permissions-me.phh.treble.app.xml
While system is on boot animation screen. (this is as far as it will go on its own)
After the adb push, for me at least, the phone starts to continue its boot operation. Still do the reboot anyway.
Click to expand...
Click to collapse
So I haven't been able to find a twrp.img file for bold n1. Sorry if I sound stupid but this is my first time doing this. I had root with magisk and something screwed it up, and my phone was reading SIM cards. I uninstalled magisk and am back stock with an unlocked bootloader ...can you possibly walk me through installing twrp and flashing the Android 10 files? I would be so appreciative!
Sergeantslaughter said:
I guess I see how to flash the gsi but how do I get twrp installed?
So I haven't been able to find a twrp.img file for bold n1. Sorry if I sound stupid but this is my first time doing this. I had root with magisk and something screwed it up, and my phone was reading SIM cards. I uninstalled magisk and am back stock with an unlocked bootloader ...can you possibly walk me through installing twrp and flashing the Android 10 files? I would be so appreciative!
Click to expand...
Click to collapse
I have not been using twrp with GSI, but if you want to try goto twrp thread. Note that the twrp is currently only working with adb command line interface. No touch screen activity.
start by looking at the threads here. You will find twrp thread there.
So I've got Android 10 up and running...so can I just go ahead and root with magisk? Or will that mess up what I just did?
Sergeantslaughter said:
So I've got Android 10 up and running...so can I just go ahead and root with magisk? Or will that mess up what I just did?
Click to expand...
Click to collapse
aosp has root built in. If you prefer majisk, you need to first remove the included -su, and then need to use PHH-Majisk, not standard version.
Information on that should be found in gsi thread. It is not device specific.
ok so i had 10 working without twrp.....went to flash twrp...flash success....reboot to recovery...screen went black and CAN NOT get the device to power back on.....no vibrate no power no nada......wtf do i do?!?!?!
Sergeantslaughter said:
ok so i had 10 working without twrp.....went to flash twrp...flash success....reboot to recovery...screen went black and CAN NOT get the device to power back on.....no vibrate no power no nada......wtf do i do?!?!?!
Click to expand...
Click to collapse
you do know the screen in twrp has long delay before turns on. Do you have adb access to device?
if twrp is dead to adb, then
not sure why it would do that. but , i would first flash stock recovery with spflash tool
mrmazak said:
not sure why it would do that. but , i would first flash stock recovery with spflash tool
Click to expand...
Click to collapse
will that work? i cant get my phone to power on at all and adb is not recognizing it...
mrmazak said:
you do know the screen in twrp has long delay before turns on. Do you have adb access to device?
if twrp is dead to adb, then
not sure why it would do that. but , i would first flash stock recovery with spflash tool
Click to expand...
Click to collapse
everything is dead....phone no power or vibration while pushing buttons...no reaction when charging....adb says no device....fastboot the same
ive tried spflash tool but since computer isnt even detecting device, no luck.......im so upset. i just bought this phone.....the only kind of life i get is when plugging into windows laptop the connected "doop" sound for connected and then about 5 seconds later the same sound for disconnect.....repetitively and its driving me crazy
when trying to install the vcon drivers for spflash as the log is running says finish because its not detecting, but then says detected and drivers are newer what is trying to be installed...then not detected again
any advice? any chance at saving my phone??
Sergeantslaughter said:
everything is dead....phone no power or vibration while pushing buttons...no reaction when charging....adb says no device....fastboot the same
ive tried spflash tool but since computer isnt even detecting device, no luck.......im so upset. i just bought this phone.....the only kind of life i get is when plugging into windows laptop the connected "doop" sound for connected and then about 5 seconds later the same sound for disconnect.....repetitively and its driving me crazy
when trying to install the vcon drivers for spflash as the log is running says finish because its not detecting, but then says detected and drivers are newer what is trying to be installed...then not detected again
any advice? any chance at saving my phone??
Click to expand...
Click to collapse
That repeating sound is sign of bootloop.
Spflash tool is the recommended repair tool.
Download the factory restore package,
Extract the downloaded file.
Open flashtool, select scatter file from the extracted download. Ensure tool is on "download only" mode
Clear all select boxes in the tool window. Put check only in the recovery line.
Press download button, plug USB into phone. The bootloop in the phone is enough to make connection start.
What twrp did you use, where did it come from. Did you verify md5 of the downloaded file.
The only twrp I found was the one I shared, and it did not cause that kind of issue for me. So maybe you did something that you didn't mention?
I think I found the culprit... I download a file called "twrp" that actually turned out to be orangefoxrecovery... So I'm pretty positive that that's what caused it... Also, I've got a green check mark that says download OK.... Yellow bar at bottom of screen says recovery download flash 100%... What is my next step sir...?
---------- Post added at 05:11 AM ---------- Previous post was at 05:06 AM ----------
By the way I just wanna say you're awesome and thank you so much for your help!, this is my first time trying to do all this and I'm grateful to have someone so knowledgeable to save my a$$! Thanks man!
Sergeantslaughter said:
I think I found the culprit... I download a file called "twrp" that actually turned out to be orangefoxrecovery... So I'm pretty positive that that's what caused it... Also, I've got a green check mark that says download OK.... Yellow bar at bottom of screen says recovery download flash 100%... What is my next step sir...?
---------- Post added at 05:11 AM ---------- Previous post was at 05:06 AM ----------
By the way I just wanna say you're awesome and thank you so much for your help!, this is my first time trying to do all this and I'm grateful to have someone so knowledgeable to save my a$$! Thanks man!
Click to expand...
Click to collapse
Oh, last step is unplug USB. Then long press power button.
10 second should do. But maybe 20
Sergeantslaughter said:
everything is dead....phone no power or vibration while pushing buttons...no reaction when charging....adb says no device....fastboot the same
ive tried spflash tool but since computer isnt even detecting device, no luck.......im so upset. i just bought this phone.....the only kind of life i get is when plugging into windows laptop the connected "doop" sound for connected and then about 5 seconds later the same sound for disconnect.....repetitively and its driving me crazy
when trying to install the vcon drivers for spflash as the log is running says finish because its not detecting, but then says detected and drivers are newer what is trying to be installed...then not detected again
any advice? any chance at saving my phone??
Click to expand...
Click to collapse
Same happened to me, ended up fixing issue by using spflah tool (latest) and updated stock rom (mrmazak posted it) ?
I haven't bought the N1 yet but just might thanks to @mrmazak testing! Anyone tried Q v204 yet? Also curious if PHH regular Pie is bug free.
mrmazak said:
PHH aosp gsi confirmed to boot on BOLD-N1.
Need to be fully stock
--boot
--vendor
--recovery
Restoring device to factory condition , see this thread
Download PHH-AOSP 10
Download will be a compressed file *.gz , ectract the *.img file from inside
.
Code:
fastboot flash system **extracted-GSI.IMG**
fastboot oem reboot recovery
Perform factory reset inside stock recovery.
my tests trying to complete these steps with twrp all end with unknown imei.
V203 boots with only found issue is the fingerprint sensor Not working. For me i feel mtk devices are not secure anyway, the fingerprint sensor is more of a gimmick, so if it is not working, i do not care.
Current version v204 not tested by me yet.
https://github.com/phhusson/treble_experimentations/releases
Click to expand...
Click to collapse
Do not tell me in v 203 which version to download? I tried several but all to no avail
elephone p8000
any insight as to why every computer i plug my bold n1 into it shows up as a elephone p8000?
and on that note, say i found a working twrp for the elephone p8000 would that be possible?
i lost my root and android 10 due to bootloop. i used spflash to restore stock pie firmware. but now no matter what method or gsi or rom i try to flash my phone just will not accept it. The flashing is always successful, but upon reboot, i get a yellow/green screen flash followed by boot anim boot loop? any idea what would be causing this? i cant for the life of me figure out why my phone wont accept any system imgs i try to flash..
Sergeantslaughter said:
any insight as to why every computer i plug my bold n1 into it shows up as a elephone p8000?
and on that note, say i found a working twrp for the elephone p8000 would that be possible?
i lost my root and android 10 due to bootloop. i used spflash to restore stock pie firmware. but now no matter what method or gsi or rom i try to flash my phone just will not accept it. The flashing is always successful, but upon reboot, i get a yellow/green screen flash followed by boot anim boot loop? any idea what would be causing this? i cant for the life of me figure out why my phone wont accept any system imgs i try to flash..
Click to expand...
Click to collapse
Elephone p8000 is at least 3 years old. And would not think twrp from it will work on your bold n1.
As for why your PC shows your bold n1 as different phone, I can only guess that your PC drivers are somehow modified.
Or your phone is maybe not stock?
Hello everyone.
Small Intro:
So, I bought Note 10 [Exynos] N970F. I wanted to use custom rom on it. I tried both Dr. Ketan's ROM and 420 Rom. Both of these roms were surely amazing and Dr. Ketan's rooting guide really helped in rooting and all things. Such a kind person to help for new comer.
As there are only these two roms at the moment and AOSP roms are either not available or very old with incomplete guide to flash. So after trying many different ways for flashing Generic System image (GSI) for my device. After series of failures, bootloops as I surely found some method to actually install GSI on N970F
Tested GSI
Havoc 3.8
Descendants
CrDroid v222 200816
Type of GSI to Use for our device:
ARM64-AB (As known as ARM64-bvN)
What's working:
Sim/IRC
Calls
Data/4g
Bluetooth
Wifi
Camera
Storage
Sensors
NFC/Location/Hotspot
Bugs:
MTP/USB connection not working
FingerPrint not working with Descendants Rom
(Can't confirm any further bugs. If you found please report so I can update thread)
Don't do anything without reading 4th Post (Disclaimer)
Your phone's internal storage will be wiped, deleting all of your data so make a backup
Prep:
1: Download firmware for your phone (Extract firmware and copy AP file to phone)
Either Use Frija or This website (Make account here, connect to GDrive and you can download from google server or IDM. Fast, Resume)
2: Download TWRP for your phone (It is better to have TWRP based on same base as is your phone's firmware download)
See here for TWRP (Usually has updated twrp) or see telegram of developer
(Extract twrp zip to have recovery.img. If it has different name, save it as "recovery.img", We will call it twrp-recovery.
3: Download Magisk Manager, install on phone
4: Patch AP file you copied to phone with Magisk Manager (Run magisk manager, --Install --> Select & Patch file --> Select AP)
A new file "Magisk-Patched.tar" will be saved in download folder. Copy it to PC. We will call it Patched-AP.
5: Open Patched-AP with 7-Zip. You should see files in it. (There should be a recovery.img in it) Now drag & drop twrp-recovery to 7-Zip window open Patched-AP. Wait for process, as it will replace stock recovery with twrp recovery. We now have an AP file with magisk & TWRP pre-patched.
Now we will use this updated Patched-AP
6: Download Latest Multi-disable from here
7: Download your desired GSI. Havoc GSI, CrDroid GSI, Descendants,Others
(Download ARM64-AB or ARM64-bVN) If you want Google apps it is better to download GSI with built-in GAPSS.
Steps to Follow:
(Enable USB Debugging on your phone, Turn on OEM Unlock option in developers option)
1: First Unlock Bootloader of your device (Boot to download mode-- Power off, Volume up + volume down and connect to pc)
2: Follow on-screen instructions to unlock bootloader (While in download mode -- long press volume up for unlock area, volume up to unlock)
Info: Now phone will do wipe and you should be back into system. Now due to some Samsung restriction, you must enable USB debugging again & see OEM unlock check if greyed out (untouchable). (You must do it as system gives download mode a signal to prevent issue with custom files flashing)
3: Boot to download mode, Press volume up. Connect to PC.
4: Run Odin, Select files, AP as Patched-UP we created, CSC as Home-CSC, CP and bootloader that your extracted.
(Uncheck auto-reboot in odin)
5: Start Flashing, wait for it to pass. Now we will boot to recovery from here
6: To boot into recovery, first we should exit download mode then boot to recovery during that process.
First Hold volume down + Power --> wait for screen to go black--> as soon as screen goes black--> leave all buttons --> now press Volume UP + Power --> Keep pressing until you boot into TWRP recovery.
7: Now Swipe to allow modifications --> Wipe --> Format Data --> type "yes" --> swipe. Wait for Wipe.
8: Now Click reboot --> Reboot to Recovery. Wait for Phone to boot back into TWRP recovery.
9: Again Swipe to allow modification. Connect to PC & Copy the Multi-Disable to phone.
10: Install Multi-Disabler --> Install --> Select Multi-Disable --> Swipe to flash. Wait for it. Reboot again to recovery.
11: Copy your downloaded GSI img to Phone. Select Wipe and do a factory reset.
12: Install GSI --> Install --> Select IMG --> Click on GSI image --> Select System partition to flash. It takes few seconds.
13: Now Reboot to System.
Phone Should be booted into new GSI installed
Credits:
IanMacD for Multidisable, TWRP
Dr.Ketan for excellent guides & such helpfulness
TopJohnWu for Magisk, patched AP
Respective GSI teams for their hard work
Reservation
2nd Reservation
Disclaimer:
Before proceeding, remember I’m not responsible for anything bad happened to your device by following this or any of my guide. I’m just trying to help. So always do it on your own risk…
Don’t blame me or Any other developer.
All tools here are developed by different personalities. I’m just providing a guide on using these tool. Always say thanks to me and them. And If possible, donate them. They really deserve it.
Thank you. Can i install on note 10 5G korea (N971N) with this method?
can i use this method with N971N ?