Photo by Logxen (aka not my trash!)
{
"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"
}
No warranties, no guarantees. If this ruins your device, your fault, not mine. Consider this a test build, backup important stuff manually to your PC for now (photos etc)
This requires an sdcard installed
[Image]
http://download.cunninglogic.com/cwr_ventana_2.img
39b5557cf3802d677e33cce76047ef60 *cwr_ventana_2.img
[Source]
https://github.com/CunningLogic/android_device_lenovo_ventana
[Instructions]
Code:
adb push cwr_ventana_2.img /data/local/
adb shell
su
mount -o rw,remount /system
echo "#!/system/bin/sh" > /system/etc/install-recovery.sh
dd if=/data/local/cwr_recovery_2.img of=/dev/block/mmcblk0p1
[Credits]
djrbliss - For rooting the thinkpad
utkanos - walking me through the device config setup
CM, Koush and everyone who has worked on CWR
FIRST
yea, FIRST!
J/K, space reserved for future use.
Yo second!!!!!
Indeed. Thanks jcase and everyone else..
thanks!
Will check every hours this thread for image link
Thats fantastic! will try this as soon as an image file gets posted! Hopefully it wont be long till it will be running ICS!
Can confirm root as I'm currently running it on my tablet. Bliss did it himself and is going to package it and release it in a couple of hours.
Thanks to everyone for their hard work with this.
quyTam said:
thanks!
Will check every hours this thread for image link
Click to expand...
Click to collapse
Same here.
TS
Umm, I can't find a "HOW-TO-ROOT" thread.
Where is it??
yirsung said:
Umm, I can't find a "HOW-TO-ROOT" thread.
Where is it??
Click to expand...
Click to collapse
its not released yet waiting for confirmation for bounty collection
Sent from my ThinkPad Tablet using Tapatalk
Thanks for sharing this it worked great, except for the instructions I needed to use
dd if=/data/local/cwr_ventana_2.img of=/dev/block/mmcblk0p1
rather than
dd if=/data/local/cwr_recovery.img of=/dev/block/mmcblk0p1
to match the name of your file.
Thanks again for sharing, CWR seems to be running perfectly.
Also for those looking for root the exploit has been posted here.
Hello, can't install CWM. Made everything as in first post (but changed filename). After reboot tried to enter recovery mode, there was text on screen entering recovery or something but device booted to system and nothing happend. Whats wrong. Here is output of instalation:
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb push cwr_ventana_2
.img /data/local/
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
1298 KB/s (4452352 bytes in 3.347s)
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ su
su
# mount -o rw,remount /system
mount -o rw,remount /system
# echo "#!/system/bin/sh" > /system/etc/install-recovery.sh
echo "#!/system/bin/sh" > /system/etc/install-recovery.sh
# dd if=/data/local/cwr_ventana_2.img of=/dev/block/mmcblk0p1
dd if=/data/local/cwr_ventana_2.img of=/dev/block/mmcblk0p1
8696+0 records in
8696+0 records out
4452352 bytes transferred in 1.903 secs (2339648 bytes/sec)
#
CWR test
did not seem to work . doesn't reboot in recovery but straight in normal boot
what info do you need to help debugging
redbaron said:
Hello, can't install CWM. Made everything as in first post (but changed filename). After reboot tried to enter recovery mode, there was text on screen entering recovery or something but device booted to system and nothing happend. Whats wrong. Here is output of instalation:
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb push cwr_ventana_2
.img /data/local/
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
1298 KB/s (4452352 bytes in 3.347s)
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ su
su
# mount -o rw,remount /system
mount -o rw,remount /system
# echo "#!/system/bin/sh" > /system/etc/install-recovery.sh
echo "#!/system/bin/sh" > /system/etc/install-recovery.sh
# dd if=/data/local/cwr_ventana_2.img of=/dev/block/mmcblk0p1
dd if=/data/local/cwr_ventana_2.img of=/dev/block/mmcblk0p1
8696+0 records in
8696+0 records out
4452352 bytes transferred in 1.903 secs (2339648 bytes/sec)
#
Click to expand...
Click to collapse
have you tried usiing rom manager? ¿? I have not had the chance if not I would test currently backing up using titanium backup
Sent from my ThinkPad Tablet using Tapatalk
I installed it. It works. Though /sdcard cannot be found and backup doesn't work. But I'm sure these will be figured out in the near future
I've got it installed just fine and even got the back up files
Gonna do a clean install and then see about dumping the images
ClockworkMod Recovery boots for me and was backing up but failed while it was backing up /data for me (I have tried twice now). It seems to backup /system just fine though, I don't know why it would fail during the /data backup. Has anyone else successfully made a backup yet?
failed to restart in recovery for me (exactly as redBaron)
Try to install CWM 3 times
OK, booting in recovery works fine, but NOT via Rom Manager !
(only by pressing and releasing vol+ button when booting)
jhankinson said:
Thanks for sharing this it worked great, except for the instructions I needed to use
dd if=/data/local/cwr_ventana_2.img of=/dev/block/mmcblk0p1
rather than
dd if=/data/local/cwr_recovery.img of=/dev/block/mmcblk0p1
to match the name of your file.
Thanks again for sharing, CWR seems to be running perfectly.
Also for those looking for root the exploit has been posted here.
Click to expand...
Click to collapse
Yes ... one has to take great care with naming files ... I did something similar and used Root Explorer to rename the cwr file correctly.
recovery
still not workign for me.
tried to re-install it a few times
when i boot in recovery with Vol++ i see the booting into recovery message and then after a second or so vibrate again and start normal boot
I am very excited to see this news - though i'm going to wait until there is a semi-stable, well establish path for Root. Hopefully this achievement leads to the Thinkpad Tablet getting much more attention, its a pretty badass tablet and should prove to be a pretty good performer once all the Lenovo crapware is tossed out. Glad I remained faithful and patient!
Related
Firstly i did not do this guide. it took it from this forum and just compile so that newbie like me can easily root their tattoo.....
ROOTING TATTOO
Download the ZIP file attached to this post. Extract the files to a safe location - perhaps C:\Tattoo ?
Now, you'll need adb for windows. You can get it from COBURN website's server here: ADB for windows.
Make sure your device is in USB Debug Mode (Settings > Applications > Development).
Extract all the files in the adb4win zip file to your C:\Tattoo folder.
Now, go to Command Prompt. In XP, it's under System Tools in Accessories. In Vista/7, it'll be under accessories.
Do the following at the command line:
C:\Users\Coburn> cd C:\Tattoo
Then you will get this C:\Tattoo
Next type in this:
C:\Tattoo> adb-windows shell "mkdir /data/local/bin" (with the quotes!).
If you get a error (like mkdir failed, file/folder exists), this is fine!
just means that the folder already exists in your phone
Now, run this command:
C:\Tattoo> adb-windows push m7 /data/local/bin/m7
this will just take a few seconds
Run this:
C:\Tattoo> adb-windows shell "cd /data/local/bin && chmod 755 ./m7" (with the quotes!)
This allows you to run the sucker. Looks like something nothing happen but it did something.
C:\Tattoo> adb-windows shell
This will dump you at a "$" shell. do the following:
C:\Tattoo> adb-windows shell
$ cd /data/local/bin
$ while ./m7 ; do : ; done
...lotsa text will flow down your screen. This is normal.
Soon, you'll be greeted with this:
#
This is the root prompt! If you get stuff like this:
# usage: reboot ...
usage: reboot ....
usage: reboot ...
Just keep your cool, press enter and the # will pop again. This is due the exploit spawning reboots to gain the shell.
Next type in this:
export LD_LIBRARY_PATH=/system/lib
export PATH=/system/bin
Check if u have root, type:
id
you will get
# id
uid=0(root) gid=1000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet)
The uid=0(root) is important, so call your phone is root.
REMOUNT PARTITION (SU)
Now you need to install su. Exit your root shell (via CTRL+C) and download this su.zip and extract it to C:\Tattoo.
DO NOT EXIT THE COMMAND PROMPT WINDOW.
in your command prompt window, do this:
C:\Tattoo> adb-windows push su /data/local/bin/su
Then break out a shell...
C:\Tattoo> adb-windows shell
at the $ prompt, enter:
$ chmod 755 /data/local/bin/su
$ cd /data/local/bin/
$ while 'true' ; do ./m7 ; done
It will change from $ to #
Type in this:
export LD_LIBRARY_PATH=/system/lib
export PATH=/system/bin
Next type in this:
# chown root.root /data/local/bin/su
# chmod 4755 /data/local/bin/su
# mount -o rw,remount /dev/block/mtdblock5 /data
# mount -o rw,remount /dev/block/mtdblock3 /system
After that, you can exit out of the root shell, and try a normal shell and this:
$ /data/local/bin/su
...which should make you get a nice # prompt.
Custom Boot.img:
Boot img v2:http://forum.xda-developers.com/show...0&postcount=38
Tattoo-hack.ko:http://forum.xda-developers.com/atta...2&d=1266670581
Download this flash_image:http://forum.xda-developers.com/attachment.php?attachmentid=287463&d=1267386499
adb push flash_image ./data/local/bin/flash_image
adb push Mainfram3.boot.02.img /sdcard/Mainfram3.boot.02.img
adb push tattoo-hack.ko ./data/local/bin/tattoo-hack.ko
c:\tattoo>adb shell
$ su
su
su: access granted, courtesy of www.magicandroidapps.com
# insmod /data/local/bin/tattoo-hack.ko
#mount -o rw,remount /dev/block/mtdblock5 /data
#mount -o rw,remount /dev/block/mtdblock3 /system
#chmod 755 /data/local/bin/flash_image
#/data/local/bin/flash_image boot /sdcard/Mainfram3.boot.02.img
Cutom Recovery Img:
After custom boot.img
adb push TCRI.alpha.img /sdcard/TCRI.alpha.img
c:\tattoo>adb shell
#/data/local/bin/flash_image recovery /sdcard/TCRI.alpha.img
once again i did not make the guide...i only compile it from different thread and put them as 1....tats all....thanks to all the devs that came up with the guide.....
hi!
will be possible flash official ROM made HTC after rooting proces?
I'm totaly new to this android applications
correct me if im wrong...you can always flash official rom frm htc for that paticular phone model....whether root or not....
the flash image no longer exists...
@Bikers
Download here:http://forum.xda-developers.com/attachment.php?attachmentid=287463&d=1267386499
@shazarul
Correct the link in the post.
c:\tattoo>adb shell
$ su
su
su: access granted, courtesy of www.magicandroidapps.com
i get permision denied! I know there is somewhere else a thread like this but i jus t can't find it...
try it with root 1 click by maverixx
have change the flash_image link..... biker i think u have to root it again???/ i think should b the easy way out....
just flashed custom boot img using this tutorial, thanks !
Thanks a lot, but I have a problem.
When I get to:
Code:
adb push Mainfram3.boot.02.img /sdcard/Mainfram3.boot.02.img
I get this:
{
"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"
}
I had the same problem with http://forum.xda-developers.com/showthread.php?t=644279&page=6 1 click root script when pushing to /sdcard...
have you tried to put it directly in your sd card? Did you putted your phone in MSSync at the usb options?
try to unmount sdcard from the phone, with the command in the notification bar of the tattoo
i am having this error while flashing custom recovery image ...
# /data/local/bin/flash_image boot /sdcard/Mainfram3.boot.02.img
/data/local/bin/flash_image boot /sdcard/Mainfram3.boot.02.img
error opening /sdcard/Mainfram3.boot.02.img: No such file or directory
#
Click to expand...
Click to collapse
where am i getting it wrong ??? till that i have no issues in following tutorial...
please help me...
chtamina said:
try to unmount sdcard from the phone, with the command in the notification bar of the tattoo
Click to expand...
Click to collapse
this suggestion solved my problem.... thanks chtamina..... you made my day...
I'm running one-click root, unleash the beast, circle battery and ext2 lag fix. Unleash the beast updated my hosts file to block ads but unfortunately also blocks the Audiogalaxy servers which I'd like to use for their new streaming app.
Trying to edit the hosts file I did an adp pull to my PC, edited the file and saved. But I can't push it back to /system/etc/hosts as I get a "permission denied" error.
After some reading it seems this means my root directory doesn't mounted with write permissions. I tried "adb root" but it gives me error "cannot run as root in production builds" and tried "adb remount" but that gives me error "remount failed: No such file or directory". I'm stuck at this point.
Any ideas? Could this be because I'm running the ext2 lag fix?
phishie said:
I'm running one-click root, unleash the beast, circle battery and ext2 lag fix. Unleash the beast updated my hosts file to block ads but unfortunately also blocks the Audiogalaxy servers which I'd like to use for their new streaming app.
Trying to edit the hosts file I did an adp pull to my PC, edited the file and saved. But I can't push it back to /system/etc/hosts as I get a "permission denied" error.
After some reading it seems this means my root directory doesn't mounted with write permissions. I tried "adb root" but it gives me error "cannot run as root in production builds" and tried "adb remount" but that gives me error "remount failed: No such file or directory". I'm stuck at this point.
Any ideas? Could this be because I'm running the ext2 lag fix?
Click to expand...
Click to collapse
did you type in su before using pushing the file?
Edit: it would be like this
su (press enter)
adb push blah*
tytdfn said:
did you type in su before using pushing the file?
Edit: it would be like this
su (press enter)
adb push blah*
Click to expand...
Click to collapse
Yea I had tried that. "su" by itself is not a recognized command. "adb su" just prints the adb help text (lists commands).
{
"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"
}
Ok maybe I need to simplify my question:
Does anyone know how to get the root directory to mount to USB with write permissions?
This is what I use to put things in and out of /system/. Haven't a clue what most of the commands mean, but it works for me all the time.
(You have to be root'd)
Code:
First, put the file on your desktop.
adb push %userprofile%\desktop\<filename> /sdcard
adb shell
su
mount -o rw,remount /system
rm /system/.../<filename>
busybox mv /sdcard/<filename> /system/...
Hope that helps.
MikeyMike01 said:
This is what I use to put things in and out of /system/. Haven't a clue what most of the commands mean, but it works for me all the time.
(You have to be root'd)
Code:
First, put the file on your desktop.
adb push %userprofile%\desktop\<filename> /sdcard
adb shell
su
mount -o rw,remount /system
rm /system/media/<filename>
busybox mv /sdcard/<filename> /system/media
Hope that helps.
Click to expand...
Click to collapse
Cool I'll try that, are you running any lag fixes by chance?
phishie said:
Cool I'll try that, are you running any lag fixes by chance?
Click to expand...
Click to collapse
Yeah, the one that come in the old SuperRooter.
MikeyMike01 said:
This is what I use to put things in and out of /system/. Haven't a clue what most of the commands mean, but it works for me all the time.
(You have to be root'd)
Code:
First, put the file on your desktop.
adb push %userprofile%\desktop\<filename> /sdcard
adb shell
su
mount -o rw,remount /system
rm /system/.../<filename>
busybox mv /sdcard/<filename> /system/...
Hope that helps.
Click to expand...
Click to collapse
Permission denied when trying to push to /sdcard.
MikeyMike01 said:
This is what I use to put things in and out of /system/. Haven't a clue what most of the commands mean, but it works for me all the time.
(You have to be root'd)
Code:
First, put the file on your desktop.
adb push %userprofile%\desktop\<filename> /sdcard
adb shell
su
mount -o rw,remount /system
rm /system/.../<filename>
busybox mv /sdcard/<filename> /system/...
Hope that helps.
Click to expand...
Click to collapse
By the way this worked perfectly once I realized I needed to physically approve the "su" request on the phone. Thanks again.
Hey Samsung Galaxy tab users and devs.
So im' having a bit of a problem here trying to remount my galaxy tab so i can read/write to it. My cache size is the famous and well hated 25 MB file size limit so i wanted to change it by using this method:
http://forum.xda-developers.com/showpost.php?p=18840882&postcount=227
Im currently running gingerbread 2.3 with root priviliges, and Clockworkmod 3.0.5
{
"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] [/IMG]
Whenever i've try to use the remount command it get this error:
http://imageshack.us/photo/my-images/600/androidadb.jpg/
So what am im doing wrong? running WIn 7 64 bit and my tablet is set to usb debugging mode.
Been searching Google and XDA the couple of days but haven't found any solution.
In advance thanks, jakk212
Jakk212 said:
Hey Samsung Galaxy tab users and devs.
So im' having a bit of a problem here trying to remount my galaxy tab so i can read/write to it. My cache size is the famous and well hated 25 MB file size limit so i wanted to change it by using this method:
http://forum.xda-developers.com/showpost.php?p=18840882&postcount=227
Im currently running gingerbread 2.3 with root priviliges, and Clockworkmod 3.0.5
[/URL] [/IMG]
Whenever i've try to use the remount command it get this error:
http://imageshack.us/photo/my-images/600/androidadb.jpg/
So what am im doing wrong? running WIn 7 64 bit and my tablet is set to usb debugging mode.
Been searching Google and XDA the couple of days but haven't found any solution.
In advance thanks, jakk212
Click to expand...
Click to collapse
Hi Jakk,
I'm not a developer, but, the error seems indicate that adb can't remount as RW the /system, so:
1) adb shell work? (you must see a "#" if you are root)
2) have you installed busybox?
3) the 01newcache script in init.d directory work if you have a rom/kernel that suppor init.d
I use the script and i can confirm that work very fine
Bye
Idk
1) How am i able to see that? Should i see a # at the ADB CMD box? Root checker veryfies that my device is rooted.
2) Yes it's installed using V1.16.2androidminimal - updating now.
3) How can i check if my ROM supports that? My rom is the Stock safe Rom provided when flashing to Overcome.
Using the "adb shell" command in ADB gives me a $
using the adb shell command gives me the $ as i said.
When using the command su it gives me the # you're where talking about.
Jakk212 said:
using the adb shell command gives me the $ as i said.
When using the command su it gives me the # you're where talking about.
Click to expand...
Click to collapse
Though im still not capable of remounting my galaxy tab
Jakk212 said:
using the adb shell command gives me the $ as i said.
When using the command su it gives me the # you're where talking about.
Click to expand...
Click to collapse
Hi Jakk,
Yes, so you have a working superuser thats ok, but if you have stock kernel (i think) there isn't any init.d support so the only way is to try manually.
Another way is installing a custom rom (boca, overcome, etc..) or custom kernel that have init.d support.
Bye
Idk
---------- Post added at 02:01 PM ---------- Previous post was at 01:55 PM ----------
Jakk212 said:
Though im still not capable of remounting my galaxy tab
Click to expand...
Click to collapse
There is some errore message when you try to remount via adb? Try to remount filsystem directly in a root shell, here :
http://forum.xda-developers.com/showthread.php?t=859712
there is, at the end of first post, the instruction to mount r/o the /system
Bye
Idk
Hmm actually not sure that there is a custom kernel installed (i don't suppose since it's a stock firmware, then the kernel should be stock - dosen't allow me to overglock however xD )
I've get this message:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
30336CA087D400EC device
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb remount
remount failed: Operation not permitted
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ su
# adb remount
adb remount
adb: not found
# remount
remount
remount: not found
#
Gonna try with to remount it directly in a root shell as you've said - see if that works.
I'll suppose that this is what im gonna write in adb?
Code:
> adb shell
# mount -o remount,rw -t rfs /dev/block/stl9 /system
# exit
Tried to flash the overcome kernel v3.3.1
Also i've connected the tab while in recovery mode now i get a ~$ when entering adb shell.
Jakk212 said:
Hmm actually not sure that there is a custom kernel installed (i don't suppose since it's a stock firmware, then the kernel should be stock - dosen't allow me to overglock however xD )
I've get this message:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
30336CA087D400EC device
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb remount
remount failed: Operation not permitted
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ su
# adb remount
adb remount
adb: not found
# remount
remount
remount: not found
#
Gonna try with to remount it directly in a root shell as you've said - see if that works.
I'll suppose that this is what im gonna write in adb?
Code:
> adb shell
# mount -o remount,rw -t rfs /dev/block/stl9 /system
# exit
Click to expand...
Click to collapse
Hi Jakk,
1) adb is use only from PC (windows or linux), there isn't any adb command into android OS...
2) My mistake: read this links: http://android-tricks.blogspot.com/2009/01/mount-filesystem-read-write.html and http://forum.xda-developers.com/showthread.php?t=685146; the above command is about rfs (Samsung Robust File System); if you have converted the filesystem into ext4, i'm not sure that above command work....
sorry
Bye
Idk
Im am able to mount using the
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Command you told me about but when i try to push the newcache file
Code:
adb push 01newcache /system/etc/init.d/
it simply says:
adb: Not found
When trying to copy it outside the shell it says:
failed to copy "01newcache" to "system/etc/init.d/": Is a directory.
Jakk212 said:
Im am able to mount using the
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Command you told me about but when i try to push the newcache file
Code:
adb push 01newcache /system/etc/init.d/
it simply says:
adb: Not found
When trying to copy it outside the shell it says:
failed to copy "01newcache" to "system/etc/init.d/": Is a directory.
Click to expand...
Click to collapse
Hi,
if you try the adb into android phone shell, simply don't work because adb is a windows command (adb = android debug bridge).
The good is seems you have the init.d directory, so try this:
go to android phone shell and remount /system
in a windows cmd shell do this:
adb push 01newcache /system/etc/init.d/
return into android phone shell:
adb shell
cd /system/etc/init.d
chmod 777 01newcache
ls -l /system/etc/init.d (to show the contend of init.d)
exit
Bye
So you mean that i'll just simply open a cmd box without refering to adb and then use the adb push 01newcache /system/etc/init.d/ command? How's that gonna work?
If you've got the time could you please assist me over teamwiever or something similair?
Jakk212 said:
So you mean that i'll just simply open a cmd box without refering to adb and then use the adb push 01newcache /system/etc/init.d/ command? How's that gonna work?
If you've got the time could you please assist me over teamwiever or something similair?
Click to expand...
Click to collapse
Hi Jakk,
Rollback, read this:
http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
The operation is in 2 steps, pc and android terminal: adb is pc side the rest in android terminal.
I'm sorry, i prefer forum support, i've no time at this moment.....
If i'm not clear enough please tell me, i don't know your skill level...
Bye
Idk
pretty skilled, gonna start my IT-technician education after christmas, and i've know a bit bat programming from working with windows server and also a bit html and php.
capable of flashing ROMS, unbricking etc but haven't used ADB before. I've configured adb the exact same way as the tut you've sent me.
However i still just get's error codes like adb not found, remount not found, Is a directory, or are you sure you are rooted?
Jakk212 said:
pretty skilled, gonna start my IT-technician education after christmas, and i've know a bit bat programming from working with windows server and also a bit html and php.
capable of flashing ROMS, unbricking etc but haven't used ADB before. I've configured adb the exact same way as the tut you've sent me.
However i still just get's error codes like adb not found, remount not found, Is a directory, or are you sure you are rooted?
Click to expand...
Click to collapse
Is working ?:
Code:
adb shell
If yes then:
Code:
su
mount -o remount rw /system
then - if you are not able to use "push" - copy the file in your SDcard then, while in adb shell:
Code:
cp /sdcard/yourfile /your-destination/
Seem easy
then which one am i going to choose? The overwrite?
and am i just supposed to write it like this:
cp /mnt/sdcard/01newcache /system/etc/init.d/
Because then i've get a cp can't create /system/etc/init.d/: Is a directory
Jakk212 said:
then which one am i going to choose? The overwrite?
and am i just supposed to write it like this:
cp /mnt/sdcard/01newcache /system/etc/init.d/
Because then i've get a cp can't create /system/etc/init.d/: Is a directory
Click to expand...
Click to collapse
Try this:
cp /mnt/sdcard/01newcache /system/etc/init.d/01newcache
Bye
If you have the init.d folder then just manul copy "01newcache" to your sd card and from your tab, with a root explorer (i use esfile explorer with root option enabled from option menu) copy it to system/etc/init.d.
...to solve the original problem...
I fixed this on my device from a windows command prompt by typing "adb root" , which restarts the daemon on the device with root permissions.
Okay I've done enough research before deciding to make this post but couldn't find any solution.
Situation is I tried to install CF3D using CWM and now I'm stuck at the black boot screen that says GT N7000.
I tried to log into ADB shell and execute /system/lib/cf3d_uninstall.sh since that is the general solution but it seems I do not have the file there. Can someone give me the sh file if they have or tell me how to remove the drivers manualls through the ADB shell so that I can boot back normally. I did not backup before doing this..and I guess today isn't my day! Please help me remove the drivers! It's a little urgent.
I am new to the ADB shell concept and these are the commands I executed after connecting:
adb devices
adb shell
su
ls -d */
cd system
cd lib
sudo cf3d_uninstall.sh
Here it says that the file isn't found.
Edit: Nevermind.. Restoring back to CM9 for tonight...
Click to expand...
Click to collapse
tried these ?
sh system/lib
sh /cf3d_uninstall.sh
Should I just execute the contents of this shellscript via ADB? I found these on Google Code
Code:
#!/system/bin/sh
mount -o rw -o remount /dev/block/mtdblock4 /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
nokiamodeln91 said:
tried these ?
sh system/lib
sh /cf3d_uninstall.sh
Click to expand...
Click to collapse
Heya it says "Can't open 'cf3d_uninstall.sh' "
What Rom are you on?
nokiamodeln91 said:
What Rom are you on?
Click to expand...
Click to collapse
Ultimate N7000 XXLSC JellyBean 4.1.2 v5.1 ... And I really don't wanna reflash :/
Pl first try to locate where the cf3d files are and then run the command with right paths
[RESOLVED] CF3D Uninstall after boot loop
agvulcan said:
Okay I've done enough research before deciding to make this post but couldn't find any solution.
Situation is I tried to install CF3D using CWM and now I'm stuck at the black boot screen that says GT N7000.
I tried to log into ADB shell and execute /system/lib/cf3d_uninstall.sh since that is the general solution but it seems I do not have the file there. Can someone give me the sh file if they have or tell me how to remove the drivers manualls through the ADB shell so that I can boot back normally. I did not backup before doing this..and I guess today isn't my day! Please help me remove the drivers! It's a little urgent.
I am new to the ADB shell concept and these are the commands I executed after connecting:
adb devices
adb shell
su
ls -d */
cd system
cd lib
sudo cf3d_uninstall.sh
Here it says that the file isn't found.
Click to expand...
Click to collapse
Resolved (for me) :
I actually had the same error using the same command you did. You made a mistake though : when using an "sh" script, you have to invoke it's command, simply using "sh" before the name of the script you attempt to launch.
This is the way you have to go :
you should have typed : "sudo sh cf3d_uninstall.sh"
I actually managed to get it to work this way, and to stop boot loop / freeze (call it whatever you want), as it actually DID uninstall CF3D faulty drivers.
DO NOT USE CF3D with Jelly Bean, at the moment at least. Though Chainfire wrote he wouldn't develop anymore his drivers for JB, as it would need too much coding, again. Stick to GB or even ICS (it used to work for me)
--------
Full technique :
Prerequisites :
-CWM
-Aroma File Manager : Download it here :
Way to go :
-Take out your SD card from your device
-Copy Aroma FM to your Ext. SD Card using a microSD adapter (you can find one at any classical SD card retailer for a few bucks)
-Stick it back in your device
-Launch ClockWorkRecoveryMod
-"Install zip file"
-"Install from SD Card'
-Choose Aroma FM zip file, and install it.
-Tap on option key to get option menu, and launch the shell
-Then type :
su
cd system
cd lib
sh cf3d_uninstall.sh
Your device will automatically reboot, and boot your system normally.
See Ya
Chain Fire 3d boot loop .. not booting help plz ASAP
hello.. i am facing the same problem
i am using Panasonic T11, i had rooted it but it does not have any CWM,etc
when i installed Chain Fire 3d. it prompt me to reboot, bt it was boot looped, and i tried the ways u suggested
the problem its shows this errors in pic . plz suggest me something i can do about my phone
{
"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"
}
when i tried to go in recovery mode it shows ENTRY QPST DOWNLOAD
plz help me
Hi.
I have problem with my m7.
Can't use RUU (error 120), can't mount phone storge for paste rom.zip.
I using adb fastboot and command "adb fastboot sideload rom.zip" and "error: close"
I have installed recovery TWRP and unlock bl, try used THIS tutorial but i have error
C:\Users\Mati>cd /d c:\mini-sdk
c:\mini-SDK>adb push mkfs.ext4 /tmp
adb server is out of date. killing...
* daemon started successfully *
2669 KB/s (3537143 bytes in 1.294s)
c:\mini-SDK>adb shell
~ # ←[6nchmod 777 /tmp/mkfs.ext4
chmod 777 /tmp/mkfs.ext4
~ # ←[6n/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,
^extra_isize -m 0 /dev/block/mmcblk0p37
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext
ra_isize -m 0 /dev/block/mmcblk0p37
mke2fs 1.41.12 (17-May-2010)
/dev/block/mmcblk0p37 is mounted; will not make a filesystem here!
~ # ←[6nmount /data
mount /data
mount: mounting /dev/block/mmcblk0p37 on /data failed: Device or resource busy
~ # ←[6nmkdir -p /data/media/0
mkdir -p /data/media/0
mkdir: can't create directory '/data/media/': Read-only file system
~ # ←[6nexit
Click to expand...
Click to collapse
Any ideas?
Sorry for my english..
Thanks!
Sony156 said:
Hi.
I have problem with my m7.
Can't use RUU (error 120), can't mount phone storge for paste rom.zip.
I using adb fastboot and command "adb fastboot sideload rom.zip" and "error: close"
I have installed recovery TWRP and unlock bl, try used THIS tutorial but i have error
Any ideas?
Sorry for my english..
Thanks!
Click to expand...
Click to collapse
the command is adb sideload rom.zip
and the phone must be in TWRP / Advanced / Sideload / Swipe to sideload
The link you posted has nothing to do with sideloading a Rom
Thanks for reply.
I know, i have running sideload in TWRP.
But adb don't see my m7
{
"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"
}
C:\adb>adb sideload rom.zip
loading: 'rom.zip'
* failed to write data 'protocol fault (no status)' *
Click to expand...
Click to collapse
Sony156 said:
Thanks for reply.
I know, i have running sideload in TWRP.
But adb don't see my m7
Click to expand...
Click to collapse
update your adb and reinstall your pc drivers
I try different version adb and drivers for htc.
I too install fresh windows 7 on my imac and this same..
Using this: http://forum.xda-developers.com/showthread.php?t=2588979 and http://forum.xda-developers.com/showthread.php?t=2232799
Sony156 said:
I try different version adb and drivers for htc.
I too install fresh windows 7 on my imac and this same..
Using this: http://forum.xda-developers.com/showthread.php?t=2588979 and http://forum.xda-developers.com/showthread.php?t=2232799
Click to expand...
Click to collapse
Here use my ADB / Fastboot
does fastboot devices return the phones serial number in the bootloader ?
same with adb devices in TWRP ... you should see the phones serial number
i use this adb and my computer don't see htc in fastboot.
In recovery adb see phone
hboot 1.44
in bl is serial number, imei
Sony156 said:
i use this adb and my computer don't see htc in fastboot.
In recovery adb see phone
hboot 1.44
in bl is serial number, imei
Click to expand...
Click to collapse
adb doesn't work in the bootloader (fastboot does)
adb works in recovery and when the phone is booted up
in bootloader -> fastboot devices
Problem solved.
Phone had errors in the partition.
Thanks for all.