Database Info

[ROM] Stock RUU 1.32.651.1 | Update.zip Format

This is a download for the stock evo rom, rooted and in update.zip format. Please note that you will NOT be able to just flash this on your phone and have root. This is here for you to be able to have a totally stock rom (with root, superuser, and debugging turned on) once you do root your Evo. Those instructions will be coming soon. So again remember... for right now this doesn't technically serve you any purpose. However once you root your Evo, you can use this to flash a totally stock rom that is rooted.
Not much else to say here.
Base: Supersonic_1.32.651.1
Download: http://geekfor.me/evo/21/stock-evo-update-zip

flipzmode said:
This is a download for the stock evo rom, rooted and in update.zip format. Please note that you will NOT be able to just flash this on your phone and have root. This is here for you to be able to have a totally stock rom (with root, superuser, and debugging turned on) once you do root your Evo. Those instructions will be coming soon. So again remember... for right now this doesn't technically serve you any purpose. However once you root your Evo, you can use this to flash a totally stock rom that is rooted.
Not much else to say here.
Base: Supersonic_1.32.651.1
Download: http://geekfor.me/evo/21/stock-evo-update-zip
Click to expand...
Click to collapse
Thumbs up!

killer! thanks!

is it possible to get more details on what the exact changes are between this and stock?
the su binary was added to /system/bin and set chmod 4755 in the system image?
usb debugging was turned on so the settings file in /data for adb is set to 1 instead of 0?
superuser.apk was added to /data/data or /system/app ?
also, why does this need to flash boot.img? it seems the boot.img in this .zip is slightly larger than the matching boot.img from the original stock RUU and the userdebug RUU PC36IMG.zip? has/what is modified in this boot.img?
from the update-script:
show_progress 0.1 0
format BOOT:
write_raw_image PACKAGE:boot.img BOOT:
show_progress 0.1 0
thanks flipzmode!!!

thanks for this

Sorry, what is the difference between this and the RUU(PC36IMG.zip) in Toast's tutorial thread?

splicitysplat said:
Sorry, what is the difference between this and the RUU(PC36IMG.zip) in Toast's tutorial thread?
Click to expand...
Click to collapse
the PC36IMG.zip is a full RUU. it contains radio, wipes /data, loads /system, loads bootloader and recovery, etc.
this Supersonic.zip is ONLY the STOCK /system with su (root), superuser and adb turned on.
if you want root in normal android mode, you'll want to install this.

so whats the easiest way to upgrade to this Rom? Can you simply use rOM Manager? or do you have to do it through command prompt while the phone is in recovery mode?\\\\
Never mind I think I answered my own question. - Thanks

joeykrim said:
the PC36IMG.zip is a full RUU. it contains radio, wipes /data, loads /system, loads bootloader and recovery, etc.
this Supersonic.zip is ONLY the STOCK /system with su (root), superuser and adb turned on.
if you want root in normal android mode, you'll want to install this.
Click to expand...
Click to collapse
Thank you. So, my check list should go:
-Get EVO
-Root using Toast's tutorial
-Flash Flipz ROM
Is this correct?

splicitysplat said:
Thank you. So, my check list should go:
-Get EVO
-Root using Toast's tutorial
-Flash Flipz ROM
Is this correct?
Click to expand...
Click to collapse
-Get EVO
-Root using Toast's tutorial
-Apply Custom Recovery using Toast's tutorial
-Flash Flipz ROM
yup, sounds good.

Does this rom disable OTA update from Sprint? What I'm thinking is, since Sprint has temporarily enable the WiFi hotspot to work without us paying the $29.99 fee, if we disable the OTA update, then maybe they can't modify the WiFI hotspot it in the future, that requires us to pay the fee?

apexi350z said:
Does this rom disable OTA update from Sprint? What I'm thinking is, since Sprint has temporarily enable the WiFi hotspot to work without us paying the $29.99 fee, if we disable the OTA update, then maybe they can't modify the WiFI hotspot it in the future, that requires us to pay the fee?
Click to expand...
Click to collapse
never heard of them temporarily enabling it. do you currently have a working wifi hotspot? did you have to take it into the store to enable it?

i believe that the tethering app from sprint is free to use for the first month. they wont start charging for it until july

So does this rom disable OTA update?
joeykrim said:
never heard of them temporarily enabling it. do you currently have a working wifi hotspot? did you have to take it into the store to enable it?
Click to expand...
Click to collapse
http://www.engadget.com/2010/05/28/evo-4g-on-sale-at-8am-on-june-4th-with-one-month-free-4g-mobile/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

from the sounds of that article, it is a sprint dedicated app installed on the phone. my guess is it will check thru the internet, whether or not you are allowed to wifi tether, and then either activate the application or forward you to an activation page in the browser.
i could be completely wrong but im guessing this will have absolutely nothing to do with OTA.
If this rom is completely stock as Flipz indicated in his first post, OTA will not be disabled.

OTA on Sprint
In my experience, OTA has not been the same on Sprint that it was on T-mobile. Each time an update came out, I had to use the Device Self Service app to get the update. I've been running a rooted ROM based on stock for the Hero and have never just had an OTA update start up.

I just flashed this after rooting because this supposedly fixed a market problem and now I'm stuck in an endless boot cycle on the Sprint 4g logo...any idea how to fix?
Edit: I'm currently restoring based on the backup I made. But people should beware that this can cause problems!

when sprint makes u pay for the hotspot it wont be a ota update. all that will happen is a change in the system on ur account on the back end just like if u loose ur phone and u have them restrict it

I wonder how sprint is going to determine who to charge. If it is active now it is going to take a OTA to turn it off. that is if they are tracking by the application. They could be just monitoring data amounts being transferred and going to charge if you are over a certain amount. Anyone from sprint on that knows for sure.

damnit. i had no problem with toasts root instructions.. despite this being my first android, but i'm having a helluva time finding instructions to install your custom rom.. bah humbug

[FIX]Pokemon/Android Pay root on/off zips! 10/14/2016 CM13 Tested!

I was trying a few other mods that took me to installing apps to toggle root but needed special SU and all that jazz...I was not very comfortable with installing another app just to toggle it.
So I tried a terminal command way and it worked well, but remembering the commands and typing it in all the time sucked so I found an updater script that will work just the same.
Only bug is reverting back might take two flashes because of the mounting another folder. I might try and solve it when I have time but works flashing it twice.
The code I used makes it easy to know if it's working....look at theses screenshots of the recovery log
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PokeFix.zip recovery messages:
renaming files bin = Root off
renaming files xbin = Root off
nothing to rename = already done
PokeFix-revert.zip recovery messages:
reverting files bin = Root on
reverting files xbin = Root on
nothing to revert = already done
Click to expand...
Click to collapse
How this works:
The script will look at the folders bin and xbin where the su files are located so simply remaning them suBU will kill root and apps that look for root...the other script renames it back to su from suBU so rooted again on boot! Simple and clean!
To confirm you can flash them and get the nothing to message just to make sure!
If you have root in other folders and this does not work let me know and I will try and make special zips.
Hope this helps you CATCH 'EM ALL and use android Pay of course.
DJDARKKNIGHT96
TeamBlackOut
Link to files:
Gimmie Pokemon and Android pay on CM
Gimmie Pokemon and Android pay on DU/SuperSU comming soon hopefully but this thread seems to work with systemless root http://forum.xda-developers.com/apps/supersu/suhide-t3450396/post68424603

@djdarkknight96 Nice job David!!! Awesome thinking
Sent from my Nexus 6P using XDA Labs

Seems this is the place I need to be for PoGo fix.
LG G2 d800. Custom LolPop ROM. Apparently I am no longer rooted, but the LP cust ROM must be causing the PoGo "not compatible". Have tried a few suggestions to no avail. Cant access TWRP anymore either. Any ideas?

davizzyus said:
Seems this is the place I need to be for PoGo fix.
LG G2 d800. Custom LolPop ROM. Apparently I am no longer rooted, but the LP cust ROM must be causing the PoGo "not compatible". Have tried a few suggestions to no avail. Cant access TWRP anymore either. Any ideas?
Click to expand...
Click to collapse
Oh man no TWRP access, you need recovery or you could root then use a terminal app and do these commands to find and hide the files they check for.
I got that from G+ so no credit to me for that, and it inspired my script.
Reboot after done

djdarkknight96 said:
Oh man no TWRP access, you need recovery or you could root then use a terminal app and do these commands to find and hide the files they check for.
I got that from G+ so no credit to me for that, and it inspired my script.
Reboot after done
Click to expand...
Click to collapse
Okay, used Kingroot, but It's acting kind of funny. I think it's rooted. At least it passed root checker app twice. Then tried to use Flashify to flash TWRP img. 2.8.6 which was on there as my recent recovery image. Tapped boot into recovery and the LG logo with the boot certificate error came up. I thought I was screwed, but hit power button, and it did a regular boot into Lolli.
I'm nervous about messing with it. Last thing I want is another brick. Is there a way to check for sure that TWRP is on there successfully?
And if it is, and if I am rooted, You're saying that entering all of that code into terminal command will work and allow Pogo? Sounds too good to be true. I'm sure I'll find another new and unusual way to brick that I haven't done yet...
---------- Post added at 07:05 PM ---------- Previous post was at 07:00 PM ----------
djdarkknight96 said:
Oh man no TWRP access, you need recovery or you could root then use a terminal app and do these commands to find and hide the files they check for.
I got that from G+ so no credit to me for that, and it inspired my script.
Reboot after done
Click to expand...
Click to collapse
Does this do the same as if I went into the file through ES File Explorer and delete the su out of xbin? That trick worked for me over the weekend after I flashed CM13 and MM. I think I read somewhere it only works on CM13.

davizzyus said:
Okay, used Kingroot, but It's acting kind of funny. I think it's rooted. At least it passed root checker app twice. Then tried to use Flashify to flash TWRP img. 2.8.6 which was on there as my recent recovery image. Tapped boot into recovery and the LG logo with the boot certificate error came up. I thought I was screwed, but hit power button, and it did a regular boot into Lolli.
I'm nervous about messing with it. Last thing I want is another brick. Is there a way to check for sure that TWRP is on there successfully?
And if it is, and if I am rooted, You're saying that entering all of that code into terminal command will work and allow Pogo? Sounds too good to be true. I'm sure I'll find another new and unusual way to brick that I haven't done yet...
---------- Post added at 07:05 PM ---------- Previous post was at 07:00 PM ----------
Does this do the same as if I went into the file through ES File Explorer and delete the su out of xbin? That trick worked for me over the weekend after I flashed CM13 and MM. I think I read somewhere it only works on CM13.
Click to expand...
Click to collapse
If you boot recovery then it's safe now. Yes that script worked on non systemless root but I got lazy and made zips to do the same thing in recovery. While Android is running I wouldn't delete Root files..Just a bad feeling. I go to recovery for all system files just for piece of mind lol

djdarkknight96 said:
If you boot recovery then it's safe now. Yes that script worked on non systemless root but I got lazy and made zips to do the same thing in recovery. While Android is running I wouldn't delete Root files..Just a bad feeling. I go to recovery for all system files just for piece of mind lol
Click to expand...
Click to collapse
Someone suggested renaming the files, instead of deleting them. Also, I don't want MM. I prefer LP. Do you know if I can flash CM 13 and run Lollipop on it?
I'm still really new to all this.

davizzyus said:
Someone suggested renaming the files, instead of deleting them. Also, I don't want MM. I prefer LP. Do you know if I can flash CM 13 and run Lollipop on it?
I'm still really new to all this.
Click to expand...
Click to collapse
My script does rename them inside the zip, I just got the idea from that pic on G+. CM13 is Marshmallow though lollipop would be CM12....I recommend whatever runs good on your device. I use CM13 but I'm a Nexus user.

Yeah, that's what I thought. I just wasn't a fan of MM when I used it for a day last weekend, plus PoGo would freeze for a second or two every time I caught one. Anyway, thanks for your feedback. Maybe someone will come up with a workaround, or maybe those Niantic F"ers Will come to their senses and stop their idiocy of blocking innocent root users.

Hi @djdarkknight96, could please help me on my HTC Desire 620? I successfully flashed the PokerFix.zip file, however after rebooting, Android Pay still identifying the device as rooted, unlocked bootloader or running a custom ROM...any ideas? Many thanks in advance.

ptreber said:
Hi @djdarkknight96, could please help me on my HTC Desire 620? I successfully flashed the PokerFix.zip file, however after rebooting, Android Pay still identifying the device as rooted, unlocked bootloader or running a custom ROM...any ideas? Many thanks in advance.
Click to expand...
Click to collapse
I'm using Magisk now, this mod only worked on Cyanogen mod 13 but Magisk is great and gives root and safety net passes.

How to install January 5th patch while using custom recovery and root on Google Pixel

Okay, I am sure a lot of you already know how to do this to your Pixel. Some of us do not, and I was one of them. I am the standard noob that just followed Youtube videos to unlock previous carrier locked phones. I am now enjoying this Google Pixel that is unlocked!
So if you are reading this thread, hopefully there isn't another one just like this (yes I looked).
To start off, if you are in here reading this, you have unlocked your bootloader and installed a custom recovery such as TWRP and rooted. Now you are seeing that you need to update your phone with the latest security patch. You try and you try and you can't do it. Even when you unroot it will still fail to update, or at least it did for me. Here I will explain what I went through and did to obtain the latest update. (Warning, you will loose root and custom recovery). THIS IS INTENDED FOR THE GOOGLE STORE PURCHASED PHONES
Lets get this started finally.....
Go into your developer options and enable usb debugging.
Download the newly released package file from google that has fastboot and ADB without needing android SDK.
DOWNLOAD or read about it HERE
Now you will need to download the Factory Image for you device
Find your correct device HERE
Make sure you choose the correct device and correct update, for me I downloaded the "7.1.1 (NMF26U, Jan 2017)" for my Pixel. Also a USA phone.
So now you have the adb fastboot binary package and your factory image. You will need to extract the platform-tools-latest-windows.zip and open the folder and you will see another folder, open it and now you will see a bunch of files. Now open another window and extract your factory image. Once it is done, open the folder until you see the files. Now copy these into the Platform tools folder in the directory with the fastboot.
Once this is done your folder should look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now you will want to right click "flash-all" and click edit. It will open notepad and show the contents of the batch file. You can hit Ctrl+F and type in -w in the search and hit okay, or you can look for it without search (it is near the bottom). Once you find it, just delete the "-w" and save the file. Make sure to keep it as the batch file or this won't work.
Once this is done, in the folder that is shown above, click a blank area in the folder so no file is highlighted. Now hold shift and right click, it will come up with a dialog saying open command window here, click that.
Now we are going to reboot the phone into bootloader mode. In the command window, type everything that is underlined below
adb reboot bootloader
Now your phone should have booted into the bootloader screen or it should be asking for USB rights to use adb. If it asks for permission, hit okay and re run the code above and your phone should reboot.
Once you are in the bootloader screen you will need to do is run the flash-all.bat. It will load and go though some text on the CMD window it brings up. It will say some files are missing, which is fine. But if it fails it will tell you that it did. You can also tell by rebooting the phone or click "start" in the bootloader mode and then checking for OTA updates. It should say January 5th patch installed.
Now you can go through and install your custom recovery again and re root. Which takes no time at all and I am sure someone on here has posted before. If not, let me know and I can make a tutorial over it.
Note: I am very sorry for the bad layout and extended write up. First time ever doing this and I am hoping to help people. If there are any errors, let me know!

All of this is already well known and documented. It is device molding 101
No one with 2 licks of common sense uses YouTube videos for something like this.

zelendel said:
All of this is already well known and documented. It is device molding 101
No one with 2 licks of common sense uses YouTube videos for something like this.
Click to expand...
Click to collapse
Haha well my apologies, I did state that I was a complete noob about all of this. I'm sure there are other noobs like myself

exbtlegends said:
Haha well my apologies, I did state that I was a complete noob about all of this. I'm sure there are other noobs like myself
Click to expand...
Click to collapse
I'm not a noob, but i'm a old fart, and we forget things, even simple things like this, I'm glad to have a simple reminder of how to do things. Thanks for the refresher.

jrat69 said:
I'm not a noob, but i'm a old fart, and we forget things, even simple things like this, I'm glad to have a simple reminder of how to do things. Thanks for the refresher.
Click to expand...
Click to collapse
Not a problem ?

I know you say this is for the GPS version, but has anyone tried it on Verizon? I'm not sure if the firmware is the same on both phones, so I don't want to soft-brick by downloading the Google version if they're different. Same boat as you were, OTA fails even after unrooting.

32BitWhore said:
I know you say this is for the GPS version, but has anyone tried it on Verizon? I'm not sure if the firmware is the same on both phones, so I don't want to soft-brick by downloading the Google version if they're different. Same boat as you were, OTA fails even after unrooting.
Click to expand...
Click to collapse
As long as you never re-lock your bootloader, the process is the same. There's no more separate Verizon images, just USA and international.

This is really complicated. ADB side load the OTA file, reinstall TWRP and root, done.

Good work. This is a very minute stuff of removing -w from the batch file. Very handy work.
Sent from my Pixel using Tapatalk

Do you need to reflash stock kernel before removing root/TWRP before flashing?

32BitWhore said:
Do you need to reflash stock kernel before removing root/TWRP before flashing?
Click to expand...
Click to collapse
Flashing the image overwrites anything you customized besides the regular user data and internal storage (with the -w removed). You don't have to remove or reflash anything else before following these instructions.

TCPDump said:
This is really complicated. ADB side load the OTA file, reinstall TWRP and root, done.
Click to expand...
Click to collapse
I couldn't side load the update.. TWRP would not load the side load feature.

I'm having an issue also: https://forum.xda-developers.com/pixel/help/sideload-ota-t3534926... Can we just unroot, take the OTA and then reroot?

km8j said:
I'm having an issue also: https://forum.xda-developers.com/pixel/help/sideload-ota-t3534926... Can we just unroot, take the OTA and then reroot?
Click to expand...
Click to collapse
Even when I un rooted mine. I was still failing to get the update.

If you made any changes the the system partition then it will fail and simply unrooting doesn't make the all the changes needed. So if OTA mean anything to you then I would suggest not messing with your device as there is Jo promise that after an OTA you will be able to root again tonight away

jesssiii said:
As long as you never re-lock your bootloader, the process is the same. There's no more separate Verizon images, just USA and international.
Click to expand...
Click to collapse
I know the past 2 were the same for google pixel and Verizon pixel but I wouldn't assume they are always going to be. I'm sure some of them will be specific at times whenever Verizon decides they wanna mess with them

FYI, I was able to sideload after updating TWRP to RC1, but now SuperSU 2.79 will install from within TWRP but when the phone restarts SuperSU is not installed... not sure if we have to wait until a new version of SuperSU is released.

SpoiledHeeb said:
FYI, I was able to sideload after updating TWRP to RC1, but now SuperSU 2.79 will install from within TWRP but when the phone restarts SuperSU is not installed... not sure if we have to wait until a new version of SuperSU is released.
Click to expand...
Click to collapse
You need SuperSU 2.79 RC3

Mount system as writable in TWRP?

As title says can I safely mount system writable in TWRP to modify build.prop? I would like to push pull the file from TWRP as any changes I make while in Android won't save.
I am mha-l29c567b190 with unlocked bootloader and rooted with phh method. My data is still encrypted at this point.
I'm not familiar enough if what I want to do is going to cause a bootloop or something. I know this will modify system so future OTA will break and I'll probably just decrypt data or figure out how to get back to stock.
I do have backups of everything right after TWRP install (except data since again I'm encrypted) so I may be able to restore that too but don't know if that would work on this phone or not. Thanks!

2nd question. Based on my phone setup, could I uninstall phh superuser from Android, boot to TWRP and restore boot and flash stock recovery to get back to stock? Rooting this phone doesn't seem to have the same advantages of any other phone I've owned so might want to revert back.

Good questions
1. Yes. You can mount /system as read/write if you installed phh superuser using manual. There are two options:
- only root
- root + dm-verity off
Dm-verity is kind of phone's security which is protecting important partition to be modified. Even if you have root and mounting system as read/write and doing something with system, your system partition will go stock state after reboot.
But turning dm-verity off removes this protection and you will able to modify system and other partitions.
2.
To get stock state back you need restore stock boot and recovery.
If you modified system, you have to revert all changes.
But sometimes it is too hard to remember all changes, so best way to get stock is:
- flash stock recovery
- flash stock ROM via Firmware Finder (FF)
It is easiest and quick method.

5[Strogino said:
;74089991]Good questions
1. Yes. You can mount /system as read/write if you installed phh superuser using manual. There are two options:
- only root
- root + dm-verity off
Dm-verity is kind of phone's security which is protecting important partition to be modified. Even if you have root and mounting system as read/write and doing something with system, your system partition will go stock state after reboot.
But turning dm-verity off removes this protection and you will able to modify system and other partitions.
2.
To get stock state back you need restore stock boot and recovery.
If you modified system, you have to revert all changes.
But sometimes it is too hard to remember all changes, so best way to get stock is:
- flash stock recovery
- flash stock ROM via Firmware Finder (FF)
It is easiest and quick method.
Click to expand...
Click to collapse
Thank you for the responses. How do I get dm-verify off?

Does anyone know the drivers needed to get ADB to work in TWRP? I have ADB working fine when in Android and fastboot works fine in bootloader. I would like to modify the build.prop and push it back to the phone. I can't seem to do it either inside of twrp file manager, as it sees /system/vendor as a file and not a path.

bhint15 said:
Thank you for the responses. How do I get dm-verify off?
Click to expand...
Click to collapse
Here is SuperRoot without dm-verity: https://forum.xda-developers.com/ma...oot-mate-9-decrypt-data-t3569986/post71346651
Decrypting data is optional. If you don't wanna it, don't format data (skip linked steps)

5[Strogino said:
;74102755]Here is SuperRoot without dm-verity: https://forum.xda-developers.com/ma...oot-mate-9-decrypt-data-t3569986/post71346651
Decrypting data is optional. If you don't wanna it, don't format data (skip linked steps)
Click to expand...
Click to collapse
That's the guide I used but still can't get build.prop edited. My data is encrypted but system won't write while in Android and while in TWRP adb won't work and I can't copy the file over the old one using TWRP file explorer. Guess I'm giving up with root on this phone seems pointless to have done it with O on its way I just hope I can get it back to stock without breaking it to get the OTA (if it ever hits since I'm C567 and this thing hasn't had a damn update since April)

bhint15 said:
That's the guide I used but still can't get build.prop edited. My data is encrypted but system won't write while in Android and while in TWRP adb won't work and I can't copy the file over the old one using TWRP file explorer. Guess I'm giving up with root on this phone seems pointless to have done it with O on its way I just hope I can get it back to stock without breaking it to get the OTA (if it ever hits since I'm C567 and this thing hasn't had a damn update since April)
Click to expand...
Click to collapse
I can't say what happens on new ROMs, cause this guide slightly old. If you installed phh SuperRoot and phh superuser app from play store, you are able to use root. Check it in terminal.
If yes, try to mount system as read/write.
If yes, use Root Explorer and change system files.
Try reboot after that and notice everything works or not.

5[Strogino said:
;74138910]I can't say what happens on new ROMs, cause this guide slightly old. If you installed phh SuperRoot and phh superuser app from play store, you are able to use root. Check it in terminal.
If yes, try to mount system as read/write.
If yes, use Root Explorer and change system files.
Try reboot after that and notice everything works or not.
Click to expand...
Click to collapse
I have root. It prompts and works. Root explorer (or any other app that modified system) will not write to system, it errors out.
Other weird stuff too though, like Xposed installs in TWRP but doesn't work (says not installed)
I really only wanted root to unlock hotspot so it's not that big of deal.

Here is the solution to your problem my friends. Enjoy!
Works like a charm in Android 10 and later.
https://forum.xda-developers.com/t/script-mount-system-as-read-write-android-10.4240703/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

J415GN/DS TWRP HELP

yo, can someone help or answer me. I can't seem to find any official/unofficial version of twrp for sm-j415gn/ds. Does anyone have any link?

lamawkalabaw said:
yo, can someone help or answer me. I can't seem to find any official/unofficial version of twrp for sm-j415gn/ds. Does anyone have any link?
Click to expand...
Click to collapse
https://forum.xda-developers.com/f/samsung-galaxy-j4-roms-kernels-recoveries-ot.8287/
There is one here.

ashyx said:
Unofficial release -TWRP recovery for the Galaxy J4 plus 2018 - SM-J415 MSM8917
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.3.1-0 Released
May 22, 2019
TWRP 3.3.1-0 is out now for most currently supported devices.
What's new in 3.3.1-0:
* Fix selinux issues during formatting - dianlujitao
* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
* Add option to uninstall TWRP app from /system - Dees_Troy
* Create digest for subpartitions - bigbiff
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
Update - 17/8/2019
TWRP 3.3.1-1 OO/PP build released
Current status - Beta
Treble supported
Bugs: brightness slider
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
*****INSTALL INSTRUCTIONS:*****
Flash with ODIN in the AP slot.
1. Put your device in DOWNLOAD mode.
(Plug in the USB cable and then hold POWER + VOL DOWN + VOL UP)
2. Load the respective file below into the AP slot, uncheck Auto-reboot(not required for twrp_3.3.1-1) and hit start.
twrp_3.2.3-1_sm-j415f_30319
twrp_3.3.1-1_j415x_17819
3. After flashing and ODIN reports PASS immediately force reboot to recovery. (Not required for twrp_3.3.1-1 as it should auto reboot to recovery). You should now see TWRP recovery.
Do NOT let the device boot to the OS.
4. Flash the V3 RMM bypass zip
https://forum.xda-developers.com/showpost.php?p=79745844&postcount=627
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT AND BECOMING RMM LOCKED FOR 7 DAYS.
I ALSO SUGGEST BACKING UP ANYTHING YOU NEED ON INTERNAL STORAGE. AT SOME POINT YOU MAY EXPERIENCE A 'VERIFICATION FAILED MESSAGE' .
THIS IS NORMAL, BUT WILL REQUIRE THE DATA PARTITION TO BE FORMATTED IN TWRP.
5. Reboot to TWRP (Do not boot to the OS yet)
***** ROOT INSTRUCTIONS:*****
OREO ONLY
1. Flash the Forced encryption disabler patch. This is only required if you wish to have full functionality in TWRP.
Flashing this will disable Samsung's forced encryption. Disabling encryption will allow TWRP to mount the data partition.
After flashing the patch it is necessary to *FORMAT* (not wipe) the /DATA partition using the FORMAT DATA button under the wipe options.
PLEASE NOTE THIS WILL DELETE EVERYTHING ON INTERNAL STORAGE AND FACTORY RESET THE DEVICE, SO BACK UP ANYTHING YOU WISH TO KEEP.
J4+J6+_oreo_forced_encryption_disabler
2. To root I suggest installing the latest Magisk beta as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
(NOTE: The DEFEX patched Oreo kernel below may be needed for full root support if certain apps do not work with root):
https://androidfilehost.com/?fid=1395089523397921797
3. Enjoy your rooted device.
PIE ONLY
1. Due to some new securities in Samsung's latest Pie kernels, root will not work with the stock kernel. The patched kernel below is required to gain root on Pie.
Features:
Dmverity, proca, five and defex disabled.
OTG and NTFS file system support.
Selinux permissive switchable.
This kernel may require the U4 bootloader.
(NOTE: flashing a custom kernel on PIe breaks the lockscreen. Ensure NO lockscreen is enabled before installing the kernel.)
J415FXXU4BSF7_patched_boot_318919
2. To root I suggest installing the latest Magisk beta as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/app...mless-t3473445
3. If you wish to have access to internal storage /DATA in TWRP then encryption will need to be disabled. See step 1 of the Oreo root instructions then instead of installing the J4+J6+_oreo_forced_encryption_disabler install the zip below with TWRP:
Disable_Dm-Verity_ForceEncrypt_Quota_08.02.2019
3. Reboot.
The device will take a good 10 mins to boot first time.
Enjoy your rooted device.
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my tester @kapmino269 [MENTION=6037748]Zackptg5 for the DM-VERITY & FORCEENCRYPT DISABLER @teamwin, @corsicanu for RMM V3 bypass zip.
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
Here.

Kenora_I said:
Here.
Click to expand...
Click to collapse
yo thanks, but is it compatible for my model? i really am confused because i don't know if j415gn/ds and j415gn are the same.

lamawkalabaw said:
yo thanks, but is it compatible for my model? i really am confused because i don't know if j415gn/ds and j415gn are the same.
Click to expand...
Click to collapse
Lol there isnt a j415gn
Just the j415gn/ds
Anyway they are the same phone nonetheless but ive given the one specific to your phone
The devs dont put /ds for convenience probably.

Kenora_I said:
Lol there isnt a j415gn
Just the j415gn/ds
Anyway they are the same phone nonetheless but ive given the one specific to your phone
The devs dont put /ds for convenience probabl
Click to expand...
Click to collapse
Kenora_I said:
Lol there isnt a j415gn
Just the j415gn/ds
Anyway they are the same phone nonetheless but ive given the one specific to your phone
The devs dont put /ds for convenience probably.
Click to expand...
Click to collapse
gee, i owe you a lot man. I just wanted to get the best out of this phone since I'm just a student and broke. I am very nervous that i might hardbrick this since it's my only phone. Anyways, thanks again dude.

lamawkalabaw said:
gee, i owe you a lot man. I just wanted to get the best out of this phone since I'm just a student and broke. I am very nervous that i might hardbrick this since it's my only phone. Anyways, thanks again dude.
Click to expand...
Click to collapse
LOL IM NOT A DUDE
But yeah no issue lol
i kinda do this for fun anyway
i just like helping around
Yeah i hate dem hard bricks. Ive had phones become paperweights, but i seem to unbrick them in the end

Kenora_I said:
LOL IM NOT A DUDE
But yeah no issue lol
i kinda do this for fun anyway
i just like helping around
Yeah i hate dem hard bricks. Ive had phones become paperweights, but i seem to unbrick them in the end
Click to expand...
Click to collapse
lmao I'm sorry and thank you
i might ask for your help again if i had any problems.

lamawkalabaw said:
lmao I'm sorry and thank you
i might ask for your help again if i had any problems.
Click to expand...
Click to collapse
Sure! Ill be here.