Related
I have tried everything I know to do so I'm here asking for help....
I run Calks ROM and recently tried updating without wiping (normally never do). After a couple days of a buggy phone, I decided to wipe data, format, format, format, wipe data, etc and flashed it again. Start using it and it starts acting up again. Did my wipe/format deal and flashed stock...and left it stock. Within the first day it locked up and reset itself multiple times.
I don't know what to do...is there anyway to start any "cleaner" than formatting everything multiple times? I would really like a working phone again...
Are you restoring your information with titanium backup? If you are that's your problem.
Sent from my PC36100 using XDA App
gqstatus0685 said:
Are you restoring your information with titanium backup? If you are that's your problem.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
+1. You can restore apps only, but don't restore apps + data.
Is this the only rom that's causing it?
I never, ever, ever use any "backup" anything. All apps get reloaded one by one and settings get modified one by one...
This is happening with every rom I try. I format EVERYTHING (except SD card, which is my next attempt at fixing...). This is why it's so frustrating. I can't blame anything. I try running the ROMs stock (no not-included apps) and the phone is still running like crap.
Tried deleting the ".android_secure" folder from the sd card?
If it's happening on every rom, and you completely wipe every thing correctly, the only thing they have in common is the sd card contents. Right?
My Evo made me Swype this from the XDA App.
xNotta said:
Tried deleting the ".android_secure" folder from the sd card?
If it's happening on every rom, and you completely wipe every thing correctly, the only thing they have in common is the sd card contents. Right?
My Evo made me Swype this from the XDA App.
Click to expand...
Click to collapse
Android secure is supposed to be deleted during the fActory reset. I will try getting the SD formatted tonight and start FRESH, FRESH....
perhaps it's the kernel?
SpaceMonky said:
perhaps it's the kernel?
Click to expand...
Click to collapse
I've tried many kernels (stock, stock tweaked, ziggy, kingxklack)
awenthol said:
Android secure is supposed to be deleted during the fActory reset. I will try getting the SD formatted tonight and start FRESH, FRESH....
Click to expand...
Click to collapse
Mines never been deleted from stock factory reset or reset with amon.
It started to cause problems with app downloads from me switching roms and reinstalling all my apps and moving them.
Just remember, if you have apps on your sd card (Not on a separate partition) move them to the phone before deleting it if you want to keep them.
Any luck fixing it yet?
What bout nand restore? Did you ever make a nand backup? It has always fixed any issues I've ever had.
I've been traveling for work and haven't had a chance to sit down and mess with it since the night I initially posted. Hopefully it is as simple as androidsecure not getting deleted...thanks for the heads up.
I just did a FULL FULL FULL wipe of the phone. "Factory reset," "format; SD, SD ext, system, boot, data, etc"....
I then flashed zip, rebooted and let it sit for 10 min before turning it on...upon unlocking, it locked up.
THIS IS GETTING RIDICULOUS!!! Is it possible the phone is just effed???
squick said:
What bout nand restore? Did you ever make a nand backup? It has always fixed any issues I've ever had.
Click to expand...
Click to collapse
No good either...the last "good" backup comes up with "checksum error."
I'm not big on nand backups, since I usually do full wipes and restart from scratch. I don't really care if I can restore an old setup.
If you can't find a software reason for its acting up, it's a hardware problem. Full wipes take care of pretty much any software problem.
I would suggest unrooting and taking it by a Sprint store. If none of the suggestions you've tried so far have done any good, that's about your only option.
Sent from my PC36100 using XDA App
TheMagicalSock said:
If you can't find a software reason for its acting up, it's a hardware problem. Full wipes take care of pretty much any software problem.
I would suggest unrooting and taking it by a Sprint store. If none of the suggestions you've tried so far have done any good, that's about your only option.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
That's not an option either...as I bought it outright off ebay.
Guess I'll just go to the Epic...
I don't know what to do. I'm having this issue with a couple ROM's.
First happened after installing the latest version of Baked Snack (2.3 - EB13-based). Flashed according to instructions, ran fine for a few days, started acting a little laggy one day so I shut it down and started it back up. Once it started back up, it started boot looping. Only thing that worked was to wipe and start over.
I thought it might be a no-journaling data corruption thing, so I decided to try the journaled version of midnight 5.1 (which I think is based off of Bonsa 4.0.1). Used odin to go back to stock, rooted with cw3.0.0.6/ext4, etc. flashed ROM according to instructions. Again worked great for a few days, then after shutting my phone down tonight and restarting it a few minutes later, boot loops. Reverting to an earlier nandroid backup worked, and I'm assuming wiping and reflashing would work, but I gotta get to the bottom of this.
What's baffling to me is that everything works fine for a few days. I'm shutting the phone down normally, I'm not doing anything strange before shutting down. In both cases I was using setCPU, but with very conservative settings (200min 1000max, conservative or on demand). I can't think of what else I may be doing to cause these problems.
Anyone else run into this?
rsage said:
I don't know what to do. I'm having this issue with a couple ROM's.
First happened after installing the latest version of Baked Snack (2.3 - EB13-based). Flashed according to instructions, ran fine for a few days, started acting a little laggy one day so I shut it down and started it back up. Once it started back up, it started boot looping. Only thing that worked was to wipe and start over.
I thought it might be a no-journaling data corruption thing, so I decided to try the journaled version of midnight 5.1 (which I think is based off of Bonsa 4.0.1). Used odin to go back to stock, rooted with cw3.0.0.6/ext4, etc. flashed ROM according to instructions. Again worked great for a few days, then after shutting my phone down tonight and restarting it a few minutes later, boot loops. Reverting to an earlier nandroid backup worked, and I'm assuming wiping and reflashing would work, but I gotta get to the bottom of this.
What's baffling to me is that everything works fine for a few days. I'm shutting the phone down normally, I'm not doing anything strange before shutting down. In both cases I was using setCPU, but with very conservative settings (200min 1000max, conservative or on demand). I can't think of what else I may be doing to cause these problems.
Anyone else run into this?
Click to expand...
Click to collapse
Sounds like you got everything covered. The only thing I can think of is do you have a lot of apps on your SD card? Could be the card is starting to get corrupted. Backup everything on the card to a computer and reformat the card and restore the data.
kennyglass123 said:
Sounds like you got everything covered. The only thing I can think of is do you have a lot of apps on your SD card? Could be the card is starting to get corrupted. Backup everything on the card to a computer and reformat the card and restore the data.
Click to expand...
Click to collapse
Thanks I'll try that. The first time, I did have a ton of apps on the sd card. Second time, I didn't really reinstall many apps because I was a little gunshy from what happened, then it happened again anyway. I'll try this tonight.
rsage said:
Thanks I'll try that. The first time, I did have a ton of apps on the sd card. Second time, I didn't really reinstall many apps because I was a little gunshy from what happened, then it happened again anyway. I'll try this tonight.
Click to expand...
Click to collapse
Formatting your SD card is always a good step when ROMs don't seem to flash right.
Also, Baked Snack is not/will never be supported here.
k0nane said:
Formatting your SD card is always a good step when ROMs don't seem to flash right.
Also, Baked Snack is not/will never be supported here.
Click to expand...
Click to collapse
Thanks k0nane, reformatting as I type this, hopefully this works as I'm out of ideas.
And yes, wasn't asking for support for BS, but for a general issue I'm having with all ROM's at the moment. From now on if I ever have to refer to that ROM, I will call it "the ROM that shall not be named"...
rsage said:
Thanks k0nane, reformatting as I type this, hopefully this works as I'm out of ideas.
And yes, wasn't asking for support for BS, but for a general issue I'm having with all ROM's at the moment. From now on if I ever have to refer to that ROM, I will call it "the ROM that shall not be named"...
Click to expand...
Click to collapse
While you are working on your phone, if you are going to stick with midNIGHT, I suggest you move to 5.2, 5.1 was a little goofy for some and 5.2 seems to have fixed any issues it had.
budderocks said:
While you are working on your phone, if you are going to stick with midNIGHT, I suggest you move to 5.2, 5.1 was a little goofy for some and 5.2 seems to have fixed any issues it had.
Click to expand...
Click to collapse
I'd love to, but the 5.2 update is only available for the no journaling version
rsage said:
I'd love to, but the 5.2 update is only available for the no journaling version
Click to expand...
Click to collapse
You are in luck, it is updated now. I believe he is uploading it as I type this
Sent from my SPH-D700 using XDA App
budderocks said:
You are in luck, it is updated now. I believe he is uploading it as I type this
Click to expand...
Click to collapse
Yep, XDA thread not updated yet but I see the upload on his site, thanks for the heads up! Hopefully the card reformat and ROM update will resolve the situation.
So I'm having a problem I can't seem to fix.
I'm rooted, have been running the stock everything but with a few tweaks and some bloat removed. Everything works great but I am hoping to improve battery life. So I researched a few ROMs and pick a couple to try. I can flash them just fine with no problems, get all my apps back and set up with no problems. and I can use the phone all day just like normal.
Now the problem: if ever I have to restart for some reason, or even after I make a nandroid back up, when it restarts and boots up I eventually get several messages where processes are one by one stopping. until the phone is useless and froze up.
So it goes through 10 or more of these:
Unfortunately, the process android.process.media has stopped
Unfortunately, the process android.process.phone has stopped
etc, etc,etc
I have tried everything I could find on here to fix, but it seems all fixes are for a single process failing. This happens to me on all Roms I have tried, but I am just wanting to run Sonic. Even if I restore the nandroid I get the messages. If I factory reset or restore my kid-of-stock backup I am fine. If I start over and reflash a clean Rom I can set up and use but as soon as I restart it happens again. Sometimes when restarting I get a message about android updating but can't figure out how to stop that from happening.
Thanks in advance for any help!!! This is very annoying.
Are you doing full wipes and factory reset? If you are doing this between each flash then it sounds like you are restoring bad data into your apps.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Try re-flashing the latest Gapps and seeing if that will help.
It has done when I've had the same problem before.
edfunkycold said:
Are you doing full wipes and factory reset? If you are doing this between each flash then it sounds like you are restoring bad data into your apps.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
I thought the same thing so I tried without putting back in any apps. And still happened. And if I flash Sonic with TB it does it right away when I get booted up for some reason.
KidCarter93 said:
Try re-flashing the latest Gapps and seeing if that will help.
It has done when I've had the same problem before.
Click to expand...
Click to collapse
Thanks, I'll try to find the latest Gapps now and report back if it helps out. But I'm not real familiar with the Gapps part so it may take some searching to figure out what theya re for Sonic Rom if it matters the rom.
This is the reason why I do not do any backup.. Most stuff on my phone is not important enought to require a back up.. If I have issues, I just reinstall the rom and my apps from the market.. I have only reinstalled my current rom once, and that is because I was not able to change my current prl...
Jorgy11 said:
So I'm having a problem I can't seem to fix.
I'm rooted, have been running the stock everything but with a few tweaks and some bloat removed. Everything works great but I am hoping to improve battery life. So I researched a few ROMs and pick a couple to try. I can flash them just fine with no problems, get all my apps back and set up with no problems. and I can use the phone all day just like normal.
Now the problem: if ever I have to restart for some reason, or even after I make a nandroid back up, when it restarts and boots up I eventually get several messages where processes are one by one stopping. until the phone is useless and froze up.
So it goes through 10 or more of these:
Unfortunately, the process android.process.media has stopped
Unfortunately, the process android.process.phone has stopped
etc, etc,etc
I have tried everything I could find on here to fix, but it seems all fixes are for a single process failing. This happens to me on all Roms I have tried, but I am just wanting to run Sonic. Even if I restore the nandroid I get the messages. If I factory reset or restore my kid-of-stock backup I am fine. If I start over and reflash a clean Rom I can set up and use but as soon as I restart it happens again. Sometimes when restarting I get a message about android updating but can't figure out how to stop that from happening.
Thanks in advance for any help!!! This is very annoying.
Click to expand...
Click to collapse
Sounds like you need to do a FULL Wipe before you Flash. Also make sure your Downloading the Rom over WiFi, or Hardline.
prboy1969 said:
Sounds like you need to do a FULL Wipe before you Flash. Also make sure your Downloading the Rom over WiFi, or Hardline.
Click to expand...
Click to collapse
I have been doing a full factory reset, wipe system, wipe cach and dalvic. I downloaded the Roms onto my computer and transferred them to sd card. It happens for all ROMs except the stock backup I made.
Jorgy11 said:
I have been doing a full factory reset, wipe system, wipe cach and dalvic. I downloaded the Roms onto my computer and transferred them to sd card. It happens for all ROMs except the stock backup I made.
Click to expand...
Click to collapse
Do not restore anything with TB whatsoever and I can assure you it will work. There is corrupt data somewhere.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Jorgy11 said:
I have been doing a full factory reset, wipe system, wipe cach and dalvic. I downloaded the Roms onto my computer and transferred them to sd card. It happens for all ROMs except the stock backup I made.
Click to expand...
Click to collapse
The process I use for Flashing Roms is the same one I've always used. It's the one that's in my Sig. I'll also relink, in case your on the mobile. I have used it for a very long time now. It avoids a lot of the hassles of a bad flash.
http://forum.xda-developers.com/showthread.php?p=17647821
Thank You All
Thank you all for your help!!!
So far I have managed to flash the rom and reboot several times with no issues.
I have only had this GS3 for a week now and I feel I can finally play with some roms and see what I like. I usually find one I like and stick with it. On my EVO Shift I used the same rom for 2 years.
Here is what I did for anyone that may have same problem:
Wiped everything, per-normal.
Loaded ROM.
Loaded a few of the apps I wanted to keep some settings for (like GO Launcher and Handcent) using Rom Toolboxes App manager.
I then rebooted to see if I had any problems... none.
Used Rom Toolbox to install just the apps and no data for my other 50+ apps I wanted to keep.
Made Nandroid backup, which forced reboot... no problems.
Installed Titanium Backup, this is where I was nervous because I thought it might be that app causing problems with asking about new ID and such. Installed just 2 apps that I wanted to keep data for that Rom Toolbox for whatever reason didn't have, maybe I didn't have a recent backup. 2 apps were Tasker and GO Bookmark widget. When asked to change ID I selected "later" and after restoring 2 apps I imediatly deleted TB.
Reboot to see if I got errors... none
Setup all settings and tweaks I wanted.
Made Nandroid backup... no issues yet
I then deleted all TB backups I had on SD card figuring one was the culprit.
I am still nervous to re install TB but at least as of now I have a working nandroid to revert to so after a couple days I will reuse it.
As of now I have had no issues what so ever... and I can tell battery life on this Sonic rom is much better.
Glad your all sorted out . I do not think that Titanium Backup the App itself is was causing the issues. Although I do recognize somethings that could. Restoring GoLauncher with settings Data could cause issues. Especially from one Rom to the next. Hopefully your not trying to restore the Data settings you had on the Shift. Also with Handcent, I would not restore settings across different Roms.
TEAM MiK
MikROMs Since 3/13/11
com.android.phone has stopped
Jorgy11 said:
So I'm having a problem I can't seem to fix.
I'm rooted, have been running the stock everything but with a few tweaks and some bloat removed. Everything works great but I am hoping to improve battery life. So I researched a few ROMs and pick a couple to try. I can flash them just fine with no problems, get all my apps back and set up with no problems. and I can use the phone all day just like normal.
Now the problem: if ever I have to restart for some reason, or even after I make a nandroid back up, when it restarts and boots up I eventually get several messages where processes are one by one stopping. until the phone is useless and froze up.
So it goes through 10 or more of these:
Unfortunately, the process android.process.media has stopped
Unfortunately, the process android.process.phone has stopped
etc, etc,etc
I have tried everything I could find on here to fix, but it seems all fixes are for a single process failing. This happens to me on all Roms I have tried, but I am just wanting to run Sonic. Even if I restore the nandroid I get the messages. If I factory reset or restore my kid-of-stock backup I am fine. If I start over and reflash a clean Rom I can set up and use but as soon as I restart it happens again. Sometimes when restarting I get a message about android updating but can't figure out how to stop that from happening.
Thanks in advance for any help!!! This is very annoying.
Click to expand...
Click to collapse
I had the exact same problem with a reoccurring message that would flash on and off every second or so. I did both a data restart then a reboot of the android software by pushing the down volume button then holding the power button. When the LG logo appeared I released both buttons and followed the instructions for an android factory reboot. Apparently it is the SIM card. The android com.android.phone communicates with the SIM card and allows calls and texts to be sent and received using the android software. My SIM card got damaged somehow and could not receive the call from the android app com.android.phone. I had to buy a new SIM card for ten dollars and had my stored files on the SIM moved to the new one and no more problems. Telus and Bell move the files to the new SIM for free i'm sure other major service providers offer the same free service.
@pokey2000 Thanks for that info. But this is the Sprint S3 section. And the user you are replying to has a Sprint S3. Sprint phones are Cdma and do not have a removable sim card.
His issues where resolved 6 months ago. This is the second thread you bring back up that is old and dead. Please look at and read the thread. Before bringing dead topics back up.
Remember search is your best friend, Have a great day!
I was on Tweaked 1.0 and was loving every minute of it. Until i heard that we had just got new kit kat roms. So i made a back up and proceeded to install the new Liquid. Coming from Note 2, It felt like I was in AOSP heaven again. But needless to say i shouldn't have been so excited for a alpha build just yet. A couple of things i needed weren't working just yet so i went back into twrp and wiped everything. Once i had restored my tweaked backup i booted up and it started constantly boot looping. So this is what i did. I wiped everything again (including system) and just flashed the tweaked rom. It kept loading up over and over to a screen that said "Process System is not responding, Close it?" So i wiped again and re-flashed the Liquid and i got nothing. Lastly i grabbed the Stock MI7 md5 and flashed it with odin three times. It finishes every time, but still the same system error when booting up. Can anyone please help me fix my phone. All help is much appreciated.
Man I'm telling you the smarter the phones are becoming the more problems it gives us. I used to be a flashaholic back on the note 2 now with the note 3 I had a brickloop out of nowhere. I'm freaked as to flash things unto my rom for real
Sent from my SM-N900T using xda app-developers app
Precisely
Exactly what i mean. With my Note 2 i flashed very frequently, but almost never had problems like these. I'm also glad to hear i'm not the only one whose had those random brickloops. It doesn't seem to matter what rom it is. Everything goes fine for a good while then out of nowhere, constant rebooting. I think if I can fix my phone this time i'm gonna just go stock rooted
treytreytaylor said:
Exactly what i mean. With my Note 2 i flashed very frequently, but almost never had problems like these. I'm also glad to hear i'm not the only one whose had those random brickloops. It doesn't seem to matter what rom it is. Everything goes fine for a good while then out of nowhere, constant rebooting. I think if I can fix my phone this time i'm gonna just go stock rooted [/QUOT
If you read through the forum for the note 3 this is a common problem after a restore of the efs partition on older twrp editions. flash this to fix
Click to expand...
Click to collapse
Ill flash roms and mods to my hearts content.. One thing you won't catch me doing its restoring a backup. Hell I won't even make a ⊼ nandroid .. Lol
sent from my ??????? note 3?
treytreytaylor said:
I was on Tweaked 1.0 and was loving every minute of it. Until i heard that we had just got new kit kat roms. So i made a back up and proceeded to install the new Liquid. Coming from Note 2, It felt like I was in AOSP heaven again. But needless to say i shouldn't have been so excited for a alpha build just yet. A couple of things i needed weren't working just yet so i went back into twrp and wiped everything. Once i had restored my tweaked backup i booted up and it started constantly boot looping. So this is what i did. I wiped everything again (including system) and just flashed the tweaked rom. It kept loading up over and over to a screen that said "Process System is not responding, Close it?" So i wiped again and re-flashed the Liquid and i got nothing. Lastly i grabbed the Stock MI7 md5 and flashed it with odin three times. It finishes every time, but still the same system error when booting up. Can anyone please help me fix my phone. All help is much appreciated.
Click to expand...
Click to collapse
Don't restore jack. No recovery is right as of yet for this. Phones are very temper mental
NOTE 3
BACARDILIMON said:
Don't restore jack. No recovery is right as of yet for this. Phones are very temper mental
NOTE 3
Click to expand...
Click to collapse
second to last release of twrp (2.6.3.7) says it fixed the efs back-up does this not address the back up issue?
slamindamalibu said:
second to last release of twrp (2.6.3.7) says it fixed the efs back-up does this not address the back up issue?
Click to expand...
Click to collapse
I know they said that bit it did for a few. Just don't trust me been thru it
NOTE 3
Lesson learned. No more backing up with twrp. I was fine with good ol' Titanium Backup. But anyways, found a fix for this. Took a couple minutes.
http://forum.xda-developers.com/showthread.php?t=2471421
treytreytaylor said:
Lesson learned. No more backing up with twrp. I was fine with good ol' Titanium Backup. But anyways, found a fix for this. Took a couple minutes.
http://forum.xda-developers.com/showthread.php?t=2471421
Click to expand...
Click to collapse
That fix works but has also failed me. Just try and not use backups
NOTE 3
treytreytaylor said:
Lesson learned. No more backing up with twrp. I was fine with good ol' Titanium Backup. But anyways, found a fix for this. Took a couple minutes.
http://forum.xda-developers.com/showthread.php?t=2471421
Click to expand...
Click to collapse
the file i attached is just a script that does exactly this flashed through recovery.
What about CWM?
Sent from my SM-N900T using xda app-developers app
BACARDILIMON said:
Don't restore jack. No recovery is right as of yet for this. Phones are very temper mental
NOTE 3
Click to expand...
Click to collapse
I have restored multiple multiple backups already on twrp latest and more recently with cwm.. So they are pretty solid guys.. I do have the brickloop fix on SD though.. Thanks to twrp,, and Just in case I need it again.
Sent from my SM-N900T using Tapatalk
jdidtht said:
I have restored multiple multiple backups already on twrp latest and more recently with cwm.. So they are pretty solid guys.. I do have the brickloop fix on SD though.. Thanks to twrp,, and Just in case I need it again.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
I have used both and they both are the same. But do a restore and if ur phone likes it ur ok if not then u get boot loop or brick. As long as he knows it it is his gamble to make
NOTE 3
i was using jedi rom then i tried to flash darthstalker romnow i'm stuck in a boot loop and when it does finally boot it says process system isn't responding, if i choose wait i get the drop down menu with toggles and that's it rest of the screen is black if i hold power button i get power off or reboot option only. if i choose close it goes into a boot loop. haven't got anything that's been able to fix it yet. help pls
Yea this happened to me a couple of days ago. Im done restoring from backups now.
Sent from my SM-N900T using Tapatalk
So my friends Boss' son tried to be all "l33t h4x3r" and mess with his S6(sm-g920p). First he ruined his EFS section of the phone, the Baseband is Unknown, no IMEI number, Software Version is Unknown, and his radio wasn't working. I think he then tried to do some crazy **** in ODIN, "No Clue he doesn't remember". Well i've never ran into a constant reboot issue with any Android phones i've owned. I've had bootloops but this is throwing me for a loop. I've tried:
Loading TWRP wiping everything and trying a Custom ROM
Using Odin to Recover back to Stock
Honestly im not sure whats up anymore or if his phone is even fixable at this time.
Link to Probs: http5://youtu.be/QVLgYF_7tGU
Hi, you certainly have a challenge there. It sounds like you need to restore both the partitions and the stock OS.
If the phone is a 32 GB model, please see the whole thread at http://forum.xda-developers.com/sprint-galaxy-s6/help/operating-smg920p-t3263325
There is a PIT file linked at post 16, instructions for using it at post 22. Also a link for the latest stock TAR file.
Again, this would be for 32 GB model, but you want to flash first the PIT and then the TAR.
I think I may have done that already too but I'll look again once in home and see if maybe I did it in the wrong order. Thanks for the quick reply friend. ?
Well i did as instructed but Baseband is still unknown and it is still rebooting over and over :/
jbowman21 said:
Well i did as instructed but Baseband is still unknown and it is still rebooting over and over :/
Click to expand...
Click to collapse
If he messed up the efs partition, like it's empty, without a backup. I'm pretty sure the phone is done.
Sent from my SM-G900P using Tapatalk
elesbb said:
If he messed up the efs partition, like it's empty, without a backup. I'm pretty sure the phone is done.
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
I recommend he brings it to Sprint, after they "diagnose" it and declear its broken they should be able to replace it. Just make sure its as close to stock as possible that way it does not seem rooted.
1619415 said:
I recommend he brings it to Sprint, after they "diagnose" it and declear its broken they should be able to replace it. Just make sure its as close to stock as possible that way it does not seem rooted.
Click to expand...
Click to collapse
That is about the only option left. There are other options to restore the efs (pretty much rebuild it from scratch) but that is not something an every day user can do. I had an efs issue on my S4. I was tinkering with things I shouldn't have, forget exactly what I was doing, it was on T-Mobile so I think I was trying to remove the data cap (was on prepaid). Was pretty much in the same boat as OP but was able to completely from scratch rebuild the stuff that belongs in the efs directory. Some stuff I never restored but didn't seem to affect the device.
elesbb said:
That is about the only option left. There are other options to restore the efs (pretty much rebuild it from scratch) but that is not something an every day user can do. I had an efs issue on my S4. I was tinkering with things I shouldn't have, forget exactly what I was doing, it was on T-Mobile so I think I was trying to remove the data cap (was on prepaid). Was pretty much in the same boat as OP but was able to completely from scratch rebuild the stuff that belongs in the efs directory. Some stuff I never restored but didn't seem to affect the device.
Click to expand...
Click to collapse
Huh, if you remember, write a guide that way you can help people.
1619415 said:
Huh, if you remember, write a guide that way you can help people.
Click to expand...
Click to collapse
This was many many years ago. What saved me was the fact that Notepad++ keeps a copy of the file you have open even when you close the program. I just had to remember what things needed to be reverted back and the edits undone. I guess I didn't really rebuild it from scratch lol.
elesbb said:
This was many many years ago. What saved me was the fact that Notepad++ keeps a copy of the file you have open even when you close the program. I just had to remember what things needed to be reverted back and the edits undone. I guess I didn't really rebuild it from scratch lol.
Click to expand...
Click to collapse
Lol
1619415 said:
Lol
Click to expand...
Click to collapse
Yeah sadly I have no idea how the efs is populated. The second instance I get a new phone, dd is done on the efs partition and created into a .img file.
jbowman21 said:
So my friends Boss' son tried to be all "l33t h4x3r" and mess with his S6(sm-g920p). First he ruined his EFS section of the phone, the Baseband is Unknown, no IMEI number, Software Version is Unknown, and his radio wasn't working. I think he then tried to do some crazy **** in ODIN, "No Clue he doesn't remember". Well i've never ran into a constant reboot issue with any Android phones i've owned. I've had bootloops but this is throwing me for a loop. I've tried:
Loading TWRP wiping everything and trying a Custom ROM
Using Odin to Recover back to Stock
Honestly im not sure whats up anymore or if his phone is even fixable at this time.
Link to Probs: http5://youtu.be/QVLgYF_7tGU
Click to expand...
Click to collapse
Koop's firmware didn't work with my phone either. This version of it fixed mine for some reason. Try flashing it to yours
mediafire.com/download/c55xaeb7geq0i2d/G920PVPU3BOJ7_G920PSPT3BOJ7_SPR.zip
Now i got same issue i accidently restored efs and ah man ive tried every thing it reboots after 2 or 3 mins no matter what rom back up i have and i have efs and radio with all my back ups ive restored it also no luck. Guess im going to the sprint store tomorrow even after i flashed stock 6.0.1 i can get to about half way through wifi setup before it reboots no matter what 2-3 minutes phone reboots unless in twrp
Still no luck becareful and dont try to restore efs i suppose in twrp. Your phone may never stop rebooting ive flashed 2 different 6.0.1 builds one was the revo other was from sammobil both @koop1955 has them PB6 6.0.1 odin doesnt fix this.
YOYOYO
Well wtf or omg it completely died left it for a day. Now its working so far it hasnt rebooted in 30 mins LOL but dude sucks going to a phone with kitkat after using marshmallow and one of the fastest phones made for awhile. I did pull the sim card out and try it in a old boost maybe that reset something idk its working though.My problems were Rebooting constantly after 2-3 mins no matter what rom i had even stock.
---------- Post added at 12:31 PM ---------- Previous post was at 12:11 PM ----------
Saafir said:
Backed up my EFS before ever even rooting. Stuck that bad boy in Dropbox for safety. *pats self on back*
Last one of these topics I seen, end result was JTAG.
Click to expand...
Click to collapse
BEcareful if u restore that efs. i backed up too but once in twrp. Now all i did was check restore efs by accident just tried restoring a renegade rom system,boot, and data. Tell you what i wont be rushing through crap and am fine with stock for awhile. Probably will still take the replacement when it comes its white the black one i got is too blue.
Saafir said:
I've got a raw partition backup as well as one through TWRP. If you check md5/sha hashes for data integrity, and only install software instances specific to your device, aside from manually monkeyin around
Hey needless to say im researching full partition backups did you use a app by wanam partitions back up and restore? Or just simple adb commands. Last used adb on a moto e 2nd with success on unlocking. Once i got a new harddrive haven't needed it.
Click to expand...
Click to collapse
Theres similar issues happening on sprint note 5s as well and has a couple threads currently speaking about this problem. Strange strange. It happened to me after updating to mm and then rooting.
Well i did try the note rom right before and when i did hit restore efs it after wiping system data boot from moar MM rom phone rebooted for days then after few resets and odin flashes i let it die then a day later it worked.
Correct but have always preferred the 925p roms.
Well i helped another with the rebooting issue on any rom.
He tried everything then but let it die after battery died plug it in and bingo his worked to
IF CONSTANT REBOOTING.
LET THE BATTERY COMPLETLY DRAIN.
AFTER FLASHING STOCK.