Updated my unlocked rooted phone yesterday. Didnt realise it wouldnt root. Tries chainfires root and it goes through the motions but doesnt mount the internal SD card so no root.
Its very slow to wake up but otherwise seems ok. My problem is I really want root so if I cant would like to go back to my old firmware but have been told you cant go back.
Downloaded the superuser apk as advised in another post but it wont install from recovery as cannot see internal sd. Am stuck can anyone help please?
Use CF auto root, not the old version.
Or flash a rooted rom.
boomboomer said:
Use CF auto root, not the old version.
Or flash a rooted rom.
Click to expand...
Click to collapse
Yes it was the latest cf autoroot that I used. Would like to stay with this but root it or return to older firmware.
I dont really wish to flash a custom rom yet.
I meant a stock rom, but already rooted:
http://forum.xda-developers.com/showthread.php?t=1825272
boomboomer said:
I meant a stock rom, but already rooted:
http://forum.xda-developers.com/showthread.php?t=1825272
Click to expand...
Click to collapse
Thanks for that. Havent flashed a rom since Darky days! Would love to root this one though if I could first. Cant understand why it wont do it.
Am now back to a rooted 4.1.2. Normality restored.
Related
Hi all,
Excuse the noobness but trying to get my head straight before I dive into rooting and flashing custom ROMS
I currently have a Telstra Australia S2 on kernel DVKF4. My aim is to root and flash Litening ROM
I think to flash Litening ROM I do not have to Root I can just go ahead and flash it however I would like to take a backup of my current firmware first, if I go ahead an install Litening my original Telstra will be gone and wont be able to back it up now?
If I understand this correctly I first need to root and I need to flash an insecure ROM. Now currently the DVKF4 insecure ROM hasnt been uploaded yet... Can I use any old kernel to get root access?
I know if I do this I will get the yellow warning label but will this even matter since after I gain root I am going to flash litening anyway so that will replace the kernel anyway with the litening one and I will not get the yellow warning. Correct?
Anyhoo I wanted to backup current Telstra firmware in case I need to flash it back for warranty. Also I would have to unroot it. So in order to do this I would firstly restore the backup made which would flash back the original telstra ROM but the phone will still be rooted?
Since I made the backup with the 'any old' kernel to get root does that when I restore I am going to have that kernel still on phone and giving me yellow warning?
OK so I would have to flash back the correct DVKF4 kernel to get rid of it again. So I would have to flash back the original (secure) kernel to get rid of this and user superoneclick to unroot and then its back to its original state? (besides the download counter of unsigned ROMS which can be reset with jig)
Also does the yellow warning come up even if you use an insecure kernel which is the same version your firmware needs?
I thought it's the kernel which gives the root access but it's not is it? It just allows superoneclick to install the superuser files etc?
Thanks!
icanfly77 said:
Hi all,
Excuse the noobness but trying to get my head straight before I dive into rooting and flashing custom ROMS
I currently have a Telstra Australia S2 on kernel DVKF4. My aim is to root and flash Litening ROM
I think to flash Litening ROM I do not have to Root I can just go ahead and flash it however I would like to take a backup of my current firmware first, if I go ahead an install Litening my original Telstra will be gone and wont be able to back it up now?
True but you may find copy on Branded roms post dev section or use vanilla Samsung stock rom .
If I understand this correctly I first need to root and I need to flash an insecure ROM. Now currently the DVKF4 insecure ROM hasnt been uploaded yet... Can I use any old kernel to get root access?
Depends upon what the instructions say but generally as near to possible as your rom .
I know if I do this I will get the yellow warning label but will this even matter since after I gain root I am going to flash litening anyway so that will replace the kernel anyway with the litening one and I will not get the yellow warning. Correct?
Incorrect you will need the USB recovery jig to remove the warning and reset the custom rom counter to zero the easy way .
Anyhoo I wanted to backup current Telstra firmware in case I need to flash it back for warranty. Also I would have to unroot it. So in order to do this I would firstly restore the backup made which would flash back the original telstra ROM but the phone will still be rooted?
A backup via CWM of a phone will restore what you backup .
To restore unrooted you will need to save unrooted in the first instance .
Original rom or branded rom flashed via Odin will remove root .
I thought it's the kernel which gives the root access
Yes if you use the usual method no if you use another method .
Root & CWM kernel.
http://forum.xda-developers.com/showthread.php?t=1103399
jje
Click to expand...
Click to collapse
JJEgan said:
icanfly77 said:
A backup via CWM of a phone will restore what you backup .
To restore unrooted you will need to save unrooted in the first instance .
Click to expand...
Click to collapse
Hey thanks but how do I make a backup of the unrooted current carrier ROM? Don't I first need to gain root access to be able to run CWM and make the backup?
Or is there a way I can go into recovery now with the device currently unrooted and stock carrier ROM and make a backup?
Thanks
Click to expand...
Click to collapse
icanfly77 said:
Hey thanks but how do I make a backup of the unrooted current carrier ROM? Don't I first need to gain root access to be able to run CWM and make the backup?
Click to expand...
Click to collapse
As was pointed out above by JJEgan, either wait for the Telstra carrier branded firmware to hit this thread.
Or you can try the root/unroot method as described here. Good luck
mrxd said:
As was pointed out above by JJEgan, either wait for the Telstra carrier branded firmware to hit this thread.
Or you can try the root/unroot method as described here. Good luck
Click to expand...
Click to collapse
yeah thanks I get that part it's just that he mentioned if I want back a backup of an unrooted rom I need to make the backup while unrooted but I did not think this was possible since you need to root first before being able to backup?
Just after some clarification about that.. Thanks
GT-I9300 International No carrier
Current FW v 4.1.2
hxxp://i.imgur.com/DxDXONZ.png
Update Details
hxxp://i.imgur.com/18JE68Z.jpg
Phone Rooted using CF-Auto-Root
SuperSU and Busybox installed
CWM not installed
Using Stock ROM
Using Stock Kernel
As you can see Kies has prompted me an update and the update seems to have already downloaded OTA using WiFi.
It is prompting me to install the update again and again.
My question is, if I do select to install this update,
1.) Will it remove root?
2.) Will it completely wipe my phone? (previous incremental updates haven't wiped my data, but the phone wasn't rooted then.)
3.) Can I root again using CF-Auto-Root?
Thank you.
Jaxx89 said:
GT-I9300 International No carrier
Current FW v 4.1.2
hxxp://i.imgur.com/DxDXONZ.png
Update Details
hxxp://i.imgur.com/18JE68Z.jpg
Phone Rooted using CF-Auto-Root
SuperSU and Busybox installed
CWM not installed
Using Stock ROM
Using Stock Kernel
As you can see Kies has prompted me an update and the update seems to have already downloaded OTA using WiFi.
It is prompting me to install the update again and again.
My question is, if I do select to install this update,
1.) Will it remove root?
AS per thousands of posts YES.
2.) Will it completely wipe my phone? (previous incremental updates haven't wiped my data, but the phone wasn't rooted then.)
NO
3.) Can I root again using CF-Auto-Root?
YES
All this is posted multiple times .
jje
Click to expand...
Click to collapse
JJEgan said:
Jaxx89 said:
GT-I9300 International No carrier
Current FW v 4.1.2
hxxp://i.imgur.com/DxDXONZ.png
Update Details
hxxp://i.imgur.com/18JE68Z.jpg
Phone Rooted using CF-Auto-Root
SuperSU and Busybox installed
CWM not installed
Using Stock ROM
Using Stock Kernel
As you can see Kies has prompted me an update and the update seems to have already downloaded OTA using WiFi.
It is prompting me to install the update again and again.
My question is, if I do select to install this update,
1.) Will it remove root?
AS per thousands of posts YES.
2.) Will it completely wipe my phone? (previous incremental updates haven't wiped my data, but the phone wasn't rooted then.)
NO
3.) Can I root again using CF-Auto-Root?
YES
All this is posted multiple times .
jje
Click to expand...
Click to collapse
Sorry about that. Maybe my searching skills aren't good enough or maybe I don't know how to use this forum coz I found only one thread that too with a Gingerbread FW, which is why I posted this Q
Really sorry.
Thanks for the quick reply.
Click to expand...
Click to collapse
Device status modified and cannot update
tried using triangle away and did not reset the flash counter
Because triangle away can reset your flash counter only if you're running stock recovery, stock kernel, stock rom etc.
CF-AutoRoot should not make your status "modified" but probably like you see it did. Maybe some other apps did that, maybe not, nobody knows anyway. If you really need these updates then you should flash newest firmware from samsung through odin and then root it + reset flash counter, it should work also for further updates (but I'm not sure).
JustArchi said:
Because triangle away can reset your flash counter only if you're running stock recovery, stock kernel, stock rom etc.
CF-AutoRoot should not make your status "modified" but probably like you see it did. Maybe some other apps did that, maybe not, nobody knows anyway. If you really need these updates then you should flash newest firmware from samsung through odin and then root it + reset flash counter, it should work also for further updates (but I'm not sure).
Click to expand...
Click to collapse
Thanks a lot.
I know where to get the FW updates to flash via Odin but don't really understand how to reset the flash counter if not by using TriangleAway.
Could you please be kind enough to guide me?
And these are the apps I used after root
SuperSU
Busybox
Root checker
Titanium Backup
Lucky patcher
Market enabler
Greenify
Could any of these apps modify the stock kernel, rom or recovery? Coz I never flashed any custom ones just rooted using CF-Auto-Root and installed the root apps
P.S: I was able to do the FW update via Kies and now the status is back to normal, but I'm afraid to root coz the status might go back to modified.
It's more like, you know. If we're talking about warranty then they'll find that your rooted your phone anyway. If we're talking about updates then probably it's still better to keep an eye on some stock-based custom roms, mostly because of frequent updates (nearly instantly after new baseband), while you still need to wait some time for OTA to arrive. Of course it's much easier to apply OTA than whole custom rom but hey, how often are you doing that?
About your question - busybox is my choice because it modifies /system apps, many of them.
And lastly - in odin you have a checkbox to reset flash counter, so you don't need to worry about anything using this tool. At least in general.
Overall I'd stick with pure stock non-rooted firmware if you don't need it in general or rooted custom rom (f.e. mine ) for much better experience. I couldn't go back to stock after getting used to much better performance, less battery drain etc.
Choice is yours.
Lucky patcher
Warez is totally banned on XDA you are stealing from developers .
As its a warez app who knows what sort of malware it could add to your phone .
I would wipe the phone install original firmware .
http://forum.xda-developers.com/showthread.php?t=1978840
Then update it and to stick with unrooted stock .
jje
JustArchi said:
It's more like, you know. If we're talking about warranty then they'll find that your rooted your phone anyway. If we're talking about updates then probably it's still better to keep an eye on some stock-based custom roms, mostly because of frequent updates (nearly instantly after new baseband), while you still need to wait some time for OTA to arrive. Of course it's much easier to apply OTA than whole custom rom but hey, how often are you doing that?
About your question - busybox is my choice because it modifies /system apps, many of them.
And lastly - in odin you have a checkbox to reset flash counter, so you don't need to worry about anything using this tool. At least in general.
Overall I'd stick with pure stock non-rooted firmware if you don't need it in general or rooted custom rom (f.e. mine ) for much better experience. I couldn't go back to stock after getting used to much better performance, less battery drain etc.
Choice is yours.
Click to expand...
Click to collapse
Thanks for the quick response
I rooted mainly coz I needed to use market enabler
In Odin are you referring to the option F. Reset time??
I am using the Odin version provided by Chainfire in his S3 rooting thread in which all options are disabled except for Auto reboot.
@JJEgan I don't even know how to use half of the apps I mentioned, I only installed them as my friend suggested it as must have root apps.
As you might see, I am still a N00b at this and am in the learning process.
BTW Thanks for the link to the guide.
Jaxx89 said:
Thanks for the quick response
I rooted mainly coz I needed to use market enabler
In Odin are you referring to the option F. Reset time??
I am using the Odin version provided by Chainfire in his S3 rooting thread in which all options are disabled except for Auto reboot.
@JJEgan I don't even know how to use half of the apps I mentioned, I only installed them as my friend suggested it as must have root apps.
As you might see, I am still a N00b at this and am in the learning process.
Click to expand...
Click to collapse
I suggest going through my flashing guide located in ArchiDroid thread, with newest odin and newest methods for flashing/rooting.
JustArchi said:
I suggest going through my flashing guide located in ArchiDroid thread, with newest odin and newest methods for flashing/rooting.
Click to expand...
Click to collapse
Thanks a lot.
If I'm not mistaken, ArchiDroid is a Custom ROM(pre-rooted) which requires a Custom Recovery.
I will be learning a bit more first before I install a Custom ROM.
A question though. Will I have to take a backup of my app data if I decide to install a custom ROM?
Also if I want to install the stock FW via Odin, will I have to take a backup first?
Thanks and I'm really sorry about asking such questions.
Jaxx89 said:
Thanks a lot.
If I'm not mistaken, ArchiDroid is a Custom ROM(pre-rooted) which requires a Custom Recovery.
I will be learning a bit more first before I install a Custom ROM.
A question though. Will I have to take a backup of my app data if I decide to install a custom ROM?
Also if I want to install the stock FW via Odin, will I have to take a backup first?
Thanks and I'm really sorry about asking such questions.
Click to expand...
Click to collapse
Yes it requires custom recovery for installing .zip package.
There is nothing to learn if you ask me, you have complete guide for installing everything you need in step-by-step howto. If you want to keep your data then you need to use some nice app for that f.e. Titanium Backup but for that you need root and... yeah. It's easier to start from scratch on new pre-rooted rom.
I'd suggest flashing custom recovery (tutorial in my topic) and then you can create a backup directly from that, with everything you want to, including actual system, efs folder, recovery, kernel etc. So you can easily get back to original rom whenever you want to. Keep in mind that you still need custom recovery for that.
JustArchi said:
Yes it requires custom recovery for installing .zip package.
There is nothing to learn if you ask me, you have complete guide for installing everything you need in step-by-step howto. If you want to keep your data then you need to use some nice app for that f.e. Titanium Backup but for that you need root and... yeah. It's easier to start from scratch on new pre-rooted rom.
I'd suggest flashing custom recovery (tutorial in my topic) and then you can create a backup directly from that, with everything you want to, including actual system, efs folder, recovery, kernel etc. So you can easily get back to original rom whenever you want to. Keep in mind that you still need custom recovery for that.
Click to expand...
Click to collapse
Ok Now I'm really confused
I still haven't learnt how to use Titanium Backup to backup, or how to do a nandroid backup. I have read it's better to do a backup b4 installing a custom ROM. And if I'm not mistaken, I need ROOT to do a nandroid backup too.
As I said before that I used CF-Auto-Root, I just followed the instructions to the word.
I had tried doing a ADB backup before root, but for some reason it kept exiting(I guess coz I have just about 1GB memory left on my Internal memory SD card)
Thanks for the quick reply. Man ur really fast in answering questions. :good:
EDIT: Just did the CF-Auto_Root again and didn't install any other apps like busybox(uninstalled all root apps) and used triangleaway to reset the flash counter. But the counter still stuck on 1
The device status shows normal though.
Jaxx89 said:
Ok Now I'm really confused
I still haven't learnt how to use Titanium Backup to backup, or how to do a nandroid backup. I have read it's better to do a backup b4 installing a custom ROM. And if I'm not mistaken, I need ROOT to do a nandroid backup too.
As I said before that I used CF-Auto-Root, I just followed the instructions to the word.
I had tried doing a ADB backup before root, but for some reason it kept exiting(I guess coz I have just about 1GB memory left on my Internal memory SD card)
Thanks for the quick reply. Man ur really fast in answering questions. :good:
Click to expand...
Click to collapse
First of all you need custom recovery to perform nandroid backups. So you can stick with my first 10 steps in my howto. After that enter recovery, enter backup section and make a custom backup (or default, doesn't matter) of everything you have, especially /efs folder as it's really important. When you finish doing backup then boot to your normal system and copy these backups to your PC. Now you're sure that they won't disappear and if you want to backup your phone from that then simply put them back on your phone and restore them from the recovery.
But overall I'd suggest clean start without these backups. Of course it's always recommended and I recommend it as well but as long as you won't want to go back to original rom, there is no real point for backing it up. You can always download latest official firmware and flash it through odin.
Hi there, I'm not so experienced so far but I'd like to root my Galaxy S3 All stock with 4.3 build, I9300XXUGMK6 (unbranded italian). So far I understood that as long as I only want to run some root apps, I can use cf auto root and mantain all stock, 'cause it will reinstall stock recovery. Then I want to know if triangle away works on 4.3 (recently has been updated to 3.26).
After that will I be able to get OTA, as long as the system files are stock and the only difference is the root and some root apps? Can someone confirm this? Thanks everyone.
Yes to CF auto root, yes to triangle away, no to ota -it won't update if you have modified your phone.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Yes to CF auto root, yes to triangle away, no to ota -it won't update if you have modified your phone.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Are you sure? There's much confusion in this forum about ota with root, some say that it is possible to get it, if the reovery and the rom are full stock, only there's the possibility to lose root... In fact, there is an option, in SuperSU, which allows to mantain root even after OTA, so I guess it's posible to get it... Am I wrong?
Sure lets put it this way 99% of posts that have OTA problems are rooted and the install fails .
Via the method you post just going to have to try it as i have only seen one claiming it works .
But as i don't have OTA i cannot test .
JJEgan said:
Sure lets put it this way 99% of posts that have OTA problems are rooted and the install fails .
Via the method you post just going to have to try it as i have only seen one claiming it works .
But as i don't have OTA i cannot test .
Click to expand...
Click to collapse
Thank you for the answer. So assuming Ota not possible, after reset flash counter with triangle away if I want to download it or to claim warranty back I'll only have to flash a stock firmware with odin and it's done? Right?
The first step for flashing Alliance was making sure i have the 4.3 firmware. Flashed via Odin.
I experfienced some trouble with a bootloop issue so i changed cables and then partitioned with the .pit file.
All's well now, it at least runs the stock firmware just fine. Now i'm strugglling with the most basic simple part IMO... how do i install the custom Rom without the recovery??
sduffy89 said:
The first step for flashing Alliance was making sure i have the 4.3 firmware. Flashed via Odin.
I experfienced some trouble with a bootloop issue so i changed cables and then partitioned with the .pit file.
All's well now, it at least runs the stock firmware just fine. Now i'm strugglling with the most basic simple part IMO... how do i install the custom Rom without the recovery??
Click to expand...
Click to collapse
You are rooted still correct? Easiest way I guess is to just download Rom Manager or GooManager depending on using TWRP or CWM.
KuNiT said:
You are rooted still correct? Easiest way I guess is to just download Rom Manager or GooManager depending on using TWRP or CWM.
Click to expand...
Click to collapse
I chose to bump up my android version cuz i friend another SIM card. I tether for my Hulu, Netflix, Amazon Prime, and whatever else, thankfully my laptop can get weak unsecured internet signals, but i'm walking my Note around the apartment trying to get good 1x reception Problems may be overlapping but next step is something basic from the Play Store to verify root.
I read of some luck with root for 4.3, just not bootloader. Am i correct?
KuNiT said:
You are rooted still correct? Easiest way I guess is to just download Rom Manager or GooManager depending on using TWRP or CWM.
Click to expand...
Click to collapse
Not rooted. it sounds like rooting is still an option, just not custom recovery?
Is using ODIN to flash stock rooted an option? No valuable files on phone currently.
(Fortunately I'm at work right now so I have time to make well informed decisions. Thanks for your help)
sduffy89 said:
Not rooted. it sounds like rooting is still an option, just not custom recovery?
Is using ODIN to flash stock rooted an option? No valuable files on phone currently.
(Fortunately I'm at work right now so I have time to make well informed decisions. Thanks for your help)
Click to expand...
Click to collapse
I believe if you took/flashed the OTA update, your kinda out of luck and stuck now. I'm not 100% certain of this though but I think it probably relocked the bootloader and the only thing to do is wait for someone to root/unlock 4.3.
KuNiT said:
I believe if you took/flashed the OTA update, your kinda out of luck and stuck now. I'm not 100% certain of this though but I think it probably relocked the bootloader and the only thing to do is wait for someone to root/unlock 4.3.
Click to expand...
Click to collapse
Correct. If you took the OTA it relocked your bootloader and you are stuck. You can still root the official 4.3 but you are stuck waiting until someone unlocks the bootloader. This means no custom ROMs/Recovery.
Which 4.3 firmware did you flash? If its the OTA then yes you're outta luck.
If you did follow the Alliance's rom thread. There is a 4.3 MJ9 firmware you need to flash. It doesn't have the locked bootloader. You are then able to boot up in the basic recovery and then flash either TWRP or CWM recovery.
Hi folks,
Ive been having a strange problem with a couple Galaxy Mega I9200. I have rooted both before without any problems using KINGO originally. The i decided to update both of them with version UBUCNA2. When i tried to re root them back, even though the process have run fine a couple times the phone is not rooting. At this point i dont know what else to do to try to root those phones. I have tried every single method around this forum i think not just KINGO this time. And have not been able to reach root the way it should. Titanium backup shows not able to aquire root priviledges, and other root apps also. Can someone please help me on this?? Keep in mind im not a newbie so dont give me the recovery method advice without something new or to use KINGO because ive have done that already. Thanks a lot guys
You upgraded your phones to the latest knox enabled firmware which has the knox bootloader. You cannot go back to an older firmware or flash a custom rom now.
To root, try the directions provided in this thread and use the melius3gxx files instead of meliusltexx.
Silesh.Nair said:
You upgraded your phones to the latest knox enabled firmware which has the knox bootloader. You cannot go back to an older firmware or flash a custom rom now.
To root, try the directions provided in this thread and use the melius3gxx files instead of meliusltexx.
Click to expand...
Click to collapse
Ok thanks, the phones already had the knox apk so my guess was that it was going to be the same thing. Thanks for clarifying that one. And thanks for the advice.
Thanks again, turns out the only thing that is failling root access is when i try to unlock the phone via box. For some reason when its checking for SU access it fails. But thanks anyway i managed to solve the Root problem.
root.
I rooted through Phill touch Recovery.