I have a rooted and unlocked GS3 with liquidsmooth running on it. I tried the encryption feature which turned out to be a horrible mistake, every time the phone locks it turns off then restarts(Which I am pretty sure it isn't supposed to be doing) and now I am stuck in safe mode hell with a phone that keep restarting, should I just reflash it, or is there a way to fix this issue? Sorry if this is the wrong forum, I am rather new.
MrChubbs said:
I have a rooted and unlocked GS3 with liquidsmooth running on it. I tried the encryption feature which turned out to be a horrible mistake, every time the phone locks it turns off then restarts(Which I am pretty sure it isn't supposed to be doing) and now I am stuck in safe mode hell with a phone that keep restarting, should I just reflash it, or is there a way to fix this issue? Sorry if this is the wrong forum, I am rather new.
Click to expand...
Click to collapse
Odin back to stock and reroot, easiest way to solve the problem
Sent from my SCH-I535 using xda app-developers app
You can try to reflash the ROM to see if that works. Don't forget to do factory reset when flashing. That should get you back to factory settngs of the rom and reset your setup including the encryption mess.
Alrighty, thank you both for the help
Related
If I have cognition on my device now, would it be ok to do a factory reset. My phone keeps turning off by it's self and I want to try to do a reset since some people in other forums said thats what they did to fix their problem.
not sure if that is the problem, i've heard its actually a hardware issue, try odin one click to stock, and reflash! my cap is a 1007 build and i used to get random shutdowns while on stock, but when i started flashing custom ROM's it all stopped. the last person that did a factory reset on a custom ROM was asking how to build a jig... so maybe some of the other more expierenced people can help on this issue!
Soulweaver said:
If I have cognition on my device now, would it be ok to do a factory reset. My phone keeps turning off by it's self and I want to try to do a reset since some people in other forums said thats what they did to fix their problem.
Click to expand...
Click to collapse
Has your phone shutdown on its own before running cog?
If your phone is experiencing the random shutdown issue, than it most likely will not matter which rom you are on as the problem is hardware related.
You could always try doing the reset - just remember you will lose your apps
Sent from my GT-I9000 using XDA App
So, how do you fix it? Should I have AT&T replace my device or what?
If you are in that return period, might as well! You will loose your apps, but if you use TiBu to back up, then copy all the contents of titanium backup to your desktop!
Sent from my SAMSUNG-SGH-I897 using XDA App
Hey everyone, I've done some searching but I can't seem to find what I'm looking for. I was having a problem with my CM10 installations so I decided to revert back to a stock rom and start fresh.
I used odin to flash "I727UCLF6_I727ATTLF6_I727UCLF6_HOME.tar.md5" (which is supposed to be the stock ICS rom for at&t) and everything goes great, but the phone now hangs on the "Rethink Possible" AT&T logo. I've let it sit for about an hour so I'm pretty certain that nothing is going to happen.
I tried doing the same thing over hoping that maybe it was a bad flash or some kind of fluke, but came back to the exact same problem.
Any suggestions here would be phenomenal! :silly:
Factory reset
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mmerlina said:
Hey everyone, I've done some searching but I can't seem to find what I'm looking for. I was having a problem with my CM10 installations so I decided to revert back to a stock rom and start fresh.
I used odin to flash "I727UCLF6_I727ATTLF6_I727UCLF6_HOME.tar.md5" (which is supposed to be the stock ICS rom for at&t) and everything goes great, but the phone now hangs on the "Rethink Possible" AT&T logo. I've let it sit for about an hour so I'm pretty certain that nothing is going to happen.
I tried doing the same thing over hoping that maybe it was a bad flash or some kind of fluke, but came back to the exact same problem.
Any suggestions here would be phenomenal! :silly:
Click to expand...
Click to collapse
Reboot into recovery which will be stock recovery factory reset 3x and wipe cache 3x reboot and it will come up.
Yep you guys were right that did the trick! I didn't even think of it. I meant to post this last night when I actually did it but I fell asleep.
Do you know what exactly the phone is doing (or trying to do) when this actually happens to cause it? Just out of curiosity.
Thanks again!
Only way to find out is connect a debugger. Android SDK, ddms.bat
I'm not sure exactly but I have had similar issues with getting stuck in a boot loop. Usually formating and factory reset and a fresh flash did the trick.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I've figured out how to fix it! First, I went to Section 5 of this http://forum.xda-developers.com/showthread.php?t=1762709 thread and odin-ed back to stock. Next I fixed my IMEI using a guide I found on xda. It was the second part of thishttp://forum.xda-developers.com/showthread.php?t=1804117 thread that says "IMEI is already corrupt".
Next, I did a bunch of things that I don't think I should have done and I ended up with a soft brick phone so I went and flashed back to stock via odin by following this http://forum.xda-developers.com/showthread.php?t=1840030 guide. I don't really know if it was necessary and I ended up getting stuck on the activation screen. If at any time you can not get past the activation screen, the third post down from here shows how to get past it so you could go to your settings and check them out or unlock your bootloader or whatever it is you need to do. But this whole part may not be necessary.
This is the part that I think completely fixed the phone. Probably the most important part of this whole guide. You have to dial *2767*3855# from a completely stock rom (root66 or others). It factory reset my phone and somehow the calls work, although it always says I'm roaming
A couple days ago I rooted my s3 and flashed the CM10.1 ROM. It had problems with mobile data and connecting to 4G and phone calls, so I tried out a bunch of different ROMs before deciding it had to be something else.
I figured out that my IMEI had been erased and since I didn't have it backed up (and I have no idea where my nandroid backup is or what happened to it) I had to manually restore it using some NV items reader writer tool and some other similar tool. It worked but there was something else, I think it was called ERI, was set to none. I kept trying stuff and ended up doing a factory reset. I attempted to unroot my S3, I have no idea if I succeeded in unrooting.
What I just did was soft brick my s3, not completely sure how, but I did then re flash root66 using odin successfully and now I'm back to the activation screen. Now it is stuck trying to activate the phone, but it fails every-time, and I can't do anything but restart the phone. So I restart the phone and have to go through the set up screen again and it tries to re-activate but fails and goes through the whole thing again.
Could someone please help me?
According to the Verizon website the phone is activated.
Update 8:24 PM EST: I have gotten past the activation screen but it says that the phone is out of service and when I try to call someone it says that the "mobile network is not available". Please help.
Since nobody is here to answer me, I will post the answer once I figure out what to do, just in case somebody in the future has the same problem.
I'm going to start by re-rooting my phone. I'll let you know how that goes and if anybody else could help me out that would be great. Thanks.
UPDATE 7:45PM EST:
I successfully re rooted the phone via odin and tried to start it up to no avail. Next I tried to flash a ROM, but I must have forgotten to unlock the bootloader since I couldn't even get the phone to boot completely. Right now I'm flashing back to the vzw root66 rom and then I'm going to re root and try to unlock the boot loader.
UPDATE 8:07PM EST:
I finally figured out how to get past the activation screen and I unlocked my bootloader. Before I flash AOKP I'm going to see if I could fix everything else. I think I'm pretty close to a solution. If anybody else is having the same problem send me a message or reply here, I'll try to answer your questions if you let me know what you've done.
I really just need a way past the activation screen. After that I think I could figure out what to do.
Sorry your having problems. I wish I could help but never ran into that problem so everything you said went over my head otherwise I would of fine a lot of research. At least now you are learning more and more.I just figured I would respond since no one else did.Good luck.
Sent from my SCH-I535 using xda premium
http://forum.xda-developers.com/showpost.php?p=30182790&postcount=1
Have you tried this?
defkult said:
http://forum.xda-developers.com/showpost.php?p=30182790&postcount=1
Have you tried this?
Click to expand...
Click to collapse
Yes, I managed to bypass the activation screen but now I still can not make any calls.
mikeman45 said:
Sorry your having problems. I wish I could help but never ran into that problem so everything you said went over my head otherwise I would of fine a lot of research. At least now you are learning more and more.I just figured I would respond since no one else did.Good luck.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Thanks.
Well I suppose it is hard for a phone to make calls when it isn't activated.
Goodluck on your quest though.
Thanks for the help, I finally got it working.
myoussef0 said:
Thanks for the help, I finally got it working.
Click to expand...
Click to collapse
What was the main problem?
Sent from my SCH-I535 using xda premium
In case someone else has this problem...When I flashed pure 4.2.1, I couldnt get past activation and then found out how to bypass the screen. Tap once in each corner of the screen to bypass activation screen. Then once at home screen go to settings>more(right below WiFi/Bluetooth/data)>mobile networks>CDMA subscription. NV will be selected, change it to RUIM/SIM. Reboot phone. Worked perfectly for me.
No mobile network found
jmarch said:
In case someone else has this problem...When I flashed pure 4.2.1, I couldnt get past activation and then found out how to bypass the screen. Tap once in each corner of the screen to bypass activation screen. Then once at home screen go to settings>more(right below WiFi/Bluetooth/data)>mobile networks>CDMA subscription. NV will be selected, change it to RUIM/SIM. Reboot phone. Worked perfectly for me.
Click to expand...
Click to collapse
Thanks for this post. I ran into the same problem (flashing CM 10.1) with my first S3 phone but did not know how to fix it (wish I saw your post ahead of time). I returned phone to stock via Odin and was able to exchange for a second S3 phone via Verizon (since I have phone insurance). I flashed AOKP ms 1 (jb 4.1.2) on second S3 phone and noticed it was hanging on activation and also said no mobile network when trying to make a call. Luckily, the phone spontaneously rebooted on its own and then started working. Previous to my first S3 phone, I had a Galaxy Nexus. Never ran into any problems with the Galaxy Nexus and almost tempted to go back to it since the S3 seems buggy when flashing a new rom. I am afraid I'm going to brick yet another S3 and be out $400 since I don't think phone insurance will allow me to exchange a second time since this probably alert them to the fact that I'm flashing custom roms.
Also, under mobile networks>system select be sure to change from home to automatic. Reboot.
jmarch said:
Also, under mobile networks>system select be sure to change from home to automatic. Reboot.
Click to expand...
Click to collapse
All was working fine until I tried to do this. At first nothing was selected and everything was working, but when I tried selecting automatic and rebooted it selected home for me and it is impossible to change back to automatic without it automatically changing it back to home against my will.
I was running slim 4.2.1 for quite some time with no problems, i loved it. I flashed 4.2.2 and my phone got stuck in NV and my phone number would come up as 000-000-3370. On first boot everything seems to be fine except that i get an error when i try to open up the play store. On my next boot is when I would see these problems. I tried everything from dirty flashing from a working 4.2.1 rom to completely formatting everything, even my external sd, and the same thing happens. This happens with every 4.2.2 rom out there. When i reboot i get stuck on the activating screen and my phone will get stuck in NV and ruim/sim wont stick no matter what i do. i don't know what else to do. someone please help!
It isn't a rom issue it is an S 3 issue that randomly occurs when flashing ROMs. You will have to flash the stock rom and reprovision your phone. I know because it has happened to me twice and both times it was with a Touchwiz ROM. You should have backed up your IMEI just in case this happens.
my imei is backed up. but why is it only 4.2.2 roms that do this?
I was able to flash back to a 4.2.1 Rom, namely pure Google for now, with no problems. but when I flash any 4.2.2 Rom the same thing happens.
All 4.2 ROMs used to do this to me.
However.
Only also happened when I flashed miui.
Now I run liquid smooth and haven't had the problem since.
sent from that young galaxy.
God bless the American people!
do u guys think I should Odin back to stock, then root, unlock, and try to flash 4.2.2?
Actually, there is an easier way
I have had this happen numerous times and it lef me to mess with my phone a little bit. I originally thought that setting it to CDMA/SIM and then rebooting would fix the problem, but I found a simpler solution to that. The last time I encountered the problem I simply set the phone to RUIM/SIM under mobile networks and then Turned on airplane mode for a few seconds then turned it off and I found my number under phone settings and everything. Try that and let me know how it goes.
Edit: Sorry, the term is RUIM/SIM, not CDMA/SIM. My bad.
hmmm, I'll definitely give that a shot later on tonight.
well I tried it, it works. but only temporarily. once I reboot it reverts back to how it was. any other thoughts?
anyone?
Chitala383 said:
anyone?
Click to expand...
Click to collapse
try this. i had the same problem. http://forum.xda-developers.com/showpost.php?p=35600769&postcount=2
nope, none of that works either. no matter what I do ruim/sim will not stick on a reboot on any 4.2.2 Rom. I'm really getting frustrated with this.
no one has any other solutions for me?
Chitala383 said:
anyone?
Click to expand...
Click to collapse
Does your phone display an IMEI number?
Settings->About->Status
Don't need the number, just to know if you have it there....
Also do you still have Root/Unlocked bootloader?
yes, i have an imei. i lost it once before so now its backed up, i'll never make that mistake again. it was a nightmare trying to get it back. and yes, i am rooted and unlocked.
Chitala383 said:
yes, i have an imei. i lost it once before so now its backed up, i'll never make that mistake again. it was a nightmare trying to get it back. and yes, i am rooted and unlocked.
Click to expand...
Click to collapse
Have you done a complete factory restore through Odin? You would lose root and unlocked bootloader, but it may be faster to restore to stock, and reroot/mod than to try to find an "easy" fix. I was having some issues the other day in between a few ROM's, but I just factory restored, and restarted from "scratch". Now I am running perfect.
You may have already tried, but on page 1 you asked if you should, and I did not see a confirmation you did so.
Had the same problem... And yes, the phone must be reprovisioned. Although sometimes you can just adjust the network settings and change it from NV. That worked for me also.
Sent from my SCH-I535 using Tapatalk 2
I flashed root 66 via Odin, bootloop. flashed the ma2 stock image, bootloop. then flashed the lk3 stock image with success. but still with the same results as before.
tomorrow I'll try flashing g1 and start from scratch there. what do u guys think?
well, I odin'd back to bone stock G1, rooted with rootdebugfs, flashed cwm with ez recovery, unlocked my bootloader with ez unlock, flashed liquidsmooth 4.2.2 rc2 and guess what. same ****!!!!!!!!!!!!! i'm really getting fed up with this. someone has to have a solution to this cuz this is really pissing me off.
I was messing around with CM and I went into twrp to restore a backup and now my phone is locked. Can anyone point me where to go with this?
If you encrypted your device they only solution to decrypt is to factory reset.
Sent from my HTC6525LVW using Tapatalk
You need to search around here. This is a documented issue with aosp ROMs. Someone put out a command line fix (i think it's in the noon-carrier-specific m8 forum) or you can use the ruu files found in this forum.
electric turd said:
I was messing around with CM and I went into twrp to restore a backup and now my phone is locked. Can anyone point me where to go with this?
Click to expand...
Click to collapse
i just sent in my phone after this same issue i had tried the newest nightly from CM and flashed fine ran through the whole set up process then found out my bluetooth dont work so i restored my most recent bak booted my phone up and i get a message to put in my password that i have never set up
electric turd said:
I was messing around with CM and I went into twrp to restore a backup and now my phone is locked. Can anyone point me where to go with this?
Click to expand...
Click to collapse
I have had this twice now, i fixed it by formatting data in twrp then factory resetting and restoring a backup from my sd. I lost all my internal storage.
factory reset dont work either sorry were both S.O.L. unless u have insurance then just "loose ur phone"
I'm back guys!!!!! I ruu'ed in fastboot. Weird thing was when my phone booted back up it still had supersu!!!!!! That made me happy. I then flashed twrp through flashify and restored a back up I made before this whole fiasco. Thanks again for everything!!!!
So you returned your phone to Verizon over this? If it turns on you can fix it.
electric turd said:
I'm back guys!!!!! I ruu'ed in fastboot. Weird thing was when my phone booted back up it still had supersu!!!!!! That made me happy. I then flashed twrp through flashify and restored a back up I made before this whole fiasco. Thanks again for everything!!!!
So you returned your phone to Verizon over this? If it turns on you can fix it.
Click to expand...
Click to collapse
mine turns off right after it boots dosent matter where it boots to
skcitzo said:
i just sent in my phone after this same issue i had tried the newest nightly from CM and flashed fine ran through the whole set up process then found out my bluetooth dont work so i restored my most recent bak booted my phone up and i get a message to put in my password that i have never set up
Click to expand...
Click to collapse
So you sent in a phone that you broke and that can be fixed but are too lazy to research? And this is why companies lock down bootloaders. If you cant do basic searching, then dont root your phone.