Okay, as a newby poster on this forum, I can ask this question here, hopefully someone reads here that can help *smile*.
I've followed the rooting guide for my post JB OTA updated Galaxy S3. My phone is now apparently rooted, I can grant root access to apps and all. I should have a custom recovery installed as well (I chose TWRP since a lot of people seem to choose CWM, and I'm a rebel without a cause), but I'm not sure, since when I booted out of recovery after installing the SU app, I didn't see the "Disable recovery flash" prompt. And I haven't tried to boot into recovery mode yet to verify whether the TWRP version that I installed is still there. Doesn't seem to have affected the resulting root access ability one way or the other, though.
My question is that when I boot my phone normally now, I see an unlocked lock icon, and "CUSTOM". Since I re-flashed the stock boot when I was done, this is a bit disturbing, I didn't expect that. I've read that if I have a custom recovery that I'll see this even if I have stock boot. Is this true? I think that stock boot is a good idea, but am not convinced that I have it. Is there any way to tell if I have a stock boot or not?
A little puzzled, although I definitely like the rooted phone better than the non-rooted one, so thanks much for that.
Just rebooted the phone into TWRP recovery a couple of times this morning, so I guess that I still have the custom recovery installed *smile*. And I'm also assuming that flashing the stock boot at the end of rooting worked, despite the unlocked lock icon and "CUSTOM" when I boot my phone now.
I guess there's no need for a reply here, since I've answered at least part of my own questions. I'm assuming then that I'm seeing "CUSTOM" and the unlocked lock icon when I boot because I have the custom recovery installed, and when I un-root it will go away. I've already set my flash count back to 0, since I wanted to remember to do that while I still had root, in case I un-root to send the phone to Samsung, and forget to do that.
Again, thanks for the guide thread on rooting, very helpful. The only first-time snag was booting into TWRP from Odin mode so I could install the SU app. Eventually figured out how to do that, so when/if I do this again should be much quicker.
Related
I own a t-mobile g2x that is rooted and has been flashed multiple times. However, rooting and flashing on that device is extremely different than the GS3. My buddy owns a verizon GS3 and has an unlocked boot loader (an unlocked lock appears under "samsung" logo at boot). Does this mean that it is rooted? I was able to install titanium backup and ROM manager and flash CWM 5.x.x.x on it without any problems so I am assuming it is rooted. However, he is having trouble downloading anything from the internet. For some reason anytime he attempts to download something on his phone an error shows up saying "download failed." Any idea why this is happening? Also, there are a few ROMS in the dev section that he's interested in flashing. I'm not very knowledgeable about this device....but if it has an unlocked boot loader and is rooted, is he all set to flash a custom ROM?
Pain-N-Panic said:
I own a t-mobile g2x that is rooted and has been flashed multiple times. However, rooting and flashing on that device is extremely different than the GS3. My buddy owns a verizon GS3 and has an unlocked boot loader (an unlocked lock appears under "samsung" logo at boot). Does this mean that it is rooted? I was able to install titanium backup and ROM manager and flash CWM 5.x.x.x on it without any problems so I am assuming it is rooted. However, he is having trouble downloading anything from the internet. For some reason anytime he attempts to download something on his phone an error shows up saying "download failed." Any idea why this is happening? Also, there are a few ROMS in the dev section that he's interested in flashing. I'm not very knowledgeable about this device....but if it has an unlocked boot loader and is rooted, is he all set to flash a custom ROM?
Click to expand...
Click to collapse
The unlocked lock means that the bootloader is locked but a custom recovery is installed. Make sure he used the 1.2 version of ez unlock.
If you flash a custom rom without it being unlocked you'll have to Odin back to stock. Anyways, he should be exactly sure what he's doing and how he'd go about fixing it if something does go wrong. There are many guides that are stickied that should help him recover from any situation.
Before flashing anything, I'd make an IMEI backup since the guide to fix it has been pulled.
The download error usually happens with either a weak Internet connection or it eventually timing out. He's most likely trying to download large files. Make sure he downloads under a strong wifi or 4g connection.
Sent from my SCH-I535 using Tapatalk 2
Gotcha. Appreciate the help in the right direction. Ill go through the stickies when i have some time.
-custom sig.
Hi,
I would like to root my phone mantaining the stock recovery, and booting temporarily a custom recovery
If i execute a "fastboot boot customrecovery.img" and then i install from zip the "UPDATE-SuperSU-v1.69.zip" for example, I know that i will have a rooted phone with stock recovery.(right?)
I would like to do this in order to receive OTA without manual installation (i'm right?), thing that i have already done on my "old " Galaxy Nexus and now i would like to avoid doing it on the N5. I know that, in a case like this, i will lose root and then i have to do the process again.
The question is: There's just some contraindication doing this?
Thank you very much. I already tryed to find an exaustive answer searching the forum.
PS. Sorry for my poor English
Chainfire has the solution for you. Root and keep everything else stock.
http://forum.xda-developers.com/showthread.php?t=2507211
You will have to unlock your bootloader if you haven't already done so.
DreamLinker said:
Hi,
I would like to root my phone mantaining the stock recovery, and booting temporarily a custom recovery
If i execute a "fastboot boot customrecovery.img" and then i install from zip the "UPDATE-SuperSU-v1.69.zip" for example, I know that i will have a rooted phone with stock recovery.(right?)
I would like to do this in order to receive OTA without manual installation (i'm right?), thing that i have already done on my "old " Galaxy Nexus and now i would like to avoid doing it on the N5. I know that, in a case like this, i will lose root and then i have to do the process again.
The question is: There's just some contraindication doing this?
Thank you very much. I already tryed to find an exaustive answer searching the forum.
PS. Sorry for my poor English
Click to expand...
Click to collapse
Your method of booting a recovery image will work fine. That's the way I would do it.
Thanks you all very much!
So, I just got the phone and I've unlocked the bootloader with instructions from another site because none were here in a sticky as most phone sections on here have, and how to root and install recovery isn't on here either (This isn't a criticism or shot at this section, I know this is a new phone and these things take time). Though I know how to do most of this from years of doing it, I do not want to flash a custom recovery permanently just yet, but I do want to root. A lot of phones have toolkits or something that will allow you to boot into TWRP temporarily to root, but I don't seen anything available for this phone yet to do this. Does anyone know if this exist, and if not when it may? Once again, I know this is a new phone and development will pick up over time, just curious.
fastboot boot twrp.img
Temporary recovery possible
Use this. instructions are given in that post. I have tried temporary as well as permanent. Both works good.
Alright, where do I start?
So I'm not really and expert on flashing stuff on Android. I was pretty comfy not rooting my phone for more than a year. TBH, I didn't really need it, because I was not a power user, but I've recently installed a root app called King User (King Root, etc.). Before you say anything... YES! I know it is the lazy way to do it. It made things easy for the very few apps I could not use without root permission. However, when I received the latest OTA (5.1.1. security update) I had to disable root authorization in order to install it. So I disabled it using the app's built in authorization setting.
The OTA update failed and gave me the error with the opened up android and the red exclamation mark. So I thought that the app messed something up. Disabling in house did nothing. Uninstalling it did nothing. So I decided to replace it with SuperSU using this guide: http://forum.xda-developers.com/general/help/replace-kinguser-supersu-t2903003. I bet I'm not the only one who had problems after doing this. This, obviously, made things even worse. After SuperSU deleted KingUser and updated itself the phone remained stuck inside a bootloop. So I figured this replacement process messed up permissions.
Here is where it gets tricky, or rather stupid... My bootloader is locked and I have no custom recovery (because like I said, I just needed temporary root access for a couple of apps and wanted to avoid the hassle). When I enter Recovery mode in default fastboot it gives me the "No command" error (probably because of SuperSU permission). Now I don't even know if the phone is rooted or not. USB debugging was not enabled last time the phone was on and now I think I'm stuck in this point where nothing works without something else. I've been reading a couple of threads around here and elsewhere and I don't know what to do next... Doing a full recovery now would probably be asking for a lot, but right now, I would be happy if I could just do a factory reset or something...
Anyone?
val3nteen said:
Alright, where do I start?
So I'm not really and expert on flashing stuff on Android. I was pretty comfy not rooting my phone for more than a year. TBH, I didn't really need it, because I was not a power user, but I've recently installed a root app called King User (King Root, etc.). Before you say anything... YES! I know it is the lazy way to do it. It made things easy for the very few apps I could not use without root permission. However, when I received the latest OTA (5.1.1. security update) I had to disable root authorization in order to install it. So I disabled it using the app's built in authorization setting.
The OTA update failed and gave me the error with the opened up android and the red exclamation mark. So I thought that the app messed something up. Disabling in house did nothing. Uninstalling it did nothing. So I decided to replace it with SuperSU using this guide: http://forum.xda-developers.com/general/help/replace-kinguser-supersu-t2903003. I bet I'm not the only one who had problems after doing this. This, obviously, made things even worse. After SuperSU deleted KingUser and updated itself the phone remained stuck inside a bootloop. So I figured this replacement process messed up permissions.
Here is where it gets tricky, or rather stupid... My bootloader is locked and I have no custom recovery (because like I said, I just needed temporary root access for a couple of apps and wanted to avoid the hassle). When I enter Recovery mode in default fastboot it gives me the "No command" error (probably because of SuperSU permission). Now I don't even know if the phone is rooted or not. USB debugging was not enabled last time the phone was on and now I think I'm stuck in this point where nothing works without something else. I've been reading a couple of threads around here and elsewhere and I don't know what to do next... Doing a full recovery now would probably be asking for a lot, but right now, I would be happy if I could just do a factory reset or something...
Anyone?
Click to expand...
Click to collapse
Start here, http://forum.xda-developers.com/showthread.php?p=53439068. I'd return to stock and start all over, it will wipe your device, see the return to stock thread linked there. Then don't be lazy and read some more in the thread I linked you to. The n5 is one of the easiest devices to work with and you don't need kingroot, tool kits and junk like that
Sent from my Nexus 5 using XDA Free mobile app
You should flash TWRP custom recovery on your phone that way you can copy your personal data to your pc first, then you should flash the factory image
deelan_chan said:
You should flash TWRP custom recovery on your phone that way you can copy your personal data to your pc first, then you should flash the factory image
Click to expand...
Click to collapse
Thanks, but that is not possible, as I have not enabled USB debugging before bootloop. I need to unlock the bootloader (wipe) to install TWRP and backup data.
Can you get into fastboot mode? You can flash twrp from there no USB debugging needed
Sent from my Nexus 5 using Tapatalk
Problem is his bootloader is locked, so follow fastboot for unlocking bootloader and then clean install latest factory image. Also, flash twrp after everything is working (and relock bootloader if you want) so this does not happen again.
wangdaning said:
Problem is his bootloader is locked, so follow fastboot for unlocking bootloader and then clean install latest factory image. Also, flash twrp after everything is working (and relock bootloader if you want) so this does not happen again.
Click to expand...
Click to collapse
Did just that. All fine now. However, I had to flash all .img files separately in fastboot (system, boot, cache, etc.), because adb was not working. Had some problems with the drivers. The device did not show up correctly within device manager. Fortunately, I did not loose anything. Had all my contacts and apps backed up with Google.
Thanks for all advice! I appreciate everyone's guidance.
val3nteen said:
Did just that. All fine now. However, I had to flash all .img files separately in fastboot (system, boot, cache, etc.), because adb was not working. Had some problems with the drivers. The device did not show up correctly within device manager. Fortunately, I did not loose anything. Had all my contacts and apps backed up with Google.
Thanks for all advice! I appreciate everyone's guidance.
Click to expand...
Click to collapse
But it is so fun to use fastboot. I remember almost dunking my wife's G2 until I got it to fastboot. Pain in the butt, but the command prompt does not lie
So, I finally got my phone (SM-J320FN) rooted, thanks to info and downloads on this forum.
But now I have some questions, to which I haven't found the answers to anywhere else on the web.
1. To root, I followed instructions that told me to switch-on OEM unlock and USB debugging. However, there was no mention about turning them off again after root. Should they be on, or off?
2. Part of my rooting process involved installing/flashing TWRP. I did read that TWRP can be removed after root. What are the advantages/disadvantages of leaving or removing?
3. Now my phone is rooted, what is the best app/way to prevent it becoming unrooted by updates?
That's all for now, thanks.
SGJ3 said:
So, I finally got my phone (SM-J320FN) rooted, thanks to info and downloads on this forum.
But now I have some questions, to which I haven't found the answers to anywhere else on the web.
1. To root, I followed instructions that told me to switch-on OEM unlock and USB debugging. However, there was no mention about turning them off again after root. Should they be on, or off?
2. Part of my rooting process involved installing/flashing TWRP. I did read that TWRP can be removed after root. What are the advantages/disadvantages of leaving or removing?
3. Now my phone is rooted, what is the best app/way to prevent it becoming unrooted by updates?
That's all for now, thanks.
Click to expand...
Click to collapse
It's better to let them on.
You can remove the TWRP recovery by flashing stock recovery. But TWRP can backup your whole android partitions (nandroid backup) that can restore your android if anything goes wrong.
TWRP can flash custom roms, mods, mount partitions, and many more. So, it's better to you have TWRP(custom recovery) installed.
If you are using SuperSU superuser app then in option you found OTA survival that prevent root from OTA updates.
I think you can't get OTA updates because you are rooted. If you get OTA updates and applied on rooted android then it chances of brick your android.
Hi every one. First sorry for bad grammar I am not so good at english. Now to the problem at hand.
Jester day I bought a smj320fn and realise it is not what I paid for, so I tried to root witk KingoRoot and fail. Then I realised there is a "bootlock" witch prevents root (I think it does that).
So I tried ODIN and installed a custom FMW and it worked, allso I instaled a custom twrp and boot win.rar file. and there is the problem.
Every time I hold the power buton the samsung logo apears for 5 seconds and then goes black. It wont take any commands. I tride the recover meny to open, no it wont, but I can restars it to boot again and fails every time.
I tried to do it from a youtube tutorial and maby I know what I did wrong. I Instaled a Sm-j320h boot on my smj320fn so I think thats the problem. Any whay how do I fix this. All and any solution are good.