This will void your warranty, like all root exploits. Use this at your own risk. Do not take OTAs on rooted devices unless you know what you are doing, as it may cause a bootloop or a soft brick.
RockMyMoto is designed for MotoXs that have recieved the Camera update, patching PwnMyMoto. If you are unsure of your firmware, try PwnMyMoto first.
First step is to install Cydia Impactor, by Saurik. http://www.cydiaimpactor.com/ This is required. You will also need adb installed and working, and be comfortable with the command line. Your phone must be on the same network as your PC.
Figure out the ip address of your phone:
adb shell getprop dhcp.wlan0.ipaddress
Click to expand...
Click to collapse
unzip RockMyMoto-{version}.zip and push the exploit and su to /sdcard/:
adb push su /sdcard/
adb push RockMyMoto.jar /sdcard/
Click to expand...
Click to collapse
Run Impactor and select "# start telnetd as system on port 2222", then hit start.
Once the process is complete, run telnet:
telnet {your phone's ipaddress} 2222
Click to expand...
Click to collapse
Run the exploit through telnet
dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
Click to expand...
Click to collapse
The exploit will tell you to use adb to reboot:
adb reboot
Click to expand...
Click to collapse
Run the exploit through telnet for the second time, it will reboot on it's own:
dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
Click to expand...
Click to collapse
Run the exploit through telnet for the third time, it will not reboot:
dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
Click to expand...
Click to collapse
Wait 0-60 seconds, for su to install, then install SuperSu from the market.
Enjoy!
Known issues:
If you have AP isolation mode enabled in your AP (aka WiFi router) you won't be able to connect to your phone via telnet, disable isolation.
Windows users having trouble see here
I confirm that this does work on the Droid Maxx on the new OTA update !!!
Thanks JCASE Much Appreciated !!!
Thank you!
Looks like I'm going to be at a loss. I never learned how to use adb :/
Sent from my XT1080 using XDA Premium 4 mobile app
This might a dumb question, but why don't we just release a rooted OTA update?
Quick question about this exploit. I know that the issue with the first two earlier methods is that everything is still signature checked, which prevents Custom ROM/Kernel flashing, as well as Custom Recoveries.
Does this exploit bypass the signature check to allow for custom recovery, or not just yet?
PS: Your skills are godlike. A million thanks for your root hacks!
Where's the Rockmymoto download link? Has it been pulled?
Mike
runner1717 said:
Where's the Rockmymoto download link? Has it been pulled?
Mike
Click to expand...
Click to collapse
LoL he made this for the MotoX then after someone tested in on the droid maxx he coppied the post over to here but didnt post the link. Dont worry I used this method on my droid maxx it works. just download RockMyMoto from post 1 right here
http://forum.xda-developers.com/showthread.php?t=2509590
runner1717 said:
Where's the Rockmymoto download link? Has it been pulled?
Mike
Click to expand...
Click to collapse
no, just me forgetting to attach it, seems ppl were using hte one i have in the motox forum. attached and fixed, thanks
I'm not sure why or how I did this but I am rooted with no write protection off I still have stock recovery. Everything went smooth but when I entered dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto for the first time it said I was rooted and to install super user I have tried since to go through the steps but i end up in the same spot
~ $ dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
RockMyMoto 1.0
by Justin Case
PayPal Donations maybe sent to: [email protected]
Special thanks to saurik, you rock!
You are rooted, please install SuperSu. Exiting...
~ $ dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
RockMyMoto 1.0
by Justin Case
PayPal Donations maybe sent to: [email protected]
Special thanks to saurik, you rock!
You are rooted, please install SuperSu. Exiting...
bigv5150 said:
I am rooted with no write protection off
Click to expand...
Click to collapse
youve almost got a triple negitive going on there, so to clarify, you are rooted, with write protection disabled (ie cant make lasting changes to /system) and you still have stock recovery. is that right?
I am getting link failed file exists when attempting to start telnet.
Forget all that, I was using the wrong port, now the process beings to start the telnet process hangs at waiting for completion then goes back to the impactor main menu, the telnet connection is not successful after that.
I am using the latest soak test update, Am I wrong thinking that this method works with that update?
---------- Post added 6th November 2013 at 12:05 AM ---------- Previous post was 5th November 2013 at 11:47 PM ----------
I uh, i'm an idiot, forgot I have multiple subnets at home. Worked like a charm.
TheWhiteChallenger said:
youve almost got a triple negitive going on there, so to clarify, you are rooted, with write protection disabled (ie cant make lasting changes to /system) and you still have stock recovery. is that right?
Click to expand...
Click to collapse
Yup sorry if it was confusing.
Ok I think I figured it out my phone is already rooted even after a factory reset. I used voodoo when I took the update and everything worked but I had no touchless controls so I did a factory reset after installing stock recovery. I must have had the protected su on the phone still and it stayed unless jcase has a work around for this I am stuck until the new fxz comes out. Then I can completely wipe su out and I will be able to start all over. It really is not that big of a deal I can use almost everything with just root even xpsosed setting work. It would appear the exploit does not allow you to run it if you have root it must verify you do and thinks all is well so it never installs the writer protection off and replaces the stock recovery. My stupid mistake for trying to short cut this I should have just did an fxz took the update and used this method.
Aaaaaaaaand back to rooted. JCASE you are the man!!
If anyone has questions on what to do ask away. it was very simple
I've never used adb before in my life. Would you recommend me trying it lol. Meaning would it be easy for a first timer.
Sent from my XT1080 using XDA Premium 4 mobile app
ADB is not difficult. There are tons of tutorials all over the web. I wish I knew more about telnet and the other stuff involved tho
Sent from my XT1080 using Tapatalk
how come there is no more development options in the new ota update?
ceelos218 said:
how come there is no more development options in the new ota update?
Click to expand...
Click to collapse
You need to go into settings and about phone. Scroll to the bottom to build number and tap it like 6-7 times you'll see it countdown and say "now you are a developer". This enables developer options
Sent from my XT1080 using Tapatalk
Franzie3 said:
You need to go into settings and about phone. Scroll to the bottom to build number and tap it like 6-7 times you'll see it countdown and say "now you are a developer". This enables developer options
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
ohh man thank you.. i was about to give up and just wait for kitkat. im off to try this rockmymoto again... so frustrating for my noobiness,
ceelos218 said:
ohh man thank you.. i was about to give up and just wait for kitkat. im off to try this rockmymoto again... so frustrating for my noobiness,
Click to expand...
Click to collapse
No problem. The rest should be cake if you have adb and have used it before. Let me know if you have trouble
Sent from my XT1080 using Tapatalk
Related
Hey guys. Just worked with joeykrim to get root on the fascinate, he has updated his guide here: http://forum.sdx-developers.com/epic-development/adb-root-exploit-test/
Works great for me, let me know what yall think and donate to him / thank him!
Nice. I won't get my phone for a couple of weeks. Hoping there is a one click method out by then.
I did mine just using the rage.bin and I restarted and checked it twice and mine is persistent without doing all those steps.
Dirrk said:
I did mine just using the rage.bin and I restarted and checked it twice and mine is persistent without doing all those steps.
Click to expand...
Click to collapse
that shouldnt be right, you didnt copy the playlogo or anything? rage is a temporary root exploit that allows us to modify /system
Correct. I have 2 at home that are still in the box. After I get out of class tonight I will try it on those to verify.
fallingup said:
that shouldnt be right, you didnt copy the playlogo or anything? rage is a temporary root exploit that allows us to modify /system
Click to expand...
Click to collapse
I've confirmed the rage.bin exploit combo'd with installing the buysbox/su binaries gives you perm root.
I've rebooted the device and the adb service a few times, and I just grab a shell, su, and I"m seeing #.
I assume this is why busybox is there in the first place, to provide a consistent exploitable binary?
Error Code: 160.
Error Reason: MID Not Allowed.
Wish I had been active enough here to post in development. But ****. Ideas?
You don't need to be able to post in order to read. Just read the stickies in the development section.
joeshmoetogo said:
Error Code: 160.
Error Reason: MID Not Allowed.
Wish I had been active enough here to post in development. But ****. Ideas?
Click to expand...
Click to collapse
Try new automated script and if it fails do factory reset and try again, also follow all instructions it will give you
jose51197 said:
Try new automated script and if it fails do factory reset and try again, also follow all instructions it will give you
Click to expand...
Click to collapse
This was my fourth factory reset with automated script. This time I registered at HTCdev with a different e-mail address and it took my device identifier token. Go figure.
Thanks for all your work and support.
The script didn't seem to get the right code for me. So I just opened another command prompt to get my unlock code manually. Other than that, the whole thing worked perfectly for me. Thanks jose and CaptainRewind.
I have been unable to get past the step where I have to type in:
Code:
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done"
I've tried it on Windows XP 32-bit and Windows 7 64-bit and the error doesn't seem to come to an end. The error specifically reads:
link failed No such file or directory
I've tried it with both the automated script and doing it manually on both. I get the device to show up with adb devices, get the restore prompt on the device, but can't seem to go any further. I keep reading the topic and dissecting the automated script trying to find out what I'm not doing, and can't seem to figure it out.
Hesacon said:
I have been unable to get past the step where I have to type in:
Code:
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done"
I've tried it on Windows XP 32-bit and Windows 7 64-bit and the error doesn't seem to come to an end. The error specifically reads:
link failed No such file or directory
I've tried it with both the automated script and doing it manually on both. I get the device to show up with adb devices, get the restore prompt on the device, but can't seem to go any further. I keep reading the topic and dissecting the automated script trying to find out what I'm not doing, and can't seem to figure it out.
Click to expand...
Click to collapse
I had the same problem until I realized I had to wait until after this step to accept the restore on my phone.
ceayuso said:
I had the same problem until I realized I had to wait until after this step to accept the restore on my phone.
Click to expand...
Click to collapse
That's just it, this step doesn't seem to end. On both computers I've tried, it goes on for a long time. If I don't give it up, it seems to keep going.
Hesacon said:
That's just it, this step doesn't seem to end. On both computers I've tried, it goes on for a long time. If I don't give it up, it seems to keep going.
Click to expand...
Click to collapse
So when you do this step on your computer, you then go to your phone and accept the restore?
ceayuso said:
So when you do this step on your computer, you then go to your phone and accept the restore?
Click to expand...
Click to collapse
I've accepted the restore while it was looping before, this is what I see with cmd. I've let it go a good 20 minutes now. When I try to restore while it's looping, after reboot with or without adb, I'm still a normal user.
Factory reset your phone. I got the same thing...until I reset mine.
Hesacon said:
I've accepted the restore while it was looping before, this is what I see with cmd. I've let it go a good 20 minutes now. When I try to restore while it's looping, after reboot with or without adb, I'm still a normal user.
Click to expand...
Click to collapse
mine did that too, then i did a second factory reset and made sure the password (restore) was disabled in development section, then ran jose's script and bingo, she worked.
i should say Jose's-Capt Rewind and mdmower's
jose's script seems to have worked, not sure why it wasn't before or why it wasn't manually working, but I've got an unlocked bootloader and I'm rooted! It says s-on on the bootloader still, but superuser and titanium backup seem to be working appropriately.
Thanks guys!
hesacon said:
jose's script seems to have worked, not sure why it wasn't before or why it wasn't manually working, but i've got an unlocked bootloader and i'm rooted! It says s-on on the bootloader still, but superuser and titanium backup seem to be working appropriately.
Thanks guys!
Click to expand...
Click to collapse
glad Your on the go, yipee
Hesacon said:
jose's script seems to have worked, not sure why it wasn't before or why it wasn't manually working, but I've got an unlocked bootloader and I'm rooted! It says s-on on the bootloader still, but superuser and titanium backup seem to be working appropriately.
Thanks guys!
Click to expand...
Click to collapse
I haven't been monitoring this thread subforum until now, but looks like the automated script seems to have helped.
Getting the temproot was all about timing. On the day we found this, it was tough getting the timing just right. The script really helped with that.
Now that you're rooted, the hardest part is over.
Sent from my ADR6410LVW using xda app-developers app
Problems With Automatic Script
CaptainRewind said:
I haven't been monitoring this thread subforum until now, but looks like the automated script seems to have helped.
Getting the temproot was all about timing. On the day we found this, it was tough getting the timing just right. The script really helped with that.
Now that you're rooted, the hardest part is over.
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
I'm having a bit of a problem with the automatic script. I make it a few steps in (accept restore, etc). But then it hangs up at "Waiting for Device" and never advances beyond that. On the phone's screen is the Droid Eye. I've tried it a couple times and haven't made it past that stage. I didn't do a factory reset before starting. Would that make a difference? Sorry to post in an old thread. I've been monitoring the Development threads but don't have enough posts to participate. Thanks.
dodgerinNH said:
I'm having a bit of a problem with the automatic script. I make it a few steps in (accept restore, etc). But then it hangs up at "Waiting for Device" and never advances beyond that. On the phone's screen is the Droid Eye. I've tried it a couple times and haven't made it past that stage. I didn't do a factory reset before starting. Would that make a difference. Sorry to post in an old thread. I've been monitoring the Development threads but don't have enough posts to participate. Thanks.
Click to expand...
Click to collapse
Yes you HAVE to factory reset
Please see this safer/easier/faster method instead of using the one below http://forum.xda-developers.com/showthread.php?p=36976137#post36976137
Original guide provided below for historial purposesonly, seriously use hte one above:
Please refrain from repackaging, or rehosting my materials, ask prior to deciding to.
If this guide fails, or the auto script (which I will not recommend you use) fails, please do a factory reset before attempting again.
If you appreciate this, please make sure you check out my original article on the AndroidPolice. Without the support of AP, I wouldn't spend nearly as much time doing this. To the bloggers who will chose to link to a forum post, rather than the original post on a better blog, you suck.
http://www.androidpolice.com/2012/11/24/exclusive-how-to-unlock-the-droid-dnas-bootloader/
Donations for new test devices can be made at the paypal link to the left. I reserve the right to send leftover funds to whatever charities I feel like. Generally I choose Boys and Girls club of america, sometimes I choose seasonal charity, or a medical related one.
Known Problems:
Adb server is out of date
Uninstall HTC Sync, Samsung Kies, etc any software that talks to the phone.
If you get stuck, please immediately find someone in our chat that knows what they are doing. It is very easy to brick your phone if you follow these directions incorrectly, or if a problem arises!
Need faster help? or Want to help visit our chat
http://chat.andirc.net:8080/?channels=#droid-dna
Credits:
Original development: jcase
Awesome saver of the day: Sean Beaupre
Crash test dummy: dsb9938 (I bricked his phone making this!)
Artem and all @AndroidPolice for putting up with my nonsense.
Special thanks to Fuses for recommending a better target, and the numerous testers that let me play with their new phones.
Click to expand...
Click to collapse
Warning: This is semi complicated, and is known to ruin phones if done incorrectly. Proceed at your own risk
Needed:
1gb free space on the phone.
Working adb, must support the adb restore feature (ICS and up!)
Downloads:
backup.ab (300mb) mirrors: http://d-h.st/tau - http://depositfiles.com/files/9c61r4lgo - http://www.filefactory.com/file/2va8yp2i1h99/n/backup.ab
DNA_TeamAndIRC mirrors - http://d-h.st/D4r - http://www.putlocker.com/file/F357F205F5235B3D - http://rapidgator.net/file/59342799/DNA_TeamAndIRC.zip.html
Unzip DNA_TeamAndIRC, put runme.sh, CIDGen.apk and backup.ab into the directory where adb is (or anywhere if you have your paths setup right).
Please Check the readme.txt before continuing!
Code:
adb install CIDGen.apk
Run the CIDGen app on your phone, enter the last digit of your IMEI (NOT YOUR MEID) and press generate. Then confirm the generated file exists.
Code:
adb shell ls -l /sdcard/CIDBLOCK.img
If CIDBLOCK.img does not exist, run the app and try again. Do not proceed without generating a CIDBLOCK.img, it is needed to repair the phone and unlock.
Once you have CIDBLOCK.img on your sdcard, open two terminals (command prompts) and continue
In the first terminal/cmd prompt run these commands:
Code:
adb push runme.sh /data/local/tmp/
adb shell chmod 755 /data/local/tmp/runme.sh
adb shell /data/local/tmp/runme.sh
runme.sh will continue to loop and spit out No such file or link failed errors, just leave it running for now.
In the other terminal/cmd prompt run this commands:
Code:
adb restore backup.ab
Then allow the restore on your phone. Once the process is finished, you can go back to the looping terminal and stop it with control + c, or close the terminal
At this point, do not continue unless you are certain you can do this. Past this point, is where people can brick if they do not follow the directions correctly. If you run into a problem, find someone to help you. Do NOT power your phone off or reboot it. Leave it charging and find someone.
Code:
adb shell rm /data/data/com.htc.usage/files/exploit/*
adb shell mv /data/DxDrm /data/DxDrm_org
adb shell mkdir /data/DxDrm
adb shell ln -s /dev/block/mmcblk0p5 /data/DxDrm/DxSecureDB
adb reboot
Once the phone is rebooted, open two terminals and repeat the restore exploit:
In the first one:
Code:
adb shell /data/local/tmp/runme.sh
This process will also loop forever and give out lots of "No such file" or "link failed" errors - again, just leave it running.
In the second terminal, restore the backup again:
Code:
adb restore backup.ab
After the restore is done, we will undo the DxDrm symlink attack and write the new CIDBLOCK.img:
Code:
adb shell mv /data/DxDrm /data/DxDrm_trash
adb shell dd if=/sdcard/CIDBLOCK.img of=/dev/block/mmcblk0p5
If this returns an "out of space error" come to our chat, and find either jcase or beaups. Do not reboot. Do not continue.
Code:
adb reboot
After reboot, you can go to http://HTCDev.com, and unlock through their official process. Choose the "All other supported models" option when selecting your phone.
Cheers!
Is there a one-click for this?
Sorry, I couldn't resist!
Support chat: http://chat.andirc.net:8080/?channels=#droid-dna
D
.
no comment...
btw great job guys!! :good:
dsb9938 said:
Is there a one-click for this?
Sorry, I couldn't resist!
D
.
Click to expand...
Click to collapse
Awesome.....now I just need the actual phone.
UPS HURRY UP!!!
awesome
Awesome work J and D...
Aight D where is the "cubed" lol
gramsey1911 said:
Awesome work J and D...
Aight D where is the "cubed" lol
Click to expand...
Click to collapse
Next week! Sheesh.
D
.
dsb9938 said:
Next week! Sheesh.
D
.
Click to expand...
Click to collapse
I'm feenin ova here for the cubed...lol
dsb9938 said:
Is there a one-click for this?
Sorry, I couldn't resist!
Support chat: http://chat.andirc.net:8080/?channels=#droid-dna
D
.
Click to expand...
Click to collapse
Lol.... I'm going to wait for the one click, can't afford to brick my device while trying to unlock with 2 kids running around lol...
P.s. thank you j case and DSB for the unlock and root
Sent from my HTC6435LVW using xda premium
typeriz said:
Lol.... I'm going to wait for the one click, can't afford to brick my device while trying to unlock with 2 kids running around lol...
P.s. thank you j case and DSB for the unlock and root
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I wouldnt trust a one click, i automated the PITA part already with the CIDGEN app
This is for the new bootloader right. Just wanna make sure.
Sent from my HTC Droid DNA
typeriz said:
Lol.... I'm going to wait for the one click, can't afford to brick my device while trying to unlock with 2 kids running around lol...
P.s. thank you j case and DSB for the unlock and root
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I just did it, and it's really not that hard, took maybe 10 minutes, just copy and paste the commands and you should be good :good:
So I was able to unlock with this method via HTCDev, I installed TWRP and the insecure kernel, but my SuperSU will not work after I flashed the file in recovery. None of my apps can get root access, and I cannot update the superuser binary via SuperSU. What's going on here?
Argumentation said:
I just did it, and it's really not that hard, took maybe 10 minutes, just copy and paste the commands and you should be good :good:
Click to expand...
Click to collapse
I'm going to wait till I put the kids to bed, tonight. Thanks again !!
Sent from my HTC6435LVW using xda premium
---------- Post added at 04:32 PM ---------- Previous post was at 04:29 PM ----------
TheBiles said:
So I was able to unlock with this method via HTCDev, I installed TWRP and the insecure kernel, but my SuperSU will not work after I flashed the file in recovery. None of my apps can get root access, and I cannot update the superuser binary via SuperSU. What's going on here?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=34551547
How unlock and root work on the Droid DNA.
I belive you have to manually update it
Sent from my HTC6435LVW using xda premium
jonah1234 said:
This is for the new bootloader right. Just wanna make sure.
Sent from my HTC Droid DNA
Click to expand...
Click to collapse
Huh, this is for the htc droid dna in general.
TheBiles said:
So I was able to unlock with this method via HTCDev, I installed TWRP and the insecure kernel, but my SuperSU will not work after I flashed the file in recovery. None of my apps can get root access, and I cannot update the superuser binary via SuperSU. What's going on here?
Click to expand...
Click to collapse
Sounds like bad or incorrect su binary
Try Superuser instead of SuperSU
WHERE IS THE IMEI!?
madzozs said:
Try Superuser instead of SuperSU
Click to expand...
Click to collapse
That worked! I'm not sure why SuperSU doesn't work, but oh well!
jonah1234 said:
WHERE IS THE IMEI!?
Click to expand...
Click to collapse
On your box!
Never mind. Figured out the issue. Now it's just hanging at full restore. There's no password right? I selected restore my data and nothing happens.
thebiles said:
that worked! I'm not sure why supersu doesn't work, but oh well!
On your box!
Click to expand...
Click to collapse
found it haha i fail
This guide is for the select few that need to root their Samsung Galaxy S4 via Mac.
This guide only shows how to swap kernels in order for you to run motochopper then swap back to stock kernel.
Please keep in mind this is technical and involves using manual commands for heimdall in terminal.
If you have anything to add or have any questions, don't hesitate to ask.
I have tested this method using Heimdall on my Windows 7 machine.
I do not own a Mac to fully test this.
I am not an expert nor do I portray myself to be one.
I am not responsible to any problems from this method including bricking any devices, loss of data, or other issues that may arise with your device or computer. (Just to cover my behind.)
Things you need:
1. Heimdall
2. prerelease kernel boot.img (MD5: cd49d9c337d624abec5f6f1229e1abf6)
3. stock kernel boot.img (MD5: 3c776b87c2c1390787189e60d311c769)
4. Motochopper Root Exploit Tool
5. Drivers can be installed by installing Kies
First install Heimdall.
And make sure you have the drivers installed.
Make sure you have the prerelease kernel boot.img (MD5: cd49d9c337d624abec5f6f1229e1abf6) in an easy place to find and make sure you keep it seperate from the stock kernel boot.img (MD5: 3c776b87c2c1390787189e60d311c769).
If you have Kies installed, uninstall it.
Then open the heimdall-frontend application that was installed with heimdall.
Use the heimdall-frontend app to detect the device by going to Utilites > Detect.
Next open a terminal type
Code:
sudo heimdall flash --BOOT <full path to prerelease kernel>
Enter your password.
The prerelease kernel will be flashed and your device will reboot.
Go to Settings > More > About phone
and check to make sure your kernel version is 423399.
Then go into Settings > More > About phone > tap "Build number" about 7 times until it unlocks Developer options
Verify in Developer options setting on your device that you have "USB debugging" checked.
Verify in Developer options setting on your device that you have "Verify apps via USB" unchecked.
Verify in Security setting on your device that you have "Unknown sources" checked.
Verify in Security setting on your device that you have "Verify apps" unchecked.
Extract the motochopper.zip file.
Open terminal, navigate to the motochopper folder and type
Code:
sudo chmod +x run.sh
Then type
Code:
sudo ./run.sh
Follow the on screen prompts.
After you are rooted, make sure you update the su binaries.
Otherwise you will lose root later on.
Next boot your phone into download mode in order to put the stock kernel back.
Open the heimdall-frontend application and detect your device once again. (Utilities > Detect)
Next open a terminal and type
Code:
sudo heimdall flash --BOOT <full path to stock kernel>
Then go to Settings > More > About phone
and make sure the stock 562219 kernel is installed.
Credits go to djrbliss, chainsdd, Samsung, creators of Heimdall, and if I missed anybody please let me know and I will add them to it.
Thanks to Doppletronica for confirming the method.
If you found this guide helpful please hit the thanks button
EDIT: If this thread now belongs somewhere else due to its nature, please move it mods.
Also anybody is free to share this guide, just link them to this thread and please give credit where credit is due.
Thanks.
klabit87 said:
Is there anybody willing to test a root method running a Mac?
I may have found a way but I don't have any way to test it myself otherwise I would.
If interested please pm me.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
Click to expand...
Click to collapse
does it have an unroot? i'd be willing to try it out. if so
theidoctor said:
does it have an unroot? i'd be willing to try it out. if so
Click to expand...
Click to collapse
I'm not too sure about an unroot method.
I'm sure if I looked at it hard enough I could come up with something.
Are you looking for an unroot method via Mac?
Sent from my Verizon Galaxy S4 using Tapatalk 2.
klabit87 said:
I'm not too sure about an unroot method.
I'm sure if I looked at it hard enough I could come up with something.
Are you looking for an unroot method via Mac?
Sent from my Verizon Galaxy S4 using Tapatalk 2.
Click to expand...
Click to collapse
yea. i mean, just for testings sake. i dont want to have to go through the whole unroot just to test a root method drama.
i could unroot on my VM and try your root, but what are the possible effects to it going down? does it work with you?
theidoctor said:
yea. i mean, just for testings sake. i dont want to have to go through the whole unroot just to test a root method drama.
i could unroot on my VM and try your root, but what are the possible effects to it going down? does it work with you?
Click to expand...
Click to collapse
Pm sent.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
Update:
I tried making an unroot method.
That completely failed.
So I had to use Odin to get running again.
I did however get a chance to test the root method for Mac users.
It worked with no problems for me.
I may continue working on the unroot method but that depends on my own free time.
If anyone is interested in assisting with it that would be great.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
klabit87 said:
Update:
I tried making an unroot method.
That completely failed.
So I had to use Odin to get running again.
I did however get a chance to test the root method for Mac users.
It worked with no problems for me.
I may continue working on the unroot method but that depends on my own free time.
If anyone is interested in assisting with it that would be great.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
Click to expand...
Click to collapse
pm me instructions and i will try it out tonight. i dont mind being a flashaholic tonight
theidoctor said:
pm me instructions and i will try it out tonight. i dont mind being a flashaholic tonight
Click to expand...
Click to collapse
I will finish my write-up and get it to you as soon as I can.
I'm not around a computer at work so it may be later this evening possibly.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
theidoctor said:
pm me instructions and i will try it out tonight. i dont mind being a flashaholic tonight
Click to expand...
Click to collapse
Pm has been sent. Let me know if you have any questions or concerns.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
You can unroot it the same way you root. Use Heimdall.
DarkMenace said:
You can unroot it the same way you root. Use Heimdall.
Click to expand...
Click to collapse
Thanks. I knew I was making it harder than it was supposed to be.
I was really only interested in the root guide since a good few people were asking about it.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
I was wondering if someone can help me. I keep getting this error message:
patxp:desktop ArmandoOrona$ sudo heimdall detect
Password:
Device detected
patxp:desktop ArmandoOrona$ sudo heimdall flash --BOOT boot.img
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
libusbx: error [darwin_claim_interface] USBInterfaceOpen: another process has device opened for exclusive access
ERROR: Claiming interface failed!
patxp:desktop ArmandoOrona$
I uninstalled kies and android file transfer and restarted mac. Any help would be greatly appreciated.
Has anyone else tested this? Just curious.
anothamexican said:
I was wondering if someone can help me. I keep getting this error message:
Initialising connection...
Detecting device...
Claiming interface...
libusbx: error [darwin_claim_interface] USBInterfaceOpen: another process has device opened for exclusive access
ERROR: Claiming interface failed!
patxp:desktop ArmandoOrona$
I uninstalled kies and android file transfer and restarted mac. Any help would be greatly appreciated.
Click to expand...
Click to collapse
I got this same error. What I did was uninstall kies and then open the heimdall-frontend app that was installed with heimdall, and use it to detect the phone. (In Utilities->Detect) From there I could run the command line part successfully. Worked for me.
Doppletronica said:
I got this same error. What I did was uninstall kies and then open the heimdall-frontend app that was installed with heimdall, and use it to detect the phone. (In Utilities->Detect) From there I could run the command line part successfully. Worked for me.
Click to expand...
Click to collapse
So just to clarify, are you saying the whole process worked for you?
Whereas you successfully rooted your phone?
Sent from my Verizon Galaxy S4 using Tapatalk 2.
klabit87 said:
So just to clarify, are you saying the whole process worked for you?
Whereas you successfully rooted your phone?
Sent from my Verizon Galaxy S4 using Tapatalk 2.
Click to expand...
Click to collapse
Yep. Once I got the kernel to flash okay, The rooting process worked flawlessly.
Doppletronica said:
Yep. Once I got the kernel to flash okay, The rooting process worked flawlessly.
Click to expand...
Click to collapse
Great! Thanks for your confirmation.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
Man.....I wish I saw this yesterday. I spent 2 hours getting my old imac up and running with bootcamp to install windows.....another hour looking for my old XP disc to actually install it on the iMac, another half hour to install XP, then a good 45 minutes or so trying and failing to gett all the samsung drivers to wok (too several installs and unistalls til it finally worked). After all that, I downloaded the all in one root kit and install recovery as well.
Doppletronica said:
I got this same error. What I did was uninstall kies and then open the heimdall-frontend app that was installed with heimdall, and use it to detect the phone. (In Utilities->Detect) From there I could run the command line part successfully. Worked for me.
Click to expand...
Click to collapse
I got heimdall frontend to detect the device, where do I type in the commands? Under which tab?
anothamexican said:
I got heimdall frontend to detect the device, where do I type in the commands? Under which tab?
Click to expand...
Click to collapse
The guide has been updated.
You need to continue the process in terminal.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
Has anyone successfully gotten to TWRP Recovery to install for their Omate?
I have tried to do it using GooManager, but it says it cant find it.
I have also attempted to do the alternate methods but cant find a scatter file for it ?
Is there any tutorial on this that has worked for anyone?
fibroman said:
Has anyone successfully gotten to TWRP Recovery to install for their Omate?
I have tried to do it using GooManager, but it says it cant find it.
I have also attempted to do the alternate methods but cant find a scatter file for it ?
Is there any tutorial on this that has worked for anyone?
Click to expand...
Click to collapse
I installed TWRP on my TrueSmart this morning via adb while booted to Android. Rename the file that you download to twrp.img and then do the following:
adb push twrp.img /sdcard/twrp.img
adb shell dd if=/sdcard/twrp.img of=/dev/recovery
Done.
Dees_Troy said:
I installed TWRP on my TrueSmart this morning via adb while booted to Android. Rename the file that you download to twrp.img and then do the following:
adb push twrp.img /sdcard/twrp.img
adb shell dd if=/sdcard/twrp.img of=/dev/recovery
Done.
Click to expand...
Click to collapse
Thanks for the info. I now have it installed.
But when trying to do a backup it says( Failed )
Updating Partition details...
Kernel does not have support for running this application.
I was having the same issue. Did exactly what Dees_Troy suggested and it worked like a charm.
Thanks!
Now to wait for roms, because the stock one blows so far.
mortis2600 said:
I was having the same issue. Did exactly what Dees_Troy suggested and it worked like a charm.
Thanks!
Now to wait for roms, because the stock one blows so far.
Click to expand...
Click to collapse
Ouch!!! I can always take Operative and instead of a 100MB file make it +600MB file and call it a "ROM" if it will help.
fibroman said:
Thanks for the info. I now have it installed.
But when trying to do a backup it says( Failed )
Updating Partition details...
Kernel does not have support for running this application.
Click to expand...
Click to collapse
Try running the backup again. If you get an error, adb pull /tmp/recovery.log without rebooting and attach or paste the log to a paste site.
Lokifish Marz said:
Ouch!!! I can always take Operative and instead of a 100MB file make it +600MB file and call it a "ROM" if it will help.
Click to expand...
Click to collapse
Sorry, I have a fairly high standard of roms at this point.
Dont want to go too far off topic, but I've had some issues with bluetooth (pairs, doesn't stay connected, thus making the companion app useless), battery life, etc.
I may have to run tasker scripts to emulate some of the things I want it to do with notifications and turning the screen on. Finally, if I install a new launcher, it'd be wonderful if it didn't cover up the notifications bar.
mortis2600 said:
Sorry, I have a fairly high standard of roms at this point.
Dont want to go too far off topic, but I've had some issues with bluetooth (pairs, doesn't stay connected, thus making the companion app useless), battery life, etc.
I may have to run tasker scripts to emulate some of the things I want it to do with notifications and turning the screen on. Finally, if I install a new launcher, it'd be wonderful if it didn't cover up the notifications bar.
Click to expand...
Click to collapse
I quit anyways so no biggie
mortis2600 said:
Sorry, I have a fairly high standard of roms at this point.
Click to expand...
Click to collapse
Then.... build.... your.... own?
Be a part of the solution.
Sent from my Galaxy Nexus using Tapatalk 2
Lokifish Marz said:
I quit anyways so no biggie
Click to expand...
Click to collapse
Did you build the stock rom? If so, I meant no offense.
mortis2600 said:
Did you build the stock rom? If so, I meant no offense.
Click to expand...
Click to collapse
It was built from broken, crappy Umeox firmware so better battery life, memory management and pretty much every fix or improvement came form me. Like I said I'm done so no offense taken.
Lokifish Marz said:
It was built from broken, crappy Umeox firmware so better battery life, memory management and pretty much every fix or improvement came form me. Like I said I'm done so no offense taken.
Click to expand...
Click to collapse
I don't have yours installed. Mine is just running completely stock firmware right now.
And it sucks that you're quitting. Your build looked to be the one thing that might make the OS on this thing worth using.
---------- Post added at 08:09 PM ---------- Previous post was at 07:42 PM ----------
kuronosan said:
Then.... build.... your.... own?
Be a part of the solution.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
If I had the expertise to do so, I would be inclined to do so. Sadly, I'll just have to settle for reporting bugs and making feature requests and being happy to have my device at all.
[SOLVED] backup failed on TWRP
fibroman said:
Thanks for the info. I now have it installed.
But when trying to do a backup it says( Failed )
Updating Partition details...
Kernel does not have support for running this application.
Click to expand...
Click to collapse
If you are getting 'Unable to create folder' error, then rename the backup name and it should work :good:
nbarm2 said:
If you are getting 'Unable to create folder' error, then rename the backup name and it should work :good:
Click to expand...
Click to collapse
That did the trick!!! Renaming the backup. Thanks.
One final question here: I have been using apps like goomanager to reboot into recovery, but how can you enter TWRP straight from turning the watch on.
Is there a key combo that needs to be held when turning the watch on to get right into TWRP? I tried holding down the bottom right key and that did not work.
Hold both keys for 10 seconds then toggle to recovery
Sent from my Galaxy Nexus using Tapatalk 2
kuronosan said:
Hold both keys for 10 seconds then toggle to recovery
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
This, but your battery pretty much has to be fully charged or else it will just flash the Omate logo on the screen for a couple seconds and then shut off.