yashsingh1/xdaforums huggingface dataset:
[Galaxy S5 Mini Original Android Development] Hamza_0:
Ohhh. Ok now you have to do some steps of the process. First make a backup.

Then go here and dowload the deodexer http://xdaforums.com/showpost.php?p=65741469&postcount=574

Copy app, framework, priv-app and build.prop from /system of you phone to your pc.

Put Them in a folder. Rename that folder to "system".

Extract the deodexer and open it.

In it, browse to where you have placed the folder and select it.

Tick app, framework and priv-app and start it. It takes some time.

Aftet finished, go to the folder where you have extracted the deodexer. There will be five folder There.

Copy app, framework and priv-app to your phone.

Go to recovery and delete these folders from /system through aroma fm. Then paste these deodexer ones There.

Flash the permission setter zip and wipe data and reboot. It should work since you have only deodexed your rom and havent installed ay s6 files.

If they work, upload these folders in a zip so i can download them and modify them.

Btw, If you make backup of stock system and boot you will not have to Flash stock rom again. Just restore the backup.

See this tut for modifying odin flashable files http://www.rwilco12.com/forum/showthread.php?tid=92
[Galaxy S5 Mini Original Android Development] nico_vo:
nope, bootloop. [MENTION=6177902]Faisal_0[/MENTION]

after deodexing, some error logs are opened (see attached file)
[Galaxy S5 Mini Original Android Development] Hamza_0:
It says files deodexed=0! I suppose there is a problem with g800f. Atleast it should be deodexed successfully. This deodexer is made specifically for s5 but it also works on s5 variants like s5 mini. I had deodexed g800h using that successfully.
[Galaxy S5 Mini Original Android Development] nico_vo:
Maybe trying an older 5.1.1 firmware works?

Enviado desde mi SM-G800F mediante Tapatalk
[Galaxy S5 Mini Original Android Development] br3acker:
i use Serbia firmware, 5.1.1
[Galaxy S5 Mini Original Android Development] Hamza_0:
I saw that g800f lollipop came much later after g800h. So try this:

Go to the folder where you have extracted deodexer.

In that you'll see a file called oat2dex.jar.

Replace that oat2dex.jar with the oat2dex.jar that I have attached.

Run the deodexer again and tell me that whether it deodexes this time or not.

The do this:
[Galaxy S5 Mini Original Android Development] lfom:
Some info that may be helpful, maybe you already know: then main difference between G800H and G800F is different processors: H uses Snapdragon while F uses Exynos, besides H not supporting LTE as far as I know. Maybe deodexing apps for G800H are for Snaodragon only. Good luck.
[Galaxy S5 Mini Original Android Development] nico_vo:
[MENTION=6177902]Faisal_0[/MENTION] nope, again no deodexed files
[Galaxy S5 Mini Original Android Development] nico_vo:
Okay, so I searched for other softwares to deodex the rom and came up with one named lordroid one, which seems to take quite much more time for deodexing (the other one was ~1/2 minutes) and even can create a flashable zip after deodexing, so I will post any results.

Enviado desde mi SM-G800F mediante Tapatalk
[Galaxy S5 Mini Original Android Development] quanqw:
Please port galaxy j3 rom for our device. It has s bike mode very useful.
[Galaxy S5 Mini Original Android Development] Hamza_0:
Nope, its a universal deodexer, it deodexes bot s5 variants g900h and g900f so it should deodexes g800f as it deodexes G800H.

good luck! Nope it deodexes.

Link?
[Galaxy S5 Mini Original Android Development] nico_vo:
It deodexes, but doesn't want to boot

Enviado desde mi SM-G800F mediante Tapatalk
[Galaxy S5 Mini Original Android Development] br3acker:
[MENTION=6177902]Faisal_0[/MENTION] you make room ??
[Galaxy S5 Mini Original Android Development] Hamza_0:
Dodexed firmware is required to port my rom. I cant make it if the system isnt deodexed. Try an older or newer or any other firmware of g800f. Maybe the problem of deodexing is only with this firmware? It shouldnt bootloop when the firmware is deodexed.
[Galaxy S5 Mini Original Android Development] nico_vo:
I think it is just related to this ROM version, as also when I try and restore the backup, I end up in a bootloop..

Already flashed an older version (the first one that came out here in Germany) and I am currently extracting these three folders and build.prop from system folder. As deodexing and flashing + booting deodexed ROM in the phone takes so long, I think that I will leave it tonight and post results here tomorrow. :fingers-crossed:
[Galaxy S5 Mini Original Android Development] Hamza_0:
Hopefully it would work! Make sure that you have cleared dalvic cache!
[Galaxy S5 Mini Original Android Development] Andrea224:
[MENTION=6088230]nico_vo[/MENTION] [MENTION=6177902]Faisal_0[/MENTION] So, S6 port is working on G800F?
[Galaxy S5 Mini Original Android Development] nico_vo:
I can't get the deodexed rom to boot

Enviado desde mi SM-G800F mediante Tapatalk
[Galaxy S5 Mini Original Android Development] Andrea224:
Damn! If only my S5 Mini was my secondary phone!
[Galaxy S5 Mini Original Android Development] nico_vo:
S5 mini is my main phone ?

Enviado desde mi SM-G800F mediante Tapatalk
[Galaxy S5 Mini Original Android Development] Andrea224:
Me too, but I need it. So I can't spend so much time to experiment or doing a tester, because I have to study and go to school.
[Galaxy S5 Mini Original Android Development] Hamza_0:
Ohh... So it didnt boot again?

In that case... we'll need to know the cause of bootloops.

For that, install adb on your pc from here : http://xdaforums.com/showthread.php?t=2588979

Then flash stock rom which boots, after flash go settings>about device and tap some times on build number to enable developer options. Press back and Then click on developer options and enable usb debugging. Flash supersu and Then go to its settings and tick 'enable su during boot'.

Now in your pc, go to where you have installed adb (usually disk in which windows is installed>adb) and open a command prompt there by preesing and holding SHIFT and Then right click on the empty space in folder. Click on 'open command windows here'. Then in command windows, type:

adb device

if it shows some random letters and number, you have successfully installed adb.

Now flash the deodexed system zip.

It will bootloop.

Now connect your phone to pc again and as soon as 'galaxy S5 mini' disappears and bootanimation starts, type in command prompt:

adb device

If your device is connected, fastly type this:

adb logcat > logcat.txt

You will have to type command fastly or copy/paste them since in bootloop, it turns off and starts again and again instead of just stock at bootanimation.

Logcat.txt file will be in adb folder. Attach it here. I will look for what error is causing bootloop.

its my primary phone too!
[Galaxy S5 Mini Original Android Development] nico_vo:
Okay, done.

Oh, and hey, thanks for taking time to try and port the s6 rom to the g800f :)
[Galaxy S5 Mini Original Android Development] quanqw:
Can you help me to port cm 13 base on stock lollipop. Because I want to keep touchwiz dialer app on cm system. TouchWiz dialer app has native video call and cm is smoothly.

This is link of j3 rom but I think visual voice mail is better than s bike mode.
[Galaxy S5 Mini Original Android Development] Andrea224:
Touchwiz's app system doesn't work on CM13. Touchwiz's apps works only on stock based rom.
[Galaxy S5 Mini Original Android Development] Hamza_0:
Your welcome ;)

I'll check for fatal errors which cause boot failure.

Currently I am working for poting my rom to g800f so I cant port it. As [MENTION=7218412]Andrea224[/MENTION] said, touchwiz app dont work on aosp rom like cm.ISearch google play, you'll sure get sone apps which support video calling and have good ui.
[Galaxy S5 Mini Original Android Development] nico_vo:
Do you think you are going to have something for tonight?

Enviado desde mi SM-G800F mediante Tapatalk
[Galaxy S5 Mini Original Android Development] quanqw:
Like that http://xdaforums.com/showthread.php?t=2100060
[Galaxy S5 Mini Original Android Development] Hamza_0:
I am working on it though I didnt found any fatal error which causes bootloop. There are a number of simple errors but not big enough to cause bootloop. But do this flash your stock rom, then go to twrp and backup boot and system and then wipe everything except internal storage and finally restore the backup of system and boot. You said that this also causes bootloop???

If it causes, then I suppose there is something that causes error in your stock rom or in your internal storage since everything else have been wiped. There is also another probability that causes bootloop. In g800h, if you flash lollipop stock rom then twrp, your device wont boot unless you flash a custom kernel which is not seandroid enforcing. So, if the above fails, flash a custom kernel then restore the backup of system only. Dont restore boot if you have flashed custom kernel.

?? What should I do with that? Its tw5 port for galaxy gio.
[Galaxy S5 Mini Original Android Development] quanqw:
My mean we can port a rom like that for our device. That rom is touchwiz app base on cm system.

But if we can't, you can help me modify the usb setting to show usb tethering. On touchwiz lollipop, usb setting show only mtp and ptp. Thanks for your help.
[Galaxy S5 Mini Original Android Development] nico_vo:
Okay, done.

First, I flashed a kernel, but it was not seandroid enforcing and did not boot(stuck at Samsung galaxy s5 mini screen).

Then, I reflashed stock ROM and flashed a cm13 kernel (did not realize until I finished flashing xD) and this one passed the galaxy s5 mini screen, but stuck at samsung bootlogo

After the cm13 kernel, I flashed the same kernel, but built for stock TW, which is not seandroid enforcing, but it also got stuck at the samsung galaxy s5 mini screen, with the blue "kernel is not seandroid enforcing" letters.

what is curious, is that kernel made for TW won't pass the first screen, but kernel for cm3 passed the first screen, even though it did not finally boot.

I also though that, if the stock rom wont boot after restoring the stock firmware because of the custom recovery, maybe I can send you the deodexed files and you somehow replace them in the samsung stock system.img and include this system.img in the stock TAR ball (I could also send you the link of this if you don't want to download it from sammobile, as it is very slow for free users)

Tell me what you think about this ASAP, so that we can get over this soon ;)
[Galaxy S5 Mini Original Android Development] Be bero:
Problem please fix :(

Hay bro when i instal theme my phone restarting and do not turn on restart restart and restart please fix :(
[Galaxy S5 Mini Original Android Development] Hamza_0:
A great developer has done it and i am not a great developer :v Btw i think old touchwiz was not as mooded as it is nowadays so we cant port it. Otherwise, popular non-samsung device like flagships of htc would have got samsung ports since the have cm.

Settings doesnot need to Be modified, connect phone to pc using usb cable, go to settings>tethering and mobile hotspot>usb tethering and tick it.

hmm. . There IS a problem with your stock rom. Have you tried another? The custom kernel for samsung lollipop must not bootloop your device, its developer would have tested it. You cant flash any custom kernel? I think you should ask the developer of the kernel for which stock rom he uses since his kernel works on that stock rom. When the kernel would work, hopefully everything else would work since modifing the firmware you are using even a bit causes bootloop. Deodexing a rom never causes bootloop. I have done it many times for different devices. Basically, the problem is with the stock rom you are using. I know how to create a new system.img, but i dont think it will work. It will again cause bootloop since if we cant modify even boot partition and modifying it causes bootloop so modifying system will also causes bootloop.

s6 theme arent currently compatible yet, they dont work on any device except s6 and note 5 and later devices like s7. To fix restart again and again, go to twrp. Backup you DATA partition in by clicking on BACKUP. After Backup, press back and click on WIPE. Swipe the slider at the bottom and reboot. After reboot, your data will not Be there, it has been wiped but you can get your apps back. For that install Nandroid Manager from play store. Open it and click on your Backup of DATA . You will see your apps, you can restore them with their data.
[Galaxy S5 Mini Original Android Development] quanqw:
I want usb setting show usb tethering because I don't want to go to settings app. I want it show option protocol like HTC rom or Mashalow rom.
[Galaxy S5 Mini Original Android Development] rxmd:
That will be hard to change, I guess you'll just have to accept it.

Going to the settings app is really just two clicks, but if you don't want to do those two clicks every time, you can use a tethering app like this that enables USB tethering automatically when you connect a PC.
[Galaxy S5 Mini Original Android Development] Hamza_0:
You can also use DriveDroid (find it on play) and in it, change permanent usb settings to usb tethering so whenever you connect to pc, usb tethering will automatically start.
[Galaxy S5 Mini Original Android Development] Trunik:
does not turn on Wi Fi

does not turn on Wi Fi
[Galaxy S5 Mini Original Android Development] Hamza_0:
See the whole thread before posting. I have already answered that.
[Galaxy S5 Mini Original Android Development] nico_vo:
Okay, I have tried another different ROM and got the custom kernel to work, but not the deodexed ROM. I have also tried with wiping everything (including internal storage), but nothing.

I Will try another deodexing software and see :(

Enviado desde mi SM-G800F mediante Tapatalk
[Galaxy S5 Mini Original Android Development] Hamza_0:
You should deodex the new firmware. Using the older deodexed files may cause bootloop. The deodexer i had mentioned is the best for me just in its folder, replace oat2dex.jar with the one i had attached since its new and the one without sv deodexer is outdated.
[Galaxy S5 Mini Original Android Development] nico_vo:
No, no, I pulled again the files from the New ROM

Enviado desde mi SM-G800F mediante Tapatalk
[Galaxy S5 Mini Original Android Development] nico_vo:
I replaced oat2dex.jar posted before, but again no success.
[Galaxy S5 Mini Original Android Development] Hamza_0:
Ok. Custom kernel works on the new firmware, right? If you could, try to upload the folders of new firmware. I will download them and try deodexing them myself. Also, since everything has been changed but it still doesnot boot, try changing recovery to cwm or some other. I know its very improbable but still the recovery ypu are using might have caused this problem.
[Xperia Z Q&A, Help & Troubleshooting] ManagementCritic:
I have been back and forth with both T-Mobile and Sony tech support about unlocking my Sony Xperia Z Model C6606 4.3 T-Mobile variant Build 10.4.C.0.814. When I entered the service code '*#* blah blah blah' it says unlock = No. Not possible. No beans. Sorry Charlie. No luck, no joy.

The following is a

paraphrase

of the exchanges with these two corporate giants, modified for brevity and the hope that the crushingly depressing outcome might be presented as slightly humorous.

I asked them, 'How do you update the system software when new releases are available?' They replied that there are 'special codes' that unlock the bootloader for the update. And I thought to myself, Really? Isn't that special.

I remarked that if it was possible for them to remotely upgrade the system software (read: kernel), then it is possible for them to remotely unlock the bootloader. The song and dance routine that followed was remarkable. In essence, they declined. Not possible. No beans. Sorry Charlie. No luck, no joy.

I said, if you won't unlock the bootloader now that we have established that you can, would you downgrade the system software to something where I can unlock the bootloader? Again, they declined and left me with nothing more than visions of 'special codes' dancing in my head. Not possible. No beans. Sorry Charlie. No luck, no joy.

My only question is, "Why not? Why on some and not on others?"
[Xperia Z Q&A, Help & Troubleshooting] Akinaro:
This is what you call company's politic, and people who work for it need to fallow this politic, even if its bad for consumer.

This world that we created for our self and we need to deal with it, just like with government.

There are codes for maintaining device(not only codes that you type on phone), that cellular companies get from phone manufactures to make their branded systems, just like their get bunch of other tools that help them doing this.

But its not like SIM-lock code and it cant be thrown around like peace of paper, because:

1) its can be used in bad way(hacking, unlocking etc)

2)it could be used by people that would sell that code to others and make money from it(illegally).

3) It breach of contract that you ACCEPTED buying that phone from t-mobile or as a free handset.

When you bought that phone you accepted agreement that you get with phone AND your operator, that clearly say that you can't mess with your phone system in any way that its said in contract and system it self, and you can use your phone as you get it.

Any modifications break terms of use, and you actually lost any rights to even ask support for help.

My point is that asking support for that code is actually really stupid, because their work doesnt include unlocking devices for modifications that user want to make(illegally looking from contract perspective), As far as device is not damaged or doesnt have problems, you actually have no reason write to them.

Its like going to car dealer where you bought car, and ask to remove engine because you want to put there new one... They totally dont care because this is not part of deal you made with them and its just nothing more than breaking regulations.

It is forum about modifications of phones, but we actually all make silent agreement that we KNOW that we can lost warranty and dont have rights for official support when we modify our phones. I think you forgot about that
[Xperia Z Q&A, Help & Troubleshooting] Akinaro:
Sorry, but my point is still valid.

You still asking support, that is made for helping with damaged/inoperative devices in way as guarantee say it, for unsupported access to device that is not part of ANY agreement that you accepted buying this phone.

People you talked with can be nice or not, can understand that its personal and for developing purpose. Its all doesnt matter because its company politic.

Even if I support full access to device that you bought(

after all ITS YOURS

) in other way I know that more than half of people that would see that they have access to it, they would start messing with it and then whine that their phones doesnt work.

In fact, actually damn good part of post on XDA is such whining of people that messed their phone and now they cry that it doesnt work and ask for help, and saddest part is that they never learn lesson from it so its never ending story.

So again, asking support for unlocking your phone, as far as its not SIM-lock, its useless and just silly.

You can ask technician from support if he could do this "on the side, out of records", but you would need +10 charisma for that if you dont know him, or some cash, that for most of time work. I actually loots of time just paid technician to make it on the side, especially when you dont need to wait few days for phone, few minutes, few hours and they fix/unlock your phone without a problem.

Or just find someone who would help you unlock it in different way... but XZ is just old and not "trendy" so no one care anymore and its hard to find anyone here.
[Xperia Z Q&A, Help & Troubleshooting] ManagementCritic:
OK Akinaro. That's enough with the ad hominem attacks. You have accused me of everything from trying to steal company secrets to unethical breaches of contractual agreements. All I did was try to negotiate some assistance and report on my progress.

Point 1. I am still a long term customer of my carrier. They encourage me to seek their help. So I don't care if you like it or not. What you characterize as abuse or illegal behavior, THEY characterize as completely acceptable.

Point 2. I am a consumer of the OEM's products. They encourage me to seek their help. So I don't care if you like it or not. What you characterize as abuse or illegal behavior, THEY characterize as completely acceptable.

Point 3. This is a development forum. My OP is within bounds and my responses to you have been civil. So I don't care if you like it or not. What you characterize as abuse or illegal behavior, THEY characterize as completely acceptable.

So far, you have accused me of everything from unethical acts and intentions to stupidity and whining. You haven't said anything of any real value. You haven't contributed any constructive ideas how I might get them to help. Nor have you been able to substantiate your wild accusations with anything that resemble facts or logic. So no, you haven't made a single valid point.
[Xperia Z Q&A, Help & Troubleshooting] Akinaro:
You realize that Im just writing obvious things? Because idea of asking official support for unlocking bootloader is just weird.

You can be mad that from your perspective my point is not valid.... because core of your question contain no fricking point at all.

You asked support for unlocking: They said they dont do this.

In your phone manual there is mention: "Any change or modification not expressly approved by Sony may void the user's authority to operate the equipment.", and I think access to bootloader just to have fun with kernel is part of that "modification"

There is about 1000 topic about bootloader on XDA, and they all mention the same thing: if it say no, its no. Simple.

So what you expect them to do? What you expect from XDA when you made this topic? All we can say is obvious thing that everyone know: ts not possible, especially with help of official support, that is not made for that.

Before you even bought your phone you should think and check your device, I always ask to turn phone on before buy it, its a matter of typing *#*#service#*#* to check it, its about 9sec to find bootloader section.

You can be mad at me, Sony or Obama, or anyone who is trendy right now, No one care. All what I write, is obvious things that everyone known.