Is it still possible?
Yup just did it before! Flashed all the way back to 4.1.26 actually! The only thing is you gotta reapply the unlock again afterwards.
Ok.
You mean the Bootloader is re-locked when you flash an SBF?
Shaydar said:
Ok.
You mean the Bootloader is re-locked when you flash an SBF?
Click to expand...
Click to collapse
Yeah seems that way at least partially.
Gutterball said:
Yup just did it before! Flashed all the way back to 4.1.26 actually! The only thing is you gotta reapply the unlock again afterwards.
Click to expand...
Click to collapse
You absolutely do not have to re-apply the unlock after.
Shaydar said:
Ok.
You mean the Bootloader is re-locked when you flash an SBF?
Click to expand...
Click to collapse
No.
Gutterball said:
Yeah seems that way at least partially.
Click to expand...
Click to collapse
I'd like to know where you heard this from Gutterball? Or did you just assume this was the case because the device no longer has "Unlocked" in the corner?
I can assure you the bootloader is still unlocked. With 100% certainty.
nexxusty said:
You absolutely do not have to re-apply the unlock after.
No.
I'd like to know where you heard this from Gutterball? Or did you just assume this was the case because the device no longer has "Unlocked" in the corner?
I can assure you the bootloader is still unlocked. With 100% certainty.
Click to expand...
Click to collapse
It may be "unlocked" but you can not flash a custom recovery or custom system until you flash the pudding sbf again. It gives an error. It has to say UNLOCKED in top left corner to get the magic flowing.
Related
I have not yet taken the plunge to unlock my runs-hot Rezound, but I had a question brought on by seeing how prolific Nils is with his releases.
I know the initial unlock wipes the phone. I also know that you cannot run a RUU to save your butt in an emergency if your phone is unlocked. From this, it makes sense to unlock, flash your rom, relock. If you have an emergency, you can RUU, and that is probably a real good way to be.
But this leaves me wondering ... anyone know if a subsequent unlock from a re-lock wipes the phone as well (because THAT would be a pain if you wanted to update a ROM).
Thanks!
jdmba said:
I have not yet taken the plunge to unlock my runs-hot Rezound, but I had a question brought on by seeing how prolific Nils is with his releases.
I know the initial unlock wipes the phone. I also know that you cannot run a RUU to save your butt in an emergency if your phone is unlocked. From this, it makes sense to unlock, flash your rom, relock. If you have an emergency, you can RUU, and that is probably a real good way to be.
But this leaves me wondering ... anyone know if a subsequent unlock from a re-lock wipes the phone as well (because THAT would be a pain if you wanted to update a ROM).
Thanks!
Click to expand...
Click to collapse
1. I think you can RUU with unlock.
2. Yes. You would have to wipe.
Thanks!
dmeadows013 said:
1. I think you can RUU with unlock.
Click to expand...
Click to collapse
Thanks for the answer! I guess its a tough decision to have to make because I am 99.9999999999999999999999999999% sure (from reading XDA very carefully and constantly) that you CANNOT run a RUU (from a PC) if your phone is in the unlocked state; meaning if you really bork it, you are stuck if you left it unlocked.
jdmba said:
Thanks for the answer! I guess its a tough decision to have to make because I am 99.9999999999999999999999999999% sure (from reading XDA very carefully and constantly) that you CANNOT run a RUU (from a PC) if your phone is in the unlocked state; meaning if you really bork it, you are stuck if you left it unlocked.
Click to expand...
Click to collapse
Ah. You should be able to flash the HBOOT RUU with unlock. They are posted in my Root Thread in Development
Hi guys (=
I unlocked my bootloader via testpoint. It's clear to me that I can't do OTA updates now (afaik, I'd appreciate opposing information). But is it still possible to update via SUS/PCC. In my opinion with official unlock, it's impossible to do a repair/update via SUS/PCC (denied by program in advance). But with testpoint-unlocked bootloader I'm given the possibility to do a repair. Can I do it without any danger for my phone?
So long,
mar_sss
mar_sss said:
But with testpoint-unlocked bootloader I'm given the possibility to do a repair. Can I do it without any danger for my phone?
Click to expand...
Click to collapse
Yes.
But no OTA update, right?
i update 4.04 through OTA...but not successfull.i have to relock bootloader and unlock again with test point...
mar_sss said:
But no OTA update, right?
Click to expand...
Click to collapse
Unlocked bootloader by test point not affect any updades! If you not delete or replace any system file, OTA update should be right!
mar_sss said:
But no OTA update, right?
Click to expand...
Click to collapse
Better not try.
Lietotajs said:
Unlocked bootloader by test point not affect any updades! If you not delete or replace any system file, OTA update should be right!
Click to expand...
Click to collapse
Actually, I'm not 100% sure in that. Some users reported problems.
I didn't try as I never seen a need for ota, have you tried it?
didn't try it. no need till now, because I unlocked with testpoint and installed/rooted .432
i was testpoint unlocked but then i needed alot of relocking and unlocking for testing stuff so testpoing procedure became so damn boring. bite the dust and did the official unlock, now relock/unlock is fast and easy.
official way unlock -> relock -> OTA. no brick. thats how i got from 4.0.3 to 4.0.4
all i lost is DRM (and warranty ofc ..), but havent seen any situation that i need DRM in first place.
pirate mp3's yar yar
Gjole86 said:
i was testpoint unlocked but then i needed alot of relocking and unlocking for testing stuff so testpoing procedure became so damn boring.
Click to expand...
Click to collapse
May I ask what could be the reason to relock BL?
Except OTA. But then again, OTA is kinda useless, IMHO.
Madfysh said:
May I ask what could be the reason to relock BL?
Except OTA. But then again, OTA is kinda useless, IMHO.
Click to expand...
Click to collapse
i had this funky stuff when i flash tft it wont boot. it ended in bootloop or just stuck on SE writing. did a relock and it went on. have no idea why is that but i took it as "dont fix if its not broken"
yeah logic says lock BL-> stock kernels only. unlock BL -> all kernels.
makes no sence i know just the way things work arround here. same as the wifi crap i have on ICS, so few other ppl have the same thing.
Due to a soft brick and the recovery from it I ended up with a locked bootloader now with MJ9. I have re-rooted but cannot flash anything like the modded framework.
What are my options now? (I do have unlimited)
khw1959 said:
Due to a soft brick and the recovery from it I ended up with a locked bootloader now with MJ9. I have re-rooted but cannot flash anything like the modded framework.
What are my options now? (I do have unlimited)
Click to expand...
Click to collapse
This might do the trick for you.
http://forum.xda-developers.com/showpost.php?p=49326229&postcount=21
jcollier said:
This might do the trick for you.
http://forum.xda-developers.com/showpost.php?p=49326229&postcount=21
Click to expand...
Click to collapse
Thank you! I will pursue that.
Hi, I literally opened the nexus 9 out of the box, powered it on & after choosing a wifi network it began updating, the device crashed during this update and now it won't boot! I've tried & searched for everything, anyone have any ideas?
Booting to recovery with HW buttons, wiping cache/userdata/factory reset - Nada!
Can boot into fastboot, no permission to flash as oem unlock is disabled!
I cant get into the tablet to unlock fastboot oem unlock within devOpitons or usb debugging etc, (com.android.phone has stopped on boot) black screen indefinitely.
I can't flash any images while it is locked
surely there must be a simple method?
desperate here
Return it
I'd just return it. I'm no expert, but I'd seek a way to avoid the update during setup and try to postpone it until you unlock developer options and OEM unlock. I'm not sure how you'd bypass the update during setup, but you're in the right place if it's possible.
VermontKindBud said:
I'd just return it. I'm no expert, but I'd seek a way to avoid the update during setup and try to postpone it until you unlock developer options and OEM unlock. I'm not sure how you'd bypass the update during setup, but you're in the right place if it's possible.
Click to expand...
Click to collapse
Hmm, its one of works, just bought bulk amount of them. surely it can't be stuck in an unescapable cycle?
syko9 said:
Hmm, its one of works, just bought bulk amount of them. surely it can't be stuck in an unescapable cycle?
Click to expand...
Click to collapse
Certainly it can. If it started to install the 5.0.2 OTA, there have been a lot of bricks.
cam30era said:
Certainly it can. If it started to install the 5.0.2 OTA, there have been a lot of bricks.
Click to expand...
Click to collapse
Alright thanks for the info, guess it shall be replaced thanks.
syko9 said:
Alright thanks for the info, guess it shall be replaced thanks.
Click to expand...
Click to collapse
Welcome. And FWIW: there's a button for that.
If I remember correctly you can still flash the stock images even with the boot loader locked. Its only custom images that google will not accept unless you unlock boot loader.
Ripx88 said:
If I remember correctly you can still flash the stock images even with the boot loader locked. Its only custom images that google will not accept unless you unlock boot loader.
Click to expand...
Click to collapse
Bootloader has to be unlocked to "fastboot flash" anything.
You can sideload an OTA with a locked bootloader, but you have to be able to access recovery.
cam30era said:
Bootloader has to be unlocked to "fastboot flash" anything.
You can sideload an OTA with a locked bootloader, but you have to be able to access recovery.
Click to expand...
Click to collapse
Ah ok gotcha. My apologizes, I thought I heard somewhere you could. Thank you for the correction.
Ripx88 said:
Ah ok gotcha. My apologizes, I thought I heard somewhere you could. Thank you for the correction.
Click to expand...
Click to collapse
No problem. That's how we learn.
cam30era said:
No problem. That's how we learn.
Click to expand...
Click to collapse
Indeed I'm still new to nexus devices. I've been flashing on Samsung devices for years so I'm still stuck in my Odin ways. Just got the N9 less then a week ago. The whole fastboot thing was foreign at first but I'm getting there lol. Thank you again.
So, long story short, I recently bought a Nexus 9 from ebay which arrived with factory reset protection.
I have spoken to both Google and HTC about the situation and both were of no real help except for saying a few things outright between them to give me good enough reason to believe one of two things.
That 1 - it is possible to flash factory images over a device with a locked bootloader
or 2 - it is possible to unlock the bootloader without having access to developer settings
Anyone have any experience with either of these possibilities?
https://developers.google.com/android/ota
Full OTA Images can be flashed onto devices with locked boot loaders.
You need to boot into recovery and select sideload update.
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
enriquejones666 said:
https://developers.google.com/android/ota
Full OTA Images can be flashed onto devices with locked boot loaders.
You need to boot into recovery and select sideload update.
Click to expand...
Click to collapse
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
BigDomTheFirst said:
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
Click to expand...
Click to collapse
Those are full ota images, same as factory image. Meaning full package.
BigDomTheFirst said:
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
Click to expand...
Click to collapse
Ah yes, now I see your predicament. Unfortunately, there is no "there" there. You do need an unlocked bootloader to wipe the system clean with a factory image, and as you noted, the Full OTA Image will recover you from a system that won't boot, but it won't get rid of FRP.
enriquejones666 said:
Ah yes, now I see your predicament. Unfortunately, there is no "there" there. You do need an unlocked bootloader to wipe the system clean with a factory image, and as you noted, the Full OTA Image will recover you from a system that won't boot, but it won't get rid of FRP.
Click to expand...
Click to collapse
Exactly Hence my questions as to how do the manufacturers wipe everything and flash the new image without unlocking the bootloader? Or will it always be a trade secret?...... Hmmmm
BigDomTheFirst said:
Exactly Hence my questions as to how do the manufacturers wipe everything and flash the new image without unlocking the bootloader? Or will it always be a trade secret?...... Hmmmm
Click to expand...
Click to collapse
did we ever fix this? my bootloader is locked and no os installed. Was trying to return to factory and went thru all the flashing steps successfully then at the end locked the bootloader. Now tablet says "for development purposes only not for production use" and boots back to fastboot. It will not reboot at all
Uncleheff said:
did we ever fix this? my bootloader is locked and no os installed. Was trying to return to factory and went thru all the flashing steps successfully then at the end locked the bootloader. Now tablet says "for development purposes only not for production use" and boots back to fastboot. It will not reboot at all
Click to expand...
Click to collapse
Never found out how they do this.... are you able to boot in to recovery? if you can do that you may be able to flash a recovery OTA through 'apply update from ADB'. Worth a shot
Uncleheff said:
did we ever fix this? my bootloader is locked and no os installed. Was trying to return to factory and went thru all the flashing steps successfully then at the end locked the bootloader. Now tablet says "for development purposes only not for production use" and boots back to fastboot. It will not reboot at all
Click to expand...
Click to collapse
If up dont mind my asking how did it get that way by just locking the bootloader? I was just about to flash stock and lock on my volantis, then read this...?
Bryanx86 said:
If up dont mind my asking how did it get that way by just locking the bootloader? I was just about to flash stock and lock on my volantis, then read this...?
Click to expand...
Click to collapse
definitely don't lock your bootloader. That is a horrible move and serves no purpose
madbat99 said:
definitely don't lock your bootloader. That is a horrible move and serves no purpose
Click to expand...
Click to collapse
I actually reflashed last factory stock image and relocked without issue. It is a horrible move, I agree...I already miss root, but it suits the purpose. Thanks for your reply.
Bryanx86 said:
I actually reflashed last factory stock image and relocked without issue. It is a horrible move, I agree...I already miss root, but it suits the purpose. Thanks for your reply.
Click to expand...
Click to collapse
it's only a bad move if you make a mistake and can't repair it because your bootloader is now locked. But if it goes well then you're all set.