Related
Well, Hi!
A little history before the real problem.
My girlfriend bought a U8800-51 phone by my recommendations, because it's a great phone in this range of prices.
The phone had a problem. It reboot many times in a day (10~20 times) So I decided to upgrade the OS to GB with the gingermovida v1.1 ROM.
The phone stopped in the bootanimation secuence. I tried 5 times with the same result.
I downloaded the official 2.2.2 ROM from the Huawei website and put it in the SD card. I turned on the phone in download mode and started the install secuence. But stopped in the 2/2 step with the "Update Failed" message.
I tried to enter in recovery mode without success, with 5 different "recovery.img" files. In a thread in this forum somebody explained a method to back to stock froyo ROM using a .img file and the Roadkil's Disk Image tool, but with a AT&T img file.
My brother has the same phone so i made a backup of his phone and put it in my girlfriend phone. Everything works great! Boot OS and load all the information, 3G work and USB Mass storage work, so I did a wipe data - factory reset and everyrhing works again.
At this point I discovered that the IMEI is the same of my brother's phone. I tried many different tricks or tutorials (QPST, CDMA Tool, DFS, AT Command in Terminal, etc) and nothing changed. In the last try I upgraded the OS using CM7 movida v2 and 3G works, WiFi works, but I still have the same IMEI and a new problem came out. When I plug the USB cable and activate the Mass Storage Mode, only shows a Read Only CD drive with all SD Card files.
In the stock froyo ROM I went to the "Project Menu" and changed the USB options, but I can't remember in what option I leave it. In this ROM (CM7 movida v2) i can't go to this menu and check if I have the same Stock ROM configuration.
Besides, I didn't backed up my GF'S IMEI. So I don't know if it can be recovered.
She's gonna kill me, so I need a little help ASAP!
That's all. So here's the thing:
- I have the same IMEI of my brother's phone.
- Everything works except for the Read-Only Mass Storage Mode.
P.S: I don't know if the different driver that I installed affect something here.
Try to upgrade your phone, puting dload folder on sdcard, maybe it can fix your IMEI. About the mounting, I dont know what is happening, but maybe if you upgrade your OS, it will work fine..
What ROM can I use? The Official Huawei ROM (Movilnet U8800-51) didn't work (to solve the IMEI problem) If I try to downgrade using that ROM the phone stop in the 2 step and then I will need to do everything again.
What about B565? You can download it here: http://www.huaweidevice.com/cn/downloadCenter.do?method=toDownloadFile&flay=software&softid=NDEyMTU=
And I also found this topic, there is a user who says the solution so check it out http://forum.xda-developers.com/showthread.php?t=1513439
Well, that ROM is for PRO version of the U8800 phone and I have the U8800-51 version. Baseband and other thing are different between versions. I will try the steps of your link when my girlfriend let me try again
Sorry, my mistake :/
I dont own a u8800 51 but the software isnt the same as u8800?
No, unfortunately, like I said: Baseband and other tiny thing are differents :crying:
-.-" Wait a bit, maybe someone will help you
Do you have any sort of backup from where you were when the phone worked correctly?
that's why I don't share backup. The fw on the -51 is tightly locked. I'm surprised they allowed pink screen. Your better off going for warranty. Unless, you can open the background password. I'll look for an alternative fix.
Sent from my U8800-51
eyeconic said:
Do you have any sort of backup from where you were when the phone worked correctly?
Click to expand...
Click to collapse
I don't have any backup.
Somcom3X said:
that's why I don't share backup. The fw on the -51 is tightly locked. I'm surprised they allowed pink screen. Your better off going for warranty. Unless, you can open the background password. I'll look for an alternative fix.
Click to expand...
Click to collapse
But I tried with differents codes for the background password without success
0, 000, 1234, 111, 999... etc nothing work
xolott said:
I don't have any backup.
But I tried with differents codes for the background password without success
0, 000, 1234, 111, 999... etc nothing work
Click to expand...
Click to collapse
Gotta love Att.
Sent from my U8800Pro using Tapatalk 2
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 .
Hi.
I work in China ow and then and i bought my self a Lenovo K920 yesterday. A GREAT phone but sadly the it does not have any Google programs/system but just a similar Chinese system which i know nothing about. I have found some ROMs out there but on some forum people warns about flashing the Chinese K920pro as it will brick.
Any one here who could tell me how to proceed.... Thanks
__ZOOM__ said:
Hi.
I work in China ow and then and i bought my self a Lenovo K920 yesterday. A GREAT phone but sadly the it does not have any Google programs/system but just a similar Chinese system which i know nothing about. I have found some ROMs out there but on some forum people warns about flashing the Chinese K920pro as it will brick.
Any one here who could tell me how to proceed.... Thanks
Click to expand...
Click to collapse
There's a video showing how to unlock the developer option in settings and the switch to Google UI is inside the Developer Option. Looks quite awesome, im gonna own this phone later.
AyieStyx said:
There's a video showing how to unlock the developer option in settings and the switch to Google UI is inside the Developer Option. Looks quite awesome, im gonna own this phone later.
Click to expand...
Click to collapse
Yes, i read about this too..... I have the Developer Option available already (a few taps on the version number) but no Google UI option there, just 3 options to chose from. Or do you know how to get more options?
I did a try a russian "2014-10-14--10-16-45 K920_ROW_S126_140825.7z" with their "twrp_2.8.0.1_recovery_K920Pro.7z" file but it "killed" my phone....
I can still access the Lenovo Re ovey and the root menu though.. But the operating system just hangs at the Chinese 4G logo.....
Im not able to restart the TWRP again. I start to dislike this odd phone now after spending 30-40 hours to try to get google play, gmail etc to work.. I should have bought a HTC or Samsung instead..
__ZOOM__ said:
I did a try a russian "2014-10-14--10-16-45 K920_ROW_S126_140825.7z" with their "twrp_2.8.0.1_recovery_K920Pro.7z" file but it "killed" my phone....
I can still access the Lenovo Re ovey and the root menu though.. But the operating system just hangs at the Chinese 4G logo.....
Im not able to restart the TWRP again. I start to dislike this odd phone now after spending 30-40 hours to try to get google play, gmail etc to work.. I should have bought a HTC or Samsung instead..
Click to expand...
Click to collapse
You shouldn't do that at the early release of the phone. Even any phone. You need to wait for the official rom release. How about you try fastboot and flash the twrp/cwm recovery. From the recovery use sideload to reflash the stock rom. Keep in mind that you should wait for a review or someone who actually successfully flash the custom roms/non-official rom. Except root, theres a number of successful root.
AyieStyx said:
You shouldn't do that at the early release of the phone. Even any phone. You need to wait for the official rom release. How about you try fastboot and flash the twrp/cwm recovery. From the recovery use sideload to reflash the stock rom. Keep in mind that you should wait for a review or someone who actually successfully flash the custom roms/non-official rom. Except root, theres a number of successful root.
Click to expand...
Click to collapse
I know but i was desperate to get Google to work... Bricked or Chines system is same same for me...
Fastboot and TWRP cant find any device. Factory reset or wipe did not help either. Can access boot menu and Lenovo recovery, but need a recovery file first, and then we have problem with that i cant access the phones internal storage.... And this crap has no SD-memory either...
$700 down the drain for sure... Still have to buy a new phone though, and im still in China... Have to fly to HK to get a new phone... This is going to be expensive.
Thats what happen when you flash the unofficial rom. You know the risk. Make sure you have installed fastboot driver and adb driver. Im sure you can reflash the rom after you able to enter fastboot
AyieStyx said:
Thats what happen when you flash the unofficial rom. You know the risk. Make sure you have installed fastboot driver and adb driver. Im sure you can reflash the rom after you able to enter fastboot
Click to expand...
Click to collapse
Drivers are okay and have worked before. But now when running ABD Devices command, it show "? unautorized" so i get stuck there.
I SOLVED IT....... Except that the both SIM-card shows a red X.. but everything else seems, camera, GPS, WiFi to work AND it has GOODLE PLAY etc now.. Anyone know how to make the phone to work again?
I have tried ABD, Fastboot, TWRP, MiFlash, QPST, QMSCT_DL_EMMC_TOOL but nothing worked except following this instruction
I used the files in the Bin-folder of K920_ROW_S126_140825_user_1408251128 rom
https://forums.lenovo.com/t5/Lenovo-Phones/Lenovo-K910-Vibe-Z-bricked/m-p/1611710#M6838
Flashed back to the Chinese version and the SIM-cards works again... Any idea why the SIM-cards stops to work on the ROW rom?????
__ZOOM__ said:
Flashed back to the Chinese version and the SIM-cards works again... Any idea why the SIM-cards stops to work on the ROW rom?????
Click to expand...
Click to collapse
Slightly different hardware and radio modules.
On lenovo forum there is something about radio calibration.
Hi guys,
Im getting PMs about this...
Yes, I have resolved it. It works to 100% with all i have tested. I will share it with you as soon im back from my business trip in a week or two.
Z
__ZOOM__ said:
Hi guys,
Im getting PMs about this...
Yes, I have resolved it. It works to 100% with all i have tested. I will share it with you as soon im back from my business trip in a week or two.
Z
Click to expand...
Click to collapse
Hi,
can you share with us the method you used to flash row rom on a Chinese K920?
thanks
row rom on china k920
i have chinese version of k920 and i hate the chinese rom on it!Is it possible to explain how can i have the row version working on my phone and have the radio fixed and have the two sim working!I tested row rom and my sims didnt work (no signal).Any help will be appreciated!
lenovo K920 how to active sim card
Hello good friend merry christmas.I have lenovo k920 Chinese version and I flashed the rom k920_ROW_S126_140825, only sim that do not work, how did you solved this? rom the Chinese version was not able to install google play.Can you help me solve this problem ? thank you
flash row rom to china k920pro
-Download ROW firmware in needrom.com and download CN rom modem file.
-Copy the downloaded "NON-HLOS.bin" file.
-Paste "NON-HLOS.bin" to ROW Rom bin folder.
-Flash Row rom the phone (QPST)
Finaly simple and basicly solution.
CN rom Modem file: https://mega.co.nz/#!mMIilAzZ!9DB3fn-69ewVKzdwWFdeTeKL7Si7zf9gims6Cl7OTMk
soulfreem said:
-Download ROW firmware in needrom.com and download CN rom modem file.
-Copy the downloaded "NON-HLOS.bin" file.
-Paste "NON-HLOS.bin" to ROW Rom bin folder.
-Flash Row rom the phone (QPST)
Finaly simple and basicly solution.
CN rom Modem file: https://mega.co.nz/#!mMIilAzZ!9DB3fn-69ewVKzdwWFdeTeKL7Si7zf9gims6Cl7OTMk
Click to expand...
Click to collapse
Did you try it? Is it work?
vgiazitzis said:
Did you try it? Is it work?
Click to expand...
Click to collapse
of course it works otherwise i wouldnt post the solution.After you flash the rom everything works flawlessly but dont update ota to the latest version because you will lose the radio again.
Thank you very much. I will try it right now.
soulfreem said:
of course it works otherwise i wouldnt post the solution.After you flash the rom everything works flawlessly but dont update ota to the latest version because you will lose the radio again.
Click to expand...
Click to collapse
2 sims works? Could you explain me the what I do? The qualcomm program is in chinese. Please. Thank you
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.
I just recently flashed CM13 to my phone and since then i haven't been able to use my network. After looking about i got told to check my baseband number which turned out to be "unknown". I then checked my IMEI number which also turns out to be "unknown". Iv looked at countless posts on all websites to find a fix for this but i still cant seem to find one.
Update:
I have tried to backup my EFS files from my working backup and then restore them on CM13 but havent had any luck.
Iv also been told to update my modem to a 6.0.1 version but i havent been able to find one after searching everywhere.
If anyone can give me link to somewhere that i can download an updated modem or give me clear instructions on how to restore EFS partitions that would be much appreciated.
Is anyone able to help me at all with this? I will provide any screenshots necessary to fix this problem if i need to. I have also continued to look at more posts about how to fix this and still cant seem to find a working fix.
Sorry I don't know the answer but didn't you make full Backup before flash rom. Including esf partition.
If you make backup try to restore.
Chamaka said:
Sorry I don't know the answer but didn't you make full Backup before flash rom. Including esf partition.
If you make backup try to restore.
Click to expand...
Click to collapse
i made a full back up but i have no idea what esf partitions are. If i didnt back them up does that mean i cant fix this?
I have restored my stock rom and the network services work again BUT i still cant get them to work with CM13 or CM12.1
-JoshF said:
I have restored my stock rom and the network services work again BUT i still cant get them to work with CM13 or CM12.1
Click to expand...
Click to collapse
It's always a risk flashing a custom Rom. You must have a Nandroid backup or at least a backup of your EFS.
GrippingSphere said:
It's always a risk flashing a custom Rom. You must have a Nandroid backup or at least a backup of your EFS.
Click to expand...
Click to collapse
i have a nandroid backup of my stock rom and CM13 rom which includes my EFS. i would really like to use CM13 but i still cant get it to work. If anyone knows how to fix this issue on the newest nightly version please tell me.
-JoshF said:
i have a nandroid backup of my stock rom and CM13 rom which includes my EFS. i would really like to use CM13 but i still cant get it to work. If anyone knows how to fix this issue on the newest nightly version please tell me.
Click to expand...
Click to collapse
I haven't flashed a CM Rom since my Galaxy S1 days 6 years ago. I did experience then what you experienced now, getting a corrupted IMEI. I'm not in a good position now to help you as I don't have much experience in CM Roms. Best to ask help from the CM thread.
Alternatively, you can try some EFS backup and restore apps from Playstore to restore your EFS (one of which is Flashfire by Chainfire), or you can search in Xda how to restore a backup of your EFS.
i have updated the post with a little more information if anyone could please help me with this issue that would be great.
anyone willing to help me with this?