Related
Recently i have come across a puzzling bug when i flashed deodexed UK firmware S5830IXXLK3 (by Alucard1989PL) and was wondering if anyone else had come accross this,
I flash my phone via ODIN 3.07 to stock XXLK3 UK firmware as normal , this gives me stock kernel & ROM.
I fire up ODIN and flash either Rafael or Hells kernel (it doesnt matter which), reboot, check phone status and i have IMEI.
I root my phone via CWM next just to make sure and check that debug is ticked, reboot.
I then flash the S5830IXXLK3 deodexed ROM via CWM, no problem. When the phone boots i check the phone status and each time i have lost my IMEI number.
On all previous deodexed ROMS i have used i have never come accross this, could it be the latest firmware thats been deodexed or am i overlooking a simple detail here?
Any comments would be appreciated.
Viprdxd said:
Recently i have come across a puzzling bug when i flashed deodexed UK firmware S5830IXXLK3 (by Alucard1989PL) and was wondering if anyone else had come accross this,
I flash my phone via ODIN 3.07 to stock XXLK3 UK firmware as normal , this gives me stock kernel & ROM.
I fire up ODIN and flash either Rafael or Hells kernel (it doesnt matter which), reboot, check phone status and i have IMEI.
I root my phone via CWM next just to make sure and check that debug is ticked, reboot.
I then flash the S5830IXXLK3 deodexed ROM via CWM, no problem. When the phone boots i check the phone status and each time i have lost my IMEI number.
On all previous deodexed ROMS i have used i have never come accross this, could it be the latest firmware thats been deodexed or am i overlooking a simple detail here?
Any comments would be appreciated.
Click to expand...
Click to collapse
I haven't problem with IMEI. The deodexed rom has already root so i don't know why you installed root before you install my deodexed xxlk3 rom -_-" LOL. Try reflash rom with odin than my deodexed rom and at last custom kernel . . .
Alucard1989pl said:
I haven't problem with IMEI. The deodexed rom has already root so i don't know why you installed root before you install my deodexed xxlk3 rom -_-" LOL. Try reflash rom with odin than my deodexed rom and at last custom kernel . . .
Click to expand...
Click to collapse
Hey Alu, i tried all methods but result is the same i lose IMEI number, not to worry for now i will try another deodexed. BTW any eta on when you will release 15 toggle for XXLK3? this will motivate me to try again.
Txs for the reply.
Viprdxd said:
Hey Alu, i tried all methods but result is the same i lose IMEI number, not to worry for now i will try another deodexed. BTW any eta on when you will release 15 toggle for XXLK3? this will motivate me to try again.
Txs for the reply.
Click to expand...
Click to collapse
I'll try in this weekend make this mod for xxlk2 and xxlk3.
Alucard1989pl said:
I'll try in this weekend make this mod for xxlk2 and xxlk3.
Click to expand...
Click to collapse
Good stuff :good:
Viprdxd said:
Recently i have come across a puzzling bug when i flashed deodexed UK firmware S5830IXXLK3 (by Alucard1989PL) and was wondering if anyone else had come accross this,
I flash my phone via ODIN 3.07 to stock XXLK3 UK firmware as normal , this gives me stock kernel & ROM.
I fire up ODIN and flash either Rafael or Hells kernel (it doesnt matter which), reboot, check phone status and i have IMEI.
I root my phone via CWM next just to make sure and check that debug is ticked, reboot.
I then flash the S5830IXXLK3 deodexed ROM via CWM, no problem. When the phone boots i check the phone status and each time i have lost my IMEI number.
On all previous deodexed ROMS i have used i have never come accross this, could it be the latest firmware thats been deodexed or am i overlooking a simple detail here?
Any comments would be appreciated.
Click to expand...
Click to collapse
Hi Viprdxd, I have also just experienced this problem after flashing the same XXLK3 UK firmware and then flashing a custom deodexed ROM that I am currently building. My custom ROM is currently based on XXLI1 firmware and I thought there may be some incompatibility problem. However obviously you have flashed Alucard's XXLK3 deodexed ROM so it can't be that. You say its not a kernel issue either so at the moment I currently have very little idea what is causing this. I need to find out though to make my custom ROM compatible with all firmwares so I will be investigating this issue.
I'm just glad I got my IMEI back by reflashing the XXLK3 firmware with ODIN cause I've already permanently lost it once before when I was a bit of a noob and didn't have a backup or anything!
makeyourself said:
Hi Viprdxd, I have also just experienced this problem after flashing the same XXLK3 UK firmware and then flashing a custom deodexed ROM that I am currently building. My custom ROM is currently based on XXLI1 firmware and I thought there may be some incompatibility problem. However obviously you have flashed Alucard's XXLK3 deodexed ROM so it can't be that. You say its not a kernel issue either so at the moment I currently have very little idea what is causing this. I need to find out though to make my custom ROM compatible with all firmwares so I will be investigating this issue.
I'm just glad I got my IMEI back by reflashing the XXLK3 firmware with ODIN cause I've already permanently lost it once before when I was a bit of a noob and didn't have a backup or anything!
Click to expand...
Click to collapse
Yeah I know that feeling all to well when you see your IMEI number missing I'll keep playing around to see if I can find out why but my feeling is its an issue ROM side with XXLK3., Hey good luck with your ROM I'll defo check it out when its done.
Viprdxd said:
Yeah I know that feeling all to well when you see your IMEI number missing I'll keep playing around to see if I can find out why but my feeling is its an issue ROM side with XXLK3., Hey good luck with your ROM I'll defo check it out when its done.
Click to expand...
Click to collapse
Nice one thanks :good:
Edit: Sorry Actually I still can't figure this out, if I flash XXLK3 with ODIN, IMEI number is fine. If I install Rafael's kernel, nothing else, it disappears.
If I extract the XXLK3 ROM and flash it in recovery no problems, if I deodex it no problems, if I install custom kernels then IMEI dissappears.
Which leads me to the conclusion its a problem with custom kernels except for the fact that if I flash the ROM I'm building on stock kernel IMEI also dissappears!! So for now it remains a mystery!
makeyourself said:
Nice one thanks :good:
Edit: Sorry Actually I still can't figure this out, if I flash XXLK3 with ODIN, IMEI number is fine. If I install Rafael's kernel, nothing else, it disappears.
If I extract the XXLK3 ROM and flash it in recovery no problems, if I deodex it no problems, if I install custom kernels then IMEI dissappears.
Which leads me to the conclusion its a problem with custom kernels except for the fact that if I flash the ROM I'm building on stock kernel IMEI also dissappears!! So for now it remains a mystery!
Click to expand...
Click to collapse
I have concluded that its not a problem with XXLK3 or The custom Kernels as both work, let me explain, XXLK3 standard and deodexed on stock (came with package) kernel works as it should. Raf's or Hell's Kernel works fine on every other firmware.
It seems to be a problem of compatibility of the two maybe Samsung changed some small detail or a tweek is needed in the kernels or both? I don't know as I am not a dev.
My thread on what I found: http://forum.xda-developers.com/showthread.php?t=2052690
:highfive:
I'm now starting to bang my head against the wall. I ave just bought an Orange locked I9305 which I only wanted to unlock to use on another network. Unfortunately I couldn't unlock it as it came with 4.1.2. I read that I had to downgrade to 4.1.1 which is where the problems started. I followed the instructions at the start of this post and made a backup of my IMEI / NV Data which went well. I then installed Odin and tried to install
Product Code: GT-I9305TADEVR (4.1.1) (EE UK)
PDA: XXALI5
PHONE: BVALI5
CSC: EVRALI5
Released: 17/09/2012
from the Pre-Rooted / Original Stock Odin Packages! thread.
I thought this had gone well but it got stuck rebooting at the Samsung screen after the start up swirling screen for at least an hour. I then tried to install the
Product Code: GT-I9305TADEVR (4.1.1) (EE UK)
PDA: XXALK3
PHONE: XXALK2
CSC: EVRALI5
This also got stuck and after another hour I tried to install a stock rom from http://samsung-updates.com/ which was I9305XXALI5_I9305EVRALI5_I9305BVALI5_HOME.tar.md5
This worked and it installed 4.1.1 but when I went to unlock the phone it didn't have any of the menus and when I checked the IMEI it said null / null.
I then though that this isn't too bad as I can just restore the IMEI but when I tried to connect through QPST it sees the port (Com3) but cannot see the phone so I cannot do the restore.
I have tried re-installing QPST after deleting anything in the registry that mentions it, I have re-installed the samsung drivers, I have flashed Param_Bin_I9305.tar.md5 with odin, have rooted properly as there was no superuser app with both busybox and I9305 clockwork mod. These worked ok as I was able to install triangle away and use it and have supersu in my apps.
Does anyone have a clue as to what I can try next as thinking of going back to HTC as I have had there phones since windows and never had a problem rooting and unlocking them
Just a thought I have looked at the box and it says the phone is I9305 PM will this make a difference
gordy1 said:
I'm now starting to bang my head against the wall. I ave just bought an Orange locked I9305 which I only wanted to unlock to use on another network. Unfortunately I couldn't unlock it as it came with 4.1.2. I read that I had to downgrade to 4.1.1 which is where the problems started. I followed the instructions at the start of this post and made a backup of my IMEI / NV Data which went well. I then installed Odin and tried to install
Product Code: GT-I9305TADEVR (4.1.1) (EE UK)
PDA: XXALI5
PHONE: BVALI5
CSC: EVRALI5
Released: 17/09/2012
from the Pre-Rooted / Original Stock Odin Packages! thread.
I thought this had gone well but it got stuck rebooting at the Samsung screen after the start up swirling screen for at least an hour. I then tried to install the
Product Code: GT-I9305TADEVR (4.1.1) (EE UK)
PDA: XXALK3
PHONE: XXALK2
CSC: EVRALI5
This also got stuck and after another hour I tried to install a stock rom from http://samsung-updates.com/ which was I9305XXALI5_I9305EVRALI5_I9305BVALI5_HOME.tar.md5
This worked and it installed 4.1.1 but when I went to unlock the phone it didn't have any of the menus and when I checked the IMEI it said null / null.
I then though that this isn't too bad as I can just restore the IMEI but when I tried to connect through QPST it sees the port (Com3) but cannot see the phone so I cannot do the restore.
I have tried re-installing QPST after deleting anything in the registry that mentions it, I have re-installed the samsung drivers, I have flashed Param_Bin_I9305.tar.md5 with odin, have rooted properly as there was no superuser app with both busybox and I9305 clockwork mod. These worked ok as I was able to install triangle away and use it and have supersu in my apps.
Does anyone have a clue as to what I can try next as thinking of going back to HTC as I have had there phones since windows and never had a problem rooting and unlocking them
Just a thought I have looked at the box and it says the phone is I9305 PM will this make a difference
Click to expand...
Click to collapse
After the initial downgrade all you had to do was reset to factory settings to make it boot again (recovery mode). I would suggest installing the ROM that came with the phone to see if it magically springs back to life.
Restoring back ime
I had the same problem yesterday, but luckily for me i restore back my IME by flashing the paraffin with odin. But the rom on it as at the time when i lost my IME was warmalite. Try the warmalite and then the paraffin this might help.
Thanks guys,
I finally sorted it as it must be a problem with the Pre-Rooted / Original Stock Odin Packages. I finally got it to work by flashing a different kernel, I then unlocked the phone to any network and flashed a 4.1.2 Pre-Rooted / Original Stock Odin Package where it lost all its IMEI again. Flashed a new kernel and all working as I wanted it too as it's now unlocked on 4.1.2.
gordy1 said:
Thanks guys,
I finally sorted it as it must be a problem with the Pre-Rooted / Original Stock Odin Packages. I finally got it to work by flashing a different kernel, I then unlocked the phone to any network and flashed a 4.1.2 Pre-Rooted / Original Stock Odin Package where it lost all its IMEI again. Flashed a new kernel and all working as I wanted it too as it's now unlocked on 4.1.2.
Click to expand...
Click to collapse
Is this new kernel you are flashing the Perseus kernel by any chance?
Rekoil said:
Is this new kernel you are flashing the Perseus kernel by any chance?
Click to expand...
Click to collapse
Yes that's the one I used why does it make a difference?
gordy1 said:
Yes that's the one I used why does it make a difference?
Click to expand...
Click to collapse
The difference is, if I am correct, you are no longer able to use any other kernel. Stock kernels, as well as CyanogenMod or other AOSP-based kernels will no longer properly set up your modem for you, you will need to always run Samsung-based ROMs with a Perseus kernel.
The same is happening with my device, and I have seen a few others as well.
Rekoil said:
The difference is, if I am correct, you are no longer able to use any other kernel. Stock kernels, as well as CyanogenMod or other AOSP-based kernels will no longer properly set up your modem for you, you will need to always run Samsung-based ROMs with a Perseus kernel.
The same is happening with my device, and I have seen a few others as well.
Click to expand...
Click to collapse
Oh well at least the phone is working now where as before I couldn't even restore my IMEI, Just got to hope the phone doesn't break then as I don't think I would be able to send it back with that kernel
Rekoil said:
The difference is, if I am correct, you are no longer able to use any other kernel. Stock kernels, as well as CyanogenMod or other AOSP-based kernels will no longer properly set up your modem for you, you will need to always run Samsung-based ROMs with a Perseus kernel.
The same is happening with my device, and I have seen a few others as well.
Click to expand...
Click to collapse
Right! It happens with my device as well.
I recently tried Adam Kernel which you can download using the Update Me App in Ripper ROM and it worked, my phone worked. So right now you can either use Perseus Kernel which is really good or use Adam Kernel which is far close to the stock one. That kernel isn't in a thread, you have to install Ripper ROM and then download it through the Update Me App if you want to use it.
I just wanted to point that out
Sent from my GT-I9305 using xda premium
jjpro45 said:
Right! It happens with my device as well.
I recently tried Adam Kernel which you can download using the Update Me App in Ripper ROM and it worked, my phone worked. So right now you can either use Perseus Kernel which is really good or use Adam Kernel which is far close to the stock one. That kernel isn't in a thread, you have to install Ripper ROM and then download it through the Update Me App if you want to use it.
I just wanted to point that out
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
Good to know, thanks!
hi everyone i have flashed my note n7000 with a custom rom but now my simcard doesnt work anymore, it was sim free before i started falshing but now it appears to have locked it.
can this happen as i thought the sim lock was at the provider level ?
kev
kevwiener said:
hi everyone i have flashed my note n7000 with a custom rom but now my simcard doesnt work anymore, it was sim free before i started falshing but now it appears to have locked it.
can this happen as i thought the sim lock was at the provider level ?
kev
Click to expand...
Click to collapse
Some more informations will help helping you. What Custom Rom? What exactly do you mean with "doesnt work"? Did you try to change the Sim pin and check if it is recognized again?
ThaiDai said:
Some more informations will help helping you. What Custom Rom? What exactly do you mean with "doesnt work"? Did you try to change the Sim pin and check if it is recognized again?
Click to expand...
Click to collapse
hi thaidai
i installed the revolt jb rom, when i was using it on the stock ICS the sim card would work and get signal and i could make and recieve calls but now since i have put the revolt rom on there it will not get signal at all, i do not have a sim pin on that sim.
Model : GT-N7000 (international)
Android Version : 4.2.2
baseband version : N7000XXLT3
Kernel : 3.0.31-CM-g7ce58e6
kevwiener said:
hi thaidai
i installed the revolt jb rom, when i was using it on the stock ICS the sim card would work and get signal and i could make and recieve calls but now since i have put the revolt rom on there it will not get signal at all, i do not have a sim pin on that sim.
Model : GT-N7000 (international)
Android Version : 4.2.2
baseband version : N7000XXLT3
Kernel : 3.0.31-CM-g7ce58e6
Click to expand...
Click to collapse
could it be the wrong baseband version ?
kevwiener said:
could it be the wrong baseband version ?
Click to expand...
Click to collapse
Reinstall your old Stock Rom and check what happens. Or install the correct JB release for your country.
No need to speculate about the cause.
ThaiDai said:
Reinstall your old Stock Rom and check what happens. Or install the correct JB release for your country.
No need to speculate about the cause.
Click to expand...
Click to collapse
i will give a restore a go from my backup and see how that goes, i could not find the stock rom on the list for my country when i checked before i will let you know how i go
thanks
kevwiener said:
i will give a restore a go from my backup and see how that goes, i could not find the stock rom on the list for my country when i checked before i will let you know how i go
thanks
Click to expand...
Click to collapse
ok i gone back to GB and i get signal now i will go up to ICS and see if this is the same or do you think i could go back to my custom rom from GB ?
kevwiener said:
ok i gone back to GB and i get signal now i will go up to ICS and see if this is the same or do you think i could go back to my custom rom from GB ?
Click to expand...
Click to collapse
ok went upto ICS and that worked also but then when i went to revolt it got stuck in the boot loop and now when i flashed back to GB i cannot get into recovery only download mode what would you suggest to do ? i have flashed the GB rom about 3 times with odin but still the same
kevwiener said:
ok went upto ICS and that worked also but then when i went to revolt it got stuck in the boot loop and now when i flashed back to GB i cannot get into recovery only download mode what would you suggest to do ? i have flashed the GB rom about 3 times with odin but still the same
Click to expand...
Click to collapse
hey thaidai i think i may have found the root cause to my issues and if you could clarify that would be great. it would appear that my sdcard is faulty so would plashing kernels from there have caused the issues i am having ?
Hey guys,
i recently bought an GT-I8190 off eBay. Problem is, it won't connect to any provider's network. It doesn't even find the correct network. It's not a SIM problem, SIM in different phone will find and connect to the right provider.
IMEI is correct though. I flashed cyanogenmod 11 (goldennova) and I8190XXANI4 Baseband. Still not able to connect. I already backed up EFS.
Any suggestions are greatly appreciated!
Hi,
Install by Odin latest stock rom, after restart turn off phone and go to recovery and do factory reset. After this check working connection.
Or here you find solution
http://forum.xda-developers.com/showthread.php?p=45527911
Sent from my GT-I8190 using XDA Free mobile app
eqal said:
Hi,
Install by Odin latest stock rom, after restart turn off phone and go to recovery and do factory reset. After this check working connection.
Or here you find solution
http://forum.xda-developers.com/showthread.php?p=45527911
Sent from my GT-I8190 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for your help. But i think you got me wrong, the problem existed even before i flashed cm. I don't think it has anything to do with cm.
I am on Linux, so i used Heimdall to flash latest Stock ROM. Did a factory reset, from within android and another one from recovery. Didn't help. At least the right provider is shown now, but i still can't connect. Now i am back to where i started, before i flashed cm.
Do you think it would help, if i flash modemFS?
I also checked if my IMEI is stolen here: http://www.amta.org.au/pages/amta/Check.the.Status.of.your.Handset
but I'm in germany, i don't know if their IMEI check is valid for me.
I also tried to repartition during flash, to wipe out all corrupted remainings, but heimdall fails to initialise protocol if i try to repartition. I downloaded my phone's .pit file and used that one.
Thanks in advance!
Still no success.
I tried different ROMs, Stock and Custom, even with repartitioning enabled.
I don't know what to do... must be a problem in one of the files/partitions that aren't touch by a full flash with repart, right?
Please help
Halp
Moootze said:
Halp
Click to expand...
Click to collapse
are you sure is it software or rom problem? maybe its Hardware problem and you should check it in a shop or something? maybe just something inside phone broken during carrier or something.
I'm in the same boat. Have a Swiss factory unlocked phone that I was given by a friend. I decided to flash it to CM11.
I tried initially to do it via the stock recovery but when that failed to due a lack of root I did it via Android Toolkit 1.3.4 which I found through the forum. It loaded the TWRP 2.6.3 recovery and then completed the flash of novafusion CM11 no which I had had already on SD card all by itself pretty much. Before first boot I went in and flashed google apps mini and the "original logo" file that novafusion had under extras.
Upon first boot, there was no cell signal and I've been trying ever since to fix it.
Tried flashing modemfs.zip
Tried flashing versions of stock roms via odin.
Tried the latest I8190N stock rom.
Tried repartitioning via .pit method in odin.
Tried various basebands.
Tried basebands + modemfs
Tried flashing the param/logo file
I'm basically out of ideas...
i9305 Imei shows null/null after flashing I9305XXUFNL1_DBTFNL1 which was a stock rom
Also no signal as you would guess
Now I cant even downgrade to any roms apart from 4.4.4.
Phoen is rooted and tried 4.1.1. I9305XXALI5_I9305EVRALI5_I9305BVALI5 through Odin and Mobile ODIN
On Mobile odin phone looks like its working then stays on the SAMSUNG Logo for ages and nothing, just stays there
I have a Back up of an efs which I done through Rom Manager but not sure if its corrupted or how to restore it
If someone coud give me a walkthrough :highfive:
EwOkie said:
i9305 Imei shows null/null after flashing I9305XXUFNL1_DBTFNL1 which was a stock rom
Also no signal as you would guess
Now I cant even downgrade to any roms apart from 4.4.4.
Phoen is rooted and tried 4.1.1. I9305XXALI5_I9305EVRALI5_I9305BVALI5 through Odin and Mobile ODIN
On Mobile odin phone looks like its working then stays on the SAMSUNG Logo for ages and nothing, just stays there
I have a Back up of an efs which I done through Rom Manager but not sure if its corrupted or how to restore it
If someone coud give me a walkthrough :highfive:
Click to expand...
Click to collapse
Hi,
About IMEI null/null with 4.4.4 firmware, you should search in this Q/A forum, there a lot of threads asking for this issue. Maybe you should get an answer yourself
However, you should try again to do a clean flash of latest official 4.4.4 firmware with ODIN v3.09 by following this GUIDE HERE from @MaHo_66.
AFAIK, it's impossible to downgrade from 4.4.4 because of KNOX bootloader. It has been said many times in this Q/A forum. Maybe it exists somewhere a tricky trick to do it but I'm not aware of this.
FLooDW said:
Hi,
About IMEI null/null with 4.4.4 firmware, you should search in this Q/A forum, there a lot of threads asking for this issue. Maybe you should get an answer yourself
However, you should try again to do a clean flash of latest official 4.4.4 firmware with ODIN v3.09 by following this GUIDE HERE from @MaHo_66.
AFAIK, it's impossible to downgrade from 4.4.4 because of KNOX bootloader. It has been said many times in this Q/A forum. Maybe it exists somewhere a tricky trick to do it but I'm not aware of this.
Click to expand...
Click to collapse
In Addition to @FLooDW 's answer:
Try to use Philz 6.48.4 or 6.59.0 as your recovery rather then TWRP or the old CWM (6.0.4.7), especially DON'T use the latest TWRP from their official website, its a broken build and its known to mess up the partitions! That could be your problem if you have done that before...
Any recovery you want to use, download from my RECOVERY/GUIDE thread that FLooDW linked to you, use those they work fine.
PS. before flashing official firmware with ODIN, make sure you have a custom recovery installed, then boot into recovery, wipe system/data/cache/dalvik-cache/internalSD/boot/modem etc. this is to ensure when you have flashed the firmware, there is nothing left from the previous firmware that was installed.
Note: when explaining your issue, try to do that by providing as much as possible info about your actions before and after the problem occured, that way anyone who wants to help can help you the best way possible.
MaHo_66 said:
In Addition to @FLooDW 's answer:
Try to use Philz 6.48.4 or 6.59.0 as your recovery rather then TWRP or the old CWM (6.0.4.7), especially DON'T use the latest TWRP from their official website, its a broken build and its known to mess up the partitions! That could be your problem if you have done that before...
Any recovery you want to use, download from my RECOVERY/GUIDE thread that FLooDW linked to you, use those they work fine.
PS. before flashing official firmware with ODIN, make sure you have a custom recovery installed, then boot into recovery, wipe system/data/cache/dalvik-cache/internalSD/boot/modem etc. this is to ensure when you have flashed the firmware, there is nothing left from the previous firmware that was installed.
Note: when explaining your issue, try to do that by providing as much as possible info about your actions before and after the problem occured, that way anyone who wants to help can help you the best way possible.
Click to expand...
Click to collapse
Really helpful addition !
Trying what you guys have mentioned just now, let you know as soon as :good:
What 4.4.4. om do you suggest?
Also the efs I backed up (not sure if its working or not as it was with Rom Manager)
How do I restore, can it be done with root explorer?
Tried the [ROM][i9305][18.10.15]>>>4.4.4<<<[KK][STOCK][TW][STABLE][+AROMA] S5 Elite Lite v4.0
which I posted a few days ago, left a post with no reply and thats when I started getting the null/null
PSN_AGNi_pureSTOCK-v5.9.5-4.4.x_I9305_AROMA
Currently trying this rom.. watching the installation set up and says so far that set_perm: some changes failed
used philz_touch_6.59.0-i9305
Rebooting and stays on Samsung Galaxy boot screen ??
EwOkie said:
PSN_AGNi_pureSTOCK-v5.9.5-4.4.x_I9305_AROMA
Currently trying this rom.. watching the installation set up and says so far that set_perm: some changes failed
used philz_touch_6.59.0-i9305
Rebooting and stays on Samsung Galaxy boot screen ??
Click to expand...
Click to collapse
AGNi is not a ROM, this is a kernel. Did you flash AGNi kernel over official Samsung firmware ?
As MaHo_66 said, you have to explain more what you have done and what you need if you want us to help you.
Steps :
reflashed a Stock Rom then Rooted it then added Philz Recovery
Then Tried this rom : I9305XXUFNL1_O2UFOB1_4.4.4_KK.zip
Currently trying various modems to see what this gives me
Failing this will need to try QPTS or EFS Professional again.
* I know how to flash and root roms if you look at my signature along with kernels I am basically telling you what I have tried to get
this null/null away as I think its a baseband/modem issue somewhere as I have read various posts and some people agree.
Cant even do the *#197328640# or *#*#197328640#*#* to get into certain modes
Thinking it maybe the sim card slot now .......... I am losing my mind now!
EwOkie said:
Steps :
reflashed a Stock Rom then Rooted it then added Philz Recovery
Then Tried this rom : I9305XXUFNL1_O2UFOB1_4.4.4_KK.zip
Currently trying various modems to see what this gives me
Failing this will need to try QPTS or EFS Professional again.
* I know how to flash and root roms if you look at my signature along with kernels I am basically telling you what I have tried to get
this null/null away as I think its a baseband/modem issue somewhere as I have read various posts and some people agree.
Cant even do the *#197328640# or *#*#197328640#*#* to get into certain modes
Thinking it maybe the sim card slot now .......... I am losing my mind now!
Click to expand...
Click to collapse
There are few other possible solutions you could try:
- try this, it shows you how to get in service mode and the restoring of the golden efs backup, that should be present if its good.
If above doesnt work, then try the one below.
- have you tried to flash the param_bin file? if not try that with ODIN, it might work.. file attached.
Let us know how it goes.
H yes tied that file and didnt work
will the imei work from another phone or efs?
isnt that link just gps?