Today i decided to go from Cyan 6 Nightly to Stock OTA 2.2.
so i tried flashing PASSIMG.zip and all the tests pass, except for USERDATA.img: I want to downgrade to 2.1 first, then ill upgrade
so i tried running
Code:
fastboot erase userdata
and it faild saying that it was not allowed.
i did have an unlocked bootloader with Amon RA Recovery 1.7.0.1
i also wiped data in the recovery so it can boot up into the launcher.
my phone still thinks its unlocked because i ran the code
Code:
fastboot oem unlock
and it said:
Code:
C:\Users\Family\Documents\Android\Nexus One\Root\Recoveries>fastboot oem unlock
... INFODevice was already unlocked!
OKAY [ 0.070s]
finished. total time: 0.070s
my entire command looked like this:
Code:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Family>cd C:\Users\Family\Documents\Android\Nexus One\Root\Recoveries
C:\Users\Family\Documents\Android\Nexus One\Root\Recoveries>fastboot devices
HT065P800670 fastboot
C:\Users\Family\Documents\Android\Nexus One\Root\Recoveries>fastboot erase userdata
erasing 'userdata'... FAILED (remote: not allowed)
finished. total time: 0.068s
C:\Users\Family\Documents\Android\Nexus One\Root\Recoveries>fastboot oem unlock
... INFODevice was already unlocked!
OKAY [ 0.070s]
finished. total time: 0.070s
C:\Users\Family\Documents\Android\Nexus One\Root\Recoveries>fastboot erase userdata
erasing 'userdata'... FAILED (remote: not allowed)
finished. total time: 0.068s
C:\Users\Family\Documents\Android\Nexus One\Root\Recoveries>
I was under the impression PASSIMG.zip was for the stock recovery, not Amon RA.
Try the Stock 2.2 image for users with custom recoveries.
Clarkster said:
I was under the impression PASSIMG.zip was for the stock recovery, not Amon RA.
Try the Stock 2.2 image for users with custom recoveries.
Click to expand...
Click to collapse
sorry i forgot to mention, i wanted to downgrade to Shipped 2.1 and ill use stock recovery to upgrade to 2.2
I still think my answer stands. You can't flash it with Amon RA. Someone else may chime in and say otherwise, but until then I think I am right.
Clarkster said:
I still think my answer stands. You can't flash it with Amon RA. Someone else may chime in and say otherwise, but until then I think I am right.
Click to expand...
Click to collapse
i have stock recovery now bc passimg returned it to stock
Good to know I was completely wrong then
Do you know what the problem was in case I see someone else asking this?
Clarkster said:
Good to know I was completely wrong then
Do you know what the problem was in case I see someone else asking this?
Click to expand...
Click to collapse
i have no idea. ive been going at it and researching all day. basically the problem is my unlocked bootloader wont let me erase or flash userdata from passimg or from fastboot.exe
Related
hi, i had the frf91 vodafone version on my nexus one. i thougth to install the frg83d posted here with rom manager. Everything went fine but the installation didn't restore the recovery and if i try to flash it with fastboot:
C:\android\tools>fastboot devices
HT05EP800252 fastboot
C:\android\tools>fastboot flash recovery recovery.img
sending 'recovery' (2294 KB)... OKAY [ 0.344s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.734s
am i doing something wrong?
is it because i'm rooted? i rooted my N1 without unlocking the bootloader.
Thanks
I dont think you can use fastboot to flash the recovery image without unlocking, you need to install the appropriate binary (/system/bin/flash_image) and call it from a shell on your phone (using a desktop is ok)
see http://forum.xda-developers.com/showthread.php?t=687280
http://www.droidforums.net/forum/dr...covery-framework-res-apk-custom-boot-ani.html
I would also say you lost root when updating your ROM. Also, you can't fastboot flash unofficial files without unlocking the bootloader.
Root, and flash through adb or ROM Manager, etc
Sent from my Nexus One using XDA App
Hey guys, I did something really stupid.
I acquired an Atrix HD through a third party, network/sim unlocked it to work on T-Mobile, and tried to flash 4.1.2 Mexican Retail (MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX) through RSD Lite 6.1.5 after removing the getvar command and.. it failed half way. I forgot to unlock the bootloader before flashing.
Now I'm stuck and I've tried almost everything to fix it. I've searched Google and XDA, in the process I have downloaded Myth Tools, sirhoover_atrixhd_utility, motochopper, motopocalypse, and moto-fastboot, tried them all to the best of my knowledge and nothing is working. I've even edited the XML file to exclude the files it fails on.
Common errors I encounter:
Fastboot reason: Boot failure
Fastboot reason: Flash failure
Partition (boot) Security Version Downgraded
Preflash Validation Failed for boot
Partition (system) Security Version Downgraded
PIV black validation for system failed
Invalid PIV image: system
Worst part is, I can't unlock my bootloader because I need ADB to do so! Recovery will give me ADB but only to sideload (available on certain recoveries I've managed to flash). If you have any ideas or information that could assist me in getting my phone back to normal, whether that's unlocking the bootloader through fastboot or flashing a stock rom sucessfully, I would greatly appreciate it! :good:
You don't need a unlocked bootloader to flash firmware through rsd.. Try flashing the stock att back.
Sent from my PACMAN MATRIX HD MAXX
deeje00 said:
You don't need a unlocked bootloader to flash firmware through rsd.. Try flashing the stock att back.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
Thanks for your reply
I've tried flashing several stock firmwares already, I get preflash validation failed errors every time on boot.img and system.img
Here's the firmwares I have downloaded:
MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX
MB886_bell-user-4.1.2-9.8.2Q-8_MB886_FFW-11-4-release-keys-BellMobility-CA
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA
7.7.1Q-144_MB886_MR1-22_SIGNED_CFC
7.7.1Q-115_MB886_FFW-14_SIGNED_CFC
I wish I knew exactly the version I had before I started flashing, but unfortunately I do not..
DaveTheRave said:
Thanks for your reply
I've tried flashing several stock firmwares already, I get preflash validation failed errors every time on boot.img and system.img
Here's the firmwares I have downloaded:
MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA
7.7.1Q-144_MB886_MR1-22_SIGNED_CFC
7.7.1Q-115_MB886_FFW-14_SIGNED_CFC
I wish I knew exactly the version I had before I started flashing, but unfortunately I do not..
Click to expand...
Click to collapse
Once your phone's OS has been upgraded, I don't think you can flash to an older firmware unless you have an unlocked bootloader. I'm not sure but that maybe the reason you're getting validation errors.
Did you try re-downloading the firmware?
audit13 said:
Once your phone's OS has been upgraded, I don't think you can flash to an older firmware unless you have an unlocked bootloader. I'm not sure but that maybe the reason you're getting validation errors.
Did you try re-downloading the firmware?
Click to expand...
Click to collapse
Just tried re-downloading everything on a brand new Windows install on a different computer, still having problems.
No matter how hard I try, I cannot get boot.img or system.img to flash from any Stock firmware, whether it's AT&T, Mex, or Bell
Using snap-fastboot:
snap-fastboot flash boot boot.img
sending 'boot' (10240 KB)...
OKAY [ 0.788s]
writing 'boot'...
Preflash validation failed
FAILED (remote failure)
snap-fastboot flash system system.img
sending 'system' (30720 KB)...
OKAY [ 2.343s]
writing 'system'...
Preflash validation failed
FAILED (remote failure)
I'm going to try making a Motorola Factory cable in the meantime. Any other suggestions?
EDIT: Factory cable didn't help.. is there a way to generate a higher security version? No matter what, the bootloader always displays Partition (boot/system) Security Version Downgraded
I really don't want this to end up being a paperweight
Is this where you got the firmware: http://sbf.droid-developers.org/dinara/list.php ?
Did you reboot each time you loaded a different set of fastboot files? Did you remove the previous fastboot files before installing a new set of fastboot files? Are you able to try this on a different computer?
I just got a new Atrix HD replacement and its showing firmware of 9.8.0Q-97_MB886_FFW-20 . Its not the same as the firmware available here: http://sbf.droid-developers.org/ .... I get the same error even after modifying the XML file in the SBF. Wonder if the last update caused an issue. Running into some similar issue with the replacement. Its not wanting to bootloader unlock.
Did you mount the system before installing?
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
Found a fix for the AP Fastboot loop
List of commands to type in. ( in order)
1. adb reboot bootloader
2.fastboot oem fb_mode_set
3.fastboot oem fb_mode_clear
3.fastboot erase userdata
4.fastboot erase cache
5.fastboot reboot
Source:http://www.droidrzr.com/index.php/topic/17320-sticky-bit-fastboot/
Sorry I've been MIA, been busy with work.
TabascoTX said:
Found a fix for the AP Fastboot loop
List of commands to type in. ( in order)
1. adb reboot bootloader
2.fastboot oem fb_mode_set
3.fastboot oem fb_mode_clear
3.fastboot erase userdata
4.fastboot erase cache
5.fastboot reboot
Source:http://www.droidrzr.com/index.php/topic/17320-sticky-bit-fastboot/
Click to expand...
Click to collapse
Thanks for the reply! I wished this worked for me. After completing the steps successfully, I get:
Partition (boot) Security Version Downgraded
Fastboot Reason: Boot Failure
Code:
adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
fastboot oem fb_mode_set
...
OKAY [ 0.006s]
finished. total time: 0.006s
fastboot oem fb_mode_clear
...
OKAY [ 0.005s]
finished. total time: 0.005s
fastboot erase userdata
erasing 'userdata'...
OKAY [ 3.095s]
finished. total time: 3.095s
fastboot erase cache
erasing 'cache'...
OKAY [ 1.669s]
finished. total time: 1.669s
fastboot reboot
rebooting...
finished. total time: 0.005s
audit13 said:
Is this where you got the firmware: http://sbf.droid-developers.org/dinara/list.php ?
Did you reboot each time you loaded a different set of fastboot files? Did you remove the previous fastboot files before installing a new set of fastboot files? Are you able to try this on a different computer?
Click to expand...
Click to collapse
That's exactly where I got my firmwares from. And to answer your question, I have tried this on different computers but I wasn't doing much rebooting when changing fastboot files.
DaveTheRave said:
...I have tried this on different computers but I wasn't doing much rebooting when changing fastboot files.
Click to expand...
Click to collapse
Try logging off and back on to see what happens. For me, using fastboot/adb commands on an x86 Win7 machine works more consistently than using an x64 Win7 machine.
TabascoTX said:
Found a fix for the AP Fastboot loop
List of commands to type in. ( in order)
1. adb reboot bootloader
2.fastboot oem fb_mode_set
3.fastboot oem fb_mode_clear
3.fastboot erase userdata
4.fastboot erase cache
5.fastboot reboot
Source:http://www.droidrzr.com/index.php/topic/17320-sticky-bit-fastboot/
Click to expand...
Click to collapse
When I run fastboot oem fb_mode_set, it just says "< waiting for any device >"
Sorry for the late reply. make sure you have adb installed and the drivers for the Atrix. Also,if possible and not in a boot loop or stuck in fastboot, device debugging should be enabled.
Boot problem
Hello here I have a problem and I made everything from my knowledge but It's not fixed.
I have a Motorola Droid Maxx X8 verison XI1080, version 4.4.4, built number SU4.21,
If I install or do something and I switch off and I turn on my phone it disappears as if it is never done and if I try to reinitialize the phone I have a error Fastboot Reason: Boot Failure
If I get the fastboot and I take recovery its said Boot up failed.
I did everything I flashed with RSD and I update it with Motorola update but still nothing we see that the flashing and the update works but on reboot Its has no effect on the phone its stays as if you did nothing.
Please help me! I look forward to a solution, I thank you more.
have u solved the problem
Please explain how u have solved the problem ,my moto g4 plus in same problems
When I try:
fastboot boot recovery.img
I only get this and it wont boot into the Cyanogen Recovery :/
downloading 'boot.img'...
OKAY [ 0.217s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.221s
Any idea what I can do?
Check to see what Fire OS version you have. If it is 5.11 then booting a custom recovery will not work til a new custom boot.img can be created for it.
tuckerwagner said:
When I try:
fastboot boot recovery.img
I only get this and it wont boot into the Cyanogen Recovery :/
downloading 'boot.img'...
OKAY [ 0.217s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.221s
Any idea what I can do?
Click to expand...
Click to collapse
As far as I know you can only do temporary recovery boots (either twerp or Cyanogen) using a PC to push the recovery image and then boot it.
Code:
adb reboot bootloader
fastboot TWRP_Fire_2.8.7.0.img
Is what works for me.
same problem. Any way to downgrade?
skola28 said:
same problem. Any way to downgrade?
Click to expand...
Click to collapse
Same here... Bought two, got one to work and I think my girlfriend let the other update and now I am getting the "FAILED (remote: unknown command)" on the other.....
Ugh, time to look at Amazon's return policy?
skola28 said:
same problem. Any way to downgrade?
Click to expand...
Click to collapse
If on 5.1.1, at this time,
cannot root
cannot boot custom recovery
cannot downgrade
once a the update.zip is captured, maybe a new twrp can be built
RW2112 said:
Check to see what Fire OS version you have. If it is 5.11 then booting a custom recovery will not work til a new custom boot.img can be created for it.
Click to expand...
Click to collapse
Turns out it is 5.1.1. I guess I will wait for a new boot.IMG unless there is a way to downgrade. Thanks for your help!
Hi everyone
Yesterday I've installed Android 6.0. Tesla ROM after downgrading to Stock Android 5.1. (Stock 6.0. was slow as hell)
When I was beginning to install Android 5.1. stock fastboot had said that it cant install gpt.bin file. I've read that it's possible to do the install without it. Restarting or turning on after completely successful install it shows every time the bootloader and I always have to press START. I've decided to install Tesla ROM thinking it will fix that. But the problem remains still. I've tried to re-lock my bootloader but it says Please fully flash the signed build before locking phone. What do I have to do now to fix it? Thanks in advance
Check your phone box, there is a sticker that should say "XT 1541 retXX" so you know wich region is right for your phone, then download the fw from the filefacory repo http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=50 and flash it whit mfastbootV2
PS
Your phone have a dedicated section --> http://forum.xda-developers.com/2015-moto-g
edrpomidor said:
Hi everyone
Yesterday I've installed Android 6.0. Tesla ROM after downgrading to Stock Android 5.1. (Stock 6.0. was slow as hell)
When I was beginning to install Android 5.1. stock fastboot had said that it cant install gpt.bin file. I've read that it's possible to do the install without it. Restarting or turning on after completely successful install it shows every time the bootloader and I always have to press START. I've decided to install Tesla ROM thinking it will fix that. But the problem remains still. I've tried to re-lock my bootloader but it says Please fully flash the signed build before locking phone. What do I have to do now to fix it? Thanks in advance
Click to expand...
Click to collapse
Use mfastboot v2, and try to flash a 5.1 firmware from the same region (if your phone was from Latin America use retLA, if it's from asia use retasia, for the US use retUS, etc.)
benjausen said:
Use mfastboot v2, and try to flash a firmware FROM THE SAME REGION. Did you change motoboot.img? If so then skip 5.X gpt.bin and motoboot.img flashing.
Click to expand...
Click to collapse
No I didn't
deleted
benjausen said:
Use mfastboot v2, and try to flash a 5.1 firmware from the same region (if your phone was from Latin America use retLA, if it's from asia use retasia, for the US use retUS, etc.)
Click to expand...
Click to collapse
I've done everything you said (gpt.bin has been installed!), showing of bootloader is gone.
But the problem with blocking of bootloader exist yet... However, thanks
C:\Users\\Desktop\ADB and Fastboot>fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.047s]
finished. total time: 0.052s
C:\Users\\Desktop\ADB and Fastboot>fastboot oem lock begin
...
(bootloader) Please fully flash the signed build before locking phone!
OKAY [ 0.015s]
finished. total time: 0.017s
or in mfastboot-v2
C:\Users\\Desktop\Новая папка>mfastboot oem lock begin
...
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.020s
C:\Users\\Desktop\Новая папка>mfastboot oem lock
...
(bootloader) Please flash valid signed images just after lock begin
(bootloader) command!
OKAY [ 0.032s]
finished. total time: 0.035s
edrpomidor said:
I've done everything you said (gpt.bin has been installed!), showing of bootloader is gone.
But the problem with blocking of bootloader exist yet... However, thanks
C:\Users\\Desktop\ADB and Fastboot>fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.047s]
finished. total time: 0.052s
C:\Users\\Desktop\ADB and Fastboot>fastboot oem lock begin
...
(bootloader) Please fully flash the signed build before locking phone!
OKAY [ 0.015s]
finished. total time: 0.017s
or in mfastboot-v2
C:\Users\\Desktop\Новая папка>mfastboot oem lock begin
...
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.020s
C:\Users\\Desktop\Новая папка>mfastboot oem lock
...
(bootloader) Please flash valid signed images just after lock begin
(bootloader) command!
OKAY [ 0.032s]
finished. total time: 0.035s
Click to expand...
Click to collapse
Try to flash a 6.0 firmware for your region after the lock. Might not be the best, but at least you will have a working phone. It seems you relocked it, so you won't be able to use other images or to root and install custom ROMS. My XT1072 runs 6.0.1 CM13 and the touchscreen is lagged plus a reduced gaming perfomance, but the phone works.
benjausen said:
Try to flash a 6.0 firmware for your region after the lock. Might not be the best, but at least you will have a working phone. It seems you relocked it, so you won't be able to use other images or to root and install custom ROMS. My XT1072 runs 6.0.1 CM13 and the touchscreen is lagged plus a reduced gaming perfomance, but the phone works.
Click to expand...
Click to collapse
Now I have stock Android 6.0.1 RETEU XT1541, working phone with unlocked bootloader, so if I want, I can flash other ROMs.
edrpomidor said:
Now I have stock Android 6.0.1 RETEU XT1541, working phone with unlocked bootloader, so if I want, I can flash other ROMs.
Click to expand...
Click to collapse
Try flashing CM12.1 then.
Hey all, new poster but long time user of the site, just never needed an account until today lol. Anyways, just got a Pixel 5a5G that I am trying to install LineageOS on. I am following the instructions from here, and once I get to the point of flashing the vendor_boot partition, I receive this:
Code:
PS C:\Windows\system32> fastboot flash vendor_boot C:\Users\bobby\Downloads\vendor_boot.img
target reported max download size of 268435456 bytes
sending 'vendor_bootb' (98304 KB)...
OKAY [ 2.225s]
writing 'vendor_bootb'...
FAILED (remote: Not allowed to flash (vendor_bootb))
finished. total time: 2.307s
When running fastboost unlock bootloader, I receive this:
Code:
PS C:\Windows\system32> fastboot flashing unlock
...
(bootloader) Device already unlocked
OKAY [ 0.055s]
finished. total time: 0.056s
I have reflashed the stock firmware with the Android Flashing Tool to 13.0.0, both keeping the bootloader locked and unlocked. I have tried unlocking and relocking the bootloader. I used the utility's "full-flash" feature to flash both partitions, all to no avail. Research on here seems to point that the bootloader is locked, but fastboot says it isn't, settings is greyed out saying the bootloader is already unlocked, and fastboot mode on the phone says Device state: unlocked.
Any ideas?
Did you remove your screenlock and Google account before flashing?
Leberkuchen said:
Did you remove your screenlock and Google account before flashing?
Click to expand...
Click to collapse
Yes. I've flashed from a factory install with no passcode or account ever set. Same issue
From the output it's trying to write vendor_bootb??? Some combination of this should fix it:
-Make sure to use platform tools r33.0.3, the latest r34 has at least one known problem with fastboot and I don't trust it
-If you're using powershell you have to run the command as .\fastboot flash you can only run fastboot flash if you are in cmd
-Make sure both slots are on latest February firmware (probably not really necessary but a last ditch effort)