Found a one root script. Just need to see if it'll work on the Amaze. If it does, I'll add it in my tool and give proper credits as always. If not, I'll look into it myself.
Prerequisites?
_________________________
Am I on Candid Camera?
Same as usual. S-off or unlock boot loader.
I will be able to help after work in few hours if still needed. Unless I don't need a computer, in which if that's the case, I'll help ya out now
_________________________
Am I on Candid Camera?
You need a computer, I just need a few testers. Thanks GG!
hasoon2000 said:
You need a computer, I just need a few testers. Thanks GG!
Click to expand...
Click to collapse
I'm home I'm an hour and half... I'll ccheck in then. No prob
_________________________
Am I on Candid Camera?
replacement is due in an hour or two so I will test it then.
zPacKRat said:
replacement is due in an hour or two so I will test it then.
Click to expand...
Click to collapse
Before you s-off/unlock your boot loader, run the script. Tell me if it works. If it does, reboot the phone twice and see if it is a perm root or temp root.
Wife says I'm busy :banghead:
Sorry 4 now
_________________________
Am I on Candid Camera?
hasoon2000 said:
Before you s-off/unlock your boot loader, run the script. Tell me if it works. If it does, reboot the phone twice and see if it is a perm root or temp root.
Click to expand...
Click to collapse
first attempt it hangs:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
749 KB/s (2005736 bytes in 2.613s)
640 KB/s (91980 bytes in 0.140s)
713 KB/s (570342 bytes in 0.781s)
REBOOT
cannot create /data/local.prop: permission denied
AGAIN REBOOT
After rebooting from power button it provided the following:
AGAIN!?
mount: Operation not permitted
mount: Operation not permitted
cannot create /system/xbin/busybox: read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
busybox: permission denied
busybox: permission denied
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
rm failed for /data/local.prop, No such file or directory
Unlock your boot loader and try it.
hasoon2000 said:
Unlock your boot loader and try it.
Click to expand...
Click to collapse
same!
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
4544 KB/s (2005736 bytes in 0.431s)
3592 KB/s (91980 bytes in 0.025s)
2978 KB/s (570342 bytes in 0.187s)
REBOOT
cannot create /data/local.prop: permission denied
AGAIN REBOOT
AGAIN!?
mount: Operation not permitted
mount: Operation not permitted
cannot create /system/xbin/busybox: read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
busybox: permission denied
busybox: permission denied
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
rm failed for /data/local.prop, No such file or directory
Flash a recovery. Boot into recovery, run the command. Sorry for all this lol
from 4ext nothing, just hangs.
Hold on, adb is giving me issues.
Alright. Try CWM
no go from cwm
it seems that in recovery it hangs a "@adb wait-for-device"
below is what happened when I removed the wait for device command and changed reboot to reboot recovery.
I had dropped the last part of the script in manually to finish the process.
* server not running *
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
788 KB/s (2005736 bytes in 2.483s)
747 KB/s (91980 bytes in 0.120s)
704 KB/s (570342 bytes in 0.791s)
mv: can't rename '/data/local/tmp': No such file or directory
REBOOT
error: device offline
AGAIN REBOOT
error: device offline
AGAIN!?
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "echo ro.kernel.qemu=1 > /data/local.prop"
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>ECHO
AGAIN REBOOT
AGAIN REBOOT
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
reboot recovery
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "mount -wo remount rootfs /"
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "mount -o remount,rw -t ext4
/dev/block/mmcblk0p30 on /cache type ext4 (rw,nodev,noatime,nodiratime,barrier=1
,data=ordered)
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>/dev
/block/mmcblk0p33 /system"
The system cannot find the path specified.
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "cat /data/local/busybox >
/sbin/sh: syntax error: unexpected end of file
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>/sys
tem/xbin/busybox"
The system cannot find the path specified.
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "chmod 777 /system/xbin/busybox"
chmod: /system/xbin/busybox: No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "/system/xbin/busybox --install -s
/sbin/sh: /system/xbin/busybox: not found
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>/sys
tem/xbin"
The system cannot find the path specified.
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "busybox cp /data/local/Superuser.apk
BusyBox v1.19.3-cm9 static (2011-11-20 14:44 +0100) multi-call binary.
Usage: cp [OPTIONS] SOURCE DEST
Copy SOURCE to DEST, or multiple SOURCE(s) to DIRECTORY
-a Same as -dpR
-R,-r Recurse
-d,-P Preserve symlinks (default if -R)
-L Follow all symlinks
-H Follow symlinks on command line
-p Preserve file attributes if possible
-f Overwrite
-i Prompt before overwrite
-l,-s Create (sym)links
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>/sys
tem/app/Superuser.apk"
The system cannot find the path specified.
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "busybox cp /data/local/su /system/xbin/su"
cp: can't stat '/data/local/su': No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "chown 0.0 /system/xbin/su"
chown: /system/xbin/su: No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "chmod 06755 /system/xbin/su"
chmod: /system/xbin/su: No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "chmod 644 /system/app/Superuser.apk"
chmod: /system/app/Superuser.apk: No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "rm /data/local.prop"
rm: can't remove '/data/local.prop': No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "rm /data/local/tmp"
rm: can't remove '/data/local/tmp': No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "mv /data/local/tmp.bak /data/local/tmp"
mv: can't rename '/data/local/tmp.bak': No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>
try this. It will reboot you in recovery
Just a heads up, I've s-offed and am upgrading to ICS because I have to get it ready for work tomorrow. let me know if there is any other way I can help.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Wait til you are in recovery, then press a button
Press any key to continue . . .
6359 KB/s (2005736 bytes in 0.308s)
6416 KB/s (91980 bytes in 0.014s)
5460 KB/s (570342 bytes in 0.102s)
mv: can't rename '/data/local/tmp': No such file or directory
mount: mounting /dev/block/mmcblk0p33 on /system failed: Invalid argument
/sbin/sh: can't create /system/xbin/busybox: nonexistent directory
chmod: /system/xbin/busybox: No such file or directory
/sbin/sh: /system/xbin/busybox: not found
cp: can't create '/system/app/Superuser.apk': No such file or directory
cp: can't create '/system/xbin/su': No such file or directory
chown: /system/xbin/su: No such file or directory
chmod: /system/xbin/su: No such file or directory
chmod: /system/app/Superuser.apk: No such file or directory
mv: can't rename '/data/local/tmp.bak': No such file or directory
C:\Users\user.account\Desktop\Oneclickroot>
I wouldn't recommend running this batch script on Amaze.
It doesn't even know where our system partition is mounted.
And if my memory is correct, we won't have root previledge to do much with adb shell right after unlocking the bootloader; we need to flash su binary using updater-script to begin with. As for the busybox, just install the 'busybox installer' so that users can run it in Android.
BTW, your all-in-one tool is very handy. Why no 4EXT recovery, though...
ringochan said:
I wouldn't recommend running this batch script on Amaze.
It doesn't even know where our system partition is mounted.
And if my memory is correct, we won't have root previledge to do much with adb shell right after unlocking the bootloader; we need to flash su binary using updater-script to begin with. As for the busybox, just install the 'busybox installer' so that users can run it in Android.
BTW, your all-in-one tool is very handy. Why no 4EXT recovery, though...
Click to expand...
Click to collapse
His tool does have ext4... You just have to get the full version from android-dev
Sent from my HTC_Amaze_4G using Tapatalk 2
Some time ago I rooted with photo torpedo direct v1.1. Then I did a factory reset ..
Now I would like to remove root and go back to "stock"
When running photon torpedo direct and choosing 2. Root Cleaner (unroot) I get the following...
Code:
Sending Torpedo to Phone
1008 KB/s (2817536 bytes in 2.727s)
Setting Permissions
chmod: permission denied
Unpacking Torpedo
/bin/tar: not found
Press any key to continue . . .
Likewise I get the same error when attempting to root.
I tried using adb manually to see if those tools even exist and get the following.
Code:
c:\root>adb.exe shell
$ chmod
chmod
chmod: permission denied
$ /bin/tar
/bin/tar
/bin/tar: not found
$ su
su
# chomd
chomd
chomd: not found
# /bin/tar
/bin/tar
/bin/tar: not found
#
Please help I seem to be stuck in some limbo mode.
I gave up trying to fix the issue and reflashed using this post
Synicasm said:
Some time ago I rooted with photo torpedo direct v1.1. Then I did a factory reset ..
Now I would like to remove root and go back to "stock"
When running photon torpedo direct and choosing 2. Root Cleaner (unroot) I get the following...
Code:
Sending Torpedo to Phone
1008 KB/s (2817536 bytes in 2.727s)
Setting Permissions
chmod: permission denied
Unpacking Torpedo
/bin/tar: not found
Press any key to continue . . .
Likewise I get the same error when attempting to root.
I tried using adb manually to see if those tools even exist and get the following.
Code:
c:\root>adb.exe shell
$ chmod
chmod
chmod: permission denied
$ /bin/tar
/bin/tar
/bin/tar: not found
$ su
su
# chomd
chomd
chomd: not found
# /bin/tar
/bin/tar
/bin/tar: not found
#
Please help I seem to be stuck in some limbo mode.
Click to expand...
Click to collapse
Dear Users,
I have a tablet - Acer Iconia A1-B71, which works fine but I dont have root permission what is very annoying when I want to do something with Files Manager or Total Commander. I readed this thread:
http://forum.xda-developers.com/showthread.php?t=2240029
But for my bad I get errors. Below is a log file from CMD:
http://pastebin.com/EEiihY01
The most important part is this (I think):
Enter a selection:
system.img.gz found in folder 'system_image'.
/data/local/tmp/busybox telnet 127.0.0.1 1234
chmod 777 /cache
chmod 777 /cache/system.img.gz
[email protected]:/ $ /data/local/tmp/busybox telnet 127.0.0.1 1234
telnet: can't connect to remote host (127.0.0.1): Connection refused
1|[email protected]:/ $ chmod 777 /cache
Unable to chmod /cache: Operation not permitted
10|[email protected]:/ $ chmod 777 /cache/system.img.gz
Unable to chmod /cache/system.img.gz: Permission denied
10|[email protected]:/ $ exit
failed to copy 'system_image\system.img.gz' to '/cache/system.img.gz': Permissio
n denied
opendir failed, Permission denied
Failed to copy system.img.gz. Make sure the folder 'system_image' of this toolki
t contains a system.img.gz suiting to your installed firmware.
Press Enter to leave Application...
Click to expand...
Click to collapse
If you can tell me - Am I doing something wrong? Is there any solution?
Thank you for the smallest help.
Kind Regards,
Raintek
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.