Database Users

[solved] SD write failing for rooting

So my NookTouch finally arrived!
But I'm having trouble writing images to a SD card.
It's a 16gb micro SD HC class 6 card...
i thought that would be ok?
Windows Image writer says `Not enough space` so I used dd for windows but after this the disk isn't readable. The same for linux (remembered to use bs=1M).
edit::
Solved answer - confusion using windows tools, don't really know why it wasn't working but it could have been due to an incorrect dd command on linux beforehand.
You need to write to /dev/sdcardRoot (aka masterbootpartition) rather than /dev/sdcard1 (partition1). After you've rooted though and written the image you can format the card and partition the SD card.

I had a similar problem with my 5 in 1 built in card reader.
Some apps would say "not enough space" while some would write the img without complaints, but the Nook wouldn't boot it, no matter what.
I ended up pushing the image file to my phone (X10) and using that to write the image to the sd card, worked perfectly.

Are you using WinImage?

Thanks for fast reply!
Verfied the image is ok with winimage.
Wierd. After writing TouchNooter to sd card via the sd card drive in the laptop the card is no longer readable. After putting it in the NookTouch the nook can't see it either and I can't get linux mount it. But... with the card in the Nook and USB plugged in I get 2 drives come up; `Nook` and `TouchNooter`
Nook software version is `1.0.0`.
In linux the disk looks like this:
Code:
Disk /dev/sdb: 251 MB, 251641856 bytes
8 heads, 60 sectors/track, 1023 cylinders
Units = cylinders of 480 * 512 = 245760 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
Disk /dev/sdc: 16.0 GB, 16038952448 bytes
128 heads, 32 sectors/track, 7647 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 38 77808 c W95 FAT32 (LBA)
/dev/sdc3 7 7 0 0 Empty
Partition 3 does not end on cylinder boundary.
[email protected]:/media/WindowsStorage/download/nook$
With WinImage I can read the contents of the image but if I try to write it I get `The current image format is not supported by the disk drive` --- ***correction, it's writing now after I reformatted the card***....
now testing...
`nook is starting up...` aha `Rooted forever!!` hmm.. seems to be taking a very long time....
ok, nothing's happening... i wonder if it's turned on or crashed! ok trying usb now... ah, got a different device recognised by windows (omap3630).. trying apb etc...
perhaps I should be using noogie only for the touch though... hmm...
right, need to find the omap3630 driver in the android sdk to get those 7 partitions mounted... this is my first android device I've used... no usb driver listed in the sdk under available packages.. perhaps I should try linux...

Ok, got the shell. What next to install? I'll have a search.
The confusing thing was the android sdk. It took me a while to find the USB driver comes through via google's distro service on Windows and that the adb command is in there too. The location of the USB driver has also moved to the google/usbdriver subdirectory now too.
Next stop, trying to install some android .apk's...
Thanks one and all!
edit::
I'll use this as a diary for a moment to note what I'm finding until I'm sure enough to put it in the Wiki.
In general I'm finding some things that work on the color work on the touch but not all. VNCServer works but we only have /dev/input/event0-2 - the server notes the input clicks but doesn't do anything about them ("injectTouchEvent (x=0, y=0, down=1)" even when specifying -k trying each of those events...
this could be related to the NookTouch using infared rather than a touchscreen. Perhaps there's a new B&N dev file in there rather than a custom resident running program or something.
VNCViewer on the NookTouch seems to work but personally I couldn't get it to connect to my server. I'll try linux to confirm.
WiFi locker doesn't work, complaining that's it's an incompatible app: http://nookdevs.com/Nook_WiFi_Locker the wiki is the only place for a download link, there appears to be no mention now of it on the nooktools page:
Code:
E:\ProgramFiles\androidSDK\platform-tools>adb install "h:\nookWifiLocker.apk"
503 KB/s (40277 bytes in 0.078s)
pkg: /data/local/tmp/nookWifiLocker.apk
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
E:\ProgramFiles\androidSDK\platform-tools>
Plugging in my USB stops the nook turning off while using adb though. Need to turn off wifi and connect over usb...
Nooklets look like a great idea - could it be scripted to allow direct access to webpages saved via scrapbook extention for firefox?
Other things to improve the wiki:
-suggest putting adb.exe in path
Any problems?
-because I don't have any other android devices I can't see how to get access to apk's from android market... http://phandroid.com/2011/02/04/sol...-android-phones-associated-with-this-account/ "No phones associated with this account"
This confused me:
adb -d shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb push NookColorTools_0.2.apk /system/app
adb reboot
Click to expand...
Click to collapse
- was that an old way to install apps before `adb install`? Because any app I install via adb install isn't listed in /system/apps, yet it is installed because if I try to install again it tells me so...
edit: note for myself regards the confusion over google accounts, gmail and missing libaries:
Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY]
To set this up correctly, there are 2 key files that need to be copied to the system:
com.google.android.maps.xml
com.google.android.maps.jar
These files are located in the any of these google app packs:
http://android.d3xt3r01.tk/cyanogen/gapps/gapps-gb-20110120-signed.zip
http://goo-inside.me/gapps/gapps-gb-20110120-signed.zip
http://android.local.host.name/gapps/gapps-gb-20110120-signed.zip
After unzipping any of these files, you want to copy the files to your system, like-ah-so:
adb remount
adb push system/etc/permissions/com.google.android.maps.xml /system/etc/permissions
adb push system/framework/com.google.android.maps.jar /system/framework
adb reboot
Read more: http://nookdevs.com/Honeycomb_Google_Apps_and_Market#ixzz1ZUFM1yei
Under Creative Commons License: Attribution Non-Commercial Share Alike
Click to expand...
Click to collapse
this probably works better than:
http://senk9.wordpress.com/2010/12/03/how-to-install-google-apps-gapps-on-your-android-device-phone/

jago25_98 said:
- was that an old way to install apps before `adb install`? Because any app I install via adb install isn't listed in /system/apps, yet it is installed because if I try to install again it tells me so...
Click to expand...
Click to collapse
No
adb install (or Market for that sake) will push apps to /data/app where apps normally reside.
/system/app is where the pre-packaged apps normally live, some choose to put them there to save space, but there might be other differences as I've seen that some apps needs to be put there in order to work properly .. haven't really looked into it tho.

/data/app, ah ok thanks Ros
I see you're on Netcom. Are they still super expensive? I was on pay as you go on holiday in Norway and man they still had per mb charging for both netcom and telenor when I was there, it was super expensive!
What I don't understand is how I'm supposed to install the market app... in order to get access to the market, seeing as I don't have another android device... the market apk says it needs some kind of dependency, but I can't find any mention of this, or get adb to tell me what the dependency is I need to satisfy
...
I must have plugged and unplugged the usb port a 50x already... need a port saver I can tell it's going to break quick!

jago25_98 said:
/data/app, ah ok thanks Ros
I see you're on Netcom. Are they still super expensive? I was on pay as you go on holiday in Norway and man they still had per mb charging for both netcom and telenor when I was there, it was super expensive!
Click to expand...
Click to collapse
Sorry for the late reply mate
I have no idea when it comes to personal plans, but neither one of them is particularly bad when it comes to business plans.
Ofc they make a lot of money on people not choosing the right plans and services for their needs, but if you do it right it's not bad at all
---------- Post added at 01:17 AM ---------- Previous post was at 01:10 AM ----------
jago25_98 said:
What I don't understand is how I'm supposed to install the market app... in order to get access to the market, seeing as I don't have another android device... the market apk says it needs some kind of dependency, but I can't find any mention of this, or get adb to tell me what the dependency is I need to satisfy
Click to expand...
Click to collapse
Market requires a ****load of stuff in order to work at all.
A successful TouchNooter should give you Market access assuming you followed the instructions (logging into youtube with your gmail account etc)
Problem with TouchNooter Market is that search doesn't work, so you have to use a web browser to log into market and push the apps you want to your Nook.

[24sept12]How to Root/Unroot Samsung Galaxy Note + CWM

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?

Motochopper unauthorized access to system

Hello
Im trying to root my Samsung Galaxy S4 i9505 factory unlocked international version using motochopper. The last step is being prevented by the phone with a prompt on the phone that says "...unauthorized access to file system was prevented...". `Superuser has been installed but cannot update the binary and my device is still not rooted.
this is what is says in terminal at the end after a second attempt:
*] Pushing root tools...
3361 KB/s (366952 bytes in 0.106s)
4677 KB/s (1867568 bytes in 0.389s)
4738 KB/s (1578585 bytes in 0.325s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
[*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.
[*] Cleaning up...
[*] Exploit complete. Press enter to reboot and exit.
please help
thank you
Hani

This is a screenshot of what it does on my phone to prevent it from rooting
haceleven said:
Hello
Im trying to root my Samsung Galaxy S4 i9505 factory unlocked international version using motochopper. The last step is being prevented by the phone with a prompt on the phone that says "...unauthorized access to file system was prevented...". `Superuser has been installed but cannot update the binary and my device is still not rooted.
this is what is says in terminal at the end after a second attempt:
*] Pushing root tools...
3361 KB/s (366952 bytes in 0.106s)
4677 KB/s (1867568 bytes in 0.389s)
4738 KB/s (1578585 bytes in 0.325s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
[*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.
[*] Cleaning up...
[*] Exploit complete. Press enter to reboot and exit.
please help
thank you
Hani
Click to expand...
Click to collapse

haceleven said:
This is a screenshot of what it does on my phone to prevent it from rooting
Click to expand...
Click to collapse
use CF-auto root method

I am using a mac so I can't run odin..
samersh72 said:
use CF-auto root method
Click to expand...
Click to collapse

haceleven said:
I am using a mac so I can't run odin..
Click to expand...
Click to collapse
if you have one of new firmwares for I9505 installed, i guess that Motochopper will not succeed.

iptrba been
What can I do instead using mac?
samersh72 said:
if you have one of new firmwares for I9505 installed, i guess that Motochopper will not succeed.
Click to expand...
Click to collapse

haceleven said:
What can I do instead using mac?
Click to expand...
Click to collapse
use heimdall instead of odin for mac (no idea how it works)
or get a window machine and use odin

[HDX 8.9] Root, google apps and wallpaper fix

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 ?

R1 HD Amazon Bootloader unlock method

BOOTLOADER UNLOCK METHOD 1
Hi Guys thanks to a team effort the Amazon R1 HD has root access with SP Flash Tool and TWRP recovery image.
I went ahead with the help of @jcase and unlocked the bootloader because i wanted full access.
What i did is put together this script that will walk you through the steps to unlocking your Amazon R1 HD bootloader.
Steps are simple you just download this script that i created and click on the batch file once you have extracted it to your desktop. Follow the script it will walk you through everything.
Note Root access is required to use the script and you can watch a video on how to root the device below. My Script as been updated to work on Linux Mac or WIndows
Download Files Here
BLU-R1-HD-Amazon-Bootloader-Unlock.zip
How to unlock the bootloader video
<Mod Edit: Link removed for promoting affiliate sales link.>
How to root and install twrp recovery video
<Mod Edit: Link removed for promoting affiliate sales link.>
Here are the steps to check if your bootloader is unlocked since people are asking. With the device turned on and adb debugging working. Run these commands in terminal or command window
Code:
adb reboot bootloader
Once in fastboot mode run this command to check if unlocked.
Code:
fastboot getvar all
It will return yes for unlock and no for locked.
BOOTLOADER UNLOCK METHOD 2
View attachment 3825569
Steps
1. Download SP-Flash-Tool-bootloader-unlock.zip
2. Extract the SP-Flash-Tool-bootloader-unlock.zip to your desktop. Note 7zip is great to extract files.
3. lauch Flash_tool.exe
4. select scatter-loading and browser to load MT6735_Android_scatter_R1_Unlock.txt
5. click download button to start.
6. now plug your phone into the computer. to boot the device to preloader and start the flash. You can do it two ways: 1. power off the phone and flash will start or 2. From a powered off stat power on the device while plugged into the computer. either way will start the sp flash tool.
7. once the flash is complete which should take seconds you can unplug the device and reboot it. Congrats you can now unlock the bootloader like any normal device now.
WARNING UNLOCKING YOUR BOOTLOADER WILL WIPE DATA FACTORY RESET THE DEVICE
How to unlock the bootloader now that you have turned on this feature.
1. power off the device
2. holder volume up and power until you are at the boot menu with recovery fastboot and normal as options scroll with volume up to fastboot then press power button to select
3. once in fastboot mode you will need to option a command window on your computer and make sure you have your adb and fastboot files
4. cd to the folder with your adb and fastboot files then run these commands
5. to maks sure your devices are working correctly
Code:
fastboot devices
6. to unlock the bootloader
Code:
fastboot oem unlock
7. follow the directions on your device screen. once it is finished unlocking you can check it with
Code:
fastboot getvar all
8. Next to reboot the device use
Code:
fastboot reboot
thats it your bootloader is unlocked
Note: if you have twrp recovery install and unlock your bootloader with METHOD 2 the device will try and boot to recovery and wipe data which will fail because you and twrp installed.
The only way to fix this is to boot to fastboot mode and run this command
Code:
fastboot format userdata
then just reboot out of fastboot mode and the device will boot up.
Code:
fastboot reboot
Need help with these commands check out this video jump ahead to 6min 45sec to see commands above
<Mod Edit: Link removed for promoting affiliate sales link.>
For More info check HERE

Nice job!
Subbed to your YouTube channel!

Awesome. Can't wait for that Linux version!

triggerlord said:
Nice job!
Subbed to your YouTube channel!
Click to expand...
Click to collapse
thank buddy glad you liked it

Video tut is so much better than just typing out the steps.
good job.

Tomsgt said:
thank buddy glad you liked it
Click to expand...
Click to collapse
--------------------------------------------------------------------------------
[*] now that the device is in fastboot mode we are going to unlock the
[*] bootloader. on the next screen on your phone you will see [*] PRESS THE VOLUME UP/DOWN BUTTONS TO SELECT YES OR NO [*] just press volume up to start the unlock process.
--------------------------------------------------------------------------------
[*] press any key to start the unlock
< waiting for any device >
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock operation is not allowed
) finished. total time: 12.588s
[*] once the bootloader is unlocked press any key to wipe data
Creating filesystem with parameters:
Size: 838860800
Block size: 4096
Blocks per group: 32768
Inodes per group: 7328
Inode size: 256
Journal blocks: 3200
Label:
Blocks: 204800
Block groups: 7
Reserved block group size: 55
Created filesystem with 11/51296 inodes and 6651/204800 blocks
target reported max download size of 134217728 bytes
erasing 'userdata'...
FAILED (remote: format for partition 'userdata' is not allowed
)
finished. total time: 0.021s
[*] Press any key to reboot the device
This is what I got and I'm assuming the boot loader unlock failed.
EDIT: Ran the .bat again and it seemed to work perfectly! Thanks

krchi said:
--------------------------------------------------------------------------------
[*] now that the device is in fastboot mode we are going to unlock the
[*] bootloader. on the next screen on your phone you will see [*] PRESS THE VOLUME UP/DOWN BUTTONS TO SELECT YES OR NO [*] just press volume up to start the unlock process.
--------------------------------------------------------------------------------
[*] press any key to start the unlock
< waiting for any device >
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock operation is not allowed
) finished. total time: 12.588s
[*] once the bootloader is unlocked press any key to wipe data
Creating filesystem with parameters:
Size: 838860800
Block size: 4096
Blocks per group: 32768
Inodes per group: 7328
Inode size: 256
Journal blocks: 3200
Label:
Blocks: 204800
Block groups: 7
Reserved block group size: 55
Created filesystem with 11/51296 inodes and 6651/204800 blocks
target reported max download size of 134217728 bytes
erasing 'userdata'...
FAILED (remote: format for partition 'userdata' is not allowed
)
finished. total time: 0.021s
[*] Press any key to reboot the device
This is what I got and I'm assuming the boot loader unlock failed.
EDIT: Ran the .bat again and it seemed to work perfectly! Thanks
Click to expand...
Click to collapse
that means that you must not have give adb shell root access before booting into fastboot mode and so you cant unlock the bootloader. run the script again and this time make sure you have root access and adb debugging working on the device

Just wanted to pop in and thank you for the work. I never thought we'd be able to achieve bootloader unlock so soon after root!

Wow, thanks for the great work !!!
Worked like magic !!!
From Amazon prime day (& BLU R1 release) to unlocked bootloader in 2 weeks !!! :laugh::laugh::laugh::laugh::laugh:

jasonmerc said:
Just wanted to pop in and thank you for the work. I never thought we'd be able to achieve bootloader unlock so soon after root!
Click to expand...
Click to collapse
its a media tec device they arent every secure lol

Tomsgt said:
its a media tec device they arent every secure lol
Click to expand...
Click to collapse
That'll teach Amazon won't it

jasonmerc said:
That'll teach Amazon won't it
Click to expand...
Click to collapse
Lol yeah have you seen what I did with the Moto G from Amazon also.

Tomsgt said:
Lol yeah have you seen what I did with the Moto G from Amazon also.
Click to expand...
Click to collapse
You're Amazon Public Enemy #1 aren't you. I'm gonna go look now.

jasonmerc said:
You're Amazon Public Enemy #1 aren't you. I'm gonna go look now.
Click to expand...
Click to collapse
Once you find that you should check out my Amazon fire tablet 5th gen super tool

...ran out of thanks from last night but this sub-forum is my new home guys. lmao
Was already subbed to your channel and liked the video
Thanks again

Do not run this script as administrator. It will fail. It would no unlock in fastboot. I tried without admin rights and it worked perfect.
Thanks for all of your work!

choder said:
Do not run this script as administrator. It will fail. It would no unlock in fastboot. I tried without admin rights and it worked perfect.
Thanks for all of your work!
Click to expand...
Click to collapse
Interesting not sure what that is about but not really a big deal thanks for the heads up I am sure it will help others.

Tomsgt said:
Interesting not sure what that is about but not really a big deal thanks for the heads up I am sure it will help others.
Click to expand...
Click to collapse
{
"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"
}
Thats the error I received. And on the phone it said "unlock failed.... return to fastboot 3s"

choder said:
Thats the error I received. And on the phone it said "unlock failed.... return to fastboot 3s"
Click to expand...
Click to collapse
Run the script again and this time make sure you grant root to adb shell

jesus tittie effing christ, i love XDA devs!
thank you SO much for this!
I bought the Amazon version specifically with the hopes that some XDA ppl would be able to root and BL-unlock it.
gamble = paid off.
bring on the ROMS! lol