yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Mini Android Development] Android-Andi:
17.09.2014

1.5.4 -> 1.5.5

- get rid of DVFS limit without breaking Stock 4.1 or Android 4.3 / Android 4.4

thanks [MENTION=5562153]LuuchoRocha[/MENTION] and [MENTION=4832589]cocafe[/MENTION]

Sidenote:

Maybe some of you know Recognized Developer "DerTeufel1980" (Hellybean & Hellkat Roms or his great dual-boot "Devil" Kernel), i'll meet him today, hopefully he can help fixing USB on Stock :)

Stock 4.1 also seems not to work, still looking for a way to fix it.

New Blackhawk Recovery later, compileing right now,

[MENTION=4021423]ketut.kumajaya[/MENTION] found an derp and fixed it - maybe there have been too many changes since first blackhawk recovery :)
[Galaxy S III Mini Android Development] meduza:
...looking forward to new recovery!

m.
[Galaxy S III Mini Android Development] samnettt:
is the flickering and black screen bugs still present during flashing 2nd ROM?

also when nexttool-0.2-golden.zip is flashed ?
[Galaxy S III Mini Android Development] Android-Andi:
[MENTION=5562153]LuuchoRocha[/MENTION] does USB working for you on StockRom using your kernel?

[MENTION=4898082]samnettt[/MENTION] blackscreen / flickering gone. NEXT Tool not needed, run from advanced options inside philz touch. it is added to the recovery and can be run without flashing.
[Galaxy S III Mini Android Development] Android-Andi:
New PhilZ Touch Blackhawk Recovery http://xdaforums.com/devdb/project/dl/?id=8635
[Galaxy S III Mini Android Development] meduza:
...unfortunately backup of data on the second partition still not working... :(

Strange thing happend though, After the procedure of flashing new recovery, trying backup, flashing new kernel, I lost my file manager app(!) and had to restore it with TB ??!?

m.
[Galaxy S III Mini Android Development] Android-Andi:
[MENTION=4662107]meduza2[/MENTION] nothing changed that could have cause you are loosing filemanager. TWRP mode? I.never used it, and if i got right on my mind TWRP mode not working correctly on all devices.

About the backup not working:

i will contact [MENTION=4021423]ketut.kumajaya[/MENTION]

>> Backing up /data...
E:Unable to find mounted volume: '/data'
I:/data locked in 2nd recovery!
E:Error while making a backup image of /data!
press any key to continue.

(...)

Backup of system completed.

>> Backing up /data...
Unable to find mounted volume: /data
E:Error finding an appropriate backup handler.
press any key to continue.

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Android Development] jstath1972:
You've got right. The same problem with PhilZ Touch "TWRP mode" has the Tab 3. I know that because i had it. :crying:
[Galaxy S III Mini Android Development] meduza:
[MENTION=5153662]Android-Andi[/MENTION],

I tried both CWM & TWRP mode...

With the FM this wasn't a big problem, just very strange... .Maybe because I moved the app to external SD... but at the other hand I moved some apps and they are there... Well, what ever :)

m.
[Galaxy S III Mini Android Development] Android-Andi:
Lets wait for ketut. He seems to be really busy atm, got no answer om my last pms about usb for stock... also DerTeufel1980 could not help... just a small meeting today. :(

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Android Development] albertusac:
Thanks for the great Kernel, it's controlable now :D
[Galaxy S III Mini Android Development] ketut.kumajaya:
TWRP backup mode will not work in the 2nd recovery since there no real block device for /data but bind mounted /data/media/.secondrom/data as /data, the 1st recovery should work.

Please check updated dual boot tool: https://github.com/kumajaya/android_device_samsung_lt01-common/commits/cm-11.0-philz
[Galaxy S III Mini Android Development] Android-Andi:
Thx [MENTION=4021423]ketut.kumajaya[/MENTION]! I'll update Next Tool later today and recompile PhilZ.

Backing up 2nd Roms data also not working for normal backup, it also fails. Meduza2 posted a whole recovery.log on last page.

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Android Development] samnettt:
thanks Andi,

hope you will update it to the main post so that the new users can try without worries

thanks again
[Galaxy S III Mini Android Development] Android-Andi:
[MENTION=4898082]samnettt[/MENTION] 1.post got updated directly when i fixed it ;) all known problems mentioned there.

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Android Development] ketut.kumajaya:
Please check attached recovery log.
[Galaxy S III Mini Android Development] ketut.kumajaya:
Thanks [MENTION=5153662]Android-Andi[/MENTION] https://github.com/kumajaya/android...mmit/e58ad67c729a049552bc84c363ba7d18f276cd2e
[Galaxy S III Mini Android Development] albertusac:
The frequency bounces like the problem where we catch :(
[Galaxy S III Mini Android Development] Android-Andi:
Thanks a lot :)

Just one question

if /sbin/busybox [ $(/sbin/busybox mount | /sbin/busybox grep "/cache" | /sbin/busybox grep -c "HIDDEN") -eq 1 ]; then
/sbin/umount /cache
fi

We don't use by-name, we only have real block :p do i need to replace "HIDDEN" with something else?
[Galaxy S III Mini Android Development] ketut.kumajaya:
Just replace it with appropriate 2nd recovery/ROM /cache block device (mmcblk*p*). And I found a bug (again), my previous data-free.sh fix not really fix /data free space information :( Please change:

# Extra space from system.img
if /sbin/busybox [ -f /data/media/.secondrom/system.img ]; then
FREESPACE=$(($FREESPACE + $(busybox ls -s /data/media/.secondrom/system.img | busybox cut -d " " -f3)))
fi

to

# Extra space from system.img
if /sbin/busybox [ -f /data/media/.secondrom/system.img ]; then
FREESPACE=$(($FREESPACE + $(busybox ls -s /data/media/.secondrom/system.img | /sbin/busybox awk '{printf $1}')))
fi
[Galaxy S III Mini Android Development] Android-Andi:
Thanks a lot again [MENTION=4021423]ketut.kumajaya[/MENTION] !

<3 (:D)

I hope some of golden user bought you a beer or will do it now :)

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Android Development] Android-Andi:
Will upload NEXT kernel 1.5.6 & new PhilZ Touch recovery later. Recovery compileing right now.

Need to sleep 1 or 2 hours now - i had a really short night while trying to fix usb for stock :( i did not woke up with first 3 of my 5 alarmclocks in the morning ...

But i found a commit that fixes a warning in dmesg (sysfs: cannot create duplicate filename '/devices/virtual/switch/usb_audio').

Tested 1.5.6 allready,

will test the new PhilZ Touch after sleep.

Will upload both together then.

Stock on 2nd Rom still broken atm, still not sure why (system.img to small? hard to debug without a working usb connection, i'll try to get last_kmesg from recovery after booting failed ) :(

[MENTION=4021423]ketut.kumajaya[/MENTION] can you take a look on attached last_kmesg? SlimKat did not boot (got kernel panic) after applying "USB: initializing Android USB depending on the rom type" and setting needed config in defconfig - StockRom boots, but USB not working.
[Galaxy S III Mini Android Development] meduza:
Schlaf gut :)

(sleep well)

m.
[Galaxy S III Mini Android Development] Android-Andi:
Still backing up 2 nd rom failed... recompileing again...

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Android Development] Android-Andi:
19.07.2014

Update dual boot tool 0.3

- Create 1.5 GB dynamic growth sparse image

- Ext4 formatting fix

- Free space calculation fix

Adapted from Tab 3 8.0 - thanks to [MENTION=4021423]ketut.kumajaya[/MENTION]

NEXT Tool 0.3 will be included in next PhilZ Touch , atm still looking for a solution why backing up 2nd rom not working.

1.5.5 -> 1.5.6

- fixes a warning in dmesg (sysfs: cannot create duplicate filename '/devices/virtual/switch/usb_audio')

Dev-Info for [MENTION=4021423]ketut.kumajaya[/MENTION]:

I just pulled "/etc/recovery.fstab" and "/etc/fstab" from booted 2nd recovery

/etc/fstab

/dev/block/loop0 /system ext4 defaults
/dev/block/mmcblk0p11 /efs ext4 defaults
/dev/block/mmcblk0p24 /cache ext4 defaults
/.secondrom/media/.secondrom/data /data ext4 defaults
/dev/block/mmcblk0p12 /modemfs ext4 defaults

/etc/recovery.fstab

# 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/loop0 /system ext4 ro,noatime,nodiratime wait
/dev/block/mmcblk0p11 /efs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check
/dev/block/mmcblk0p24 /cache ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check
/.secondrom/media/.secondrom/data /data ext4 noatime,nosuid,nodev,discard,noauto_da_alloc,journal_async_commit,errors=panic wait,check,encryptable=footer

# Vold managed volumes (External SDCard)
/devices/sdi0/mmc_host/mmc1/mmc1 auto vfat defaults voldmanaged=sdcard1:auto

# Recovery
/dev/block/mmcblk0p12 /modemfs ext4 defaults recoveryonly
/dev/block/mmcblk0p20	/boot emmc defaults recoveryonly
/dev/block/mmcblk0p21	/recovery emmc defaults recoveryonly

Why am i getting this in recovery.log while backing up 2nd Rom?

checking ext4 <-> f2fs conversion...
get_real_fstype: unknown filesystem (/data)

recovery filesystem table
=========================
0 /system ext4 /dev/block/loop0 0
1 /efs ext4 /dev/block/mmcblk0p11 0
2 /cache ext4 /dev/block/mmcblk0p24 0
3 /data ext4 /.secondrom/media/.secondrom/data 0
4 /storage/sdcard1 vfat /devices/sdi0/mmc_host/mmc1/mmc1 0
/storage/sdcard1 auto /devices/sdi0/mmc_host/mmc1/mmc1 0
5 /modemfs ext4 /dev/block/mmcblk0p12 0
6 /boot emmc /dev/block/mmcblk0p20 0
7 /recovery emmc /dev/block/mmcblk0p21 0
8 /tmp ramdisk ramdisk 0

I:/data locked in 2nd recovery!
(...)
I:/data: tot size=0Mb, free=0Mb, backup size=0Mb, used=1547Mb, media=1547Mb
(...)
>> Backing up /data...
Unable to find mounted volume: /data
E:Error finding an appropriate backup handler.
press any key to continue.
[Galaxy S III Mini Android Development] ketut.kumajaya:
[MENTION=5153662]Android-Andi[/MENTION] Please restore back the original /data block device. Please recheck Tab 3 device tree, cm-11-philz branch.
[Galaxy S III Mini Android Development] Android-Andi:
Delete me: Why doubleposted?
[Galaxy S III Mini Android Development] Android-Andi:
I cross-checked already, at least 10 times :( https://github.com/andi34/android_d...-boot/recovery/root/res/misc/recovery.fstab.2

Send from OnePlus One using Tapatalk

Edit:

Maybe i flashed the wrong Recovery, will check again after sleep...
[Galaxy S III Mini Android Development] ketut.kumajaya:
My previous comment based on "3 /data ext4 /.secondrom/media/.secondrom/data 0" recovery log info.
[Galaxy S III Mini Android Development] Android-Andi:
I played around with the fstab,

Maybe i took the wrong log or flashed the wrong Recovery :p

I tried to run

busybox mount -t ext4 -o noatime,nodiratime,noauto_da_alloc,barrier=1 $DATADEV /.secondrom
/code] while 2. Recovery booted already, it failed because it could not find /.secondrom in fstab.
Inside the fstab mountpoint for /data was set with real block.

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Android Development] ketut.kumajaya:
[MENTION=5153662]Android-Andi[/MENTION] You have to use the recommended /sbin/mount and /sbin/unmount command to mount/umount a partition and mount/unmount /data partition will be always failed by design:

https://github.com/kumajaya/android...11.0-philz/recovery/root/res/misc/mount.2#L28

https://github.com/kumajaya/android...1.0-philz/recovery/root/res/misc/umount.2#L11

The recovery will be always refuse to umount /data by design:

https://github.com/kumajaya/philz_touch_cwm6/blob/cm-11.0/roots.c#L763

Mounted on boot and will never be unmounted by design:

https://github.com/kumajaya/android...11.0-philz/recovery/root/sbin/bootmenu.sh#L46

Not only the recovery, I also have to fool the nandroid backup :laugh:
[Galaxy S III Mini Android Development] Android-Andi:
Lol yeah, forgot that mount and unmount will be replaced. :D caused by not much sleeping...(?).

So any idea what could be wrong?

Maybe i am blind, but many times crosschecked my adapted changes...

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Android Development] ketut.kumajaya:
Please compare your local source to https://github.com/kumajaya/philz_touch_cwm6
[Galaxy S III Mini Android Development] Android-Andi:
Did yesterday again:

Different:

https://github.com/andi34/philz_touch_cwm6/commit/609122afc16507377cc73210794d54e065a4b5ac

And

https://github.com/andi34/philz_touch_cwm6/commit/634442df3a86ed0c5ef892c8f41ed9deb583a9db

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Android Development] ketut.kumajaya:
Looks good :confused:
[Galaxy S III Mini Android Development] Android-Andi:
Mh.... maybe busybox not working correctly? Maybe i should unmount /data first?

https://github.com/andi34/android_d...-boot-f2fs/recovery/root/sbin/bootmenu.sh#L47

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Android Development] ketut.kumajaya:
Please give me "mount" command output after recovery boot completed. Also please set more sleep time to https://github.com/andi34/android_d...-boot-f2fs/recovery/root/sbin/bootmenu.sh#L45 , 2 or 3.
[Galaxy S III Mini Android Development] Android-Andi:
Will do after work :)

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Android Development] ketut.kumajaya:
[MENTION=5153662]Android-Andi[/MENTION] Somehow /.secondrom/media/.secondrom/data not get mounted to /data. The possible caused, initially there's no /data directory in your ramdisk. Please try interchange https://github.com/andi34/android_d...-boot-f2fs/recovery/root/sbin/bootmenu.sh#L96 and https://github.com/andi34/android_d...-boot-f2fs/recovery/root/sbin/bootmenu.sh#L97 order.

EDIT:

Sorry, please add "mkdir -p /data" before https://github.com/andi34/android_d...-boot-f2fs/recovery/root/sbin/bootmenu.sh#L95
[Galaxy S III Mini Android Development] Android-Andi:
[MENTION=4021423]ketut.kumajaya[/MENTION] will try in the evening, some private life stuff to do or.my gf will kill me :D

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Android Development] ketut.kumajaya:
[MENTION=5153662]Android-Andi[/MENTION] "/sbin/mount" and "/sbin/busybox mount" is different. Your change should be:

# Bind mount /.secondrom/media/.secondrom/data to /data for transparent operation
# no real block device and always locked
[COLOR="DarkGreen"]+ mkdir -p /data[/COLOR]
mkdir -p /.secondrom/media/.secondrom/data
busybox mount --bind /.secondrom/media/.secondrom/data /data
mkdir -p /data/media

2nd recovery/ROM media directory should be inside /.secondrom/media/.secondrom/data
[Galaxy S III Mini Android Development] Android-Andi:
Does not work this way.

Just backed up 2nd Rom (SlimKat), deleted 1st rom.

after that restored SlimKat backup from 2nd Rom. No problems on 1st rom slimkat now.

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Android Development] Android-Andi:
Also setting wait to 2 did not changed anything.

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Android Development] ketut.kumajaya:
Sleep time change not required. Please confirm if data directory available by unpacking recovery.img

Please try install a clean 2nd ROM, make sure you delete /data/media/.secondrom/data first from 1st ROM or 1st recovery over "adb shell" or Aroma FM.
[Galaxy S III Mini Android Development] Android-Andi:
No, not inside.

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Android Development] Android-Andi:
Deleted 2nd Rom from next tool.

Ls -l does not show /data/media/.secondrom after that in 1st recovery.

Flashed next tool to create sparse image.

Flashed CM10.2 as 2nd rom. Flashed next kernel.

Booted CM10.2 without problems as 2nd rom.

Rebooted to run 1st rom (SlimKat), no.issues.

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Android Development] ketut.kumajaya:
This is the root of problem you experienced before :good:

I just committed important update, please check https://github.com/kumajaya/android...mmit/5968812fb96d22f3a52df62671bc9856cb3158f8 Now, it's much easier to port my solution to a new device.
[Galaxy S III Mini Android Development] Android-Andi:
I will adapt for tab2 and golden tonight :)

Thanks a lot! I love to learn from such a great develeoper and human! Without you i would never be at the point i am today!

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Android Development] ketut.kumajaya:
Without action you aren’t going anywhere -- Mahatma Gandhi
[Galaxy S III Mini Android Development] meduza:
[MENTION=5153662]Android-Andi[/MENTION] & [MENTION=4021423]ketut.kumajaya[/MENTION],

thank you guys for your efforts to make Phlz backingup the 2nd partition! I`ve faith in you :)

The first partition is not a problem because we can use an other recovery like andi`s TWRP for example to backup it.

m.
[Galaxy S III Mini Android Development] MounirHero:
[MENTION=4021423]ketut.kumajaya[/MENTION][MENTION=5153662]Android-Andi[/MENTION] Can you guys please explain me what is the difference between Dual Boot and Boot from SD Card? Thanks in advance..
[Galaxy S III Mini Android Development] Android-Andi:
[MENTION=4662107]meduza2[/MENTION] i adapted all changes now :) compileing now :)

[MENTION=5375824]MounirHero[/MENTION] faq in 3rd post.

We use the internal storage.

You can install 2 android systems at the same time. You can choose on boot which of both system boots. Maybe you need KitKat for daylie use and Stock 4.1 or AOSP 4.3 for some special function not working.on other roms. Maybe you.only want to test a rom without messing your current rom... there are some more reason. Developer also like it testing stuff on a 2 nd system.

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Android Development] meduza:
Great :) Can't wait to test...

m.
[Galaxy S III Mini Android Development] Android-Andi:
[MENTION=4662107]meduza2[/MENTION] no need to wait :D

New PhilZ Touch Blackhawk uploaded :)

http://xdaforums.com/devdb/project/dl/?id=8686

Backup 2nd rom is working now. I also changed menutext color to red, the blue does not look good on this small display, red looking more sharp.

Sometimes 1st recovery will take the red menu color from 2nd recovery, not sure why, but i or [MENTION=4021423]ketut.kumajaya[/MENTION] will find a fix for it.

Have a nice weekend together!

Enjoy the new Recovery and Dual-Boot-Tool to create a 2nd sytem.img!

I am out for this week (maybe find some time tonight, maybe not)
[Galaxy S III Mini Android Development] moonryder:
Ok

If am i right i have to flash NEXT kernel after flashing a ROM on the second partition every time. And this will replace the kernel of the "second ROM". So it is impossible to test the included kernel of this ROM...
[Galaxy S III Mini Android Development] :
So any instructions?
[Galaxy S III Mini Android Development] Android-Andi:
You can test other kernel on first Rom, only dualboot get lost.

Wipe in one recovery does not hurt the other rom.

You need to flash next kernel every time after a rom, no matter if first or second recovery - both roms use same boot partition.

I will add FAQ to 3rd post, maybe [MENTION=5051515]tetakpatak[/MENTION] can rework it later if necessary :)

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Android Development] daywalk3r666:
i am on an older release of omnirom(2.rom)...when i will update it...i must boot into the 2.recovery ...flash the update and then the next kernel?right?
[Galaxy S III Mini Android Development] Android-Andi:
Right.

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Android Development] Android-Andi:
FAQ added to 3rd Post - take your time and read carefully :)

Something i never forgot: respect other peoples works - that's why i am on the point i am now on Android Development:

I am still learning each day, i learnd most stuff from our great Developer Ketut P. Kumajaya ( [MENTION=4021423]ketut.kumajaya[/MENTION] )

- i think HE deserves a Beer instead donating to me ATM. If you like you can spend Ketut a beer using PayPal

He reworked my initial (not booting) boot.img and made all needed changes to get Dual-Boot work on our Golden :)
[Galaxy S III Mini Android Development] Android-Andi:
NEXT Kernel 1.0.1 uploaded

Changelog:

1.0.0 -> 1.0.1:

- fix "com.android.phone" crashed on Vanir Rom

Thanks [MENTION=5230062]daywalk3r666[/MENTION] for testing and confirm working.
[Galaxy S III Mini Android Development] moonryder:
Hi Andy,

This NEXT kernel does include all govs and scheds of the slim-kernel (3.031+) ?

Or is it totally different?
[Galaxy S III Mini Android Development] Android-Andi:
[MENTION=5835372]moonryder[/MENTION] It is the same kernel source ;) So yes, same as on my SlimKat builds.

Maybe i can also add InteractiveX and ZEN Sheduler, haven't added it yet because [MENTION=5384881]Fred6681[/MENTION] has it's own kernel.

Also will check later if Linaro really makes a differents.
[Galaxy S III Mini Android Development] moonryder:
Best combi is smartassV2 and deadline ;)
[Galaxy S III Mini Android Development] Android-Andi:
Uploaded NEXT Kernel 1.0.2

- fix an Superuser issue, added back init.superuser.rc

Sorry for the new update... :D

[YOUTUBE]78sHY43byb8[/YOUTUBE]
[Galaxy S III Mini Android Development] meduza:
...lucky me, still prepering the dual boot ;)

m.
[Galaxy S III Mini Android Development] meduza:
The recovery isn`t good, I couldn't restore any backups, I created with it :( Mostly md5 checksum problems. Disabling it or trying the TWRP mode didn't help... The restoring espacialy the advanced is anywhere confusing...

But dual boot worked with slim & vanir :)

Do the second ROM have to be always clean installed? Or could it be a backup...? I tryed that too but with no succes...

m.
[Galaxy S III Mini Android Development] Android-Andi:
You can also restore a Backup, but don't forget to flash the kernel after that.

Will check your reported issue later.

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Android Development] Android-Andi:
[MENTION=4662107]meduza2[/MENTION] no problems restoreing my just created backup as 2 nd Rom.

Only factory reset and clean to install a new rom does not work, getting fc after booting because some old stuff from vanir left :( deleting 2 nd system.img , recreate and wipeing after that in recovery Works.

Will ask [MENTION=4021423]ketut.kumajaya[/MENTION] if there are problems on his Tab3 for 2 nd recovery wipe.

Have not tested wipeing internal storage yet.

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Android Development] daywalk3r666:
battery drain is good with the kernel...0,9%/h and 98% deepsleep
[Galaxy S III Mini Android Development] mattiawhite:
May i say "that's just sick!"

Its like having 2 wife's!!

Wait, that actually could be a benefit!...

Hmm thank you for being so "sick" ;)
[Galaxy S III Mini Android Development] tetakpatak:
Correct, it is impossible to run rom's stock kernel on the secondar FS partition.

For testing any rom with its stock kernel, it must be installed on the primary FS partition.

tetakpatalked from the legendary i9000
[Galaxy S III Mini Android Development] ketut.kumajaya:
LOL :laugh:
[Galaxy S III Mini Android Development] meduza:
report

Slim & Vanir with different runtime are running on dual boot :)

I tryed to restore a vanir backup (using twrp mode in philz recovery) instead of installing a fresh vanir but only system was restored, data not :(

But to be honest, it doesn't metter :) I`ve now two great updated ROMs on dual boot! This is just great :)

m.
[Galaxy S III Mini Android Development] daywalk3r666:
great work...thx

Gesendet von meinem GT-I8190
[Galaxy S III Mini Android Development] ketut.kumajaya:
[MENTION=5153662]Android-Andi[/MENTION] Dual boot solution help me debugging Sammy to make a better AOSP port, boot to Sammy when I need a better camcorder :laugh: Since my development device also my daily communication device, I always have an option when so tired fixing no booting AOSP port :victory: