yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] napstersnook:
boss it seem to have failed running the injector aroma though it said that it extracted successfully when i tried doing it in recovery.

please see the attachment for the injector.log and the screenshot of my phone when i tried installing the aroma. sorry for the blurry image though, i only used my old phone in taking the picture. i hope i'll still be able to use mount2sd... hope you can still help me and the others too... thanks

injector.log:

Starting Injector v.0.2.8

Using /tmp/busybox as the toolbox for this script

Using configuration file global.conf

Extracting the device boot.img

27152+0 records in

27152+0 records out

13901824 bytes (13.3MB) copied, 0.414940 seconds, 32.0MB/s

Android Boot Image Info:

* file name = /tmp/boot.img

* image size = 13901824 bytes (13.26 MB)

page size = 4096 bytes

* Boot Name = ""

* kernel size = 4516392 bytes (4.31 MB)

ramdisk size = 571289 bytes (0.54 MB)

* load addresses:

kernel: 0x00208000

ramdisk: 0x01500000

tags: 0x00200100

* cmdline = androidboot.hardware=qcom loglevel=1 vmalloc=200M

* id = 0xad8595a5 0xcd8a330a 0xd1bd1d8e 0xe0b44f8d 0x2ec22c39 0x00000000 0x00000000 0x00000000

Unpacking the boot.img

writing boot image config in bootimg.cfg

extracting kernel in zImage

extracting ramdisk in initrd.img

Disassembling the initrd.img

1791 blocks

The disassembled initrd.img is corrupted!

Moving log file to /sdcard/Injector/injector.log
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Yes, it seams that your device uses a different ramdisk structure than most android devices. Will need to add a specific config file and script to handle your device. Will see if I can collect enough info about the device to build it.
[Android Software/Hacking General [Developers Only]] napstersnook:
im glad to hear that boss... i hope my phone will be supported as soon as you guys are not so busy... im sure a lot of us like me might have this phone in the next coming days due to its great features/specs... so the next update from you will be of great help. thanks in advance. kindly let me know if you need more info about Flame 2.0, i may be able to help too atleast for sharing the contents of it.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
The info I need is about the boot.img. I normally get this by surfing the device files on the custom github entries, but can't find anything about your device.

So I will have to extract the information myself, but to do this I need your boot.img. In the attachment below is another injector version. This version will make a copy of the extracted boot.img in the root of your sdcard. Just run this like before and select option 2. Ignorer the errors that you got before. When it is done, just reboot your phone and the boot.img should be saved on the sdcard. Attach it here for me.
[Android Software/Hacking General [Developers Only]] napstersnook:
here is the file boss as requested, sorry for the delay, had some problems uploading here but it's ok now...kindly check the attachment. thanks
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
It seams that whomever build your device, decided to use a custom mkbootimg binary instead of the one provided by the Android source. I will have to make a new binary myself that matches the changes that they have made, while keeping it compatible with the normal boot.img structure. Not sure this will be done today, as the C language is not my strongest side. Maybe it will be done tomorrow.
[Android Software/Hacking General [Developers Only]] napstersnook:
Thanks a lot boss... just take your time coz I can still wait til you're free to work on this... no pressure, if only i can help with programming but i'm just more on troubleshooting computer hardware/software. I'll be checking this thread every hour if possible... :cool:
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
While your waiting, could you extract the file /system/build.prop? You can use ADB or a root file manager. I will also need /recovery.fstab or /etc/recovery.fstab. This however needs to be extracted while your in the recovery, so ADB is your only way.
[Android Software/Hacking General [Developers Only]] napstersnook:
hi boss, gud morning...sorry i fell asleep last time coz it was actually around 4am our time...hehe. attached now is your requested build.prop and recovery.fstab extracted using adb command. please let me know if i can provide you more details for us to get mount2sd working...thanks so much for the help and patience.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Thanks, config has been created along with a new mkbootimg binary which will support your device. Just download the new 0.1.16 version :)
[Android Software/Hacking General [Developers Only]] gregferns:
Hi dk, for my phone Micromax a 116 canvas HD, the only error message I get in the log is that the script has not been fully executed during boot.

I am running a custom ROM Sam HD . I even tried installing the latest legacy injector. It rebooted recovery and hung there. I had to pull battery. Then I tried installing aroma injector of 20th may. I tried second option but it hung on injecting...

Please help and let me know what info you need from me regarding the phone.

Thanks
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Try the latest injector with second option, if it hangs, then get the log /tmp/injector.log using adb before rebooting or pulling battery. I need to know where it hangs.
[Android Software/Hacking General [Developers Only]] gregferns:
That will take a few days to a week as I currently don't have access to a pc.. I know it requires adb because of the tmp part but can't help it.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
I may have an idea. Will look at that when I have time, but I have no way of testing if it actually works as all my 4 test devices and my own daily device works fine as it is.
[Android Software/Hacking General [Developers Only]] gregferns:
Cool, am willing to try out any idea from you...

By the way, no githubs etc for my devce i think but there are a few custom roms for it

http://xdaforums.com/showthread.php?t=2111559

Feel free to check it out IF YOU HAVE THE TIME :)

thanks

greg
[Android Software/Hacking General [Developers Only]] aelfinn:
Sorry if this has been asked before, but search turned up nothing relevant.

If I install e.g. VJ’s 4.2.2 rom, do I install the M2SD zip from recovery right after that without reboot? Is there anything else I need to do once I have booted into Android?
[Android Software/Hacking General [Developers Only]] napstersnook:
hi boss, thanks for the update. i was actually excited to test it but when i tried the update, it seem to have the same info on the logfile... kindly let me know if i may be missing out some process...note: cwm/recovery is ok, rooted by aio, busybox installed, and sd-ext2 partition is ok. I am really curious on what may be causing the m2sd to not work properly... hope to hear from you again.

here's the content:

Starting Injector v.0.2.10

/tmp/aroma-data/injector/injector.sh: line 362: /tmp/busybox: not found

Using /tmp/aroma-data/busybox as the toolbox for this script

Using configuration file global.conf

Extracting the device boot.img

27152+0 records in

27152+0 records out

13901824 bytes (13.3MB) copied, 0.499349 seconds, 26.5MB/s

Android Boot Image Info:

* file name = /tmp/boot.img

* image size = 13901824 bytes (13.26 MB)

page size = 4096 bytes

* Boot Name = ""

* kernel size = 4516392 bytes (4.31 MB)

ramdisk size = 571289 bytes (0.54 MB)

* load addresses:

kernel: 0x00208000

ramdisk: 0x01500000

tags: 0x00200100

* cmdline = androidboot.hardware=qcom loglevel=1 vmalloc=200M

* id = 0xad8595a5 0xcd8a330a 0xd1bd1d8e 0xe0b44f8d 0x2ec22c39 0x00000000 0x00000000 0x00000000

Unpacking the boot.img

writing boot image config in bootimg.cfg

extracting kernel in zImage

extracting ramdisk in initrd.img

Disassembling the initrd.img

1791 blocks

Running injector scripts

Executing 05-remover.sh

Executing 09-installer.sh

Re-assambling the initrd.img

Re-packing the boot.img

reading config file /tmp/boot_img/bootimg.cfg

reading ramdisk from /tmp/boot_img/initrd.img

Writing Boot Image /tmp/boot.img

Android Boot Image Info:

* file name = /tmp/boot.img

* image size = 13901824 bytes (13.26 MB)

page size = 4096 bytes

* Boot Name = ""

* kernel size = 4516392 bytes (4.31 MB)

ramdisk size = 572225 bytes (0.55 MB)

* load addresses:

kernel: 0x00208000

ramdisk: 0x01500000

tags: 0x00200100

* cmdline = androidboot.hardware=qcom loglevel=1 vmalloc=200M

* id = 0xad8595a5 0xcd8a330a 0xd1bd1d8e 0xe0b44f8d 0x2ec22c39 0x00000000 0x00000000 0x00000000

Writing the new boot.img to the device

Segmentation fault

It was not possible to write the boot.img to the device!

Moving log file to /sdcard/Injector/injector.log
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Recovery install if ment when you update your ROM. If you are doing a lean install, then you can do whatever you want, play store or recovery.

That is a bigger problem. It seams that you are able to extract the boot.img from the partition, but not allowed to write to the partition, which means that we cannot put it back after altering it. Same issue as with most HTC devices and SonyEricsson (Not the new Sony).

Do you have fastboot on your device? This is what we use on the other devices with part locked boot partitions. If you do, then you need to select option 2 in Aroma, then boot into Android and extract the boot.img from your sdcard into your PC and use fastboot to flash it to the device with the command "fastboot flash boot boot.img" after entering fastboot stage on the device.
[Android Software/Hacking General [Developers Only]] aelfinn:
And by “update your ROM” you mean what exactly? You mean I can replace A2SD, which is currently running on my phone, with M2SD?

My usual scenario, though, would be to do a full wipe and then install the new rom. Any advantages then if I install M2SD directly from recovery without reboot?
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Let's cover everything.

Let's say that you have a clean install (You just wiped everything and flashed a ROM), no installs from play store or anything. Now you install M2SD from Play Store. During the first reboot, the script, which is placed on the system partition, will move content from /data to /sd-ext, a partition now known to Android, so we link the folders back to /data so that Android may find them, thinking that they are still placed on /data.

A few days/weeks/months later, it's time to update your ROM (A new version is out). You reboot into recovery and flash the new ROM (No wipe of data). You still have data content placed on /sd-ext, but the script controlling it (Placed in /system) is gone since flashing a new ROM will delete any old content from /system. If you reboot your device now, all of the content stored on /sd-ext will not be available to Android since the script was not present to create the link between /data and /sd-ext, so rebooting and reinstalling M2SD from Play Store is not much of an option in this case. This is what the recovery installer is meant for. It allows you to reflash M2SD after flashing a new version of a ROM, so that when you reboot, the script placed on /system will be present during boot and the link between the two partitions will be created.

So again. If you have nothing on your sd-ext partition, then it does not mater how you install this. Otherwise, recovery would be a good idea.
[Android Software/Hacking General [Developers Only]] PerfectSlayer:
Nearly all the others scripts are disable when installing Mounts2SD.

If the rom has incompatible scripts, you may remove it from /system/etc/init.d/ directory (find the related script and remove it).

Otherwise, you could always remove Mounts2SD :( (removing the app remove the script).
[Android Software/Hacking General [Developers Only]] napstersnook:
yes boss i have fastboot on my flame 2.0, that's what i used in extracting build.prop and recovery.fstab and i was also successful in flashing the boot.img extracted from the phone and injected by aroma as per your instructions...ummm i tried rebooting after flashing but m2sd still wont work...the radio buttons of status and the others don't have check mark which means disabled, although from the settings of it, the busybox was configured and the script was also ok...there's not even a log from it or anything saying that there's an error somewhere. i also tried repartitioning my sdcard from fat32 with ext2 to fat32 with ext3 to check wether it's what causing the problem but still no go.can you still advice me boss of something that may solve m2sd issue on my phone? again, thanks for the time you're spending and patience.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Well, since you seam to familiar with most of the android tools and knows how to debug things, it should not be all that dificult figering out the last issues.

Shutdown your device, plug-in your USB cable and open a terminal, type the below commands and turn on your device.

Windows:

adb wait-for-device && adb logcat | findstr /I "mounts2sd"

Linux:

adb logcat | grep -i "mounts2sd"

Mounts2SD should be executed during boot if you have the init.d support. It properly just errors out before the log is ready. The above code will print only logcat entries related to M2SD.

If you want to be sure that the init.d support was successfully injected, type in the below commands while booted in Android.

Linux & Windows:

adb shell busybox grep "sysinit" /init.rc

This should return both an "exec ..." line along with an "service ..." line.
[Android Software/Hacking General [Developers Only]] napstersnook:
that's a fast response, thanks. please see below the printed logcat entries for m2sd as per the instructions, dunno what it exactly means, i thought it may be having some problem/s with busybox?kindly relay to me what it means...

E:\Napster\Software\Applications\Unlocking Tools\Cherry Mobile Flame 2.0\Android

AIO Flasher\tools>adb wait-for-device && adb logcat | findstr /I "mounts2sd"

I/ActivityManager( 481): Start proc com.spazedog.mounts2sd for broadcast com.sp

azedog.mounts2sd/.StartupReceiver: pid=2016 uid=10075 gids={1015, 1023, 1028}

E/mounts2sd( 2104): No busybox binary is present on the device!

I/ActivityManager( 481): No longer want com.spazedog.mounts2sd (pid 2016): hidd

en #16

I/ActivityManager( 481): START {act=android.intent.action.MAIN cat=[android.int

ent.category.LAUNCHER] flg=0x10200000 cmp=com.spazedog.mounts2sd/.StatusActivity

u=0} from pid 753

I/ActivityManager( 481): Start proc com.spazedog.mounts2sd for activity com.spa

zedog.mounts2sd/.StatusActivity: pid=2957 uid=10075 gids={1015, 1023, 1028}

I/ActivityManager( 481): Displayed com.spazedog.mounts2sd/.StatusActivity: +641

ms

I/ActivityManager( 481): START {flg=0x10000000 cmp=com.spazedog.mounts2sd/.LogA

ctivity u=0} from pid 2957

I/ActivityManager( 481): Displayed com.spazedog.mounts2sd/.LogActivity: +94ms

^C^C

E:\Napster\Software\Applications\Unlocking Tools\Cherry Mobile Flame 2.0\Android

AIO Flasher\tools>adb wait-for-device && adb logcat | findstr /I "mounts2sd"

I/ActivityManager( 483): Start proc com.spazedog.mounts2sd for broadcast com.sp

azedog.mounts2sd/.StartupReceiver: pid=2010 uid=10075 gids={1015, 1023, 1028}

E/mounts2sd( 2112): No busybox binary is present on the device!

I/ActivityManager( 483): No longer want com.spazedog.mounts2sd (pid 2010): hidd

en #16

when i tried to check as well if init.d support was successfully injected as per your instructions this is what the result was:

E:\Napster\Software\Applications\Unlocking Tools\Cherry Mobile Flame 2.0\Android

AIO Flasher\tools>adb shell busybox grep "sysinit" /init.rc

grep: /init.rc: Permission denied

do you think boss it would help if i try injecting the boot.img again and reflash it? im a bit confused on whats happening...
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
You are missing busybox. Search for it on play store and install it.
[Android Software/Hacking General [Developers Only]] xeraphael:
Thanks for the long explanation. Is there a way to tell whether I need the ext4 or the MTD version of the recovery zip, though? I have my sd-ext partition formatted with ext4, but /proc/mtd exists on my system (SE Xperia ray, CM10). Internal memory is yaffs2, but I'm not 100% sure on this.

Thanks in advance.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
It does not come down to the sd-ext file system. It comes down to whether your internal partitions use ext4 or not. Yours uses yaffs2
[Android Software/Hacking General [Developers Only]] MetinKale38:
Couldnt you let your script just try both methods? It would be easier, because lots of people do not know which to use

Tapatalked with my JellyBean powered HTC Desire
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
It's not about the script. It's about Android's updater-binary (The installer used in the recovery). The one used for the newer EMMC devices often does not work on older MTD devices or the other way around. When I am done with the new app, I will make an 100% Aroma based installer without anything of the original Android stuff, this will make one installer compatible with all devices. But for now, this was the only solution as you cannot place two binaries in one package, and the Aroma version at that time depended on device specific screen adjustments which made it impossible to make an Aroma based installer which would be compatible with all devices.
[Android Software/Hacking General [Developers Only]] napstersnook:
boss, i'm not missing busybox based on the message:

E:\Napster\Software\Applications\Unlocking Tools\Cherry Mobile Flame 2.0\Android

AIO Flasher\tools>adb shell busybox grep "sysinit" /init.rc

grep: /init.rc: Permission denied

but just to be sure i tried reinstalling busybox pro 1.0... and left it open... then i tried the commands again and here's the message:

E:\Napster\Software\Applications\Unlocking Tools\Cherry Mobile Flame 2.0\Android

AIO Flasher\tools>adb shell busybox grep "sysinit" /init.rc

exec /system/bin/sysinit

start sysinit

service sysinit /system/bin/logwrapper /system/xbin/run-parts /system/etc/boot.d

E:\Napster\Software\Applications\Unlocking Tools\Cherry Mobile Flame 2.0\Android

AIO Flasher\tools>

after that i tried reconfiguring m2sd based on my preference and rebooted my phone hoping that it'll work... but still nope, didn't work.

i tried to check again by using the commands you gave me and yep permission denied again...it seems that busybox is not working on my phone during boot up and will only work when opened first...probably the reason why m2sd isn't working properly.i don't have an idea now what's next, please advice boss... thanks again. (i may be able to read your response probably after 5 to 6hrs from now...still have to sleep since it's 3am here now)
[Android Software/Hacking General [Developers Only]] acestars:
I just tried "reverse mount" and it worked but i found bugs

1. cache partition not mounted if before reverse mount activated moved to /sd-ext.

2. /data/local still use /data (after reverse mount become /sd-ext) after reverse mount activated.

Thanks.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Cache is by default set to auto. It will be moved only if the internal is below 40mb

/data/local will use the partition with most available space, data, sd-ext or cache.

There is no bug, just a script that adapts to the specific devices current states.
[Android Software/Hacking General [Developers Only]] gian569:
Hi all a friend of mine can't use mounts2sd, he had a STONEX STX S, which is the main problem cuz as far as i know there aren't recovery, custom roms or kernels for it. Anyway he rooted it, he installed busybox, he got init.d support, and the script is still saying 'the sd-ext partition could not be mounted' and 'error detected while checking sd-ext. Everything was left uncorrected!'

Is there anything i can do or i have to give up?thanks!

Inviato dal mio HTC Desire HD con Tapatalk 2
[Android Software/Hacking General [Developers Only]] acestars:
Thanks for your fast respons, :D

Before i activated reverse mount, i set app,data,cache moved to /sd-ext and my internal data space is around 19mb. So based on your explanation the /data/local will mount to /data partition (it's /sd-ext before reverse mount activated) but it still mounted into /sd-ext (it's /data before reverse mount activated). The /cache partition is "really" not mounted when i run command "df -h" there is no /cache partition.
[Android Software/Hacking General [Developers Only]] mdfzhi:
Just passing by and saying thanks for this wonderful app. Been using this since its just a simple flashable script until now, an app in market.

Btw, i dont know if its just me, but with cm10.1 its always reverted to safe mode. Looking into kernel ramdisk, turns out cm10.1 changed how it called sysinit. They changed it so sysinit would be called right after kernel bootlogo really early in boot process. Probably for making boot faster. Checking to disable safe mode made moving dalvik works again.
[Android Software/Hacking General [Developers Only]] dejanxxxx:
On my ROM -AOKP Milestone 6 which ported on Alcatel ot 990 dont work. When flashing scripts get bootlop, when install applications dont work, say NOT EXECUTED something like this-first option. And dont see EXT, write N/A.

What do, my internal memory is small.
[Android Software/Hacking General [Developers Only]] gian569:
Please guys could someone help me?

Inviato dal mio HTC Desire HD con Tapatalk 2
[Android Software/Hacking General [Developers Only]] PerfectSlayer:
Did he add an ext partition at the start of his sdcard?
[Android Software/Hacking General [Developers Only]] gian569:
What do you mean with 'at the start'? Anyway i formatted it with my 4ext recovery, i set 2048mb ext3 partition and no swap

Inviato dal mio HTC Desire HD con Tapatalk 2
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
This is usually a busybox issue. Update busybox from Play Store.
[Android Software/Hacking General [Developers Only]] gian569:
Freshly installed busybox when doing all the rest, no update avaiable...

Inviato dal mio HTC Desire HD con Tapatalk 2
[Android Software/Hacking General [Developers Only]] PerfectSlayer:
As the first partition. But if you did it throw recovery, it should be fine. (if you used GParted, for exemple, you may have inverted partition order ;))
[Android Software/Hacking General [Developers Only]] gian569:
Ok then so what could it be? I don't know if it may be the cause, but phone has sh*tty management of the memory...seen through a file manager, there is root which is the rom, sdcard which is the 2gb internal memory, and sdcard2(the real sd card).so when trying to put apps to sd,they go to 2gb mem so there's no way to put them on sd...

Inviato dal mio HTC Desire HD con Tapatalk 2
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Sd-ext does not use any Android's management of anything. For further assistance, I will need a complete log from M2SD with debug enabled.

Off Topic

About External/Internal sdcard (Storage Partitions, not sd-ext), when attaching the phone to the computer via UMS or MTP (Whatever is used by the device), it should provide access to both partitions. And inside Android, a good file manager like ES Explorer or Solid Explorer is a great tool for managing once storage spaces, Solid is even better than whatever you can get on your regular PC, whatever OS you are running.
[Android Software/Hacking General [Developers Only]] Daniel D.:
Is it possible that the app won't work or produce errors if I have not enough internal space? Currently I've 40 MB free space and want to use the app. Every boot there are errors that data/app/private couldn't be copied to sd-ext. I use an EXT4 partition with Lupus kernel.

https://docs.google.com/file/d/0B2BjC2gRHSTnNGx0bW4xN3Z0TTg/edit?usp=docslist_api

This is my log. Sorry for providing only this log, but I'm on my phone.