It seems as tho there hasnt ever been a sticky made for rooting the Gear 2 Neo, so here ya go(lets hope they make it a sticky).
youre going to need Odin and the tar.md5 file you flash in Odin to get this accomplished. No worries tho, its quite easy to do and the tar linked below works with every version attempted so far, and I've personally flashed all of the versions available on Sammobile.com.
WARNING!!! Do this at your own risk! If you mess it up, its on you, not me!!
download these 2 files
Odin 3.10
Gear 2 Neo tar.md5
the next best thing is to do is to create a folder on your desktop, name it whatever you like, and put those 2 files in it.
next, open Odin by right clicking and open as administrator.
there are some settings that can be changed in Odin, but leave them as they are for this.
click on the "AP" button in Odin and navigate to the folder on your desktop that has the tar.md5 file in it and double click on it to select it.
Go to your gear 2 neo and go to the gear icon. Scroll to the bottom and touch the icon with a lower case "i" in a circle, then check the box that says "USB Debugging"
connect a usb to micro usb cable to your computer and connect the charging dock to the watch, but do not connect the micro usb end of the cable to the cradle.... yet
press and hold the button on the Gear 2 Neo. It will present a menu asking if you want to reboot etc etc, but just keep pressing it. Itll eventually (about 8, or so, seconds later) turn the screen off for a second and then say "rebooting" At this point its critical that you rapidly press the button 5 times. No more, no less. It will then bring you to a screen that gives 4 options. Single press the button to navigate thru the choices and long press to select. The option you want is "Download"
Once the watch is in download mode, connect the micro usb to the cradle. Your computer will likely install some drivers and when its done, the top left box of Odin should show "Com:#" (the pound sign will be a random number of a com port your computer selected)
Next press the start button is Odin.
There will be a dialogue box on the bottom left of Odin that says what its doing and a progress bar that shows on the watch and Odin itself. This process should take around 70 to 90 seconds.
Once complete, the watch should reboot and you should now have root access.
The following posts will be reserved for instructions on how to add custom ringtones. The only supported file type for ringtones and message notifications is .OGG. Ill also include some notif tones im currently using myself because i think theyre HILARIOUS!!!
putting custom ringtones and notification sounds on the neo with stock firmware is done via SDB. Very similar to ADB, you use command prompt to push the tones to specific folders within the file structure of the watches internal storage.
Ok, so to add notification tones, you need to SDB into the filesystem of the watch
fist thing youll need is the SDK itself found here
Follow the install instructions on the page linked above and open a command prompt session, then navigate to the folder that the SDK is located in.
Next, youll need some tones. The notif tones need to be in .ogg format (there are many free tools online available to convert files from mp3 to ogg.) Word of warning here, dont make the notifs too long as the watch has a very limited amnt of space reserved for notif tones, and if you put too much in there, it could corrupt the existing tones. Here are a couple nice-n-short tones of Brak (from Space Ghost) saying woah, hey and dont touch me.
The one i use is Wilford Brimley saying diabeetuhs. (I need to say that diabetes isnt even slightly funny, but the way he says it is)
next thing after either creating your own files or downloading mine is to put them into the same folder that the SDK is located in (its just easier this way) and type the following commands
PHP:
sdb root on
then
PHP:
sdb push YOUR_RINGTONE.ogg /opt/share/settings/Alerts/
(but replace the YOUR_NOTIFICATION.ogg with the actual name of the file you want to inject to your watch)
id also like to stress the importance of not guessing at the commands, as in doing so, you can corrupt the existing tones and theyll not be recoverable on the device. To me, thats ok because the stock ones are lame anyways, but be forewarned
ringtones are basically the same process as above, but you push the files to a different location. Here is the code
PHP:
sdb push YOUR_RINGTONE.ogg /opt/share/settings/Ringtones/
as above, make sure to replace the "YOUR_RINGTONE.ogg" with the actual file name
reserved 3
reserved 4 (just in case i have MOAR fun stuff to add )
Have a question. The stock ringtones and notifications. Can those be removed? I would have asked elsewhere, but i believe you and I are the only ones in this ghost town of a forum. Thanks man.
Sent from my SM-N920P using Tapatalk
Thanks for the tutorial. My Gear 2 Neo was having issues with bluetooth, so I installed this new ROM with root and now it connects again.
fsunoles101 said:
Have a question. The stock ringtones and notifications. Can those be removed? I would have asked elsewhere, but i believe you and I are the only ones in this ghost town of a forum. Thanks man.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
yes you can. the command is something like "sdb rm /opt/share/settings/Ringtones/YOUR_RINGTONE.ogg"
and if that doesnt work try "sdb shell rm /opt/share/settings/Ringtones/YOUR_RINGTONE.ogg"
and to see whats in the folder "sdb LS /opt/share/settings/Ringtones/"
similarly, you might need to add a shell command to LS to see the contents of the folder you seek.
Also also, make sure to "sdb devices" and "SDB root on" before doing any of that stuff with usb debugging checked
youdoofus said:
yes you can. the command is something like "sdb rm /opt/share/settings/Ringtones/YOUR_RINGTONE.ogg"
and to see whats in the folder "sdb LS /opt/share/settings/Ringtones/"
Click to expand...
Click to collapse
Awesome. I will give it a try this evening. Thanks.
Sent from my SM-N920P using Tapatalk
fsunoles101 said:
Awesome. I will give it a try this evening. Thanks.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
not a problem. lemme know if you have any problems with it. ive removed most of my stock ringtones and alerts because i think theyre kinda dumb lol i just have space ghost, wilford brimley and some mario sounds on mine
Novakingwai said:
Thanks for the tutorial. My Gear 2 Neo was having issues with bluetooth, so I installed this new ROM with root and now it connects again.
Click to expand...
Click to collapse
No problem man. This section of the forum is a ghost town! Glad i could help
I know you said it takes 70-90 seconds for the rom to copy over, but mines been sitting here for almost an hour and it only moves a tiny bit every 10-15 minutes.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is it normal?
Not even slightly. Might want to try a different cable, USB port or computer.
Sent from my SM-G900P using XDA Free mobile app
uh oh!
so i found my gear 2 in a drawer the other day and decided to play with it. After flashing this thru odin it doesnt boot up. Everything in Odin showed it was good. How do i fix this now?
Can it even get to download mode?
Also, is it the gear 2 or gear 2 neo? The firmware posted was for the neo only
Yes I can get into download and it is the neo as well.
If you can get to download mode, then its likely a bad download. Try a fresh download and reflash in Odin. If that doesn't work, I'll grab the link from sammobile.com and try the flash from that download link
jwwolfe77 said:
Yes I can get into download and it is the neo as well.
Click to expand...
Click to collapse
Try downloading the firmware from here if the fresh download doesn't work.
http://www.sammobile.com/firmwares/download/46122/R381XXU0BOA2_R381OXA0BOA2_XJP/
If you can get to download mode in Samsung devices, you're not in trouble 99% of the time
youdoofus said:
Try downloading the firmware from here if the fresh download doesn't work.
http://www.sammobile.com/firmwares/download/46122/R381XXU0BOA2_R381OXA0BOA2_XJP/
If you can get to download mode in Samsung devices, you're not in trouble 99% of the time
Click to expand...
Click to collapse
youdoofus said:
If you can get to download mode, then its likely a bad download. Try a fresh download and reflash in Odin. If that doesn't work, I'll grab the link from sammobile.com and try the flash from that download link[/QUOTE
Ok. tried both and still nothing. It kinda does a boot loop a couple times and then the green just stayed black.
---------- Post added at 02:22 AM ---------- Previous post was at 01:50 AM ----------
so just to try, i flashed the android wear and that is working good. Id just rather have the tizenmod 3.0.
---------- Post added at 02:43 AM ---------- Previous post was at 02:22 AM ----------
HAHA!!!! i got it working.....the hard way. I flashed android wear, then the tizenmod full restore file and it worked after that. Everything is good. Thank you for all of your help.
Click to expand...
Click to collapse
Related
I wrote this basic little application to help out those who are either afraid of the command prompt or simply just don't want to deal with it. Drop it in the same folder as adb and run it.
Feel free to leave feedback or contact me with any questions/comments.
http://incredible.groove2.net/IncredibleRooter.zip
If people decide they like this, I will continue development and add some new features to it.
Check out the Readme.txt for more information and detailed explanations.
Thank you, I had rooted mine before using the command prompt, your application save me time on taking off the battery and waiting for reboot. Thanks again.
vVv mDaWg said:
I wrote this basic little application to help out those who are either afraid of the command prompt or simply just don't want to deal with it. Drop it in the same folder as adb and run it.
Feel free to leave feedback or contact me with any questions/comments.
http://incredible.groove2.net/IncredibleRooter.zip
If people decide they like this, I will continue development and add some new features to it.
Check out the Readme.txt for more information and detailed explanations.
Click to expand...
Click to collapse
Thanks for your work, it doesn't go unappreciated =).
Glad to see people are finding it useful. Expect a CityID removal button in the near future.
where exactly do we drop this? what's the path?
As the OP stated, place this program in the same folder as adb, so depending on where your sdk is located it might go in C:\sdk\tools\
what's the adb?
Please bare with me...
Robes1 said:
what's the adb?
Please bare with me...
Click to expand...
Click to collapse
Found it...thanks anyway.
Appreciate it, wish I would have seen before I rooted. I will try this as I need to get back there to remove cityid anyways.
-------------------------------------
Sent via the XDA Tapatalk App
lol.. you know whats sad... is i almost guarantee besides trying 2.2 on this beast.. CityID is #1 on peoples list of crap to remove that is absolutely useless
Nice App.
Thanks!
What does the app do? Will it help get people into the adb shell? That seems to be the real problem.
When will option be avail to remove cityid? that is big reason for me to root.
also please explain more on where to find adb folder?
thanks for this app cant wait to try it.
metalmenance said:
When will option be avail to remove cityid? that is big reason for me to root.
also please explain more on where to find adb folder?
thanks for this app cant wait to try it.
Click to expand...
Click to collapse
Extract it or place it inside the tools folder.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
hmmmm
well I'm stuck. tried several cards tried all the methods and still no go. It goes to the screen with the red triangle and dead ends. and after that it just says cant open cache recovery command guess im screwed oh well thanx for posting all the steps you guys went through effen pisses me off though
Has anyone used this and has it worked. I've tried every method on every site and nothing, I'm going to try this when I get home from work.
Hey guys, sorry if there's been any confusion.
This app will not make ADB start up in recovery. That's still something that we still have to achieve to get any of this to work.
Peronally I used the Kingston 4GB Class 4 card and it works pretty much almost every single time I just do a simple adb reboot.
This application was designed to make the rooting process a quick and painless command prompt-less process after you achieve adb running in recovery mode. I used this on my friend's Incredible and the rooting process took me literally 30 seconds to complete.
vVv mDaWg said:
Hey guys, sorry if there's been any confusion.
This app will not make ADB start up in recovery. That's still something that we still have to achieve to get any of this to work.
Peronally I used the Kingston 4GB Class 4 card and it works pretty much almost every single time I just do a simple adb reboot.
This application was designed to make the rooting process a quick and painless command prompt-less process after you achieve adb running in recovery mode. I used this on my friend's Incredible and the rooting process took me literally 30 seconds to complete.
Click to expand...
Click to collapse
Does the red triangle with the exclaimation point mean it has failed, or do you wait further?
Thanks,
Jim
I used a SanDisk 2GB works everytime.
After your in recovery mode and have clicked the Step 3: button "Check for ADB In Recovery".
If you get the "sorry adb not running" message try this:
Unplug your usb cord from the device and remove your battery.
Replace your battery and hold down the volume- key and press the power button.
Highlight Recovery as soon as possible.
Plug the usb cord back in and press the power button at the same time.
Note: If you hear a noise when you plugged in the usb cord before you see the black Recovery screen you did it wrong.
Click the Step 3: button one to five times.
If it doesn't work try it again or try a different SD card.
Touch thanks for all the help Bro. My incredible is just a stubborn ***** LOL Great job on the windows app
Team,
This One-Click Root process will copy over the rooted-update.zip or unroot-update.zip file then reboot your phone. Follow the instructions in the CMD prompt that launches.
Credits:
LeshaK at Samdroid: for the original rooted-update.zip.
gunnarhafdal : for creating the Mac GUI for my app.
This has been tested on stock Android 2.1 Eclair only. If you rooted using another process you can use this process to unroot as long as you didnt load a rom that created links to busybox.
For the following models:
GT-I9000
Captivate SHG-I897
Vibrant SGH-959
GT-I9000M
Epic SPH-D700 (Untested but should work like other phones. Post with your results. This is harmless it will either work or it wont. It copies over 3 files to your existing build.)
Rooting adds the following to your system and unrooting removes them:
/system/xbin/busybox (version 1.17.1)
/system/xbin/su
/system/app/Superuser.apk (version 2.3.1)
and links /system/bin/su to /system/xbin/su
More will follow as they are released. PM me to add your Galaxy S Model.
Warning: I am not responsible for bricked phones, rooting can void your warranty....
PC Instructions:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download the app: GalaxyS_One-Click_Root_All_Models-PC. Or down Below.
Watch the video for the full procedure on The Unlockr.
Video/Procedure Link Click Here
Requirements: Install Link: Dot Net Framework version 4
Rooting Instructions:
1. Make sure your phone is on USB Debug mode: (MENU > Settings > Applications > Developement > USB debugging = Checked )
2. For Windows x86 and x64 systems make sure that the Samsung Drivers are installed. You can get them here.
3. Extract the contents of GalaxyS_Vibrant_One-Click_Root.rar to a folder.
4. Connect your phone to your PC via the USB cable and launch the file "T-Mobile Vibrant One-Click Root.exe" file.
5. Click the "One-Click Root" button. This will launch a command shell follow the instructions in the CMD window.
Mac Instructions:
Download the app: OneClickRootMac. Or Down Below.
It requires Mac OS X 10.5 or higher.
Rooting Instructions:
1. Make sure your phone is on USB Debug mode: (MENU > Settings > Applications > Developement > USB debugging = Checked )
2. Connect the phone to your computer.
3. Click one of the buttons depending on what you want to do.
4. After the phone has rebooted into recovery select "apply sdcard:update.zip" for I9000 and I9000M and choose "Reinstall Packages" for the US models using the volume keys and then press the home button for I9000 and I9000M and the power button on the right top side for US models to start the process.
=====================================================================
Done! You are rooted.
=====================================================================
Un-Rooting Instructions:
To Un-Root follow the same instructions except click on the Un-root button. If you rooted using another process you can use this process to un-root as long as you didnt load a rom that created links to busybox. I would suggest to restore you phone back to stock ROM before even needing to unroot and if you are on stock un-root all you want otherwise what is the point of un-rooting.
=====================================================================
Getting Started with Android After Rooting:
Flash Clockwork Custom Recovery On your phone:
Follow this URL to find fill information on ROM Manager:
http://forum.xda-developers.com/showthread.php?t=734164
Install ROM Manager from Market.
Launch ROM Manager and click on Backup ROM and save you android O/S stock rooted making getting back to stock un-rooted much easier..
the simplest root just got simpler
So is this actually faster? Or just "easier" not to mess up...
sounds like more work than just DLing, moving, and renaming with your phone... expecially for those without a comp...
anyway, this method has been added to the sticky in dev section..
junkdruggler said:
So is this actually faster? Or just "easier" not to mess up...
sounds like more work than just DLing, moving, and renaming with your phone... expecially for those without a comp...
anyway, this method has been added to the sticky in dev section..
Click to expand...
Click to collapse
I'd say its easier to not mess up. Faster for sure, if you already have the drivers installed.
This is for our newer brethren or anyone else that want a straight forward root method. And for those having trouble entering recovery from the button presses. ADB is bundled in the rar file so you don't need Android SDK.
Another thing that will help most is when I add unroot to the app which I should have completed tomorrow.
Doon2 asked for it, so here it is.
I appreciate the effort and skill...
BUT, how is this easier than downloading a file directly to your phone, renaming it and putting it at the root of your sd card and going to recovery?
s15274n said:
I appreciate the effort and skill...
BUT, how is this easier than downloading a file directly to your phone, renaming it and putting it at the root of your sd card and going to recovery?
Click to expand...
Click to collapse
Good question because that is what I do. Just an alternative method. The upcoming unroot will probably be more helpful to some.
But this method will help some for sure. It will download it to your phone for ya and put you in recovery. Well most of the other phones have it so why not ours.
Someone made the request and here it is. I will also be adding other tweaks to the app over time and useful info after rooting to this thread.
Sent from my SGH-T959 using XDA App
TGA_Gunnman said:
Good question because that is what I do. Just an alternative method. The upcoming unroot will probably be more helpful to some.
But this method will help some for sure. It will download it to your phone for ya and put you in recovery. Well all most of the other phones have it so why not ours.
Someone made the request and here it is. I will also be adding other tweaks to the app over time and useful info after rooting to this thread.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
this
I am stoked that someone would take the time to make this program. I dont have immediate access to a PC(I use a mac) but an easy unroot program clinches the decision to root my phone. thank you for taking the time to make this much props
please do it for Mac OS.
best wishes...
Awesome application thanks!
Sent from my SGH-T959 using XDA App
Great, easy app. Works!
Wish I had seen this a few hours ago! Just spent 30mins trying to get the button presses right to get into recovery mode before I finally got it.
alsatea said:
please do it for Mac OS.
best wishes...
Click to expand...
Click to collapse
Sorry I don't have a Mac to dev/test on. Neither do any of my friends. But, I will see what I can do.
Can't you dual boot windows on your Mac?
TGA_Gunnman said:
Sorry I don't have a Mac to dev/test on. Neither do any of my friends. But, I will see what I can do.
Can't you dual boot windows on your Mac?
Click to expand...
Click to collapse
If you write it in java, then it will run any OS, right?
Relase src code. I may be able to port to unix/macosx and/or java.
I have Windows 7 installed through Bootcamp and it worked perfectly. Thanks
kelmerp said:
If you write it in java, then it will run any OS, right?
Click to expand...
Click to collapse
Ok Let me see what I can do.
Yeah release the source... Ports will follow if necessary
jganyard said:
Wish I had seen this a few hours ago! Just spent 30mins trying to get the button presses right to get into recovery mode before I finally got it.
Click to expand...
Click to collapse
I know what you mean. I'm still used to holding down the buttons until the recovery screen pops up like on my G1. On the Vibrant, I have to remind myself to let go of the buttons as soon as the "Vibrant" screen comes up.
Yes, the overall process involved to use this program is longer, involves more steps, and, therefore, easier to screw up. Also, the fact that you have to download more than one file increases the chances of messing something up because of the possibility of corrupted files. Also, the "flash in recovery" method is OS agnostic, and technically doesn't even require a computer since you can download and rename the zip file right on your phone if you want to. Still, it's very easy to follow and would appeal to those who are new to rooting and don't feel comfortable with booting into recovery mode.
Updated the app to include unroot. Created a new update.zip file that will remove root. Also fixed the CMD shell launching minimized.
Lets see the java port. or even an APK to do so
jganyard said:
Wish I had seen this a few hours ago! Just spent 30mins trying to get the button presses right to get into recovery mode before I finally got it.
Click to expand...
Click to collapse
Why fuss with button pushes, just enable debugging, plug in your phone, open a command prompt and type the following
Code:
adb reboot recovery
It's easier than messing with those buttons I assure you.
Root Your RAZR i
Before you do anything, you must unlock the bootloader on your RAZR i. See my thread here for details: http://forum.xda-developers.com/showthread.php?p=32576654
If you do NOT want to unlock your bootloader, use this x86 version of motofail2go by Dan Rosenberg: http://174.132.194.66/~batakang//ftp/RAZRi/RootUtility/motofail2go_razri.zip
What does this do?
Flash this .zip in Clockworkmod by turl1 to Root your device.
Download:
http://batakang.com/ftp/RAZRi/RootUtility/RAZRiRoot.zip
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Brought to you by Batakang and turl1 for his Clockworkmod Recovery. Cheers!
Yeah! now I'm rooted, I'm ready to theme... Thanks for this simple root methode.
But, if I make mistake(s) while modify system apks, is there a solution to go back to original? I have to modify framework and a lot of system apks, it will not easy to do that only with root explorer...
Thanks and happy Razr i!
ZeuBug said:
Yeah! now I'm rooted, I'm ready to theme... Thanks for this simple root methode.
But, if I make mistake(s) while modify system apks, is there a solution to go back to original? I have to modify framework and a lot of system apks, it will not easy to do that only with root explorer...
Thanks and happy Razr i!
Click to expand...
Click to collapse
Here you are
http://forum.xda-developers.com/showthread.php?t=1936512
mattlgroff said:
Here you are
http://forum.xda-developers.com/showthread.php?t=1936512
Click to expand...
Click to collapse
I saw that but I didn't realize it could flash .zips... so I go to work a little bit and going back here just after! Happy to see you here!
Sent from my XT890 using xda premium
ZeuBug said:
I saw that but I didn't realize it could flash .zips... so I go to work a little bit and going back here just after! Happy to see you here!
Sent from my XT890 using xda premium
Click to expand...
Click to collapse
We can't flash zips just yet, need a custom recovery. These are not flashable, but contain fastbootable files for the firmware's system and boot images. The systems are not signed so it won't work on locked device.
mattlgroff said:
We can't flash zips just yet, need a custom recovery. These are not flashable, but contain fastbootable files for the firmware's system and boot images. The systems are not signed so it won't work on locked device.
Click to expand...
Click to collapse
But could we do it: adb push framework-res.apk /system/framework/framework-res.apk ?
ZeuBug said:
But could we do it: adb push framework-res.apk /system/framework/framework-res.apk ?
Click to expand...
Click to collapse
Well if your framework-res.apk is broken the phone tends to not boot normally. If you did have working adb you would need to mount the system as re-writable. Whether this is with the root exploit and stopping the batch at the "adb remount" command or flashing the razr_i_boot_insecured.img to allow you to run "adb remount" doesn't make a difference.
Fastboot flashing system works even if adb doesn't (assuming you have good enough battery power or a factory-style adapter from Team Black Hat).
mattlgroff said:
Well if your framework-res.apk is broken the phone tends to not boot normally. If you did have working adb you would need to mount the system as re-writable. Whether this is with the root exploit and stopping the batch at the "adb remount" command or flashing the razr_i_boot_insecured.img to allow you to run "adb remount" doesn't make a difference.
Fastboot flashing system works even if adb doesn't (assuming you have good enough battery power or a factory-style adapter from Team Black Hat).
Click to expand...
Click to collapse
Sorry to ask you more detail, but it will be first time I will modifiy system files without cwm...
1-I could edit your .bat to push my modded apks?
2-with razr_i_boot_insecured.img? which lines I have to keep or not to keep?
3-is-it safe? if I do mistakes, pushing the original apks could solve the problems?
4-what is chmod number for those apks?
Thanks a lot...
ZeuBug said:
Sorry to ask you more detail, but it will be first time I will modifiy system files without cwm...
1-I could edit your .bat to push my modded apks?
2-with razr_i_boot_insecured.img? which lines I have to keep or not to keep?
3-is-it safe? if I do mistakes, pushing the original apks could solve the problems?
4-what is chmod number for those apks?
Thanks a lot...
Click to expand...
Click to collapse
You can find modified source here:
http://pastebin.com/gnNfBU1H
Just edit the batch in notepad and paste that in. Have framework-res.apk in the same folder. The best idea is to just always have the insecured boot.img on your phone, so you only have to type "adb remount"
Hey Mattlgroff,
after the SS3 Hype is over here, i finally got time to get new stuff into our RazR i Forum. First thing i saw was the new Root Method. I'm right, this can be done with an complete locked Bootloader? Sounds great for many users i guess.
HSD-Pilot said:
Hey Mattlgroff,
after the SS3 Hype is over here, i finally got time to get new stuff into our RazR i Forum. First thing i saw was the new Root Method. I'm right, this can be done with an complete locked Bootloader? Sounds great for many users i guess.
Click to expand...
Click to collapse
Yup. Some Carrier branded phones cannot be unlocked and need it to root.
Sent from my XT890 using Tapatalk 2
Great, thanks! I will add it right now.
So no big Warnings to write, just run the bat and profit
HSD-Pilot said:
Great, thanks! I will add it right now.
So no big Warnings to write, just run the bat and profit
Click to expand...
Click to collapse
Nah worked on my phone fine.
Just give thanks to Dan Rosenberg for his work and maybe link his donate link. He deserves all he can get
Sent from my XT890 using Tapatalk 2
Credits already added :good:
The Donate Link sounds great, i'll do that (yours, too )
Cheers
http://www.handy-faq.de/forum/motor...-motorola_razr_i_root_rooten.html#post2241544
All up, you Guys rock the i :good:
Ok , i like to think that i'm not stupid with these kind of things...
But i can't get the vol up + power thing right.
here's what i do.
- Factory reset (from phone menu...how do we enter recovery ??)
- skip account setup
- enable usb debugging and unknown sources
- start motofail2go
- it copies the files correct to my phone..adb is working.
Then i can't get the phone to vibrate with pressing vol up + power at the same time...
Should it be a short press , long press .. tried it all with 3 different persons..
When i give up and continue without the phone vibrating , it states exploid succes , but no sign of root.. (no superuser app , no su in system/bin , no su with su checker)
HELP.....
arnoldl said:
Ok , i like to think that i'm not stupid with these kind of things...
But i can't get the vol up + power thing right.
here's what i do.
- Factory reset (from phone menu...how do we enter recovery ??)
- skip account setup
- enable usb debugging and unknown sources
- start motofail2go
- it copies the files correct to my phone..adb is working.
Then i can't get the phone to vibrate with pressing vol up + power at the same time...
Should it be a short press , long press .. tried it all with 3 different persons..
When i give up and continue without the phone vibrating , it states exploid succes , but no sign of root.. (no superuser app , no su in system/bin , no su with su checker)
HELP.....
Click to expand...
Click to collapse
It took me many tries as well. Pressing power slightly before volume up seemed to help me.
mattlgroff said:
It took me many tries as well. Pressing power slightly before volume up seemed to help me.
Click to expand...
Click to collapse
Really not working for me... tried about 500 times now.
should it be a long or a short double press ?
phone still connected with usb ?
press when phone is tuned on just in homescreen ?
sorry to ask..but it really bugs me that i cant get this to work....
greetings , arnold
arnoldl said:
Really not working for me... tried about 500 times now.
should it be a long or a short double press ?
phone still connected with usb ?
press when phone is tuned on just in homescreen ?
sorry to ask..but it really bugs me that i cant get this to work....
greetings , arnold
Click to expand...
Click to collapse
Its a lot if trial and error. I tried about 10 different ways and finally got it. The best way to root is to unlock the boot loader and use my tool. No timing problems
Sent from my XT890 using Tapatalk 2
When I plug my Gear in to my pc it's not showing, I have enabled usb debugging & have the driver installed as I have got the Note 3 as well.
Is there something I'm missing?
Try changing your usb cable. I had the same problem dude
Sent from my GT-I9500 using XDA Premium 4 mobile app
The Gear doesn't have the options to be mounted as a Windows volume.
So you can't see it in the explorer.
Just use adb to push/pull files and install apk. It's free and work well.
@home said:
When I plug my Gear in to my pc it's not showing, I have enabled usb debugging & have the driver installed as I have got the Note 3 as well.
Is there something I'm missing?
Click to expand...
Click to collapse
hi,
the easiest is to install Wondershare MobileGO for ANDROID
search Google for free 15 day trail.! ( i am running stock and no root on Gear and phone ,so no problems )
install on pc and run and connect either your gear or Note 3 etc
Make sure USB debugging is enabled on Gear in settings/Gear info/About Gear /software version ..tap till you see notice ,"you are one step away from been a developer" ( something like that )Go one step back , tick USB debugging that is now visible ?
.(i use a old note 2 usb cable to connect to pc )
It will install drivers for gear or phone automatic !
with Wondershare you can sideload apps ,
,( tip ...be sure to install ES file explorer or something similar to see any relevant files from watch
i also use usb cable to charge my gear from pc /laptop,its easier )
You can also install most free apps directly from Play store within Wondershare MobileGo..( Gear connected to laptop and select" Playstore" at top of .menu, if you are in Wondershare...
se attached snip of my Gear in Wondershare MobileGo
good luck
Or use my rom and enable MTP, will come up in windows explorer like any other device.
fOmey said:
Or use my rom and enable MTP, will come up in windows explorer like any other device.
Click to expand...
Click to collapse
Just holding off rooting & romming just for the moment. Want to be sure that it all works ok for now.
But I have been looking at your thread, thanks.
I've kies & odin to see the gear now, I tired another usb cable.
fOmey said:
Or use my rom and enable MTP, will come up in windows explorer like any other device.
Click to expand...
Click to collapse
Wow and I didn't even think about that! My Wondershare trial ran out. Downloading your latest and going to flash it today.
BTW, I am glad I rooted and installed null_ and I saw a post that Kingo can root the the Gear.
BTW if you use the Null ROM you can also connect ES File Explorer with Dropbox and just drop files back and forth into the Gear that way, without having to use adb push or even connect it via USB.
Just to be curious, how can we enable MTP without null_ ?
I manage to activate it via adb shell with sys.usb.config mtp,adb and sys.usb.state mtp,adb.
A Galaxy Gear appears in the device manager, which isn't the case in the natural Gear's state (sys.usb.config acm).
So I guess a part of the work is done. But nothing shows up in Explorer. So something is missing
aviguera said:
BTW if you use the Null ROM you can also connect ES File Explorer with Dropbox and just drop files back and forth into the Gear that way, without having to use adb push or even connect it via USB.
Click to expand...
Click to collapse
OK Here's my lazy question. How do you do that? I mean the drop box trick.
Tyia
Sent from my SM-N9005 using xda app-developers app
3vo3d said:
OK Here's my lazy question. How do you do that? I mean the drop box trick.
Tyia
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
If you swipe right in ES File Explorer you'll see the option for "Cloud" (instead of LAN / SD). You can then click on the "+" button to add a new "cloud server" and choose Dropbox
You then authenticate with your dropbox account and select the folder you want to sync.
BruceFeuillette said:
Just to be curious, how can we enable MTP without null_ ?
I manage to activate it via adb shell with sys.usb.config mtp,adb and sys.usb.state mtp,adb.
A Galaxy Gear appears in the device manager, which isn't the case in the natural Gear's state (sys.usb.config acm).
So I guess a part of the work is done. But nothing shows up in Explorer. So something is missing
Click to expand...
Click to collapse
Any success with non null mtp? I find that null seems to slow down the flick response for viewing the time compared to the stock rom and various leaks ( I suppose it's part of battery life extension). It is a watch first and foremost for me, so I need the time to POP. It would be nice to transfer files to it like every other android device I own without custom roms or $40 applications. I know the function is in there somewhere.
No success at this point.
Something is missing but I don't know what. I manage to have 2 ghost drives using the mass_storage mode but I didn't try to mount the volumes.
A thing that I remarked. After installing null_, enabling MTP and switching to stock ML1, the MTP has remained. So I guess there's a parameter somewhere but I can't figure where at the moment.
BruceFeuillette said:
No success at this point.
Something is missing but I don't know what. I manage to have 2 ghost drives using the mass_storage mode but I didn't try to mount the volumes.
A thing that I remarked. After installing null_, enabling MTP and switching to stock ML1, the MTP has remained. So I guess there's a parameter somewhere but I can't figure where at the moment.
Click to expand...
Click to collapse
Look at the Triangulum Kernel thread. It will enable MTP in a "stock" rom. I can now dump files to the device from windows explorer (I'm also rooted with TWRP recovery on the BNA3 rom).
Not tethering yet so I still have to adb install apps as the Gear doesn't allow unknown sources. Is there an entry in settings.db I can tweak to allow unknown sources?
edit: found the key in settings storage - settings.db/global/install_non_market_apps but no keyboard to edit it on the gear (
along the same lines I found settings.db/system/mtp_drive_display key, currently set to 1 with mtp working. Can you compare to you settings with no mtp working?
There's no such key on the settings.db.
Only mtp_open_session, mtp_running_status, mtp_sync_alive, mtp_usb_conditions_met, mtp_usb_connection_status.
All is set to 0.
Can you give me all the key and values with this command : SELECT * FROM system WHERE name LIKE '%mtp%' ?
papashex said:
no keyboard to edit it on the gear (
Click to expand...
Click to collapse
Install one via adb install
Ok, I've set mtp_running_status and mtp_open_session to 1 according to my S3.
The Gear shows up like "Galaxy Gear (DC***)". The driver failed to install.
Relaunching it leads to a SAMSUNG Mobile MTP Device driver that fails too...
Ok, I manage to get it work.
That's great. But I can't do it again... Damn.
The Gear must be rooted, because some apps need to be launch as root.
The last thing is done via adb shell
Code:
am start com.android.systemui/.usb.UsbStorageActivity
So you had to click on the connect button and there the Gear is in visible in Explorer.
Some commands that i've launched before that are related to MTP.
Code:
am startservice com.android.MtpApplication/.MtpService
am start com.android.MtpApplication/.MtpApplication
I'm trying to figure it out. But unfortunately it's not as simple as to check the MTP checkbox...
EDIT : the pieces of the puzzles
I manage to got it right a second time, but it's a total mess...
Code:
su
sqlite3 /data/data/com.android.providers.settings/databases/settings.db
INSERT INTO system(name,value) VALUES('mtp_dipslay_drive',1);
update system set value=1 where name="mtp_running_status";
.quit
am startservice com.android.MtpApplication/.MtpService
am start com.android.MtpApplication/.StoreAddPopup
setprop sys.usb.config mtp,adb
am start com.android.systemui/.usb.UsbStorageActivity
The truth is somewhere in this lines. I don't know the order so far. Maybe some of them are useless.
Ok, I got it.
I need confirmation that the manipulation is the right one.
Here's a quick How To.
You need : rooted Gear, sqlite3.
For rooting, there's a sticky in this forum. So, install sqlite3 on your /system/bin/.
Launch adb.
Here are the commands you have to type.
Code:
su
sqlite3 /data/data/com.android.providers.settings/databases/settings.db
INSERT INTO system(name,value) VALUES('mtp_display_drive',1);
UPDATE system SET value=1 WHERE name="mtp_running_status";
.quit
setprop persist.sys.usb.config mtp,adb
Reboot your Gear and it should be done. MTP is enabled at boot and your Gear is visible.
As it's persistent there's no need to redone this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a stock Gear running NA3.
Sorry for the delayed response. Once I found the Trianguluum kernel provided MTP I stopped worrying about manually triggering MTP.
I see there's a new UK firmware, US can't be far behind. When I'm flashing that I'll give your mtp method a try.
When I connect my Gear to Mobilego it shows up as a Samsung GT-S5690 and so can't load Null. Has anyone seen this before?
device not found, device not found, device not found, device not found, device not fo
no matter what i do , no matter what i try its always device not found!!! Regardless of pc, mac, usb, mobilego, airdroid, terminal commands, dos prompt commands, odin, cydia, you name it have tried it! im seriously losing my mind. I just want to root my gear! Whether that entails rooting my galaxy 3 is irrelevant, i just want to open my gear! This is my last try to get some help before I THROW IT IN THE F*ing garbage! Sorry, just really upset. Thanks for any help you may be able to provide!
Root is not required to update to PD6
Edit: @rahilm is saying the zip extension is not required, I can't verify but it's quite likely true, so you can just skip adding .zip to the file name.
Edit2: Thanks to @Red5, PC2 has a patch level of March, PD6 has a patch level of May. Also all links are still up as of May 6, 2016
Edit3: If links are broken, @Zero4 has posted mirrors here
Edit4: For those with dm-verity issues, download files 2 and 3, and use Odin to flash to BOJ7, instructions are in step 2.
Hey there guys, I haven't seen a full guide yet to update to PD6, from 5.1.1 (BOJ7 or 9) so I decided to make one. Of course none of this would be possible if the people in the other thread that found all the OTAs.
There are a few Marshmallow version for the 920A right now, PC2 (with a patch level of March and build date 2 months ago) seems to be the first one that Samsung shared with AT&T, while PD6 (with a patch level of May and a build date of Apr 29) is the most recent version.
Tools required:
1. ADB, download here, install with arguments Y, N, Y
2. Odin, get a clean version from Sammobile here
3. Get this if you are on Cricket firmware(BOJ6), or not on AT&T firmware BOJ9 or BOJ7 or facing dm-verity errors. Link to BOJ7
4. Get this if you are on AT&T firmware, but not on the most recent BOJ9 Lollipop firmware: BOJ7 -> BOJ9 OTA
5. Get this to update from Lollipop to Marshmallow: BOJ9 -> PD5 OTA
6. Get this to get to the newest most recent build of Lollipop PD5 -> PD6 OTA
This was tested on a Windows 10 64 bit machine.
1. Make sure you have all your stuff backed up! These steps will wipe your phone!
2. If you are on Cricket BOJ6 or facing dm-verity issues, use Odin to flash your phone to AT&T BOJ7, this is necessary before you proceed. If you are on BOJ9, skip to step 4. Do this by downloading file 2 and file 3, plugging in your phone to your computer, turning on Odin, turn off your phone, and enter download mode by pressing volume down, home and power together for a few seconds. Then you should see Odin say that a phone has been added, and a box on the top left becoming blue colored. Now extract the files from part 3, and press the "BL, AP, CP, and CSC" buttons in order, each time there will be a popup asking you to load a file, simply load the file containing the text in the button. eg, load the BL_G920AUCU3BOJ7_CL5927475_QB6773820_REV02_user_low_ship.tar.md5 file after pressing BL. Verifying the files may cause Odin to freeze, just wait a few minutes, and Odin will unfreeze. DO NOT TOUCH anything else, once all the four files are loaded, press start, and keep your phone plugged in.
Odin:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. Wait for BOJ7 to finish flashing, and reboot. Now, open up CMD by pressing windows and "R" on your computer together, then typing in CMD.
Now, make sure you have "show file extension" enabled in Windows, and add the .zip extension to SS-G920AUCU3BOJ7-to-U3BOJ9-UP, so it is now called SS-G920AUCU3BOJ7-to-U3BOJ9-UP.zip.
Now, open up CMD, and cd to the directory that you put this file in. By typing in "cd directory", in my case this would be "cd C:\Users\MYUSERNAME\Downloads"
Once in that folder, fire up ADB by typing adb in the command console, if it installed correctly it should print out a bunch of help. Once you get to the welcome screen on your phone, you can now shut the phone down, and enter recovery mode. Do this by pressing the volume up, home and power button together. Once you enter recovery, use the volume buttons to select apply update from adb, and use the power button to confirm.
In cmd, type "adb devices", it should show a random string if your phone is connected and adb is working. Now type adb sideload SS-G920AUCU3BOJ7-to-U3BOJ9-UP.zip wait for completion, this will take a while. Once this has completed, your phone will show the AT&T logo for around half a minute, and the welcome screen will show up again.
4. Shutdown your phone, and enter recovery mode by pressing volume up, home and power button together
Open up cmd, type in "cd directory" to go the the directory where you place the download, in my case it was "cd C:\Users\MYUSERNAME\Downloads", if you did not read step 3.
Rename file 5, and add a zip extension (make sure explorer has the show file extension option checked), it should now be called SS-G920AUCU3BOJ9-to-U3CPD5-UP.zip, type in adb sideload SS-G920AUCU3BOJ9-to-U3CPD5-UP.zip, this will take roughly 15 minutes, once completed and a reboot has happened, you may now turn the phone off again
5. Similarly to step 4, side load file 6
You are now on the most recent build of Marshmallow!
CMD and ADB on windows:
Edit: screen shot of PD6:
Also make sure to go in and turn on usb debugging between the different adb updates
Any drawbacks of not waiting for OTA? Samsung Pay still works using this, knox not tripped, etc?
Your data gets wiped, that's a big no-no for a lot of people, otherwise samsung pay still works and knox isn't tripped.
Also USB debug mode isn't required, as long as you boot into recovery mode.
Wanted to mention that you don't need to cd to directory. Just press shift + right click where your Ota files are located and click on "open command window here". Saves a minute or two since your command window is already showing the crrect directory.
Sent from my SM-P600 using Tapatalk
sand_bit said:
Your data gets wiped, that's a big no-no for a lot of people, otherwise samsung pay still works and knox isn't tripped.
Also USB debug mode isn't required, as long as you boot into recovery mode.
Click to expand...
Click to collapse
Thank you. Data backup/restore isn't an issue for me, just concerned about functionality so that addresses my concern.
Thank you. It work great
Is it possible to skip step 5 if I have the "SS-G920AUCU3BOJ9-to-U3CPD6-UP" file from another thread? Or best to go OJ9 to PD5 to PD6?
Sent from my Galaxy S7 Edge.
runner77 said:
Is it possible to skip step 5 if I have the "SS-G920AUCU3BOJ9-to-U3CPD6-UP" file from another thread? Or best to go OJ9 to PD5 to PD6?
Sent from my Galaxy S7 Edge.
Click to expand...
Click to collapse
OJ9 to PD6 has failed for most people when tried... the path that works is OJ9 to PD5 then PD5 to PD6.
Dante087 said:
OJ9 to PD6 has failed for most people when tried... the path that works is OJ9 to PD5 then PD5 to PD6.
Click to expand...
Click to collapse
I was able to upgrade from OJ9 to PD6 without any issues. I only ran into the issue with the open error, which I used a different computer and it worked.
ryguy2010 said:
I was able to upgrade from OJ9 to PD6 without any issues. I only ran into the issue with the open error, which I used a different computer and it worked.
Click to expand...
Click to collapse
That's good to know... I was on PC2 so I had to make the jump to PD4, then PD5 and PD6.
ryguy2010 said:
I was able to upgrade from OJ9 to PD6 without any issues. I only ran into the issue with the open error, which I used a different computer and it worked.
Click to expand...
Click to collapse
Thank you both for the replies.
Sprint guy here who sits next to a extremely frustrated AT&T S6 coworker/boss. He's been b!tching for months for the MM update. Just trying to make him happy.
Sent from my Galaxy S7 Edge.
sand_bit said:
There are a few Marshmallow version for the 920A right now, PC2 (with a patch level of May and build date 2 months ago) seems to be the first one that Samsung shared with AT&T, while PD6 (with a patch level of March and a build date of Apr 29) is the most recent version.
Click to expand...
Click to collapse
Just pointing out that you have your security dates backwards... PC2 has the March security patches, and PD6 has the May security patches.
Plz guys, why is it so complicated with G920A than all other G920xxx to upgrade to MM !!? I need an answer with hot thanks
Sent from my SAMSUNG-SM-G920A using XDA Free mobile app
Hi, the link to the cricket one is dead.
sand_bit said:
Edit: @rahilm is saying the zip extension is not required, I can't verify but it's quite likely true, so you can just skip adding .zip to the file name.
Click to expand...
Click to collapse
Just a few minutes ago I went from BOJ9 -> PD5, then from PD5 ->PD6, both times WITHOUT adding .zip to the end. Great write up by the way, thank you for taking the time to put this together!
Tim
Any knowledge of the MM files for the ATT s6 Edge PLus? (g928A) Thanks.
Do I want PD6? How do I get there from PC2?
Should people on PC2 wait for a proper tar?
it worked with me very well, thanks a lot for making finally my G920A 6 MM. Good luck to our forum ( forum of genius)
LLStarks said:
Do I want PD6? How do I get there from PC2?
Should people on PC2 wait for a proper tar?
Click to expand...
Click to collapse
I think PD6 runs a lot smoother than PC2... also has the May security patch built in if you care about that