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.
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"
This thread is designed for representation of the current progress on the Nook Tablet rooting and exploits, the second post will contain how to guides so you can learn to work on it for you self. REMEMBER I DO THIS FOR FUN, please respect the thread as well as others opinions
OLD UPDATES AT THE END OF THIS POST.
First off if you haven’t read the wiki yet to know what is currently in the device you should look here.
Also you should look at the http://www.nooktabletdev.orgfor information on the Nook Tablet Development process. - Thanks to dj_segfault
Rooting ScriptsWindows: Root, OTA block, De-bloat, Gapps Thanks to Indirect
Mac/Linux: Rooting script Thanks to t-r-i-c-k
Mac/Linux: Root,OTA Block, Gapps
CURRENT PROGRESS
adb connection: COMPLETE
adb root: COMPLETE
busybox:COMPLETE
permanent root: COMPLETE BY INDIRECT
GApps and Market: COMPLETE BY INDIRECT & Anlog
recovery mode: COMPLETE BY nemith
{
"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"
}
THANKS TO NEMITH
bootloader: Locked and Signed Irrelevant
uboot: CRACKED BY BAUWKS
THANKS TO BAUWKS
Loglud said:
bauwks method uses the flashing_boot.img to his advantage, and since it is not checked by security, effectively he has made an insecure uboot. While this is not an unlocked bootloader, it is a way to get around the security, and enable custom recovery and higher level processes to be run.
I have been looking at this line of code for a long time, and as im sure hkvc and bauwks saw it is a large (but 100% necessary) flaw:
distro/u-boot/board/omap4430sdp/mmc.c: 559 : setenv ("bootcmd", "setenv setbootargs setenv bootargs ${sdbootargs}; run setbootargs; mmcinit 0; fatload mmc 0:1 0x81000000 flashing_boot.img; booti 0x81000000");
Without this line of code, it would be impossible for any one but the factory whom could JTAG flash (but since it is secured, most likely they also have to make a flashing_boot.img).
Click to expand...
Click to collapse
12/9/11:
UBUNTU is here, thanks to ADAMOUTLER
http://www.youtube.com/watch?v=PwUg17pVWBs&hd=1
Keep in mind this is only an overlay verson but it is prof that one day we might be able to push roms and kernels over existing ones, then hijack then (next work) and then use them.
Please PM me or post if you know anything else, and or want to add anything.
Usefull threads
Usefull threads:
ROOTING:
Full root for Nook Tablet. [11/20/11] [Yes this is a permanent root!] Thanks to indirect
Noot Tablet - Easy root & Market on MAC (1 download, 1 script to run) Thanks to t-r-i-c-k
[Windows/Linux] Unroot and uninstall gApps for the nook tablet [Scripts] Thanks to indirect
MODS to Default Rom:
[Full Mod + Root + OTA block] Snowball-mod: Full Modification Root [1/6/2012] Thanks to cfoesch
[DEV][WIP] Enable init.d scripts and build.prop mods for Nook Tablet! Thanks to [DEV][WIP] Enable init.d scripts and build.prop mods for Nook Tablet! 1 Attachment(s) (Multi-page thread 1 2 3 ... Last Page)
Originally Posted By: diamond_lover
Kernels:Coming Soon
ROMS:Coming Soon
APPS:
[Tutorial][WIP] Installing alternative Keyboards on the NT. Thanks to robertely
[DEV] - HomeCatcher Redirect n Button to any Launcher Thanks to gojimi
Hidden Settings App Updated 12/30/11 Thanks to brianf21
Replacement SystemUI.apk v2: Permanent back and menu buttons, n as Home button Thanks to revcompgeek
DEVELOPMENT:
[Dev]Files of interest in the system Thanks to indirect
[REF] Nook Tablet Source Code Thanks to diamond_lover
BHT Installer (Basic Hacking Tools) Thanks to AdamOutler
[Stock Firmware]Restore Barnes & Nobel Nook 1.4.0 from SDCard Thanks to AdamOutler
Guides
Table of Contents
Enableing adb Connection (eab1)
Rooting using zergRush (rug2)
Installing busyboxy (ibb3)
Permanent root (pr4) THANKS TO INDIRECT
Installing GApps (aga5) THANKS TO ANLOG
Full system restore/wipe (fsr6) THANKS TO INDIRECT
Enableing adb Connection (eab1)
Install the andriod SDK that is required for your Operating system.
NOTE: This will requries the SDK, and JDK both of which can be downloaded by clicking the links, downloading and installing it.
Run the andriod SDK Manager and Install "Andriod SDK Platform-tools"
[*]Modify your adb_usb.ini file to read such as the following:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x2080
This will be in your /home/{username}/.andriod/ folder for mac and linux
This will be in your C:/Users/{username}/.andriod folder for Windows.
ADB is now enabled for your device, however it is not ON your device. YOU MUST DO THIS EVERY TIME YOU WISH TO ADB INTO YOUR DEVICE.
[*]To do this you will need to download any app, and attempt to install it.
You can use this app if you need.
[*]Click on the Package Installer, and then a prompt will pop up asking if you want change the settings to allow 3rd party apps.
*DO NOT ENABLE IF YOU WISH TO ACCESS ADB*
I am working on a way to have it enabled by default.
[*]In the settings page you should see *2* USB Debuggin modes.
[*]Press them both and accept the prompt.
[*]PLUG IN YOUR DEVICE.
Note* You should see the Android Development icon on the bottom of the screen.
ADB will now be able to see your device. How ever you will need to restart the server before it sees it.
Rooting using zergRush (rug2)
This is for the poeople whom have access to adb. You will also need this file. Unzip the file.
Type in the following command (while in the folder with the zergRush Binary):
Code:
adb push ./zergRush /data/local
[*]Once thats installed run this:
Code:
adb shell chmod 777 /data/local/tmp
[*]And lastly:
Code:
adb shell /data/local/zergRush
[*]You are now rooted (only for this reboot)
Installing busyboxy (ibb3)
You will need root and the following busybox file.
Type in the following command while in the location where busy box was downloaded to:
Code:
adb push ./busybox /data/local
[*]Busybox works by calling binaries from a file outside of /system/bin/. We must make this file by issuing the following command:
Code:
adb shell mkdir /data/busybox
[*]Lets make sure we can install busybox without permission probles:
Code:
adb shell chmod 777 /data/local/busybox
[*]Next install busybox in the folder:
Code:
adb shell /data/local/busybox --install
[*]We now need to take the /system/folder, and mount it as a writeable folder:
Code:
adb shell mount -rw -o remount /dev/block/platform/mmci-omap-hs.1/by-name/system /system
[*]Link it into bin:
Code:
adb shell ln -s /data/local/busybox /system/bin/busybox
You now have busybox installed
Permanent root (pr4)
THANKS TO INDIRECT for Files and Scripts
We will need SU and Superuser.apk
First we need to install the Superuser.apk:
Code:
adb wait-for-device install Superuser.apk
adb remount
[*]Next lets go ahead and push the su application up to the /data/local/ folder
Code:
adb push su /data/local/
[*]Next we will need to change the permissions and cp su from the /data/local/ folder to the /system/bin/
Code:
adb shell chmod 4755 /data/local/su;mount -o remount,rw /dev/block/platform/mmci-omap-hs.1/by-name/system /system;busybox cp /data/local/su /system/bin
Installing GApps (eab1)
THANKS TO ANALOG and INDIRECT for Scripts
First things first we need to download the GAPPS. The most reacent one is this one or get the most recent one here.
[*] Unzip and navigate to the most root folder of that package in your shell.
[*]We need to verify that adb is booting into root. To do this we can issue the command:
Code:
adb shell id
If id doesn't return root then you will need to re-zergRush your device
[*]Now it is time for us to export the apps to the directories.
Code:
adb shell mount -o remount,rw /dev/block/platform/mmci-omap-hs.1/by-name/system /system
adb push system/app/CarHomeGoogle.apk /system/app/
adb shell chmod 644 /system/app/CarHomeGoogle.apk
adb push system/app/FOTAKill.apk /system/app/
adb shell chmod 644 /system/app/FOTAKill.apk
adb push system/app/GenieWidget.apk /system/app/
adb shell chmod 644 /system/app/GenieWidget.apk
adb push system/app/GoogleBackupTransport.apk /system/app/
adb shell chmod 644 /system/app/GoogleBackupTransport.apk
adb push system/app/GoogleCalendarSyncAdapter.apk /system/app/
adb shell chmod 644 /system/app/GoogleCalendarSyncAdapter.apk
adb push system/app/GoogleContactsSyncAdapter.apk /system/app/
adb shell chmod 644 /system/app/GoogleContactsSyncAdapter.apk
adb push system/app/GoogleFeedback.apk /system/app/
adb shell chmod 644 /system/app/GoogleFeedback.apk
adb push system/app/GooglePartnerSetup.apk /system/app/
adb shell chmod 644 /system/app/GooglePartnerSetup.apk
adb push system/app/GoogleQuickSearchBox.apk /system/app/
adb shell chmod 644 /system/app/GoogleQuickSearchBox.apk
adb push system/app/GoogleServicesFramework.apk /system/app/
adb shell chmod 644 /system/app/GoogleServicesFramework.apk
adb push system/app/LatinImeTutorial.apk /system/app/
adb shell chmod 644 /system/app/LatinImeTutorial.apk
adb push system/app/MarketUpdater.apk /system/app/
adb shell chmod 644 /system/app/MarketUpdater.apk
adb push system/app/MediaUploader.apk /system/app/
adb shell chmod 644 /system/app/MediaUploader.apk
adb push system/app/NetworkLocation.apk /system/app/
adb shell chmod 644 /system/app/NetworkLocation.apk
adb push system/app/OneTimeInitializer.apk /system/app/
adb shell chmod 644 /system/app/OneTimeInitializer.apk
adb push system/app/Talk.apk /system/app/
adb shell chmod 644 /system/app/Talk.apk
adb push system/app/Vending.apk /system/app/
adb shell chmod 644 /system/app/CarHomeGoogle.apk
adb push system/etc/permissions/com.google.android.maps.xml /system/etc/permissions/
adb push system/etc/permissions/features.xml /system/etc/permissions/
adb push system/framework/com.google.android.maps.jar /system/framework/
adb push system/lib/libvoicesearch.so /system/lib/
Now you have GApps installed from Anlog's. All Credits go to him and Indirect
Full system restore/wipe (fsr6)
THANKS TO INDIRECT
WARNING THIS WILL WIPE YOUR ENTIRE FILESYSTEM!!!
Go into adb shell or terminal emulator.
Issue command:
Code:
echo -n '0000' > /bootloader/BootCnt
Next reboot your device by conventional methods or issue:
Code:
reboot
Your nook will now restart and tell you it is resetting.
You now have a clean slate!
Got some links for howto's on the adb connection/root.
Yeah - if someone has details on how to adb connect and root, it'd be helpful to include links. I've yet to see specifics for either.
Reserved
Sent from Tapatalk, NOOK Color CM7 Nightly's!
I aplogize im still typing them up
Damn loglud, I ended up beating you to the root lol. Sorry about that! D:
The Droid 2 and Droid X had locked bootloaders with the 'e-fuse' and Koush got around them and installed CWM with this...
http://www.koushikdutta.com/2010/08/droid-x-recovery.html
What do you guys think? I don't have a NT yet to try anything (probably won't get one until sometime around x-mas).
l
Indirect said:
Damn loglud, I ended up beating you to the root lol. Sorry about that! D:
Click to expand...
Click to collapse
Its no problem at all. Hints why i posted these guides. I was hoping someone wouod figure it out. I found it last night too. It sucked cause im now back at my childhood home trying to get my macbook pro to boot fedora and windows. Im gonna repackage the root with Superoneclick. Thanks so much for your effort. Would you mind if i added that to the guides?
Loglud said:
l
Its no problem at all. Hints why i posted these guides. I was hoping someone wouod figure it out. I found it last night too. It sucked cause im now back at my childhood home trying to get my macbook pro to boot fedora and windows. Im gonna repackage the root with Superoneclick. Thanks so much for your effort. Would you mind if i added that to the guides?
Click to expand...
Click to collapse
Superoneclick...love!
Sent from my Nook Tablet using Tapatalk
Loglud said:
l
Its no problem at all. Hints why i posted these guides. I was hoping someone wouod figure it out. I found it last night too. It sucked cause im now back at my childhood home trying to get my macbook pro to boot fedora and windows. Im gonna repackage the root with Superoneclick. Thanks so much for your effort. Would you mind if i added that to the guides?
Click to expand...
Click to collapse
Not at all so long as you give proper credits.
Loglud said:
This thread is designed for representation of the current progress on the Nook Tablet rooting and exploits, the second post will contain how to guides so you can learn to work on it for you self.
First off if you haven’t read the wiki yet to know what is currently in the device you should look here.
CURRENT PROGRESS
adb connection: COMPLETE
adb root: COMPLETE
busybox: COMPLETE
permanent root: IN PROGRESS
bootloader: Locked and Signed
By the bootloader being locked and signed it is very difficult to design anything that will boot besides nook roms. In order to solve this some of the Devs have suggested the following:
kexec: RESEARCHING
2nd init: RESEARCHING
CWM: NOT STARTED
Please PM me or post if you know anything else, and or want to add anything.
Click to expand...
Click to collapse
hopefully it is cracked soon cause i dont want to buy this if i can't have a full custom rom, all of the verizon motorola phones run roms off of 2nd init and it just isnt the same to be honest. you can never run a full custom rom with second init(well you can but you have to build the rom to fit the kernel) and honestly i want my device to be mine
you should tweet cvpcs or someone who makes and maintains 2nd init roms to get more info on it though
Can't get busybox installed
I'm stuck... I get errors for #3 for busybox... errors like...
Code:
$ adb shell /data/local/busybox --install
busybox: /data/busybox/[: No such file or directory
busybox: /data/busybox/[[: No such file or directory
busybox: /data/busybox/addgroup: No such file or directory
.....
busybox: /data/busybox/yes: No such file or directory
busybox: /data/busybox/zcat: No such file or directory
busybox: /data/busybox/zcip: No such file or directory
So I logged into root via adb shell, set busybox permissions to execute and tried that but same messages?!
Also, adb won't let me 'remount' - (I thought i'd try to copy it direct to /system/bin)?
(I'm running from OSX, if that matters)
EDIT: and of course I'm getting...
Code:
$ adb shell ln -s /data/local/busybox /system/bin/busybox
link failed Read-only file system
$ adb remount
remount failed: Operation not permitted
kgingeri said:
I'm stuck... I get errors for #3 for busybox... errors like...
Code:
$ adb shell /data/local/busybox --install
busybox: /data/busybox/[: No such file or directory
busybox: /data/busybox/[[: No such file or directory
busybox: /data/busybox/addgroup: No such file or directory
.....
busybox: /data/busybox/yes: No such file or directory
busybox: /data/busybox/zcat: No such file or directory
busybox: /data/busybox/zcip: No such file or directory
So I logged into root via adb shell, set busybox permissions to execute and tried that but same messages?!
Also, adb won't let me 'remount' - (I thought i'd try to copy it direct to /system/bin)?
(I'm running from OSX, if that matters)
EDIT: and of course I'm getting...
Code:
$ adb shell ln -s /data/local/busybox /system/bin/busybox
link failed Read-only file system
$ adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
Sorry it took me so long to get back to you. I have updatd my guide to help you out. First of you will need to make the busybox directory, then change the permissions of the binary file, then run the install. You will then have to mount -rw
Still some glitches installing busybox...
Loglud said:
Sorry it took me so long to get back to you. I have updatd my guide to help you out. First of you will need to make the busybox directory, then change the permissions of the binary file, then run the install. You will then have to mount -rw
Click to expand...
Click to collapse
Thanks Loglud, but I still had trouble using adb. It's like I don't have root from adb? I get permission errors on mkdir and remounting etc?
Weird that the 'adb shell mkdir /data/busybox' gave me permission errors?! It did work fine with the interactive adb shell - weird!?
After the initial 'push' command, I could install via:
Code:
mac-osx$ adb shell
$ su root
# cd /data/local
# chmod 755 busybox
# ls -l
-rwxr-xr-x shell shell 1745016 2011-11-21 00:21 busybox
# mount -rw -o remount /dev/block/platform/mmci-omap-hs.1/by-name/system /system
# mkdir ../busybox
# ./busybox --install
Also, is the line:
Code:
# ln -s /data/local/busybox /system/bin/busybox
not supposed to be
Code:
# ln -s /data/busybox /system/bin/busybox
Things went weird on me in the final step, but I did manage to get all the hard linked busybox files to show up in /system/bin eventually, so I'm a happy camper.
EDIT: PS my mount on data is as follows..
Code:
# mount|grep /data
/dev/block/platform/mmci-omap-hs.1/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,data=ordered 0 0
EDIT2:
Hmmm... seems like maybe my /data folder has weird permissions - if so not sure why?...
Code:
# cd /
# ls -l | grep '\<data\>'
drwxrwx--x system system 2011-11-21 18:25 data
# chmod 777 data
kgingeri said:
Thanks Loglud, but I still had trouble using adb. It's like I don't have root from adb? I get permission errors on mkdir and remounting etc?
Weird that the 'adb shell mkdir /data/busybox' gave me permission errors?! It did work fine with the interactive adb shell - weird!?
After the initial 'push' command, I could install via:
Code:
mac-osx$ adb shell
$ su root
# cd /data/local
# chmod 755 busybox
# ls -l
-rwxr-xr-x shell shell 1745016 2011-11-21 00:21 busybox
# mount -rw -o remount /dev/block/platform/mmci-omap-hs.1/by-name/system /system
# mkdir ../busybox
# ./busybox --install
Also, is the line:
Code:
# ln -s /data/local/busybox /system/bin/busybox
not supposed to be
Code:
# ln -s /data/busybox /system/bin/busybox
Things went weird on me in the final step, but I did manage to get all the hard linked busybox files to show up in /system/bin eventually, so I'm a happy camper.
EDIT: PS my mount on data is as follows..
Code:
# mount|grep /data
/dev/block/platform/mmci-omap-hs.1/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,data=ordered 0 0
EDIT2:
Hmmm... seems like maybe my /data folder has weird permissions - if so not sure why?...
Code:
# cd /
# ls -l | grep '\<data\>'
drwxrwx--x system system 2011-11-21 18:25 data
# chmod 777 data
Click to expand...
Click to collapse
ok so whats happening? i modified the guides and i was hopping that would help you. The command is
Code:
# ln -s /data/local/busybox /system/bin/busybox
and as for your permissions it seems as though your root since your in the # shell but, you have to change the permissions on your /system folder not the /data folder the permsisions on the data file should be fine since i think shell is a member of system, so you can put all your data in there.
Loglud said:
ok so whats happening? i modified the guides and i was hopping that would help you. The command is
Code:
# ln -s /data/local/busybox /system/bin/busybox
and as for your permissions it seems as though your root since your in the # shell but, you have to change the permissions on your /system folder not the /data folder the permsisions on the data file should be fine since i think shell is a member of system, so you can put all your data in there.
Click to expand...
Click to collapse
Yeah, I'm root in the 'adb shell' because I 'su root' but adb commands fail from the Mac shell. I'll reboot my NT and give you the script. My /data permissions get reset when I reboot...
Here you are as it happens
MBAir$ ls busybox
busybox
MBAir$ adb push ./busybox /data/local
2881 KB/s (1745016 bytes in 0.591s)
MBAir$ adb shell mkdir /data/busybox
mkdir failed for /data/busybox, Permission denied
Of course there is no point continuing until I do the following...
MBAir$ adb shell
$ su root
# chmod 777 /data
# exit
$ exit
MBAir$ adb shell mkdir /data/busybox
MBAir$ adb shell chmod 777 /data/local/busybox
MBAir$ adb shell /data/local/busybox --install
MBAir$ adb shell mount -rw -o remount /dev/block/platform/mmci-omap-hs.1/by-name/system /system
mount: Operation not permitted
To get around the last error, I had to do another 'adb shell', 'su root' and do 'ln' commands manually.
(I actually ran a shell 'for loop' on the tablet, using all files found in /data/busybox as a list and issued ln commands for each against a copy of busybox in /system/bin)
kgingeri said:
Yeah, I'm root in the 'adb shell' because I 'su root' but adb commands fail from the Mac shell. I'll reboot my NT and give you the script. My /data permissions get reset when I reboot...
Here you are as it happens
MBAir$ ls busybox
busybox
MBAir$ adb push ./busybox /data/local
2881 KB/s (1745016 bytes in 0.591s)
MBAir$ adb shell mkdir /data/busybox
mkdir failed for /data/busybox, Permission denied
Of course there is no point continuing until I do the following...
MBAir$ adb shell
$ su root
# chmod 777 /data
# exit
$ exit
MBAir$ adb shell mkdir /data/busybox
MBAir$ adb shell chmod 777 /data/local/busybox
MBAir$ adb shell /data/local/busybox --install
MBAir$ adb shell mount -rw -o remount /dev/block/platform/mmci-omap-hs.1/by-name/system /system
mount: Operation not permitted
To get around the last error, I had to do another 'adb shell', 'su root' and do 'ln' commands manually.
(I actually ran a shell 'for loop' on the tablet, using all files found in /data/busybox as a list and issued ln commands for each against a copy of busybox in /system/bin)
Click to expand...
Click to collapse
re run zergRush exploit. your adb shell is defaulting to the shell username. by rerunning the zergy you will allow for yourself to use the adb shell as root. make sure you dont run it as the root user though. you are also more then welcome to hop in irc and ask questions.
Any one having difficulty rooting or see anything that needs to be updated?
I know there has been a lot of tutorials how to root the Xperia X10 mini. But almost a lot of them don't work (for me). But there is one way to root it.
It is very simple, you need to follow the instructions, then it will be easy.
1.) We need to download Android SDK, link: http://developer.android.com/sdk/index.html
2.) We need to download SuperOneClick.rar, link: http://shortfuse.org/
3.) Unzip the SuperOneClick .zip and pull out the su-v3, busybox, Superuser.apk, psneuter, and GingerBreak files, and rename the su-v3 into su, and place all the files in adt-bundle-windows-x86-20130219/sdk/platform-tools. I recommend changing the "adt-bundle-windows-x86-20130219" to something simple like "Android SDK".
4.) Now, you have to use CMD, open it, and type the location of your files, type like this, cd C:/Users/Me/Desktop/Android SDK/sdk/platform-tools.
5.) Now plug in your phone, and make sure your debugging and unknown sources are on.
6.) Now write all the following commands, one at a time!
adb devices
adb push psneuter /data/local/tmp
adb shell
$ cd /data/local/tmp
$ chmod 777 psneuter
$ ./psneuter
adb kill-server
adb devices
adb shell
# mount -o remount,rw -t rfs /dev/block/st19 /system
# exit
adb push busybox /system/bin
adb push su /system/bin
adb install Superuser.apk
adb shell
# chmod 4755 /system/bin/busybox
# chmod 4755 /system/bin/su
# mount -o remount,ro -t rfs /dev/block/st19 /system
# exit
adb reboot
And now u are all done! Your phone will reboot, then download Root Checker, and check if you are rooted.
If you write "adb shell" and you don't get "#" in the ending (not the beginning) but "$" then you have done something wrong, check everything that I wrote. If u have some problems, don't be shy to tell me.
Thanks a bunch, this tutorial was the only one that worked for me. What's more, I saw the procedure step-by-step so I saw exactly what was going on.
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