Database Develop

Firmware updates for the FE

Just received the August security patch.
Takes a while for the restart.

jah said:
Just received the August security patch.
Takes a while for the restart.
Click to expand...
Click to collapse
do you intend to keep your device stock/unrooted? i'm reluctant to take the update for fear of losing root.

cortez.i said:
do you intend to keep your device stock/unrooted? i'm reluctant to take the update for fear of losing root.
Click to expand...
Click to collapse
My Note FE is my prime device. Not keen to experiment too much.

ROOT?!
cortez.i said:
do you intend to keep your device stock/unrooted? i'm reluctant to take the update for fear of losing root.
Click to expand...
Click to collapse
I haven't found a reliable method of rooting my N935L model. I am dying to root it. Can you link me?

ClrDaLane said:
I haven't found a reliable method of rooting my N935L model. I am dying to root it. Can you link me?
Click to expand...
Click to collapse
i followed the same process to install the latest version of TWRP for the Note 7 and flash the latest version of SR1-SuperSU-v2.82-SR1-20170608224931.zip. that's how i rooted my 935K. so far, this process still works with the latest AQG6 release which is available from updato.com. NOTE: if you flash the full OEM ROM via Odin, be sure to backup your internal storage; i had to format data after flashing the OEM ROM.

cortez.i said:
i followed the same process to install the latest version of TWRP for the Note 7 and flash the latest version of SR1-SuperSU-v2.82-SR1-20170608224931.zip. that's how i rooted my 935K. so far, this process still works with the latest AQG6 release which is available from updato.com. NOTE: if you flash the full OEM ROM via Odin, be sure to backup your internal storage; i had to format data after flashing the OEM ROM.
Click to expand...
Click to collapse
Good to know. Do we still have adhell? I expect Google will want to see that app spiked ASAP. Also, whether you update OTA or flash the full firmware, you will need to format data to get root. I long ago routined this process so that it takes about an hour all told.

zamzenos said:
Good to know. Do we still have adhell? I expect Google will want to see that app spiked ASAP. Also, whether you update OTA or flash the full firmware, you will need to format data to get root. I long ago routined this process so that it takes about an hour all told.
Click to expand...
Click to collapse
correct, the format data requirement is a bit of a pain; however, i keep very little important "stuff" on internal storage and back up my external and internal storage once a week.

Have updated by flashing stock to clear Knox first. Adhell still works. Just as well: cannot install TWRP, neither Exynos variant. Not such a pain while adhell keeps ads out and allows me disable copious junk. Still, am I doing something wrong? Odin installs always a success (four times so far). Any other reports?
Perhaps we need a device specific variant now...

zamzenos said:
Have updated by flashing stock to clear Knox first. Adhell still works. Just as well: cannot install TWRP, neither Exynos variant. Not such a pain while adhell keeps ads out and allows me disable copious junk. Still, am I doing something wrong? Odin installs always a success (four times so far). Any other reports?
Perhaps we need a device specific variant now...
Click to expand...
Click to collapse
what do mean by flashing stock to clear Knox first? and you flashed build N935KKKU3AQG6? i had no problem flashing twrp-3.1.1-0-gracelte.img.tar (not the Korean version twrp-3.1.1-0-graceltekor.img.tar) using Odin 3.12. reboot to Download mode and be sure to untick Auto reboot. next load twrp-3.1.1-0-gracelte.img.tar to the AP slot, flash and when complete, reboot to recovery. my method is to hold the down-volume and power key until the phone turns off, then press and hold the up-volume key, the power key and the the home key until the device boots to TWRP.

cortez.i said:
what do mean by flashing stock to clear Knox first? and you flashed build N935KKKU3AQG6? i had no problem flashing twrp-3.1.1-0-gracelte.img.tar (not the Korean version twrp-3.1.1-0-graceltekor.img.tar) using Odin 3.12. reboot to Download mode and be sure to untick Auto reboot. next load twrp-3.1.1-0-gracelte.img.tar to the AP slot, flash and when complete, reboot to recovery. my method is to hold the down-volume and power key until the phone turns off, then press and hold the up-volume key, the power key and the the home key until the device boots to TWRP.
Click to expand...
Click to collapse
1. Probably clumsily expressed. I flashed the original AQFE stock to get out of root then updated that. I was dloading the AQG6 firmware at that time but rather than wait (when I could have flashed that instead) I went ahead.
2. Usually I flash TWRP, allow the restart, close down and reboot into recovery-TWRP. Didn't work this time - is this a significant change? Followed your method, which worked - except perhaps to underline that the device should remain connected to the PC while closing it down (otherwise it will automatically reboot). Thanks for taking the trouble to give detailed instructions.

Just received an update

jah said:
Just received an update
Click to expand...
Click to collapse
THX! :good:
I manually update,been a while since I last looked:
Just checked my Note FE & got the same update on the SK Telecom version.

why i did't reveice?
i use note fe too

Whats new?
Wysłane z mojego SM-N935K przy użyciu Tapatalka

https://www.sammobile.com/news/galaxy-note-fan-edition-updated-december-security-patch/
Samsung starts rolling out December patch for the Koreans Note FE users.

RicePlay33 said:
https://www.sammobile.com/news/galaxy-note-fan-edition-updated-december-security-patch/
Samsung starts rolling out December patch for the Koreans Note FE users.
Click to expand...
Click to collapse
This is an old one I guess. Found this new firmware on Sammoblie on 2017/12/13 but I cannot flash it at the moment.
Can anyone try it? Hope it will bring bixby voice to our Note Fe

Got my K-version updated through OTA, no Bixby.

cortez.i said:
what do mean by flashing stock to clear Knox first? and you flashed build N935KKKU3AQG6? i had no problem flashing twrp-3.1.1-0-gracelte.img.tar (not the Korean version twrp-3.1.1-0-graceltekor.img.tar) using Odin 3.12. reboot to Download mode and be sure to untick Auto reboot. next load twrp-3.1.1-0-gracelte.img.tar to the AP slot, flash and when complete, reboot to recovery. my method is to hold the down-volume and power key until the phone turns off, then press and hold the up-volume key, the power key and the the home key until the device boots to TWRP.
Click to expand...
Click to collapse
That's a bit unrelated but I was wondering : how did you managed to show your carrier name (AT&T) in the status bar ?
I've always tried but other than with root capabilities I've never been able to display it.

Just received January security patch.

Me too!
Sent from my SM-N935F using Tapatalk

[ROM][TMOBILE][S7_SM-G930T][Oreo Rooted]

I created a new ROM with WifiCalling: [ROM][TMOBILE][S7_SM-G930T][Oreo 8.0 Rooted][WifiCalling]
ROM last updated: 9/24/2018
Introduction:
HUGE thanks to the guys that got this going like root & figuring out hybrid stocks! This thread here is just my take and customization on what they already did. Ultimately, I wanted Oreo rooted & modded, but I couldn't find a single guide. And the ROMs that existed weren't exactly what I was looking for. I wanted something exclusive to Tmobile. So I did a ton of reading and compiled it all together into a HOPEFULLY easy guide to follow. PS If you like Samsung bloatware, this is NOT for you!
Description:
EXTREMELY debloated! Nearly bare minimum, while still retaining hardware functionality. Eg, Samsung Gallery & Camera exist so we get 4k recording, and there aren't errors when we pull up the Gallery to edit, etc.
Everything possible I replace Samsung with Google
Solid ROM, very fast
There are very few options in Aroma to limit issues & repeatability. There are many options once booted up after initial setup
If you hate Samsung SW and just want a solid working ROM with very few install options to get you up and running this is for you.
Aroma installer layout is a little wonky, apologies (If anyone knows how to fix this please chime in )
This will delete all of your data! This is the only way so don't ask. Backup your data!
Features:
Optional Tmobile Apps
Optional Google Apps
Root Features: See Downloads->Recommended Root Zip & thank him for his work!!
Debloated
Deodexed
De-Knoxed
Zipalign
Instant Face Unlock mod
Disable signature verification
S9 Dolby Atmos
Memory Saver
OperMax
More Toggles
Mulit User
Private Mode
Unlock Stock NetWork Speed
Build Prop Tweaks
Device Status Official
White Page
CallRecord
Capture and Record Screen
Remove Volume Safe Warning
Remove brightness Warning
Added Bike Mode
Allow fingerprint unlock after a reboot
Google MarkUp
Force always visible Free Form Menu item in notifications
Substratum Theme
Dual speaker
Samsung Weather
Samsung Video Editor and Trimmer
LancControl Mods:
Ui Mods
3Mint Clock
Gradient statusbar
Virtual Lock Home Recent Button
Phone Mods
Clock Face Setting Aod
AdAway
Dpi Changer
Disable/Enable Apps
Kernel Adiutor
TW Mods:
Adaptive Fast Charging
Wireless Fast Charging
Usb Plug in/out Wakeup
OutDoor Mode
HardKey Lights
TouchLight
Recents Menu Mods:
Tasks Changer
Blur recent and Notification Menu
Download Links:
Base.7z & Oreo_Kevin71246Modded_v1.zip
VoLTE Fix
Steps:
This will delete all of your data! If you continue, you acknowledge that the Author is NOT responsible for anything that happens to your phone!
Install Stock Oreo:
Download mode & Setup
Make sure you have latest device drivers setup on your PC
Enable USB Debugging on phone in Developer Settings
Boot phone into Download Mode:
Turn off your device
Press and hold Volume Down + Home + Power button
When you see the warning screen, release buttons & press Vol UP. Phone should say "Downloading..."
Download and unzip Base.7z to PC (This contains stock Oreo, ODIN, & root)
ODIN
Open ODIN on PC (\Base\Odin_313.exe)
Connect USB from PC to phone. ID:COM in Odin should turn Blue with a COM port
Select AP, BL, CP and CSC files from the \Oreo_Stock\Base\ folder for corresponding files
Select HERO2QLTE_USA_VZW.pit
Select Start
Finished: Phone will reboot & show Carrier screen for 3-5mins. Wait until Setup screen & go through quickly (bare minimum) since you'll wipe it again
Root Instructions: (+Flashfire, SuperSU)
Reboot phone into Download mode
Odin
AP: Select \Base\Root\AP_SM_G930_OREO_ENG_BOOT.tar
Start-> Wait for phone to boot to Android OS
Root
Double-click \Base\Root\cmd-here.exe & Type: root.bat [enter]
Option: 1 (Install Root No tweaks) (Or pick whatever you want)
OPTIONAL: (Testing, WIP...) Backup with Titanium Backup (or whatever) at this time the following apps so they work in the end: Visual Voicemail, Wifi...
OPTIONAL: (Testing, doesnt work. Please provide a fix if you know!) VoLTE Icon Fix: via FlashFire app: Flash OREO_VOLTE_ICON_HOTSPOT_FIX.zip (Flashes fine but doesnt fix it!!)
*Note: With this system root, do not update su binary. Disable notifications for SuperSU app. Don't flash any superuser zips in recovery that are not made by jrkruse
Install Custom Hybrid ROM
Download & copy Oreo_Kevin71246Modded_v#.zip to phone
Flashfire
Open Flashfire on phone
Red + symbol->Flash ZIP or OTA-> Select Oreo_Kevin71246Modded_v#.zip-> Default options-> Check mark-> Lighting bolt at bottom-> OK
Phone will reboot to Aroma
Aroma Setup
Choose options as desired (Use vol up/down+power buttons to select! Touch is offset so if you use this touch BELOW your option to select)
Use very Bottom Right "Next" button if you see multiple
*Wait 3-5min on loading screen. If it doesn't boot after 10min: Hold Vol Down+Pwr buttons (~10sec) until phone restarts. After restarts, IMMEDIATELY hold VolUp + Home buttons. Should say Recovery. Wipe Data/Factory & Wipe cache. Restart Phone. Should load to Setup.
OPTIONAL: Root: Follow "Root Instructions" above, again.
Followup-Steps:
Fix Dialer: Phone Settings->Apps->Menu->Default Apps->Calling App->Select Phone
Known Issues:
Wifi Calling not working despite flashing Tmobile Wifi & Tmobile Wifi Settings app
Visual Voicemail not working (disabled until we can figure this out)
VoLTE Icon wont go away despite flashing known working fixes
Changelog:
Version 1: First build
Immediate References:
[Rom][ALL_CARRIERS_G930_CRF1][Stock_Oreo_Hybrid][Safestrap_Preinstalled]
Root For S7/S7Edge Oreo And Nougat
Project L s7 Google/Samsung Oreo Rom CRF1 Base
Credits:
(Im copying/pasting credits from other links since so many people participated I dont want to miss anyone!)
- @jrkruse & @klabit87 for root
- @Lanc-City for ROM base
- @gustco for eng boot.img
- @Raymonf for modified odin
- @afaneh92 for safestrap
- @me2151 for finding this method
- @tytydraco for some instructions
- @mweinbach for some instructions
- @Craz Basics for xposed on non rooted
- @partcyborg for finding the root method!
- @elliwigy for being great help and original S8 root
- @rayan-refoua for boot animation
- @FatalONEM8 - For posting Oreo OTA
- @stang5litre
- @jds3118
- @Krog18
- @klabit87 for S7 Safestrap
- @amarullz Aroma Installer
- @mrRobinson for adaway
- @Chainfire for Flashfire
- @JaeKar99 for Reactor_BootAnimation
- echoe rom and noname rom
- stang5litre Test Group
- Please PM me if you were forgotten!

Reserved1

Reserved2

Reserved3

Ayy mentioned. Good work on the rom ?

Okay I don't know what's going on here but I have never talked to you or never given you permission to reuse my Rom/work this is stealing my rom is still being worked on this thread must come down this is not cool
IF YOU WANT TO share something Make your own Rom My Rom/Work is not to be reused in any type of way I put a lot of time and work into it

Lanc-City said:
Okay I don't know what's going on here but I have never talked to you or never given you permission to reuse my Rom/work this is stealing my rom is still being worked on this thread must come down this is not cool
IF YOU WANT TO share something Make your own Rom My Rom/Work is not to be reused in any type of way I put a lot of time and work into it
Click to expand...
Click to collapse
Meant no offensive at all, I assure you. Did I completely misunderstand the point of the xda community? I clearly gave you credit and didn't say I created this from scratch, rather pieced it together, literally what every Dev here does. I am not doing this for money. I mentioned & thanked you, which is probably how you found this thread. All I am trying to do is give back to the community. I spent a TON of time going through guides, updating what I found, creating a guide, and testing this - I didn't just rebrand it.
That said, I did use part of your work so I'll give you the choice: can I use part of your work and allow the xda community to benefit, or do you want me to remove your segment & Lanc app this comes with?
Btw see the post above yours. And shouldn't this chat be on PM? For reference, what I used from you was your apks so I didn't have to redownload & retest them and aroma script for a starting point, but the script is 90% different at this point.
Again, I did not mean to offend, but please let me know if I have your permission. Thank you

Good news! We got @Lanc-City 's blessing to continue to use his base ROM & LancControl app. This XDA community is AWESOME! Don't forget to go and check out his original Mod'd ROM: Project L s7 Google/Samsung Oreo Rom CRF1

VoLTE icon fix
Not sure if this will work for everyone. Download System UI Tuner by Zach Wander from Play Store. Once in menu, go to TouchWiz, scroll down to IMS VoLTE Icon and toggle on then off. I did not apply the fix that you have the link for above, and I was able to uninstall the app and the icon does not come back.

Hey, I am trying to use your ROM but after I flash the zip file and finish set up with Aroma and reboot, I get stuck in the boot screen where the rainbow colored X symbol is spinning. I followed the guide exactly so I'm not sure what I'm doing wrong. Maybe my default options in flash fire are not correct? All the boxes in that screen are unchecked. Should I mount /system read/write? I just hit the checkmark and flash. Also I did hit Install Root with Interactive Governor, if that makes a difference. Any help? Thanks.

infamouz421 said:
Hey, I am trying to use your ROM but after I flash the zip file and finish set up with Aroma and reboot, I get stuck in the boot screen where the rainbow colored X symbol is spinning. I followed the guide exactly so I'm not sure what I'm doing wrong. Maybe my default options in flash fire are not correct? All the boxes in that screen are unchecked. Should I mount /system read/write? I just hit the checkmark and flash. Also I did hit Install Root with Interactive Governor, if that makes a difference. Any help? Thanks.
Click to expand...
Click to collapse
deleted, wrong thread

infamouz421 said:
Hey, I am trying to use your ROM but after I flash the zip file and finish set up with Aroma and reboot, I get stuck in the boot screen where the rainbow colored X symbol is spinning. I followed the guide exactly so I'm not sure what I'm doing wrong. Maybe my default options in flash fire are not correct? All the boxes in that screen are unchecked. Should I mount /system read/write? I just hit the checkmark and flash. Also I did hit Install Root with Interactive Governor, if that makes a difference. Any help? Thanks.
Click to expand...
Click to collapse
Copying/Pasting PM I sent you for others, and added some things:
Did you let the "rainbow" sit there for at least 10 min? (It should be 3-5 but who knows.) Are you soft-bricked in your current situation? If you start again, at "Install Stock Oreo:" does this at least restore your phone back to stock Oreo? If so, then try again and proceed with ALL the remaining steps again, CAREFULLY reading the instructions again & again.
Also, what phone model do you have? And I admit I haven't tested the CPU governors in the root script ; I ALWAYS chose none - I'll remove those options in the next version since I have tested them and there are plenty of CPU overclocking options once booted inside the ROM.
If you are able to restart this process and get stock Oreo back, AND chose NO CPU governors in the root script, maybe you want to either try "NO" to Google & Tmobile options just to make sure you can get Android booted- If it boots fine, then try the ROM again and pick Google and/or Tmobile to isolate any issues (things that are breaking)
Have you used ONLY what I provided, such as ODIN (version is important), etc?
Re Flashfire: Default options should be fine. The ROM script will set all the partitions, mounts, permissions, etc.
Good luck!
*Above response I guess is for overall troubleshooting the ROM, if any issues present themselves.
On another note: I'm actively working on this ROM as time allows. Trying to ease the install process, correct some issues, further customize, & improve...

kevin71246 said:
Copying/Pasting PM I sent you for others, and added some things:
Did you let the "rainbow" sit there for at least 10 min? (It should be 3-5 but who knows.) Are you soft-bricked in your current situation? If you start again, at "Install Stock Oreo:" does this at least restore your phone back to stock Oreo? If so, then try again and proceed with ALL the remaining steps again, CAREFULLY reading the instructions again & again.
Also, what phone model do you have? And I admit I haven't tested the CPU governors in the root script ; I ALWAYS chose none - I'll remove those options in the next version since I have tested them and there are plenty of CPU overclocking options once booted inside the ROM.
If you are able to restart this process and get stock Oreo back, AND chose NO CPU governors in the root script, maybe you want to either try "NO" to Google & Tmobile options just to make sure you can get Android booted- If it boots fine, then try the ROM again and pick Google and/or Tmobile to isolate any issues (things that are breaking)
Have you used ONLY what I provided, such as ODIN (version is important), etc?
Re Flashfire: Default options should be fine. The ROM script will set all the partitions, mounts, permissions, etc.
Good luck!
*Above response I guess is for overall troubleshooting the ROM, if any issues present themselves.
On another note: I'm actively working on this ROM as time allows. Trying to ease the install process, correct some issues, further customize, & improve...
Click to expand...
Click to collapse
So I did let it sit for a long time, maybe like 30 mins, but nothing happened. So I tried again from installing from stock and repeating each step. I'm using the odin files you supplied. Same thing. I was using install Google Apps and No T-mobile apps, and interactive governor for both situations. Stuck on boot animation screen. I did not try the options you suggested above since I eventually got it to work. So while stuck on the boot animation screen, I just ended up holding the Vol down, power and home until it rebooted and said entering recovery mode and let go before it went into download mode. From there I just wiped data, and cache, which may not be necessary, and then rebooted, and everything works. Thanks.

infamouz421 said:
So I did let it sit for a long time, maybe like 30 mins, but nothing happened. So I tried again from installing from stock and repeating each step. I'm using the odin files you supplied. Same thing. I was using install Google Apps and No T-mobile apps, and interactive governor for both situations. Stuck on boot animation screen. I did not try the options you suggested above since I eventually got it to work. So while stuck on the boot animation screen, I just ended up holding the Vol down, power and home until it rebooted and said entering recovery mode and let go before it went into download mode. From there I just wiped data, and cache, which may not be necessary, and then rebooted, and everything works. Thanks.
Click to expand...
Click to collapse
That's odd since the installer does exactly that. But I added this to the guide. Thanks for the feedback!

Thanks for the tutorial. Deeply appreciate the effort you put in foraging the resources and putting all the pieces together. The rom works great and all but I can't seem to get the lockscreen to display the wallpaper. It's just black lol. The adaptive clock works however. Would be grateful if you could drop a fix for this.

Alkan3 said:
Thanks for the tutorial. Deeply appreciate the effort you put in foraging the resources and putting all the pieces together. The rom works great and all but I can't seem to get the lockscreen to display the wallpaper. It's just black lol. The adaptive clock works however. Would be grateful if you could drop a fix for this.
Click to expand...
Click to collapse
(Not sure why I didn't get an email from XDA for this post.) Mind walking me through the exact place this setting is? Here? PhoneSettings->Lock screen and security->Clock and Facewidgets->Clock Style->Select a style for "Lock screen" tab at top->Done? (Im able to get these to work)
BTW, Im glad you found this thread resourceful! & Im working on another one, which will be better & more original. Takes a TON of time!

Hey i have two questions, if i'm on oreo already do i need to flash base? And, does this need an unlocked bootloader?

nam2amna said:
Hey i have two questions, if i'm on oreo already do i need to flash base? And, does this need an unlocked bootloader?
Click to expand...
Click to collapse
Your stock oreo should work without issues but I always flash his stock firmware just in case(it's smoother too I think). And no, it doesnt require an unlocked bootloader.
Oh and happy modding

Alkan3 said:
Your stock oreo should work without issues but I always flash his stock firmware just in case(it's smoother too I think). And no, it doesnt require an unlocked bootloader.
Oh and happy modding
Click to expand...
Click to collapse
There are a couple ways an installer can work for custom rom mods like this: start with base then remove everything we don't want. OR: delete everything then add in what we want. This rom happens to work with the latter method. You can see why the base would be so important with the first method. (Because if we don't start with a given base then we can't predict the results because we don't know what u froze or deleted). Regardless, for expected & reliable results, I would always start with an Odin flash of stock for a rom like this. Roms like this are different than vanilla AOSPs because we strip what Samsung & tmobile brewed up, and we often then refer to it as a hybrid- as opposed to vanilla aosp which would be google only & only Samsung for drivers, etc. Hope that helps.

Btw I'm working on another rom with tmobile wifi calling working. I had to start from scratch, literally to get it working. Btw I'm curious if anyone else got it to work after the fact with a custom rom. If so, PLEASE chime in & let me know. Thanks!

[GUIDE]Unlocking Bootloader + Magisk Root for Huawei Mate 20 Pro

I read through quite a few post here to get everything sorted out and in order to save every one some time here is a summary of all the info I have gathered so far, and my way to thank the forum for offering me so many helpful tips. I'll try to keep this thread updated as information comes in.
All credit goes to their respective owners, I am only aggregating all the information here.
Current status on BL Unlock:
China version: OEM unlock not greyed out, direct BL unlock possible
EU/NA version (L09/L29/L0C): OEM unlock greyed out in developer options, BL unlock possible via FunkyHuawei method by upgrading to .170.
UPDATE 2019/01/02: Some users reported they have already received the .171 update from carrier (https://forum.xda-developers.com/showpost.php?p=78571337&postcount=6), if that is the case you can skip the FH Method part and go directly to unlock BL.
Note: Currently .170 is not GooglePay certified, so Google Pay won't work on this, if you must have Google pay please wait for your carrier to update to some version that support OEM unlock (tap build number 7x to get Developer Options in Settings -> System -> About Phone and then go to Settings -> System -> Developer Options and see if Enable OEM Unlock option is enabled).
Also current recovery install requires you to boot into recovery (Power and volume up with phone disconnected from USB) every single time if you want root, which is not perfect.
The only time you'd be required to wipe your phone is right after your BL is unlocked with fastboot OEM unlock, please make sure you have a backup before doing that step.
Where to get unlock code?
In order to get BL unlocked, you need both allow OEM unlock option NOT greyed out (i.e., you can enable it) AND a BL unlock code. BL unlock code can only be purchased either from FunkyHuawei (55 USD one time for BL unlock code only or if you buy an unlimited pass 132USD for unlimited flashing + BL unlock code (note that it is locked to your phone and can not be transferred)), or MinistryOfSolutions (30 Euro, https://ministryofsolutions.com/huawei-bootloader-unlock-service-all-new-models-new-firmwares, BL unlock code only).
FunkyHuawei Method (for non-China version)
1. Create an account in https://funkyhuawei.club/membersarea, buy 1 credit (if you just want to download .170 firmware, each credit cost 18USD).
2. Go to Select Firmware tab, use LYA-Global if you don't see the exact model. Then select .171 version.
3. Follow instructions here: https://pastebin.com/raw/Db5ZSyqu, you must download the specific HiSuite version (9.0.2.301）and the specific installer executable. Run the executable FHHiSuiteInstaller.exe as administrator (right-click and choose Run As Administrator) <- must run as admin since it will need to modify your host file. Make sure the script runs without error.
3.1 (Additional step for L0C): Edit the c:\users\YOURHOMEFOLDER\appdata\local\hisuite\userdata\updatedogdev\hisuiteconfig.xml file and change LYA-L29 to LYA-L0C everywhere it occurs and save the file. (Thanks to FunkyHuawei Support for pointing this one out).
4. Put the phone into fastboot mode (adb reboot-bootloader or with the phone off connect the usb cable while holding volume down, or boot the phone holding volume down with USB cable connected to PC).
5. Go to HiSuite on your PC and click on System Recovery (furthest to the right towards the bottom of the main screen), and let it do the magic. You will see some cmd windows pop up however it should get to the download progress with a percentage pretty fast, if you don't see that pop up then please check to make sure you have at least one credit in the FH Select Firmware tab and you have installed the specific versions of HiSuite and ran the installer as admin in Step 3.
6. Once everything is completed please verify to see if your firmware version is .171.
Unlock Bootloader
Again, get the BL code and go to Settings -> System -> Developer Options and make sure Enable OEM Unlock option is enabled. Also check to make sure you have everything backed up. Also enable USB Debugging in the same screen as well.
Rest is pretty standard:
Code:
adb devices (will bring up the authorization window on your phone, click on Always Trust)
adb reboot-bootloader
fastboot devices (make sure the device is in fastboot mode)
fastboot oem unlock *UNLOCK CODE*
at this point there will be a format operation performed on the phone, if it didn't complete successfully don't worry, your phone is wiped. During the boot you should see a black window with yellow text of warnings to tell you your phone is unlocked and not secured.
Go through all the steps to initialize the phone, turn on Developer options again, and enable USB Debugging again.
Root
1. Download and install Magisk Manager from this XDA post: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
2. Switch channel, go to Magisk Manager -> Settings -> Update Channel , set it to Custom, and the URL is https://bit.ly/2N8UVlq (at the moment, per https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337). Go back to main screen and down swipe to refresh, it should say Latest Version > v18.0.
3. You will need to find the stock RECOVERY_RAMDIS.img file, I used HW Firmware Finder (https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146) to help me with the task, however I couldn't find the L0C update file and ended up using L09 update file instead, which appear to work. I also couldn't find the update.zip for .171 so I ended up using the latest full update version that was available to me (http://update.hicloud.com:8180/TDS/...69/g1750/v181585/f1/full/update_full_base.zip).
4. Unzip the file, drag out UPDATE.APP file in the zip package, and opened it with Huawei Firmware Extractor (I used 0.9.9.5 in this thread: https://forum.xda-developers.com/showthread.php?t=2433454). Extract and open the UPDATE.APP in update file. If you get a checksum error make sure to uncheck both of the verify checksum in Settings -> Extract.
5. Now you should see a RECOVERY_RAMDIS.img file, right click and extract it.
6. Send the RECOVERY_RAMDIS.img file back to your phone (anywhere is fine), go back to Magisk Manager -> Install -> Patch boot, get the patched_boot.img file from the phone back to the PC.
UPDATE 2019/01/02: @pvillasuso was kind enough to post the ramdisk image (both original and Magisk modified) for Mate 20 Pro LYA-L09 (Firmware version .171):https://forum.xda-developers.com/showpost.php?p=78575496&postcount=13, obviously use it at your own risk.
7. Go to fastboot mode again:
Code:
adb devices
adb reboot-bootloader
fastboot devices
fastboot flash recovery_ramdisk "PATH_TO_patched_boot.img"
fastboot reboot
Now your phone should be back to normal with no root yet, turn off your phone and turn it back on by booting into recovery (Power and volume up with phone disconnected from USB)
Boot up and if you go to Magisk now you should be able to see Magisk installed with Installed Version same as Latest Version.
Congrats you are now rooted!
In future you will need to boot into recovery each time to maintain root (which requires you to turn phone off and power + vol up), if you prefer not to do so @ThatsJustLogic suggested you can use the app https://forum.xda-developers.com/showpost.php?p=78569733&postcount=2 to add a one-click reboot from your dropdown menu.
Credits:
@ThatsJustLogic - Figured out the installation steps to patch ramdisk: https://forum.xda-developers.com/showpost.php?p=78554707&postcount=125
@duraaraa - Guy behind FunkyHuawei for figuring out the .171 upgrade and make everything works smoothly https://forum.xda-developers.com/mate-20-pro/how-to/unlock-rebrand-unbrick-update-t3855065
@mutahharbashir - Guy behind MinistryOfSolutions for the unlock BL code.
And creators of Magisk, HWFirmwareFinder, HWUpdateExtractor.

zhuanyi said:
Now your phone should be back to normal with no root yet, turn off your phone and turn it back on by booting into recovery (Power and volume up with phone disconnected from USB)
Click to expand...
Click to collapse
To stop you needing to do this on every boot this app: https://play.google.com/store/apps/details?id=com.superthomaslab.rootessentials allows you to add a "Reboot Recovery" button to your notification tray so its just a one tap reboot instead of holding volume up when you want to reboot after applying a change or something its something small but it saves some hassle.

Awwsome, thank you so much. Now I can finally use Google pay on global firmware 9.0.0.171. It's working perfectly

This is amazing development

Hi, can someone post his oeminfo?

On firmware versions; I have an Australian L29 running an ota update v 168. Oem unlock is available, and Google pay works.

Thank you for the guide.
Can we re-brand from Chinese to international now?

thunderpossuem said:
On firmware versions; I have an Australian L29 running an ota update v 168. Oem unlock is available, and Google pay works.
Click to expand...
Click to collapse
How come? Can you post a screenshot with developer options on yhe screen?? Oh, you have. Can this mean that we will be able to unlock bootloader for free when v168 update arrives to other countries??
Sent from my LYA-L29 using XDA Labs

The 171 official firmware also allows OEM Unlock..
Maybe wait until you get the new update , save a few bucks

deepsrd said:
The 171 official firmware also allows OEM Unlock..
Maybe wait until you get the new update , save a few bucks
Click to expand...
Click to collapse
That's just what i thought
Sent from my LYA-L29 using XDA Labs

Thanks for the guide , Im rooted now !
One question , I have the patched_boot.img file , is it the same for everyone ?
I can share it and it will save some extra steps
Let me know

pvillasuso said:
Thanks for the guide , Im rooted now !
One question , I have the patched_boot.img file , is it the same for everyone ?
I can share it and it will save some extra steps
Let me know
Click to expand...
Click to collapse
The patched file will work for anyone who has the mate 20 pro and the same FW version as you. Theres no extra steps it just removes the finding the FW, extracting and patching the image yourself They will still need magisk and the canary channel.
If you are going to share I would specify Firmware version and attach a non patched one incase people have issues and want to revert.

My phone model : Mate 20 Pro LYA-L09 (Firmware version 9.0.0.211)
patched_boot.img > https://www.mediafire.com/file/fp3jk281d47bh6k/patched_boot.img/file
Apply on your own risk , worked for me !

Hi, glad to hear that even L0C model has to the chance to root. Just wondering after flash the global .171 version which should solve the OEM greyed-out problem, the next step is to purchase a BL unlock code? And is there a chance that after BL and FRP unlocked. My model (LYA-L0C) can be rebrand to another one?

deepsrd said:
The 171 official firmware also allows OEM Unlock..
Maybe wait until you get the new update , save a few bucks
Click to expand...
Click to collapse
Indeed it is 18 USD saved, also hopefully it is more compatible with your phone.

Can you give an example of your path to "PATH_TO_patched_boot.img"
I must be getting syntax incorrect for the file in internal storage download folder, and I have tried everything with and without / leaving out folders.

is this ota proof?

Some rooting questions....
Hi.
I will try to be brief and on topic. Feel free to remove post if not according to Xda forum rules.
Long story short. I am an heavy iOS user from the apple jailbreak scene. I am no developer (only user) and now I have taken the big step from IOS to Android.
Huawei mate 20 pro broke my curiosity. I have always "jailbroken" my iPhone since 2007 and now I am considering root of my HM20PRO.
I have some questions before I try this and brick my phone.
I have Norwegian model, LYA-L29 with 9.0.0.153 (c432) software. (BL unlock greyed out here as well)
How is the partitions setup on this device?
Easy explanation of RAM disk, main disk or whatever?
Do I always have the option to revert to stock setup no matter what? With simple erase/wipe/recover?
Is hisuite the recovery software to use if I want to go back?
Is it possible to unlock the boot loader and go back to 9.0.0.153??
Is the software builds so the highest number software has the latest fixes? (108,122,153,168,171 +++)
Do i loose the safety net like google pay, and other apps that can see that my phone is rooted?
Is there an app to run to trick the apps into believing that the phone is not rooted? (like on iOS)
Hope that someone can take the time to help me with my questions.
The boot via ramdisk/fastboot or what you call it to get rooted is only nesecary on each boot up right? You stay rooted until the next shutdown?
(Semi.tethered on iOS)
sorry for the noob questions, but I am new with this so thanks...
Regards,
Kenneth - Trondheim, Norway
PS:I have to say the switch from iOS to android and Huawei mate 20 pro have been great so far (except new replacement phone on the first day with green screen on BOE screen.) Now all is good.
Main reasons to root android?
I like to have different custom gestures through out the software. And also tweaked apps and notification tweaks, icons.

fromiOS2Android said:
Hi.
How is the partitions setup on this device?
Easy explanation of RAM disk, main disk or whatever?
Do I always have the option to revert to stock setup no matter what? With simple erase/wipe/recover?
Is hisuite the recovery software to use if I want to go back?
Is it possible to unlock the boot loader and go back to 9.0.0.153??
Is the software builds so the highest number software has the latest fixes? (108,122,153,168,171 +++)
Do i loose the safety net like google pay, and other apps that can see that my phone is rooted?
Is there an app to run to trick the apps into believing that the phone is not rooted? (like on iOS)
The boot via ramdisk/fastboot or what you call it to get rooted is only nesecary on each boot up right? You stay rooted until the next shutdown?
(Semi.tethered on iOS)
Main reasons to root android? I like to have different custom gestures through out the software. And also tweaked apps and notification tweaks, icons.
Click to expand...
Click to collapse
Hi, first of all, welcome to Android
My advice is to NOT root until you got an answer to all your questions
I'll let some pros answer the technical questions on the partitions) but here's what I can tell you:
- Main reason to root for me is adblockers and (not a must though) custom roms.
- There is a function within magisk to hide root from apps.
- On the fixes, yes, 171 is the one that allows root and that's also the latest one with all the fixes.
- Once you root you stay rooted, you don't have to repeat the whole process at every boot.
- From what I read in several threads, right now you can't revert to older firmwares. Also, the 171 seems to be market specific, what I will do is to wait until the update gets rolled out in my market by Huawei, I read that the unlock bootloader option is then available officially.
- I would also like to know about google pay (does it brake with root?) and are there other functions that break (camera functions,etc) like it does on other phones (sony for instance)

charliebigpot said:
- I would also like to know about google pay (does it brake with root?) and are there other functions that break (camera functions,etc) like it does on other phones (sony for instance)
Click to expand...
Click to collapse
Using Magisk Hide on Google Pay will prevent it from detecting root, however if SafetyNet fails then it probably still won't work.
There are a few Magisk modules that can (apparently) force SafetyNet to pass, however I haven't ever used any of them.

(Guide) Upgrade from Oreo to Pie/One UI (Snapdragon/SM-N960, SM-N960U1, SM-N960W)

Let me start off by stating that this is by no means my tutorial, all information was gathered from this community and organized into, hopefully, a helpful tut. Thank you to Max Weinbach, who originally posted this tutorial - due to issues with the file hosting server, that page hasn't been updated in a bit. Hopefully this will help in the meantime... And a big thank you to Venom0642 for hosting these files!
NO ROOT!!!
MUST BE SNAPDRAGON VARIANT (SM-N960, SM-N960U1, SM-N960W)
Optional: This will wipe the data on your phone. Use SmartSwitch to backup your phones data to your computer
Step 1: Download the 3 Items listed below (AT&T N960USQS1ARJA, Odin3, N960USQS1ARJA-U1CSA7)
Venom0642 said:
Download here: AT&T N960USQS1ARJA
Download here: Odin3_v3.13.1_3B_PatcheD
Click to expand...
Click to collapse
Venom0642 said:
Download here: N960USQS1ARJA-U1CSA7
Click to expand...
Click to collapse
Step 2: Copy or Move the "N960USQS1ARJA-U1CSA7.zip" file to your SD card and insert SD card into your Note 9 - If you do not have an SD card you can use ADB sideload to flash this .zip later in the process but I will not be going into much detail on this option. Skip this step if this is you and I will let you know when to use adb later on
Step 3: Unzip the "AT&T_N960USQS1ARJA" folder - Notice that you will have 5 files within this folder, we will only be using the 4 that begin with BL, AP, CP, and CSC
Step 4: Unzip the "Odin3_v3.13.1_3B_PatcheD" folder and launch the Odin3 executable
Step 5: Within Odin, click on the "BL" box and navigate to your "AT&T_N960USQS1ARJA" folder and select the corresponding file that beings with "BL". Do the same thing for the AP, CP and CSC fields within Odin, you can leave USERDATA empty - The BL, AP, CP, and CSC fields within Odin should now be populated with the "AT&T_N960USQS1ARJA" files
Step 6: Power down your phone. Once it is off, enter Odin mode by: holding Power button + Volume Down + Bixby button - Your phone may prompt you asking if you want to download a custom OS, press the Volume Up button to continue.
Step 7: Plug your Note 9 into your computer - If Odin is communicating with your phone, on the left hand side of the screen (odin on your computer), under "Log", you should see something like "Added!!"
Step 8: Hit "Start" within Odin - Your phone will now flash to N960USQS1ARJA and will automatically reboot into recovery mode when it is done. This will take a few minutes!
Step 9: You should now be in recovery mode. If you are not, power down your phone and boot into recovery by holding Power button + Volume Up + Bixby button. Use the volume keys to highlight "Wipe data/factory reset" , use the Power button to select it and select "Yes" to continue. - After the wipe completes, you will be brought back to the main menu of Recovery Mode
Step 10: Use the volume keys to highlight “apply update from SD card” and select it with the power key - If you do not have an SD card, this is where you would select "apply update from adb", open a command prompt/terminal on your computer and type: adb sideload <file location of N960USQS1ARJA-U1CSA7.zip>
Step 11: Now find the N960USQS1ARJA-U1CSA7.zip file that you put onto your SD card earlier by using the volume buttons to navigate and power button to select it - Your phone will now flash to N960USQU1CSA7 (Pie/OneUI) and will boot up normally when it is finished. This will take a few minutes!
Step 12: You are now on Android Pie. Walk through the normal startup menus and then use SmartSwitch to restore your data. Done!
Hope this helps a few people! I will try to keep this thread up to date with current builds as Venom0642 makes them available

I have a Snapdragon 845 U1 Unlocked version, using firmware.science it appears that I can upgrade directly to the Unlocked bloatfree firmware. Using your method I'll be upgrading to ATT version with ATT bloat. Is my understanding correct?

ceo.mtcl said:
I have a Snapdragon 845 U1 Unlocked version, using firmware.science it appears that I can upgrade directly to the Unlocked bloatfree firmware. Using your method I'll be upgrading to ATT version with ATT bloat. Is my understanding correct?
Click to expand...
Click to collapse
I do not know anything about the firmware science route, you would need someone else to help you there. But this version will have at&t bloat, you will have to disable the handful of apps they preload so you don't have to deal with them

Rwhyayn said:
I do not know anything about the firmware science route, you would need someone else to help you there. But this version will have at&t bloat, you will have to disable the handful of apps they preload so you don't have to deal with them
Click to expand...
Click to collapse
I went ahead and did that anyway and Viola! I have pie now. Just applied update

I'm running zrll what are the benefits running this over zrll? Does Samsung pay still work?

Does it work with every SD variant? Mine is SM-N9600 Brazil

Nice job on the tutorial!! I have been doing the Z beta builds, but have gone back to Oreo to wait for the official release!! Hopefully within the next week... but your guide here is very easy to understand and I'm sure it will help alot of people!!

Jaimesco12 said:
I'm running zrll what are the benefits running this over zrll? Does Samsung pay still work?
Click to expand...
Click to collapse
C builds add full support for carrier features. With T-Mobile, you get Advanced Messaging and a few other things I can't remember now. Samsung Pay works on all beta builds, just not Google Pay.

NotATreoFan said:
C builds add full support for carrier features. With T-Mobile, you get Advanced Messaging and a few other things I can't remember now. Samsung Pay works on all beta builds, just not Google Pay.
Click to expand...
Click to collapse
Ok gotcha, so this latest c build is still a beta? If not Will there be a path to just flash zip on the c builds when the official pie release comes out?

Cristiano Matos said:
Does it work with every SD variant? Mine is SM-N9600 Brazil
Click to expand...
Click to collapse
I don't think so, as far as I know you can't crossflash firmwares from different variants (in this Case N960U or N960U1 to N9600 or vice versa).
But I'm on the same boat, mine is also N9600 and eagerly waiting for any sign of Pie.
Have you seen the release notes for Pie in the members app? Make no sense to me.

Fota showing 1CSA8 lol.
Sent from my SM-N960U using XDA Labs

Venom0642 said:
Fota showing 1CSA8 lol.
Click to expand...
Click to collapse
Dam I just got on 7 lol

Venom0642 said:
Fota showing 1CSA8 lol.
Click to expand...
Click to collapse
I guess I'm skipping 7 lol

Thanks for tutorial.
One question, if I'm already on the N96OUSQS1ARJA build can I skip that part and go straight to the PIE upgrade? Or is there any reason I should install ARJA version your showing?
TIA
Sent from my SM-N960U using XDA Labs

LouK said:
Thanks for tutorial.
One question, if I'm already on the N96OUSQS1ARJA build can I skip that part and go straight to the PIE upgrade? Or is there any reason I should install ARJA version your showing?
TIA
Click to expand...
Click to collapse
If your on N96OUSQS1ARJA yes can go straight to 1CSA7 , so no need to odin to 1ARJA
Sent from my SM-N960U using XDA Labs

LouK said:
Thanks for tutorial.
One question, if I'm already on the N96OUSQS1ARJA build can I skip that part and go straight to the PIE upgrade? Or is there any reason I should install ARJA version your showing?
TIA
Click to expand...
Click to collapse
Happy to help brotha! Venom already answered your question, but yes you can do step 1 (even though you don't need all of those files) and step 2 and then skip right to step 9

Venom0642 said:
If your on N96OUSQS1ARJA yes can go straight to 1CSA7 , so no need to odin to 1ARJA
Click to expand...
Click to collapse
Thanks ....
So now I have something to do this weekend.....
Sent from my SM-N960U using XDA Labs

q173242 said:
I don't think so, as far as I know you can't crossflash firmwares from different variants (in this Case N960U or N960U1 to N9600 or vice versa).
But I'm on the same boat, mine is also N9600 and eagerly waiting for any sign of Pie.
Have you seen the release notes for Pie in the members app? Make no sense to me.
Click to expand...
Click to collapse
I saw the release notes now and they said march only

My release notes only contain a mess... no mention of note 9, only low or mid tier devices listed with date 28th of February.

I'm using Samsung Note 9 N600 dual SIM. Can I update using this method.

Root galaxy S10 (July security patch update)

hi to all, has anyone managed to root on galaxy s10 with the July security patch update? I tried the same method with magisk but there is nothing to do, every time it gives me a different error. In the last attempt I made during the boot phase, in the upper left corner, it was written: "only official released binaries are allowed to be flashed" or something like that.

You didnt do it right. I would suggest youtube the magisk rooting process

Same tried to root it
I, was able to get it to root but the camera still makes my device rebooted
And tried to do it with ap file by changing recovery inside to the patched twrp that didn't work just booted into stock recovery instead

Cristian-104 said:
hi to all, has anyone managed to root on galaxy s10 with the July security patch update? I tried the same method with magisk but there is nothing to do, every time it gives me a different error. In the last attempt I made during the boot phase, in the upper left corner, it was written: "only official released binaries are allowed to be flashed" or something like that.
Click to expand...
Click to collapse
I have already tried EVERYTHING, in download mode I can not get the> Prenormal <to> Check ing <. The option of OEM lockdown is there, has always been there.

TheUndertaker21 said:
Same tried to root it
I, was able to get it to root but the camera still makes my device rebooted
And tried to do it with ap file by changing recovery inside to the patched twrp that didn't work just booted into stock recovery instead
Click to expand...
Click to collapse
TWRP ≠ Root.
With the latest patch the camera crashes if TWRP is flashed. With stock recovery everything should work fine.
I'm on Exynos ASG8 without any issues, except slow wifi in apps (not browser).

Jannomag said:
TWRP ≠ Root.
With the latest patch the camera crashes if TWRP is flashed. With stock recovery everything should work fine.
I'm on Exynos ASG8 without any issues, except slow wifi in apps (not browser).
Click to expand...
Click to collapse
OH that's a known issue then?
I need my custom rom and twrp lol

TheUndertaker21 said:
OH that's a known issue then?
I need my custom rom and twrp lol
Click to expand...
Click to collapse
It is...nearly everytime Samsung throws out a new security patch TWRP is crashing the camera.
This is what I found out after having the same issue. I don't know if there's a new version for the latest patch.
Aren't the custom roms based on One UI? Shouldn't the stock recovery still work? (I really don't know)

Jannomag said:
It is...nearly everytime Samsung throws out a new security patch TWRP is crashing the camera.
This is what I found out after having the same issue. I don't know if there's a new version for the latest patch.
Aren't the custom roms based on One UI? Shouldn't the stock recovery still work? (I really don't know)
Click to expand...
Click to collapse
TWRP is good to have if something goes wrong.
I can have custom rom without twrp but that's not the whole of it.
Hope it gets patch soon

TheUndertaker21 said:
TWRP is good to have if something goes wrong.
I can have custom rom without twrp but that's not the whole of it.
Hope it gets patch soon
Click to expand...
Click to collapse
It's easy to flash it, even without running system.

Hi everyone, I'm still ASD4 and basically haven't update since because everything is a hassle these days. Now I thought maybe it's time to update, but keep reading things like this and camera, wifi bootloops problems etc.
Are these issues a real thing? or just some individual cases where it happens?

It's real like a $2 dollar bill.

bininga59 said:
I have already tried EVERYTHING, in download mode I can not get the> Prenormal <to> Check ing <. The option of OEM lockdown is there, has always been there.
Click to expand...
Click to collapse
You have to turn off all data ( wi-fi and 4g) and manually set the date to 7 days back.

FlatOutRU said:
You have to turn off all data ( wi-fi and 4g) and manually set the date to 7 days back.
Click to expand...
Click to collapse
I have already made. As I said, I unlock the bootloader and lock (developer option or download mode) as I want,> prenormal <does not go away.

Did a root today without issues on my S10 with ASG8

ru_dimka said:
Did a root today without issues on my S10 with ASG8
Click to expand...
Click to collapse
everything works? twrp installed? magisk etc.?

chieco said:
everything works? twrp installed? magisk etc.?
Click to expand...
Click to collapse
There is no twrp for ASG8. Others stuff works well!

ru_dimka said:
There is no twrp for ASG8. Others stuff works well!
Click to expand...
Click to collapse
I'm always afraid that I install something or make a small change and end up in a bootloop... I wish twrp and everythign work just fine like before and I could make a backup after installing a rom and doing the most basic stuff.

Since this is the first post that comes on Google for "only official released binaries" "s10".
I had this problem again and again, and it seems that it was caused by one of the reboot not being done with the correct timing with the 3 buttons.
The thing I was missing was after flashing the patched AP files (and the other files).
When you restart, keep the 3 buttons pressed until you see the blue screen and then release only power (keep vol up + bixby) to get into reset mode.
I think I didn't keep them pressed long enough.
If the device restarts, keep pressing the 3 buttons (never let it restart without pressing them).
Once the factory wipe has been done: Restart with the 3 buttons, and keep them pressed until 1 to 2 sec after the screen that asks you to press the power button to continue.