So I've spent the past two hours trying to flash a custom recovery onto my phone so I can root and debloat.
I first tried to root following some instructions on this site and Odin, but that method failed. Then I tried to use towelroot and that method failed. I then googled the problem to find that it had to do with knox and a recent security update released by ATT. Then I flashed a custom recovery onto my phone so I could manually root and that triggered an auto stock recovery. After that I attempted to install cm11. It installed then before the rom could load, it asked me about disabling auto stock recovery and also rooting. I choose to disable it and then root. Then my phone reverted back to stock touchwiz.
How do I get rid of knox so I can root my phone?
Do you want to have a custom ROM on your phone? Root is not required to load a custom ROM.
I originally wanted to get rid of the bloatware on my phone since I don't mind some of the Touchwiz features, but if I can't gain root access due to the phones security features then I'll install something else if I have to. Right now I'm attempting to CM11 install again since I was able to install custom recovery( I had to pull the battery before Touchwiz rebooted though I superSU said it did not have binaries).
If you want TW features, flash a custom ROM based on TW.
Will doing so also give me root access?
I've rooted two devices in the past and they were never this hard so I want to be careful so I don't end up bricking my device.
UPDATE: Just tried to reinstall CM11 just to see what would happen and the same happened: it booted straight into stock touchwiz.
I've been at this for about 5 hours now and I'm at my wits end. Has anyone successfully rooted their phone from 4.4.2 over the past month?
What custom recovery is on your phone?
I had clockwork flashed.
Make sure you have the latest cwm and format the system before installing a ROM.
Before installing a custom ROM, make a nandroid backup of your current tw ROM.
I used the cyanogen installer on the website. I've installed CM before on previous devices so I'm familiar with installing roms. The CM installer is supposed to do that for me so I'm not sure if it's due to Knox and the latest ATT security update that's making it difficult to gain root access to do such as install custom mods. I've gone a google search and people seem to be having the same trouble and I don't know if a fix has been found since the last update that ATT pushed out last week.
Did you try installing a custom using the custom recovery? I have never used the installer so I can't comment, using the cm installer may not allow you to install non-cm roms.
I didn't.
Before I flashed CM11, I checked the Q/A from Cyanogen about the installer:
http://wiki.cyanogenmod.org/w/CyanogenMod_Installer
In it, they state that all you need to do is have your stock rom and software will do the rest for you. Keep in mind, that flashing CM11 was my backup option. My original intent was to simply root my device so I can remove some Samsung and ATT apps.
Here's the article from Android Central about the ATT update. Apparently I'm not the only one who is having issues trying to root:
http://www.androidcentral.com/att-brings-android-os-enhancements-galaxy-note-2-galaxy-s3-galaxy-mega
I might just have to wait out for the S6.
I have never used a CM installer even though I have used CM11 on an s3, Note2, Note3, and a Nexus 4.
I don't trust the installer and always did it the old-fashioned way with a custom recovery.
I'm going to try today since I have some time. Can you give me a link to a custom recovery? I'm going to install using odin and then try it.
Are there no stable builds for CM11?
https://download.cyanogenmod.org/?device=d2att
You should be looking for d2lte builds, not d2att.
I also did that earlier since they're universal and all I see are nightlies and experimentals.
https://download.cyanogenmod.org/?device=d2lte
The unified msm8960 ROMs have been out for a while and even though they are nightlies, they are at the stage where I would consider them stable.
Thank you.
I tried flashing another rom earlier today and it didn't install. I reloaded a backup I made before flashing and now the backup is stuck in a com.google. process. gapps loop.
What are my options?
I recommend flashing the latest Philz Touch tar.md5 recovery from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Try re-flashing the latest CM11.
Related
So I was able to use Odin to flash over a custom rom and do a rooting method (Probably screwed up somewhere) it installed SuperSU. Super SU stopped working and i updated it and thought nothing of it since I could get to my Recovery. I made a nandroid and formatted system, cache, etc. I tried to flash over Task650's AOKP and the original stock rom. I have 3 different AOKP roms and the stock rom. I have tried to use a different recovery and everytime I do it wont let me flash roms so I'm stuck. It looks like my Recoveries see that there is no root access. how can i fix this?
My I747 is currently running Carbon Rom nightly 20131102 (4.3.1), it's quite old and I want to upgrade to 4.4.
So last night I nandroid backup , format system, data, flashed Carbon KK on it, then gapps, data, cache, delvik, reboot. But it stayed at the CM alien. I reflashed several times but still stuck at there. But I can nandroid back so I'm kind of fine now. But anyone know why?
Second, I notice my \0\ folder is under sdcard\download\0\ than usual sdcard\0\, I must have done something wrong when I first flash the carbon but I don't know what it is. I usually put my .zip in download, could that be why? Could that cause the bricking I have with KK?
Last, I know there's a flash counter and when I first root/flash last year, I went thru many things to avoid that&IMEI, instead of directly flashing a recovery. I think that could be the source of the problems above??? Now 1 year is up and my warranty is already over so I don't have to worry about the counter anymore. If I want to redo everything, and have to noobiest/simpliest method to flash to KK, what should I do?
Sorry if I lack any essential information. I'd be happy to find it to help.
Did you update to the latest CWM before flashing the ROM? Is your current bootloader supported by the ROM?
Not the latest but 6.0.4.3
I'll update it to 6.0.4.7 and try again.
Unfortunately I don't know if my bootloader is supported. I don't really know how to find mine.
I would update to the latest CWM and then try to flash a 4.4.2 custom ROM. If it doesn't install, it should generate an error message.
Most custom ROMs will look for a particular bootloader. If the bootloader is not found, CWM will give you get prop errors.
audit13 said:
I would update to the latest CWM and then try to flash a 4.4.2 custom ROM. If it doesn't install, it should generate an error message.
Most custom ROMs will look for a particular bootloader. If the bootloader is not found, CWM will give you get prop errors.
Click to expand...
Click to collapse
Thanks, I'll try when I get home.
I installed the ROM fine last night without any error. So I believe the bootloader is supported then.
afyaff said:
Thanks, I'll try when I get home.
I installed the ROM fine last night without any error. So I believe the bootloader is supported then.
Click to expand...
Click to collapse
To be sure, look at the bootloaders mentioned in the ROM's updater script.
I'm sorry to make my first post so noobish, but I've been trying for a day now to get CM 11 onto my phone, and the installation keeps failing, something about the signature failing. I tried miui just to see if the rom iteself was the issue, and i had the same result. I have the phone rooted via odin(CF-Auto-Root-d2can-d2vl-sghi747m). I found a rom (cm-11-20140217-NIGHTLY-d2att) and dropped the zip on my sd, popped that in, put the phone in recovery. I formatted and cleared cache. Then tried to install the rom from external. I see it there but the installation fails every time.
Where am I going wrong? do i need something else on the phone?
thanks for any help.
1. You need to root and disable Knox (I saw you rooted but did you disable knox?)
2. You need a custom recovery. A quick way todo this is download this http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.7.0.0-d2att.tar (its the newest TWRP) and flash it using Odin.
3. then you should be able to flash which ever rom you want, BUT be careful because I think some can mess up the i747m. (PS cm11 isnt that great, still very buggy and battery life is not as good as stock.)
Oh one more thing. the CM11 file you have is old since it says d2att, cm renamed the device to d2lte which supports all north american galaxy s3's I believe.
I did disable Knox. does this matter though? I mean once you reset the phone in recovery mode and clear the cache? is CM10 any better? im not too concerned with battery life (7200mah battery)
Do you have the 4.3 bootloader on your phone? I assume you do since you mentioned that you disabled knox.
For a custom recovery, I recommend Philz Touch for the d2lte which is based on the latest CWM which can be flashed through Odin.
The best ROM I have used on the s3, and other Android phones, is Validus 13 Ground Zero ROM.
I am trying to restore a backup made with TWRP. Here's what has happened so far:
Flashed TWRP several weeks ago. I've made several backups with no problems.
Flashed NK2 radio with no apparent problems.
Full wipe of phone. Phone was not rooted at this point.
Flashed 5.01 GPE ROM.
Phone boots and I get the "Kernal not SELinux enforcing" message (ugh...KNOX). Phone won't boot to new rom. I can only get to TWRP.
Try to restore backup. TWRP checks MD5 on backup-it passes and then screen blanks and TWRP reboots. It does this several times.
After research I restore phone to stock MB4 through Odin.
Phone boots into Android and is indeed 4.4.2 MB4.
Using Unified Toolkit re-flash TWRP and then proceed to root phone. After procedure SuperSU gives me "SuperSU has stopped" msg. Follow toolkit procedure to get around KNOX. SuperSU runs and I also install Busybox. Reboot phone. Root not held. Redo toolkit procedures to attain root. Still lose it upon reboot.
TWRP still reboots when trying to do anything involved with the filesystem (restore backup--wipe cache and dalvik--none works. TWRP blanks and reboots.) . At this point I'm scratching my head. I'd like to restore the backup and also root and change to GPE. I'm thinking this comes down to not being able to do anything in the filesystem due to root not being held. Any suggestions as to how to get root to stick so I can do the restore and change ROMS? Thanks folks.
Steve KS4KJ
If you don't have root you wouldn't have twrp, you would have the stock recovery.
You need to do a factory reset and start from there.
If you can't do it in twrp, flash back to stock with Odin, then do a factory reset. At this point you may have corrected what got borked by flashing the 5.0 rom.
I would recommend flashing to latest firmware NH7 or NK2 and running phone for 24hrs just to make sure there are no issues and that everything works.
ShinySide has links in general section.
Pp.
PanchoPlanet said:
If you don't have root you wouldn't have twrp, you would have the stock recovery.
You need to do a factory reset and start from there.
If you can't do it in twrp, flash back to stock with Odin, then do a factory reset. At this point you may have corrected what got borked by flashing the 5.0 rom.
I would recommend flashing to latest firmware NH7 or NK2 and running phone for 24hrs just to make sure there are no issues and that everything works.
ShinySide has links in general section.
Pp.
Click to expand...
Click to collapse
In flashing the stock 4.4.2 rom (which is where my phone was when I started this journey) I have done a reset haven't I? That is what I did when the 5.0 GPE rom wouldn't boot. I can certainly try loading the 4.4.4 NK2 rom and seeing what that will do. Pretty sure I did not root before using the toolkit to replace the stock recovery with (originally) CWM and then later with TWRP. I remember wanting to do a Nandroid backup before installing the 4.4.4 OTA (which then didn't work because I had changed the stock recovery). I keep thinking that KNOX is involved with this but not sure what to try to remedy it (other than the 4.4.4 suggestion which I will try). Thanks for the reply.
Steve
The only thing Knox does is tell Samsung if you rooted and installed a custom recovery, and that is only while your still under warranty (12 months ) after you get the phone. After that warranty runs out they don't give a hoot what you do to your phone.
You need to flash it twice so that it works properly, after d/l Samsung info app, in play store and check that you have current bootloader and modem .
And use Chainfire's auto root to root afterwards.
Pp.
PanchoPlanet said:
The only thing Knox does is tell Samsung if you rooted and installed a custom recovery, and that is only while your still under warranty (12 months ) after you get the phone. After that warranty runs out they don't give a hoot what you do to your phone.
You need to flash it twice so that it works properly, after d/l Samsung info app, in play store and check that you have current bootloader and modem .
And use Chainfire's auto root to root afterwards.
Pp.
Click to expand...
Click to collapse
I'll try that. Thanks again.
I love this phone but recently switched to a note 3 and love it as well. However, my wife is having problems with her phone and thought it time to factory reset to remedy the problem. However I figured i should put a custom rom on her E980 if I'm going to go through all that, I'd experiment with mine. Wow, what's with installing a custom recovery? I tried numerous ways after spending countless hours yesterday and nothing seemed stable. I had to "tot" back to stock 4.4 numerous times.
Could someone explain the procedure please as after I root how do I install custom recovery and what else I need to install and what order. Also, a good stable rom for my with based off of lollipop.
mikelets456 said:
I love this phone but recently switched to a note 3 and love it as well. However, my wife is having problems with her phone and thought it time to factory reset to remedy the problem. However I figured i should put a custom rom on her E980 if I'm going to go through all that, I'd experiment with mine. Wow, what's with installing a custom recovery? I tried numerous ways after spending countless hours yesterday and nothing seemed stable. I had to "tot" back to stock 4.4 numerous times.
Could someone explain the procedure please as after I root how do I install custom recovery and what else I need to install and what order. Also, a good stable rom for my with based off of lollipop.
Click to expand...
Click to collapse
From my personal experience, easiest 'path' would be to start from stock Jellybean, then to install recovery via Freegee after rooting, and then to update that recovery to latest TWRP (process I'm using for years now).
If you really want to start with KK as base, you should install GPRO_Recovery.apk and install a recovery from there, after you obtain root. After that, update that ancient recovery to TWRP and you're good to go.
For AOSP LP ROMs, you have to choose between 4 available ROMs (there are maybe more, but those mentioned should be updated more frequently) - CyanogenMod, BlissPop, Carbon and SlimLP. There are some builds of Resurrection Remix and AICP but I know nothing about them because I have never used them. Others are pretty much stable for everyday usage and should play nice on your e980s.
Start with one of four ROMs mentioned above and you won't have any troubles/issues.
ShadySquirrel said:
From my personal experience, easiest 'path' would be to start from stock Jellybean, then to install recovery via Freegee after rooting, and then to update that recovery to latest TWRP (process I'm using for years now).
If you really want to start with KK as base, you should install GPRO_Recovery.apk and install a recovery from there, after you obtain root. After that, update that ancient recovery to TWRP and you're good to go.
For AOSP LP ROMs, you have to choose between 4 available ROMs (there are maybe more, but those mentioned should be updated more frequently) - CyanogenMod, BlissPop, Carbon and SlimLP. There are some builds of Resurrection Remix and AICP but I know nothing about them because I have never used them. Others are pretty much stable for everyday usage and should play nice on your e980s.
Start with one of four ROMs mentioned above and you won't have any troubles/issues.
Click to expand...
Click to collapse
i can't find anyway to root my phone neither i think if there is any recovery installed in my phone (idk if that's even possible) because it doesn't go to recovery at boot
I am already on stock lollipop for F240L but it have too much blootware.
edit: so it turns out recovery is installed on mobile but in an attempt to root i ran into another error. when the program(root software) it restarts Phone into recovery, i received this error. "NO command" and i cant push updates thorough ADB.
edit2: after pressing random keys it started working but when i try to push update through adb it say
"you need adb 1.0.32 or newer to sideload to this device." any help?
ShadySquirrel said:
From my personal experience, easiest 'path' would be to start from stock Jellybean, then to install recovery via Freegee after rooting, and then to update that recovery to latest TWRP (process I'm using for years now).
If you really want to start with KK as base, you should install GPRO_Recovery.apk and install a recovery from there, after you obtain root. After that, update that ancient recovery to TWRP and you're good to go.
For AOSP LP ROMs, you have to choose between 4 available ROMs (there are maybe more, but those mentioned should be updated more frequently) - CyanogenMod, BlissPop, Carbon and SlimLP. There are some builds of Resurrection Remix and AICP but I know nothing about them because I have never used them. Others are pretty much stable for everyday usage and should play nice on your e980s.
Start with one of four ROMs mentioned above and you won't have any troubles/issues.
Click to expand...
Click to collapse
Tayyab.Hasan said:
i can't find anyway to root my phone neither i think if there is any recovery installed in my phone (idk if that's even possible) because it doesn't go to recovery at boot
I am already on stock lollipop for F240L but it have too much blootware.
edit: so it turns out recovery is installed on mobile but in an attempt to root i ran into another error. when the program(root software) it restarts Phone into recovery, i received this error. "NO command" and i cant push updates thorough ADB.
edit2: after pressing random keys it started working but when i try to push update through adb it say
"you need adb 1.0.32 or newer to sideload to this device." any help?
Click to expand...
Click to collapse
I did it. went back to KK using download mode, rooted and now i will flash new ROM. Thanks.