Database Develop

Rooting Galaxy s3 mini....

Hi, I posted about this on another thread, but was then told that there is a forum for the S3. I would like to root my S3 mini GT-18190N, running 4.1.2. Its still under guarantee so it needs to be able to unroot.
Somebody mentioned CydiaImpactor, as it would be the easiest. So I installed to my mac, ticked both usb debugging and accept unknown sources, and ran the program. Within seconds I got an error, 'Error signature bugs unavailable'.......which I posted to the thread, and heard nothing from there and still havent about what that meant. I eventually found out that it means the bug has been fixed. But that is all I got.
I just wondered, what does that mean, does it affect any other ways of rooting? I found another rooting program on here, was given the the stock firmware for my phone but that needs to be unlocked. I did ask about whether the same problem would affect that firmware, but no answer. It seems the advice given on the first thread I started, about taking this to the correct forums needs to be done, which is why I am asking here. Sorry for multiple posting its not spam, its on advice from members on here.
I am a complete novice, never rooted before. So could anybody show me a root system that works for my phone.
Thank you

johnmwc2 said:
Hi, I posted about this on another thread, but was then told that there is a forum for the S3. I would like to root my S3 mini GT-18190N, running 4.1.2. Its still under guarantee so it needs to be able to unroot.
Somebody mentioned CydiaImpactor, as it would be the easiest. So I installed to my mac, ticked both usb debugging and accept unknown sources, and ran the program. Within seconds I got an error, 'Error signature bugs unavailable'.......which I posted to the thread, and heard nothing from there and still havent about what that meant. I eventually found out that it means the bug has been fixed. But that is all I got.
I just wondered, what does that mean, does it affect any other ways of rooting? I found another rooting program on here, was given the the stock firmware for my phone but that needs to be unlocked. I did ask about whether the same problem would affect that firmware, but no answer. It seems the advice given on the first thread I started, about taking this to the correct forums needs to be done, which is why I am asking here. Sorry for multiple posting its not spam, its on advice from members on here.
I am a complete novice, never rooted before. So could anybody show me a root system that works for my phone.
Thank you
Click to expand...
Click to collapse
hi bro, maybe i will buy this s3mini because i notice that it cost only 114.50 euro in my country, more than 50% less than the official price
so...
about root:
you can root the s3mini flashing the firmware with odin
else you can use cydia impactor(be sure to download the latest version from official websites)
i notice that samsung patched the masterkey bug exploited by cydiaimpactor in other galaxy phone but i dont know about s3mini 18190
however i rooted an s3mini of one of my friend s1 months ago, he has never made a firmware update and after he enabled debug usb and installed driver it work! and got root access on his phone, after root you CAN'T do ota update! you an use odin however maybe samsung upgrade to kitkat android 4.4
did you do some firmware update?

-Install TWRP (this video might be of help)
-enter recovery mode and reboot. TWRP will ask you whether you want to root or not

Hi, before I did anything I took a copy of the phone which I have stored on the laptop, windows 7. Then with CWM rooted the phone, and installed a ROM I found. The first time it didnt work, so I had to find another ROM, and install that. This ROM works but its not from my Carrier, which is EE/Orange. The Base version ends in AMJ2, which I dont seem to be able to find to get the correct ROM. The Build Number I have which is the ROM is DMod v6. It works, but its causing problems with Samsung. I have given hope of getting back to the original, but if I could get it to work with EE, it would be better. DModv6 is a US based ROM.
I hope I have explained it ok, its the first time I have done this, so not sure. Please ask for more details.
Sorry it took me so long to answer, have not been very well.
Thank you for your help

What do you mean by it not working with EE/Orange? What functionality do you not have?
Sent from my GT-I8190 using xda app-developers app

Mermaid Man said:
What do you mean by it not working with EE/Orange? What functionality do you not have?
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
As I have already mentioned, its a US based ROM, which only recognises T-Mobile UK. My phone keeps loosing the connection all the time. and I have to reconnect. T-Mobile UK is the US version of T-Mobile even though we have T-Mobile in the country, but without the UK at the end of it. And believe me it is not working properly. The phone itself does work, its faster, the battery life is much longer than when it was on EE. But I am also now having problems with Samsung, they have stopped me from using their software, because they say my phone is not using the correct software.
My first try, I did get Kit Kat running, but without the CAMERA, it wouldnt work. But there again, it was on a US based ROM, and had problems keeping the connection going. That was awesome but without the Camera, it was a bit useless. If I could get a ROM thet had either EE or Orange,

johnmwc2 said:
As I have already mentioned, its a US based ROM, which only recognises T-Mobile UK. My phone keeps loosing the connection all the time. and I have to reconnect. T-Mobile UK is the US version of T-Mobile even though we have T-Mobile in the country, but without the UK at the end of it. And believe me it is not working properly. The phone itself does work, its faster, the battery life is much longer than when it was on EE. But I am also now having problems with Samsung, they have stopped me from using their software, because they say my phone is not using the correct software.
My first try, I did get Kit Kat running, but without the CAMERA, it wouldnt work. But there again, it was on a US based ROM, and had problems keeping the connection going. That was awesome but without the Camera, it was a bit useless. If I could get a ROM thet had either EE or Orange,
Click to expand...
Click to collapse
Hey mate,
Try to use Maclaw's Recovery and KitKat ROM. They work perfectly! Flash Maclaw's recovery first (TWRP) and then wipe cache and dalvik and then flash the kitkat ROM (CM 11).
find them all here: maclaw.pl/downloads/ (stupid 10 post rule for new accounts doesn't let me post the link to HELP the user (johnmwc2)
---------- Post added at 06:32 PM ---------- Previous post was at 06:28 PM ----------
Also the reason that your phone has gone all crazy is because of the ROM you flashed (US version) probably only supports the US frequencies which is why you only get t-mobile network (in some places) as the frequencies change in each location as the phone masts give out different frequencies in different locations according to their surroundings (some frequencies penetrate walls much easier but may not go as far and vice versa).
Im 70% sure the ROM is the problem. the other 30% is me thinking maybe the ROM might not have anything to do with allowing the phone to receive phone signal ( in terms of SOFTWARE not hardware - before anyone tries flaming me). My other instinct tells me maybe its the baseband/modem version thats incompatible witht the US ROM?
just use Maclaws KitKat and TWRP!
They work a treat! :laugh:

[Q] Android 4.3 C5303 Update problem!

Hello to everyone!
This is my first post to this great forum. Recently I bought a Sony SP C5303 and now I face a complicated problem and I want your help.
The situation:
The phone was bought as unlocked (and not rooted) and when I got it, it prompt me to update to the 4.1.2 12.0.A.2.254 as previously had an older build version. I successfully did the update and everything works fine BUT right now I am wondering why I can't see the official update for 4.3
After a lot of search I realised that the phone was supplied from T-mobile (UK) as it has customization version 1272-7168_R6A
So, the phone is unlocked, unrooted and since I bought it operates on Three network.
However either when I connect it with PC companion, or I do the manual search for updates through the headset, I am unable to see the update to 4.3
I am wondering if there is any conflict between the T-mobile unlock and the Three network that I operate the phone.
Is there any way so I can trigger the update? Should I wait a little bit more? I am not sure and I am not so good with these things.
The only I want is not to cause the phone to lock somehow or to install a custom rom, neither root it.
Thank you very much for your help and your answers!

I would stay on 4.1.2. 4.3 is a piece of crap. I made the mistake of upgrading and had to downgrade. I tired many roms and did not like any of them. Stock, root and xposed frameworks still best for stability, features and battery life.

spsony120 said:
Hello to everyone!
This is my first post to this great forum. Recently I bought a Sony SP C5303 and now I face a complicated problem and I want your help.
The situation:
The phone was bought as unlocked (and not rooted) and when I got it, it prompt me to update to the 4.1.2 12.0.A.2.254 as previously had an older build version. I successfully did the update and everything works fine BUT right now I am wondering why I can't see the official update for 4.3
After a lot of search I realised that the phone was supplied from T-mobile (UK) as it has customization version 1272-7168_R6A
So, the phone is unlocked, unrooted and since I bought it operates on Three network.
However either when I connect it with PC companion, or I do the manual search for updates through the headset, I am unable to see the update to 4.3
I am wondering if there is any conflict between the T-mobile unlock and the Three network that I operate the phone.
Is there any way so I can trigger the update? Should I wait a little bit more? I am not sure and I am not so good with these things.
The only I want is not to cause the phone to lock somehow or to install a custom rom, neither root it.
Thank you very much for your help and your answers!
Click to expand...
Click to collapse
This is due to the mobile operator themselves. I am with o2 and do not have the 4.3 update for my SP either, it is down to the operator to decide when they release the update as they have to fill it with their bloatware first!
You can of course flash 4.3 yourself using flashtool I did, their are plenty of guides on this forum

kidicarus1602 said:
This is due to the mobile operator themselves. I am with o2 and do not have the 4.3 update for my SP either, it is down to the operator to decide when they release the update as they have to fill it with their bloatware first!
You can of course flash 4.3 yourself using flashtool I did, their are plenty of guides on this forum
Click to expand...
Click to collapse
To be honest I am a little bit confused what determines if the phone is going to update or not.
I mean that is the provider responsible for delivering the update or the customization version? If we think that with no sim, we just plug the phone to pc companion and it is able to see the update, then it depends on customization version.
Is there any official reference for how the phone is determined to be valid for the update?
I still believe that there is a conflict here between the current provider I operate the phone (Three) and the customization version that comes from T-mobile (the phone was unlocked from T-mobile).
Thanks guys!
P.S @xEaGLeNeC Wow!!I heard completely the opposite from many people. They claimed that the phone battery last more with 4.3! I will try to search more if it finally worth to update or not.

[Q] Lost network & relocked BL?

Hello,
I've a weird problem with my Xperia SP. Today i wanted to get back to rom based on stock rom to get miracast feature.
I downloaded newest existenz rom and williams kernel for stock based roms. Installation went fine system booted ok and everything worked fine. After some time phone turned off and didn't wanted to start. Only flashmode worked. I've decided to download stock .205 CE1 rom and flash it.
It booted up, sim card was recognized(had to write PIN). After that network was not found. Signal with red "X". I've tried to manually register to network but i could not.
Next thing is that after flashing stock rom fastboot mode stopped working. Service menu shows that Bootloader can not be unlocked even that it was unlocked before and flashtool(BLU option) shows that it is still unlocked. Flashtool also shows Bootloader: NOT_ROOTABLE.
I have actually no idea what have happend. Now i'm installing stock rom using Sony PC Companion but i think this wont help for network problem.
My main network is PLUS GSM(Poland network).
Could sim card die? It is old type card (almost 10 years) and i had to cut it manually to fit micro sim for the phone.
prntscr,com/45wtip (swap ','(comma) with '.'(dot))

KrychoPL said:
Hello,
I've a weird problem with my Xperia SP. Today i wanted to get back to rom based on stock rom to get miracast feature.
I downloaded newest existenz rom and williams kernel for stock based roms. Installation went fine system booted ok and everything worked fine. After some time phone turned off and didn't wanted to start. Only flashmode worked. I've decided to download stock .205 CE1 rom and flash it.
It booted up, sim card was recognized(had to write PIN). After that network was not found. Signal with red "X". I've tried to manually register to network but i could not.
Next thing is that after flashing stock rom fastboot mode stopped working. Service menu shows that Bootloader can not be unlocked even that it was unlocked before and flashtool(BLU option) shows that it is still unlocked. Flashtool also shows Bootloader: NOT_ROOTABLE.
I have actually no idea what have happend. Now i'm installing stock rom using Sony PC Companion but i think this wont help for network problem.
My main network is PLUS GSM(Poland network).
Could sim card die? It is old type card (almost 10 years) and i had to cut it manually to fit micro sim for the phone.
prntscr,com/45wtip (swap ','(comma) with '.'(dot))
Click to expand...
Click to collapse
Use flashtool to flash stock firmware by ftf file. Here:
http://forum.xda-developers.com/showthread.php?t=2311964
Use an older one and if that does not work, try one or two more. Hopefully, that will help. Best of luck!

shahrukhqasim said:
Use flashtool to flash stock firmware by ftf file. Here:
http://forum.xda-developers.com/showthread.php?t=2311964
Use an older one and if that does not work, try one or two more. Hopefully, that will help. Best of luck!
Click to expand...
Click to collapse
Does it matter which country is it for? I can try some of them but i think that won't help. I've checked other sim card and it was recognized but didn't even ask me for pin. Weird Oo.
If nothing helps i will just flash stock firmware with SEUS and let sony service take care of it, hopefully. Phone still has guarantee.

KrychoPL said:
Does it matter which country is it for? I can try some of them but i think that won't help. I've checked other sim card and it was recognized but didn't even ask me for pin. Weird Oo.
If nothing helps i will just flash stock firmware with SEUS and let sony service take care of it, hopefully. Phone still has guarantee.
Click to expand...
Click to collapse
Regions perhaps. But the thing that does not make sense it that that why did it work before and not now? It should work. Anyway, my SIM was mini too. I, too, had to cut it. It works. Or possibly contact your service provider maybe something is wrong with the SIM. They might have have locked it or something?

shahrukhqasim said:
Regions perhaps. But the thing that does not make sense it that that why did it work before and not now? It should work. Anyway, my SIM was mini too. I, too, had to cut it. It works. Or possibly contact your service provider maybe something is wrong with the SIM. They might have have locked it or something?
Click to expand...
Click to collapse
If none sim card works on phone then it is IMEI problem or phone itself somehow. I'm trying to flash other roms now. Hopefully it will help if not then sending to service.

KrychoPL said:
Hello,
I've a weird problem with my Xperia SP. Today i wanted to get back to rom based on stock rom to get miracast feature.
I downloaded newest existenz rom and williams kernel for stock based roms. Installation went fine system booted ok and everything worked fine. After some time phone turned off and didn't wanted to start. Only flashmode worked. I've decided to download stock .205 CE1 rom and flash it.
It booted up, sim card was recognized(had to write PIN). After that network was not found. Signal with red "X". I've tried to manually register to network but i could not.
Next thing is that after flashing stock rom fastboot mode stopped working. Service menu shows that Bootloader can not be unlocked even that it was unlocked before and flashtool(BLU option) shows that it is still unlocked. Flashtool also shows Bootloader: NOT_ROOTABLE.
I have actually no idea what have happend. Now i'm installing stock rom using Sony PC Companion but i think this wont help for network problem.
My main network is PLUS GSM(Poland network).
Could sim card die? It is old type card (almost 10 years) and i had to cut it manually to fit micro sim for the phone.
prntscr,com/45wtip (swap ','(comma) with '.'(dot))
Click to expand...
Click to collapse
i got the exact same problem right now after using william kernel, can you fix it?

Muh_lukman94 said:
i got the exact same problem right now after using william kernel, can you fix it?
Click to expand...
Click to collapse
I've reflashed stock rom using SEUS and sended phone to sony service. Hopefully they can help. Be careful with Williams Kernel for stock roms. This may be a common bug.

For anyone who had the same problem. Sony exchanged my whole phone with information that mainboard was broken. They said that phone could not be fixed.
Good luck
PS. Topic can be closed i think.

KrychoPL said:
For anyone who had the same problem. Sony exchanged my whole phone with information that mainboard was broken. They said that phone could not be fixed.
Good luck
PS. Topic can be closed i think.
Click to expand...
Click to collapse
Where have you been before? I have the same problem after flashing William kernel for stock rom((( What to do now?

Everything i've done is described in the thread. Phone was exchanged by sony after all.

KrychoPL said:
Everything i've done is described in the thread. Phone was exchanged by sony after all.
Click to expand...
Click to collapse
I think i have the same problem, but up till now no one knows the answer, the biggest problem is my warranty is over, i hope someone here can help :crying:
---------- Post added at 07:29 PM ---------- Previous post was at 07:24 PM ----------
KrychoPL said:
Everything i've done is described in the thread. Phone was exchanged by sony after all.
Click to expand...
Click to collapse
I have the same problem here, and the biggest problem is my warranty expired, hope someone here can help..

Muh_lukman94 said:
i got the exact same problem right now after using william kernel, can you fix it?
Click to expand...
Click to collapse
do a restore of Your TA will fix the problem, now my phone can detect SIM card

Docomo Question

Hey guys,
I just bought a Z3 Compact (D5803) for my girlfriend on eBay. It said the condition was new (other). I set up the device, and it was running 4.4.4 Kit Kat. Everything was fine and normal. I just plugged it in and updated the phone to Lollipop, and now when I boot it up there is a docomo screen, and in the settings there is a new section for docomo. All I did was update the phone through the Sony Xperia Companion program on Windows 10. Is this something I can get rid of? Or do I have to unlock the bootloader and flash a non-docomo ROM? I would hope there is a way to get rid of the docomo stuff, but I guess that's probably not possible?
Thanks.
EDIT:
I fixed it. I found the thread with all of the firmware, and I flashed the FTF for the USA 6.0.1. Now everything is great, no more Docomo!

chris23445 said:
Hey guys,
I just bought a Z3 Compact (D5803) for my girlfriend on eBay. It said the condition was new (other). I set up the device, and it was running 4.4.4 Kit Kat. Everything was fine and normal. I just plugged it in and updated the phone to Lollipop, and now when I boot it up there is a docomo screen, and in the settings there is a new section for docomo. All I did was update the phone through the Sony Xperia Companion program on Windows 10. Is this something I can get rid of? Or do I have to unlock the bootloader and flash a non-docomo ROM? I would hope there is a way to get rid of the docomo stuff, but I guess that's probably not possible?
Thanks.
EDIT:
I fixed it. I found the thread with all of the firmware, and I flashed the FTF for the USA 6.0.1. Now everything is great, no more Docomo!
Click to expand...
Click to collapse
I know you've fixed the issue so I don't really need to say anything but I thought I would anyway.
DoCoMo's a Japanese provider if I remember correctly. I'm guessing that the phone was originally from Japan so Companion just put the latest Japanese rom on. As long as it still works with your network, that shouldn't be a problem. Boot animations and settings in..er..Settings can always be changed.

Ticklefish said:
I know you've fixed the issue so I don't really need to say anything but I thought I would anyway.
DoCoMo's a Japanese provider if I remember correctly. I'm guessing that the phone was originally from Japan so Companion just put the latest Japanese rom on. As long as it still works with your network, that shouldn't be a problem. Boot animations and settings in..er..Settings can always be changed.
Click to expand...
Click to collapse
Thank you for the response. The story has gotten a bit complicated for me haha. When I put the newest firmware, NFC stopped working completely on the phone. It said the NFC firmware couldn't update. Apparently if you run firmware that is different than the DoCoMo firmware, NFC breaks. But the weird thing is, the DoCoMo variant has a different model number, and has the DoCoMo logo all over the back. Mine is supposed to be the D5803 and doesn't have the logo on the back. So now I'm trying to talk to Sony and the eBay seller to see what's going on with that. Not sure if you have any idea about that. I wonder if it was the DoCoMo variant and the eBay seller just replaced the back cover or something.

Crossflashing possible? my DualSIM HongKong V405EBW20a to European DualSIM firmware

Hi all, finally decided to bite bullet again after bricked LG V20 (2 yrs ago) and bought DualSIM V405EBW. LGUP reports that its on OPEN_HK_DS and last released firmware was 20a
Is it possible that I crossflash to OPEN_EU_DS 20g without losing any functionality for dualSIM ?
What about bootloader unlock? LG dev website reports my device isn't supported for bootloader unlock so I guess I have to try v35 engg bootloader method.
I keep phones for root+adblock+mods . Especially can't live without adblock. Blockada is just a workaround which doesn't work to my satisfaction.

dark_prince said:
Hi all, finally decided to bite bullet again after bricked LG V20 (2 yrs ago) and bought DualSIM V405EBW. LGUP reports that its on OPEN_HK_DS and last released firmware was 20a
Is it possible that I crossflash to OPEN_EU_DS 20g without losing any functionality for dualSIM ?
What about bootloader unlock? LG dev website reports my device isn't supported for bootloader unlock so I guess I have to try v35 engg bootloader method.
I keep phones for root+adblock+mods . Especially can't live without adblock. Blockada is just a workaround which doesn't work to my satisfaction.
Click to expand...
Click to collapse
Be careful, you might have signal loss like me, I still don't have a solution for my signal loss. You better make a back up of your original FW with qfil. Make a dump and if you're kind enough share it with me I need to get my signal back.

g3lv1n said:
Be careful, you might have signal loss like me, I still don't have a solution for my signal loss. You better make a back up of your original FW with qfil. Make a dump and if you're kind enough share it with me I need to get my signal back.
Click to expand...
Click to collapse
which particular partitions u need? Also, have u tried partitionDL OPEN-HK 20a?
I stuck with 20a and BL unlocked, TWRP etc. I'm on havoc 3.5 now with everything working (except only one back camera and one front camera being accessible. Edit: Fixed that with burial Gcam 7 + config + enabling the 3 cameras from advanced settings )

I need the modem**.bin if you have all the modem part just share them with me. I'm still stuck with no signal ?
---------- Post added at 10:08 AM ---------- Previous post was at 09:53 AM ----------
dark_prince said:
which particular partitions u need? Also, have u tried partitionDL OPEN-HK 20a?
I stuck with 20a and BL unlocked, TWRP etc. I'm on havoc 3.5 now with everything working (except only one back camera and one front camera being accessible. Edit: Fixed that with burial Gcam 7 + config + enabling the 3 cameras from advanced settings )
Click to expand...
Click to collapse
Hey check this out all the updated for our v40.
https://drive.google.com/folderview?id=1LCV10vKPWUgVFO1T1mdt7ubn0LWV8mw0

g3lv1n said:
I need the modem**.bin if you have all the modem part just share them with me. I'm still stuck with no signal
https://mega.nz/file/9QcV3aJQ#rA21Cvqal7Ruvfny74t_nz0nq9Nnejh1Rm_ipGSzOQI
This is my backup. I recovered my EBW_HK when i was stuck with no baseband and null IMEI. Flash every partition and then refurbish teh stock kdz of EBW_HK.
Do it only if your phone is EBW_HK.
Click to expand...
Click to collapse

dark_prince said:
g3lv1n said:
I need the modem**.bin if you have all the modem part just share them with me. I'm still stuck with no signal
https://mega.nz/file/9QcV3aJQ#rA21Cvqal7Ruvfny74t_nz0nq9Nnejh1Rm_ipGSzOQI
This is my backup. I recovered my EBW_HK when i was stuck with no baseband and null IMEI. Flash every partition and then refurbish teh stock kdz of EBW_HK.
Do it only if your phone is EBW_HK.
Click to expand...
Click to collapse
Do you have any password when you back up your partition? I flashed you partitions and got secure start-up which need a password.
Thanks
Click to expand...
Click to collapse

i also lost mine after flashing KDZ, but i don't know what region my 405EBW is... is there a way to identify the region?