Related
Hi! I just got my xplay a month or two ago, and my last phone was a iphone. As such, stepping from the relatively easier to handle ios to android system's not exactly a piece of cake...
And I still have a couple questions despite lurking in this forums for a while...
1) im running 2.3.2 , rooted with gingerbreak. I heard there's an improvement in battery life.. so im quite tempted to update, but the thought of bloatware coming back kind of scares me.. ._.
So should I update?
2) is unlocked or locked bootloader better?
3) finally, will there be a final or complete version of cm7?
Also, would be great if anyone could explain what is an OTA and kernel...
Thanks!
1) its up to you, it is possible to upgrade with root as long as you have any model except a r800 x
2) I dont think either is better just depends on what you want to do to your phone
3) It depends what you mean by complete. There will probably be a stable version that is better than the stock rom eventually, but im not a dev
Ota means "over the air" and a kernel if im not mistaken is the part of the phone responsible for managing sysyem resources and the like. Not that I know much about anything and I could be wrong lol
Sent from my R800i using XDA App
LemonPlusTea said:
Hi! I just got my xplay a month or two ago, and my last phone was a iphone. As such, stepping from the relatively easier to handle ios to android system's not exactly a piece of cake...
And I still have a couple questions despite lurking in this forums for a while...
1) im running 2.3.2 , rooted with gingerbreak. I heard there's an improvement in battery life.. so im quite tempted to update, but the thought of bloatware coming back kind of scares me.. ._.
So should I update?
2) is unlocked or locked bootloader better?
3) finally, will there be a final or complete version of cm7?
Also, would be great if anyone could explain what is an OTA and kernel...
Thanks!
Click to expand...
Click to collapse
This will be my second numbered answer today. Anyway:
1) What model do you have? I assume it's an r800i or r800a. If it is, I would head over to the development section and check out how to get the UK generic firmware on your phone without unlocking the boot loader. I did that, rooted it, then updated to 2.3.3 and removed a lot of bloat and it's good to go now.
2) I have unlocked the boot loader on every Android I've owned, but I haven't on this phone. I wouldn't until development takes off a little bit more. It will soon, but I probably won't even do it then, personally.
3) Yes, we have great people working on it. It's progressing majorly with each update.
Just next time search before posting...nah, I'm just kidding. Welcome to Android.
adb shove iPad2post.apk to /forum/thread
OTA means you are updating the firmware on your phone through your phone over wifi.
If you didn't remove the boats you can still do it by pressing the software update button on your phone. Just make sure that your bootloader is is still LOCKED.
Sent from my XPlay using XDA App.
Thanks guys! I'll try to flash the firmware on my phone after I get home from school. my xplay is a r800i. Also, if I use the UK firmware and update to 2.3.3, will it affect my ability to update to 2.3.4 as I live in Singapore?
No, when 2.3.4 comes out it would probably be available to generic uk before any other versions. As long as you freeze and not remove boats, you would be able to ota update to 2.3.4
Sent from my XPlay using XDA App.
Hey guys Im back from school.
Is it this thread to follow ?
http://forum.xda-developers.com/showthread.php?t=1119074
Because I saw another one ..
http://forum.xda-developers.com/showthread.php?t=1097591
^ which requires an unlocked BL. :O
Oh my god.. I didnt enable debugging and the process stopped halfway.. now the phone displays an exclaimation mark next to a phone.. did i just brick my phone? ...
EDIT : googled around and now im trying to restore my phone via SEUS...
Ok.. my phone started up fine after running SEUS.. but I clicked restore to factory instead of update..
I want to try updating to 2.3.3 with root again.. So can anyone point out anything I did wrong the previous time?
1. I downloaded the generic UK version (http://forum.xda-developers.com/showthread.php?t=1119074) and flashtool 0.2.8 (http://forum.xda-developers.com/showthread.php?t=920746)
2. I used flashtool and flashed the .tft file and followed the onscreen instructions...
3. the flashing stops halfway cause i didnt enable usb debugging (?) and it causes my phone to be unable to boot up and trauma for me for panicking for 30 minutes. ._.
I tried flashing again with USB debugging on..?
My version is now 2.3.3 after I restored with SEUS, however.
07/046/2011 18:46:02 - INFO - Flashing adsp.sin
07/046/2011 18:46:05 - INFO - Flashing kernel.sin
07/046/2011 18:46:07 - INFO - Flashing amss_fs.sin
07/046/2011 18:46:07 - INFO - Flashing fota1.sin
07/046/2011 18:46:08 - INFO - Flashing fota0.sin
07/046/2011 18:46:09 - INFO - Flashing apps_log.sin
07/046/2011 18:46:09 - INFO - Flashing amss.sin
07/046/2011 18:46:19 - INFO - Flashing cache.sin
07/046/2011 18:46:20 - INFO - Flashing system.sin
07/046/2011 18:46:44 - ERROR - Error flashing. Aborted
07/046/2011 18:46:44 - INFO - Now unplug the device and power it on
07/046/2011 18:46:44 - INFO - Then go to application settings
07/046/2011 18:46:44 - INFO - turn on Unknown Sources and Debugging
( after that resulted in the same problem as before but luckily I knew how to fix it again.. ._. )
It might be that you're not using the latest version of flashtool, it's 0.2.9.1 and it's the beta one and afaik it's the only one to support the play.
Regards Dousan...
Dousan said:
It might be that you're not using the latest version of flashtool, it's 0.2.9.1 and it's the beta one and afaik it's the only one to support the play.
Regards Dousan...
Click to expand...
Click to collapse
I see.. Cause I thought beta might not be stable!
Thanks alot! Time to go try again ^_^
EDIT : Same error with the newest flashtool.. ._.
Crapp...
I unpacked the 0.2.9.1 and ran the X10 Flash Tool... and it still doesnt like me..
It seems it hates me more and more..
now instead of even starting flashing after i send my phone into flash mode it gives me this error..
ERROR - USB\VID_0FCE&PID_ADDE\5&1F015A4B&0&5
Triple edit : Now Im back to square one of flashing till system.sin and getting an error.. ._.
LemonPlusTea said:
I see.. Cause I thought beta might not be stable!
Thanks alot! Time to go try again ^_^
EDIT : Same error with the newest flashtool.. ._.
Crapp...
I unpacked the 0.2.9.1 and ran the X10 Flash Tool... and it still doesnt like me..
It seems it hates me more and more..
now instead of even starting flashing after i send my phone into flash mode it gives me this error..
ERROR - USB\VID_0FCE&PID_ADDE\5&1F015A4B&0&5
Triple edit : Now Im back to square one of flashing till system.sin and getting an error.. ._.
Click to expand...
Click to collapse
Maybe it's a corrupt download or the unpacking of the .zip/.rar file went bad. Could try a reunpacking or/and redownload?
Regards Dousan...
Redownloaded the flashtool 2 times and the generic UK ftf 3 times already.. could it be my computer's problem?
LemonPlusTea said:
Redownloaded the flashtool 2 times and the generic UK ftf 3 times already.. could it be my computer's problem?
Click to expand...
Click to collapse
I know back in my Galaxy S days the firmware tool Samsung used worked on one of my computers but didn't work on the other. I would try another computer if you had access to one.
adb shove iPad2post.apk to /forum/thread
TheBassman369 said:
I know back in my Galaxy S days the firmware tool Samsung used worked on one of my computers but didn't work on the other. I would try another computer if you had access to one.
adb shove iPad2post.apk to /forum/thread
Click to expand...
Click to collapse
Alright, I'll try it with my sister's laptop ^^..
Entire day has been miserable without my apps... :l
Nope.. still doesnt work.. ._.
LemonPlusTea said:
Nope.. still doesnt work.. ._.
Click to expand...
Click to collapse
Man. That's crazy. I have no idea what to do. Hopefully you can get it.
When flashing, have you ticked the 'erase data' (I'm not sure it's the exact name) or are you flashing without erasing? Cus it looks like that's where the error occurs when it's supposed to flash the data?
Regards Dousan...
Did you install the Sony software from your phone first?
Mine needed it to get the drivers. It said it had errors but I let it go for a while and it finished no problem.
Dousan said:
When flashing, have you ticked the 'erase data' (I'm not sure it's the exact name) or are you flashing without erasing? Cus it looks like that's where the error occurs when it's supposed to flash the data?
Regards Dousan...
Click to expand...
Click to collapse
Yeah I checked the erase data box all the time...
@ncaissie, im not entirely sure what you mean... Would you mind explaining?
What is EFS
This part of the device contains some important and some basic info related to our device identity like Bluetooth MAC address, wireless devices MAC addresses, product code (also in the nv_data.bin) and the very main IMEI address (nv_data.bin), programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, and a whole bunch of other things. So you can guess it's will be different for each device and one can't use others.
How it can corrupt :
- Any bad flashing, mishandling system modification can cause this.
- Also It can be corrupted by downgrading stock ROM. If you flash any old ROM (older to first ME6) on newer ROM (ME6 or any other rom released after ME6) it can corrupt EFS. Basically newer ROM believed to have new kernel that changes EFS data which older Modems can't read and results to fail in reading IMEI.
Impact on device/How I know I have corrupted EFS
When there is EFS partition is corrupted, device loses IMEI and due to this device can't gets connected to network. Baseband info also sometimes shows unknown.
-Check your IMEI in setting / by dialling *#06# if it is null OR if it starts with 0049** then IMEI is generic and corrupted. In Normal case IMEI which you can see in device setting or dialing *#06# is exactly same you can see on bill/box/sticker under battery compartment
-If you are unable to connect to network in spite of correct IMEI, chance are
A. Your device is Locked to specific Network OR
B. Your device is banned due to tempered IMEI
-If your AP,CP,CSC all are correct and even you are getting error (unknown CSC XXX) on kies update, it may be due to corrupt Product code in EFS. Read This for detail.
What care should i take
Before flashing anything, first thing you should do is to make EFS backup. Every person who have rooted device should make EFS backup earliest and place it to safer place on PC and /Cloud.
If you are on older ROM, make EFS backup on older ROM as well make another after upgrading ROM too.
If you have already updated to newer ROM, make backup on current ROM.
Here is different common methods for EFS Backup/Restore [There are hundreds of tools available on play store and don't use blindly, as unsupported tool can cause EFS partition failed to mount and to recover it need to use adb shell and more. Better use one of the below mentioned time tested tools]
You must have device rooted. Read post #2 of this thread, how to root Note2
you can use any of method said below.
1.With Aroma installer - No need to have PC, need CWM/TWRP installed. Here is Other Tool I recommend to must have for Newbies, Which also have many other options.
2.From Device itself - No need of PC, just requires installing application from play store.
3.Philz recovery - Also you can find this option on other CWM/TWRP, but i have tested only this.
4.EFS Backup/Restore Tool - you needs to use PC to work this.
How to recover lost IMEI that happens with downgrading ROM
If you have lost IMEI just by downgrading (as said by above by flashing older ROM), still you can recover IMEI without having EFS backup.
-Again upgrade ROM will restore IMEI OR
-Flash latest Modem. You can find it here.. You can download MG1 modem and flash using PC Odin with 'Phone' tab instead of PDA.
Remember above said works only if IMEI is corrupted by downgrading ROM only, if it was corrupted by other things, this won't be helpful.
Also Read This, if you have issue restoring EFS OR device stuck to factory mod.
Hope this will find helpful to all newbies regarding question about EFS and IMEI problem. I have posted this to general section so newbie can post to it if they have any queries.
Informative
Very informative and helpful thread Brother :good::good::good::good:
:good: great guide ketan :good:
you are one of the best things to happen to Note 1 and Note 2 as well..!!
god bless ya bro..! :good::good:
Very informative in precise words!
Thanks, +1:good:
There is already a post about this.
Sent from my GT-N7100 using XDA Premium 4 mobile app
Zionator said:
There is already a post about this.
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can you link to it? I have not found in general section where newbies can post. Though you can report it to moderator if double post.
Sent from my GT-N7100 using xda premium
The EFS image backup has proved to be immensely helpful all the way with the Terminal emulator!:good:
Please confirm: can the EFS backup image be flashed with Philz Recovery as an alternative to the Terminal emulator?
Provided you put it to correct place.
Sent from my GT-N7100 using xda premium
Thank you for info and helpful Pro ^_^
Sent from my GT-N7100 using XDA Premium 4 mobile app
You can easily make efs backup and restore with this app Andromizer(free version) with one click
https://play.google.com/store/apps/details?id=com.j.y.daddy.customizer
These models of note 2 supported
GT-N7100,GT-N7102,GT-N7105,SHV-E250S,SHV-E250K,SHV-E250L
SPH-L900,SGH-T889,SGH-T889V,SGH-L317,SGH-I317M,SCH-I605,SCH-R950
dr.ketan said:
Can you link to it? I have not found in general section where newbies can post. Though you can report it to moderator if double post.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Finally you have listened my request.
Dr.Ketan, he may be talking about this thread.
This guide is very helpfull. :thumbup:
May helps and warn all mates before flashing different roms.
Please make this thread sticky.
sent from my GT-N7100. Press thanks if I helped..
It's already been added to sticky roll up (list of thread worth to stick)
Sent from my GT-N7100 using xda premium
dr.ketan said:
What is EFS
This part of the device contains some important and some basic info related to our device identity like Bluetooth MAC address, wireless devices MAC addresses, product code (also in the nv_data.bin) and the very main IMEI address (nv_data.bin), programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, and a whole bunch of other things. So you can guess it's will be different for each device and one can't use others.
How it can corrupt :
- Any bad flashing, mishandling system modification can cause this.
- Also It can be corrupted by downgrading stock ROM. If you flash any old ROM (older to first ME6) on newer ROM (ME6 or any other rom released after ME6) it can corrupt EFS. Basically newer ROM believed to have new kernel that changes EFS data which older Modems can't read and results to fail in reading IMEI.
Impact on device/How I know I have corrupted EFS
When there is EFS partition is corrupted, device loses IMEI and due to this device can't gets connected to network. Baseband info also sometimes shows unknown.
-Check your IMEI in setting / by dialling *#06# if it is null OR if it starts with 0049** then IMEI is generic and corrupted. In Normal case IMEI which you can see in device setting or dialing *#06# is exactly same you can see on bill/box/sticker under battery compartment
-If you are unable to connect to network in spite of correct IMEI, chance are
A. Your device is Locked to specific Network OR
B. Your device is banned due to tempered IMEI
-If your AP,CP,CSC all are correct and even you are getting error (unknown CSC XXX) on kies update, it may be due to corrupt Product code in EFS. Read This for detail.
What care should i take
Before flashing anything, first thing you should do is to make EFS backup. Every person who have rooted device should make EFS backup earliest and place it to safer place on PC and /Cloud.
If you are on older ROM, make EFS backup on older ROM as well make another after upgrading ROM too.
If you have already updated to newer ROM, make backup on current ROM.
Here is different common methods for EFS Backup/Restore
You must have device rooted. Read post #2 of this thread, how to root Note2
you can use any of method said below.
1.From Device itself - No need of PC, just requires installing application from play store.
2.Philz recovery - Also you can find this option on other CWM/TWRP, but i have tested only this.
3.EFS Backup/Restore Tool - you needs to use PC to work this.
How to recover lost IMEI that happens with downgrading ROM
If you have lost IMEI just by downgrading (as said by above by flashing older ROM), still you can recover IMEI without having EFS backup.
-Again upgrade ROM will restore IMEI OR
-Flash latest Modem. You can find it here.. You can download MG1 modem and flash using PC Odin with 'Phone' tab instead of PDA.
Remember above said works only if IMEI is corrupted by downgrading ROM only, if it was corrupted by other things, this won't be helpful.
Also Read This, if you have issue restoring EFS OR device stuck to factory mod.
Hope this will find helpful to all newbies regarding question about EFS and IMEI problem. I have posted this to general section so newbie can post to it if they have any queries.
Click to expand...
Click to collapse
Dr. Ketan,
Kem chho bhai!!
I am facing problem with EFS , i read your post and come to know that my IMEI is corrupt. It is starting with 0049*** and not matching with phone sticker. Following procedure mentioned in your post but no success!! STill am not able to connect network how should i proceed now??
Already flashed kernel, recovery, modem from pc odin also tried to switch to stock rom. i.e. UAE i guess now downloading Saudi Arabia and will gong to try all.
Please help!!!
You need to mention how does it happen in Details.
How does happend it, i mean what did you flashed? And what rom you had when you flash it.
Do you have efs backup?
Sent from my GT-N7100 using xda premium
Hi Dr. Ketan,
No I don;t have EFS backup and till today flashed many times but not faced any problem like this.
I recently flashed PRobam rom which works on 4.3 android and later return back to my region flashing CWM recovery. Later i tried toolkit for note 2 and tried mod for camera HD.But later come to know that toolkit has no support for my rom.
I think i lost my IMEI while flashing Probam but using wrong baseband trough toolkit can also be problem.No so sure.
Tried to go back on regional rom by different methods but no success.
Thanks!!
Basically it happens if you flash older kernel (it may happened by wrong selection in toolkit)
Reflash latest modem and try.
Just want to get this straight into my head here before I go diving into flashing a ROM sorry for being silly I just like to get it clear lol
Ok my phone is on DME6 so that means I can't flash any samsung based custom ROM that is using a version lower than that yes? but AOSP ROM's don't matter as they don't use the modem so won't corrupt the EFS correct? I am aware that for the SIII there was a flashable zip you can use to make the modem the newer one for flashing older firmware custom ROMS is there one for this? I want to flash this ROM or the HD revolution ROM (HD rev showing an older version in the title) mainly want a custom stock ROM that gets rid of that pesky SMS conversion thing
Thanks for your time
You have already flashed ME6 so you will have latest modem so yes flashiung older ROM you will lose IMEI. regarding AOSP ROM i am not sure, i have never used any AOSP ROM and not following so not familiar with that.
1.Make EFS backup Use one of the tool mentioned in OP)
2.Flash desired ROM, if you select older ROM and lose IMEI, you can find latest modem from my All in one thread (look signature) post #7. simply extract and use modem.tar.md5 to flash with 'Phone' tab (Not PDA) of Odin.
yeah I made a backup of the EFS (on the ME6 version not the older as this is how i got the phone) so I can use any stock based ROM as long as i flash that modem? think i'll probably stay with a ROM labeled as ME6 anyway to keep it easier on myself
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 .
i have g900i
i was on note 7 based rom
after some day of use'my imei is null
baseband unknown
no network signal!!
any help will be appritiatble!!
nikhil_setia03 said:
i have g900i
i was on note 7 based rom
after some day of use'my imei is null
baseband unknown
no network signal!!
any help will be appritiatble!!
Click to expand...
Click to collapse
I just copy what I wrote in another thread (First and second Post):
MysteryIII said:
If you don't have a proper Backup you need to use NV Writer to write IMEI to EFS Partition yourself. Everything about it here.
Read everything careful, it's an immersive action! If you tried everything exactly like described in this thread and it still doesn't work (some kind of connect or R/W error) than you have a fully corrupted EFS Partition. To fix this you need to flash working PIT file for your device and than write IMEI again.
It sounds easy as I write it, but it took me a whole while to find out the trick and you must be extremely careful.
Click to expand...
Click to collapse
MysteryIII said:
Link for NV Reader/Writer is working. You can get latest drivers here. If you have KIES/Smart Switch installed you already have necessary drivers. But make sure any process of KIES/Smart Switch is terminated!
Also check if drivers are installed correctly after connecting device and setting it to RMNET Mode or Download Mode. For me drivers for RMNET weren't installed automatically, so I needed to install drivers manually in Device Manager.
At first I flashed only PIT file than PIT file together with ROM just to be sure. Than it worked and I could write IMEI to "new" EFS partition. I added my own PIT file, you can try if it helps (SM-G900F 16GB).
Here is another tutorial.
Click to expand...
Click to collapse
MysteryIII said:
I just copy what I wrote in another thread (First and second Post):
Click to expand...
Click to collapse
Links not working. Please can you give to the proper links or a walk through of how to fix this issue? My s5 has been broken for 6 months because of this....First i had baseband null then i flashed something and now whenever i turn on my phone it says enter sim unlock code.it was a globally unlocked phone from the beginning. Please help me.
Seems like links in quote broke, but if you go to original posts (linked) they still work.
However I uploaded files I have:
EFS Professional (NV Reader/Writer is integrated in this powerful tool)
NV-Items Reader/Writer
RMNET Driver for S5 (probably need to be installed manually with Device Manager in Windows)
http://www8.zippyshare.com/v/7PT0oMuc/file.html
NV Generator
Official Driver Installer
And here is the link to the alternative method.
€: Links removed. All tools that edit an IMEI are banned here due to legal issues in many countries.
MysteryIII said:
I just copy what I wrote in another thread (First and second Post):
Click to expand...
Click to collapse
i have g900i
u have g900f
is there any problem or procedure is same!!!
MysteryIII said:
Seems like links in quote broke, but if you go to original posts (linked) they still work.
However I uploaded files I have:
EFS Professional (NV Reader/Writer is integrated in this powerful tool)
NV-Items Reader/Writer
RMNET Driver for S5 (probably need to be installed manually with Device Manager in Windows)
http://www8.zippyshare.com/v/7PT0oMuc/file.html
NV Generator
Official Driver Installer
And here is the link to the alternative method.
€: Links removed. All tools that edit an IMEI are banned here due to legal issues in many countries.
Click to expand...
Click to collapse
Brother i have downloaded everything but can't do it properly. The nv writer doesn't detect my phone but the rmnet drivers are installed. Can you please give me some detailed instructions? I can't use a sim in my s5. It has been broken for the last 2 months..
Probably whole partition corrupt (at least this was my problem). In second post I wrote that flashing PIT file fixed it for me.
Somebody else made a new thread to for this question and here is another way to fix it.
MysteryIII said:
Probably whole partition corrupt (at least this was my problem). In second post I wrote that flashing PIT file fixed it for me.
Somebody else made a new thread to for this question and here is another way to fix it.
Click to expand...
Click to collapse
Brother my problem is that at 1st i lost my baseband but after flashing a file through Odin i fixed it but now when i turn on my phone it shows sim locked need unlock code. I bought my phone unlocked. It's a globally unlocked g900f.. Please can you tell me how i can fix it?
Hbk6699 said:
Brother my problem is that at 1st i lost my baseband but after flashing a file through Odin i fixed it but now when i turn on my phone it shows sim locked need unlock code. I bought my phone unlocked. It's a globally unlocked g900f.. Please can you tell me how i can fix it?
Click to expand...
Click to collapse
I'm really sorry, but never had an issue like that. I don't really know if it helps, but try to downgrade to Kitkat ROM and flash compatible pit file + rewrite IMEI. I don't really know if it helps, but as I read along this forum it seems Kitkat ROM is less restrictive.
Hello!
Oneplus 8 pro 12/256.
Such Problem.
CrashDump Mode after MSMdownload tool. I think the problem is with persist.img.
I have backup of persist.img which I made after buying device.
But I can't boot it because bootloader is locked.
I can't unlock bootloader because remote flashing is not allowed.
I can't allow remote flashing in Dev's Options because system doesn't boot.
I have an idea to boot persist.img from msmdownload tool but I don't know how.
I read that on xiaomi devices it is possible.
Can anybody suggest something?
n1kola14 said:
I have an idea to boot persist.img from msmdownload tool
Click to expand...
Click to collapse
Maybe by changing something in ROM for MSMdownload tool. But I don't know how to do it
one idea would be a modified MSMtool that installs TWRP recovery
n1kola14 said:
Hello!
Oneplus 8 pro 12/256.
Such Problem.
CrashDump Mode after MSMdownload tool. I think the problem is with persist.img.
I have backup of persist.img which I made after buying device.
But I can't boot it because bootloader is locked.
I can't unlock bootloader because remote flashing is not allowed.
I can't allow remote flashing in Dev's Options because system doesn't boot.
I have an idea to boot persist.img from msmdownload tool but I don't know how.
I read that on xiaomi devices it is possible.
Can anybody suggest something?
Click to expand...
Click to collapse
This makes no sense. The msm tool overwrites and fixes all partitions. Like, did you have a bad persist.img and use msm, it will revert all to stock. Its basically reinstalling OOS as if phone has no partitions on it. An example, on my oneplus 7 pro using dual boot, I have 3 data partitions a/b/c but when I use msm tool, it fixes and reverts back to a/b. And I don't have the same persist.img that came with phone installed. I had to install a different one
jamescable said:
This makes no sense.
Click to expand...
Click to collapse
Unfortunately, but it is.
I tried India 10.5.13 and global 10.5.4. The same result.
Msm downloads 100% without any mistakes (and locks bootloader) and than I have this:
Qualcom Crash Dump Mode
err_qdi.c:1038:EF:sensor_process:0x1:SNS_REG_INIT :0x5c:sns_registry_sensor.c:94:SNS_RC_SUCCESS == rc
subsys_err_fatal_intr_handlersubsys-restart: Resetting the SoC - slpi crashed. subsys_unregister
n1kola14 said:
Unfortunately, but it is.
I tried India 10.5.13 and global 10.5.4. The same result.
Msm downloads 100% without any mistakes (and locks bootloader) and than I have this:
Qualcom Crash Dump Mode
err_qdi.c:1038:EF:sensor_process:0x1:SNS_REG_INIT :0x5c:sns_registry_sensor.c:94:SNS_RC_SUCCESS == rc
subsys_err_fatal_intr_handlersubsys-restart: Resetting the SoC - slpi crashed. subsys_unregister
Click to expand...
Click to collapse
That might have been what ****ed your phone up. You are ONLY supposed to use the msm tool that matches your model. For me, global msm tool not Europe or china etc. There is a thread in development stating this
If you're going to use MSM, match your device variant it's not safe to rebrand using this method.
If your bootloader locks (which it should). And your fingerprint is still borked..,(which it could still be)
Then unlock the bootloader and run through the persist.img guide found in the guides section.
Tbh the MSM tool doesn't always fix the persist partition that's why people have RMAd their devices before there was a viable fix, otherwise there wouldn't have been like a 100 threads created when the persist issue arised.
FYI you don't need the back up to your persist partition to fix it..
had the same issue. Use Android 11 MSM tool and my battery was low like 0% idk if it helps but try.
Yeh, full battery is a wise idea!
I wish they had a Linux MSM tool for our Chromebooks, etc...
The only thing that fixes and overwrites ur persist partition is SMT download mode in MSM. But BE CAREFUL cuz it will delete ur IMEI and the Widevine certificates from the phone. I used it before and wished I didn't do it, now I'm with 0 IMEI and can't flash unlock_token to unlock bootloader cuz it says verify failed obviously due to no IMEI.
So use it with care and ONLY if you have no choice.
L0ND0NB0Y said:
The only thing that fixes and overwrites ur persist partition is SMT download mode in MSM. But BE CAREFUL cuz it will delete ur IMEI and the Widevine certificates from the phone. I used it before and wished I didn't do it, now I'm with 0 IMEI and can't flash unlock_token to unlock bootloader cuz it says verify failed obviously due to no IMEI.
So use it with care and ONLY if you have no choice.
Click to expand...
Click to collapse
You dont need an unlocked bootloader to fix your imei hit me up on telegram i will help you
gsser said:
You dont need an unlocked bootloader to fix your imei hit me up on telegram i will help you
Click to expand...
Click to collapse
Ok sir I'll PM you as soon as I get home
L0ND0NB0Y said:
Ok sir I'll PM you as soon as I get home
Click to expand...
Click to collapse
hey can you help as my imei is lost and baseband is also showing unknown after i flashed with smt download mode
i have serched everywhere but cant find the solution of this i m feeling dumb now
Nimnim12 said:
hey can you help as my imei is lost and baseband is also showing unknown after i flashed with smt download mode
i have serched everywhere but cant find the solution of this i m feeling dumb now
Click to expand...
Click to collapse
Just use SMT again it'll fix your baseband, and don't use random qcn files to fix IMEI cuz they corrupt the baseband.
L0ND0NB0Y said:
Just use SMT again it'll fix your baseband, and don't use random qcn files to fix IMEI cuz they corrupt the baseband.
Click to expand...
Click to collapse
thanks bro will be replying back if it works or not
Nimnim12 said:
thanks bro will be replying back if it works or not
Click to expand...
Click to collapse
Np I'll wait for response.
thankyou so much bro baseband is back now although imei is still not revered but got a hope
Happy I helped, now you reached my point no IMEI. Hmu on telegram so we can work on a solution @l0nd0nb0y_alt