Database Develop

[App2SD] NEW Script ! Working App2SD For LG GT540 Optimus

App2SD Optimus
Use At Your Own Risk !!
Tutorial version by mohicanrat and App2SD file from joe.stone
Risk :
* Lost Your Memory Card
Click to expand...
Click to collapse
{
"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"
}
Follow The Instruction Below to get App2SD in your LG optimus
Requirements :
* Rooted
* Superuser
* Android 2.1 Eclair
Click to expand...
Click to collapse
How To Do It :
1. Before Install app2sd. Don't forget is partition your sd card. use paragon partition manager portable (u can look everywhere)
2. Release your microSD card from the phone and insert into card reader on the Computer
3. Backup all of the data in microSD card
4. Open The paragon manager and choose Partition Manager 9.0
5. After partition manager 9.0 Opened, find the HDD diagram below and locate the picture diagrams to sdcard. (Be careful, which is a diagram on select microSD card)
6. Delete partition and create another partition like this :
* First Partition is 70% of The Size of microSD card And The Filesystem is FAT32
* Second Partition is 25% of The Size of microSD card And The Filesystem is linux ext2
* Third, create a new partition in the same place and same way but the file type is swap.
Click to expand...
Click to collapse
After it successfully Partitioning your microSD its mean your microSD cannot readed by the Computer/Windows. But don't worry, just insert the card into your phone and it can be readed again.
The next is to follow the step below to app2sd:
1.Download the file here app2sd_new
2.Extract zip file it and produces 3 folders.
3.Copy all folders to the SDCard. (Remember its three folders directly copied to SDCard)
4.OpenAndroid Market, and download application called GScript.
5.After GScript finish downloaded, open the application GScript in you Optimus
6.in GScript, click the Menu button on the phone, then select Add Script
7.Click Load File button and select the file on top, namely app2sd.sh
8. after the scripts GScript appear in the application, then push the Save button.
9.so you will see the name of the save and script was added in the list GScript.
10. Repeat step 6 until all the script was loaded in GScript.
11. if those all the step are finished, now is the time to do Optimus app2sd.
12.in existing scripts in Application GScript, choose a distinguished name a2sd_data and wait until the script execute and complete. (if finished script back to the List2 view more)
13. Turn off the HP and restart.
14. after HP flame back, Please to the settings menu hp, sdcard & phone storage agan, how tough the internal phone storage ?
Click to expand...
Click to collapse
Enjoy

this source app2sd have a bug. please change a source app2sd.

mohicanrat said:
this source app2sd have a bug. please change a source app2sd.
Click to expand...
Click to collapse
yes i have post the fixed one

Nice simple tut.
There is a simpler one-click auto install method, but I guess this is simple enough too

sorry for bad english
after my phone restart, it dont see sdcard, "unavailable", and it cant be seen on my computer too. I want to re-flash my phone but USB debugging not working. I ticked up it already, but my computer cant see it, I had tried factory reset but nothing happen.Does anyone can repair it?

this is my tutorial. all ....
please put my name in this tutor.

mohicanrat said:
this is my tutorial. all ....
please put my name in this tutor.
Click to expand...
Click to collapse
you make the indonesian and i make the english one

wtf?
if you copy tutor from someone, please put author name. this is a ethic.

hmms
mohicanrat said:
wtf?
if you copy tutor from someone, please put author name. this is a ethic.
Click to expand...
Click to collapse
idd, thanks for the english version but mohicanrat is right, u have to add the original source, thats rule nr 1.
if i need to do a school project and rip it from for example an indonesian person, and translate it to english, and say its mine. I would get a 0 and get banned from university....
(just to make a point)
your image says follow the rules, etc ,etc ,etc, RESPECT OTHER MEMBERS,

khakha258 said:
sorry for bad english
after my phone restart, it dont see sdcard, "unavailable", and it cant be seen on my computer too. I want to re-flash my phone but USB debugging not working. I ticked up it already, but my computer cant see it, I had tried factory reset but nothing happen.Does anyone can repair it?
Click to expand...
Click to collapse
u try to reflash your phone with firmware 2.1 of GT540 (France ). Next,Hardreset your phone and flash phone again with firmware (Baltic).It was successful with me.
Hope it is useful with you

Hello!
I want to ask the author of the post.
And from what considerations you used to mount mtdblock4?
I apologize for my English.

ehhm...
dont get this part
The next is to follow the step below to app2sd:
1. Download The App2SD File From here :
h*tp://www.mediafire.com/file/ih0dyjy4bxy5m9m/app2sdgt540_2_1.en_.zip
2. Install Via Adb Shell, and type like this :
- Adb shell
- Su (when the superuser appear, click allow)
- Sh /sdcard/app2sd/app2sd.sh
3. Wait till it restart itself
Enjoy
you download the stuff the app2sd folder where to place it lol

RDilus said:
ehhm...
dont get this part
The next is to follow the step below to app2sd:
1. Download The App2SD File From here :
h*tp://www.mediafire.com/file/ih0dyjy4bxy5m9m/app2sdgt540_2_1.en_.zip
2. Install Via Adb Shell, and type like this :
- Adb shell
- Su (when the superuser appear, click allow)
- Sh /sdcard/app2sd/app2sd.sh
3. Wait till it restart itself
Enjoy
you download the stuff the app2sd folder where to place it lol
Click to expand...
Click to collapse
Place The APP2sd Folder to the root of the MicroSD

When I typed
Sh /sdcard/app2sd/app2sd.sh
I get - not found. Then I seach in google and typed another code:
# sh /sdcard/gscript/a2sd.sh
sh /sdcard/gscript/a2sd.sh
mount: No such file or directory
/sdcard/gscript/a2sd.sh: cannot create /system/bin/busybox: read-only file system
: not found
failed.
: not found
mkdir failed for /system/sdcard, Read-only file system
: not found
mount: No such file or directory
/sdcard/gscript/a2sd.sh: 22: Syntax error: end of file unexpected (expecting "th
en")
Now I get read-only file system. How to fix it?
Thank you

gdavidkov said:
When I typed
Sh /sdcard/app2sd/app2sd.sh
I get - not found. Then I seach in google and typed another code:
# sh /sdcard/gscript/a2sd.sh
sh /sdcard/gscript/a2sd.sh
mount: No such file or directory
/sdcard/gscript/a2sd.sh: cannot create /system/bin/busybox: read-only file system
: not found
failed.
: not found
mkdir failed for /system/sdcard, Read-only file system
: not found
mount: No such file or directory
/sdcard/gscript/a2sd.sh: 22: Syntax error: end of file unexpected (expecting "th
en")
Now I get read-only file system. How to fix it?
Thank you
Click to expand...
Click to collapse
first: your phone must by rooted
second: connect your phone to PC withe USB debug mod, make "adb shell" command, make "su" command, confirm access on your phone... enjoy.

TheGiga said:
Place The APP2sd Folder to the root of the MicroSD
Click to expand...
Click to collapse
something else...
app2sd.sh is in gscript folder why is that?
write a proper guide or fix the files pls

I have no luck then tried run this from adb.. But when I used gscrit to run a2sd.sh everithing go fine.. Thank you.
Sent from my GT540 using XDA App

Is there any way to do this without using PC and card reader?
Cuz I unfortunatly have a desktop PC. not a laptop, and I dont have card reader.

ok i tried alot of times but this isnt just working everytime same damn errors
not a good tut
seirous fix the files!

did u ever get it fixed??

[Obsolete] [ROM] Stock 3.2.78 firmware rooted on squashfs/ext4 for SDE enabled Gen9

Hi All,
Here is rooted 3.2.78 firmware for SDE enabled devices.
I did two versions:
- squashfs (like my previous build), in this one, system is read-only, you can't add/remove stock apps and edit system files. Files are compressed so it takes less storage space than ext4, it should be also slower than ext4.
- ext4, system is read/write and should be quicker. Be careful if you modify system files though.
Both have kernel/modules from 3.2.78.
To install it:
0) You must have SDE installed. If you didn't do it already, check there instructions on how to do it.
1) Extract zip file content
2) Copy android_3.2.78.squashfs (or android_3.2.78.ext4) to internal storage root. You can do it the usual way or with adb with this:
Code:
adb push android_3.2.78.squashfs /data/media
or
Code:
adb push android_3.2.78.ext4 /data/media
3) Reboot
4) On boot menu, select "Recovery system"
{
"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"
}
5) Select "developer edition menu"
6) Select "flash kernel and initramfs"
6) A drive should appear on your PC, copy zImage and initramfs.cpio.gz to it.
7) Select OK, the kernel should flash.
8) Select OK to reboot and maintain vol+ pressed. Boot menu should appear after reboot.
9) Select SDE in boot menu, you should be rooted and SuperUser functional.
The only change from stock: I enabled vibrator control panel option, it has been reported to work on some, it doesn't on mine.
I checked 3.2.78 stock firmware, it has an updated bootloader, it may be worth flashing stock firmware too to have everything synched.
Download rooted 3.2.78 on squashfs here.
Download rooted 3.2.78 on ext4 here.
Cheers,
LeTama

great thank you
gonna flash it as soon as its downloaded
btw do i have to do any special things to flash the ext4 ?

Ok...good job....!!!
I understand now why I did not have options rw in root-explorer....because I managed the Rom with squashfs and not with ext4.....
Now everything is ok....thanks again @letama...

No, nothing special for ext4, same thing as squashfs...

letama said:
No, nothing special for ext4, same thing as squashfs...
Click to expand...
Click to collapse
Are you saying that installing with ext4 partition I'll can't be mount RW in root_explorer ?
-because with squashfs I can't ....

surdu_petru said:
Are you saying that installing with ext4 partition I'll can't be mount RW in root_explorer ?
-because with squashfs I can't ....
Click to expand...
Click to collapse
no i think he answered my question from above

surdu_petru said:
Are you saying that installing with ext4 partition I'll can't be mount RW in root_explorer ?
-because with squashfs I can't ....
Click to expand...
Click to collapse
No, sorry, our posts crossed, I was effectively replying to djnilse. I'm trying to refrain my "quote mania", it was not a good idea this time
Ext4 is R/W, and permanently, no need to remount it in root explorer.
I would have preferred ext4 mounted first as r/o and allow the option to remount as r/w when needed, but this is not possible with the way Archos designed their rootfs.

Hi Letama,
Thanks for your build but I cant use your kernel with 3.2.78 kernel modules and when I extract kernel from 3.2.78, init kernel does not boot :/.
Thanks in advance
Thaolia

ok i flashed it everything worked fine
i have now a dualboot recovery menu with Android(non-root) and developer(root)
on developer the root is ok, also the system is r/w
thx letama for the rooted newest update

As a question to get out of the way early in the thread, I'm on your earlier rooted one, do I need to wipe?
Sent from my HTC Desire HD using xda premium

Tha0lia said:
Hi Letama,
Thanks for your build but I cant use your kernel with 3.2.78 kernel modules and when I extract kernel from 3.2.78, init kernel does not boot :/.
Thanks in advance
Thaolia
Click to expand...
Click to collapse
Archos kernel is using a new compression scheme for initrd, check my howto, the "find . | cpio ..." command. You need to rebuild your initrd.

Quinny899 said:
As a question to get out of the way early in the thread, I'm on your earlier rooted one, do I need to wipe?
Click to expand...
Click to collapse
I don't think so, Archos firmware update doesn't, so it shouldn't be necessary.
I had to wipe mine for another reason so I can't be sure though.

letama said:
Archos kernel is using a new compression scheme for initrd, check my howto, the "find . | cpio ..." command. You need to rebuild your initrd.
Click to expand...
Click to collapse
My extract kernel is of 5Mb (I use your howto for extract the 3.2.78 kernel). Init and recovery extract kernel doesn't boot with a lzop initramfs.cpio. Wheras with your kernel and modules, all works fine.
Sry but I certainly forget somethings.
Thanks in advance
Thaolia

Tha0lia,
5 MB is wrong:
- aos-unpack gives you 9_MMCF (5145304)
- dd strips header and gives you init_kernel which contains zImage+initrd (5145040)
- aos-kernel-unpack of init_kernel gives you kernel and initrd separated (unpacked-kernel, unpacked-cpio.gz), that I renamed to init-zImage afterwards.
This is the one you want, size should be 3993572.
Cheers,
LeTama

Noticed an issue in the first post:
adb cp should read
adb push
Sent from my ARCHOS 80G9 using xda premium

Quinny899 said:
Noticed an issue in the first post:
adb cp should read
adb push
Click to expand...
Click to collapse
Thanks! I shouldn't post when I'm in a hurry . First post fixed.

letama said:
Tha0lia,
5 MB is wrong:
- aos-unpack gives you 9_MMCF (5145304)
- dd strips header and gives you init_kernel which contains zImage+initrd (5145040)
- aos-kernel-unpack of init_kernel gives you kernel and initrd separated (unpacked-kernel, unpacked-cpio.gz), that I renamed to init-zImage afterwards.
This is the one you want, size should be 3993572.
Cheers,
LeTama
Click to expand...
Click to collapse
Sorry, your kernel and my extract kernel have same md5sum.
It's my fault but thanks for your help.
Have a nice day !
Thaolia

For the Buzz in FRANCE
http://www.jbmm.fr/?p=25015
(ps : je recherche des rédacteurs "techniques" pour jbmm - envoyez un MP)

Is it possible to get swap working in the build modifications?
When I use swapper for root from the market, reboot and type free, I get this:
It shows it as empty and unused. Any idea why? There's a swapfile on /sdcard, in fat, which is being activated by the app on boot. Could this be fixed? I'm using the latest rooted ext4 version btw
Sent from my ARCHOS 80G9 using xda premium

I got swap working!
You use swapper 2 and direct it to /mnt/sdcard, and rather than /sdcard. Turns out internal is ext and it needs fat
Sent from my ARCHOS 80G9 using xda premium

[DEV][TOOLS] Unpack Repack boot.img (Kernel) Files And Modify Ramdisk

Hello!
This is -at least I hope it is- an easy to follow guide on how to unpack boot.img files (aka custom kernels) and modify the ramdisk.
Now, why would you want to do that?
First and simplest thing that comes to mind is for editing the kernel boot logo (the one that appears before the boot animation).
There are also a lot of other things you can edit in the ramdisk, but they require a bit more advanced knowledge, so we won't talk about them here.
Requirements:
1. Linux (any form will do, for example virtual box etc)
2. Perl (already included in Ubuntu, me thinks)
3. The Xperia Boot Tools package attached in this post
4. The mkbootimg binary (I already compiled it for Linux x86 and included it in the attachment)
5. Reading this post VERY VERY VERY carefully
Step 1: The mkbootimg binary
Let's install mkbootimg (we need it in order to repack the boot.img).
In a terminal window, cd to the directory where you extracted the mkbootimg file and type:
Code:
[B][I]sudo cp mkbootimg /bin/[/I][/B]
And then
Code:
[B][I]sudo chmod 755 /bin/mkbootimg[/I][/B]
Done!
* After first command, terminal will ask for your user password, type it, press enter and the command will be executed immediately.
Step 2: Splitting the boot.img
At this point, we need a boot.img file to play with.
Pick your favorite custom kernel and get the .img.
Place it in a folder along with the 2 perl scripts from the attached package.
In a terminal window, cd to the above-mentioned folder.
Next, type this command:
Code:
[B][I]perl split_bootimg.pl boot.img[/I][/B]
The command will return something like this:
Page size: 2048 (0x00000800)
Kernel size: 3132176 (0x002fcb10)
Ramdisk size: 3484496 (0x00352b50)
Second size: 0 (0x00000000)
Board name:
Command line:
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
Now the kernel is successfully extracted to your current directory.
It consists of 2 files: boot.img-kernel and boot.img-ramdisk.gz.
Step 3: Unpacking ramdisk
So we unvealed the ramdisk in our previous step but it is still of no use to us, so we need to un-gzip and then un-cpio it.
In the same terminal window as before, type:
Code:
[I][B]mkdir ramdisk[/B]
Code:
[B]cd ramdisk[/B]
Code:
[B]gzip -dc ../boot.img-ramdisk.gz | cpio -i[/B][/I]
Last command will return something like:
10503 blocks
Our ramdisk is unpacked now in the newly created /ramdisk folder.
Step 4: Editing ramdisk files
Now you can edit the contents of the ramdisk.
BE EXTREMELY CAREFUL AND NEVER EVER DO ANYTHING "JUST 'CAUSE"...
You need to be fully aware of what you're doing.
Good news is, changing the logo.rle (the static boot logo image) is fairly easy.
You just need to replace it with your .rle file.
I am not going to explain how to make your own .rle files right now.
Feel free to have a look at this thread for more info.
However, I attach the stock SE boot logo in case anyone misses it when he's on custom kernel.
IMPORTANT: Don't accidentally add irrelevant files to the ramdisk directory as cpio will include them too and your new boot.img will be useless.
Also, bear in mind:
DooMLoRD said:
there is a bug in the semc S1 bootloader... sometimes if the boot.img isnt of a correct size then the device will not boot... the workaround is to add a "filler" file (which is say 512KB file with junk data) to the ramdisk so as to increase the size of the final boot.img file...
thanks to jerpelea for this incredible tip... i must have wasted atleast 10-15 hrs trying to figure out why my kernel failed to boot
Click to expand...
Click to collapse
Step 5: Repack the ramdisk
Now that's all done, we need to pack the kernel back up into a flashable img file.
First, we will pack the ramdisk back to it's original state.
In the same terminal window as before, type:
Code:
[B][I]find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz[/I][/B]
Step 6: Repack the boot.img
In our last step, back into the terminal we go to use the "repack-bootimg" perl script that will give us our brand new boot.img.
Make sure to cd to the directory that the perl scripts are, much like in Step 1.
Type this command:
Code:
[B][I]perl repack-bootimg.pl '/.../.../.../boot.img-kernel' '/.../.../.../ramdisk' newboot.img[/I][/B]
Of course, replace /.../.../ with the path to the boot.img-kernel file and the ramdisk directory respectively.
All done! Your new img is newboot.img and is ready to be flashed!
ADVICE: Use fastboot boot and not fastboot flash boot the first time, to test that the new kernel boots. If all is well, proceed with the actual flashing!
FAQ:
- Can I do this on Windows?
- Not that I know of, no. You can use Vmware or VirtualBox to install a raw Ubuntu image (pure command line) on your Windows PC though.
- Great! How can I do this then?
- Wish I knew! I have a Linux partition on my PC, it has been like that forever. Google is your friend!
- This is so complicated, is there an easier way? Can you make a zip for me to use in recovery?
-
{
"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, don't get upset. Can you do it for me?
- I will have to say no, because I know that the minute word gets out that I take requests, I will be overwhelmed.
Took me several hours to figure all this out but it will take you less than 10 minutes to do it yourself if you carefully follow the instructions.
- I think this or that is wrong and it should be like this or that.
- Thank you very much for correcting me! I am still learning! Please post your corrections here or PM me and I will update the thread ASAP!
References:
- HOWTO: Unpack, Edit, and Re-Pack Boot Images
- How to Port Android to Another Device
- [How-To] Make custom bootscreen/bootlogo (image to rle)/(rle to image)
Thanks to:
- Riyal for giving me the idea to get into this.
- pvyParts because without him I'd only be "pulling Irises"...
Cheers!

Thank you very much. I've been looking for something like this.
Anyways, use VirtualBox instead of VMware. It's a thousand times better.

or try pendrivelinux,boot linux from windows..great tutorial,gonna try it
so everyone can be doomlord
question,if i manage to change boot image and repack the it back,is there any chance for me to "brick" the kernel?
Sent from my LT18i

Locked Bootloader
Hello Iridaki,
many thanks for your apports (this and the init.d script). I'm actually user from a Spanish forum called www.htcmania.com (you may have heard about thedr0idboy, which is a Neo developer) and we were trying to pack kernels in order to flash it in locked bootloader devices or at least try to create an Overclock module for stock kernel that can be flashed in locked devices.
Do you think we can use this to achieve this goal? I just hate Arc S with it's damn 1.4 GHz processor :S. It was released only a month after I got my Arc.
Many thanks for your time and your efforts!!
P.D: a girl developer!!!

rashid.fairus said:
so everyone can be doomlord
question,if i manage to change boot image and repack the it back,is there any chance for me to "brick" the kernel?
Click to expand...
Click to collapse
Nah, it takes a lot more to be DoomLord..!!!
If there are no errors in the cmd, boot.img should be OK.
By using flashboot boot command, the kernel is sent to the phone and it tries to boot it. It's not flashing it, so if it fails, it immediately goes back to previous kernel.
So don't worry! Imagine that until I found the correct script, I had tried more or less 10 crapernels (crappy kernels)!!!
iR¡[email protected]!* via Tapatalk

iridaki said:
Nah, it takes a lot more to be DoomLord..!!!
If there are no errors in the cmd, boot.img should be OK.
By using flashboot boot command, the kernel is sent to the phone and it tries to boot it. It's not flashing it, so if it fails, it immediately goes back to previous kernel.
So don't worry! Imagine that until I found the correct script, I had tried more or less 10 crapernels (crappy kernels)!!!
iR¡[email protected]!* via Tapatalk
Click to expand...
Click to collapse
looks like our themes and apps forum have a new section,kernel theming,,(iridaki,you have purple theme for apps and roms,how about kernel?)
Sent from my LT18i

A big thanks, iridaki!
I was looking forward to such thread.
I did also a lot of search on google too, but somehow I couldn't find any match.
I am an experienced Linux user, so that shouldn't be a problem for me.
I'll try everything this weekend.
Afaik, CWM is also stored in the kernel, so is it possible to modify it with the tool?
I don't want to have a step by step guide, just a reference would be great (of course if you know one).
Anyway, thanks for your great contributions in XDA.
Sent from my LT18i using xda premium

OMG... :-o Iris you are a genius.
Sent from my Arc S LT18i using Xda Premium App

glaudrem said:
Hello Iridaki,
many thanks for your apports (this and the init.d script). I'm actually user from a Spanish forum called www.htcmania.com (you may have heard about thedr0idboy, which is a Neo developer) and we were trying to pack kernels in order to flash it in locked bootloader devices or at least try to create an Overclock module for stock kernel that can be flashed in locked devices.
Do you think we can use this to achieve this goal? I just hate Arc S with it's damn 1.4 GHz processor :S. It was released only a month after I got my Arc.
Many thanks for your time and your efforts!!
P.D: a girl developer!!!
Click to expand...
Click to collapse
currently we cant use custom kernels on locked bootloader...
there is a way to make overclock module for stock kernel... i am looking into that possibility & i have contacted a few devs... i will work on it when i get time...
@Iris
there is a bug in the semc S1 bootloader... sometimes if the boot.img isnt of a correct size then the device will not boot... the workaround is to add a "filler" file (which is say 512KB file with junk data) to the ramdisk so as to increase the size of the final boot.img file...
thanks to jerpelea for this incredible tip... i must have wasted atleast 10-15 hrs trying to figure out why my kernel failed to boot

DooMLoRD said:
@Iris
there is a bug in the semc S1 bootloader... sometimes if the boot.img isnt of a correct size then the device will not boot... the workaround is to add a "filler" file (which is say 512KB file with junk data) to the ramdisk so as to increase the size of the final boot.img file...
thanks to jerpelea for this incredible tip... i must have wasted atleast 10-15 hrs trying to figure out why my kernel failed to boot
Click to expand...
Click to collapse
Great tip indeed!!! Added to the OP!
I haven't come across the issue yet because I am only editing some tweaks and the logo.rle but say someone uses a much smaller logo and deletes some scripts, would he need to use a filler file, even if it is for 20-30 KB?
THANKS!

iridaki said:
Great tip indeed!!! Added to the OP!
I haven't come across the issue yet because I am only editing some tweaks and the logo.rle but say someone uses a much smaller logo and deletes some scripts, would he need to use a filler file, even if it is for 20-30 KB?
THANKS!
Click to expand...
Click to collapse
size of logo doesnt really matter... just the final size of the boot.img matters...
btw the logo.rle must have correct permissions (644)

DooMLoRD said:
size of logo doesnt really matter... just the final size of the boot.img matters...
btw the logo.rle must have correct permissions (644)
Click to expand...
Click to collapse
Yes, but if the logo.rle is replaced with a smaller one in size, ramdisk size is reduced accordingly, isn't it?
Permissions are taken care of while unpacking/repacking.
Overall, this guide works, since I've sorted everything out, hasn't failed me yet!
dp94 said:
Afaik, CWM is also stored in the kernel, so is it possible to modify it with the tool?
I don't want to have a step by step guide, just a reference would be great (of course if you know one).
Anyway, thanks for your great contributions in XDA.
Click to expand...
Click to collapse
My initial response would have to be: I have no idea!
However, tell me what exactly do you want to edit. Images, colors, features?
I'll look into it, currently I have never been in involved with recovery.
theduke89 said:
OMG... :-o Iris you are a genius.
Click to expand...
Click to collapse
I have my moments.

Presumably, kernel.sin can be renamed to boot.img for splitting without problems, or am I missing something pertinent to SE?

LenAsh said:
Presumably, kernel.sin can be renamed to boot.img for splitting without problems, or am I missing something pertinent to SE?
Click to expand...
Click to collapse
NOOOOOOO!!
DoomLord has released a .sin unpacker. Unpack the kernel.sin with it, then repack it with my script.
iR¡[email protected]!* via Tapatalk

Found that previously, but the repacker doesn't work. I think the script he published is a hack of something else and may have errors.

LenAsh said:
Found that previously, but the repacker doesn't work. I think the script he published is a hack of something else and may have errors.
Click to expand...
Click to collapse
Well, no, the script is OK, it's just made to work with the particular unpacker I included in the package. You need to edit it a wee bit to work with the sin unpacker. If I get some time in the weekend, I'll look into it too.
iR¡[email protected]!* via Tapatalk

Magic, thanks Iris. I recall the unpacking is fine, it is just repacking that doesn't yield either a boot.img OR kernel.sin due to the mixed file names/folders etc. It's been a few months since I tried... forgive me. All I was doing at the time was taking a stock Neo kernel and making it insecure. Which is dead easy normally. done it plenty with other phones, but SE .sin files threw me.

iridaki said:
My initial response would have to be: I have no idea!
However, tell me what exactly do you want to edit. Images, colors, features?
I'll look into it, currently I have never been in involved with recovery.
Click to expand...
Click to collapse
Just to change the colors, rename options, maybe integrate some features into one option.
I have really tried to search a lot, here in XDA & Google, but I have no idea.

dp94 said:
Just to change the colors, rename options, maybe integrate some features into one option.
I have really tried to search a lot, here in XDA & Google, but I have no idea.
Click to expand...
Click to collapse
You would have to rebuild CWM from sources or so i believe. dont ask me how either as i've not a clue
LenAsh said:
Magic, thanks Iris. I recall the unpacking is fine, it is just repacking that doesn't yield either a boot.img OR kernel.sin due to the mixed file names/folders etc. It's been a few months since I tried... forgive me. All I was doing at the time was taking a stock Neo kernel and making it insecure. Which is dead easy normally. done it plenty with other phones, but SE .sin files threw me.
Click to expand...
Click to collapse
use this tool
http://forum.xda-developers.com/showthread.php?t=1262656
and then you will have a kernel and ramdisk and then it is just like any other boot img i had to edit it to make it unpack the ramdisk aswell. ( had to remove the ../ right after the gzip command )
basicaly use the file in that post instead of iridakis "split_bootimg.pl"
Pvy

I can change the boot logo now. Thanks very much.. I'm using doomlord kernel, but I love SE original boot logo. Finally I managed to change it. Thanks again. I just follow the instruction and it works. The reduce in size of boot.img didn't cause any problem at all... ;-)
Sent from my LT15i using xda premium

vold.fstab or fstab.aries storage issue

So my i9000 has a broken internal memory chip and I fixed the situation with a tutorial and an 8gb memory card and the phone works again BUT it says I have no internal or external sd card. In the video, the man shows how to fix this, but he does it for ICS which has a diferent vold.fstab file and he also does it very quickly.
I need someone who can help me for the fstab.aries text modification in 4.3 android. Thank you.
These are the links I used
http://forum.xda-developers.com/showpost.php?p=35915484
http://www.youtube.com/watch?v=zdMhYYdMB08
UPDATE:
So currently I have Cyanogenmod 10.2 installed, these are the two files fstab.aries and fstab.goldfish (I read that vold.fstab which was previously found in system/etc has been deleted)
fstab.aries code
# Android fstab file.
# <src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
recovery /recovery mtd defaults recoveryonly
boot /boot mtd defaults recoveryonly
radio /radio mtd defaults recoveryonly
cache /cache yaffs2 defaults recoveryonly
datadata /datadata yaffs2 defaults recoveryonly
/dev/block/mmcblk0p1 /sdcard vfat defaults recoveryonly,lun=/sys/devices/platform/s3c-usbgadget/gadget/lun0/file
/dev/block/mmcblk1p1 /external_sd vfat defaults recoveryonly,lun=/sys/devices/platform/s3c-usbgadget/gadget/lun1/file
# LVM Volumes
/dev/lvpool/system /system ext4 ro wait
/dev/lvpool/userdata /data ext4 noatime,nodev,nosuid,nomblk_io_submit,errors=panic wait,encryptable=footer,length=-16384
/devices/platform/s3c-sdhci.0/mmc_host/mmc0 /storage/sdcard0 auto defaults voldmanaged=sdcard0:1,nonremovable
/devices/platform/s3c-sdhci.2/mmc_host/mmc2 /storage/sdcard1 auto defaults voldmanaged=sdcard1:auto
Click to expand...
Click to collapse
fstab.goldifsh code
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/mtdblock0 /system ext4 ro,barrier=1 wait
/dev/block/mtdblock1 /data ext4 noatime,nosuid,nodev,barrier=1,nomblk_io_submit wait,check
/dev/block/mtdblock2 /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check
/devices/platform/goldfish_mmc.0 /storage/sdcard vfat defaults voldmanaged=sdcard:auto
Click to expand...
Click to collapse

samidoi said:
fstab.aries code
Click to expand...
Click to collapse
try switch these two lines (after you have backed up original as .bak file)
/devices/platform/s3c-sdhci.0/mmc_host/mmc0 /storage/sdcard0 auto defaults voldmanaged=sdcard0:1,nonremovable
/devices/platform/s3c-sdhci.2/mmc_host/mmc2 /storage/sdcard1 auto defaults voldmanaged=sdcard1:auto
Highlighted Blue part goes up
Highlighted red part comes down
also test this app and let me know if it works, without altering the fstab

Thank you so much mister, it worked!! Sorry for the delayed the response, I didn't have time to install 4.3 again but I finally did it now; I owe you a lot!!

So don't forget to hit his Thanks-Button
samidoi said:
Thank you so much mister, it worked!! Sorry for the delayed the response, I didn't have time to install 4.3 again but I finally did it now; I owe you a lot!!
Click to expand...
Click to collapse

samidoi said:
Thank you so much mister, it worked!! Sorry for the delayed the response, I didn't have time to install 4.3 again but I finally did it now; I owe you a lot!!
Click to expand...
Click to collapse
please, describe to me the detailed procedure. I did for CM10.1, CM10.2 but not.
I make the changes, but when I restart, returns to its original state. (I am root)

ethansetan said:
please, describe to me the detailed procedure. I did for CM10.1, CM10.2 but not.
I make the changes, but when I restart, returns to its original state. (I am root)
Click to expand...
Click to collapse
Same here... can't upgrade to CM10.2 until I figure this out. Any changes to the new fstab files are reverted when I reboot.

Ok so I found a different/interim solution using an init.d script. This is specifically for my Galaxy S2 Skyrocket (with broken internal memory), but can be modified for other phones.
Create a script file in your /system/etc/init.d/ directory called something like 11sd_remount:
Code:
sleep 2
mount -t vfat -o umask=0000 /dev/block/vold/179:97 /storage/sdcard0
mount -t vfat -o umask=0000 /dev/block/vold/179:28 /storage/sdcard1
Then chmod 755 the script file. Upon reboot, the internal/external sdcards should be swapped. I've attached an update.zip which sets up the script automatically, and can be used after updating CM.
To get this to work on other devices, you really just need to figure out the mount points for your internal and external sdcards. To do this, type mount in adb shell (from within CM, not recovery), and you'll see a list of mount points. Somewhere towards the end will be the lines for /storage/sdcard0 and /storage/sdcard1, looking something like /dev/block/vold/179:97. Simply modify the script using these points, and you should be good to go.

srnoth said:
Simply modify the script using these points, and you should be good to go.
Click to expand...
Click to collapse
was this done in addition to switching mounts in fstab or only this?
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
{
"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 are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.​

xsenman said:
was this done in addition to switching mounts in fstab or only this?
Click to expand...
Click to collapse
This works without switching mounts in any fstab files, since that method no longer works in 4.3/CM10.2.

srnoth said:
This works without switching mounts in any fstab files, since that method no longer works in 4.3/CM10.2.
Click to expand...
Click to collapse
Hi All,
Regading the problems in fstab files, I have been facing some problem, the famous "No External Storage Available" when I try to open the camera or gallery.
I tried to update fstab.aries, but after reboot, it was replaced to original file. Btw, I tried to update init.aries.rc also, but the same thing, it was recovered to the original one.
Anyone have some idea?

japzjapz said:
Hi All,
Regading the problems in fstab files, I have been facing some problem, the famous "No External Storage Available" when I try to open the camera or gallery.
I tried to update fstab.aries, but after reboot, it was replaced to original file. Btw, I tried to update init.aries.rc also, but the same thing, it was recovered to the original one.
Anyone have some idea?
Click to expand...
Click to collapse
Your Internal SD card may be corrupted, try to fix that first, try reading this and links in it
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.​

hey, thanks for the work
your File includes
System/Etc/init.d > 11sd_remount
and also:
META-INF > CERT.RSA
META-INF > CERT.SF
META-INF > MANIFEST.MF
META-INF/com/android > metadata
META-INF/com/google/android > update-binary & updater-script
and those are all required.. right? and where do we put the META-INF folder? on the Devices top folder, in the same location as "system"?
and then on the script, we put our current physical sdcard1 onto the current sdcard0's mount point, & vice versa?
so 179:97 is typically where sdcard1 is by default, so we just change 179:97 to be the point for sdcard0 instead, and point sdcard1 to the default mount point for sdcard0?
i guess I got that right?
and when you say "CHMOD 755" (verb) the file, you mean:
Owner= Read, Write, Execute
Group= Read, Execute
Others=Read Execute
is that right? and is that ONLY for the file found at System/Etc/init.d > 11sd_remount??
and can I just change those permissions for that file in ES File Explorer?
thanks

chinarabbit said:
hey, thanks for the work
your File includes
System/Etc/init.d > 11sd_remount
and also:
META-INF > CERT.RSA
META-INF > CERT.SF
META-INF > MANIFEST.MF
META-INF/com/android > metadata
META-INF/com/google/android > update-binary & updater-script
and those are all required.. right? and where do we put the META-INF folder? on the Devices top folder, in the same location as "system"?
and then on the script, we put our current physical sdcard1 onto the current sdcard0's mount point, & vice versa?
so 179:97 is typically where sdcard1 is by default, so we just change 179:97 to be the point for sdcard0 instead, and point sdcard1 to the default mount point for sdcard0?
i guess I got that right?
and when you say "CHMOD 755" (verb) the file, you mean:
Owner= Read, Write, Execute
Group= Read, Execute
Others=Read Execute
is that right? and is that ONLY for the file found at System/Etc/init.d > 11sd_remount??
and can I just change those permissions for that file in ES File Explorer?
thanks
Click to expand...
Click to collapse
The only file you actually need is the 11sd_remount. The other files in the .zip are just part of the flashing process for your recovery.
So either you can:
Edit the .zip file to match your device, then flash, or
Simply edit the 11sd_remount file, copy it to /system/init.d/ and then "chmod 755 11sd_remount"
You can change the file permissions with ES Explorer, but it's simpler to use terminal emulator or adb shell to navigate to the correct folder and then chmod the script. The main thing you're doing is setting the permissions for the script to be executable.
Regarding the actual mount points, the best thing to do is, with your phone on & connected to a computer, run adb shell and type "mounts". This will give you a list of the current, default mount points, including both the internal and external sd cards. Use that info to enter the correct points in the 11sd_remount script.

OK, i copied the 11sd_remount file to the init.d folder, then set permissions to rwx r-x r-x, then Rebooted the device, and it didnt work.. actually I think my SD card disappeared, then I booted to recovery and cleared cache and rebooted and now things seem back to normal.. addresses didnt change, its as if nothing has been done.
except, now i think i'm missing the following mount point from my list of Android System Info:
- /mnt/asec/net.dinglisch.android.appfactory-1
/dev/block/dm-0 ext4 ro,dirsync,nosuid,nodev,noatime
which was the last thing on the list.. but I dont know if its related..
also, the original info says it: "can be used after updating CM." I dont have CyanogenMod
thoughts?

well I got Internal 2 External to work after reboot
after copying everything from the internal SD to a freshly formatted SD card
launched the app, clicked the green arrow, clicked ASUS,
clicked "Use per default"
set my original internal to /mnt/sdcard and external to /mnt/sdcard1
then hit "Show other devices" scrolled down and clicked the 2nd to the last, and went up to make the sure that "The ext. sdcard device access" was set to the same number
then clicked External 2 Internal to return to the top page
then I unchecked "Apply at boot" and clicked "External2 Internal", waited a few minutes, clicked it again, then checked "apply at boot", clicked "External2 Internal" again, waited, did it again, then again..
then clicked the "init.d" button once, waited, then rebooted, then waited a few minutes after booting, then checked storage and everything was working.. except my internal sd card is the same as my external sd card now.. there is a repeat of the 32GB card, which is fine with me, so long as everything worked
that'll work

xsenman said:
Your Internal SD card may be corrupted, try to fix that first, try reading this and links in it
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.​
Click to expand...
Click to collapse
hey i have the same problem, i copied the new fstab.aries file to root direction but always when i start up my phone it is replaced by the original file and the switch doesnt works ...
i also have read the threader you give us, but i dont understand what i have to do ...
can you please help me my explaining what i have to do.
i'm sorry my english is not so good and i try my best.

jojo895 said:
hey i have the same problem, i copied the new fstab.aries file to root direction but always when i start up my phone it is replaced by the original file and the switch doesnt works ...
i also have read the threader you give us, but i dont understand what i have to do ...
can you please help me my explaining what i have to do.
i'm sorry my english is not so good and i try my best.
Click to expand...
Click to collapse
look here and you can use the i9000 swap kernels ( depends on ROM) or other methods mentioned in post No. 3, when it does not stick
Check this out! Links to useful Guides and " Banned " Documentaries ​ Merry Christmas everyone ​

xsenman said:
look here and you can use the i9000 swap kernels ( depends on ROM) or other methods mentioned in post No. 3, when it does not stick
Check this out! Links to useful Guides and " Banned " Documentaries ​ Merry Christmas everyone ​
Click to expand...
Click to collapse
hey, thank you for the fast answere but when i flash the other kernel or use the methode from post n.3 my smartphone cant boot anymore ...
i use cyanogenmod 10.2 stable version

jojo895 said:
hey, thank you for the fast answere but when i flash the other kernel or use the methode from post n.3 my smartphone cant boot anymore ...
i use cyanogenmod 10.2 stable version
Click to expand...
Click to collapse
I remember reading that for kernel, it works once you flash the Rom again, but did you check Settings >Mackay Settings? Vold methods read Post 1 and Post 2 , here or attach your vold fstab.aries file
Check this out! Links to useful Guides and " Banned " Documentaries ​

I have another way to fix a corrupted Internal memory at CM11 (KitKat).
My approach is make a symlink (/storage/sdcard0 -> /storage/sdcard1/scard/0) from /etc/init.d script.
After flashing CM11, I have mounted external memory to /storage/sdcard1 and clean folder for internal memory /storage/sdcard0.
We'll be fixing it..
To start, create a directory for "internal memory":
Code:
mkdir /storage/sdcard1/sdcard/0
and create an empty file .nomedia in /storage/sdcard1/sdcard directory:
Code:
touch /storage/sdcard1/sdcard/.nomedia
Then create the /etc/init.d/99intmem file with the contents:
Code:
#!/system/bin/sh
mount -o remount,rw /
rm -r /storage/sdcard0
ln -s /storage/sdcard1/sdcard/0 /storage/sdcard0
mount -o remount,ro /
and make it executable:
Code:
chmod +x /etc/init.d/99intmem
and reboot now!
That's all!

Partitions not mounting @boot

Hey Guys,
first off i had this issue once before, but in that case i could restore a cwm backup from sd card and after sometime the problem fixed itself,
this time, i switched to bacon and i wanted to prepare the p880 for my sister to use, i downloaded zaiben, formatted my external sd card and put the rom on it, i rebooted to recovery wiped( i used the clean to install new rom in philz recovery if i remember correctly) everything and flashed the rom and exactly as last time, the flash seems to go way too fast and ofc i cant boot into android. now as i formatted my sd i have no backup to restore to. kdz flashing seems hopeless as well, as none of the tools recognize the phone when i put it in s/w upgrade mode,
for proof: i checked /system with aromafm and found it being empty after flashing a rom, i even tried extracting the rom zip on sd and moving the content from the zip to /system manually but after a recovery reboot, /system was empty again( only empty "bin" folder)
is somebody able to explain me why i have this issue and maybe how to fix it, or upload a clean cwm backup of whatever rom for me to use?
thx

Thanks for the help until now, really.......
In Further investigation i could find out that Roms ARE actually flashing properly, but /system and probably other partitions are not being mounted
At Boot or in recovery(manually mounting works Here) which is why aromafm reports an empty /system, after a manual Mount in either recovery itself of Aroma console i can See /system being filled with Rom files, now i will change the thread title accordingly, and now ASK: can i force /system to be mounted at Boot somehow? Someone pls answer this time

Okay this is ridicoulous.... why am i getting no help AT ALL?, thank you srsly.....
i investigated even further and suspected that something with fstab might be wrong, but fstab file looks fine to me:
Code:
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 rw
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 rw
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 rw
if someone bothers to answer: what do you think?
pls help........

bump
please help

What recovery are you using? Are you sure your partitions aren't formatted to F2FS? (which would explain why the (F2FS-) recovery can mount the partitions but the system cannot as it expects an ext4 formatted partition rather than a F2FS formatted one)

i'm using an older version of philz touch (i dont think it has f2fs functionality), as i had weird flickering issues with latest philz,
using cat /proc/mounts shows ext4 for /system and other partitions

~MaX~ said:
i'm using an older version of philz touch (i dont think it has f2fs functionality), as i had weird flickering issues with latest philz,
using cat /proc/mounts shows ext4 for /system and other partitions
Click to expand...
Click to collapse
Did you try to boot another ROM (Slim, nameless, whatever) or using another kernel?

laufersteppenwolf said:
Did you try to boot another ROM (Slim, nameless, whatever) or using another kernel?
Click to expand...
Click to collapse
i tried latest aospa,zaiben, pa 3.99 and iodak kernel (stock or cm according to the kind of rom i tried to boot)
thank you for helping btw, i appreciate it
EDIT: I attached an image of output of cat /proc/mounts (sorry for the size)
{
"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"
}

~MaX~ said:
i tried latest aospa,zaiben, pa 3.99 and iodak kernel (stock or cm according to the kind of rom i tried to boot)
thank you for helping btw, i appreciate it
EDIT: I attached an image of output of cat /proc/mounts (sorry for the size)
Click to expand...
Click to collapse
hmm, can you please grab me a kmsg? (from when it is stuck)

laufersteppenwolf said:
hmm, can you please grab me a kmsg? (from when it is stuck)
Click to expand...
Click to collapse
could you give me a quick how to on using adb in recovery from pc? i put the phone in sideload mode and tried "adb shell dmesg" but the output just was "error close" and using the command in aromafm terminal gave me an endless stream of log
(Also currently need to charge the phone a bit)
EDIT: NVM kmesg incoming....
okay next question, how can i dump the output into a file and how do i know where it hangs? time in recovery is not correct anymore(i set it once but after reboot it was wrong again, also in kmesg the time again seems to be different)

does that part help? i think it has to do with boot

~MaX~ said:
does that part help? i think it has to do with boot
Click to expand...
Click to collapse
nah, I need the entire log
here's how you get it:
boot the system until it is stuck
hard reboot into recovery (don't enter sideload)
then run the following commands:
Code:
adb shell cat /proc/last_kmsg > /sdcard/last_kmsg
adb pull /sdcard/last_kmsg C:\whatever\path\you\like\last_kmsg
then post the file via pastie.com or any other online paste site

laufersteppenwolf said:
nah, I need the entire log
here's how you get it:
boot the system until it is stuck
hard reboot into recovery (don't enter sideload)
then run the following commands:
Code:
adb shell cat /proc/last_kmsg > /sdcard/last_kmsg
adb pull /sdcard/last_kmsg C:\whatever\path\you\like\last_kmsg
then post the file via pastie.com or any other online paste site
Click to expand...
Click to collapse
no such file or directory
by hard reboot you mean vol - and hold power without pulling battery after hang?

~MaX~ said:
no such file or directory
by hard reboot you mean vol - and hold power without pulling battery after hang?
Click to expand...
Click to collapse
Yes, I meant that. But no kernel log seems like your boot partition/kernel is messed up... I guess you'll have to find a way to restore your entire phone via LG tools, I can't see any other way around that..

laufersteppenwolf said:
Yes, I meant that. But no kernel log seems like your boot partition/kernel is messed up... I guess you'll have to find a way to restore your entire phone via LG tools, I can't see any other way around that..
Click to expand...
Click to collapse
two last things then: when i hold vol - and then hold power until i reboot, recovery does not start, it tries to boot android again (has always been like that)
and also: all roms except cm official show no bootanimation before hang, cm does

~MaX~ said:
two last things then: when i hold vol - and then hold power until i reboot, recovery does not start, it tries to boot android again (has always been like that)
and also: all roms except cm official show no bootanimation before hang, cm does
Click to expand...
Click to collapse
1) yeah, I know, easiest way to fix that is to simply pull the battery and then boot into recovery
2) if the bootanimation shows up, it means the kernel as well as the ramdisk have booted properly. So in this case, you should be able to grab a last_kmsg as well as a logcat

hi
today I installed that application " LG-Optimus-4XHD-Recovery-v1.0.apk "
I have selected ClockworkMod Custom Recovery.
It showed that Operation is successful.
than i clicked on "Boot Recovery" to restart my Phone in CloclworkMod Custom Recovery.
since then I am getting only Starting animation. (LG LOGO).
nothing happens.
My battery was full when i performed this procedure
any help please