Database Users

Please BIG PROBLEM with 6.1 Lightening

This morning my friend give to me a gs2 new but i haven't read what version is.
But i started to download the new lightnening 6.1 and open Odin .
All seems to be correct but after the reboot the sim card dont work.
I try everything ! But the only way to use the phone is flashing by odin the KH3 firmware .
Can anyone tell me if i made some wrong thing ?
The gs2 can be rooted first ? no ?
i can flash the 6.1 lightening in every case or not ?
Thank's

lucalaco said:
This morning my friend give to me a gs2 new but i haven't read what version is.
But i started to download the new lightnening 6.1 and open Odin .
All seems to be correct but after the reboot the sim card dont work.
I try everything ! But the only way to use the phone is flashing by odin the KH3 firmware .
Can anyone tell me if i made some wrong thing ?
The gs2 can be rooted first ? no ?
i can flash the 6.1 lightening in every case or not ?
Thank's
Click to expand...
Click to collapse
Where do you live, what country?
Before you flashed with Odin, did you close Samsung Kies with windows taskmanager (Kies Trayagent and KiesPDLR )?

What the hell! I got the same problem today and I think i´m a quiet experienced user... Under "Baseband" there is just "Unkwown" stated I flashed manually Modems in Odin, restored a backup and tried it in a Stock-rom... This all happened after flashing the Frankenstein KH4.

Not wiped your IMEI i hope....
*#06#
Sent from my GT-I9100 using Tapatalk

It seems that you lost your IMEI number. If you have backed up your /efs folder you can easily restore it. If not you might be able to get a generic IMEI which lets you use your phone again.
There are several threads here on xda and oder sites. There is even a youtube video how to restore your IMEI. Good luck.

My efs folder is backed up and still on my sdcard... I just have to overwrite the old efs folder right? Because i´ve done this and nothing changed. The phone is just completly ignoring my simcard (I also tried different simcards).
PS: And yes *#06# gives me an erased field

Flash back to stock KH3, root it, backup the /efs folder, flash Lite'ning and restore the /efs folder from the backup
Sent from my GT-I9100 using xda premium

I tried now almost everything! Flashed stock, flashed Lightning, restored backup folder and tried to restore a generic one with the youtube tutorial but everything does´nt help meto get rid the proplem with the undetected simcard...

One is your IMEI correct
Two have you flashed a clean stock rom ONLY
Three have you cleaned the sim card contacts and on the phone
Four dialling *#1234# are you showing the correct CSC.
Five are you getting a network connection when entering manual details of the network APN etc .
As you have broken a new phone within a day i suggest you take it to a service centre .
Follow that up by reading the guides before flashing as plainly you don't understand what you are doing .
jje

I´ve just flashed stock KH4. The result was the gone IMEI! I own this device now since two months! Dude dont blame me for this... I´m just not able to restore my backed up IMEI.
My english is not the best but you're a real british guy and you have the possibility to write useful and understandable, particularly with this amount of posts.

Maybe your SGS2 was locked on some network. But.. if you erased EFS, you have to copy back all files and reboot phone. How did youo backe up /EFS? There is a HC-kTool app somwhere on XDA which can backup and restore EFS.
If you manage to restore EFS, run sgs2 sim unlock app to find unlock code (if its sim-locked)
You should explain how did you backup /efs and how did you tried to restore. Maybe restore procedure is not correct.

it´s an fully unlocked device. I have a tar packed backup of the efs folder on my sdcard, but can´t remember when and why I´ve done this. Until now I just overwrote the old efs folder with the original one (i´m not quite sure if it´s a real backup. Is there any way to find that out?) , but is it normal that I don´t even got an generic IMEI?

I had the exact problem with my cousin's SGS II, brand new phone on orange network, when I flashed Lite'ning rom 6.1, got no baseband and no IMEI, flash back to stock XXKH3 and everything fine. Problem for Mr Lite'ning to sort I think. Thing is my release SGS II runs it fine

*** ATTENTION *** STOCK FIRMWARE I9300XXEMG4 -> Changes EFS Folder

Just to update you guys,
What happened?
Several of the guys who flashed the MG4 firmware had their EFS partition modified. Which means that MG4 ROMs work only with MG4 modems at this moment.
Which ROM?
[Stock Official Firmwares] I9300XXEMG4 (4.1.2) - United Kingdom (BTU) and all firmware above MG4
What does it mean to us?
So in case if you have to go back to earlier firmware you will have problems with IMEI. You have to then,
(1) Restore EFS (that is backed up before this change) or
(2) Flash MG4 modem which can still read the modified EFS.
----------------------------------------------------------------------------------------------------
Samsung starting from firmware MG4 is changing the format of the EFS folder partition from one version (read v1) into some kind of new format (read v2). The EFS v2 is only readable by the latest modems from MG4. If an old modem is used with EFS v2 firmware there will be no network connectivity and the IMEI will change to unknown (starting from numbers 0079).
Make a Nandroid / EFS v1 backup, if you plan to flash MG4 firmware or above.
----------------------------------------------------------------------------------------------------
Update: Take a look at the helpful post from User 'JustArchi'
And discussions: here
Thanks: JustArchi, Peter (User:whiskerp) and User:SignetSphere

I have it detailed here too: http://forum.xda-developers.com/showpost.php?p=43935512&postcount=11934

I think this needs more studying, I'm not sating it's not an issue, but I just checked mount points for each partition in adb checking the mounts folder, and that shows this:
/dev/block/mmcblk0p3 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered 0 0
which tells me that /efs is not seen as a folder, but a seperate partition with the mount point mmcblk0p3. Therefore unless the Odin tar has an efs.img inside it cannot be changed flashing a stock rom, and this rom only contains system, recovery, boot, modem, cache, hidden, bootloader and trustzone, so by all rights the update cannot change the efs, therefore the problem you are explaining must be down to something else.

delsus said:
I think this needs more studying, I'm not sating it's not an issue, but I just checked mount points for each partition in adb checking the mounts folder, and that shows this:
/dev/block/mmcblk0p3 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered 0 0
which tells me that /efs is not seen as a folder, but a seperate partition with the mount point mmcblk0p3. Therefore unless the Odin tar has an efs.img inside it cannot be changed flashing a stock rom, and this rom only contains system, recovery, boot, modem, cache, hidden, bootloader and trustzone, so by all rights the update cannot change the efs, therefore the problem you are explaining must be down to something else.
Click to expand...
Click to collapse
Hmm... I kinda of agree to what you're saying. It may not be changing the EFS but it maybe changing on how it reads it I really can't say for sure. The truth is I'm still confused by this issue and since i'm no developer i'm just stating the problem based on what I and some others experienced it. I do hope that a more advanced user(s) can enlighten us with this issue since it can confuse others.

SignetSphere said:
Hmm... I kinda of agree to what you're saying. It may not be changing the EFS but it maybe changed on how it reads it I really can say for sure. The truth is I'm still confused by this issue and since i'm no developer i'm just stating the problem based on what I and some others experienced it. I do hope that a more advanced user(s) can enlighten us with this issue since it can confuse others.
Click to expand...
Click to collapse
I would suggest trying to find a developer who will help us to at least understand what's going on, just mention there is a problem, and try to find the root cause of the issue, then tell people what it is and what they can do.

Yes, let's wait for a developer to zero-in on this.

ysrini said:
Yes, let's wait for a developer to zero-in on this.
Click to expand...
Click to collapse
better change the title of the thread then. Add something like *Not confirmed yet, developer input needed*

SignetSphere said:
better change the title of the thread then. Add something like *Not confirmed yet, developer input needed*
Click to expand...
Click to collapse
I'm not sure if I can edit it now

deleted

EVERYONE on this section of the site (at the least) should be backing up their EFS folder.

His happened to me too => after few hours i lose my IMEI too with just flash modem & ril from this rom (EMG4) and i use Wanam7.1 based on FME7 leak. But thanks to my EFS save . I restored my EFS folder & i recover my original IMEI.
And people READ the Advice on this forum => save your EFS folder before any flashs,mods,unlock, etc ...

I backed up my efs ages ago when i first got my phone to this day i never had to once restore it. Then yesterday i was flashing the new EMG4 and it changed my imei number. so i just restored it woot...

wtf... i have no efs backup.
what can ibdo now?

diddsen said:
wtf... i have no efs backup.
what can ibdo now?
Click to expand...
Click to collapse
Stick with EMG4 modem, it only breaks if you try to downgrade.

delsus said:
I would suggest trying to find a developer who will help us to at least understand what's going on, just mention there is a problem, and try to find the root cause of the issue, then tell people what it is and what they can do.
Click to expand...
Click to collapse
Hello guys. I'm glad to tell you that today I've tested everything attached to this issue and want to let you know.
1. Problem is caused by a modem. On the first boot with XXEMG4 modem it changes /efs folder/partition into some kind of new format.
2. This problem isn't caused by RIL or Samsung ROM. It's caused by a modem. That means it also affects CM/AOSP/AOKP/Other, tested on ArchiDroid 2.X.
3. If we use old modem with already changed /efs we won't be able to connect to the network and our IMEI will change to unknown, starting from numbers 0049.
4. If you don't want to mess with /efs folder anymore or don't have a backup of your old /efs you can temporarily use my emergency zip, which changes modem into XXEMG4, not touching RIL or any other stuff, so it's also compatible with CM/AOSP/AOKP/Other variants.
Most important thing - XXEMG4 doesn't corrupt your /EFS, it changes it into a new format.
For now I strongly recommend to not touch anything linked to XXEMG4 and if you did that already I recommend immediately creating a backup of current already changed /efs partition and using my zip to stay on XXEMG4 modem unless we'll have more info.
I'm using XXEMG4 for about a few days already and don't have any problems with it so we can say that it's stable enough. Just keep in mind changes and you can use it.
It's possible that Samsung made it on purpose so basicly they'll fix it in next release or from now modems pre-XXEMG4 won't be compatible with XXEMG4+.
Thanks, hope it helps.
EDIT:
Yes, you can use any rom for SGS3 with already changed /efs to V2, just stick with my emergency zip and flash it every time you're flashing a new version of your rom. This way you'll have xxemg4 modem whole the time and every rom will work with that. Tested on ArchiDroid 2.0.3 (AOSP), 1.6.1 (XXUFME7) and 1.5.3 (XXEMF1).

JustArchi said:
Hello guys. I'm glad to tell you that today I've tested everything attached to this issue and want to let you know.
1. Problem is caused by a modem. On the first boot with XXEMG4 modem it changes /efs folder/partition into some kind of new format.
2. This problem isn't caused by RIL or Samsung ROM. It's caused by a modem. That means it also affects CM/AOSP/AOKP/Other, tested on ArchiDroid 2.X.
3. If we use old modem with already changed /efs we won't be able to connect to the network and our IMEI will change to unknown, starting from numbers 0079.
4. If you don't want to mess with /efs folder anymore or don't have a backup of your old /efs you can temporarily use my emergency zip, which changes modem into XXEMG4, not touching RIL or any other stuff, so it's also compatible with CM/AOSP/AOKP/Other variants.
Most important thing - XXEMG4 doesn't corrupt your /EFS, it changes it into a new format.
For now I strongly recommend to not touch anything linked to XXEMG4 and if you did that already I recommend immediately creating a backup of current already changed /efs partition and using my zip to stay on XXEMG4 modem unless we'll have more info.
It's possible that Samsung made it on purpose so basicly they'll fix it in next release or from now modems pre-XXEMG4 won't be compatible with XXEMG4+.
Thanks, hope it helps.
Click to expand...
Click to collapse
I wouldn't assume that Samsung will "fix" anything, since this is not broken. I don't think a recommendation to NOT use is advisable at all. Samsung wouldn't risk changing the EFS format of many, many phones only to go ahead and rerun the same risk unchanging them... especially considering the boost in performance this new radio has supposedly brought about.

Kryten2k35 said:
I wouldn't assume that Samsung will "fix" anything, since this is not broken.
Click to expand...
Click to collapse
Same. Especially because I still think that they made it on purpose.
---------- Post added at 09:15 PM ---------- Previous post was at 09:06 PM ----------
Kryten2k35 said:
I wouldn't assume that Samsung will "fix" anything, since this is not broken. I don't think a recommendation to NOT use is advisable at all. Samsung wouldn't risk changing the EFS format of many, many phones only to go ahead and rerun the same risk unchanging them... especially considering the boost in performance this new radio has supposedly brought about.
Click to expand...
Click to collapse
As for now it's just the first release of a new format and it takes some time to prove stability. You can't say after first day of a release that it's completely fine and nothing to worry about . If same situation appears with newer versions then yes, slowly people will change into new /efs base with less worries.

Well, they wouldn't issue the update OTA and via Kies if it was a problem, imho.

Kryten2k35 said:
Well, they wouldn't issue the update OTA and via Kies if it was a problem, imho.
Click to expand...
Click to collapse
Sudden Death also wasn't a problem until some moment .

So if i have this firmware i should play with it at all ?
Can i at least reflash it , i wanna root it , use triangleaway and than reflash whole firmware again with odin ?

[GUIDE] How to restore EFS on I9300

It started when I was trying Swapper 2 from the Play Store. Will, I guess I should read the comment, but I didn't. And yes, it corrupted my EFS and my phone was stuck at the Samsung boot logo. I have tried many method I can search over XDA, but non works. (I'm not sure about this one, which I only find while writing this guide.)
This is by far the easiest method for me, and it doesn't involve Linux, which was a pain since I haven't use Linux in years. I had to VM one for some of the XDA method, which didn't work at end of the day.
1. Flash the firmware with ODIN (original firmware) with original version that you had before. Not the custom ROM, but the original firmware version.
2. Recover with EFS with the EFS image attached in the thread. I used kTool as it faster and easier than any other tool. (Yes, I tried them all...)
3. Download Chimera Tool and buy their cheapest license (or whatever you want) which is €12.90.
That it. Yes you pay, but it the easiest, and most time saving. I spent a week Googling, trying all this various method over ADB, and no, non works. And for Samsung to repair, which they refuse and simply want to change a board and charge me US$ 200 for it, I rather pay €12.90 and do it myself. If you still have problem connection to the network after restoring IMEI, please read post 3.

FAQ
If you need the ODIN, you can find theme over here. Myself I've always used version 3.07. And as always under options you only need the 'Auto Reboot' and 'F. Reset Time' checked. Whether it a modem or stock ROM, click on 'PDA' choose the correct file and than click on start.
Q: Won't flash the EFS image I provide means I'm getting your IMEI?
A: I've wondered this as well. If it were so simple, there wouldn't be so many thread on recovering and so may people cry for help... (I'm included). As my last resort before I buy Chimera Tool's license, I flashed over my bro's S3 EFS, which I didn't want to, as I said it was a last resort. And as it turned out, I didn't get his IMEI. Instead I got his phones' Update S3 product code and serial number. And that was it. IMEI has changed from my previous 'NULL' to the infamous generic 004999010640000.
Q: Why do I still need to do EFS recovery if Chimera Tool can restore it.
A: I've experiment this myself, as I also absolutely did not want my bro's EFS. But unfortunately Chimera can only restore the IMEI and serial number, not rest of the missing files in the EFS folder. If I repartition the EFS folder and using Chimera to restore my IMEI, it would show the correct IMEI but still refuse to connect to the network. And it will have the annoy overly showing my CSC and other bunch of info on my homescreen, as if my EFS is still corrupt.
Q: Does Chimera need some special box?
A: No, a normal USB cable will work. That pretty much means standard ADB command would work, but unfortunately I can't find any info on that. I wish I did, so I don't need to get the Chimera Tool but there was no other way for me. I was also sceptical at first, as I read over many forums and they say it impossible with some sort of service box/tool. I gambled, and luckily it worked out.
Q: Where does the EFS image go for kTool?
A: Sorry, don't remember. Google it, or use the backup option first than overwrite the EFS.IMG file. That what I did.
Q: Now that I got my IMEI back, how do I back it up?
A. Use kTool again? Personally I use TWRP, as I think it the easiest. Since you can do it at a recovery level. No trying of ODIN the OS for corrupt OS before restoring the EFS. In any case, Chimera would still be function for the next couple of month and you can still mess around until than.
Q: Why the need of ODIN the original firmware?
A: I was on a custom TW ROM and Chimera didn't work. Maybe CM and other custom ROM will will work, you can give it a try. But this is how I did it and I know it works.

EFS / Baseband(modem)
It easy to criticize a member and simply tell him use the 'search function', but without realize sometimes the article will help you the most, simply just doesn't come up. Murphy's law. I was on stock 4.1.2 and after restore IMEI and EFS, the phone indicate it register on the network, but I couldn't make calls or connect to the net. This is a vary good article regarding EFS, and sadly it didn't come up easily on my search result. I came across it after I fixed the issue with tones of Googling and was searching for a different topic. But I understand people that desperate need to solve the problem quick (like I was) simply spent hour reading over hundreds of post under that article is just testing a persons sanity. So I'm going to summarised some of the stuff along with my experience. First thing you need to know:
- EFS v2 Basebands (modem) was introduced at Android 4.3 and can read EFS partition v2 and EFS v1
- EFS v1 Basebands (modem) CANNOT read EFS v2, ONLY EFS v1
If you phone is still under warranty and cannot connect to network, the best way is to stay on stock firmware and use TriangleAway to reset the flash counter and sent back to Samsung. With your IMEI number correctly showing, Samsung has absolutely no excuse on not fixing it. If you are no longer warranty, read on.
Q: My IMEI is now showing correctly but I still cannot make calls!
A: This is where the Ariza Patch kicks in. If you are on stock fimware 4.1.2, you need the Ariza Patch to fix the baseband. But after long reading over plenty post, it seems once this patch has been done, it irreversible. So beware. Before you try this patch, you may want to try update to the stock 4.3 firmware and see if it solves the problem before applying the patch.
Q: I'm on stock 4.3, now what?
A: If you still have problem connecting to the network, you need a patched modem (baseband) file. You can find them here. I think this is from the original author who did it. Instead of searching over the forums and files scatter all over the place, I'm pretty sure I dug the link out of XDA while reading through. Someone please tell me if it isn't and provide the the proper link. I'll fix it.
Q: I was on stock 4.1.2 and went to a custom 4.3 ROM, what fix shall I apply?
A: This was my scenario. And I was kind of desperate as well since I just fix my IMEI and was expect the phone to work. I wish I could come across the article on top earlier. I would've tried stock 4.3 first instead of applying the Ariza patch. Any ways, I was on stock 4.1.2 and it didn't work, so I tried a modified 4.3 TW ROM. I wish the OP would mention the EFS thing, which he didn't. I'm not blaming him or anything, but seriously not everyone keep in track of what happening with Android. The OP should mention about the EFS thing or simply post a link such as the topic above and just let people know instead of wasting hours on figuring out why it wasn't working. What I did was, after using the mod 4.3 TW ROM, the IMEI went crazy. So I thought it was corrupt again, so I ODIN back the stock 4.1.2 TW. Than I applied the Ariza patch, wolla, I could call and browse again. So I decide to give the mod 4.3 TW ROM another try. To my surprise, the IMEI still went crazy. So after more Googling only I found out because I wasn't on stock 4.3, my baseband would still 4.1.x. I tried the modem (baseband) patch which for some reason still did not work for me. So I decide to keep the stock 4.1.2 baseband and simply use a custom kernel that could read EFS v1 and v2 - Boeffla Kernel. Remember to download the 4.3 kernel not the 4.1.x! That it, you should now have a working phone.

I just use SA manager .It will backup EFS & MODEM .store it in Ext SD .If EFS corrrrupted just install SA mgr back & restore .
Most important is backup and its very simple process

u need HKCtool to backup efs both img and tar files first of all.
if this is not possible u need a stock rom and odin .after installing stock rom the efs will be repaired.

nainaabd said:
I just use SA manager .It will backup EFS & MODEM .store it in Ext SD .If EFS corrrrupted just install SA mgr back & restore .
Most important is backup and its very simple process
Click to expand...
Click to collapse
Didn't try SA manager as I was in a rush and looking specifically for Samsung phones only. But it definately somehting I want to try if I get a Sony phone. Though I still prefer at a recover level. It just so simple.

keenimo said:
u need HKCtool to backup efs both img and tar files first of all.
if this is not possible u need a stock rom and odin .after installing stock rom the efs will be repaired.
Click to expand...
Click to collapse
TAR file is just a compressed version of IMG file.

im in nairobi kenya, unfortunately i can not buy the chimera tool because we dont have the necessary paying methods. anyone who can lend me theirs please? my S3 has the generic imei, repair would cost 15k here, which is too much. anybody that can help will be highly appreciated.

TNCS said:
It started when I was trying Swapper 2 from the Play Store. Will, I guess I should read the comment, but I didn't. And yes, it corrupted my EFS and my phone was stuck at the Samsung boot logo. I have tried many method I can search over XDA, but non works. (I'm not sure about this one, which I only find while writing this guide.)
This is by far the easiest method for me, and it doesn't involve Linux, which was a pain since I haven't use Linux in years. I had to VM one for some of the XDA method, which didn't work at end of the day.
1. Flash the firmware with ODIN (original firmware) with original version that you had before. Not the custom ROM, but the original firmware version.
2. Recover with EFS with the EFS image attached in the thread. I used kTool as it faster and easier than any other tool. (Yes, I tried them all...)
3. Download Chimera Tool and buy their cheapest license (or whatever you want) which is €12.90.
That it. Yes you pay, but it the easiest, and most time saving. I spent a week Googling, trying all this various method over ADB, and no, non works. And for Samsung to repair, which they refuse and simply want to change a board and charge me US$ 200 for it, I rather pay €12.90 and do it myself. If you still have problem connection to the network after restoring IMEI, please read post 3.
Click to expand...
Click to collapse
you can also downgrade to 4.0.4 and do flash i9300 efs.tar via odin 3.07 but first backup your EFS with helroz's app from here https://market.android.com/details?id=com.boiteoutilssgshelroz&feature=search_result or use any other efs backup maker
But YOU NEVER NEED TO RESTORE EFS after a flash or whenever, just in case you have an issue with it.
if u have 0049xxxx or 00xxxx imei just flash I9300XXUNA7 or any latest android 4.3 and that's it you have your unknown baseband and null imei fixed aka efs corrupt issue.
Warning!!!!
i am not responsible if you get any damage to your device as per my experience i have fixed many i9300's efs and didn't get any problem .
Good luck!
(CHANGE THE ATTACHED FILE'S EXTENSION TO .md5)

Xubair91 said:
you can also downgrade to 4.0.4 and do flash i9300 efs.tar via odin 3.07 but first backup your EFS with helroz's app from here https://market.android.com/details?id=com.boiteoutilssgshelroz&feature=search_result or use any other efs backup maker
But YOU NEVER NEED TO RESTORE EFS after a flash or whenever, just in case you have an issue with it.
if u have 0049xxxx or 00xxxx imei just flash I9300XXUNA7 or any latest android 4.3 and that's it you have your unknown baseband and null imei fixed aka efs corrupt issue.
Warning!!!!
i am not responsible if you get any damage to your device as per my experience i have fixed many i9300's efs and didn't get any problem .
Good luck!
(CHANGE THE ATTACHED FILE'S EXTENSION TO .md5)
Click to expand...
Click to collapse
From what I understand, that still under the condition of prior having an EFS back-up first, right? My guide is for people who doesn't. Like in my situation, where the app screwed up the EFS partition and I had no back-ups.
If you really want in details - Swapper 2 moved the EFS partation on to my ext SD card and format the EFS partition. I was in a flat panic with the soft-brick froze at the Samsung boot logo, assume the SWAP was on the ext SD and screwed it up than format the ext SD. Well, boom, without expectation the app would do something like that and had no prior experience with EFS - no back-ups of EFS at all. And no, full nandroid back-up from CWM does not contain EFS, I've tried that. This isn't some normal scenario of incompatibility between kernel/ROM and EFS/Modem. This is recovery guild for corruption of EFS with NO back-ups.

trying ....

mezo_mmm said:
trying ....
Click to expand...
Click to collapse
And how did it go? The suspense it killing me .

[Q] Problems on N9005 after installing multiple OS

So, my Note 3 N9005 worked fine, then i tried to install CM 12 The phone kept locking so i tried to install CM 12.1 instead. It did the same thing. Then i tried to install CM11. Phone got stuck to a bootloop. Then i tried to install the stock firmware. It launched but the phone lags like hell, apps don't open at all. Waking up the phone takes a lot of time. And the phone doesn't recognize the sim-card anymore. I used CWM to install all the custom roms, and i wiped cache, dalvik cache and did a factory reset every time before i installed a new rom. I used Odin v. 3.04 to flash the stock firmware.
So my question is this, how do i get my phone back up and running smoothly again, like it was fresh out the box? I'll appreciate all the help i can get because i am starting to get very desperate, i really wouldn't like to tell my mom i need a new phone. Note 3 cost like hell after all.
I am from Finland so i used the N9005XXUEND5 version of the stock firmware, KitKat 4.4.2.
The only thing i can think of that can cause this problem is that if the OS's i installed didn't get deleted fully, so there would be multiple OS's on my phone running at the same time. This may be a bit far fetched.
Please help as fast as possible. And i'm not that good at these things so i would appreciate if you could walk me through this step by step and explaining each step as specifically as you can.

Judging from your post, you didn't even bother to read the install instructions of the roms you were flashing.
And this is the result you get.

In CWM recovery mounts and storage format sdcard system cache data preload .
Reboot to download mode and flash stock rom .

The last time i flashed the stock ROM I formatted everything, including the firmwares and such. Now i flashed AOKP ROM and the phone is working fine, except it doesn't recognize the sim card. Any idea how to fix that. Thanks for all the help so far

Basics check you have correct IMEI and correct modem change sim card .

I'm sorry, i have no idea what IMEI and correct modem change sim card. :/

If you don't understand the very basics of flashing and firmware then i suggest you take your phone to a repair shop .Its not a game you are going to end up with a dead phone with no chance of a fix .

I think i understand the very basics of flashing, considering i have done it before twice and on both times it has worked. My sim card worked on my moms Lumia, so is it possible that the sim card reader broke. Can flashing a rom or formatting system do that? Are there a kernel i should flash? I heard it might fix problems like these. And when i go to settings there are no options for IMEI or modem change, that's why i'm confused.
**********************************************
I do have my backup still, but when i try to restore it with CWM, it says something about md5 sums, any idea how to deal with that, because i think that would help if i could use that backup. The stock rom that i downloaded wasn't from any known page. Mostly because SamMobile doesn't have my version anymore for some reason. And i tried to download it from samsung-updates.com but it said that the download would take about 9 hours. I think that the download time would only keep growing and growing so eventually it would be a waste of time.

I think i understand the very basics of flashing,
No you don't and that's your problem this post only makes it more obvious and makes it nearly impossible to give guidance .
MD5 and cwm basics turn off MD5 check in recovery .
You cannot go flashing kernels for no reason .
Modem change is not settings neither is IMEI .
Broken sim reader yes its possible but highly unlikely from a firmware bad flash .
Its entirely possible that you have downloaded a bad firmware .
You also have a non Samsung rom flashed now (aokp)
suggest you read up on that for problems .Though i cannot see any 9005 AOKP roms here .
But first you need to check you have the correct IMEI if your IMEI does not match then you restore the EFS folder you backed up before you started flashing .

I said that i would appreciate that if you would guide me through this step by step. How can i check IMEI? I'm sorry i'm making this so hard for you. The only thing i care about now is that i get my phone back stock and running smooth.
*****************************************************
That is also true that i might have downloaded a bad firmware. Are there any other place to get a stock firmware other than samsung-updates.com?

Download from sammobile.com. It is advised to flash the newest 5.0 firmware on your N9005 (N9005XXUGBOB6) with Odin 3.09 or later.
Check your IMEI from Settings/About device/Status/IMEI. If it starts with 0049, your phone has lost its IMEI. Try flashing to the newest 5.0 firmware to fix it.

WhateverMan said:
Download from sammobile.com. It is advised to flash the newest 5.0 firmware on your N9005 (N9005XXUGBOB6) with Odin 3.09 or later.
Check your IMEI from Settings/About device/Status/IMEI. If it starts with 0049, your phone has lost its IMEI. Try flashing to the newest 5.0 firmware to fix it.
Click to expand...
Click to collapse
I checked and it sais my IMEI is unknown. But i will try to flash that software you suggested

Restore the EFS folder you backed up .

JJEgan said:
Restore the EFS folder you backed up .
Click to expand...
Click to collapse
I think i already said something about it not working because of incorrect md5 sums.

You said backup that's not your EFS backup .
Solution given for MD5 .

JJEgan said:
You said backup that's not your EFS backup .
Solution given for MD5 .
Click to expand...
Click to collapse
I'm sorry that i have to make this hard for you again, but can you tell what EFS backup means and what i'm supposed to do with it?

The EFS folder contains your phones unique identification code or IMEI . Without correct IMEI your phone cannot connect . That is why the EFS folder is backed up before anything is ever flashed . No backup and wrong IMEI then you probably need a service centre repair . EFS/ IMEI can be damaged during flashing that is why rule one is backup your EFS folder first .

Nansus said:
I'm sorry that i have to make this hard for you again, but can you tell what EFS backup means and what i'm supposed to do with it?
Click to expand...
Click to collapse
Dude you are like 12 years old. Why do you even have such a phone? Your attitude toward the dude that was helping you was very rude.
If you don't know what EFS is, it is highly likely that you don't have a back-up. In that case you can try to flash the stock firmware suggested previously. But I really doubt that it will actually magically "cure" your IMEI. I would really go to a service center before you do anymore damage. It could be a little expensive, but at least they do know what they are doing.
That being said, I'm not sure even a service center could help you.

You can restore your backed up EFS folder .
CWM backup restore does not include EFS .
You can flash lollipop .
You can flash a matching modem .
All these may restore IMEI or make the situation worse that is why a service repair is recommended .

phonexpert_alex said:
Dude you are like 12 years old. Why do you even have such a phone? Your attitude toward the dude that was helping you was very rude.
If you don't know what EFS is, it is highly likely that you don't have a back-up. In that case you can try to flash the stock firmware suggested previously. But I really doubt that it will actually magically "cure" your IMEI. I would really go to a service center before you do anymore damage. It could be a little expensive, but at least they do know what they are doing.
That being said, I'm not sure even a service center could help you.
Click to expand...
Click to collapse
I'm sorry if i sounded rude towards to anybody, that is totally not what i'm trying to be. I know you guys are trying to help so i really don't see why i would be rude towards to anyone. I guess my english is still so bad that i'm sounding rude.
I think the best option now is to take the phone to a service repair. Especially if flashing anything can make the situation worse.
I thank everyone that has tried to help. It seems like that i have to accept the fact that i ****ed up my phone. At least this will serve as an example to anyone who's trying to flash custom roms and don't know what they are doing.
Oh, and the reason i have this phone because i'm a student i high school. I just started doing flashing and trying custom roms and i guess i thought it would be really simple. Clearly it wasn't.

(help) baseband unknown n-9005

i've got a baseband problem in my galaxy note 3 snapdragon variant. i try to backup mg efs partition on note 3 using efs pro and it is running on qualcomm mode. after i click backup efs, it reboots and i've got baseband problem. please give some solution. thanks a lot xda.

Your going to have to completely reprogram the radios, I can help you do this...but you need to use Kies 3 and backup EVERYTHING FIRST!
Then message me your exact model and serial number off the sticker under battery! I will get what you need and post instructions

PAPalinskie said:
i've got a baseband problem in my galaxy note 3 snapdragon variant. i try to backup mg efs partition on note 3 using efs pro and it is running on qualcomm mode. after i click backup efs, it reboots and i've got baseband problem. please give some solution. thanks a lot xda.
Click to expand...
Click to collapse
Do you have custom Recovery? If so, enter Recovery and do a backup. Then simplest is to flash a ROM and if that doesn't work, get the latest firmware from Sammobile website and use Odin to flash that, then Restore your data.
Info you should provide for this kind of thing is what firmware or ROM you are running, do you have root access, do you have custom Recovery and if so which one... Also can you get into the phone itself or are you bootlooping? If you can get into the phone does your IMEI still show the same as what is under the battery?
And TBH, no offence KaosMaster, but I am unsure why you'd need the serial number for a fix.

Journyman16 said:
And TBH, no offence KaosMaster, but I am unsure why you'd need the serial number for a fix.
Click to expand...
Click to collapse
I use the serial number to download the OFFICIAL Samsung service files thru KIES to use with ODIN. I use the files to help others. And, IMHO, repairing radios with a messed up device, using ROMS, is kind of a waste....when you can fix everything...and start clean and better off!

KaosMaster said:
I use the serial number to download the OFFICIAL Samsung service files thru KIES to use with ODIN. I use the files to help others. And, IMHO, repairing radios with a messed up device, using ROMS, is kind of a waste....when you can fix everything...and start clean and better off!
Click to expand...
Click to collapse
How is that different to DL'ing the firmware and flashing it? i.e. the 2nd suggestion
I suggest ROM's first because very often, others have had a problem and have constructed the fix into a full system - simple flash can fix things without returning the phone to stock. It's only software after all, and it may be easier to simply flash the non-hlos and modem files than to do whatever it is you're suggesting.
And I am still unsure why you'd need a serial number to get the firmware.

Journyman16 said:
How is that different to DL'ing the firmware and flashing it? i.e. the 2nd suggestion
And I am still unsure why you'd need a serial number to get the firmware.
Click to expand...
Click to collapse
The firmware on SamMobile are images. They are not the same as service files that Samsung uses. These files have everything to re-flash and fix all parts. Including partitions usually. You have to input the model and serial in Samsung software to download the correct service files for that device, and the ones like it.
My method allows ODIN, with the checkboxes marked to completely reprogram the EFS and all parts that are messed up by ROMS.
AND...This method takes 10 minutes to fix everything

KaosMaster said:
The firmware on SamMobile are images. They are not the same as service files that Samsung uses. These files have everything to re-flash and fix all parts. Including partitions usually. You have to input the model and serial in Samsung software to download the correct service files for that device, and the ones like it.
My method allows ODIN, with the checkboxes marked to completely reprogram the EFS and all parts that are messed up by ROMS.
AND...This method takes 10 minutes to fix everything
Click to expand...
Click to collapse
Ah... cool. Not something I'd heard about before. Is the Samsung SW you mention something service agents use or is it available for the rest of us?

Samsung Kies Software
This is my current project...take a peek and what I have done!
http://forum.xda-developers.com/showthread.php?t=3122222