Related
i have root/superuser but cannot get clockwork to work.
it says it is flashing clockwork when i run:
http://forum.xda-developers.com/showthread.php?t=808103
(the other sticked threads wont recognize my phone)
the phone is running eclair. not sure if that is the problem. do i need to use odin? i'm on a mac...
just rerun it should work normally takes two try's for me if that diesnt work reboot computer
rebooted computer and ran it again still nothing. attempt #4 coming up
ugh same thing
here:
Code:
Original credits go to joeykrim, noobnl, skeeterslint, and firon
for their original exploit, root, recovery, busybox, and kung fu
MENU:
1) Simple One Click Root & ClockworkMod 2.04
2) Andromeda Kernel 1.4.1 by noobnl
3) Install SDX Stock App Removal 1.5 apk
4) Install Wireless Tether 2.0.5-pre15 apk
5) Simple Root Uninstaller 2.04
6) Reinstate Stock DI18 Kernel
7) Reinstate Samsung Stock Recovery
8) Quit
ONLY ONE MENU ITEM IS RUN AT A TIME
PLEASE READ GUIDE.HTML INSIDE FOLDER
Please type a number [1-8]:
+++++++++++++++++++++++++++++++++++++++++++++++++++++
Simple One Click Root and ClockworkMod v2.04
+++++++++++++++++++++++++++++++++++++++++++++++++++++
Bash Scripts by DRockstar and Firon
exploit made by joeykrim
original one click 2.5.4 installer made by noobnl and firon
busybox by skeeterslint
IF YOU HAVE PROBLEMS WITH ROOT INSTALL
REBOOT PHONE OR TRY DIFFERENT USB PORT
SAFE FOR ANDROID 2.1 ECLAIR OR 2.2 FROYO
Press any key to continue, or M for Main Menu :
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Looking for device
Device found in 13 seconds
Checking current root status and run exploit if necessary
Copy and run the exploit (may take up to two minutes)
Ignore messages about re-logging in.
If more than five minutes pass, reboot the phone and try again.
366 KB/s (5392 bytes in 0.014s)
5 KB/s (43 bytes in 0.007s)
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3712, 3712}
[*] Searching for adb ...
[+] Found adb as PID 2199
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
Wait 20 seconds...
Looking for device
Device found in 0 seconds
Removing exploit files
Mount as RW
Basic cleanup of past one click roots
407 KB/s (5010 bytes in 0.011s)
Removing remount script
Setup config files
13 KB/s (320 bytes in 0.022s)
Move root files into place
505 KB/s (26264 bytes in 0.050s)
539 KB/s (196521 bytes in 0.355s)
1243 KB/s (486948 bytes in 0.382s)
38 KB/s (479 bytes in 0.012s)
Set permissions
Installing busybox
Checking current phone build
Build ID is ECLAIR
Installing clockworkmod recovery
605 KB/s (313888 bytes in 0.506s)
861 KB/s (5820868 bytes in 6.595s)
RedBend Update Agent 6,1,14,1
FOTA : Make Block Device Nodes
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
page_msize: 4096, phy_unit_size: 262144
src: /data/local/tmp/zImage
dst: /dev/block/bml8 partition size: 0x780000
part_size: 0x780000
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 53700 bytes
read finished
Wait for phone reboot
Looking for device
Device found in 0 seconds
Cleaning up files...
ROOT AND CLOCKWORKMOD INSTALL APPEARS SUCCESSFUL.
TEST ROOT AND CLOCKWORKMOD ON PHONE.
Done
Press any key to exit, or M for Main Menu :
you can't flash clockwork via an update.zip or terminal emulator on the epic?
What do you mean you can't get clockwork to work? You can't boot into recovery with 3 finger method?
Sent from my Battery Munching Epic using XDA App
Also make sure you installed the samsung drivers. I think that got me my first time.
Sent from my Battery Munching Epic using XDA App
Try a different cable. The stock USB cable is a pile of crap.
rip2 said:
Also make sure you installed the samsung drivers. I think that got me my first time.
Sent from my Battery Munching Epic using XDA App
Click to expand...
Click to collapse
on a mac
rip2 said:
What do you mean you can't get clockwork to work? You can't boot into recovery with 3 finger method?
Sent from my Battery Munching Epic using XDA App
Click to expand...
Click to collapse
power, camera, volume down
i can get into recovery but even after it says it flashed clockwork i end up in the stock recovery
k0nane said:
Try a different cable. The stock USB cable is a pile of crap.
Click to expand...
Click to collapse
using my trusty cable that i've used on my evo 11 thousand times, charged the epic with, transferred a bunch of data to the SD card of the epic etc
The OP of that topic says it currently not working on eb13 that might be your problem. I'm out of ideas and don't have a mac gl.
Sent from my Battery Munching Epic using XDA App
rip2 said:
The OP of that topic says it currently not working on eb13 that might be your problem. I'm out of ideas and don't have a mac gl.
Sent from my Battery Munching Epic using XDA App
Click to expand...
Click to collapse
is eb13 stock eclair?
maybe this will shed some light on the situation:
dwd3885 said:
This doesn't seem to work for me. On a Mac, can terminal and select option 1 just fine, but It appears to install Root and Clockworkmod recovery. But whenever I try to boot into clockworkmod, I will still get the Samsung Recovery Util.
Click to expand...
Click to collapse
DRockstar said:
I have heard a couple reports of this phenomenon... I haven't been able to recreate it myself, but that doesn't mean it isn't real. For those that are having this issue, please run the one click root by noobnl and firon, and please report back to me if it works for you:
http://forum.xda-developers.com/showthread.php?t=770388x
Now that I've finally tackled the ext4 and rfs conversion process, I will be posting a new update within the next week, and I hope to fix this issue.
Please keep me updated on your findings, and thanks for reporting.
Click to expand...
Click to collapse
but then when i run the file i get 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"
}
solved all my own problems - pulled out my old vista laptop and did it that way!
this thread can be locked/closed
How to Root/Unroot Samsung Galaxy Note N7000 + CWM
This guide How to root galaxy note is divided in three part, according to running ROM
post #1 Root ICS/JB ROM
Post #2 Root Older GB ROM
post #3 Root access on Newer GB ROM
Click to expand...
Click to collapse
Rooting Note on JB/ICS ROM
Using CWM.zip (temporary/Touch recovery)method to root is said to be unsafe by entropy, and till safe release don't use it
Read This http://forum.xda-developers.com/showthread.php?t=1810954
So present options for rooting are - Here below 5 option to root Note, You can select any of one.
0.Root with apk (NO MORE WORKING ON LATEST ROM)
1A.Root with stock recovery including safe kernel
1B.Root with stock recovery
2. Using Odin (will raise counter)
3.Using Mobile Odin
NEW 17 Dec2012
0.Root with apkCredit goes to Chainfire, alephzain (This method won't replace kernel, so if you root with this method,I recommend to flash safe kernel)(NO MORE WORKING ON LATEST ROM)
1.Download latest from chainfire's original thread
2.Install application as routine apk installation and open it.
3.Open Exynos Abuse application from App drawer
4.Select Root device (see image)
{
"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"
}
5.It will ask SuperSU permission, Grant it See image)
6.Now your device is rooted, for security purpose you can disable Exploit.(see image)
Note : This may break camera, but unchecking disable exploit make it working again
7.Open SuperSU from app drawer and update binary (see image)
How to Unroot and make status Normal
Open Exynos Abuse app, uncheck disable explot and select Unroot device (see image)
Restart device and wait for 10 min. and then you can check status.
1.Rooting with stock recovery - Thanx to Entropy who direct this way,as well always looking for safety measures for us, Chainfire for creating great tool SuperSu (and many more), Phil3759 as files,scripts derived from his Thread and Linus Yang for Busybox.
You can have two choice to root device from recovery
1A.Root + safe kernel + advance recovery. [Recommended method]
Here this will not just root your device but also add safe kernel (patched for mmc erase cap command) so you can safely wipe your device. as well gives you advanced recovery with it you can flash flashable zip files, nandroid backup/restore and more.
All credit goes to Phil3759 for awesome work.
Visit this thread
http://forum.xda-developers.com/showthread.php?t=1901191
And download kernel in zip format according ROM you are having on device.
-Copy downloaded file to Ext SD card to root directory
-Reboot into recovery (vol up+Home+power)
-Select install(update) zip from ext SD card
-select '[your downloaded kerenel].zip' which you have copied to Ext card above
-Reboot device
Now you will have Root + safe kernel
1B.If you want just Root but not kernel, follow this
- Download Root_SuperSu 0.95
-Copy downloaded file to Ext SD card.
-Reboot into recovery (vol up+Home+power)
-Select install zip from ext SD card
-select 'root_SuperSU-*.zip' which you have copied to Ext card above
-Reboot device
-You can see superSU on appl drawer. open it and update.
-Now This will give you only SuperSU not busybox, though application which doesn't depends on system busybox will still works.e.g.Titanium Backup.
-To get full Root+busybox, Download Root_busybox *.zip
-Copy Root_busybox* only to Ext SD card
-Reboot into recovery, Select Install zip from Ext SD card. select Root_busybox* .zip and Flash.
-Done !
PS : If you can't see superSU after flashing above file(sometimes happen if there is too low space like in LQ3 ROM, then use this Root_superSU, followed by same above Root_busybox file.
Immediately after This I recommend to
1.Backup EFS
2.Flash any safe kernel with mobile Odin.
UnRoot :
Busybox uninstaller - Flash in recovery
Complete unroot (busybox+Superuser) - Flash in recovery
2. Short, easy - requires to reset counter
-Download Odin (.tar) version of custom kernel like Notecore, Speedmod, CF root kernel Or other any with same function. If newbies have confusion to select, here is one for example Notecore V12 std kernel. You can use this. But newer version can be found on link mentioned above.
-Flash it using PC odin for PDA tab.
-You will get exclamation mark and raised counter, which can be reset with Triangle Away
-First time opening triangle away application, it will ask to download file(flasher), let it complete. then choose to reset counter, it will restart in special recovery an finish job.
3. Long, No raised couter OR Exclamation mark
-Downgrade to Rootable GB ROM and Root it. OR Download This pre rooted GB ROM and flash using PC Odin
-Wipe cache, data and delvic cache from recovery
-Install Mobile Odin Pro
-Copy ICS ROM file in .tar (you want to flash) to Internal SD card (recommended, but you can have it on EXT too)
-Download Odin (.tar) version of custom kernel like Notecore, Speedmod, CF root kernel Or other any with same function. If newbies have confusion to select, here is one for example Notecore V12 std kernel. You can use this. But newer version can be found on link mentioned above.
-Open Mobile Odin Pro
-select open file
-Point to ROM file you have copied
(file name varies from image above, this is for demo purpose)
-All fiels will popup and feel automatically
-select kernel and point to custom kernel file you have copied
Tick 'Enable ever root' and 'Inject superuser(super SU) -(see image)
Flash.
Done!
First thing you should do after rooting is
-backup EFS folder ( you can use Ktool for that)
-to make some space (at least 15MB). You can safely remove google+, youtube and later install from market.
Now your device is full rooted, and use Titanium backup(or which you have used to backup) to restore
For Rooting on GB ROM, see post no 2 and 3.
How to Root/Unroot Older GB ROM + CWM
Rooting Older GB (Directly rootable) ROM
Now first thing someone newer like to know what is directly rootable and non rootable ROM
Directly rootable GB ROM is older release of ROM before Nov11, which can be root with zergrush exploit directly, without odin it (and so without exclamation mark and raising flash counter)
Which ROMs are directly rootable? and how do i know my ROM directly rootable or not?
Go to Settings -> About phone -> Kernel Version. Note the string present there: 2.6.35.7-N7000XXKJ4-CL641703 Here Red is your kernel version)
If it is one of below mentioned then proceed otherwise follow post #3
These are directly rootable ROM
If ROM having one of these kernels, then it is directly Rootable.
KJ1/KJ4/KJ6/KJ7/KJ8/KJA
KK1/KK2/KK3/KK4/KK5/KK6/KK9/KKA
KL1
KL3(few of KL3 only is directly rootable e.g. Indian KL3. so in case your KL3 cudn't get root with zergrush you should consider it as non directly rootable )
Rooting Procedure
Here procedure divided in two part
Part 1. For whom who just want to root device (you will have option to move to part two anytime)
Part 2. For those who want to Root + CWM (advance clockworkmode recovery, to use upgrade ROM / Nandroid backup restore) - Recommended
Part 1 : - Credit goes to DooMLoRD for his zirgrush exploit
Download This
Before u begin:
Code:
(1) make sure u have installed adb drivers for ur device.
OR you can install kies, that will do the job.
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) Close kies SW completely, close if any antivrus SW running
Procedure for window:
-Extract file you have downloaded.
-Connect device to PC
-Execure Run Me from extracted file, and follow instruction on screen
Done. Device will be rebboted after successfull root.
On successful rooting, you can see working Superuser app in drawer.
Procedure for Max & Linux
Download This
- Extract on PC
- Confirm you have installed driver on PC (Kies will do it)
- Enable unknown sources in setting - application on device.
- Enable USB debugging in setting - application - development on device
- For Mac, double-click and run runmemac.sh. Or you might have to run it in terminal like this:
sh runmemac.sh
-For Linux, double-click and run runmelinux.sh. Or you might have to run it in terminal like this:
sh runmelinux.sh
Connect device N run script
Device should rebooted N you can confirm it by working superuser application on device.
Part 2. Credit goes to Chainfire
Which kernel You have?
(Go to Settings -> About phone -> Kernel Version. Note the string present there: 2.6.35.7-N7000XXKJ4-CL641703 Here Red is kernel version)
Now download tool from below according kernel you have.
I have Kernel KJ1 - Download This– and Extract
I have Kernel KJ4 - Download This - and Extract
I Have Kernel KJ6/KJ7/KJ8 - Download this - and extract
I have Kernel KK1/KK2/KK3/KK4/KK5 - Download This - and Extract
I have Kernel KKA - Download This - and Extract
I have Kernel KK9 - Download This - and Extract
I have kernel KL3 - Download This - and Extract
I have Kernel KL1 - Download This - and Extract
Before u begin:
Code:
(1) make sure u have installed adb drivers for ur device.
OR you can install kies, that will do the job.
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) Close kies SW completely, close if any antivrus SW running
Procedure :
-Connect device to PC
-Execute "not-rooted-yet.bat" and follow the instructions.
-Device will reboot after successfull root, and you can see superuser and CWM application in drawer.
For those who have Root device earlier(with part 1) and want CWM
Download tool as mentioned in part two
-Connect device to PC
-Execute 'Already rooted.bat' from downloaded tool.
-Device will reboot after successfull pushing zImage, and you can see CWM application in drawer.
OR
If you are already Rooted, you can use Mobile Odin Pro to flash CWM
Unrooting
Download This
-Extract - Execute - Rum Me unroot.bat (same as mentioned in part1)
PS : Unrooting by above tool may leave some footprint, so if you want to do it for warranty purpose then best way is to flash stock ROM using PC Odin followed by wipe.
Get root access on Newer GB ROM (non rootable directly)
Get root access on Newer GB ROM (non rootable directly)
Here as name suggest non rootable directly ROMs. guide is not for How to root it, but better we can term it, How to get root access on such newer ROM.
As i said if you ROM not having kernel as mentioned in previous post (#2), you have to consider your ROM as non rootable.
Available option to get root access on such ROMs
1. Flash Pre rooted ROM
As name suggest flashing This ROM with PC odin, you will have ready made Root + CWM. This ROM was modified by ChainFire (All credit goes to him only). And you can flash it using PC Odin without getting exclamation mark/raise flash counter.
Download :
http://d-h.st/HJM
Mirror
Installation method is same as flashing other rootable ROM described here
After flashing you will have Root + CWM
PS: This is first ever GB ROM, and you may notice some screen issue if your Note is newer, dont worry for that once you upate to newer ROM, this issue will go. You can now update to any newer GB ROM with keeping your root intact, mentioned in option 2 below.
2. Update Newer GB ROM using Mobile Odin / CWM
If you are currently on Rooted GB ROM, you can update to any newer GB (non rootable) ROM using PC Odin OR CWM with keeping your root intact.
Here is description available How to use Mobile Odin OR CWM to update newer ROM
After updating to newer ROM, you can flash CF root kernel from here
according to newer ROM kernel. And Flash it using Mobile Odin OR CWM.
I have Kernel KL7 - Download
I have kernel KL8 - Download
I have kernel LA1 - Download
I Have Kernel LA3 - Download
I have kernel LA4 - Download
I have kernel LA6 - Download
I have Kernel LB1 -Download
I have Kernel LC1 - Download
i can confirm, it works whit gt-n7000, kernel and binary counter untouched..
dr.ketan said:
Easy Rooting Toolkit [v1.0](zergRush Exploit)
(WINDOWS ONLY)
Click to expand...
Click to collapse
Ok,and CWM, how install it???
This post is temporary backup while maintanance and not to be use for any procedure
JUST FOR BACKUP post
DONT USE ANYTHING FROM THIS POST
---------------------------------------------------------------------------------------------------------------
When No Any other method works to Root your device, use this
---------------------------------------------------------------------------------------------------------------
Note that, this will downgrade your ROM to KJ1, after that you can update it.
Download: https://rapidshare.com/files/369028110/SGN_XX_OXA_KJ1_FACTORYFS.zip Thanx to Chainfire for making it.
(special thanx to schiwa for providing premium a/c to host file)
Mirror : http://d-h.st/HJM (Thnx to Dev host for providing premium ac to XDA recognise contributor)
- Make sure your SGN is NOT connected to your computer
- Reboot your SGN into "download mode" (Vol down + Home + Power))
- Start ODIN
- Click the PDA button, and select the "SGN_XX_OXA_KJ1_FACTORYFS.tar" file
- Connect the SGN to your computer
- Make sure "repartition" is NOT checked
- Click the START button
- Wait for the phone to reboot TWICE
- Done.
Now you have your device Rooted, Install Mobile Odin Pro n update your device to any new ROM with Mobile Odin
Root GB ROM
NEW
Download dr.Ketan's guide - How to Root & Update ROM on G-Note
Download , Extract n Hit Dr.Ketan's guide No need to enter inside folder.
--------------------------------------------------------------------------
Note : This won't be works on KL7/KL8/LA1 n newer. To gain Root access in such ROM, see post # 2 n 3 of this thread.
----------------------------------------------------------------------------------------------------------------------
Part 1 : Acknowledgement purpose (No need to download from this section)
Method 1 :
Easy Rooting Toolkit [v1.0](zergRush Exploit) with newest zergRush binary (16 Nov 2011) and newer superuser files
Watch Video Guide :
Unrooting
Rooting
video by cursed4Eva Root Unroot
Big Thanx to DooMLoRD Donate DooMLoRD
(WINDOWS ONLY)
WILL WORK ON BOTH LOCKED & UNLOCKED BOOTLOADER DEVICES!
just download the attached file, extract it using winzip/winrar
go to the folder where its extracted and execute "RUNME.bat"
read and follow the instructions on the screen!
Code:
Easy rooting toolkit (v1.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using zergRush exploit
(2) install Busybox (1.18.4)
(3) install SU files (3.0.5)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device.
OR you can install kies, that will do the job. Kies is [URL="http://org.downloadcenter.samsung.com/downloadfile/ContentsFile.aspx?CDSite=UNI_NL&CttFileID=4564828&CDCttType=SW&ModelType=N&ModelName=GT-N7000&VPath=SW/201110/20111010173222709/Kies_2.0.3.11082_152_2.exe"]here[/URL]
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
Tested & Reported to be working on the THESE devices
·
Code:
Sony Xperia X10 (GB firmware)
·Sony Xperia Arc (.42 firmware)
·Sony Xperia Arc S
·Sony Xperia Play [R800i/R800x]
·Sony Xperia Ray
·Sony Xperia Neo
·Sony Xperia Mini
·Sony Xperia Mini Pro
·Sony Xperia Pro
·Sony Xperia Active
·Samsung Galaxy S2 [GT-9100/GT-9100P]
·Samsung Galaxy S II for T-Mobile (SGH-T989)
·Samsung Galaxy S [i9000B]
·Samsung Galaxy GT5570
·Samsung Galaxy W [i8150]
·Samsung Galaxy Tab [P1000] (2.3.3 firmware), [P1000N]
·[COLOR=Red]Samsung Galaxy Note [N7000][/COLOR]
·Samsung Galaxy Player YP-G70 2.3.5 (GINGERBREAD.XXKPF)
·Samsung Nexus S [i9023] (2.3.6)
·Samsung Nexus S 4G 2.3.7
·Samsung Exhibit (SGH-T759)
·Motorola Milestone 3 [ME863 HK]
·Motorola XT860, Bell XT860
·Motorola Defy+
·Motorola Droid X sys ver 4.5.605 w/ gingerbread
·Nexus One (2.3.6 stock)
[ Credits ]
Credits go to all those involved in making this possible!
zergRush Binary from: Revolutionary - zergRush local root
Source:
Inspired from: http://forum.xda-developers.com/showthread.php?t=1319653
DooMLoRD_v4_ROOT-zergRush-busybox-su
--------------------UNROOTING TOOLS---------------
UNROOTING SCRIPT v1.0
so here is the unrooting script to be USED ONLY AND ONLY IF U HAVE USED Easy Rooting Toolkit FOR ROOTING
[ WARNING ]
if u have used any other way/solution for rooting then PLEASE DO NOT RUN THIS... you MIGHT END UP with damaged system...
(thats cause some ppl create symlinks for busybox in /system/bin/ which wipes out stock symlinks to /system/bin/toolbox and breaks/damages system)
[ DISCLAIMER ]
I AM NOT TO BE HELD RESPONSIBLE IF U DAMAGE UR PHONE / SPILL UR COFFEE / MISS UR ALARMS / ANY OTHER CALAMITY/MISHAP
REMEMBER YOU ARE DOING THIS AT YOUR OWN RISK
now that the warning is clear (hopefully) lets get to unrooting
so here is the file.. (WINDOWS ONLY)
just download the attached file, extract it using winzip/winrar
go to the folder where its extracted and execute "RUNME-UNROOT.bat"
read and follow the instructions on the screen!
Code:
---------------------------------------------------------------
Easy rooting toolkit (v1.0)
UNROOTING SCRIPT
created by DooMLoRD
based heavily on FlashTool scripts (by Bin4ry and Androxyde)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) unroot ur device using special script
(2) remove Busybox and assocaited symlinks
(3) remove SU files and assocaiated data
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
--------------------------------------------------------------
DooMLoRD_v1_UNROOTING.zip
---------------------------------------------------------------------------
Method 2: Root + CWM recovery
Souce : http://forum.xda-developers.com/showthread.php?t=1331784
Big Thanx to ChainFire - Donate chainFire
Here simplified Rooting and CWM recovery for Galaxy Note N7000
- Download Root package, see at end of post
- There are three folder
1. Initial CFroot flasher
2. Two other folder having zImage file , you need one only
Which file do I use ?
Listen closely, for I will say zis only once!
Go to Settings -> About phone -> Kernel Version. Note the string present there:
2.6.35.7-N7000XXKJ4-CL641703
What matters most (KJ4) in this case, is in bold. Try to find the matching file
e.g. CF-Root-SGN_XX_XEN_KJ4-v5.0-CWM4.zip)
so choose accordingly
- Place the zImage file accordingly in folder 1.initial CFroot flasher /zImage folder
- Start "already-rooted.bat" and follow the instructions If you are Rooted already
OR
- Start "not-rooted-yet.bat" and follow the instructions.
Note : Just below this, where you download actual flash programme, that includes initial CF root as well i have already placed zimage accordingly.
Click to expand...
Click to collapse
edit 16Nov11 Simplified
-----------------------------------------Forget all Above and follow simple Step below------------------------------
Part Two : Final Procedure
1. I want just Root- Download This
Now Execute RunMe – follow screen instruction
(Note : Who are on Linux look to End of this post)
New method edit 19Feb12
If you fail to Root with aove method, You can try this
Keep you mobile debugging on, connect to PC and use tool mention above
2. I Want ROOT + CWM
I will do with PC (all credits goes to Chainfire for making Cf root kernel)
Which kernel You have?
(Go to Settings -> About phone -> Kernel Version. Note the string present there: 2.6.35.7-N7000XXKJ4-CL641703 Here Red is kernel version)
I have Kernel KJ1 - Download This– and Extract
I have Kernel KJ4 - Download This - and Extract
I Have Kernel KJ6/KJ7/KJ8 - Download this - and extract
I have Kernel KK1/KK2/KK3/KK4/KK5 - Download This - and Extract
I have Kernel KKA - Download This - and Extract
I have Kernel KK9 - Download This - and Extract
I have kernel KL3 - Download This - and Extract
I have Kernel KL1 - Download This - and Extract
Below mentioned are Non Rootable(to use for CWM only. You have to flash using Mobile odin), so you wont get Root from here, Read this thread, Post # 2 n 3
I have Kernel KL7 - Download
I have kernel KL8 - Download
I have kernel LA1 - Download
I Have Kernel LA3 - Download
I have kernel LA4 - Download
I have kernel LA6 - Download
I have Kernel LB1 -Download
I have Kernel LC1 - Download
NOW Ready to begin
I am Already Rooted - Execute "already-rooted.bat" and follow the instructions
I am Non-rooted - Execute "not-rooted-yet.bat" and follow the instructions.
OR
I will Go with Mobile Odin option (No PC needed)
After root with above mention method, Go to Market download this, Again Thnx to great ChainFire
https://market.android.com/details?...xLDEsImV1LmNoYWluZmlyZS5tb2JpbGVvZGluLnBybyJd
Now place CF root kernel to your Int/Ext memory, N flash with Mobile Odin Pro
Tip: Just to note that, who have to use root for application purpose e.g.Root explorer, titanium backup etc, they shud select 'I want just Root' option. these all application will work, as well stock recovery also will work like reset, wipe cache partition, wipe data
You shud only apply CWM, if really you are need to backup/restore firmware, regularly updating ROM, using ChainFire application(which need CF root)
---------------------------------------------------------------------------------------------------------------------
CF Root ICS ROM
N7000XXLPY - CF-Root-SGN_XX_OXA_LPY-v5.3-CWM5.zip
Extract till zImage N flash Kernel using Mobile Odin Pro
-----------------------------------------------------------------------------------------------------------------------
Now How I can revert back to Stock ROM/Unroot (In case of replacemet may i need)
I you have Just rooted only but not added CWM - Just Download this Extract - Execute - Rum Me unroot.bat
If You have Root + CWM - then first find out original stock kernel (zImage file)
Now place this file in zImage folder, n repeat procedure(Initial CFRoot Flasher), which you have done at time of pushing CWM by selecting I am rooted already
Now unroot with above said unrooting tool.
---------------------------------------------------------------------------------------------------------------
When No Any other method works to Root your device, use this
---------------------------------------------------------------------------------------------------------------
Note that, this will downgrade your ROM to KJ1, after that you can update it.
Download: https://rapidshare.com/files/369028110/SGN_XX_OXA_KJ1_FACTORYFS.zip Thanx to Chainfire for making it.
(special thanx to schiwa for providing premium a/c to host file)
Mirror : http://d-h.st/HJM (Thnx to Dev host for providing premium ac to XDA recognise contributor)
- Make sure your SGN is NOT connected to your computer
- Reboot your SGN into "download mode" (Vol Down + Home + Power)
- Start ODIN
- Click the PDA button, and select the "SGN_XX_OXA_KJ1_FACTORYFS.tar" file
- Connect the SGN to your computer
- Make sure "repartition" is NOT checked
- Click the START button
- Wait for the phone to reboot TWICE
- Done.
Now you have your device Rooted, Install Mobile Odin Pro n update your device to any new ROM with Mobile Odin
----------------------------------------------------------------
Root Note using Mac & Linux
---------------------------------------------------------------
Download This
- Extract on PC
- Confirm you have installed driver on PC (Kies will do it)
- Enable unknown sources in setting - application on device.
- Enable USB debugging in setting - application - development on device
- For Mac, double-click and run runmemac.sh. Or you might have to run it in terminal like this:
sh runmemac.sh
-For Linux, double-click and run runmelinux.sh. Or you might have to run it in terminal like this:
sh runmelinux.sh
Connect device N run script
Device should rebooted N you can confirm it by working superuser application on device.
Click to expand...
Click to collapse
dr.ketan can u explain it better please. I don't know how to do it
thanks in advance
refer this to install CWM with rom manager
http://www.addictivetips.com/mobile/how-to-install-clockwork-recovery-to-your-android-phone/
Edit : Rom manager not supporting Note
i already postet the same way some days ago here on the general note thread ----
http://forum.xda-developers.com/showthread.php?t=1326955
Where can I get the ADB drivers for the samsung note?
It's not in the Google USB driver package of their SDK Manager.
And do I need to load the drivers on the CDC Serial or the Samsung_Android device?
it isn't working for me...
c:\Temp\Samsung_Galaxy_Note\Root\zergRushAIO>runme
---------------------------------------------------------------
Easy rooting toolkit (v1.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using zergRush exploit
(2) install Busybox (1.18.4)
(3) install SU files (3.0.5)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
adb server is out of date. killing...
* daemon started successfully *
--- cleaning
--- pushing zergRush"
2250 KB/s (23052 bytes in 0.010s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x0002e118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Zerglings found a way to enter ! 0x18
[+] Overseer found a path ! 0x000309d8
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Overseer found a path ! 0x000309d8
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Overseer found a path ! 0x000309d8
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Overseer found a path ! 0x000309d8
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Overseer found a path ! 0x000309d8
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[-] Zerglings did not leave interesting stuff
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
2611 KB/s (1075144 bytes in 0.402s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
Click to expand...
Click to collapse
ROM version KJ4. Any ideas? Tahnk you!
---------- Post added at 03:06 PM ---------- Previous post was at 02:58 PM ----------
Second attempt worked!
c:\Temp\Samsung_Galaxy_Note\Root\zergRushAIO>runme
---------------------------------------------------------------
Easy rooting toolkit (v1.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using zergRush exploit
(2) install Busybox (1.18.4)
(3) install SU files (3.0.5)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
--- pushing zergRush"
1875 KB/s (23052 bytes in 0.012s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x0002e118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Zerglings found a way to enter ! 0x18
[+] Overseer found a path ! 0x00030610
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Overseer found a path ! 0x000309d8
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Zerglings caused crash (good news): 0x40322cd4 0x0074
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd25b15 0xafd395df
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 181 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
2120 KB/s (1075144 bytes in 0.495s)
--- correcting permissions
--- remounting /system
--- copying busybox to /system/xbin/
2099+1 records in
2099+1 records out
1075144 bytes transferred in 0.136 secs (7905470 bytes/sec)
--- correcting ownership
--- correcting permissions
--- installing busybox
--- pushing SU binary
2411 KB/s (22228 bytes in 0.009s)
--- correcting ownership
--- correcting permissions
--- correcting symlinks
--- pushing Superuser app
2439 KB/s (762010 bytes in 0.305s)
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
Click to expand...
Click to collapse
If you have the Samsung Galaxy S2, then you are in the wrong forum.
You need to be here: http://forum.xda-developers.com/forumdisplay.php?f=1055
I have not updated my signature yet, yes I own a GN.
I'm in!
Hi there,
Me too, I can confirm that the described rooting method is working fine!
At start I did have an issue with the CDC something driver wanting to be installed, but that can be solved by installing the KIES software for the phone, that can be downloaded from the Samsung website.
Regards,
Worked like a charm.... thanks!
Worked like a charm.... thanks!
Thanks for the tip. The KIES software from Samsung had the ADB driver that was needed.
And it worked very well.
You can Download KIES Here
It feels like doing startcraft on my phone. Haha.
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
--- pushing zergRush"
360 KB/s (23052 bytes in 0.062s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x0002e118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Zerglings found a way to enter ! 0x18
[+] Overseer found a path ! 0x00030610
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Overseer found a path ! 0x000309d0
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Zerglings caused crash (good news): 0x40322cd4 0x0074
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd25b15 0xafd395df
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 181 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
1919 KB/s (1075144 bytes in 0.546s)
--- correcting permissions
--- remounting /system
--- copying busybox to /system/xbin/
2099+1 records in
2099+1 records out
1075144 bytes transferred in 0.123 secs (8741008 bytes/sec)
--- correcting ownership
--- correcting permissions
--- installing busybox
--- pushing SU binary
463 KB/s (22228 bytes in 0.046s)
--- correcting ownership
--- correcting permissions
--- correcting symlinks
--- pushing Superuser app
2267 KB/s (762010 bytes in 0.328s)
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
Click to expand...
Click to collapse
I'm out!
Hi there,
Can confirm that unrooting works too.
Sadly I have to say that I must return my Note because the phone speaker went dead.
Regards,
Does it also SIM unlock the Galaxy Note?
ok for the root but i dont undestending for the CWM.
thanks
Plz who have successfully rooted, share your experience here.
have anybody installed ROM manager after ROOT?
Wifi tethering working ?
any error reported?
I know that someone probably asked this but can someone tell me how to root official ICS ?
and i prefer if u have tried it already.
Or at least tell me if it can be rooted at all
Thank you.
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=1520469
japinder said:
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=1520469
Click to expand...
Click to collapse
That one worked for me.
yes
Yes I tried it the tab just froze and i restarted it but nothing happened
I used Civato's guide in his flexreaper rom thread, and it worked just fine. Follow all instructions to the letter.
japinder said:
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=1520469
Click to expand...
Click to collapse
Worked for me with official update.
worked
At the first time i have done something wrong so it didn't work but now that i have done it right it worked thanks alot.
Can you unroot it the same way?
speeddaddy said:
Can you unroot it the same way?
Click to expand...
Click to collapse
2nd.... this would be good to know...
If you got stok ICS running and you got the unlocked booltoader and custom recovery running you can flash the patched boot.img (kernels from Flexreaper thread) for ICS bootloader users , they give you full root without any other proces except installing superuser app. No need to use the easy root tool then.
If you want to go back flash the stock boot.img back or restore it from a nandroid backup , remove the super user app and you are root less.
japinder said:
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=1520469
Click to expand...
Click to collapse
everything works... but in the end I get:
./root.sh: line 282: syntax error: unexpected end of file
when I try again I get:
Is your device listed? (y/n) y
[: 144: y: unexpected operator
[+] Uploading exploit
1020 KB/s (37273 bytes in 0.035s)
[+] Uploading busybox
1296 KB/s (821340 bytes in 0.618s)
[+] Setting permissions
[+] Creating directories
[+] Uploading files...
[: 164: ==: unexpected operator
[: 173: 0: unexpected operator
[: 178: 0: unexpected operator
[: 183: 0: unexpected operator
[: 188: 0: unexpected operator
[: 193: 0: unexpected operator
./root.sh: 281: Syntax error: end of file unexpected (expecting "fi")
So, just to give a brief intro here... I used to have a DX, first buying it way back in its Eclair days, but have since (regretfully) moved to a D3. Trying to make the best of Moto's D3 flop, I've become pretty active over in the D3 sub-forum and have begun to learn the basics (I stress this, I ported a Bell Canada 2.3.6 ROM to the US D3 with 2.3.4, added light theming and 1% battery mods with assistance) of ROM creation and theming. I'm comfortable with RSD Lite and other programs like that.
Now, for this DX, I'm attempting to root it with Pete's 1 Click (Verision 1.06) which says it has worked on the DX. It fails on Step 3 pushing SU, BusyBox, etc. I thought the MotoFail method for the D4, Bionic, etc. which works for the D3 may work, so I attempted that, but it too failed on the same step. Just this morning I updated it to OTA 4.5.621, could this be the issue?
My friend has since crossed over to the dark side (iOS), so I want to make a nandroid backup of this phone as is, back up his SD cards, then wipe everything and play around with ICS on the DX since ICS on the D3 isn't a daily driver yet IMO, but I still want to mess with ICS.
Any advice about rooting .621? Also, does the DX only have BootStrap, or does a SafeStrap style hijack exist as well?
EDIT:
Ok, after some more Google'ing, I've found I need to root with Linux, and not windows because I've "accidentally" taken .621 OTA. I have a second HDD in my desktop with Ubuntu 12.04, so I should be able to follow a guide to root via Linux from that machine, correct?
redsox985 said:
So, just to give a brief intro here... I used to have a DX, first buying it way back in its Eclair days, but have since (regretfully) moved to a D3. Trying to make the best of Moto's D3 flop, I've become pretty active over in the D3 sub-forum and have begun to learn the basics (I stress this, I ported a Bell Canada 2.3.6 ROM to the US D3 with 2.3.4, added light theming and 1% battery mods with assistance) of ROM creation and theming. I'm comfortable with RSD Lite and other programs like that.
Now, for this DX, I'm attempting to root it with Pete's 1 Click (Verision 1.06) which says it has worked on the DX. It fails on Step 3 pushing SU, BusyBox, etc. I thought the MotoFail method for the D4, Bionic, etc. which works for the D3 may work, so I attempted that, but it too failed on the same step. Just this morning I updated it to OTA 4.5.621, could this be the issue?
My friend has since crossed over to the dark side (iOS), so I want to make a nandroid backup of this phone as is, back up his SD cards, then wipe everything and play around with ICS on the DX since ICS on the D3 isn't a daily driver yet IMO, but I still want to mess with ICS.
Any advice about rooting .621? Also, does the DX only have BootStrap, or does a SafeStrap style hijack exist as well?
EDIT:
Ok, after some more Google'ing, I've found I need to root with Linux, and not windows because I've "accidentally" taken .621 OTA. I have a second HDD in my desktop with Ubuntu 12.04, so I should be able to follow a guide to root via Linux from that machine, correct?
Click to expand...
Click to collapse
Correct.
©2012 Galaxy Note i717
So, for tethering, all I need is WiFi Tether from the Play Store? On the D3, we have to use a Moto proprietary program called RadioComm to rewrite the radio's data type signatures so that all 3G data through the phone looks as if it's phone use 3G and not tethered data.
Also, I'm looking for an ICS ROM... Suggestions?
Lastly, I did the Linux/Ubuntu SBF to the Milestone X, then ran ZergRush from Windows, but don't have root access.
Code:
----------------------------------
Easy rooting toolkit
created by DooM
using exploit zergRush (Re
Credits go to all those involve
----------------------------------
[*] This script will:
(1) root ur device using late
(2) install Busybox (1.18.4)
(3) install SU files (binary:
(4) some checks for free spac
(will remove Google Maps
[*] Before u begin:
(1) make sure u have installe
(2) enable "USB DEBUGGING"
from (Menu\Settings\App
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\App
(4) [OPTIONAL] increase scree
(5) connect USB cable to PHON
(6) skip "PC Companion Softwa
----------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or d
--- pushing zergRush
68 KB/s (23060 bytes in 0.327s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 l
[**] (C) 2011 Revolutionary. All r
[**] Parts of code from Gingerbrea
--- WAITING FOR DEVICE TO RECONNEC
if it gets stuck over here for a l
disconnect usb cable and reconn
toggle "USB DEBUGGING" (first d
--- DEVICE FOUND
--- pushing busybox
3558 KB/s (1075144 bytes in 0.295s
--- correcting permissions
--- remounting /system
mount: permission denied (are you
--- checking free space on /system
214 KB/s (439 bytes in 0.002s)
df: /mnt/secure/asec: Permission d
--- Free space on /system : 92% by
test: 92%: bad number
--- NOT enough free space on /syst
--- making free space by removing
rm: can't remove '/system/app/Maps
--- copying busybox to /system/xbi
/system/xbin/busybox: cannot open
--- correcting ownership
Unable to chmod /system/xbin/busyb
--- correcting permissions
Unable to chmod /system/xbin/busyb
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/sys
--- correcting ownership
Unable to chmod /system/bin/su: No
--- correcting permissions
Unable to chmod /system/bin/su: No
--- correcting symlinks
rm failed for /system/xbin/su, Rea
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.ap
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
I seem to be hitting some errors with ZergRush.
Phone info:
4.5.604.MB809.ACG-nTelos.en.US
Milestone X
2.3.5
BP_C_01.09.15P
4.5.1_57_MX2-34
redsox985 said:
So, for tethering, all I need is WiFi Tether from the Play Store? On the D3, we have to use a Moto proprietary program called RadioComm to rewrite the radio's data type signatures so that all 3G data through the phone looks as if it's phone use 3G and not tethered data.
Also, I'm looking for an ICS ROM... Suggestions?
Lastly, I did the Linux/Ubuntu SBF to the Milestone X, then ran ZergRush from Windows, but don't have root access.
Code:
----------------------------------
Easy rooting toolkit
created by DooM
using exploit zergRush (Re
Credits go to all those involve
----------------------------------
[*] This script will:
(1) root ur device using late
(2) install Busybox (1.18.4)
(3) install SU files (binary:
(4) some checks for free spac
(will remove Google Maps
[*] Before u begin:
(1) make sure u have installe
(2) enable "USB DEBUGGING"
from (Menu\Settings\App
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\App
(4) [OPTIONAL] increase scree
(5) connect USB cable to PHON
(6) skip "PC Companion Softwa
----------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or d
--- pushing zergRush
68 KB/s (23060 bytes in 0.327s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 l
[**] (C) 2011 Revolutionary. All r
[**] Parts of code from Gingerbrea
--- WAITING FOR DEVICE TO RECONNEC
if it gets stuck over here for a l
disconnect usb cable and reconn
toggle "USB DEBUGGING" (first d
--- DEVICE FOUND
--- pushing busybox
3558 KB/s (1075144 bytes in 0.295s
--- correcting permissions
--- remounting /system
mount: permission denied (are you
--- checking free space on /system
214 KB/s (439 bytes in 0.002s)
df: /mnt/secure/asec: Permission d
--- Free space on /system : 92% by
test: 92%: bad number
--- NOT enough free space on /syst
--- making free space by removing
rm: can't remove '/system/app/Maps
--- copying busybox to /system/xbi
/system/xbin/busybox: cannot open
--- correcting ownership
Unable to chmod /system/xbin/busyb
--- correcting permissions
Unable to chmod /system/xbin/busyb
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/sys
--- correcting ownership
Unable to chmod /system/bin/su: No
--- correcting permissions
Unable to chmod /system/bin/su: No
--- correcting symlinks
rm failed for /system/xbin/su, Rea
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.ap
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
I seem to be hitting some errors with ZergRush.
Phone info:
4.5.604.MB809.ACG-nTelos.en.US
Milestone X
2.3.5
BP_C_01.09.15P
4.5.1_57_MX2-34
Click to expand...
Click to collapse
Mine is actually almost bricked right now. I used gummy ics but I'm going to use blackice or something like that. As for tethering I don't know, as this is just my music player.
©2012 Galaxy Note i717
Still can't acquire root... Ideas?
redsox985 said:
Still can't acquire root... Ideas?
Click to expand...
Click to collapse
I literally just went through this process and it worked perfectly. Try SBFing to .621 again then do the Ubuntu steps again then use zergrush v3. That's exactly what I did.
©2012 Galaxy Note i717
Orange_furball said:
I literally just went through this process and it worked perfectly. Try SBFing to .621 again then do the Ubuntu steps again then use zergrush v3. That's exactly what I did.
©2012 Galaxy Note i717
Click to expand...
Click to collapse
I'm supposed to SBF to .621, then to Milestone X .605 via Ubuntu, then ZergRush you're saying? I also tried the live CD method to no avail.
redsox985 said:
I'm supposed to SBF to .621, then to Milestone X .605 via Ubuntu, then ZergRush you're saying? I also tried the live CD method to no avail.
Click to expand...
Click to collapse
Yes that is what I did
©2012 Galaxy Note i717
Ok, so I did the RSD Lite .621 SBF, that worked, I went to Linux, flashed that Milestone X SBF, went back to Windows, ran ZergRush v4, same damn error...
redsox985 said:
Ok, so I did the RSD Lite .621 SBF, that worked, I went to Linux, flashed that Milestone X SBF, went back to Windows, ran ZergRush v4, same damn error...
Click to expand...
Click to collapse
Do you have the drivers installed? Also, is USB debugging and unknown sources checked?
©2012 Galaxy Note i717
Orange_furball said:
Do you have the drivers installed? Also, is USB debugging and unknown sources checked?
©2012 Galaxy Note i717
Click to expand...
Click to collapse
Yep, yep, and yep. Would I possibly be able to manually root via ADB? I have it set up and connected now, the problem lies in that I can't really find much about manual roots any longer.
redsox985 said:
Yep, yep, and yep. Would I possibly be able to manually root via ADB? I have it set up and connected now, the problem lies in that I can't really find much about manual roots any longer.
Click to expand...
Click to collapse
I don't think you can manually root on .621. Have you tried another computer, or have you tried zergrush v3?
©2012 Galaxy Note i717
Just go here and read the instructions. Once you've taken the .621 update it's a bit of a process to regain root, but totally doable.
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
Or here.
http://rootzwiki.com/topic/19318-important-information-regarding-621-system-update/
SaurusX said:
Just go here and read the instructions. Once you've taken the .621 update it's a bit of a process to regain root, but totally doable.
http://rootzwiki.com/topic/19318-important-information-regarding-621-system-update/
Click to expand...
Click to collapse
This is what he is trying to do. Root the .621 using Ubuntu.
©2012 Galaxy Note i717
SaurusX said:
Just go here and read the instructions. Once you've taken the .621 update it's a bit of a process to regain root, but totally doable.
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
Or here.
http://rootzwiki.com/topic/19318-important-information-regarding-621-system-update/
Click to expand...
Click to collapse
I took the .621 OTA, booted Ubuntu 12.04 from my 2nd HDD, SBF'd to Milestone X in Ubuntu, went over to Windows 7 64bit HP, ran ZergRush v4, ZergRush v3, Pete's Moto Root Tools, and MotoFail, all of which failed to root. I then used RSD Lite to apply the .621 SBF (I'm now questioning if I should've done this via Ubuntu), went into Ubuntu, did the MX SBF, tried all rooting methods above and failed.
Then I tried rooting via ADB and I believe I successfully pushed su, busybox, and Superuser.apk to /data/local via ADB, but when issuing "adb remount", I'm unable to mount /system as read-write. I'm applying the .621 SBF via RSD Lite currently and having my second guesses about this doing this via RSD now...
This one via RSD 1FF-p3a_shadow_cdma_shadow-user-2.3.4-4.5.1_57_DX8-51-120111-test-keys-signed-Verizon-US.sbf
redsox985 said:
I took the .621 OTA, booted Ubuntu 12.04 from my 2nd HDD, SBF'd to Milestone X in Ubuntu, went over to Windows 7 64bit HP, ran ZergRush v4, ZergRush v3, Pete's Moto Root Tools, and MotoFail, all of which failed to root. I then used RSD Lite to apply the .621 SBF (I'm now questioning if I should've done this via Ubuntu), went into Ubuntu, did the MX SBF, tried all rooting methods above and failed.
Then I tried rooting via ADB and I believe I successfully pushed su, busybox, and Superuser.apk to /data/local via ADB, but when issuing "adb remount", I'm unable to mount /system as read-write. I'm applying the .621 SBF via RSD Lite currently and having my second guesses about this doing this via RSD now...
Click to expand...
Click to collapse
Why don't you sbf in windows using rsd lite back to .621 Droid x then do the Ubuntu followed by zergrush
©2012 Galaxy Note i717
Orange_furball said:
Why don't you sbf in windows using rsd lite back to .621 Droid x then do the Ubuntu followed by zergrush
©2012 Galaxy Note i717
Click to expand...
Click to collapse
redsox985 said:
I then used RSD Lite to apply the .621 SBF (I'm now questioning if I should've done this via Ubuntu), went into Ubuntu, did the MX SBF, tried all rooting methods above and failed.
Click to expand...
Click to collapse
I did...?
redsox985 said:
I did...?
Click to expand...
Click to collapse
Try it again maybe?
©2012 Galaxy Note i717
Oh man I feel for you redsox985. I love my Droid x and I wish that I could help. But the only thing I can reccomend is try sbfing in windows with the newest version of red lite. And then when it is done or tries to reboot, or then bootloops is to unplug the phone. Boot into the stock recovery or whatever you call it (you get to it by pressing the home and power until you see the android dude and exclamation point. Then you push either search or back. It varies with the version.) Then you want to wipe data and cache. Then try rebooting. It has worked for me in the past when I have come out of 2nd init roms.
If you have tried that then I am sorry. I can't help anymore.
OK here we go... I hope...
1. Boot into windows. I used 7, but whatever.
2. Then download rsd lite 5.x.x and download the Droix X .621 sbf file.
3. Enter download mode on the dx and connect it to the computer.
4. Sbf your phone in rsd lite to .621.
5. Unplug your phone.
6. Pull the battery of your phone.
7. Hold down POWER AND HOME until you see the triangle with exclamation point.
8. Click both the VOLUME UP AND DOWN buttons
9. This is stock recovery.
10. Wipe data/Factory reset.
11. Reboot.
12. Verify it works (connect to wifi, browse a few sites, etc.)
13. Start Ubuntu and follow the guide for sbfing to the Milestone X file.
***back to windows****
14. Root using Zergrush *****v3*****!!!!
15. Install the bootstrap .apk
***on the phone****
16. Install clockwork mod
17. Flash whatever you want*
*Nothing below 2.3.5. Definitely NO Froyo
If this doesn't work I'll walk you through it while IMing or texting or something. If I can follow the steps I can figure it out.
©2012 Galaxy Note i717
IF THIS HELPS... HIT "THANKS"!!!
Hi,
I wrote a little script with some nice utilities to customize the Kindle Fire HDX 8.9.
Options available :
Superuser
Remove signature check
Install Google Apps
Fix wallpaper
It runs under Linux, and you need to have java, jar, sed, wget, adb and aapt set up on your computer.
To use it, plug your device and enable adb.
Extract the archive and run hdx.sh in a terminal.
Everything is not perfect, but it seems to work pretty good for me
Thanks to everybody who worked on the tools I use in this script.
Is play store working for downloading
Sent from my SPH-L900 using xda app-developers app
Tanks to cpasjuste tips it is
I know u mentioned Linux us it possible to run this from windows
Sent from my SPH-L900 using xda app-developers app
I have the same question... can we run this script under windows somehow. I already have root, gmail and music working... play store can't connect though... I also used adb to do the wallpaper fix and it says it is applied but nothing seems to have happened. Still no wallpapers anyway. btw, I also have superuser and busybox installed too.
Same question here. Also, can the wallpaper fix be used stand alone and will we be able to have wallpapers on stock launcher? I am on 7“
Sent from beneath my invisibility cloak
Judging by the content of the .sh file, i believe a .bat file can be written to run on windows... however, it would be prudent to do it in a safestrap rom slot, you know, just in case something goes wrong...
Thanks for sharing @Ptiwee !
Ill try manual execution of some of the steps in your guide (most especially on the ones related to DownloadProvider) and see how it goes !
Cheers!
If you want just the wallpaper fix I thought I'd mention my fix still works on the hdx that I designed for the HD, though you may have to install busybox on your kindle first.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
It should be possible to use it on Windows, though you have to find the equivalent for all programs used inside (especially for sed ...)
I don't have time to care about it before Christmas ...
stunts513 said:
If you want just the wallpaper fix I thought I'd mention my fix still works on the hdx that I designed for the HD, though you may have to install busybox on your kindle first.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Do i have to be rooted?
Sent from beneath my invisibility cloak
Will this allow Amazon Appstore to work?
It doesn't look like it as you've used the same cm10 apks, but I thought it wouldn't hurt to ask before I go through the trouble of trying it out...
Sent from my KFTHWI using Tapatalk 4
Hanzo.Hasashi said:
Do i have to be rooted?
Click to expand...
Click to collapse
You'll need to root before applying the wallpaper fix
Sent from my KFTHWI using Tapatalk 4
I have tried this and after applying the Google Apps 3rd option it rebooted and now its stuck with the kindle fire logo and not coming up anymore
The device answers to adb commands (lists up with adb devices) and reboots with "adb reboot fastboot" and/or "adb reboot recovery"
Although resetting with the recovery to factory defaults doesnt help...
Anyone know whats happening? (I cant afford to send it back to US as I live in Colombia)
Sorry for the double post
Root works, but when trying the signature check (I just went past 1-2-3-4 and 5 without checking for errors I was just too sleepy)
It gives me this:
Waiting for device ...
Pulling files ...
8403 KB/s (3479504 bytes in 0.404s)
335 KB/s (27576 bytes in 0.080s)
5837 KB/s (1083168 bytes in 0.181s)
6180 KB/s (1505152 bytes in 0.237s)
9411 KB/s (10893168 bytes in 1.130s)
6375 KB/s (1398376 bytes in 0.214s)
1422 KB/s (130136 bytes in 0.089s)
4940 KB/s (765056 bytes in 0.151s)
7 KB/s (313 bytes in 0.040s)
1 KB/s (72 bytes in 0.040s)
Deodexing ...
Exception in thread "main" org.jf.util.ExceptionWithContext: services.odex is not an apk, dex file or odex file.
at org.jf.dexlib2.DexFileFactory.loadDexFile(DexFileFactory.java:111)
at org.jf.dexlib2.DexFileFactory.loadDexFile(DexFileFactory.java:54)
at org.jf.baksmali.main.main(main.java:247)
Editing /com/android/server/pm/PackageManagerService.smali ...
./hdx.sh: line 40: smali/com/android/server/pm/PackageManagerService.smali.new: No such file or directory
mv: cannot stat ‘smali/com/android/server/pm/PackageManagerService.smali.new’: No such file or directory
Recompiling ...
UNEXPECTED TOP-LEVEL EXCEPTION:
java.lang.RuntimeException: Cannot find file or directory "smali"
at org.jf.smali.main.main(main.java:174)
./hdx.sh: line 44: jar: command not found
rm: cannot remove ‘smali’: No such file or directory
rm: cannot remove ‘classes.dex’: No such file or directory
Reodexing on device...
7 KB/s (313 bytes in 0.040s)
push: scripts/remove_signature_check/dexopt-wrapper -> /data/local/tmp/dexopt-wrapper
push: scripts/remove_signature_check/odexsign.sh -> /data/local/tmp/odexsign.sh
2 files pushed. 0 files skipped.
70 KB/s (5822 bytes in 0.081s)
Signing and replacing services.odex ...
--- BEGIN 'services.jar' (bootstrap=0) ---
--- waiting for verify+opt, pid=6931
--- would reduce privs here
--- END 'services.jar' --- status=0xff00, process failed
20+0 records in
20+0 records out
20 bytes transferred in 0.001 secs (20000 bytes/sec)
Cleaning ...
Done, push any key to continue ...
Click to expand...
Click to collapse
Any ideas why services.odex is not what its looking for? (Maybe someone could upload it?)
Guys, if ANY PART OF THIS FAILS & YOUR DEVICE REBOOTS, IT WILL BRICK THE HDX.
Several people are having issues (maybe running this in a terminal on device or via mnty) that leads to the endless bootloop. This can also occur if there are files left in Dalvik cache from the old download manager & UI.
Use caution & common sense when trying to modify your device. My brother works for Amazon & has told me that they are supposed to start cracking down on device returns this week. If you mess your device up because you don't really know what you are doing (much of this is early developmental stage) there is an increasing chance that you will be stuck with a non-functioning device &/or out several hundred dollars.
Poesini said:
Sorry for the double post
Root works, but when trying the signature check (I just went past 1-2-3-4 and 5 without checking for errors I was just too sleepy)
It gives me this:
Any ideas why services.odex is not what its looking for? (Maybe someone could upload it?)
Click to expand...
Click to collapse
If you are still stuck in bootloop, I can help you. Based on your post, I bricked on purpose & was able to recover. Hit me up, or check out my thread in the HDX General forum section.
GSLEON3 said:
If you are still stuck in bootloop, I can help you. Based on your post, I bricked on purpose & was able to recover. Hit me up, or check out my thread in the HDX General forum section.
Click to expand...
Click to collapse
WOW
FKN WOW
You saved my life man you just saved my life... Followed your guide and now I have my device back again YAY
Thanks a lot man
Jocky & I probably saves 100's of Kaisers back in the WM days. Been a while since I've had time to really get into Android firmware, but I can still piddle with the best of the average, lol...
Glad you are fixed .
Now you can mod the build.prop & start anew if so desired. What I did. Once you've used the exploit, SU is almost garunteed to stay, at least until Amz patches it in an update.
Sent from my Nexus 7 using XDA Premium HD app
Ptiwee said:
Hi,
I wrote a little script with some nice utilities to customize the Kindle Fire HDX 8.9.
Options available :
Superuser
Remove signature check
Install Google Apps
Fix wallpaper
It runs under Linux, and you need to have java, jar, sed, wget, adb and aapt set up on your computer.
To use it, plug your device and enable adb.
Extract the archive and run hdx.sh in a terminal.
Everything is not perfect, but it seems to work pretty good for me
Thanks to everybody who worked on the tools I use in this script.
Click to expand...
Click to collapse
Hi,
I tried to install the Google Apps with the scripts, and now every time I boot up it shows "Kindle is upgrading ...."
After a while it still boot up successfully. But it is taking longer time.
Also, the Google Play store only works for me once after I first reboot. Afterward, it app closes itself right after I click on it.
Reboot does not help.
Did I do anything wrong here? Any idea how I can fix it?
Thanks.
I'm back from Christmas celebrations, sorry ...
As GSLEON3 stated, it is important to use those scripts safely. I put them here for crazy people who know what they are doing
The Kindle update is a known bug, it doesn't disturb me a lot but maybe I'll try to find a solution
For the Google Play store not working, did you disabled the signature check ?