Database Info

[Q] Completely awkward behaving Nexus S

I just bought this phone yesterday and it is the i9020t (AWS version). The phone function works fine but every so often every application fails and gives an error asking to report it. I cannot manage to change the screen lock, it just comes back after reset. I only managed to remove it once. Also I cannot reset it no matter what I do, whether it is from settings or from the recovery menu. All data seems impossible to remove. How is this happening?
So Far:
-I got the boot loader unlocked (does this mean it is rooted yet?), failed to install superboot.zip
-Got the adb setup with using only part of the sdk files
(http://esausilva.com/2010/10/02/how-to-set-up-adb-android-debug-bridge-in-mac-osx/)
Now I have tried this:
http://forum.xda-developers.com/showthread.php?t=884093
I can't get clockworkmod on here, I don't even know what it is exactly.
I believe I need to flash the phone onto stock firmware, the current seems corrupt as I can't do any changes such as password or wipe data.
More info on phone:
Android version: 2.3.4; Baseband version: I9020XXKD1; Kernel version: 2.6.35.7-ge382d80 [email protected]#1; Build number: GRJ22;
BTW I am on Mac OS X but can access a PC if I really have to.
Anything else I need to provide?

Doesn't sound like an odd behaving phone, just that you weren't very prepared for the rooting process.
If your bootloader is unlocked you need to flash a custom recovery such as clockworkmod or twrp. To do this you will use the fastboot flash recovery nameofrecovery.img after you have flashed the recovery you can either flash a new rom or flash the superuser.zip to achieve root on the stock rom.
Sent from my Nexus S 4G using xda premium

He said weeny hah but other than that he's right
Rem3Dy said:
Doesn't sound like an odd behaving phone, just that you weeny very prepared for the rooting process.
If your bootloader is unlocked you need to flash a custom recovery such as clockworkmod or twrp. To do this you will use the fastboot flash recovery nameofrecovery.img after you have flashed the recovery you can either flash a new rom or flash the superuser.zip to achieve root on the stock rom.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
sent from my nexus s on a kang from simms

sinik420 said:
He said weeny hah but other than that he's right
sent from my nexus s on a kang from simms
Click to expand...
Click to collapse
Owned by auto correct
Sent from my Nexus S 4G using xda premium

Rem3Dy said:
Doesn't sound like an odd behaving phone, just that you weren't very prepared for the rooting process.
If your bootloader is unlocked you need to flash a custom recovery such as clockworkmod or twrp. To do this you will use the fastboot flash recovery nameofrecovery.img after you have flashed the recovery you can either flash a new rom or flash the superuser.zip to achieve root on the stock rom.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
It was a messed up phone. Returned it. Nothing would write onto sdcard. Which explains why it would not allow many functions that require data retention.

New guy

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.

HTC one x question about twrp

Hello. I am new to the HTC one x coming previously from an HTC inspire. I am with att. I followed the directions and unlocked the bootloader. I have been reading and noticed S-Off is still being worked on. I'm Confused on what my next step is to load a custom ROM. Sorry I know this has probably been answered but I'm still confused. Can I do the next set of steps without a computer and just do it from my phone? I downloaded an app called recovery manager not sure of that will help me out. Thanks for any help you guys can provide. I'm on 2.20 and 4.0.4 thanks again.
Sent from my HTC One X using xda app-developers app

I think at that time after unlock of the bootloader you will need to install a recovery software the one we use is TWRP i would stick with 2.2.0.0 and install it thought goomanager that is avaliable though the play store.
Instructions : http://forum.xda-developers.com/showthread.php?t=1677447

To use goomanager I need to be rooted though right?I don't think I'm rooted. Farthest I have gotten so far is unlocking the bootloader. And I'm not sure what to do after that. I'm not sure if I can do the rest from my phone (which I hope I can). Thanks ks for your help.
Sent from my HTC One X using xda app-developers app

You'll have you fastboot flash SU.. I don't remember where to get the file or the command.... Sorry
Sent from my One X using Tapatalk 2

unlock bootloader, flash twrp in fastboot, then flash file below in twrp
CWM-SuperSU-v0.98.zip

DvineLord said:
unlock bootloader, flash twrp in fastboot, then flash file below in twrp
Click to expand...
Click to collapse
Do you absolutely have to flash SuperSU to flash ROMs? Can you just go right from TWRP and flash a rooted ROM and be considered as "rooted"?
Thanks

Lunatic00 said:
Do you absolutely have to flash SuperSU to flash ROMs? Can you just go right from TWRP and flash a rooted ROM?
Thanks
Click to expand...
Click to collapse
Hmmm I'm pretty sure you can flash a rooted Rom

Lunatic00 said:
Do you absolutely have to flash SuperSU to flash ROMs? Can you just go right from TWRP and flash a rooted ROM and be considered as "rooted"?
Thanks
Click to expand...
Click to collapse
You can just flash a custom ROM, which will have SuperSU or SU cooked in. Only need to flash SuperSU if you want to stay on stock ROM and have root.

you made your situation sound different. the steps i take is use my token, flash recovery, then flash a rom or supersu depending if i want a custom rom or keep using stock.

Strange TWRP problem, no OS detected etc. Boots fine to stock

I ran the causal root applet on a new SG3 on 4.1.2. Ran root, the unlock script and installed TWRP. Booted into recovery and I got the error for a locked bootloader. I used download mode to get back to the stock rom and then used E-Z unlock to unlock the bootloader. Was able to boot into recovery this time but TWRP read internal and external memory as 0mb, unable to make a backup, and gave a no OS error when went to reboot. I updated TWRP with TWRP manager but the problems are still persistent. Phone boots fine and reboots fine at the moment.
I'm not sure what to do now though. I'm at the point were I don't care if I get stuck with the OTA update but I'm afraid that will brick the phone. I'm not sure what went wrong with TWRP, since this is the second S3 I've rooted.
Any sugestions? I'm afraid to use odin or try anything else since the phone currently works fine. But I'd prefer to not have to sleep in fear it might force the OTA update while I'm asleep and wake up to a bricked phone.
I tried searching, the best I could find is that newer versions of TWRP can't read the memory on a 4.1.2 rom, but the problems were there when I originally started with the recommended version.
Thanks for any help anyone can give.

Try to use cwm or philz and see if you have the same issue.
Sent from my SCH-I535 using Tapatalk 2

Xx

BadUsername said:
Try to use cwm or philz and see if you have the same issue.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Can you install a different custom recovery over one using the causal applet? I was planning on trying to reinstall TWRP but I wasn't sure if I had to do it a certain way like through odin or Using the unified tool kit?
Thanks for the help so far!

Smogon said:
Can you install a different custom recovery over one using the causal applet? I was planning on trying to reinstall TWRP but I wasn't sure if I had to do it a certain way like through odin or Using the unified tool kit?
Thanks for the help so far!
Click to expand...
Click to collapse
No.
Download latest philz touch recovery d2lte zip, then flash it in recovery, then reboot recovery.
Then check and see if you're getting a similar error message.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
No.
Download latest philz touch recovery d2lte zip, then flash it in recovery, then reboot recovery.
Click to expand...
Click to collapse
I can't, recovery doesn't detect my internal or external memory. That's my main issue.

Smogon said:
I can't, recovery doesn't detect my internal or external memory. That's my main issue.
Click to expand...
Click to collapse
OK.
Then download the Odin version and flash through that. Then boot the phone into recovery.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
OK.
Then download the Odin version and flash through that. Then boot the phone into recovery.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'll try the second option, Thanks!

BadUsername said:
OK.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I tried CWM and the stock recovery through EZ, both gave the same error as TWRP, unable to mount /
I'm really confused as to whats wrong. At this point I don't care if I get stuck with the OTA 4.3, but I don't want to try to update it with the recovery still not reading either my SD cards.
Any Ideas?

Are you sure of your phone model? I believe it puts it on the screen in download mode and also on a sticker under the battery. I'm mostly curious because you mention that this is a new phone with 4.1.2. Are you trying older versions of cwm as well?
Sent from my SCH-I535 using XDA Premium 4 mobile app

Smogon said:
I ran the causal root applet on a new SG3 on 4.1.2. Ran root, the unlock script and installed TWRP. Booted into recovery and I got the error for a locked bootloader. I used download mode to get back to the stock rom and then used E-Z unlock to unlock the bootloader. Was able to boot into recovery this time but TWRP read internal and external memory as 0mb, unable to make a backup, and gave a no OS error when went to reboot. I updated TWRP with TWRP manager but the problems are still persistent. Phone boots fine and reboots fine at the moment.
I'm not sure what to do now though. I'm at the point were I don't care if I get stuck with the OTA update but I'm afraid that will brick the phone. I'm not sure what went wrong with TWRP, since this is the second S3 I've rooted.
Any sugestions? I'm afraid to use odin or try anything else since the phone currently works fine. But I'd prefer to not have to sleep in fear it might force the OTA update while I'm asleep and wake up to a bricked phone.
I tried searching, the best I could find is that newer versions of TWRP can't read the memory on a 4.1.2 rom, but the problems were there when I originally started with the recommended version.
Thanks for any help anyone can give.
Click to expand...
Click to collapse
by any chance did u try to setup dualboot? I have a similar issue where nothing gets mounted and o mb for storage, .only receovery i get to work is cwm. im pretty sure its a partition issue but idk. i tried flashing pit files for my phone but so far the issue remains.

xevildoerxx said:
by any chance did u try to setup dualboot? I have a similar issue where nothing gets mounted and o mb for storage, .only receovery i get to work is cwm. im pretty sure its a partition issue but idk. i tried flashing pit files for my phone but so far the issue remains.
Click to expand...
Click to collapse
No I just used the causal tool.
dpeeps74 said:
Are you sure of your phone model? I believe it puts it on the screen in download mode and also on a sticker under the battery. I'm mostly curious because you mention that this is a new phone with 4.1.2. Are you trying older versions of cwm as well?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm pretty sure, has all the verizon bloat and logos, also I'm pretty sure the causal applet bricks the international ones. I don't remember the version of twrp that the causal script flashed, but I tried that one, the most recent one, and 2.5 i think from EZ recovery. The stock recovery from EZ has the same issue now though which is what really confuses me. at the moment I have root dissabled and the bootloader is locked and its back with the stock recovery, it still says custom when i reboot the phone though.

Flashing PA with locked bootloader?

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).