Related
Well I just got my cappy today. I decided to install froyo, I went with cognition.
So i rooted, installed Rom manager, backed up. Installed Titanium backup. Backed up everything i didn't knew what it was. Installed cognition.
After this when it loaded it keeps giving me this error constantly and lagging the phone. Since its my first android phone I'm not sure what to do. I didn't restored anything with Titanium, though I'm not sure if this program does this automatically...
I cleared user data and cache and the error persists.
I'm currently on Ubuntu on my pc so odin is not an option. So I want to have the phone working fast, preferrably with froyo, should i download another rom and reflash with rom manager? Any ideas on what I've done wrong or why the error is displayed?
I'm very thankfull for any sort of help, premature answers are more than welcomed
Either try to get odin to work with ubuntu... Wine?
Find someone with windows PC and odin.
Dual boot xp / 7 and do it yourself
First this is NOT the area for questions per se this is for DEVELOPMENT.
I suggest you try in the General or Q&A section or in this case the Cognition thread since that is the one having issues for you.
Without ODIN I cannot recommend anything so I suggest you try the Cognition thread amigo.
Regards
Just removed my simcard and the error stopped
Does this mean the phone is no longer unlocked?
I bought the phone unlocked so I'm not sure how to restore it to the way it was. Should the unlock code still be somewhere over my phone internal memory? Any quick ideas on how to do this? Or should i look into the whole unlocking post on froyo?
rastanthology said:
Well I just got my cappy today. I decided to install froyo, I went with cognition.
So i rooted, installed Rom manager, backed up. Installed Titanium backup. Backed up everything i didn't knew what it was. Installed cognition.
After this when it loaded it keeps giving me this error constantly and lagging the phone. Since its my first android phone I'm not sure what to do. I didn't restored anything with Titanium, though I'm not sure if this program does this automatically...
I cleared user data and cache and the error persists.
I'm currently on Ubuntu on my pc so odin is not an option. So I want to have the phone working fast, preferrably with froyo, should i download another rom and reflash with rom manager? Any ideas on what I've done wrong or why the error is displayed?
I'm very thankfull for any sort of help, premature answers are more than welcomed
Click to expand...
Click to collapse
Check out this thread...http://forum.xda-developers.com/showthread.php?t=778609. It involves setting up a VM(virtual machine) but that is a very easy task. I hope you find this helpful. But do not flash over Cog. You need to use Odin, flash back to stock, do a master clear and then re-flash Cog via CWM.
You prob's flashed Cognition right after the reboot forced by ClockworkRecovery, so the media scan wasn't completed, phone freaked and just lost most of its powarrrr.
Oh yeah: wrong subforum...
Sorry about the subforum btw
You prob's flashed Cognition right after the reboot forced by ClockworkRecovery, so the media scan wasn't completed, phone freaked and just lost most of its powarrrr.
Click to expand...
Click to collapse
That sounds logic. Any ideas on what should I do so I can make the phone stop giving me this error with my simcard inside?
btw i dont know if this has anything to do but with my simcard inside i noticed 2 things
First it gets gsm signal crashes, looses the signal, regains it and this loops over and over.
After this i also noticed one service restarts over and over when this happens
rastanthology said:
Sorry about the subforum btw
That sounds logic. Any ideas on what should I do so I can make the phone stop giving me this error with my simcard inside?
Click to expand...
Click to collapse
This happened to me once, so I went back into recovery and used CM to reflash. My files were still on the root of the internal SD card, so I figured I'd give it a shot. It worked for me - cleared up my FC problems.
kegobeer said:
This happened to me once, so I went back into recovery and used CM to reflash. My files were still on the root of the internal SD card, so I figured I'd give it a shot. It worked for me - cleared up my FC problems.
Click to expand...
Click to collapse
Sorry for my ignorance, but what do you mean by using CM to reflash? When i boot into recovery i only have three options:
reinstall
clear user data
clear cache
rastanthology said:
Sorry for my ignorance, but what do you mean by using CM to reflash? When i boot into recovery i only have three options:
reinstall
clear user data
clear cache
Click to expand...
Click to collapse
Select reinstall - hopefully it will launch the CM recovery mode. Then you can select to install from the SD card.
Just reinstalled cognition but it still has the same problem. Should i download the i9000 reoriented and try with that one to see if by any chance...?
Did you try reflashing with sim card out? Maybe a master clear would help too?
Yes the last time i tried with the simcard out. I'm guessing the phone is still unlocked, a master clear woudn't change this? If anyone can confirm this I'll try it asap.
I'm downloading as well Doc's rom 7.5 to try reflashing that instead, I can do that or I have to downgrade and then reflash?
Minor723 said:
Did you try reflashing with sim card out? Maybe a master clear would help too?
Click to expand...
Click to collapse
It worked!!!!!!!! It seemed that wiping the data without entering the reinstall menu doest not do the same thing.
Thanks all of you for helping me. I can now go to sleep in peace. Well as soon as i figure out how to put an alarm
rastanthology said:
It worked!!!!!!!! It seemed that wiping the data without entering the reinstall menu doest not do the same thing.
Thanks all of you for helping me. I can now go to sleep in peace. Well as soon as i figure out how to put an alarm
Click to expand...
Click to collapse
How did you do it? I tried reinstalling without sim card and it did not work.
I had the same problem, so I reflashed to factory /w Odin and made sure to wipe cache and data, and it worked without a hitch.
simetra420 said:
I had the same problem, so I reflashed to factory /w Odin and made sure to wipe cache and data, and it worked without a hitch.
Click to expand...
Click to collapse
Did factory w/Odin, then wipe cache and data through reboot and then reinstall the package?
rastanthology said:
Just removed my simcard and the error stopped
Does this mean the phone is no longer unlocked?
I bought the phone unlocked so I'm not sure how to restore it to the way it was. Should the unlock code still be somewhere over my phone internal memory? Any quick ideas on how to do this? Or should i look into the whole unlocking post on froyo?
Click to expand...
Click to collapse
I think the problem could be that your unlock code was deleted. When you flashed. If you can not use odin try this, find the jh7 ota update. I think you can get it from the cognition download page. Flash this it will bring you back to a 2. 1 Rom. Read up on how to unlock your phone. Unlock then copy the unlock code. Then flash cognition again and follow steps to unlock.
If you are on the newest cog make sure you disable the voodoo lagfix prior to flashing. I can not guarantee this will work but it is worth a go. If you created a nandroid prior to flashing once you are on jh7 you should be able to restore
Captivate
Cog 2.2
I have tried to find more about my situation but asking seems to be the only way since all the info is either scattered or not available!
For two weeks I've been trying to fix my note from this ics emmc bug which made me loose efs folder and I have tried several methods with no luck, so I thought that repartitioning sd might kill the bug, so I repartioned just (parts)7,9,10,11 and also went for efs part that was empty anyway thought it might clear bad blocks, although afterwards I flashed efsfix.zip from another thread on here somewhere, because of which network and everything works just no lock screen and power button dialog? And when I flash any rom stock/custom it says (in red) error mounting efs, I found a solution for that by using terminal emulator and commanding "mount", But gotta do it manually afer every reboot?
And my imei is not the same as under my fone, how could I manually edit the imei and insert original fone info?
Could anyone help or guide me to a link so that I can recreate efs partition to ext 4 and the sort out other issues?
Edit: info in-depth!!
Thanks!
Does anyone know how to create/recreate an efs ext 4 partition on galaxy note? Is there a command or certain way to mount efs part as ext 4?
without efs backup you have lost your emei. Unless you resort to illegal methods in most countries (expensive z3x box)
At this point, just go to Samsung and have them illegally legally restore it lmao, they somehow are allowed to do it.
Anyway, how did you analyze its efs thats corrupted, cause if you can flash gb from pc odin succesfully its not super bricked
Sent from my GT-N7000 using Tapatalk 2
recreate can be done by flashing gb with pitfile and option clear efs. Then you should get generic emei. Which stupidly is also blocked in some countries.
That emei stuff is so overrated by secret agencies.
Sent from my GT-N7000 using Tapatalk 2
Thanks for the reply baz77.
Basically, I wasnt aware of this emmc wipe bug when I bought Note, I got my rom flashing experience and knowledge from SGS2, so after like a week of purchase I tried to flash ICS stunnner on my Note with squeaky clean, but resulted in getting my fone back from samsung after being revived, took 3weeks to return.
At this point I still didnt know about the bug because I had assumed that my own doing caused the super hardbrick, till I flash a criskelo rom with a wipe and my problems started off with not registered on network, after that I have been krazily searching and flashing to have the fone working flawless again without having to send the fone back to samsung becasue of the wait and tiny chips n crack on my fone.
And I figured that efs is corrupted by googling and gathering info about my particular problem and everything pointed towards efs being corrupted!
I am really hoping for them release a fix and I can get my fone back working as a whole again!
Edit: added missing words! Lol
Sent from my GT-N7000 using xda premium with Alliance Rom v1.2 + no lock screen and power button dialog!?!?
Could I plz ask, where can I get the stock gb with pit file samsung
Sent from my GT-N7000 using xda premium with Alliance Rom v1.2 + No lockscreen and No Power button dialog!?!?
baz77 said:
recreate can be done by flashing gb with pitfile and option clear efs. Then you should get generic emei. Which stupidly is also blocked in some countries.
Click to expand...
Click to collapse
Apparently, pitfile and efs clear option doesn't work, I tried GB with pitfile got the red 'error mounting efs' and tried stock UK ICS 4.0.3 from (thanks to) Dr.Ketan but Ive still got the error and no lockscreen and faulty power button?!? Plus:- Sim Network is gone :banghead: , i'll just have to flash that efsfix.zip and do the terminal "mount" procedure again!!! manually!
"Probaly Leagality issues there" I'll try the same pitfile procedure with rom from another country if it doesnt work then dont really want to but guess this fone's going back to Samsung for repairs before I sell it off.
Many Thanks for your help!!
<<SUNG>>from my <<SAM>> GT-N7000
baz77 said:
At this point, just go to Samsung and have them illegally legally restore it lmao, they somehow are allowed to do it. 2
Click to expand...
Click to collapse
I have the custom binary count reset, so they shouldnt have any problems with repairing illegally then?? With stock UK ICS 403 Rom from this forum!?!
<SAMSUNG><ASONG> From GT-N7000!
I thought each rom had efs file, not so sure anymore. download and install 7zip, open the tar md5 rom file with it and ignore the warnings. should be efs. img in there, if not best download one, same csc as you have, if you know what it was before it became corrupt. I think kj4 has one, so you can flash whole gb rom with options efs clear and the pitfile.
If that fails, then perform a factory reset with code, do this only from gb, *2767*3855# in dialer. That might force the efs to reset itself to generic. Should not be needed, but hey it cant harm trying on gb. note own risk
If that fails, flash stock ics which you had in first place and ask them to fix it.
You need them anyway to get original emei back, which is why I said best go there. However if you still want to try above could give you a working emei. Its generic test emei and blocked in some countries thought, so if you need to travel...
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
I thought each rom had efs file, not so sure anymore. download and install 7zip, open the tar md5 rom file with it and ignore the warnings. should be efs. img in there, if not best download one, same csc as you have, if you know what it was before it became corrupt. I think kj4 has one, so you can flash whole gb rom with options efs clear and the pitfile.
If that fails, then perform a factory reset with code, do this only from gb, *2767*3855# in dialer. That might force the efs to reset itself to generic. Should not be needed, but hey it cant harm trying on gb. note own risk
If that fails, flash stock ics which you had in first place and ask them to fix it.
You need them anyway to get original emei back, which is why I said best go there. However if you still want to try above could give you a working emei. Its generic test emei and blocked in some countries thought, so if you need to travel...
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Hey baz77,
I tried the same pitfile method with a GB236 Rom built from HongKong and flashed it twice, because I read on this forum somewhere that in the event of errors, missing files and apps after a flash, roms should be flashed atleast once more to get'em fully loaded but unfortunately even that method failed to mount the efs part.
Afterwards, I was just googling for more solutions and I decided to download and flash another GB236 rom Open europe built (wipe version) from Dr. Ketan's stock rom deposites and to my joyous surprise there were 2 extra tar. files, one named efs.md5.tar, so I quickly got my fone in download mode and flashed the rom with pitfile and when that was done, I got the fone back in download mode and Flashed the efs.tar (PDA), CSC, Modem (PHONE) and for the first time in 2 weeks the fone booted up normally as it should with the welcome screen, working lock screen and power button dialog! pheeeewwww!!!
But the imei is still not the same as under the hood, but I guess since the efs part had been corrupted, my fones probabaly using the emergency imei, Im using Alliance v1 with no apprent faults or errors.
i'll flash the GB Rom and try the factory rest code method by you and if it works then dont have to go to samsung and if doesnt then i'll keep using the fone as it is for as long as I have it and keep looking for solutions, if nothing happens then i'll get it sorted from samsung before selling it.
Your help is much appreciated, Thanks baz77!!! :thumbup: :thumbup:
<SAMSUNG><ASONG>from<GT-N7000
back then.. there was an application on playstore that can fix IMEI issues... its called GSII repair.
https://play.google.com/store/apps/...GwsMSwxLDEsImNvbS5oZWxyb3ouR1NJSV9SZXBhaXIiXQ..
It worked mostly on all phones that I have heard of.. including the Note's of my friends whom their IMEIs got toasted.
See if you can give that a shot bud..
Ps. by the way.. most corrupted IMEIs have a mocked imei of 004999010640000
Others said that they were able to restore their original IMEI by flashing to stock GB, root the phone and install Root explorer, after that, you need to go to /EFS folder inside your phone(thru root explorer) and backup first your orig ' nv_data.bin ', now if you see a nv_data.bak in there with a previous date different from the bin file, then delete accordingly the nv_data.bin and rename the bak file to nv_data.bin reboot phone and check if orig IMEI is back on your phone.
Now this isn't applicable if your bak and bin files for ( nv_data) are all on the same date though.
don't try this yet unless your willing to give all possible options to restore back your original IMEI. Don't forget to try first the link I showed to you at the top.
Cheers.
:good:
letters_to_cleo said:
back then.. there was an application on playstore that can fix IMEI issues... its called GSII repair.
https://play.google.com/store/apps/...GwsMSwxLDEsImNvbS5oZWxyb3ouR1NJSV9SZXBhaXIiXQ..
It worked mostly on all phones that I have heard of.. including the Note's of my friends whom their IMEIs got toasted.
See if you can give that a shot bud..
Ps. by the way.. most corrupted IMEIs have a mocked imei of 004999010640000
Others said that they were able to restore their original IMEI by flashing to stock GB, root the phone and install Root explorer, after that, you need to go to /EFS folder inside your phone(thru root explorer) and backup first your orig ' nv_data.bin ', now if you see a nv_data.bak in there with a previous date different from the bin file, then delete accordingly the nv_data.bin and rename the bak file to nv_data.bin reboot phone and check if orig IMEI is back on your phone.
Now this isn't applicable if your bak and bin files for ( nv_data) are all on the same date though.
don't try this yet unless your willing to give all possible options to restore back your original IMEI. Don't forget to try first the link I showed to you at the top.
Cheers.
:good:
Click to expand...
Click to collapse
Hi Letters_to_cleo,
Thank you for the suggestions mate, at the moment Im on Alliance v.1 403 rom, and I have just tried the fix from your link, did the steps1 & 2 restarted checked imei and it's the same serial (#to#) as you have stated, then i tried the step 3 which indicated that the nv_data.bin file is missing from that folder.
I have already gone to certain extents to return the fone in its generic state, so it won't matter if I tried once more besides trying repairs on GB rom is probably much safer then on ICS builts as long as the fone doesnt die on me,(completely again!), I 'll try your 2nd method in a bit and report back after!
Thanks for the support!!:thumbup:
<SAMSUNG><ASONG>from<GT-N7000
yeah that app wont work if you dont have efs backup. It distills from original. bak file the emei, now with the reflash of efs, even before you had lost it. only generic stuff left.
you need as mentioned before to go to samsung to repair emei, or find a phone place that can do it. You can yourself but in most countries its illegal. You need z3d box or equivalent for that, 150$$$$ lol, I have seen people who bought it offer that service for small fee. But be careful as ot could be illegal in your country, even if its going from generic emei to original emei lol.
Oh and you are welcome, been there done that, with the efs stuff. Samsung fixed mine.
My help is free, now if another has this you know how to help them
After Samsung fixes it,stay on gb, root phone and backup efs on multiple locations(pc, cdrom, floppy disk, bank vault you get it) In future when you buy android do that first. How to is in dr ketans toolbox thread in general section.
edit efs backup is not in nandroid, nor titanium backups. In fact still to date there is not one solution that can back everything up on your phone.
Sent from my GT-N7000 using Tapatalk 2
letters to cleo, corrupt emeis are empty or 0000000000000000000000000,
the 490000 emei is given when resetting efs. That is not corrupt anymore to my knowledge
Sent from my GT-N7000 using Tapatalk 2
oh I ran into missing lockscreen issues after fully fixing it, I have in my profile then statistics started a thread which links to a solution for that
Sent from my GT-N7000 using Tapatalk 2
Hi Enseven reporting,
@Letters_to_cleo, the methods you suggested dont work but thanks for trying to helping, i didnt find the bak file in efs folder but there 2 nv_data files, and they're both dated from Jan2011, renaming them just disable's the network and doent change the imei#, it remains the same!
@baz11, Yes mate, you are right this fone's going back to samung bcuz im not looking to $pend 150 on some box that I wont even use twice.
Im not really that fussed about imei not being as same on fone hardware, just as long the fone works, but like you said it probably is illegal to sell a fone with messed up serial no.
And on top of that fone's price would drop for having software issues, only wanted to fix it so that I could sell it on without loosing much $$ from the original price I paid for it, it'll be disapointing since Ive only had the fone for just over 2 months.
And I did manage to fix the welcome/lockscreen/power button issues by flashing efs.tar I got from that wipe version Open Europe Rom but even after the flash, it restore's the needed files but doesnt really prompt the features so I gotta insert this command through terminal emulator: "echo n- ON> /efs/imei/keystr" "sync"and factory reset, then the fone reboots normally with everything working but the IMEI ofcourse!
Wonder if your lockscreen fix works ive looked for it on your profile's statistic's tab but uable to find it, could you plz provide a link. Thanks
Ive tried all methods with some luck and no further progress apart from having to buy expensive equipment, so I guess i'll keep using the fone and looking for any miraculous solution till I resort to Samsung.
P.S: If they cant find a fix for the emmc bug by working on scripts , they should atleast invent a nano tech powder (gadget bug killer) to sprinkle on the motherboard, LOL!!!
because this problem goes way back, like another user said on here you could make a movie about now, and ithink it started off as a scifi now its a scifi/thriller, "shall I wipe before flashing & risk hardbrick Or shall I wait for samsung to pace up the support!!!
Thanks to xda and memebrs for being online 247 and all the support though!!
<SAMSUNG><ASONG>from<GALAXY-GTN7000>using xda premium!!!
Hi En7,
Sorry to hear my steps didn't work on your phone bud.
I checked some forums here in XDA and I've come across this one: http://forum.xda-developers.com/showthread.php?t=1804117. (I'm not sure though if you have come across that link before or not).
It is for the S3 forum but there's a tool in there that you can try to download and run to somehow restore your corrupted IMEI. It's worth taking the risk I should say but who knows..any given tool/info is highly useful and it could be a clear shot in bringing back your original IMEI back right?
Cheers bud!
lol that cracked me up nano powder hahaha good one.
you found the lockscreen fix, its the same fix I found while back from some guru.
I guess you can change emei to original with someone who has such a box. Finding is not to difficult, just need to go to a shop that can repair emei. Preferably Samsung thought, Just go to a samsung service centre, or store where you bought phone. Best unroot and put stock firmware that matches your phones original csc, to avoid anoying questions. Just tell the truth you updated phone and emei was gone/changed and you want original imei back. Samsung can fix it. Note, this time dont use pit or clear csc. Its not needed anymore.
I searched hard and long when I had that issue with emei, wasnt without a backup able to change it back to original, other then Samsung or such a box.
It annoyed the crap out of me. I can relate to what you were going through.
Everybody is nandroid this titaniun backup that, apparently efs is the only thing not standardly backed up with any standard mainstream solution.
Sent from my GT-N7000 using Tapatalk 2
oh, and good idea, maybe you should write a scifi thriller
Sent from my GT-N7000 using Tapatalk 2
Hello guys
Is there a way to disable "Wrong IMEI Notification" on system startup?
I know how to restore IMEI, but my network works fine with generic IMEI, so I don't care about it much.
The only thread I was able to find is here:
http://forum.xda-developers.com/showthread.php?t=1862416
It's about 4 months old and no answer is given.
Currently I'm running Helly Bean 4.2.1 (Release - 05.01.13)
Thanks in advance
archildroid said:
Hello guys
Is there a way to disable "Wrong IMEI Notification" on system startup?
I know how to restore IMEI, but my network works fine with generic IMEI, so I don't care about it much.
The only thread I was able to find is here:
http://forum.xda-developers.com/showthread.php?t=1862416
It's about 4 months old and no answer is given.
Currently I'm running Helly Bean 4.2.1 (Release - 05.01.13)
Thanks in advance
Click to expand...
Click to collapse
It's cooked into the system apps, so unless someone has the knowledge to change it, the answer is no.
Fixing the problem is quite easy though and takes 15min at most after a good TiBu backup, if it gets too annoying, take that extra 15min
BWolf56 said:
It's cooked into the system apps, so unless someone has the knowledge to change it, the answer is no.
Fixing the problem is quite easy though and takes 15min at most after a good TiBu backup, if it gets too annoying, take that extra 15min
Click to expand...
Click to collapse
I flashed "i897uckk4 Odin One Click NO Bootloaders, Re-partition, Full Wipe" - IMEI is still some generic 0049...
What should I do now?
archildroid said:
I flashed "i897uckk4 Odin One Click NO Bootloaders, Re-partition, Full Wipe" - IMEI is still some generic 0049...
What should I do now?
Click to expand...
Click to collapse
Is it still giving you the error msg?
Is your phone a refurb?
BWolf56 said:
Is it still giving you the error msg?
Is your phone a refurb?
Click to expand...
Click to collapse
I was on Helly Bean 4.2.1 and it was giving me an error message because of wrong IMEI.
I didn't have efs backup, so I backed up everything and flashed stock kk4 assuming that it would restore my IMEI, but it's still 00499...
So how do I restore my IMEI?
No it's not refurbished.
archildroid said:
I was on Helly Bean 4.2.1 and it was giving me an error message because of wrong IMEI.
I didn't have efs backup, so I backed up everything and flashed stock kk4 assuming that it would restore my IMEI, but it's still 00499...
So how do I restore my IMEI?
No it's not refurbished.
Click to expand...
Click to collapse
That's actually how you restore your IMEI.. By flashing Odin KK4. Did you restore anything after flashing?
I went ahead and did a little google search (which can go a long way ). Here's what I got: http://forum.xda-developers.com/showpost.php?p=24175451&postcount=2
BWolf56 said:
That's actually how you restore your IMEI.. By flashing Odin KK4. Did you restore anything after flashing?
I went ahead and did a little google search (which can go a long way ). Here's what I got: http://forum.xda-developers.com/showpost.php?p=24175451&postcount=2
Click to expand...
Click to collapse
First I flashed Odin kk4 - wrong IMEI, reflashed few times, no luck. Than Eclair, Froyo - same result
Guide mentioned above didn't help, there were no files in /data/radio, and there is no folder /factory, or /data/factory. I copied nv_data.bin from /efs to /data/radio set chmod 700 but it didn't change anything.
Any more ideas?
Seems like I'm just unlucky (
Now flashed back to HellyBean 4.2.1, restoring backups...
archildroid said:
First I flashed Odin kk4 - wrong IMEI, reflashed few times, no luck. Than Eclair, Froyo - same result
Guide mentioned above didn't help, there were no files in /data/radio, and there is no folder /factory, or /data/factory. I copied nv_data.bin from /efs to /data/radio set chmod 700 but it didn't change anything.
Any more ideas?
Seems like I'm just unlucky (
Now flashed back to HellyBean 4.2.1, restoring backups...
Click to expand...
Click to collapse
Umm Your file explorer probably doesn't have root rights if you can't see those or you have to show hidden folders in settings.
BWolf56 said:
Umm Your file explorer probably doesn't have root rights if you can't see those or you have to show hidden folders in settings.
Click to expand...
Click to collapse
I'm using ES File Explorer (root settings were checked, permissions granted) and Yes, I rooted device (first flashed corn kernel).
Already flashed HellyBean 4.2.1 (10JAN13). Will take a chance after restoring backups.
Just tried to do like described in the link - folder /data/radio is empty for me, unable to find /factory folder
I wonder why flashing stock kk4 didn't restore IMEI ((
I backed up efs folder after installing Odinkk4, but I don't think it can help.
Good thing is that my carrier works just fine no matter IMEI
Anyway, thanks for trying to help me out. :good:
@archildroid, Josh at Mobiletechvideos.com I believe can restore your imei without having a back up. There will be a charge for it, but next to Adam Outler, you won't find a better set of tech fix it hands.
Sent From The Land Of Frag
I have tried lots of methods to restore my IMEI, but no luck.
One thing I encountered: This wrong IMEI popup has "Galaxy S Settings" icon in the corner, so I froze it with Titanium and the popup disappeared.
Of course you lose all the abilities, that Galaxy S settings have - TV Out, Color tuning etc.
I hope someone with sufficient knowledge will modify Galaxy S Settings, to disable this popup.
P.S. Before changing anything in system apps, MAKE NAND BACKUP, I'm not responsible for anything you do to your phone!
archildroid said:
I have tried lots of methods to restore my IMEI, but no luck.
One thing I encountered: This wrong IMEI popup has "Galaxy S Settings" icon in the corner, so I froze it with Titanium and the popup disappeared.
Of course you lose all the abilities, that Galaxy S settings have - TV Out, Color tuning etc.
I hope someone with sufficient knowledge will modify Galaxy S Settings, to disable this popup.
P.S. Before changing anything in system apps, MAKE NAND BACKUP, I'm not responsible for anything you do to your phone!
Click to expand...
Click to collapse
Usually, going back to stock KK4 with Odin fixes your IMEI problem. Once there, you make a backup of your efs folder and you're set for your android's life. It's a one time backup (as long as you don't delete it..) and can be restored whenever.
Hi all, I've seen that there are a few threads in this and other forums that are saying that using a particular other persist will help restore IMEI, Volte, or other lost functionality after installing a custom Rom and reverting back to stock nougat. As this sort of suggestion has resulted in many devices being permanently broken, I'm sharing a thread I made in potter.
Fix Persist, resolve IMEI=0, Explanation, Requirements
Now, the most important thing here is to NEVER EVER flash another device's persist. Your persist contains key files that have your IMEI data (in encrypted form), and it will not work with another device (or vice versa). In the thread above, I explain what has been happening, how to detect it, what can be done to fix (note - this may differ from device to device - I recommend not applying the fix until after other who have 'fully working devices' can confirm key details, such as the "rfs" user), and why other persist files gave the appearance of working (but were actually causing permanent damage).
Also note that the fix is for stock nougat. I have already seen in the cedric devices that the upcoming Oreo may apply the same type of fix on boot (i.e. changing ownership of key folders and files).
Happy to answer any questions if people ask. Please keep questions for this device in this thread.
Is there any hope to fix IMEI 0?
Himanshu.Shukla said:
Is there any hope to fix IMEI 0?
Click to expand...
Click to collapse
It all depends on what you have or haven't done. If you flashed another persist, you're out of luck. If you haven't flashed another persist, back it up now and save it to the cloud so you never lose it. Then the principles in the guide may help. You can see if you are affected or not by following the section 1), as long as you are on a stock nougat rom.
NZedPred said:
Hi all, I've seen that there are a few threads in this and other forums that are saying that using a particular other persist will help restore IMEI, Volte, or other lost functionality after installing a custom Rom and reverting back to stock nougat. As this sort of suggestion has resulted in many devices being permanently broken, I'm sharing a thread I made in potter.
Fix Persist, resolve IMEI=0, Explanation, Requirements
Now, the most important thing here is to NEVER EVER flash another device's persist. Your persist contains key files that have your IMEI data (in encrypted form), and it will not work with another device (or vice versa). In the thread above, I explain what has been happening, how to detect it, what can be done to fix (note - this may differ from device to device - I recommend not applying the fix until after other who have 'fully working devices' can confirm key details, such as the "rfs" user), and why other persist files gave the appearance of working (but were actually causing permanent damage).
Also note that the fix is for stock nougat. I have already seen in the cedric devices that the upcoming Oreo may apply the same type of fix on boot (i.e. changing ownership of key folders and files).
Happy to answer any questions if people ask. Please keep questions for this device in this thread.
Click to expand...
Click to collapse
Dude , thank you so much for that thread and Info. Finally someone is starting to explain the root cause of this IMEI/4G/Volte mess in our devices. Unfortunately I got my phone second hand and the dude had flashed a lineage ROM on it. He had mentioned radio problems but has said he had flashed the wrong modem and fixed it. The phone was 100% operational with the Lineage ROM he had on it so I didn't think much of and I figured since I've been rooting/flashing my phones since the day I got my first android, I could deal with it anyway. In any case, I soon went to flash an 8.1 ROM and discovered my IMEI gone. Eventually I found a few 8.1 ROMs that worked and I'm completely happy with AEX 5.2 which I'm on now. I have the EFS and Persist backups as of the moment I acquired the phone. I wondering though if there is a way to tell if my persist is the one that is supposed to be there or if the owner flashed a different persist? Also when I input the terminal command from your post it returns a list of folder within persist but no ownership tags as shown in your post.
jesslegentil said:
Dude , thank you so much for that thread and Info. Finally someone is starting to explain the root cause of this IMEI/4G/Volte mess in our devices. Unfortunately I got my phone second hand and the dude had flashed a lineage ROM on it. He had mentioned radio problems but has said he had flashed the wrong modem and fixed it. The phone was 100% operational with the Lineage ROM he had on it so I didn't think much of and I figured since I've been rooting/flashing my phones since the day I got my first android, I could deal with it anyway. In any case, I soon went to flash an 8.1 ROM and discovered my IMEI gone. Eventually I found a few 8.1 ROMs that worked and I'm completely happy with AEX 5.2 which I'm on now. I have the EFS and Persist backups as of the moment I acquired the phone. I wondering though if there is a way to tell if my persist is the one that is supposed to be there or if the owner flashed a different persist? Also when I input the terminal command from your post it returns a list of folder within persist but no ownership tags as shown in your post.
Click to expand...
Click to collapse
I think the only way to tell if the persist is definitely the one for the phone is to revert to stock nougat, follow the guide (I did find that one of the posters in the thread tried it on their sanders device and it worked for them - fortunately there is enough consistency so that the guide applies to many phones) to fix the folder ownership, then erase EFS and reboot. If your IMEI comes back, you're in luck. If it doesn't, hold onto your EFS backup for the rest of your phone's life!
(Also note that reverting to stock nougat should be done carefully. Don't downgrade the bootloader, otherwise you'll run into other problems..)
Also, just to emphasize, the output from the commands that list ownership is taken from nougat. Oreo has changed things, so it's not surprising if you get different things. E.g. Cedric's Oreo appears to not have an rfs user, instead it is using something like oem_2903.
Just wanted to chime in and say that this has fixed my phone! I've had iffy VoLTE and other issues since going back to stock and couldn't even use custom ROMs since it wouldn't allow me to search for a network. This seems to have cleared it all up. Thanks!
thanks a lot. I've had no lte data since the day I got the phone, but thanks to this it is fixed.
edit: for verizon peoples who only had 3g, I can confirm that lte still works after flashing at least msm xtended so probably other roms too.
any solution to this problem, i installed this rom and now baseband is not found and imei zero
sanders-twrp-flashable-OPS28.49-2.zip
jakson7474 said:
any solution to this problem, i installed this rom and now baseband is not found and imei zero
sanders-twrp-flashable-OPS28.49-2.zip
Click to expand...
Click to collapse
Folks, the rom above was a test version of the Oreo soak test that I made. Unfortunately it seems the is an issue on the build. I have pulled it for now. Hoping that a downgrade to stock nougat will help fix it. Goodness knows I'm trying to help with the IMEI issue, not contribute to it *facepalm*
Edit: user got everything back by flashing a nougat twrp flashable build. So issue was definitely just in that particular Oreo build
Can anyone confirm if this should work on the g5s plus with those commands? It doesnt seem to for me
Nyvia said:
Can anyone confirm if this should work on the g5s plus with those commands? It doesnt seem to for me
Click to expand...
Click to collapse
I can confirm it worked on my xt1806.
Back up the EFS, run these commands, then run the fastboot commands to wipe your modem. It will rebuild and you should have imei back
Nyvia said:
Can anyone confirm if this should work on the g5s plus with those commands? It doesnt seem to for me
Click to expand...
Click to collapse
Can you check if you have a file dhob.bin.bak after running the find command in the post? Many people who don't have success with the guide are missing that file.
I have successfully executed this procedure and I got a hd calling option or an hd calling icon..is that correct??. Then I backed up the efs and again i got to custom ROM then and flashed the efs partition but no sign of volte or can't make call from Jio...
The question is can I use the efs partition which I recovered through this on a custom ROM?
subinsrk said:
I have successfully executed this procedure and I got a hd calling option or an hd calling icon..is that correct??. Then I backed up the efs and again i got to custom ROM then and flashed the efs partition but no sign of volte or can't make call from Jio...
The question is can I use the efs partition which I recovered through this on a custom ROM?
Click to expand...
Click to collapse
Answer as per the other thread:
Yes, I get an H+ icon on my phone, so that would be what you'd want if the procedure worked. If Volte doesn't work on the custom rom, then it's a custom rom issue.
my volte worked without restoring the efs... just fixed permissions from stock, flashed rom, everything worked.
xtasquee said:
my volte worked without restoring the efs... just fixed permissions from stock, flashed rom, everything worked.
Click to expand...
Click to collapse
Bro how you can fix the volte can you tell me?
just flashed stock and fixed the permissions like op said. when i rebooted everything was fixed and still works with at least gzosp-based roms and probably others too. no tricks needed.
Thank you bro...it's worked backuped the efs and persist partion on the stock ROM and again flashed pe ROM and reflashed the efs and persist volte is now working fine thanks....
is there a way to get this post pinnedor something?
Hi guys. Reported success earlier in the thread but my issues came back. IMEI is there, everything functions properly in stock, but in non-stock I get an "error searching for network" that I didn't get before I flashed a broken gapps file that edited my persist file.
I know my persist partition is currently stock, and I'd like a copy of a working persist file from an xt1806 that I can copy my known good persist data to. Thanks!
I have a G5S plus (xt1806) on sprint. Every rom I flash results in me not having LTE, and 3G cuts in and out unreliably. I have checked and my imei is still there. I have flashed the modems, and I have restored my efs backup to no avail. This has happened on every rom, no matter if I clean flash, dirty flash, I end up with the same result. Does anyone have any insight on this?
L4ndon said:
I have a G5S plus (xt1806) on sprint. Every rom I flash results in me not having LTE, and 3G cuts in and out unreliably. I have checked and my imei is still there. I have flashed the modems, and I have restored my efs backup to no avail. This has happened on every rom, no matter if I clean flash, dirty flash, I end up with the same result. Does anyone have any insight on this?
Click to expand...
Click to collapse
I had a similar issue on Verizon. When I got the phone I never inserted my new sim card & connected to the network before I unlocked the bl, flashed TWRP, custom ROM, etc. Every ROM I flashed had the same issue as you describe in your post.
Solution: I backed everything up to a pc & fastboot flashed back to stock & started over. Everything has been fine ever since.
***Keep that efs backup you made too - just in case you lose IMEI on your return to stock; efs restore should fix it.
Bob nesta said:
I had a similar issue on Verizon. When I got the phone I never inserted my new sim card & connected to the network before I unlocked the bl, flashed TWRP, custom ROM, etc. Every ROM I flashed had the same issue as you describe in your post.
Solution: I backed everything up to a pc & fastboot flashed back to stock & started over. Everything has been fine ever since.
***Keep that efs backup you made too - just in case you lose IMEI on your return to stock; efs restore should fix it.
Click to expand...
Click to collapse
Yea, I've tried reverting back to stock. I get back my service after restoring efs partition, but whenever I do it again, service is broken. I am at a loss.
L4ndon said:
Yea, I've tried reverting back to stock. I get back my service after restoring efs partition, but whenever I do it again, service is broken. I am at a loss.
Click to expand...
Click to collapse
Fwiw - I worked with another Sprint user a while back who could only get reliable service with the original firmware - that which came with the phone when purchased. Fortunately he had a bu of that and it was the only thing that worked. There is a thread about checking/fixing permissions on your persist partition that may help. Check it out - ya never know.
Phazmos said:
Fwiw - I worked with another Sprint user a while back who could only get reliable service with the original firmware - that which came with the phone when purchased. Fortunately he had a bu of that and it was the only thing that worked. There is a thread about checking/fixing permissions on your persist partition that may help. Check it out - ya never know.
Click to expand...
Click to collapse
I really dislike how sprint deals with unlocked phones, they never play nice, I have had carrier specific issues with them in the past. If it wasn't for my grandfathered truly unlimited plan I would switch in a heartbeat.
And yea, I'll be sure to check that thread out, thanks!
L4ndon said:
I have a G5S plus (xt1806) on sprint. Every rom I flash results in me not having LTE, and 3G cuts in and out unreliably. I have checked and my imei is still there. I have flashed the modems, and I have restored my efs backup to no avail. This has happened on every rom, no matter if I clean flash, dirty flash, I end up with the same result. Does anyone have any insight on this?
Click to expand...
Click to collapse
I had the same problem. I made a thread about it and somebody gave the solution. See if it works for you. https://forum.xda-developers.com/moto-g5s-plus/help/4g-to-t3829195
L4ndon said:
I really dislike how sprint deals with unlocked phones, they never play nice, I have had carrier specific issues with them in the past. If it wasn't for my grandfathered truly unlimited plan I would switch in a heartbeat.
And yea, I'll be sure to check that thread out, thanks!
Click to expand...
Click to collapse
I had initially had this in my previous reply - Sprint has always been special - but I deleted it, should have left it in. I've heard many bad stories from Sprint users in the past, going back years. Just glad I always stayed away from them (they have no coverage in my neck of the woods anyway).
Good luck!
PS - the link in the above post has the instructions to set correct permissions on affected files in persist partition - they came from the thread I mentioned.
Join telegram group. You got help from G5s+ community for sure if you still not the member of Moto G5s Plus telegram group community.
Link: https://t.me/g5splus
Sent from my Moto G (5S) Plus using Tapatalk