Database Develop

Nexus 6 shows 4,000% battery life after root?

I got my Nexus 6P for Christmas, and I decided to root my Motorola Nexus 6 from last year. I've been waiting to do this for a few months, and was excited to finally enable several of the options I couldn't otherwise enable (such as double tap to wake and auto rotate on the lock screen and Google Now launcher). About an hour ago I got around to rooting and done so with little issues. It's been a little under an hour since I rooted, and I just now noticed that the battery life is being displayed as having over 4,000% charge. I rooted following the steps in a YouTube video by DroidModderX and the device is running perfectly fine. The device hasn't died yet, and I'll be interested to see when it will die. The battery life seems to fluctuate between 4,001% and 4,204% (Those two figures being the highest and lowest figures respectively). Rebooting does not fix this error.
I know it's not a massive problem, but I'd like to know what's causing this issue and how to resolve it. I haven't flashed any custom OS's on my phone, I'm still running stock Android 6.0.1 Marshmallow with the latest December security patches. The device is carrier unlocked also. How can I fix this?
Thanks,
Eamonn.

sonic2kk said:
It's been a little under an hour since I rooted, and I just now noticed that the battery life is being displayed as having over 4,000% charge. being the highest and lowest figures respectively). Rebooting does not fix this error.
Click to expand...
Click to collapse
You need to use updated root files. The battery issue arises when you're on 6.0.1 but aren't using the right file version. Easily fixed not to worry, just re-root with updated files and it will resolve with no lasting harm.

sansnil said:
You need to use updated root files. The battery issue arises when you're on 6.0.1 but aren't using the right file version. Easily fixed not to worry, just re-root with updated files and it will resolve with no lasting harm.
Click to expand...
Click to collapse
Ah, thank goodness. I'll re-root tomorrow and post back if I have any problems. Thanks!

Thanks, that fixed the issue. I re-rooted and everything is working fine. I flashed the ElementalX kernel. However on boot I now get a warning with a red triangle saying "Your device is corrupt. It cannot be trusted and may not work properly". This warning goes away, and the phone proceeds to boot up successfully. Everything on the device works perfectly fine with no issues. I am successfully rooted running Android Marshmallow 6.0.1, but this screen scares me somewhat. I rooted my Galaxy SII and I have a yellow triangle on boot but only on the Samsung splash screen. Is this something new in Android M or something unique to Nexus devices? I researched this a bit and found one post on Reddit that said this happened in the M previews, and that it was nothing to be concerned about. Is there a way to remove this screen, or is it just like the yellow triangle on the SII? Should I even be concerned with this, or is it something to just dismiss? Is my device at risk any more than normal when rooting, and have I done something wrong? I'm a bit of a newbie at the rooting stuff, but I intend to use my Nexus 6 and SII to learn more about it (and my 6P way into the future, once I get a new phone).
Thanks in advance.

Why did you need root for the Google now launcher?

mikeprius said:
Why did you need root for the Google now launcher?
Click to expand...
Click to collapse
What do you mean? I can run the Google Now launcher perfectly fine. Root works fine as well. The problem isn't with the Google Now launcher but with the warning on boot. I didn't need to root, I chose to. Am I misunderstanding?

Your original post made it seem like you need root for double tap to wake and Google now launcher.

sonic2kk said:
Thanks, that fixed the issue. I re-rooted and everything is working fine. I flashed the ElementalX kernel. However on boot I now get a warning with a red triangle saying "Your device is corrupt. It cannot be trusted and may not work properly". This warning goes away, and the phone proceeds to boot up successfully. Everything on the device works perfectly fine with no issues. I am successfully rooted running Android Marshmallow 6.0.1, but this screen scares me somewhat. I rooted my Galaxy SII and I have a yellow triangle on boot but only on the Samsung splash screen. Is this something new in Android M or something unique to Nexus devices? I researched this a bit and found one post on Reddit that said this happened in the M previews, and that it was nothing to be concerned about. Is there a way to remove this screen, or is it just like the yellow triangle on the SII? Should I even be concerned with this, or is it something to just dismiss? Is my device at risk any more than normal when rooting, and have I done something wrong? I'm a bit of a newbie at the rooting stuff, but I intend to use my Nexus 6 and SII to learn more about it (and my 6P way into the future, once I get a new phone).
Thanks in advance.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24269982087021512 gives you 6.0.1 bootstack for Nexus 6 (shamu). Flash this in TWRP. This should fix your corrupted boot splash screen. It's new in Android M when you've installed custom kernel and/or roms. It does not hurt anything except Android Pay is unlikely to work once rooted.
EDIT: I forgot to included mmb29k, non-encrypt boot.img made by GerardF: https://www.androidfilehost.com/?fid=24340319927534323 (flash this also after you flash the bootstack).

HueyT said:
(removed url) gives you 6.0.1 bootstack for Nexus 6 (shamu). Flash this in TWRP. This should fix your corrupted boot splash screen. It's new in Android M when you've installed custom kernel and/or roms. It does not hurt anything except Android Pay is unlikely to work once rooted.
EDIT: I forgot to included mmb29k, non-encrypt boot.img made by GerardF: (removed url) (flash this also after you flash the bootstack).
Click to expand...
Click to collapse
Worked perfect. That got rid of the corrupt message. One last question: (This is the last one, I swear! ) Are you saying that Android Pay won't work at all after rooting or that it wouldn't have worked if that screen had have appeared on boot? I hope to use the service if and when it comes to the UK.
mikeprius said:
Your original post made it seem like you need root for double tap to wake and Google now launcher.
Click to expand...
Click to collapse
Ah, sorry for the confusion my friend ?

I would have kept it at 4,000% - that's like 2 weeks of battery life with no charge...

orangekid said:
I would have kept it at 4,000% - that's like 2 weeks of battery life with no charge...
Click to expand...
Click to collapse
Haha if it wasn't a display error I might have (Though it would have only been like 3 days on the Nexus 6 )

Stupid question but where do I get updated files. I followed the method on root junky for the Nexus 6

Dalek Caan said:
Stupid question but where do I get updated files. I followed the method on root junky for the Nexus 6
Click to expand...
Click to collapse
Sorry, I don't remember where I got the updated files now. I do remember sticking to looking on XDA and not just searching randomly online, maybe you could try searching the forums?

is it possible to root with chainfire root files. I did a clean install of the January security update, then flashed the latest boot.img from chainfire then flashed SuperSU 2.66.zip through TWRP, but im still getting this. I received this same issue with the last patch. Im at the point where it isnt worth rooting. Any help would be appreciated.

[GUIDE] How to root Salaxy Tab S2 T817T

How to Root Samsung Tab S2 T817T (Step-By-Step Guide)
Obligatory notices
This procedure is only for the Samsung Tab S2 SM-T817T
Performing any of the operations in this post risks bricking your device
Performing any of the operations in this post will irreversibly void your warranty
Performing any of the operations in this post will irreversibly trip Knox and make it unusable for Samsung Pay (and any other features which require Knox)
I am not using a SIM card with my device, so I have no idea how this procedure will impact that functionality. People on the XDA thread (forum.xda-developers.com/tab-s2/help/sm-t817t-root-t3206079) where I pieced together these instructions from suggested that the SIM card still works for mobile data. UPDATE: Later in this thread people have confirmed that mobile data DOES work after rooting. Yay!
Introduction
OK, so a brief story of how/why I was forced to figure this method out. I found a listing on eBay for the Samsung Tab S2 T810N, paid $300 for it and received it into my impatient hands. Without checking the specific version of the tab I push right into the rooting procedure I had thoroughly researched for the T810N. Suddenly my tablet is in a bootloop and I am panicking that it is ruined. In the recovery mode I see that I have the T817T. Anger towards the seller aside, I frantically research how to recover the T817T. There is virtually no documentation for this procedure, so I am forced to mix-and-match. After about 5 hours, the tablet is finally up, running, and rooted!
TL;DR - verify your model number before attempting root
Files
All the files can be found here (drive.google.com/folderview?id=0BxPb6XhrMsaoa01zdjVUVWMzQWs&usp=sharing). Let me explain what each file is:
T817TUVS2AOL1_T817TTMB2AOL1_TMB.zip (drive.google.com/file/d/0BxPb6XhrMsaoeGpmbnRoeFA5MUU/view?usp=sharing) - This is an Android 5.1.1 image for Samsung Tab S2 T817T. You may not even need this, but just in case. If you use this, unzip the file to get the .md5 file!
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.51.0.exe (drive.google.com/file/d/0BxPb6XhrMsaoc09qNm41OFhKLWc/view?usp=sharing) - Necessary Windows drivers for Samsung devices. Install this!
Odin3_v3.10.6.zip (drive.google.com/file/d/0BxPb6XhrMsaoLWtkek9UYWZGNGM/view?usp=sharing) - A flashing tool for Windows. Unzip these files!
twrp_2.8.7.1_LL_5.1.1_t810.tar (drive.google.com/file/d/0BxPb6XhrMsaoN0N6V3JzX290aGc/view?usp=sharing) - This is a custom recovery tool for Android. Although designed for the T810 series, it does work on the T817T. Do not untar these files!
Tab_S2_t817T_boot.zip (drive.google.com/file/d/0BxPb6XhrMsaob0hyME0zV2EtSnc/view?usp=sharing) - A custom bootloader for the T817T which is required to root. Do not unzip these files!
BETA-SuperSU-v2.52.zip (drive.google.com/file/d/0BxPb6XhrMsaoNk9uWkxRZ0wwTE0/view?usp=sharing) - A newer version of SuperSu which works on the T817T. Do not unzip these files!
Preparation
Download all the files above. Install, unzip, and untar (or not) as instructed.
Settings -> About device - Verify that you have the SM-T817T
Settings -> About device - Verify that you are running Android 5.1.1
Backup all your files, contacts, apps, etc.
Verify that your device has at least 80% charge
Rooting Procedure
(OPTIONAL) Flash Android 5.1.1 image. This step is not necessarily required. If you are running Android 5.1.1, then you should be fine. However, this is what I had to do, since I got into a bootloop by not checking my version number first (yes, stupid me). Further, if you have any errors or issues below you absolutely will need to perform this step to recover and restart the rooting procedure. Anyway:
Turn off your tablet
Boot into 'download mode' by holding POWER + VOLUME DOWN + HOME. Verify by pressing VOLUME UP
Run program Odin3 v3.10.7.exe
Plug your device to the computer with a USB cable
Verify that Odin message window states "<ID:#/###> Added!!"
Click the "AP" button in Odin and select T817TUVS2AOL1_T817TTMB2AOL1_T817TUVS2AOL1_HOME.tar.md5 file
Press "Start" button and wait for Green "PASS" message to appear. This will take a long time since this is a large file
Your device will automatically reboot
Perform basic setup procedures on Android so that you can access the Settings menu
From this point onward your must perform every step in the exact order as stated. Not doing so seriously risks putting your device into a bootloop or bricking it. You should be able to recover from that, but still...
Enable developer options:
Settings -> About device - click on "Build number" like 10 times until "Developer options" are enabled and button is added to Settings menu
Settings -> Developer options - enable:
Developer options - ON
OEM unlock - ON
USB debugging - ON
Flash TWRP recovery software:
Turn off your tablet
Boot into 'download mode' by holding POWER + VOLUME DOWN + HOME. Verify by pressing VOLUME UP
Run program Odin3 v3.10.7.exe
Plug your device to the computer with a USB cable
Verify that Odin message window states "<ID:#/###> Added!!"
Click the "AP" button in Odin and select twrp_2.8.7.1_LL_5.1.1_t810.tar (drive.google.com/file/d/0BxPb6XhrMsaoN0N6V3JzX290aGc/view?usp=sharing) file
Press "Start" button and wait for Green "PASS" message to appear
Your device will automatically reboot, verify that the tablet boots properly
Copy bootloader and SuperSu to tablet:
With your tablet on, attach it to your computer with a USB cable
Navigate to the root directory of the tablet storage
Copy Tab_S2_t817T_boot.zip (drive.google.com/file/d/0BxPb6XhrMsaob0hyME0zV2EtSnc/view?usp=sharing) and BETA-SuperSU-v2.52.zip (drive.google.com/file/d/0BxPb6XhrMsaoNk9uWkxRZ0wwTE0/view?usp=sharing) files to the root directory
Detach tablet from your computer
Flash custom bootloader with TWRP:
Turn off your tablet
Boot into 'recovery mode' by holding POWER + VOLUME UP + HOME
Select "Install"
Select Tab_S2_t817T_boot.zip and click "Install"
Verify install with slider
STOP HERE!!! READ THE NEXT STEPS CAREFULLY!!!
TWRP will now offer to install SuperSu for you. DON'T DO IT!! Doing this will cause your tablet to bootloop because it is not the right version of SuperSu
Decline the SuperSu installation and restart your tablet
Verify that the tablet boots properly
REPEAT "Flash TWRP recovery software:" instructions. This is a necessary step. Without it your tablet will go into a bootloop and you will need to start the root procedure over. Weird, I know. Just do it.
Flash SuperSu with TWRP:
Turn off your tablet
Boot into 'recovery mode' by holding POWER + VOLUME UP + HOME
Select "Install"
Select BETA-SuperSU-v2.52.zip and click "Install"
Verify install with slider
Reboot the tablet
DONE! Assuming your tablet boots properly your should now be rooted and see the SuperSu app installed on your tablet.
Recovery
If you need to recover from some error you will need to start over completely. Use the Android 5.1.1 image file T817TUVS2AOL1_T817TTMB2AOL1_TMB.zip (same as above) to perform this. You can also use this Android image to restore the device to an unrooted version. This will not restore your warranty or Knox.
Extras
To get rid of the pesky KNOX security notification which will persist, use a program like ROM Toolbox Lite (play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox&hl=en). In the App Manager select the following apps and 'freeze' them:
SecurityLogAgent 4.1.4 (this one is critical to freeze!)
KNOX 2.3.0
KNOX 2.3.1
KNOX II 2.3.0
KNOX SetupWizardClient 2.3.0
KnoxFolderContainer 2.4.0
To get rid of the "No SIM card inserted" notification (if you aren't using a SIM card) use the build.Prop Editor in ROM Toolbox Lite. Add the following entry:
Property Name: ro.config.donot_nosim
Property Value: 1
Conclusions
I put this guide together for people who are having trouble finding a simple and easy-to-follow guide for rooting the T817T. Hopefully this can save you a number of frustrating and worrisome hours (not that rooting your Android device is ever a calm undertaking).
Please let me know if there are any errors in the procedure or if you have any suggestions regarding the steps or presentation of the material. Enjoy being a super-user!
Original content: blog.mchristian.co/blogs/post/How-to-Root-Samsung-Tab-S2-T817T/

phduhblog said:
Long time user, first time poster.
First off, let me say, THANK YOU XDA! You guys have been a crazy valuable resource over the years.
However, with regard to the T817T, the documentation is lacking severely. I have created a comprehensive step by step guide to rooting the T817T. Unfortunately, as a first time poster, I cannot post links or anything like that so...if somebody could fix that I would appreciate it. I spent a long time formatting the posting and adding file download links with the XDA formatter so that it wouldn't look like I was link whoring to my blog, just to be told to **** off... . Seeing as that's not possible, here is the url to my blog with the rooting instructions:
blog.mchristian.co/blogs/post/How-to-Root-Samsung-Tab-S2-T817T
Click to expand...
Click to collapse
http://blog.mchristian.co/blogs/post/How-to-Root-Samsung-Tab-S2-T817T
Thanks my friend
Edit: Completely professional and well done how to.. written just the way I like it, fantastic!! I think you should just edit your first post and paste all this in here on XDA... and ill be happy to carry your url link for you.

Complete text of the GUIDE
Edited and posted it above. Good luck with the rooting. Thanks!

An excellent guide. I'd spent the last few hours reading post after post gathering the correct information for the T817T specifically. I had come to the same basic conclusion as your guide states but its great to have some confirmation! I have a few differences in my install process than you did though. I did things in this order:
Enable developer options:
Copy bootloader and SuperSu to tablet:
THEN
Flash TWRP recovery software:
and between 6 and 7
Uncheck AutoReboot in the Options tab
7. Press "Start" button and wait for Green "PASS" message to appear
8. Use Power+VolumeDown+Home to reboot from bootloader and AS SOON as the screen goes black slide your finger from VolumeDown to VolumeUp
This should boot you into TWRP
Flash custom bootloader with TWRP:
after 4:
press "add another zip" and select the SuperSU zip as well.
5. Verify install with slider
6. Reboot
Done
By booting directly into TWRP the stock recovery doesn't have a chance to overwrite it. It won't need to be flashed a second time. You can also flash the kernel (...boot.zip) and SuperSU zip in the same pass. Saves a couple steps.
Either way I can confirm this works and all of the files are correct!
Thanks again for organizing all of this and making this great guide!

patrioticparadox said:
An excellent guide. I'd spent the last few hours reading post after post gathering the correct information for the T817T specifically. I had come to the same basic conclusion as your guide states but its great to have some confirmation! I have a few differences in my install process than you did though. I did things in this order:
Enable developer options:
Copy bootloader and SuperSu to tablet:
THEN
Flash TWRP recovery software:
and between 6 and 7
Uncheck AutoReboot in the Options tab
7. Press "Start" button and wait for Green "PASS" message to appear
8. Use Power+VolumeDown+Home to reboot from bootloader and AS SOON as the screen goes black slide your finger from VolumeDown to VolumeUp
This should boot you into TWRP
Flash custom bootloader with TWRP:
after 4:
press "add another zip" and select the SuperSU zip as well.
5. Verify install with slider
6. Reboot
Done
By booting directly into TWRP the stock recovery doesn't have a chance to overwrite it. It won't need to be flashed a second time. You can also flash the kernel (...boot.zip) and SuperSU zip in the same pass. Saves a couple steps.
Either way I can confirm this works and all of the files are correct!
Thanks again for organizing all of this and making this great guide!
Click to expand...
Click to collapse
I'm glad you have figured out another way! This is turning into what a proper thread on rooting should look like
I had actually tried the non-auto-reboot from Odin method too, but couldn't time the change to VOLUME UP correctly. After a couple times I just gave up and tried things the long way around. Never thought to flash the zip files in the same TWRP session though. I generally like doing things the long way around and getting confirmation that things still work after each and every step. Whatever works though!
Thanks for the reply

phduhblog said:
I'm glad you have figured out another way! This is turning into what a proper thread on rooting should look like
Click to expand...
Click to collapse
Indeed it is.
Are your volume buttons functioning properly after this? Just noticed yesterday mine aren't adjusting the volume.

patrioticparadox said:
Indeed it is.
Are your volume buttons functioning properly after this? Just noticed yesterday mine aren't adjusting the volume.
Click to expand...
Click to collapse
Hmmm, odd. Sorry to hear that. Yes, mine work just fine.

Turns out my volume buttons are fuctioning just fine. I think I just pressed it wrong and didn't have a minute to double check it at the time.

patrioticparadox said:
Turns out my volume buttons are fuctioning just fine. I think I just pressed it wrong and didn't have a minute to double check it at the time.
Click to expand...
Click to collapse
Whew! I'm glad to hear that. Now people can root their T817T without concern!

Yep! Been using this for two weeks now and no problems!

Can anyone confirm that the mobile internet still work when you have a SIM card in? Thanks.

phduhblog said:
Can anyone confirm that the mobile internet still work when you have a SIM card in? Thanks.
Click to expand...
Click to collapse
SIM does not work-- just restored back to stock.. going to wait a little bit before re-rooting.

androidcues said:
SIM does not work-- just restored back to stock.. going to wait a little bit before re-rooting.
Click to expand...
Click to collapse
Hmmm. Well that's good to know at least. Thanks for the update!
Also I'm glad you were able to revert to stock and get it working.

Yeah... Ive fully unrooted and gone back to samsung for a bit.. wont be long because I automatically gravitate back to CM. hehe.
vibration doesnt work on CM... that was a big thing because i rely on tactile vibration for notifications.... (i am deaf so.. the noisy parts are useless ?)
but anyway... taking a moment to thank you again for your writeup...i really needed that...soon after i read your blog i was rooted and rocking!
But Samsung sucks bro... i cant stand all these ****ty apps on my tablet so maybe I'll come back sooner.
0x1
Sent from my Nexus 5X using XDA Premium HD app

androidcues said:
Yeah... Ive fully unrooted and gone back to samsung for a bit.. wont be long because I automatically gravitate back to CM. hehe.
vibration doesnt work on CM... that was a big thing because i rely on tactile vibration for notifications.... (i am deaf so.. the noisy parts are useless )
but anyway... taking a moment to thank you again for your writeup...i really needed that...soon after i read your blog i was rooted and rocking!
But Samsung sucks bro... i cant stand all these ****ty apps on my tablet so maybe I'll come back sooner.
0x1
Sent from my Nexus 5X using XDA Premium HD app
Click to expand...
Click to collapse
Yep, I can definitely see why vibration notifications would be important for you!
As much as I dislike bloatware, from any company, Samsung just makes the most powerful tablets/phones. My best solution is to root and disable all the bloatware.
I'm glad the guide was well received and it seems to work for people.

My mobile data and SIM functions all work fine. Not sure why yours didn't

patrioticparadox said:
My mobile data and SIM functions all work fine. Not sure why yours didn't
Click to expand...
Click to collapse
Awesome! That is weird it didn't work for the other guy. Did you flash the provided Android version first or just go straight into the rooting? Thanks for the update!

phduhblog said:
Awesome! That is weird it didn't work for the other guy. Did you flash the provided Android version first or just go straight into the rooting? Thanks for the update!
Click to expand...
Click to collapse
Sorry for the late reply. I Odined the latest firmware to reset everything to a stock base before then flashing as your steps suggest (with the noted exceptions from my first post). My mobile data has worked flawlessly and I have had zero SIM related issues. In fact, I have had no issues what-so-ever. (I did think I had an issue with my volume rocker not working but that was user error. I have my tablet in a case of sorts and was not pressing hard enough). @phduhblog and @androidcues are you both still experiencing mobile data and SIM issues as of now?

patrioticparadox said:
Sorry for the late reply. I Odined the latest firmware to reset everything to a stock base before then flashing as your steps suggest (with the noted exceptions from my first post). My mobile data has worked flawlessly and I have had zero SIM related issues. In fact, I have had no issues what-so-ever. (I did think I had an issue with my volume rocker not working but that was user error. I have my tablet in a case of sorts and was not pressing hard enough). @phduhblog and @androidcues are you both still experiencing mobile data and SIM issues as of now?
Click to expand...
Click to collapse
Wording changed! Thanks for the update.

One question pls. I have the T817V tab 9.7 w/OEM bootloader option button. Is any of this available to use for my tab? TWRP recovery maybe? Any files? Any reply is appreciated. Novice seeking knowledge. Thank you so much.

Xposed Issue

- FIXED -
I keep trying to install an alternate version of xposed by wanam on my phone. i've flashed it multiple times today and always the same thing, I never progress from the "samsung galaxy note 4" screen after I reboot. Or sometimes, I do end up on the tmobile screen, but still my phone doesn't go anywhere from there.
I'm on MM.
any help?
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960 flashed this version of xposed
I think I read somewhere that my selinux had to be set to permissive, but I'm not sure how to do that. I've checked multiple threads and tried a lot of things but I just cant seem to get it to work.

I'm having this same issue.

joelle_sin said:
I keep trying to install an alternate version of xposed by wanam on my phone. i've flashed it multiple times today and always the same thing, I never progress from the "samsung galaxy note 4" screen after I reboot. Or sometimes, I do end up on the tmobile screen, but still my phone doesn't go anywhere from there.
I'm on MM.
any help?
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960 flashed this version of xposed
I think I read somewhere that my selinux had to be set to permissive, but I'm not sure how to do that. I've checked multiple threads and tried a lot of things but I just cant seem to get it to work.
Click to expand...
Click to collapse
Sorry things aren't working so good for you. I personally am running a clean odined MM FW with the 1st exposed listed on the thread you linked. SE Enforcing. Verifying checksums are a must. Also full wipes are pretty much mandatory prior to flashing FW upgrades
I am rooted and running TWRP 3.0.2. Everything is working superb. I came from a custom LL rom. Maybe if you could give some details about your flashes to MM prior to exposed it would be easier to help out.

ganns1980 said:
I'm having this same issue.
Click to expand...
Click to collapse
someone on another thread helped me. if you have note 4 with marshmallow, and the normal arm build doesn't work for you, download the alternative that's in the downloads. it worked for me.

[ROM] [Stock] J320A/J320AZ/J320AG deodex'd

Today i bring you the very first rom for our device.
It's only stock, but the installer includes enough options to keep us happy for a while.
The core installation includes a stripped down system menu with Google play and contacts. I also added, by default, the WiFi fix and hotspot mod. The rest of what you install is your choice.
Aroma options:
Choose which J320 you own
Debloat (fully customizable)
Deknox
Install root
Install busybox
Install Init.d
Install Xposed
Bugs:
None
If you find any let me know, but if you do not wipe, please don't even report bugs.
Link:
Download
Installation:
Flashfire
Enjoy
-D

This uses the same base files for each room, AQG1. So even tho the highest firmware for J320AG is only AQB1 you still get the July security update (minus the new sboot)
All devices are interchangable for me, on Cricket. Depending on your carrier maybe they'll all work for you too.

I have AT&T Samsung Galaxy Express Prime GoPhone, J320A. Owned it for one week. It has been carrier-unlocked. I'm now using T-Mobile SIM. Seems to work OK. Only issue I can find is where the SIM status page does not show my phone number.
I would appreciate pointers or maybe a place to look for installation steps. I assume I'll to need to root via Kingroot then replace with SuperSU (if possible). Then install FlashFire.​ I have rooted and installed ROMs on other devices (Galaxy Exhibit, 2012 Nexus tablet, Moto G), but seemingly devices are more locked-down these days. I understand that TWRP is not available for this device and likely will not be.
Last year, I bought a couple of inexpensive T-Mobile phones and "rooted" them with KingRoot which is still installed on those phones. (Not really thrilled about that.) I put rooted in quotes because it doesn't quite behave like a fully-rooted phone, IMO. I'm not very expert in these things, but I know how to follow steps and have used ODIN, TWRP, et cetera.
I'm leery of working with these more locked-down phones. Am I being paranoid and/or incorrect about these matters?
BTW, thanks for the ROM! I'm surprised there aren't more replies.
Maybe this phone is not as popular as I think it should be. Maybe it's too low-spec for the tech-savvy crowd. I got mine for just $64 at Walmart online, but they've since raised the price to $79. Seems like a good deal, even at that price.
I paid $15 to carrier-unlock it. I had to flash firmware (modem file?) before unlocking, then flash another file (restored modem?) after unlocking. I was following emailed instructions after the initial unlock procedure failed.

Here's the root thread
https://forum.xda-developers.com/galaxy-j3-2016/how-to/root-samsung-sm-j320a-galaxy-express-t3573628
There's a xposed module that does just that, never tried it tho, and of course it's not permanent.
https://forum.xda-developers.com/ga...pp-sim-changer-change-registered-sim-t2106490
I definitely like the phone and yeah, it's a good price.
Being locked does hurt it tho. No easy recovery and no roms from source. The only thing we might get will be ported. And with no kernel, porting is a pain to track down problems... but i like a challenge

My J3 was unlocked out of the box? Still don't quite get the different names for it though. Rooted with infixremix method and worked fi e until its download caused the dialer to crash whenever it was opened. Still trying to sort out the mess I made of this one.

original stock
hey do any of you guys know where I can get the original firmware to restore this device? mine is the S/W: j320aueu1ape9
on the box it says j320x UD

Odin files are posted here
https://forum.xda-developers.com/galaxy-j3-2016/how-to/root-samsung-sm-j320a-galaxy-express-t3573628

How is this ROM working out?
Can anyone -- or DamienMc, the creator -- post a review of how this ROM is working out? Brief or long; any type of review would be appreciated.
I'm thinking of trying this ROM and I haven't rooted my phone yet.
Although I did unlock the carrier via a paid unlocker site. I'm using it on T-Mobile with no apparent issues. My phone is stock, of course, except for being carrier-unlocked. …Several questions, if I might:
Are those "extra" AT&T and Samsung accounts present? (ref. screenshot)
Are Samsung factory (i.e.: theme-able) dialer, messaging, and contacts apps installed?
Is it still possible to theme the UI with the Samsung theme installer?
Finally, which bloat icons have been purged? (ref. screenshot) I realize one's idea of bloat may vary from individual.
Any feedback or commentary is welcome. Thank you for your consideration.

could it work on J320H?
i know it's for 320A/Az but i want to try it

danny8 said:
Can anyone -- or DamienMc, the creator -- post a review of how this ROM is working out? Brief or long; any type of review would be appreciated.
Any feedback or commentary is welcome. Thank you for your consideration.
Click to expand...
Click to collapse
I'm not going to review it (someone else can)
But I used it heavily before I started work on something new.
It's as stable as stock... cause it is stock Nothing tweaked just the few add-ons to let you tweak it easier.
About the bloat.
I did notice I should have left Samsung account (and maybe billing) with the standard install. Because you can't use the theme store without them. But they're in 'bloat'.
You can always install all the debloat options and have 100% deodex stock and edit to your liking.
hamzaeid said:
could it work on J320H?
i know it's for 320A/Az but i want to try it
Click to expand...
Click to collapse
Sorry bud, different chipset

How do we flash this to our device mainly because twrp and cwm ain't a thing for the j320a. Also I'm using kingroot and I cannot go to su I've tried also flashify does not work either does flashfire how would you go about rooting with su cause I've tried the mrw method and contanstaly it would pop up kinguser has stopped working so do you have another method of rooting the J320A. I just followed the first post about rooting it.

iiFir3z said:
How do we flash this to our device mainly because twrp and cwm ain't a thing for the j320a. Also I'm using kingroot and I cannot go to su I've tried also flashify does not work either does flashfire how would you go about rooting with su cause I've tried the mrw method and contanstaly it would pop up kinguser has stopped working so do you have another method of rooting the J320A. I just followed the first post about rooting it.
Click to expand...
Click to collapse
I just rooted my phone with Kingroot and used the mrw method to remove it well keeping my root. after got Su in my terminal emulator, I deleted the kingroot apk not the app itself. then just installed SuperSu thru my play store and been working just fine for me.

gus8347 said:
I just rooted my phone with Kingroot and used the mrw method to remove it well keeping my root. after got Su in my terminal emulator, I deleted the kingroot apk not the app itself. then just installed SuperSu thru my play store and been working just fine for me.
Click to expand...
Click to collapse
I've tried that it would just constantly spam me with kinguser has stopped working and that message would constantly spam me so I'm not ever using that way again.

iiFir3z said:
I've tried that it would just constantly spam me with kinguser has stopped working and that message would constantly spam me so I'm not ever using that way again.
Click to expand...
Click to collapse
Yeah i guess i never had kinguser app or apk i had to delete. Was just kingroot apk that i downloaded and used.

iiFir3z said:
I've tried that it would just constantly spam me with kinguser has stopped working and that message would constantly spam me so I'm not ever using that way again.
Click to expand...
Click to collapse
After mrc and kinguser crashes you should have supersu. You need to run that first, let it update the files and then reboot.
If su doesn't even get installed, have the apk ready and install.
Another thing you should make sure your really rooted, reboot after king and recheck.
Also what versions of kingroot and mrw are you using?

iiFir3z said:
I'm using Kingroot and I cannot go to SU. I've tried also Flashify does not work. Either does Flashfire. How would you go about rooting with SU…
Click to expand...
Click to collapse
I followed the rooting thread OP directions carefully and had many problems. My initial Kingroot was really ugly and heated the phone. I then attempted to use SuperSU-Me Pro (paid version). It was never able to complete, even after several tries. I struggled using various techniques over many hours. (I did have root with Kingroot.) Nothing would remove Kingroot 5.0.5, and as you probably know, Kingroot won't allow for many apps such as Flashfire. Very frustrating. I probably shortened the life of my phone and battery with all the crap I tried. Many pulls of my battery were needed.
I finally wrested control from Kingroot by uninstalling version 5.0.5 and installing Kingroot 4.5 instead. Then SuperSU-Me Pro did its work. Had I used Kingroot 4.5 from the outset, would things would have gone better? I don't know. The rooting process for this phone is a one-way trip with a dubious outcome. I know the Express Prime is not costly, but if you're risk adverse think twice before trying to root. I suppose you can undo the whole thing, but I haven't tried and likely will not.
Despite the problems I had, I believe using SuperSU-Me Pro was worth the cost and ultimately saved time. I'm glad I rooted my phone, but -- damn, it was a lot of effort compared to previous phones and my tablet.
I have not tried the de-odexed ROM posted in this thread's OP, but it's on my to-do list. I'm kind of afraid of messing with my phone for the time being. I'll post a review if and when I try it out.
For what it's worth, I wasn't able to get my built-in flashlight toggle to work. I ran the fix script via flashfire with no success. Update: Fixed after installing Busybox. Thanks, DamienMc!

danny8 said:
I wasn't able to get my built-in flashlight toggle to work. I ran the fix script via flashfire with no success.
Click to expand...
Click to collapse
You need busybox installed as well

Busybox
Oh, you're very good. It works!

Help! After flashing the rom, it does not let me log in to the google account and I can not exit that screen, the message it displays is as follows:

danny8 said:
I have AT&T Samsung Galaxy Express Prime GoPhone, J320A. Owned it for one week. It has been carrier-unlocked. I'm now using T-Mobile SIM. Seems to work OK. Only issue I can find is where the SIM status page does not show my phone number.
I would appreciate pointers or maybe a place to look for installation steps. I assume I'll to need to root via Kingroot then replace with SuperSU (if possible). Then install FlashFire.​ I have rooted and installed ROMs on other devices (Galaxy Exhibit, 2012 Nexus tablet, Moto G), but seemingly devices are more locked-down these days. I understand that TWRP is not available for this device and likely will not be.
Last year, I bought a couple of inexpensive T-Mobile phones and "rooted" them with KingRoot which is still installed on those phones. (Not really thrilled about that.) I put rooted in quotes because it doesn't quite behave like a fully-rooted phone, IMO. I'm not very expert in these things, but I know how to follow steps and have used ODIN, TWRP, et cetera.
I'm leery of working with these more locked-down phones. Am I being paranoid and/or incorrect about these matters?
BTW, thanks for the ROM! I'm surprised there aren't more replies.
Maybe this phone is not as popular as I think it should be. Maybe it's too low-spec for the tech-savvy crowd. I got mine for just $64 at Walmart online, but they've since raised the price to $79. Seems like a good deal, even at that price.
I paid $15 to carrier-unlock it. I had to flash firmware (modem file?) before unlocking, then flash another file (restored modem?) after unlocking. I was following emailed instructions after the initial unlock procedure failed.
Click to expand...
Click to collapse
Could you please tell the name of the service/company you used to carrier-unlock it ? (I'm in the same situation) Thanks! @danny8

Samsung S10 Plus - Everytime I restart my phone Magisk would get unrooted. Need help

I am super new to rooting I mainly use it for PokemonGo. I am following this video on YouTube.
Basically when I flashed via Odin, I then install Magisk. Then everything is working and rooted BUT when I restart my phone my Magisk is then magically unrooted (I dont know if this is the right term) it says 'Magisk is not installed' and underneath that is says 'Magisk Manager is up to date'
So why does it keep doing this? Everytime this happens I need to Flash again via Odin and do the whole procedure again. This only happens when I restart the phone. Why does it keep doing this and how do I fix this? I will pay someone who can fix this for me. Ive been trying to figure out for the past day and Im going insane. I have no knowledge about rooting etc like i said i just want to play Pokemongo location spoofing.
Appreciate everyones help.

What did that guide say on how to boot up your device? On devices like yours, that matters...
Here's what the official docs/instructions have on that:
https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery

Didgeridoohan said:
What did that guide say on how to boot up your device? On devices like yours, that matters...
Here's what the official docs/instructions have on that:
https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery
Click to expand...
Click to collapse
Hi it says bixy, power and volume up I believe.

littlepuppies said:
Hi it says bixy, power and volume up I believe.
Click to expand...
Click to collapse
You mean from the guide? Yes, as far as I understand that's the combo that you'd need on an s10 (I don't do Samsung). If you look at John's instructions he's covered that prety well.
Are you sure that you are doing the button combo properly? Because if you don't you'll just end up with Magisk not loading during boot and the system will seem to be unrooted.
But, as I wrote above I don't do Samsung so I'm not the best person to give advice about this... You might be better of asking for advice in your devices forum (because there you'll find people who knows the ins and outs):
https://forum.xda-developers.com/s10-plus

Thread closed as duplicate of https://forum.xda-developers.com/s10-plus/help/samsung-s10-plus-everytime-restart-t4099659