Related
Is there any work being done for a temporary Root option? I ask because it seems that I only need Root for certain issues!
Scenario: Access my hosts file, Tor...etc!
TIA
What is the benefit to only being rooted temporarily? Honestly there isn't a huge security benefit to it, and usability suffers because you have to root it when you want to do anything in your scenarios.
Why not just use SuperUser.apk and not have it remember any associations? That way you only authorize root privileges when you need them, but can stay rooted.
Temp rooting shouldn't even be released for this since we have a permroot so either root your xoom and leave it that way or stay stock
I wouldn't mind a temp root because I haven't rooted from the start, waiting for the 4G upgrade, and because fastboot oem unlock requires a wipe, I don't want to do it, then restore, then do it again. A temp root would be perfect.
I actually have to second Archon810's post. I also would like a temp-root solution so that I could backup my Xoom BEFORE fastboot oem unlock, due to the wipe. I moved all my games off my G2, and started playing further on the tablet screen. However, now I'm gonna lose all those save games. Kinda sucks...
flamingblue8z said:
I actually have to second Archon810's post. I also would like a temp-root solution so that I could backup my Xoom BEFORE fastboot oem unlock, due to the wipe. I moved all my games off my G2, and started playing further on the tablet screen. However, now I'm gonna lose all those save games. Kinda sucks...
Click to expand...
Click to collapse
Either I have completely forgotten how linux works, or you guys just don't get it. AFAIK there's no "temp root". You root, you're rooted.
Not getting what the issue is here either. With superuser you have full control over what app has root access and which not. Root access can be granted and revoked at any time. So certain "things" can have root access, certain not...
cwizardtx said:
Either I have completely forgotten how linux works, or you guys just don't get it. AFAIK there's no "temp root". You root, you're rooted.
Click to expand...
Click to collapse
I believe people want something like the "temp" root achieved for Sensation: http://forum.xda-developers.com/showpost.php?p=15260896&postcount=1; it works quite well for me (no unlock required, one can disable unwanted apps, Titanium works).
"Temporary", since after rebooting updated parts of a locked NAND are overwritten and the changes lost.
This would be useful if you wanted to watch movies from the Market but still wanted to use other things that required root access. Reboot clean, watch movies, run root app, make backups.
My wife's MyTouch 3G Slide had a temporary root app that she only needed when she needed to use the phone as a WiFi Hotspot.
JohannFaust said:
I believe people want something like the "temp" root achieved for Sensation: http://forum.xda-developers.com/showpost.php?p=15260896&postcount=1; it works quite well for me (no unlock required, one can disable unwanted apps, Titanium works).
"Temporary", since after rebooting updated parts of a locked NAND are overwritten and the changes lost.
Click to expand...
Click to collapse
The only reason this is out, is because they don't have real root. And yes you can disable apps...but they are still there.
Sent from my PG86100
I still think a temp root solution would have been nice. Because I just rooted (which is less root, more NAND unlock) so I could upgrade to 3.2 and have full root functionality from MyBackup Pro. Some stability issues, but I will try reflashing in a bit. Would have really been nice to back everything up first, though.
Guys it seems like everyone is concerned about saving apps prior to rooting. Fyi- you can use Androidcommander and back up all your apps and install apps prior to rooting or after rooting. So if thats your concern problem solved...Don't root if your scared but when you follow directions its really a simple root and you learn a little as well.
Sent from my Xoom using Tapatalk
playya said:
Guys it seems like everyone is concerned about saving apps prior to rooting. Fyi- you can use Androidcommander and back up all your apps and install apps prior to rooting or after rooting. So if thats your concern problem solved...Don't root if your scared but when you follow directions its really a simple root and you learn a little as well.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
This is also why the first thing you should do is fastboot oem unlock. You haven't rooted and all apps will still work. But if you decide to root later, you will not loose anything.
playya said:
Guys it seems like everyone is concerned about saving apps prior to rooting. Fyi- you can use Androidcommander and back up all your apps and install apps prior to rooting or after rooting. So if thats your concern problem solved...Don't root if your scared but when you follow directions its really a simple root and you learn a little as well.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
No no, I have my apps already backed up by MyBackup Pro. Its my APP DATA, the save games n'at, that I was trying to back up. Its a moot point now, for me, since I already bit the bullet and rooted, but it would have been valuable to others.
bwcorvus said:
The only reason this is out, is because they don't have real root. And yes you can disable apps...but they are still there.
Sent from my PG86100
Click to expand...
Click to collapse
Not true at all. The Droid X could get permanent OR Temp Root from Z4root, as could MANY phones on froyo. It could Temp root 99% of phones on froyo or earlier according to the developer and the numerous people chiming in that it worked for htem. Some things i just want temp root, so i can backup or access some file. Otherwise, i don't need root full time on this tablet, didn't need it full time either on my Galaxy tab, which i also could Temp root with Z4Root. And did numerous times with ease and no problems
Some of us don't need permanent root. Why is that so hard to understand. I have full root on my X, don't need that on my tablet. Biggest reason is for what was listed, don't want ot have to wipe the whole device. That is just overkill and silly to me. If you want root with a Xoom you realy need to do it from day 1 so you lose nothing.
cwizardtx said:
Either I have completely forgotten how linux works, or you guys just don't get it. AFAIK there's no "temp root". You root, you're rooted.
Click to expand...
Click to collapse
No offense but by saying that you don't know how linux works... If you are on the command line in Linux and type SU or SUDO plus a command after it you gain TEMPORARY ROOT for that command once you put in the password. It is TEMP, after that command passes you are normal user again. Yes you can root yourself full time, but that is a silly thing to do on a linux system and removes a lot of security. Not hard to plug in a password the few times you need to access stuff or edit things
Legato Bluesummers; said:
don't want ot have to wipe the whole device. That is just overkill and silly to me.
Click to expand...
Click to collapse
that's my point, if I can root my HTC EVO without wiping why should I have to do that with my xoom?
Guys
Mybackup Root Androidcommander Titanium Backup can all put your rom back to where it was in minutes. It takes longer to.read why you don't want to root than it would take to restore IMO. Don't root of you don't want to but really do t use the my programs line..
No disrespect though just think with what we have today restoring is not that not big of a deal and after you root clockwork and nandroids are your best friends
Sent from my EVO rocking Evervolv Gingerbread
IceCreaMan said:
that's my point, if I can root my HTC EVO without wiping why should I have to do that with my xoom?
Click to expand...
Click to collapse
Yup thats holding me back, too. Unlike my phones (Hero and Desire) I have not rooted my Xoom on the first day just because I was unsure if I would keep it. Now I am stuck in this mess while one side of me wants to root and install 3.2 and the other side doesn't want to lose all the progress made in the apps/games/whatever...
Hello everyone,
I'm back to a nexus 6 after a very short stint with a 6+.
A little background for my questions: This is the very first time that I rooted a phone. I'm rooting to only install these 3 apps:
adaway
titanium backup
greenify
I do not plan on using any custom ROMs or kernels.
I see from all the guides and tutorials that people also create a custom recovery whenever they root. I haven't done that yet and wasn't sure if I had to. I would like to maintain the stock recovery that I have currently so that I can go back to stock if I unRoot. My questions are:
1. Am I wrong in thinking that I can still use the stock recovery if I unRoot?
2. When a new OTA comes out and I flash it (since I'm rooted an no longer can install them automatically), will that also upgrade my still stock recovery properly?
3. Following up on the previous question, when I upgrade manually because I'm rooted, would that be a fresh install where I have to go in and configure things the way I like them again (system settings, apps and their settings, root the phone again, etc)?
Thanks in advance!
LordGrahf said:
Hello everyone,
I'm back to a nexus 6 after a very short stint with a 6+.
A little background for my questions: This is the very first time that I rooted a phone. I'm rooting to only install these 3 apps:
adaway
titanium backup
greenify
I do not plan on using any custom ROMs or kernels.
I see from all the guides and tutorials that people also create a custom recovery whenever they root. I haven't done that yet and wasn't sure if I had to. I would like to maintain the stock recovery that I have currently so that I can go back to stock if I unRoot. My questions are:
1. Am I wrong in thinking that I can still use the stock recovery if I unRoot?
2. When a new OTA comes out and I flash it (since I'm rooted an no longer can install them automatically), will that also upgrade my still stock recovery properly?
3. Following up on the previous question, when I upgrade manually because I'm rooted, would that be a fresh install where I have to go in and configure things the way I like them again (system settings, apps and their settings, root the phone again, etc)?
Thanks in advance!
Click to expand...
Click to collapse
1. No, you're not wrong. Recovery will stay stock and can be used normally
2. You can't simply flash the new OTA. This will not work manually nor automatically.
3. All you need to do is not flash the user data image and you will not loose your data, settings etc. You will loose root however. See bellow.
Google posts android stock images for each device typically before OTA hits your phone. That's what you want to grab and use for the update. Just make sure you don't run the automatic scripts that come with those images because you need to avoid flashing user data image.
OTA zip file does you no good unless you get your system back to unmodified stock.
Thank you sir!
obsanity said:
1. No, you're not wrong. Recovery will stay stock and can be used normally
2. You can't simply flash the new OTA. This will not work manually nor automatically.
3. All you need to do is not flash the user data image and you will not loose your data, settings etc. You will loose root however. See bellow.
Google posts android stock images for each device typically before OTA hits your phone. That's what you want to grab and use for the update. Just make sure you don't run the automatic scripts that come with those images because you need to avoid flashing user data image.
OTA zip file does you no good unless you get your system back to unmodified stock.
Click to expand...
Click to collapse
Based on the OP, it sounds like he has only rooted. Thus, the OTA will work fine. No need to flash image files.
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
I'm kinda curious myself. I had no idea root killed OTA's. Maybe I wouldn't have done that if I knew that. I'm very new to the Nexus device. It's my 1st. I unlocked the bootloader and rooted already.
Sent from Mark's Nexus 6
crowbarman said:
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
Click to expand...
Click to collapse
This is pretty scary. So you can unroot and GI back to stock and still can't update in anyway?
I have always side-loaded OTAs, I have never flashed anything.
After installing an OTA, on the next reboot, Android takes some time to optimize all your apps. Does this also happen after flashing a new system image? Thanks!
LordGrahf said:
This is pretty scary. So you can unroot and GI back to stock and still can't update in anyway?
Click to expand...
Click to collapse
not sure what you mean by GI, but according to some others, after uninstalling root via SuperSU an OTA will still not install. This should not be the case unless the boot or recovery images are modified. Easily fixed by following the procedures above to fastboot the stock images on your phone.
kjnangre said:
I have always side-loaded OTAs, I have never flashed anything.
After installing an OTA, on the next reboot, Android takes some time to optimize all your apps. Does this also happen after flashing a new system image? Thanks!
Click to expand...
Click to collapse
Yes, it behaves exactly the same.
crowbarman said:
Based on the OP, it sounds like he has only rooted. Thus, the OTA will work fine. No need to flash image files.
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
Click to expand...
Click to collapse
Root on Lollipop is not what it used to be. There are files that need to be modified in order to allow root. That's why this time OTA will fail if you are rooted.
Un-rooting however, will allow OTA as long as it is done properly and all traces are covered up and returned to stock. If it does fail after you have un-rooted, go back to the developer of that un-root method and let the know they missed something.
Here is the best way to un-root. Flash all of the old stock images besides user data image.
obsanity said:
Root on Lollipop is not what it used to be. There are files that need to be modified in order to allow root. That's why this time OTA will fail if you are rooted.
Un-rooting however, will allow OTA as long as it is done properly and all traces are covered up and returned to stock. If it does fail after you have un-rooted, go back to the developer of that un-root method and let the know they missed something.
Here is the best way to un-root. Flash all of the old stock images besides user data image.
Click to expand...
Click to collapse
That makes sense. Is there a manual root procedure or list of required modifications for root out there? I did some precursors searches but Came up empty. Can't tell what's missing in SuperSU unroot without those details.
crowbarman said:
That makes sense. Is there a manual root procedure or list of required modifications for root out there? I did some precursors searches but Came up empty. Can't tell what's missing in SuperSU unroot without those details.
Click to expand...
Click to collapse
Explanation from Chainfire:
https://plus.google.com/113517319477420052449/posts/S5zoKTzKUW1
obsanity said:
Explanation from Chainfire:
https://plus.google.com/113517319477420052449/posts/S5zoKTzKUW1
Click to expand...
Click to collapse
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
crowbarman said:
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
Click to expand...
Click to collapse
That's the problem with Chainfire's work... he does not release source.
Again, best un-root method is to flash original images less user data.
obsanity said:
That's the problem with Chainfire's work... he does not release source.
Again, best un-root method is to flash original images less user data.
Click to expand...
Click to collapse
Thanks for sharing this info. Its a bit concerning tbh. Is there a cleaner way to root other than using superSU?
LordGrahf said:
Thanks for sharing this info. Its a bit concerning tbh. Is there a cleaner way to root other than using superSU?
Click to expand...
Click to collapse
I'm afraid not but Chainfire's is probably the cleanest possible. Koush was the one with an open source solution but he hasn't updated his to 5.0 yet.
obsanity said:
I'm afraid not but Chainfire's is probably the cleanest possible. Koush was the one with an open source solution but he hasn't updated his to 5.0 yet.
Click to expand...
Click to collapse
There is an argument that publishing the method would allow Google to close it that much quicker, I suppose.
crowbarman said:
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
Click to expand...
Click to collapse
The base changes and reasoning for those changes are actually documented on my website. Specific policy adjustments are present in plain text in the supolicy executable, as any hex editor will show you. Those who really wanted to know rather than whine about OSS, know.
By far most policy adjustments just drop audit log output for contexts that are already permissive, though.
All that information is still completely useless unless you understand SELinux in detail and how it's implemented on Android, though.
I assume that the encryption doesn't get in the way of being able to flash the images?
When I went from 5.0 to 5.0.1 on my old Nexus 5 all I did was flash the two new 5.0.1 images I extracted from the full factory image, then re-rooted. This is far cleaner than reverting back to the previous image then doing an OTA. I've not had to update my N6 yet so I don't know if my method will work still, but I hope it does.
Chainfire said:
The base changes and reasoning for those changes are actually documented on my website. Specific policy adjustments are present in plain text in the supolicy executable, as any hex editor will show you. Those who really wanted to know rather than whine about OSS, know.
By far most policy adjustments just drop audit log output for contexts that are already permissive, though.
All that information is still completely useless unless you understand SELinux in detail and how it's implemented on Android, though.
Click to expand...
Click to collapse
Thanks for the additional information.
I did spend a fair amount of time reading your documentation but failed to utilize a hex editor. I am not 'whining' about the lack of open source, rather, simply mildly surprised, but your website aptly describes the challenges with 5.0. Many are used to various root methods being available.
Your solution is fine with me.. I love your work.
Edit: I thought I'd add that the discussion has devolved from the OP, which was whether an OTA can be applied after uninstalling root. The answer was no, due to the unknowns about what still might be modified following the uninstall via SuperSU.
Hey so do you think the blu advance 5.0 hd will be compatible with the work being done on the R1 hd? I would really like to jump on this hype train with my similar but slightly less powerful phone.
I am hoping that I will be able to install a custom rom like R1 users. I also want to root my phone to disable google services in the meantime.
xda123455 said:
Hey so do you think the blu advance 5.0 hd will be compatible with the work being done on the R1 hd? I would really like to jump on this hype train with my similar but slightly less powerful phone.
I am hoping that I will be able to install a custom rom like R1 users. I also want to root my phone to disable google services in the meantime.
Click to expand...
Click to collapse
That phone is based on the 6580 SoC, the R1 uses a 6735. There is a site that lists some roms for blu products that may help, I don't know how reliable they are, I have never used them, but if you want to check it out...
http://www.blu-dev.com
kal250 said:
That phone is based on the 6580 SoC, the R1 uses a 6735. There is a site that lists some roms for blu products that may help, I don't know how reliable they are, I have never used them, but if you want to check it out...
http://www.blu-dev.com
Click to expand...
Click to collapse
Thanks I checked out the site and it seems like there is no blue advance 5.0 roms and no forum activity =/
xda123455 said:
Thanks I checked out the site and it seems like there is no blue advance 5.0 roms and no forum activity =/
Click to expand...
Click to collapse
If your wanting to root it, I'm hearing Kingroot is working, never used it though, so I can't say if it works or if it's safe??
kal250 said:
If your wanting to root it, I'm hearing Kingroot is working, never used it though, so I can't say if it works or if it's safe??
Click to expand...
Click to collapse
I've tried Kingroot, Kingo Root and Frama root. All with no luck.
devanttrio said:
I've tried Kingroot, Kingo Root and Frama root. All with no luck.
Click to expand...
Click to collapse
Did you use the desktop versions? Those have higher success rates. I tried rooting an HTC that way and it worked flawlessly even when the apk didn't.
Autolounge said:
Did you use the desktop versions? Those have higher success rates. I tried rooting an HTC that way and it worked flawlessly even when the apk didn't.
Click to expand...
Click to collapse
I did.
I also tried the apps, of the ones that have apps.
devanttrio said:
I did.
I also tried the apps, of the ones that have apps.
Click to expand...
Click to collapse
You're going to have to do it manually.
no go on kingo
I'm in the same boat. I've got 20 of these BLU Advance 5.0 HD devices and I need to root them to gain access to the VirtualSensor app to emulate a gyroscope. I've tried Kingo and Mobogenie (barf-boo-hisssss). I'm wondering if kingo isn't working on these since they have Marshmallow. I read somewhere they originally shipped with Lollipop.
Did you get anywhere Devanttrio??
trc117 said:
I'm in the same boat. I've got 20 of these BLU Advance 5.0 HD devices and I need to root them to gain access to the VirtualSensor app to emulate a gyroscope. I've tried Kingo and Mobogenie (barf-boo-hisssss). I'm wondering if kingo isn't working on these since they have Marshmallow. I read somewhere they originally shipped with Lollipop.
Did you get anywhere Devanttrio??
Click to expand...
Click to collapse
consider yourself blessed my friend, i'd like to root mine just to get marshmallow.... i have lollipop and checked for updates and says i'm up to date, i can only install 1 app at a time because there is no room on the internal storage, i have to move every app to sd card and then clean cache for each and every app i want.. never recommending blu to anyone
trc117 said:
I'm in the same boat. I've got 20 of these BLU Advance 5.0 HD devices and I need to root them to gain access to the VirtualSensor app to emulate a gyroscope. I've tried Kingo and Mobogenie (barf-boo-hisssss). I'm wondering if kingo isn't working on these since they have Marshmallow. I read somewhere they originally shipped with Lollipop.
Did you get anywhere Devanttrio??
Click to expand...
Click to collapse
I was able to root mine successfully the long way.... had to obtain a dump of the boot.img / recovery.img using software that I'm not sure of the policy of discussion on here at XDA - compile TWRP - unlock bootloader - fastboot boot the compiled recovery - flash SuperSU to get patched boot.img (kitchen was being dumb and systemless root didn't want to work) - Flash SuperSU in system mode - Convert SuperSU.apk to system app so it doesn't get removed every reboot. I can post my compiled TWRP when I'm back at my office or grab it from my repository that I'm trying to establish - https://bluroms.info . Sorry for the design mess / lack of much there at moment haven't had much free time lately in process of cleaning up the device kernel sources to build from source... its sort of ... messy in there...... can post on github if anyone wants in
zjr8 said:
I was able to root mine successfully the long way.... had to obtain a dump of the boot.img / recovery.img using software that I'm not sure of the policy of discussion on here at XDA - compile TWRP - unlock bootloader - fastboot boot the compiled recovery - flash SuperSU to get patched boot.img (kitchen was being dumb and systemless root didn't want to work) - Flash SuperSU in system mode - Convert SuperSU.apk to system app so it doesn't get removed every reboot. I can post my compiled TWRP when I'm back at my office or grab it from my repository that I'm trying to establish - https://bluroms.info . Sorry for the design mess / lack of much there at moment haven't had much free time lately in process of cleaning up the device kernel sources to build from source... its sort of ... messy in there...... can post on github if anyone wants in
Click to expand...
Click to collapse
I've been trying to root a Blu Advance 5.0 HD for a while now and stumbled on this post. I visited your site but am not sure what a 'Scatter File' is, or in what order I need to do things in order to get root.
If you could provide a little more detailed info that would be very much appreciated.
Thanks!
rAy
EDIT: Sorry, to clarify I tried all of the other PC and APK rooting solutions but was able to unlock the bootloader using ADB. I guess I'm just looking for the proper way to root and add TWRP. Thanks!
ray2jerry said:
I've been trying to root a Blu Advance 5.0 HD for a while now and stumbled on this post. I visited your site but am not sure what a 'Scatter File' is, or in what order I need to do things in order to get root.
If you could provide a little more detailed info that would be very much appreciated.
Thanks!
rAy
EDIT: Sorry, to clarify I tried all of the other PC and APK rooting solutions but was able to unlock the bootloader using ADB. I guess I'm just looking for the proper way to root and add TWRP. Thanks!
Click to expand...
Click to collapse
I found a option in developer settings that is "Enable OEM unlocking" and it makes it so you can unlock the bootloader from fastboot, if you do adb reboot-bootloader and then fastboot unlock it should undo the bootloader for you
zjr8 said:
I was able to root mine successfully the long way.... had to obtain a dump of the boot.img / recovery.img using software that I'm not sure of the policy of discussion on here at XDA - compile TWRP - unlock bootloader - fastboot boot the compiled recovery - flash SuperSU to get patched boot.img (kitchen was being dumb and systemless root didn't want to work) - Flash SuperSU in system mode - Convert SuperSU.apk to system app so it doesn't get removed every reboot. I can post my compiled TWRP when I'm back at my office or grab it from my repository that I'm trying to establish - Sorry for the design mess / lack of much there at moment haven't had much free time lately in process of cleaning up the device kernel sources to build from source... its sort of ... messy in there...... can post on github if anyone wants in
Click to expand...
Click to collapse
Like the others said, I would really appreciate if you could give an explanation or tutorial on how to use these files that you uploaded to root the phone. I'm willing to donate some money if required. I only know basic technical stuff haha.
CreativiTimothy said:
Like the others said, I would really appreciate if you could give an explanation or tutorial on how to use these files that you uploaded to root the phone. I'm willing to donate some money if required. I only know basic technical stuff haha.
Click to expand...
Click to collapse
I too am trying to root this device, and am unclear on a few of the steps here. I actually found your site with the recovery and boot images independently, really appreciated! I am at the point where I just need to patch the boot image, though I am not sure how to do this. If you could help me out with this step I might be able to put together some sort of list of steps to get through the whole process if you don't have the time.
Any help would be appreciated, thanks!
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
Just a month ago, OnePlus was caught collecting personally identifiable data from phone owners through incredibly detailed analytics. While the company eventually reversed course on the data collection, another discovery has been made in the software of OnePlus phones. One developer found an application intended for factory testing, and through some investigation and reverse-engineering, was able to obtain root access using it.
Read more Androidpolice:
http://www.androidpolice.com/2017/11/13/oneplus-left-backdoor-devices-capable-root-access/
Does anyone know if uninstalling that app via adb (without root: https://www.google.nl/amp/s/www.xda...arrier-oem-bloatware-without-root-access/amp/) will cause any problems?
swa100 said:
Does anyone know if uninstalling that app via adb (without root: https://www.google.nl/amp/s/www.xda...arrier-oem-bloatware-without-root-access/amp/) will cause any problems?
Click to expand...
Click to collapse
You can root easily using the EngineerMode APK then (after that) uninstall it! ::
I'm trying to push the su binaries, but when I try to mount /system as rw using "mount -o rw,remount,rw /system" I get the following error:
Code:
mount: '/dev/block/dm-0'->'/system': Device or resource busy
Any ideas on how to get around this? Something to do with dm-verity?
Update:
Got the system to mount using:
Code:
mount -o rw,remount -t ext4 /dev/block/dm-0 /system
But whenever I try to push the su binary, the phone reboots.
Update 2:
SuperSu is now working. See https://www.reddit.com/r/oneplus/comments/7cuu0w/gain_root_via_the_recent_backdoor/
I think it's time to switch to aosp
Sent from my Oneplus 5 using Tapatalk
Waits patiently for him to push apk out to root without rooting
Yeah,im waiting/on it since morning.I did run the adb command,it says Root successfull in engineering mode app ,but Super su says Binary not found.
And the best part it has MR ROBOT references everywhere.
The guy who found exploit has twitter account themed MrRobot.
The final best one the IRONY,the password of backdoor is 'ANGELA'
Looks like fan of series in Oneplus or Qualcomm.
I will be incredibly happy even if the only thing this allows us to do is to install adaway without having to unlock bootloader, install custom recovery and all that...
I've found the app and set "Modify system settings" to "no". Would that stop someone giving root access? [I know it can be re-enabled, just asking]
Alan
IonAphis said:
I will be incredibly happy even if the only thing this allows us to do is to install adaway without having to unlock bootloader, install custom recovery and all that...
Click to expand...
Click to collapse
i don't understand what's the matter with unlocking the bootloader n flashing a custom recovery n everything ? what's the problem with it ?
ReyTheBoss said:
i don't understand what's the matter with unlocking the bootloader n flashing a custom recovery n everything ? what's the problem with it ?
Click to expand...
Click to collapse
Reasons.
This app "Engineer mode" is present in many "chinese" phones and in mediateks phones.
Personnaly, i'm not surprised but this exploit was never expoited before...
Time to install aosp rom... OnePlus is a youg company and i think security is not a priority for them
AOSP and other open source ROMs are most secure than Oxygen, but has too much bugs and requires more time to configure it.
Isn't a good solution to all users.
bartito said:
AOSP and other open source ROMs are most secure than Oxygen, but has too much bugs and requires more time to configure it.
Isn't a good solution to all users.
Click to expand...
Click to collapse
blinkin said:
I think it's time to switch to aosp.
Click to expand...
Click to collapse
I'm going to suggest the NoLimits ROM, which is based upon OOS but no spying junk; I'm not seeing the engineering mode app in the list of apps.
https://forum.xda-developers.com/on...xxx-nolimits-1-1-speed-ram-optimized-t3627121
(Don't be lazy; push yourself to learn something new.)
It's pretty stable and has a few nice bells and whistles which make it a compelling alternative to OOS.
If you want spying junk you can't easily get rid off, stick with OOS. If you want more control and better privacy, go with a custom ROM, even one that is based on OOS.
ReyTheBoss said:
i don't understand what's the matter with unlocking the bootloader n flashing a custom recovery n everything ? what's the problem with it ?
Click to expand...
Click to collapse
Same question here, is that hard to unlock the bootloader and install a custom recovery?
The only reason that I can think is because maybe someone that don't have access to a PC
ReyTheBoss said:
i don't understand what's the matter with unlocking the bootloader n flashing a custom recovery n everything ? what's the problem with it ?
Click to expand...
Click to collapse
Unlocking bootloader wipes of our data including internal storage. And we have to take backup whole data and restore once its done which is pain in the a$$
When will the APK come out to root? Hopefully before OnePlus patches it.
pacattack81 said:
When will the APK come out to root? Hopefully before OnePlus patches it.
Click to expand...
Click to collapse
But... The reason you gained access in the first place is because the app was there. When the app goes so does your root access. No?
I am surprised that no one is commenting on the weird apparent coincidence that the password is a theme on the same movie that the discoverer of the exploit is a fan on. Emphasis on "apparent". Anyone want to bet that we soon learn that the "discoverer" is either an OP or Qualcomm employee who had a hand of putting it there in the first place?
And finally, is there any apparent downside of just deleting this thing? Or a Magisk module to disable it, just like the one that got made for the other Spyware?
NoLimits is removing EngineeringMode app (and also other related apps) if you select the agressive debloating mode on install.
I have done it this morning on my rooted O+5.
Now I delete the following apps each time that I reinstall OOS:
Code:
/system/app/AndroidPay"
/system/app/BasicDreams"
/system/app/BookmarkProvider"
/system/app/BTtestmode"
/system/app/Calculator"
/system/app/Calendar"
/system/app/CalendarGoogle"
/system/app/Chrome"
/system/app/DMAgent"
/system/app/Drive"
/system/app/Duo"
/system/app/Email"
/system/app/EngineeringMode"
/system/app/EngSpecialTest"
/system/app/ExactCalculator"
/system/app/FaceLock"
/system/app/Gmail2"
/system/app/GoogleTTS"
/system/app/GoogleWallpaperPicker"
/system/app/LatinIME"
/system/app/LatinIme"
/system/app/LatinImeGoogle"
/system/app/LiveWallpapersPicker"
/system/app/LogKitSdService"
/system/app/Maps"
/system/app/messaging"
/system/app/Music2"
/system/app/MusicFX"
/system/app/NFCTestMode"
/system/app/OemAutoTestServer"
/system/app/OEMLogKit"
/system/app/OPBackup"
/system/app/OPBugReportLite"
/system/app/OPPush"
/system/app/OPSocialNetworkHub"
/system/app/OpenWnn"
/system/app/OPLauncher_aosp"
/system/app/OPWallpaperResources"
/system/app/PartnerBookmarksProvider"
/system/app/Photos"
/system/app/PhotosOnline"
/system/app/PicoTts"
/system/app/PrintSpooler"
/system/app/SecureSampleAuthService"
/system/app/SensorTestTool"
/system/app/Stk"
/system/app/talkback"
/system/app/Videos"
/system/app/WifiRfTestApk"
/system/app/YouTube"
/system/priv-app/Eleven"
/system/priv-app/Gallery2"
/system/priv-app/H2DefaultIconPack"
/system/priv-app/H2FolioIconPack"
/system/priv-app/H2LightIconPack"
/system/priv-app/Launcher3"
/system/priv-app/Launcher3-azaidi"
/system/priv-app/OPDeviceManager"
/system/priv-app/OPDeviceManagerProvider"
/system/priv-app/OneplusCircleIconPack"
/system/priv-app/OnePlusGallery"
/system/priv-app/OneplusIconPack"
/system/priv-app/OneplusSquareIconPack"
/system/priv-app/OPMms"
/system/priv-app/Snap"
/system/etc/usb_drivers.iso"
/system/bin/bugreport*"
/system/bin/fmfactorytest*"
/system/bin/oemlogkit"
/system/bin/WifiLogger_app"
CaptShaft said:
I'm going to suggest the NoLimits ROM, which is based upon OOS but no spying junk; I'm not seeing the engineering mode app in the list of apps.
https://forum.xda-developers.com/on...xxx-nolimits-1-1-speed-ram-optimized-t3627121
(Don't be lazy; push yourself to learn something new.)
It's pretty stable and has a few nice bells and whistles which make it a compelling alternative to OOS.
If you want spying junk you can't easily get rid off, stick with OOS. If you want more control and better privacy, go with a custom ROM, even one that is based on OOS.
Click to expand...
Click to collapse
I have two question to the people who actually have some knowledge. If I gain root access via ADB and that app:
1) will I be able successfully to flash OTAs in the future?
2) will the root disappear once the next ota is applied to my phone (in case the answer for the previous question is positive)?