• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [International] i9300 EMEI + Broadband Uknown

I'd try it with the second firmware you downloaded as the problem with ktool may have been due to compatibility issues with the latest firmware and since you'll need to restore the img backup after its best to play it safe.
 
So i downloaded the luxenbourg firmware , didn't cleared efs for the first flash all went well .

So after the flash he rebooted into samsung original ROM :D
So every thing is back to normal now i will back-up efs now ! thanks mate i will give you a BIG like
 
Got one problem still , if i go to available networks he tells me Selected network not found (MOBISTAR) , any clue how i could fix this ?

He finds my broadband now and EMEI but just can't connect to network (also not asking for PIN code at boot up)

Should i try to flash this firmware again but wipe efs files?
 
It could be that the firmware was branded to a Luxembourg carrier so won't recognise yours. That 4.1.2 firmware you downloaded will be unbranded and should flash fine now that your phone's up and running so give that another try. If still no luck you may need to check your access point names
Mobile Carrier Settings for Mobistar - Belgium
 
Ok as soon as I'm home I will flash that firmware again now the firmware is an android 4.0.4 Iwill flash the other one again but if I'm not wrong the one we downloaded yesterday was for untied kingdom region ?
 
So , i flashed the firmware again he did everything perfectly

He's now on the unbranded firmware but he's still giving the "unable to cennect to network"

I dont know but he gave me in red a message on my phone "factory mode is on"
so its still the same but he updated everything perfectly

Any other steps i can try?
 
Try removing the SIM and battery for a couple of minutes. While the batterys out also hold the power button for 30 seconds.
 
Also got a blaxk box on start screen (if booted)

PDA : I9300XXEMA1
Phone : i9300XXELLA
H/W : REV__
RF Cal Date : none
SMD :01N,PBA : 04n
Camera : N/A , frontCAM :N/A
TSP = 0xbd
TSK : 0x0
Band : HSDPA, CH : n/a
UART : n/a, USB : N/A
un: CVTF16B2570B05F

This is the complete message i get on my screen.
 
Using root explorer or any root file manager go to
/efs/FactoryApp
Open factorymode in the text editor and if it doesn't say ON change it to ON
 
Aight, I will root tomorrow , I'm so dang stupid ! my cable to connect the phone is still at work pff.. I'll get back to you then, if that's OK for you?


And again thanks for everything , really appreciate it!
 
hi , goodmorning sir!

So i did what you told me , so the phone is rooted again with the link you gave me , all went well !

Booted up great , I needed to initialize again after I used root explorer to efs/factorymode it was OFF edited to ON rebooted , no message (yellow letters in black box) any more so I can register on the network now but after a while he gives me with a warning mark "network unavailable" , but when I use the tool galaxy SIM unlock he tells me EMEI still undefined.

But when i go to settings he still gives me a EMEI number so its not unknown any more.

I was thinking a cousin of me also has a samsung s3 maybe I can back-up he's EFS and restore mine with he's?
 
I was thinking a cousin of me also has a samsung s3 maybe I can back-up he's EFS and restore mine with he's?

I don't think that will work I'm afraid, your IMEI number is unique, and I'm pretty sure that changing your IMEI to a different one is illegal in most places.
 
Don't hate me here.
Everything I've learnt about android says that if you flash firmware or a Rom which is intended for another device your phone will end up in a bootloop but I guess I can throw that book out the window. Since your phone was booted it never occurred that the Rom you had wasn't compatible but I've just spotted this

(AOPK_JB_4.2_d2att-ota-eng.task560...)

The at&t Rom would have an incompatible modem which was probably the course of you having no signal and not the efs folder. The problem you have now with the efs folder was probably caused by trying to restore it to an incompatible Rom. So if you restore the efs.img you made with ktool everything should be fine.
 
Yes indeed it's my own fault , i just flashed a complete wrong file by accident ofc .

It's the hard truth I bricked it myself like most users but I will try to restore the image I made with Ktool of the EFS file

Again thanks for helping a DERP like me LOL
 
Sorry I didn't mean that to come across like that. I was kind of hating myself for not spotting it earlier as it could of saved you a lot of time and effort. :)
 
Soz , just to be sure do I only have to restore the IMG or also TAR?

Dont wanna end up with no boot like last time with that tar file :p
 
Back
Top Bottom