Hi all,
By follow the sony open device aosp build instruction with all the steps successfully.
https://developer.sony.com/develop/...structions/build-aosp-android-android-11-0-0/
But when starting the phone, it shows an error message and nothing more
`Your device software can't be checked for corruption. Please lock the bootloader.`
{
"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"
}
So I try to relock the bootloader, it did shows that the device already unlocked
but when I try to lock, it shows 'unknown command'
Any ideas? thanks
Hey. Just a heads up--the screen notifying about unlocked bootloader is normal. Since unlocking the bootloader I get the same notification during startup and then it boots normally into the ROM. Whatever the startup issue is, I wouldn't conclude it's caused by unlocked bootloader based off that screen.
In regards to the issue with relocking the bootloader, I had ran into a similar nondescript error with adb while trying to flash TWRP, it read 'FAILED (Status read failed (No such device))' and after a lot of googling I found that the solution is to try different computers/USB ports. In my case I had to use another laptop's USB port while running Linux/EndeavourOS from thumb drive (fastboot was/is unreachable under Windows for my XZ1c).
upd. Oh, it seems relocking the bootloader is not as easy as fastboot oem lock. Nevermind.
I'm not sure which question you're asking.
If it's that you see the message, it's normal, because you (or someone else) unlocked your bootloader. It's normal, and a warning (not an error), not a sign that anything's broken. But you maybe want to check your ROM or recovery, if you weren't the one who installed them, or you don't trust the person that did.
If it's that you can't re-lock the bootloader, that's ... also expected. You can't. No one has found a way to re-lock the bootloader on the XZ1 compact. So that command will always fail. It's not supported on your phone.
If the phone won't boot or is broken, it's likely for some other reason.
Related
Yo.
After countless hours of just trying to unlock the damn fastboot/hboot whatever, I finally did it, flashed the recovery, then a custom OS. But I forgot to do the hboot downgrade s-off thing, and now it's stuck on the HTC logo and doesn't boot. I was supposed to try the IncS Downgrade script http://forum.xda-developers.com/showthread.php?t=1373697
But this requires me to be booted up in a rom, which is kinda silly I guess because it restarts into fastboot afterwards.
But anyway, phone doesn't get recognized on the script when I'm allready in fastboot, and I've been trying all kinds of fixes and I'm about to lose it.
So I'm giving up and asking if anyone got a solution while I still got some of my sanity left :silly:
{
"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 all I'm seeing atm.
ruckus92 said:
Yo.
After countless hours of just trying to unlock the damn fastboot/hboot whatever, I finally did it, flashed the recovery, then a custom OS. But I forgot to do the hboot downgrade s-off thing, and now it's stuck on the HTC logo and doesn't boot. I was supposed to try the IncS Downgrade script http://forum.xda-developers.com/showthread.php?t=1373697
But this requires me to be booted up in a rom, which is kinda silly I guess because it restarts into fastboot afterwards.
But anyway, phone doesn't get recognized on the script when I'm allready in fastboot, and I've been trying all kinds of fixes and I'm about to lose it.
So I'm giving up and asking if anyone got a solution while I still got some of my sanity left :silly:
This is all I'm seeing atm.
Click to expand...
Click to collapse
Extract boot.img from custom Rom zip file, place in PC's fastboot directory. Enter fastboot mode on phone. Type
Code:
fastboot flash boot boot.img
and restart.
THAAAAAAAAAAAAAAAAAAAAAAAAAANK YOOOOOOOOOUUUUUUUUUUUUUUUU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! that just made my day bro:good:
I have the same problem ... I did that but when I restart I must do it again !!
Sent from my Incredible S using xda premium
Fshtiwi said:
I have the same problem ... I did that but when I restart I must do it again !!
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
Make sure you are typing the command correctly and not just fastboot boot boot.img
Here is the situation I have an HTC ONE (M7) Here which does absolutely nothing but show this message...
It does not have usb debugging enabled and adb will not register it. I can however connect to it via fastboot....
Ive gotten as far as unlocking the bootloader... But now cannot seem to get any further as everything I have read uses ADB and i cannot get it to recognize ADB Device.
Basically from what i am reading.... Is flash custom recovery such as TWRP (Which i have downloaded) and i want to just reinstall stock rom etc. Not trying to root or anything here, just simply trying to reinstall factory software for HTC One (M7) - Telus Canada to hopefully resolve the issue.
Please any help is greatly appreciated I have been up now for nearly 20 Hours trying to get this done.
Exactly like this
dugie33 said:
Here is the situation I have an HTC ONE (M7) Here which does absolutely nothing but show this message...
It does not have usb debugging enabled and adb will not register it. I can however connect to it via fastboot....
Ive gotten as far as unlocking the bootloader... But now cannot seem to get any further as everything I have read uses ADB and i cannot get it to recognize ADB Device.
Click to expand...
Click to collapse
Because you are boote din bootloader mode. ADB can't work when in bootloader mode, only from custom recovery or from a booted rom + usb debug on. Here a nice table I made last week to explain the same thing to another guy:
{
"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"
}
Basically from what i am reading.... Is flash custom recovery such as TWRP (Which i have downloaded) and i want to just reinstall stock rom etc. Not trying to root or anything here, just simply trying to reinstall factory software for HTC One (M7) - Telus Canada to hopefully resolve the issue.
Click to expand...
Click to collapse
Post the output of "fastboot getvar all" (remove your imei and sn before posting)
So before I start I just wanted to say that I have been rooting and installing roms back at the time when I had my galaxy s3, I knew this stuff before upgrading to my nexus 6.
So the problem as you can see on the title that I cant unlock the oem option, means I cant unlock my bootloader, but there is a twist.
When I bought my nexus, I remember it was 5.0, and there was an update to 5.1, the update was OTA, and I remember the update had problems, it couldn't finish and the phone stayed on 5.0 and you could not
update to 5.1 unless you flash 5.0 again. So I unlocked my bootloader back at the time, and installed 5.0 all over again, and everthing was fine until now(now I am on 7.0)
Now I want to root my phone and install things and I cant do that, because of the oem options, but when i go into fastboot it says device is unlocked, and when I turn my phone on under the google sign there is small open lock sign that I know tells the bootloader is unlocked.
So there is my problem, I cant root it and so on, very sorry of the long post but I think it was necessary so I could explaine my problem.
{
"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"
}
Not quite sure what your problem is. Your bootloader is already unlocked, you just flash twrp via faatboot
Code:
faatboot flash recovery nameoffile.img
then flash SuperSU. If it asks for a password, or you can't find any files on your device in twrp, that means you're encrypted, and will have to completely wipe data on device. You do that by hitting cancel (if it's asking for a password) then go to wipe. Then select format. You'll have to type yes. Now you'll be unencrypted.
As a side note, you may be able to get away with just flashing twrp, and then sideloading the SuperSU zip
dictionary said:
Not quite sure what your problem is. Your bootloader is already unlocked, you just flash twrp via faatboot
Code:
faatboot flash recovery nameoffile.img
then flash SuperSU. If it asks for a password, or you can't find any files on your device in twrp, that means you're encrypted, and will have to completely wipe data on device. You do that by hitting cancel (if it's asking for a password) then go to wipe. Then select format. You'll have to type yes. Now you'll be unencrypted.
As a side note, you may be able to get away with just flashing twrp, and then sideloading the SuperSU zip
Click to expand...
Click to collapse
Thank you very much, apparently it worked even if the oem option is not available, hope I wont get into more troubles.
Hello, what I did was the following:
1. signed on a new phone with account A, waited a week and unlocked the bootloader
2. signed on the same phone with account B
3. flashed fastboot rom on the device with mi flash tool, but forgot to uncheck the " lock the bootloader"
4. the phone is not starting - i can only get the recovery and the fastboot mode.
5. mi flash tool wont let me flash to locked device . Mi flash tool2 makes me go into Mi assistant mode, starts the instalation process but failes after a few mins ( on the pc i reach ~ 700% but on the phone the bar is on 4.99 or 52.78 % )
6. Xiaomi ADB/Fastboot Tools doesnt want to flash as the device is locked and if i try the OEM UNLOCK button i get "FAILED (status read failed (Too many links))"
7. If I try to unlock the bootloader again and I log account B i get message that i need to log on the phone and wait for a week
If i log accont A i get 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"
}
Any Idea how to fix it
Thanks in advance, and sorry if this is the wrong place for this question
As far as I know, the only way is to ask after-sale for help.
ddspj said:
As far as I know, the only way is to ask after-sale for help.
Click to expand...
Click to collapse
They might have more underlying tools to unlock and flash your phone.
fastboot flashing unlock
for most of aosp rom this is the command. but i'm not sure that works on miui. i found a java tool that maybe can help you. https://miui.blog/any-devices/xiaomi-adb-fastboot-tools-one-utility/ i have used to debrand my phone without unlock it
I had to send it to a friend of mine who was able to install chaina rom, using EDL mode, but now, for some reason the IMEI's are gone. I can not add mi account, and for that reason I can't unlock the bootloader, right now I am battaling with the IMEI restoration ( i have the original imei's on the phone case) I am trying to use modem_meta_tool, but with no suxcess . I can't get my phone connected
Long story short, EDL mode was needed to get out of my original situation
seem you have lost imei cause you have installed china rom. or a rom incompatible with your region. try install global rom via edl. but if you lost imei, restore it is not simply... you can try to enter into engineering mode. i'm not sure but there's a function to change imei. but not working for all mtk processors
Hello,
I've been trying to install Pixel Experience on my phone following these guides
Install PixelExperience on NB1 - PixelExperience Wiki
Install PixelExperience on NB1 - PixelExperience Wiki
wiki.pixelexperience.org
Nokia 8 (NB1) Full ROM Installation Guide
In this guide, you will find: What you should do before installing a custom ROM on your Nokia What are the button combinations of Nokia 8 for reboot to download mode, recovery mode, and etc How to install T-Virus (project treble) on Nokia 8 How...
forum.xda-developers.com
Just as described I've downloaded Nokia drivers. My phone already had unlocked bootloader via official HMD method so i went over to the next step and T-Virus.
I entered fastboot sucesfully by enabling USB debugging. Downloaded T-Virus from the guide link and executed Windows command. Followed all steps in command window.
During the process I've noticed repeating error "Invalid sparse file format at header magic" if it's important.
Anway it finished and said that my phone will enter ROM now but after restarting it's back at bootloader.
I tried entering recovery via key combinations but they won't work.
I can detect my phone in fastboot and even when i type in
fastboot reboot recovery
It will still reboot into download mode.
Any help appreciated how to get my phone to work again.
Okay, crisis averted, I reverted T-Virus and now i can boot to android again.
But I still want to know why T-Virus failed and cause bootloop on my device?
I've noticed that despite having unlocked bootloader my critical is locked. Could t
{
"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"
}
his be the source of issue?
Yup that was it.
I had to repeat fastboot flash unlock unlock.key and then fastboot flashing unlock_critical to get critical unlocked and now T-Virus installed without any issues.
Hey got the same problem, how did you revert and unlock critical?