Database Info

Please help a noob fix her phone :(

Hello. I recently tried to use Magisk Manager to root my phone using a step by step walk through. It worked, everything was great, I finally was able to get my mobile data to turn off automatically when I connected to Wi-Fi. Goal achieved. Hooray. But then a new update came out for the Pixel 2 XL, I believe what is called OTA? See how new I am, it's pathetic. Anyway, I can't get the OTA installed because I have Magisk. I found a good walk through to how to fix it github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips BUT when I go to uninstall Magisk and restore images, it says "stock backup does not exist". Guys. I'm in over my head and I don't know what to do to fix it. Can any one explain in simple language, maybe with pictures, so my idiot self can understand, how do I get a stock back up, and get Magisk to recognize it, so that I can proceed to install the OTA? Thank you so much for any advice,and your patience for dealing with me.

Megin said:
Hello. I recently tried to use Magisk Manager to root my phone using a step by step walk through. It worked, everything was great, I finally was able to get my mobile data to turn off automatically when I connected to Wi-Fi. Goal achieved. Hooray. But then a new update came out for the Pixel 2 XL, I believe what is called OTA? See how new I am, it's pathetic. Anyway, I can't get the OTA installed because I have Magisk. I found a good walk through to how to fix it github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips BUT when I go to uninstall Magisk and restore images, it says "stock backup does not exist". Guys. I'm in over my head and I don't know what to do to fix it. Can any one explain in simple language, maybe with pictures, so my idiot self can understand, how do I get a stock back up, and get Magisk to recognize it, so that I can proceed to install the OTA? Thank you so much for any advice,and your patience for dealing with me.
Click to expand...
Click to collapse
Search the forum, there are a lot of walk through threads.
You won't remove anything, IE Magik.
Download the Factory Image, OTA will not work.
You'll remove "-w" from one file to not wipe data.
Flash update.
Reroot with Magisk.
If you have problems finding the links or threads, I can link them.
Sent from my Pixel 2 using Tapatalk

What diesel said, it isn't really that hard ?.
Nathanchanche made a really good guide for us. Take your time to read it really well and you should be able to solve your problem.
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417

In my experience, if rooted, don't use OTAs. Stick with factory images if possible.
Like other responses, it's best to use the guides on XDA. I usually do the following when an update is available:
- Download factory image
- Edit batch file (if you're using Windows) to remove the -w option so I don't lose my data
- Boot into bootloader (power off phone, then hold down power and volume down until you get to the bootloader)
- Run batch file (I have had issues on occasion with this). If you get an error, try using a different USB cable
- After factory image is installed, let phone reboot.
- After rebooting and device is fully ready to go, reboot back to bootloader.
- Install latest TWRP (follow instructions on their website...the steps they have works perfectly)
- After TWRP is installed, reboot phone back to bootloader and then go to the 'recovery' option. Make sure TWRP is working correctly and you can decrypt your data (that is, if you have a security password)
- After decrypted, you should be able to access your data where you've downloaded Magisk. You can then install Magisk.
- After install, reboot phone and you should be rooted.
These steps work for me, but I'm a bit anal when it comes to updates and rooting.

pgarlinski said:
In my experience, if rooted, don't use OTAs. Stick with factory images if possible.
Like other responses, it's best to use the guides on XDA. I usually do the following when an update is available:
- Download factory image
- Edit batch file (if you're using Windows) to remove the -w option so I don't lose my data
- Boot into bootloader (power off phone, then hold down power and volume down until you get to the bootloader)
- Run batch file (I have had issues on occasion with this). If you get an error, try using a different USB cable
- After factory image is installed, let phone reboot.
- After rebooting and device is fully ready to go, reboot back to bootloader.
- Install latest TWRP (follow instructions on their website...the steps they have works perfectly)
- After TWRP is installed, reboot phone back to bootloader and then go to the 'recovery' option. Make sure TWRP is working correctly and you can decrypt your data (that is, if you have a security password)
- After decrypted, you should be able to access your data where you've downloaded Magisk. You can then install Magisk.
- After install, reboot phone and you should be rooted.
These steps work for me, but I'm a bit anal when it comes to updates and rooting.
Click to expand...
Click to collapse
Ok what am I doing wrong here? prntscr.com/iqefpd

Megin said:
Ok what am I doing wrong here? prntscr.com/iqefpd
Click to expand...
Click to collapse
You need to install fastboot. Download plataform tools from the Android SDK and try again.

Megin said:
Ok what am I doing wrong here? prntscr.com/iqefpd
Click to expand...
Click to collapse
Follow the full tutorial in my signature, it will cover all the steps in detail.

Megin said:
Ok what am I doing wrong here? prntscr.com/iqefpd
Click to expand...
Click to collapse
As said previously you need fastboot.exe. Download from https://dl.google.com/android/repository/platform-tools-latest-windows.zip.
Extract everything to folder that contains your extracted image. If the fastboot.exe is still not recognized:
one option is to modify flash-all.bat line: PATH=%PATH%;"%SYSTEMROOT%\System32"; to PATH=%PATH%;"%SYSTEMROOT%\System32";"%cd%"

Telperion said:
Follow the full tutorial in my signature, it will cover all the steps in detail.
Click to expand...
Click to collapse
Worked!! Thanks

[GUIDE] Dirty update: stay stock, rooted, unencrypted and RETAIN ALL YOUR DATA

I've wrote it in many thread and I report here for users that want:
stay stock and updated
root (with Magisk)
unencrypted
never lose data and configuration
Here's my procedure, I'm using it since since I bought my S8 exynos (jun 2017), never had a problem, never lost a single bit of my data. And I don't know any alternative until now.
G950FXXU4DSDA (pie) tested​
I assume you have:
unencrypted device
oem unlock option checked (never uncheck it)
stock rom: any system mod is ok, but you'll lose it
What you need:
last odin (download here)
last stock rom for your country (download here)
last twrp on your exynos device (download here)
last Magisk zip on your device (download here)
Here's the steps:
if you haven't did before, create a magisk config file executing this two command on a shell (this file remain until you clean /data partition):
Code:
echo KEEPVERITY=false>>/data/.magisk;
echo KEEPFORCEENCRYPT=false>>/data/.magisk;
extract the rom and delete CSC_OXM_G950Fxxx (you don't need it, this file do the factory reset we don't want)
reboot you phone in download mode (boot with voldown+power+bixby)
connect your phone (you already have the driver, right?)
select all files in odin
uncheck auto-reboot option
press start
at the end manually restart the phone with voldown+power
the phone will boot in stock recovery and complete the installation ("Installing system update..." and "Erasing...")
keep attention because when rebooting you have to put your finger on voldown+power+bixby to return in download mode (if system boot your data partition will be encrypted)
in odin select TWRP file in AP slot
check auto-reboot option
put your finger on volup+power+bixby and keep there
press start
after a while you'll be in TWRP and you can relase the finger
flash Magisk
reboot in system
Then you can do any other mod you wan't, my favourites here.
I wrote this thread because all the guides I found skip the important (and tricky) 9-10 step and my tests results in:
interrupted csc install (twrp tried to execute a script producing "Error installing zip file 'CACHE:recovery/sec_omc.zip'")
empty CSC (Phone Info app) and no /system/omc folder
phone works well, but i'm not sure I was using VoLTE because I didn't see the icon
dial codes aren't working
korean operator "KT" voice in settings

Anyone else tried this method? Hoping to give it a try later this week when I have some time should something go wrong

so on s8 works too. nice. I've been doing this on my S7 edge every FW update. dirty flash, then root then xposed. So I hope this trick works in my S8 too.
are you on Nougat or Oreo?

Yea it works just fine, dirty flash can cause issues though. Might wanna let people know that.

t12icky0 said:
Yea it works just fine, dirty flash can cause issues though. Might wanna let people know that.
Click to expand...
Click to collapse
this way works like an ota for my experience, not a single issue in one year of updates

Can i root in your way? Im on CRD7 all stock, unroted.
If i follow your guide will be my phone rooted?
Sent from my SM-G950F using Tapatalk

zelenko said:
Can i root in your way? Im on CRD7 all stock, unroted.
If i follow your guide will be my phone rooted?
Sent from my SM-G950F using Tapatalk
Click to expand...
Click to collapse
if you've never modify the phone, you're encrypted
if you,re encrypted, you need to format your data partition to get root permission (for what I know is not possible / not safe to stay encrypted)
you can follow my guide adding a format data step before flashing supersu, but the phone will be factory reset

so after doing this i'll still get ota updates and i can install them fine plus having the root privileges ?

No, I've never tried ti install otas (I expect it will fail).
To stay updated you have to repeat the procedure whit the new stock image, usually released before the ota.

pie tested ​:good:

Does is still work? I want to upgrade to Pie but dont want to wipe and lose all data.
Is it still rooted after?
Sorry i'm a noob
S8 rooted
TWRP and Magisk

can you help me please???

silverik1 said:
Does is still work? I want to upgrade to Pie but dont want to wipe and lose all data.
Is it still rooted after?
Sorry i'm a noob
S8 rooted
TWRP and Magisk
Click to expand...
Click to collapse
Confirming, it's working perfectly
@c3k ,
Thanhs for this great solution !!
m.

I still have the stock rom and rooted with magisk. But in twrp I can not mount the data partition. Is it because it's still encrypted ?

... that's what I assume but it`s strange because you should be decrypted already after formatting data installing twrp, magisc etc. ...
m.

Yeah..I know...any suggestions ?

... it sounds like a data format is needed then ... Or does this method from c3k work for you ... ?
You `ve the latest TWRP installed?
m.

How do I install the latest one if I have an older version ? Can I use flashify for it ?

Or with twrp itself ?

I install new twrp via the installed one as an img file.
m.

[Root] Magisk for Moto E5 XT1944-2 (nora_row)

Hi guys!
I've bought Moto E5 XT1944-2 just few days ago, I was looking for some info to root the device but I couldn't find any tutorial, and after a couple of hours I found a way to root the device, so I'm going to explain how to root this device.
Disclaimer
I'm not responsible for any dead phones, even if they explode or cause a war
If you didn't follow the steps one by one
VERY IMPORTANT!!
There's no way to backup using TWRP (cos is not available yet)
Also it seems that it doesn't works with XT1944-1 (try by your own risk)
REQUIREMENTS:
1. Unlocked Bootloader
2. Magisk Manager apk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
3. Boot Image from stock rom (you need to choose your current variant to avoid some possible problems) https://forum.xda-developers.com/moto-e5/how-to/firmware-moto-e5-xt1944-4-dual-sim-t3820901
4. Motorola Drivers and ADB/Fastboot Drivers also
5. PC
6. A good brain and some patience LOL
Well, considering that already have all what I've mentioned lest begin.
FIRST STEP
Download and install Magisk Manager, It will show and advertisement asking if you want to install Magisk v16 (the screenshot says v16.7 but it's because I've got root already).
https://www.dropbox.com/s/a8mj0w0mk7uho7x/Screenshot_20180803-232248%5B1%5D.png?dl=0
Press no thanks, then open the app and in settings change the Update Channel into Beta , it's very important to know that because only Magisk v16.7 works, previous versions wont work!!
https://www.dropbox.com/s/vk404a1d0oou0ji/Screenshot_20180803-225740%5B1%5D.png?dl=0
https://www.dropbox.com/s/fyi6b3c1tgtfj5u/Screenshot_20180803-225745%5B1%5D.png?dl=0
SECOND STEP
After you have already downloaded the zip from your variant, use Winrar/7 Zip or any program to extract boot.img and then copy boot.img to you internal/external storage
THIRD STEP
Open again Magisk Manager, it will show if you want to install Magisk v16.7, press install, and select Patch Boot Image File
https://www.dropbox.com/s/9xyqgu8p4mm2ddy/Screenshot_20180803-232254%5B1%5D.png?dl=0
Then you need to look for the boot.img previously unzipped and moved onto your storage
https://www.dropbox.com/s/xlik3p9cau4952f/Screenshot_20180803-232720%5B1%5D.png?dl=0
After that the process began and it will save a new file called "patched_boot" that will be located on storage/MagiskManager
FOURTH STEP
Reboot your phone to bootloader mode and move to your computer the patched_boot.img, then flash that boot image via CMD with this command:
fastboot flash boot patched_boot.img
https://www.dropbox.com/s/xlik3p9cau4952f/Screenshot_20180803-232720%5B1%5D.png?dl=0
https://www.dropbox.com/s/h0r03mio06jezzz/XDA2.png?dl=0
It might delay less than a minute.
Finally run the command:
fastboot reboot
In my case shows a black screen saying, invalid key with white letters, if that is your case wait a minute, it will boot, if says N/A maybe something is wrong but first wait until the phone starts, if not, you have chosen the incorrect boot.img, to fix that just flash the original boot.img you've extracted with the command:
fastboot flash boot boot.img
And your phone will start normally, you don't need to wipe, and you wont loose your data
If you have some questions, let me know, oh, forget to mention, I'm not a dev so I don't know if it will be any rom available soon...
P.D I've tested only Substratum and it doesn't works, Xposed not tested yet because it turn the phone slower (in my experience) also some modules are not compatible and it will brick your device, Viper4Android works fine, you only need to install it via Magisk but keep in mind to use version 6.1 designed for Masigk v15 and upper...
I've created a telegram channel to help each others =)
https://t.me/joinchat/AAAAAEkiNbz-qY1tlKVgGQ

Woooow the scene grow up!. This guide is compatible with the Moto E5 xt1944-1?.

intherior said:
Woooow the scene grow up!. This guide is compatible with the Moto E5 xt1944-1?.
Click to expand...
Click to collapse
If it is nova_row I guess so, but well you need to try, remember that you need the stock ROM to extract boot and then in case of something wrong, also bootloader unlocked sir

Nice work @Fersho. Thank you for your contribution and your time.

Good descriptive guide.

I try to follow the guide using the Xt1944-1 stock rom image and after do it everything my Moto E5 get stucks on the Moto logo and reboots everytime. Only restoration guide of pal MotoJunkie01 revives.

intherior said:
I try to follow the guide using the Xt1944-1 stock rom image and after do it everything my Moto E5 get stucks on the Moto logo and reboots everytime. Only restoration guide of pal MotoJunkie01 revives.
Click to expand...
Click to collapse
Glad you got it back to life.

MotoJunkie01 said:
Nice work @Fersho. Thank you for your contribution and your time.
Click to expand...
Click to collapse
Thank you, all in the name of development and to help each others

intherior said:
I try to follow the guide using the Xt1944-1 stock rom image and after do it everything my Moto E5 get stucks on the Moto logo and reboots everytime. Only restoration guide of pal MotoJunkie01 revives.
Click to expand...
Click to collapse
You've tried flashing only boot? beause I mentioned that it wasn't necessary to flash the whole time, just flashing the stock boot the phone will start normally, but well that means that the XT1944-1 is unable to root, did you follow the correct steps? I mean you tried with Magisk v16.7?

Fersho said:
You've tried flashing only boot? beause I mentioned that it wasn't necessary to flash the whole time, just flashing the stock boot the phone will start normally, but well that means that the XT1944-1 is unable to root, did you follow the correct steps? I mean you tried with Magisk v16.7?
Click to expand...
Click to collapse
I think that i follow well. And i put my boot.img from stock rom with Magisk to make the patched_boot.img. Then i connect to the Pc to copy that file to the adb directory, reboot on bootloader mode and flash with the command that you post. Everything well, buy when i reboot after flash that appears the N/A letters and stucks rebooting everytime. When i reflash the smartphone with the stock rom then the Bad Key letters appears and make the boot well.
I dont know if isn't compatible yet

intherior said:
I think that i follow well. And i put my boot.img from stock rom with Magisk to make the patched_boot.img. Then i connect to the Pc to copy that file to the adb directory, reboot on bootloader mode and flash with the command that you post. Everything well, buy when i reboot after flash that appears the N/A letters and stucks rebooting everytime. When i reflash the smartphone with the stock rom then the Bad Key letters appears and make the boot well.
I dont know if isn't compatible yet
Click to expand...
Click to collapse
Well at least you've restored your phone, I think the same, that is not compatible, but well we won't know if something works til' we try, but thanks to share your experience I've edited the thread telling that issue, that happened to me but it boots while shows N/A

Does not work on xt1944-4

Hi, the ROM link for the stock rom is for the Moto E5 Play (James). Is this also the right one for Moto E5 (nora_row), because both phones have different specifications (according to GSM arena).
Otherwise, thanks for your help @Fersho.

artemis1102 said:
Hi, the ROM link for the stock rom is for the Moto E5 Play (James). Is this also the right one for Moto E5 (nora_row), because both phones have different specifications (according to GSM arena).
Otherwise, thanks for your help @Fersho.
Click to expand...
Click to collapse
My mistake, I didn't notice that I put the link for E5 Play Stock ROM, now is updated with the right one

Fersho said:
My mistake, I didn't notice that I put the link for E5 Play Stock ROM, now is updated with the right one
Click to expand...
Click to collapse
Seems like the right one now, thanks for your help. I'll give it a try.
Edit: I checked the page and there is no mention of the OPP27.91-72 build. Do you think the OPP27.91-25 will work or should I get the firmware from stock rom .net, which seems to have the correct one.
Thanks for updating the link anyways @Fersho

artemis1102 said:
Seems like the right one now, thanks for your help. I'll give it a try.
Edit: I checked the page and there is no mention of the OPP27.91-72 build. Do you think the OPP27.91-25 will work or should I get the firmware from stock rom .net, which seems to have the correct one.
Thanks for updating the link anyways @Fersho
Click to expand...
Click to collapse
The thread is not updated yet, so It will work because you only need the stock rom for your specific device, if it is updated or not, doesn't matter, I guesss that nora and hannah have got a security patch, but is not necessary, I mean still outdated, so don't take care about it

Hi
Have someone this firmware "XT1944-4 NORA_ROW_OPP27.91-146_cid50_subsidy-DEFAULT" for share ?

I would like to verify once magisk is I stalled and the manager is running and root works if we update will it still work. There are supposed exports who have said that if you update the magiks manager to the latest version 18+ or magiks 18+ versions that magics won't work anymore for the Moto e5 play can any one vetify

daktras said:
I would like to verify once magisk is I stalled and the manager is running and root works if we update will it still work. There are supposed exports who have said that if you update the magiks manager to the latest version 18+ or magiks 18+ versions that magics won't work anymore for the Moto e5 play can any one vetify
Click to expand...
Click to collapse
running 18 on e5+ perfectly

It worked on my XT1944-2 but only with Stock-ROM. Until nowI have no solution to Root with Lineage 17.1 OS on it.

2022_VZW_EMMC_15_ AIO_Tool To Unlock_Bootloader+Install_TWRP And MM_QL1_Rooted_Rom Works On Any Version Bootloaders_MM_LL_KK-Reactivation Lock Remover

This Process Will Root Phone Unlock Your VZW EMMC 15 Chipset Bootloader Install TWRP Recobery And Imstall Latest QL1 Stock Rom .​
Downloads
S5_Root_Tools_2023.7z
EMMC_15_Rom.zip -- Stock QL1 6.0
Directions For Unlocking Stock Phone
I would recommend Windows defender is turned of before starting
1. Download S5_Root_Tools_2023.7z and unzip
2. Make sure Usb debugging is enabled on your phone
3. Plug in phone and run Safestrap.exe and follow directions on command window
4. This process is pretty much 1 click all automatic except following command window prompts
5. This will detect if your phone is EMMC 11 or 15
6. If it detects EMMC 15 it will automatically unlock your bootloaders.
7. Once process is done reboot too twrp and flash rom of choice or use provide one and flash root zip of choice
Regular Magisk
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Magisk Delta
Releases · HuskyDG/magisk-files
Contribute to HuskyDG/magisk-files development by creating an account on GitHub.
github.com
ETFSU
EFTSU Root Solutions
The Largest Database for the Root Solutions on the Internet
eftsu.com
Safteynet Fix Module
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
Old Method And Old Downloads
EMMC_15_SS_Install_QL1_6_0_1_MM_Bootloader_Unlock_AIO_Rom.zip -- Rom Zip
EMMC_11_S5_Root_Tools_2022_V7.7z
-- Files Needed To Root Phone
Instructions To Root And Install Safestrap
**If you already have safestrap installed you can skip to Instructions To Unlock Bootloader
**If you are already rooted but do not have safestrap installed download View attachment S5_Safestrap.apk install then skip to Instructions To Unlock Bootloader**
Directions
1. Download both files and unzip EMMC_15_And_11_S5_Root_Tools_2022_V7.7z
2. Reboot phone too Download Mode by holding Power+VolDwn+HomeButton as phone starts up
3. Plug phone into computer and open the Odin provided in the above file in the Odin_Folder
4. In Odin Choose BL slot and choose the COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5 Located in the Odin_Folder
5. Flash the file using provided Odin let phone reboot. This will wipe your phone
6. Once phone is rebooted make sure its plugged into computer and phone use recognized by computer
7. Run the Install_One_Click.cmd this should install safestrap. If this method fails countinue with below methods.
8. If above method fails you can reboot and try again or run the Manual_Install_Root_Apps.cmd and try below methods to root
Towel Root Method
These steps are only needed if above root method failed
1. You need too be connected to a network. Try one of towel root apps and if not successful then try the other one. If it doesn't work go to King root section
2. If towel root succeeds then run the click on the super su app and choose to update su binary and choose normal once successfully updated reboot phone
King Root Method
These steps are only needed if towel root failed
1. You will need to be connected to a network. Click on King root app then click try root
2. Once root is successful don't click on the optimize and close the king root app.
3, Run the Manual_Install_SuperSu.cmd
Installing Safestrap
9. This only needs to be done if 1Click bat method failed. Now click on safestrap app and clisk install safestrap click allow in root dialog app once installed click reboot to safestrap
10. Busybox must be installed ifirst if you used towelroot method too root
Instructions To Unlock Bootloader
11. Enter safestrap now in safetrap it will ask you to swipe to allow modding system make sure to do this now . If you have not copied the EMMC_15_SS_Install_QL1_6_0_1_MM_Bootloader_Unlock_AIO_Rom.zip from the EMMC_15_Bootloader_Unlock_Zip folder do so now Click install tab and choose EMMC_15_SS_Install_QL1_6_0_1_MM_Bootloader_Unlock_AIO_Rom.zip and install.
12. When done phone will power off.
13. Reboot phone to recovery you should now have TWRP recovery installed and the choose wipe the advanced wipe and wipe data only then reboot
14. Phone will reboot and stick on red Verizon screen for probably 15 to 20 min be patient. When finally booted you will have an unlocked bootloader with TWRP recovery running a Deodexed Rooted QL1 stock MM 6.0 Rom Rooted with EFTSU with root hide and safetynet pass module
Disabling Reactivation Lock
Thanks bbsc
1. Follow above directions too obtain safestrap and root
2. Download and flash EMMC_11_NCG_KK_Safestrap_Full.zip in safestrap then wipe data
This has Samsung Setup Wizard removed so you can get through setup
3. Set up a wireless connection or use your SIM-card and internet connection from your provider.
4. Navigate to Settings - Security, find Reactivation Lock and untick it. The phone will ask you for your existing credentials or to register a new Samsung account. Accept too update app then allow google check when it ask
5. Login to your new account and you will be able to untick Reactivation Lock.
6. When it unticked, Navigate to Settings - Backup Reset - Factory data Reset.
7. Phone will reboot too stock recovery and wipe data and remove current samsung account and you are good too go.
8. Now proceed with unlocking bootloader step 11 you have to enter safestrap from the safestrap splash screen on bootup its not installed as a recovery image because stock recovery is needed
Credits
beaups Sourcecode and tool
ryanbg
haggertk For his CID
autonomousperson For compiling the source to a app
magic_man185 For compiling the source
GeTex
klabit87 - Basically Everything
@GSMCHEN Lots of stuff
elliwigy Lots of stuff
afaneh92 -Safestrap and too much too mention
Sourcecode
https://github.com/beaups/SamsungCID

Instructions for downgrading or updating bootloaders can be found here
2022_VZW_EMMC_15_Chipset For Unlocked Dev BL To Downgrade To LL_KK Or Upgrade To MM_And Keep Unlock Bootloader
This Process Will Update Or Downgrade Your VZW EMMC Chipset DEV Aboot Bootloader Unlocked S5 To Marshmallow 6.0 Lollipop 5.0 Or Kitkat 4.2 or 4.4 Root And Unlock Instructions Can Be Found Here EMMC 15 Rooting And Bootloader Unlocking EMMC 11...
forum.xda-developers.com
​

jrkruse said:
mine
Click to expand...
Click to collapse
Nice job man! [emoji106]
stang5litre Edition 5.0 Roms

stang5litre said:
Nice job man! [emoji106]
stang5litre Edition 5.0 Roms
Click to expand...
Click to collapse
I was bored so I thought it would be fun to mess around with some old school stuff. Man things were alot more simple back in these days

@jrkruse awesome job...!! :good:You definitely must be bored... Lol. May try that on an old one for craps and giggles... Lol. Again, awesome to bring a lil history back to life... :good:

jrkruse said:
I was bored so I thought it would be fun to mess around with some old school stuff. Man things were alot more simple back in these days
Click to expand...
Click to collapse
Nice job man, much appreciated.
If you ever get bored try to make a pre-rooted rom/safestrap recovery (course no bootloader unlock) for the G930U/G935U with the latest firmware UUESACSI1 (Aug 27 2019), since it looks like Samsung has stopped updating this phone, or better yet a root-patcher for a stock sytem.img like you did for the G950/N950. I have uploaded the latest eng-boot vA/10 here: https://forum.xda-developers.com/sho...postcount=1826

jrkruse said:
I was bored so I thought it would be fun to mess around with some old school stuff. Man things were alot more simple back in these days
Click to expand...
Click to collapse
How do I update the bootloader and rom to newer QL1 if I had already unlocked the bootloader and installed twrp with much older stock rom and bootloader?
I still have the stock rom from 2016 when the bootloader unlock method was discovered.

googlephoneFKLenAsh said:
How do I update the bootloader and rom to newer QL1 if I had already unlocked the bootloader and installed twrp with much older stock rom and bootloader?
I still have the stock rom from 2016 when the bootloader unlock method was discovered.
Click to expand...
Click to collapse
https://forum.xda-developers.com/ve...ent/vzwemmc15chipset-dev-bl-unlocked-t4010757
Sent from some device I modified

the rar seems to be corrupted ... says unknown or damaged format. I tried a few of the download points.
Would you be able to re-create / upload?

bigstack said:
the rar seems to be corrupted ... says unknown or damaged format. I tried a few of the download points.
Would you be able to re-create / upload?
Click to expand...
Click to collapse
What are you extracting it with?
Sent from some device I modified

First of all, thank you so very much Jkruse! I followed all of your instructions and everything went perfectly! The reason why I wanted to get this completed on my old S5, is that we want to gift this phone to my wife's mother. The catch is, she only speaks Russian, and I was wondering if I would now be able to flash an international version of firmware on the S5, so that she can have access to Russian as a language option? Is this doable?

Remedy1230 said:
First of all, thank you so very much Jkruse! I followed all of your instructions and everything went perfectly! The reason why I wanted to get this completed on my old S5, is that we want to gift this phone to my wife's mother. The catch is, she only speaks Russian, and I was wondering if I would now be able to flash an international version of firmware on the S5, so that she can have access to Russian as a language option? Is this doable?
Click to expand...
Click to collapse
Its really no easy process to flash an international rom if you are using Verizon then data will probably not work with out some editing. You can always try it but Verizon will probably need Verizon csc stuff to work and build.prop edits.
Sent from some device I modified

Hey thanks for this post! I was worried about using some of the old guides on my phone, glad I found this.
However, I have a question due to why I want to root my phone.
My situation: My phone went through the factory reset process without giving me a warning before doing so. I plan on rooting my phone and trying a few different methods for recovering the files.
My Main Question: Will I be good to go with a fully rooted phone after completing step 12?
I don't feel a need to unlock the bootloader for what I'm doing (although I might do so anyway after I'm done attempting to recover files).
I've never rooted a phone before. Aside from verifying that I'm using the EMMC 15 chipset (I used the eMMC_CID_Checker_apk from this thread:https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529), is there anything else I should do or know about?

SaltedSand said:
Hey thanks for this post! I was worried about using some of the old guides on my phone, glad I found this.
However, I have a question due to why I want to root my phone.
My situation: My phone went through the factory reset process without giving me a warning before doing so. I plan on rooting my phone and trying a few different methods for recovering the files.
My Main Question: Will I be good to go with a fully rooted phone after completing step 12?
I don't feel a need to unlock the bootloader for what I'm doing (although I might do so anyway after I'm done attempting to recover files).
I've never rooted a phone before. Aside from verifying that I'm using the EMMC 15 chipset (I used the eMMC_CID_Checker_apk from this thread:https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529), is there anything else I should do or know about?
Click to expand...
Click to collapse
By the time you root there will be no files to recovery. There is another wipe involved to root so chances are there will not be much left to recover
Sent from some device I modified

jrkruse said:
By the time you root there will be no files to recovery. There is another wipe involved to root so chances are there will not be much left to recover
Sent from some device I modified
Click to expand...
Click to collapse
I'm wondering if he's wanting to root to use a file recovery app, like DiskDigger. It can recover but device needs to be rooted to access the complete internal system to recover files. As he mentioned a few times about recovering/restoring files. I recall using that (DD) a couple times and it actually worked after I mistakenly did a full wipe/reset when I was switching between ROM's and back to stock...

al50 said:
I'm wondering if he's wanting to root to use a file recovery app, like DiskDigger. It can recover but needs device needs to be rooted to access the complete internal system to recover files. As he mentioned a few times about recovering/restoring files. I recall using that (DD) a couple times and it actually worked after I mistakenly did a full wipe/reset when I was switching between ROM's and back to stock...
Click to expand...
Click to collapse
Like i said though in order to root you have to wipe again before you can root. So there aren’t going to be much left to recovery after 2 wipes and a repartition
Sent from some device I modified

al50 said:
I'm wondering if he's wanting to root to use a file recovery app, like DiskDigger. It can recover but device needs to be rooted to access the complete internal system to recover files. As he mentioned a few times about recovering/restoring files. I recall using that (DD) a couple times and it actually worked after I mistakenly did a full wipe/reset when I was switching between ROM's and back to stock...
Click to expand...
Click to collapse
Yeah that's what I have in mind.
jrkruse said:
Like i said though in order to root you have to wipe again before you can root. So there aren’t going to be much left to recovery after 2 wipes and a repartition
Sent from some device I modified
Click to expand...
Click to collapse
Yeah I figured, makes sense, but I don't see a mention of wiping before step 12 though. This is why I'm asking if it would be okay for me to stop there, attempt to recover some files, and then continue with the rest of the steps?
Could this potentially screw something up if I do it this way? I'd rather play it safe than sorry, most of my important stuff on this phone is backed up anyway.

SaltedSand said:
Yeah that's what I have in mind.
Yeah I figured, makes sense, but I don't see a mention of wiping before step 12 though. This is why I'm asking if it would be okay for me to stop there, attempt to recover some files, and then continue with the rest of the steps?
Could this potentially screw something up if I do it this way? I'd rather play it safe than sorry, most of my important stuff on this phone is backed up anyway.
Click to expand...
Click to collapse
Flashing the combo firmware so you can root wipes your phone
Sent from some device I modified

jrkruse said:
Flashing the combo firmware so you can root wipes your phone
Sent from some device I modified
Click to expand...
Click to collapse
Ah, I see, but would it be safe for me to stop at step 12 anyway?
I figure I might as well give it a shot anyway, even if It's unlikely I'll recover anything, but I'd rather only wipe it a single time than twice.

SaltedSand said:
Ah, I see, but would it be safe for me to stop at step 12 anyway?
I figure I might as well give it a shot anyway, even if It's unlikely I'll recover anything, but I'd rather only wipe it a single time than twice.
Click to expand...
Click to collapse
If you stop at 12 you will just have king root and some apps work with kingroot but some do not
Sent from some device I modified

General Rooting with Magisk

Just a heads up to anyone who is wondering about root for this phone - I successfully rooted it with Magisk. It was pretty easy. Basically I just followed the same steps as outlined in this thread, which was for rooting last year's Moto G Stylus model, and it worked. Obviously you need to have already unlocked the bootloader before doing any of this.
I got the stock boot.img from the firmware linked in this thread. I patched it using Magisk Manager (v8.0.7) then flashed it via fastboot. My installed Magisk version is 21.4 (21400).
-- A WORD OF CAUTION: --
As of now there is no TWRP or any other custom recovery for this phone that I am aware of, so if you mess something up due to root, your only option to fix it might be to reflash the stock firmware.
A note about mobile banking apps:
After I installed Magisk Manager, my banking app stopped working and SafetyNet check was failing. After flashing the patched boot.img and rebooting, the SafetyNet check passed but my banking app still wasn't working. I used Magisk Hide and checked off the banking app in the list, but that didn't help either. What I had to do was use the Hide Magisk Manager option where it reinstalls Magisk Manager under a different name. Now my banking app is working again.

DM.IDOL said:
... - I successfully rooted it with Magisk. It was pretty easy. Basically I just followed the same steps as outlined in this thread, which was for rooting last year's Moto G Stylus model, and it worked. ...
Click to expand...
Click to collapse
It worked for me too. It was also easy for me because the only RETUS upload on the mirrors.lolinet site was my exact firmware version. Downloaded that, extracted and used that boot.img for magisk-patching.
The only issues I'm left with are:
1. Adaway isn't working (can't write to any of the canned hosts file paths) and I haven't figured out where I might be able to store a writable hosts file, and . . .
2. Titanium Backup (Pro) works to freeze almost every app that I wanted to disable. The one exception was Motorola Update Service. TiBu toasts that it was disabled and "invisible from the app drawer", but it actually wasn't disabled and still isn't. It still shows under System Applications. So I dunno . . . it's not a deal breaker as long as auto updating stays turned off.
Bootloader is unlocked and rooting via Magisk worked on my Stylus 2021, exactly as advertised.
Update: My solution for AdAway was here, AdAway 5.3 (newest version I believe).
Update2: Sans freezing Motorola Update Service, updates are of course frozen from actually running because of system changes by root & TWRP. So no big worries, just the nuisance of notifications.

cant the new maagisk be used as an alternative custom recovery? Something about renaming the apk to zip and then flashing zip file on recovery?

Mr.Morgan said:
cant the new maagisk be used as an alternative custom recovery? Something about renaming the apk to zip and then flashing zip file on recovery?
Click to expand...
Click to collapse
No, Magisk is not custom recovery.
There are two ways to install Magisk, using the .zip version, with a custom recovery like TWRP or
Using the magisk app to patch a boot.img then flash with fastboot.exe

sd_shadow said:
No, Magisk is not custom recovery.
There are two ways to install Magisk, using the .zip version, with a custom recovery like TWRP or
Using the magisk app to patch a boot.img then flash with fastboot.exe
Click to expand...
Click to collapse
I appreciate the knowledge, but perhaps you can shed some light on what the app means by " Custom Recovery lovers, no worries! The Magisk app APK itself is a custom recovery flashable zip, just like MAGIC. Check out the updated installation guide for more info"

Mr.Morgan said:
I appreciate the knowledge, but perhaps you can shed some light on what the app means by " Custom Recovery lovers, no worries! The Magisk app APK itself is a custom recovery flashable zip, just like MAGIC. Check out the updated installation guide for more info"
Click to expand...
Click to collapse
You are partly correct, there has been a big change with Magisk.
You can just change the Magisk.apk to Magisk.zip
But the zip does not replace a custom recovery.
It just eliminates the need for a separate manager.zip
In some custom recoveries, the installation may fail silently (it might look like success but in reality it bootloops). This is because the installer scripts cannot properly detect the correct device info or the recovery environment does not meet its expectation. If you face any issues, use the Patch Image method as it is guaranteed to work 100% of the time. Due to this reason, installing Magisk through custom recoveries on modern devices is no longer recommended. The custom recovery installation method exists purely for legacy support
Click to expand...
Click to collapse
Magisk in Recovery
If your device does not have ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to reboot to recovery every time you want Magisk.
When Magisk is installed in your recovery, you CANNOT use custom recoveries to install/upgrade Magisk! The only way to install/upgrade Magisk is through the Magisk app. It will be aware of your device state and install to the correct partition and reboot into the correct mode.
Since Magisk now hijacks the recovery of the device, there is a mechanism to let you actually boot into recovery mode when needed: it is determined by how long you press the recovery key combo.
Click to expand...
Click to collapse
This does not replace the stock recovery, just patches the recovery.

I recently purchased this phone, Moto G Stylus 2021, from Amazon. When I enter the dev options menu, OEM Unlocking is greyed out. I did a bit of research and found another thread online where another two users had the same problem, for all of two days.
After two days, the option to enable OEM Unlocking was no longer greyed out for the both of them. Fascinating! I may return this phone before that time is up, but if I don't, I'll report back on any changes for sure.
EDIT: I've decided to return this phone and get a Galaxy Tab S7 instead; there's more room to draw and a better pen!

Can't find my firmware on lolinet (boost mobile qpc30.q4-31-93)
Tried lenovo's rescue tool to see if I could grab the firmware that way and it just kept giving me errors.
If anyone has some how acquired the appropriate firmware would you mind sending it to me?

I can't remember exactly where I seen someone else commenting on this topic but they had lost their cellular network after rooting ,
My problem / question is that I have also my lost my cellular network connection after rooting but not completley only to the original carrier I got t this phone with witch is boost, but if I try another carrier such as tmobile or sprint or even metro it will work because they are basically all 1 company now , but how do I fix this problem to get my phone to read my sim card as valid (I get the invalid sim msg) when I put my original sim in and I just went and got a brand new replacement sim from them to see if that would solve the issue.also going off reading the forums on here I went with the mask retus firmware for flashing because there isn't one on there anywhere for so any help would be hysteria l greatly appreciated. This is my only problem I'm having since rooting everything else is working perfectly fine.

BobbyBlunt said:
Can't find my firmware on lolinet (boost mobile qpc30.q4-31-93)
Tried lenovo's rescue tool to see if I could grab the firmware that way and it just kept giving me errors.
If anyone has some how acquired the appropriate firmware would you mind sending it to me?
Click to expand...
Click to collapse
just an idea but on the site that has all the firmware im thinking could submit a request to them using that telegram messenger thing for the firmware needed.....it may be kind of a longshot but just thought of that myself and the closest one i see to what you posted is the metro version

riggin said:
just an idea but on the site that has all the firmware im thinking could submit a request to them using that telegram messenger thing for the firmware needed.....it may be kind of a longshot but just thought of that myself and the closest one i see to what you posted is the metro version
Click to expand...
Click to collapse
I tried the lenovo recovery tool again and this time it was able to find the appropriate firmware. I was able to successfully root

Hey well i just installed latest magisk and patched boot img and moved it to my pc and went thru fast boot and just did fastboot flash boot patched.img and it works fine. I dunno if latest update fixed whatever was wrong on yours but if i installed the older one it would not even let me pick the boot img to patch *shrugs* but all working on mine now...we just need full device tree etc so we can get us a a recovery def want that before i go adding mods. If it helps any I have cricket same as ATT the person who lost cell may need to redo their apn or take sim card out and reapply it hope that works.

Moondroid said:
The one exception was Motorola Update Service. TiBu toasts that it was disabled and "invisible from the app drawer", but it actually wasn't disabled and still isn't. It still shows under System Applications.
Click to expand...
Click to collapse
I've been having the same problem trying to disable the update prompts. Titanium Backup doesn't work, nor can I disable it via terminal using pm. The system update screen will pop up multiple times a day, interrupting whatever I'm currently doing to tell me I have an update. It's really annoying that it can't be frozen.

Well after a few days of LTE connection my own unlock now works got root

riggin said:
just an idea but on the site that has all the firmware im thinking could submit a request to them using that telegram messenger thing for the firmware needed.....it may be kind of a longshot but just thought of that myself and the closest one i see to what you posted is the metro version
Click to expand...
Click to collapse
hey was just wondering since im kinda in the same situation you were in with not being able to obtain exact firmware need at first for boost model if maybe you can proovide tthe brief steps you made to get the lmsa tool to recognize it and pull the corerct firmware....ty so much if u can

riggin said:
hey was just wondering since im kinda in the same situation you were in with not being able to obtain exact firmware need at first for boost model if maybe you can proovide tthe brief steps you made to get the lmsa tool to recognize it and pull the corerct firmware....ty so much if u can
Click to expand...
Click to collapse
Unfortunately, either LMSA determines the correct firmware or it doesn't, there isn't anything that can be done to fix it, except contacting Motorola.
For other options see
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com

Hey Guys, I'm continuing on this thread since I've gotten further. I used LMSA to download the firmware zip using the Resuce button. Afterwards I copy that zip (2+ gigs) to my download folder. I open up Magisk and select intall and select the firmware zip. I starts out successfully but then fails. I get this in the log folder.
- Device platform: arm64-v8a
- Installing: 23.0 (23000)
- Copying image to cache
- Unpacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
! Unsupported/Unknown image format
! Installation failed
I even tried to resuce the phone using the firmware provided by the LMSA program which essentially wipes my phone and try again with a clean Magisk load and I'm getting the same. The only thing I'm thinking is I could be getting my Magisk from another source. I'm using version 23 from github.

steppinthrax said:
Hey Guys, I'm continuing on this thread since I've gotten further. I used LMSA to download the firmware zip using the Resuce button. Afterwards I copy that zip (2+ gigs) to my download folder. I open up Magisk and select intall and select the firmware zip. I starts out successfully but then fails. I get this in the log folder.
- Device platform: arm64-v8a
- Installing: 23.0 (23000)
- Copying image to cache
- Unpacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
! Unsupported/Unknown image format
! Installation failed
I even tried to resuce the phone using the firmware provided by the LMSA program which essentially wipes my phone and try again with a clean Magisk load and I'm getting the same. The only thing I'm thinking is I could be getting my Magisk from another source. I'm using version 23 from github.
Click to expand...
Click to collapse
It isn't a zip file it's a folder or at least every firmware I have downloaded is automatically unzipped by LMSA.
You only need to copy the boot.img and maybe the recovery.img to the device.

sd_shadow said:
It isn't a zip file it's a folder or at least every firmware I have downloaded is automatically unzipped by LMSA.
You only need to copy the boot.img and maybe the recovery.img to the device.
Click to expand...
Click to collapse
Thanks I figured it out last night. I also figured out pretty quickly that once you root a phone certain applications will no longer function. I didn't deal with this before, but since I work from home I have to use some of those apps that create a "Work Profile". The one app "Intelligent Hub" removed itself and my work profile. When trying to re-install and authenticate with my work it literally said "Won't provision a compromised device".
Within Magsik I used the Magsik hide feature and tried selected that app and hiding all methods that it could detect root. I even then rebooted, removed/reinstall etc. Nothing worked. The app still kept detecting root. I know that the Xposed Framework modules may work in hiding root but I decided to go all the way back to normal since there's little benefit for me to root except for the ability for me to remove bloatware. This is a retail unlocked and there's little if any bloatware on the device.
I removed Magsik and any other junk, turned on OEM locking and rebooted and I'm back to mormal. Thank you everyone this was a leaning exp. I haven't rooted in like 5 years.

DM.IDOL said:
I've been having the same problem trying to disable the update prompts. Titanium Backup doesn't work, nor can I disable it via terminal using pm. The system update screen will pop up multiple times a day, interrupting whatever I'm currently doing to tell me I have an update. It's really annoying that it can't be frozen.
Click to expand...
Click to collapse
FYI, for posterity, instead of getting multiple notifs per day I just tap and let it try to update. It fails quickly and the notification is nixed for a while.