yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Mini General] llbranco:
don't flash yet, even with this fixies

---------- Post added at 06:14 PM ---------- Previous post was at 06:09 PM ----------

only extracted using 7z... corrupted when i try to use winrar (or even unrar)

where I need to drop and how to upgrade using this boot.img file?

edit:

my fault, on the root of "zip file"
[Galaxy S III Mini General] xda tuerkrom:
You can edit the boot.img with Image Kitchen!
[Galaxy S III Mini General] llbranco:
ow, sorry

my bad

I mean about ".rar" file, not "boot.img"

hahaha

sorry

---------- Post added at 07:44 PM ---------- Previous post was at 07:44 PM ----------

ow, sorry

my bad

I mean about ".rar" file, not "boot.img"

hahaha

sorry
[Galaxy S III Mini General] xda tuerkrom:
Ok.

I have packed the boot.img in rar
[Galaxy S III Mini General] Sebeq1:
Another "update-binary" file.
[Galaxy S III Mini General] llbranco:
still unflashable :(

wipe+kernel+cm11 + updatebinary+updatescripts+all other files posted by [MENTION=6997497]Sebeq1[/MENTION]

:(
[Galaxy S III Mini General] Sebeq1:
Can you quote the updater-script?
[Galaxy S III Mini General] llbranco:
update-script

my zip file don't have install-script
[Galaxy S III Mini General] Sebeq1:
Can you quote errors appearing during installation?
[Galaxy S III Mini General] llbranco:
how to get logfile from device? (I just type what is displayed, it's not a full log)
[Galaxy S III Mini General] Sebeq1:
Maybe logcat...

Another "updater-script" file.
[Galaxy S III Mini General] llbranco:
I found some problems...

set_perm(0, 2000, 0755, "/system/bin/hostapd");

set_perm(0, 2000, 0755, "/system/bin/clatd");

those files are missing and probable have some more files missing

(I changed from Philz touch to TWRP, now I can copy recovery.log to SDCARD)

now trying to install without those lines
[Galaxy S III Mini General] Sebeq1:
All binaries please extract and copy to "/system/bin" to add missing/update existing binaries.
[Galaxy S III Mini General] xda tuerkrom:
Good work!

Sorry I have no Times i would work later next.
[Galaxy S III Mini General] llbranco:
cm11(from 1st post ~170MB), baroni kernel, TWRP, boot.img updated, update-binary and update-script updated and all binary files updated too

installed successfuly

but, black screen on boot no bot animation, no animation on charge

cm11(from other post ~325MB), baroni kernel, TWRP, boot.img updated, update-binary and update-script updated and all binary files updated too

install fail
[Galaxy S III Mini General] llbranco:
accumulated updates (by: [MENTION=7239418]xda tuerkrom[/MENTION] and [MENTION=6997497]Sebeq1[/MENTION]

(boot.img, update-binary, update-script, bin files, media files etc)

this is unflashble, its to update your flashable cm... just all updates inside
[Galaxy S III Mini General] [S]hadoW:
I thınk only problem is kernel for now
[Galaxy S III Mini General] xda tuerkrom:
I think too the problem is Kernel.We must create new Kernel or edit the baroni for i8200 only for cm 11 rom.
[Galaxy S III Mini General] OwellR:
It works already or still has errors ?
[Galaxy S III Mini General] llbranco:
I was tested with THIS TWRP (http://xdaforums.com/galaxy-s3-mini/general/s-iii-mini-ve-i8200-n-t2826565) (outdated no SELINUX support)

now I flashed this one (http://xdaforums.com/galaxy-s3-mini/general/kernel-baroni-kernel-alpha-t2976241) but still stuck on black screen.

no charging animation too

:(

waiting for more things to test
[Galaxy S III Mini General] pdalfarra:
Good luck with kernel modification! Thanks a lot for all your work and efforts!! :)
[Galaxy S III Mini General] xda tuerkrom:
Thanks!I start morning with kernel modifications.I hope the new kernel will work for cm11.
[Galaxy S III Mini General] SolarPlexus:
Which Kind of changes you will do on the kernel? I' m still puzzled what your migrating process include for the ROM. What are the steps you do while the migrating? If you really want to know what happens then you have to read the early stage of kmsg and catlog with adb binding (which is activated on my kernels). There you will see which module will stuck, and what did not start.

Gesendet von meinem A0001 mit Tapatalk
[Galaxy S III Mini General] xda tuerkrom:
Device can't boot with your kernel.
[Galaxy S III Mini General] xda tuerkrom:
You can help me!Can you please try port your kernel to cm11?
[Galaxy S III Mini General] pdalfarra:
Hi,

From your profile, comments and device list, i.e., "Samsung S III Mini - I8200N (on Stock but Baroni Kernel )" it looks like your are knowledgeable about ROM and kernel (re)crafting. Would you consider 'joining your force" with [MENTION=7239418]xda tuerkrom[/MENTION] ?

By the way, do you know about any initiative to get cm 12+ on Samsung S III Mini - I8200N ?

(main point is to have ART running fine .. should be the case with cm11, but I suppose ART is 'better/faster/stronger' in cm12+, is it)

Thanks ;)
[Galaxy S III Mini General] SolarPlexus:
Sorry, but for me is still unclear:

How do you port the Rom?

Why do you think my kernel is the problem?

I'would pleased to help, but I remember, what you did in the past, and you never explained what your porting process is. You started to port Roms from a completely different hardware basis, and for me you did not really know how a rom works. Maybe I'm wrong, but just to copy files from one zip into a other, and modifying the build.prop is not enough.

What I can try is to include all hardware related modules in the kernel, but the most common problem is to adapt the innit process that the drivers are called in the right way. You can not just copy the kernel to the new initram.fs, you must also made some work there... Anyhow we can try to made that as blank as possible, and then maybe the phone will start, but no data, wlan or whatever will then work...

So as requested before: What is your porting-process. If you did not want to explain it here, you can send it also per pm to me. If I did not understand what you do, I can not help you so much..

---------- Post added at 09:00 ---------- Previous post was at 08:44 ----------

As I'm the maintainer of Baroni-kernel, I think you're right. But this is all learned the hard way, and I'm not finished. I've tried several times to understand what XDA-Turkrom did, but unfortunatly he did not explain, so it is not really possible for me to join our forces... Let me state it in that way: this phone is far away from a stable new rom, as Samsung has blocked every knowledge on it, and no other developer with more experiance is working on it. To small profit to made a rom for this phone for them... Better to made the next of thousends avalible roms for a well documented device... So no, I did not know any progress from someone for a cm12+ rom... We are clearly alone here. And my time is not free, as I have a lot of other work,m so I need a clear picture to do something...
[Galaxy S III Mini General] pdalfarra:
Hi,

I just read [MENTION=3470903]SolarPlexus[/MENTION] 's post#161 and it looks like you he could help (a bit) if you write some documentation about what you have done.

This could be a great way to share your knowledge with him and, possibly have new people helping. I am sure a clear documentation (not have to be that big, but surely accurate) could help any 'ROM maker' to join this thread, and help you to have the "CM 11 for S III Mini VE 8200N" job done.

No matter how complex/simple, great / not so great is the job you have done so far, it's surely worth documenting it ;)

Thanks a lot for your efforts and determination to make this work: this is awesome :good:
[Galaxy S III Mini General] xda tuerkrom:
1. Create new folder where you want and name it « Rom port for i8200 »

2. Download Stock or custom rom for you device which the rom you want to port

3. Download the rom you want to PORT

4. Extract each zip ROM in separate folder in « Rom port_for i8200 »

5. Now it will appears two folders. Open both.

In PORT folder delete META-INF folder and copy/paste the META-INF folder of BASE in PORT folder.

6. Open system folder in PORT rom and delete vendor folder

7. Now in PORT folder open lib folder and delete these folders :

modules

hw

egl

8. Now go in BASE folder and select (if exists) these folders :

addon.d

bin

etc

customize

framework

lib

vendor

xbin

Now open build.prop of PORT rom and replace these lines with BASE build.prop :(example)

ro.product.model=

ro.product.brand=

ro.product.name=

ro.product.device=

ro.product.board=

ro.product.cpu.abi=

ro.product.cpu.abi2=

ro.product.manufacturer=

ro.board.platform=

ro.build.product=

ro.product.brand=

ro.product.name=

ro.product.device=

ro.product.board=

ro.product.cpu.abi=

ro.product.cpu.abi2=

ro.product.manufacturer=

ro.board.platform=

ro.build.product=

#

# system.prop for goldenve3g

#

--------------------

Open dsixda's Android Kitchen

Decompile both boot.img/kernel

Open both init.environ.rc files

In baroni kernel replace BOOTCLASSPATH by the one from PORT boot.img ROM

In baroni kernel do these changes:

--> ro.secure=1 to ro.secure=0

--> ro.debuggable=0 to ro.debuggable=1

--> persist.sys.usb.config=mtp to persist.sys.usb.config=mtp,adb

--> ro.adb.secure=1 to ro.adb.secure=0

Save and recompile kernel

Use modified kernel in your rom. (this way is not working on cm11)

-----------

Now ZIP the PORT rom and sign with zipsigner.

I have ported the cm11 Rom with this Way.
[Galaxy S III Mini General] SolarPlexus:
after deleting the vendor folder, what you put there as the replacement? To explain: this folder contains specific files, which can not be compiled, because its closed source. So you need in this directory files for your device. If empty, the phone can not work properly.

here the same, if you delete this three directorys you delete specific device dependend files, and additionaly the egl-settings for the right work of the display... What will you use here as a replacement?

I guess you mean not only select, but copy? If yes, then your rom will not be able to work, because the Framework is an essencial Rom specific stuff. If you copy that from the old rom, then the new rom with a other version as the source will not work (its the same for the other folders more or less).

You will have no success with Androids kitchen (or other standart Kernel tools like Makeinitfs), because the bootloader of i8200 has problems with the zip-magic-Bytes. Only the manual packaging with Linux tools will work.

For the settings, you can send me the BOOTCLASSPATH, which you whant to should have in the kernel. But as far as I remember this should be the same for the specific rom version... The other settings I think I've made them as a standart in my kernel... But I have to recheck, maybe this was only on my private Dev-Kernel...

So to sumarize, if I understand it right: Your modifications seems to be not complete, and the modified Kernel will not work. And this are the only points I see... As I write sometimes bevore: its not just only to copy some files together to port a rom to a new Android version. This will only work if you stay on the same Android-version (4.2.2 in our case).
[Galaxy S III Mini General] llbranco:
We need to make some kind of list with all devices with same hardware or even with same chipsets, cpu/gpu.

doing this we can try to port more things like using their source codes or even files.

I'll try to follow some guides to port CM or PAC-ROM (for 4.2.2 based)

(we need a Git-HUB to share our work)

c ya
[Galaxy S III Mini General] xda tuerkrom:
You can share me a guide of Rom port for i8200
[Galaxy S III Mini General] llbranco:
https://github.com/llbranco/cm10_gt-i8200

https://github.com/llbranco/cm11_gt-i8200

https://github.com/llbranco/cm12_gt-i8200
[Galaxy S III Mini General] [S]hadoW:
I think problem is kernel because i8200 have touchwiz os tw is different than others example :

You cant use cm system ui on tw because kernel isnt support it
[Galaxy S III Mini General] xda tuerkrom:
I mean too.
[Galaxy S III Mini General] SolarPlexus:
I'm not really sure what do you think??? Let me say in that way: If I have a guide to port a rom from a lower Version to a higher version, you can be sure then we still will have a rom. If it would be so easy, then I guess others will have more success. Maybe you can ask +PaulRichter, because I think he used also a similar way as you try.

But to be sure: to get really a stable rom, the only way will be to Complie it completley...
[Galaxy S III Mini General] xda tuerkrom:
Ok.

Sorry my english is not good.I live in austria.I try later port a android 4.2.2 rom to i8200 example:lewa os,slimrom,miui...

I must find Rom.

Sorry i can't help next port or fix for cm11.

I try find another source and try some roms to port.
[Galaxy S III Mini General] SolarPlexus:
What I generally understand is, that touchwiz is a sort of frameworks and launcher with several additional apps. normally the kernel take not care about that, except the framework needs some specific modules (lets say it needs more than a basis kernel, but to need more will normally not produce a problem). But maybe I'm wrong on that, and I'll investigate further. Nevertheless: what XDA Turkrom has done up to now can not work (I've explained it several times. I would appreciate it if I'm wrong, and he will made a working higher version rom with his way, but I fear - with what I have learned up to now - it can not work...)

What I can say is: I needed half a year to get the F*#@ing Kernel to work... And the biggest issue was, that one header in the kernel source contained a really old compiler bug what you can only found if you digging very deep on kernel debugging lists, and the repacking of the kernel was not possible with the standard android-tools. I can swear you: to made something for this phone is a big piece of #@!§%*#! (that's nothing to blame someone, its just reality...)
[Galaxy S III Mini General] PaulRichter:
When I tried to make a 4.3 rom I used stock rom as base and only edited the sdk line in build.prop so it can install and maybe run apps that were designed for android 4.3+ and make it look like aosp I didnt really port anything.

But that resulted in some force closes and bugs.

So I changed the thread to -How to run 4.3+ apps on GT-I8200/N/L/Q more complicated but at least stable.

I dont have any knowledge regarding kernel or rom only some basic stuff like editing system/app system/framework system/media or system/build.prop.

At least Im honest.
[Galaxy S III Mini General] llbranco:
what about to start make a research to find compatible devices and list it here, in order to make our work easier?

I think to make a Custom 4.2.2 1st, is a 1st step (even if it runs unstable), then we can try to make it more stable, finally we can try to port it to an unstable version of 4.4(for example) and make it more stable...

we can try to follow the same steps or working in different ways together
[Galaxy S III Mini General] person123321:
Good Idea i think the same. we should try to port an android 4.2.2 ROM then if we do that then try to move forward with trying to port android 4.4.

Sorry if I've said something wrong I have no real experience in porting roms/kernels
[Galaxy S III Mini General] llbranco:
take a look in these links

https://github.com/goldenvess3g

https://www.androiddevice.info/submission/2298/show

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

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

if you know Russian or don't care about gtranslator http://4pda.ru/forum/index.php?showtopic=209610&st=4720

I think it's useful

let's try to port from this ones

product.board	PXA986 (https://www.androiddevice.info/devices?search=PXA986)

cpu hardware	PXA988 (https://www.androiddevice.info/devices?search=PXA988)
[Galaxy S III Mini General] llbranco:
I'll try to port stock 4.2.2 from SM-T210/T211/T2105/T110/T111(or variants) to GT-i8200L

It's look insane but I'm not conversant ("familiarizado" in Portuguese) with ROM PORTING,

if it work I will try to port 4.4

if it work finally I will try to port CM or AOSP/AOKP based ROM (if exist).

(w/o source codding.)

if port w/o source codding won't work

I'll try to study a lot of things from CM Wiki and port it from source (perhaps, I don't know if my available time will be enough)

***this is not a promise or a commitment***
[Galaxy S III Mini General] bierma32:
The SM - T210 / 211 has as lastest Version 4.4.2 , SM- T110 / 111 AS lastest Version 4.2.2
[Galaxy S III Mini General] llbranco:
I know, but some guys have been

part of the port

work to CM or to 4.4.2 to T110/111

and SM-T110/111/210/211 and GT-i8200/L/N/Q have same SoCs and CPU.

it's about ROM/Hardware compatibility not about limitations
[Galaxy S III Mini General] llbranco:
Dumping ROM to start porting

using 4.2.2 from SM-T210R just for testing proposes if it work (even with bugs) I'll try to port 4.4.2 then CM 11 (or 12)

---------- Post added at 01:45 AM ---------- Previous post was at 01:14 AM ----------

@SolarPlexus, can u try to port (or even FORK) SM-T210R ( lt02wifi ) kernel [ https://www.androiddevice.info/submissions/988 ]

3.4.5-blackhawk+, 3.4.5-2364900 ( or http://xdaforums.com/galaxy-tab-3/development-7/kernel-werewolf-kernel-v001-sm-t210r-t2820573 ) to i8200 ?

[MENTION=4933755]adryyy[/MENTION], just ported our rom to T110 http://xdaforums.com/newreply.php?do=postreply&t=3139478

maybe we can give his help

(sorry for my english, I'm not fluent yet)
[T-Mobile LG G4] KryogenikX:
I can't seem to find where the boot animation zip is on 20o, does anyone know?
[T-Mobile LG G4] dtomlin:
In system/media.
[T-Mobile LG G4] Bowmanspeer:
I am actively looking right now to find bootanimation file. It is not in this media file. Any other ideas? I have just installed the CM posted by Turbo.
[T-Mobile LG G4] raptorddd:
you using the CM rom from turbo.? does it boot with black background and white android letters .? if so theres no bootanimation. is in system/media if you see that black android logo its been deleted.
[T-Mobile LG G4] Bowmanspeer:
That's what it is. Is it possible to just drop one back in there? Hmm. Couldn't hurt anything to try I guess...
[T-Mobile LG G4] raptorddd:
yes you can.. just make sure it has the right persmissons. if you have folder. and using file explorer to move it there,

or find a flashable zip.
[T-Mobile LG G4] Bowmanspeer:
What exactly would the right permissions be?
[T-Mobile LG G4] raptorddd:
i beleive 644 rw-r-r
[Moto G 2015 Q&A, Help & Troubleshooting] Acidfire.TM:
How does the unlocked bootloader logo removal

Work.

Any repercussions?

I assume you flash it through twrp?

Do you have to reflash if you change roms, recovery's?
[Moto G 2015 Q&A, Help & Troubleshooting] robot_head:
It flashes logo.bin file, no repercussions, just a nice splash screen, boot logo , whatever you wanna call it. And no it'll survive roms and switching recoveries, it goes into a different partition
[Moto G 2015 Q&A, Help & Troubleshooting] HelpMeruth:
"the ultimate moto g 2015" can I ask why? :P
[Moto G 2015 Q&A, Help & Troubleshooting] androidbaba:
Wrong thread bro...this is development thread there is a separate q and a thread for this...
[OnePlus 2 Q&A, Help & Troubleshooting] Theevilsocks:
Happened when I was updating twrp:

I downloaded the .img from their website, booted into my older version of twrp, went to flashing pressed the butting in the bottom right corner, selected the file and selected 'recovery'

Said it was successful, so I rebooted, then it wouldn't do anything anymore except for fastboot.

1. Can't boot into recovery

2. Can't boot normally

3. USB debugging disabled

4. oem locked

Only thing I can enter is fastboot.

I followed this guide, but no luck on my end.

https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
[OnePlus 2 Q&A, Help & Troubleshooting] passion8059:
Have you tried this?

http://xdaforums.com/oneplus-2/general/guide-return-op2-to-100-stock-unbrick-t3229606

and

All in one toolbox by mauronofrio.

I my self had lost recovery myself and flashed stock image in toolbox and then flashed image from above link to restore to stock and started custom rom process again.

Should not erase twrp once recovered if it has reflash your previous version of twrp or hybrid version.

Hope this helps.
[OnePlus 2 Q&A, Help & Troubleshooting] Theevilsocks:
It's no use because oem is locked. That means I can't flash anything.
[OnePlus 2 Q&A, Help & Troubleshooting] passion8059:
toolbox should still help you unlock bootloader again
[OnePlus 2 Q&A, Help & Troubleshooting] pitrus-:
Just use the Qualcomm factory restore image to return the phone to original shape of things.
[OnePlus 2 Q&A, Help & Troubleshooting] Theevilsocks:
I have no idea how I would do this without being able to flash anything.
[OnePlus 2 Q&A, Help & Troubleshooting] pitrus-:
Do you mean that the Qualcomm download program also crashes like fastboot? Sounds like you either have some problems with your windows installation or perhaps you haven't searched for and downloaded the Qualcomm restore if your still trying to flash the ordinary way instead of the emergency way.
[OnePlus 2 Q&A, Help & Troubleshooting] Theevilsocks:
Was able to fix it when I was messing around. Not sure what I did but it worked.

Thank you for all your help guys
[OnePlus 2 Q&A, Help & Troubleshooting] Redjax:
I'm having this problem too, and this isn't helpful. What were the last steps, or at least some of them, that you took to get it working? Which toolkit/script/program were you using? etc
[OnePlus 2 Q&A, Help & Troubleshooting] Theevilsocks:
I used this tool: http://xdaforums.com/oneplus-2/general/guide-official-op2-stock-reset-to-oos-3-t3402020

I fiddled around a bit with it, but I'm not sure what I did, and I already deleted the files.
[OnePlus 2 Q&A, Help & Troubleshooting] Redjax:
Literally JUST finished with this guide, and my OP2 is alive again! I was going to come back and post. Thanks for the link.

Anyone trying to use this guide without success:

There's one very important step I somehow missed. You MUST disconnect your phone, hold the power button for ~15-20 seconds until it's off, and hold the Volume+ button, THEN plug it back in. Your computer will make the "device connected" sound, but the screen will stay black. THIS IS OK! That means you're in a special recovery, which is where you need to be for the tool.

I also installed the certificate file in the folder I downloaded, then rebooted (it did not work before a reboot, but did work after).

So, the steps:

1. Download the files, make sure your signature signing for drivers is off.

2. Install the trusted certificate, then the driver.

3. Reboot PC

4. Power off phone (hold power for 15-20 secs), hold volume+, then connect through USB (wait for device connected sound, screen on phone will still be black)

5. Run the tool (I ran as admin, not sure if that's required)

6. Weep with joy that you finally found a solution that works.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] bjwx2:
Going to sell my mini, cleared everything and did a factory reset, can't get rid of UC Mini browser, keeps giving notice every

10 seconds, "Unfortunately UC Mini has stopped", have tried everything I know, to no avail, any ideas?
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] DarkJoker360:
Which rom you have?

Inviato dal mio GT-I9195 utilizzando Tapatalk
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] bjwx2:
4.2.2
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] DarkJoker360:
Try to update your phone

Inviato dal mio GT-I9195 utilizzando Tapatalk

---------- Post added at 09:59 PM ---------- Previous post was at 09:58 PM ----------

Update to 4.4.2

Inviato dal mio GT-I9195 utilizzando Tapatalk
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] bjwx2:
Sorry, already have 4.4.2 but thanks for the shout!
[JAMin, XDA Neo, S200 ROM Development] maxniper:
Does any one arrived to put this workin on ore Prophet,

i have tryed many cabs and OEM packages but nothing.

I NEED HELP ;)
[JAMin, XDA Neo, S200 ROM Development] ogum:
It didn't work for me either.

But I like pocketCM instead, check it here http://www.pocketcm.com/
[JAMin, XDA Neo, S200 ROM Development] kamalneet:
same here need some luck on this one , possibly because randomaccess.exe is used both by pocket cm and this program so its a name overlap ,means dead lock