Database Develop

Problem restoring IMEI

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!

[Q] Desperate Please Help

i recently flashed the firmware back on my sg900a and it wouldnt take ...although odin said it was passing on the fifth try I used my three point cable and it passed but I do not have internet data connection except on wi-fi. Any advice or ideas would be greatly appreciated.

chrislatham08 said:
i recently flashed the firmware back on my sg900a and it wouldnt take ...although odin said it was passing on the fifth try I used my three point cable and it passed but I do not have internet data connection except on wi-fi. Any advice or ideas would be greatly appreciated.
Click to expand...
Click to collapse
More info would help. What firmware version did you flash? What version of Odin did you use? Have you checked your APN? What firmware was running on your phone before you flashed back?

dirtydodge said:
More info would help. What firmware version did you flash? What version of Odin did you use? Have you checked your APN? What firmware was running on your phone before you flashed back?
Click to expand...
Click to collapse
I started with the G900AUCU1ANCE and flashed theG900AUCU2AND3 Doungraded the kernal installed towel root then upgraded the kernal and achieved root. now my device has android version 4.42 baseband version G900AUCU2ANG3 My build number is KOT49H G900AUCU1ANCE Is this mismatch the problem?

chrislatham08 said:
I started with the G900AUCU1ANCE and flashed theG900AUCU2AND3 Doungraded the kernal installed towel root then upgraded the kernal and achieved root. now my device has android version 4.42 baseband version G900AUCU2ANG3 My build number is KOT49H G900AUCU1ANCE Is this mismatch the problem?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3077652
Download this NCE file to your desktop, extract it. Flash the tar.md5 file in the AP slot using Odin 3.09. That should fix your problems. However it will reset your phone to stock so save everything that you may want to your desktop from your phone.

thanks dirtydodge
i did as you said it worked YOUR GREAT

I think I messed up with Twi5sted Lollipop

As in the title I think I messed up when I installed Twi5sted Lollipop; the phone shows the following:
Model Number: SM-G900T (Here I guess is where I messed up because afaik T is for TMobile while I should have A for AT&T)
Android Version: 5.0
Baseband: G900AUCU3BOC4
Kernel: 3.4.0-4432708
Build Number: Twi5ted Lollipop V-7
The phone has lost root and I cannot use Flashfire to install another ROM.
Is there any way to downgrade to stock ROM and then be able to root/flashfire again?

You should be able to I did it with mine 4x in one day trying to get the order right just use Odin to get back to stock and upgrade from there kind of a pain but I think I'm a pro at it now just be sure not to take the 5.1 Ota or you will b screwed

The model number listed in the settings is determined by build.prop, you can make it say butts if you want . I'm the dude who ported the rom, its a T-Mobile rom, therefore the build.prop has the model as g900t, that's fine. The "loosing root" problem you have is pretty easy to fix, you still have root SuperSU is just borked, try reinstalling it and tell me what happens.
Sent from my SAMSUNG-SM-G900A using Tapatalk

Yeah it worked thank for Tha info I love the rom for sure I was wanting to change my bootamation so I dwn loaded the sick bootamation flashed n it sends it into bootloop I've only been doing this for 3 months so I'm pretty new on the changing that stuff using terminal emulator n such

Question about flashing N910TUVU2DOK2 Firmware/Baseband

I'm running an N910T with Rapture 8.2. As this ROM apparently isn't under development or support any longer, I'd like to move to another ROM that is. I'd also like to update my baseband to N910TUVU2DOK2. To update the baseband, do I need to ODIN back to stock and upgrade from there, or can I simply ODIN the baseband and move forward? I believe that I'm currently on COG1, but can't tell because I'm running a backup just now.

dmathis said:
I'm running an N910T with Rapture 8.2. As this ROM apparently isn't under development or support any longer, I'd like to move to another ROM that is. I'd also like to update my baseband to N910TUVU2DOK2. To update the baseband, do I need to ODIN back to stock and upgrade from there, or can I simply ODIN the baseband and move forward? I believe that I'm currently on COG1, but can't tell because I'm running a backup just now.
Click to expand...
Click to collapse
You always need to Odin to the full firmware that matches the ROM you want to use. Please keep in mind that once you go to 5.1.1, you'll be stuck on lollipop bootloader.
Sent from my SM-N910T using Tapatalk

Thanks! Should I ODIN to stock, or straight to the new ROM? I rooted and flashed my old note 2 gobs of times, but the note 4 I'm not that sure about.

dmathis said:
Thanks! Should I ODIN to stock, or straight to the new ROM? I rooted and flashed my old note 2 gobs of times, but the note 4 I'm not that sure about.
Click to expand...
Click to collapse
You use Odin to put stock firmware on and to root and add TWRP. You use TWRP to flash ROM's.
Sent from my SM-N910T using Tapatalk

Thanks! That's just what I needed.

You're very welcome
Sent from my SM-N910T using Tapatalk

Pick_A_Name said:
You always need to Odin to the full firmware that matches the ROM you want to use. Please keep in mind that once you go to 5.1.1, you'll be stuck on lollipop bootloader.
Click to expand...
Click to collapse
I have gone back and forth between 5.1.1, 5.0.1, and 4.4.4 roms by using odin to flash the COG2, COD6, or ANK4 firmware first, then using odin to flash autoroot and TWRP. Then use TWRP to flash the desired rom. I have no problem going from lollipop to kitkat and back. I have used the COG2 firmware for all the 5.1.1 roms, like Texxodus, Resurrection, Slim, CM12, etc. I have used COD6 for 5.0.1 like Alliance, I have used ANK4 for Firekat. I have never had a problem reverting between any of them.
Why is DOK2 different? Does it trip some kind of hardware switch, like knox? If I was on it and used odin to flash, say, the kitkat firmware, what happens? Does odin no longer work when you're on DOK? Does it crash? Does the flash appear to work but it stays on DOK? Does it flash the firmware but bootloop? Does it brick the phone? I always thought that odin flashed firmware to the lowest level so that as long as you could connect the phone to a PC and had a good firmware load, you could restore it.

AT&T Note 3 (USA) - Emergency Call Only

Hi Everyone,
I am kind of lost in the upgrade process.
6 months ago, my Samsung Note 3 (USA AT&T) phone was working perfectly fine, but just with OLD firmware. ,then due to urge on upgrading, i searched so many sites and found a link somewhere on droidviews.com (as my firmware was NJ1 or something, website said i need to upgrade to NC2, and then to OC1), this process messed up my phone call receiving & making capabilities.
Most of the time callers see me unreachable and I am unable to call them as i get "emergency calls only"....I still don't have a way out from this issue. Some places I read i need to install right CSC / modem etc, I even tried this thread by reflashing using ODIN & N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar. Even after this, i still have calls related issues same as above.
Can someone guide me to right direct (or) did i totally messed up with this? BTW, i am now in INDIA, using Airtel services...

I believe nj1 firmware is newer than nc2.
The Odin files came from here: https://forum.xda-developers.com/note-3-att/general/100-stock-lollipop-5-0-n900aucueoc1-t3069609 ?

audit13 said:
I believe nj1 firmware is newer than nc2.
The Odin files came from here: https://forum.xda-developers.com/note-3-att/general/100-stock-lollipop-5-0-n900aucueoc1-t3069609 ?
Click to expand...
Click to collapse
Thanks. I tried flashing to OC1, still same problem. my calls are mostly not working. Is there a way i can go back to original 4.3 stock rom that came with Note3 AT&T? or is there a way i can get current AT&T rom (latest) to try with?
Good part is, i can go between 4.4.3 and 5.0 as i have original stock roms downloaded. But bad part is, my calls still failing...
appreciate any clue/help.

Where did you get the stock ROM? AT&T never released full firmware for the 900a.
There is no way to go back fully to 4.3 since the phone bootloader can be downgraded to 4.3.

audit13 said:
Where did you get the stock ROM? AT&T never released full firmware for the 900a.
There is no way to go back fully to 4.3 since the phone bootloader can be downgraded to 4.3.
Click to expand...
Click to collapse
Hi, i downloaded NC2 & OC1 stock firmwares from XDA only. they are loading up fine (using ODIN). But my calling problem remains same.
So, Yesterday, i tried rooting the phone and installed AllianceROM. then i went into series of issues like "unfortunately NFC has stopped", "unfortunately settings has stopped" etc... then followed the instruction to wipe/factory reset, 3 to 4 times and disabled NFC services etc. As of now, phone works fine, but still need to check the calling function for a week...
thanks for your time.

audit13 said:
Where did you get the stock ROM? AT&T never released full firmware for the 900a.
There is no way to go back fully to 4.3 since the phone bootloader can be downgraded to 4.3.
Click to expand...
Click to collapse
Are we SOL with 900a? I was in the wrong forum earlier and was ready to use update to 7...until I realized it wasn't for me.
Dying on Lollipop (where I landed after the 7 fallout)

I re-read my post and noticed that I made an error: the bootloader on an n900a CANNOT be downgraded.
You cannot flash any ROM to the phone using TWRP, you must use flashfire. Only ROMs based on the stock Samsung ROM can be flashed to the n900a.

audit13 said:
I re-read my post and noticed that I made an error: the bootloader on an n900a CANNOT be downgraded.
You cannot flash any ROM to the phone using TWRP, you must use flashfire. Only ROMs based on the stock Samsung ROM can be flashed to the n900a.
Click to expand...
Click to collapse
We can flash roms using safestrap and flashfire