Related
Can someone please type the following line inside the Terminal Emulator or an ADB Shell and post the results.
Code:
ls -l /system/bin/mount-
After rooting my A100 for the second time (after an ICS Over The Air Update) the backup created by the next line, which is part of the getroot.sh script got over-written
Code:
mv /system/bin/mount /system/bin/mount-
Right now this is what I am getting (If I type: ls -l /system/bin/mount-):
Code:
lrwxrwxrwx root root 2012-06-30 18:43 mount- -> /system/sbin/mount
I just want to check if the original mount command was a symlink to the Toolbox multi-function program, like many commands inside the /system/bin/ directory.
The Build number is: Acer_AV041_A100_1.037.00_WW_GEN1
Thanks.
PS: I did not post in the corresponding thread (http://forum.xda-developers.com/showthread.php?t=1531646) because I don't have the required 10 posts, sorry about that.
If you did not root your A100 using the method described in: http://forum.xda-developers.com/showthread.php?t=1531646 you will get:
Code:
/system/bin/mount-: No such file or directory
But I could also use the output of:
Code:
ls -l /system/bin/mount
I tried it with my other Android devices and I get different outputs.
In my Motorola Atrix 4G I get:
Code:
lrwxrwxrwx root root 2012-06-24 18:39 mount -> /data/local/toolbox
And in my LG-P500h I get:
Code:
lrwxr-xr-x root root 2010-06-30 21:04 mount -> toolbox
They both are symlinks to the Toolbox multi-function program in the Android system, but in the Atrix 4G I have two different Toolbox files, one in the /data/local/ directory and one in /system/bin/ directory.
Thanks again for any help.
There's a lot of fine-tuning you can do by modifying init.rc that is packed into uRamdisk in the boot partition.
In the Unix world to modify init.rc inside uRamdisk you would need to:
Use dd to strip the image header
Use gzip to expand the contents
Use cpio to separate it into files
Edit what you want in init.rc
Use cpio to combine the files
Use gzip to compress the contents
Use mkimage to wrap the contents
In the Windows world a command line utility simplifies this:
Code:
bootutil /v /x uRamdisk init.rc
Edit init.rc
Code:
bootutil /v /r uRamdisk init.rc
As always, be careful and make a backup.
Making a Clockwork Recovery update to restore the original uRamdisk might be a good idea.
Download bootutil.exe in the signature.
Renate NST said:
There's a lot of fine-tuning you can do by modifying init.rc that is packed into uRamdisk in the boot partition.
In the Unix world to modify init.rc inside uRamdisk you would need to:
Use dd to strip the image header
Use gzip to expand the contents
Use cpio to separate it into files
Edit what you want in init.rc
Use cpio to combine the files
Use gzip to compress the contents
Use mkimage to wrap the contents
In the Windows world a command line utility simplifies this:
Code:
bootutil /v /x uRamdisk init.rc
Edit init.rc
Code:
bootutil /v /r uRamdisk init.rc
As always, be careful and make a backup.
Making a Clockwork Recovery update to restore the original uRamdisk might be a good idea.
Download bootutil.exe in the signature.
Click to expand...
Click to collapse
Cool!
Now we will see real hard core modding! :highfive:
I've added delete to the operations of bootutil:
Code:
usage: bootutil image file [...]
/d delete files
/l list files
/r replace files
/x extract files
/v verbose
Here's some ideas of what you can do with bootutil.
Install adbd in /system/bin and chmod 755 it.
Delete both sbin and sbin/adbd from uRamdisk.
Change the start of adbd in init.rc from /sbin/adbd to /system/bin/adbd
Trim the cruft from PATH in init.rc and make it only /system/bin
Delete the whole secton in init.rc for the /data/media/B&N Downloads
Add a mount point for USB drives right before the root gets ro in init.rc
Delete all that stuff for /sys/devices/platform/omapdss
Where/when/what did that ever exist?
Renate, Thank you very much for your tool. I've been looking for a way to change mount point from /sdcard to /mnt/sdcard for a long time. With bootutil it's much easier.
How I did it:
1. Flash noogie.img to sdcard.
2. Boot from sdcard and connect NST to PC.
3. In partition manager assign letter to boot partition.(ex. MiniTool Partition Wizard)
4. Update mount points in init.rc at E:\uRamdisk with bootutil.(Don't forget to mkdir your mount points)
5. Remove letter from boot partition with partition manager.
6. Reboot NST.
7. Update mount points /system/etc/vold.conf
I've added more stuff and more flags to bootutil.exe
It won't make a lot of difference for modifying just init.rc,
but it will allow you to make your own ramdisks and insert files and symlinks.
Code:
usage: bootutil [flags] image file [file...]
/d delete files
/g group id
/i insert before
/l list files
/m file mode
/n new archive (name)
/r replace files
/s symlink (path)
/x extract files
/u user id
/v verbose
[b]# create 3 symlinks to busybox[/b]
bootutil /v uRamdisk /i /sbusybox date ls ps
[b]# insert adbd before stuff with chmod 755[/b]
bootutil /v uRamdisk /istuff system/bin/adbd /m755
Error Messages
Many thanks for bootutil! I'm trying to modify the init in uRamdisk and am getting the following errors messages:
GZip signature not found OR
Image signature not found.
Any suggestions?
Thanks!
dnordquest said:
Any suggestions?
Click to expand...
Click to collapse
Are you sure that what you have is a uRamdisk?
Try this:
Code:
C:\>bootutil /l /v uRamdisk
Read image, 11 files
drwxrwx--x data
-rw-r--r-- 89 2013-02-08 08:54 default.prop
drwxr-xr-x dev
-rw-r--r-- 324 env.txt
-rwxr-x--- 107344 2012-02-03 09:13 init
-rwxr-x--- 1677 init.goldfish.rc
-rwxr-x--- 19131 2013-02-08 08:54 init.rc
-rwxr-x--- 40205 initlogo.rle
drwxr-xr-x proc
drwxr-xr-x sys
drwxr-xr-x system
Then try:
Code:
C:\>bootutil /x /v uRamdisk init
"Are you sure that what you have is a uRamdisk?"
When I try bootutil.exe on the uRamdisk from my boot directory, I get "Gzip signature not found."
When I try it on the uRamdisk from the binaries.zip file you linked to as a source for a good init, I get what you say I should get. The uRamdisk from my 1.2.1 updated, rooted NST is 182K. The uRamdisk that works is 168k. Should I look for another?
Thanks.
I do have version 1.1, 1.1.2, 1.1.5, 1.2, 1.2.1 of the uRamdisk and they all work fine with bootutil.
Maybe whoever did your rooted uRamdisk did a sloppy job?
Get that file to me and I'll take a look.
Code:
E:\>bootutil /v /l E:\Nook11\ramdisk.img
Read image, 13 files
drwxrwx--x data
-rw-r--r-- 118 default.prop
drwxr-xr-x dev
-rw-r--r-- 324 env.txt
-rwxr-x--- 127964 init
-rwxr-x--- 1677 init.goldfish.rc
-rwxr-x--- 18728 init.rc
-rwxr-x--- 40205 initlogo.rle
drwxr-xr-x proc
drwxr-x--- sbin
-rwxr-x--- 134136 sbin/adbd
drwxr-xr-x sys
drwxr-xr-x system
E:\>bootutil /v /l E:\Nook112\ramdisk.img
Read image, 13 files
drwxrwx--x data
-rw-r--r-- 118 default.prop
drwxr-xr-x dev
-rw-r--r-- 324 env.txt
-rwxr-x--- 127964 init
-rwxr-x--- 1677 init.goldfish.rc
-rwxr-x--- 18728 init.rc
-rwxr-x--- 40205 initlogo.rle
drwxr-xr-x proc
drwxr-x--- sbin
-rwxr-x--- 134136 sbin/adbd
drwxr-xr-x sys
drwxr-xr-x system
E:\>bootutil /v /l E:\Nook115\ramdisk.img
Read image, 13 files
drwxrwx--x data
-rw-r--r-- 118 default.prop
drwxr-xr-x dev
-rw-r--r-- 324 env.txt
-rwxr-x--- 127964 init
-rwxr-x--- 1677 init.goldfish.rc
-rwxr-x--- 19067 init.rc
-rwxr-x--- 40205 initlogo.rle
drwxr-xr-x proc
drwxr-x--- sbin
-rwxr-x--- 134136 sbin/adbd
drwxr-xr-x sys
drwxr-xr-x system
E:\>bootutil /v /l E:\Nook12\ramdisk.img
Read image, 13 files
drwxrwx--x data
-rw-r--r-- 118 default.prop
drwxr-xr-x dev
-rw-r--r-- 324 env.txt
-rwxr-x--- 128000 init
-rwxr-x--- 1677 init.goldfish.rc
-rwxr-x--- 19259 init.rc
-rwxr-x--- 40205 initlogo.rle
drwxr-xr-x proc
drwxr-x--- sbin
-rwxr-x--- 134136 sbin/adbd
drwxr-xr-x sys
drwxr-xr-x system
E:\>bootutil /v /l E:\Nook121\ramdisk.img
Read image, 13 files
drwxrwx--x data
-rw-r--r-- 118 default.prop
drwxr-xr-x dev
-rw-r--r-- 324 env.txt
-rwxr-x--- 128000 init
-rwxr-x--- 1677 init.goldfish.rc
-rwxr-x--- 19259 init.rc
-rwxr-x--- 40205 initlogo.rle
drwxr-xr-x proc
drwxr-x--- sbin
-rwxr-x--- 134136 sbin/adbd
drwxr-xr-x sys
drwxr-xr-x system
So, mystery solved.
My bootutil.exe never addressed the possibility of name or comment fields on the internal GZip.
It does now, download in the signature.
See also: http://forum.xda-developers.com/showpost.php?p=38695314&postcount=137
Used new bootutil to replace init in uRamdisk and keyboard now working fine! On to audio!
Many thanks!
Dear Renate NST,
I used bootutil to modify uRamdisk , but i got "Image data CRC error".
batchaesir said:
i got "Image data CRC error".
Click to expand...
Click to collapse
The problem is that the CRC for the image data is wrong.
I don't know what tool made this file, but it's wrong.
The problem is that the "guts" of the file are 1/4 Meg but it's padded out to 1 Meg with zeroes.
Take your file and truncate it to 0x3d339 (250,681) in length.
There's a new bootutil.exe in the signature with less ambiguous error reporting.
Code:
C:\>bootutil /l ramdisk.uimg
Image data size error
C:\>modfile /t ramdisk.uimg 3d339
C:\>bootutil /l ramdisk.uimg
drwxrwx--x data
-rw-r--r-- 118 default.prop
...
Renate NST ,
Thanks so much. I used dd command. Problem is solved.
imgutil usage
Renate NST said:
There's a lot of fine-tuning you can do by modifying init.rc that is packed into uRamdisk in the boot partition.
In the Unix world to modify init.rc inside uRamdisk you would need to:
Use dd to strip the image header
Use gzip to expand the contents
Use cpio to separate it into files
Edit what you want in init.rc
Use cpio to combine the files
Use gzip to compress the contents
Use mkimage to wrap the contents
In the Windows world a command line utility simplifies this:
Code:
bootutil /v /x uRamdisk init.rc
Edit init.rc
Code:
bootutil /v /r uRamdisk init.rc
As always, be careful and make a backup.
Making a Clockwork Recovery update to restore the original uRamdisk might be a good idea.
Download bootutil.exe in the signature.
Click to expand...
Click to collapse
Hi Renate,
I was just wondering about the usage of imgutil commands.
In the command Usage: imgutil [flags] image [file...], I would like to modify init.rc on uRamdisk. Do I simply type uRamdisk like above? Or is there a path I need to specify?
On my system under /proc/partitions I have:
179 16 1024 mmcblk0boot1
179 8 1024 mmcblk0boot0
and under /proc/mtd I have nothing
Will this be a problem?
Cheers,
Stephan
First: As general information, this is now called imgutil, uses (mostly?) the same arguments and is available in the signature below.
It has had improvements to make it more robust and it can deal with images with garbage on the end.
It also supports DTB, the device tree blob used on some newer devices.
I use this on many non-B&N devices, including Marshmallow.
@stephangm
You first have to get the raw image.
Depending on your device, it might be a file in a partition or a raw partition.
A file always has an explicit size, a partition has an explicit size too, but it's usually bigger than the actual image.
For instance, the NST uses a uRamdisk file inside the FAT partiton mmcblk0p1
The Glow Plus uses a combined kernel/ramdisk that's in the raw (emmc) partition mmcblk0p1
To get this, you might do something like:
Code:
C:\> adb shell
# cat /dev/block/mmcblk0p1 > /sdcard/p1.img
# ^D
C:\> adb pull /sdcard/p1.img
C:\> dir p1.img
--- 12 Megs or something
C:\> imgutil /v /x p1.img init.rc
C:\> myeditor init.rc
C:\> imgutil /v /r p1.img init.rc
C:\> dir p1.img
--- 7 Megs or something
C:\> adb push p1.img /sdcard
C:\> adb shell
# cat /sdcard/p1.img > /dev/block/mmcblk0p1
Note that when you first copy the file it will be the full size of the partition, that is, the image plus useless stuff at the end.
Once imgutil has modified it, it will be truncated to the useful size.
As far as figuring out which partition the boot one is, there are multiple ways, including fdisk, /proc, by-name or in the sysfs uevent.
When i tried to use this command with imgutil (the new name for bootutil from Renate NST) on NST
"imgutil /l /v uRamdisk"
i received this message : Could not open uRamdisk ???
Secondly, copying this row of code :
"adb shell
# cat /dev/block/mmcblk0p1 > /sdcard/p1.img"
i get this answer:
"cannot create /sdcard/p1.img, read-only file system"
Why these commands don't work as intended ???
gsms said:
I received this message : Could not open uRamdisk ???
Click to expand...
Click to collapse
Probably because the file does not exist.
gsms said:
Secondly, copying this row of code :
"adb shell
# cat /dev/block/mmcblk0p1 > /sdcard/p1.img"
i get this answer:
"cannot create /sdcard/p1.img, read-only file system"
Click to expand...
Click to collapse
Those instruction were for the Glow Plus.
Since you haven't even copied over the uRamdisk from the NST, it makes the first part above even less sensible.
The NST has the uRamdisk as a file on the vfat on mmcblk0p1
There's a new version of imgutil.exe available in the signature.
The changes include the addition of the /a (append) flag and different behavior for the /i (insert) flag.
It no longer is necessary (or legal) to supply an argument to the /i flag.
/a puts all the files at the end of the archive in the order that they appear on the command line.
Code:
imgutil /a /v boot.img bats zebras cats
At the end of the archive would be bats, zebras, cats.
Code:
imgutil /i /v boot.img bats zebras cats
The three files would be inserted at the sorted position.
From a previous update, the /c flag allows you to change the command line that is fed to the kernel.
Hello,
After flashing the most recent TuchMi ROM on my galaxy s3, trying it out and restoring to my nandroid backup of kyanrom I have a TuchMi folder I cannot delete. I have tried ES Fileexplorer and Root Explorer both. There are three zip files in the TuchMi folder that cannot be deleted, tells me file permissions cannot be changed.
That said, the timestamp on the /TuchMi folder is 8 March 1970. I am wondering if this is causing something to fail in deleting or being able to change permissions. I don't know if this is right place to ask this question but I can't ask in the TuchMi thread because I am too new. Anyone have an idea on what I can do to fix this?
Thanks
JMD
rezin44 said:
Hello,
After flashing the most recent TuchMi ROM on my galaxy s3, trying it out and restoring to my nandroid backup of kyanrom I have a TuchMi folder I cannot delete. I have tried ES Fileexplorer and Root Explorer both. There are three zip files in the TuchMi folder that cannot be deleted, tells me file permissions cannot be changed.
That said, the timestamp on the /TuchMi folder is 8 March 1970. I am wondering if this is causing something to fail in deleting or being able to change permissions. I don't know if this is right place to ask this question but I can't ask in the TuchMi thread because I am too new. Anyone have an idea on what I can do to fix this?
Thanks
JMD
Click to expand...
Click to collapse
Run "fix permissions" from recovery, and then try again.
(One of the most common reasons you can't delete something, even as root, is that its file attributes are set to "immutable" (which under linux often means you've been hacked, but no worries here))
Thanks for the quick reply but that didn't seem to fix it. I am at a loss, the folder is only 32meg so I am not too concerned but it is a little annoying. If there's another thing you can think of I'd appreciate it.
Sent from my SGH-I747M using Tapatalk 2
rezin44 said:
Thanks for the quick reply but that didn't seem to fix it. I am at a loss, the folder is only 32meg so I am not too concerned but it is a little annoying. If there's another thing you can think of I'd appreciate it.
Sent from my SGH-I747M using Tapatalk 2
Click to expand...
Click to collapse
Nuke it (rm -rf somedir) from an adb shell, so you can see the actual error.
zmore said:
Nuke it (rm -rf somedir) from an adb shell, so you can see the actual error.
Click to expand...
Click to collapse
Here's what it says.
Code:
[email protected]:/ $ cd sdcard
cd sdcard
[email protected]:/sdcard $ ls
ls
Alarms
Albums
Android
Application
DCIM
Download
EVA
Evernote
GOLauncherEX
GoStore
Library
Movies
Music
Notifications
Pictures
PlayerPro
Podcasts
Ringtones
SpeedSoftware
TuchMi
ba-superkeyboard
backups
data
ivona
mdm
media
rootz
svox
temp
[email protected]:/sdcard $ rm -rf TuchMi
rm -rf TuchMi
rm failed for -rf, No such file or directory
255|[email protected]:/sdcard $ rm TuchMi
rm TuchMi
rm failed for TuchMi, Is a directory
255|[email protected]:/sdcard $ cd TuchMi
cd TuchMi
[email protected]:/sdcard/TuchMi $ ls
ls
Stock_SystemUI.zip
Voice_Reinstall.zip
XXBLG1_AndroidGX-MOD_NexusBattery.zip
[email protected]:/sdcard/TuchMi $ rm Stock_SystemUI.zip
rm Stock_SystemUI.zip
rm failed for Stock_SystemUI.zip, Permission denied
255|[email protected]:/sdcard/TuchMi $ ls -l
ls -l
-rw-rw-r-- root sdcard_rw 1280043 2008-08-01 07:00 Stock_SystemUI.zip
-rw-rw-r-- root sdcard_rw 29694315 2008-08-01 07:00 Voice_Reinstall.zip
-rw-rw-r-- root sdcard_rw 2582686 2008-08-01 07:00 XXBLG1_AndroidGX-MOD_Nex
usBattery.zip
[email protected]:/sdcard/TuchMi $
and these are the permissions of the subject directory.
drwxrwxr-x root sdcard_rw 1970-03-08 01:48 TuchMi
Thank you for taking the time to respond to this.
JMD
I had to delete it while plugged into my pc. Was just driving me crazy that I couldn't get rid of it.
Well, I've resigned myself to failure deleting these three files and the folder they're in. I've tried 8 or 9 different file managers. I downloaded and installed adb, learned enough to really screw up my phone, but that didn't work either. I tried deleting them through windows and debian too.
That said, I'm just going to live with things as they are now. In the future when a more mature JB rom comes out I'll try that but my question is this, can I just format (wipe) my sdcard partition and restore the stock at&t/Samsung rom using Odin?
Sent from my SGH-I747M using Tapatalk 2
rezin44 said:
Well, I've resigned myself to failure deleting these three files and the folder they're in. I've tried 8 or 9 different file managers. I downloaded and installed adb, learned enough to really screw up my phone, but that didn't work either. I tried deleting them through windows and debian too.
That said, I'm just going to live with things as they are now. In the future when a more mature JB rom comes out I'll try that but my question is this, can I just format (wipe) my sdcard partition and restore the stock at&t/Samsung rom using Odin?
Sent from my SGH-I747M using Tapatalk 2
Click to expand...
Click to collapse
I noticed in your terminal output, that you weren't root (# vs $). "su" to root, and try again.
zmore said:
I noticed in your terminal output, that you weren't root (# vs $). "su" to root, and try again.
Click to expand...
Click to collapse
Yeah, I caught that before you mentioned it yesterday but I thought I'd try it again as this is very new to me and I am using cheat sheets with adb common commands to navigate through this. Here is the output though. Still no bueno..
Code:
drwxrwxr-x root sdcard_rw 1970-03-08 01:48 TuchMi
drwxrwxr-x root sdcard_rw 2012-09-04 08:05 ba-superkeyboard
drwxrwxr-x root sdcard_rw 2012-09-04 09:45 backups
drwxrwxr-x root sdcard_rw 2012-09-05 02:05 clockworkmod
drwxrwxr-x root sdcard_rw 2012-09-03 20:09 data
drwxrwxr-x root sdcard_rw 2012-09-04 14:24 ivona
drwxrwxr-x root sdcard_rw 2012-08-31 09:00 mdm
drwxrwxr-x root sdcard_rw 2012-08-14 17:39 media
drwxrwxr-x root sdcard_rw 2012-09-03 21:31 rootz
drwxrwxr-x root sdcard_rw 2012-09-04 23:14 temp
[email protected]:/sdcard # rm -rf TuchMi
rm -rf TuchMi
rm failed for -rf, No such file or directory
255|[email protected]:/sdcard # cd TuchMi
cd TuchMi
[email protected]:/sdcard/TuchMi # ls -l
ls -l
-rw-rw-r-- root sdcard_rw 1280043 2008-08-01 07:00 Stock_SystemUI.zip
-rw-rw-r-- root sdcard_rw 29694315 2008-08-01 07:00 Voice_Reinstall.zip
-rw-rw-r-- root sdcard_rw 2582686 2008-08-01 07:00 XXBLG1_AndroidGX-MOD_Nex
usBattery.zip
[email protected]:/sdcard/TuchMi # rm Stock_SystemUI.zip
rm Stock_SystemUI.zip
rm failed for Stock_SystemUI.zip, Permission denied
255|[email protected]:/sdcard/TuchMi # rm Stock_SystemUI.zip
rezin44 said:
Yeah, I caught that before you mentioned it yesterday but I thought I'd try it again as this is very new to me and I am using cheat sheets with adb common commands to navigate through this. Here is the output though. Still no bueno..
Code:
...snip...
[email protected]:/sdcard/TuchMi # ls -l
ls -l
-rw-rw-r-- root sdcard_rw 1280043 2008-08-01 07:00 Stock_SystemUI.zip
-rw-rw-r-- root sdcard_rw 29694315 2008-08-01 07:00 Voice_Reinstall.zip
-rw-rw-r-- root sdcard_rw 2582686 2008-08-01 07:00 XXBLG1_AndroidGX-MOD_Nex
usBattery.zip
[email protected]:/sdcard/TuchMi # rm Stock_SystemUI.zip
rm Stock_SystemUI.zip
rm failed for Stock_SystemUI.zip, Permission denied
255|[email protected]:/sdcard/TuchMi # rm Stock_SystemUI.zip
Click to expand...
Click to collapse
Weird. As root, you normally only see that for immutable files, so, try:
lsattr foo.zip
and if you see an "i" flag for immutable, do a:
chattr -i file.zip
zmore said:
Weird. As root, you normally only see that for immutable files, so, try:
lsattr foo.zip
and if you see an "i" flag for immutable, do a:
chattr -i file.zip
Click to expand...
Click to collapse
Code:
D:\android-sdk\platform-tools>adb devices
List of devices attached
b41c0497 device
D:\android-sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # cd sdcard/TuchMi
cd sdcard/TuchMi
[email protected]:/sdcard/TuchMi # ls -l
ls -l
-rw-rw-r-- root sdcard_rw 1280043 2008-08-01 07:00 Stock_SystemUI.zip
-rw-rw-r-- root sdcard_rw 29694315 2008-08-01 07:00 Voice_Reinstall.zip
-rw-rw-r-- root sdcard_rw 2582686 2008-08-01 07:00 XXBLG1_AndroidGX-MOD_Ne
usBattery.zip
[email protected]d:/sdcard/TuchMi # lsattr Stock_SystemUI.zip
lsattr Stock_SystemUI.zip
lsattr: reading Stock_SystemUI.zip: Function not implemented
[email protected]:/sdcard/TuchMi # lsattr Voice_Reinstall.zip
lsattr Voice_Reinstall.zip
lsattr: reading Voice_Reinstall.zip: Function not implemented
[email protected]:/sdcard/TuchMi #
It kicked out those "Function not implemented" errors, I did some searching and some of the sites that popped up were fedora and ubuntu and they hinted at maybe I have the wrong file system for lsattr to work? In windows it shows the file system on both sdcards, int and ext, as 'generic hierarchical'.
I have had this issue with a couple of folder where I could NOT delete them on my i777 no matter what/how I tried. The files/folders I had were some that I extracted. Then when I was done with it I couldn't delete it. After I had two folders I couldn't delete as it too was bugging me was I connected up my phone via ums to my PC and transfered everything I wanted/needed from my sdcard (internal unremovable). Then when I had it all backed up I went into recovery and formatted my internal sdcard (I removed my external sdcard first to be safe). Then I booted up phone and saw it was all clean. Then I reconnected to PC and transferred all my needed files/folders back onto phone.
I THINK what happened was somehow it was a corrupted file and caused my issues. Completely wiping my sdcard fixed it though. Good luck to you.
Sent from My SGH-I777 Running Red Reaper Rom
RockRatt said:
I have had this issue with a couple of folder where I could NOT delete them on my i777 no matter what/how I tried. The files/folders I had were some that I extracted. Then when I was done with it I couldn't delete it. After I had two folders I couldn't delete as it too was bugging me was I connected up my phone via ums to my PC and transfered everything I wanted/needed from my sdcard (internal unremovable). Then when I had it all backed up I went into recovery and formatted my internal sdcard (I removed my external sdcard first to be safe). Then I booted up phone and saw it was all clean. Then I reconnected to PC and transferred all my needed files/folders back onto phone.
I THINK what happened was somehow it was a corrupted file and caused my issues. Completely wiping my sdcard fixed it though. Good luck to you.
Sent from My SGH-I777 Running Red Reaper Rom
Click to expand...
Click to collapse
Thanks, Im gonna give this a try
Well, it's beat me. After trying all the above things I still cannot delete the TuchMi folder. I tried formatting the sdcard partition from windows, CWM, and fedora. All three did format and manage to wipe everything from that partition except the TuchMi folder.
All I can say is be wary of that ROM.
Sent from my SGH-I747M using Tapatalk 2
Hi! I've been all day trying to install a recovery on my Xperia S, but to no result. At least, I'm always able to flash the stock kernel back.
I've tried a lot of methods (DoomLord's modified kernel, TWRP, RecoverX,...), but in the end, the result is the same. The installers/flashers report an OK, i boot the phone and start tapping the screen on the Sony logo. In some cases it ignores me and goes on to the Xperia logo (a normal boot), or in other cases the Sony logo disappears and all I get is a black screen.
Can anybody help me?
If you are root ;
http://forum.xda-developers.com/showthread.php?t=2634382
Xavali7 said:
Hi! I've been all day trying to install a recovery on my Xperia S, but to no result. At least, I'm always able to flash the stock kernel back.
I've tried a lot of methods (DoomLord's modified kernel, TWRP, RecoverX,...), but in the end, the result is the same. The installers/flashers report an OK, i boot the phone and start tapping the screen on the Sony logo. In some cases it ignores me and goes on to the Xperia logo (a normal boot), or in other cases the Sony logo disappears and all I get is a black screen.
Can anybody help me?
Click to expand...
Click to collapse
On most custom kernels, you need to keep on pressing the volume buttons when you see the Sony logo (or doom kernel logo) instead of tapping on the logo. For doom kernel -
Volume up - Cwm
Camera - TWRP
Sent from my Xperia S using Tapatalk
Zorbeyd said:
If you are root ;
http://forum.xda-developers.com/showthread.php?t=2634382
Click to expand...
Click to collapse
I follow the Method 3th, but it doesn't work. There is no Blue or any other LED appear.
My Device: Sony Xperia S lt26i, JB4.1.2, 6.2.B.1.96, rooted.
Code:
[email protected]:/system/bin # ls -l *.tar
-rwxr-xr-x root shell 3041280 2014-02-25 01:43 cwmrecovery.tar
-rwxr-xr-x root shell 5314560 2014-02-25 01:43 recovery.tar
[email protected]:/system/bin # md5sum *.tar
0beb12af614c79b17ddf10ff368e8d30 cwmrecovery.tar
e7ea2e3f8154ca88d0993119daf67188 recovery.tar
[email protected]:/system/bin # cd ../etc/
[email protected]:/system/etc # ls -l pre_hw_config.sh step2.sh
-rwxr-xr-x root shell 801 2014-02-25 01:46 pre_hw_config.sh
-rwxr-xr-x root shell 3397 2014-02-25 01:46 step2.sh
[email protected]:/system/etc # md5sum pre_hw_config.sh step2.sh
665738dead1c009c4cb3b2d5af400d4b pre_hw_config.sh
aa2990c79269ae335dee8aab5875b978 step2.sh
[email protected]:/system/etc # uname -a
Linux localhost 3.4.0+1.0.21100-313065-g1ccebb5-00193-gcbc50fc #1 SMP PREEMPT Tue Jul 23 15:55:38 2013 armv7l GNU/Linux
Nothing, no blue LED appears, and wether I press volume up or down, it goes from the SONY logo to the XPERIA logo and boots normally... :S
yorks.yang said:
I follow the Method 3th, but it doesn't work. There is no Blue or any other LED appear.
My Device: Sony Xperia S lt26i, JB4.1.2, 6.2.B.1.96, rooted.
Code:
[email protected]:/system/bin # ls -l *.tar
-rwxr-xr-x root shell 3041280 2014-02-25 01:43 cwmrecovery.tar
-rwxr-xr-x root shell 5314560 2014-02-25 01:43 recovery.tar
[email protected]:/system/bin # md5sum *.tar
0beb12af614c79b17ddf10ff368e8d30 cwmrecovery.tar
e7ea2e3f8154ca88d0993119daf67188 recovery.tar
[email protected]:/system/bin # cd ../etc/
[email protected]:/system/etc # ls -l pre_hw_config.sh step2.sh
-rwxr-xr-x root shell 801 2014-02-25 01:46 pre_hw_config.sh
-rwxr-xr-x root shell 3397 2014-02-25 01:46 step2.sh
[email protected]:/system/etc # md5sum pre_hw_config.sh step2.sh
665738dead1c009c4cb3b2d5af400d4b pre_hw_config.sh
aa2990c79269ae335dee8aab5875b978 step2.sh
[email protected]:/system/etc # uname -a
Linux localhost 3.4.0+1.0.21100-313065-g1ccebb5-00193-gcbc50fc #1 SMP PREEMPT Tue Jul 23 15:55:38 2013 armv7l GNU/Linux
Click to expand...
Click to collapse
Did you set permissions of scripts to 755?
Zorbeyd said:
Did you set permissions of scripts to 755?
Click to expand...
Click to collapse
Yes. Please see the code section I POST.
rwx -->7
r-x --> 5
Code:
[email protected]:/system/bin # ls -l *.tar
-rwxr-xr-x root shell 3041280 2014-02-25 01:43 cwmrecovery.tar
-rwxr-xr-x root shell 5314560 2014-02-25 01:43 recovery.tar
[email protected]:/system/etc # ls -l pre_hw_config.sh step2.sh
-rwxr-xr-x root shell 801 2014-02-25 01:46 pre_hw_config.sh
-rwxr-xr-x root shell 3397 2014-02-25 01:46 step2.sh
yorks.yang said:
Yes. Please see the code section I POST.
rwx -->7
r-x --> 5
Code:
[email protected]:/system/bin # ls -l *.tar
-rwxr-xr-x root shell 3041280 2014-02-25 01:43 cwmrecovery.tar
-rwxr-xr-x root shell 5314560 2014-02-25 01:43 recovery.tar
[email protected]:/system/etc # ls -l pre_hw_config.sh step2.sh
-rwxr-xr-x root shell 801 2014-02-25 01:46 pre_hw_config.sh
-rwxr-xr-x root shell 3397 2014-02-25 01:46 step2.sh
Click to expand...
Click to collapse
Oh sorry.
Can you put this " busybox " to /system/xbin folder with 755 permissions?
Link : http://d-h.st/LU0
Zorbeyd said:
Oh sorry.
Can you put this " busybox " to /system/xbin folder with 755 permissions?
Click to expand...
Click to collapse
Good, it works!
is the busybox problem? I had install it from google play, the latest version.
yorks.yang said:
Good, it works!
is the busybox problem? I had install it from google play, the latest version.
Click to expand...
Click to collapse
Hell yeah! :fingers-crossed:
When busybox version changes, i guess some busybox commands change occured. So, some codes on pre-hw and step2 scripts belongs this version of busybox.
Will that fix my problem too?
Xavali7 said:
Will that fix my problem too?
Click to expand...
Click to collapse
This only about installing recovery,
How can be able to fix it?
Whats your problem?? We need more details with it..
Well, I can't say much more than what I already did on the first post. I've tried a lot of methods to install the recovery, but none of them work. I even tried what Zorbeyd posted here, but it didn't work neither.
The results are always similar. Either the phone boots normally (ignoring any key combination I press), or it goes to a black screen after the Sony logo. I'm always able to go back flashing the stock rom with Flashtool, but I wanted to try KitKat, and not having a recovery prevents me from doing that...
PS: I tried method 1 on the thread Zorbeyd linked. Should I try method 3? I didn't, because I don't know how to hange those permissions on the folders. Could you give me some direction?
Okay, I looked it up, and did method 3. It doesn't work, the phone boots normally, and no blue LED appears...:crying:
Xavali7 said:
Well, I can't say much more than what I already did on the first post. I've tried a lot of methods to install the recovery, but none of them work. I even tried what Zorbeyd posted here, but it didn't work neither.
The results are always similar. Either the phone boots normally (ignoring any key combination I press), or it goes to a black screen after the Sony logo. I'm always able to go back flashing the stock rom with Flashtool, but I wanted to try KitKat, and not having a recovery prevents me from doing that...
PS: I tried method 1 on the thread Zorbeyd linked. Should I try method 3? I didn't, because I don't know how to hange those permissions on the folders. Could you give me some direction?
Click to expand...
Click to collapse
If you share logs about Method 1 , we can help you.
I guess electronics work that way sometimes... I did the same steps again, and now it's working!
Thanks guys, problem solved! Admins, you can close the thread now! :good:
Zorbeyd said:
Oh sorry.
Can you put this " busybox " to /system/xbin folder with 755 permissions?
Link
Click to expand...
Click to collapse
thank you man so much i had same problem and this solved it thank again
Hi,
I was about to start the PurpleDrake-Lite shell script in my distro, phone plugged in and configured thoroughly following the tutorial, but the output gave an error message right at start so I Ctrl+c'd to stop the script. Here is the issue:
In purpledrake_linux.sh, on line 17:
Code:
chmod -R 755 ./assets/linux/
of course, the error says "no such file or directory", because in the 'assets' directory there is:
Code:
$ ls -l
drwxr-xr-x linux32
drwxr-xr-x linux64
drwxr-xr-x osx
-rw-r--r-- permaroot.bin
-rwxr-xr-x purpledrake_main.sh
-rw-r--r-- start_restore
-rw-r--r-- temproot.bin
drwxr-xr-x windows
(I stripped the unnecessary bits from the output,) but no 'linux' directory.
I don't know if I should report it as a bug, and if so, where exactly?
Else, it seems even pointless to quit the process right at this stage, because the second script called, purpledrake_main.sh might well find it's way to the relevant directory? (In linux32 or in linux64, depending on the architecture of the machine, right?) and they all have the right 755 permissions anyway as it appears from the output.
What do you think?
Best regards,
Mélodie
meylodie said:
Hi,
I was about to start the PurpleDrake-Lite shell script in my distro, phone plugged in and configured thoroughly following the tutorial, but the output gave an error message right at start so I Ctrl+c'd to stop the script. Here is the issue:
In purpledrake_linux.sh, on line 17:
Code:
chmod -R 755 ./assets/linux/
of course, the error says "no such file or directory", because in the 'assets' directory there is:
Code:
$ ls -l
drwxr-xr-x linux32
drwxr-xr-x linux64
drwxr-xr-x osx
-rw-r--r-- permaroot.bin
-rwxr-xr-x purpledrake_main.sh
-rw-r--r-- start_restore
-rw-r--r-- temproot.bin
drwxr-xr-x windows
(I stripped the unnecessary bits from the output,) but no 'linux' directory.
I don't know if I should report it as a bug, and if so, where exactly?
Else, it seems even pointless to quit the process right at this stage, because the second script called, purpledrake_main.sh might well find it's way to the relevant directory? (In linux32 or in linux64, depending on the architecture of the machine, right?) and they all have the right 755 permissions anyway as it appears from the output.
What do you think?
Best regards,
Mélodie
Click to expand...
Click to collapse
Hi,
The header of the script contains this information:
# PurpleDrake root for LG G3 - Linux launcher
# - A collaboration between @autoprime , @thecubed (iomonster) , and @teamandirc (jcase)
Click to expand...
Click to collapse
Is there a specific place in this forum dedicated to bug reports? If so, where?
Now, what if I would start directly with the script which is inside the assets/ sub-directory: the file having for name "purpledrake_main.sh"? Would this have a chance to work directly? Or perhaps, should I reather use the first script, and just ignore the first error message and continue?
up! \o/
meylodie said:
Hi,
The header of the script contains this information:
Is there a specific place in this forum dedicated to bug reports? If so, where?
Now, what if I would start directly with the script which is inside the assets/ sub-directory: the file having for name "purpledrake_main.sh"? Would this have a chance to work directly? Or perhaps, should I reather use the first script, and just ignore the first error message and continue?
up! \o/
Click to expand...
Click to collapse
It looks like there is a Q&A forum for purpledrake here: http://forum.xda-developers.com/tmobile-lg-g3/help/qa-root-twrp-tmo-g3-purpled-t2926609 maybe ask the question there and you will get a faster response.
justmpm said:
It looks like there is a Q&A forum for purpledrake here: http://forum.xda-developers.com/tmobile-lg-g3/help/qa-root-twrp-tmo-g3-purpled-t2926609 maybe ask the question there and you will get a faster response.
Click to expand...
Click to collapse
Hi,
I don't think so, the topic contains "D851 only". I would risk being struck by lightning if I would not obey the rules?!
meylodie said:
Hi,
I don't think so, the topic contains "D851 only". I would risk being struck by lightning if I would not obey the rules?!
Click to expand...
Click to collapse
Hi,
Solved here:
http://forum.xda-developers.com/lg-...purpledrake-lite-t2821000/page78#post58280432
The script needs '*' at the end of the string "linux". Line 17:
Code:
chmod -R 755 ./assets/linux*/
instead of
Code:
chmod -R 755 ./assets/linux/
Thanks to tzvi.