Software info:
Android 8.1
Samsung Experience: 9.5
Security patch level: Aug 2018
No Treble
Build version: J727PVPU4BRH5 or J727PVPS6BSK1 for SM-J727P
Build version: J727VVRU2BRH1 for SM-J727V
Build version: J727VPPVRU2BRH1 for SM-J727VPP
Build version: J727AUCU3BRH2 for SM-J727A
Build version: J727R4TYU1BRH5 for SM-J727R4
Build version: J727TUVU3BRH3 for SM-J727T
Build version: J727T1UVU3BRH3 for SM-J727T1
I have only tested magisks on SM-J727P, When you flash it you need to format your data again and then manually patch via the magisks manager then it will work properly.
SM-J727P (Galaxy J7 Perx)
J727PVPS6BSK1 (Newer)
Full rom download:
https://www.androidfilehost.com/?fid=8889791610682942431
J727PVPU4BRH5 (Older)
Full rom download:
https://www.androidfilehost.com/?fid=1322778262904004250
4 file rom download:
https://www.androidfilehost.com/?fid=1322778262904004263
SM-J727V (Galaxy J7 V)
4 file rom download:
https://www.androidfilehost.com/?fid=1322778262904007457
SM-J727VPP (Galaxy J7 V Prepaid)
4 file rom download:
https://www.androidfilehost.com/?fid=1322778262904007456
SM-J727A (Galaxy J7 2017 AT&T)
4 file rom download:
https://www.androidfilehost.com/?fid=1322778262904007526
SM-J727R4 (Galaxy J7 2017 US Cellular)
4 file rom download:
https://www.androidfilehost.com/?fid=1322778262904007527
SM-J727T (Galaxy J7 2017 T-Mobile)
full rom download:
https://www.androidfilehost.com/?fid=1322778262904011167
SM-J727T1 (Galaxy J7 2017 MetroPCS)
4 file rom download:
https://www.androidfilehost.com/?fid=1322778262904011170
Credits: @dbreed53 for the newer J727PVPU4BSK1 firmware
this can be ported to others J7? ?
J727P update
deadman96385 said:
I have gotten the 2 available firmware packages from easy firmware, One is a full rom package and the other is a traditional 4 file package. I have uploaded both but have only tested the full rom package.
Software info:
Android 8.1
Samsung Experience: 9.5
Security patch level: Aug 2018
No Treble
Build date: Aug 23rd
I have tested magisks, When you flash it you need to format your data again and then manually patch via the magisks manager then it will work properly.
Full rom download:
https://www.androidfilehost.com/?fid=1322778262904004250
4 file rom download:
https://www.androidfilehost.com/?fid=1322778262904004263
Click to expand...
Click to collapse
can you add in a how to Root 8.1.0 for this phone for all of us ! Thank you !!
Hi,
Is there Rom also for SM -G610F .
Magisk
So I flashed it and everything is working fantastic but I still can't get root. I don't have twrp anymore and can't flash twrp over again Odin keeps say fail so how would I format data?? Sorry I'm a noob...
J727P
Shaddow313 said:
So I flashed it and everything is working fantastic but I still can't get root. I don't have twrp anymore and can't flash twrp over again Odin keeps say fail so how would I format data?? Sorry I'm a noob...
Click to expand...
Click to collapse
Use the stock recovery an do a factory reset then flash twrp !
??
peter couniaz said:
Use the stock recovery an do a factory reset then flash twrp !
Click to expand...
Click to collapse
thanks for your quick reply.
So I tried started from scratch I re-flashed the 8.1 rom file, then went in to stock recovery performed data factory reset, tried to flash twrp 3.2.1-1 using odin 3.13.1 said it work but I'm still stuck with stock recovery. So I tried flashing twrp once more and odin says operation failed...
peter couniaz said:
Use the stock recovery an do a factory reset then flash twrp !
Click to expand...
Click to collapse
Wjat is meant by recovery? Is it not flashing factory rom?
Now, I don't think I understand TWRP fully, What it does. Is it used to fix root or system problems?
Thanks
---------- Post added at 11:22 PM ---------- Previous post was at 11:00 PM ----------
peter couniaz said:
Use the stock recovery an do a factory reset then flash twrp !
Click to expand...
Click to collapse
If I flash this update, will I be able to activate the phone, I am outside Sprint and legacy carrier's network. I'm in Africa.
My phone is unusable right now, I flashed August nougat update, I couldn't go past activation screen
Help please
Added AT&T, Verizon, Verizon Prepaid, US Cellular 8.1 firmwares to OP
J727P update
deadman96385 said:
Added AT&T, Verizon, Verizon Prepaid, US Cellular 8.1 firmwares to OP
Click to expand...
Click to collapse
Ok this is what worked for me to get Root !
#1 go into stock recovery data factory reset the phone pull battery !
#2 boot download mod using Odin 3.13.1 install latest twrp make shore before flashing twrp to unlock auto reboot in odin options then flash twrp pull battery again !
#3 boot into twrp wipe data in advanced options then mount system an flash magisk 17.1 zip wipe data again an boot phone setup phone an install magisk manager open manager in popup click yes it run threw an go away after that when ever you open magisk manager the popup will there an just click no thanks ! You should have no reason to open again it should just keep granting your root app access ! Hope this works for you all !!
A note about root; Magisk 17.1 will sometimes lose root. If this happens simply reflash magisk and reboot. The devs are working on it. We aren't the only one's with this problem. There is now a magisk 17.2 canary build which is in testing to bring better support for Oreo/Pie. I've tried it and had very good success so far.
Amazing!!
peter couniaz said:
Ok this is what worked for me to get Root !
#1 go into stock recovery data factory reset the phone pull battery !
#2 boot download mod using Odin 3.13.1 install latest twrp make shore before flashing twrp to unlock auto reboot in odin options then flash twrp pull battery again !
#3 boot into twrp wipe data in advanced options then mount system an flash magisk 17.1 zip wipe data again an boot phone setup phone an install magisk manager open manager in popup click yes it run threw an go away after that when ever you open magisk manager the popup will there an just click no thanks ! You should have no reason to open again it should just keep granting your root app access ! Hope this works for you all !!
Click to expand...
Click to collapse
You sir, are awesome another successful root...
I just have a question on twrp I flashed TWRP 3.2.2-0 because I couldn't get TWRP 3.2.3-0 to work for some reason. But now if I try and make a Back-up, my Data partition is empty and won't successfully back-up.. I can't figure out what I'm doing wrong I formatted Data and flashed no-dm-verity still no luck. Any idea's??
J727P
Shaddow313 said:
You sir, are awesome another successful root...
I just have a question on twrp I flashed TWRP 3.2.2-0 because I couldn't get TWRP 3.2.3-0 to work for some reason. But now if I try and make a Back-up, my Data partition is empty and won't successfully back-up.. I can't figure out what I'm doing wrong I formatted Data and flashed no-dm-verity still no luck. Any idea's??
Click to expand...
Click to collapse
Yes I know we are still having a problem with twrp even twrp 3.2.3.0 ! PS they should be fixing soon with the next update of twrp !
Shaddow313 said:
You sir, are awesome another successful root...
I just have a question on twrp I flashed TWRP 3.2.2-0 because I couldn't get TWRP 3.2.3-0 to work for some reason. But now if I try and make a Back-up, my Data partition is empty and won't successfully back-up.. I can't figure out what I'm doing wrong I formatted Data and flashed no-dm-verity still no luck. Any idea's??
Click to expand...
Click to collapse
Currently TWRP lacks quota storage support, so it can't read the Oreo /data partition. You can remove quota storage from the fstab by using the patch found here. After flashing it TWRP will be able to mount the data partition. There are some downsides though. Disabling quota storage is slightly slower than having it on. And TWRP still won't be able to make/restore a backup unless the partition is less than 649mb in size. There were changes to the bootloader in Oreo that prevents making a backup. You'll reboot midway. TWRP 3.2.3-1 should fix this when it gets released.
J727P update
Spaceminer said:
Currently TWRP lacks quota storage support, so it can't read the Oreo /data partition. You can remove quota storage from the fstab by using the patch found here. After flashing it TWRP will be able to mount the data partition. There are some downsides though. Disabling quota storage is slightly slower than having it on. And TWRP still won't be able to make/restore a backup unless the partition is less than 649mb in size. There were changes to the bootloader in Oreo that prevents making a backup. You'll reboot midway. TWRP 3.2.3-1 should fix this when it gets released.
Click to expand...
Click to collapse
Ok has anyone tried flash empire tweaks zip V1.3 on to the 8.1.0 system yet ? Using current twrp build ?
I'll be adding T-mobile and MetroPCS firmware to op hopefully tonight
J727P update
deadman96385 said:
I'll be adding T-mobile and MetroPCS firmware to op hopefully tonight
Click to expand...
Click to collapse
Can you post the firmware for Virgin mobile an Boost ? Thank you !!
peter couniaz said:
Can you post the firmware for Virgin mobile an Boost ? Thank you !!
Click to expand...
Click to collapse
They are included in the sprint firmware
J727P update
deadman96385 said:
They are included in the sprint firmware
Click to expand...
Click to collapse
Ok thank you wasn't shore about that !
peter couniaz said:
Ok this is what worked for me to get Root !
#1 go into stock recovery data factory reset the phone pull battery !
#2 boot download mod using Odin 3.13.1 install latest twrp make shore before flashing twrp to unlock auto reboot in odin options then flash twrp pull battery again !
#3 boot into twrp wipe data in advanced options then mount system an flash magisk 17.1 zip wipe data again an boot phone setup phone an install magisk manager open manager in popup click yes it run threw an go away after that when ever you open magisk manager the popup will there an just click no thanks ! You should have no reason to open again it should just keep granting your root app access ! Hope this works for you all !!
Click to expand...
Click to collapse
Did this work on the usc variant or....
Related
Android N Preview npc56p (flashable & image with no encryption and dm verification)
This thread is for the first Android N Preview.
For Android N Preview 2 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-2-npc91k-flashable-t3358335
For Android N Preview 3 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-3-beta-npd35k-t3381845
For Android N Preview 4 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-4-beta-npd56n-t3399473
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **** The following are instruction for installing Android N Preview image released by Google on 3/9/2016. After the installation you will have TWRP recovery 3.0.0-1 and the data partition will be erased and unencrypted if you use method 2, which means you will have ~ 3GB more space and ~ 10 seconds faster boot speed **Always backup your data before flashing something a total stranger gives you!
Method 1: Flash update through TWRP recovery
1- You need to have TWRP installed on your phone.
2- Download this flashable zip.
3- Copy to the phone internal storage and flash via recovery.
4- Reboot. Your data should still be intact and your OS is upgraded to N. If your internal storage is unencrypted before flashing it remains unencrypted. Your TWRP is also upgraded to 3.0.0-1.
Method 2: Flash update using a computer
1- ALL of your data including the internal storage will be lost so make a backup. (If you know what you are doing and you are coming from unencrypted Marshmallow you can modify the instructions to not lose data but I won't help you with that).
2- Download this file. Note that it is NOT a flashable zip.
3- Unzip into a folder of your choice on your PC.
4- Open a command window (cmd) and cd to this directory. then run the following:
Code:
flash-all
5- Wait until prompted, then press key to reboot the phone.
6- Your data is wiped and your OS is upgraded to N with unencrypted internal storage. Your TWRP is also upgraded to 3.0.0-1.
Technical details: this is a repacking of the Google image with a modified Kernel and removed userdata and recovery images. Everything else is stock.
Problem downloading from Mega on a mobile browser? Change the page setting to "Request desktop site".
About root
To obtain root after installing this update you should flash SuperSU 2.70 (or higher) in recovery. Get it from here: http://forum.xda-developers.com/apps/supersu/wip-android-n-preview-t3335726. Note that at least at the moment (as of SuperSU 2.70) the root method is a hack solution which requires a lot of further refinement. Many programs are still unable to acquire root and mount the system partition for R/W. However, it is possible to install the android terminal emulator, do an su, mount /system as rw, and do all the modifications within the terminal emulator. Of course you can always use TWRP to modify the system, for which you don't even need to root the device.
Hot dog! First for once... Thanks!
Sent from my Nexus 6 using Tapatalk
#2
will this wipe internal storage ? or only data partition?
For anyone interested...
I enrolled in the Developer Beta program and the OTA worked for me even though I was rooted with SuperSU v2.68.
However, despite installing TWRP 3.0.1 and then SuperSU v2.68 again, root doesn't stick. Fortunately the only critical previously-root-only app I want is a firewall, and Netguard doesn't need root. I can live for a while without Double Tap To Wake, Wakelock detector, Quick Reboot, etc. And the only app that seems to crash is BBC Radio Player, though BBC News and iPlayer still seem ok (warning about libraries, but still plays). And Battery Bot Pro seems to have lost its status bar display...
So it does pretty much what the warnings say - it's stable but not everything will work.
so if i flash this i will still have twrp once rebooted?
kidhudi said:
so if i flash this i will still have twrp once rebooted?
Click to expand...
Click to collapse
if you only flash the boot.img and system.img, then yes. if you flash the whole thing, which includes a stock recovery, itll install the stock recovery. but all you have to do is type in one line into fastboot to reflash twrp.
It would be nice moving forward if Google just made SuperSU/root part of their factory image under developer options. So once you enable developer option, there's a little toggle next to OEM unlock that says "root/SuperSU".
Would make life much easier.
simms22 said:
if you only flash the boot.img and system.img, then yes. if you flash the whole thing, which includes a stock recovery, itll install the stock recovery. but all you have to do is type in one line into fastboot to reflash twrp.
Click to expand...
Click to collapse
kidhudi said:
so if i flash this i will still have twrp once rebooted?
Click to expand...
Click to collapse
The zip doesn't include stock recovery so if you flash everything according to the instructions you will have twrp at the first reboot.
This kernel worked great thanks. I'm still decrypted and didn't have to wipe internal storage. I didn't run the .bat I manually flashed the img files. Wiped data with TWRP.
so can we flash this via twrp?
omaralkha99 said:
so can we flash this via twrp?
Click to expand...
Click to collapse
no, those are IMG format, flash via fastboot.
I'd wait for root ready then flash...
omaralkha99 said:
so can we flash this via twrp?
Click to expand...
Click to collapse
It literally says right next to the link, "Note that it is NOT a flashable zip."
PainToad said:
It literally says right next to the link, "Note that it is NOT a flashable zip."
Click to expand...
Click to collapse
it says twrp recovery in title, so I was wondering....
what about phh superuser? he modified his root to run for android n http://forum.xda-developers.com/and...apable-superuser-t3216394/page30#post65748721
chapelfreak said:
what about phh superuser? he modified his root to run for android n http://forum.xda-developers.com/and...apable-superuser-t3216394/page30#post65748721
Click to expand...
Click to collapse
I flashed that boot img and now i am encrypted and boot-looping. No access to SD card.
Does this build have new bootloader and radio? If so, is it backward compatible to Marshmallow roms or do we need to flash back M bootloader and radio to get M roms work?
---------- Post added at 02:31 PM ---------- Previous post was at 02:29 PM ----------
PainToad said:
It literally says right next to the link, "Note that it is NOT a flashable zip."
Click to expand...
Click to collapse
I lold at this. :laugh::laugh::laugh::laugh:
Flashed and everything is working great except I have no LTE and the only internet I get is on wifi. Running on Verizon sim on StraightTalk.
kclive said:
Flashed and everything is working great except I have no LTE and the only internet I get is on wifi. Running on Verizon sim on StraightTalk.
Click to expand...
Click to collapse
Toggle on and off airplane mode. Turn off wifi and see if it works. I was at work and had to do this a few times
Flashed phh kernel (su-noverity - 3rd one) and installed this superuser. I now have root working.
OnePlus Team has finally rolled out long-awaited Marshmallow Update. This time, it isn't community build or beta, it is a STABLE update!
This post will guide you to upgrade from 2.2.2 to 3.1.2 for both non-rooted and rooted users.
Disclaimer:
Code:
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
For non-rooted, unmodified system users (who haven't tinkered anything with the device's software):
1a. You must have received a notification to update to OOS 2.2.3
Download it, and hit reboot now! This will automatically install the update which will prepare your device to install MM update.
1b. If you haven't received the update notification for 2.2.3 then download it manually from here - https://goo.gl/NkZm2I
Place it in the root directory of Internal Storage (not inside any folder, just directly on Internal storage) and then enter recovery mode by turning off your phone and then pressing Power button + volume down button at the same time. Once you get into recovery, select Install from Internal Storage and the select your file and flash it!
Congratulations, now you are on OOS 2.2.3!
Download MM OOS 3.1.2 from here - http://s3.amazonaws.com/oxygenos.on...OTA_017_all_201609231354_e675a52db5a044e7.zip
and place it on your SD card again, like above, go to recovery and flash the file!
You are now on Official Oxygen OS 3.1.2 MM Update!
For rooted users, who have modified system:
1. Download the zip http://s3.amazonaws.com/oxygenos.on...OTA_017_all_201609231354_e675a52db5a044e7.zip and place it on your SD Card or Internal Storage
2. Go to your recovery (TWRP is preferred)
3. Wipe System, Data, Cache, and Dalvik Cache
4. Select Install and navigate to your file location, select your file and flash it!
5. Flash https://drive.google.com/file/d/0B4K5cvm1zdldcmZpc3RuVnRjUUE/view to get root access!
6. Reboot! Enjoy your MM Update!
(Optional) These are steps I followed for a safer install:
1. Took the whole backup of 2.2.2 from official TWRP
2. Flashed Whole 2.2.2 zip from here - http://downloads.oneplus.net/oneplus-x/oneplus_x_oxygenos_2.2.2/ which I had already downloaded
3. Flashed Stock Lollipop recovery
4. Unrooted my phone
5. Locked and unlocked my bootloader (don't know why I was getting locked bootloader error while flashing blu-spark twrp so did it)
6. Unrooted my phone
7. Flashed 3.1.2 zip from stock lollipop recovery
8. Flashed blu-spark TWRP using fastboot
9. Flashed modified SuperSU
10. Restored just data partition from my 2.2.2 backup and wiped cached.
This way is long and tedious but ensures you get the data, which was important for me.
Edit: Above process can be applied to install Oxygen OS 3.1.3 (link below) Directly! Hope you have a pleasant experience on Marshmallow, cause I'm definitely loving it
Feel free to ask any queries!
Useful Links: -
1. Stock Lollipop Recovery - https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img
2. Official TWRP Recovery - https://dl.twrp.me/onyx/
3. Blu Spark Recovery - http://forum.xda-developers.com/devdb/project/dl/?id=20236
4. SuperSU for OOS 3.x.x - https://drive.google.com/file/d/0B4K5cvm1zdldcmZpc3RuVnRjUUE/view
5. Unbrick Guide - http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
6. Official Oxygen OS 3.1.2 link - http://s3.amazonaws.com/oxygenos.on...OTA_017_all_201609231354_e675a52db5a044e7.zip
7. SD Card Writable fix in MM - http://forum.xda-developers.com/android/software/fix-extsd-fix-v1-0b-2016-01-18-t3296266
6. Official Oxygen OS 3.1.3 link - http://downloads.oneplus.net/oneplus-x/oneplus_x_oxygenos_3.1.3/
Credits: Joshwin Aranha, OnePlus Team, Google and everyone who I forgot to mention
Hit Thanks if this post helped you!
The 3.1.2 official update isn't in oneplus download center. And it seams that there is no mention in oneplus forums.
Is your info legit?
Sent from my ONE E1001
OP didn't announced officially about oxygen os 3.1.2 but sone OPX users have installed it
Strange......
This rom file can be installed as stand alone? Im currently on community 3.1.1.
Sent from my ONE E1001
sniper20 said:
Strange......
This rom file can be installed as stand alone? Im currently on community 3.1.1.
Sent from my ONE E1001
Click to expand...
Click to collapse
It can be flashed directly using TWRP (use Latest TWRP by blu spark)
sniper20 said:
The 3.1.2 official update isn't in oneplus download center. And it seams that there is no mention in oneplus forums.
Is your info legit?
Sent from my ONE E1001
Click to expand...
Click to collapse
It was announced but then again removed. I personally saw and downloaded it from there.
Mystery solved.... Hehe. I ll install it via official recovery.
Sent from my ONE E1001
sniper20 said:
Mystery solved.... Hehe. I ll install it via official recovery.
Sent from my ONE E1001
Click to expand...
Click to collapse
Let me know how that works out for you!
I'm using Sultan's CM 13. Can i flash Oxygen via Blu_spark TWRP after factory reset ?
aadnanrulz said:
I'm using Sultan's CM 13. Can i flash Oxygen via Blu_spark TWRP after factory reset ?
Click to expand...
Click to collapse
You will have to wipe system, data and both cache and then flash the zip!
Sachin7843 said:
Let me know how that works out for you!
Click to expand...
Click to collapse
I ll post today late at night.....
Sent from my ONE E1001
Thanks mate !
Do we need to upgrade to 2.2.3 first or upgrade from 2.2.2 is also fine ?
Szaby59 said:
Do we need to upgrade to 2.2.3 first or upgrade from 2.2.2 is also fine ?
Click to expand...
Click to collapse
I didn't have right resources with me for now so I just flashed 2.2.2 zip (had downloaded the whole zip from downloads.oneplus.net), unrooted and flashed stock recovery (check the main post for links) and directly flashed 3.1.2 zip! Worked flawlessly!
Sachin7843 said:
I didn't have right resources with me for now so I just flashed 2.2.2 zip (had downloaded the whole zip from downloads.oneplus.net), unrooted and flashed stock recovery (check the main post for links) and directly flashed 3.1.2 zip! Worked flawlessly!
Click to expand...
Click to collapse
i have two questions here
1. were you able to format external SD card as internal?
2.how to flash modified/original TWRP after install OOS 3.1.2?
I flashed and rooted it properly but xposed isn't active. What version do I have to flash?
Which custom recovery is supported for this ROM ? I couldn't install the package using official twrp recovery. Had to switch to official recovery to install the ROM
Darkside1984 said:
I flashed and rooted it properly but xposed isn't active. What version do I have to flash?
Click to expand...
Click to collapse
Ok, I answer myself: xposed sdk23 arv version. Everything works fine (I've installed all zips by custom recovery).
working on twrp
just dirty flashed over oos 3.1.1 with bluspark latest recovery & working well
nitheshg said:
i have two questions here
1. were you able to format external SD card as internal?
2.how to flash modified/original TWRP after install OOS 3.1.2?
Click to expand...
Click to collapse
I couldn't understand your question 1... for your second question - I flashed 3.1.2, unlocked bootloader, flashed Blu-spark's TWRP, flashed Modified Super SU and then restored just Data from my 2.2.2 backup!
UPDATE 14.05.2017: Chainfire has released autoroot for Galaxy S5 Mini G800F based on firmware 6.0.1. It can be downloaded from the official CF Autoroot website (direct link to the G800F file). It is by far the easiest and fastest method for getting root access on your device without the need for TWRP.
Procedure for rooting with CF autoroot:
1. Charge your S5 Mini's battery to at least 80% and make sure you have Samsung USB drivers installed on your PC
2. Enable USB debugging on the S5 Mini
3. Download the CF autoroot file from the link above and unpack the zip archive
4. Open ODIN as administrator (right click -> Run as administrator)
5. Put the S5 Mini in download mode and connect it via USB cable to the PC
6. After ODIN recognizes the device, click "AP" and select the autoroot file
7. Click "Start" and wait for the process to finish - shouldn't take more than a few seconds
8. When the log in ODIN says "Disconnected", unplug the USB cable from the phone and wait for it to restart itself
9. Verify proper root with a tool like Root Checker
If you want to have TWRP recovery and Xposed framework, use the guide below.
This method applies only to the S5 Mini G800F variant running Android 6.0.1. Trying this on other variants may result in bricking your device. I used this procedure to get root access and Xposed working on my European S5 Mini G800F using a German (DBT) Marshmallow firmware. Use at your own risk, I'm not responsible for anything that happens to your device. Note that this procedure voids your warranty. This guide assumes that you already have TWRP recovery or know how to flash it.
Backup everything important like contacts and photos before you begin.
Requirements for this method to work:
unrooted Samsung Galaxy S5 Mini G800F running official stock Android 6.0.1 Marshmallow
Samsung USB driver
enable USB debugging
charge your phone's battery to 100% just in case
TWRP Recovery 3.0.2 installed Official TWRP Recovery 3.1.1 is available now - check out this thread for download links
IMPORTANT NOTE ABOUT RECOVERY: Official TWRP now available
Procedure for getting root access:
1. Download Chainfire's SuperSU v2.78 SR5 [link] and store the zip file in the phone's internal memory or SD card.
2. Boot into TWRP recovery, navigate to the SuperSU zip and flash it, reboot after it finishes.
3. You should now see the SuperSU icon, open it and update the binary. Verify proper root with a tool like Root Checker.
Congratulations, you have successfully rooted your G800F! If you only want root - stop here, you're done.
Procedure for getting Xposed Framework:
1. After rooting your S5 Mini, download Xposed v87.1 built by wanam [link], Xposed uninstaller [link], and Xposed Installer APK [link]. Put all 3 files on the phone's internal memory or SD card.
2. Boot into TWRP recovery, navigate to the file named "xposed-v87.1-sdk23-arm-custom-build-by-wanam-20161125.zip" and flash it.
3. After the flashing is finished, wipe cache and dalvik then reboot.
4. Using a file manager, navigate to where you put the Xposed Installer APK and install it.
5. Open it and confirm that Xposed is installed properly.
weird enough all those files where already on my pc. i just wanted to know if it would work
it says no root
Zakipoophead27 said:
it says no root
Click to expand...
Click to collapse
Which firmware version are you trying to root and did you use the exact files I've linked?
kom-pakt said:
Which firmware version are you trying to root and did you use the exact files I've linked?
Click to expand...
Click to collapse
The netherland marshmallow firmare. And i have used all the files you linked. I even tried other one's. None work
I also have 6.0.1 Germany DBT but this didn't root my s5 mini
Tomislav3383 said:
I also have 6.0.1 Germany DBT but this didn't root my s5 mini
Click to expand...
Click to collapse
Same for me - rooting (Germany DBT) according to your instructions didn't work
Gesendet von meinem kminilte mit Tapatalk
Zakipoophead27 said:
The netherland marshmallow firmare. And i have used all the files you linked. I even tried other one's. None work
Click to expand...
Click to collapse
Tomislav3383 said:
I also have 6.0.1 Germany DBT but this didn't root my s5 mini
Click to expand...
Click to collapse
Helius61 said:
Same for me - rooting (Germany DBT) according to your instructions didn't work
Gesendet von meinem kminilte mit Tapatalk
Click to expand...
Click to collapse
When you flash the SuperSU observe the log during the process, does it reboot by itself after posting this?
Code:
******************
SuperSU installer
******************
- Mounting /system, /data and rootfs
- Extracting files
- Detecting system compatibility
If it reboots after this, turn off your phone and boot into recovery, go to "Wipe" and wipe cache and dalvik. Immediately after that try to flash the SuperSU again, if successful it should post this:
Code:
******************
SuperSU installer
******************
- Mounting /system, /data and rootfs
- Extracting files
- Detecting system compatibility
- System-less mode, boot image support required
- Creating image
- Mounting image
- Creating paths
- Removing old files
- Placing files
******************
Boot image patcher
******************
and then some more lines, at the end it should say "Done!" and then give you the option to reboot. Remember if the flashing is successful you should reboot manually, if the phone reboots by itself then the flashing failed.
Note that I always recommend to start with a freshly installed firmware i.e. wipe the entire phone, flash new firmware, flash TWRP 3.0.0 and then flash SuperSU.
Thank you very much for your instant support. I'm currently traveling and I'll try your solutions once I'm back home again. Then, I'll provide an update whether it works or not.
kom-pakt said:
When you flash the SuperSU observe the log during the process, does it reboot by itself after posting this?
Code:
******************
SuperSU installer
******************
- Mounting /system, /data and rootfs
- Extracting files
- Detecting system compatibility
If it reboots after this, turn off your phone and boot into recovery, go to "Wipe" and wipe cache and dalvik. Immediately after that try to flash the SuperSU again, if successful it should post this:
Code:
******************
SuperSU installer
******************
- Mounting /system, /data and rootfs
- Extracting files
- Detecting system compatibility
- System-less mode, boot image support required
- Creating image
- Mounting image
- Creating paths
- Removing old files
- Placing files
******************
Boot image patcher
******************
and then some more lines, at the end it should say "Done!" and then give you the option to reboot. Remember if the flashing is successful you should reboot manually, if the phone reboots by itself then the flashing failed.
Note that I always recommend to start with a freshly installed firmware i.e. wipe the entire phone, flash new firmware, flash TWRP 3.0.0 and then flash SuperSU.
Click to expand...
Click to collapse
Wiped cache and dalvik, got the same lines you posted, rebooted, but root is still not working.
Tomislav3383 said:
Wiped cache and dalvik, got the same lines you posted, rebooted, but root is still not working.
Click to expand...
Click to collapse
Same for me
Does this root trigger the knox counter?
Hello, had the same problem . No root after reboot.
You need to use an older twrp.
With 2.8.1.0 it all works
i did it!
it works but you gotta have twrp 3.0.2-0 and then flash the zip file.
pop ups where blocked so i just changed it from always ask to always allow.
you gotta install twrp 3.0.0-0 and then flash the twrp 3.0.2-0 .img to recovery.
after that just flash the superSU zip and your done.
hope it works for you
Helius61 said:
Thank you very much for your instant support. I'm currently traveling and I'll try your solutions once I'm back home again. Then, I'll provide an update whether it works or not.
Click to expand...
Click to collapse
Glad I can help, also check out the other solutions posted in the meantime.
Dark_Horse said:
Does this root trigger the knox counter?
Click to expand...
Click to collapse
Yes.
Snowgay said:
Hello, had the same problem . No root after reboot.
You need to use an older twrp.
With 2.8.1.0 it all works
Click to expand...
Click to collapse
Zakipoophead27 said:
i did it!
it works but you gotta have twrp 3.0.2-0 and then flash the zip file.
pop ups where blocked so i just changed it from always ask to always allow.
you gotta install twrp 3.0.0-0 and then flash the twrp 3.0.2-0 .img to recovery.
after that just flash the superSU zip and your done.
hope it works for you
Click to expand...
Click to collapse
It seems that the culprit for the failed rooting were the different versions of TWRP you were using. I will add links to 2 versions of TWRP and a note about this in the main post.
Can someone help me? I did it like in the tutorial but it does not work. Thanks all
Scharnhorst1939 said:
Can someone help me? I did it like in the tutorial but it does not work. Thanks all
Click to expand...
Click to collapse
What version of twrp do you have?
Scharnhorst1939 said:
Can someone help me? I did it like in the tutorial but it does not work. Thanks all
Click to expand...
Click to collapse
I keep updating the first post with additional information and links, read it again and follow the instructions carefully without skipping any of the steps.
thanks for answer. Now it work with Version 2.8.0
Scharnhorst1939 said:
thanks for answer. Now it work with Version 2.8.0
Click to expand...
Click to collapse
Good to hear, version 3.0.2 works too and is more up to date.
This guide is for update within versions if you are rooted, if not, simply download and install de ota or with FF.
If you update to B394 from any version, downloading the last complete packet in update system, it locks the bootloader !!! be advised
If you update to B399 or B401, B402 from B394, downloading the last complete packet in update system, DO NOT LOCK the bootloader !!! good news
My first problem was when I was in B380 and rooted , the b389 ota arrived...then I unroot, put stock recovery and unistalled busybox, but ota failed at 8%
The solution to this :
1 - flash stock recovery from version you have
2 - download the last complete packet in update system , for me 2.41 Gb, not the ota
3 - (optional but useful for future) connect to pc and copy the 3 files downloaded the update in HWOUC to pc
4 - make the normal update in update system
7 - copy supersu 2.82.zip original file or Magisk to SD
8 - Flash last twrp recovery twrp-3.1.1-1-frd , enter in twrp recovery and:
9 - Tick the option "Keep vendor partition mounted" inside OpenKirin in Settings (last option in settings) for me is ticked as default
10 - Make a backup of boot (for future) if you want
11- flash supersu 2.82 original or Magisk
12 - reboot and it's done!!!!!!!!
Update to B394
if you have done all the process and you want now to update to b394, you can uninstall first supersu within options menu saying yes to all questions when uninstalling and without errors or bad uninstallation; then, delete binaries of busybox, flash stock recovery and try to install ota...for me the ota not installed and done with errors.
Then I installed b394 full and locked my bootloader, forcing me to format all because i unlocked the bootloader (remember to activate oem bootloader unlock on and usb depuration on).
After installing the same twrp recovery, I tested the magisk v14 and works perfect, but with an inconvenient, you have to disable the option of magisk manager "magisk hide" to work with fingerprint ,At version 15.3 I didn't see this error.
B394 to B399
Tried the uninstaller of magisk flashed with twrp to unroot and then put the stock recovery and failed, then I flashed stock boot and failed ....finally it worked downloading the last complete packet in update system.Then the habitual, flash twrp recovery, magisk v15.3 from twrp and magisk manager v5.5 in android...and worked perfect
B399 to B401
This time I only unistalled binaries from busybox and flashed stock recovery; then launched Full update (2.41 Gb) without problems.Then flashed twrp, magisk 15.3 from twrp as usual and nothing more...magisk manager detected all ok and I have a rooted device again.
B401 to B402
Simplified the process, now only flash the stock recovery 401 and make the full update packet (2.41Gb). Then flash twrp, enter in twrp, flash magisk 16.0, reboot and that's all. Install busybox script, adaway hosts and done.
Notes:
1 - If the system downloaded automatically the small ota update. you must to try to update with an obvious error, then you can download the full update packet.
1 - the installation of magisk is simple, in twrp flash the magisk.zip , reboot and install magisk manager to control all. This is another app to root and don't need supersu. The advantages to make this is magisk hide, it permits to work with apps that can't work if your phone is rooted.
Wow awsome guide. Thanks alot bro .+1
gopinaidu77 said:
Wow awsome guide. Thanks alot bro .+1
Click to expand...
Click to collapse
happy to help!
9 - Tick the option "Keep vendor partition mounted" inside OpenKirin in Settings (last option in settings) for me is ticked as default
pla can y help for this option
warindo said:
9 - Tick the option "Keep vendor partition mounted" inside OpenKirin in Settings (last option in settings) for me is ticked as default
pla can y help for this option
Click to expand...
Click to collapse
in the options of the twrp, last tab , there's a thick that says this
deadko said:
in the options of the twrp, last tab , there's a thick that says this
Click to expand...
Click to collapse
Bro , y u should mount vendor?
warindo said:
9 - Tick the option "Keep vendor partition mounted" inside OpenKirin in Settings (last option in settings) for me is ticked as default
pla can y help for this option
Click to expand...
Click to collapse
gopinaidu77 said:
Bro , y u should mount vendor?
Click to expand...
Click to collapse
to root correctly with supersu original version
deadko said:
to root correctly with supersu original version
Click to expand...
Click to collapse
But i dont think modifying vendor part is good .
gopinaidu77 said:
But i dont think modifying vendor part is good .
Click to expand...
Click to collapse
I didn't say nothing to modify nothing, I said thick this option on, and in my case, I did nothing because is marked by default.
deadko said:
I did nothing to modify nothing, I said thick this option on, and in my case, I do nothing because is marked by default.
Click to expand...
Click to collapse
Oh ,but i request u to remove that point. Since ticking that mean no sense as it allows to modify vendor part
gopinaidu77 said:
But i dont think modifying vendor part is good .
Click to expand...
Click to collapse
gopinaidu77 said:
Oh ,but i request u to remove that point. Since ticking that mean no sense as it allows to modify vendor part
Click to expand...
Click to collapse
I didn't invent that part myself, is the rooting instructions I read in twrp 3.1.1-1 (you can go to the post I linked, and read it) , and only knows that it works
deadko said:
I didn't invent that part myself, is the rooting instructions I read in twrp 3.1.1-1 (you can go to the post I linked, and read it) , and only knows that it works
Click to expand...
Click to collapse
Ok , thanks though
On point 4 - download complete package - but where? On update app there offer only ota update package not full.
Nortonko said:
On point 4 - download complete package - but where? On update app there offer only ota update package not full.
Click to expand...
Click to collapse
at the tab up to the right in update system
Nortonko said:
On point 4 - download complete package - but where? On update app there offer only ota update package not full.
Click to expand...
Click to collapse
Click on 3 dots on the top right corner . U will see the option.
deadko said:
4 - download the last complete packet in update system , for me 2.41 Gb, not the ota
Click to expand...
Click to collapse
My option is greyed out, what should i do?
Nortonko said:
On point 4 - download complete package - but where? On update app there offer only ota update package not full.
Click to expand...
Click to collapse
fabh2o said:
My option is greyed out, what should i do?
Click to expand...
Click to collapse
the ota is avaliable for you?
deadko said:
the ota is avaliable for you?
Click to expand...
Click to collapse
Yes i'm downloading it right now
Edit: i'm downloading the 2,41 gb update, thanks for the support.
I had B381, TWRP & Root and I just used points from guide - 2.2,3,6,7,8,9,11,12. I had to remove SuperSU in the app - complete unroot option. Flashed stock recovery.img (and recovery2.img) in fastboot mode, which I extracted from my firmware version update.app. Restarted the device and did a full OTA update to B389, hard reset, flashed latest TWRP 3.1.1-1 in fastboot mode, than installed modified SuperSU for EMUI 5.0 from XDA and all is done.
Snowjack said:
I had B381, TWRP & Root and I just used points from guide - 2.2,3,6,7,8,9,11,12. I had to remove SuperSU in the app - complete unroot option. Flashed stock recovery.img (and recovery2.img) in fastboot mode, which I extracted from my firmware version update.app. Restarted the device and did a full OTA update to B389, hard reset, flashed latest TWRP 3.1.1-1 in fastboot mode, than installed modified SuperSU for EMUI 5.0 from XDA and all is done.
Click to expand...
Click to collapse
very large process, but you make a hard reset, and my process is to preserve data and use original supersu not the modified , thanks for info
DISCLAIMER: YOU ARE RESPONSIBLE FOR WHAT YOU DOThe only reason behind posting this guide is because now we have a way to fix device if any unusual things happen after flashing beta builds. Beginners & noobs who doesn't have any idea about flashing stuff should stay away.
PREREQUISITES:
1. Bootloader Unlocked Device
2. OrangeFox
3. Stable OZIP (Android 10 | realmeUI 1.0 | C35)
4. Beta ZIP (Android 11 | realmeUI 2.0 | F06)
5. Unofficial OrangeFox beta build (For realmeUI 2.0 A11 FW only)
6. realmeUI 2.0 stock recovery
7. A11 VBMETA
8. Patched VBMETA
PROCESS TO FLASH:
1. Just to be on safer side we are going to make sure everything is stock & all partitions are unmodified. So reflash latest Stable OZIP (C35) via OrangeFox.
2. Format data & reboot to System (This is optional but better to do it, we never know what might happen with realme device)
3. Reboot back to Bootloader if realmeUI 1.0 boots fine
4. Flash OrangeFox build which you used previously & also flash patched vbmeta (fastboot flash vbmeta patched_vbmeta.img)otherwise you get "Boot is destroyed........"
5. Boot into custom recovery & copy downloaded Beta ZIP
6. Flash the Beta ZIP & format data.
7. Reboot to System. realmeUI 2.0 should boot now.
COMMON ISSUES & FIXES:
1. Device stuck at white realme splash logo
Sol. Few people reported it booted when they flashed patched vbmeta so you can first try that. If doesn't work then you can flash A11 vbmeta (fastboot flash vbmeta vbmeta.img) attached here & reboot to system
2. Device stuck at Yellow realme boot animation
Sol. If it's stuck for more than 2-3mins then reboot to bootloader & format data by executing fastboot erase userdata ., never do fastboot -w it's messing up data partition in A11 due to new changes introduced by realme
3. Stuck in bootloader (fastboot)
Sol. Flash the unofficial OrangeFox rescue build & boot into it, copy C35 OZIP to internal storage. Flash it & format data. Reboot to System. Wait for public realmeUI 2.0 release.
4. Unofficial OrangeFox beta build stuck at Ofox splash & display keeps blinking
Sol. This happens because Ofox can't decrypt realmeUI 2.0 data, only way to boot this ofox build properly is by formatting data, reboot back to bootloader. fastboot erase userdata
5. Device doesn't have realmeUI 2.0 Stock Recovery
Sol. Flash the attached stock recovery
reserved
Congrats! Will try now
EDIT: Works fine but just 2 hints.
1: Don't Use TWPR 3.5.0_9 or you will get Zip Treble Error
2: After you flash RUI 2.0 it's a MUST flash A11 VBMETA
Can i Flash on Locked Bootloader device via stock recovery or filemanager currently i am c 34 locked bootloader
bharatgsp said:
Can i Flash on Locked Bootloader device via stock recovery or filemanager currently i am c 34 locked bootloader
Click to expand...
Click to collapse
na it doesn't work
ChromiumPD said:
Congrats! Will try now
EDIT: Works fine but just 2 hints.
1: Don't Use TWPR 3.5.0_9 or you will get Zip Treble Error
2: After you flash RUI 2.0 it's a MUST flash A11 VBMETA
Click to expand...
Click to collapse
Right will update guide, thank you
What does the check look like that prevents the stock recovery from accepting to flash the beta build (if you try to upgrade from C.35)?
kurtextrem said:
What does the check look like that prevents the stock recovery from accepting to flash the beta build (if you try to upgrade from C.35)?
Click to expand...
Click to collapse
Stock recovery only accepts signed OZIP/ZIP like the ones uploaded in their website, OTA updates we receive are signed with different certificate that's why installing those custom OZIPs fail if we do it manually.
It can't install on TWRP 3.4.0.0 -> Error this package is for RMX1931L1, this is a ""
Zippka224 said:
It can't install on TWRP 3.4.0.0 -> Error this package is for RMX1931L1, this is a ""
Click to expand...
Click to collapse
edited guide, use ofox only. TWRP doesn't seem to work for everyone.
Hi, first thanks for the post.
I would like to ask you if there is a way to revert back to c35 after?
Thank you in advance
4j17h said:
Stock recovery only accepts signed OZIP/ZIP like the ones uploaded in their website, OTA updates we receive are signed with different certificate that's why installing those custom OZIPs fail if we do it manually.
Click to expand...
Click to collapse
Thank you. I wonder how the software update works then? How does the software update "app" manage to flash those builds then?
Tierri said:
Hi, first thanks for the post.
I would like to ask you if there is a way to revert back to c35 after?
Thank you in advance
Click to expand...
Click to collapse
Well there are two ways, we can use stock recovery to downgrade from beta builds to C34
Another way would be to flash unofficial Ofox build, copy C34 OZIP to internal storage & flash it.
kurtextrem said:
Thank you. I wonder how the software update works then? How does the software update "app" manage to flash those builds then?
Click to expand...
Click to collapse
OTA updater app is verifying the update & rebooting to stock recovery, so if we can figure out the same way we can install custom ozips via stock recovery too
How would you recommend to bring over apps & their settings to A11? After formatting data they'll be lost. Which backup method is able to restore them? Have you rooted it already?
Magisk?
Cool ! It works fine thank you.
but I noticed that the "Unofficial OrangeFox beta build" cant mount internal storage issue with following error : "could not mount /data and unable to find crypto footer"
So is there another way to Root my device without wiping data?
Hi
First Thank you for this post .
I want to restore a stock recovery UI 1.0 now i am using orangefox recovery on C.34
can i restore without format data or waiting UI 2.0 stable ??
Many Thanks
Hi,
I've followed the steps and no errors. After reboot, the system stucks at Realme white logo. How it's said on common issues, i've flashed then A11 vbmeta, and the same. Ive waited about 10minutes and it keeps there. I've tried flash the Ofox recovery again to repeat the process but now I can't get Ofox working. I can access fastboot and if I try reboot to recovery, it symply reboots to bootloader... What should I do? I also tried all the options in common issues but without success...
Thanks
tuga49 said:
Hi,
I've followed the steps and no errors. After reboot, the system stucks at Realme white logo. How it's said on common issues, i've flashed then A11 vbmeta, and the same. Ive waited about 10minutes and it keeps there. I've tried flash the Ofox recovery again to repeat the process but now I can't get Ofox working. I can access fastboot and if I try reboot to recovery, it symply reboots to bootloader... What should I do? I also tried all the options in common issues but without success...
Thanks
Click to expand...
Click to collapse
try to install patched vbmeta its work form me
So for me I dirty flashed the f06.zip beta on c.35 in official [email protected]_1 release and flashed vbmetaA11 but it failed to then i flashed patched_vbmeta.img and voila it booted just fine and optimizing apps appeared.
Thanks very much to Original Poster we can now use Realme UI 2.0 because of him.
Thanks a lot once again