Database Info

()()()()()()() everyone having the force close issue read this ()()()()()

More and more people keep having this problem. Your phone suddenly has tons of force closes, and becomes unfunctional. Well we seem to have a problem with our recovery, possibly causing a corrupt partition. There is a solution .......use odin to flash the stock recovery tar found in development. Boot into stock recovery.. wipe data, and cache 3 times each ,and boot the rom back up. Then use rom manager to flash the tmobile gs2 cwm recovery. This does work. And has been proven numerous times.
Here is the stock recovery http://forum.xda-developers.com/showthread.php?t=1360943.
If for some reason you still have this issue after following my advice. Use odin to flash the stock firmware tar found here http://forum.xda-developers.com/showthread.php?t=1342348. After your done. Let it boot. If u get the force closes. Then proceed to power off, boot into stock recovery, and then wipe your data/cache, and reboot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Excellent post... Thx

another good one Silver Thanks....im curious as well to see how many are really having this issue<<<

Is there a difference between the TMobile GS2 CWM recovery and the CWM recovery flashed using this method (http://forum.xda-developers.com/showthread.php?t=1340526)?

I had the described problem, but wiping and reloading the intended ROM in CWM recovery fixed it.

That is good but alot of times that does not work. It can actually get to the point where it will not read the internal sd card

How are you guys flashing....and what are you flashing that is giving you these issues.
I have yet to experience these issues on T-Mobile or skyrocket roms.
What are the exact steps you follow when flashing a from to begin with?
Sent from my SAMSUNG-SGH-I727 using XDA App

I have experienced this on stock, and custom roms. And im not the only one. Alot of people have had this issue
Lets put it this way enough people have had this problem, and more will to the point where i made this thread, and asked a mod (jayharper08) to sticky it.

yes ALOT have......they may not have known it was a known issue and solved it. but it is there.

I am not saying you guys are not having issues...there has to be a reason I am not which is why I ask.....What steps exactly do you guys use to flash a rom and what roms. The process to fix it is great but if we could prevent it in the first place wouldn't that be better????.
silver03wrx said:
I have experienced this on stock, and custom roms. And im not the only one. Alot of people have had this issue
Lets put it this way enough people have had this problem, and more will to the point where i made this thread, and asked a mod (jayharper08) to sticky it.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I727 using XDA App

Silver,
Question...based on several of your other posts in threads, if we have 2.3.6 and use http://forum.xda-developers.com/showthread.php?t=1340526 to root/install recovery, are things ok?
Or should we still follow this thread to update CWM via ROM Manager?
Thanks.

^^^
That was my question too. What's the difference between the two recovery's?

I was having the issue too. I had the issue on stock(pure from store) as well as stock rooted, skyrocketeer, and cm7.
One thing I have tied it to, which I am not sure is the true reason but I was too impatient to test it thoroughly, is excessive SMS messages.
I have over 32k messages currently stored on my HTC Inspire. These have been moved from my G1, to Nexus One, to Inspire with no issue at all. When importing to my Skyrocket, the messages will import fine for a while. Afterwards, I would get random FCs, screen freezes up(can't do anything, not even turn off the screen), and network disconnects. I can force a reboot by holding the power button and it will work for about 5 minutes and then repeat the issues as before.
At first I thought it was the specific device having radio issues so I exchanged it for a new unit at Best Buy. I was still having the same issues with the new unit so I just figured I could cut my losses (on screen protectors and phone case) by just returning the until outright. I figure I will wait for the ICS update for this phone, hoping it will be more stable. Maybe at that point I can compare with other phones available as well.

I have had this problem repeating several times even after flashing the Rom and repeating steps as mentioned. I think it does it with a certain number of apps that downloaded from the market.

silver03wrx said:
More and more people keep having this problem. Your phone suddenly has tons of force closes, and becomes unfunctional. Well we seem to have a problem with our recovery, possibly causing a corrupt partition. There is a solution .......use odin to flash the stock recovery tar found in development. Boot into stock recovery.. wipe data, and cache 3 times each ,and boot the rom back up. Then use rom manager to flash the tmobile gs2 cwm recovery. This does work. And has been proven numerous times...
Click to expand...
Click to collapse
Is this a problem that develops as you start flashing more and more ROMs? Is there a known cause?
I'm new at this stuff - just rooted and tried my first ROM this week. I'm tempted to try others but if chances are good that I'll run into problems/issues even if I'm going about things the right way - I might hold off on making a change given that the phone is stable right now.
Thoughts?

NO rom does not cauz this issues. What causes issue is when you restore data from ur backups. Plus there is problem with cwm it does not fully wipe data because cwm was not particularly made for our phone. That being said you do not have to worry about a thing. I am flashaholic and i used to flash every other day since i m with Sky ice cream rom by Sean i don't flash a lot. Don't worry just try out all the roms you won't have problem by roms at all. There was only one rom that had problem Alien the first or second build.
Locoman_ said:
Is this a problem that develops as you start flashing more and more ROMs? Is there a known cause?
I'm new at this stuff - just rooted and tried my first ROM this week. I'm tempted to try others but if chances are good that I'll run into problems/issues even if I'm going about things the right way - I might hold off on making a change given that the phone is stable right now.
Thoughts?
Click to expand...
Click to collapse

Thank for the reply.
BTW, I'm using Sean's Sky IC too. Sooo nice.

Do you need to go into download mode to flash the recovery in ODIN? Or do you do it when the phone is just turned on regularly?

You have to go to dload mode in order to flash recovery. and use odin.
nutsngum said:
Do you need to go into download mode to flash the recovery in ODIN? Or do you do it when the phone is just turned on regularly?
Click to expand...
Click to collapse

I tried this process and I wanted to flash a new ROM. But in recovery mode it wouldn't read my SD card, and when I transferred the .zip to my internal memory and I tried to install it said I had no space.
Any ideas?

Unlock "Custom" Icon at initial boot

Apologies for not actually being a helpful contributor to the actual problem of unlocking the Verizon Galaxy S3 bootloader, but I came across this one time after booting my phone after replacing the battery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The Samsung logo, with an icon of an unlocked padlock, and the word "Custom" (this is the very first boot screen, before the boot animation and the Galaxy S3 logo), so it's the bootloader screen.
The only way I can replicate this is by taking out the battery and replacing it. Simply rebooting the phone does not show the icon. I suppose this could have been due to one of three things:
(all as directed by http://forum.xda-developers.com/showthread.php?t=1756885 for reference )
flashing the rooted boot image using Odin
installed custom Clockworkmod recovery
flashed custom boot image
Everything still boots properly, I don't have a brick. Is anyone else experiencing this that perhaps didn't follow these three steps?

A lot of people have been reporting this. Sometimes its completely random, sometimes can be replicated. Seems to be related to recovery image afaik, however some have reported being 100% bone stock and getting it. Its absolutely nothing to worry about.
Sent from my Galaxy S3 using Tapatalk 2

I wasn't worrying about it, as I said, the phone still boots completely fine, I was wondering if it was indicative of something unusual with the bootloader (such as the impossible chance of it actually being unlocked) or if it was reported by a large number of users.

I literally just saw that on my phone for the first time about 2 hours ago..... im having major issues right now from deleting busybox i guess the "wrong way"... this is my first time posting on this site, though i have read it for years, anyones help or advice would be appreciated......
I came across this image when i would hold the power button then hit restart and that image came up.... only after i attemped to install chainfire 3D and deleting busybox...
Please help me out my brothers n sisters
http://forum.xda-developers.com/showthread.php?t=1830457

RealMuphukkinG said:
I came across this image when i would hold the power button then hit restart and that image came up.... only after i attemped to install chainfire 3D and deleting busybox...
Click to expand...
Click to collapse
Mm, if you're having issues booting, then I think that's something different. I wouldn't know exactly how to fix that.

I have it also.
- Installing VRALG1 rooted alone won't trigger it--in fact, I wipe, flash that, reboot to clear the "Custom" tripwire
- Installing NoSympathy VRALG1 deodexed triggered it for me, twice
- Installing blueui with metamorph triggered it (cf. http://forum.xda-developers.com/showthread.php?p=30085423)
- Installing BlueICSFull.zip (http://forum.xda-developers.com/showthread.php?t=1775235) plus some other action (like configuring/using e-mail, not sure, installing some normal app) triggered it for me
Other than giving VZW an [illegal] excuse to void your warranty, I haven't seen an issue with it.

I just started getting this last night during a reboot .

My device showed this screen right out of the box!

I've seen this after a battery pulls. I'm on my 2nd GSIII and I was worried they wouldn't refund the amount to me if that showed up.

I rooted and flashed the Synergy Rom on my GSIII, as well as my fiancee's and my brothers. My phone was the only one to display this custom lock icon (randomly). I'm pretty sure it had something to do with flashing the cwm touch, then the cwm6. To fix it, I read users gained success just by wiping cache and dalvik, but it didn't work. So I tried flashing the stock recovery instead (hearing it's a recovery issue that 'throws' some sort of flag). It didn't fix the issue. I even ODIN'd back to stock, and it still didn't fix the issue. Everything I tried didn't work.
However, after I went ahead and re-rooted using the root66 method, then installing cwm touch, and then booting into recovery, wiping system, data, cache, dalvik, performing a factor data reset, and then installing the Synergy rom (I used 1.6), (ASSUMING I was just going to have to deal with the custom lock icon forever).... it somehow magically fixed itself.
Hope that helps. Ever since then, it's worked just fine, no custom lock icon. Since then, I've booted into cwm touch, wipe cache/dalvik, and have even updated to the newest Synergy (1.7), and it's remained just fine.
Hope this helps.

I froze the SysScope process. I don't get the custom padlock at boot, but because that process can no longer communicate with the phone I do have phone status as modified.
Sent from my SCH-I535 using xda app-developers app

I found that I triggered it by changing cpu settings, doing a recovery or basically changing any system setting. I cured it by flashing stock recovery, wiping data and cache. Then I rooted again but didn't change anything and still no padlock.:thumbup:
Sent from my SCH-I535 using xda app-developers app

Broadley1 said:
I found that I triggered it by changing cpu settings, doing a recovery or basically changing any system setting. I cured it by flashing stock recovery, wiping data and cache. Then I rooted again but didn't change anything and still no padlock.:thumbup:
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I have the same problem as well. By any chance was everyone here with the problem running TWRP as their recovery?

I'm bone stock and have gotten that, from time to time during reboots since release day.

Apologies for bumping an old thread....
I never had this screen before until I bought an extended battery from Gorilla Gadgets and as soon as I started using it I started getting that screen...
I did flash the Verizon stock (with root) but even then it never showed this screen until the moment I used the battery.
Does this void the warranty?

Casual root
I just did the casual ver. 795b root last night so I could stay on 4.1.2 for right now and I have this custom and unlock pic on the Samsung screen not sheer if I should do something or not?????? help if you have any ideas

Broadley1 said:
I found that I triggered it by changing cpu settings, doing a recovery or basically changing any system setting. I cured it by flashing stock recovery, wiping data and cache. Then I rooted again but didn't change anything and still no padlock.:thumbup:
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
How did you flash stock recovery?
Sent from my SCH-I535 using XDA Premium 4 mobile app

XXDroidZillaXX said:
How did you flash stock recovery?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Seems like he have to root again so he probably used ODIN.

I get this and then my phone has a yellow triangle of death... I still can't figure out how to fix this as I've tried JOdin on my macbook pro with stock flash's and pit files that are corrupt apparently. Anyone else know what I can do to debrick this? I've checked the other brick posts and nothing ;\

I believe this is caused by KNOX Security being triggered - which is irreparable
I think this indicates KNOX security was triggered and therefore your phone is no longer "pure". I don't know exactly what KNOX does, but I believe it burns a fuse in your phone that locks to either a 1 or a 0 - and once it's triggered, it can't be undone.
All of this is speculation though, I suggest looking up KNOX security and see what the experts say. This happened to me a few years ago and at the time, there was no fix. I'm sure someone found a way around it by now - or at least a way to prevent or remove it completely.

[Solved] Baseband unknown IMEI unknown HELP!

When i flash CM based roms i lose my baseband and imei, i have tried flashing a lot of roms and every rom makes my baseband and imei unknown. I used to flash roms all the time and this would never happen, but one time before flashing omni rom i accidentally wiped /system in CWM, and after that every rom has the same problem. I have tried flashing stock via odin and that brings back the imei and baseband every time, but i don't wan't to use stock. Can anyone help me?

One more thing. I have tried backing up both efs and modemfs while on stock and then recovering them on CM but it doesn't work, Also I have noticed that the efs folder is not empty when the baseband and imei are unknown.

[email protected] said:
One more thing. I have tried backing up both efs and modemfs while on stock and then recovering them on CM but it doesn't work, Also I have noticed that the efs folder is not empty when the baseband and imei are unknown.
Click to expand...
Click to collapse
Try with this http://forum.xda-developers.com/showthread.php?t=2165344&page=4

shut_down said:
Try with this http://forum.xda-developers.com/showthread.php?t=2165344&page=4
Click to expand...
Click to collapse
the user in that thread is on ginger bread, wouldn't the process be different in jelly bean?

It won't be a problem since you're issuing commands through ADB. Just have rooted JB + cocore + working busybox and give it a try.

here is what i did in terminal emulator:
$su
#busybox mke2fs /dev/block/mmcblk0p7
mke2fs: can't format mounted filesystem
it seems that /efs is mounted but android isn't recognizing it, I'm on CM11

I've read in other threads that nv_data.bin is my imei, but when I went to /efs to see if I have a nv_dada.bin I noticed I only have a nv_data.bin.md5 and a nv.log, this is what the nv.log had inside:
Sun Jan 1 00:00:03 2012: NV data back-up begin.
Sun Jan 1 00:00:03 2012: nv_data.bin does not exist.
Sun Jan 1 00:00:03 2012: NV data backup stopped due to NV data size.
Sun Jan 1 00:00:03 2012: MD5 is turned on.
Also I have noticed that nv_data.bin.md5 is 0B

bump

[email protected] said:
bump
Click to expand...
Click to collapse
Better try searching about that problem, on our sections. Do not use other phones fix because we can have differend partitions, so you can mess up even more...

I have searched and tried almost everything, nobody has experienced this problem

[email protected] said:
I have searched and tried almost everything, nobody has experienced this problem
Click to expand...
Click to collapse
On what baseband is your phone? The one from Hong Kong make this problem, and no one solved it.

I'm on the latest Italy Firmware, and I have been able to flash roms before without experiencing these problems.

I found a thread where there was an Odin flashable modem/baseband so now I'm going to try to flash that on TC CM 11 and report back... good luck to me

still baseband unknown

Some additional things I have noticed...
When I flash the Italy Firmware, which the CSC is I9070ITVLQ5, after the flashing process finishes ODIN shows the blue "RESET!" and even if I wait it doesn't show "PASS!" and my phone goes in a bootloop, so i have to go to recovery to wipe data/factory reset, and only then it will boot, now every thing seems to work good, but, when I go to setting the baseband should be I9070ITVLQ5 but it shows I9070XXLQ4. I've flashed one other firmware and the same happens, bootloop and the baseband doesn't change.
What I'm going to try is revert back to gingerbread and then update it via Kies... maybe then i could flash CM roms... good luck to me!

[email protected] said:
Some additional things I have noticed...
When I flash the Italy Firmware, which the CSC is I9070ITVLQ5, after the flashing process finishes ODIN shows the blue "RESET!" and even if I wait it doesn't show "PASS!" and my phone goes in a bootloop, so i have to go to recovery to wipe data/factory reset, and only then it will boot, now every thing seems to work good, but, when I go to setting the baseband should be I9070ITVLQ5 but it shows I9070XXLQ4. I've flashed one other firmware and the same happens, bootloop and the baseband doesn't change.
What I'm going to try is revert back to gingerbread and then update it via Kies... maybe then i could flash CM roms... good luck to me!
Click to expand...
Click to collapse
well, that pass/reset in odin doesn't matter. just wiping data and cache will solve it and i too experienced it many times, afik in our device imei is in efs and you may have want to search about it. i found a thread somewhere for this problem and solution is clearly written there, if i get that thread i will say

PradeepMurugan said:
well, that pass/reset in odin doesn't matter. just wiping data and cache will solve it and i too experienced it many times, afik in our device imei is in efs and you may have want to search about it. i found a thread somewhere for this problem and solution is clearly written there, if i get that thread i will say
Click to expand...
Click to collapse
believe me I have tried wiping data/factory reset and also wiping the cache many times, my problem is still there

M0shi said:
believe me I have tried wiping data/factory reset and also wiping the cache many times, my problem is still there
Click to expand...
Click to collapse
I read in another forums, for another devices, if you flash another modem.bin in the rom, it works, i don't try this but you don't loose anithing triying
Sorry for my bad english, hope you undestand me

shompy said:
I read in another forums, for another devices, if you flash another modem.bin in the rom, it works, i don't try this but you don't loose anithing triying
Sorry for my bad english, hope you undestand me
Click to expand...
Click to collapse
Thanks, I will try that after i go back to jb...
Right now I'm on GB, used this tutorial http://forum.xda-developers.com/showthread.php?t=2100642 , network is working but my baseband is still LQ4, everything stock i flash my baseband stays LQ4... weird :/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Okay so I got back to Jelly Bean LQL, my baseband is still LQ4, I tried flashing the LQL modem.bin via ODIN (on a tar file) and via CWM with a script someone made, still no change

Lost EFS / IMEI?

So stupid me. I've had a Nexus S and a Galaxy S2. I should've known better. However, in my defense I've only run into EFS problems once on my Nexus S and never on my S2. In proper ROM flashing it never becomes an issue.
Up til now I had been doing well. But I guess it has to do with the recent addition by CM to include modems in the ROMs also that causes trouble? TWRP seems to have trouble restoring them. To make a long story short, I was trying to bug test for CM by going back nightly by nightly from 0913 and backwards. Once I isolated the bug, I tried to restore back to my TWRP 0913 backup.
Well what happened upon restore? No signal. No IMEI. No WiFi. Well Crap. No EFS backup.
Steps I have taken to try to restore:
Tried this fix: http://forum.xda-developers.com/oneplus-one/general/fix-people-corrupt-efs-mobile-data-t2836389
Tried flashing Calkulin's 33R Rooted http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-4-4-4-xnph33r-t2855276
But no dice. I've noticed that my root folder just does not have an EFS folder. I'm not even sure what to do. Am I SOL? Do I just need to return the phone? The worst part is my Nexus 5 is out on RMA as of YESTERDAY (wow timing?).
Question to those who managed to restore their EFS, was your EFS folder somewhat intact? Mine was completely gone. Not sure if anyone can help me here.
Update 9/15:
I flashed Unofficial TWRP 2.7.0.1 and performed a restore of the TWRP backup. It seems that WiFi and Bluetooth can work. Bluetooth and WiFi Mac addresses show. However, IMEI is still empty.
When I reboot its gone.
So I've gotten closer, but no mobile connectivity yet.
I'm not sure whats missing!!! Agh.

First thing have you searched the forum. You are not the first and there have been success stories. You should be searching through here looking for them Instead of waiting for them to come to you. Search man search and I hope you get it done good luck..

playya said:
First thing have you searched the forum. You are not the first and there have been success stories. You should be searching through here looking for them Instead of waiting for them to come to you. Search man search and I hope you get it done good luck..
Click to expand...
Click to collapse
I did search. I showed you links to the threads I found and the solutions I tried. I'm reporting that I've had no luck with those that people claim success with. I'm also asking for more information here because I'm saying that my EFS folder is completely nonexistent (compared with my GS2 for example).
I'm trying to understand what everyone else's situation was because there's even in the threads with success stories, people just say "wow it worked." Done. No more info.

dmo580 said:
I did search. I showed you links to the threads I found and the solutions I tried. I'm reporting that I've had no luck with those that people claim success with. I'm also asking for more information here because I'm saying that my EFS folder is completely nonexistent (compared with my GS2 for example).
I'm trying to understand what everyone else's situation was because there's even in the threads with success stories, people just say "wow it worked." Done. No more info.
Click to expand...
Click to collapse
That was not up when I responded you have since edited your post but its ok I see you are in other threads trying to fix it. I am seeing colorOs, I read where someone reflashed stock rom then flashed radio and it worked.
Edit: Do you have another nandroid you can possibly restore?

playya said:
That was not up when I responded you have since edited your post but its ok I see you are in other threads trying to fix it. I am seeing colorOs, I read where someone reflashed stock rom then flashed radio and it worked.
Edit: Do you have another nandroid you can possibly restore?
Click to expand...
Click to collapse
The posts were there. I only edited the post becuase it said "Lots EFS" and not "Lost."
As for what else I've tried, I have since tried flashing the stock ROM using the 33R ZIP from CyanogenMod. Using Fastboot it basically wipes all your partitions and repartitions everything. No dice. No IMEI still.
I have only 1 Nandroid. Its 5gb so I don't usually make multiple. I actually have Online Nandroid Manager usually keep 2, but since 2.8.0.1 just dropped that day I did a NEW backup prior to going to an older CM ROM. As a result of new backup, I deleted the older ones to save space.
Stupid me. But either way I think the restore feature just screws things up. I never used the unofficial TWRPs to make EFS backups because I'm more scared of unoffical recoveries. I should've just done it anyway. Ugh.

dmo580 said:
The posts were there. I only edited the post becuase it said "Lots EFS" and not "Lost."
As for what else I've tried, I have since tried flashing the stock ROM using the 33R ZIP from CyanogenMod. Using Fastboot it basically wipes all your partitions and repartitions everything. No dice. No IMEI still.
I have only 1 Nandroid. Its 5gb so I don't usually make multiple. I actually have Online Nandroid Manager usually keep 2, but since 2.8.0.1 just dropped that day I did a NEW backup prior to going to an older CM ROM. As a result of new backup, I deleted the older ones to save space.
Stupid me. But either way I think the restore feature just screws things up. I never used the unofficial TWRPs to make EFS backups because I'm more scared of unoffical recoveries. I should've just done it anyway. Ugh.
Click to expand...
Click to collapse
I used the script to back mine up... Well I am always looking around so if I see anything I will let you know
Sent from my A0001 using Tapatalk

playya said:
I used the script to back mine up... Well I am always looking around so if I see anything I will let you know
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Yeah good idea. What script BTW if you don't mind sharing.
I should've been more aware, but somehow I figured "its not a Samsung" so I wasn't careful enough.

dmo580 said:
Yeah good idea. What script BTW if you don't mind sharing.
I should've been more aware, but somehow I figured "its not a Samsung" so I wasn't careful enough.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=54623075&postcount=81

Update 9/15:
I flashed Unofficial TWRP 2.7.0.1 and performed a restore of the TWRP backup. It seems that WiFi and Bluetooth can work. Bluetooth and WiFi Mac addresses show. However, IMEI is still empty.
When I reboot its gone.
So I've gotten closer, but no mobile connectivity yet.
I'm not sure whats missing!!! Agh.

dmo580 said:
Update 9/15:
I flashed Unofficial TWRP 2.7.0.1 and performed a restore of the TWRP backup. It seems that WiFi and Bluetooth can work. Bluetooth and WiFi Mac addresses show. However, IMEI is still empty.
When I reboot its gone.
So I've gotten closer, but no mobile connectivity yet.
I'm not sure whats missing!!! Agh.
Click to expand...
Click to collapse
I lost EFS on my S3. I assume you know that EFS is a partition? I had to to type in commands (via ADB or a shell on your phone) to set the permissions and make them stick. This way, when you reboot it stayed.
I half guess that it's something along similar lines.
Ok, EDIT..here is my post relating to S3.
Originally Posted by kocweb
Here is the exact solution for this problem which i have recently had!
You have to root your phone and install Terminal Emulator from Google Play.
Open terminal emulator and type as ;
su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
You now should not see the that message anymore. Its because of an EFS corruption. ( Thanks to yesilcin*com (sawgent) ) for exact solution.
Hope it helps!!!
Click to expand...
Click to collapse

dmo580 said:
Update 9/15:
I flashed Unofficial TWRP 2.7.0.1 and performed a restore of the TWRP backup. It seems that WiFi and Bluetooth can work. Bluetooth and WiFi Mac addresses show. However, IMEI is still empty.
When I reboot its gone.
So I've gotten closer, but no mobile connectivity yet.
I'm not sure whats missing!!! Agh.
Click to expand...
Click to collapse
ok so now flash the Color OS that people say seem to help when you get to that point or try flashing stock rom and radio like others have said worked

playya said:
ok so now flash the Color OS that people say seem to help when you get to that point or try flashing stock rom and radio like others have said worked
Click to expand...
Click to collapse
Yeah so i tried flashing both after my recovery and with stock I get WiFi and BT. Reboot and its gone
With ColorOS it doesn't work.

Hang in there guys I think I found a fix. On my way home to prepare a permanent fix for absolutely everything
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061

markbencze said:
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Click to expand...
Click to collapse
As you may know, I have already tried your method and its no good.
Other things I've tried:
Flashing ColorOS 1.20, 2.18, no go
Flashing the factory image of 33R, 38R
Flashing my supposed backup of modemst1, modemst2, but I suspect they are corrupted because they were corrupted when I accidentally restored modem in TWRP
So what's interesting is when I do flash the factory image of 38R with the flashall.bat, upon initial boot, Wifi does work. However, after a reboot, it goes away.
Does anyone think they can help me figure out why that happens and if I can just keep WiFi around at the very minimum?
Edit: I think I'm a special case because most people have just seen reboot loops or persist partition corruption which is easily fixed by flashing the backup persist or the persist in that other thread. However, the issue here is I think what triggered my issue was somehow TWRP offered an option to restore the modem partition (I'm guessing it was TWRP trying to restore an Online Nandroid Backup which by default includes the modem partition). As a result, my modem likely got screwed.
However the fact that I can get WiFi on a first boot after a factory flash leads me to think maybe I'm not all screwed? Even if my IMEI is lost forever, I'll accept that, but if I can get a WiFi only device, that would still be sweet?

dmo580 said:
As you may know, I have already tried your method and its no good.
Other things I've tried:
Flashing ColorOS 1.20, 2.18, no go
Flashing the factory image of 33R, 38R
Flashing my supposed backup of modemst1, modemst2, but I suspect they are corrupted because they were corrupted when I accidentally restored modem in TWRP
So what's interesting is when I do flash the factory image of 38R with the flashall.bat, upon initial boot, Wifi does work. However, after a reboot, it goes away.
Does anyone think they can help me figure out why that happens and if I can just keep WiFi around at the very minimum?
Edit: I think I'm a special case because most people have just seen reboot loops or persist partition corruption which is easily fixed by flashing the backup persist or the persist in that other thread. However, the issue here is I think what triggered my issue was somehow TWRP offered an option to restore the modem partition (I'm guessing it was TWRP trying to restore an Online Nandroid Backup which by default includes the modem partition). As a result, my modem likely got screwed.
However the fact that I can get WiFi on a first boot after a factory flash leads me to think maybe I'm not all screwed? Even if my IMEI is lost forever, I'll accept that, but if I can get a WiFi only device, that would still be sweet?
Click to expand...
Click to collapse
If nothing is working why not just RMA?
All opo come with 1 year warranty

Thanks for the reminder to back up my EFS!

Did anyone manage to find a fix for lost imei
Same thing happened to me yesterday, restored a nandroid, and efs disappeared
Tried flashing full stock, no result
Phone comes on, reboots after a minute
IMEI,bt, wifi mac id,baseband=unknown

Had any luck fixing it?

Looks like I'm in the same boat too.
I have tried everything discussed in this thread and more, to no avail.
Watching this thread closely

[Q] Phone screen error

Hi all, this is my first post in this forum.
I own a rooted Samsung Gt-N7000 with KK custom rom.
Before it was rooted, I would experience that if there was some pressure on the phone, because it was in my pocket and I bended my legs, the phone would reboot.
I checked it out manually by trying to apply pressure on the screen or trying to bend it, and the result was always that the screen would flicker for a second and right away reboot.
Now fast forward to after I rooted the phone. At that point the phone wouldn't automatically reboot anymore, but I would pull it out of my trouser pocket and the screen would be off. The only way to reset it would be to hold the power button for an extended time or remove the battery.
I tested it again the same way I did before it was rooted, and it would also give the screen flicker but not automatically reboot anymore.
Next I started to notice that after I manually rebooted, it would reboot normal but as soon as the boot image started to appear it would give the same screen error.
All small lines in different colors or a single horizontal white line which moved over the screen. I could boot into TWRP recovery and the screen would look normal and touch would work, but as soon as I the system boot image appeared the screen would go in error.
This is an example of how my phone screen looked ( this is not my phone)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I did a clean reinstall from the ROM, whereby wiping everything, but same result.
Then I went into the mount section of the recovery and noticed that EFS-System and data were not mounted. So I ticked them, reboot and everything is fine.
The following times I experienced the error it was exactly same. Rebooting or re-flashing ROM would give no positive result, only after going into the mount tab and tick EFS-system and data and reboot the problem is solved.
Any advise what is happening will be much appreciated.

basjke said:
Hi all, this is my first post in this forum.
I own a rooted Samsung Gt-N7000 with KK custom rom.
Before it was rooted, I would experience that if there was some pressure on the phone, because it was in my pocket and I bended my legs, the phone would reboot.
I checked it out manually by trying to apply pressure on the screen or trying to bend it, and the result was always that the screen would flicker for a second and right away reboot.
Now fast forward to after I rooted the phone. At that point the phone wouldn't automatically reboot anymore, but I would pull it out of my trouser pocket and the screen would be off. The only way to reset it would be to hold the power button for an extended time or remove the battery.
I tested it again the same way I did before it was rooted, and it would also give the screen flicker but not automatically reboot anymore.
Next I started to notice that after I manually rebooted, it would reboot normal but as soon as the boot image started to appear it would give the same screen error.
All small lines in different colors or a single horizontal white line which moved over the screen. I could boot into TWRP recovery and the screen would look normal and touch would work, but as soon as I the system boot image appeared the screen would go in error.
This is an example of how my phone screen looked ( this is not my phone)
I did a clean reinstall from the ROM, whereby wiping everything, but same result.
Then I went into the mount section of the recovery and noticed that EFS-System and data were not mounted. So I ticked them, reboot and everything is fine.
The following times I experienced the error it was exactly same. Rebooting or re-flashing ROM would give no positive result, only after going into the mount tab and tick EFS-system and data and reboot the problem is solved.
Any advise what is happening will be much appreciated.
Click to expand...
Click to collapse
This is a GT.i9300 or i9305, not N7000.
EDIT: I SEE, this is not your phone.
Sorry for my mistake
However, BACK UP ALL DATA Before doing anything.
Then you can root/unroot/reinstall/up or downgrade as much as you like.

I understand the OP is lengthy and since English is not my native language it may be confusing, but I think you missed the point of my question, which is that the phone is rooted already with a custom ROM installed.
I have searched a bit more in the mean time and it sounds as if the EMMC chip is the cause of my problem. I have the affected chip in my phone, but I understand that the available patch is to prevent sudden death. I don't know if the patch also resolves the screen issue.
My understanding is that I have applied the patch by installing the latest Lanchon kernel with TRIM FPBug and have the latest Slimsaber ROM installed which to my understanding has the patch integrated as well.
Please correct me if I'm wrong.

basjke said:
I understand the OP is lengthy and since English is not my native language it may be confusing, but I think you missed the point of my question, which is that the phone is rooted already with a custom ROM installed.
I have searched a bit more in the mean time and it sounds as if the EMMC chip is the cause of my problem. I have the affected chip in my phone, but I understand that the available patch is to prevent sudden death. I don't know if the patch also resolves the screen issue.
My understanding is that I have applied the patch by installing the latest Lanchon kernel with TRIM FPBug and have the latest Slimsaber ROM installed which to my understanding has the patch integrated as well.
Please correct me if I'm wrong.
Click to expand...
Click to collapse
In order to make me read your posts, please quote my message or mention me .
Thanks

Hannah Stern said:
In order to make me read your posts, please quote my message or mention me .
Thanks
Click to expand...
Click to collapse
Thanks for pointing out, but as I said I'm a very recent member, so I will have to learn.
So since you have read my post now, can you please tell me if I'm correct or not in the assumptions I made in my previous post

basjke said:
Thanks for pointing out, but as I said I'm a very recent member, so I will have to learn.
So since you have read my post now, can you please tell me if I'm correct or not in the assumptions I made in my previous post
Click to expand...
Click to collapse
That's no problem

Hannah Stern said:
That's no problem
Click to expand...
Click to collapse
So I have read up more on the issue and the eMMC chip I have installed is the VYL00M rev 0x19.
According to the Cyanogen wiki my chip may be affected with the wear leveling bug.
This problem also occurs in fwrev 0x19, but has not been observed there, and is in any event far less severe than the infamous "Superbrick" secure erase bug, as the user only needs to perform a wipe data/factory reset operation to recover.
There is a patch from Samsung which is here.
https://android.googlesource.com/kernel/omap/+/3c57a612f12b069bbc863ec0c74a26850d76a9e8^!/
Only thing is that it is Chinese to me as how to apply the patch. Can someone help me with instructions how to apply the patch?

basjke said:
So I have read up more on the issue and the eMMC chip I have installed is the VYL00M rev 0x19.
According to the Cyanogen wiki my chip may be affected with the wear leveling bug.
This problem also occurs in fwrev 0x19, but has not been observed there, and is in any event far less severe than the infamous "Superbrick" secure erase bug, as the user only needs to perform a wipe data/factory reset operation to recover.
There is a patch from Samsung which is here.
https://android.googlesource.com/kernel/omap/+/3c57a612f12b069bbc863ec0c74a26850d76a9e8^!/
Only thing is that it is Chinese to me as how to apply the patch. Can someone help me with instructions how to apply the patch?
Click to expand...
Click to collapse
If you Factory-Reset the phone, all data gets completely lost so do a backup before doing anything.

Hannah Stern said:
If you Factory-Reset the phone, all data gets completely lost so do a backup before doing anything.
Click to expand...
Click to collapse
I understand that but with the patch applied my problems should be solved, at least that is my understanding, so I would not need to factory reset the phone anymore.
Problem is that I have no idea how to apply the patch.
Also take note that factory reset and re-flash ROM doesn't solve my problem.
To solve my screen problem I have to go into the mount tab of the TWRP recovery, tick EFS - DATA _ SYSTEM, and reboot.
This works even without factory reset or reinstall the ROM.

basjke said:
I understand that but with the patch applied my problems should be solved, at least that is my understanding, so I would not need to factory reset the phone anymore.
Problem is that I have no idea how to apply the patch.
Also take note that factory reset and re-flash ROM doesn't solve my problem.
To solve my screen problem I have to go into the mount tab of the TWRP recovery, tick EFS - DATA _ SYSTEM, and reboot.
This works even without factory reset or reinstall the ROM.
Click to expand...
Click to collapse
Ok, i see.