On my Nexus One that is running OS version 2.3.4 Build GRJ22, when I try to unlock Bootloader i get an error on my N1 screen that read tells me there’s “no image or wrong image”. It flashes on the screen for a split second in about 4 rows on the upper left and then disappears. Also, on my computer, in the cmd prompt, after I enter the fastboot command listed in the instructions it just gets hung up on “” PLEASE HELP!!! I’m about to throw the damn thing against the wall.
Since unlocking the bootloader wipes the phone anyway, why not try and do a passimg restore first, to make sure everything is as it should be?
what is a passimg and how do i do it?
Look at the unroot/restore guide in the wiki...
So, why is this better or worth doing instead of unlocking Bootloader and then rooting?
It's not an alternative.
You seem to be having problems unlocking the bootloader. I doubt the problem is the fastboot executable on your PC, so I would try fixing the software on your phone instead.
It's just a hunch, but I suspect that you will have more success unlocking your bootloader after trying this...
Related
I am trying to install Amon_RA recovery on my N1.
I followed the instructions from the Full Update Guide (wiki.cyanogenmod) and from XDA (recovery RA-passion-v2.2.1 by Amon-RA who does an outstanding dev).
Checked md5sum of recovery-RA-passion-v2.2.1.img : matched
Checked md5sum of recovery-RA-passion-v2.2.1-CM.img: matched
The phone is unlocked. I use fastboot to flash the recovery. I get “Signature verify fail”.
I made a thorough search and I did not find an explanation and an answer other than for rooted phone.
I do not want to root.
I tried disabling the anti virus program. I reset the phone. I checked the installation of SDK. I checked the Environment Variables in “Advanced settings” on Widows Vista and Win7. I even checked my sanity.
I would appreciate any guidance to solve this issue.
Nexus One unlocked
S-ON HBOOT-0.35.0017 RADIO-5.08.00.04
GB 2.3.6 Kernel 2.6.35.7-59465-g42bad32 Build # GRK39F
Device recognised under ADB and Fastboot. Recovery put in android-sdk-windows/platform-tools.
__________________
Google G1 (from Frayo to ICS) - CM -7.2.0-DS
Google Nexus One - Stock
Google Galaxy Nexus - Stock
What do you mean by "the phone is unlocked"?
Network unlocked?
It's meaningless. They all come unlocked.
Bootloader unlocked?
No way. You wouldn't be getting signature verification failures.
I think you're confused by the meaning of "unlocked" term. Check if you see a padlock on your screen when colorful "X" shows. If not - your bootloader is locked.
Jack_R1 said:
What do you mean by "the phone is unlocked"?
Network unlocked?
It's meaningless. They all come unlocked.
Bootloader unlocked?
No way. You wouldn't be getting signature verification failures.
I think you're confused by the meaning of "unlocked" term. Check if you see a padlock on your screen when colorful "X" shows. If not - your bootloader is locked.
Click to expand...
Click to collapse
Thank you very much for your very helpful reply.
I am ashame and I am frustrated by not following my first idea of checking the bootlader.
When the phone was given to me as a gift my relative pointed out that it was unlocked. It was a misunderstanding because the phone was originally on T-mobile while I thought "bootlader" when he said that the phone was unlocked.
Lesson learnt.
Thank to you I see the light and the mention in red letters "unlocked" on the bootlader screen.
Try renaming to recovery.img. It's been a long time since I used N1, but I vaguely remember something about fastboot not liking names with hyphen.
Make sure you're in FASTBOOT and not HBOOT mode.
Don't have any more ideas.
OK, so I've followed the newb guide to relocking my unlocked bootloader here:
http://forum.xda-developers.com/moto-x/general/noob-guide-unroot-relock-bootloader-vzw-t2571786/page4
I had issues getting the bootloader locked but found another guide here:
https://forums.motorola.com/posts/029f68b0a0
I used the command listed in the xml file listed at the bottom of the page, adapter to my phone of course.
After a few tried I got everything transferred with fastboot and the fastboot screen on my phone now says locked. My issue now is that the phone still boots up with the Bootloader Unlocked Warning screen.
Will I still be able to upgrade with the OTA? If not, what do I need to do to get rid of this warning screen on boot so that I can upgrade?
Any help is much appreciated, and I apologize if this has already been answered somewhere, but I've been looking for the past 3 hours with no success.
-----------------------------------------------
Nevermind, this has been solved.
I was able to upgrade even with the warning screen on boot. Hopefully this helps someone.
vapor100LL said:
OK, so I've followed the newb guide to relocking my unlocked bootloader here:
http://forum.xda-developers.com/moto-x/general/noob-guide-unroot-relock-bootloader-vzw-t2571786/page4
I had issues getting the bootloader locked but found another guide here:
https://forums.motorola.com/posts/029f68b0a0
I used the command listed in the xml file listed at the bottom of the page, adapter to my phone of course.
After a few tried I got everything transferred with fastboot and the fastboot screen on my phone now says locked. My issue now is that the phone still boots up with the Bootloader Unlocked Warning screen.
Will I still be able to upgrade with the OTA? If not, what do I need to do to get rid of this warning screen on boot so that I can upgrade?
Any help is much appreciated, and I apologize if this has already been answered somewhere, but I've been looking for the past 3 hours with no success.
-----------------------------------------------
Nevermind, this has been solved.
I was able to upgrade even with the warning screen on boot. Hopefully this helps someone.
Click to expand...
Click to collapse
There was absolutely no reason whatsoever to "relock" your bootloader. In fact, it was very foolish to do this.
Glad you got it solved, but for future reference, there IS NO REASON TO EVER RE-LOCK THE BOOTLOADER.
Having an unlocked BL does NOT prevent you from taking OTAs.
What's the process for going about it? I did do a search, but didn't find anything useful. Any help would be appreciated.
Reasoning: I'm going to be upgrading and turning in the phone, so it's time to put it back to factory.
mlw4428 said:
What's the process for going about it? I did do a search, but didn't find anything useful. Any help would be appreciated.
Reasoning: I'm going to be upgrading and turning in the phone, so it's time to put it back to factory.
Click to expand...
Click to collapse
1. Go back to stock everything by following section 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
2. While in bootloader mode, use the fastboot command "fastboot oem lock"
If you're turning in the phone to Verizon, this method is okay. However, don't do this if you plan on selling the phone to someone else. If they were to try and unlock the phone again, they would most likely brick it.
According to jcase relocking the bootloader it still shows a modified status code. Your warranty is permanently voided.
Are you on an Edge plan? Otherwise I don't know why you would be returning the phone to upgrade. Also not sure what their rules are on permanently modifying the software of one of these essentially "lease-to-own" devices, so might want to check the terms and conditions if this applies to you. If you are just trading it in for credit toward a new phone, I'd just sell it yourself unlocked and get a lot more for it.
Sent from my XT1254 using Tapatalk
SpyderPride said:
If you are just trading it in for credit toward a new phone, I'd just sell it yourself unlocked and get a lot more for it.
Click to expand...
Click to collapse
A bootloader unlocked, rooted XT1254 would be more valuable to a buyer than one locked down. You've already done all the hard work.
TheSt33v said:
1. Go back to stock everything by following section 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
2. While in bootloader mode, use the fastboot command "fastboot oem lock"
If you're turning in the phone to Verizon, this method is okay. However, don't do this if you plan on selling the phone to someone else. If they were to try and unlock the phone again, they would most likely brick it.
Click to expand...
Click to collapse
Heya so I'm in a serious bind.
I skipped your step 1 and locked my bootloader. I have an unlocked bootloader. I recently upgraded through the normal verizon pushed update the marshmallow update. Anyhow. I now want to return the phone for an upgrade and well... I locked the bootloader. Then turn the phone off and turned it back on and it now says locked, but it says failed to validate system image. I then got freaked out and downloaded all the step 1 files and tried to flash the stock rom (which i already had installed!) and that doesn't seem to work. Did I brick my phone? Is there any way to get it working now that it is locked with any kind of android at all?
You're probably fine @droidfun1. You just need to use the marshmallow firmware package instead of the lollipop one. Get it here: https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Yup, I tried flashing the stock 6.0.1 rom with fastboot on my mac but I got all kinds of fails.
I found a mac compatible command line version of RSDLite and it totally worked! Not sure why fastboot couldn't successfully flash the same stock rom?
Now I just need to remove the bootloader unlocked warning (my phone is now locked status 2), but not sure if I can now that it is locked.
TheSt33v said:
You're probably fine @droidfun1. You just need to use the marshmallow firmware package instead of the lollipop one. Get it here: https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Click to expand...
Click to collapse
droidfun1 said:
Yup, I tried flashing the stock 6.0.1 rom with fastboot on my mac but I got all kinds of fails.
I found a mac compatible command line version of RSDLite and it totally worked! Not sure why fastboot couldn't successfully flash the same stock rom?
Now I just need to remove the bootloader unlocked warning (my phone is now locked status 2), but not sure if I can now that it is locked.
Click to expand...
Click to collapse
Strange. As far as I understand it, RSDlite just automates fastboot, so even if you're using RSDlite, you're actually using fastboot. Whatever works though.
As for the unlocked bootloader message, see my response to that post you made.
Eager to try out Android 11, I sideloaded the ota zip of the latest Developer preview on my Pixel 4 XL. I have the Verizon version, so my bootloader is locked and I was unable to get it to unlock. So, I figured the ADB sideload method would be perfect.
Everything went smoothly until after the OTA was installed:
I just get a screen that says "Can't find a valid operating system. Device will not start." -- this screen appears for recovery and rescue mode.
The only thing I do have access to is Fastboot. Device appears when I type in "Fastboot devices", but I'm guessing that it doesn't matter since my bootloader is locked and I can't flash anything?
Google support was no help and just send me the address of a repair shop.
Does anyone know if I'm totally F'd in this situation?
Thanks
Nevermind I'll keep looking
Can you change slots? fastboot --set-active=a
It tells you what slot you are on in the bootloader screen. It won't hurt anything. You can always change it back. It's the only thing I know to try.
You can get a stock image and flash it from the stock recovery; dont recall how that procedure is done but there is a guide floating around here as it comes up every once in a while. Usually a Verizon owner...
Are you able to unlock the bootloader (activated before sideload)? So flash unlock and then the factory Image. If you can't unlock your bootloader you are stuck and best option is to open a warranty case by Google...
Try this - https://pixelrepair.withgoogle.com/
You may need to use a VPN if it says not supported in country. Never used it before but worth exploring.
Hey Everyone,
I'm looking for help. I tried reverting my pixel 5 to stock from beta and am stuck at the boot screen with " your device is corrupt. It cannot be trusted and may not work properly."
I've spent days fiddling with it, and cannot get anywhere with the google repair website because it's saying my bootloader is locked. I don't understand how I purchased it unlocked. Anyway, I cannot get into the settings to unlock the bootloader. It's been a long time since I've been a tinkerer but I do have all the software downloaded to do so. I cannot get my PC to recognize the phone in the command prompt window to try and sideload a software install.
Has this happened to anyone and is there a solution out there somewhere?
Sean Hicks said:
Hey Everyone,
I'm looking for help. I tried reverting my pixel 5 to stock from beta and am stuck at the boot screen with " your device is corrupt. It cannot be trusted and may not work properly."
I've spent days fiddling with it, and cannot get anywhere with the google repair website because it's saying my bootloader is locked. I don't understand how I purchased it unlocked. Anyway, I cannot get into the settings to unlock the bootloader. It's been a long time since I've been a tinkerer but I do have all the software downloaded to do so. I cannot get my PC to recognize the phone in the command prompt window to try and sideload a software install.
Has this happened to anyone and is there a solution out there somewhere?
Click to expand...
Click to collapse
Buying it "unlocked" means you bought it free of a carrier, such as Verizon, who lock the bootloader, and can't be unlocked.
But you still need to unlock the bootloader, it comes locked, for security reasons. So if you never unlocked it, it's locked.
I haven't installed beta 12 yet.
Do you have the latest SDK tools? (adb, fastboot, etc)
I was under the impression though, that you can't downgrade with a locked bootloader. But not sure.
Sean Hicks said:
Hey Everyone,
I'm looking for help. I tried reverting my pixel 5 to stock from beta and am stuck at the boot screen with " your device is corrupt. It cannot be trusted and may not work properly."
I've spent days fiddling with it, and cannot get anywhere with the google repair website because it's saying my bootloader is locked. I don't understand how I purchased it unlocked. Anyway, I cannot get into the settings to unlock the bootloader. It's been a long time since I've been a tinkerer but I do have all the software downloaded to do so. I cannot get my PC to recognize the phone in the command prompt window to try and sideload a software install.
Has this happened to anyone and is there a solution out there somewhere?
Click to expand...
Click to collapse
This probably isn't of any help now, but going forward, it may be. In Developer options, you can enable 'OEM unlocking'. As you can see now, it may well be a very good idea to enable that **before** you start messing with the phone, because if something does go wrong (as it has for you), then you can (hopefully) still get to fastboot and do 'fastboot flashing unlock'.
So, knowing this, you may want to keep an eye out for some tool or something that will allow you to possibly turn on oem unlocking (because your device won't boot).
Another thing to try is switching slots and see if the other slot boots? If you can get to fastboot try; fastboot --set-active=(a or b), then fastboot reboot. (If you don't know which slot is active, do 'fastboot getvar all', in the output it will tell you which is current.
cheers
Your bootloader being locked should not affect your ability to restore factory images/OTAs from Google. They are signed by Google and will pass the signature checks. You should try to download the latest factory image (either 11 or 12beta) and flash it via recovery => adb sideload.