Hey guys..
Anyone know what causes this? I finally got my IMEI back and the phone on the network and now this..
Currently after loading the stock for GNote 2 (sch-i605) I'm back on the network after losing my IMEI I have loaded the root66. Phone boots up and said in a red message below "Loaded in factory mode. Some things not working." That message went a way fast but now this one is on the screen.
SOLVED
MrDerby01 said:
Hey guys..
Anyone know what causes this? I finally got my IMEI back and the phone on the network and now this..
Currently after loading the stock for GNote 2 (sch-i605) I'm back on the network after losing my IMEI I have loaded the root66. Phone boots up and said in a red message below "Loaded in factory mode. Some things not working." That message went a way fast but now this one is on the screen.
Click to expand...
Click to collapse
Found the answer to this issue.
You will first need a rooted phone and edit the file using ES File Explorer or Root Explorer.
Open the file “factorymode” in /efs/FactoryApp directory, it probably says OFF. Change it to ON then reboot your phone.
Also, you can use adb shell to do this too:
adb shell
su
echo -n ON > /efs/FactoryApp/factorymode
Related
Ok first of all Im sticking this question in general android Q&A because there in no XDA Forum for this phone. It is a Straight Talk LG Optimus Q 55c, this is my girlfriends phone its basically an optimus p500/v with a sliding keyboard Overclocked too 800mhz. I own a virgin optimus V so I have a lot of experience with this platform but Im stumped maybe im just neglecting to see something, Im hoping "another set of eyes" will help turn on a light and get my girlfriends phone working again as she cant afford another :/!
So here is what Im dealing with. I had rooted the phone for her and installed clockwork mod recovery & fastboot. Since she got the thing its had problems freezing (probably because it stock overclocked), and occasionally pulls a random reset. She asked me If I could install another ROM on it to see if it may help make the phone more stable. I went a searching and found that the Optimus Q community is very small almost nothing and her only real choice was a port of the Area51 Rom. So Installed the rom.... A few days later she had told me her phone was mega slow now and acting up way more, so I told her I would flash back to stock.
I rebooted the phone and found to my surprise CWM and fastboot seemed to be gone... what the h*ll? Im assuming when I flashed AreaRom it installed the stock Recovery and removed fastboot, I cant figure out any reason why the stock recovery would be back on the phone. Anyways I didnt feel like flashing a new recovery at the time. Well 3 days go by and her phone crashes and gets stuck in a boot loop. So she went in to recovery and wiped it. The phone then went through the process of collecting e-mail and password, asking about backing up, then asking whether or not to turn the location services on. Once you hit next Android throws an exception and says setupwizard.apk failed to initialize or something along those line. So after that the launcher does not load only the task bar at the top. When rebooted the phone enters a boot loop againg until wiped.
So heres the deal I can use adb, but when I try to get into an adb shell the prompt says error: closed. I have been able to use adb to push and pull files that is all. I tried to push setupwizard.apk to the system/apps directory but of coures it needs to be remounted to read write and I dont have any shell access to do that. So basically adb sees the phone but the shell doesnt work, when i type adb root it reports adbd is running as root on the phone, so I guess the shell service just never loads.... I do have stock recovery but the problem with that is there is no update.zip files it will except I have tried a myraid of methods to sign an update.zip but every time I try to run the update the stock recovery says verification failed. Of course LG has no official updates for this phone using there signature that I can use.
So basically my phone works recovery works android starts but cant finish setting up and never starts the adb shell service. If anyone knows how I can push setupwizard to /system/app, get adbd to initialize, or sign a 3rd party rom and have the stock recovery use it I would be very gratefull! Maybe there is a way to get fastboot back on there or enabled or something? adb reboot-fastboot just reboots like normal. I am at the point where I going to take the phone apart to find a serial uart connection and pray I can get a shell that way!!
Ive looked into a few programs like kdz update and lgmdp but they dont seem to work with this phone and I cant get into any emergency mode, maybe Im doing it wrong this is the first ive heard of emergeny mode.
So after having some issues with my phone I had US Cellular flash my phone to stock.
First issue:
Webtop does not work at all. When plugged into the dock I get a mouse cursor on the screen and the keyboard can be used to type text on the phone. The only option the phone gives is to mirror the display . Under setting it shows that my webtop version is not available. This also takes away the option the use the webtop to help root my phone.
Second issue:
I can't get root. I'm trying to use the photon-torpedo method as I did successfully last time and after pushing the .tar file all I get after running the "/bin/tar xf /data/tmp/photon-torpedo.tar" command I get told "/bin/tar: not found"
Any help would be awesome in getting my phone back to normal.
Whenever I try to run any command (including regular linux commands such as ls) all I get is permission denied. Interestingly enough, running cd without anything after gives me a "cd: HOME not set" error.
aha355 said:
So after having some issues with my phone I had US Cellular flash my phone to stock.
First issue:
Webtop does not work at all. When plugged into the dock I get a mouse cursor on the screen and the keyboard can be used to type text on the phone. The only option the phone gives is to mirror the display . Under setting it shows that my webtop version is not available. This also takes away the option the use the webtop to help root my phone.
Second issue:
I can't get root. I'm trying to use the photon-torpedo method as I did successfully last time and after pushing the .tar file all I get after running the "/bin/tar xf /data/tmp/photon-torpedo.tar" command I get told "/bin/tar: not found"
Any help would be awesome in getting my phone back to normal.
Click to expand...
Click to collapse
A factory reset should fix webtop. As for root. Go to MotoSunfire.com and try the 2.3.5 root method listed.
Sent from my SCH-R950 using XDA
Nope, same error I've been getting.
Interestingly enough, I still have the su binary on the phone. When in the shell typing 'su' gives me root prompt but any commands entered give me a "not found" error.
The superuser app pops up whenever any apps request root access but no apps actually get root access.
If this gives me to many issues I'm probably just going to pay the $35 and get a "new" phone.
A thought I have that would hurt to try is to do the 2.3.5 reflash and then retry the root. I don't care about having an unlocked bootloader because the device came locked.
well if you're already on 2.3.5 then you're locked for good anyway (unless factory shipped this way). so flashing the 2.3.5 sbf will only help fix things. i recommend it. it will fix webtop since it sounds like it's broken.
Hello,
I've had my S3 for over a year now and it has been mostly running great. Whenever I've had issues I tried to solve them by myself, but this time I was unable to fix my phone, so I must ask for help.
Here's what happened. I left my phone on my desk today and one of my co-workers fiddled with it. He opened SuperSU and then a message popped up saying that SU binary needs to be updated. He then choose to update it via CWM. The phone then restarted and upon starting shows the startup screen then it tries to enter the recovery, but instead it just shows it for a brief moment and then it restarts again. It keeps doing that over and over again. If I remove the battery and then insert it back again, the phone will turn on by itself and continue to reboot after failing to open CWM.
I tried to enter the recovery, but had no success. The phone did enter the Download Mode though, but flasing a ROM via ODIN will remove all of the data stored on the phone and I really need it. The phone is currently running Android Revolution HD 40.
Is there a way to get my phone operational again without loosing the data stored on it?
Thanks in advance.
laxsrbija said:
Hello,
I've had my S3 for over a year now and it has been mostly running great. Whenever I've had issues I tried to solve them by myself, but this time I was unable to fix my phone, so I must ask for help.
Here's what happened. I left my phone on my desk today and one of my co-workers fiddled with it. He opened SuperSU and then a message popped up saying that SU binary needs to be updated. He then choose to update it via CWM. The phone then restarted and upon starting shows the startup screen then it tries to enter the recovery, but instead it just shows it for a brief moment and then it restarts again. It keeps doing that over and over again. If I remove the battery and then insert it back again, the phone will turn on by itself and continue to reboot after failing to open CWM.
I tried to enter the recovery, but had no success. The phone did enter the Download Mode though, but flasing a ROM via ODIN will remove all of the data stored on the phone and I really need it. The phone is currently running Android Revolution HD 40.
Is there a way to get my phone operational again without loosing the data stored on it?
Thanks in advance.
Click to expand...
Click to collapse
did you try reflashing your recovery via Odin?
SuperSU
laxsrbija said:
Hello,
I've had my S3 for over a year now and it has been mostly running great. Whenever I've had issues I tried to solve them by myself, but this time I was unable to fix my phone, so I must ask for help.
Here's what happened. I left my phone on my desk today and one of my co-workers fiddled with it. He opened SuperSU and then a message popped up saying that SU binary needs to be updated. He then choose to update it via CWM. The phone then restarted and upon starting shows the startup screen then it tries to enter the recovery, but instead it just shows it for a brief moment and then it restarts again. It keeps doing that over and over again. If I remove the battery and then insert it back again, the phone will turn on by itself and continue to reboot after failing to open CWM.
I tried to enter the recovery, but had no success. The phone did enter the Download Mode though, but flasing a ROM via ODIN will remove all of the data stored on the phone and I really need it. The phone is currently running Android Revolution HD 40.
Is there a way to get my phone operational again without loosing the data stored on it?
Thanks in advance.
Click to expand...
Click to collapse
First of all what are co workers doing messing with your phone I would seriously not be happy!! screen lock comes to mind!
As the above post said flash another recovery in odin I recommend Philz recovery,backup your data in recovery then factory reset if that does not work flash another rom via recovery or return to stock with odin. You can also boot into recovery with adb but I would try above first.
Then charge your co-worker for all the time wasted trying to fix phone
Thank you so much for the idea, I just tried this and it worked! After flashing new recovery via ODIN, I'm now able to access my phone. There was no need to flash the ROM again, as it was fine, the only problem was with the recovery.
And I still have my data!
Thank you very much again, cheers :laugh:
tallman43 said:
First of all what are co workers doing messing with your phone I would seriously not be happy!! screen lock comes to mind!
Click to expand...
Click to collapse
He's actually a good guy and I'm sure he didn't do it on purpose. He told me that he was playing a game and he tried to add more coins using GameCIH. Then the prompt to allow root access to the app came up along with a notification to update the SU binary. He said he pressed that button by mistake. I wasn't mad at the guy, I was only upset that I may lose my data.
laxsrbija said:
Thank you so much for the idea, I just tried this and it worked! After flashing new recovery via ODIN, I'm now able to access my phone. There was no need to flash the ROM again, as it was fine, the only problem was with the recovery.
And I still have my data!
Thank you very much again, cheers :laugh:
Click to expand...
Click to collapse
you are welcome! glad to see that it works again.
So, when I waked up this morning I found my S3 turned off. Nothing to worry about, I thought, since I use SlimKat+Googy it had already happened sometimes in the past that phone auto-reboots or something.
However, when I tried to turn it on I was just stuck in the bootscreen "Galaxy S III etc", but NOT in a bootloop, just stuck, the slimkat animation never start. I can enter recovery and all.
So I tought "whatever, i'll just wipe". So I did, full wipe and reinstall of SlimKat, just to be greeted again by the same problem. I repeated some times and same thing.
Trying to adb shell it says "- exec '/system/bin/sh' failed: No such file or directory (2) -" and I can't enter shell.
At this point I was totally WTF, starting to fear the worst. Just now I'm downloading a stock rom to make a last try with it. However I would like to know if someone else had this problem and if they solved it.
Anyone?
matrixino said:
So, when I waked up this morning I found my S3 turned off. Nothing to worry about, I thought, since I use SlimKat+Googy it had already happened sometimes in the past that phone auto-reboots or something.
However, when I tried to turn it on I was just stuck in the bootscreen "Galaxy S III etc", but NOT in a bootloop, just stuck, the slimkat animation never start. I can enter recovery and all.
So I tought "whatever, i'll just wipe". So I did, full wipe and reinstall of SlimKat, just to be greeted again by the same problem. I repeated some times and same thing.
Trying to adb shell it says "- exec '/system/bin/sh' failed: No such file or directory (2) -" and I can't enter shell.
At this point I was totally WTF, starting to fear the worst. Just now I'm downloading a stock rom to make a last try with it. However I would like to know if someone else had this problem and if they solved it.
Anyone?
Click to expand...
Click to collapse
Flash stock rom with Odin... that should fix your problem.
AbhiLP said:
Flash stock rom with Odin... that should fix your problem.
Click to expand...
Click to collapse
Yup, I was waiting for the download to finish. It indeed worked, but I have some yellow debug text on screen. I did a search and seems related to efs corruption or something like that. However I'm now trying to go back to slimkat from here. Now I'm less scared anyway
Ok, now I'm scared again. I get no signal. Nor with stock or custom. Also tried to restore a nandroid and nothing.
Update: I luckily found an EFS backup in the lost+found folder. Thanks god. All working now.
So, I have this Coolpad Catalyst 3622A LTE Running MetroPCS carrier With android 5.1.1 and something weird has happened. The phone happened to be rooted at the time.
I used the app called "Boot Animations" ya'know everything nornal just like all my other devices... and I was trying to change the boot animation it had with one of the ones in the app.... Then i don't know how, or exactly the cause, But now the phone doesn't load as normal.
The Android OS loads correctly and responds I can confirm it, But there is just now a Black Screen.
Recovery mode doesn't seem to be affected.
I've basically tried all I could to fix this..
Anyone know how I can fix this?
Have you tried replacing the changed bootscreen with the stock one? Also, I would suggest not using apps to change the bootscreen. Do it manually.
EnkryptedSpirit said:
Have you tried replacing the changed bootscreen with the stock one? Also, I would suggest not using apps to change the bootscreen. Do it manually.
Click to expand...
Click to collapse
i can't. the phone is working, but blank. i need to get a active adb shell connection to fix this.
I'm having the same issue.....I think.
My phone still boots properly, connects to WiFi, and I can even boot to the recovery menu. The phone just boots to a blank screen and the only thing I can access is the pulldown menu. From there I've been able to confirm there are still apps on the phone and have even managed to use a couple of them. I'm actually using the phone now to write this. The rooting was successful Ive been using the phone for several weeks without an issue. At some point the phone started saying "invalid sim" in the notification bar but since I didn't have service I ignored it. Yesterday I went to MetroPCS to activate it. They told me that they reset it and ever since then I've had this problem. I'm pretty new to all this which is why I'm looking for guidance. If I had to guess it would be a problem with the app launcher and the fix is to wipe and install the stock everything. I do have access to a PC and will need instructions for a noob please. Thank you.
I have a coolpad cell that's been checked into do anyone knows how I can fix this problem I can't get in to reset my phone