Related
I noticed there were 2 newer images on the Google developers page and thought I would flash the latest and greatest (MDB08M) since it wasn't coming down OTA. I enabled Developer Options and set USB debugging and OEM unlock, rebooted to bootloader, did a fastboot oem unlock, rebooted then back to bootloader and ran the flash-all.bat from the new image, rebooted and all was well. I re-enabled USB debugging and went back to bootloader to re-lock the bootloader and am getting an error:
...
FAILED (remote: unknown command)
finished. total time: 0.016s
Results of fastboot getvar version-main are blank:
version-main:
finished. total time: -0.000s
I rolled back to MDB08K but it made no difference. I then tried rolling back to MDA89D and letting it pull MDB08K OTA but that too made no difference.
Any suggestions?
Are you using the following command after flashing stock images?
fastboot flashing lock
Click to expand...
Click to collapse
Cares said:
Are you using the following command after flashing stock images?
Click to expand...
Click to collapse
No, I was trying to do "fastboot oem lock". "fastboot flashing lock" relocked the bootloader, but fastboot getvar version-main is still blank. I suppose I have achieved my goal of relocking the bootloader, but should I worry about the version-main being blank?
boofa said:
No, I was trying to do "fastboot oem lock". "fastboot flashing lock" relocked the bootloader, but fastboot getvar version-main is still blank. I suppose I have achieved my goal of relocking the bootloader, but should I worry about the version-main being blank?
Click to expand...
Click to collapse
That I have no idea. I just know that the fastboot commands have changed so that's why you couldn't relock.
Cares said:
That I have no idea. I just know that the fastboot commands have changed so that's why you couldn't relock.
Click to expand...
Click to collapse
Why are you locking the bootloader anyway? If you're flashing system images and then locking the bootloader you are risking having a device with a non-functioning OS and no way to fix it. Either stay locked and wait for OTA's or leave it unlocked.
I was going to root it, but decided against it since I only needed root for Tasker and WiFi hotspot in the past and I get WiFi hotspot at no charge since switching to Fi. I'll just do without the Tasker stuff since alot of what it was doing is probably not necessary any more and was setup back on Jellybean. I wasn't attempting to lock the bootloader until I had done a clean boot and verified basic functionality. I'm all good now though, thanks for the assist.
I've followed a couple tutorials of that explain how to unlock Motorola's Moto G4 bootloader. This seems to be the "official" one from Motorola:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
I copied part of it up to where I get stuck. Here it is:
Put your device in fastboot mode (power off, then press the power and volume down buttons simultaneously).
On your desktop, open a command prompt or terminal, and go to the directory where you installed the Android SDK tools (or make sure fastboot is in your $PATH)
At the prompt, type $ fastboot oem get_unlock_data
The returned string will be used to retrieve your unlock key.
Example: On a Windows Desktop, the returned string format would be $ fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
****************************************
OK, so I just bought a Moto G4 for $125 on Amazon's prime day. This means that it has ads on the lock screen. I'm OK with that. But I think they also made the locked bootloader unlocakble as 3 times I've gotten this from a Windows machine in ADB mode:
(bootloader) Unlock data:
(bootloader) 3A45210407248602#
(bootloader) 5A59323233433246534C004D6F746F2047200000#
(bootloader) 1095EFAB6000EDC14660539C503A04F7900B9A01#
(bootloader) 9F93C800000000000000000000000000
There should be numbers in that first Bootloader line and then Motorola says:
You're device does not qualify for bootloader unlocking.
Has anybody else had this happen? This is my second time doing this to a Motorola phone and the Moto g2 was a snap! I was hoping to install a custom recovery like TWRP so I could get a nandroid backup while everything is new
Marty
LinuxHippy said:
You're device does not qualify for bootloader unlocking.
Has anybody else had this happen? This is my second time doing this to a Motorola phone and the Moto g2 was a snap! I was hoping to install a custom recovery like TWRP so I could get a nandroid backup while everything is new
Marty
Click to expand...
Click to collapse
A Lot of us have already unlocked our bootloader
Rempala said:
A Lot of us have already unlocked our bootloader
Click to expand...
Click to collapse
Do u have the Amazon moto g4?
I do and I unlocked my bootloader and rooted the phone already.
Yes I have the Amazon G4
Well, these posts gave me hope that I was repeating the same mistake and I was. Forth time worked to unlock the BL. I was deleting the # signs at the end of each line. That was the mistake. It should be this from 4 lines:
3A45210407248602#5A59323233433246534C004D6F746F2047200000#1095EFAB6000EDC14660539C503A04F7900B9A01#9F93C800000000000000000000000000
Now I'm trying to boot into the TWRP image I flashed with fastboot and fastboot gave me errors about it not being signed so I'm not sure it worked. Where are people here getting the Moto g4 TWRP images? I went here:
https://www.androidfilehost.com/?w=...23bf15e9165ccc3b437c48af2047195d3fae863dca817
This is what I get when I try to flash TWRP now and then reboot into it with adb:
C:\Users\Huntz\Downloads>fastboot devices
ZY223C2FSL fastboot
C:\Users\Huntz\Downloads>fastboot flash recovery twrp_athene_20160526.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (12498 KB)...
OKAY [ 0.398s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.344s]
finished. total time: 0.746s
C:\Users\Huntz\Downloads>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: no devices/emulators found
Just FYI, Motorola's bootloader unlock website has a webtool that you can use to clean the output of get_unlock_data, so you'll only get the relevant info. Copy-paste the raw code into the tool, hit clean, copy paste the output into the unlock code line on the website, submit.
Regarding TWRP, yes I think everyone gets that "Image not signed or corrupt" message. Also, you can't "adb reboot recovery" from fastboot. Just flash it via fastboot, reboot into fastboot, then go into recovery.
Maybe it did install twrp OK since it still boots into the original stock ROM OK. How do u get into twrp with the buttons on the phone?
LinuxHippy said:
Maybe it did install twrp OK since it still boots into the original stock ROM OK. How do u get into twrp with the buttons on the phone?
Click to expand...
Click to collapse
Boot into fastboot (press and hold power + volume down, let go when the bootloader screen shows up), press down on the volume rocker twice, and it'll say "recovery mode" on the screen. Press power once and it'll boot into TWRP.
Something's wrong then. I get to the fastboot screen OK but when I go into recovery it says your device has been unlocked and can't be trusted. It will reboot in 5 sec and then I see a dead robot.
EDIT
it does boot OK into the stock ROM from there if u do nothing for a minute or two or if u just hold in power button for 15 secs to get a black screen and then release the button and hold it 4 secs to get a normal boot
Sounds like TWRP didn't flash correctly, or maybe was a bad download (can download directly from TWRP's website here: https://dl.twrp.me/athene/). Reboot back into fastboot and try flashing TWRP again (you might also want to try renaming it to recovery.img, so the flashing command would be "fastboot flash recovery recovery.img").
I'll try again later today-hopefully it works and thanks for the link
I'm gonna try doing adb in Linux too.
xtermmin said:
Sounds like TWRP didn't flash correctly, or maybe was a bad download (can download directly from TWRP's website here: https://dl.twrp.me/athene/). Reboot back into fastboot and try flashing TWRP again (you might also want to try renaming it to recovery.img, so the flashing command would be "fastboot flash recovery recovery.img").
Click to expand...
Click to collapse
When u reboot now, do u get a 5 second delay screen that says your device has been unlocked and can't be trusted?
Marty
LinuxHippy said:
When u reboot now, do u get a 5 second delay screen that says your device has been unlocked and can't be trusted?
Marty
Click to expand...
Click to collapse
Yes, that is normal for devices with unlocked bootloaders. You can get rid of it by rebooting into fastboot and following this guide: http://forum.xda-developers.com/showpost.php?p=67031810&postcount=5
(if you don't have mfastboot, you can use plain-old fastboot as well)
I'm puzzled-the md5 on twrp was right and I unlocked the BL OK. I'll try it in Linux later and see if it takes.
Might be worth trying another USB port or even another cable. Some people have issues when trying to flash things on a USB 2.0 phone plugged into a USB 3.0 port.
About how much time should it take to flash twrp? I don't think it even flashed anything yesterday because it was too quick.
LinuxHippy said:
About how much time should it take to flash twrp? I don't think it even flashed anything yesterday because it was too quick.
Click to expand...
Click to collapse
It is almost instantaneous. As for the booting into recovery and seeing the dead robot, that is probably due to the fact that the phone tries to re-write the recovery when you reboot automatically. Just flash the twrp.img, and then go to recovery from the bootloader without rebooting and you will be fine; just make sure you have whatever you want to flash (e.g. supersu) on your device storage when you get there.
Sounds like a plan! What's the md5 on the supersu file?
Hello guys, I unlocked and then locked the bootloader after an attempt to bring back the 1+2 to stock.
I have used TOOL ALL IN ONE by MAURONOFRIO to do all this stuff.
Now I want to unlock the bootloader to try the CM13 , but when I write
fastboot oem device-info
It tells me that
Device tampered: false
Device unlocked: false
It seems like I can't unlock the bootloader, no matter how I try. Also I do not have the root so I can't follow this other guide.
Do you have any tip to help me out?
Ok I just wiped data.
Now it says:
tampered: false
unlocked: true.
Now it seems like I can't flash the recovery.
I have used the same tool from before, it didn't work.
So I just used:
fastboot flash recovery *filename.img*
and it still goes back to stock recovery.
Any ideas?
Make sure you boot into recovery before letting the OS boot. If its stock OS it will replace the recovery if you let it boot. This may also be a big help http://forum.xda-developers.com/oneplus-2/general/guides-how-to-guides-beginners-t3146568/page1 Go to first post and then how to install custom recovery.
Thank you, I solved the issue Now I have the latest CM13 and it works really good. Thanks!!
Currently I have installed latest official nightly LineageOS 14.1 on my device. I want to return to stock ROM and lock bootloader. Previously, before bootloader unlocking, I had 6.0.1 stock, version with january security updates (probably).
I have downloaded latest stock 6.0.1 MPD24.107-52 ( https://github.com/motoxplay/stock ).
Unfortunately, I got an error when tried to flash it:
HTML:
$ fastboot flash partition gpt.bin
it returns:
HTML:
(bootloader) Preflash validation failed
same with recovery.img
To lock bootloader I have to flash all stock files.
Any ideas? Thanks
skip it. You cant flash same bootloader and same gpt.bin again.
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
NOTE: You must use a factory firmware image that is the same version as what you have installed or newer to successfully relock the bootloader, you cannot just grab the old (shipped) version from Moto's site. If you attempt to use a firmware image that is older than what you have installed currently, you will receive a Preflash Validation Error indicating such when you attempt to flash the partition table (gpt.bin). At this point you can either continue the flash and NOT lock the bootloader at the end, or stop until you can find the most current image. Moto used to be quite willing to hand these out when they were requested, so if you have a very new firmware installed you may not find one that you can use to relock with on the Internet. Part of the requirements to lock the bootloader is you must successfully flash the partition table (gpt.bin) in order to complete the lock process, if you can't then the bootloader lock process cannot be finished.
Click to expand...
Click to collapse
so i have to wait for the official nougat flashable file.
bump
any workaround?
Yesterday, I was messing about trying to fastboot boot other MSM8998 TWRP boot.imgs, with the hopes that the device-trees on some of them would be close enough to get far enough in boot to bring up the USB port (even if they didn't mount anything or bring up the screen). As it turns out, none of them did (and, in fact, they all blanked the screen and went back to having the USB interface enumerate as fastboot -- how could that be? does anyone understand what could cause fastboot to reject a kernel before even trying to boot it?), but when I was done for the day, I had another disturbing event: when I tried to boot the device normally, it would simply sit there at the fastboot screen, and in fact, when I tried to boot into recovery, it would still just kick me back to fastboot.
This was very scary -- without factory images to reflash it with, I thought I had bricked my device! I did a fastboot getvar all, and saw:
Code:
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:0
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:3
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
So apparently just fastboot booting something that fails to boot can cause fastboot to declare that the live system image is no good.
If this happens to you, the answer to this is to make sure that you have the latest platform-tools (I had a properly oldschool version of fastboot that I've been kicking along on my Mac from the unrevoked era...) -- get them from Google -- and you can un-confuse the bootloader even without flashing a new image by doing a fastboot set_active a.
Then your phone will boot again. Phew!
So useful, thanx man!
Thank you, this is good to know.
Can anyone share system dump pls?
No need for system dump, the factory images are up: https://developers.google.com/android/images
joshua_ said:
Yesterday, I was messing about trying to fastboot boot other MSM8998 TWRP boot.imgs, with the hopes that the device-trees on some of them would be close enough to get far enough in boot to bring up the USB port (even if they didn't mount anything or bring up the screen). As it turns out, none of them did (and, in fact, they all blanked the screen and went back to having the USB interface enumerate as fastboot -- how could that be? does anyone understand what could cause fastboot to reject a kernel before even trying to boot it?), but when I was done for the day, I had another disturbing event: when I tried to boot the device normally, it would simply sit there at the fastboot screen, and in fact, when I tried to boot into recovery, it would still just kick me back to fastboot.
This was very scary -- without factory images to reflash it with, I thought I had bricked my device! I did a fastboot getvar all, and saw:
So apparently just fastboot booting something that fails to boot can cause fastboot to declare that the live system image is no good.
If this happens to you, the answer to this is to make sure that you have the latest platform-tools (I had a properly oldschool version of fastboot that I've been kicking along on my Mac from the unrevoked era...) -- get them from Google -- and you can un-confuse the bootloader even without flashing a new image by doing a fastboot set_active a.
Then your phone will boot again. Phew!
Click to expand...
Click to collapse
With that said you should still probably reflash partition_b because it might interfere with future updates which I assume you know how they work. Images like @hazzamon said are finally available.
Sent from my marlin using XDA Labs
Doesn't pixel 1 have a TWRP version which can see both slots and boot to either? Did you try to install or just fastboot to .img file? Did you unlock the bootloader? If you bought it from Google, I would think the bootloader should be pretty easy to unlock, there is the option to allow it in the dev settings.
I flashed the 8.1 beta using an old fastboot (that didn't know about slots) and now I'm stuck in the bootloader. I can't get android to boot, and I can't even get into the stock recovery or download options.
I've tried flashing the stock image several times, but that didn't do any good.
Any Help would be greatly appreciated!
Thanks!
I was looking through the bootloader screen and apparently there is a download mode, perhaps you could sideload an OTA
RagedElimanator said:
With that said you should still probably reflash partition_b because it might interfere with future updates which I assume you know how they work. Images like @hazzamon said are finally available.
Click to expand...
Click to collapse
Reflashing slot B is kind of funny on these devices. When they come from the factory, slot B doesn't come with an Android image, but instead the extra space is used to host prebuilt .odex images, to speed up first boot. (They comment on this in the A/B appnote: https://source.android.com/devices/...size-of-the-system-partition-without-squashfs ). So you actually don't really want to reflash slot B if you can avoid it.
pvillegeek said:
I flashed the 8.1 beta using an old fastboot (that didn't know about slots) and now I'm stuck in the bootloader. I can't get android to boot, and I can't even get into the stock recovery or download options.
I've tried flashing the stock image several times, but that didn't do any good.
Click to expand...
Click to collapse
Have you tried with a modern fastboot?
What does 'fastboot getvar all' tell you?
You need to set_active, like I mentioned.
pixel-painter said:
I was looking through the bootloader screen and apparently there is a download mode, perhaps you could sideload an OTA
Click to expand...
Click to collapse
The download mode is a no-op on production Walleye, I think
pixel-painter said:
Doesn't pixel 1 have a TWRP version which can see both slots and boot to either? Did you try to install or just fastboot to .img file? Did you unlock the bootloader? If you bought it from Google, I would think the bootloader should be pretty easy to unlock, there is the option to allow it in the dev settings.
Click to expand...
Click to collapse
I took the steps I mentioned in the OP You can't fastboot boot, fastboot set_active, or fastboot flash something without unlocking the bootloader.
joshua_ said:
Reflashing slot B is kind of funny on these devices. When they come from the factory, slot B doesn't come with an Android image, but instead the extra space is used to host prebuilt .odex images, to speed up first boot. (They comment on this in the A/B appnote: https://source.android.com/devices/...size-of-the-system-partition-without-squashfs ). So you actually don't really want to reflash slot B if you can avoid it.
Have you tried with a modern fastboot?
What does 'fastboot getvar all' tell you?
You need to set_active, like I mentioned.
The download mode is a no-op on production Walleye, I think
I took the steps I mentioned in the OP You can't fastboot boot, fastboot set_active, or fastboot flash something without unlocking the bootloader.
Click to expand...
Click to collapse
Which is why I asked if the bootloader was unlocked
joshua_ said:
Reflashing slot B is kind of funny on these devices. When they come from the factory, slot B doesn't come with an Android image, but instead the extra space is used to host prebuilt .odex images, to speed up first boot. (They comment on this in the A/B appnote: https://source.android.com/devices/...size-of-the-system-partition-without-squashfs ). So you actually don't really want to reflash slot B if you can avoid it.
Click to expand...
Click to collapse
I wonder if that means that flashing the factory image replaces the opposite slot with those prebuilt odex files then. On the original Pixel and Pixel XL it just flashed the opposite slot with an empty image.
joshua_ said:
Reflashing slot B is kind of funny on these devices. When they come from the factory, slot B doesn't come with an Android image, but instead the extra space is used to host prebuilt .odex images, to speed up first boot. (They comment on this in the A/B appnote: https://source.android.com/devices/...size-of-the-system-partition-without-squashfs ). So you actually don't really want to reflash slot B if you can avoid it.
Have you tried with a modern fastboot?
What does 'fastboot getvar all' tell you?
You need to set_active, like I mentioned.
The download mode is a no-op on production Walleye, I think
I took the steps I mentioned in the OP You can't fastboot boot, fastboot set_active, or fastboot flash something without unlocking the bootloader.
Click to expand...
Click to collapse
Well if you want to use slot_b then you might as well flash the image over that the slot_a pretty much takes place of what slot_b was in the beginning, but yeah you are right though about having slot_b at preconfigured state yet that's if you are on slot_a.
I think I might be in real trouble. I can't boot anything at all, just like others in this thread. I can't even boot TWRP, and I get this error:
PS C:\Users\hanna\Desktop\platform-tools> fastboot boot twrp-3.1.1-beta1-walleye.img
downloading 'boot.img'...
OKAY [ 0.715s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.734s
Click to expand...
Click to collapse
I've tried setting the active slot to a, and back to b. I've tried multiple times to flash the stock image files from Google. They appear to flash normally, but I still can't boot.
All of this started after I accidentally tried to boot the recovery image from the pixel 2 xl. Something got seriously messed up, and I can't figure out how to repair it.
Does anyone know what else I can try?
mtpease said:
I think I might be in real trouble. I can't boot anything at all, just like others in this thread. I can't even boot TWRP, and I get this error:
I've tried setting the active slot to a, and back to b. I've tried multiple times to flash the stock image files from Google. They appear to flash normally, but I still can't boot.
All of this started after I accidentally tried to boot the recovery image from the pixel 2 xl. Something got seriously messed up, and I can't figure out how to repair it.
Does anyone know what else I can try?
Click to expand...
Click to collapse
Use cmd instead of powershell. I've had issues relating to fastboot/adb with PS in the past
Sent from my Pixel 2 using Tapatalk
mtpease said:
I think I might be in real trouble. I can't boot anything at all, just like others in this thread. I can't even boot TWRP, and I get this error:
I've tried setting the active slot to a, and back to b. I've tried multiple times to flash the stock image files from Google. They appear to flash normally, but I still can't boot.
All of this started after I accidentally tried to boot the recovery image from the pixel 2 xl. Something got seriously messed up, and I can't figure out how to repair it.
Does anyone know what else I can try?
Click to expand...
Click to collapse
I was in the same boat. Would only boot to bootloader after typical manual flash-all of the system image (no recovery, no nothing, just bootloader).
Here's what I did (Windows 10):
1) Update fastboot/adb
2) Download and extract latest 8.0 image (ends in 25)
3) Open CMD (not powershell)
4) fastboot set_active other
5) Manually flash bootloader (failed for me), radio (went ok), update .zip (some errors), reboot bootloader between each:
fastboot flash bootloader <location>
fastboot flash radio <location>
fastboot update <location of image-walleye-opd1.170816.025.zip>
6) fastboot set_active other then repeat bootloader, radio, update.zip manual flashes
Though I read this about the og Pixels... Basically just manually flash images to both slots when all else fails.
joetheshmo said:
Use cmd instead of powershell. I've had issues relating to fastboot/adb with PS in the past
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
I'm trying this now, but I can't get my phone to boot. It just goes back to the bootloader (which is unlocked). I'm getting the same "FAILED (remote: Failed to load/authenticate boot image: Load Error)" error. My adb/fastboot is at the latest version. Trying to flash the 8.1 factory image.
joshua_ said:
Yesterday, I was messing about trying to fastboot boot other MSM8998 TWRP boot.imgs, with the hopes that the device-trees on some of them would be close enough to get far enough in boot to bring up the USB port (even if they didn't mount anything or bring up the screen). As it turns out, none of them did (and, in fact, they all blanked the screen and went back to having the USB interface enumerate as fastboot -- how could that be? does anyone understand what could cause fastboot to reject a kernel before even trying to boot it?), but when I was done for the day, I had another disturbing event: when I tried to boot the device normally, it would simply sit there at the fastboot screen, and in fact, when I tried to boot into recovery, it would still just kick me back to fastboot.
This was very scary -- without factory images to reflash it with, I thought I had bricked my device! I did a fastboot getvar all, and saw:
Code:
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:0
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:3
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
So apparently just fastboot booting something that fails to boot can cause fastboot to declare that the live system image is no good.
If this happens to you, the answer to this is to make sure that you have the latest platform-tools (I had a properly oldschool version of fastboot that I've been kicking along on my Mac from the unrevoked era...) -- get them from Google -- and you can un-confuse the bootloader even without flashing a new image by doing a fastboot set_active a.
Then your phone will boot again. Phew!
Click to expand...
Click to collapse
What if both partitions show as not successful?
Code:
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:5
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no
Sorry to resurect this from the dead, but I was in the same boat and there doesn't seem to be an answer here, So I'll tell you what I did.
1. I booted into linux
2. Made sure my android platform tools were up to date
3. from the bootload I went to recovery(which would not open, ended up with phone with black screen)
4. from that black screen I could use Duece's tool and that fix the phone to where it will at least boot properly.
In hope this helps