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
Related
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
Welcome to Twrp 3.0.0.0 for our Zenwatch 2's
This release I was able to flash the recovery, flash the supersu zip, and flash some others, so far I have not encountered our wild soft brick madness.
Thanks to @acbka for showing me how to get into log files, essentially helping me figure out why the partitions were not mounting correctly when I compiled and recompiled.
Here is TWRP 3.0.0.0
Directions:
Get into fastboot, either by enabling adb by enabling developer options going into settings, about, and taping the Build number 8 times, and going back, down to developer options and enable ADB Debugging.
Then you can type into your CMD or terminal adb reboot-bootloader or by powering down by holding the button or power down in settings, when the screen goes black, repress and hold the button and swipe the screen from the upper left down to the lower right and that should bring up the ASUS logo with CSC Fastboot Mode! on the screen
continue to boot the recovery by typing fastboot flash recovery twrp3.img
OR load up your tethered twrp and flash the image under that.
Hope you guys enjoy! So far I have not encountered soft bricks so it should be safe and sound
thank you, will test now
---------- Post added at 09:21 PM ---------- Previous post was at 09:01 PM ----------
Works perfectly, my zenwatch 2 is now rooted
thank you, you`re amazing
Thank you very much! I hope this will be one of the first steps into advanced development for our watches! Does this work for WI502Q? But what's a benefit of rooting this watch?
okaay3D said:
Thank you very much! I hope this will be one of the first steps into advanced development for our watches! Does this work for WI502Q? But what's a benefit of rooting this watch?
Click to expand...
Click to collapse
That im not sure, it might, wouldnt hurt to fastboot boot it and see if itll start twrp. I have the 501
Root will go with modifying the Momentum kernel so you wont have much lag on the watch, and any other root modifications that can go with it, like maybe xposed?
Next step in development is fixing twrp so it can be flashed, then maybe modifying the wear os? Or maybe porting some stuff
T10NAZ said:
As far as I understand people are able to get backups of their watch in order to preserve OTA's before rooting
Click to expand...
Click to collapse
I want to test it. But how do I backup my watch and restore it to get updates? And is there something like a KNOX-counter to tell whether the device was modified?
matze19999 said:
Works perfectly, my zenwatch 2 is now rooted
thank you, you`re amazing
Click to expand...
Click to collapse
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Awesome! Got supersu flashed and was able to use Advanced Settings to disable some of the built-in bloatware apps. I'll have to try out the kernel but I'm currently at work and don't want to spend all day messing around with my watch (well... I want to, but I like not getting fired).
4RK4N said:
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Click to expand...
Click to collapse
I do have the 5.0.1 wear downloaded and installed! And as far as i know, Its working ok
okaay3D said:
I want to test it. But how do I backup my watch and restore it to get updates? And is there something like a KNOX-counter to tell whether the device was modified?
Click to expand...
Click to collapse
You can tell twrp to preserve the system protection, back every single thing up that you can in the twrp option, push that backup to your computer, and then you can disable system protection. twrp itself wont do anything, however playing with options will modify the watch.
OR you can fastboot pull things off the watch, the system.img and boot.img yourself, in case the ones uploaded in my general thread didnt have the protection enabled.
If you want to hang tight until 1.4 comes out, that can be a good thing too
And im not sure if there is something like that on the watch. I have not seen anything about it before
My attempt was a failure on my WI502Q. I got the following messages. And, OP, how do you pull system.img from a device through fastboot? I thought you needed root permission to do that through adb.
"
C:\adb\zw2>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.381s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.834s
"
Thanks for this! I was losing hope on any development for this watch but now we have the most crucial component to modifying anything on android, a custom recovery. Going to perform a backup, root and flash your custom kernel you kindly released as well!
T10NAZ said:
Hello everyone, I have been working hard last night to make twrp run on our watches, and this I think is a good representation on what itll be like with actual development going on
As far as I understand people are able to get backups of their watch in order to preserve OTA's before rooting, and I was able to flash some zips and kernels successfully, and I fixed the UI to look better and actually usable on the watch
Also, I was able to flash this puppy, and I got android wear to boot with it flashed, however most of the time, it goes haywire and only boots into recovery. Same thing applies, this shall be a Tethered recovery only until I know why its going crazy.
As always, problems can arise on your watch, so be careful!
read the entire instructions, This is a known way to get system protection off, and to flash zips/kernels when need be. Do not flash please.
Here is the link to the updated twrp
Get into fastboot, either by enabling adb by enabling developer options going into settings, about, and taping the Build number 8 times, and going back, down to developer options and enable ADB Debugging.
Then you can type into your CMD or terminal adb reboot-bootloader or by powering down by holding the button or power down in settings, when the screen goes black, repress and hold the button and swipe the screen from the upper left down to the lower right and that should bring up the ASUS logo with CSC Fastboot Mode! on the screen
continue to boot the recovery by typing fastboot boot recovery.img like the other one.
I also have a kernel underway if people would like to try it out and test it in the next couple days
Click to expand...
Click to collapse
What are the Advantages of installing TWRP in Zenwatch 2 WI501Q..???
does it allow to uninstall stock apps..!!
yash92duster said:
What are the Advantages of installing TWRP in Zenwatch 2 WI501Q..???
does it allow to uninstall stock apps..!!
Click to expand...
Click to collapse
it could lead to that, yea, since this is the only root method basically, it adds a few extra steps to do it
can we root with regular supersu .zip, or do we need a special build for wear devices?
slothdabski said:
can we root with regular supersu .zip, or do we need a special build for wear devices?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view?usp=sharing there ya go. dunno if the regular supersu works. havent tried that out. this one does. and alrdy has a busybox installer wear app included which u need anyway sooner or later.
there is no supersu manager app in it though like on phones. apps requiring root just have it. tested advanced settings so far for disabling built-in stuff and a reboot option. but maybe there is a supersu-wear.apk somewhere?
not my link. taken from here: http://forum.xda-developers.com/showpost.php?p=65759835&postcount=14 he took it from the G watch R forums iirc.
zenwatch2
hi dear freind
after the flash twrp recovery
after the wipe
my watch was brick and hang on asus logo
help me plase
mehdi.ahmadi said:
hi dear freind
after the flash twrp recovery
after the wipe
my watch was brick and hang on asus logo
help me plase
Click to expand...
Click to collapse
Let me know the steps you took from when you downloaded it, to when it sits on the asus logo, and do you have the 502 or the 501 watch?
mehdi.ahmadi said:
after the flash twrp recovery
Click to expand...
Click to collapse
guess that means he flashed it. now his watch is bricked. not that it hasent been mentioned NOT to flash it just fastboot boot ...
flash the stock images via fastboot or tethered (NOT flashed) twrp and you should get your watch working again.
4RK4N said:
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Click to expand...
Click to collapse
I flashed this zip file
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view
matze19999 said:
I flashed this zip file
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view
Click to expand...
Click to collapse
found it about 2 weeks ago somewhere here on xda and alrdy linked it to several ppl here in the thread.
but thx
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.
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.