[THEME] Samsung Galaxy S II [10-02-2012] [62][58][42]

[THEME] Samsung Galaxy S II [10-02-2012] [62][58][42] - Xperia Arc Themes and Apps

Samsung Galaxy S II theme
{
"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
AdamTt, for the reboot mod
Ospi, for the reboot and screenshot icon
pvyParts, for help with the notification toggles
Download the full version here

Hi!
It looks very good , i love the icons on config menu.
But what changes with Conversations, Calendar, SemcPhone, SemcMusic packages?

rafuru said:
Hi!
It looks very good , i love the icons on config menu.
But what changes with Conversations, Calendar, SemcPhone, SemcMusic packages?
Click to expand...
Click to collapse
Glad you like it!
Just some statusbar icons are changed in those apk's
Sent from my iPad using Tapatalk

whoa, nice themes. :-D

Do anyone test it on Neo?

FrozenSE said:
Do anyone test it on Neo?
Click to expand...
Click to collapse
Nope, mind testing it for me? Should work if you're using .145 fw

phone must be rooted to install it ??

philansel7 said:
phone must be rooted to install it ??
Click to expand...
Click to collapse
yes of course.

2 vraagjes: hoe heet de klok widget die je daar hebt, en hoe root ik mn experia arc, ik dacht dat dat nog niet kon??

thomassafca said:
Nope, mind testing it for me? Should work if you're using .145 fw
Click to expand...
Click to collapse
Do you mean that files on Neo and Ark .145 FW is the same (except display drivers)? I will test it on my Neo today and post result.

I try to put files using Root Explorer. Roboot and phone not loading (shows onle splash "Sony Ericsson" on black background.

ragdoll20 said:
2 vraagjes: hoe heet de klok widget die je daar hebt, en hoe root ik mn experia arc, ik dacht dat dat nog niet kon??
Click to expand...
Click to collapse
Clock: http://gu5taf.deviantart.com/art/MIUI-Clock-Calendar-Widgets-214627542
Can you unlock your bootloader? If yes, check this.
If not, check this
@FrozenSE, did you changed the permissions?

Where' the download button on that side?
Can't find it when viewing with my phone.
Sent from my LT15i using XDA Premium App

Start copiyng -> reboot (phone restarts, I dont enter commands) -> not loads.

This is a how-to use adb: http://www.youtube.com/watch?v=Z3SpI7m7mFI
commands:
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
00000000000000000000 device
C:\android-sdk-windows\platform-tools>adb push Calendar.apk /sdcard/
229 KB/s (359426 bytes in 1.529s)
C:\android-sdk-windows\platform-tools>adb push Conversations.apk /sdcard/
2806 KB/s (868038 bytes in 0.302s)
C:\android-sdk-windows\platform-tools>adb push framework-res.apk /sdcard/
1732 KB/s (4881322 bytes in 2.751s)
C:\android-sdk-windows\platform-tools>adb push SemcDeskClock.apk /sdcard/
258 KB/s (387747 bytes in 1.464s)
C:\android-sdk-windows\platform-tools>adb push SemcGenericUxpRes.apk /sdcard/
1096 KB/s (1013607 bytes in 0.903s)
C:\android-sdk-windows\platform-tools>adb push SemcMusic.apk /sdcard/
260 KB/s (667725 bytes in 2.501s)
C:\android-sdk-windows\platform-tools>adb push SemcPhone.apk /sdcard/
1200 KB/s (1589678 bytes in 1.293s)
C:\android-sdk-windows\platform-tools>adb push Settings.apk /sdcard/
1314 KB/s (2661869 bytes in 1.978s)
C:\android-sdk-windows\platform-tools>adb push SystemUI.apk /sdcard/
3903 KB/s (159911 bytes in 0.040s)
C:\android-sdk-windows\platform-tools>adb shell
$ su
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
# busybox cp -R /sdcard/Calendar.apk /system/app/
busybox cp -R /sdcard/Calendar.apk /system/app/
# busybox cp -R /sdcard/Conversations.apk /system/app/
busybox cp -R /sdcard/Conversations.apk /system/app/
# busybox cp -R /sdcard/framework-res.apk /system/framework/
busybox cp -R /sdcard/framework-res.apk /system/framework/
# busybox cp -R /sdcard/SemcDeskClock.apk /system/app/
busybox cp -R /sdcard/SemcDeskClock.apk /system/app/
# busybox cp -R /sdcard/SemcGenericUxpRes.apk /system/framework/
busybox cp -R /sdcard/SemcGenericUxpRes.apk /system/framework/
# busybox cp -R /sdcard/SemcMusic.apk /system/app/
busybox cp -R /sdcard/SemcMusic.apk /system/app/
# busybox cp -R /sdcard/SemcPhone.apk /system/app/
busybox cp -R /sdcard/SemcPhone.apk /system/app/
# busybox cp -R /sdcard/Settings.apk /system/app/
busybox cp -R /sdcard/Settings.apk /system/app/
# busybox cp -R /sdcard/SystemUI.apk /system/app/
busybox cp -R /sdcard/SystemUI.apk /system/app/
# sync
sync
# reboot
reboot
C:\android-sdk-windows\platform-tools>
Click to expand...
Click to collapse
enjoy!

same was happening here, but i solved installing busybox.
Also i make a script (for linux) to automate the process and make the changes so fast before the device reboots.

Tunatje said:
This is a how-to use adb: http://www.youtube.com/watch?v=Z3SpI7m7mFI
commands:
enjoy!
Click to expand...
Click to collapse
Okay,this is so confusing.
Is there an easier,noob friendly way to install this theme?

Come on guys, put some bloody effort in. You can install it the same way as any other arc theme.
Use root explorer, change permissions, move, reboot. You can get more detailed instructions from any of the other theme posts.
One word of advice, copy framework file last and reboot straight away.
Also, I get a very long reboot after applying a theme, be patient lol

It won't let me move it,it says it's a read-only file.

Okay,I was able to move it.Rebooted and nothing changed :S

Related

X8 Custom ROM

Because propoff2 got himself banned, I've decided to re-create his threads for you, hopefully with easier to follow instructions than before.
X8 Android 2.1-rus
X8 Android 1.6
Modified Image (x8.img)
Data.img
Busybox, Rootshell, Chargemon
(If for whatever reason any of the above links don't work, scroll down and see propc's post.)
Before moving on, decide whether you want to boot the rom from the sdcard or from the internal memory, then use the correct instructions to do so.
If you've tried this method and REALLY don't like the customized rom, then see this thread for how to install a clean, pre-rooted rom!
==BOOTING CUSTOM ROM FROM SD==
Before you begin, put chargemon, busybox, rootshell, x8.img and data.img onto the sdcard.
1. Flash 1.6 firmware to the phone.
2. Root the phone.
3. Copy the files rootshell, chargemon and busybox to /system/bin
(You can do this by putting the files on the sdcard, and using a file manager such as root explorer to copy the files into /system/bin. Command line instructions will be here soonish. This guide is still a WIP).
4. Chmod the files.
Code:
chmod 4755 /system/bin/rootshell
chmod 755 /system/bin/busybox
chmod 777 /system/bin/chargemon
5. Copy both x8.img (/system) and data.img (/data) to the sdcard.
6. Flash 2.1 kernel using this flashing utility. (The GUI version is perfectly fine to use.)
Remember to remove system.sin and userdata.sin from the flash files!
7. Reboot and hope it works.
==BOOT CUSTOM ROM FROM INTERNAL MEMORY==
Before you being, copy x8.img and busybox on to the sdcard.
1. Follow steps 1-2 from the instructions above.
2. Copy busybox to /data/local/tmp
Code:
cd /data/local/tmp
cat /sdcard/busybox > /data/local/tmp/busybox
3. Chmod busybox.
Code:
chmod 755 busybox
4. Using busybox, remount /system as rewriteable.
Code:
./busybox mount -o remount,rw /system
./busybox sh
5. Mount x8.img.
Code:
./busybox mkdir /data/local/tmp/1
./busybox losetup /dev/block/loop1 /sdcard/x8.img
./busybox mount -t ext2 -o rw,noatime,nodiratime /dev/block/loop1 /data/local/tmp/1
6. Remove the contents of /system. ADVICE: Remove the folders one by one, leave /system/bin and /system/app last! That way your phone is less likely to crash whilst doing this step. DO NOT TRY AND USE YOUR PHONE WHILE DOING THIS, YOUR PHONE IS CERTAIN TO CRASH! Make sure the phone is locked.
Code:
./busybox rm -rf /system/media
./busybox rm -rf /system/usr
./busybox rm -rf /system/etc
./busybox rm -rf /system/lib
./busybox rm -rf /system/xbin
./busybox rm -rf /system/framework
./busybox rm -rf /system/fonts
./busybox rm -rf /system/drm
./busybox rm -rf /system/build.prop
./busybox rm -rf /system/app
./busybox rm -rf /system/bin
7. Now copy the files into the phone's internal memory. Again, we have to copy these over one by one, as the phone WILL run out of memory during this process! Most important files go first.
Code:
./busybox cp -prfR /data/local/tmp/1/bin /system/
./busybox cp -prfR /data/local/tmp/1/xbin /system/
./busybox cp -prfR /data/local/tmp/1/etc /system/
./busybox cp -prfR /data/local/tmp/1/usr /system/
./busybox cp -prf /data/local/tmp/1/build.prop /system/
./busybox cp -prfR /data/local/tmp/1/lib /system/
./busybox cp -prfR /data/local/tmp/1/framework /system/
./busybox cp -prfR /data/local/tmp/1/fonts /system/
./busybox cp -prfR /data/local/tmp/1/drm /system/
./busybox cp -prfR /data/local/tmp/1/media /system/
./busybox cp -prfR /data/local/tmp/1/app /system/
Hopefully you won't run out of space until you try and copy /app over. No worries! Your phone will still start, and you can easily restore those files after.
8. Flash the 2.1 kernel, and userdata.
Unlike in the previous instructions, you only want to remove system.sin from the flash files! Put userdata.sin back if you've removed it!
9. Turn on your phone and just hope you didn't mess up!
==APPS ON SD==
See this thread: App2SD Mod (Moves dalvik cache to SD) Instructions
ARGH!! MY PHONE IS STUCK IN A ETERNAL REBOOT? WHAT DO I DO?!
Well, if you know for sure what you did, and don't fancy reflashing all over again, then just plug in your phone and use adb to shell into the phone. Quickly fix the problem before the phone reboots!
Just putting this out there: These instructions were roughly written up. If you're having issues, don't be afraid to ask! If you spot any mistakes, please let me know! I'll expand on these instructions later.
All credits go to pulpoff2, for figuring out this solution, and propc for re-uploading the files, discovering steps 6 and 7 in the internal memory instructions, and for helping me fix these instructions multiple times.

Thank you! I will try this as soon as the files are available.
Are there any downsides? Is everything working as before? What about the speed (when loading apps for example)?

Yes, there are a few downsides. While booting from the sdcard, you cannot mount the sdcard via the phone (you'll need to use a card reader, or push/pull files with adb). There may be some performance issues while booting from the sdcard aswell. The camera and the music player also don't work.
However, if you decided to put the rom into the phone's internal memory, all this is fixed! Absolutely no downsides. Unless you don't like the theme, then I guess that is a downside.

thanks for making a new thread, thread pulpoff2 was hacked by ****-arsehole people! maybe.

I don't think so. The site that he used to host the files has been redirected to an anti-muslim site, by the looks of it.

aktw
Thanks man! Really appreciate it! Now I just need your tut for internal memory. Thanks again!
ML

Edit: Can you add app2sd tutorial?
Much more concise internal flashing (for anyone who wants it)
Code:
adb shell
su
cd /data/local/tmp
cat /sdcard/ext/bin/busybox > /data/local/tmp/busybox
chmod 755 busybox
./busybox mount -o remount,rw /system
./busybox sh
/data/local/tmp/busybox mkdir /data/local/tmp/1
/data/local/tmp/busybox losetup /dev/block/loop1 /sdcard/x8.img
/data/local/tmp/busybox mount -t ext2 -o rw,noatime,nodiratime /dev/block/loop1 /data/local/tmp/1
/data/local/tmp/busybox rm -r /system
/data/local/tmp/busybox cp -prf /data/local/tmp/1/* /system

There, the internal memory instructions are up.

EDIT
ALL FILES NEEDED FOR ABOVE METHOD STATED BY a-k-t-w
Mediafire folder
http://www.mediafire.com/?2kk19r7u4x1w3\
duckload:
data.img
X8.img
X8 2.1 russian
Hotfile:
data.img
X8.img
X8 2.1 russian
ext.rar at the attachment
for external rom (if you use adb shell)
Code:
su [B]look at phone screen and press "allow"[/B]
cd /data/local/tmp
cat /sdcard/ext/bin/busybox > /data/local/tmp/busybox
chmod 755 busybox
./busybox mount -o remount,rw /system
./busybox cp -r /sdcard/ext/* /system/
chmod 755 /system/bin/busybox
chmod 777 /system/bin/chargemon
chmod 755 /system/bin/e2fsck
chmod 4755 /system/bin/rootshell
to mount x8.img
Code:
mkdir /data/local/tmp/1
cat /sdcard/ext/bin/busybox > /data/local/tmp/busybox
/data/local/tmp/busybox losetup /dev/block/loop1 /sdcard/x8.img
/data/local/tmp/busybox mount -t ext2 -o rw,noatime,nodiratime /dev/block/loop1
EDIT : a-k-t-w completed the instruction himself. LOL..i think i'll be here for support..
-there you go.
ext.rar and unyaffs uploaded
i'll help by uploading the firmware files on mediafire.

actually I need the firmware 2.1 unmodified, but I'm okay to waiting.
Thx before.

That can be done. You mean unmodified, but rooted, right?
propc said:
...
i'll help by uploading the files on mediafire.
Click to expand...
Click to collapse
Thank you very much!! You have the latest ROM right? I'll add these to the OP when you are done.
a-k-t-w said:
[highlight]Mod Edit: Sorry, but I had to remove the link to the former dev's site due to the nature of that link[/highlight]
Click to expand...
Click to collapse
Understood.
Edit: @propc, What is unyaffs used for?

will the custom ROM have Timescape???? Or it will be the non-customized Android version.....
sry if this is a stupid question....
and i am just a beginner, so want a ask, what to you mean by "Flash 2.1 kernel" how to do it.....what are the files?? what is 2.1 kernel file??
i am new here...sry!

a-k-t-w said:
That can be done. You mean unmodified, but rooted, right?
Thank you very much!! You have the latest ROM right? I'll add these to the OP when you are done.
Click to expand...
Click to collapse
I think it's the latest. btw, it's stable no worries

mohakrastogi said:
will the custom ROM have Timescape???? Or it will be the non-customized Android version.....
sry if this is a stupid question....
and i am just a beginner, so want a ask, what to you mean by "Flash 2.1 kernel" how to do it.....what are the files?? what is 2.1 kernel file??
i am new here...sry!
Click to expand...
Click to collapse
Sorrry, I'll edit the OP. What I mean is, flash the 2.1 firmware, but without the files system.sin and userdata.sin (if your doing the sdcard method). This is basically flashing the 2.1 kernel only. Hang in there, the files will be available for download soon.
The custrom rom does not have timescape. You may have to restore ALL apps as there are some missing that will prevent you downloading your providers settings. I'm not sure which it is, so my solution is restoring them all. :-S
propc said:
I think it's the latest. btw, it's stable no worries
Click to expand...
Click to collapse
Excellent! Thanks again for the help.

a-k-t-w said:
Sorrry, I'll edit the OP. What I mean is, flash the 2.1 firmware, but without the files system.sin and userdata.sin (if your doing the sdcard method). This is basically flashing the 2.1 kernel only. Hang in there, the files will be available for download soon.
The custrom rom does not have timescape. You may have to restore ALL apps as there are some missing that will prevent you downloading your providers settings. I'm not sure which it is, so my solution is restoring them all. :-S
Excellent! Thanks again for the help.
Click to expand...
Click to collapse
i'm uploading data.img, x8.img and russian 2.1(.sin files)
any other files that need to be upload?
using unyaffs, you can extract x8.img directly to /system
maybe needed for future
folder for needed files are up (uploading other files .....)
HERE

please help me when write a command i got a problem with copy file
screenshot:
{
"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"
}
this a file problem with copy:
/data/local/tmp/busybox rm -r /system/app/com.mizusoft.relaxandsleep.apk
/data/local/tmp/busybox cp -prf /data/local/tmp/1/bin/* /system/bin/
/data/local/tmp/busybox cp -prf /data/local/tmp/1/drm/* /system/drm/
/data/local/tmp/busybox cp -prf /data/local/tmp/1/fonts/* /system/fonts/
/data/local/tmp/busybox cp -prf /data/local/tmp/1/framework/* /system/framework/
/data/local/tmp/busybox cp -prf /data/local/tmp/1/lib/* /system/lib/
/data/local/tmp/busybox cp -prf /data/local/tmp/1/usr/* /system/usr/
/data/local/tmp/busybox cp -prf /data/local/tmp/1/xbin/* /system/xbin/
/data/local/tmp/busybox cp -prf /data/local/tmp/1/build.prop /system/build.prop
/data/local/tmp/busybox cp -prf /data/local/tmp/1/media/* /system/media/
Click to expand...
Click to collapse
but remove a system -rm -r work for all files. help me pls

What is this custom ROM I keep reading about? What exactly is different there, except for the theme? I would like to see a screenshot of the theme, btw. Is JIT enabled?

Uhh. Probably not. The difference is just the theme, and root on 2.1. Because you can't get root any other way, if I'm not mistaken.

novincobra said:
please help me when write a command i got a problem with copy file
screenshot:
this a file problem with copy:
but remove a system -rm -r work for all files. help me pls
Click to expand...
Click to collapse
My guess is that you didn't mount the x8.img properly?
Or my cp command could be wrong. OH! Don't copy each app one by one, just the folders!
Don't put /* at the end! That means you are copying the contents of the folder! You want the entire folder on /system !

Ok, this means we have to use this customized ROM to gain root. Thanks for clarifying.

[Daily Update]Root / Unroot Sony Ericsson Xperia 2011 v1.5 without unlock bootloader

This is software i wrote to gift my friend and for vietnamese but i think should share here for easy to install all in one solution. My post translated by google so some silly words can be there Don't mind about that !
All credit for DooMLoRD : http://forum.xda-developers.com/showthread.php?t=1321582
{
"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"
}
Hello guys,
This is for all root or unroot Android machine production line in 2011 with Android versions from 2.1.x to 2.3.x without a unlock boot loader based on Revolutionary zergRush exploit! This version for all phones of Samsung phones Sony, HTC, Motorola, LG Goole Nexus and more!
Instructions:
First of all , we have to install NetFrameWork 3.5 to run this program
Now we have to do exactly 6 steps :
- Install PC Companion for adb driver installation
- Enable USB Debugging by going to: Menu \ Settings \ Applications \ Development
- Enable Install from Unknow sources by going to: Menu \ Settings \ Applications
- Increase screen timeout over 1 min
- Connect your phone to your computer via USB connection.
- Press Root button to complete proccess. Please post your log in this topic so i can see and tell you your phone rooted or not
The phone model can perform successful root:
Sony Xperia X10 (GB firmware)
Sony Xperia Arc (4.0.2.A.0.42)
Sony Xperia Arc S
Sony Xperia Play [R800i/R800x]
Sony Xperia Ray
Sony Xperia Neo
Sony Xperia Mini
Sony Xperia Mini Pro
Sony Xperia Pro
Sony Xperia Active
Live with Sony Walkman (WT19i/WT19a)
NTT Docomo Xperia ARCO SO-02C
Samsung Galaxy S2 [GT-i9100/GT-9100P]
Samsung Galaxy S II for T-Mobile (SGH-T989)
Samsung Galaxy S II for AT&T (SGH-I777), Skyrocket (SGH-i727)
Samsung Galaxy S II LTE Rogers Canada (SGH-I727R), Android version 2.3.5, Baseband version I727RUXKJ7
Samsung Galaxy S II Epic 4g Touch
Samsung Galaxy S2 HD LTE (SHV-E120S)(korea)
Samsung Galaxy i9100G
Samsung Galaxy S [i9000B] & [i9000 2.3.3 (PDA I9000BOJV8, Phone I9000XXJVO, CSC I9000GDTMJV7) and german T-Mobile branding]
Samsung Galaxy S Plus (GT-I9001) OS 2.3.3 and 2.3.6 (I9001ZSKP6)
Samsung Galaxy Mini GT-S5570 (GB only)
Samsung Galaxy Mini Pro i5510
Samsung Galaxy W [i8150]
Samsung Galaxy Y
Samsung Galaxy Tab [P1000] (2.3.3 firmware), [P1000N]
Samsung Galaxy Note [N7000]
Samsung Galaxy Player YP-G70 2.3.5 (GINGERBREAD.XXKPF)
Samsung Galaxy Ace (2.3.3, 2.3.4 firmware)
Samsung Nexus S [i9023] (2.3.6)
Samsung Nexus S 4G 2.3.7
Samsung Galaxy Nexus S [i9020] (2.3.6)
Samsung Exhibit (SGH-T759)
Samsung Exhibit 4G (SGH-T759) (2.3.3) Build UVKE8
Samsung Captivate i897 UCKH3
Motorola Milestone 3 [ME863 HK]
Motorola XT860, Bell XT860
Motorola Defy+
Motorola Droid X sys ver 4.5.605 w/ gingerbread
Motorola Droid X2 (2.3.4) Sys ver 1.3.380.MB870.Verizon.en.US Build 4.5.1A-DTN-150-30
Motorola XT883 (China Telecom)
Motorola XT862 (Verizon Droid3)
Motorola DROID RAZR
Nexus One (2.3.6 stock)
LG Revolution
Vizio VTAB1008 Tablet
Huawei IDEOS U8150 (2.2)
Log version:
- V1.0: First version
- V1.1: The stable version
- V1.2: Upgrade exploit zergRush, SupperUser 3.06
- V1.4 : Update Android Debug Bridge version 1.0.29
- V1.5 : Update exploit zergRush, SupperUser 3.07
All credits for : DooMLoRD and Revolutionary Team
Link to download: http://www.mediafire.com/?66ocvejtbs4m9

No one use this ??

mm just press root whit he phone connected at debbugin mode?
Works whit .58?

mmwwaaahahahaa FAIL.

I'll write instructions again because this post translated by google and you guys cannot understand
First of all , we have to install NetFrameWork 3.5 to run this program
Now we have to do exactly 6 steps :
- Install PC Companion for adb driver installation
- Enable USB Debugging
- Enable Install from Unknow sources
- Increase screen timeout over 1 min
- Connect your phone to your computer via USB connection.
- Press Root button to complete proccess. Please post your log in this topic so i can see and tell you your phone rooted or not

No one report for it ??

quangnhut123 said:
No one report for it ??
Click to expand...
Click to collapse
Sorry mate,rooted my phone o'redy ,Thanks for your effort to us

didnt work for me... xperia mini pro, 4.0.2.A.0.58
[+] Found a GingerBread ! 0x00015118
[*] Scooting ...
adb wait-for-device
adb push "data/busybox" /data/local/tmp/.
adb shell "chmod 755 /data/local/tmp/busybox"
adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
mount: permission denied (are you root?)
adb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox"
/system/xbin/busybox: cannot open for write: Read-only file system
adb shell "chown root.shell /system/xbin/busybox"
Unable to chmod /system/xbin/busybox: No such file or directory
adb shell "chmod 04755 /system/xbin/busybox"
Unable to chmod /system/xbin/busybox: No such file or directory
adb shell "/system/xbin/busybox --install -s /system/xbin"
/system/xbin/busybox: not found
adb shell "rm -r /data/local/tmp/busybox"
adb push "data/su" /system/bin/su
adb shell "chown root.shell /system/bin/su"
Unable to chmod /system/bin/su: No such file or directory
adb shell "chmod 06755 /system/bin/su"
Unable to chmod /system/bin/su: No such file or directory
adb shell "rm /system/xbin/su"
rm failed for /system/xbin/su, Read-only file system
adb shell "ln -s /system/bin/su /system/xbin/su"
link failed Read-only file system
adb push "data/Superuser.apk" /system/app/.
adb shell "cd /data/local/tmp/; rm *"
adb reboot
---------- Post added at 05:41 PM ---------- Previous post was at 05:26 PM ----------
my fault, now it worked! tried 2 times than it worked great! thx!

Anyone success with this root please report me to update phone can be root @@

before i installed cwm,i accidentally delete my "xbin" folder on system\xbin
then i put a new folder named xbin then put "sh" file for cwm. The cwm works,but did i messed up my phone?
Kindly someone upload the contents of xbin without with 7zip
edit:installed the busybox and then it restore the content of xbin

Black_jackss said:
before i installed cwm,i accidentally delete my "xbin" folder on system\xbin
then i put a new folder named xbin then put "sh" file for cwm. The cwm works,but did i messed up my phone?
Kindly someone upload the contents of xbin without with 7zip
edit:installed the busybox and then it restore the content of xbin
Click to expand...
Click to collapse
I dont think so . Xbin folder contain many and many files in this folder

quangnhut123 said:
I dont think so . Xbin folder contain many and many files in this folder
Click to expand...
Click to collapse
I thought the old files are back,coz xbin contain busybox file

thanks! 100% works!

- V1.4 : Update Android Debug Bridge version 1.0.29

awesome work dude finally rooted my phone and its very easy

Thanks for your comment Hopefull

Thanks.
WT19i ROOTED with firmware 4.0.2.a.0.58

VERY VERY NICE AND SIMPLE - Thank you

hanybanoub said:
VERY VERY NICE AND SIMPLE - Thank you
Click to expand...
Click to collapse
Thanks for ur reply

adb wait-for-device
adb server is out of date. killing...
* daemon started successfully *
adb shell "cd /data/local/tmp/; rm *"
rm failed for *, No such file or directory
adb push "data/zergRush" /data/local/tmp/.
adb shell "chmod 777 /data/local/tmp/zergRush"
adb shell "./data/local/tmp/zergRush"
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00015118
[*] Scooting ...
[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[+] Overseer found a path ! 0x000151e0
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x2abcccc4 0x0054
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0x6fd193d3 0x6fd39667
[*] Popping 24 more zerglings
[*] Sending 173 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
adb wait-for-device
adb push "data/busybox" /data/local/tmp/.
adb shell "chmod 755 /data/local/tmp/busybox"
adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
adb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox"
1520+1 records in
1520+1 records out
778324 bytes transferred in 0.268 secs (2904194 bytes/sec)
adb shell "chown root.shell /system/xbin/busybox"
adb shell "chmod 04755 /system/xbin/busybox"
adb shell "/system/xbin/busybox --install -s /system/xbin"
adb shell "rm -r /data/local/tmp/busybox"
adb push "data/su" /system/bin/su
adb shell "chown root.shell /system/bin/su"
adb shell "chmod 06755 /system/bin/su"
adb shell "rm /system/xbin/su"
adb shell "ln -s /system/bin/su /system/xbin/su"
adb push "data/Superuser.apk" /system/app/.
adb shell "cd /data/local/tmp/; rm *"
adb reboot
------
Seems to be ok?
Whats that:
adb shell "cd /data/local/tmp/; rm *"
rm failed for *, No such file or directory

[DEV] Current Progress and Guides: CRACKED UBOOT!!! Roms and Kernels Comming Soon

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?

[ROOT]Sony Xperia Tablet S SGPT121US ICS 4.0.3 ROOTED!!

I Rooted my New SONY XPERIA TABLET S SGPT121US ICS 4.0.3
{
"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"
}
Guide to Root your Xperia Tablet S!! ATTENTION: I am not responsible if you brick or damage your device, use at your OWN RISK!!
Files you need:
All in one Xperia Tablet root.zip
OR
ADB Tools
SonyTabletICS-2.zip
Superuser-3.1.3-arm-signed.zip
VpnFaker.apk (Attachment)
ATTENTION: For those who are not using the US firmware, the attached VpnFaker.apk may not be suitable for your tablet.
Please follow these steps(click me) to resign the VpnFaker.apk. Thanks to WonderEkin
***Pls Execute the command line by line***
Unzip those files into a dir, Open cmd console, cd to that dir
Run the following command and press Restore on your tablet
Code:
Code:
adb restore settings.ab
Check the result
Code:
Code:
adb shell ls -ld /data/data/com.android.settings/a
[COLOR="Green"]drwxrwxrwx system system a[/COLOR]
And continue, ignore the "rm -r a" permission denied error
Code:
Code:
adb shell
cd /data/data/com.android.settings
rm -r a
while : ; do ln -s /data a/file99; done
While the loop is running, open another cmd console and run
Code:
Code:
adb restore settings.ab
Once the restore process is completed, you can press CTRL+C on the 1st cmd console to break the loop
Check the /data permission
Code:
Code:
adb shell ls -ld /data
[COLOR="Green"]drwxrwxrwx system system data[/COLOR]
Then continue
Code:
Code:
adb push busybox /data/local/tmp
adb push rootkit.tar.gz /data/local/tmp
adb push Superuser.apk /data/local/tmp
adb push su /data/local/tmp
adb shell
cd /data/local/tmp
chmod 755 busybox
./busybox tar zxf rootkit.tar.gz
exit
Push the resigned VpnFaker.apk(resign by ZipSigner 2) and update the timestamp
Code:
Code:
adb push VpnFaker.apk /data/local/tmp
adb shell
touch -t 1346025600 /data/local/tmp/VpnFaker.apk
exit
Now, replace the VpnDialogs (ignore "cp: can't open 'system/xxxxxxx': Permission denied" while you execute "/data/local/tmp/busybox cp -r system system2")
Code:
Code:
adb shell
cd /data
/data/local/tmp/busybox cp -r system system2
/data/local/tmp/busybox find system2 -type f -exec chmod 666 {} \;
/data/local/tmp/busybox find system2 -type d -exec chmod 777 {} \;
mv system system-
mv system2 system
mv app app-
mkdir app
mv /data/local/tmp/VpnFaker.apk /data/app
Make sure the datatime is 2012/08/27 00:00
Code:
Code:
TZ=0 ls -l /data/app
[COLOR="green"]-rw-r--r-- shell shell 198580 2012-08-27 00:00 VpnFaker.apk[/COLOR]
Generate the packages.xml
Code:
Code:
/data/local/tmp/busybox sed -f /data/local/tmp/packages.xml.sed system-/packages.xml > system/packages.xml
And double check the result
Code:
Code:
/data/local/tmp/busybox grep vpndialogs system/packages.xml
[COLOR="green"]<updated-package name="com.android.vpndialogs" codepath="/system/app/VpnDialogs.apk" nativelibrarypath="/data/data/com.android.vpndialogs/lib" flags="1" ft="136f14be668" it="136f14be668" ut="136f14be668" version="15" shareduserid="1000">
<package name="com.android.vpndialogs" codepath="/data/app/VpnFaker.apk" nativelibrarypath="/data/data/com.android.vpndialogs/lib" flags="1" ft="1396560b400" it="1396560b400" ut="1396560b400" version="45" shareduserid="1000">[/COLOR]
Exit adb shell and reboot, you should see something like "Android is updating" during startup.
Code:
Code:
exit
adb reboot
Start the injected Terminal Emulator
Code:
Code:
adb shell am start -n com.android.vpndialogs/.Term
In Terminal Emulator
Code:
Code:
id
You should see the uid is 1000(system)
Still in the Terminal Emulator, ignore the script error
Code:
Code:
/data/local/tmp/onload.sh
/data/local/tmp/onload2.sh
Now back to the cmd console
Code:
adb shell
/dev/sh
id
Check the uid is 2000(shell)
And
Code:
Code:
chown 0.0 /data/local/tmp/_su
chmod 6755 /data/local/tmp/_su
/data/local/tmp/_su
id
Check the root access uid 0(root)
Backup /system (you may just skip it)
Code:
Code:
dd if=/dev/block/mmcblk0p3 of=/mnt/sdcard/system.ext4 bs=128K
Copy su & Superuser.apk to /system
Code:
Code:
/data/local/tmp/busybox mount -o rw,remount /system
/data/local/tmp/busybox cp /data/local/tmp/_su /system/xbin
chown 0.0 /system/xbin/_su
chmod 6755 /system/xbin/_su
/data/local/tmp/busybox cp /data/local/tmp/su /system/xbin
chown 0.0 /system/xbin/su
chmod 6755 /system/xbin/su
/data/local/tmp/busybox cp /data/local/tmp/Superuser.apk /system/app
/data/local/tmp/busybox mount -o ro,remount /system
sync
exit
Check the /system _su is working or not
Code:
Code:
_su
id
Should be uid 0(root)
And move the original /data/app & /data/system back (the original steps will keep the VpnFaker.apk, but i skip it)
Code:
Code:
cd /data
mv app app2
mv app- app
mv system system2
mv system- system
exit
exit
Reboot your tab
Code:
adb reboot
Now, your Sony Xperia Tablet S ICS 4.0.3 should be rooted.
Credits Yupandra2012 for link to Original Root Method.
& WonderEkin for his Translation from Japanese to English.

I have the Sony Tablet S and this is as far as I can get:
c:\SonyTablet>adb shell
[email protected]:/ $ cd /data
cd /data
[email protected]:/data $ /data/local/tmp/busybox cp -r system system2
/data/local/tmp/busybox cp -r system system2
cp: can't open 'system/entropy.dat': Permission denied
cp: can't open 'system/batterystats.bin': Permission denied
cp: can't open 'system/users/userlist.xml': Permission denied
cp: can't open 'system/users/0.xml': Permission denied
cp: can't open 'system/accounts.db': Permission denied
cp: can't open 'system/accounts.db-journal': Permission denied
cp: can't open 'system/called_pre_boots.dat': Permission denied
cp: can't open 'system/wallpaper_info.xml': Permission denied
cp: can't open 'system/appwidgets.xml': Permission denied
1|[email protected]:/data $
Any ideas?

This Thread is for Xperia Tablet S, but anyways you ignore this error and complete the rest of the steps, I had the same error, ignored it and it worked for me.

Another road block:
c:\STS>adb shell
[email protected]:/ $ cd /data
cd /data
[email protected]:/data $ /data/local/tmp/busybox cp -r system system2
/data/local/tmp/busybox cp -r system system2
cp: can't open 'system/entropy.dat': Permission denied
cp: can't open 'system/batterystats.bin': Permission denied
cp: can't open 'system/users/userlist.xml': Permission denied
cp: can't open 'system/users/0.xml': Permission denied
cp: can't open 'system/accounts.db': Permission denied
cp: can't open 'system/accounts.db-journal': Permission denied
cp: can't open 'system/called_pre_boots.dat': Permission denied
cp: can't open 'system/wallpaper_info.xml': Permission denied
cp: can't open 'system/appwidgets.xml': Permission denied
1|[email protected]:/data $ /data/local/tmp/busybox find system2 -type f -exec chmod
666 {} \;
d system2 -type f -exec chmod 666 {} \; <
[email protected]:/data $ /data/local/tmp/busybox find system2 -type d -exec chmod 7
77 {} \;
system2 -type d -exec chmod 777 {} \; <
[email protected]:/data $ mv system system-
mv system system-
[email protected]:/data $ mv system2 system
mv system2 system
[email protected]:/data $ mv app app-
mv app app-
[email protected]:/data $ mkdir app
mkdir app
[email protected]:/data $ mv /data/local/tmp/VpnFaker.apk /data/app
mv /data/local/tmp/VpnFaker.apk /data/app
[email protected]:/data $ TZ=0 ls -l /data/app
TZ=0 ls -l /data/app
-rw-rw-rw- shell shell 200436 2012-08-27 00:00 VpnFaker.apk
[email protected]:/data $ /data/local/tmp/busybox sed -f /data/local/tmp/packages.xm
l.sed system-/packages.xml > system/packages.xml
tem-/packages.xml > system/packages.xml <
/system/bin/sh: cannot create system/packages.xml: Permission denied
1|[email protected]:/data $ /data/local/tmp/busybox grep vpndialogs system/packages.
xml
p vpndialogs system/packages.xml <
<package name="com.android.vpndialogs" codePath="/system/app/VpnDialogs.apk" nat
iveLibraryPath="/data/data/com.android.vpndialogs/lib" flags="1" ft="138eb7f41b0
" it="138eb7f41b0" ut="138eb7f41b0" version="15" sharedUserId="1000">
[email protected]:/data $ exit
exit
c:\STS>adb reboot
c:\STS>adb shell am start -n com.android.vpndialogs/.Term
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Starting: Intent { cmp=com.android.vpndialogs/.Term }
Error type 3
Error: Activity class {com.android.vpndialogs/com.android.vpndialogs.Term} does
not exist.
c:\STS>
There were a few things that didn't match up along the way as well...
I am lost...

same here:
adb shell am start -n com.android.vpndialogs/.Term
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Starting: Intent { cmp=com.android.vpndialogs/.Term }
Error type 3
Error: Activity class {com.android.vpndialogs/com.android.vpndialogs.Term} does
not exist.

Do you type this in?
Code:
while : ; do ln -s /data a/file99; done

Now, can you please upload a system dump of Xperia Tablet S?
Thanks!

Guys the error you are facing means missing terminal emulator is not installed on your device. make sure you have terminal emulator downloaded and installed from Google play. Also note you will face errors with the onload scripts using the emulator just ignore it and resume normally.

could you upload the terminal emulator?
zorbakun said:
Guys the error you are facing means missing terminal emulator is not installed on your device. make sure you have terminal emulator downloaded and installed from Google play. Also note you will face errors with the onload scripts using the emulator just ignore it and resume normally.
Click to expand...
Click to collapse
I am a user in China,and my tablet S cant's download any app from googleplay.Can you upload the terminal emulator?
Thank you very much.

txiangyang said:
I am a user in China,and my tablet S cant's download any app from googleplay.Can you upload the terminal emulator?
Thank you very much.
Click to expand...
Click to collapse
The Vpnfaker.apk has already injected with terminal emulator. Moreover, all installed apps will temporary missing during the process.

as WonderEkin pointed out, people with problem (Error: Activity class {com.android.vpndialogs/com.android.vpndialogs.Term} does
not exist.) don't have the US version of the device hence They will need to re-sign the VpnFaker.apk as described here and start all over again from the beginning.
Guide has been updated to reflect the same.
Credits to WonderEkin

This method works like a charm. Yay for rooted Tablet S!
Thank you so much!

I was getting this:
adb shell am start -n com.android.vpndialogs/.Term
Starting: Intent { cmp=com.android.vpndialogs/.Term }
Error type 3
Error: Activity class {com.android.vpndialogs/com.android.vpndialogs.Term} does not exist.
I have a Tablet S, US Tablet, US Firmware, what am I suppose to do with the VpnFaker.apk?
"ATTENTION: For those who are not using the US firmware, the attached VpnFaker.apk may not be suitable for your tablet.
Please follow these steps(click me) to resign the VpnFaker.apk. Thanks to WonderEkin"
Not clear to me...

Is this only for new xperia tab s or does it work for the old tab s?

WOW so fast ..
Even though Sony Xperia Tablet S ain't Global out there yet ..
Great Job .

typo86 said:
I was getting this:
adb shell am start -n com.android.vpndialogs/.Term
Starting: Intent { cmp=com.android.vpndialogs/.Term }
Error type 3
Error: Activity class {com.android.vpndialogs/com.android.vpndialogs.Term} does not exist.
I have a Tablet S, US Tablet, US Firmware, what am I suppose to do with the VpnFaker.apk?
"ATTENTION: For those who are not using the US firmware, the attached VpnFaker.apk may not be suitable for your tablet.
Please follow these steps(click me) to resign the VpnFaker.apk. Thanks to WonderEkin"
Not clear to me...
Click to expand...
Click to collapse
If you don't have the US version of the tablet, then you may need to re-sign the VpnFaker.apk, but since you own the US version, then no need to resign it. just make sure you follow the procedure carefully one step at a time, and if possible have terminal emulator installed on your tab as well.

Roscobigfoot said:
Is this only for new xperia tab s or does it work for the old tab s?
Click to expand...
Click to collapse
Check this thread for old Sony Tablet S.

SWFlyerUK said:
Do you type this in?
Code:
while : ; do ln -s /data a/file99; done
Click to expand...
Click to collapse
Yes you do.

Still no luck...
Tried it both ways, followed instructions and I still end up here:
adb shell am start -n com.android.vpndialogs/.Term
Starting: Intent { cmp=com.android.vpndialogs/.Term }
Error type 3
Error: Activity class {com.android.vpndialogs/com.android.vpndialogs.Term} does not exist.
US old Tablet S, US Firmware...Is there anyone with a US tablet that has been able to root this way?

Now you can use my new All in one Xperia Tablet Root.zip for easier process, just extract it to an easy path like C:/Xperia root/ then open CMD pointing to the same path and Follow the guide in the first page.

Stuck on kindle fire screen

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

Better Mobile App

welcome