Below you will find instructions how to root this device.
The following procedure has been tested up to firmware MMB29K.J320AUSC2AQA1
KNOX should remain 0x0
However you undertake this at your own risk.
(NOTE: This procedure will also work for the SM-J320AZ (Cricket))
Issues:
Wifi passwords not remembered (fix below)
Stock Flashlight app not working.
Model number may be missing from build.prop (fix below)
Instructions
1.Download the eng boot image.
This is a special boot image normally used by engineers, it allows selinux to be booted in permissive mode with relaxed root restrictions.
Do not replace this image with the stock image after rooting your device or you will possibly soft brick your device.
(See below for how to recover)
ENG_BOOT_J320A_PG1
2. Flash the boot image:
Download Odin v3.11.1
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the ENG_BOOT_J320A_PG1.tar to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
3. Install and run Kingroot:
http://www.apkmirror.com/apk/kingro...-release/kingroot-5-0-5-android-apk-download/
You may need to run Kingroot several times to gain successful root.
4. Install and run SuperSU me to remove Kingroot and convert to SuperSU (not required) :
https://play.google.com/store/apps/...ore&pcampaignid=APPU_1_uzPDVbGyFcGNyATHrqmoCA
Alternative (free) method to replace Kingroot:
Follow Steps 3 to 12.
https://forum.xda-developers.com/ga...ide-how-to-root-tripping-knox-kitkat-t3129484
Don't flash the boot partition with Flashfire, uncheck.
You will also need to flash the system version of SuperSU not EverRoot.
When you get to step 12, don't flash the firmware. Disable EverRoot and just flash this:
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
5. Wifi fix:
modify the line below in /system/build.prop:
ro.securestorage.support=true to false
6. Model number fix:
http://www.techgainer.com/change-fake-android-device-model-number-and-brand-name/
7. To fix “Unauthorized actions have been detected”
disable 'Security log agent'
Enjoy your rooted device.
Recovering from a soft brick:
Flash the stock firmware provided below wirh ODIN in the AP slot.
https://www.androidfilehost.com/?fid=745425885120713788
J3 forum link: https://forum.xda-developers.com/t/galaxy-j3-2016
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
Thanks bud. Your post in the other thread convinced me to purchase this device... so far so good
To everyone else, I had to use the patched version of supersu me to remove kingroot
Bugs in the system
So i reflashed the stock rom, everything was great. when i reflashed the file you gave us, debugging has failed to work as well as the flashlight. other than that no issues so far
bobbyp1086 said:
So i reflashed the stock rom, everything was great. when i reflashed the file you gave us, debugging has failed to work as well as the flashlight. other than that no issues so far
Click to expand...
Click to collapse
What do you mean debugging does not work? Adb is enabled by default, it's an engineering boot image.
ashyx said:
What do you mean debugging does not work? Adb is enabled by default, it's an engineering boot image.
Click to expand...
Click to collapse
instead of it asking if i want the computer to read i get this
bobbyp1086 said:
instead of it asking if i want the computer to read i get this
Click to expand...
Click to collapse
What response do you get for
adb devices
In adb?
Think the dous firmware has issues on our devices.
I'll upload j320aucu2apj2 shortly
DamienMc said:
Think the dous firmware has issues on our devices.
I'll upload j320aucu2apj2 shortly
Click to expand...
Click to collapse
How is an older firmware going to be better when most people will already be running AQA1 firmware?
ashyx said:
What response do you get for
adb devices
In adb?
Click to expand...
Click to collapse
The generic. But then i set the directory to sdk/platformtools and it worked.
But flashlight gone. Keyboard,google services and cell gone. Cant uninstall kingroot with every method out there and my phone is glitching
---------- Post added at 10:04 PM ---------- Previous post was at 10:02 PM ----------
DamienMc said:
Think the dous firmware has issues on our devices.
I'll upload j320aucu2apj2 shortly
Click to expand...
Click to collapse
Mine is stock duos, i love the stock rom, but my conputer died this morning,no hopes of odin
bobbyp1086 said:
The generic. But then i set the directory to sdk/platformtools and it worked.
But flashlight gone. Keyboard,google services and cell gone. Cant uninstall kingroot with every method out there and my phone is glitching
---------- Post added at 10:04 PM ---------- Previous post was at 10:02 PM ----------
Mine is stock duos, i love the stock rom, but my conputer died this morning,no hopes of odin
Click to expand...
Click to collapse
King root can be replaced with supersu me or the script. It can also be easily uninstalled via its settings.
What did you actually install?
My system went haywire. I need a command thru terminal on android to factory reset, can't boot into recovery.
bobbyp1086 said:
My system went haywire. I need a command thru terminal on android to factory reset, can't boot into recovery.
Click to expand...
Click to collapse
Just hold POWER + HOME + VOL DOWN until the device reboots then immediately change to POWER + HOME + VOL UP to get in to recovery mode or in Terminal type
su
reboot recovery
.
Thats a no go, can't boot up. kingroot seems to have killed my phone i just get "unfortunatley System UI has Stopped" when i power up. I will reflash withwork comp and update in a few hours...
bobbyp1086 said:
Thats a no go, can't boot up. kingroot seems to have killed my phone i just get "unfortunatley System UI has Stopped" when i power up. I will reflash withwork comp and update in a few hours...
Click to expand...
Click to collapse
You can't possibly have lost the recovery, nothing has touched it. It does take a short while for stock recovery to boot.
ashyx said:
Just hold POWER + HOME + VOL DOWN until the device reboots then immediately change to POWER + HOME + VOL UP to get in to recovery mode or in Terminal type
su
reboot recovery
.
Click to expand...
Click to collapse
ashyx said:
You can't possibly have lost the recovery, nothing has touched it. It does take a short while for stock recovery to boot.
Click to expand...
Click to collapse
Iam lost as to how it happened as well lol but its ok, just a tester phone for fun 3rd time i have done something wrong :laugh:
---------- Post added at 04:33 PM ---------- Previous post was at 04:12 PM ----------
Reflashed Stock Firmware, regained access to recovery, factory reset and back up and running. i actually noticed some new features in recovery. i can actually apply update from sd now, whereas before i could not access files on sd, looks like dm-verity is also gone, or at least not showing up in recovery as before (maybe because it was a failed test) also the start up of the phone has skipped the initial set up (no add account or set up password) and the main screen is way more crisp and clear than what i had on before, even with the other 3 reflashes i have previously done. so far so good though
DamienMc said:
Thanks bud. Your post in the other thread convinced me to purchase this device... so far so good
To everyone else, I had to use the patched version of supersu me to remove kingroot
Click to expand...
Click to collapse
How did the patch work? mine keeps opening saying licence validated and closing....going to try script version
bobbyp1086 said:
How did the patch work? mine keeps opening saying licence validated and closing....going to try script version
Click to expand...
Click to collapse
The model number missing is a known issue. You just need to edit the build.prop and put it back.
See this link for more info: http://www.techgainer.com/change-fake-android-device-model-number-and-brand-name/
bobbyp1086 said:
How did the patch work? mine keeps opening saying licence validated and closing....going to try script version
Click to expand...
Click to collapse
Used an old version, 9.7.4P
And I only got the script to work once :/
DamienMc said:
Used an old version, 9.7.4P
And I only got the script to work once :/
Click to expand...
Click to collapse
ok so the script is working but there is a different way
1. install kingroot 4.5 from apk mirror
2. Run script
3. update Su
4. update Binary
(i had to reinstall kingroot and deny kingroot root permission before binary would update and uninstall and keep root)
it seems denying kingroot root permission keeps the root on the device, letting su take over for root permission and uninstall of kingroot.
i know it seems weird but it works, the hang up was updating su, which you can do from google play
---------- Post added at 05:14 PM ---------- Previous post was at 04:56 PM ----------
Anyone have a stock "Build.prop" for this model
bobbyp1086 said:
Anyone have a stock "Build.prop" for this model
Click to expand...
Click to collapse
I'll upload it later.
Related
http://phandroid.com/2012/08/13/t-mobile-springboard-getting-android-4-0-4-this-wednesday/
Sent from my HUAWEI OsiMood MediaPad using Tapatalk 2
How about mediapad?
Is it has a ics 4.0.4 too?
ZEII said:
How about mediapad?
Is it has a ics 4.0.4 too?
Click to expand...
Click to collapse
Huawei had released ICS for media pad a while ago. Check the development section.
Sent from my HUAWEI OsiMood MediaPad using Tapatalk 2
but only 4.0.3, not 4.0.4
441Excelsior said:
but only 4.0.3, not 4.0.4
Click to expand...
Click to collapse
True.
Sent from my HUAWEI OsiMood MediaPad using Tapatalk 2
From tmonews, it's 4.0.3 and not 4.0.4. I think 4.0.3 is the correct one. Anyway, we will know it soon enough.
Would somebody be so kind and try to keep the update.zip for those of us who have problems getting back to stock?
ICS is now released and my Springboard is downloading the update!
Here is the ZIP file update for anyone that want to grab it to extract and play...
http://www.gamefront.com/files/22180781/Springboard-ics-update.zip
Update:
OTA failed for me right away. I got the update to manually install with the following steps:
1) Created a folder on root of my SDcard, dload
2) Copied the update ZIP file above into dload and renamed it to update.zip
3) Created a zero length file unlmt.cfg in the dload folder
Rebooted with normal VOL+ key held down to start a SD install.
Note: After upgrade completed the Launcher would not start and kept repeating "Unfortunately Launcher has stopped".
To fix, click Ok and quickly bring up the Statusbar menu by swiping it at the bottom of the screen and click on the clock/date, next enter Settings->Apps->All->Launcher, then clear data.
Looks like a full update So everyone who flashed the Springboard to MediaPad could go back now, if wanted.
Best feature in this update for me is, the startup T-mobile sound is about 1/4 the old volume!
:fingers-crossed:
Does this T-mobile ICS seem to support the phone function?
vicfuze said:
ICS is now released and my Springboard is downloading the update!
.......
Click to expand...
Click to collapse
Thanks for the info and link vicfuze!
Update worked great, and I got it rooted without problems.
Have been eagerly awaiting this.
vicfuze said:
Here is the ZIP file update for anyone that want to grab it to extract and play...
Click to expand...
Click to collapse
Much appreciated but it would have been even nicer if you could have posted the original URL from Google
I'm downloading it now. I think I might try to flash just the radio files and see if that improves things for me. I'm otherwise satisfied with the international ICS firmware.
---------- Post added at 10:36 PM ---------- Previous post was at 10:35 PM ----------
vicfuze said:
Best feature in this update for me is, the startup T-mobile sound is about 1/4 the old volume!
:fingers-crossed:
Click to expand...
Click to collapse
You can remove that sound with root. I think it's:
/cust/tmobile/us/media/animationsounds/bootSound.ogg
Rename or delete it.
---------- Post added at 10:51 PM ---------- Previous post was at 10:36 PM ----------
Question: What's the baseband version post-update?
Hi,
does anybody know, if I can run this update on the German Version of the Mediapad or shall I better refrain from trying?
Thank you
Made some Mirrors...
Mirror 1
Mirror 2
Happy Flashing !
springboard root
Does the springboard have to be rooted before the update to get root? I used the update but it is not rooted now nor was it before and I would like to get root.
whgarner said:
Does the springboard have to be rooted before the update to get root? I used the update but it is not rooted now nor was it before and I would like to get root.
Click to expand...
Click to collapse
Nope the update is a full wipe. So you will need to root after the update.
http://www.modaco.com/topic/354579-...-mediapad-t-mobile-springboard-orange-tahiti/
nightanole said:
Nope the update is a full wipe. So you will need to root after the update.
http://www.modaco.com/topic/354579-...-mediapad-t-mobile-springboard-orange-tahiti/
Click to expand...
Click to collapse
Here is a mirror of the SU installer pkg from that post for US folks.
http://www.gamefront.com/files/22185176/Huawei+MediaPad+ROOT+ICS+Android+4.0.x.rar
vicfuze said:
Here is a mirror of the SU installer pkg from that post for US folks.
http://www.gamefront.com/files/22185176/Huawei+MediaPad+ROOT+ICS+Android+4.0.x.rar
Click to expand...
Click to collapse
Have you actually got this root method to work for the non-Mediapad Springboard with the T-Mobile firmware? I run Linux and so the command script in this package will not exactly execute on my machine. I tried manually sequentially entering the adb commands contained in the command script, and got stuck at a 'permission denied' error within the first several commands. If this does work for the Springboard, and not just the Mediapad, then there might be something about the embedded windows drivers and software for the device that allows it to work...because I sure can't get it to fly on Ubuntu.
xdajunkman said:
Have you actually got this root method to work for the non-Mediapad Springboard with the T-Mobile firmware? I run Linux and so the command script in this package will not exactly execute on my machine. I tried manually sequentially entering the adb commands contained in the command script, and got stuck at a 'permission denied' error within the first several commands. If this does work for the Springboard, and not just the Mediapad, then there might be something about the embedded windows drivers and software for the device that allows it to work...because I sure can't get it to fly on Ubuntu.
Click to expand...
Click to collapse
I actually used the below method to install root again on ICS. I believe there is a fastboot for Linux if you cannot find a DOS/Windows machine.
Only issue I was my Springboard was recovery booting off of "recovery2" partition so I needed to flashboot that partition to get CWM recovery to boot. Since the Official Springboard ICS zip package contains the stock recovery.img file you really can flash both recovery/recovery2 partitions and revert back later if needed.
http://forum.xda-developers.com/showthread.php?t=1850367
And to clarify, for booting into Fastboot, you hold the power button and the VOL closest to it down at the same time.
To boot recovery/CWM hold the power button and VOL key furthur away from the power button (its VOL Up) for some reason.
Also, don't try to use the Touch recovery (TWM) package, it froze up on me when trying to run the root zip installer, but luckily reverting to the basic CWM recovery, I was able to re-install and fix my boot looping.
i found this trwp recovery floating around i dont know who made it.
it boots fine but no touch screen hopefully someone can fix it
https://www.androidfilehost.com/?fid=457095661767138152
kvip60 said:
i found this trwp recovery floating around i dont know who made it.
it boots fine but no touch screen hopefully someone can fix it
https://www.androidfilehost.com/?fid=457095661767138152
Click to expand...
Click to collapse
What's the easiest way to install this?
I didn't install it I just used" fastboot boot image-name"
kvip60 said:
I didn't install it I just used" fastboot boot image-name"
Click to expand...
Click to collapse
Ok Thanks. I am in and generating a backup. The touch screen was working for me mostly. It won't let me select Micro SDCard to save my backup.
Yeah like I said it need some repair I am pretty sure the mount points aren't perfect and I didn't compile it I had to use an otg and mouse to navigate
kvip60 said:
Yeah like I said it need some repair I am pretty sure the mount points aren't perfect and I didn't compile it I had to use an otg and mouse to navigate
Click to expand...
Click to collapse
What I did to navigate was I had to push the power button then it would bring the screen up where you can swipe the bottom to unlock the screen and use touchscreen. Navigating the storage was odd because it shows it is stuck on Internal storage, but If i click on SDCard, it will take me to that directory. I hope there is a nice update to this is the near future, so we don't have to access it through "adb reboot recovery"
You can flash it if you like I just don't trust this copy yet waiting for an update before I flash it
You can use" fastboot flash recovery twrp.img" to flash rather than "fastboot boot twrp.img " to boot it
kvip60 said:
You can flash it if you like I just don't trust this copy yet waiting for an update before I flash it
You can use" fastboot flash recovery twrp.img" to flash rather than "fastboot boot twrp.img " to boot it
Click to expand...
Click to collapse
Oh man you were so right. I had it flashed and it caused me all kinds of problems, like booting the screen upside down etc. I was finally able to find the recovery.img in another thread and get back the stock recovery. I think I will also wait until there is a more stable TWRP version.
I always use boot to test and I always backup my recovery before flashing because I had that happen to me before
Any idea on when a decent working custom recovery will be available?
blahforme said:
Any idea on when a decent working custom recovery will be available?
Click to expand...
Click to collapse
Probably when someone will have the will & time to work on it.
Maybe you'd like to take on this topic?
Lol. I hear you. I have very little understanding of Linux I have tried to make one but there aren't enough information about compiling device /vendor tree for a new device to go on
Just visit this page and you will get TWRP for Z016D. It's a Taiwan website with Chinese but you can see the blue link marked as "TWRP" and there you are.
https://www.asus.com/zentalk/tw/thread-214217-1-1.html
lssong99 said:
Just visit this page and you will get TWRP for Z016D. It's a Taiwan website with Chinese but you can see the blue link marked as "TWRP" and there you are.
https://www.asus.com/zentalk/tw/thread-214217-1-1.html
Click to expand...
Click to collapse
Thanks for this. Posting the Mega so people don't have to make an Asus account to grab it.
https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
The 20170218 recovery works perfectly with my phone (6/64gb, 820). The first one posted in the OP worked, but was a bit glitchy. The updated one has working SD reading and touchscreen works without having to lock it first.
Could someone please tell me why twrp is booting upside down on my device, and how do I fix it? I just tried to run it in fastboot boot twrp-3.0.3-0-Z016D-20170218.img and once again it loads upside down, however the touch screen is where it normally is suppose to be, which makes it very difficult to navigate the menus. It is very frustrating. This has happened to me multiple times this week. I can't seem to get it to boot/load properly.
blahforme said:
Could someone please tell me why twrp is booting upside down on my device, and how do I fix it? I just tried to run it in fastboot boot twrp-3.0.3-0-Z016D-20170218.img and once again it loads upside down, however the touch screen is where it normally is suppose to be, which makes it very difficult to navigate the menus. It is very frustrating. This has happened to me multiple times this week. I can't seem to get it to boot/load properly.
Click to expand...
Click to collapse
Are you using the Snapdragon 821 version by any chance? Cause people with the s820 seem to be working fine.
I am using 821 my screen is flipped and no touch even after locking it
Huffy1 said:
Are you using the Snapdragon 821 version by any chance? Cause people with the s820 seem to be working fine.
Click to expand...
Click to collapse
No, I am using the sd820.
---------- Post added at 08:25 PM ---------- Previous post was at 08:07 PM ----------
I really don't want to wipe everything and start all over from scratch because everything else is working great right now. I guess if there is no easy solution, then I will just leave it alone. I ran it with fastboot and then made a backup and saved it on my microSD card. But I am worried if I wipe everything and start all over again, then I will have to call my bank again to verify my cards for Android pay. I am running the stock firmware version 1698, with stock recovery, an unlocked bootloader, & rooted. Also have Magisk & Titanium Pro installed, and I verified that Andoid pay works for me. (I already bought something using Android pay).
blahforme said:
No, I am using the sd820.
---------- Post added at 08:25 PM ---------- Previous post was at 08:07 PM ----------
I really don't want to wipe everything and start all over from scratch because everything else is working great right now. I guess if there is no easy solution, then I will just leave it alone. I ran it with fastboot and then made a backup and saved it on my microSD card. But I am worried if I wipe everything and start all over again, then I will have to call my bank again to verify my cards for Android pay. I am running the stock firmware version 1698, with stock recovery, an unlocked bootloader, & rooted. Also have Magisk & Titanium Pro installed, and I verified that Andoid pay works for me. (I already bought something using Android pay).
Click to expand...
Click to collapse
How did you install Magisk having stock recovery? Using the in-app installation?
---------- Post added at 01:08 PM ---------- Previous post was at 01:05 PM ----------
It seems @EypCnn is the developer of this TWRP builds...
sebastiandg7 said:
How did you install Magisk having stock recovery? Using the in-app installation?
Click to expand...
Click to collapse
I flashed Magisk v11.1 with TWRP, then installed Magisk Manager from the Google Play Store, after I rebooted my device. I did that by booting in to TWRP with fastboot to flash the .zip file. I did not flash TWRP to install Magisk.
I got this device used and it had been updated to the newest firmware. It would not work with Kingroot, Framaroot, SRS, or Kingo. The only option was to attempt to downgrade to an older firmware with unpatched exploits. The Verizon J1 has a locked bootloader so it cannot flash full firmware packages with older bootloaders. Luckily it can be downgraded to older firmware of the same android version with older kernel. I just had to unpack the firmware and remove the bootloader and repack. I tried to make a rooted stock firmware but can't seem to repack the system.img.ext4 properly after mounting it.
Now let's get down to business
1. Download Odin 3.09
2. Download modified (by me) rootable firmware. Do not rename file it might mess up md5sum.
3. Boot phone to download mode. Hold power+vol down+ home.
4. Start Odin and connect phone with original factory sync cable.
5. Click on the AP button and select the firmware downloaded above. It will check the md5sum automatically when it finishes and passes then press the start button. Once the flash finishes it will reboot.
6. Enable usb debugging.
7. Download Kingoroot for PC (google) and let it run. The apk will not work to root. It should install drivers automatically.
8. Profit!!
I'm testing a method to reliably switch to Supersu but having trouble updating binary 100% of the time. I've tried to flash exposed but Flashfire doesn't seem to work properly with this device. If anyone can suggest a workaround please share.
OP, is it okay if I don't have original factory sync cable in hands?
volibyro said:
OP, is it okay if I don't have original factory sync cable in hands?
Click to expand...
Click to collapse
Yeah its ok you just run into less issues with original cable.
**Working on updating links I have a slow upload speed though.
HideTheCookies said:
I got this device used and it had been updated to the newest firmware. It would not work with Kingroot, Framaroot, SRS, or Kingo. The only option was to attempt to downgrade to an older firmware with unpatched exploits. The Verizon J1 has a locked bootloader so it cannot flash full firmware packages with older bootloaders. Luckily it can be downgraded to older firmware of the same android version with older kernel. I just had to unpack the firmware and remove the bootloader and repack. I tried to make a rooted stock firmware but can't seem to repack the system.img.ext4 properly after mounting it.
Now let's get down to business
1. Download Odin 3.09
2. Download modified (by me) rootable firmware. Do not rename file it might mess up md5sum.
3. Boot phone to download mode. Hold power+vol down+ home.
4. Start Odin and connect phone with original factory sync cable.
5. Click on the AP button and select the firmware downloaded above. It will check the md5sum automatically when it finishes and passes then press the start button. Once the flash finishes it will reboot.
6. Enable usb debugging.
7. Download Kingoroot for PC (google) and let it run. The apk will not work to root. It should install drivers automatically.
8. Profit!!
I'm testing a method to reliably switch to Supersu but having trouble updating binary 100% of the time. I've tried to flash exposed but Flashfire doesn't seem to work properly with this device. If anyone can suggest a workaround please share.
Click to expand...
Click to collapse
If u want to switch to SuperSu from KingoROOT, the best and easiest method would be backing up ur phone and performing a soft reset. Afterwards simply install SuperSu, the superuser binary is already installed from kingroot - no worries, just update it normally via SuperSU and disable KNOX after the update is complete.
That switch idea of yours might get you bricked
Confirmed it works now we need a recovery so we can just flash su
SuperSUme works really really well lol, this phone is 32bit only any1 wanna try 4 a recovery?
Thxx bro
I've tried porting a few times from the j100h twrp and keep getting a return to Verizon dealer screen. So I'd assume the bootloader is still locked. Im going to try the old safestrap and see if i can't get that working. But im kinda a noob so I'll do my best.
p.s. Don't try flashing any recovery until you backup your current one with rashr or flashify.BE SAFE.btw I've yet to see supersume actually work but hey it could happen. I'd much rather just flash the su from a recovery.
gravyd316 said:
I've tried porting a few times from the j100h twrp and keep getting a return to Verizon dealer screen. So I'd assume the bootloader is still locked. Im going to try the old safestrap and see if i can't get that working. But im kinda a noob so I'll do my best.
p.s. Don't try flashing any recovery until you backup your current one with rashr or flashify.BE SAFE.btw I've yet to see supersume actually work but hey it could happen. I'd much rather just flash the su from a recovery.
Click to expand...
Click to collapse
Agreed about flashing the recovery, but you need to be rooted with KingOroot to get SuperSUme to work, & it helps to just keep the screen timeout turned off thru this process , after it says "complete" I downloaded SuperSU & installed, updated, "disabled" knox, & I can also use flashfire although its pretty worthless for anything other than backups, as the little AROMA shell emulator thingy does run after the verizon logo is showing, which indicates to me yea its locked down pretty solid lol.
I tried Safestrap & it gave me a /SS folder in my /etc so I looked into that but I can't manage to figure out how I should go placing the files to make it work lol. But i do know this thing is 32bit ONLY, so compiling the j100H twrp for instance will NOT flash no matter what we do to the bootloader, it will bootloop since the architecture is for a 64bit SoC, we need someone to compile the j100H twrp in a 32bit only compatible architecture, & then you can easily flash it like cake, & TWRP should do the rest like all other Samsung phones O.O
its gotten to the point these are all the apps I have when i restore haha, if you wanna PM me about working together to get this thing a little more flexible I'm always open to ideas . I only use this thing as a hotspot but would totally like to see a recovery at least make it over & from there I could definitely start the ROM bringup
Will I get bricked by doing this with Verizon
Weegee1 said:
Will I get bricked by doing this with Verizon
Click to expand...
Click to collapse
you cant hard brick this device, restore with ODIN start over.
LilAnt530 said:
you cant hard brick this device, restore with ODIN start over.
Click to expand...
Click to collapse
I did it. I keep getting a notification that SE for Android has been turned off. What do I do
Weegee1 said:
I did it. I keep getting a notification that SE for Android has been turned off. What do I do
Click to expand...
Click to collapse
Download any terminal app & type in 'su' then 'setenforce 1'
---------- Post added at 12:42 AM ---------- Previous post was at 12:41 AM ----------
Weegee1 said:
I did it. I keep getting a notification that SE for Android has been turned off. What do I do
Click to expand...
Click to collapse
Download any terminal app & type in 'su' then 'setenforce 1' and you should be good.
LilAnt530 said:
Download any terminal app & type in 'su' then 'setenforce 1'
---------- Post added at 12:42 AM ---------- Previous post was at 12:41 AM ----------
Download any terminal app & type in 'su' then 'setenforce 1' and you should be good.
Click to expand...
Click to collapse
THANKS! sorry last noob question, will I lose root if I turn my phone off
Weegee1 said:
THANKS! sorry last noob question, will I lose root if I turn my phone off
Click to expand...
Click to collapse
Haha believe it or not that's a pretty reasonable question! xD, you shouldn't, i cannot see why, if you have problems just restore i will help ya through it again, & if you want xposed ONLY use the material installer from xda
LilAnt530 said:
Haha believe it or not that's a pretty reasonable question! xD, you shouldn't, i cannot see why, if you have problems just restore i will help ya through it again, & if you want xposed ONLY use the material installer from xda
Click to expand...
Click to collapse
I'll get Xposed another time. I turned off my phone a couple times but the root stayed so that's a plus :victory:
Weegee1 said:
I'll get Xposed another time. I turned off my phone a couple times but the root stayed so that's a plus :victory:
Click to expand...
Click to collapse
If you havent used SUPERSUme to transfer it over to SuperSU, google the app, can't find the free one on play store anymore i guess.
LilAnt530 said:
If you havent used SUPERSUme to transfer it over to SuperSU, google the app, can't find the free one on play store anymore i guess.
Click to expand...
Click to collapse
And with SuperSU, is that one more stable
Below you will find my procedure to root the SM-J727P Galaxy J7 Perx / MSM8953
This procedure has only been tested on J727PVPU1AQB9 firmware. It may work for future releases or it may not.
If an updated firmware becomes available my advice is to update with FLASHFIRE to maintain root.
This took some doing and was a tough nut to crack. I don't own this device and much thanks goes to those that stuck with it in the testing phase, without whom it would not have even been possible. Credits below.
To see how we got here and before asking any questions click this link: https://forum.xda-developers.com/galaxy-j7/help/root-sm-j727p-galaxy-j7-perx-galaxy-j7-t3598117
DISCLAIMER: YOU FLASH THESE AT YOUR OWN RISK. THE KNOX COUNTER WILL BE TRIPPED AND WILL POTENTIALLY VOID YOUR WARANTY. HAVING THE STOCK FIRMWARE TO HAND IS ALSO ADVISED
NOTE: BEFORE MAKING MODIFICATIONS, ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Instructions:
◘ 1. Download the files below:
J727P-SuperSU-v2.79-SR3_rooted_boot_AQB9
ODIN 3.12
SAMSUNG_USB_Driver_for_Mobile_Phones
◘ 2. Install the USB driver and ODIN to Windows.
◘ 3. Boot your device to RECOVERY mode then select FACTORY RESET. THIS WILL WIPE YOUR DEVICE AND YOU WILL LOSE ALL DATA. (This procedure is required to remove encryption or your device won't boot)
◘ 4. From RECOVERY, IMMEDIATELY Boot your device to DOWNLOAD mode then connect your USB cable. (DO NOT LET YOUR DEVICE REBOOT NORMALLY OR YOUR DEVICE WILL RE-ENCRYPT)
◘ 5. Run ODIN and place the J727P_SuperSU-v2.79-SR3_rooted_boot_AQB9.tar file as is in the AP slot. Don't change any options and hit START.
◘ 6. Wait for the device to flash and reboot.
◘ 7. Install the SuperSU apk from Play store and you should be rooted.
◘ 8. Have fun!
Credits: ME, @Borams @Project89Odin @Chainfire and special thanks to @RS.85243
PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.
IF YOU APPRECIATE WHAT I DO AND WISH TO DONATE ME A COFFEE/BEER THEN CLICK HERE OR HIT THE THANKS BUTTON IF I HELPED YOU
I got the encryption error on reboot. I then did the reset it required and rebooted. I installed supersu just to see what it would say. It says root not properly installed in root checker, so I guess that means its there but I guess its a binary issue? Is there something that I didnt do correctly or a step I missed?
scbcskin said:
I got the encryption error on reboot. I then did the reset it required and rebooted. I installed supersu just to see what it would say. It says root not properly installed in root checker, so I guess that means its there but I guess its a binary issue? Is there something that I didnt do correctly or a step I missed?
Click to expand...
Click to collapse
Whoops glad you pointed that out, forgot to include that step!
I factory reset, booted directly to download mode, flashed tar, phone rebooted. I installed Supersu but still not rooted.
scbcskin said:
I factory reset, booted directly to download mode, flashed tar, phone rebooted. I installed Supersu but still not rooted.
Click to expand...
Click to collapse
When you open the SuperSU app does it complain about no binary installed?
ashyx said:
When you open the SuperSU app does it complain about no binary installed?
Click to expand...
Click to collapse
It sure does!!
scbcskin said:
It sure does!!
Click to expand...
Click to collapse
Strange, it works perfectly on Marshmallow. Looks like we're going back to the old method of manually pushing su.img to data!
Will update shortly.
Have you tried rebooting again to see if works after that?
Just did a reboot and same deal.
scbcskin said:
Just did a reboot and same deal.
Click to expand...
Click to collapse
I think I've just found the issue. Try this version instead, no need to format, just install with ODIN.
https://www.androidfilehost.com/?fid=961840155545567256
.
If you grant root permission before opening supersu apk but after downloading it, it does not ask to update binary with first op build
Project89Odin said:
If you grant root permission before opening supersu apk but after downloading it, it does not ask to update binary with first op build
Click to expand...
Click to collapse
Say again. Can you explain in more details, not sure I understand?
After process in op, after downloading supersu do not open it, download something that requires root and grant it. It will grant without ever opening supersu. I granted flashfire and flashed sr3 just to make sure. After reboot i opened the supersu app and it asks for no update. Although disabling knox did not work for me.
Project89Odin said:
After process in op, after downloading supersu do not open it, download something that requires root and grant it. It will grant without ever opening supersu. I granted flashfire and flashed sr3 just to make sure. After reboot i opened the supersu app and it asks for no update. Although disabling knox did not work for me.
Click to expand...
Click to collapse
OK I see. Can you do me a favour and test the updated version?
First delete su.img from /data or just unroot from SuperSU settings then reboot to download mode and install the new version. Your device should auto re-root.
https://www.androidfilehost.com/?fid=961840155545567256
ashyx said:
I think I've just found the issue. Try this version instead, no need to format, just install with ODIN.
https://www.androidfilehost.com/?fid=961840155545567256
.
Click to expand...
Click to collapse
Root has been achieved my friend. At first a flashed it and when it booted I got the encryption error. I just pulled the battery and then tried to boot into recovery. Instead of going in recovery it booted like normal. I installed Supersu and it got stuck attempting to disable Knox. Well after about 2 minutes or so of watching that I just went to root checker and there it was. I think I can speak for everyone when I say job well done!!!:good:
---------- Post added at 01:09 AM ---------- Previous post was at 01:00 AM ----------
Quick question, must you have custom recovery in order to install Xposed or is it just a suggestion?
After deleting su in /data andfull unroot, flashed newer build and supersu reports no binary, not even one to update, no root
scbcskin said:
Root has been achieved my friend. At first a flashed it and when it booted I got the encryption error. I just pulled the battery and then tried to boot into recovery. Instead of going in recovery it booted like normal. I installed Supersu and it got stuck attempting to disable Knox. Well after about 2 minutes or so of watching that I just went to root checker and there it was. I think I can speak for everyone when I say job well done!!!:good:
---------- Post added at 01:09 AM ---------- Previous post was at 01:00 AM ----------
Quick question, must you have custom recovery in order to install Xposed or is it just a suggestion?
Click to expand...
Click to collapse
Thanks for confirming. OP updated.
You can use Flashfire to install Xposed.
ashyx thank you for your efforts. Thanks to everyone else that helped as well. Guess what I just ordered. Can't wait to get my new phone and root, install viper4android. Both are a must for me and I never own a phone I can't have both on.
scbcskin said:
Just did a reboot and same deal.
Click to expand...
Click to collapse
When the reboot is repeated,
please flash the original firmware to odin
and try again from the beginning.
from CIAO7
after unrooting, repeating format is required to reroot. Works flawless. Thankyou again. Looking forward to a fully functional twrp now!!
Project89Odin said:
Thankyou again. Looking forward to a fully functional twrp now!!
Click to expand...
Click to collapse
It's next on my hit list. Just need to figure out why the source built kernel doesn't boot.
Now that root is achieved there's more chance of finding out what's going on, so I'll be calling on you guys again at some point for logs.
I did a factory reset of my Le Max 2 when it was freezing up intermittently. After a successful reboot, it got to the stage where it was asking for Internet access to log in to my LeEco account and continue with the process, but all attempts at inputting the password on the Wi-Fi link did not bring up the keyboard. I am now stuck at this point. Can someone please, point me to how I can activate the keyboard, or proffer some alternative solution(s) to my problem? I cannot proceed without the keyboard.
gilbolong said:
I did a factory reset of my Le Max 2 when it was freezing up intermittently. After a successful reboot, it got to the stage where it was asking for Internet access to log in to my LeEco account and continue with the process, but all attempts at inputting the password on the Wi-Fi link did not bring up the keyboard. I am now stuck at this point. Can someone please, point me to how I can activate the keyboard, or proffer some alternative solution(s) to my problem? I cannot proceed without the keyboard.
Click to expand...
Click to collapse
Was your phone rooted? And if so, did you also delete the built in keyboard app?
If you answered yes to both questions, then, that's the root (no pun intended) of your problem. A factory reset just deletes user data, and doesn't recover system apps you had uninstalled before. So if you delete a system app and factory reset your phone, that system app will still be missing. Lots of people have found themselves in the past with no launcher just because of this.
If you can connect to your phone through adb (I think you should be able to do so while on recovery mode) I think that there's a command to install an apk file from adb shell, but I never had to do that. Or you can look for a flashable zip that does the same from TWRP and installs a keyboard.
If this doesn't work, or you can't do it, I guess your only chance is to use Qualcomm recovery mode and get the phone back to a true factory state. There's a thread with tutorials and advice.
jman0 said:
Was your phone rooted? And if so, did you also delete the built in keyboard app?
If you answered yes to both questions, then, that's the root (no pun intended) of your problem. A factory reset just deletes user data, and doesn't recover system apps you had uninstalled before. So if you delete a system app and factory reset your phone, that system app will still be missing. Lots of people have found themselves in the past with no launcher just because of this.
If you can connect to your phone through adb (I think you should be able to do so while on recovery mode) I think that there's a command to install an apk file from adb shell, but I never had to do that. Or you can look for a flashable zip that does the same from TWRP and installs a keyboard.
If this doesn't work, or you can't do it, I guess your only chance is to use Qualcomm recovery mode and get the phone back to a true factory state. There's a thread with tutorials and advice.
Click to expand...
Click to collapse
Can't you just flash the ROM again?
---------- Post added at 01:37 PM ---------- Previous post was at 01:33 PM ----------
Or just flash slim7 and then gapps coz inside gapps got keyboard.
jman0 said:
Was your phone rooted? And if so, did you also delete the built in keyboard app?
If you answered yes to both questions, then, that's the root (no pun intended) of your problem. A factory reset just deletes user data, and doesn't recover system apps you had uninstalled before. So if you delete a system app and factory reset your phone, that system app will still be missing. Lots of people have found themselves in the past with no launcher just because of this.
If you can connect to your phone through adb (I think you should be able to do so while on recovery mode) I think that there's a command to install an apk file from adb shell, but I never had to do that. Or you can look for a flashable zip that does the same from TWRP and installs a keyboard.
If this doesn't work, or you can't do it, I guess your only chance is to use Qualcomm recovery mode and get the phone back to a true factory state. There's a thread with tutorials and advice.
Click to expand...
Click to collapse
Thanks for your input.
I did not delete any apps, when I factory-reset the phone. It was previously rooted with TWRP, but I had removed root for more than six months now.
Can you kindly point me to the link containing the Qualcomm recovery mode?
kkcheong said:
Can't you just flash the ROM again?
---------- Post added at 01:37 PM ---------- Previous post was at 01:33 PM ----------
Or just flash slim7 and then gapps coz inside gapps got keyboard.
Click to expand...
Click to collapse
Appreciate if you could provide guidance on flashing the ROM at this stage of recovery?
I have connected the phone to the PC, which detected it after updating the drivers. The issue now is that there are no visible partitions. Any suggestions on how to get my Le Max 2 back?
kkcheong said:
Can't you just flash the ROM again?
---------- Post added at 01:37 PM ---------- Previous post was at 01:33 PM ----------
Or just flash slim7 and then gapps coz inside gapps got keyboard.
Click to expand...
Click to collapse
I have connected the phone to the PC, which detected it after updating the drivers. The issue now is that there are no visible partitions. Any suggestions on how to get my Le Max 2 back?
gilbolong said:
I have connected the phone to the PC, which detected it after updating the drivers. The issue now is that there are no visible partitions. Any suggestions on how to get my Le Max 2 back?
Click to expand...
Click to collapse
Make sure bootloader unlocked. Go to Developer option and enable OEM unlock. Google bootloader unlock using PC and follow.
Then after unlock, flash TWRP using your PC.
Boot into TWRP and flash root.
Then download flashify to flash the TWRP again. I do this because the TWRP cannot stick.
Anyway,if you already have TWRP, just flash ROM and then flash gapps inside twrp.
Thanks everyone for the responses and suggestions.
I was able to get the phone back using the procedure outlined by gizmochina.com on how to unbrick the Le Max 2.