HI, I need help, my little brother installed ChainFire's 3D app on it I don´t know what it did but now it wont boot, to make things worst he tried to fix it doing a reset, fortunatelly (or not) I've checked root permissions with the Vroot and showed it still has root permissions, is there any way to to recover it?
?
SiulGM said:
HI, I need help, my little brother installed ChainFire's 3D app on it I don´t know what it did but now it wont boot, to make things worst he tried to fix it doing a reset, fortunatelly (or not) I've checked root permissions with the Vroot and showed it still has root permissions, is there any way to to recover it?
Click to expand...
Click to collapse
I have heard of that happening... Have you tried Google search chainfire 3d apk. Brick repair? Or forum search I have heard of it quite frequently so I know there has to be a fix here somewhere at xda ....
jimyv said:
I have heard of that happening... Have you tried Google search chainfire 3d apk. Brick repair? Or forum search I have heard of it quite frequently so I know there has to be a fix here somewhere at xda ....
Click to expand...
Click to collapse
thank you! I've found a thread here but every time I try to execute "cf3d_uninstall.sh" it shows "not found" I've already pulled "system/lib" and the file exist, am I doing something wrong?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/url]
imagen jpg[/IMG]
SiulGM said:
thank you! I've found a thread here but every time I try to execute "cf3d_uninstall.sh" it shows "not found" I've already pulled "system/lib" and the file exist, am I doing something wrong?
[/url]
imagen jpg[/IMG]
Click to expand...
Click to collapse
Adb reboot?
jimyv said:
Adb reboot?
Click to expand...
Click to collapse
abd reboot??? already did the reboot, but still leads me to the "kindle fire" screen, tried to push the renamed files but is not allowed, is there any way to push files to system/lib ? or rename them using adb?
SiulGM said:
thank you! I've found a thread here but every time I try to execute "cf3d_uninstall.sh" it shows "not found" I've already pulled "system/lib" and the file exist, am I doing something wrong?
[/url]
imagen jpg[/IMG]
Click to expand...
Click to collapse
Use adb shell to manually remove (rm) the files installed. Open that bat script in a text editor & then manually do it from your platform tools or wherever you adb is setup to run from. You'll probably need to manually mount the system/lib folder to rw first.
---------- Post added at 10:39 AM ---------- Previous post was at 10:31 AM ----------
SiulGM said:
abd reboot??? already did the reboot, but still leads me to the "kindle fire" screen, tried to push the renamed files but is not allowed, is there any way to push files to system/lib ? or rename them using adb?
Click to expand...
Click to collapse
the rm command.
adb shell rm -r /system/lib/WhateverFileNameHere.so
Don't forget to mount RW first using:
adb shell
su
mount -o remount,rw /system
Though you may need to push busybox binary & applets to xbin first.
Also, if su access is giving you issues, you can try pushing the SuperSu binary first too.
GSLEON3 said:
Use adb shell to manually remove (rm) the files installed. Open that bat script in a text editor & then manually do it from your platform tools or wherever you adb is setup to run from. You'll probably need to manually mount the system/lib folder to rw first.
---------- Post added at 10:39 AM ---------- Previous post was at 10:31 AM ----------
the rm command.
adb shell rm -r /system/lib/WhateverFileNameHere.so
Don't forget to mount RW first using:
adb shell
su
mount -o remount,rw /system
Though you may need to push busybox binary & applets to xbin first.
Also, if su access is giving you issues, you can try pushing the SuperSu binary first too.
Click to expand...
Click to collapse
Thanks for your help, I'm sorry may be I'm not getting this, I'm new to adb,.. I tried and get this error
[/url]
subefotos[/IMG]
this is the text in the unistaller file, but how do I shoul execute this manually?
"#!/system/bin/sh
mount -o rw -o remount /dev/block/platform/msm_sdcc.1/by-name/system /system
stop
cat /system/lib/libGLESv1_CM_ORG_CF3D.so > /system/lib/libGLESv1_CM.so
chown 1000.1000 /system/lib/libGLESv1_CM.so
chown 1000:1000 /system/lib/libGLESv1_CM.so
chown system.system /system/lib/libGLESv1_CM.so
chown system:system /system/lib/libGLESv1_CM.so
chmod 644 /system/lib/libGLESv1_CM.so
cat /system/lib/libGLESv2_ORG_CF3D.so > /system/lib/libGLESv2.so
chown 1000.1000 /system/lib/libGLESv2.so
chown 1000:1000 /system/lib/libGLESv2.so
chown system.system /system/lib/libGLESv2.so
chown system:system /system/lib/libGLESv2.so
chmod 644 /system/lib/libGLESv2.so
#rm /system/lib/libGLESv1_CM_ORG_CF3D.so
#rm /system/lib/libGLESv2_ORG_CF3D.so
rm /system/lib/cf3d_uninstall.sh
rm /system/lib/cf3d_sh
reboot -f
reboot
reboot normal
toolbox reboot
busybox reboot -f
busybox reboot
busybox reboot normal"
SiulGM said:
Thanks for your help, I'm sorry may be I'm not getting this, I'm new to adb,.. I tried and get this error
[/url]
subefotos[/IMG]
Click to expand...
Click to collapse
Each line is a new entry, do not run them together. Try this:
adb shell
su
mount -o remount,rw /system
now open a second command prompt window & leave the first open. In the second window enter the following:
adb shell
su
rm -r /system/lib/*cf3d.so
rm -r /system/lib/libGLESv*.so
Now open the ota or rom version you are on & extract the original LibGLESv* files & go back to first window & type this
exit
exit
adb push libGLESv1_CM.so /system/lib/
adb push libGLESv2.so /system/lib/
adb shell
su
chmod 644 /system/lib/*.so
chown root.root /system/lib/*.so
reboot
Make sure to extract the original lib files to the working folder for adb, i.e., wherever it says you are in the cmd window, the PC folder you see at the start of the cmd window.
GSLEON3 said:
Each line is a new entry, do not run them together. Try this:
adb shell
su
mount -o remount,rw /system
now open a second command prompt window & leave the first open. In the second window enter the following:
adb shell
su
rm -r /system/lib/*cf3d.so
rm -r /system/lib/LibGLESv*.so
Now open the ota or rom version you are on & extract the original LibGLESv* files & go back to first window & type this
exit
exit
adb push libGLESv1_CM.so /system/lib/
adb push libGLESv2.so /system/lib/
adb shell
su
chmod 644 /system/lib/*.so
chown root.root /system/lib/*.so
reboot
Make sure to extract the original lib files to the working folder for adb, i.e., wherever it says you are in the cmd window, the PC folder you see at the start of the cmd window.
Click to expand...
Click to collapse
Well... I think I did something relly worng... it just shows "kindle fire" on gray... then the system recovery
[/url]
subir fotos online[/IMG]
SiulGM said:
Well... I think I did something relly worng... it just shows "kindle fire" on gray... then the system recovery
[/url]
subir fotos online[/IMG]
Click to expand...
Click to collapse
I can't really tell much from a cropped screen image...
At what point did you have issues? You downloaded & pushed the original libs before rebooting, right?
Just out of curiosity, who thought it would be a good idea to used drivers that have been out of development for nearly 3 years?
GSLEON3 said:
I can't really tell much from a cropped screen image...
At what point did you have issues? You downloaded & pushed the original libs before rebooting, right?
Click to expand...
Click to collapse
I think I've deleted system/lib... btw, is not cropped, that is the way is showed on screen
SiulGM said:
I think I've deleted system/lib... btw, is not cropped, that is the way is showed on screen
Click to expand...
Click to collapse
How did you do that? You need to set the viewable width & the cache scroll to be bigger. That way you can see everything you type.
GSLEON3 said:
How did you do that? You need to set the viewable width & the cache scroll to be bigger. That way you can see everything you type.
Click to expand...
Click to collapse
I relly don´t know... I think thats I did because of this screen
[/url]
subir imagenes gratis[/IMG]
so.. is there a chance for this to work again?
SiulGM said:
I relly don´t know... I think thats I did because of this screen
[/url]
subir imagenes gratis[/IMG]
so.. is there a chance for this to work again?
Click to expand...
Click to collapse
Try to adb push the original libGLESv files into the system/lib folder. You don't need to shell for that. Just adb push as indicated in the previous posts.
You also may need to try to adb mount
GSLEON3 said:
Try to adb push the original libGLESv files into the system/lib folder. You don't need to shell for that. Just adb push as indicated in the previous posts.
Click to expand...
Click to collapse
OH, I cant now adb is not working I know the kindle is detected because a PDA.net pop up, then I try to get adb shell and shows what´s on the image after a while it reboots to the system recovery
I got this when trying to copy what I pulled fron system/lib
[/url]
subir fotos[/IMG]
GSLEON3 said:
Try to adb push the original libGLESv files into the system/lib folder. You don't need to shell for that. Just adb push as indicated in the previous posts.
You also may need to try to adb mount
Click to expand...
Click to collapse
/lib does not exist, now I've lost su, is there a way to create /lib and then push all the files in? or did I killed it?
SiulGM said:
/lib does not exist, now I've lost su, is there a way to create /lib and then push all the files in? or did I killed it?
Click to expand...
Click to collapse
Yes, but you are going to have to mount first. You may need to use Linux. Unless you entered something not in the above posts, or accidentally hit enter before finishing the command line, lib can't go anywhere, at least not from any of those commands.
GSLEON3 said:
Yes, but you are going to have to mount first. You may need to use Linux. Unless you entered something not in the above posts, or accidentally hit enter before finishing the command line, lib can't go anywhere, at least not from any of those commands.
Click to expand...
Click to collapse
Hi! first I want to thank you for all your help on this! just installed Ubuntu, what should I do now?
I would say there is no hope. If you deleted the 'lib' folder, your Kindle cannot execute programs like the adb client. With Safestrap you could reflash the folder. But if you dont have Safestrap... You have a really big problem! . Maybe fastboot could help, but i dont know how
Sent from my GT-I9505
Related
going through the entire 1.5 to 2.1 root tutorial to a tee, but once i get to the recovery image, this happens (following is an entire copy/paste of what I went through, incase i did something wrong before i hit the point)
Code:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Lemcott>cd C:\android-sdk-windows\tools
C:\android-sdk-windows\tools>adb shell mount -o rw,remount /dev/block/mtdblock3
/system
adb server is out of date. killing...
* daemon started successfully *
C:\android-sdk-windows\tools>adb shell mount -o rw,remount /dev/block/mtdblock3
/system
C:\android-sdk-windows\tools>adb push recovery.img /sdcard
1192 KB/s (3926016 bytes in 3.215s)
C:\android-sdk-windows\tools>adb push flash_image /system/bin/flash_image
448 KB/s (9640 bytes in 0.021s)
C:\android-sdk-windows\tools>adb shell flash_image recovery /sdcard/recovery.img
flash_image: permission denied
C:\android-sdk-windows\tools>
EDIT: I am a complete ass hat. nothing to see here, move a long. mods delete this if you please.
P.S. Everyone else: ALWAYS DOUBLE CHECK BEFORE POSTING FOR HELP. *ahem* now be on your way.
try programming thru fastboot. press call + vol down and select the fastboot option and use this command from the pc
fastboot flash recovery recovery.ing
Sent from my Evil Eris v1.1 using the XDA mobile application powered by Tapatalk
It looks like you forgot the step where you modify the flash_image's permissions
Code:
adb shell chmod 755 /system/bin/flash_image
I had the same thing but I just kept reentering
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
and after maybe 4 iterations it worked.
I have a very simular problem:
(moto droid with android 2.1)
$su
su
Permission denied
Click to expand...
Click to collapse
I have try to use chmod the file but it said permission denied on chmod... please help T_T
note this is rooted, of course, when i'm in the phone type su, it'll pop up ask for me to allow or not, allowed, everything seems fine, but when i try to modify files in /system/etc/wifi (trying to make it work for ad hoc) it said permission denied....(even in su???) I tried in adb and it's the same, very very frustrating, any help is appreciated, Thanks.
edit: here's what it looks like using chmod...
>adb shell chmod 755 /system
unable to chmod /system: Read-only file system
>
Click to expand...
Click to collapse
penthoy said:
I have a very simular problem:
(moto droid with android 2.1)
I have try to use chmod the file but it said permission denied on chmod... please help T_T
note this is rooted, of course, when i'm in the phone type su, it'll pop up ask for me to allow or not, allowed, everything seems fine, but when i try to modify files in /system/etc/wifi (trying to make it work for ad hoc) it said permission denied....(even in su???) I tried in adb and it's the same, very very frustrating, any help is appreciated, Thanks.
edit: here's what it looks like using chmod...
Click to expand...
Click to collapse
make it read/write
penthoy said:
I have a very simular problem:
(moto droid with android 2.1)
I have try to use chmod the file but it said permission denied on chmod... please help T_T
note this is rooted, of course, when i'm in the phone type su, it'll pop up ask for me to allow or not, allowed, everything seems fine, but when i try to modify files in /system/etc/wifi (trying to make it work for ad hoc) it said permission denied....(even in su???) I tried in adb and it's the same, very very frustrating, any help is appreciated, Thanks.
edit: here's what it looks like using chmod...
Click to expand...
Click to collapse
I wouldn't try to flash anything you find here to a Moto Droid.
This is for the HTC Droid Eris.
Otherwise, and if I'm misunderstanding you, good luck with your problem.
archmagus said:
It looks like you forgot the step where you modify the flash_image's permissions
Code:
adb shell chmod 755 /system/bin/flash_image
Click to expand...
Click to collapse
I've been bashing my head in ALL day trying to get past this and finally found this thread! This worked perfectly!
theboo7 said:
make it read/write
Click to expand...
Click to collapse
How should i make is read/write?????
i cant get it to work at all.. need help plz.
Hello Guys
why cant i mount that **** together, i have the root permission, but also i dont..somehow
Code:
Microsoft Windows [version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. Alle rettigheder forbeholdes.
C:\Users\Rasmus H. G. Johnsen>d:
D:\>cd android\tools
D:\android\tools>adb devices
List of devices attached
HT9B7LG00092 device
D:\android\tools>adb shell mount -o rw,remount /dev/block/mtdbloc3 /system
mount: Operation not permitted
D:\android\tools>adb shell
$ ls
ls
sqlite_stmt_journals
cache
sdcard
etc
system
sys
sbin
proc
logo.rle
init.rc
init.goldfish.rc
init.bahamas.rc
init
default.prop
data
root
dev
$ exit
exit
Also if I go on and try to do this:
Code:
D:\android\tools>adb push flash_image /system/bin
failed to copy 'flash_image' to '/system/bin/flash_image': Read-only file system
I know that the flash_image fil and my recovery.img file is in this library and also on my sdcard, but I cant push the gotdamn flas_image file in the /system/bin catalog.
Can some one please help me ?
PS. I have the USB-debugging turned ON.
How do you know that you have root? Or, how did you gain root?
doogald said:
How do you know that you have root? Or, how did you gain root?
Click to expand...
Click to collapse
I have the app called androot from google market, ang i have run it to get root.
wfdi said:
I have the app called androot from google market, ang i have run it to get root.
Click to expand...
Click to collapse
I'm not aware of that app, and cannot find it in the market myself (do you have a link?)
However, one way to check for sure if you truly have root is run the adb command adb shell and, when you get a prompt, type the command "su". If it returns with a "#" prompt (rather than the "$" prompt that you are seeing), then you have root on the phone.
Most people these days root with either jcase's 1click root for eris: https://market.android.com/details?id=net.andirc.erisrooter or they use the procedure here: http://androidforums.com/eris-all-things-root/127861-universal-eris-root-dummies.html
You may be able to use the steps here as well, since you seem pretty comfortable with adb and have that working already: http://androidforums.com/eris-all-things-root/125436-detailed-leak-root-tutorial.html
Guys new I found another solution (tested on u8150)
First make sure that you are rooted first.
Open adb shell
Type in su.
Remount the system partition as read write.
Change the owner of system from root to system via chown root system
the exit the shell and push flash_image to system/
also push clockworkmodrecover.img into the system partion dont forget the last /.
then exit.
use a file manager, I used rootbrowser.apk without a memory card and installed recovery.
with rootbrowser copy flash_image to the bin directory.
don't forget to change the owner back to root to the system partition after you finish with rootexplorer or whatever u use even adb can work.
then the rest follows.
The above works only if your'e rooted and have adb.
Goodluck
haha am a genius Installing ROM +Recover without sdcard on u8150
all you have to do is:-
1. Make sure u have installed clockwork mode recovery on your device and have su binary.
2. Open adb with the device normally on.
3. Remount the data partition as read write using mount remount in adb .
4. use adb and push the cynogenmode.zip or any rom that fits into the data partition using
adb push romname.zip /data/
5. Reboot into clockworkmod recovery using the various options available.
6. This is what to do if you don't have a sdcard.
open adb with phone connected and run
adb shell
mount /data /sdcard
then go back to the main recovery menu and wipe dalvik cache only
then choose update from sdcard
flash your rom and tadaaa.
your'e done.
NB:CAUTION MAKE SURE TO FLASH A ROM THAT DOES NOT WRITE INTO THE DATA PARTION
THIS CAN BE DONE BY LOOKING FOR A FILE CALL UPDATE SCRIPT IN THE zip OF THE ROM U WANT TO INSTALL
Am going to make a post about this later.
Goodluck
Lol, 3 and a half year break between responses.
The problem with flash_image & dump_image is that it doesn't work on devices devices which use emmc (recent phones)and have
mmcblk0
and cat /proc/mtd won't work here either.
This means that you have to use dd to write to this devices.
I wonder how guys determine the partitions to use on such devices, and someone should hint as to what is going on since it seems manufacturers seriously don't want people to exploit their devices.
All credit goes to the orig guy who made the d2 exploit
If you feel the need to donate money then he deserves it [email protected]
I made an easier to follow tutorial over here with pics. Sorry but I am tired of going back and forth so just go there if you are having problems. If you can follow simple adb commands just follow the directions below
Download and Install Samsung Drivers
64bit:
http://www.wikifilez.com/root files/epic4g/usb_drivers_GalaxyS_x64.zip
32bit:
http://www.wikifilez.com/root files/epic4g/SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe
1 Click Root Method
http://forum.androidcentral.com/fascinate-roms-hacks/33899-how-root.html
Manual Method
cd C:\android-sdk\tools
adb push C:\fascinate\su /sdcard/su
adb push C:\fascinate\rage.bin /data/local/tmp/rage.bin
adb push C:\fascinate\busybox /sdcard/busybox
adb shell
cd /data/local/tmp
chmod 0755 rage.bin
./rage.bin
wait....
when it brings you back to your original shell in windows then follow these commands
adb shell (you should see # this time instead of $ this is exactly what we want)
mount -t rfs -o remount,rw /dev/block/stl9 /system
cd /system/xbin
cat /sdcard/su > su
cat /sdcard/busybox > busybox
chmod 4755 su
chmod 4755 busybox
exit
adb install C:\fascinate\Superuser.apk
This is permanent.
I just updated the files here with the latest su / superuser.apk / busybox
Also check out my tutorial to fix the memory/lag issues for this phone
http://forum.xda-developers.com/showthread.php?p=8086738#post8086738
Dirrk said:
All credit goes to the orig guy who made the d2 exploit
I feel naked without my droid lol this phone is so light
adb push su /sdcard/su
adb push rage.bin /data/local/tmp/rage.bin
adb push busybox /sdcard/busybox
adb shell
cd /data/local/tmp
chmod 0755 rage.bin
./rage.bin
wait....
when it brings you back to your original shell or windows cmd promt
adb shell
mount -t rfs -o remount,rw /dev/block/stl9 /system
cd /system/xbin
cat /sdcard/su > .
cat /scard/busybox > .
chmod 4755 su
chmod 4755 busybox
exit
adb install Superuser.apk
Please let me know if I posted something wrong.
Click to expand...
Click to collapse
does it stick after reboot?
Its supposed to be a temporary root so i doubt it will.
This works on any android phone up to 2.2. I have confirmed this works on my epic, so th same sould work here.
Sent from my SPH-D700 using XDA App
see below.
confirmed root.
Had to use Superuser.apk 2.3.6.1 and the su binary in the package, but the rest worked.. except for that cat command? Why would you cat binary files instead of copying them? (not complaining, just curious). I just adb pushed them to /system/xbin, and adb shell chmod'd them.
You also have a typo near the end "scard" instead of "sdcard".
You can also use mv or cp. I just happen to use cat because I used it the other day rooting my friends stock 2.2 droid. Which required me to use cat.
And yes this is permanent
Cool, i tried using rm -rf to get rid of a directory I created accidentally, and was getting some syntax errors, so I wasn't sure how compatibile the command line on android was to linux.
Glad it's pretty close. Being very familiar with linux makes this pretty easy to understand. Day 1 with an android device was pretty darn fun. I think I'm glad I went this direction.
I just followed this and used the same files I had from my Droid 2 (just updated the Superuser.apk from this sites thread for it) and works perfectly. Rebooted phone did "adb shell" and "su" and still have root, so it is permanent
side note: steps say "/system/xbin" and assume you meant "/system/bin" like Droid 2 was. That's where I put them and it worked.
cliffr39 said:
I just followed this and used the same files I had from my Droid 2 (just updated the Superuser.apk from this sites thread for it) and works perfectly. Rebooted phone did "adb shell" and "su" and still have root, so it is permanent
side note: steps say "/system/xbin" and assume you meant "/system/bin" like Droid 2 was. That's where I put them and it worked.
Click to expand...
Click to collapse
It works either way, both are executable system folders. Glad you it worked for you, hopefully we can get some roms cooking soon and play catch up to the other galaxy s phones
doesnt work for me, i get an error device not found
ive type adb devices - device not found. usb debugging on, usb conneced on port 5037
xirnibor said:
doesnt work for me, i get an error device not found
ive type adb devices - device not found. usb debugging on, usb conneced on port 5037
Click to expand...
Click to collapse
Your USB mode might be set wrong. Flip it to whatever it's not at, and try again.
i forgot this laptop didnt have the updated usb drivers from android sdk, downloading then will try again. i have tried so far with the sdcard mounted and unmounted, while in usb debugging mode. will post after updates
How long do you actually have to wait after the execting the rage.bin file?
itznfb said:
How long do you actually have to wait after the execting the rage.bin file?
Click to expand...
Click to collapse
I dunno, ~20-30 seconds? Assuming sound is enabled you should hear the same USB device connected/disconnected sounds.
If you want to be 100% sure just wait like 90 seconds. I'm pretty sure it killed my shell though, so if it does that, you're good to go.
ok, adb recognizes the device *see below, however when i type adb push su /sdcard/su i get cannot stat 'su': no such file or directory. ?
C:\downloads\android\android\tools>adb devices
List of devices attached
I500a2d0087a device
namebrandon said:
I dunno, ~20-30 seconds? Assuming sound is enabled you should hear the same USB device connected/disconnected sounds.
If you want to be 100% sure just wait like 90 seconds. I'm pretty sure it killed my shell though, so if it does that, you're good to go.
Click to expand...
Click to collapse
ok... running the rage.bin locked up my device twice but on the third try it worked. another fascinate rooted
xirnibor said:
ok, adb recognizes the device *see below, however when i type adb push su /sdcard/su i get cannot stat 'su': no such file or directory. ?
C:\downloads\android\android\tools>adb devices
List of devices attached
I500a2d0087a device
Click to expand...
Click to collapse
su is a file (for our purposes right here, anyway). Unless you explicity specify its path, it needs to be in the same directory you're running the adb command from.
If you installed the Android SDK per guidelines, adb should be in your PATH environment variable, and you should be able to execute it from any directory. If you didn't do that, then for the sake of simplicity, copy all the files referenced in the original steps to your working directory. From your post above, it appears that is c:\downloads\android\android\tools\
I got stuck at cat /sdcard/su > . Is that supposed to be > .? It won't let me enter that...There's not something else that's supposed to be there?
EDIT: I get the same error faspalma
I'm stuck at that point too. cat /sdcard/su > . returns "cannot create .: is a directory"
Ok I have tried many times to root my Epad with no luck. It is a Epad with 512 ram 4gb internal flash and Zt-180 processor. Thing that I have tried z4 root failed trys but then when pushing root it stops and reboots. Universal root it says that the device is rooted and installs super user app, but i go to root explorer and it will not let me rw mount. And I have tried to use adb to push but I get the error can not connect please help thanks
this is what it says everytime I try
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Im still stuck does anybody have an idea what im doing wrong?
gtpdjw said:
Im still stuck does anybody have an idea what im doing wrong?
Click to expand...
Click to collapse
Try installing busy box thru titanium backup.
Hi I have the same ZT-180 , 512k - 4Gb... Running Android 2.2
I have been able to root it, but had to use the Android SDK - ADB, and I needed to download the ARM6 version of busybox and a version of SU I found on this forum.
I've attached a zip of the files I used.
Unzip the zip files onto a USB memory stick.
Put the memory stick into the ZT-180
Make sure your ZT-180 is connected via Wifi or the network cable
On the PC, open a command prompt
CD to your android SDK tools or platform-tools folder
use the next 2 ADB commands
ADB connect (the ip address of your ZT-80):5555
ADB shell
then run each of the following commands in the ADB shell (cut and paste them into the ADB shell, and press return)
After the reboot, the ZT-180 should be rooted.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mv /system/xbin/su /system/xbin/su_original
mv /system/bin/su /system/bin/su_original
busybox cp /udisk/su /system/xbin/su
busybox cp /udisk/su /system/bin/su
chmod 6755 /system/xbin/su
chmod 6755 /system/bin/su
reboot
Thanks a lot, i followed your instruction and my zt-180 2 is finally root
Thank you RogerClark so much!
Many thanks, this is the first 'su' topic that made sense, easy to read and worked!
One question, just to confirm, in doing this java code can now run stuff as super user making my system open to attack?
It's only a play development system so not that bothered.
this worked for me too, many thanks
Something to watch out for which may well stall some who try this - if at some point during the process of entering the commands via ADB shell you receive a failure message 'no such file or directory' - just ignore and persist to the end. Took me some time and googling to discover this.
RogerClark said:
Hi I have the same ZT-180 , 512k - 4Gb... Running Android 2.2
I have been able to root it, but had to use the Android SDK - ADB, and I needed to download the ARM6 version of busybox and a version of SU I found on this forum.
I've attached a zip of the files I used.
Unzip the zip files onto a USB memory stick.
Put the memory stick into the ZT-180
Make sure your ZT-180 is connected via Wifi or the network cable
On the PC, open a command prompt
CD to your android SDK tools or platform-tools folder
use the next 2 ADB commands
ADB connect (the ip address of your ZT-80):5555
ADB shell
then run each of the following commands in the ADB shell (cut and paste them into the ADB shell, and press return)
After the reboot, the ZT-180 should be rooted.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mv /system/xbin/su /system/xbin/su_original
mv /system/bin/su /system/bin/su_original
busybox cp /udisk/su /system/xbin/su
busybox cp /udisk/su /system/bin/su
chmod 6755 /system/xbin/su
chmod 6755 /system/bin/su
reboot
Click to expand...
Click to collapse
I dont seem to be able to get root explorer permissions even after completing these steps successfully :-( Ive tried reflashing with latest flash "10inch_DDR512MB_android+2.2" running above script -> installed root explorer but w/r button wont toggle and stays on r/o. I can install all root apps ok like busybox & others so not sure what you did or full steps you took to get root explorer w/r to work.. i also tried installing z4root 1st then above script and no go, same with androot... managed to get w/r working once before reflashing but noticed it only let me r/w on root and not in subfolders and files in those subfolders so couldnt edit my wifi config.. Any ideas?
EDIT: I reflashed unit again-> followed this manual root guide for V2 zt-180 ( cant show url cause im new here.. that sucks xda!! ) grant root access, tested in terminal that root access ok using su command (usually i would get "file link error: following process above!?) still root explorer fails to detect device is rooted even though i can install all root apps ok..lol.. I wanted to edit my wireless TX to be 20 instead of 100 to save power/improve reception(well known tweak for zt ) so then i mounted system in adb (mount -o rw,remount -t yaffs2 /dev/block/mtdblock1 /system) loaded Android commander in windows -> pulled RT2870STA.dat to my windows box, mad the edit to 20 and saved -> used root explorer on zt to delete RT2870STA.dat ->pushed edited RT2870STA.dat back into zt RT2870STA folder -> remounted read only in adb (
mount -o ro,remount -t yaffs2 /dev/block/mtdblock1 /system ) -> rebooted zt and tested modified wireless ok.
So I guess i can at least follow this process for any other file edits that require root access in subfolders of root drive(\).. until someone suggests an easier solution..
When you run the console on the ePad and type su what message do you get? If it's rooted you can run the su prog, if not will say you don't have access.
RogerClark, I followed your steps. And my results are kind of mixed.
Please help if you can.
I am running the ZT-180v2 512mb 4GB
I also did the 2/25/11 Flash upgrade
When I run the "Root Check v2.1" by joeykrim from the Android market it now says that I have root access and busybox installed.
However, Root Explorer 2.13.4 says "Root access coould not be obtained su failed with the following message: Make sure you granted root permission when requested by SuperUser"
Titanium Backup seems to have root rights.?
Any input??
I have the same pad and the same problem. I have root access, only root-explorer version 2.13.4 says I don't. I'm seeing it I can get an older version of it and see if it works. The first time I rooted my pad I had an older version of root-explorer that did work.
Will update my post if I get it to work...
update SDK
be sure after installing that you update all installed packages in the SDK Manager. i could not connect until i updated all a few times.
great post. Got root. Thanks a lot.
Now my 10" V1 zt-180 is rooted I can run su from an application and so do root stuff, but what I need to do is elevate my running app to root user. Any ideas?
P.s. I rooted my device a 2nd time after installing 2.2 with no problems.
Thanks.
Is there any way to back the rom before it is rooted?. So if anything goes wrong I can return it to the original state.
SoundGuy_025 said:
Is there any way to back the rom before it is rooted?. So if anything goes wrong I can return it to the original state.
Click to expand...
Click to collapse
Download the 5-3-11 rom, if anything goes wrong, just flash that and start over with the newest rom. 5-3-11 fixes most of the issues.
RogerClark said:
Hi I have the same ZT-180 , 512k - 4Gb... Running Android 2.2
I have been able to root it, but had to use the Android SDK - ADB, and I needed to download the ARM6 version of busybox and a version of SU I found on this forum.
I've attached a zip of the files I used.
Unzip the zip files onto a USB memory stick.
Put the memory stick into the ZT-180
Make sure your ZT-180 is connected via Wifi or the network cable
On the PC, open a command prompt
CD to your android SDK tools or platform-tools folder
use the next 2 ADB commands
ADB connect (the ip address of your ZT-80):5555
ADB shell
then run each of the following commands in the ADB shell (cut and paste them into the ADB shell, and press return)
After the reboot, the ZT-180 should be rooted.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mv /system/xbin/su /system/xbin/su_original
mv /system/bin/su /system/bin/su_original
busybox cp /udisk/su /system/xbin/su
busybox cp /udisk/su /system/bin/su
chmod 6755 /system/xbin/su
chmod 6755 /system/bin/su
reboot
Click to expand...
Click to collapse
ok I get - no such file or directory after "busybox cp /udisk......." finished the process and tried to start over. then after mv /system/bin/su ......" I get "No such file or directory.
my luck of course cause everyone else it works any way. what should I do? from here?
usb stick
RogerClark said:
Hi I have the same ZT-180 , 512k - 4Gb... Running Android 2.2
I have been able to root it, but had to use the Android SDK - ADB, and I needed to download the ARM6 version of busybox and a version of SU I found on this forum.
I've attached a zip of the files I used.
Unzip the zip files onto a USB memory stick.
Put the memory stick into the ZT-180
Make sure your ZT-180 is connected via Wifi or the network cable
On the PC, open a command prompt
CD to your android SDK tools or platform-tools folder
use the next 2 ADB commands
ADB connect (the ip address of your ZT-80):5555
ADB shell
then run each of the following commands in the ADB shell (cut and paste them into the ADB shell, and press return)
After the reboot, the ZT-180 should be rooted.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mv /system/xbin/su /system/xbin/su_original
mv /system/bin/su /system/bin/su_original
busybox cp /udisk/su /system/xbin/su
busybox cp /udisk/su /system/bin/su
chmod 6755 /system/xbin/su
chmod 6755 /system/bin/su
reboot
Click to expand...
Click to collapse
Hi. What should happen when I put in the USB stick? Did exactly what you wrote but still not rooted.also get no file or directory.
Hi all, i added some files into the system directory of my kindle fire hdx 7'.. when i restarted it is stuck in a boot loop on the animated Kindle Fire boot screen, i can ADB onto it, and i attempted to remove the files, but "ADB su" isn't working for me, and I'm unable to access the system directory over ADB... and i don't have custom recovery.
Any ideas on this one? is there a way of restoring the Kindle?
Thanks
osmorgan said:
Hi all, i added some files into the system directory of my kindle fire hdx 7'.. when i restarted it is stuck in a boot loop on the animated Kindle Fire boot screen, i can ADB onto it, and i attempted to remove the files, but "ADB su" isn't working for me, and I'm unable to access the system directory over ADB... and i don't have custom recovery.
Any ideas on this one? is there a way of restoring the Kindle?
Thanks
Click to expand...
Click to collapse
what you get on
Code:
adb shell
su
?
thanks for the reply. when i
adb shell
su
Click to expand...
Click to collapse
it returns to 1:[email protected] where it should show [email protected] any ideas?
osmorgan said:
thanks for the reply. when i
it returns to 1:[email protected] where it should show [email protected] any ideas?
Click to expand...
Click to collapse
after that use
Code:
mount -o rw,remount /system
if you wil get permission denied you need to do hard reset from recovery and try again
after that you could change files in /system
great, i will try this later.. any guides on doing a hard reset?? keeping in mind that i don't have custom recovery..
thanks again.
osmorgan said:
great, i will try this later.. any guides on doing a hard reset?? keeping in mind that i don't have custom recovery..
thanks again.
Click to expand...
Click to collapse
you could get into stock recovery by holding power+volume up
all of this suggesting that you are at 4.5.2 and rooted
for 3.2.X hard reset will delete su - file
You're a star. Thanks. I'll get onto this after work.
ONYXis said:
you could get into stock recovery by holding power+volume up
all of this suggesting that you are at 4.5.2 and rooted
for 3.2.X hard reset will delete su - file
Click to expand...
Click to collapse
No luck :/ was unable to mount, and hard reset via recovery still results in boot loop :/ any other ideas?
Could you post output?
and pls what is your firmware and root method?
Seems no way to recover(sorry
How do I provide the output? I was 4.5.2 and rooted with CVE
copy-paste output from cmd
like:
Code:
adb shell
su
....
ahh i see what you mean.. ive run s uagian after factory reset and its now giving me the root prompt! great! im just about to follow this guys steps
http://forum.xda-developers.com/showthread.php?t=2793253
thanks for your help.. i may be back.
any idea if this method works with stock recovery?
ONYXis said:
copy-paste output from cmd
like:
Code:
adb shell
su
....
Click to expand...
Click to collapse
nope.. that didnt work for me.. do you know how i can push a deb to reflash?
Pls post output to see that exactly doesn't work.
to use that manual you need to use 4.5.3 bin btw
I see, I was having permissions errors when pushing the file to the sdcard, I had mounted the data partition. I am unable to write anything as shell user, but fine as root. Any ideas?
Thanks
adb shell
[email protected]:/ $ su
[email protected]:/ # mount -o rw,remount /cache
[email protected]:/ # mkdir /cache/recovery
mkdir failed for /cache/recovery, File exists
[email protected]:/ # echo install /cache/kindleupdate.bin > /cache/recovery/openrecoveryscript
[email protected]:/ # chmod 0777 /cache/recovery/openrecoveryscript
[email protected]:/ # exit
[email protected]:/ $ exit
Mac-miniownloads $ adb push update-kindle-13.4.5.3_user_453011120.bin /cache/kindleupdate.bin
failed to copy 'update-kindle-13.4.5.3_user_453011120.bin' to '/cache/kindleupdate.bin': Permission denied
What do you think?
ONYXis said:
what you get on
Code:
adb shell
su
?
Click to expand...
Click to collapse
ONYXis said:
Pls post output to see that exactly doesn't work.
to use that manual you need to use 4.5.3 bin btw
Click to expand...
Click to collapse
osmorgan said:
Mac-miniownloads $ adb push update-kindle-13.4.5.3_user_453011120.bin /cache/kindleupdate.bin
failed to copy 'update-kindle-13.4.5.3_user_453011120.bin' to '/cache/kindleupdate.bin': Permission denied
What do you think?
Click to expand...
Click to collapse
You cant do this at that way
you need :
Code:
adb push update-kindle-13.4.5.3_user_453011120.bin /sdcard/update.zip
adb shell
su
mount -o remount,rw /cache
cd /sdcard
cp update.zip /cache
chmod 777 /cache
chmod 777 /cache/recovery
cd /cache/recovery
echo "--update_package=/cache/update.zip" > command
exit
exit
adb reboot recovery
thank you but i still get permissions issues -
failed to copy 'update-kindle-13.4.5.3_user_453011120.bin' to '/sdcard/update.zip': Permission denied
ONYXis said:
You cant do this at that way
you need :
Code:
adb push update-kindle-13.4.5.3_user_453011120.bin /sdcard/update.zip
adb shell
su
mount -o remount,rw /cache
cd /sdcard
cp update.zip /cache
chmod 777 /cache
chmod 777 /cache/recovery
cd /cache/recovery
echo "--update_package=/cache/update.zip" > command
exit
exit
adb reboot recovery
Click to expand...
Click to collapse
osmorgan said:
thank you but i still get permissions issues -
failed to copy 'update-kindle-13.4.5.3_user_453011120.bin' to '/sdcard/update.zip': Permission denied
Click to expand...
Click to collapse
Hmm....Strange. Are you see Fire as mtp device on you Pc (for Mac you need https://www.android.com/filetransfer/)?
If "yes" - try to copy update.zip manual into Fire's internal storage.
Hi, does anyone know how to delete a file on root with terminal, as rm -r returns screenshotted error.
kriki200 said:
Hi, does anyone know how to delete a file on root with terminal, as rm -r returns screenshotted error.
Click to expand...
Click to collapse
Did you execute this command as root ? If not enter "su" then enter your command. (Make sure you hit "Allow" when the prompt for you to allow root accès to the shell appears)
And maybe it sounds stupid but try chmod commands if your command doesn't work.
I'm not an expert with android terminal so if the problem is persistent you can try this with a root explorer.
Hope all of this helped
Have a good day
kriki200 said:
Hi, does anyone know how to delete a file on root with terminal, as rm -r returns screenshotted error.
Click to expand...
Click to collapse
The partitition you want to deal with must be mounted as READ-WRITE before.
Raiz said:
Did you execute this command as root ? If not enter "su" then enter your command. (Make sure you hit "Allow" when the prompt for you to allow root accès to the shell appears)
And maybe it sounds stupid but try chmod commands if your command doesn't work.
I'm not an expert with android terminal so if the problem is persistent you can try this with a root explorer.
Hope all of this helped
Have a good day
Click to expand...
Click to collapse
I did, kinda don't want to change permissions... same.
jwoegerbauer said:
The partitition you want to deal with must be mounted as READ-WRITE before.
Click to expand...
Click to collapse
How do I do and undo that, will it change any file permissions?
Example:
Code:
su
cd /
mount -o rw,remount -t auto /system
jwoegerbauer said:
Example:
Click to expand...
Click to collapse
Thank you, it worked, do you know how to undo it, the below command deosn't seem to work and do you know what the "auto" is for in the command?
Code:
mount -o ro,remount -t auto /system