27 replies to this topic

[kristopher]

Hello, I am new to Cyanogenmod and trying to use the installer. I have installed the app on the phone, followed the steps, installed the installer on my Windows 7 machine, ran the installer and get to the congratulations screen. Once the phone reboots it goes back to the stock Android factory image. I was getting a question, like others I have read, asking No, Yes then it would reboot back to factory. Now I just get a reboot to factory. Any suggestions? I read in previous threads this was an issue but some said it was resolved.

Support token: 9731612e-3e17-4838-8a3c-ee60f975b40a

[raywalters]

Your logs are...odd. The device is recognized, and the install starts. The recovery is downloaded and installed, then the device is rebooted (all expected). On that reboot, the device goes totally incognito and never comes back to talk to the installer. Do you have a different PC you can use to try to install?

[raywalters]

Can you get me the stock build number you are on? Also, a screenshot of your about device would be helpful as well.

[kristopher]

raywalters, on 21 August 2014 - 11:06 PM, said:

Your logs are...odd. The device is recognized, and the install starts. The recovery is downloaded and installed, then the device is rebooted (all expected). On that reboot, the device goes totally incognito and never comes back to talk to the installer. Do you have a different PC you can use to try to install?

Yes I have another PC, I will try and get back with you shortly.

raywalters, on 21 August 2014 - 11:28 PM, said:

Can you get me the stock build number you are on? Also, a screenshot of your about device would be helpful as well.

[raywalters]

Excellent, thanks for that. The devs and I are talking about the case. Let me know what happens on a different PC.

[kristopher]

raywalters, on 22 August 2014 - 12:31 AM, said:

Excellent, thanks for that. The devs and I are talking about the case. Let me know what happens on a different PC.

I tried on my other PC, Windows 7 as well. The install "looked" different, like it was installing. At one point I did see a fallen over android guy with a red triangle. Then it rebooted and installed applications. It appeared to have more steps to the install process this time. After the software said completed on the PC, the phone rebooted and came back up with stock android. Here is my token.

Support token: 35293afe-e030-41e4-8f3e-ee419ce39bc5

[raywalters]

The only error I see is stdout: Detecting device...", "stderr: ERROR: Failed to access device. libusb error: -12

This is indicative of a bad cable. Your install is saying finished in the logs, but above the finish statement is a bunch of timeout errors. Booting back to stock is indicative of Knox being on the device, but we are getting mixed reports saying that some S3's have it and others don't. Do you have knox running on the device?

[kristopher]

raywalters, on 22 August 2014 - 04:13 PM, said:

The only error I see is stdout: Detecting device...", "stderr: ERROR: Failed to access device. libusb error: -12

This is indicative of a bad cable. Your install is saying finished in the logs, but above the finish statement is a bunch of timeout errors. Booting back to stock is indicative of Knox being on the device, but we are getting mixed reports saying that some S3's have it and others don't. Do you have knox running on the device?

Not that I know of, but I don't have the phone with me today. I will look when I get home tonight. I ended up trying a different cable last night and ended up with the same result. I will dig out another cable and see what happens with that one. Is there an easy way to see if Knox is on the phone?

Thank you!

[raywalters]

Knox is two things, it can be a regular old app that you install and run, the other is an actual process that runs in a partition on the device and prevents you from tampering with the OS (which COULD be a reason you are booting to stock, but as I mentioned not all S3 devices have received Knox).

[kristopher]

Ok, I tried with a third different cable and this is the support token. Same thing happened, fallen over android guy with red triangle, installation continues, then reboot to stock. I am going to look and see if Knox is installed. If you have any other suggestions, I will keep an eye on the forum tonight.

Support token: 7cc0747b-01f1-44fb-9924-58aec05df2ea

[kristopher]

raywalters, on 22 August 2014 - 08:02 PM, said:

Knox is two things, it can be a regular old app that you install and run, the other is an actual process that runs in a partition on the device and prevents you from tampering with the OS (which COULD be a reason you are booting to stock, but as I mentioned not all S3 devices have received Knox).

I found the culprit! Now I need to figure out how to remove it. Suggestions?

[raywalters]

AHhhh well done. The solution unfortunately is to root your device and use a knox removal tool. Then you will be able to move forward.

[VMSGSIII]

Or you could use towelroot; a program that roots your Samsung device while bypassing Knox. It worked for me. You can download towelroot at towelroot.com. It's a one-click process. You don't even have to connect your phone to the PC.

[starbits]

Unfortunately I am having the same problem.  I have tried to install CyanogenMod several times.  I do have Knox but towelroot (alone) did not help. This time I installed Towelroot, and then installed superSU.  SuperSU said I had Knox and at first could not remove it (it hang).  Then I started Towelroot and ran superSU again and it said Knox was successfully removed.  So I re-ran Cyanogen install but got the same problem - the android falls over with a red triangle at the end of Operating System install and before System Applications.  At the end when it said "root access lost" I said NO to the fix.  If you have suggestions please let me know.  My Support token: 4aa4b82c-e2e0-42c2-b13e-42525b1f53aa
Thanks

[raywalters]

If that is the what you are seeing, then Knox is indeed still the issue. I would do some more research on a different method than towelroot.

[kristopher]

@Starbits - Here is the process that I went through to get Knox off of the phone. It took time and patience.

1. Root the phone
2. Install SuperSU, Explorer, NoBloat Free and Android Terminal Emulator
3. First, I ran the SuperSu and it mentioned Knox was installed. I let it try to disable Knox
4. Then I ran the NoBloat Free and removed every single item that said Knox, KLMS and anything else on this list.

com.sec.enterprise.knox.attestation

com.sec.knox.eventsmanager

KLMS Agent

KNOX

Knox Notification Manager

KNOX Store

5. After this, I used Explorer to search on the local and the SD card for items with "knox" or "klms" in the name. I made a list on paper of the name and locations.
6. I then tried to use Android Terminal emulator to delete the items but most were read only.
7. After a little searching I found a guide on how to remount the system in write mode to be able to delete (http://stackoverflow...stem-on-android)

Use this to make writeable: mount -o rw,remount /system

Use this after done to make read-only: mount -o ro,remount /system

8. I went through and deleted every time on the list. You may have to remount other folders, depending on where the files are located
9. Then I searched again and again to ensure that no files existed with these names.
10. I rebooted, ran NoBloat Free again, ran search again and finally Knox was gone.

Hopefully this will help you out. I have included the links to the two articles I used as guides.

Guide I started with: http://androidcentra...galaxy-devices/
Guide that ultimately lead to the removal of Knox: http://forums.androi...emove-knox.html

starbits, on 08 September 2014 - 08:27 AM, said:

Unfortunately I am having the same problem.  I have tried to install CyanogenMod several times.  I do have Knox but towelroot (alone) did not help. This time I installed Towelroot, and then installed superSU.  SuperSU said I had Knox and at first could not remove it (it hang).  Then I started Towelroot and ran superSU again and it said Knox was successfully removed.  So I re-ran Cyanogen install but got the same problem - the android falls over with a red triangle at the end of Operating System install and before System Applications.  At the end when it said "root access lost" I said NO to the fix.  If you have suggestions please let me know.  My Support token: 4aa4b82c-e2e0-42c2-b13e-42525b1f53aa
Thanks

And ultimately, as I mentioned here: http://forum.cyanoge...sprint-updated/. I had to side load Cyanogenmod. I couldn't get the installed to work, even after KNOX was removed from the device. I tried multiple computers and cables. The guide for side loading is easy to follow, just make sure you have Android development tools downloaded first.

Edited by kristopher, 08 September 2014 - 08:16 PM.

[starbits]

Thanks @kristopher.  I was wondering if you had ever gotten it to work; now I know it can really be done.  Your instructions will be a big help, but now it is the beginning of the week and I have work.  I am sure your advice about time and patience is correct.  I may not report back for a while but I wanted to let you know I appreciate your reply.

[jac187]

Support token: a6714627-6f5e-4346-beb9-58ba941c2dab

S3 is rooted. No signs of KNOX.  Still reboots to stock rom after running CM Installer.

[raywalters]

jac187, are you seeing any prompts on your device when the installer runs? If so, what are they?

[jac187]

raywalters, on 10 September 2014 - 02:56 PM, said:

jac187, are you seeing any prompts on your device when the installer runs? If so, what are they?

not prompts.

i do see the down droid with red triangle.
last screen is "Root access possibly lost Fix?"