[Q][HELP] Error in Nexus 4 with KitKat KRT16S ! - Nexus 4 Q&A, Help & Troubleshooting

Ok, My Nexus 4 NOT LOCK BOOTLOADER after update for Kitkat, and no lock in any Stock and Customs ROMS !
just stays on: "LOCK-STATE: unlocked"
The commando line fastboot oem lock not work :crying:
help me I'm desperate
Help pls ... how to lock my device ? .-.

Well first of all, why would you like to re-lock your bootloader?

mumaster20 said:
Well first of all, why would you like to re-lock your bootloader?
Click to expand...
Click to collapse
my friend said that the OTA updates require locked bootloader, then I would like to lock it again ...
and how this under warranty, also wanted to make everything from factory

Your friend is wrong. You don't need locked bootloader to get OTA.
To get OTA update, you need stock rom and stock recovery, locked or unlocked doesn't matter.
You can also flash the factory stock image without wiping your data (see link in my signature).
If you have root you can use this app to lock and unlock your bootloader: https://play.google.com/store/apps/details?id=net.segv11.bootunlocker

eksasol said:
Your friend is wrong. You don't need locked bootloader to get OTA.
To get OTA update, you need stock rom and stock recovery, locked or unlocked doesn't matter.
You can also flash the factory stock image without wiping your data (see link in my signature).
If you have root you can use this app to lock and unlock your bootloader: https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
Click to expand...
Click to collapse
Yes, i understand .... so, my bootloader not lock with the app BootUnlocker, or command line, i tested all methods and nothing :crying:

AndreyVilella said:
Yes, i understand .... so, my bootloader not lock with the app BootUnlocker, or command line, i tested all methods and nothing :crying:
Click to expand...
Click to collapse
I guess something is up with your phone physical memory, but it doesn't matter, it really should not affect your warrenty (but the custom rom and recoveries will). Makes zero different to OTA updates either.

eksasol said:
I guess something is up with your phone physical memory, but it doesn't matter, it really should not affect your warrenty (but the custom rom and recoveries will). Makes zero different to OTA updates either.
Click to expand...
Click to collapse
Ok, thanks, then I can rest easy while the warranty? I just be with a recovery image and also manufactures and without Root?

AndreyVilella said:
Ok, thanks, then I can rest easy while the warranty? I just be with a recovery image and also manufactures and without Root?
Click to expand...
Click to collapse
Honestly, I don't think they care if you have root either, but that's base on other user feedbacks. It seems LG warrenty is picky about other things and not very good from the feedbacks from what I read actually, but I haven't had first hand experience. But people have sent in rooted devices for repair.
I think just have factory image and stock recovery and stock kernel.

Solution !
eksasol said:
Honestly, I don't think they care if you have root either, but that's base on other user feedbacks. It seems LG warrenty is picky about other things and not very good from the feedbacks from what I read actually, but I haven't had first hand experience. But people have sent in rooted devices for repair.
I think just have factory image and stock recovery and stock kernel.
Click to expand...
Click to collapse
Ok, Thanks ! I will continue in Stock image with bootloader Unlocked ...

Related

need help returning phone to customer care

Hello
I need to return my nexus s to Samsung care since speaker is not working ..its rooted and I have miui rom currently
Plz tell me what all things I should before giving
Thank you
ancilary said:
Hello
I need to return my nexus s to Samsung care since speaker is not working ..its rooted and I have miui rom currently
Plz tell me what all things I should before giving
Thank you
Click to expand...
Click to collapse
Nope, you're pretty screwed. When unlocking the bootloader, the phone tells you that your warranty is now void.
The nexus S has a oem bootloader unlock. In other words, samsung will not hold the fact that bootloader is unlocked against you. You do need to get rid of miui and get back to stock. There is a thread showing how to do this and provides the files you need. I'll see if I can find it for you.
Sent from my Nexus S 4G
khartaras said:
Nope, you're pretty screwed. When unlocking the bootloader, the phone tells you that your warranty is now void.
Click to expand...
Click to collapse
dude shut up if u dont know what your talking about ..
go back to stock,stock recovery isnt even neccessary to be honest i know alot of people in the customer care for samsung and google they dont even check they issue command via bootloader, lastly you go into fastboot mode and issue command fastboot oem lock
mak213 said:
dude shut up if u dont know what your talking about ..
go back to stock,stock recovery isnt even neccessary to be honest i know alot of people in the customer care for samsung and google they dont even check they issue command via bootloader, lastly you go into fastboot mode and issue command fastboot oem lock
Click to expand...
Click to collapse
I said that because I was screwed over by Samsung.
I just use cwm to flash the latest ota rom then locked the bootloader and reboot.
no issues from samsung regarding voided warranty. Perhaps you had sent it in with the bootloader unlocked?
Just use rom managers stock 2.3.3 and flash it... then lock bootloader by the instructions provided a post up
Just a heads up... same thing happened to a guy and he sent it in.for a speaker that wasn't working ... he waited over a month to get his phone back rather then them sending him a new one or refurbished
Sent from my Nexus S using xda premium
khartaras said:
Nope, you're pretty screwed. When unlocking the bootloader, the phone tells you that your warranty is now void.
Click to expand...
Click to collapse
lol. are you trolling?
just flash the original system images found in the development forum, i think they are a sticky
good luck! make sure the bootloader says locked, and there is no super user app and no custom recovery!!!
I used Stock Odin image that will restore everything rom, recovery...ect then just lock bootloader. Funny thing is i sent mine back all stock and bootloader locked few months ago and got back with bootloader unlocked.
Sent from my Google Nexus S using xda premium
demo23019 said:
I used Stock Odin image that will restore everything rom, recovery...ect then just lock bootloader. Funny thing is i sent mine back all stock and bootloader locked few months ago and got back with bootloader unlocked.
Sent from my Google Nexus S using xda premium
Click to expand...
Click to collapse
LMAO it was probably cyanogen himself, they did hire him you know

[Q] Arc s on 3

I have an Arc s using the 3 branded 4.0.4 (4.1.L.0.8) firmware and have wanted to root and unlock the boot loader for ages. The problem is that I don't know the best method of unlocking the boot loader and root the phone. Was wondering if someone could send me in the right direction or give me a good tutorial on how to go from the very basic no root stock firmware to having the phone rooted with the boot loader unlocked would be great if someone if able to help me.
totalfailz said:
I have an Arc s using the 3 branded 4.0.4 (4.1.L.0.8) firmware and have wanted to root and unlock the boot loader for ages. The problem is that I don't know the best method of unlocking the boot loader and root the phone. Was wondering if someone could send me in the right direction or give me a good tutorial on how to go from the very basic no root stock firmware to having the phone rooted with the boot loader unlocked would be great if someone if able to help me.
Click to expand...
Click to collapse
See the first link in my signature.
XperienceD said:
See the first link in my signature.
Click to expand...
Click to collapse
haha love it xD
totalfailz said:
haha love it xD
Click to expand...
Click to collapse
Now that's out of the way, read the stickys, although you seem to have new F.W so it might be rootable using the existing methods or you may need to wait until someone figures out how to root it. Bootloader unlocking is the same regardless of firmware.
totalfailz said:
I have an Arc s using the 3 branded 4.0.4 (4.1.L.0.8) firmware and have wanted to root and unlock the boot loader for ages. The problem is that I don't know the best method of unlocking the boot loader and root the phone. Was wondering if someone could send me in the right direction or give me a good tutorial on how to go from the very basic no root stock firmware to having the phone rooted with the boot loader unlocked would be great if someone if able to help me.
Click to expand...
Click to collapse
I have (nearly) the same phone, also on 3 (rant to follow!). In short, your bootloader cannot be unlocked without paying someone to do it for you (around £15). You can still use custom roms (via CWM recovery) without an unlocked bootloader, so IMHO not really worth it. I was waiting for a former member of XDA to unlock my phone for around a week (we weren't free at the same times, etc) and in the end didn't bother.
There may be other ways, but personally I used this: http://forum.xda-developers.com/showthread.php?t=1683189, but for ease of use, the toolkit from here: http://forum.xda-developers.com/showthread.php?t=1601038. Bascially, you need to flash the 4.0.3 kernel using flashtool, use DooMLoRD's kit to root the device, then flash the 4.0.4 kernel back again. After that, you can get CWM recovery from the market, and use that with any rom suitable for locked bootloaders.
BTW, 3 are absolutely the WORST network in the UK, just got off the phone arguing with them about them cutting all 2G services (i now realise why my reception has been so bad for the past 6 months!) while also raising the price of my packages, all without warning.
XTCrefugee said:
I have (nearly) the same phone, also on 3 (rant to follow!). In short, your bootloader cannot be unlocked without paying someone to do it for you (around £15). You can still use custom roms (via CWM recovery) without an unlocked bootloader, so IMHO not really worth it. I was waiting for a former member of XDA to unlock my phone for around a week (we weren't free at the same times, etc) and in the end didn't bother.
There may be other ways, but personally I used this: http://forum.xda-developers.com/showthread.php?t=1683189, but for ease of use, the toolkit from here: http://forum.xda-developers.com/showthread.php?t=1601038. Bascially, you need to flash the 4.0.3 kernel using flashtool, use DooMLoRD's kit to root the device, then flash the 4.0.4 kernel back again. After that, you can get CWM recovery from the market, and use that with any rom suitable for locked bootloaders.
BTW, 3 are absolutely the WORST network in the UK, just got off the phone arguing with them about them cutting all 2G services (i now realise why my reception has been so bad for the past 6 months!) while also raising the price of my packages, all without warning.
Click to expand...
Click to collapse
thanks! just the reply I was looking for . I have had no problems on 3, the service and the network has been great for me. I just hate that I am not able to use Sony's method of unlocking the boot loader due to being on 3's branded firmware >.<
totalfailz said:
thanks! just the reply I was looking for . I have had no problems on 3, the service and the network has been great for me. I just hate that I am not able to use Sony's method of unlocking the boot loader due to being on 3's branded firmware >.<
Click to expand...
Click to collapse
Doesn't flashing generic firmware solve the bootloader-issue?
Curst said:
Doesn't flashing generic firmware solve the bootloader-issue?
Click to expand...
Click to collapse
No.
totalfailz said:
I have an Arc s using the 3 branded 4.0.4 (4.1.L.0.8) firmware and have wanted to root and unlock the boot loader for ages. The problem is that I don't know the best method of unlocking the boot loader and root the phone. Was wondering if someone could send me in the right direction or give me a good tutorial on how to go from the very basic no root stock firmware to having the phone rooted with the boot loader unlocked would be great if someone if able to help me.
Click to expand...
Click to collapse
I have 3 also in Sweden, but Alejanrissimo (a guy in the forum) unlocked the bootloader for me remotely and now it is very good. I can flash ROM, kernel, get easy root etc.
I payed 19 US dollars over PayPal and after 10 minutes (with some paper clip operation stuff) my phone was unlocked, even the SIM was unlocked too. :good:
I can still use PCC and SEUS and the TrackID is also still there.

Unlocked bootloader logo removed in JB

I WILL NOT BE HELD RESPONSIBLE FOR ANY DAMAGE TO YOUR PHONE CAUSED BY THE INFORMATION POSTED HERE. THIS IS NOT A TUTORIAL.
First of all , i know there is a thread about removing the Unlocked bootloader logo. This thread is started just to present some information based on my personal experience.
I owe a Motorola Razr I with unlocked bootloader :laugh:.......
A couple of weeks ago i decided to come back to ICS from the JB fastboot i was using(orange UK). Instead of using fastboot files made by mattlgroff I decided to fully flash the original ICS firmware for my phone using RSDlite. After the firmware was flashed i pushed the signed logo to the device.Of course the phone didn't finish booting and got stuck in bootloop. My phone became then a brick with a black screen and green led and i had to use the files from here to unbrick my phone. Big thanks to U1138 for finding the solution for unbricking.
When my phone phone finally booted i was so excited i didn't realize the ugly Bootloader unlocked logo is gone. I realized that yesterday while restarting the device and thought it's good to share it with everyone else and maybe will find a way for everyone to get rid of the ugly message on the boot screen.
free2live said:
I WILL NOT BE HELD RESPONSIBLE FOR ANY DAMAGE TO YOUR PHONE CAUSED BY THE INFORMATION POSTED HERE. THIS IS NOT A TUTORIAL.
First of all , i know there is a thread about removing the Unlocked bootloader logo. This thread is started just to present some information based on my personal experience.
I owe a Motorola Razr I with unlocked bootloader :laugh:.......
A couple of weeks ago i decided to come back to ICS from the JB fastboot i was using(orange UK). Instead of using fastboot files made by mattlgroff I decided to fully flash the original ICS firmware for my phone using RSDlite. After the firmware was flashed i pushed the signed logo to the device.Of course the phone didn't finish booting and got stuck in bootloop. My phone became then a brick with a black screen and green led and i had to use the files from here to unbrick my phone. Big thanks to U1138 for finding the solution for unbricking.
When my phone phone finally booted i was so excited i didn't realize the ugly Bootloader unlocked logo is gone. I realized that yesterday while restarting the device and thought it's good to share it with everyone else and maybe will find a way for everyone to get rid of the ugly message on the boot screen.
Click to expand...
Click to collapse
Is it still working after several reboots?
free2live said:
... [/COLOR][/SIZE]
Click to expand...
Click to collapse
So you suggest going back to ICS, bricking your device, unbricking it and flashing JB again in order to get rid of the bootloader logo?
Orbbman said:
So you suggest going back to ICS, bricking your device, unbricking it and flashing JB again in order to get rid of the bootloader logo?
Click to expand...
Click to collapse
I'm not suggesting anything. Only if you know what you are doing you can try it and even then take extra caution. It might be just a particular case.
Sent from my XT890 using xda premium
Thorstenk said:
Is it still working after several reboots?
Click to expand...
Click to collapse
Yes mate. I have like this for more than 1 week and i do reboot my device quite often due to poor network signal at my work.
Sent from my XT890 using xda premium
here's a short video to proof the unlocked bootloader message is gone
I am not a hundred perent sure of that, but I think this worked on your device because you unlocked your bootloader while on ICS then, upgraded to JB using matt's fastboot.
For someone who upgraded to JB using the OTA and only then unlocked their bootloader, this won't work because the motoboot file version is already the highest (homemade fastboot does not flash motoboot, that's why you were able to flash after a downgrade)
JackyJack said:
I am not a hundred perent sure of that, but I think this worked on your device because you unlocked your bootloader while on ICS then, upgraded to JB using matt's fastboot.
For someone who upgraded to JB using the OTA and only then unlocked their bootloader, this won't work because the motoboot file version is already the highest (homemade fastboot does not flash motoboot, that's why you were able to flash after a downgrade)
Click to expand...
Click to collapse
It maybe be possible. I did unlock bootloader while on ICS
Sent from my XT890 using xda premium
Anyone can confirm that intentionally bricking the phone by downgrading to ICS and reviving it deletes the unlocked sign?
Don't work with me
my logo returned to normal after restoring Pi-llama rom through cwm.
Could you be a bit more precise?
What do you mean with normal, no unlocked bootloader message left?
And what do you mean with restored?
Thanks!
densets said:
my logo returned to normal after restoring Pi-llama rom through cwm.
Click to expand...
Click to collapse
Thorstenk said:
Could you be a bit more precise?
What do you mean with normal, no unlocked bootloader message left?
And what do you mean with restored?
Thanks!
Click to expand...
Click to collapse
i unlocked my bootloader on ics telcel then went to 320002e.u. and did an update to 40002e.u.and my sing of unlocked bootloader disappear. but i hate is reading the warning message of unlocked bootloader in jelly bean how can i eraseed that.
http://forum.xda-developers.com/showthread.php?t=2226504
Yes, its for unlocking the bootloaders for the Snapdragon Motorolas (Atrix HD, RAZR HD and RAZR M) but after unlocking their bootloaders the same message appears (the same that we have), @tucstwo has provided a file to remove the unlocked message for these phones, I don't know if that zip could be compatible with the RAZR i, but giving the fact that the zip file removes the unlocked message for these phones ALREADY RUNNING JELLY BEAN, maybe someone can give a try and see what happens...
Link of the zip file is on the 2nd post.
don't work...
LOL try some king of custom upgrade we known that we have some chance of brick our phone and we get this risk like a bet with more chance to win, but intencionally brick the phone that cost here in brazil more than $500 we have to be a great crazy.
Does this also work on ICS?
AGISCI said:
Does this also work on ICS?
Click to expand...
Click to collapse
I can't tell you if it works or no. This is what happened to me not a tutorial.
Sent from Razr I using a bat ^o^
matheusgallo said:
Don't work with me
Click to expand...
Click to collapse
Did anybody try this method?
http://androidforums.com/motorola-razr-i/700911-bootloader-unlocked-under-jb.html
piskr said:
Did anybody try this method?
http://androidforums.com/motorola-razr-i/700911-bootloader-unlocked-under-jb.html
Click to expand...
Click to collapse
Yes! It dont work. Do not even try!

Post MHC19l update camera does not work at all

So i recently updated to the new mhc19l version on my nexus 6p (this is not android N, just the latest android update for the 6p). I did it via the flashfire method following this youtube video: https://www.youtube.com/watch?v=cvs0JQswTWw&feature=youtu.be
I dont have multirom so i didnt do the stuff it mentioned about that. At first I thought I was successful and everything was working great. I reflashed xposed to the latest version, and updated my elemental X kernal too.
But now when I do anything with the camera the phone gets really weird. Post reboot the camera preview will work only once. If I take a photo it crashes. And every time I try to do anything with the camera involved the thing will crash and not even load preview anymore. That includes 3rd party apps like snap chat. Also I can't edit quick setting tiles in system ui as it tells me system ui tuner has crashed, but that i can live with. The camera issues I can not live with.
None of that happens with my rooted 6p on the same build. I think you need to look at xposed, the kernel changes and all the other jiggerypokery you've done. I'd do begin by reflashing the factory image and do this manually either using Heisenberg's extremely clear guide, or by the flash-all.bat command that google supplies in the factory build. Then you can check camera, flash recovery (again, using Heisenberg's guide, it takes but a couple of commands), then root, add xposed, kernels and all that special sauce. Do it step by step, then you'll know when something goes wrong and only have to fix that.
Thank you for your help. I'll check that out. Do you think it may be because I updated from a pretty old build? (808L) I skipped a few updates and went right to the latest one, could that cause any problems?
Not really. I think it's because you've done too much using a tool and without checking things after each step. Stop using tools like flashfire when you don't understand what they do and get yourself up to speed with using the commands. After that, you'll spot where things have gone wrong and be able to fix or troubleshoot it within the community. No one can help you when it's an issue that could caused by one or more of a hundred things you've tinkered with.
It's not hard and worth the little bit of busy work and brain thought. You'll enjoy it!
Yea I like to tinker and stuff. It's just the customizations with dashclock and stuff that I don't want to lose. But I did app backups so hopefully I won't.
Something probably went wrong during the flash process. I highly doubt xposed or kernel modifications are to blame. I keep 12 xposed modules running at all times with kylo kernel which I have heavily modified with EX kernel app. Read Heisenberg's guide and learn to flash images properly and you should be good to go.
Before I do any reflashing today can anyone do me a favour and upload their camera APK?
Im just hoping it has something to do with that. Last ditch effort.
And thanks for the help guys
So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk
and313 said:
So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
You can't flash anything with a locked bl. Locking the BL is nothing but trouble if you like to tinker.
Sent from my Nexus 6P using Tapatalk
and313 said:
So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
dirtyuzbek said:
Before I do any reflashing today can anyone do me a favour and upload their camera APK?
Im just hoping it has something to do with that. Last ditch effort.
And thanks for the help guys
Click to expand...
Click to collapse
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?
Any Advice ?
Heisenberg said:
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?
Click to expand...
Click to collapse
Hello you seem very knowledgeable on the subject. I just picked up a 6P and was wondering how does encryption affect things such as TWRP and root. Do you advise to disable encryption on the device for ease-of-use in TWRP and root.
naruto.ninjakid said:
Hello you seem very knowledgeable on the subject. I just picked up a 6P and was wondering how does encryption affect things such as TWRP and root. Do you advise to disable encryption on the device for ease-of-use in TWRP and root.
Click to expand...
Click to collapse
Look at my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Deception isn't necessary anymore, as long as you use the latest TWRP you should have no problems.
did it flash the vendor?
Heisenberg said:
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?
Click to expand...
Click to collapse
Wait.. If the bootloader is locked and a ota fails you cant oem unlock it?
Sent from my Nexus 6P using Tapatalk
and313 said:
Wait.. If the bootloader is locked and a ota fails you cant oem unlock it?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No, because if the OTA fails you won't have access to the option in Developer Options to enable OEM unlocking. Trust me, you want to have that bootloader unlocked. You don't wanna end up like the other guys who had to send their phone back for repair because they locked it.
Heisenberg said:
No, because if the OTA fails you won't have access to the option in Developer Options to enable OEM unlocking. Trust me, you want to have that bootloader unlocked. You don't wanna end up like the other guys who had to send their phone back for repair because they locked it.
Click to expand...
Click to collapse
Right... I did not think that the first step (enable bootloader unlock from dev options) is actually necessary.
Sent from my Nexus 6P using Tapatalk

Nexus 6p nougat bootloader

I have a major problem, I need to know if it will be possible to flash a custom rom on a nexus 6p. It seems that it will be hard because of that new bootloader.
smilehead said:
I have a major problem, I need to know if it will be possible to flash a custom rom on a nexus 6p. It seems that it will be hard because of that new bootloader.
Click to expand...
Click to collapse
What do you mean? Any bootloader version on this device can be unlocked.
Heisenberg said:
What do you mean? Any bootloader version on this device can be unlocked.
Click to expand...
Click to collapse
Sorry, I'm new to this stuff. I thought they can change the bootloader when you upgrade. Thanks for the help though
smilehead said:
Sorry, I'm new to this stuff. I thought they can change the bootloader when you upgrade. Thanks for the help though
Click to expand...
Click to collapse
The bootloader does get updated. But you can unlock any bootloader, and updating it doesn't lock it again. Take a look at my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Oh, because i was afraid of the phone won't boot because of the android n won't boot if the phone has a unlocked bootloader.
smilehead said:
Oh, because i was afraid of the phone won't boot because of the android n won't boot if the phone has a unlocked bootloader.
Click to expand...
Click to collapse
Nope, nothing like that to worry about. The locked/unlocked status won't stop it from booting.
Thanks. I can now upgrade in peace

Categories

Resources