yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Fit GT 5670] misha1996:
Stock :D

Отправлено с моего GT-S5830i через Tapatalk
[Samsung Galaxy Fit GT 5670] Abhishek_DK:
Check this out Stock based on awesome touchwiz

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

hit thank too...:good:
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] VillaVor:
To the point it happen after installing lewa os rom with percy kernel. cwm based couldnt load everytime i press vol up+lock button+home button. It just shows Cwm based recovery blah blah blah and then reboot again Plus i couldnt reach odin anymore.

Can't do anything restore my backup or flash new rom.Want to figure any system file but File explorer just load sdcard directory when i installed Es file explorer it give me force's close. Factory reset not working at this rom.

From where i flash any rom etc ??
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] TheFixItMan:
maybe your sd card is corrupt - you can try formatting it either on your phone or on pc (fat32) - backup to pc first if possible

you can also flash stock rom via odin

install samsung usb drivers

download firmware from my firmware thread at top of 5360 dev section (duos see your own threads)

turn phone off

put phone into download mode (hold vol down home button then keep holding and also hold power button)

conect usb cable to pc

press vol up to start connection

wait for drivers to install

open odin 3.07 (other version may also work)

if connected it will say com then a number in a coloured box under com:id on the left hand side

put csc in csc

put phone in modem

put pda in pda

flash and wait for phone to auto restart and boot
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] VillaVor:
First, sdcard was fine as i said i can open sdcard directory via file explorer and i just want to figure out the system file which in /system directory so i used another file explorer such es file explorer but it given me force's close everytime i open it. maybe will install another explorer.

Second, As i said too in my another thread. Cant reach odin and mass storage or debug mode due to my phone's usb port problem, yeah you know what i mean.

So, any methods to this hopeless phone? Cant flash anything without these cwm right.
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] TheFixItMan:
you can only flash things in stock recovery/cwm (depending on kernel being used) or odin

have you tried going into cwm without the sd card inserted?

if you have damaged your phone in some way to the extent the usb no longer works chances are you have damaged other things in the phone and should take it to a repair shop
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] VillaVor:
Got it.

Yes. Cwm or Odin :(

Done for it but not sure. Will do it again

I think so. will take it to service center. At this moment still survive with this rom until i can flash stock firmware.
[Galaxy Note 3 Q&A, Help & Troubleshooting] aln3al:
I have note 3 n900 this is no imei and I have z3x box and octopus box please how can I repair imei /???

and this picture of it
[Galaxy Note 3 Q&A, Help & Troubleshooting] jdomadia:
IMEI is not there? tack there from where u purchase phone, they all replace free.
[Galaxy Note 3 Q&A, Help & Troubleshooting] aln3al:
Thank you, but I want to fix it myself because the company did not fix it
[Galaxy Note 3 Q&A, Help & Troubleshooting] xclub_101:
Ask in the forums for those boxes (NOT here on XDA) about how/if the box can write IMEI for N900.
[Moto G Q&A, Help & Troubleshooting] KuGeL94:
Just a couple of questions regarding our Moto G.

In this summer Google maybe present the next Android Version 4.5 or something new maybe.

All the Nexus Devices are going to get the updates after that, if the Moto G still belongs to Google do you guys think it will get that update soon after the Nexus Devices too?

And now to my second question, if I install CM11, could I install a couple of Moto G Apps, like the Camera or Gallery or other Moto G Apps?

Well, that's all, hope to see some responses. :D
[Moto G Q&A, Help & Troubleshooting] denzel09:
For 1 question i think we ll have the next update. I hope so.
[Moto G Q&A, Help & Troubleshooting] xianuro:
I think asking about a yet to exist Android version is pointless. First let them present it, and we'll go from there.

As for the Moto's camera and gallery, search in the CM11 thread, the developer uploaded a flashable zip with those apps.
[Moto G Q&A, Help & Troubleshooting] KuGeL94:
Ok thank you, but there are several CM11 Threads, could you give me a link to where the flashable zips are?

Hopefully, the Moto G will get that not yet known updated as soon as other google devices :) moto G(oogle) :P
[Moto G Q&A, Help & Troubleshooting] xianuro:
Here you http://xdaforums.com/showpost.php?p=50581967&postcount=1651

And there's only one Official CM 11 Thread http://xdaforums.com/showthread.php?t=2608377
[Moto G Q&A, Help & Troubleshooting] KuGeL94:
Ok thanks
[Android General] Modding.MyMind:
Very insightful bro. Thanks for the share. I will definitely try this out. This may be my motivation to work on my Port Rom again. Was getting tired of wiping, flashing, wiping, flashing.... Was a nuisance and I unfortunately only have one device for my current model. This will be really useful to me in the future. Huge thanks again for letting me know about this thread.
[Android General] Modding.MyMind:
Hey, getting ready to do this now with a 2gig. Using it as a test run lol. Anyways, to confirm, you leave the first part as is, meaning, fat 32, but add three additional parts to make a total of four partitions within the sdcard. So for example, part 1 (fat32), part 2-4 (ext4) which those would be the system, data, and cache. I'm confident that is how it is done, but wanted to clarify. Will do it now and check back for a reply later lol. Meanwhile, this has also given me a couple of dev ideas :)
[Android General] russellvone:
Aww snap! Lol
[Android General] dreccon:
Trust your confidence. You are right!

If you have a large card and use MiniTool, you can "shrink" your main partition to make room for the additional three. This way it won't be wiped.

Sent from the 3rd dimension!
[Android General] Modding.MyMind:
Outstanding, just finished partitioning it. Will tackle the boot.img now.
[Android General] dreccon:
One additional piece of info. Be extra careful if your secondary ROM supports OTA updates which are applied from recovery. Only download but NEVER apply them before you tweak the zips. Otherwise they will overwrite your primary ROM!

Sent from the 3rd dimension!
[Android General] Modding.MyMind:
Not unless I make a change with the recovery ;) lol

Anyways, I am still messing with my boot.img the fstab file for my device doesn't contain a list of mount points.

This is really the only thing it has as far as partitions are listed:

userdata/dataext4noatime,nosuid,nodev,noauto_da_alloc,discardencryptable=extra
[Android General] russellvone:
Here's HTC OneSV K2_CL recovery.fstab

# mount pointfstypedevice[device2]

/boot emmc/dev/block/mmcblk0p20

/cacheext4/dev/block/mmcblk0p36

/dataext4/dev/block/mmcblk0p37

/devlogext4/dev/block/mmcblk0p25

/miscemmc/dev/block/mmcblk0p22

/int_sdvfat/dev/block/mmcblk0p38

/recoveryemmc/dev/block/mmcblk0p21

/sdcardvfat/dev/block/mmcblk1p1 /dev/block/mmcblk1

/systemext4/dev/block/mmcblk0p35
[Android General] Modding.MyMind:
Thanks bro, i was actually trying to remember where that file was at haha.
[Android General] russellvone:
And the fstab.k2cl is found in the source code, I'm not sure it's in the finished boot.img
[Android General] Modding.MyMind:
It is in the boot.img, I just ended up having a blonde moment when looking for the fstab recovery file haha. I knew it would have the correct info for me.
[Android General] russellvone:
[MENTION=5537766]Modding.MyMind[/MENTION]

Could you post the fstab.k2cl in text form here please sir
[Android General] Modding.MyMind:
Here you go. That is all of it lol

# Android fstab file.
#
# 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

userdata/dataext4noatime,nosuid,nodev,noauto_da_alloc,discardencryptable=extra
[Android General] dreccon:
Is this from a JB or KK ROM?

Sent from the 3rd dimension!
[Android General] Modding.MyMind:
JB 4.1.2
[Android General] dreccon:
Then you might want to look for the mountpoints in the init.rc file also in the ramdisk.

Sent from the 3rd dimension!
[Android General] Modding.MyMind:
Already snooping around lol
[Android General] Modding.MyMind:
K2_CL info (I am wondering if I just apply the needed info to that fstab file if whether or not it will accept and read it)

rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
none /dev/timer_group cgroup rw,relatime,timer_slack 0 0
/dev/block/mmcblk0p35 /system ext4 ro,relatime,data=ordered 0 0
/dev/block/mmcblk0p37 /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p36 /cache ext4 rw,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/mmcblk0p25 /devlog ext4 rw,nosuid,nodev,noatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p32 /carrier ext4 rw,nosuid,nodev,noatime,grpid,data=ordered 0 0
/dev/block/mmcblk0p16 /firmware_radio vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p17 /firmware_q6 vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
htcfs /data/htcfs fuse.htcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/block/vold/179:38 /storage/sdcard0 vfat rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0202,dmask=0202,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,tz=UTC,errors=remount-ro,discard 0 0
/dev/block/vold/179:38 /mnt/secure/asec vfat rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0202,dmask=0202,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,tz=UTC,errors=remount-ro,discard 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:65 /storage/sdcard0/ext_sd vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[Android General] :
I believe I have figured it out. For my device, that fstab file won't be touched. It will require something a little more tedious. Will try it out and see how it works.

Edit: [MENTION=2863096]dreccon[/MENTION], and [MENTION=5089229]russellvone[/MENTION], I got it to work ;) lol. Using the fstab.k2cl file wouldnt work. I had to make some modifications within other files. I got a stock odexed rom as primary and a stock deodexed rom as secondary. Sickest part is how fast it booted it up. Normally, when booting a deodex rom for the first time, it seems like it takes forever, however, on the sdcard, it booted up faster than the stock OS hahaha.
[Android General] :
I decided to try flashing a zip using the secondary rom to see how it would pan out. Seems there is a problem with that lol. In order for the recovery to work alongside with the secondary rom there would be some needed additional editing. For example, I tried flashing a root zip for the secondary rom but it was flashing it to the primary because that is how the recovery is currently coded to operate. So, one or two things can be done. Either edit the recovery.img to make it a dual also, or, create an additional partition on the sdcard specifially for the recovery.img itself, but it would still require some editing. This is rather interesting lol. I did notice, that by having a secondary rom, it can get you out of bricking your device, and some other things as well. Definitely a sick idea. Again, thanks for this thread bro :)
[Android General] dreccon:
[MENTION=5537766]Modding.MyMind[/MENTION]

I guess the fstab.x file works only in AOSP based ROMs. I have edited the OP to include this info.

Edit: The rest of this post is obsolete. The zip editor is now available for download in 2nd post.

Sent from the 3rd dimension!
[Android General] :
Sounds good. I plan to mess with this some more. Seems ours requires a little more extra work on the instructions to setting up the dual boot right.
[Android General] dreccon:
Thanks! I believe this is because you're installing a stock-based ROM as secondary. AOSP based ROMs should go as described.

Any ideas how to detect the boot partition by terminal command? I've tried with mount, df and cat and I can't see it anywhere. For now I'm just planning to read it from the installation zip assuming that the user is not providing the wrong one...!

Sent from the 3rd dimension!
[Android General] :
Hmmm, do you mean,

[COLOR="red"]cat /proc/emmc[/COLOR]

u0_a206@android:/ $ cat proc/emmc
dev: size erasesize name
mmcblk0p22: 000ffa00 00000200 "misc"
mmcblk0p21: 00fffe00 00000200 "recovery"
mmcblk0p20: 01000000 00000200 "boot"
mmcblk0p35: 54fffc00 00000200 "system"
mmcblk0p29: 00140200 00000200 "local"
mmcblk0p36: 0dfffe00 00000200 "cache"
mmcblk0p37: 49fffe00 00000200 "userdata"
mmcblk0p25: 01400000 00000200 "devlog"
mmcblk0p27: 00040000 00000200 "pdata"
mmcblk0p38: 1097fe000 00000200 "fat"
mmcblk0p30: 00010000 00000200 "extra"
mmcblk0p32: 01900000 00000200 "carrier"
mmcblk0p16: 02d00000 00000200 "radio"
mmcblk0p17: 00a00000 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p18: 00500000 00000200 "wcnss"
mmcblk0p19: 007ffa00 00000200 "radio_config"
mmcblk0p23: 00400000 00000200 "modem_st1"
mmcblk0p24: 00400000 00000200 "modem_st2"
mmcblk0p31: 00040000 00000200 "skylink"
mmcblk0p33: 00100000 00000200 "cdma_record"
mmcblk0p34: 04729a00 00000200 "reserve"
u0_a206@android:/ $
[Android General] dreccon:
[MENTION=5537766]Modding.MyMind[/MENTION]

Wow! Can I press multiple thanks for once?

I have undertaken a tedious job here. I must confess that I can't claim to know bash, so for every function that I need, I have to search if there even exists a command that does it and then learn its syntax. Right now I'm learning awk and the use of pipes. This will put into good use the command you just told me! As you can see in my profile, my job is irrelevant to tech, so your assistance here is gold to me. Thank you once again!

Sent from the 3rd dimension!
[Android General] dreccon:
I promised scripts, right?

Well, you can find the first set in my second post!
[Android General] dreccon:
[MENTION=5177633]amazing 3D[/MENTION],

Nice to see you here! Too bad the ZipEditor doesn't work for the Optimus 3D. The LG boot.img is packed in a non-standard way and Modding.MyMind's executables can't handle it. You can still use the info on 1st post to manually edit your ZIPs and boot images.

Sent from the 3rd dimension!
[Android General] amazing 3D:
Nice to see u too buddy

I came here just wanted to Thank u because u realy deserve it.

and also to know as much info as possible about dual booting.

Keep up the good work buddy: )
[Android General] Flashalot:
Nice guide followed it from the Evo 3D tried to partition the SD on my HTC One S But Can't Get I think it may be because of the fused SD Card type but the think I may be able to force it with a tool on PC any input on this would greatly appreciate it
[Android General] dreccon:
I wouldn't mess with the internal SD. Can't you get an external one? Not that it's impossible but it would would require experience on your behalf.

Edit: I have read the specs of your phone and I've seen it doesn't have a card slot, so you're stuck with the internal storage. You can still create new partitions but not on your PC, only on the phone itself using AParted. You'll have to find which one of your internal partitions is your storage, wipe it and create a smaller one leaving the necessary empty space for your secondary ROM partitions. Create the three new partitions in that space. Of course, you can't use the automated zip editor and when you edit your zips manually, your secondary ROM partitions will NOT be mmcblk1px but mmcblk0px (the ones you just created). If you are not experienced enough, then show this thread and this post to somebody from your device forum who is and who may put up a device-specific guide based on this one.

Sent from the 3rd dimension!
[Android General] :
His should be mmcblk0p36. He sent me his boot.img and recovery.img. Just got done reviewing both of them on my phone. He can follow your guide without any problem and he can use my binaries to unpack and repack his images if he chooses to. But yea, he has no choice but to use his internal sdcard to accomplish dual booting.
[Android General] dreccon:
[MENTION=4678269]Flashalot[/MENTION]

Well, this idea of dual-boot can be expanded to also work with a USB flash drive, but that wouldn't be very practical, unless you have a docking station and you want a different OS when it's connected!

So, according to Modding.MyMind, if your storage partition is mmcblk0p36, you should wipe it and create a new one in its place which will be fat32 again but smaller by the added sizes of your system+data+cache partitions.

In the empty space, create your new ext4 partitions. System2 will be mmcblk0p37, data2 mmcblk0p38 and cache2 mmcblk0p39 (instead of 1p2, 1p3 and 1p4 as described in 1st post).

Sent from the 3rd dimension!
[Android General] :
[MENTION=2863096]dreccon[/MENTION], currently looking at your scripts. Wanting to see if I can adapt them to my cause lol. Just trying to figure out where to start haha :)
[Android General] dreccon:
If you want, I can adapt them to your guide.

Sent from the 3rd dimension!
[Android General] :
[MENTION=2863096]dreccon[/MENTION] and [MENTION=5089229]russellvone[/MENTION], I was looking at the vold.fstab file.

For my device it looks like this:

dev_mount sdcard /storage/sdcard0 emmc /devices/platform/msm_sdcc.1/mmc_host
dev_mount sdcard2 /storage/sdcard0/ext_sd [COLOR="red"]auto[/COLOR] /devices/platform/msm_sdcc.3/mmc_host

Take a look at what I highlighted in red above...

I currently have fat32 set for the first partition of my sdcard. So if I change it to:

dev_mount sdcard /storage/sdcard0 emmc /devices/platform/msm_sdcc.1/mmc_host
dev_mount sdcard2 /storage/sdcard0/ext_sd [COLOR="red"]1[/COLOR] /devices/platform/msm_sdcc.3/mmc_host

What would the results be? Lol. This is more of a rhetorical question haha. Basically, I am trying to grasp a workaround where all you need to do is simply put the sdcard in your phone and the Rom will boot immediately upon starting up (like the Nooks do with CM Roms and probably other roms as well).

Thinking out loud :)

---------- Post added at 05:35 PM ---------- Previous post was at 05:25 PM ----------

Or, maybe, setting either the third or fourth partition to fat32 instead?
[Android General] russellvone:
[MENTION=5537766]Modding.MyMind[/MENTION]

Thanks for tagging me, but ummm, this is beyond my knowledge. I don't mean to throw out ask my personals, but I'm currently 3 weeks into a 6 year old relationship breakup..... You guys keep up the awesome work! I'll be back full throttle once everything settles down.....
[Android General] dreccon:
[MENTION=5537766]Modding.MyMind[/MENTION]

Interesting...

The "auto" probably means the first mountable partition, or it may mean the first fat32 partition. Setting it to "1" would make no difference. I guess it wouldn't hurt to try. Worst case scenario, you won't be able to see your SD storage until you undo your changes and reboot.

Still, why would you want to change the position of the fat32 to other than 1? If you do, you'll have to edit the vold.fstab of your primary ROM too. The point of dual boot is to leave your primary ROM intact, right?

BTW, /proc/emmc does not exist in all Android devices. I guess I'll have to improvise...

Sent from the 3rd dimension!
[Android General] russellvone:
[MENTION=2863096]dreccon[/MENTION]

Example path

/dev/block/platform/msm_sdcc.1/by-name/

There will be a block similar to this

cd /dev/block/platform/mms_sdcc.1/by-name

Then

ls

Try something like this
[Android General] :
Been looking at the Nook. In lamen terms, what they do is they create four partitions, sometimes five, but the layout will simply be part1 - boot (fat32), part2 - system (ext*), part3 - data (ext*), part4 - sdcard (fat32).

For the "boot" partition, or partition 1 of the sdcard, they place a few files which get the boot.img for that secondary Rom to load up upon starting the device. Basically, there really is no need of flashing a boot image and/or dualboot image for primary/secondary roms.

Editing the vold.stab file is one way they go about it to allow this to work.

So, basically, think of it as burning a Rom image to an sdcard like you would burn something to a disc on a pc, but you aren't really burning anything. Then, all you have to do is just put the sdcard in to your device (or a Nook since I am referring to that), and then just power up the device, or if the device is already on, then just reboot. When the phone turns on, voila, secondary Rom is displayed on your screen. Then later on, you just remove the sdcard, and boom, primary Rom.

---------- Post added at 09:30 PM ---------- Previous post was at 09:29 PM ----------

I want to aim for this on my device needless to say haha
[Android General] Codename13:
I was looking at this and thinking - wouldn't this degrade the sdcard life pretty quickly? Would the constant reading and writing to the sdcard not kill it? What type of sdcard is needed (Class-wise) and what should the minimum read speed be? Also, do the partitions made on the sdcard have to be as big as the system, data, and cache partitions? Thanks to whoever answers this, because I would be really interested in doing this for my device while I am developing CM10.2 for it, because not everything works on it or as well as on stock ROM. I guess I'd need to get a bigger micro sdcard because mine is 2 GB and my system, data, and cache partitions are 3.5 GB in total. And one more thing - would SELinux interfere with any of this, especially if the internal ROM is ICS (which has no SELinux) and the external one is JB/KK (with SELinux)?