Related
Have installed the 4.2 update via recovery and locked the bootloader. Will I now get future OTA updates from google?
Sent from my GT-N7100 using xda premium
Retroglide08 said:
Have installed the 4.2 update via recovery and locked the bootloader. Will I now get future OTA updates from google?
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
The bootloader being locked or unlocked makes no difference. We typically see people OTA update fails from people who have modified system apps/files or installed a different kernel.
Ah ok. I had previously rooted it. But decided to revert back now that I have installed 4.2
Sent from my GT-N7100 using xda premium
Unlocking Bootloader
So, can you unlock the bootloader on 4.2? Or does it even matter on what Android version you are on?
Thanks and Cheers!
ErnestoV31 said:
So, can you unlock the bootloader on 4.2? Or does it even matter on what Android version you are on?
Thanks and Cheers!
Click to expand...
Click to collapse
It's a Nexus. Of course you can unlock the bootloader.
veeman said:
It's a Nexus. Of course you can unlock the bootloader.
Click to expand...
Click to collapse
Yeah, but is the method for unlocking it on 4.2 different from the method on 4.1.1?
Sorry Im asking all these questions, rooting is a bit different from jailbreaking lol
ErnestoV31 said:
Yeah, but is the method for unlocking it on 4.2 different from the method on 4.1.1?
Sorry Im asking all these questions, rooting is a bit different from jailbreaking lol
Click to expand...
Click to collapse
Haha, no. The method is still the same. And I suspect it will be the same for a while to come.
Oh and welcome to the Android world
The bootloader is unrelated to the version of Android you are running.
It is a " boot loader" that runs before the operating system is loaded.
Unlock it once, when you first get the device - and it should stay unlocked forever.
Nothing to do with root either - except the bootloader has to be unlocked to root the device.
Root and unroot the device as you like - just never mess with the bootloader after you unlock it.
Unlocking purges all your files...
ErnestoV31 said:
Yeah, but is the method for unlocking it on 4.2 different from the method on 4.1.1?
Sorry Im asking all these questions, rooting is a bit different from jailbreaking lol
Click to expand...
Click to collapse
fastboot oem unlock
It hasn't changed since the first Nexus device and won't be changing any time soon.
Welcome to an open platform
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!
So I did the root keeper wrong and updated, losing root. Anyone else in this club with me? It's only been a few hours and I already miss it.
Atleast I have better pictures though....
Sent from my XT1058 using xda app-developers app
You could reflash the software back to before the update with the KXZ firmware and try the process over again. Depends if the hassle is worth it to you.
http://forum.xda-developers.com/showthread.php?t=2411618
Abyssul said:
You could reflash the software back to before the update with the KXZ firmware and try the process over again. Depends if the hassle is worth it to you.
http://forum.xda-developers.com/showthread.php?t=2411618
Click to expand...
Click to collapse
This process is just flashing the firmware through rsdlite which won't happen because it's a downgrade. I tried.
Sent from my XT1058 using xda app-developers app
Maybe this will work? http://forum.xda-developers.com/showthread.php?p=45955669#post45955669
You can't flash with fastboot? I'm new to the Android ecosystem, but there must be some way to downgrade.
freak4dell said:
Maybe this will work? http://forum.xda-developers.com/showthread.php?p=45955669#post45955669
Click to expand...
Click to collapse
just tried, did not work. fails at the boot.img
Abyssul said:
You can't flash with fastboot? I'm new to the Android ecosystem, but there must be some way to downgrade.
Click to expand...
Click to collapse
first things I tried and doesn't work
I did the update and protected root but my wifi was messed up and wouldn't turn on. I did RSDLite to downgrade and redo it all and it worked fine.
BTW I used this http://forum.xda-developers.com/showthread.php?t=2446515
Some of us didn't want root in the first place! #TeamStockMotoX :silly:
I'm confused as to why someone wouldn't just unlock their bootloader if they are going to be making changes to their system. I understand the warranty issue but who uses that? Most people go through asurion and they won't even notice. Haha
Sent from my Moto X using XDA Premium
eyeisdasteve said:
I'm confused as to why someone wouldn't just unlock their bootloader if they are going to be making changes to their system. I understand the warranty issue but who uses that? Most people go through asurion and they won't even notice. Haha
Sent from my Moto X using XDA Premium
Click to expand...
Click to collapse
Because some of us can't unlock our bootloader.
eyeisdasteve said:
I'm confused as to why someone wouldn't just unlock their bootloader if they are going to be making changes to their system. I understand the warranty issue but who uses that? Most people go through asurion and they won't even notice. Haha
Sent from my Moto X using XDA Premium
Click to expand...
Click to collapse
Just remember that Retail AT&T and Verizon and MotoMaker AT&T variants aren't able to have their boot loaders unlocked
Sent from my XT1058 using Tapatalk 4
Lost root don't care. Motorola got this phone right. I'm good with stock.
rivlez said:
I did the update and protected root but my wifi was messed up and wouldn't turn on. I did RSDLite to downgrade and redo it all and it worked fine.
BTW I used this http://forum.xda-developers.com/showthread.php?t=2446515
Click to expand...
Click to collapse
Your wifi was only screwed up within Recovery mode (write off) correct?
I have a similiar issue. Whether its affecting other things or not, i dont know.
But what do you mean you restored via RSD lite and did it all over again and it was fine?
How did you ujse RSD lite to reflash the firmware since you got the updated OTA, it wont let you downgrade
emerica243 said:
Your wifi was only screwed up within Recovery mode (write off) correct?
I have a similiar issue. Whether its affecting other things or not, i dont know.
But what do you mean you restored via RSD lite and did it all over again and it was fine?
How did you ujse RSD lite to reflash the firmware since you got the updated OTA, it wont let you downgrade
Click to expand...
Click to collapse
My wifi was messed up in any mode. It wouldn't turn on for some reason. I restored the 17.51 firmware after the botched update messed up my wifi and it worked fine and I actually ended up doing it 2 times since a titanium backup messed up my phone. I was definitely on the 17.54 update. It definitely let me downgrade. How would you like me to prove it to you?
my wifi messed up in recovery mode but lte works. Normal mode everything is fine. I am rooted now with latest update.
sravanz said:
my wifi messed up in recovery mode but lte works. Normal mode everything is fine. I am rooted now with latest update.
Click to expand...
Click to collapse
Add me in as another one with no wifi in recovery. Normal mode works just fine as well. Would be nice if there was a fix for this but just glad to still have root with the update.
Rask40 said:
Add me in as another one with no wifi in recovery. Normal mode works just fine as well. Would be nice if there was a fix for this but just glad to still have root with the update.
Click to expand...
Click to collapse
Me too. My wifi is FUBARED in recovery. It's because we don't have the new kernel and to be technical were using the old system/recovery in our "recovery mode" I think that's why it's working in the regular mode and not recovery mode..... Or that's what I understand. Though I'm probably wrong.
When I upgraded I got a failed upgrade after final boot. Although it still says the newest version. I'm tempted to RSD back like some others have just to try but I don't want a paper weight.
Sent from non rooted motoX :'(
gunnyman said:
Lost root don't care. Motorola got this phone right. I'm good with stock.
Click to expand...
Click to collapse
While I'm kind of excited to see SafeStrap out, and updated (fixes phone/data, etc...), I'm still hoping some attempt is in the works for unlock on at&t.
Regardless, there aren't any custom roms to really flash anyways.
Had I an unlocked bootloader, I'd have a custom kernel in the works, and maybe some custom roms with some TeamAcid love.
Come see, come saw... Patience wins 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
Hello friends of the XDA community. I have a Sprint unlocked variant. I'm on T-Mobile, but after September's update, I got sim invalid message. I thought this would be an easy fix to downgrade back to the previous stock Pie Firware. So I went to the Essential website and downloaded the wrong firmware and flashed it, it was open market but I have a Sprint device. Now the device just bootloops every time I try to flash the correct firmware. When I try to flash the correct firmware, it says wiping data and than it starts transfering data and a second after it reboots and bootloops. Am I doomed? Thanks guys.
Open market works fine on Sprint devices. What did you download? Did you unlock your bootloader? Unlock critical?
Thank you so much for you help. I finally got it back up and running.
ziddey said:
Open market works fine on Sprint devices. What did you download? Did you unlock your bootloader? Unlock critical?
Click to expand...
Click to collapse
Sent from my Pixel XL using Tapatalk
Maybe essential will release a fix in a few days for the relocked Sprint phones. Otherwise, if you wanted to unlock it yourself so you can run the latest update, see https://forum.xda-developers.com/showpost.php?p=77532356&postcount=20 since it sounds like you already have your bootloader unlocked.
Do you mean bootloader or sim in terms of unlocking? Bootloader is fine. I'm sim locked.
ziddey said:
Maybe essential will release a fix in a few days for the relocked Sprint phones. Otherwise, if you wanted to unlock it yourself so you can run the latest update, see https://forum.xda-developers.com/showpost.php?p=77532356&postcount=20 since it sounds like you already have your bootloader unlocked.
Click to expand...
Click to collapse
Sent from my Pixel XL using Tapatalk
With an unlocked bootloader, you can either root and flash sim-unlocked modemst images with dd, or downgrade the bootloader and use it to flash.
ziddey said:
With an unlocked bootloader, you can either root and flash sim-unlocked modemst images with dd, or downgrade the bootloader and use it to flash.
Click to expand...
Click to collapse
Is there a link for this method? Thanks!