Database Users

[ROM]Updated! 4.4.4 SU4.21 fully rooted with writable system on LOCKED BL

Hello guys!
I've found the way for getting Android 4.4.4 rooted without write-protection on root filesystem
Original post on 4pda.ru Warning! Russian language detected!)
So, this is small and very simple instruction:
Preparation:​1. You should be on SU2-3.3 (Blur 19.6.3) or SU2-3-15 (Blur 19.5.3) rooted and have SafeStrap installed!
2. You have never flashed SU4.21 (Blur 21.11.21) Android version 4.4.4 via RSDLite and you have never taken OTA with 4.4.4!!!
Let's do it and enjoy fully rooted 4.4.4!​1 I've done 2 ZIP-files, download one, you prefer:
full rooted stock 4.4.4 SU4.21 with hosts-file ADBLOCK trick.
Download 4.4.4_full here
full rooted Debloated stock 4.4.4 SU4.21, with Touchless Control, Active Display, NFC, Wireless Monitor (inc. Cromecast)
Download 4.4.4_debloated here
Debloated ROM develompent was stopped, due to my smartphone physical damage. Im' sorry.
Regards, Dmitry.
2. Copy downloaded zip in to device storage.
3. Reboot to SafeStrap
4. Select Insall button, select ZIP, you prefer.
5. For locked bootloader: when installation will finish, reboot you device in to bootloader and flash stock kernel from SU4.21
you could take it here or from ZIP-file.
6. After flashing boot.img just reboot you smartphone and enjoy 4.4.4 with root and writable /system
For unlocked bootloader - all done, just reboot your device .
DO NOT PERFORM ANY WIPES!
If something happend with you phone, you can revert to SU2-3-15 (Blur 19.5.3) via RSDLite, get root, install SafeStrap
If you need to clean bloatware, use my Custom Recovery compatibility scripts, could be downloaded in this topic
If you found any features, you need, missing, please, pm me.

i am BL Unlocked, so no need for this for me... but if this is the case and it works then great find my man!!

Given the recent vulnerability published by Dan Rosenberg, I'm hesitant to update to 4.4.4, as it may patch this vulnerability - keeping the bootloader locked indefinitely. I would just keep this in mind if considering this update.
EDIT: Got my information wrong. The date on the OTA is before the date the vulnerability was published. 4.4.4. seems good to go in that case.

has anyone tried this yet?

Thinking about trying this - doing a backup now in Safestrap.
Would like to be able to see this...
"2. You have boot.img from SU4-21, you can download it below "
Where do you see this information? How do I know what version I have in 4.4?

rdenova said:
Thinking about trying this - doing a backup now in Safestrap.
Would like to be able to see this...
"2. You have boot.img from SU4-21, you can download it below "
Where do you see this information? How do I know what version I have in 4.4?
Click to expand...
Click to collapse
Settings>About Phone>Build number

summer.cat said:
1. You should be on SU2-3.3 rooted and have SafeStrap installed!
Click to expand...
Click to collapse
This, I see under Build Number.
summer.cat said:
2. You have boot.img from SU4-21, you can download it below
Click to expand...
Click to collapse
This, I do not see any place and is why I asked.

Wait so is this a fully write protection off?

mrwinkle said:
has anyone tried this yet?
Click to expand...
Click to collapse
Looks like this fella did...
http://forum.xda-developers.com/droid-ultra/general/update-19-5-3-obake-t2845903

ceelos218 said:
Wait so is this a fully write protection off?
Click to expand...
Click to collapse
sertainly)
PS: i've read many questions about build versions and firmware versions, so if you couldn't understand which firmware you have, follow this:
First update 4.4 - SU2.3-15 (suits for gaining root and wp off by @beaups wbegone)
Second update 4.4 - SU2.3-3
Latest update 4.4.4 - SU4.21
hope, it will be helpfull.

summer.cat said:
sertainly)
PS: i've read many questions about build versions and firmware versions, so if you couldn't understand which firmware you have, follow this:
First update 4.4 - SU2.3-15 (suits for gaining root and wp off by @beaups wbegone)
Second update 4.4 - SU2.3-3
Latest update 4.4.4 - SU4.21
hope, it will be helpfull.
Click to expand...
Click to collapse
Instead of using the SU for identifying builds, you should probably the system version number as that is more frequently used. 19.5.3, 19.6.3, 21.11.21

summer.cat said:
Hello guys!
I've found the way for getting Android 4.4.4 rooted without write-protection on root filesystem
Original post on 4pda.ru Warning! Russian language detected!)
So, this is small and very simple instruction:
Preparation:
1. You should be on SU2-3.3 rooted and have SafeStrap installed!
You have never flashed 4.4.4 via RSDLite and you have never taken OTA with 4.4.4!!!
2. You have downloaded boot.img from SU4-21
can be downloaded here https://drive.google.com/file/d/0B_kAWkXp3XK9VmpnSGNaVUZtTDQ/edit?usp=sharing
Let's do it!
1. Download 4.4.4_rooted.zip here
https://drive.google.com/file/d/0B_kAWkXp3XK9amVwNjJKUjk4QmM/edit?usp=sharing
2. Copy 4.4.4_rooted.zip in to device storage.
3. Reboot to SafeStrap
4. Select Insall button, select 4.4.4_rooted.zip
5. After flashing reboot to bootloader and flash via fastboot tools boot.img file from point 2 above
Code:
fastboot flash boot boot.img
6. Reboot after flashing boot.img
7. Enjoy 4.4.4 with root and writable /system
If something happend with you phone, you can revert to SU2-3.15 via RSDLite, get root, install SafeStrap
PS: You flashing clean from bloatware system! As clean as possible, but everything works fine!
Click to expand...
Click to collapse
....So, does this mean I can finally install some ROMs on my retail Moto? I came from a bootloader-locked 4.4 install with root.

thebenshow said:
....So, does this mean I can finally install some ROMs on my retail Moto? I came from a bootloader-locked 4.4 install with root.
Click to expand...
Click to collapse
i mean, you can use 4.4.4 without write protection

I'm about to try this out to n my xt1080 on 4.4.4... I will update when I'm finished

Can this be used for the droid mini?

I should have read closer I got too excited about about getting root... I already took 4.4.4 OTA... I need root

Am I the only one waiting for clear confirmation from someone who was rooted on 19.6.3 that did the steps in this thread that they are now on 4.4.4 with root and write protection permanently off?

BriCo84 said:
Am I the only one waiting for clear confirmation from someone who was rooted on 19.6.3 that did the steps in this thread that they are now on 4.4.4 with root and write protection permanently off?
Click to expand...
Click to collapse
I am too lol. Been refreshing this thread ever since I ran across it.

Anyone try this?

He is talking about using safestrap on a 4.4 ROM. If you EVER updated to 4.4.4, this will never work for you as you will never be able to disable write-protect to be able to install safestrap.
OP: perhaps you should make this more clear in the original post. Specifically that it will not work if you ever updated to 4.4.4 (Actually, the OP DOES say this...), AND that you're not actually running the 4.4.4 rom, but rather a 4.4.4 stock-based, safestrap-compatible ROM. If you are using this successfully, your bootloader AND your partition table are still on 4.4, which allows you to retain WP-off, safestrap, and root.
But yeah...this will absolutely work if you never updated past 4.4. We have known about this for a long time...I'm surprised a guide was just recently put out about this.

[Q] What to do for gaining Root on 5.0?

Hey Guys,
I had CWM installed on my nakaski since forever and used it to flash KK/PA before switching to Official Stock Lollipop which I'm currently on. I'm getting good performance for now and really not looking forward for any custom kernel or L based ROM.
But I'm definitely looking to root my N7, which I've read is not as simple as flashing the 'Update-SuperSU.zip' in custom recovery due to some kernel limitations on SELinux resulting in bootloops.
So right now, I'm wondering what should I do to root the thing, I can see the two options:
1. Flash a custom kernel which supports root and then flash the SuperSU zip in recovery.
2. Wait for CF to make the 'zygote' service method stable in the 2.27B build and flash on stock recovery.
I'm really looking to avoid bootloops at all if possible. I don't have the stock Lollipop image on me anymore and I'm stuck on a slow internet connection.
Can anyone suggest me what should I do?
If you think custom kernel is the way to go, please give a link to the thread of the custom kernel for stock L. (franco seems to be stuck on KK, right?)
PS: Can anyone give me a working mirror to TWRP based recovery for grouper. Their web portal seems down.

amangupta53 said:
Hey Guys,
I had CWM installed on my nakaski since forever and used it to flash KK/PA before switching to Official Stock Lollipop which I'm currently on. I'm getting good performance for now and really not looking forward for any custom kernel or L based ROM.
But I'm definitely looking to root my N7, which I've read is not as simple as flashing the 'Update-SuperSU.zip' in custom recovery due to some kernel limitations on SELinux resulting in bootloops.
So right now, I'm wondering what should I do to root the thing, I can see the two options:
1. Flash a custom kernel which supports root and then flash the SuperSU zip in recovery.
2. Wait for CF to make the 'zygote' service method stable in the 2.27B build and flash on stock recovery.
I'm really looking to avoid bootloops at all if possible. I don't have the stock Lollipop image on me anymore and I'm stuck on a slow internet connection.
Can anyone suggest me what should I do?
If you think custom kernel is the way to go, please give a link to the thread of the custom kernel for stock L. (franco seems to be stuck on KK, right?)
PS: Can anyone give me a working mirror to TWRP based recovery for grouper. Their web portal seems down.
Click to expand...
Click to collapse
Hi, amangupta53...
You're correct in that rooting lollipop is no longer just a simple matter of flashing a root update package via TWRP or CWM...
A modified kernel (boot.img) also need's to be flashed as well.
---
Probably the easiest way of 'pushing' the usual files, (su binary & SuperSU app) AND flashing a modified root compliant kernel/boot.img... all at the same time, and conveniently... is via Chainfire's CF-Auto-Root method.
This is the method I've used to root both my Nexus 7 and my Nexus 9, both running Lollipop.
---
Download to your PC, the CF-Auto-Root-grouper-nakasi-nexus7.zip from Chainfire..
Unzip it to some folder location on your computer/PC.
Boot the Nexus 7 into it's bootloader... and USB connect it to your PC.
Inside the folder containing the CF-Auto-Root file's you've just unzipped... run the CF-Auto-Root script appropriate to your PC... one of these, root-windows.bat, root-linux.sh or root-mac.sh.
---
If your Nexus 7's bootloader is NOT already unlocked, it will unlock it... AND IT WILL WIPE EVERYTHING ON THE DEVICE, essentially performing a factory reset... so, do be careful, and ensure you have everything that matters backed up elsewhere before you begin.
---
Once completed, reboot your Nexus 7, and you should be rooted.
Good luck, and hope this helps.
Rgrds,
Ged.

GedBlake said:
Hi, amangupta53...
You're correct in that rooting lollipop is no longer just a simple matter of flashing a root update package via TWRP or CWM...
A modified kernel (boot.img) also need's to be flashed as well.
---
Probably the easiest way of 'pushing' the usual files, (su binary & SuperSU app) AND flashing a modified root compliant kernel/boot.img... all at the same time, and conveniently... is via Chainfire's CF-Auto-Root method.
This is the method I've used to root both my Nexus 7 and my Nexus 9, both running Lollipop.
---
Download to your PC, the CF-Auto-Root-grouper-nakasi-nexus7.zip from Chainfire..
Unzip it to some folder location on your computer/PC.
Boot the Nexus 7 into it's bootloader... and USB connect it to your PC.
Inside the folder containing the CF-Auto-Root file's you've just unzipped... run the CF-Auto-Root script appropriate to your PC... one of these, root-windows.bat, root-linux.sh or root-mac.sh.
---
If your Nexus 7's bootloader is NOT already unlocked, it will unlock it... AND IT WILL WIPE EVERYTHING ON THE DEVICE, essentially performing a factory reset... so, do be careful, and ensure you have everything that matters backed up elsewhere before you begin.
---
Once completed, reboot your Nexus 7, and you should be rooted.
Good luck, and hope this helps.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks Ged.
Seems like I missed CF-Auto Root Method in my list. But I guess it's essentially the automated format of option 1 I listed above. I've already switched to SlimROM 0.8 F2FS which included the M-Kernel and thus easy to root. (A friend pointed it out to me, I took the plunge for F2FS)
Thanks again for the detailed solution. I'm sure it'll be useful for anyone looking to root Stock Lollipop with Stock Kernel.
Cheers!

[Stock][LB][5.1.1][PreRooted][SGP311][Germany] 10.7.A.0.222 VMo_De

Android: 5.1.1
Market: Germany
Branding/Operator: None (VMo)
Included:
- UPDATE-SuperSU-v2.46.zip
- TabZ-lockeddualrecovery2.8.21_5.1.1-FIX
- SuperSU-App as System-App
- Modification to reenable RW-Permission to external SDCard by Apps
Install
Flash it via TWRP or CWM.
Downloads
Mega: https://mega.nz/#!nBAE2QLY!NyJwLp2MLKffvHeSAmwRNsSArJYvQUWJKPLXv0aDX-w
MediaFire: http://www.mediafire.com/download/jjgw53sbfgavs46
Info:
Because there is no official working XZDR for first Z-Series, I included the already known fix to the current release.
For those of you, who want to use Xposed, please keep in mind that you need another Version for 5.1.1:
http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979

Oh dear, after years of flashing different roms on different devices I seem to have finally screwed up on this one. My mistake was to flash your pre-rooted 5.1.1 stock rom for SGP321 on my SGP311 - the result not surprisingly was a bootloop. I managed to flash the original stock rom - root it using DoomLord's method and install TWRP recovery. However, when I restore the recovery-made backup of the device's state previous to flashing (pre-rooted 5.0.2. stock rom), apparently successfully, I get a boot loop. I've been through this process of downgrading, rooting, installing recovery numerous times in order to install the correct SGP311 5.1.1 pre-rooted rom, the prerooted 5.0.2 rom which was working before, different versions of TWRP recovery including abZ-lockeddualrecovery2.8.21_5.1.1-FIX, abZ-lockeddualrecovery2.8.21, and abZ-lockeddualrecovery2.8.20, all to no avail. I've also tried complete system wipes in order to remove all traces of the SGP 321 rom but nothing seems to work. I have been able to recover a back-up of a rooted Kitkat stock rom from before installing 5.0.2. There seems to be a problem with Lollipop and the TWRP recovery (and yes I've tried the fixed versions). Any ideas? Should I be using Philz recovery to install the zip instead of TWRP? That's the only thing I haven't tried.

nagusia said:
Oh dear, after years of flashing different roms on different devices I seem to have finally screwed up on this one. My mistake was to flash your pre-rooted 5.1.1 stock rom for SGP321 on my SGP311 - the result not surprisingly was a bootloop. I managed to flash the original stock rom - root it using DoomLord's method and install TWRP recovery. However, when I restore the recovery-made backup of the device's state previous to flashing (pre-rooted 5.0.2. stock rom), apparently successfully, I get a boot loop. I've been through this process of downgrading, rooting, installing recovery numerous times in order to install the correct SGP311 5.1.1 pre-rooted rom, the prerooted 5.0.2 rom which was working before, different versions of TWRP recovery including abZ-lockeddualrecovery2.8.21_5.1.1-FIX, abZ-lockeddualrecovery2.8.21, and abZ-lockeddualrecovery2.8.20, all to no avail. I've also tried complete system wipes in order to remove all traces of the SGP 321 rom but nothing seems to work. I have been able to recover a back-up of a rooted Kitkat stock rom from before installing 5.0.2. There seems to be a problem with Lollipop and the TWRP recovery (and yes I've tried the fixed versions). Any ideas? Should I be using Philz recovery to install the zip instead of TWRP? That's the only thing I haven't tried.
Click to expand...
Click to collapse
Flash stock 5.0.2 ROM with flashtool, root it with kingroot, install recovery 2.8.21 official. Enter TWRP and restore your 5.0.2 backup. Restoring LP backups on earlier firmwares (like 4.4.4 or even 4.3) have some issues and may lead to bootloop.

hi
i`ve tabZ with root running 4.3. to update to 5.1.1 can i directly flash this or i have to follow a special procedure?
thanks and regards

Rootk1t said:
Flash stock 5.0.2 ROM with flashtool, root it with kingroot, install recovery 2.8.21 official. Enter TWRP and restore your 5.0.2 backup. Restoring LP backups on earlier firmwares (like 4.4.4 or even 4.3) have some issues and may lead to bootloop.
Click to expand...
Click to collapse
Many thanks Rootk1t - I followed your instructions and although I had some problems with kingroot (PC version didn't work) I was able to restore my 5.0.2 backup. I then flashed the pre-rooted McBane87's 5.1.1 ROM and this time there were no boot loop problems (it helps if you flash the right ROM, of course). All an interesting learning experience - sometimes you can't make an omelette without breaking some eggs.

mame3876 said:
hi
i`ve tabZ with root running 4.3. to update to 5.1.1 can i directly flash this or i have to follow a special procedure?
thanks and regards
Click to expand...
Click to collapse
If you have a recovery like TWRP or CWM installed, then yes you can directly flash, because it will wipe your hole System-Partition anyway. The other thing is your Data-Partion. You can try to leave it like it is and hope lollipop can deal with it. But keep in mind that this can cause error and also bootloops, which would not appear if you install the ROM in a clean way.
So the "Clean_Way" is:
1. Flash Zip via CWM or TWRP
2. Wipe cache and dalvik cache
3. wipe data
If you want try unclean, then skip step 3.

McBane87 said:
But keep in mind that this can cause error and also bootloops, which would not appear if you install the ROM in a clean way.
Click to expand...
Click to collapse
By my experience upgrading to LP without /data/ wipes go without issues mainly (official pc-companion rewrites only /system/ during upgrade, and doesn't touch /data/ so nothing should break here).
But downgrading from LP to KK with /data/ from LP will give some troubles.

Rootk1t said:
By my experience upgrading to LP without /data/ wipes go without issues mainly (official pc-companion rewrites only /system/ during upgrade, and doesn't touch /data/ so nothing should break here).
But downgrading from LP to KK with /data/ from LP will give some troubles.
Click to expand...
Click to collapse
hi
ok then if i understood correctly i can just download this rom from the link and installed it (i have recovery mounted) and i`ll move directly from my actual 4.3 rooted to 5.1.1 rooted.
will during the process all my data in my microsd vards be deleted?

mame3876 said:
ok then if i understood correctly i can just download this rom from the link and installed it (i have recovery mounted) and i`ll move directly from my actual 4.3 rooted to 5.1.1 rooted.
will during the process all my data in my microsd vards be deleted?
Click to expand...
Click to collapse
Yes, you can upgrade from 4.3. I recommend flashing through TWRP recovery. Place PreRooted_SGP311_10.7.A.0.222_VMo_DE.zip to external microSD, enter recovery, do Wipe cache/dalvik cache/System and install it.
If you don't wipe it manually or by mistake your data on microSD will be untouched. But making backup of everything you need before, is a good thing either

thanks for your reply, how do you find the tablet Z with Lollipo 5.1.1 happy with it?
---------- Post added at 02:29 PM ---------- Previous post was at 02:27 PM ----------
Rootk1t said:
Yes, you can upgrade from 4.3. I recommend flashing through TWRP recovery. Place PreRooted_SGP311_10.7.A.0.222_VMo_DE.zip to external microSD, enter recovery, do Wipe cache/dalvik cache/System and install it.
If you don't wipe it manually or by mistake your data on microSD will be untouched. But making backup of everything you need before, is a good thing either
Click to expand...
Click to collapse
thanks for your reply. last question, do i have to use a specific recovery (twrp or cwz) or the one i installed 1 year ago is good to go for the job?
how do you find the Tab Z with Lollipop 5.1.1, happy with it? i skipped kitkat and remained with 4.3 rooted of course, have to say not bad. do you suggest the upgrade?

mame3876 said:
thanks for your reply, how do you find the tablet Z with Lollipo 5.1.1 happy with it?
---------- Post added at 02:29 PM ---------- Previous post was at 02:27 PM ----------
thanks for your reply. last question, do i have to use a specific recovery (twrp or cwz) or the one i installed 1 year ago is good to go for the job?
how do you find the Tab Z with Lollipop 5.1.1, happy with it? i skipped kitkat and remained with 4.3 rooted of course, have to say not bad. do you suggest the upgrade?
Click to expand...
Click to collapse
Yep, i upgraded. It's nice in performance. I had the latest version of recovery (i was upgrading from 5.0.2). But you try with your existing version or you can update it via flashable.zip

Thx McBane87,,
the rom works great and was easy to install. root ok and original xposed-framework do a good job in this rom. :good:

sm-s903vl to verizon Sm-g900v firmware

Anyone think it be possible to flash the straight talk s5 sm-s903vl to verizon Sm-g900v 6.0.1 firmware in odin? it has the same fcc label as a verizon s5. Just wondering.

gbnm88 said:
Anyone think it be possible to flash the straight talk s5 sm-s903vl to verizon Sm-ng900v 6.0.1 firmware in odin? it has the same fcc label as a verizon s5. Just wondering.
Click to expand...
Click to collapse
I've tried using the said firmware starting from an update all the way to the full tar.md5. No luck. All I get is errors. Being straight talks with Wal-Mart, I believe Wal-Mart bought out the rights to the phone and have had the thing locked down tight. But not impossible. I was able to get root using motochopper 1.1. I noticed that even though it wouldn't let me flash any firmware it would let a kernel module slip by. So I used the kernel module for the G900V_ NCG 4.4.2 and was able to root using mottochopper followed by Supersu . After all that I rebooted into download mode and reflashed the Ph3 kernel mod.

betzj911 said:
I've tried using the said firmware starting from an update all the way to the full tar.md5. No luck. All I get is errors. Being straight talks with Wal-Mart, I believe Wal-Mart bought out the rights to the phone and have had the thing locked down tight. But not impossible. I was able to get root using motochopper 1.1. I noticed that even though it wouldn't let me flash any firmware it would let a kernel module slip by. So I used the kernel module for the G900V_ NCG 4.4.2 and was able to root using mottochopper followed by Supersu . After all that I rebooted into download mode and reflashed the Ph3 kernel mod.
Click to expand...
Click to collapse
can you please provide a short tutorial on how you exactly did it along with some download links? i found moto chopper but couldnt find any kernels online. im in the same boat but havent had any luck at all with root. i just got this phone and its running marshmallow 6.0.1 with model of sm-s903vl. i also wanted to ask that it did for sure worked with no issues of what you did. i accidentally used a kernel of a firmware before on my S4 from verizon and got a hard brick afterwards so im just trying to be cautious about messing with any kernels beings last time i did change a kernel to an earlier part, it gave the hard brick. i want to be sure that this wont do the same thing beings its going from kernel of 6.0 to .4.4. thanks

please let me know. so many people are wondering how to root this phone on 6.0.

Ditto!!!

I have been wondering about this myself. I know the verizon s3 custom roms would work on the straight talk branded s3.

Bump

Does anyone know the link to motochopper 1.1? I would be satisfied with just root privileges.

taymo said:
Does anyone know the link to motochopper 1.1? I would be satisfied with just root privileges.
Click to expand...
Click to collapse
just google it but motochopper alone doesn't give root. I've tried. I've also tried flashing the kernel and it fails so I'm not sure what the person did to get root using that program. Sorry. He won't reply to any messages ether for some reason.

Bump

I found this thread. I am having no luck with it but I am also not as experienced as some... Can someone test this out and let me know if the root method works for them?
https://forum.xda-developers.com/galaxy-s5/general/straight-talk-galaxy-s5-t3318898

HOW TO FLASH G900V (KK 4.4.4) on the SM-S903VL, AND ROOT IT!
betzj911 said:
I've tried using the said firmware starting from an update all the way to the full tar.md5. No luck. All I get is errors. Being straight talks with Wal-Mart, I believe Wal-Mart bought out the rights to the phone and have had the thing locked down tight. But not impossible. I was able to get root using motochopper 1.1. I noticed that even though it wouldn't let me flash any firmware it would let a kernel module slip by. So I used the kernel module for the G900V_ NCG 4.4.2 and was able to root using mottochopper followed by Supersu . After all that I rebooted into download mode and reflashed the Ph3 kernel mod.
Click to expand...
Click to collapse
ODIN will NOT allow FLASHING the BOOT.IMG/ABOOT of the G900V firmware due to the
bootloader being locked down on SM-903VL ( Secure Boot Enabled won't accept G900V kernels! )
But you can downgrade to SM-903VL Factory Test 4.4..2, which allows you to get ROOT!
Once ROOTED & BusyBox is installed, you can "flash" the system/cache IMG's thru the ADB shell as ROOT.
You will end up with SM-903VL 4.4.2 Kernel + G900V KK 4.4.4 System ROM ( Can be rooted with TowelRoot )
KingRoot is only used to Root the Factory Test FW. Once you "flash" the G900V files, you will lose root
(ie. KingRoot is wiped from phone, along with all other data) Simply use TowelRoot to root the G900V FW.
( You will need WIFI or DATA for TR to work though! )
================================================== =================
The Steps I used to go from SM-903VL MM 6.01 to ROOTED G900V KK 4.4.4
( See original posts here: https://forum.xda-developers.com/galaxy-s5/general/downgrade-to-4-4-2-factory-test-t3530449/page8
================================================== =================
download the official stable version of ODIN 3.12.3 here: http://samsungodin.com/
download the SM-903vl 6.01 stock image ( in case you need to recover / de-brick ) https://drive.google.com/open?id=0B4...mkyZkNIMVhrOUk
Download & downgrade to the factory test 4.4.2 SM-903vl ( Using ODIN , use "AP" button for the .MD5 file )
link: https://drive.google.com/open?id=0B4...ndnaWN1cGZ2Snc
root using KINGROOT PC version (windows) - INTERNET REQUIRED for KR to work! here: https://kingroot.net/thank-you-for-d...t-for-windows/
*** NOTE: YOU MUST HAVE STABLE INTERNET CONNECTION for KR to work!. Exit & run KR again if no root.
after ROOT successful, manually install stericson version of busybox: here: https://www.apk4fun.com/apk/6139/
( copy apk to internal SD via PC mtp & install it from MY FILES )
*** install phoneinfo.apk if your LTE DATA does not work - BEFORE "flashing" G900V rom!!!!
The STEALTH-LTE does not appear to work in G900V, so if you need to fix APN
do it now!
download the G900V KK 4.4.4 firmware here: https://www.androidfilehost.com/?fid=23991606952607146
or https://samsung-firmware.org/download/Galaxy S5 (Verizon)/858s/VZW/G900VVRU1ANK2/G900VVZW1ANK2/
(Windows use simg2img https://github.com/KinglyWayne/simg2img_win)
(Linux use a package manager to install simg2img)
Unzip the G900V KitKat Files to a folder, and then:
( use the simg2img command to CONVERT the IMG.EXT4 system & cache files to .IMG format )
use simg2img on cache.img.ext4 also ( *** temporarily rename it to system.ext4.img)
put the ext4 files in the same folder as simg2img.exe
open terminal or CMD prompt, then type:
simg2img system.img.ext4 system.img
simg2img cache.img.ext4 cache.img
then copy the system.img & cache.img to your INTERNAL SD card
next run these commands from linux terminal ( or Windows CMD prompt ):
adb shell
su
stop
dd if=/sdcard/cache.img of=/dev/block/platform/msm_sdcc.1/by-name/cache bs=10485760
dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system bs=10485760
**** Then exit the adb shell by typing exit (enter) 2 times to get back to command prompt, then
adb reboot recovery
let recovery do its thing, then when it reboots and is on the samsung boot screen
quickly do another
adb reboot recovery
then do a wipe data (Factory reset), then reboot
( I downloaded these APKS manually on PC, & copied to SD. WIFI will work on phone, but not DATA until you fix APN! )
install TR.APK ( Towelroot 3.0 ) and ROOT your phone https://towelroot.com/tr.apk
install stericson busybox-free ( found it here: https://www.apk4fun.com/apk/6139/ )
install the PhoneInfo.apk and FIX the APN for LTE data to work (Link on this page FIX APN SETTINGS post)
install XPOSED INSTALLER 2.6.1 ( KITKAT ) if you want xposed - google it
install SElinuxToggle.apk from XDA to be able to change SElinux to Permissive - google it
install SuperSu from playstore, upgrade binary & disable knox - Normal Mode ( as theres no custom recovery )
install ViperFX & ViperXHifi ( The BEST AUDIO MOD by far! Nothing can touch this! ) - google it
install a file manager with root capabilites: Rename the ContextProvider.apk in /system/priv-app/ folder to ContextProvider.apk.old
you should have ROOTED G900V normal KK 4.4.4 rom with XPOSED & Viper4Android Audio
Everything should work, EXCEPT for the FINGERPRINT SCANNER
MOBILE HOTSPOT works!
=========================================
phoneinfo.apk instructions:
Download Phone Info app to SDcard: http://apk.center/down_Phone-INFO-Sa...apkcenter.html
When it boots sideload phone info.apk from SD Open Phone Info app Click on Secret Codes Click launch STEALTHMODE Click LTE APN SETTINGS Hit the + to add APN
Enter the follow information;
Name=Verizon Internet APN=TRACFONE.VZWENTP Proxy=(LEAVE BLANK) Port=(LEAVE BLANK) Username=(LEAVE BLANK) Password=(LEAVE BLANK) Server=(LEAVE BLANK) MMSC=(LEAVE BLANK) Multimedia message proxy=(LEAVE BLANK) Multimedia message port=(LEAVE BLANK) MCC=311 MNC=480 Authorization type=None Click menu in right hand corner and save Select new APN APN type=default,dun Bearer=Unspecified Mobile virtual network operator type=None
Click menu in right corner save. Select new APN reboot phone.
------------------------------------------------------------------------------------------------------------------------------------------------------------------
This info did not come from me. I just copied & pasted it from the URL given above, so I do not take any credit for this.
If this works for someone, post a reply
=====================================================================
*** I DO NOT TAKE CREDIT FOR THIS... I PUT ALL THE PIECES TOGETHER FROM DIFFERENT SOURCES ***
But, did want to share the steps used in more detail to do this! Thanks XDA Members!!!!
---------- Post added at 04:42 PM ---------- Previous post was at 04:08 PM ----------
If you are feeling ADVENTUROUS, you could experiment using Lollipop or Marshmallow G900V system/cache IMGs instead,
following the instructions above ( AT YOUR OWN RISK of course )
You would need to GOOGLE to see if the version of G900V can be rooted first, though.
This may or may not work using the S903VL Factory Test KERNEL 4.4.2 ( BOOT.IMG ) with LL/MM - IDK.
IDK if flashing the ORIGINAL STOCK MM 6.01 KERNEL ( BOOT.IMG ) after ROOTING would give better performance,
or end up causing loss of ROOT.
Any Guinea Pigs out there willing to try? lol.
link to G900V stock fimwares: https://samsung-firmware.org/model/SM-G900V/
(I did flash the MODEM.BIN of the Original SM-903VL MM 6.01 by extracting it from the AP-md5 file, making a .TAR of the modem.bin,
and flashing it using ODIN AP mode. It appears the MM modem is faster than the 4.4.2 Factory test version BTW )
---------- Post added at 04:50 PM ---------- Previous post was at 04:42 PM ----------
taymo said:
I found this thread. I am having no luck with it but I am also not as experienced as some... Can someone test this out and let me know if the root method works for them?
https://forum.xda-developers.com/galaxy-s5/general/straight-talk-galaxy-s5-t3318898
Click to expand...
Click to collapse
I have posted a way to get ROOT on SM-S903VL and convert it to G900V KK 4.4.4.
I have been using it for awhile now and it works great. ROOTED, XPOSED, MOBILE HOTSPOT, etc WORKS.
Just the FIngerPrint scannner doesnt work ( due to mismatched KERNEL / SYSTEM ROM versions )
ALL ELSE IS GOOD!

DeepPurple72 said:
download the SM-903vl 6.01 stock image ( in case you need to recover / de-brick )
Click to expand...
Click to collapse
The Link that you have is dead. Can you repost the link?

gamer82987 said:
The Link that you have is dead. Can you repost the link?
Click to expand...
Click to collapse
I don't have this device but, I did a little searching for the correct and updated links for the downloads from those instructions.
Keep in mind that I don't have this device nor had provided those instructions but, some of those links are outdated as well as not being correctly formatted.
The following is just a list of a handful of the correct and updated links and not all of them since there's a few still good.
PLEASE only use them in place of the others but, still use those instructions
ODIN 3.12.3
https://androidfilehost.com/?fid=745425885120703496
SM-903vl 6.01 stock image:
https://drive.google.com/file/d/0B4954IfsDiYKUmkyZkNIMVhrOUk
Factory test 4.4.2 SM-903vl:
https://drive.google.com/file/d/0B4954IfsDiYKendnaWN1cGZ2Snc
KINGROOT PC version (windows):
http://king.myapp.com/myapp/kdown/img/KingRootSetup_v3.5.0.1157_105203.exe
BusyBox (Stericson):
https://www.apkmirror.com/apk/steph...ericson/busybox-stephen-stericson-60-release/
G900V KK 4.4.4 firmware: here:
https://androidfilehost.com/?fid=746010030569954769
Phone Info app:
https://www.apkmirror.com/apk/vndng...ne-info-★samsung★-3-5-9-android-apk-download/
The SELinux Toggler App (Discontinued)...
Use the SELinux Switch App:
https://androidfilehost.com/?fid=890129502657595824
SuperSu:
https://androidfilehost.com/?fid=889964283620755129
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

Thank You!
I will try these out tonight. Thanks!

[Help] Moto g4 plus root error..please help

Hey...Help me with this..
I tried to root my moto g4 plus using temporary twrp so that i get system updates,It is not working out.
I have used moto g3.. and used this same method for rooting and is successful..
In g4 plus till the last step i.e untill u need to flash supersu it works but there comes error.
Every data is lost and i have to boot into my custom rom backup...
Please suggest something to help me...please

Adarsh balu said:
Hey...Help me with this..
I tried to root my moto g4 plus using temporary twrp so that i get system updates,It is not working out.
I have used moto g3.. and used this same method for rooting and is successful..
In g4 plus till the last step i.e untill u need to flash supersu it works but there comes error.
Every data is lost and i have to boot into my custom rom backup...
Please suggest something to help me...please
Click to expand...
Click to collapse
Can I request some more details please?
OS version?
TWRP version?
Did you unlock your bootloader and enabled OEM unlocking in Developer Settings?
Which rooting method did you use (e.g. did you flash ElementalX kernel https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672 or the superboot method https://forum.xda-developers.com/mo...t-how-to-root-n-firmware-npj25-93-11-t3532556) ?
What error do you get?
EDIT - I understand you're desperate for help resolving this, please don't post the same thing in 3 places if you can.

echo92 said:
Can I request some more details please?
OS version?
TWRP version?
Did you unlock your bootloader and enabled OEM unlocking in Developer Settings?
Which rooting method did you use (e.g. did you flash ElementalX kernel https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672 or the superboot method https://forum.xda-developers.com/mo...-how-to-root-n-firmware-npj25-93-11-t3532556) ?
What error do you get?
Click to expand...
Click to collapse
Here it is
I did not use kernel
Oem done

twrp-3.0.2-0-athene
SuperSU-v2.66
My error was that I could not get booted back on...
It would not turn on..
Then i downloaded another stock rom from xda and got back...im xt1643

All steps are followed until flashing of supersu..The error comes there..is there any xt 1643 users who could suggest a correct reliable and error free method for this

Adarsh balu said:
twrp-3.0.2-0-athene
SuperSU-v2.66
My error was that I could not get booted back on...
It would not turn on..
Then i downloaded another stock rom from xda and got back...im xt1643
Click to expand...
Click to collapse
Couple of things:
Try installing the newer TWRP from here: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
I don't think TWRP 3.0.2 is supported that well.
SuperSU - use the SuperSU 2.78 or the beta https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
I think if you desire root, you'll need a modified kernel (so far, it appears that the stock kernel security prevents rooting, someone correct me if I'm wrong), which may explain the bootloops. Try with the ElementalX kernel method as linked above, seems that people have had luck with it. https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672 You may need phh's Superuser instead.

echo92 said:
Couple of things:
Try installing the newer TWRP from here: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
I don't think TWRP 3.0.2 is supported that well.
SuperSU - use the SuperSU 2.78 or the beta https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
I think if you desire root, you'll need a modified kernel (so far, it appears that the stock kernel security prevents rooting, someone correct me if I'm wrong), which may explain the bootloops. Try with the ElementalX kernel method as linked above, seems that people have had luck with it. https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672 You may need phh's Superuser instead.
Click to expand...
Click to collapse
Thanks..let me test it....
Any way thnq for the suggestions...:good:

Tell me will i be able to update if android O comes for g4 plus..please reply fast

Adarsh balu said:
Tell me will i be able to update if android O comes for g4 plus..please reply fast
Click to expand...
Click to collapse
If android o does arrive, I imagine you'll have to revert back to the stock ROM to update, so removing root and flashing your stock boot image over your existing installation. Alternatively you could fast boot a stock ROM to restore a stock install.
What's the rush anyway, no announcements have even been made for android o...?

echo92 said:
If android o does arrive, I imagine you'll have to revert back to the stock ROM to update, so removing root and flashing your stock boot image over your existing installation. Alternatively you could fast boot a stock ROM to restore a stock install.
What's the rush anyway, no announcements have even been made for android o...?
Click to expand...
Click to collapse
Im using stock rom..with nougat update....
So if o arrives i will need to do what exactly...please share

Adarsh balu said:
Im using stock rom..with nougat update....
So if o arrives i will need to do what exactly...please share
Click to expand...
Click to collapse
Again, Android O hasn't been formally announced yet...
I see you've already gotten an answer from tywinlannister regarding this question https://forum.xda-developers.com/showpost.php?p=71265934&postcount=249
I don't see much to add to his well thought out reply except if you're staying with stock (assuming you're using temporary TWRP):
1) Unroot completely using the SuperSU settings panel or follow the unrooting instructions for your superuser app.
2) Reboot into temporary TWRP, restore your boot.img (if you flashed ElementalX kernel) from within TWRP (if I recall, it's Restore >Select image and then assign it as a boot image). If you did not make a backup of your boot.img, there are images around (e.g. https://forum.xda-developers.com/moto-g4-plus/how-to/1643-indian-version-stock-boot-modem-t3460615 - i don't know if this is for nougat or marshmallow - download and extract the rar file, copy the extracted boot.img to your device and boot into temporary TWRP, then flash the boot.img).
3) Reboot and you should be fully stock - with stock kernel/boot.img, recovery and no root.
1a) As tywinlannister linked, you could just reflash the latest fastboot image which would remove root and give you a stock boot, which would be the best for reliability (which as of this post is this: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369)
Thus, when/if Android O does arrive, you should be able to update via OTA. It's gonna be at least 6-12 months away for the update, if previous Android updates have been anything to go by.