Related
Ok...I'm at my wits end here with the ZergRushRoot method.
I unlocked my bootloader and attempted the "one click" method BUT still receive the following error message:
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb wait-for-device
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb push zergRush /data/local/
2071 KB/s (21215 bytes in 0.010s)
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell chmod 777 /data/local/zergRush
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell rm /data/local/tmp/*sh
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell /data/local/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 ! 0x00017118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb wait-for-device
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell sleep 1
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb remount
remount failed: Operation not permitted
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell mount -o rw,remount rootfs /
mount: Operation not permitted
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell mount -o remount,suid /dev/blo
ck/mmcblk0p29 /system
mount: Operation not permitted
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell chmod 4755 /system/bin/sh
Unable to chmod /system/bin/sh: Read-only file system
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb push ./busybox /system/bin
failed to copy './busybox' to '/system/bin/busybox': Read-only file system
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell chmod 4755 /system/bin
Unable to chmod /system/bin: Read-only file system
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb push ./Superuser.apk /system/app
failed to copy './Superuser.apk' to '/system/app/Superuser.apk': Read-only file
system
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb install ./androidterm.apk
2831 KB/s (92780 bytes in 0.032s)
pkg: /data/local/tmp/androidterm.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb wait-for-device
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell sync
C:\Zerg_Root_OneClick(1)\Zerg rush root>pause
Press any key to continue . . .
I'm fairly certain that I followed the instructions as they were presented on the main thread and in the YouTube video by Ted.
I have verified that my bootloader is unlocked...what should I do next?
I've searched through numerous previous posts and spend over a day on this. Please suggest next steps...thank you!
dudro said:
Ok...I'm at my wits end here with the ZergRushRoot method.
I unlocked my bootloader and attempted the "one click" method BUT still receive the following error message:
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb wait-for-device
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb push zergRush /data/local/
2071 KB/s (21215 bytes in 0.010s)
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell chmod 777 /data/local/zergRush
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell rm /data/local/tmp/*sh
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell /data/local/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 ! 0x00017118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb wait-for-device
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell sleep 1
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb remount
remount failed: Operation not permitted
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell mount -o rw,remount rootfs /
mount: Operation not permitted
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell mount -o remount,suid /dev/blo
ck/mmcblk0p29 /system
mount: Operation not permitted
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell chmod 4755 /system/bin/sh
Unable to chmod /system/bin/sh: Read-only file system
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb push ./busybox /system/bin
failed to copy './busybox' to '/system/bin/busybox': Read-only file system
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell chmod 4755 /system/bin
Unable to chmod /system/bin: Read-only file system
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb push ./Superuser.apk /system/app
failed to copy './Superuser.apk' to '/system/app/Superuser.apk': Read-only file
system
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb install ./androidterm.apk
2831 KB/s (92780 bytes in 0.032s)
pkg: /data/local/tmp/androidterm.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb wait-for-device
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell sync
C:\Zerg_Root_OneClick(1)\Zerg rush root>pause
Press any key to continue . . .
I'm fairly certain that I followed the instructions as they were presented on the main thread and in the YouTube video by Ted.
I have verified that my bootloader is unlocked...what should I do next?
I've searched through numerous previous posts and spend over a day on this. Please suggest next steps...thank you!
Click to expand...
Click to collapse
Are you running as administrator?
It's not working because it's not mounting the root partition.
Why don't you try using fastboot instead?
http://forum.xda-developers.com/showthread.php?t=1316855
I don't have an unlocked bootloader but have used the method for temp root in order to restore game data backed up from my Rooted Inspire 4G. I had errors the second time I used the tool which I can only assume were caused by Norton messing up the files while they were just sitting on the computer (since I disable it which doing anything between the phone and PC).
I had to delete all the tool files and re download with the security once again disabled, that did the trick.
Good luck!
Sent from my HTC Ruby using xda premium
Binary100100 said:
Are you running as administrator?
It's not working because it's not mounting the root partition.
Why don't you try using fastboot instead?
http://forum.xda-developers.com/showthread.php?t=1316855
Click to expand...
Click to collapse
When you ask whether I am running as administrator, are you referring to my PC? If so, yes. I am logged in with Admin rights.
Once I perform the fastboot method using the "PH85IMG.zip", do I then try the Zerg one click again?
Trevorhimself said:
I don't have an unlocked bootloader but have used the method for temp root in order to restore game data backed up from my Rooted Inspire 4G. I had errors the second time I used the tool which I can only assume were caused by Norton messing up the files while they were just sitting on the computer (since I disable it which doing anything between the phone and PC).
I had to delete all the tool files and re download with the security once again disabled, that did the trick.
Good luck!
Sent from my HTC Ruby using xda premium
Click to expand...
Click to collapse
Oh...this is interesting...perhaps I will disable AVG and try again...I will post my results.
dudro said:
When you ask whether I am running as administrator, are you referring to my PC? If so, yes. I am logged in with Admin rights.
Once I perform the fastboot method using the "PH85IMG.zip", do I then try the Zerg one click again?
Click to expand...
Click to collapse
Wow you're really making this much harder than it needs to be.
You have two ways to do it.
Use the PH85IMG.zip file according to your software version.
Use the fastboot flash recovery recovery.img command.
Once you get the recovery you do not need to do Zerg. You are free to flash a custom rom.
If you don't want a custom rom then just flash the file attached for perm root (from recovery of course).
Binary100100 said:
Wow you're really making this much harder than it needs to be.
You have two ways to do it.
Use the PH85IMG.zip file according to your software version.
Use the fastboot flash recovery recovery.img command.
Once you get the recovery you do not need to do Zerg. You are free to flash a custom rom.
If you don't want a custom rom then just flash the file attached for perm root (from recovery of course).
Click to expand...
Click to collapse
This finally worked! Thank you!
dudro said:
This finally worked! Thank you!
Click to expand...
Click to collapse
No problem. You could have used the thanks button though.
I tried to root my phone and i'm having problem. Did anybody have the problem?
C:\Users\Peter\Downloads\Zerg rush root>ZergRushTempRoot.bat
C:\Users\Peter\Downloads\Zerg rush root>adb wait-for-device
C:\Users\Peter\Downloads\Zerg rush root>adb push zergRush /data/local/
2071 KB/s (21215 bytes in 0.010s)
C:\Users\Peter\Downloads\Zerg rush root>adb shell chmod 777 /data/local/zergRush
C:\Users\Peter\Downloads\Zerg rush root>adb shell rm /data/local/tmp/*sh
C:\Users\Peter\Downloads\Zerg rush root>adb shell /data/local/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 ! 0x00017118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
C:\Users\Peter\Downloads\Zerg rush root>adb wait-for-device
C:\Users\Peter\Downloads\Zerg rush root>adb shell sleep 1
C:\Users\Peter\Downloads\Zerg rush root>adb remount
remount failed: Operation not permitted
C:\Users\Peter\Downloads\Zerg rush root>adb shell mount -o rw,remount rootfs /
mount: Operation not permitted
C:\Users\Peter\Downloads\Zerg rush root>adb shell mount -o remount,suid /dev/block/mmcblk0p29 /system
mount: Operation not permitted
C:\Users\Peter\Downloads\Zerg rush root>adb shell chmod 4755 /system/bin/sh
Unable to chmod /system/bin/sh: Read-only file system
C:\Users\Peter\Downloads\Zerg rush root>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Users\Peter\Downloads\Zerg rush root>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Users\Peter\Downloads\Zerg rush root>adb push ./busybox /system/bin
failed to copy './busybox' to '/system/bin/busybox': Read-only file system
C:\Users\Peter\Downloads\Zerg rush root>adb shell chmod 4755 /system/bin
Unable to chmod /system/bin: Read-only file system
C:\Users\Peter\Downloads\Zerg rush root>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Users\Peter\Downloads\Zerg rush root>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Users\Peter\Downloads\Zerg rush root>adb push ./Superuser.apk /system/app
failed to copy './Superuser.apk' to '/system/app/Superuser.apk': Read-only file system
C:\Users\Peter\Downloads\Zerg rush root>adb install ./androidterm.apk
3124 KB/s (92780 bytes in 0.029s)
pkg: /data/local/tmp/androidterm.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\Users\Peter\Downloads\Zerg rush root>adb wait-for-device
C:\Users\Peter\Downloads\Zerg rush root>adb shell sync
C:\Users\Peter\Downloads\Zerg rush root>pause
Press any key to continue . . .
don't use that!!! it's old...use the guide on top of the page!
That only works with version 1.36. Do what seansk said and you should be fine.
Thanks guys!!!!
Now i'm getting this
C:\Users\Peter\Downloads\STOCK_RECOVERY_FLASHER>adb kill-server
C:\Users\Peter\Downloads\STOCK_RECOVERY_FLASHER>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
C:\Users\Peter\Downloads\STOCK_RECOVERY_FLASHER>fastboot flash recovery stock_recovery.img
< waiting for device >
pcurator said:
Now i'm getting this
C:\Users\Peter\Downloads\STOCK_RECOVERY_FLASHER>adb kill-server
C:\Users\Peter\Downloads\STOCK_RECOVERY_FLASHER>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
C:\Users\Peter\Downloads\STOCK_RECOVERY_FLASHER>fastboot flash recovery stock_recovery.img
< waiting for device >
Click to expand...
Click to collapse
make sure the phone drivers are installed on your computer!
P.s. did you unzip the files into a directory?
Yes i have the drivers installed. Files are unzip as well.
pcurator said:
Yes i have the drivers installed. Files are unzip as well.
Click to expand...
Click to collapse
what part of the guide are you stuck in? and what step? WHY ARE YOU TRYING TO FLASH STOCK RECOVERY??????? you need custom recovery! not stock..
---------- Post added at 06:40 PM ---------- Previous post was at 06:33 PM ----------
seansk said:
what part of the guide are you stuck in? and what step? WHY ARE YOU TRYING TO FLASH STOCK RECOVERY??????? you need custom recovery! not stock..
Click to expand...
Click to collapse
I urge you to read a little more carfeully and don't just skim over things while your following the guide!!! it specifically states what those files are and the one you're using reverts you back to stock recovery. You're trying to put a custom recovery on, not the original one that came with the factory and is already on your phone at this point...you trying to replace stock recovery with stock recovery!!!
I know you're new so It understandable but next time you should post all this stuff in the appropriate thread!!! the [How to] guide to rooting...you'll get more responses this way and people will not get pissed off, especially the moderators
I swear to GOD!!! If I keep seeing those stupid Zergrush errors for 1.43+ firmware I'm going to be forced to check myself as a 5150. This is getting out of hand.
If a .bat script isn't your thing then try this thread: [TOOL] HTC Amaze 4G All-In-One Toolkit by Hasoon2000
Binary100100 said:
I swear to GOD!!! If I keep seeing those stupid Zergrush errors for 1.43+ firmware I'm going to be forced to check myself as a 5150. This is getting out of hand.
If a .bat script isn't your thing then try this thread: [TOOL] HTC Amaze 4G All-In-One Toolkit by Hansoon2000
Click to expand...
Click to collapse
Sadly, you got my username wrong. You disappoint me, B.
hasoon2000 said:
Sadly, you got my username wrong. You disappoint me, B.
Click to expand...
Click to collapse
NO! I've sent a PM to the administrator to have you renamed to Hansoon2000.
Hope you enjoy your new name Hansoon2000. See you around the forum Hansoon2000. I'll fix it.
Binary100100 said:
NO! I've sent a PM to the administrator to have you renamed to Hansoon2000.
Hope you enjoy your new name Hansoon2000. See you around the forum Hansoon2000. I'll fix it.
Click to expand...
Click to collapse
Haha. Jackass! Hasoon is actually the name of my cat who passed away a 2 years ago. I'd rather keep it the same.
Binary100100 said:
I swear to GOD!!! If I keep seeing those stupid Zergrush errors for 1.43+ firmware I'm going to be forced to check myself as a 5150. This is getting out of hand.
If a .bat script isn't your thing then try this thread: [TOOL] HTC Amaze 4G All-In-One Toolkit by Hasoon2000
Click to expand...
Click to collapse
lol I love it when binary goes mad!!! that tool isn't needed anymore, unless for a handfull of people who wish to stay on their old firmware and do temproot!!! why don't we just get rid of it!
Binary100100 said:
I swear to GOD!!! If I keep seeing those stupid Zergrush errors for 1.43+ firmware I'm going to be forced to check myself as a 5150. This is getting out of hand.
If a .bat script isn't your thing then try this thread: [TOOL] HTC Amaze 4G All-In-One Toolkit by Hasoon2000
Click to expand...
Click to collapse
Learn my tough love Lesson from this guy... Never pissed this guy.
seansk said:
lol I love it when binary goes mad!!! that tool isn't needed anymore, unless for a handfull of people who wish to stay on their old firmware and do temproot!!! why don't we just get rid of it!
Click to expand...
Click to collapse
I could totally see you making a bunch of duplicate accounts pretending to be noobs just to piss me off.
Binary100100 said:
I could totally see you making a bunch of duplicate accounts pretending to be noobs just to piss me off.
Click to expand...
Click to collapse
too late all the new questions regarding root was me!!! I also like to answer my own questions!!
I managed to unlock my bootloader and install clockwork using hasoon2000's allinone program. but since i'm on 2.3.4 I was not able to use the permproot feature. I tried using zergrush oneclick root and that also failed, I get the following error:
C:\Users\PC\Desktop\Zerg rush root>adb wait-for-device
C:\Users\PC\Desktop\Zerg rush root>adb push zergRush /data/local/
1479 KB/s (21215 bytes in 0.014s)
C:\Users\PC\Desktop\Zerg rush root>adb shell chmod 777 /data/local/zergRush
C:\Users\PC\Desktop\Zerg rush root>adb shell rm /data/local/tmp/*sh
C:\Users\PC\Desktop\Zerg rush root>adb shell /data/local/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 ! 0x00017118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
C:\Users\PC\Desktop\Zerg rush root>adb wait-for-device
C:\Users\PC\Desktop\Zerg rush root>adb shell sleep 1
C:\Users\PC\Desktop\Zerg rush root>adb remount
remount failed: Operation not permitted
C:\Users\PC\Desktop\Zerg rush root>adb shell mount -o rw,remount rootfs /
mount: Operation not permitted
C:\Users\PC\Desktop\Zerg rush root>adb shell mount -o remount,suid /dev/block/mm
cblk0p29 /system
mount: Operation not permitted
C:\Users\PC\Desktop\Zerg rush root>adb shell chmod 4755 /system/bin/sh
Unable to chmod /system/bin/sh: Read-only file system
C:\Users\PC\Desktop\Zerg rush root>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Users\PC\Desktop\Zerg rush root>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Users\PC\Desktop\Zerg rush root>adb push ./busybox /system/bin
failed to copy './busybox' to '/system/bin/busybox': Read-only file system
C:\Users\PC\Desktop\Zerg rush root>adb shell chmod 4755 /system/bin
Unable to chmod /system/bin: Read-only file system
C:\Users\PC\Desktop\Zerg rush root>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: Read-only file system
C:\Users\PC\Desktop\Zerg rush root>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: Read-only file system
C:\Users\PC\Desktop\Zerg rush root>adb push ./Superuser.apk /system/app
failed to copy './Superuser.apk' to '/system/app/Superuser.apk': Read-only file
system
C:\Users\PC\Desktop\Zerg rush root>adb install ./androidterm.apk
3939 KB/s (92780 bytes in 0.023s)
pkg: /data/local/tmp/androidterm.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\Users\PC\Desktop\Zerg rush root>adb wait-for-device
C:\Users\PC\Desktop\Zerg rush root>adb shell sync
C:\Users\PC\Desktop\Zerg rush root>pause
Press any key to continue . . .
I did a quick search on the forums, and learned that i could directly download a img and flash it through clockwork (PH85img.rar) but i don't have a sd card and i can't seem to get clockwork to run a file from the amaze's internal storage.
help would be greatly appreciated.
C:\Users\masroorkhan\Desktop\Zerg rush root>adb wait-for-device
C:\Users\masroorkhan\Desktop\Zerg rush root>adb push zergRush /data/local/
1883 KB/s (21215 bytes in 0.011s)
C:\Users\masroorkhan\Desktop\Zerg rush root>adb shell chmod 777 /data/local/zerg
Rush
C:\Users\masroorkhan\Desktop\Zerg rush root>adb shell rm /data/local/tmp/*sh
rm failed for /data/local/tmp/*sh, No such file or directory
C:\Users\masroorkhan\Desktop\Zerg rush root>adb shell /data/local/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.
[-] Cannot copy boomsh.: Permission denied
C:\Users\masroorkhan\Desktop\Zerg rush root>adb wait-for-device
C:\Users\masroorkhan\Desktop\Zerg rush root>adb shell sleep 1
C:\Users\masroorkhan\Desktop\Zerg rush root>adb remount
remount failed: Operation not permitted
C:\Users\masroorkhan\Desktop\Zerg rush root>adb shell mount -o rw,remount rootfs
/
mount: Operation not permitted
C:\Users\masroorkhan\Desktop\Zerg rush root>adb shell mount -o remount,suid /dev
/block/mmcblk0p29 /system
mount: Operation not permitted
C:\Users\masroorkhan\Desktop\Zerg rush root>adb shell chmod 4755 /system/bin/sh
Unable to chmod /system/bin/sh: Read-only file system
C:\Users\masroorkhan\Desktop\Zerg rush root>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Users\masroorkhan\Desktop\Zerg rush root>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Users\masroorkhan\Desktop\Zerg rush root>adb push ./busybox /system/bin
failed to copy './busybox' to '/system/bin/busybox': Read-only file system
C:\Users\masroorkhan\Desktop\Zerg rush root>adb shell chmod 4755 /system/bin
Unable to chmod /system/bin: Read-only file system
C:\Users\masroorkhan\Desktop\Zerg rush root>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Users\masroorkhan\Desktop\Zerg rush root>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Users\masroorkhan\Desktop\Zerg rush root>adb push ./Superuser.apk /system/app
failed to copy './Superuser.apk' to '/system/app/Superuser.apk': Read-only file
system
C:\Users\masroorkhan\Desktop\Zerg rush root>adb install ./androidterm.apk
failed to copy './androidterm.apk' to '/data/local/tmp/androidterm.apk': Permiss
ion denied
C:\Users\masroorkhan\Desktop\Zerg rush root>adb wait-for-device
C:\Users\masroorkhan\Desktop\Zerg rush root>adb shell sync
C:\Users\masroorkhan\Desktop\Zerg rush root>pause
Press any key to continue . . .
We have a temp root?
Sent from my Amaze 4G using xda app-developers app
Did u extract (SDK) into c/: DRIVE. After it'll have folders AndroidSDK, Tools ,fastboot all folders, once that is done in your c/: DRIVE. Open command prompt type c/ , then AndroidSDK or however u spelled it, then type CD/ tools or just tools, and hopefully after that ur SDK IS set up, if so after all that type in fastboot devices then enter. If good ur device I.D should pop up and now ur good to go. If not just .... P.M.... ME
Use my toolkit.
http://forum.xda-developers.com/showthread.php?t=1493905
Also, ZergRush was only for 1.36 ROMs. This has been patched up a long time ago.
I have rooted my hdx8.9, and then I reroot it. Now I have some problem, I want to root my hdx again, but Ican't root it again, I have pushed the 4 files, but it didn't continue. It shows
Waiting for device ...
Pushing files ...
push: .\scripts\superuser/superuser.sh -> /data/local/tmp/superuser.sh
push: .\scripts\superuser/Superuser.apk -> /data/local/tmp/Superuser.apk
push: .\scripts\superuser/su -> /data/local/tmp/su
push: .\scripts\superuser/exploit -> /data/local/tmp/exploit
4 files pushed. 0 files skipped.
3401 KB/s (2845659 bytes in 0.817s)
/system/bin/sh: chmod: not found
/system/bin/sh: chmod: not found
Running the exploit ...
/system/bin/sh: /data/local/tmp/exploit: can't execute: Permission denied
Check the output. Does it looks fine?
What can I do, I want to full restore to stock rom to fix some proble as the post 'http://forum.xda-developers.com/showthread.php?t=2582773' says, but it
need your device rooted first.
Thanks.
Show us the script body you're pushing.
If you're using some ready scripts I assume the name of it is superuser.sh
CrashThump said:
Show us the script body you're pushing.
If you're using some ready scripts I assume the name of it is superuser.sh
Click to expand...
Click to collapse
I use the tool from the post “[ROOT] Rooting tutorial - hdx 8.9" 14.3.1.0” http://http://forum.xda-developers.com/showthread.php?t=2545957
@sdcardsd, Did you tried to use expression '/system/bin/toolbox chmod' instead of '/system/bin/chmod' in rootme.sh? For me it seems that you've lost the symlink. This may be caused by some busybox installation and removal.
CrashThump said:
@sdcardsd, Did you tried to use expression '/system/bin/toolbox chmod' instead of '/system/bin/chmod' in rootme.sh? For me it seems that you've lost the symlink. This may be caused by some busybox installation and removal.
Click to expand...
Click to collapse
I don't know whether I use these expression '/system/bin/toolbox chmod' instead of '/system/bin/chmod' in rootme.sh, I only use the tools to root my kindle. But I really installed busybox and then removal it by recovery to the factory reset after I reroot my device. Then I have some problem on my kindle, I think the system files be destoryed, so I want to full restore the original ROM, but I can't root my device again. And if it is caused by losing the symlink, how to fix it ? Thanks.
@sdcardsd, then make a suggested replace
CrashThump said:
@sdcardsd, then make a suggested replace
Click to expand...
Click to collapse
The only way is to replace my device? But it is very inconvenient for me, I'am not in America.
15 8556535
@sdcardsd, just replace '/system/bin/chmod' by '/system/bin/toolbox chmod' in 'rootme.sh' file.
CrashThump said:
@sdcardsd, just replace '/system/bin/chmod' by '/system/bin/toolbox chmod' in 'rootme.sh' file.
Click to expand...
Click to collapse
#!/system/bin/sh
/system/bin/mount -o remount,rw /system
/system/bin/cat /data/local/tmp/su > /system/xbin/su
/system/bin/chown 0.0 /system/xbin/su
/system/bin/chmod 06755 /system/xbin/su
your mean I modify the rootme.sh into
#!/system/bin/sh
/system/bin/mount -o remount,rw /system
/system/bin/cat /data/local/tmp/su > /system/xbin/su
/system/bin/chown 0.0 /system/xbin/su
/system/bin/toolbox chmod 06755 /system/xbin/su
CrashThump said:
@sdcardsd, just replace '/system/bin/chmod' by '/system/bin/toolbox chmod' in 'rootme.sh' file.
Click to expand...
Click to collapse
I have replace the rootme.sh into
/system/bin/sh
/system/bin/mount -o remount,rw /system
/system/bin/cat /data/local/tmp/su > /system/xbin/su
/system/bin/chown 0.0 /system/xbin/su
/system/bin/toolbox chmod 06755 /system/xbin/su
but it didn't work
the display is
======================================================================
======================================================================
Welcome to Kindle Root Utility (Faznx92 version)
Special Thanks to:
jcase
fi01
======================================================================
======================================================================
WARNING THIS WORKS ONLY WITH KINDLE HDX 8.9" version 14.3.1.0
======================================================================
======================================================================
Please connect Device with enabled USB-Debugging to your Computer!
Device connected. Pushing files...
680 KB/s (104564 bytes in 0.150s)
1 KB/s (196 bytes in 0.168s)
2024 KB/s (507888 bytes in 0.245s)
Changing permissions...
/system/bin/sh: chmod: not found
/system/bin/sh: chmod: not found
Executing Exploit (could take some minutes, be patient!)
Hit ENTER to continue
/system/bin/sh: /data/local/tmp/exploit: can't execute: Permission denied
Type "su" to check for root!
/system/bin/sh: /system/etc/mkshrc[8]: id: not found
@android:/ $
@android:/ $ su
su
/system/bin/sh: su: not found
127 @android:/ $
same for lines 24-25 of runme.bat
Code:
adb shell chmod 755 /data/local/tmp/rootme.sh
adb shell chmod 755 /data/local/tmp/exploit
change to
Code:
adb shell /system/bin/toolbox chmod 755 /data/local/tmp/rootme.sh
adb shell /system/bin/toolbox chmod 755 /data/local/tmp/exploit
CrashThump said:
same for lines 24-25 of runme.bat
Code:
adb shell chmod 755 /data/local/tmp/rootme.sh
adb shell chmod 755 /data/local/tmp/exploit
change to
Code:
adb shell /system/bin/toolbox chmod 755 /data/local/tmp/rootme.sh
adb shell /system/bin/toolbox chmod 755 /data/local/tmp/exploit
Click to expand...
Click to collapse
I replace the runme.bat
the display is changed, but it didn't work.
======================================================================
======================================================================
Welcome to Kindle Root Utility (Faznx92 version)
Special Thanks to:
jcase
fi01
======================================================================
======================================================================
WARNING THIS WORKS ONLY WITH KINDLE HDX 8.9" version 14.3.1.0
======================================================================
======================================================================
Please connect Device with enabled USB-Debugging to your Computer!
Device connected. Pushing files...
1041 KB/s (104564 bytes in 0.098s)
2 KB/s (196 bytes in 0.083s)
2128 KB/s (507888 bytes in 0.233s)
Changing permissions...
Executing Exploit (could take some minutes, be patient!)
Hit ENTER to continue
press any key to continue. . .
Device detected: KFAPWI (JDQ39)
Attempt acdb exploit...
KFAPWI (JDQ39) is not supported.
Attempt fj_hdcp exploit...
Attempt msm_cameraconfig exploit...
Detected kernel physical address at 0x00008000 form iomem
Attempt put_user exploit...
/data/local/tmp/rootme.sh[2]: /system/bin/mount: not found
/data/local/tmp/rootme.sh[3]: can't create /system/xbin/su: Read-only file syste
m
Unable to chown /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
press any key to continue. . .
Type "su" to check for root!
/system/bin/sh: /system/etc/mkshrc[8]: id: not found
@android:/ $ SU
SU
/system/bin/sh: SU: not found
127 @android:/ $
Hummmm. I'm looking into this but can't this week I'm super busy. I don't have the 8.9" I have the 7" so it is hard for me to test. I'm not sure if moving the rootme.sh was a good idea. I think the exploit code isn't finding it. You may need a rebuild of the exploit file. I say throw your question in here to see if someone can help. Still, just hope for the best.
@sdcardsd,
Code:
#!/system/bin/sh
/system/bin/toolbox mount -o remount,rw /system
/system/bin/toolbox cat /data/local/tmp/su > /system/xbin/su
/system/bin/toolbox chown 0.0 /system/xbin/su
/system/bin/toolbox chmod 6755 /system/xbin/su
/system/bin/toolbox ln -s /system/xbin/su /system/bin/su
CrashThump said:
@sdcardsd,
Code:
#!/system/bin/sh
/system/bin/toolbox mount -o remount,rw /system
/system/bin/toolbox cat /data/local/tmp/su > /system/xbin/su
/system/bin/toolbox chown 0.0 /system/xbin/su
/system/bin/toolbox chmod 6755 /system/xbin/su
/system/bin/toolbox ln -s /system/xbin/su /system/bin/su
Click to expand...
Click to collapse
I replace the rootme.sh into
#!/system/bin/sh
/system/bin/toolbox toolbox mount -o remount,rw /system
/system/bin/toolbox cat /data/local/tmp/su > /system/xbin/su
/system/bin/toolbox chown 0.0 /system/xbin/su
/system/bin/toolbox chmod 06755(or 6755) /system/xbin/su
/system/bin/toolbox ln -s /system/xbin/su /system/bin/su
but it didn't work
======================================================================
======================================================================
Welcome to Kindle Root Utility (Faznx92 version)
Special Thanks to:
jcase
fi01
======================================================================
======================================================================
WARNING THIS WORKS ONLY WITH KINDLE HDX 8.9" version 14.3.1.0
======================================================================
======================================================================
Please connect Device with enabled USB-Debugging to your Computer!
Device connected. Pushing files...
1215 KB/s (104564 bytes in 0.084s)
5 KB/s (284 bytes in 0.050s)
2194 KB/s (507888 bytes in 0.226s)
Changing permissions...
Executing Exploit (could take some minutes, be patient!)
Hit ENTER to continue
press any key to continue. . .
Device detected: KFAPWI (JDQ39)
Attempt acdb exploit...
KFAPWI (JDQ39) is not supported.
Attempt fj_hdcp exploit...
Attempt msm_cameraconfig exploit...
Detected kernel physical address at 0x00008000 form iomem
Attempt put_user exploit...
link failed File exists
press any key to continue. . .
Type "su" to check for root!
/system/bin/sh: /system/etc/mkshrc[8]: id: not found
@android:/ $ su
su
[email protected]:/ #
Faznx92 said:
Hummmm. I'm looking into this but can't this week I'm super busy. I don't have the 8.9" I have the 7" so it is hard for me to test. I'm not sure if moving the rootme.sh was a good idea. I think the exploit code isn't finding it. You may need a rebuild of the exploit file. I say throw your question in here to see if someone can help. Still, just hope for the best.
Click to expand...
Click to collapse
Thanks, I will wait for the good news.
@sdcardsd, what didn't work? you've got the su working. you've got the root.
CrashThump said:
@sdcardsd, what didn't work? you've got the su working. you've got the root.
Click to expand...
Click to collapse
I can rostore my device, thanks.
sdcardsd said:
But I didn't have the Superuser，and I can‘t edit the system file， such as the build.prop, it don't have the root right. and the root explorer also can't be opened.
Click to expand...
Click to collapse
this root exploit doesn't auto-install superuser (well it didn't for me), you either have to side-load it or get it through a store. Also if root explorer isn't working have you tried es file explorer? Additionally, you'll have to remount the system folder as rw before you can edit any system files. This can be done through adb shell with the command "mount -o rw,remount /system" after you use the su command. Just as a forewarning, be super careful when editing everything, the kindle is super sensitive to build.prop changes. I boot looped early on, so just as a warning.
S_transform said:
this root exploit doesn't auto-install superuser (well it didn't for me), you either have to side-load it or get it through a store. Also if root explorer isn't working have you tried es file explorer? Additionally, you'll have to remount the system folder as rw before you can edit any system files. This can be done through adb shell with the command "mount -o rw,remount /system" after you use the su command. Just as a forewarning, be super careful when editing everything, the kindle is super sensitive to build.prop changes. I boot looped early on, so just as a warning.
Click to expand...
Click to collapse
Thanks, I have full restore my device, and I think all is ok now.