I would like just to root the device not ready to unlock bootloader via Htc-Dev ok with stock recovery for time being just need simple root method I am fine atm on stock rom seems to be alot of threads on rooting unlocking and recovery just looking for someone to point me in right direction that is also running stock rooted So what is the best method?
Unlocking the bootloader.
Sent from my HTC VLE_U using xda premium
jmcdonald58 said:
I would like just to root the device not ready to unlock bootloader via Htc-Dev ok with stock recovery for time being just need simple root method I am fine atm on stock rom seems to be alot of threads on rooting unlocking and recovery just looking for someone to point me in right direction that is also running stock rooted So what is the best method?
Click to expand...
Click to collapse
You can't do much without unlocking bootloader (HTC-Dev). Maybe we can later down the road, but not right now.
If you don't care about bootloader unlock (tamper). Just root and flash recovery. Freeze/unistall all your bloatware.
Thanks,I guess I will hold off for another method of unlocking bl
Sent from my Galaxy Nexus using xda premium
Related
Hey
I unlocked the boatloader, which wiped the phone, and rooted it when I first got it.
I got the new update recently and just found out I lost root. Is there a way to get root back without wiping the phone? I still have the unlocked bootloader since I have the little lock on the boot screen.
I read the guides, but they all seem to also do the fastboot thing that unlocks the bootloader or installs a new ROM. I just want to keep my phone the way it is (stock) and root it. I'm just really confused about how to do it.
Thanks!
Mount USB while in Android
Copy su.zip
Boot into cwm recovery
Install su.zip from sdcard
Done
Sent from my Nexus S using XDA App
I don't have unlocked anything. I'd like a rooted phone without having to wipe anything. Is it possible?
If the bootloader isn't unlocked then doing so will wipe.
If it's unlocked installing su and recovery as I described will wipe nothing.
Sent from my Nexus S using XDA App
Ok. And I suppose you cannot root a phone without unlocking the bootloader first?
athani said:
Ok. And I suppose you cannot root a phone without unlocking the bootloader first?
Click to expand...
Click to collapse
Not anymore. Need an unlocked bootloader to root now.
Sent from my Nexus S using XDA App
i rooted my s3, then i unlocked the bootloader. i still havent flashed anything but now when i reboot my phone i get the custom notification with the unlocked padlock. did i do something wrong or is this normal.
edit: i used a windows based program to root and i used twrp to flash the unlocked bootloader
I am waiting on a stable completely functioning rom before flashing.
krbernier said:
i rooted my s3, then i unlocked the bootloader. i still havent flashed anything but now when i reboot my phone i get the custom notification with the unlocked padlock. did i do something wrong or is this normal.
edit: i used a windows based program to root and i used twrp to flash the unlocked bootloader
I am waiting on a stable completely functioning rom before flashing.
Click to expand...
Click to collapse
Sounds like it's not unlocked if you still have the custom boot screen. What method did you use to unlock?
You are not unlocked. When your bootloader is unlocked that Samsung screen just flies by. No padlock no waiting.
Sent from my SCH-I535 using Tapatalk 2
Thanks! i used a windows batch file to do the unlock...guess ill give it another go.
worked thanks!
My SGiii now does this when booting. I have root. I used the devFS root method. I to my knowledge I have not flashed the boot loader. Is this what people were talking about by adding one to there flash counter? If so I might as well flash cwm.
Is my warranty void now?
Sent from my SCH-I535 using xda app-developers app
Xiuix said:
My SGiii now does this when booting. I have root. I used the devFS root method. I to my knowledge I have not flashed the boot loader. Is this what people were talking about by adding one to there flash counter? If so I might as well flash cwm.
Is my warranty void now?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Has nothing to do with flash counter. It shows that software is modified and is caused by root. Unlocking the bootloader will get rid of lock. Warranty is void only if you don't revert to stock before return.
Hello guys I just got may galaxy S3 from a friend. I think the bootloader is still unlocked after I received an OTA today. I don't have root or recovery. I just want to be sure I use the correct root and recovery method. Could someone point me to the one they used on this build with success? I would be greatly appreciated. I did look but none are specific enough for me to be sure I'm using the correct one.
Is my bootloader still unlocked if it says (custom)?
Again I appreciate any help
Sent from my SCH-I535 using xda premium
mike216 said:
Hello guys I just got may galaxy S3 from a friend. I think the bootloader is still unlocked after I received an OTA today. I don't have root or recovery. I just want to be sure I use the correct root and recovery method. Could someone point me to the one they used on this build with success? I would be greatly appreciated. I did look but none are specific enough for me to be sure I'm using the correct one.
Is my bootloader still unlocked if it says (custom)?
Again I appreciate any help
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Welcome! In order to unlock your BL in the first place you must have had root. This is a good thread on rooting, unlocking, and flashing recovery/ROMs/kernels:
http://forum.xda-developers.com/showthread.php?t=1762709
nghtrain88 said:
Welcome! In order to unlock your BL in the first place you must have had root. This is a good thread on rooting, unlocking, and flashing recovery/ROMs/kernels:
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
Thanks so much bud! Will I be all good on the updated build I received today?
My bootloader is unlocked if it says custom on boot?
Again I really appreciate it!
Sent from my SCH-I535 using xda premium
mike216 said:
Thanks so much bud! Will I be all good on the updated build I received today?
My bootloader is unlocked if it says custom on boot?
Again I really appreciate it!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
As long as you have one of the stock builds listed in section 2 of that thread you should be good. The EZ-unlock app should be able to tell you if you're BL is unlocked.. also if you reboot the phone, if the samsung splash flashes for a split second (the one before you see Samsung Galaxy SIII), then you're prob unlocked.. if you see it for a few seconds then you're prob locked
Man I rooted flashed recovery in rom manager. (recovery wouldn't stick) so I flashed it again after making a nandroid and ended up having to recover a soft brick at 4am. Thank God for puremotive's guide on how to recover from it I was able to be back up. I don't know what went wrong. Because I didn't have busy box. Maybe I shouldn't have used the latest recovery rom manager flashes? I'm on stock with root and afraid to move anywhere! Anyone know how to make recovery stick on stock rom? I've never had this happen. Usually I would be OK and on to try AOSP on other devices uve had. Right now I'm rooted on stock rom with bootloader unlocked and have OTA root keeper in case I get another OTA. Any help would be greatly appreciated! Take care
Sent from my SCH-I535 using xda premium
How did you unlock your bootloader?
annoyingduck said:
How did you unlock your bootloader?
Click to expand...
Click to collapse
With the app
Sent from my SCH-I535 using xda premium
Ok, issue is probably that you used the current version 1.4 I think. In the app description in the playstore is a link to older versions, you want 1.2. The new ones are unlocking, but it's not sticking. There is also a link in the current root guide somewhere, but direct from the play store is fine.
annoyingduck said:
Ok, issue is probably that you used the current version 1.4 I think. In the app description in the playstore is a link to older versions, you want 1.2. The new ones are unlocking, but it's not sticking. There is also a link in the current root guide somewhere, but direct from the play store is fine.
Click to expand...
Click to collapse
link for ez-unlock 1.2
annoyingduck said:
How did you unlock your bootloader?
Click to expand...
Click to collapse
Let me be more specific because I may have had a locked bootloader.
I received the phone yesterday from my friend. He did unlock the bootloader with the app. I installed the official OTA from Verizon as soon as I got it. I rooted it. I didn't bother trying to unlock the bootloader because after the OTA when it booted it said custom with a lock symbol on boot up. I rooted and flashed the latest recovery from rom manager. I'm sure I picked the right phone. I made a nandroid but my recovery wouldn't stick. I remember it saying something about Co firming something about a recovery and I could have chosen yes. It sounded like CWM wouldn't stick if I choose yes?
I don't know if the OTA locked my bootloader back up?
I would like to try again. Any of you guys no how to make recovery stick on stock rom? I would like to try paranoid android. What recovery should I be on to flash this jelly bean based rom? I would really appreciate anyone who knows how I screwed up or has went straight to JB from a specific CWM recovery. I'm also not sure if I should said yes or know when in CWM when asking me that recovery question. I wish I remember what the question was
Sent from my SCH-I535 using xda premium
nghtrain88 said:
As long as you have one of the stock builds listed in section 2 of that thread you should be good. The EZ-unlock app should be able to tell you if you're BL is unlocked.. also if you reboot the phone, if the samsung splash flashes for a split second (the one before you see Samsung Galaxy SIII), then you're prob unlocked.. if you see it for a few seconds then you're prob locked
Click to expand...
Click to collapse
The app doesn't actually check the bootloader. It just keeps the info in the app data. Meaning if you unlock with the app then uninstall ezunlock and then reinstall it won't know if you're locked or unlocked.
mike216 said:
Man I rooted flashed recovery in rom manager. (recovery wouldn't stick) so I flashed it again after making a nandroid and ended up having to recover a soft brick at 4am. Thank God for puremotive's guide on how to recover from it I was able to be back up. I don't know what went wrong. Because I didn't have busy box. Maybe I shouldn't have used the latest recovery rom manager flashes? I'm on stock with root and afraid to move anywhere! Anyone know how to make recovery stick on stock rom? I've never had this happen. Usually I would be OK and on to try AOSP on other devices uve had. Right now I'm rooted on stock rom with bootloader unlocked and have OTA root keeper in case I get another OTA. Any help would be greatly appreciated! Take care
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
mike216 said:
Let me be more specific because I may have had a locked bootloader.
I received the phone yesterday from my friend. He did unlock the bootloader with the app. I installed the official OTA from Verizon as soon as I got it. I rooted it. I didn't bother trying to unlock the bootloader because after the OTA when it booted it said custom with a lock symbol on boot up. I rooted and flashed the latest recovery from rom manager. I'm sure I picked the right phone. I made a nandroid but my recovery wouldn't stick. I remember it saying something about Co firming something about a recovery and I could have chosen yes. It sounded like CWM wouldn't stick if I choose yes?
I don't know if the OTA locked my bootloader back up?
I would like to try again. Any of you guys no how to make recovery stick on stock rom? I would like to try paranoid android. What recovery should I be on to flash this jelly bean based rom? I would really appreciate anyone who knows how I screwed up or has went straight to JB from a specific CWM recovery. I'm also not sure if I should said yes or know when in CWM when asking me that recovery question. I wish I remember what the question was
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I'm 90% sure you wouldn't have been able to install the OTA if your bootloader was unlocked. The 'custom' on the boot doesn't mean that, and now that I think of it the fact you saw that proves that you aren't unlocked.
If you're still stock rooted then download the EZ unlock 1.2 from the link above and also go find EZ recovery on the market. Do not use the market version of EZ unlock. Now it doesn't matter what order you do it in but unlock your bootloader with the app them use EZ recovery to flash your recovery. Then you're all set to flash ROMs.
Brian Gove said:
The app doesn't actually check the bootloader. It just keeps the info in the app data. Meaning if you unlock with the app then uninstall ezunlock and then reinstall it won't know if you're locked or unlocked.
I'm 90% sure you wouldn't have been able to install the OTA if your bootloader was unlocked. The 'custom' on the boot doesn't mean that, and now that I think of it the fact you saw that proves that you aren't unlocked.
If you're still stock rooted then download the EZ unlock 1.2 from the link above and also go find EZ recovery on the market. Do not use the market version of EZ unlock. Now it doesn't matter what order you do it in but unlock your bootloader with the app them use EZ recovery to flash your recovery. Then you're all set to flash ROMs.
Click to expand...
Click to collapse
Thanks for everything Boss! That probably was the reason my recovery wouldn't stick. I used the link to grab easy unlock 1.2. I'm now unlocked, rooted. I want to flash an AOSP based rom (paranoid android) what recovery should I flash? The newest in rom manager or the slightly older one EZ-Recovery has to offer?
Thanks once again!
Sent from my SCH-I535 using xda premium
Cwm 6.0.1.2 for aosp jb, do not use the old 5 . something touch in ez recovery
mike216 said:
Thanks for everything Boss! That probably was the reason my recovery wouldn't stick. I used the link to grab easy unlock 1.2. I'm now unlocked, rooted. I want to flash an AOSP based rom (paranoid android) what recovery should I flash? The newest in rom manager or the slightly older one EZ-Recovery has to offer?
Thanks once again!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Which is the recovery that you want to use? I have the latest CWM touch on my Dropbox if that's the one you want. The regular CWM in the app is fine to use and twrp recovery has a thread in the development forum.
Brian Gove said:
Which is the recovery that you want to use? I have the latest CWM touch on my Dropbox if that's the one you want. The regular CWM in the app is fine to use and twrp recovery has a thread in the development forum.
Click to expand...
Click to collapse
I'm on stock ICS in want to go to paranoid android. Sorry guys but after last night I'm paranoid myself!
Sent from my SCH-I535 using xda premium
Brian Gove said:
The app doesn't actually check the bootloader. It just keeps the info in the app data. Meaning if you unlock with the app then uninstall ezunlock and then reinstall it won't know if you're locked or unlocked.
I'm 90% sure you wouldn't have been able to install the OTA if your bootloader was unlocked. The 'custom' on the boot doesn't mean that, and now that I think of it the fact you saw that proves that you aren't unlocked.
If you're still stock rooted then download the EZ unlock 1.2 from the link above and also go find EZ recovery on the market. Do not use the market version of EZ unlock. Now it doesn't matter what order you do it in but unlock your bootloader with the app them use EZ recovery to flash your recovery. Then you're all set to flash ROMs.
Click to expand...
Click to collapse
Thanks once again! I'm now on PA after a pack of smokes! Appreciate all your help. You were absolutely right ! Recovery stuck and it flashed with no problem. I used the current recovery straight from ROM manager
Sent from my SCH-I535 using xda premium
Good, glad to hear you got it rolling.
Just used the CF-Auto-Root and everything went smoothly. However, I only wanted my bootloader unlocked so I wouldn't have to wipe my device down the line but do not plan on using the root capabilities right now. Is there anyway to unroot the device while still maintaining the unlocked bootloader? Thanks.
Why didn't you just unlock the boot loader? Why did you use auto root knowing it would root it?
Sent from my Nexus 5
Pirateghost said:
Why didn't you just unlock the boot loader? Why did you use auto root knowing it would root it?
Sent from my Nexus 5
Click to expand...
Click to collapse
Honestly I just went through this reddit post about unlocking the bootloader. It did not mention anything about it rooting the device. I guess I should have realized it would have root when using "Auto-Root"...
So far I've unchecked the root option in SuperSU and have disabled the app. Wondering if there was a way to fully remove root access and SuperSU.
just flash the stock images back on using fastboot
Pirateghost said:
just flash the stock images back on using fastboot
Click to expand...
Click to collapse
+1
Here's some instructions for you DangKid, just incase you need them: http://www.droid-life.com/2013/11/05/how-to-flash-nexus-5-factory-images/
DangKid said:
Honestly I just went through this reddit post about unlocking the bootloader. It did not mention anything about it rooting the device. I guess I should have realized it would have root when using "Auto-Root"...
So far I've unchecked the root option in SuperSU and have disabled the app. Wondering if there was a way to fully remove root access and SuperSU.
Click to expand...
Click to collapse
There is an unroot feature in SuperSu app. Simple.
Good morning!
So, yesterday evening I rooted my N5 with Towelroot, installed TWRP and then flashed the latest SuperSU! Everything went fine and now I want to install PA (4.4 RC1). But I'm not quite sure if I need to unlock the bootloader for that... I think that only needs to be done for a kernel. So what should I do? Leave it locked and flash PA, or unlock it and flash PA?
Also, if someone could set me up with the 4.4.3 gapps, that would be nice. I downloaded a file, but its not a mini version and only has 97MB. The full versions are a lot bigger if I remember correctly, aren't they?
Anyway thanks!
*edit: I'm currently on the 4.4.3 stock ROM. That means that I don't need to update my radio, because it should already be the latest version from the OTA... Correct me if In wrong though!
Sent from my Nexus 5 using Tapatalk
Please can you ensure you ask questions in the questions section ?
The bootloader only needs to be unlocked to flash recovery which you need for rooting. This isn't an issue for you because you used the new exploit that means you can root without having to unlock the bootloader
Even though you've rooted already, I strongly urge you to read the pre root section in the thread shown in my signature to bump up your basic knowledge
Sent from my Nexus 5 using Tapatalk
rootSU said:
Please can you ensure you ask questions in the questions section ?
The bootloader only needs to be unlocked to flash recovery which you need for rooting. This isn't an issue for you because you used the new exploit that means you can root without having to unlock the bootloader
Even though you've rooted already, I strongly urge you to read the pre root section in the thread shown in my signature to bump up your basic knowledge
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I do have basic knowledge (rooted my Nexus Phones before, every time with fastboot). I'm just asking if it is important to unlock the hootloader before flashing a ROM, as I'm not sure. Sorry for posting in the false section...
Sent from my Nexus 5 using Tapatalk
julbra18 said:
I do have basic knowledge (rooted my Nexus Phones before, every time with fastboot). I'm just asking if it is important to unlock the hootloader before flashing a ROM, as I'm not sure. Sorry for posting in the false section...
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You can install custom ROMs, but only ROMs based on stock firmware and using stock kernel. ROMs like CyanogenMod, you can't install at all because you cannot flash the custom kernel that comes with it. Unlocked bootloader allows you to install unsigned kernels onto your phone.
fxdil said:
You can install custom ROMs, but only ROMs based on stock firmware and using stock kernel. ROMs like CyanogenMod, you can't install at all because you cannot flash the custom kernel that comes with it. Unlocked bootloader allows you to install unsigned kernels onto your phone.
Click to expand...
Click to collapse
Where did you get this information? My bootloader is locked and I can flash all kernels via recovery
Sent from my Nexus 5 using Tapatalk
rootSU said:
Where did you get this information? My bootloader is locked and I can flash all kernels via recovery
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Isn't that the case, or have I been misinformed? I left my boot loader unlocked since the day I was rooted, mostly because of that fact (I remembered reading it somewhere) and also because I can't do a RMA.
Sent using Etch-a-Sketch
fxdil said:
Isn't that the case, or have I been misinformed? I left my boot loader unlocked since the day I was rooted, mostly because of that fact (I remembered reading it somewhere) and also because I can't do a RMA.
Sent using Etch-a-Sketch
Click to expand...
Click to collapse
You unlock the bootloader to flash a custom recovery. You flash kernels/ROMs in a custom recovery, not in bootloader.
Also this thread is in the wrong section.
So, if I just unlock my bootloader with bootunlock I won't have any problems?
Sent from my Nexus 5 using Tapatalk
julbra18 said:
So, if I just unlock my bootloader with bootunlock I won't have any problems?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Sure. Also you wont have any problems if you DON'T unlock your bootloader
Sent from my Nexus 5 using Tapatalk
Lethargy said:
You unlock the bootloader to flash a custom recovery. You flash kernels/ROMs in a custom recovery, not in bootloader.
Also this thread is in the wrong section.
Click to expand...
Click to collapse
That was where I was getting at, since I learnt to root using the manual way and not using a toolkit, I had to unlock my bootloader first before flashing a custom recovery. Never occurred to me to relock it.
(if I made a mistake somewhere, I apologized. I'm still learning, and learnt something new today!)
rootSU said:
Sure. Also you wont have any problems if you DON'T unlock your bootloader
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'll try it with the locked one first, I can change it later on anyways! Thanks for your help!
Sent from my Nexus 5 using Tapatalk
fxdil said:
That was where I was getting at, since I learnt to root using the manual way and not using a toolkit, I had to unlock my bootloader first before flashing a custom recovery. Never occurred to me to relock it.
(if I made a mistake somewhere, I apologized. I'm still learning, and learnt something new today!)
Click to expand...
Click to collapse
You can flash a kernel/ROM in a custom recovery regardless bootloader state, but the bootloader needs to be unlocked to use fastboot (i.e. flash the custom recovery in the first place). A bunch of people relock their bootloader with an app (and unlock when necessary, doesn't delete internal storage through this method) for extra security (internal storage wipes if bootloader is unlocked via fastboot).