Yes. How to root?
Got root
Found this from goapk forum:
Dial * # * # 2846579 # * # *
Go to projectmenu, background settings, log settings, log switch and set Log on
Reboot phone
Set USB debugging on
Download DooMLoRD_v3_ROOT-zergRush-busybox-su.zip
From here http://forum.xda-developers.com/showthread.php?t=1321582
Unzip, connect usb (dont mount SD) and run runme.bat
Let it do the magic, and when phone reboots, its rooted
sanpsa said:
Got root
Found this from goapk forum:
Dial * # * # 2846579 # * # *
Go to projectmenu, background settings, log settings, log switch and set Log on
Reboot phone
Set USB debugging on
Download DooMLoRD_v3_ROOT-zergRush-busybox-su.zip
From here http://forum.xda-developers.com/showthread.php?t=1321582
Unzip, connect usb (dont mount SD) and run runme.bat
Let it do the magic, and when phone reboots, its rooted
Click to expand...
Click to collapse
Do you using chinise version or overseas? Because it don't work on overseas version.
Overseas and it worked
do not forget to disable fast boot!
Source
Rough translation:
1, download ROOT tools, there are links below. (DooMLoRD_v3_ROOT-zergRush-busybox-su.zip)
2, ensure that ADB drivers are correctly installed
3, turn on usb debugging in settings -> applications -> debugging. turn off fast boot option in settings -> applications
4, open dialer, type *#*#2846579#*#*, projectmenu, background settings, log setting, on, go back, open dump & log, turn on all options.
5 , on the PC run runme.bat
6, wait for the complete restart.
7, OK Congratulations root complete!
Tested myself. Works perfectly.
Edit: ah darn you beat me to it lol. Ah well. :-D
Yep confirmed, this method really works.
Isamu_Dyson said:
Source
Rough translation:
1, download ROOT tools, there are links below. (DooMLoRD_v3_ROOT-zergRush-busybox-su.zip)
2, ensure that ADB drivers are correctly installed
3, turn on usb debugging in settings -> applications -> debugging. turn off fast boot option in settings -> applications
4, open dialer, type *#*#2846579#*#*, projectmenu, background settings, log setting, on, go back, open dump & log, turn on all options.
5 , on the PC run runme.bat
6, wait for the complete restart.
7, OK Congratulations root complete!
Tested myself. Works perfectly.
Edit: ah darn you beat me to it lol. Ah well. :-D
Click to expand...
Click to collapse
You must also turn on Unknown sources from settings >applications>Unknown sources. Otherwise it does not work
Just did this and all went ok.
Shouldn't we have a superuser installed with the rooting?
Because my phone rebooted after rooting but I can't find any SU
it's not working
Superuser is there. Latest version also. Look harder ;-D
I think phone is not rooted as I installed the root explorer and wont show the option to mount R/W
sanpsa said:
Got root
Found this from goapk forum:
Dial * # * # 2846579 # * # *
Go to projectmenu, background settings, log settings, log switch and set Log on
Reboot phone
Set USB debugging on
Download DooMLoRD_v3_ROOT-zergRush-busybox-su.zip
From here http://forum.xda-developers.com/showthread.php?t=1321582
Unzip, connect usb (dont mount SD) and run runme.bat
Let it do the magic, and when phone reboots, its rooted
Click to expand...
Click to collapse
Oila! its working great love it.....
I am getting "adb server is out of date.killing..." and then "daemon started successfully" message after each command it executes and at the end nothing happens.
You may need drivers for adb to work, if you havent used adb before...
Should be in the Mobile partner drive, that pops up when usb is connected...
No i have all drivers and sdk installed.
I rooted the chinese gingerbread version this morning using same tool.Now i have the English version.
Now i get this messages and although it says that is completed,it is not.
---------- Post added at 09:31 PM ---------- Previous post was at 09:03 PM ----------
Ok it seems it was droidexplorer causing this problem.
I uninstalled it and it works fine.
I did a second run and root went ok and SU is now there.
New issue, the PC don't detect the phone anymore.. any ideas?
I' ve successfully root the device with your instructions, thanks. But with DoomLord tool, needed to write command su every time to get root rights in adb shell. So I tried the SuperOneClick method, and rerroot the device. After that I have root uccount automatic, as on froyo rom.
I dont know what happen but my computer stop detecting any USB devices, only pen drives.
will this DooMLoRD_v3_ROOT-zergRush-busybox-su.zip change the PC configuration????
Kamajoo said:
You must also turn on Unknown sources from settings >applications>Unknown sources. Otherwise it does not work
Click to expand...
Click to collapse
Exactly, If you dont do that, superuser.apk doesnt install.
Thanks for the guide guys. I did it with overseas version and it worked. Thanks!
Subject: (SOLVED) MTP is failing to work after a hack attempting to enable USB mass storage connections.
ABBREVIATIONS USED HEREIN
"NOTE3":
- Verizon Galaxy Note 3
- SM-N900V (JSS15J.N900VVRUBMI9)
- Android 4.3
- Successful Root de la Vega <http://forum.xda-developers.com/showthread.php?t=2481590> (thank you very much)
"NOTE0":
- AT&T Galaxy Note
- SAMSUNG-SGH-I717
- Successful root The Unofficial (by Flappjaxx and The Collective) (thank you very much)
- Android 4.0.3 after the root (I forgot what it was before; 3.0?)
"PC":
- Windows 8
- Using USB 3.0 port with USB 3.0 cable to NOTE3
SYNOPSIS
USB mass storage (block transfer mode) works on NOTE0 but not on NOTE3. I've read that this removal of USB mass storage is a new feature of Android 4 but that it may still work for external SD cards. It does NOT work on my Note 3, neither internal nor external SD, but it does work for both internal and external SDs on NOTE0. It seemed to me that perhaps MtpApplication.apk was the culprit, so I set about copying that application from NOTE0 to NOTE3.
CREATING THE FAILURE
- Ran 'adb backup ...' from PC.
- Copied MtpApplication.apk from NOTE0 to NOTE3.
- Mounted /System RW.
- Moved original "/System/app/MtpApplication.apk" to a safe location.
- Deleted "/System/app/MtpApplication.odex". I figured the new file would be dexified when first run.
- Copied NOTE0's MtpApplication.apk to NOTE3 "/System/app/MtpApplication.apk".
- Set -rw-r--r-- root root on MtpApplication.apk.
- Mounted /System RO.
- Rebooted.
- Got "Android is updating" notice.
- Connect to PC.
- + The normal Installer CD drive appeared in Windows Explorer for several seconds.
- + The device "N900V" did not appear as it always has in the past. There are no references to NOTE3 in Windows Explorer.
- + Reinstalled Samsung device drivers on PC and rebooted PC.
- + Rebooted NOTE3.
- + No change. The MTP application has the three checkboxes for MTP, PTP, and USB 3.0, and the check can be moved to each, but there is no apparent communication between NOTE3 and Windows Explorer. The notification tray does show the normal "Click here to change USB connection mode" or whatever it normally says. The Installer does run as before but it is not now followed by the Explorer link to "N900V". No apparent difference with debug mode enabled on NOTE3. Debug bridge (adb.exe) works fine.
ATTEMPTING THE REPAIR
- Mounted NOTE3 /System RW.
- Deleted "/System/app/MtpApplication.apk".
- At this point I noticed that the "MtpApplication.odex" file was NOT created.
- Copied original "MtpApplication.apk" back to "/System/apk/".
- Set "-rw-r--r-- root root" on "MtpApplication.apk".
- Mounted /System RO.
- Rebooted.
- I didn't notice if the "Android is updating" notice appeared. Maybe I wasn't looking.
- At this point all is the same as under "Connect to PC" above. Still a failure.
- Still no "MtpApplication.odex".
- Ran 'adb restore ...' from PC.
- Rebooted NOTE3.
- At this point all is the same as under "Connect to PC" above. Still a failure.
- Still no "MtpApplication.odex".
- Installed and ran OdexerTool (13-11-2013) by MatrixDJ96, 'sysapp' command. System applications, including MtpApplication.apk were odexed or reodexed. MtpApplication.odex now exists.
- Rebooted.
- "System is updating dialog with an incrementing counter.
- At this point all is the same as under "Connect to PC" above. Still a failure.
WINDOWS DEVICE MANAGER
Windows Device Mangler shows a device with errors:
. ---------------------------------------------
. Portable Devices
. SAMSUNG Mobile MTP Device
. ---------------------------------------------
Properties on "SAMSUNG Mobile MTP Device" shows:
. ---------------------------------------------
. This device cannot start. (Code 10)
.
. The process hosting the driver for this device has terminated.
. ---------------------------------------------
It remains that way after uninstalling and reinstalling the Samsung drivers and after a reboot while standing on my toes facing east with my right arm extended above my head and screaming "WOM-A-TOOMA WOM-A-TOOMA WOM-A-TOOMA".
This was NOT a solution:
. <http://forum.xda-developers.com/showthread.php?t=1797344>.
Found the key "UpperFilters" and deleted that key, unplugged and plugged and still no MTP, PTP, or USB 3.0 connection.
None of the devices under "Universal Serial Bus Controllers" show an error.
REQUEST
- What did I do wrong?
- How do I undo that wrong?
- + Should I reapply the Root de la Vega? (Is that like a Spock Lock?)
- * How?
CONTINUING ATTEMPTS TO RECOVER
The next thing I hope to try is to unroot/restore, then root again with de la Vega, but the only unroot/restore instructions I can find are for retail locked devices.
- Found a stock ROM (http://forum.xda-developers.com/showpost.php?p=46424497&postcount=1) and flashed it. Success on the flash but still no connection with Windows File Explorer.
- Flashed Root de la Vega again. Success.
SUCCESS!
Problem solved. Windows File Explorer again shows the .SM-N900V icon and it is usable. Flashing the stock system should have fixed it so perhaps I just didn't reboot enough or didn't wait long enough after the devices installer program finished.
I sure hope someone gives us USB mass storage so I can work directly with the device's file system because MTP and Explorer are not suitable for the work I wish to do. The debug bridge might work but it is nearly as cumbersome as MTP.
Frank
(Why can't I thank myself too?)
UMS
Frank Westlake said:
CREATING THE FAILURE
- Ran 'adb backup ...' from PC.
- Copied MtpApplication.apk from NOTE0 to NOTE3.
- Mounted /System RW.
- Moved original "/System/app/MtpApplication.apk" to a safe location.
- Deleted "/System/app/MtpApplication.odex". I figured the new file would be dexified when first run.
- Copied NOTE0's MtpApplication.apk to NOTE3 "/System/app/MtpApplication.apk".
- Set -rw-r--r-- root root on MtpApplication.apk.
- Mounted /System RO.
- Rebooted.
- Got "Android is updating" notice.
- Connect to PC.
- + The normal Installer CD drive appeared in Windows Explorer for several seconds.
- + The device "N900V" did not appear as it always has in the past. There are no references to NOTE3 in Windows Explorer.
- + Reinstalled Samsung device drivers on PC and rebooted PC.
- + Rebooted NOTE3.
- + No change. The MTP application has the three checkboxes for MTP, PTP, and USB 3.0, and the check can be moved to each, but there is no apparent communication between NOTE3 and Windows Explorer. The notification tray does show the normal "Click here to change USB connection mode" or whatever it normally says. The Installer does run as before but it is not now followed by the Explorer link to "N900V". No apparent difference with debug mode enabled on NOTE3. Debug bridge (adb.exe) works fine.
Click to expand...
Click to collapse
I'm only making a guess that MtpApplication.apk is where UMS is enabled and I have no idea if a copy from Note0/4.0.3 will function on Note3/4.3, but it seems to me that it should work.
Prior to the attempt at importing MtpApplication.apk I tried bringing GoogleTTS.apk from my Note0 to my Note3 and it also failed. It appeared in Settings as an option along with the Samsung TTS engine but when I enabled it Settings reported an error with the package.
Should I have odexed first? For both MtpApplication.apk and GoogleTTS.apk?
Can anyone offer some guidance on this? My problem is that I cannot use Google Play because I cannot or will not agree to their privacy statement, so I have disabled all the relevant Play applications and I download only applications I can find on freeware sites.
Frank
Hello all,
I'm having difficulty trying to run EFS Pro v2.0.70/v2.0.72 to backup my EFS folder on my GT-I9505. I get stuck at the part when it says "Initializing ADB server..." and it just sits there. I just want to point out that I had made a backup of my EFS folder on my GT-I9505 when I first got my phone (around May), but it seems to have been deleted! Anyway, I found some good steps in another thread, as follows:
Before starting, check the following:
Device is fully rooted
SuperSU (or equivalent) is active
USB debugging is ON (Settings->More->About device: Tap several times on "Build number" to enable Developer options and tick USB debugging)
Busybox downloaded AND installed (normal or smart) on your device
Microsoft .NET Framework 4.0 installed on your PC
Samsung USB driver is installed (either by installing Kies or just the driver alone.
Kies is not active (neither as application nor process, check Windows Taskmanager)
ADB fully functional ("adb devices" recognises your phone) -- (look here for a basic ADB tutorial/how to)
In case ADB is not running you need to install the ADB driver
Run EFS Professional as administrator.
Make sure to grant SuperSU access to Shell and confirm the RSA fingerprint request once they pop up on your screen.
Of course, your device should be on the home screen, not on the lock screen
I've followed all these steps, checking each methodically, and guess what, I'm still stuck at "initializing ADB server..."! I even go to cmd and type in "adb devices" and my phone shows up, I see on my phone that a shell has been granted, and yes, I am rooted, I have busybox, and Samsung drivers, .NET 4.0 framework and USB debugging, it's driving me mad, I've even tried different USB ports, and nothing!
If anyone has any suggestions, please fire away!
I have the exact same problem, but with my S3 (I9300) ...
No one who can help?
Did you get sorted my i9505 is the same and I have two phones but one wont work..
Hi
I have a Galaxy Note 4 (SM-N910G) and don’t normally muck around with the system. I have limited experience with Android.
My phone is locked (with important data stored in it)– a couple of days ago (presumably after a system upgrade) it suddenly would not recognise my fingerprint nor backup password.
I tried unlocking the phone using Android Device Manager but although I could get my phone to ring or display text, I could not change the password after locking the phone.
I called Google who said that Android Device Manager only works on earlier Android Versions - ?4 and below and most likely my phone would be running Marshmellow.
I called Samsung who said my only option is to restore to factory settings.
I wanted to use ADB
(to enter: adb shell
cd data/system
su
rm *.key) and downloaded it and tried to use it from the c:\ prompt but I don’t have USB debugging enabled. No device was recognised when running ADB.
I had not registered for a Samsung account so I could not use Find My Mobile.
I tried to apply an update via external storage in recovery mode (I downloaded files such as Lockscreen_Security_bypassV1.1.zip or Pattern-Password-disable.zip) but unfortunately when I tried to apply them, it came up with E:footer is wrong, E: signature verification is required.
(I also tried “Android Multi Tools”).
I do not have CMN recovery loaded nor Aroma+File+Manager
My question is: should I try and use Odin (have downloaded odin3_v3.11.2.zip) and TWRP to try and enable USB debugging or try to disable footer/signature verification??
Any other suggestions to try and unlock my phone???
At the minimum this has been an education!
Thank you for your help!
OK, this is driving me nuts! The phone has been restored to stock (Android Version 8.0.0) and has nothing on it from the Play Store, just the stock Samsung apps - trying to get ADB to work without any joy, as want Fluid NG on it........
It did once offer the options (weird?), but I got the Allow USB Debugging popup with the RSA Key, but also the error 'Because an app is obscuring a permission request, Settings can't verify your response' error - Went to the 'Apps that can appear on top' section (assume this is the same as 'Draw over other apps?), and disabled everything in the list - still the same error!
Now the only options I get when connecting are:
Transfer Files
Transfer Images
MIDI Device
Charge this Phone
So far I've.......
Enabled Dev mode
Enabled USB debugging
Disabled Verify Apps via USB
Installed Samsung Drivers
Installed ADB Fastboot
Disabled all 'Draw over other apps' apps in the Apps list.
Tried another laptop
Tried another USB cable
It shouldn't be this difficult, I know!!