How to root Xperia V...
Information:
1: Unlocked Bootloader
- Bootloader Unlock Guide
2: Unsecure Kernel
- Xperia V - Stock Kernel Unsecure+Debuggable 9.0.D.0.484 (championswimmer)
- [URL="http://forum.xda-developers.com/showthread.php?t=2087413"][Kernel][V LT25i] Stock + TWRP 2.3 + Insecure + Debuggable [9.0.1.D.0.10] (spida_singh)[/URL]
Click to expand...
Click to collapse
For 9.0.D.0.484:
1a: Please use the unsecure kernel by spida_singh as it has TWRP
1b: Flash the unsecure kernel using fastboot [fastboot flash boot Xperia.V.TWRP.Kernel.9.0.1.D.0.10.elf]
2: Reboot into TWRP
3: Flash this - SU-Busybox-Installer.zip - gregbradly
Click to expand...
Click to collapse
For 9.0.D.0.484:
1: Flash the unsecure kernel using fastboot [fastboot flash boot lt25i-unsecure-debuggable.elf]
2: Push SU and Busybox using ADB
Click to expand...
Click to collapse
Credits:
- championswimmer for unsecure kernel 9.0.D.0.484
- spida_singh for unsecure kernel 9.0.1.D.0.10
- gregbradly for SU-Busybox-Installer.zip
Click to expand...
Click to collapse
For Locked Bootloader:
[HOW TO] Rooting the LT25i without unlocking the bootloader by Gasai Yuno
Click to expand...
Click to collapse
If I recall correctly, it doesn't work on locked boot loaders right?
Sent from my LT25i
Aaron_035 said:
If I recall correctly, it doesn't work on locked boot loaders right?
Sent from my LT25i
Click to expand...
Click to collapse
I am not sure but based on the rootkit, it does work on locked boot loaders. But since it was originally created for 2011 device, i'm not sure if it works for Xperia V with locked bootloader. You can always try and just restore your phone with pc companion if it doesnt work
My kernel is already rooted
You just installed su and busybox
The title is misleading
Sent from my Xperia S using xda app-developers app
championswimmer said:
My kernel is already rooted
You just installed su and busybox
The title is misleading
Sent from my Xperia S using xda app-developers app
Click to expand...
Click to collapse
I'll change. This still helps you to get su and busybox. The only reason why I put root is because i'm not sure if it would work for locked bootloaders.
-SlenderMan- said:
I'll change. This still helps you to get su and busybox. The only reason why I put root is because i'm not sure if it would work for locked bootloaders.
Click to expand...
Click to collapse
No it doesn't on the 484 and 10 versions
Sorry dude.
Aaron_035 said:
No it doesn't on the 484 and 10 versions
Sorry dude.
Click to expand...
Click to collapse
Hmm. So it only gets you SU and Busybox. Thanks anyway. Still worth something.
Sent from your backyard...
Slender watches what you do...
Hope somebody will find a way to root Xperia V without unlock bootloader.
I don't have this phone.
But if i were you i would try tricks with downgradge kernel from some Xperia 2012, root and reflash oryginal Xperia V kernel
This works on many (teoretically non rootable) Xperia phones with locked BL
Pacjonek said:
I don't have this phone.
But if i were you i would try tricks with downgradge kernel from some Xperia 2012, root and reflash oryginal Xperia V kernel
This works on many (teoretically non rootable) Xperia phones with locked BL
Click to expand...
Click to collapse
Only Xperia T (old) firmware can be rooted with Bin4ry, and I don't know if you can flash only the T stock kernel (ftf) on a Xperia V and then upgrade with flashtools to V kernel again? But I dont dare to try.
If somebody dares, it might work
You could also flash the firmware from au's Xperia VL; that's how I got root on my Xperia AX.
Haven't tried with the V yet though.
I got a BAD_POOL_HEADER. x_X Not nice that it came in the form of a BSOD.
I'm going to reinstall the ADB drivers and see if it'll be okay.
EDIT: Using the link to install Flashtools, I selected all Sony drivers and installed all of them. The error didn't appear after that.
Gasai Yuno said:
You could also flash the firmware from au's Xperia VL; that's how I got root on my Xperia AX.
Haven't tried with the V yet though.
Click to expand...
Click to collapse
Interesting! Since AX and V are the same but different internal memory size.
Maybe some DEVS can read this and help us? :fingers-crossed:
http://xperia-freaks.org/2012/11/20/ax-rooted/
They flash kernel.sin-, loader.sin and system.sin from VL, make root and then flash original firmware again...
(Its japanese but use goole translate or ask the member above).
Confirmed, you can obtain root by flashing the V to VL firmware, rooting that, and going back.
Instructions later.
Gasai Yuno said:
Confirmed, you can obtain root by flashing the V to VL firmware, rooting that, and going back.
Instructions later.
Click to expand...
Click to collapse
Want me to make a tutorial?
Sent from your backyard...
Slender watches what you do...
-SlenderMan- said:
Want me to make a tutorial?
Sent from your backyard...
Slender watches what you do...
Click to expand...
Click to collapse
I am not Gasai, but I would like to have tutorial. :good::fingers-crossed:
datagubben said:
I am not Gasai, but I would like to have tutorial. :good::fingers-crossed:
Click to expand...
Click to collapse
I can follow the instructions using Google Chrome as they can translate it but it will take time for me to re-arrange the sentences. Google somehow messed up the English after translating.
Rooting the Xperia V: How-To.
You will need: TRIMMED-LT25i-SOL21_9.0.F.0.195.ftf or the original LT25i-SOL21_9.0.F.0.195.ftf (this FTF has its loader.sin replaced with LT25i's loader.sin; the trimmed version lacks unneeded files like baseband etc. and as such removes unneeded wipe/exclude options, leaving only the three files we actually need) and an LT25i FTF of your choice; the rootkit (this one is "translated" and edited for convenience; do NOT use regular GX/SX rootkits blindly as they require modification).
1. Power the phone up in Flashmode (hold Volume down; connect USB). Using Flashtool, flash LT25i-SOL21_9.0.F.0.195.ftf with:
kernel.sin
loader.sin
system.sin
(Remember to uncheck the wipe options!)
2. Unplug USB. Turn the phone on. Enable USB debugging if it wasn't enabled previously. Connect the phone via USB again.
3. Unpack the Rootkit and start it (run install.bat). Confirm restore of the backup as requested, and press any key in the cmd window. Press any key again; the device will reboot (twice).
4. Run adb shell. To do it, you can open the rootkit folder in Windows Explorer, and shift-Right Click the "files" folder inside it. Choose "Open command window here". Type "adb shell" in that window.
If you're presented with a prompt that ends with "$", type "su".
The prompt should end with "#" now.
Type "echo ro.kernel.qemu=1 > /data/local.prop" and check if the file was created successfully by typing "ls -l /data/local.prop": below you will find an example of what the output looks like.
Code:
C:\Software\Rootkit\files\> adb shell
[email protected]:/ $ su
su
[email protected]:/ # echo ro.kernel.qemu=1 > /data/local.prop
echo ro.kernel.qemu=1 > /data/local.prop
[email protected]:/ # ls -l /data/local.prop
ls -l /data/local.prop
-rw-r--r-- system system 17 2013-01-15 17:29 local.prop
[email protected]:/ #
5. Turn the phone off, and connect it in Flashmode again. Using Flashtool, flash your firmware of choice with:
loader.sin
system.sin
(Remember to uncheck the wipe options!)
6. Turn the phone on. Open a command prompt into the files subfolder of the rootkit folder, like in step 4, or return to that window if you haven't closed it.
Type "adb shell". If you get a $ prompt, try "su" to get to "#". Once in adb, type "/data/local/tmp/step2.sh", then "reboot". The phone will reboot.
When it boots back, run adb shell again, and type "/data/local/tmp/step3.sh". You'll witness another reboot or maybe two. You should be rooted now.
Code:
C:\Software\Rootkit\files\> adb shell
[email protected]:/ # /data/local/tmp/step2.sh
/data/local/tmp/step2.sh
0+1 records in
0+1 records out
57 bytes transferred in 0.001 secs (57000 bytes/sec)
[email protected]:/ # reboot
C:\Software\Rootkit\files\> adb shell
[email protected]:/ # data/local/tmp/step3.sh
data/local/tmp/step3.sh
43+1 records in
43+1 records out
22364 bytes transferred in 0.002 secs (11182000 bytes/sec)
1647+1 records in
1647+1 records out
843503 bytes transferred in 0.123 secs (6857747 bytes/sec)
2119+1 records in
2119+1 records out
1085140 bytes transferred in 0.089 secs (12192584 bytes/sec)
7. Turn the phone off, and connect it in Flashmode again. Using Flashtool, flash your firmware of choice with:
kernel.sin
loader.sin
(Remember to uncheck the wipe options!)
Do NOT skip this step: you need the LT25i kernel on your LT25i system!
8. Let's finish.
We will need adb shell once again. This time, you will need to type a few lines as follows:
Obtain root:
su
Remount /system:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p12 /system
Remove /data/local.prop since it's a security hole; this is important and is normally done by the rootkit's step 3, but we needed to save the file to get to keep root access on our LT25i firmware:
rm /data/local.prop
And finally reboot:
reboot
Code:
G:\Android\LT25i\rootkitGXSX_v3\files>adb shell
[email protected]android:/ $ su
su
[email protected]:/ # mount -o remount,rw -t ext4 /dev/block/mmcblk0p12 /system
mount -o remount,rw -t ext4 /dev/block/mmcblk0p12 /system
[email protected]:/ # rm /data/local.prop
rm /data/local.prop
[email protected]:/ # reboot
reboot
Done. You now have busybox, Superuser and su on your stock LT25i firmware.
Remember to clean up those pesky au apps.
{
"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"
}
Thank you very much Gasai for nice tutorial. :good:
It works for me and I got root on locked bootloader, but sometimes I have reboot so maybe I did something wrong.
Please copy your post and make a thread in General section.
+1
Gasai make your own thread! Your post deserves a separate thread.
Sent from your backyard...
Slender watches what you do...
Related
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.
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!
Here is a nood friendly tutorial for fastboot flashing the new CWM Touch Recovery .
Download the zip file attached and extract it anywhere .
LE:\\ You need ENG S-OFF and a rooted phone , too.
Your phone needs to be in debugging mode and you need the lastest usb drivers instaled . ( HTC Sync )
FLASHING VIA FAST BOOT :
Step 1 : Run Start Here.bat , a comand promt window will open.
Step 2 : Type in "adb reboot bootloader" . <This works on every rom , it will reboot in fastboot mod.>
Step 3 : After the phone rebooted in fastboot , type in "fastboot flash recovery recovery-clockwork-touch-5.8.0.0-ace.img" .
Step 4 : You have your Touch Recovery flashed .
UPDATE TO LASTEST VERSION :
Step 5 : Download and install "ROM Manager" from Android Market.
Step 6 : Open ROM Manager , and select "Flash ClockworkMod Touch".
Step 7 : Confirm your phone model and in about 20 seconds a message should appear "Successfully flashed ClockworkMod Recovery!" press ok and you are done.
FLASH VIA BOOTLOADER (Without enghboot) : //Thx. nteeb
nteeb said:
For those who don't have enghboot.
The recovery is flashable from bootloader if you pack it in a PD98IMG.zip.
I tried it,this is the zip,use if you want:
PD98IMG.zip
md5: E19E4461F73AB6449760D70AE906341D
Click to expand...
Click to collapse
If you are unable to flash recovery do this and try again : //THX. CostaTX
CostaTX said:
Connect phone via usb and turn on debugging/just charging
Open up cmd (eventually as administrator) and type in "adb shell"
Find out how your system partition is named: "cat /proc/mounts | grep /system"
Mount system partition write/read. replace the X's "mount -o remount,rw -t yaffs2 /dev/block/XXXXX /system"
Use the terminal emulator to install the recovery:
su
flash_image recovery /sdcard/touch.img (or whatever the recovery image is named)
remount the system partition again as read only "mount -o remount,ro -t yaffs2 /dev/block/XXXXX /system
and you're done
Click to expand...
Click to collapse
Donate to ClockworkMod for awesome job .
A new version of recovery (5.8.1.5) is available here: http://www.clockworkmod.com/rommanager
You can also use Terminal Emulator: (I prefer to place the .img file in the root of the SD card and rename the image to something simple like touch.img so I don't have to type the long name from my phone)
su
flash_image recovery /sdcard/touch.img (or whatever the recovery image is named)
reboot recovery
Enjoy!
hello, this method does n't work for me, tried in fastboot with adb, same.... it's showing "remoot error" or something lik that
Do you have S-off? That error usually indicates you do not, and it is required for this method... Any luck using Terminal Emulator, as described two posts above?
Sent from my BNTV250 using Tapatalk
winsettr said:
You can also use Terminal Emulator: (I prefer to place the .img file in the root of the SD card and rename the image to something simple like touch.img so I don't have to type the long name from my phone)
su
flash_image recovery /sdcard/touch.img (or whatever the recovery image is named)
reboot recovery
Enjoy!
Click to expand...
Click to collapse
Hey dude. This method doesn't work for me.
I keep getting a message saying 'flash_image: not found'.
I have placed the image on the root of the sd card as well as in the original download folder. Neither location works.
{
"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"
}
Any ideas?
Greg.
Sent from my Desire HD using Tapatalk
Two thoughts: when you download the recovery image its actually named something like touch-recovery-ace-5.8.0.2.img; if you want to just type in touch.img in Terminal Emulator you need to rename the file that you downloaded. If you have already done this then you may not have busybox installed (CM and MIUI do, I don't know for sure about other ROMs). To test, from Terminal Emulator type "busybox"; if it's installed, you will get a list of available commands.
Sent from my BNTV250 using Tapatalk
works perfect, thx for the new recovery
winsettr said:
Two thoughts: when you download the recovery image its actually named something like touch-recovery-ace-5.8.0.2.img; if you want to just type in touch.img in Terminal Emulator you need to rename the file that you downloaded. If you have already done this then you may not have busybox installed (CM and MIUI do, I don't know for sure about other ROMs). To test, from Terminal Emulator type "busybox"; if it's installed, you will get a list of available commands.
Sent from my BNTV250 using Tapatalk
Click to expand...
Click to collapse
Hey dude.
I had indeed already renamed the file to touch.img.
I checked TE and I do seem to have busybox installed, I'm rocking RCMIX3D V4.
Curious.
Greg.
Sent from my Desire HD using Tapatalk
Also, I took the ***** way out and I bought the touch recovery, it's only £2.
Cheers,
Greg.
Sent from my Desire HD using Tapatalk
Supporting developers is never looked down upon, glad you are up and running!
Sent from my BNTV250 using Tapatalk
It did not work for me. i get these errors:
Code:
C:\Users\Jan>cd c:\touchrecovery
c:\TOUCHRECOVERY>fastboot flash recovery touch.img
sending 'recovery' (3554 KB)... OKAY [ 0.597s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.598s
c:\TOUCHRECOVERY>notepad
i ran cmd as admin but i still get the same error. when i try installing it via terminal emulator it also says "file not found". idea?
Do you have ENG S-off (different from just rooting)? That error usually indicates you do not, and it is required for the OP method... You might try updating Busybox (search Market for Busybox Installer) if you are sure when using Terminal Emulator that the path and filename are correct.
Sent from my BNTV250 using Tapatalk
I do have eng s-off . i was able to update the the recovery in the first place. i updated busybox and su-binaries as well but still got the same error. rebooted the phone just in case but still got the errors.
i can't say if it would have worked flashing via fastboot, now with the updated busybox. I'll give it a try when i'm back home. I believe it won't work neither. Maybe you got another idea?
edit: nothing changed using fastboot
So just to confirm, you only have this problem flashing the touch recovery, and can flash other versions of CWM just fine (using fastboot or terminal)?
Sent from my Desire HD using Tapatalk
Thanks for the guide, but I have a problem. When flashing the .img file, I get the following error:
sending 'recovery' (3554 KB)... OKAY [ 0.633s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.634s
I have S-OFF, but not ENG S-OFF. Is it possible to flash this without ENG S-OFF?
ROM Manager Premium says: "Error while downloading from server. Please make sure that you have a stable internet connection, and that your SD card is inserted and has free space!"
The internet connection and the SD card are of course all right...
Edit: I read that "Engineering HBOOT is required to flash the recovery area remotely." How can I flash the recovery on the phone (not remotely)?
winsettr said:
So just to confirm, you only have this problem flashing the touch recovery, and can flash other versions of CWM just fine (using fastboot or terminal)?
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
i've tested flashing a non-touch recovery right now but nothing changed. i noticed that flashing a recovery via rom manager works without any problem.
I read a while back that some users (from a G1 forum, so may not be as helpful, but it's an idea) had to mount the recovery partition r/w manually from fastboot. I'll see if I can find the link... http://www.droidforums.net/forum/dr...e-busybox-flash_image-more-app.html#post87383
That might fix your error while flashing from fastboot, but it seems the issue with terminal emulator is that it's not recognizing the flash_image command. The above link also has instructions for installing flash_image which may be the key!
I downloaded this file: recovery-clockwork-touch-5.8.1.5-ace.zip
Is it safe to install this zip (which is a recovery) in recovery?
winsettr said:
I read a while back that some users (from a G1 forum, so may not be as helpful, but it's an idea) had to mount the recovery partition r/w manually from fastboot. I'll see if I can find the link... http://www.droidforums.net/forum/dr...e-busybox-flash_image-more-app.html#post87383
That might fix your error while flashing from fastboot, but it seems the issue with terminal emulator is that it's not recognizing the flash_image command. The above link also has instructions for installing flash_image which may be the key!
Click to expand...
Click to collapse
here ist what i did with that link
Code:
C:\TOUCHRECOVERY>adb shell
# cat /proc/mounts |grep /system
cat /proc/mounts |grep /system
/dev/block/mmcblk0p25 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
# mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p25 /system
mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p25 /system
# cat /sdcard/touch.img > /system/bin/touch.img
cat /sdcard/touch.img > /system/bin/touch.img
# chmod 755 /system/bin/touch.img
chmod 755 /system/bin/touch.img
# sync
sync
# mount -o remount,r -t yaffs2 /dev/block/mmcblk0p25
mount -o remount,r -t yaffs2 /dev/block/mmcblk0p25
mount: mounting /dev/block/mmcblk0p25 on /system failed: Invalid argument
# mount -o remount,r -t yaffs2 /dev/block/mmcblk0p25 /system
mount -o remount,r -t yaffs2 /dev/block/mmcblk0p25 /system
mount: mounting /dev/block/mmcblk0p25 on /system failed: Invalid argument
busybox was already installed so i skipped this part and started with installing the recovery right away. I don't know why i'm not able to remount the system partition as read only at the end. It looks like as if everything seems to have worked properly but the touch recovery is not showing up.
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
Hello guys!!
I just had found a way to install the xposed framwork without have to root the device!
This is usefull if your devices is unrootable or if you don't want to root your device!
If it will not work for you, pm me and tell me what kind of device you had trying, the Android build version and finally the kernel version of the device.
How it work;
On some device (before the version 5.0 of Android{until I found another way to push this unthetered}) you can mount the system partition as read/write (WR) and add files or folder inside, but if you're Android device have a "locked bootloader", it's can make fails the process.
What your need ;
1. The Busybox binary compatible with your kind of devices (armv6, armv7...)
2. The Xposed apk installed on your devices
3. Android 4.0.1 to 4.4.4 (for the moment)
4. A computer
5. ADB installed
To begin, open your terminal (CMD on windows)
connect your device to you're computer with USB.
Type these commands;
adb wait-for-device
adb shell "cd /data/local && mkdir tmp"
adb shell "cd /data/local/tmp/ && rm *"
adb push /WHERE/IS/THE/BUSYBOX/FILE/busybox /data/local/tmp/
adb shell chmod 775 /data/local/tmp/busybox
adb shell /data/local/tmp/busybox mount -o remount,rw /system
adb shell /data/local/tmp/busybox cp -a /system/bin/app_process /system/bin/app_process.orig
adb shell /data/local/tmp/busybox cp /data/data/de.robv.android.xposed.installer/bin/app_process /system/bin/app_process
adb shell /data/local/tmp/busybox chown 0:2000 /system/bin/app_process
adb shell /data/local/tmp/busybox chmod 0755 /system/bin/app_process
adb shell reboot system
For the moment this is only compatible with androis 4.0.1 to 4.4.4.... I work for above version!
Tested and work on:
SAMSUNG Galaxy Exibith 4g Stock Rom 4.1.2
SAMSUNG Galaxy Exibith 4g custom unrooted Rom Slim 4.1.2
Sony Xperia ion Lt28h stock rom 4.4.2
Sony Xperia Arc stock rom 4.2.2
Htc desire 601 stock ROM 4.4.4
(Edit: At this moment I had found a way to install xposed framework to 5.0->6.1.1 but if your reboot you lost all and on some device (like my Samsung S6 Edge+) you stuck on a bootloop or (like my S7 edge (on 6.1)) you get a soft break.. I take my freetime to find this, but with my school that going start soon, I will be not very free to find exploit... 23/8/2017:10h32AM)
#I'm not responsable for any brick or anything in your life or anyone else! !#
Credits To:
Erik Andersen (For The busybox binary)
Rovo89 (for xposed)
Proof Of Concept
{
"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"
}
IF YOU WANT SHARE MY WORK, ADD A MY USERNAME AND/OR THE LINK TO THIS FORUM AND/OR THE LINK OF MY PROFIL XDA AND/OR ALL OF UPPER
AND PLS TELL ME IF YOU WANT TO DO!
Does busybox function without root? I didn't think so.
When it push on thé sandbox (/data/local/tmp) and make like executable, it work. The fonction "mount -o remount,rw /system" put the system partition in read/write mode... My brother wanted Xposed for some tweak but hhe hate root (i dont know why) and hé uses Xposed freely like me with all of m'y rooted device...
This is sure not all fonction of busybox work fine but its do the job.
ldeveraux said:
Does busybox function without root? I didn't think so.
Click to expand...
Click to collapse
When it push on thé sandbox (/data/local/tmp) and make like executable, it work. The fonction "mount -o remount,rw /system" put the system partition in read/write mode... My brother wanted Xposed for some tweak but hhe hate root (i dont know why) and hé uses Xposed freely like me with all of m'y rooted device...
This is sure not all fonction of busybox work fine but its do the job.
Does anybody tried this?
neosinan said:
Does anybody tried this?
Click to expand...
Click to collapse
Having busybox installed doesn't allow mounting of the system partition(unless someone messed up and didn't mount the system as read only, or the system unknowingly grants the user superuser permissions), it's read-only, which requires su to enable mounting as read-write.
Just try it but the commande adb shell /data/local/tmp/busybox mount -o remount,rw /system return "mount: mounting /dev/block/dm-0 on /system failed: Permission denied"
i got the same error..can anyone help me!?
when i gave the command adb shell /data/local/tmp/busybox mount -o remount,rw /system
and errror displayed was :- mounting /dev/block/dm-0 on /system failed: Permission denied
Will this work on 5.0?
nfs2014 said:
Will this work on 5.0?
Click to expand...
Click to collapse
On Android 5+ you've to flash framework zip via twrp and then install the xposed installer app.
sachin n said:
On Android 5+ you've to flash framework zip via twrp and then install the xposed installer app.
Click to expand...
Click to collapse
okay thanks but i am not able to root my phone...
nfs2014 said:
okay thanks but i am not able to root my phone...
Click to expand...
Click to collapse
Which phone?
sachin n said:
On Android 5+ you've to flash framework zip via twrp and then install the xposed installer app.
Click to expand...
Click to collapse
sachin n said:
Which phone?
Click to expand...
Click to collapse
Intex aqua power hd 4g. I tried one click root methods like kingo and farmaroot but no success. And also xda fourm about this phone is blank. If u know any other method to root then plzz tell...
Work on 7.1
sim disco said:
Work on 7.1
Click to expand...
Click to collapse
No, there's no xposed for Nougat ATM.
Do you know if this would work on samsung note 5 sm-n920v
I am trying to install it on Xperia ray ST19i ICS 4.0.4 stock rom rooted plus busyboxed but no external sdcard(Xperia has no internal sd)....anyway to install xposed without external sd? I tried above method but there was no "app_process" inside /data/data/de.robv.android.xposed.installer/bin/????
Could u please upload that file? Thanks
Btw is the md5 hash for app_process inside /data/data/de.robv.android.xposed.installer/bin/ is F031F72B9649EF431272672CA692F7A3 ?
Thanks
regi54 said:
Just try it but the commande adb shell /data/local/tmp/busybox mount -o remount,rw /system return "mount: mounting /dev/block/dm-0 on /system failed: Permission denied"
Click to expand...
Click to collapse
What is you Android build version?
Maxemus_04 said:
Do you know if this would work on samsung note 5 sm-n920v
Click to expand...
Click to collapse
I don't know... if you can try it will be nice, cause I dont have this device...
Need Help
i have device with adb root permission so i dont have any need to install busybox because i can remount copy remove files from system using adb
so i want to know that only app process is need to be replaced with xposed app process or any other file is also needed to be replaced
as framework is also there so i need help please help me
i am on kitkat 4.4.3