N7105XXUEMK5 ROOT Tutorial – Galaxy Note 2 LTE GT-N7105 JELLY BEAN 4.3 FIRMWARE
Step by step instructions -
Download CF-Root package on your computer and extract the file.
http://download.chainfire.eu/255/CF...tn7105.zipRoot/CF-Auto-Root-t0lte-gtn7105.zip
Download Latest ODIN Software
Switch off your phone and enter into download mode.
To enter into download mode you need to press Volume down button and Home button simultaneously while turning the phone on.
Hope you have your device’s USB drivers installed on your computer if not install it.
Now open ODIN on your computer and connect your device to computer while your phone is on download mode.
When your device will be connected to your computer, one ID:COM boxes will turn yellow after some time.
Select the files that you have to flash or install on your device from the extracted files in first download.
Now in ODIN, check for Auto Reboot and F. Reset Time options.and for the Re-partition option, check only if you have selected .PIT file above.
Click start in ODIN and the flashing will begin.
This flashing might take some time.As soon as the installation ends your device will restart.
Unplug your device from computer.
Switch it off again after it turns on completely and boots to home screen.
Now you need to enter into recovery mode,to enter into recovery switch on the phone while pressing Volume up,Home and Power buttons together.
Navigate with volume buttons to and select wipe data/factory reset from the recovery menu.
Select reboot system now and wait for device to boot again.
You are done, you rooted your Samsung Galaxy Note 2 LTE GT-N7105 to 4.3 Jelly Bean N7105XXUEMK5 Firmware.
Click to expand...
Click to collapse
Method actually supplied by Chainfire.
https://twitter.com/ChainfireXDA
doesnt remove just puts it to the "uninstalled state". so u can choose to install it, from APP menu. KNOX.. then click install.
Don't seem worthwhile to flash. It doesn't have most of the note3/s4 functions
Sent from my GT-N7105 using Tapatalk 4
if your refering to "air command / snote3 etc" . those are n3 exclusive features. the skynote rom has them ported as addons but its touch and go atm some succeeded ( i myself got everything working, except a few syncing issues)
there will be ports though. no doubt
this wont work because of KNOX anyway. stupid feature.
I think knox can be gotten rid of using titanium backup
No need to post this in the dev section
If you didnt make it dont post it
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
can u please move it to general. sorry
UPDATE.
it does work. i just had to update SuperSU i got a few knox errors but it seems to be rooted. now some apps like readers hub etc. wont load (rooting detected)
addition to the tutorial above:
after you started your device again do the following:
1) update supersu through playstore
2) open supersu and update binary > reboot
and if you don't get popups to ask you for permission as soon as you use an app that needs root, open supersu and in settings set the default behavior from "ask" to "always allow".
this gets rid of the fc's and you can enjoy apps with root permission.
All i did was update SuperSU. it said binaries needed updating. i dont have twrp on this so i just selected normal. it rebooted to stock recovery , did nothing i could see. rebooted. updated gplay again. opened superSU didnt give FC. loaded greenify. WIN
all my apps ask "GRANT" permission.
wanam exposed works. got popup for KNOX again. just used it to bypass popup. still have root
4way reboot sticks
R0B3RTF1SH3R said:
All i did was update SuperSU. it said binaries needed updating. i dont have twrp on this so i just selected normal. it rebooted to stock recovery , did nothing i could see. rebooted. updated gplay again. opened superSU didnt give FC. loaded greenify. WIN
Click to expand...
Click to collapse
also used normal on my device, but it didn't reboot to recovery for me, it simply installed and told me that i needed to reboot.
i do however fail to get popup's asking me for permission.
yeah. i think everytime a new app asks it might trigger. but i have wanam exposed removing them. so all looks great. can customize away now. thats all i wanted. THANKS!
There is a nice rom for the 7100 ditto that could be updated for the 7105. It can be found in the 7100 development section. I think with some encouragement the development team would bring it to the 7105
Sent from my GT-N7105 using xda app-developers app
Yeah, 7105 isn't officially supported in neither Skynote nor Ditto. So i can't really get the N3 features on my phone without risking problems anyway. Thus going with the official 4.3 may be the best thing for the LTE people to do, which is why i'm now waiting for someone to release a stock rom modded to take away the knox bootloader. I still haven't decided what to do. There are some really good roms for 7105 in terms of performance and battery life, but those aren't the reasons for why i bought this phone. It feels like there are no good roms for the 7105 that don't also break the many unique features, like the advanced pen functions and the excellent stock camera app's steady-shot and slow-motion functionality. Those are more important to me than performance and battery life.
R0B3RTF1SH3R said:
All i did was update SuperSU. it said binaries needed updating. i dont have twrp on this so i just selected normal. it rebooted to stock recovery , did nothing i could see. rebooted. updated gplay again. opened superSU didnt give FC. loaded greenify. WIN
all my apps ask "GRANT" permission.
wanam exposed works. got popup for KNOX again. just used it to bypass popup. still have root
4way reboot sticks
Click to expand...
Click to collapse
May i know, with the step in post 1, do we have a stock recovery or CWM recovery?
saints5354 said:
May i know, with the step in post 1, do we have a stock recovery or CWM recovery?
Click to expand...
Click to collapse
i only have stock installed. sorry for delay. sleeping.
but when i updated superSU. i selected NORMAL recovery. then it said it would reboot. took about 10 seconds or more then rebooted into normal recovery. I didnt see it update or install anything automated so was like ?????? rebooted. then got messages from KNOX. then after updating my gapps APPS like. "google services" or the one that updates the gplay app. anyway. then it all seemed to work. noticed greenify asked for permission for root. i granted and it didnt get denied by knox. got a warning when trying to load "wanam exposed". then used wanam to get rid of warnings and stuff. even though i still have root.
after wipe/factory settings when I try to open SuperSU for update its blocked straight away with KNOX, any idea?
makes it 0x1
R0B3RTF1SH3R said:
makes it 0x1
Click to expand...
Click to collapse
Yeah... It does lol. But I cant open SuperSU now as its blocked straight away with KNOX, How can I open it to update and change settings for ALLOW?
Every couple of minutes I get message from knox that SuperSU has stopped.....
I am also facing the same problem... looks like the tutorial don't work...
Sent from my GT-N7105 using Tapatalk
kohmax said:
I am also facing the same problem... looks like the tutorial don't work...
Sent from my GT-N7105 using Tapatalk
Click to expand...
Click to collapse
Well it must work somehow because other guys confirms that it actually works
Sent from my GT-N7105 using XDA Premium 4 mobile app
My supersu fc-ed followed by the warning attached
Sent from my GT-N7105 using Tapatalk
Related
[Q] Can boot into a "black screen" recovery and get ADB feedback but that is it.
Strange issue I have here, well it is to me at least, my fathers SGH-I777 the AT&t model boots fine and works when booted but the play store gives me the "no connection" on both wifi and hspa+ and there are a few apps that do not work and cannot be updated for android 4.3 because of the play store. All that is just a day on android and would be fixable if recovery worked. It had or possibly still has clockworkmod recovery installed on it, no idea of the version unfortunately. The first thing that came to my mind was to just update it, well, it cannot be that easy as the latest version of ROM manager does not work, it crashes on startup. So I decided to try ADB and I will get this back if it is in its black screen version of recovery mode
Code:
C:\1>adb devices
List of devices attached
0123456789ABCDEF recovery
C:\1>
and this if it is booted into android
Code:
C:\1>adb devices
List of devices attached
0123456789ABCDEF device
C:\1>
Kind of a side note but also the main issue, when I try to "reboot to recovery" or hold both volume rockers and the power button till to logo appears all I get is a black screen and if it is dark enough in the room you can see that the backlight is on. So I am assuming a corrupted file somewhere, I just need to get somewhere and so far after 3 hours of searching for a solution today I have not. I don't know where to splice this in so i'll do it here; I am pretty sure this is a result of my father having Cyanogenmod updater update from 10.1 to 10.2 without completely re flashing boot and installing from a "factory reset" device then recovering the data.
List of some other things I have tried:
installing the latest apk of the play store
installing the latest apk of ROM manager
not much else that I can think of at this time, but ask and I will either try it or tell you if I have and try again anyways. Not too urgent but thank you for being here xda .
I just read this "http://forum.xda-developers.com/showthread.php?t=1824419" and it looks like rom manager is not a good idea, still need to find a way to install the recovery though and I have no idea how to get fastboot to work without it.
Maybe this post will help...Post #4000 http://forum.xda-developers.com/showpost.php?p=44984062&postcount=4000
Sent from my SAMSUNG-SGH-I747 using xda premium
Put in normal download mode by pulling battery and hold the volume down button as you plug the micro usb in. Reflash to stock jelly bean 4.1.2 using Odin and root with framaroot 1.42 and use aragon exploit and go from there....
Sent from my SGH-I777 using XDA Premium 4 mobile app
Alright ill try that in a few minutes, just left the house.
Starfrog6 said:
I just read this "http://forum.xda-developers.com/showthread.php?t=1824419" and it looks like rom manager is not a good idea, still need to find a way to install the recovery though and I have no idea how to get fastboot to work without it.
Click to expand...
Click to collapse
Just a couple of points, which may be helpful if you are not very familiar with the SGH-I777. Recovery is built into the kernel, not in a separate partition of it's own, so you can't just install a recovery, you must install a kernel containing a recovery.
Rom manager is said to be OK when you have CM on the phone, but in your case it would probably be best to avoid it until the problem is resolved.
The solution 4-2ndtwin posted sounds correct to me. If it were my phone, I'd try that first before flashing back to stock.
4-2ndtwin said:
Maybe this post will help...Post #4000 http://forum.xda-developers.com/showpost.php?p=44984062&postcount=4000
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Sorry for being so late but this worked and allowed me to boot into recovery. Thank you so much!
I took the OTA MJ7 4.3 update and then tried doing the M1I root technique and soft bricked my phone. I know some have tried that and others have just had issues where their phone won't boot after taking the OTA. I will share the steps I did that fixed my phone!
1. Place the update.zip from this thread (http://forum.xda-developers.com/showthread.php?t=2502591) on an SD card. You may have to put it in another phone or into an SD card reader.
2. Press and hold volume up + home button for a couple of seconds
3. While still holding those buttons press and hold the power key until the phone vibrates, then release the power key only
4. Your phone should boot into Android System Recovery. Go to Apply update from external sd card.
5. Select update.zip and apply it
6. It will reboot your phone, it will still not boot properly. Remove the battery and follow steps 2-3 again.
7. This time, select Wipe data/factory reset.
8. Once complete reboot your phone, it will boot this time!
I'm so excited my S4 works again!! Hope this helps you guys!
antisomnic said:
I took the OTA MJ7 4.3 update and then tried doing the M1I root technique and soft bricked my phone. I know some have tried that and others have just had issues where their phone won't boot after taking the OTA. I will share the steps I did that fixed my phone!
1. Place the update.zip from this thread (http://forum.xda-developers.com/showthread.php?t=2502591) on an SD card. You may have to put it in another phone or into an SD card reader.
2. Press and hold volume up + home button for a couple of seconds
3. While still holding those buttons press and hold the power key until the phone vibrates, then release the power key only
4. Your phone should boot into Android System Recovery. Go to Apply update from external sd card.
5. Select update.zip and apply it
6. It will reboot your phone, it will still not boot properly. Remove the battery and follow steps 2-3 again.
7. This time, select Wipe data/factory reset.
8. Once complete reboot your phone, it will boot this time!
I'm so excited my S4 works again!! Hope this helps you guys!
Click to expand...
Click to collapse
Cool! Glad you are up and running.
The MI1 root method flashed a MI1 ROM, so if you are on MJ7, you create a soft brick by trying to root.
Don't do that!!!!
Right. I figured that out the hard way. At least there is a solution
Sent from my SCH-I545 using xda app-developers app
Were you able to boot into android recovery while soft bricked? I experienced the same issue and booted into recovery (volume up, center button, and power button while power is off) and simply did a factory reset. I was able to keep root and fix whatever had gone wrong.
Nevermind, read wrong.
Can be deleted.
tried this.
instead of recovery i get : firmware upgrade encountered an issue. please select recovery mode in kies
slackwaresupport said:
tried this.
instead of recovery i get : firmware upgrade encountered an issue. please select recovery mode in kies
Click to expand...
Click to collapse
I had this happen too. I had to use ODIN to restore to factory MI1 then did OTA to MJ7.
teinwhite said:
I had this happen too. I had to use ODIN to restore to factory MI1 then did OTA to MJ7.
Click to expand...
Click to collapse
just tried to flash ml1.. failed on system.img.ext4
slackwaresupport said:
just tried to flash ml1.. failed on system.img.ext4
Click to expand...
Click to collapse
Did you take the MJ7 update and then try to go back to Ml1? I thought that is the error you get if you do try to go back.
-Lawless said:
Did you take the MJ7 update and then try to go back to Ml1? I thought that is the error you get if you do try to go back.
Click to expand...
Click to collapse
I was in that boat. Took the OTA and foolishly tried Root de la Vega. Couldn't flash back to MI1 (failed as described) but the new no-wipe MJ7 Odin file saved the day. Good as new (but still unrooted).
http://forum.xda-developers.com/showthread.php?t=2507217
I got root with this post: http://forum.xda-developers.com/showpost.php?p=47187227&postcount=84
As other say, it seems to be bad.
I cleared this post and if you wish, you can check the first line and open the post to see how it goes.
TheJumpingBean said:
You will prolly get banned for this! LOL Either way, it does work. I did it on mine, and all of that is true.
Click to expand...
Click to collapse
Why would i get banned ? Did i do something wrong by sharing the knowledge? I have not taken credit for this and also added the link to the post so it can be verified ;
OK, i removed the link and whoever needs it, can use Google to find it.
Trak-X said:
Why would i get banned ? Did i do something wrong by sharing the knowledge? I have not taken credit for this and also added the link to the post so it can be verified ;
OK, i removed the link and whoever needs it, can use Google to find it.
Click to expand...
Click to collapse
No there were some xda admins or w/e that said the links 2 this root arent allowed on XDA ne more. Not sure why... I used it and it worked perfectly. oh well. Sowwy
Moderator @Naddict posted this one post prior in that thread. Read up and learn about the risk you are exposing yourself to.
Be aware that as of this moment XDA has deemed the Kingo root method and Vroot method are not allowed on XDA. There are concerns with the information which is collected during the root method by the exploit. It is not about a continuous malware which may affect your device but about important information shared about your device, serial numbers etc during the root process which could be huge securities issues. You have all been warned.
Click to expand...
Click to collapse
This post, courtesy of open1your1eyes, provides some detail from the bright guys that keep us rooted and happy.
We finally have some details on these root methods:
https://twitter.com/TeamAndIRC/status/397767301811802112
TLDR: Uses "Romaster" root method
Click to expand...
Click to collapse
I would take their caution to heart if I was in your position.
--OctOS Powered VZW GS4 Dev Edition
Nice to see the wheels turning here guys. Thumbs up
I dont know what to think of this. I did the root the first day, and haven't had any problems. I have talked to a few devs and Android engineers who have checked it out and don't think its a threat. I did manage to update mine to SuperSU from the chinese superuser, just in case...
So, I dont know enough to tell you if it is or isnt dangerous, but I can tell u that Im on like day 5 with no issues. I went ahead the first day and installed DroidWall. DroidWall doesnt have any records of su or the chinese superuser trying to access anything, and netstat doesnt show that the su or superuser apps are listening for connections.
I kinda wish we could get some closure on whats happening...
teinwhite said:
I had this happen too. I had to use ODIN to restore to factory MI1 then did OTA to MJ7.
Click to expand...
Click to collapse
Im go the problem where it says Firmware upgrade encountered an issue. how do i fix this? and can u provide a link for the stock firmwares please the mi1 and mj7.
TheJumpingBean said:
I dont know what to think of this. I did the root the first day, and haven't had any problems. I have talked to a few devs and Android engineers who have checked it out and don't think its a threat. I did manage to update mine to SuperSU from the chinese superuser, just in case...
So, I dont know enough to tell you if it is or isnt dangerous, but I can tell u that Im on like day 5 with no issues. I went ahead the first day and installed DroidWall. DroidWall doesnt have any records of su or the chinese superuser trying to access anything, and netstat doesnt show that the su or superuser apps are listening for connections.
I kinda wish we could get some closure on whats happening...
Click to expand...
Click to collapse
How'd you get supersu to work and remove Chinese superuser?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Hey all, I got a Verizon Galaxy S4 16 gigs. I did the 4.3 OTA, then tried to go back to 4.2.2. I guess that soft bricked it. So do I have to use the MJ7 firmware to make my phone usable again? And if that works, is there any way to go back to 4.2.2? What do I do if it doesn't work?
Update: This worked beautifully, I'm now back to 4.3.
UPDATE 05/28/15 This works fine without doing the xposed part on Lollipop. No speed issues. It may be totally unnecessary now but I am not going to retry it to see. It may once again become necessary to follow these instructions when we get xposed for lollipop.
There are a number of threads about these two topics, I am going to consolidate my findings here.
First off root works great on the Sprint variant, secondly so does Xposed with S-Health and private mode. You just have to be careful how you set them up. There have been a lot of posts about freezing S-health and Private mode then clearing data but from my experience that is hit or miss. There are four basic steps to getting everything working and it should be done from a factory reinstall of software. The files you will need are in the following threads/links
Chainfire Autoroot - http://autoroot.chainfire.eu/
Chainfire File Link - http://download.chainfire.eu/617/CF-Root/CF-Auto-Root/CF-Auto-Root-tbltespr-tbltespr-smn915p.zip
Xposed - http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Xsecure - http://forum.xda-developers.com/xposed/modules/app-xshealth-bypass-secure-storage-t2878708
Teamwin Recovery - http://www.techerrata.com/browse/twrp2/trltespr
Root using Chainfire autoroot for Sprint it will fail just pull the battery and boot to download to install the teamwin recovery (buttons HOME, VOLUME DOWN, AND POWER) boot to recovery then install supersu. Before leaving recovery set the screen timeout off and lower the brightness to 10.
Skip past Google and Samsung setup. You can fill out the first and last name screen (only opportunity to name phone, first boot).
Download and install Xposed (not Wanam) download and install XSecure Health module install Xposed framework reboot
Activate Xsecure Health module reboot
Clear Data for Health Service and S-Health reboot
Run Private mode and set up, run S-Health and setup.
Setup your Google and Samsung accounts
If you do these steps exactly without doing anything else I can promise you will have a rooted Sprint version with Xposed, Shealth, and private mode working. When I say exactly I am serious there are a lot of things that can/will mess you up like
Signing into google or samsung on reboot after installing factory software
Starting private mode before setting up xposed
Shortcutting by doing a factory reset instead of a factory software reinstall
Restoring your data Nandroid backup (Use Titanium etc for a program by program reinstall of apps)
BTW the problem here is a little bit deeper than uninstall xposed everything works. There is a something that is changed in the software with either xposed or wanam that can permanently kill private mode until you do a factory install. At the moment I am doing Nandroids before any change I make in Xposed.
worked like a charm. Thank you very much.
blackinjun said:
Root using Chainfire autoroot for Sprint it will fail just pull the battery and boot to download to install the teamwin recovery
Click to expand...
Click to collapse
Is it absolutely necessary to install the custom recovery to achieve root? I only ask because I prefer to leave the stock recovery
Sent from my SM-N915P using XDA Free mobile app
metal666fukhead said:
Is it absolutely necessary to install the custom recovery to achieve root? I only ask because I prefer to leave the stock recovery
Sent from my SM-N915P using XDA Free mobile app
Click to expand...
Click to collapse
Sorry it is because the SU has to be installed outside of the system. There may be a way to then use TWRP or CWM to reinstall the stock recovery but I have not researched that.
Thanks blackinjun for this, I just got a Sprint variant of the Note Edge. I believe that I'm on NK1, it's been a while since I rooted a device, last one was about 2 years ago on my Galaxy S4. Will try it this weekend.
blackinjun said:
Sorry it is because the SU has to be installed outside of the system. There may be a way to then use TWRP or CWM to reinstall the stock recovery but I have not researched that.
Click to expand...
Click to collapse
@metal i now think it may be better to keep the custom recovery. Ive found that when su says it needs an update it asks to reboot ro twrp or cwm to update. I have twrm and it worked flawlessly.
Sent from my SM-N915P using Tapatalk
@Hired no prob
Sent from my SM-N915P using Tapatalk
worked for me as well just like you said..one problem im seeing though..well not sure if it matters..but while makeing my back of stock system,i see in red letters cant mount cace several times,but it completes the back up,and says sussefull..im backing up to my external sd card..i flashed the super user zip first before back up,flashed latest zip,hope this diddnt matter,did you mean to let twrp install it?..or ok to flash the zip?..anyhow,should i worry about the red letters 'cant mount cacge'??...i dont like it when i see any red letters while in recovery,just looks bad to me,like something is wroung...
blackinjun said:
@metal i now think it may be better to keep the custom recovery. Ive found that when su says it needs an update it asks to reboot ro twrp or cwm to update. I have twrm and it worked flawlessly.
Sent from my SM-N915P using Tapatalk
Click to expand...
Click to collapse
I have a client that I rooted their Note Edge but they really want Stock Recovery. Do you know how to put stock recovery back on there?
what am i doing wrong. i download the tar file for twrp but it won't show up when i open the odin because it is showing up as a .img file. if i just change it to .tar it fails
sand1303 said:
what am i doing wrong. i download the tar file for twrp but it won't show up when i open the odin because it is showing up as a .img file. if i just change it to .tar it fails
Click to expand...
Click to collapse
Download the zip file not the IMG.tar
Is it possible to do this. If my phone is already rooted?
I randomly found a YouTube video they walked me through rooting my phone before I knew shealth would have not work. This was a couple months ago I guess. So I'd like to get it back. Though doing factory reset isn't something that I'd prefer to do. But if it comes to it.
I'd assume just follow the rest of the steps in your tutorial?
sand1303 said:
what am i doing wrong. i download the tar file for twrp but it won't show up when i open the odin because it is showing up as a .img file. if i just change it to .tar it fails
Click to expand...
Click to collapse
You didn't unzip it right? Make sure you download the one with the .tar extension
ya thats what i was doing. i downloaded the .tar and unzipped it. flashing it without unzipping it worked fine
DevXen said:
Is it possible to do this. If my phone is already rooted?
I randomly found a YouTube video they walked me through rooting my phone before I knew shealth would have not work. This was a couple months ago I guess. So I'd like to get it back. Though doing factory reset isn't something that I'd prefer to do. But if it comes to it.
I'd assume just follow the rest of the steps in your tutorial?
Click to expand...
Click to collapse
this trick will work if your already rooted. Clear your D. Cache and cache and start from the download/install xposed portion of the instructions. This is what I ended up doing and haven't had any issues at all.
For those who have moved to lollipop has anyone tried this method
Sent from my SM-N915P using Tapatalk
+1, Would like to know how to root now that I have Lollipop............links, instructions, etc.
Same process as rooting kk i had no probl3ms with s health or private mode
Sent from my SM-N915P
Which method in Post #1 did you use?
Root using chainfire odin twrp ,xposed does not work on lolipop,so no other steps.
Sent from my SM-N915P
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.