Hi, apologies for another one of these threads but I've spent two days trawling the forums and haven't been able to find a fix for my Note 9 Exynos on PIE. Originally an UAE device.
Flashed UK stock rom so I could use Samsung pay, it flashed no problem, however I didn't backup my EFS like a dufus - I have no baseband, no imei's and no cell coverage.
Since then I have flashed back to stock UAE using ODIN and it didn't fix it. It's rooted, OEM unlocked and has TWRP installed.
No matter what method I use to fix, I can't get it working again. Is the phone dead now?
Thanks
Jamie
Same.
I actually accidentally solved it.
I must have flash 10 ROMs trying to fix it and finally, the DevBase ROM from the ROMS section worked.
I'm typing this on my Note 9. I don't know how it worked but it did!
Related
As the title of the thread says, I read the guide to install JVK/JVA/JVB and it says that before flashing I must have my phone unlocked.
When it was only JVK in that thread, I didn't see this note so I flashed it. That was 2 weeks ago and I haven't had any issue with the Network.
I haven't unlocked my phone and I don't want to because I read the guide for unlocking and I can't use adb.
So, can I flash JVB now? Are there any issues that my phone can suffer? I asked in the thread this question but nobody answered me, so that's why I made a new thread.
I'm using a JVB based gingerbread rom without any issues and never unlocked it... In fact this is the first time I heard this...
Sent from my GT-I9000 using XDA App
Warning:
*These firmwares are for International I9000 Galaxy S version, your device must be unlocked before flashing these firmwares.
So, I'm waiting for other opinions...
AS they are unofficial firmwares i guess instruction might be for safety .
Official updates via Kies when 2.3 is released will not need unlocked phones .
jje
flash and see yourself !
I flashed a phone with no root or unlock from 2.1 to 2.3.3 works
I had a hard time trying to root 2.1 and got it boot looping so the last a tempt was a full flash of jvk work and saved the day.
I then was able to use cf-root 3.1 to get root and app from the market to unlock.
I'm ready to do it, but what issues can it cause? I heard something about a code at the first boot that you must enter but I don't know exactly.
Can I downgrade to 2.2.1 stock for example if I have problems?
Edit: I flashed JVB without having any issue. Thanks for the help anyway, I was pretty doubtful about what can happen. All the things work.
Cheers!
Hey folks, im having issues with sim unlocking my galaxy Note. Funny enough ive done that for my girlfriends Note a couple weeks ago. By mistake i deleted the firmware i used to downgrade and now im lost. I used cf-factoryRFS KJ1 to downgrade but it still showing same baseband. So when i try helroz apk it wont unlock the tab. I know it can be Done because my girlfriend Note is the same(hers is white) and mines black. Other than that, same stock firmware and everything. Since its from ClaroPR im afraid of flashing a foreign stock KJ1 because i may lose the csc(PCT for claropr). So if someone can point me to the right direction ill be very happy... Like i said, i know it can be done because i did on hers and its they both came with same firmware and everything. I just forgot the files i used and cant remember exactly which ones.
enelyam said:
Hey folks, im having issues with sim unlocking my galaxy Note. Funny enough ive done that for my girlfriends Note a couple weeks ago. By mistake i deleted the firmware i used to downgrade and now im lost. I used cf-factoryRFS KJ1 to downgrade but it still showing same baseband. So when i try helroz apk it wont unlock the tab. I know it can be Done because my girlfriend Note is the same(hers is white) and mines black. Other than that, same stock firmware and everything. Since its from ClaroPR im afraid of flashing a foreign stock KJ1 because i may lose the csc(PCT for claropr). So if someone can point me to the right direction ill be very happy... Like i said, i know it can be done because i did on hers and its they both came with same firmware and everything. I just forgot the files i used and cant remember exactly which ones.
Click to expand...
Click to collapse
You can download any rom package, extract with 7zip and remove the CSC file (cache.img) and then flash, won't cause any issues and you'll retain your current csc.
Sent from my GT-N7000 using xda premium
Hi,
I'm pretty new to the whole custom ROM scene and have come across a problem when installing CynogenMod version 10.1.3-RC2-galaxysmtd. I've been able to get everything else working but can't seem to get any network service or GPS.
I've read numerous articles on flashing a correct radio or installing a new modem (not sure if this is the same thing or not?) if you can't get any service but haven't done this yet. I've also read articles on moving the files from sdcard\backup\efs into the efs folder in the phone memory which I've tried but doesn't seem to work either.
My baseband version is I9000XXJVT and the rom is running on android 4.2.2. Before the ROM I'm currently on I came from a stock Gingerbread ROM. Was there something I needed to do when coming from a stock ROM that I missed?
Any help on this would be appreciated as I've hit a bit of brick wall
Thanks
Hey there,
So long story short, you've probably lost your IMEI. You can check this by going into Settings -> About Phone -> Status then scrolling down to IMEI. If it begins with 044 or something similar then you know you've lost it.
So to solve this:
1. Flash back to the stock Gingerbread you were on by means of Odin, there are many guides for this but the one http://forum.xda-developers.com/showthread.php?t=2444308 is quite comprehensive (and leave the OP a thanks as well)
2. Download CM9 from the Cyanogenmod website.
3 Root your S again (this will depend on which Gingerbread rom you flash).
4. Boot into CWM recovery. Do the usual data/cache/Dalvik wipes.
5. Install CM9. Let it boot. You don't need to download ICS gapps for CM9 as all you need it to do is boot.
The reason why you install CM9 is to make sure that the IMEI sticks when you then flash a JB rom. Flashing straight to JB from GB tends to lose the IMEI as said before.
6. Once you've let it boot, reboot into recovery again. You don't really need to do the same three wipes again. Install CM10.1.3 RC2. You'll need to flash the zip a few times- three times at least. Flash Gapps as well, of course.
That should hopefully make your signal reception and GPS work
(I covered this quite briefly so if you do need clarification on any of the steps don't hesitate to ask)
Sent from my GT-P7510 using Tapatalk HD
Hi
I checked and I do have an IMEI number which begins with 3 not 0. I also checked the IMEI number and it brought back the correct phone details.
Should I still follow the guid you have linked to or do I not need to do that?
Thanks.
Odd... If the IMEI is intact then you should be geting reception. What you could do is make a backup of your rom and then try the steps I suggested to see if you get the same problem.
Most likely however its due to your modem. In the development thread there's a list of modems compatible with the I9000. Try flash XXJW4 or one for your country through recovery and see if that fixes anything- if not, try the steps.
Sent from my GT-P7510 using Tapatalk HD
I have samsung galaxy note i717d , ihad install jb rom of At&t after installing jb rom my network provider name is showing on notification bar but im not getting any signal...what is the problem please help me out..
nniirraavv said:
I have samsung galaxy note i717d , ihad install jb rom of At&t after installing jb rom my network provider name is showing on notification bar but im not getting any signal...what is the problem please help me out..
Click to expand...
Click to collapse
Wrong forum, find the AT&T Galaxy Note forum and they should have answers there
Sent from my SM-N910U using Tapatalk
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?
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