Related
I sbfed the leaked 2.3.4 onto my dx2 and i'm trying to root it with no luck. i have tried zergrush, pete's, motorolaoneclick, etc. USB debbuging is on. Charge only mode is selected when connected to computer. I have tried them all and i am not getting root access can someone help?
With Pete's root method i recieve this message: http: //prntscr.com/7efen
With Zergrush's root method i get this: http: //prntscr.com/7efg8
With Motorolaoneclickroot i get this: http: //prntscr.com/7efis but i obviously dont have root.
System Version
1.3.380.MB870.Verizon.en.US
Android Version
2.3.4
Baseband Version
n_03.13.28s
Kernel Version
[email protected] #2
Build Number
4.5.1A-DTN-150-30
Reboot yo pc. Make sure no other "phone program" is running like rsd etc. Reinstall drivers.
Petes one click is the one I use.
skwoodwiva said:
Reboot yo pc. Make sure no other "phone program" is running like rsd etc. Reinstall drivers.
Petes one click is the one I use.
Click to expand...
Click to collapse
i did as you said and still nothing ! i know it can be done because i've done it before i just dont remember how
optimusprimeuy,
You need USB debbuging & Unknown Sources checked
and just follow Moon Shadow's tut.
http://forum.xda-developers.com/showthread.php?t=1315711
I'm running into these same issues. I've tried three different rooting method. DoomLord, Petes and the one-click. Nothing seems to working. I've installed the ADB drivers, rebooted, repaired the drivers. debugging and unknown sources is checked. I've tried on my desktop and laptop computer. Nothing seems to work.
This is a DX2
System version = 1.3.418.MB870
Adroid Version = 2.3.5 (is this the issue?)
Let me know if anyone can help, thanks in advance!
ImgBurn said:
optimusprimeuy,
You need USB debbuging & Unknown Sources checked
and just follow Moon Shadow's tut.
http://forum.xda-developers.com/showthread.php?t=1315711
Click to expand...
Click to collapse
use magic md5 method
magic md5 root for d2, d2g, dx, & dx2
Sent from my XT862 using Tapatalk 2
Rooting Droid X2
optimusprimeuya said:
I sbfed the leaked 2.3.4 onto my dx2 and i'm trying to root it with no luck. i have tried zergrush, pete's, motorolaoneclick, etc. USB debbuging is on. Charge only mode is selected when connected to computer. I have tried them all and i am not getting root access can someone help?
With Pete's root method i recieve this message: http: //prntscr.com/7efen
With Zergrush's root method i get this: http: //prntscr.com/7efg8
With Motorolaoneclickroot i get this: http: //prntscr.com/7efis but i obviously dont have root.
System Version
1.3.380.MB870.Verizon.en.US
Android Version
2.3.4
Baseband Version
n_03.13.28s
Kernel Version
[email protected] #2
Build Number
4.5.1A-DTN-150-30
Click to expand...
Click to collapse
I just rooted my Droid X2 by following Moon Shadows Root Tutorial with good results. My Droid is exactly as yours is above.
I copied the command window from the process and it is below, I hope it may be helpfull. Magic MD5 method did not work.
---------------------------------------------------------------
Easy rooting toolkit (v4.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 latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] 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
* daemon not running. starting it now *
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
--- pushing zergRush
1441 KB/s (23060 bytes in 0.015s)
--- 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 ! 0x00000118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[+] Zerglings found a way to enter ! 0x18
[+] Overseer found a path ! 0x000151e0
[*] Sending 189 zerglings ...
[+] Zerglings caused crash (good news): 0x4011ccd4 0x0074
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd1965b 0xafd3949f
[*] 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
946 KB/s (1075144 bytes in 1.109s)
--- correcting permissions
--- remounting /system
--- checking free space on /system
0 KB/s (439 bytes in 1.000s)
--- Free space on /system : 67% bytes
test: 67%: bad number
--- NOT enough free space on /system!!!
--- making free space by removing Google Maps
--- copying busybox to /system/xbin/
2099+1 records in
2099+1 records out
1075144 bytes transferred in 0.080 secs (13439300 bytes/sec)
--- correcting ownership
--- correcting permissions
--- installing busybox
--- pushing SU binary
1389 KB/s (22228 bytes in 0.015s)
--- correcting ownership
--- correcting permissions
--- correcting symlinks
--- pushing Superuser app
1197 KB/s (785801 bytes in 0.640s)
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
several ways to root 2.3.4
the problem with zergrush is it removes apps like maps, so you cannot update to 2.3.5
magic md5 root was made for 2.3.5, but it will work for 2.3.4, just not the fastest option
Sent from my XT862 using Tapatalk 2
Ok, so I started off with a US 3.2 tablet with 2.6.36.3 with [email protected] #1, then flashed the official US 3.2.1R2 (signed-nbx03_001-ota-042.001.zip), which resulted in having the kernel at 5.
After running condi's tool, I was able to root. Now I am trying to follow condi's steps and upgrade to pre-rooted ICS by decrypting signed-nbx03_001-ota-12041004.zip, however at the boot to recovery mode step, it shows error:
"1 was unexpected at this time"
and self closes.
Any ideas on what what might be causing this? I'm using condi's latest version 4.1. Forgive me if this is an obvious error on my part.
I would post a screenshot but its not letting me.
Thanks
same case at AIO4.1
I'm not sure it's problem or not, so stopped to proceed.
any idea?
---------- Post added at 09:55 PM ---------- Previous post was at 09:41 PM ----------
host os:win xp sp3
android ver:3.2.1-r2 (THMAS0232400)
update firm: signed-nbx03_023-ota-120427050.zip (Japan)
etc: already rooted
log is shown in below.
Code:
[*]*****************************************************************[*]
[*] Sony Tablet S / Create decrypted update.zip [*]
[*] [+optional add root and "rescue-backdoor" built-in]. [*]
[*]*****************************************************************[*]
(..snip..)
[*]*****************************************************************[*]
[*] EXTERNAL SD is required - min. 1GB! [*]
[*]*****************************************************************[*]
Instructions:
1. Put your device in USB debugging mode. ROOT IS REQUIRED.
2. Attach it via USB
3. Run this script.
[*] Run device in normal boot.
[*] Press enter to begin...
[*] Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
[*] Checking device region...
202 KB/s (0 bytes in 6476.000s)
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Processing archive: backups\region.zip
Extracting region\region.prop
Everything is Ok
Size: 692
Compressed: 6476
1 file(s) copied.
43 KB/s (0 bytes in 692.000s)
[*] Region is OK...
[*] HACK zip is already prepared, but not on SD
[*] Pushing _hack_recovery.zip...
1295 KB/s (0 bytes in 15155925.011s)
[*] DONE. Its saved in '/sdcard/_hack_recovery.zip' for future use.
[*]**************************************************************[*]
[*] DEVICE POWERED OFF. [*]
[*]**************************************************************[*]
[*] NOW ENTER RECOVERY MODE = hold vol-up, and push power [*]
[COLOR="Red"]1 was unexpected at this time.[/COLOR]
C:\S.onyTablet.S [ALLinONE] v4.1>
hi guys,
thanks for reporting
dl attached file, unpack it and replace in /files/ directory.
please post results!
br
condi
hi condi,
That works! Thx!!
Then I proceeded to the last, almost all no problem.
But I confused in last phase because something like an error happend. (mentioned below in red)
Is it no problem?
Code:
[*]**************************************************************[*]
[*] DEVICE POWERED OFF. [*]
[*]**************************************************************[*]
[*] NOW ENTER RECOVERY MODE = hold vol-up, and push power [*]
[*] Go to update, and choose "install.zip" [*]
[*]**************************************************************[*]
[*] ...
[*]******************[*]
[*] Shell enabled! [*]
[*]******************[*]
[*] Please wait...
[COLOR="Red"]mv: can't rename '/sdcard/custom_update_signed.zip': No such file or directory
cannot create /sbin/recovery: text busy
[/COLOR]
[*]**************************[*]
[*] Flashing custom zip... [*]
[*]**************************[*]
[*] After all done - remember to DELETE /sdcard/install.zip file (your update)
or just RENAME it back to 'custom_update_signed.zip' for example ;)
[*] Press any key to exit.
after all, in that phase, I flashed install.zip at first. then, flashed custom_update_signed.zip.
Is it correct? (I'm not sure but it seems work fine ics.)
Thanks,
Thanks for the reply condi. After replacing the file I am seeing the same result as coosee when I proceed to autoflash, however, when if I skip autoflash and flash manually (custom rom menu #4 manual) the ics update was successful and I verified that I maintained root.
Thanks again!
Code:
Everything is Ok
Size: 399
Compressed: 5670
1 file(s) copied.
17 KB/s (399 bytes in 0.022s)
[*] Region is OK...
[*] HACK zip is already prepared, but not on SD
[*] Pushing _hack_recovery.zip...
1317 KB/s (18868490 bytes in 13.982s)
[*] DONE. Its saved in '/sdcard/_hack_recovery.zip' for future use.
[*]**************************************************************[*]
[*] DEVICE POWERED OFF. [*]
[*]**************************************************************[*]
[*] NOW ENTER RECOVERY MODE = hold vol-up, and push power [*]
[*] Go to update, and choose "install.zip" [*]
[*]**************************************************************[*]
[*] ...
[*]******************[*]
[*] Shell enabled! [*]
[*]******************[*]
[*] Please wait...
cannot create /sbin/recovery: text busy
[*] DONE. Now you can flash custom update.zip!!!
Choose the signed file from recovery :)
[*] Press any key to exit.
Hello,
to cut a long story short I have my device with this configuration:
Smartphone: Motorola RAZR XT910
ROM: 982.124.14.XT910.Retail.en.EU
Kernel: 3.0.8-g7198280 [email protected] #1 SMP PREEMPT
The problems that I am experiencing:
1) Neither Mac, Win, nor Linux detect my RAZR when I connect it to the computer. Weird thing is that RSD (on Win) and Terminal (Linux) seem to detect the phone.
I tried switching ON/OFF USB debugging, Mass Storage, MTP but no luck at all.
2) I cannot root it! When I try to apply the Dan Rosenberg method all I get is:
[email protected]:/tmp/share$ sudo ./run.sh
[+] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[+] Device found.
[+] Pushing exploit...
3791 KB/s (366952 bytes in 0.094s)
4466 KB/s (1867568 bytes in 0.408s)
1559 KB/s (64498 bytes in 0.040s)
4031 KB/s (1578585 bytes in 0.382s)
pkg: /data/local/tmp/Superuser.apk
Success
[+] Rooting phone...
[+] Your phone may appear to reboot. Please ignore this and continue with the exploit.
/system/bin/sh: /storage/rfs0/pwn: not found
[+] Please press any hardware button on your phone.
[+] Don't worry if the phone is unresponsive at this time.
[+] The device will vibrate when the exploit is complete.
[+] Press enter to continue once the device has vibrated.
Then it does not vibrate and no root is applied.
No luck either with this http://forum.xda-developers.com/showthread.php?t=2257137
3) I cannot boot into recovery! When I switch on pressing Power + VolUp + VolDown I get into the screen with robot & red ! triangle but even pressing buttons from there does not take me anywere! I don't know what to do.
4) Last but not least I would like to unlock the bootloader and change kernel. I got to know that this 982.124.14.XT910.Retail.en.EU appears to lock you yet I would like to ask if someone found some turnaround.
Can you help me?
Thanks a lot for the support!
Alberto
albertaz said:
Hello,
to cut a long story short I have my device with this configuration:
Smartphone: Motorola RAZR XT910
ROM: 982.124.14.XT910.Retail.en.EU
Kernel: 3.0.8-g7198280 [email protected] #1 SMP PREEMPT
The problems that I am experiencing:
1) Neither Mac, Win, nor Linux detect my RAZR when I connect it to the computer. Weird thing is that RSD (on Win) and Terminal (Linux) seem to detect the phone.
I tried switching ON/OFF USB debugging, Mass Storage, MTP but no luck at all.
2) I cannot root it! When I try to apply the Dan Rosenberg method all I get is:
[email protected]:/tmp/share$ sudo ./run.sh
[+] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[+] Device found.
[+] Pushing exploit...
3791 KB/s (366952 bytes in 0.094s)
4466 KB/s (1867568 bytes in 0.408s)
1559 KB/s (64498 bytes in 0.040s)
4031 KB/s (1578585 bytes in 0.382s)
pkg: /data/local/tmp/Superuser.apk
Success
[+] Rooting phone...
[+] Your phone may appear to reboot. Please ignore this and continue with the exploit.
/system/bin/sh: /storage/rfs0/pwn: not found
[+] Please press any hardware button on your phone.
[+] Don't worry if the phone is unresponsive at this time.
[+] The device will vibrate when the exploit is complete.
[+] Press enter to continue once the device has vibrated.
Then it does not vibrate and no root is applied.
No luck either with this http://forum.xda-developers.com/showthread.php?t=2257137
3) I cannot boot into recovery! When I switch on pressing Power + VolUp + VolDown I get into the screen with robot & red ! triangle but even pressing buttons from there does not take me anywere! I don't know what to do.
4) Last but not least I would like to unlock the bootloader and change kernel. I got to know that this 982.124.14.XT910.Retail.en.EU appears to lock you yet I would like to ask if someone found some turnaround.
Can you help me?
Thanks a lot for the support!
Alberto
Click to expand...
Click to collapse
Have you installed the latest drivers? Sounds like that's you issue..
And to boot into recovery turn off your device then press power+volume up+volume down and select recovery,when you get to the android with red triangle press volume up+volume down for about 10 seconds I think then let go and you'll enter to the recovery mode.
Sent from my XT910 using xda premium
Thanks for the reply.
Yes, I have the latest drivers installed both on Win and on Mac, as for Linux I guess they are not needed
Yet nothing happens... On Win I keep hearing that notifications sound but nothing shows up. On the RAZR screen I read something like "AT command service start", "AT command service stop" when I plus/unplug it to the PC USB. And that's it
As for the recovery: thanks a lot. It worked although I had to try a couple of times as the device sometimes freezes even during that boot stage.
AztekSoul said:
Have you installed the latest drivers? Sounds like that's you issue..
And to boot into recovery turn off your device then press power+volume up+volume down and select recovery,when you get to the android with red triangle press volume up+volume down for about 10 seconds I think then let go and you'll enter to the recovery mode.
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
I got the same problem when updated to JB to root the phone. Just try to root again since phone couldnot root first time i tried. Then i run the script again and it was ok...
After several attempts I used a linux computer and did step by step what Dan described in his root procedure.
I found out that there was a last problem which was that the phone was looking for "rfs1" while the "run.sh" on linux was using "rsf0" so I edite the "run.sh" file in the folder /tmp/share (you should find that at line 47):
echo "[+] Rooting phone..."
echo "[+] Your phone may appear to reboot. Please ignore this and continue with the exploit."
$adb shell /storage/rfs0/pwn 1 ---> I modified that into $adb shell /storage/rfs1/pwn
then I saved and re-applied the last part of the ROOT procedure and it worked smoothly.
2) USB connection reappeared!
ersink said:
I got the same problem when updated to JB to root the phone. Just try to root again since phone couldnot root first time i tried. Then i run the script again and it was ok...
Click to expand...
Click to collapse
albertaz said:
After several attempts I used a linux computer and did step by step what Dan described in his root procedure.
I found out that there was a last problem which was that the phone was looking for "rfs1" while the "run.sh" on linux was using "rsf0" so I edite the "run.sh" file in the folder /tmp/share (you should find that at line 47):
echo "[+] Rooting phone..."
echo "[+] Your phone may appear to reboot. Please ignore this and continue with the exploit."
$adb shell /storage/rfs0/pwn 1 ---> I modified that into $adb shell /storage/rfs1/pwn
then I saved and re-applied the last part of the ROOT procedure and it worked smoothly.
2) USB connection reappeared!
Click to expand...
Click to collapse
That's useful info. I always try custom roms and smtimes razr got soft bricked so i flash the firmware again then root again. Every rooting process i stuck first then reroot the phone. This is the situation why at first try phone cannot rooted.
I got the January 7th OTA update. I lost root. I do have Voodoo OTA root keeper, and it said root restored but it didn't check the box. I also have SuperUser but I keep getting the # sign in the status bar to update su bin. When I try to update it gives me an error message. I tried to use a few root dependent apps to test if root was truly gone, and, indeed, it was.
I gave up and decided I should just try to reroot. So I ran Razrblade Utility that I used to root jellybean in the first place, and not even that works. I have safestrap if that means anything. Any ideas?
Here is the dialogue box I get when I try to run Razr Blade
[*]
[*] Razr Blade: Motorola Droid Razr 4.1 Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Thanks to p3droid for assistance in testing.
[*]
[*] Note: this will not work on Razr HD, Razr M, etc.
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Motorola drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Please carefully follow any instructions provided in the exploit.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
[*] Device found.
[*] Phase one...
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Phase two...
[*] Complete the following steps on your device:
[*] 1. Open the Smart Actions application.
[*] 2. Select "Get Started".
[*] 3. Select "Battery Saver".
[*] 4. Select "Save".
[*] 5. Press the Home button.
[*]
[*] Press enter here once you have completed the above steps.
Press any key to continue . . .
55 KB/s (3477 bytes in 0.061s)
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Phase three (this will take a minute)...
failed on '/data/logger' - Permission denied
mkdir failed for /data/logger, File exists
Unable to chmod /data/logger: Operation not permitted
link failed File exists
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Phase four...
472 KB/s (91992 bytes in 0.190s)
1211 KB/s (1867568 bytes in 1.505s)
1259 KB/s (574184 bytes in 0.445s)
878 KB/s (63838 bytes in 0.071s)
[*] Cleaning up...
/system/bin/sh: su: not found
[*] Rebooting...
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
Terminate batch job (Y/N)?
Me too
thrax12 said:
I got the January 7th OTA update. I lost root. I do have Voodoo OTA root keeper, and it said root restored but it didn't check the box. I also have SuperUser but I keep getting the # sign in the status bar to update su bin. When I try to update it gives me an error message. I tried to use a few root dependent apps to test if root was truly gone, and, indeed, it was.
I gave up and decided I should just try to reroot. So I ran Razrblade Utility that I used to root jellybean in the first place, and not even that works. I have safestrap if that means anything. Any ideas?
Here is the dialogue box I get when I try to run Razr Blade
[*]
[*] Razr Blade: Motorola Droid Razr 4.1 Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Thanks to p3droid for assistance in testing.
[*]
[*] Note: this will not work on Razr HD, Razr M, etc.
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Motorola drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Please carefully follow any instructions provided in the exploit.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
[*] Device found.
[*] Phase one...
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Phase two...
[*] Complete the following steps on your device:
[*] 1. Open the Smart Actions application.
[*] 2. Select "Get Started".
[*] 3. Select "Battery Saver".
[*] 4. Select "Save".
[*] 5. Press the Home button.
[*]
[*] Press enter here once you have completed the above steps.
Press any key to continue . . .
55 KB/s (3477 bytes in 0.061s)
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Phase three (this will take a minute)...
failed on '/data/logger' - Permission denied
mkdir failed for /data/logger, File exists
Unable to chmod /data/logger: Operation not permitted
link failed File exists
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Phase four...
472 KB/s (91992 bytes in 0.190s)
1211 KB/s (1867568 bytes in 1.505s)
1259 KB/s (574184 bytes in 0.445s)
878 KB/s (63838 bytes in 0.071s)
[*] Cleaning up...
/system/bin/sh: su: not found
[*] Rebooting...
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
Terminate batch job (Y/N)?
Click to expand...
Click to collapse
I had the same problem. However after clearing the cache I was able to regain root.
1.Power the device off.
Note Press the Power button then select Power off.
Note If the device doesn't respond to input, press and hold the Volume Up / Down then press and holdPower button. When the device screen goes blank release the Power button while continuing to holdVolume Up / Down, proceed with step 3.
2.Press and hold the Volume Up / Down then press the Power button.
3.When presented with the Boot Mode Selection Menu release all buttons.
4.Press Volume Down to select Recovery then press Volume Up.
5.From the Droid triage screen, simultaneously press Volume Up / Down.
6.Select Clear the Cache Partition then press the Power button.
7.Select reboot system now then press the Power button.
I also disabled all smart actions before starting the razr blade batch file. Don't know that it made any difference. Good luck.
I got an update, 13.3.2.2. I'm confused, how do you stop updates for sure?
Also, I forgot to say that I found this website, which claims to be a rooting website, I checked the supported devices on it and the HDX appeared. I can't try it now, but if anyone else can, please do. Do not laugh if I'm wrong, though. Thanks for the support!
http://www.srsroot.com/supported
Here you can find the KFHTWI. Yay!
ferrouskid said:
http://www.srsroot.com/supported
Here you can find the KFHTWI. Yay!
Click to expand...
Click to collapse
I have the KF HDX 8.9 running 14.3.2.1_user_321093620. SRS found no vulnerabilities to exploit.
My RESULTS:
---= SRS One-Click-Root v4.7 =---
17:26:51 - Starting ADB Server..
17:26:56 - Manufacturer: Amazon
17:26:56 - Model: KFAPWI
17:26:56 - Android Version: 4.2.2
17:26:56 - Build ID: JDQ39
17:26:56 - Board ID: apollo
17:26:56 - Chipset Platform: msm8974
17:26:56 - Getting OffSets.. : 0x8003 0x8005 (False)
17:26:56 - Query Server for Best Method.. Not Found (SmartRoot not possible yet)
----= Start Rooting Process.. Please Wait =----
17:26:58 [+] Testing exploit: root1 (Please wait some minutes)....
17:26:58 [+] Executing root1 exploit Failed, Proceed next...
17:26:58 [+] Testing exploit: root2a (Please wait it can take some minutes)....
17:27:00 [+] Executing root2a exploit Failed, Proceed next...
17:27:00 [+] Installing exploit: root3c (Please wait...)
17:27:03 [+] Select 'FRODO' or 'ARAGORN' or 'LEGOLAS' on your device, then click OK
17:27:24 [+] Removing Exploit.. Please Wait..
17:27:32 [+] Analysing Results...
17:27:32 [+] Root Failed: Resume Exploit 4.
17:27:32 [+] Testing exploit: root4 (please wait..)
17:27:35 [+] Device Reboot #1 (Wait till it's started)
17:28:59 [+] Device Reboot #2 (Wait till it's started)
17:30:04 [+] Executing root4 exploit Failed. (Root Error: 0)
17:30:04 [+] Testing exploit: root4b (please wait..)
17:30:11 [+] Device Reboot #1 (Wait till it's started)
17:31:23 [+] Device Reboot #2 (Wait till it's started)
17:33:34 [+] Testing exploit: root5 (please wait..)
17:33:35 [+] Unlock your device screen, it should bring up restore mode.
17:33:49 [+] Press RESTORE button on device NOW! then wait...
17:34:21 [+] Device Reboot #1 (Wait till it's started)
17:36:40 [+] Executing root5 exploit Failed. (Root Error: 0)
17:36:40 Auto Root Failed on this device.
It might be kind of extreme, but what if we filled the Kindle with MP3s or something to keep the free space below 800mb? The update BIN shouldn't be able to download because of insufficient space.
Cevyn said:
It might be kind of extreme, but what if we filled the Kindle with MP3s or something to keep the free space below 800mb? The update BIN shouldn't be able to download because of insufficient space.
Click to expand...
Click to collapse
Worth a try, but it looks like they left a lot of space for the OS to work with...
"16GB (10.9GB available to user) or 32GB (25.1GB available to user), or 64 GB (53.7GB available to user) of internal storage"
Cevyn said:
It might be kind of extreme, but what if we filled the Kindle with MP3s or something to keep the free space below 800mb? The update BIN shouldn't be able to download because of insufficient space.
Click to expand...
Click to collapse
Technically this should work, but I'm pretty sure there is a way to delete update files. I found a nifty application called "Android Commander" which a allows you to access the system files on the HDX from the pc. Unfortunately you can not modify anything without root, but I'm hoping someone can figure out a hack for that, if it is possible than maybe the boot loader could be unlocked. And you are probably thinking what I'm thinking, AOSP ROM here I come!
matt101 said:
I have the KF HDX 8.9 running 14.3.2.1_user_321093620. SRS found no vulnerabilities to exploit.
My RESULTS:
---= SRS One-Click-Root v4.7 =---
17:26:51 - Starting ADB Server..
17:26:56 - Manufacturer: Amazon
17:26:56 - Model: KFAPWI
17:26:56 - Android Version: 4.2.2
17:26:56 - Build ID: JDQ39
17:26:56 - Board ID: apollo
17:26:56 - Chipset Platform: msm8974
17:26:56 - Getting OffSets.. : 0x8003 0x8005 (False)
17:26:56 - Query Server for Best Method.. Not Found (SmartRoot not possible yet)
----= Start Rooting Process.. Please Wait =----
17:26:58 [+] Testing exploit: root1 (Please wait some minutes)....
17:26:58 [+] Executing root1 exploit Failed, Proceed next...
17:26:58 [+] Testing exploit: root2a (Please wait it can take some minutes)....
17:27:00 [+] Executing root2a exploit Failed, Proceed next...
17:27:00 [+] Installing exploit: root3c (Please wait...)
17:27:03 [+] Select 'FRODO' or 'ARAGORN' or 'LEGOLAS' on your device, then click OK
17:27:24 [+] Removing Exploit.. Please Wait..
17:27:32 [+] Analysing Results...
17:27:32 [+] Root Failed: Resume Exploit 4.
17:27:32 [+] Testing exploit: root4 (please wait..)
17:27:35 [+] Device Reboot #1 (Wait till it's started)
17:28:59 [+] Device Reboot #2 (Wait till it's started)
17:30:04 [+] Executing root4 exploit Failed. (Root Error: 0)
17:30:04 [+] Testing exploit: root4b (please wait..)
17:30:11 [+] Device Reboot #1 (Wait till it's started)
17:31:23 [+] Device Reboot #2 (Wait till it's started)
17:33:34 [+] Testing exploit: root5 (please wait..)
17:33:35 [+] Unlock your device screen, it should bring up restore mode.
17:33:49 [+] Press RESTORE button on device NOW! then wait...
17:34:21 [+] Device Reboot #1 (Wait till it's started)
17:36:40 [+] Executing root5 exploit Failed. (Root Error: 0)
17:36:40 Auto Root Failed on this device.
Click to expand...
Click to collapse
Thanks for the effort. Now as soon as I have the ability I will try the root on the 7". But thanks a lot for the effort. By the way check out Android Commander, I have been smacking a lot of fuss about it on XDA, because I see a lot of potential in it, I'll try my best to find a hack that will enable one to write things on to the HDX system files, which it is designed to see. I gave it a try before, seemed to work just fine. Now if the update file could be deleted and the 13.3.1 image could be forced on to the HDX we could root! However one can already copy files from the HDX, so my plan is to install the HDX mojito os on sub using unetbootin and boot up the computer from it, or my netbook which closely resembles it, and then try and find a way to modify things without actually bricking the HDX, so if you can, please give it a shot. But if I'm wrong, please do correct me! Thanks again.
Cevyn said:
It might be kind of extreme, but what if we filled the Kindle with MP3s or something to keep the free space below 800mb? The update BIN shouldn't be able to download because of insufficient space.
Click to expand...
Click to collapse
On the topic of BIN files, I got my brother to edit the build prop on the old update 13.3.1, the rootable one. I asked him to change the build number in it, might sound stupid but I have a hunch that is what is checked during manual update (in case you didn't know you just drag and drop the update into internal storage, and then do it the usual way and it should appear there). Now all that has to be done is the .zip converted into a .bin, and ill give it a try as soon as it's done. Let's hope it works!
ferrouskid said:
On the topic of BIN files, I got my brother to edit the build prop on the old update 13.3.1, the rootable one. I asked him to change the build number in it, might sound stupid but I have a hunch that is what is checked during manual update (in case you didn't know you just drag and drop the update into internal storage, and then do it the usual way and it should appear there). Now all that has to be done is the .zip converted into a .bin, and ill give it a try as soon as it's done. Let's hope it works!
Click to expand...
Click to collapse
I believe the BIN files are just renamed ZIP files. 7-Zip opens them just fine.
ferrouskid said:
On the topic of BIN files, I got my brother to edit the build prop on the old update 13.3.1, the rootable one. I asked him to change the build number in it, ...
Click to expand...
Click to collapse
What build number did you have your brother change it to?
How are you getting around signing the BIN file? This would be the major stumbling block to any mods to it...
Cevyn said:
I believe the BIN files are just renamed ZIP files. 7-Zip opens them just fine.
Click to expand...
Click to collapse
Yeah, thanks. I tried it and the kindle recognised is as an update ) but it said the file wasn't valid, so I should convert it to a .bin. Maybe then it'll work? After this I'll shut my WiFi off so it doesn't connect to the internet to verify the update. Ill be back at dad with results from PC.
Let's hope it works! A little bit to go!!!
tl3 said:
What build number did you have your brother change it to?
How are you getting around signing the BIN file? This would be the major stumbling block to any mods to it...
Click to expand...
Click to collapse
I got him to change it to 13.3.3.3 and let the user bit stay the same. Now I tried it in bin format, and here are the results so far (check image).
So far it doesn't recognise it as 13.3.3.3, maybe because it's a zip? I realise that bins and zips in effect are the same thing, but maybe converting will,help?
Will be back at xda after this.
Here is the url to dropbox
https://www.dropbox.com/s/v5eo7zu155773b0/Screenshot_2014-04-11-21-33-23_kindlephoto-9182708.png
Oh yeah, I need a little help with the signing. I have found a certificate installer app on the kindle, but I'm not sure it will do the job. Maybe if I installed it in an android environment and managed to certify it from my netbook using x-86 android website downloads...
But it might not work. Please correct me, I'm quite new to this all. And also isn't there like signtool.exe for windows? Ill look into that, and I'd be grateful if you could help.
Thanks!
ferrouskid said:
I got him to change it to 13.3.3.3 and let the user bit stay the same. Now I tried it in bin format, and here are the results so far (check image).
So far it doesn't recognise it as 13.3.3.3, maybe because it's a zip? I realise that bins and zips in effect are the same thing, but maybe converting will,help?
Will be back at xda after this.
Here is the url to dropped
https://www.dropbox.com/s/v5eo7zu155773b0/Screenshot_2014-04-11-21-33-23_kindlephoto-9182708.png
Click to expand...
Click to collapse
I believe that the Kindle only recognized that there is an update file with a higher version number, but if it is not signed properly, the modified BIN file will not pass authentication and the update process will terminate. This is the stumbling block I was referring to and asking you about... it's not something trivial that can be easily defeated or bypassed.
tl3 said:
I believe that the Kindle only recognized that there is an update file with a higher version number, but if it is not signed properly, the modified BIN file will not pass authentication and the update process will terminate. This is the stumbling block I was referring to and asking you about... it's not something trivial that can be easily defeated or bypassed.
Click to expand...
Click to collapse
Ill keep on at it, and see where it goes. I have read up some things about signing bin files, I think Android Commander has the option to do so and so does Signtool, but I don't know what to sign it with yet. Yeah, you were right, it did terminate the update unfortunately, but Ill see what I can do.
Here is a snapshot
https://www.dropbox.com/s/pp6txvavncuwvti/Screenshot_2014-04-12-09-11-33.png
tl3 said:
I believe that the Kindle only recognized that there is an update file with a higher version number, but if it is not signed properly, the modified BIN file will not pass authentication and the update process will terminate. This is the stumbling block I was referring to and asking you about... it's not something trivial that can be easily defeated or bypassed.
Click to expand...
Click to collapse
Yes, this truly is a stumbling block. I need someone's help to find a certificate that Amazon use for their updates, there are numerous certificate apps installed on the kindle, but I'm not 100% sure they serve this specific purpose. There are signing tools available for free on the internet, such as signtool and stuff like that. That's all good, but I have no idea in which way Amazon sign their updates. I have the original 13.3.1 .bin officially signed by Amazon, I will have a link to my dropbox. I wonder weather there is a way to find in which way it was signed and do the same for this "update"?
Ill be looking into that.
https://dl.dropboxusercontent.com/u/67795059/update-kindle-13.3.1.0_user_310079820.bin
Keeping root across updates may be possible with simple re-signing
Amazon uses SignApk to sign their updates.
(To confirm, just unzip the .bin file and look at the first few lines of CERT.SF (or MANIFEST.MF) in the META-INF directory.)
*IF* you have root today (unfortunately, I got updated before I had a chance to try this),
you should be able to take an official Amazon update, unpack it, strip the existing signature,
add whatever you like (supersu and your own otacerts comes to mind), and re-sign
the update with your own key following the procedure described in this blog post:
FIX THE URL ::: www .. londatiga .. net // it // how-to-sign-apk-zip-files
(including instructions on how to generate your own signing key and certificate).
What you need root access for is to swap the current /system/etc/security/otacerts.zip on your device to your own zipped certificate.
Once that piece is changed, you should be able to use Amazon's manual update procedure to apply your modified update.
FIX THE URL ::: www .. amazon .. com // gp // help // customer // display.html?nodeId=201390600
You may need to change the updater-script to set the right owner and permissions for /system/xbin/su.
And, don't forget to change /system/etc/security/otacerts.zip to your own stuff in the actual update as well!
Again, this _MAY_ (or may not) work. I'd appreciate feedback if you tried this (or: are willing to try, but need help).