Related
I felt the need to create a thread explaining things a bit better. Lets get started shall we!!
1) As most folks know the I605 Galaxy Note 2 shipped with a locked bootloader. This means you Can Not flash any custom roms/kernels/ or recoveries until you unlock the bootloader!! Failure to comply will result in a yellow triangle stating "unsupported software detected"!
2) If you flashed custom software on your device without unlocking, please refer to Section 1B of my GUIDE in development section. This will bring your device back up and running in stock condition!!
3) Now you can proceed to Adams latest "Jailbreak" thread for for rooting/unlocking/flashing a custom recovery. Make sure to only use the method that applies to the firmware/bootloader version that was previously on your device.
VRAMC3 - http://forum.xda-developers.com/showthread.php?t=2272066
VRALL4 - http://forum.xda-developers.com/showthread.php?t=2118348
VRALJB- http://forum.xda-developers.com/showthread.php?t=2043636 (Unless you purchased this device within the first month of release, and never accepted a OTA, Do Not use this link).
4) And last of all, folks never accept any OTA's!! There is no reason to!! Now that your device has been rooted, unlocked, and running twrp recovery, you can now download any latest update.zip from the dev section and flash in recovery. The Devs here are always fast at packaging up the OTA into a zip format so we can update via cwm or twrp recovery. There are a couple reasons why I prefer this method,
1. Future OTA updates may relock the device permanently! There is no gurantee a unlock method will be achieved for the next OTA.
2. .Zip roms are normally smaller, so they take less time to download and imo are easier to install.
3. OTA's can sometimes fail and soft brick the device.
So please read through this thread thoroughly and remember research twice, flash once! Hopefully this helps...:good:
**Also Note the VRUEMJ9 4.3 OTA update locked the bootloader and there is no current unlock method**
This was way overdue good work droidstyle
Sent from my SCH-I605 using Tapatalk 2
kintwofan said:
This was way overdue good work droidstyle
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
now if we can just get it stickied!!
Nicely done. Maybe it will help
Sent from my SCH-I605 using Tapatalk 2
bond32 said:
Nicely done. Maybe it will help
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Thx...yea hope so! figured it couldnt hurt anyway.
droidstyle said:
now if we can just get it stickied!!
Click to expand...
Click to collapse
I see no reason why it can't be.
Good job, just be sure to keep up to date with it. :good::highfive:
jayharper08 said:
I see no reason why it can't be.
Good job, just be sure to keep up to date with it. :good::highfive:
Click to expand...
Click to collapse
will do :good:
Nice! Now let's hope people read it.
Sent from my SCH-I605 using Tapatalk 2
Error while using Casual R311b
Noob here. Just got my Note II, on VRALL4
I am trying to unlock using the Adam's instructions to the letter (and viewing the instructional video), but I keep getting
ERROR: Protocol initialisation failed!Your device should be rebooting into Android now.
The phone stays in download mode and never reboots back into Android. I've tried different USB ports, installed the drivers from Samsung Kies (I uninstalled the Kies software after getting the drivers). Tried searching through the instructional thread, but couldn't find any concrete answers. Not sure what to try next.
yeyah said:
Noob here. Just got my Note II, on VRALL4
I am trying to unlock using the Adam's instructions to the letter (and viewing the instructional video), but I keep getting
ERROR: Protocol initialisation failed!Your device should be rebooting into Android now.
The phone stays in download mode and never reboots back into Android. I've tried different USB ports, installed the drivers from Samsung Kies (I uninstalled the Kies software after getting the drivers). Tried searching through the instructional thread, but couldn't find any concrete answers. Not sure what to try next.
Click to expand...
Click to collapse
I haven't followed the new instructions yet, but have you tried manually turning your phone back on to see if it will just pick back up in the process?
Sent from my SCH-I605 using Tapatalk 2
kintwofan said:
I haven't followed the new instructions yet, but have you tried manually turning your phone back on to see if it will just pick back up in the process?
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
The only way to get my phone to boot back into Android is to disconnect the USB cable, pull the battery, and boot it. After removing the USB cable, Casual still shows "DEVICE CONNECTED".
yeyah said:
The only way to get my phone to boot back into Android is to disconnect the USB cable, pull the battery, and boot it. After removing the USB cable, Casual still shows "DEVICE CONNECTED".
Click to expand...
Click to collapse
Thought it might. Did it do Odin for you if not make sure auto reboot is checked before starting.
Sent from my SCH-I605 using Tapatalk 2
kintwofan said:
Thought it might. Did it do Odin for you if not make sure auto reboot is checked before starting.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
No, I don't believe this newest Casual uses Odin. It's just a(n almost) one-click solution. No checkboxes (see initial post in this thread for a link to the thread containing the new Casual).
Is there another way to root/unlock VRALL4? I'd be happy to try out more complex methods, as this doesn't seem to be working.
yeyah said:
No, I don't believe this newest Casual uses Odin. It's just a(n almost) one-click solution. No checkboxes (see initial post in this thread for a link to the thread containing the new Casual).
Is there another way to root/unlock VRALL4? I'd be happy to try out more complex methods, as this doesn't seem to be working.
Click to expand...
Click to collapse
I know where the post is but haven't used it yet. No this is the only way, except maybe an older version of casual. Maybe someone who's used it will be by soon to help.
Sent from my SCH-I605 using Tapatalk 2
yea the one click method seems to be having issues for some...maybe adam can put the other method back up until the kinks are worked out. sorry wish i could be of more help.
stuck on yellow triangle stating firmware problems
Hi all..i recently tried to unlock the bootloader however did not know the file i used was not compatible with the latest OTA. When using ODin the phone fails at the sboot.bin...now i can still get into the ODin menu but thats it. Ive been reading several threads and the only solution Ive seen was that the device would get its data wiped. However I have many sentimental things on the device, would there be a way for me to recover all that data. I thought I had backed all files onto my sd card but not all the files got transferred. Any help or tips would be appreciated thank you
try using root66 from section 1a of my guide it does not wipe data.
droidstyle said:
try using root66 from section 1a of my guide it does not wipe data.
Click to expand...
Click to collapse
Thanks!:good: Will try this method and will post the results....I downloaded the root66 file but ODin is not recognizing the file so I'm not able to load it...
Recovery
RoNStiZz said:
Thanks!:good: Will try this method and will post the results....I downloaded the root66 file but ODin is not recognizing the file so I'm not able to load it...
Click to expand...
Click to collapse
Alright so I realized i needed to extract the file, I did so followed directions and YES my phone is working again. Now I just need to run a recovery and hopefully everything will go back to how it was before i soft bricked my phone
RoNStiZz said:
Alright so I realized i needed to extract the file, I did so followed directions and YES my phone is working again. Now I just need to run a recovery and hopefully everything will go back to how it was before i soft bricked my phone
Click to expand...
Click to collapse
Make sure you unlock first
Sent from my SGH-T889 using Tapatalk 2
I just got my phone. Downloaded the motochopper.zip which is available for the other variants of S4, tried it, and no work.
I pushed 'busybox', 'pwn', and 'su' manually, did the chmod. Then I 'adb shell', and ran ./pwn . This is what you get:
[+] This may take a few minutes.
[-] Failure
Bummer.
blulite said:
I just got my phone. Downloaded the motochopper.zip which is available for the other variants of S4, tried it, and no work.
I pushed 'busybox', 'pwn', and 'su' manually, did the chmod. Then I 'adb shell', and ran ./pwn . This is what you get:
[+] This may take a few minutes.
[-] Failure
Bummer.
Click to expand...
Click to collapse
yes we know.. develper is working on it now.
slackwaresupport said:
yes we know.. develper is working on it now.
Click to expand...
Click to collapse
It's probably not going to. Based on version this kernel very likely contains a root block.
Meaning even if you do get su on it will be ignored.
Did kernel source drop yet?
A kernel built with those flags off (at the bottom of the common defconfig) will allow root.
I can put out an earlier kernel that shouldn't have that block also.
If not Sprint has the defconfigs and we probably can build an equivalent for you guys.
(But I assume both may need that unlocked bootloader to play)
Q: In previous models - If you get a full restore - bootloader, modem, etc. and wipes data - will that take via Odin?
If so I might have a quicker solution to at least get root.
garwynn said:
Q: In previous models - If you get a full restore - bootloader, modem, etc. and wipes data - will that take via Odin?
If so I might have a quicker solution to at least get root.
Click to expand...
Click to collapse
I recently had to do a full restore to my Samsung Galaxy S III using Odin. With the stock ROM. I used Odin to do it. Does that answer your question? There are also rooted (but otherwise stock ROMs) that you can install using Odin on the SGS3.
garwynn said:
It's probably not going to. Based on version this kernel very likely contains a root block.
Meaning even if you do get su on it will be ignored.
Did kernel source drop yet?
A kernel built with those flags off (at the bottom of the common defconfig) will allow root.
I can put out an earlier kernel that shouldn't have that block also.
If not Sprint has the defconfigs and we probably can build an equivalent for you guys.
(But I assume both may need that unlocked bootloader to play)
Q: In previous models - If you get a full restore - bootloader, modem, etc. and wipes data - will that take via Odin?
If so I might have a quicker solution to at least get root.
Click to expand...
Click to collapse
Are you making it up or is this really true? Cause that would suck.
He's correct, here is an explanation.
http://www.androidpolice.com/2013/0...os-galaxy-s4-update-but-this-is-a-good-thing/
Sent from my SCH-I545 using xda app-developers app
Patience, we'll get root access through a pre-rooted stock formware flashable in Odin like we have with prior Samsung devices. Dan Rosenberg
tweeted this morning he had successfuly rooted and booted a custom recovery on a VZW S4.
I posted a kernel on the MDK restore thread that shouldn't have the root block. You'll still need to flash it... which I thought still requires the unlocked bootloader.
Sent from my SPH-L900 using Tapatalk 2
garwynn said:
I posted a kernel on the MDK restore thread that shouldn't have the root block. You'll still need to flash it... which I thought still requires the unlocked bootloader.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=41702577
Sent from my SPH-L720 using Tapatalk 2
sextape said:
http://forum.xda-developers.com/showthread.php?p=41702577
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
Successfully flashed the kernel and rooted my VZW S4 this morning. Thanks for this!:good:
Happy to have been wrong about the bootloader requirement to get rooted. Let the party begin!!!
Sent from my SPH-L900 using Tapatalk 2
Warning: Total Noob here.
Just rooted my VZW S4 following the instructions for the ME7 build on the forums here with no problems. Installed "ROM Manager" via Play store and went thru the steps of flashing CWM. The app reports, under "Recovery Setup" that my current recovery is ClockworkMod 6.0.3.2.
BUT, when I "Reboot into Recovery" ... it always go to the default "Android System Recovery <3e>"
How can I get CWM running instead?
Thanks
You can't install a custom recovery on ME7 yet. It's been well covered here on XDA.
Sent from my SCH-I545 using xda app-developers app
AliceBToklas said:
You can't install a custom recovery on ME7 yet. It's been well covered here on XDA.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Thanks. As someone new to Android and the rooting community, is there an explanation on the whys and hows of CWM (e.g. what is required for it to work, why it requires more than rooted phone, how it should best be used, etc...)?
Just trying to figure out how everything plays together and what I should and shouldn't do.
-wg
wgpubs said:
Thanks. As someone new to Android and the rooting community, is there an explanation on the whys and hows of CWM (e.g. what is required for it to work, why it requires more than rooted phone, how it should best be used, etc...)?
Just trying to figure out how everything plays together and what I should and shouldn't do.
-wg
Click to expand...
Click to collapse
The bootloader on this phone is locked, meaning you will need an exploit to bypass it in order to install a custom recovery. The loki method that was previously working has been patched by the most recent update, eliminating the only publicly known hole to install custom recovery. Without an exploit to bypass or an unlocking method we have no way to install a custom recovery like CWM or TWRP, without these it makes it nigh on impossible to install a custom ROM.
Anyone else please correct me if I am wrong but this was my understanding of the current state of things.
Your 100% correct sir...
Sent from my SCH-I545 using xda premium
I tried to run the root but when putting the commands in the emulator I get file not found. SD card is exfat
Hope someone makes a bootstrap like we had for the old droids.
goherd said:
I tried to run the root but when putting the commands in the emulator I get file not found. SD card is exfat
Click to expand...
Click to collapse
Make sure you are very specific on letters that need to be caps.
For example; when you type cd /mnt/extSdCard......make sure the S and C are caps or it will not work.
First time I did it I put in extSdcard and not extSdCard and I got the file not found error.
That should do the trick.
MikeyFid said:
Make sure you are very specific on letters that need to be caps.
For example; when you type cd /mnt/extSdCard......make sure the S and C are caps or it will not work.
First time I did it I put in extSdcard and not extSdCard and I got the file not found error.
That should do the trick.
Click to expand...
Click to collapse
Im sorry your answer was wrong.
To OP... Custom recovery has not been working on ME7. No exploit has even been found to get a custom bootloader on them. Research can teach a lot if found.
ballsagna said:
Im sorry your answer was wrong.
To OP... Custom recovery has not been working on ME7. No exploit has even been found to get a custom bootloader on them. Research can teach a lot if found.
Click to expand...
Click to collapse
Um, Linux command line is often case sensitive. The question above wasn't about custom recoveries, it was simply referring to rooting ME7 which has long been possible.
Sent from my SCH-I545 using Tapatalk 2
ballsagna said:
Im sorry your answer was wrong.
To OP... Custom recovery has not been working on ME7. No exploit has even been found to get a custom bootloader on them. Research can teach a lot if found.
Click to expand...
Click to collapse
That command line is in fact case sensitive. So you're wrong. The previous post was about using the root exploit method which has been done already, not unlocking the bootloader.
I just purchased the Sprint variant of the HTC One Max and decided to unlock the bootloader to root it. I followed the instructions up to the point where I have to have to run the fastboot command in CMD. The example shows the CMD changing its directory to \Android. When I try to do this, I'm given the error: "The system cannot find the path specified." I tried just doing fastboot command, but came back with "fastboot is not recognized..."
Any help with this would be greatly appreciated.
P.S. Android SDK, Java Runtime, and HTC Sync are all installed and updated.
Thanks in advance!
bb2si said:
I just purchased the Sprint variant of the HTC One Max and decided to unlock the bootloader to root it. I followed the instructions up to the point where I have to have to run the fastboot command in CMD. The example shows the CMD changing its directory to \Android. When I try to do this, I'm given the error: "The system cannot find the path specified." I tried just doing fastboot command, but came back with "fastboot is not recognized..."
Any help with this would be greatly appreciated.
P.S. Android SDK, Java Runtime, and HTC Sync are all installed and updated.
Thanks in advance!
Click to expand...
Click to collapse
You need to run cmd prompt as admin and CD to wherever the platform tools folder is installed (part of the sdk)...
Sent from my Nexus 7 using Tapatalk
dottat said:
You need to run cmd prompt as admin and CD to wherever the platform tools folder is installed (part of the sdk)...
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thank you for the quick reply.
This worked, but when I attempt to run the command for the fastboot I get an error saying "The program can't start because AdbWinApi.dll is missing from your computer."
Was this something that was supposed to be installed from one of the Android SDK installs?
bb2si said:
Thank you for the quick reply.
This worked, but when I attempt to run the command for the fastboot I get an error saying "The program can't start because AdbWinApi.dll is missing from your computer."
Was this something that was supposed to be installed from one of the Android SDK installs?
Click to expand...
Click to collapse
Sounds like part of it didn't install correctly. Rinse and repeat. Maybe something got hosed in your earlier attempts.
Sent from my HTC6600LVW using Tapatalk
dottat said:
Sounds like part of it didn't install correctly. Rinse and repeat. Maybe something got hosed in your earlier attempts.
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
I happened to have found the file in a different folder. Should I just drag and drop it into the adt folder?
bb2si said:
I happened to have found the file in a different folder. Should I just drag and drop it into the adt folder?
Click to expand...
Click to collapse
Which folder and what else was in it ?
Sent from my HTC6600LVW using Tapatalk
dottat said:
Which folder and what else was in it ?
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
It was in the sdk\platform-tools folder.
Does the command line have to be directed to the folder containing the fastboot application file? Inside said platform-tools folder is the fastboot file as well as the ApbWinApi.dll file.
OH! I think I got it! I'll report back with final details...
Keep your fingers crossed!!!
bb2si said:
OH! I think I got it! I'll report back with final details...
Keep your fingers crossed!!!
Click to expand...
Click to collapse
Lol....didn't I say platform tools the first time ? Good luck man...
Btw if you get it working you just learned one of the most important prerequisites for android modding.
Sent from my HTC6600LVW using Tapatalk
dottat said:
Lol....didn't I say platform tools the first time ? Good luck man...
Btw if you get it working you just learned one of the most important prerequisites for android modding.
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
Yep! Unlocked the bootloader successfully! Now, I'm trying to Root and the instructions I'm following are good, but I'm stuck again - It says to run CMD and use the command "adb devices." It comes back with nothing found, yet, according to the instructions my phone's serial number should be listed. I placed the Superuser.zip file in the phone's storage (per requisite) and tried to run the command with the phone on normally and again in the bootloader.
No luck... Suggestions?
Edit: USB Debugging wasn't on... Trying again...
bb2si said:
Yep! Unlocked the bootloader successfully! Now, I'm trying to Root and the instructions I'm following are good, but I'm stuck again - It says to run CMD and use the command "adb devices." It comes back with nothing found, yet, according to the instructions my phone's serial number should be listed. I placed the Superuser.zip file in the phone's storage (per requisite) and tried to run the command with the phone on normally and again in the bootloader.
No luck... Suggestions?
Edit: USB Debugging wasn't on... Trying again...
Click to expand...
Click to collapse
If you are unlocked you can simply download a custom recovery for your phone into your fastboot directory and boot your phone to boot loader (fastboot) mode. Flash your recovery using your appropriate fastboot command. Then boot to your new custom recovery and flash the su.zip you copied to the phone from recovery.
Sent from my Nexus 7 using Tapatalk
dottat said:
If you are unlocked you can simply download a custom recovery for your phone into your fastboot directory and boot your phone to boot loader (fastboot) mode. Flash your recovery using your appropriate fastboot command. Then boot to your new custom recovery and flash the su.zip you copied to the phone from recovery.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Everything went smoothly! I am now rooted and excited to get to work!
Thank you for your time and help!
bb2si said:
Everything went smoothly! I am now rooted and excited to get to work!
Thank you for your time and help!
Click to expand...
Click to collapse
Good deal. You may want to investigate s-off'ing that thing too while you still can. Just make sure you download the right version for your phone and run as admin
http://forum.xda-developers.com/showthread.php?t=2525375
Sent from my Nexus 7 using Tapatalk
dottat said:
Good deal. You may want to investigate s-off'ing that thing too while you still can. Just make sure you download the right version for your phone and run as admin
http://forum.xda-developers.com/showthread.php?t=2525375
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Would that solve my next problem? (I'm such a sputz)
I'm rooted, but I can't uninstall anything with Titanium Backup. The last time this happened on my S3 I was told to install SuperSU and install updated binaries. I did that, but when I reboot and go back into SuoerSU it acymts as if it never happened. Apps I uninstalled are still present, too.
Would S-offing solve this?
Edit: Also, I get an annoying pop-up when I start the phone up that says vDN client has failed. Even before I unlocked and rooted. Any way to stop this?
Sent from my HTC0P3P7 using XDA Premium 4 mobile app
bb2si said:
Would that solve my next problem? (I'm such a sputz)
I'm rooted, but I can't uninstall anything with Titanium Backup. The last time this happened on my S3 I was told to install SuperSU and install updated binaries. I did that, but when I reboot and go back into SuoerSU it acymts as if it never happened. Apps I uninstalled are still present, too.
Would S-offing solve this?
Edit: Also, I get an annoying pop-up when I start the phone up that says vDN client has failed. Even before I unlocked and rooted. Any way to stop this?
Sent from my HTC0P3P7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You need to flash an insecure boot.img to disable system write protection. S-off would allow you to recover your phone using both signed and unsigned ruu. The advantage of that is when you hose your phone and there's not a current ruu for the version your phone is on - s-on user would be screwed because you cannot downgrade. Just one of many reasons.
The fc problem I'm not sure. If you aren't using that app you can disable it in the stock app manager. Same goes for stuff you might normally remove with tibu. Be warned too that future otas will likely fail if system apps are missing.
Sent from my HTC6600LVW using Tapatalk
bb2si said:
Would that solve my next problem? (I'm such a sputz)
I'm rooted, but I can't uninstall anything with Titanium Backup. The last time this happened on my S3 I was told to install SuperSU and install updated binaries. I did that, but when I reboot and go back into SuoerSU it acymts as if it never happened. Apps I uninstalled are still present, too.
Would S-offing solve this?
Edit: Also, I get an annoying pop-up when I start the phone up that says vDN client has failed. Even before I unlocked and rooted. Any way to stop this?
Sent from my HTC0P3P7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i have noticed someelse posting about the vDN client failing.. it your providers bloatware if i remember correctly and i think @dottat has a good suggestion! disabled it
So I somehow lost root privileges... After S-offing, I was asked to update the SU binary through the Superuser app (not SuperSU) and I did so. When the install finished, I went into Titanium Backup and was told I'm not rooted.
Went back into Superuser and it didn't prompt for an update, but SuperSU did. Attempted and failed.
Went into recovery and tried to recover root - no luck.
HALP!
bb2si said:
So I somehow lost root privileges... After S-offing, I was asked to update the SU binary through the Superuser app (not SuperSU) and I did so. When the install finished, I went into Titanium Backup and was told I'm not rooted.
Went back into Superuser and it didn't prompt for an update, but SuperSU did. Attempted and failed.
Went into recovery and tried to recover root - no luck.
HALP!
Click to expand...
Click to collapse
Easy...Download this and flash in recovery
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Make sure you aren't running both supersu and superuser. I prefer supersu
Sent from my Nexus 7 using Tapatalk
Huzzah! Thanks again! Hopefully I can actually freeze/remove system apps without them being brought back after a reboot. Also, in the picture provided, what is that icon in the notification bar just right of the GPS icon? And, is there any way to hide some of the icons?
Sent from my HTC0P3P7 using XDA Premium 4 mobile app
Don't use Superuser by ChainsDD anymore.. Personally I would love to continue to use it but he is basically no longer supporting his Superuser app and binary and hasn't updated it in a very long time. SuperSU by Chainfire is constantly being updated therefore made to work with all current versions of Android.. Quite frankly it's all the same basically anyways I just liked the skull and cross bone look lol... Chainfire is a monster as well and has a ton of root related apps and cool things going on. ChainsDD I guess passed the torch on to Chainfire???
bb2si said:
Huzzah! Thanks again! Hopefully I can actually freeze/remove system apps without them being brought back after a reboot. Also, in the picture provided, what is that icon in the notification bar just right of the GPS icon? And, is there any way to hide some of the icons?
Sent from my HTC0P3P7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
---------- Post added at 07:54 PM ---------- Previous post was at 07:53 PM ----------
Also I have no idea what that icon is next to the GPS icon.. You must be on Sprint, I'm on Verizon and I don't think I've seen that icon before..
Ive been trying to root this thing, and got really close but ruined the /system.
So i found one in the discontinued Twrp thread but that one is rooted. I need to be able to update the watch from what it is at
My goal is to try and bring everyone together to make this a group project.
Edit*
Looks like kingroot can be uninstalled via their exe so i can update the watch.
Could the /system be retrieved by any user?
Maybe you should write a tutorial?
r0tati0n said:
Could the /system be retrieved by any user?
Maybe you should write a tutorial?
Click to expand...
Click to collapse
What im finding is that su is absolutely needed to pull the system partition which kinda sucks a little bit.
Tomorrow I will be working on another solution, which if I can get it to work, can be used to pull whatever off the watch, which in turn, can be used to get a absolutely untouched image. If not ill dump what i have made onto the forum so other people can poke at it in hopes that we can root this thing, and get it going.
Stock system image
https://www.dropbox.com/sh/zinfxtbmo3xkyw6/AAAe-Tsz_xwCS3ygbYrOFNGDa?dl=0
Here bro
T10NAZ said:
What im finding is that su is absolutely needed to pull the system partition which kinda sucks a little bit.
Tomorrow I will be working on another solution, which if I can get it to work, can be used to pull whatever off the watch, which in turn, can be used to get a absolutely untouched image. If not ill dump what i have made onto the forum so other people can poke at it in hopes that we can root this thing, and get it going.
Click to expand...
Click to collapse
Why don't you just do a rooted boot img. Your over working yourself. Unlock the bootloader. Make your boot.img. then inject superuser. Enjoy root.
Sent from my ASUS_Z00A using Xparent BlueTapatalk 2
blazinandroid1 said:
Why don't you just do a rooted boot img. Your over working yourself. Unlock the bootloader. Make your boot.img. then inject superuser. Enjoy root.
Sent from my ASUS_Z00A using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Yes however, I want to be on the latest android wear release.