Related
the question is short, sweet, and to the point. How do I get (or keep intact) root access on the newest version of CyanogenMod?
ANNOYING- (I lose root access every time I install CyanogenMod, and I have to boot into CMW and restore back to stock ROM every time to get root back)
I did some research on this issue, and most sources say "CyanogenMod has officially decided not to include root rights in their newer ROMs".
EEEK! :/ HALP PL0X!!1!111!!!!
Root access is turn off by default but you can still turn it on.
Look in Developer Options menu.
In developer options, enable Root for ADB & Apps.
deleted
I replied to this post....But I wanted to reply to another post,actually....sorry, I opened too many browser tabs....and caused this mistake
Restore Root status to Captivate phone w/CyanogenMod 11 M12
Moderators, If this is not the right place to post, kindly move to proper location.
I have a AT&T Captivate phone (SGH-I897 Samsung) that I rooted and changed to a Cyanogenmod 11 M12.
Before changing to KitKat
Code:
Capivate
Model: Samsung SGH-I897
Firmware: 2.3.5
Baseband: I897UCKK4
Kernel: 2.6.35.7-I897UCKK4-CL614489
Build#: GINGERBREAD.UCKK4
I changed the OS from GingerBread to KitKat with Odin3 V1.85 and this thread
http://forum.xda-developers.com/showthread.php?t=1350266
Instead of (speedmod kernel) I used Corn kernal 7.0A Odin flashable version .
My phone now reads:
Code:
Capivate
Model: Samsung SGH-I897
Firmware: 4.4.4
Baseband: I9000UGK3
Kernel: 3.0.101-gd54123e [email protected] #1 Tue Nov 11 21:49:07 PST 2014
Build#: cm_captivatemtd-userdebug 4.4.4 KTU84Q a842ce8199 test-keys
Most of the apps need to be reinstalled (not an issue). I will need to restore phone contacts, txt msging logs. (If I can not, it will just be inconvenient. (I did {I think correctly} a backup of the data. Will see if info can be restored.)
My main question: My phone is no longer Rooted. Is there a procedure to restore the Rooted state? How can this be accomplished? (Detailed directions preferred if available.)
Thank you in advance for your assistance.
EDIT -- Problem solved regarding ROOT Access
Congrats! Android 4.4.2 KitKat firmware based custom ROM CM11 M4 is now installed and running on your AT&T Galaxy Captivate SGH-I897. [Note: Root may turned off by default in CM ROM, To enable it, enable developer settings first (tap the build number 8 times under about device), then enable root under Developer Settings]
Click to expand...
Click to collapse
androidiphonehacker said:
the question is short, sweet, and to the point. How do I get (or keep intact) root access on the newest version of CyanogenMod?
ANNOYING- (I lose root access every time I install CyanogenMod, and I have to boot into CMW and restore back to stock ROM every time to get root back)
I did some research on this issue, and most sources say "CyanogenMod has officially decided not to include root rights in their newer ROMs".
EEEK! :/ HALP PL0X!!1!111!!!!
Click to expand...
Click to collapse
MITHRAND1R said:
Thank you in advance for your assistance.
Click to expand...
Click to collapse
You are, in fact, in the wrong forum.... this is for the S4, not the Captivate. Any way, check either security settings or developer options for an entry called root access. It should be something to do with that.
lordcheeto03 said:
You are, in fact, in the wrong forum.... this is for the S4, not the Captivate. Any way, check either security settings or developer options for an entry called root access. It should be something to do with that.
Click to expand...
Click to collapse
Thanks. I'll look for the Captivate forum and post my question there.
You may have to update superusr.
So I've been through getting the bootloader unlocked, getting superuser permission, and getting CWM installed (version 6.0.4.6). Everything is going swimmingly except my phone seems to think it is an international variant somehow. When I try to install multiple version of Cyanogemod they all fail with error 7 and say this build is for a different device variant. Because I've got root access I jumped straight into build.prop using root explorer but ro.product.device, ro.build.product, and every other instance of the device name are all set to m7vzw. I'm not really sure what to do or why my phone is reporting as an m7ul. Any Ideas?
Euthyphro said:
So I've been through getting the bootloader unlocked, getting superuser permission, and getting CWM installed (version 6.0.4.6). Everything is going swimmingly except my phone seems to think it is an international variant somehow. When I try to install multiple version of Cyanogemod they all fail with error 7 and say this build is for a different device variant. Because I've got root access I jumped straight into build.prop using root explorer but ro.product.device, ro.build.product, and every other instance of the device name are all set to m7vzw. I'm not really sure what to do or why my phone is reporting as an m7ul. Any Ideas?
Click to expand...
Click to collapse
Did you install the Recovery for the m7vzw or for the m7?
The one for the m7vzw can be found in the Verizon Original Android Development sub-forum.
It's not the same as the one for the m7 and could cause that issue.
Either that or you changed your CID and/or MID and didn't change it back.
santod040 said:
Did you install the Recovery for the m7vzw or for the m7?
The one for the m7vzw can be found in the Verizon Original Android Development sub-forum.
It's not the same as the one for the m7 and could cause that issue.
Either that or you changed your CID and/or MID and didn't change it back.
Click to expand...
Click to collapse
That will be just it, Didn't realize the CWM version mattered.
I was going to use CS-Auto-Root but just had a couple questions. After reviving the tablet today, I did numerous updates. Would CF root still work with the new software? The only thing diffrent I can see is the build numberm does that matter? Details below, and thanks!
Model #: SM-T700
Android Version: 4.4.2
Build number: KOT49H.T700XXU1ANK2
atech087 said:
I was going to use CS-Auto-Root but just had a couple questions. After reviving the tablet today, I did numerous updates. Would CF root still work with the new software? The only thing diffrent I can see is the build numberm does that matter? Details below, and thanks!
Model #: SM-T700
Android Version: 4.4.2
Build number: KOT49H.T700XXU1ANK2
Click to expand...
Click to collapse
Numerous updstes? Anyways, try it, if it soft brivks your Tab S, just flash the stock firmware with Odin.
It shouldn't soft brick it most likely. If it fails it will just revert back to stock recovery and not give you root. Try cfautoroot first then try rooting with twrp.
Hello, it's been a long time since I messed with this but I'm smart. I'm also in a rush (unfortunately) to find a TW-based firmware that I can flash to from CM11.
The end goal is to use the unlock code I just purchased, but that won't work because I'm on CM11, I assume.
I'm knee deep in information, half of which I understand, half of which I think I barely understand.
What information do you need to help me?
From what I understand, being on a 4.4.4 CM 11 I must have a firmware that is at least android 4.3 or higher, is that correct?
If so, what other specs do I need to ensure I don't brick the phone from having the wrong bootloader, modem, ect from being incompatible?
Effectively, I'm tyring to find firmware to get back to any TW-based firmware from CM11 android 4.4.4. (Also somewhat unsure if it needs to be just TW based or 100% stock)
politelyowned said:
Hello, it's been a long time since I messed with this but I'm smart. I'm also in a rush (unfortunately) to find a TW-based firmware that I can flash to from CM11.
The end goal is to use the unlock code I just purchased, but that won't work because I'm on CM11, I assume.
I'm knee deep in information, half of which I understand, half of which I think I barely understand.
What information do you need to help me?
From what I understand, being on a 4.4.4 CM 11 I must have a firmware that is at least android 4.3 or higher, is that correct?
If so, what other specs do I need to ensure I don't brick the phone from having the wrong bootloader, modem, ect from being incompatible?
Effectively, I'm tyring to find firmware to get back to any TW-based firmware from CM11 android 4.4.4. (Also somewhat unsure if it needs to be just TW based or 100% stock)
Click to expand...
Click to collapse
The first thing I would recommend is to verify your bootloader and modem version. There is a playstore app, Phone Info *Samsung*, by vndnguyen that will do this. Or you can use the terminal emulator that is in CM roms and find out with these two commands:
Code:
getprop ro.bootloader
getprop | grep version.baseband
All I have seen indicates you will need to be on a stock rom with a stock dialer to use the code. You may even need to unroot before using (I am not sure about root/unroot.) Before recommending any stock rom source, are you using an i747 or an i747M?
dawgdoc said:
The first thing I would recommend is to verify your bootloader and modem version. There is a playstore app, Phone Info *Samsung*, by vndnguyen that will do this. Or you can use the terminal emulator that is in CM roms and find out with these two commands:
Code:
getprop ro.bootloader
getprop | grep version.baseband
All I have seen indicates you will need to be on a stock rom with a stock dialer to use the code. You may even need to unroot before using (I am not sure about root/unroot.) Before recommending any stock rom source, are you using an i747 or an i747M?
Click to expand...
Click to collapse
I know that it is an I747. I will comment again when I have the info for bootloader and modem.
So lets assume we find a rom that is; i747 gs3 stock rom and stock dialer; meets android version requirements (which I would love to have confirmed, based on the OP); compatible bootloader and modem; and is rooted, and the unlock code doesn't work. If we assume the unlock failed because it is rooted, is there a way to unroot the phone that doesn't require flashing a different, unrooted, to spec, rom? That is something that I truly don't understand what is happening.
Is there a wiki, or a list, or somewhere I can go to learn more about bootloaders and modems? I don't understand how they play into the overall configuration; such as how they may be X or Y when I'm running CM11, instead of being mandatory for a given configuration. I guess that question is, what prerequisites determine the bootloader and modem options that one may be and can be running or that one can flash successfully.
politelyowned said:
I know that it is an I747. I will comment again when I have the info for bootloader and modem.
So lets assume we find a rom that is; i747 gs3 stock rom and stock dialer; meets android version requirements (which I would love to have confirmed, based on the OP); compatible bootloader and modem; and is rooted, and the unlock code doesn't work. If we assume the unlock failed because it is rooted, is there a way to unroot the phone that doesn't require flashing a different, unrooted, to spec, rom? That is something that I truly don't understand what is happening.
Is there a wiki, or a list, or somewhere I can go to learn more about bootloaders and modems? I don't understand how they play into the overall configuration; such as how they may be X or Y when I'm running CM11, instead of being mandatory for a given configuration. I guess that question is, what prerequisites determine the bootloader and modem options that one may be and can be running or that one can flash successfully.
Click to expand...
Click to collapse
Some of the stock ROMs will remove root, that would be one way to resolve the issue. If you flash a stock image that is rooted, and it is rooted with SuperSu you can use the options in the SuperSu app to either temporarily unroot or to completely remove root.
I don't recall seeing a specific source for info about what bootloader / modem is needed in each situation. Most is accumulated knowledge from reading many posts and threads.
There are variations on what is correct, it all depends on the specifics of a device's status. For example, CM 11 would run on 4.3 bootloaders and modems up until about September of a year ago (or was that two years ago), since then you need to be on 4.4.2 bootloaders and modems. I think the same held true for AOSP based roms. I don't recall seeing where any of the 5.x.x roms have run on 4.3 bootloaders and modems. (Well, I think the devices run but have signal and data issues - both 4.4.x and 5.x.x roms.)
Generally you will see it said that the 4.4.2 Touchwiz based custom roms must be on 4.4.2 bootloaders and modems. In truth there were a number of such roms that would run with the 4.3 bootloader and modem IF one of a few specific kernels were flashed just after the rom was flashed.
All,
my sgh-i747 WiFi doesn't appear to work. under settings> WiFi slider (OFF)> slide to on (remains off)
next goto WiFi setup screen: no devices listed, buttons at bottom of screen dim/greyed out.
history:
phone was bricked by a forced ATT update. I finally did a rom update/reinstall to push a working stock kernel kitkat 4.4.2
thx
Rob
ALSO i need working links to Lollipop for sgh-1747 using oden
PS: I do ROM , hardware and software updates on data storage systems with petabytes of storage. BUT THIS PHONE MAKES ME FEEL STUPID....
My Hats Off to All Of You Who Hack, Play, or Make Mods for the Phones.
Boot image not matching firmware on your phone can cause wifi to not work. The kernel doesn't have the what it needs to work with the radio you have installed. It is a fairly typical stock rom problem. Custom roms typically have broader support instead of being targeted at a specific firmware.
First step is to figure out what exactly you have on your phone now. Need to know bootloader, modem, and boot image versions since this phone is finicky. Hard bricks are possible, so don't do anything hasty. There's an app in the Play store called phone info samsung by vndnguyen that helps with that. Install it and see what it says you have for bootloader and modem/baseband. Also check in Settings -> About and see what kernel version you have (the app might tell you that too, it has been a long time). Report that all back here and it will help with how to fix it.
Alternately if you don't want to mess with the app enter this in a terminal app or adb shell:
Code:
getprop ro.bootloader
getprop gsm.version.baseband
You won't find an Odin package for lollipop. Samsung never updated this device past kitkat. Anything lollipop or newer would be a custom rom, and those are all custom recovery flashable zips, not Odin.
jason2678 said:
Boot image not matching firmware on your phone can cause wifi to not work. The kernel doesn't have the what it needs to work with the radio you have installed. It is a fairly typical stock rom problem. Custom roms typically have broader support instead of being targeted at a specific firmware.
First step is to figure out what exactly you have on your phone now. Need to know bootloader, modem, and boot image versions since this phone is finicky. Hard bricks are possible, so don't do anything hasty. There's an app in the Play store called phone info samsung by vndnguyen that helps with that. Install it and see what it says you have for bootloader and modem/baseband. Also check in Settings -> About and see what kernel version you have (the app might tell you that too, it has been a long time). Report that all back here and it will help with how to fix it.
Alternately if you don't want to mess with the app enter this in a terminal app or adb shell:
Code:
getprop ro.bootloader
getprop gsm.version.baseband
You won't find an Odin package for lollipop. Samsung never updated this device past kitkat. Anything lollipop or newer would be a custom rom, and those are all custom recovery flashable zips, not Odin.
Click to expand...
Click to collapse
Thank You
jason2678 what you said makes perfect sense to me. like needing a VIN # for a 2002 Toyota to figure out what water pump or alternator because they used 6 different versions of each, LOL
so i would like to use 5.1 lollipop which is a custom ROM i believe, if you can suggest one i will defer to your judgement
but as a fallback suggest a kitkat ROM as well
bootloader I747UCUFNJ1
BASEBAND I747UCUFNJ1
KERNEL VERSION:
3.4.0-1514807
[email protected] #1
32-bit
modem msm8960
please and thank you
respectfully
123RobH
At NJ1 you're not on the latest bootloader and modem, but you're close enough. And your bootloader and modem match. I wouldn't mess with it. You'll be able to run all the latest custom ROMs on that, no problem.
If you want lollipop, look around the development section here. I'm not sure if you'll be able to track down a lollipop rom download linked to XDA. You might have to poke around old uploads for d2att on androidfilehost.com for 5.1.1 roms. I'm pretty partial to slimkat stable 9 on this phone, and it runs fine on NJ1 firmware too.
Oct-Os is probably the most actively supported rom currently. They've moved on to nougat these days. You'll be able to run it on NJ1 too. You might want to give it a shot.
Track down a rom and matching gapps. Then full wipe and flash them with TWRP recovery. If you run into any trouble or have any questions, just ask. I'm pretty certain once you get a custom rom on your phone your wifi problems will go away. Stick to lollipop, marshmallow, or nougat and you'll be fine. Even newer KitKat ROMs will be OK on NJ1.