Develop Bugs

Looking for some help...

Ok all, i think i have hit my limit of what i can think to do to fix my phone so i'm throwing this out looking for some help.
So i have run into a major problem. Starting back on the first i flashed from CyanogenMod Nightly 175 to nightly 181, 181 FC's alot on the google processes framework and such, and it was unusable so i went back to my Nightly 175 restore i had created. It was working fine until today and it became unusable, FC's for everything.
So i first started by trying to get into Safe Mode to do a restore, and RomManager FC'ed before i could get it to do anything
Then i tried to get into the restore area, same thing, FC
Tried to use the notification Tray icon to "update" to 181, same thing FC
All these steps were attempted again after a normal reboot
None worked
I then went to reboot into recovery, and it only would reboot into the Bootloader
Once in the Bootloader i tred to do the Recovery option, but all it does is reboot into the bootlaoder
I do know that i had just updated the RomManager recovery option to 5.0.2.0 or whatever the latest was. I'm wondering if there is a problem with that?
My phone was originally reflashed with unrevoked 3.
i went to dougpiston.com and got the RUU program from there after searching through some forums, but that program when run says it is unable to communicate with my phone when attempting to verify software on my phone
I also tried un-sync'ing all of the google accounts on the phone and a factory reset, but even after the reboot the last account is still there and it appears as if the factory reset did not work
I also have this posted over in CM's forums, but i was hoping maybe someone here could help.
anything is appreciated at this point

garaxiel said:
Ok all, i think i have hit my limit of what i can think to do to fix my phone so i'm throwing this out looking for some help.
So i have run into a major problem. Starting back on the first i flashed from CyanogenMod Nightly 175 to nightly 181, 181 FC's alot on the google processes framework and such, and it was unusable so i went back to my Nightly 175 restore i had created. It was working fine until today and it became unusable, FC's for everything.
So i first started by trying to get into Safe Mode to do a restore, and RomManager FC'ed before i could get it to do anything
Then i tried to get into the restore area, same thing, FC
Tried to use the notification Tray icon to "update" to 181, same thing FC
All these steps were attempted again after a normal reboot
None worked
I then went to reboot into recovery, and it only would reboot into the Bootloader
Once in the Bootloader i tred to do the Recovery option, but all it does is reboot into the bootlaoder
I do know that i had just updated the RomManager recovery option to 5.0.2.0 or whatever the latest was. I'm wondering if there is a problem with that?
My phone was originally reflashed with unrevoked 3.
i went to dougpiston.com and got the RUU program from there after searching through some forums, but that program when run says it is unable to communicate with my phone when attempting to verify software on my phone
I also tried un-sync'ing all of the google accounts on the phone and a factory reset, but even after the reboot the last account is still there and it appears as if the factory reset did not work
I also have this posted over in CM's forums, but i was hoping maybe someone here could help.
anything is appreciated at this point
Click to expand...
Click to collapse
You're problem is ClockworkMod. Version 5 is a steaming heap of crap that's caused this sort of problem, not only for dInc users, but Tbolt and other device users. The solution seems to be flashing back to an older recovery. And if it works, don't fix. I'm still running version 3.something on my Tbolt and have no plans to change that. I NEVER use ROM Manager and recommend nobody ever touch it except for a few things. I almost never have it installed on any device.

OK then dumb question but if RomManager FC's on me, how do i flash back to a working version or to an alternate version entirely? i have been unable to find other ways of flashing outside of RomManager

Older Recovery versions are available on "dougpiston.com" just follow the directions.

www.dougpiston.com has what you're looking for under "recoveries". They're flashed in hboot like a radio, RUU, splash screen, etc.

Also if that doesn't work, which it probably will, you can also flash a PB31IMG which essentially is the RUU but you do not need a PC. You put that on the root of the SD (as in, not in any folders. Probably know that already...) and reboot into HBOOT (Power and volume down) and itll load it up.
Note: Make sure the file is PB31IMG.zip and not PB31IMG.zip.zip

Ha!!! got it back (well on the road to back anyways)
Was able to find a PB31IMG on dougpiston.com and hboot flashed it in (3.0.0.8). I had one on my PC but it must have been corrupt because it didn't work before. once that was working i was able to get into recovery get a restore back to my 175 nightly and am in the process now of flashing nightly 181 on there cleanly and rebuild the whole phone from scratch. damn i hope this works thanks all for help and ideas.

Nice, I actually had the same problem when I updated cwm but it was way back when they first updated to the 2.x.x recoveries. I was freakin for a bit lol....glad you got it working. Does anyone know why whenever I flash a different version of cwm I have to flash it twice?
Sent from my ADR6300 using xda premium

pete_kowalski83 said:
Nice, I actually had the same problem when I updated cwm but it was way back when they first updated to the 2.x.x recoveries. I was freakin for a bit lol....glad you got it working. Does anyone know why whenever I flash a different version of cwm I have to flash it twice?
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
No idea...are you using ROM Manager?

[Q] EFS Problem, need help, input from someone in the know!!!

Okay, I have spent hours upon hours searching the subject and it becomes a bit hard to find a correct procedure as there are tons of hearsay and perhaps singular examples because no one really seems to fully grasp the concept of the issue. So I guess different fixes work for different people.
But here is my issue:
I have a Wind T889V. Was working fine, done lots of ROM ranges, big geek, ETC.
Well, I made a mistake and I flashed T889UVBMD1 Radio. For whatever reason I flashed it since thanks to so many ROMs flashed I forgot that I have a T889V and not a T889.
So that killed my radio. No 3G, no data, IMEI and Baseband, Mobile Network type say "unknown." I tried flashing proper radio immediately after and my phone WOULD bootup but then would reboot about 3-5 minutes into it. The reboot cycle was so short it would hardly let me do anything with it.
Then I read that booting up to an early version of stock might bring IMEI info back. Did not work. In fact, my phone boots up minutes after being being turn on unless I flash the T889UVBMD1 Radio. So I think I am stuck with it. T889V radios I have tried boots the phone up sometimes and sometimes it does not, or it cycles right at the Samsung screen.
Yes, I did a EFS backup when I first rooted. However the process only g=created a IMG file which I kept safe. Which is 20 megs in size. However, when I try to open it with a 7.Zip to look inside it appears to be empty!! I have done a restore multiple times and nothing happens. Even though the process seems to go without errors.
I check the EFS folder on my phone as it is still in there. However I do not see any .bin files. And under IMEI, there is only one file:
mps_cod.dat which when open only has the words GLW in it. That is it. So needless to say, that is not the way it should be.
I have tried to install T889VVLALJ4 (which is the original ROM through CWM) and it soft loops, even though members have said that it has magically saved their phone it sounds to me like perhaps in those cases the EFS folder still had the data and the flashing of the rom simply just rediscovered the info.
I have been reading about a member who was able to inject the IMEI info the folder but I have not been able to get in touch with him or find the exact procedure how it was done.
My last resort would be to try to restore to original, soft looping and all and take it back to the service provider see what they say.
Thoughts? And Thank you.

Try restoring via kies.
http://forum.xda-developers.com/showthread.php?p=46164552
Sent from my SGH-T889 using xda app-developers app

ciphercodes said:
Try restoring via kies.
http://forum.xda-developers.com/showthread.php?p=46164552
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Okay.
For those in the same issue as me, the problem with trying to solve it KIES is that it will look to see if your phone is factory everything. If you are like me, and you go the FACTORY ROM/RESET route then your phone will reboot every 30 seconds to every 2 minutes. So KIES will never have time to recognize your phone, assuming that your phone boots at all.
Then if you go back to the issue I had... which was to put the T889 Modem which stops your phone from rooting, then KIES will tell you the phone is not suitable for an update. So there goes your option.
The best way for the time being is to use the AWS QCN (Google this) route. Which enables the AWS on your phone and allows you to at least to connect to your provider. As of this writing and three days of doing work, I have found a fix, that sort of fixes the phone. I have tested with a few people and they hear some background noise on Wind. So it is not a full fix, but it is a round about way to have your phone sort of back.
The biggest issue I have found after doing in-depth search on this issue and most so-called fixes is that most users have no bloody clue what the issue is so for some it is easier to fix than for others and as such you get a lot of false negative fixes.
The fact is I have found so far is that there is no 100% that I have found.
You first need to know if the issue is with the Modem, your IMEI getting fudged, your EFS folder messing up and whether once it got fudged whether your EFS info still remains on your phone. Different fixes fix different issues.

[Q] No ROMs taking, keep getting no MD5 message, phone close to bricked.

I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.

gvazquez82 said:
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
Click to expand...
Click to collapse
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient

MrHaPpY66 said:
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
Click to expand...
Click to collapse
First of all thank you for trying to help me, I hope you are having a good Thanks Giving.
I used the thread you linked to, and downloaded the version with out knox. I followed the instructions
transferred ROM and flashed kernel file to SD card
used odin to flash TWRP,
used twrp to flash rom and kernel file.
and it takes the file thankfully, there's only one issue. My phone can't make or receive calls/texts. Is yours able to?

I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Next Update
the bootloader I flashed apparently flashed to the external sd card? I flashed another one and it is booting from the internal sd. I had to flash a different modem the one in the bootloader/modem file I flashed from the link above didnt take? I got most everything sorted out, but im getting tired, it has been an all night adventure. its 08:23 est now
sorry for the delay in updating this I had to get some rest.

theramsey3 said:
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Click to expand...
Click to collapse
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.

spongdangly said:
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
Click to expand...
Click to collapse
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?

gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.

theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I will give that a shot, but what's an APN, sorry. And how do I create one, and is it needed for me to do so?

gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
It should be, I'm working right now so I don't have time to fine the guide on how to inject your IMEI. If I remember correctly it involves using QPST. If you have an old (or any) working Nandroid backup that should fix the problem.
FYI, make sure you don't use the guide for the international S3 as it has different hardware and folder structure/contents.
As for the APN, it should automatically fill itself in since it reads it off the SIM Card (I might be wrong).

theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I tried it and it work!!!!!!!!!!!!!!!!!
67 texts just came in. Sir, I thank you oh so kindly. You have made this gloomy rainy day oh so joyous.

No problem. Glad I could help you.
The real credit should go to -Mr.X-, loserskater and anyone else(no disrespect there were alot of files) whose stuff I tried to flash lastnight thank you all in the dev community who contribute.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.

gvazquez82 said:
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
Click to expand...
Click to collapse
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.

flexfulton said:
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
Click to expand...
Click to collapse
do you know of a good stable kit kat like ROM I could use for the s3? And any speculation as to why the ROMs werent taking for me?

Bootloop LG G2 Sprint

Hello everyone thanks for checking out my post for assistance.
I was running the OpTimuS 2.2 yesterday when my phone jumped into a boot-loop. The phone will be on for about 20-40 seconds then reboot. During that time I have no service and when I update the profile I get a message that I don't have any service. I can get into recovery and Download mode. I tried to just wipe and install the rom again. That process resulted in the same boot loop. I have a back up but that was done before the "spark" update and I didn't want to restore that because I know there will be an issue with the radio. I downloaded the stock rooted rom but the phone will not stay on long enough to transfer the file and when I try and load via recovery it will not allow me to transfer the file. (never shows up on computer I might be doing that wrong) I then attempted to bring the phone back to stock following this process http://www.rwilco12.com/forum/showthread.php?tid=96 but when I get down to step 13 the program will not respond anymore. I am going a friends house to try on a different computer but I wanted to get this out there just in case that has the same result.
Thanks again for any info that you could provide.

usvi525 said:
Hello everyone thanks for checking out my post for assistance.
I was running the OpTimuS 2.2 yesterday when my phone jumped into a boot-loop. The phone will be on for about 20-40 seconds then reboot. During that time I have no service and when I update the profile I get a message that I don't have any service. I can get into recovery and Download mode. I tried to just wipe and install the rom again. That process resulted in the same boot loop. I have a back up but that was done before the "spark" update and I didn't want to restore that because I know there will be an issue with the radio. I downloaded the stock rooted rom but the phone will not stay on long enough to transfer the file and when I try and load via recovery it will not allow me to transfer the file. (never shows up on computer I might be doing that wrong) I then attempted to bring the phone back to stock following this process http://www.rwilco12.com/forum/showthread.php?tid=96 but when I get down to step 13 the program will not respond anymore. I am going a friends house to try on a different computer but I wanted to get this out there just in case that has the same result.
Thanks again for any info that you could provide.
Click to expand...
Click to collapse
Flashing back to stock won't work, I had the same thing happened.......it's the EFS Partition (http://forum.xda-developers.com/showthread.php?t=2451390) If you made a EFS Partition Backup, then flashing that will be your best hope.....I didn't make a backup so I went to sprint cuz I have insurance and they are ordering me a new phone

Shadow_God said:
Flashing back to stock won't work, I had the same thing happened.......it's the EFS Partition (http://forum.xda-developers.com/showthread.php?t=2451390) If you made a EFS Partition Backup, then flashing that will be your best hope.....I didn't make a backup so I went to sprint cuz I have insurance and they are ordering me a new phone
Click to expand...
Click to collapse
They replaced it even though your phone was rooted?

Try installing an updated modem for your variant from this thread. It's worth a try.
http://forum.xda-developers.com/showthread.php?t=2451426
If you get it working, definitely make an EFS backup right away.

usvi525 said:
They replaced it even though your phone was rooted?
Click to expand...
Click to collapse
I used the LGFlashTool to bring it back to stock unrooted.......but my phone had no sevice and rebooted every couple minutes, plus the touchscreen wasn't working either.....I told them I took the Spark update and thats when it happened, he said they had alot of issue with touchscreen stopped working and rebooting issue with the spark update......so they didn't look at it long...lol
I have tried back to stock numbers of times....installing modems....restoring my backups....nothing would get it to work, so I gave up and went to sprint...lol

On the rom you were using, have you tried enabling airplane mode to prevent reboots? You could try to get a stock-based flashable zip on the device if possible.

alone-together said:
Try installing an updated modem for your variant from this thread. It's worth a try.
http://forum.xda-developers.com/showthread.php?t=2451426
If you get it working, definitely make an EFS backup right away.
Click to expand...
Click to collapse
Thanks for the option. I was able to install the radio but the issue remains.

usvi525 said:
Thanks for the option. I was able to install the radio but the issue remains.
Click to expand...
Click to collapse
Have we ruled out the possibility to flash a stock ROM in TWRP? If by any chance you have a USB OTG cable, you could try to connect a flash drive with another ROM.

This is my last ditch effort. Small back story: I somehow wiped EVERYTHING on my G2. EFS partition, ESN, data, SIM info., everything with dialer codes. All of my network information reads "unknown". I tried many methods from here on the forums to get this data back and it turns out I have lost my EFS partition- DNA for the network? I sent it to LG to get it fixed, having done a hard reset and leaving no trace of root. They sent it back without even asking and did no repairs. The note said "board bent". WTF?? How does the user bend the main board, especially when I never opened it? They voided my warranty and ripped off my IMEI/MEID sticker from the back of the phone.
Anyways, I am here with a brick. No network still. Here is what I have done:
1) .tot method to ZVC. Several more times... once to ZV7 where I lost touch capability. Luckily saved my arse with a micro->usb cable and a mouse.
2) attempted to root with ioroot25. Failed because the phone WILL NOT find recovery mode. adb, voldown+pwr then again from power off, and apps are unable to force the phone into recovery mode. I assume it is possible that my recovery mode is deleted?
3) Would have tried all of these "rewrite your efs/imei/etc" things but I can't do any without root. Can't root without recovery, can I?
4) Spent the last two weeks scouring the internet for a fix and going back to my Epic 4G temporarily.
Please help me, has anyone seen this before? Can anyone help me fix it? I am to the point where I would pay to have it fixed. Any experts out there? XDA has yet to let me down... I just need to know if I can fix it or if it is a brick so I can go searching for an old Sprint GS3.
Thanks all,
baublitz

Sprint galaxy s3 e:failed to mount /es (invalid argument)

Hey guys, been reading through the threads and not really finding a clear answer or solution to this problem. This is a completely stock sprint sph-l710. I started getting this box with yellow lettering overshadowing the primary display of which I've learned indicates the phone is in 'factory mode'. I thought performing a factory reset would fix this but it did not. I noticed when you boot the phone in recovery mode I see the efs error. I am thinking the underlying issue is with fixing the efs problem. Now that I have reset the phone I no longer have data network access, im guessing because of this factory mode. I am new to this and not real understanding of the lingo everyone uses. From what I've read Im worried im going down a rabbit hole if i start tinkering. I am looking for clear instructions to repair what I think is corrupted software (I'm guessing the operating system software). The instructions I've seen seem to skip steps that are probably rudimentary to everyone else but leaves me without a starting place. I have downloaded oden but i am not certain again without precise instructions that I am not going to permanently mess up my phone.. there appear to be a number of variations of this device and i want to make sure the instructions I get will work on mine. I will take any advise on getting this resolved. I am not opposed to rooting the phone either if that fixes the problem (no idea how to do this, never tried, but some threads on here I think I can follow to do it safely). With that said, different threads also seem to indicate (emphasize 'seem to') that team win recovery can fix this but there are no clear responses regarding my issue of a solid fix. Thank you for any help

timbow4 said:
Hey guys, been reading through the threads and not really finding a clear answer or solution to this problem. This is a completely stock sprint sph-l710. I started getting this box with yellow lettering overshadowing the primary display of which I've learned indicates the phone is in 'factory mode'. I thought performing a factory reset would fix this but it did not. I noticed when you boot the phone in recovery mode I see the efs error. I am thinking the underlying issue is with fixing the efs problem. Now that I have reset the phone I no longer have data network access, im guessing because of this factory mode. I am new to this and not real understanding of the lingo everyone uses. From what I've read Im worried im going down a rabbit hole if i start tinkering. I am looking for clear instructions to repair what I think is corrupted software (I'm guessing the operating system software). The instructions I've seen seem to skip steps that are probably rudimentary to everyone else but leaves me without a starting place. I have downloaded oden but i am not certain again without precise instructions that I am not going to permanently mess up my phone.. there appear to be a number of variations of this device and i want to make sure the instructions I get will work on mine. I will take any advise on getting this resolved. I am not opposed to rooting the phone either if that fixes the problem (no idea how to do this, never tried, but some threads on here I think I can follow to do it safely). With that said, different threads also seem to indicate (emphasize 'seem to') that team win recovery can fix this but there are no clear responses regarding my issue of a solid fix. Thank you for any help
Click to expand...
Click to collapse
Odin will flash the factory firmware for you. Get firmware from sammobile. Look for sph L710 device, and firmware with NJ2 in the name. Put phone in download mode, (power off then hold power+home+volume down) plug in phone to pc. Wait till Odin says added. Click AP in odin, select firmware you downloaded, click start. When it's done, unplug phone, remove battery, put it back in and reboot.
This may not fix your efs partition, but it's the first thing to try.
Odin
I found the thread for nj2 firmware here

issue still persists
Hey Madbat, thank you so much for reaching out to me and giving me the advise. Installing the firmware through odin was really easy. Thank you for that! However, it did not fix the issue. When the phone came back up it still has the exact same problem. I am going to attach a couple pictures to show you what i am seeing... Really appreciate your time and help!
hell, sorry it says im a new user and wont let me post the pictures...

timbow4 said:
Hey Madbat, thank you so much for reaching out to me and giving me the advise. Installing the firmware through odin was really easy. Thank you for that! However, it did not fix the issue. When the phone came back up it still has the exact same problem. I am going to attach a couple pictures to show you what i am seeing... Really appreciate your time and help!
hell, sorry it says im a new user and wont let me post the pictures...
Click to expand...
Click to collapse
Sorry, I never had that issue. Maybe someone else will chime in with experience on the efs partition. That's not a triband s3 is it? (Sph l710t?) T at the end means triband. Second thought, I don't think the firmware would have flashed if it was triband.
How did you wipe your efs?

Its not a tri band. Just SPH-L710. Wish this forum would let me post the pictures of what my phone is doing.. Since the firmware doesnt correct the issue I would think then its a problem with the operating system itself. I have been scouring the web and have found various threads specifically about efs repairs but they entail doing things that seem awful complicated. And i dont know if those things work on my model phone. Maybe rooting the phone gets deep enough to over write or repair the issue. Is there not a way to restore the operating system itself maybe or is that what a replacement ROM does? I am thinking of trying my hand at rooting the phone and seeing what happens. One thread indicated TWRP would backup and restore the EFS file. Im thinking if it backs up a corrupt efs file what good is that, maybe it fixes it too. Found an excellent video on XDA for rooting the S3. Hopefully it or I dont make it worse. Love to get this one fixed but i guess the reality is the phone is old. Thank you for the input

timbow4 said:
Its not a tri band. Just SPH-L710. Wish this forum would let me post the pictures of what my phone is doing.. Since the firmware doesnt correct the issue I would think then its a problem with the operating system itself. I have been scouring the web and have found various threads specifically about efs repairs but they entail doing things that seem awful complicated. And i dont know if those things work on my model phone. Maybe rooting the phone gets deep enough to over write or repair the issue. Is there not a way to restore the operating system itself maybe or is that what a replacement ROM does? I am thinking of trying my hand at rooting the phone and seeing what happens. One thread indicated TWRP would backup and restore the EFS file. Im thinking if it backs up a corrupt efs file what good is that, maybe it fixes it too. Found an excellent video on XDA for rooting the S3. Hopefully it or I dont make it worse. Love to get this one fixed but i guess the reality is the phone is old. Thank you for the input
Click to expand...
Click to collapse
Backing up and restoring it won't help. You already installed a new operating system ( that's what the firmware is).the efs is part of your radios. If I remember correctly it contains your imei and other important things specific to your phone.
You may be out of luck there dude. Don't know how you wiped your efs.
Rooting this phone is simple. Just flash TWRP with Odin. Download the Twrp image from their site. Same as flashing the firmware, only you select recovery instead of AP in odin and select the Twrp image.tar instead of the firmware tar.
https://dl.twrp.me/d2spr/
Use the top on the page. (Newest)
And then use twrp to flash either SuperSU, or Magisk.
Done.
Flashing a custom rom will not fix your issue. You need a working efs. Flashing any operating system will not fix it (you already flashed the whole operating system).
Twrp can restore an efs, but only if you have a working one to backup first. You were right about backing up yours now and restoring will do nothing.
Has it ever been activated?

Prior to this, every once in awhile when i changed a battery out and turned the phone on it would have a pop-up screen tell me something was bad and the phone needed to be reset (something along those lines) and i always just turned the phone back off and on and it booted up fine each time. That may have been an indicator that something, file or system file maybe was corrupted. Then a few week ago when it booted up it started doing this whole thing. Prior to me factory restoring the phone here recently it was completely functional but since the restoration it will no longer connect me to the network. If you goto settings and click on some system features it will turn the network on for that specific function (temporarily) but does not give me any other access. It tells me that the network works but it being blocked (maybe because of the factory mode issue). The wifi works and i can make and receive calls. Still manageable but very annoying. Im going to try your instructions with installing TWRP. If i am successful then maybe i can also get into the system files and possibly restore the broken one.. Thanks again

update
So I have successfully rooted the phone by intstalling TWRP ver 3.2.1 and using TWRP to flash SuperSU ver 2.82. I also installed root explorer to get access to system files. I gained access to the EFS folder and it is empty. So now I'm not understanding if the folder is completely empty how does the phone still work at all? More research led me to a XDA developer that put together a program called EFS Professional which is supposed to backup and restore efs or imei data. Really slick program, basically takes the complication out of locating and backing up the EFS information yourself. (I would include a link but I still cant..) It includes an ADB shell and the ability to make some changes to the phone including directly turning off factory mode . It also had me install an application called BusyBox Pro which is also a very handy tool for getting access to system files. What I don't understand is that the EFS Professional program seems to locate the efs information on my phone and backups it up and then restores it from said backup however when I look at the efs folder its empty. Perhaps not all the efs information is located in the efs folder. And of course since that folder is empty the function of turning factory mode off fails because it cant find the files. I have found a few threads that has very simple instructions once you have super user access you can go right into the efs folder to factory mode and simply turn it off. Mine is empty.. So again the problem continues. Possibly with access to the ADB shell and more help from folks on here I can figure out a way to restore my efs information. I don't know if the efs information can be used from a another same model phone, I'm guessing not if it has a specific imei identification. Im working hard on this but still unsolved. I know way more at this point then I did but I think I still know just enough to be dangerous. Thankfully my phone is still functional at this point..