Question Error in locking bootloader. - Google Pixel 6

Hi I am getting an error when trying to relock the bootloader, I reboot into bootloader put in the command to lock "Fastboot flashing lock" get the error below in the image. Any idea why?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Have you restored the full stock firmware? If not then do that first using: https://pixelrepair.withgoogle.com/carrier_selection

foobar66 said:
Have you restored the full stock firmware? If not then do that first using: https://pixelrepair.withgoogle.com/carrier_selection
Click to expand...
Click to collapse
I don't recommend using the Pixel Repair Tool unless absolutely necessary.
If you are trying to return your device to absolute stock, I recommend using the Android Flash Tool. You can choose which factory build to flash, whether to wipe the device, and whether to relock the bootloader.

aymuhamm said:
Hi I am getting an error when trying to relock the bootloader, I reboot into bootloader put in the command to lock "Fastboot flashing lock" get the error below in the image. Any idea why?
View attachment 5475895
Click to expand...
Click to collapse
It is likely that you rooted your phone at one point, or perhaps flashed an alternative operating system which does not support verified boot.
Traditionally but not in all cases, re-locking your bootloader requires you to be unequivocally 100% stock. If you plan on being on stock and you are not (which I am assuming), you can either follow the # Flashing Instructions steps on the Nexus/Pixel Factory Images page. If you find that a bit tedious, there is always the flash-all.sh/flash-all.bat which will do this all for you.
After this, your device will be set straight back to factory, and you can follow the steps to re-lock your bootloader.

VozerCozer said:
It is likely that you rooted your phone at one point, or perhaps flashed an alternative operating system which does not support verified boot.
Traditionally but not in all cases, re-locking your bootloader requires you to be unequivocally 100% stock. If you plan on being on stock and you are not (which I am assuming), you can either follow the # Flashing Instructions steps on the Nexus/Pixel Factory Images page. If you find that a bit tedious, there is always the flash-all.sh/flash-all.bat which will do this all for you.
After this, your device will be set straight back to factory, and you can follow the steps to re-lock your bootloader
Click to expand...
Click to collapse
This is why I like to recommend the Android Flash Tool - simply from a perspective of ease of use, and the fact it's practically impossible to get wrong; additionally, the user can elect to lock the bootloader during the process when choosing the flash options. This removes the need to do anything else manually; the tool takes care of the entire process.
It's also very useful for updates.

Related

[Q] Atrix 4G Update Error

All I get is this screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please help its been like that for awhile after the update is done downloading and I try to install it!
Sent from my HTC Sensation 4G using XDA App
it seem you have some mods in /system or /webtop partition
Did you ever unlock your bootloader?
ATT right?
mramirezusa said:
it seem you have some mods in /system or /webtop partition
Did you ever unlock your bootloader?
ATT right?
Click to expand...
Click to collapse
if you Answer are NO
and YES
this is the way to do it follow this link and you need a PC and your phone attached to it by USB:
"http://direct.motorola.com/hellomoto/motosupport/source/SoftwareUpdateSummary.asp?country=USA&language=ENS&web_page_name=SUPPORT&strCarrierId=ATT&strPhone=Motorola%20ATRIX%28TM%29%204G&strCable=Micro%20USB%20Data%20Cable&strURL=https://rsddownload.motorola.com/download/SoftwareUpdateforATTATRIX4Gversion.4.5.91.pdf"
I believe i just rooted it with gingerbreak but then i followed this tutorial: http://atrix4ghacks.com/atrix-4g-hacks/how-to-enable-webtop-without-laptopusb-dock/
it edited my webtop stuff so how do i fix it so i can update
lol don't panic! (....I have a towel =D)
You just entered the recovery menu. To see the error message, you need to un-hide it by touching the screen on the bottom right corner (right above the search button). This will show you what error you encountered.
If you're OTAing up, then you probably had Titanium or something that removed bloatware or modded the system with a theme or custom files. If that's the case, any OTA will fail because you will not have passed the pre-install check. You have three options:
1.) Go here and get the Automated Upgrade for PC Users. That will allow you to upgrade and bypass the test, while also keeping your data. This doesn't require any mods or unlocked bootloaders. (BE WARNED THAT IF YOU USE THIS, YOUR BOOTLOADER WILL BE BLOWN. DON'T DOWNGRADE WITH SBFs AND STICK TO EATING YOUR FRUITCAKE! However, Radio and Bootloader SBFs are still considered safe. As any wise man would do, proceed with caution.)
OR
2.) Unlock your bootloader, install CWM from Tenfar, and then get KP's 2.3.4 ROM Beta 4 and put it in your SD card. Boot up CWM and install it. That easy. =] (BE WARNED SOME PEOPLE BRICKED THIS WAY.)
ORRRRRR
3.) Using the fastboot from Motorola and unlocking your bootloader, just flash the images here. (Currently the best method and seems to produce the best results, but if you don't know how to do it, then don't do it.)
If you need instructions on how to do any of the above, use this noob bible. And lastly, if you want to root, use the preinstall method (also in bible.)
Happy upgrading!
~jojojohnson7410~
I had the same problem and also had only used gingerbreak and webtop mod. I tried using pc update software but it thought I was on orange france (mine is AT&T) so I didn't proceed. Decided to flash the gingerbread plus pudding sbf in pudding thread, worked perfect and kept all data, you don't need to unlock bootloader before updating
Same problem
I'm having the exact same problem.
Except my bootloader is unlocked.
Any help would be greatly appreciated.
Thanks!

[SEEK] Thread with complete explanations on custom rom protocol installation

Hello there, I won't lie, I ask for help, you answer me.
I don't understand enought your method, because it's not well described.
But.. Therefore...
I'm able to root my device.
I'm able to backup my ta partition or my drm keys.
I'm able to unlock my bootloader.
I'm able to restore my bootloader to lock it back.
i'm able to unbrick my phone when it couldn't boot via flashtool.
Click to expand...
Click to collapse
But I'm unable to install a custom recovery and or even launch the stock on it there was one.
I tried this method: http://forum.xda-developers.com/showthread.php?t=2647492 (normal boot and no pink led).
I tried this method: http://forum.xda-developers.com/showthread.php?t=2799388 via flashtool and my phone couldn't boot, even to the SONY logo, but it were vibrating when pushing on the power button.
Anyway, I flashed via flashtool the 14.4.A.0.108 back, now I'm still rooted and the bootloader is still unlocked.
Click to expand...
Click to collapse
What can I do to install a custom recovery via the 14.4.A.0.108 ?
Or this operation is impossible and I have to downgrade ?
(I read about downgrade and I'm affraid to lose my IMEI)
Click to expand...
Click to collapse
Thank you for your glorious complete explanations.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm pretty sure the problem here is that there is a stock firmware development aka the custom ROMs can't just start "taking over from where the devs left off" like it happened with Samsung Devices that get stuck at v4.1.2 unless someone else does something about it.
I guess most things here just are not stable. I hope the stock works out for you. Did you get the rooting done? I found a video tutorial for that here http://forum.xda-developers.com/xpe...de-root-android-4-4-4-ver-14-4-0-108-t2801587
Zhuinden said:
I'm pretty sure the problem here is that there is a stock firmware development aka the custom ROMs can't just start "taking over from where the devs left off" like it happened with Samsung Devices that get stuck at v4.1.2 unless someone else does something about it.
I guess most things here just are not stable. I hope the stock works out for you. Did you get the rooting done? I found a video tutorial for that here http://forum.xda-developers.com/xpe...de-root-android-4-4-4-ver-14-4-0-108-t2801587
Click to expand...
Click to collapse
Hello, of course I have done rooting, now I'm back in full stock, nk rooting, just pure sony beauty. And everything works better without root, or it doesn't matter, but the navigation and the use of the device is much smoother without lags

"This is a development device not intended for production use"

Hello,
After unrooted and re-locked (bootloader) my Nexus 9.
When i boot it, i got this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"This is a development device not intended for production use"
After that, I have flashed the stock rom 6.0.1,so I'm 100% stock now, but I still get this message when the device boot
Is it a bug, or my seller sold me a tablet supposed to be not sold?
Do you think I can ask for a replacement? Because I would like to sell it and buy a other tablet... But with this weird message at the boot, I can't expect a lot from it...
Thanks
Strange. I am interested and want to know more.
The warning only recently appeared?
dmantilal said:
Strange. I am interested and want to know more.
The warning only recently appeared?
Click to expand...
Click to collapse
Just after re-locked my device. So i have unlocked it again to flash the last 6.0.1 stock rom, locked the bootloader, and the red message is still here. But I have seen that, if I unclock the bootloader, the message disappears, and if I lock it, the message appear... Strange.
One other thing, (with bootloader locked), I have an ota update, 7,7mb, but when I update, it fail each time
So if I send it to HTC, I think they will change it with a new one, because even with a factory reset, flash stock rom, I don't know what more they can do.
And I have light bleed on the screen, so i really hope they will give me a new one!
That's strange. I don't know whether that red message appears even if you lock the bootloader with everything being stock, but you may try this method: http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
Edit: If OTA update fails, your device may not be completely stock. Try troubleshooting by consulting the recovery log, or use the "flash-all.bat" to flash stock ROM again.
LeoYL said:
That's strange. I don't know whether that red message appears even if you lock the bootloader with everything being stock, but you may try this method: http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
Edit: If OTA update fails, your device may not be completely stock. Try troubleshooting by consulting the recovery log, or use the "flash-all.bat" to flash stock ROM again.
Click to expand...
Click to collapse
Ok thanks for your help
I have send an email to HTC to ask for a replacement. I have seen that some people who got the same issue, (even without root or unlock bootloader) got a replacement :fingers-crossed: . And I have ugly light bleed on the screen, so I really hope I will got a replacement too
If the OTA fails then you aren't full stock..
DITTO to downloading the google stock image and flashing using the included flash-all.bat.

Can't flash any Rom - "assert failed: oppo.very_trustzone ERROR 7"

I'm currently on CM 13.0-20160809-NIGHTLY-onyx and I've tried to flash three different Roms on my phone (Two different versions of cm14 and OOS3) with TWRP. But every time I get the error message attached in the screenshot.
Now, I've seen a few people online having similar problems, but it was mostly for cm12 and the suggested fixes are not really helpful for my situation.
I've somehow lost my stock backup so I'm kinda lost right here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In general Error 7 usually means you're using the wrong version of TWRP. I'm still using Blu_Sparks version for the new bootloader.
quoakkaflocka said:
I'm currently on CM 13.0-20160809-NIGHTLY-onyx and I've tried to flash three different Roms on my phone (Two different versions of cm14 and OOS3) with TWRP. But every time I get the error message attached in the screenshot.
Now, I've seen a few people online having similar problems, but it was mostly for cm12 and the suggested fixes are not really helpful for my situation.
I've somehow lost my stock backup so I'm kinda lost right here.
Click to expand...
Click to collapse
You need to upgrade your bootloader and TWRP.you are using very old CM and now everything is changed so upgrade your boot loader and recovery.
I already use TWRP 3.0.2-0 which is the newest version according to TWRP Manager.
How do I upgrade my bootloader?
Edit: So I found this way to do it :Link
The thing is: it says the bootloader must be unlocked, but if I type "fastboot devices" I get nothing back. "adb devices works. I'm pretty sure that my bootloader is unlocked since I have a custom rom and my device is rooted but I'm not sure if I have activated the CM recovery option in the developer settings ever since.
I really don't wanna brick my phone so I'm not sure if I should blindly follow the steps in the link above.
quoakkaflocka said:
I already use TWRP 3.0.2-0 which is the newest version according to TWRP Manager.
How do I upgrade my bootloader?
Edit: So I found this way to do it :Link
The thing is: it says the bootloader must be unlocked, but if I type "fastboot devices" I get nothing back. "adb devices works. I'm pretty sure that my bootloader is unlocked since I have a custom rom and my device is rooted but I'm not sure if I have activated the CM recovery option in the developer settings ever since.
I really don't wanna brick my phone so I'm not sure if I should blindly follow the steps in the link above.
Click to expand...
Click to collapse
"fastboot devices" doesn't work unless you are in the bootloader

Question Error when trying to unlock bootloader

Hi all.
I'm trying to unlock the bootloader of my 8 Flip but am having a couple of issues. First one is that there's no "OEM Unlock" option in my Dev settings. I've tried running the official unlock tool anyay, and it errors out saying "Failed to unlock your device, please try again later.[11006]"
Any ideas?
Thanks.
Solved it - Just had to turn wifi off and use mobile data and it worked
My friend has an error code when unlocking the Bootloader. Do you know why?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Why are you trying to unlock the bootloader? Are there custom roms available?
lew4man said:
Why are you trying to unlock the bootloader? Are there custom roms available?
Click to expand...
Click to collapse
To root the phone
where did you buy the phone? Some vendors sell phones that cannot be rooted.
You can see it with the app CPU-Z in System section if you see bootloader : no, you can't root
I was just about to unlock the bootloader to try to dump the recovery.img and use that to create a twrp image.
But there is a big warning saying:
Before you download, install, and use the Unlock Device App (“Service”), you understand that you need to take all risks in terms of quality and performance of the Service, including but not limited to: once you trigger the Service, you’re not able to recover your ASUS products to the original status at the time of manufacturing (“Original Product”) anymore. Original Products which is used with the Service (“Changed Product”) will no longer be regarded as the Original Products. The software updates will not be available to the Changed Product, and the digital content in the Changed Product may no longer be used. (...)
Click to expand...
Click to collapse
Does this mean I would not get security updates and later the Android 13? I only want to get twrp to be able to root the device. but losing the OS updates would be a big no-no.
Are those who have unlocked it getting updates? Can anyone confirm this?
iceinsight said:
I was just about to unlock the bootloader to try to dump the recovery.img and use that to create a twrp image.
But there is a big warning saying:
Does this mean I would not get security updates and later the Android 13? I only want to get twrp to be able to root the device. but losing the OS updates would be a big no-no.
Are those who have unlocked it getting updates? Can anyone confirm this?
Click to expand...
Click to collapse
Would also like to know the answer to this. Did you ever find out?

Categories

Resources