Related
Hi all,
on my Nexus 9, update to LRX21Q failed: After reboot, the android icon was shown with "error" below.
I suppose, update failed as my system is rooted with the method Chainfire posted in the development forum.
After an additional reboot, the previous firmware is still shown. The system does not offer the update anymore but claims to be up-to-date.
Any hints? Thanks in advance.
Maybe it's the modified kernel from Chainfire. Try to get back to the stock kernel and try again.
Download the factory image, flash recovery, boot, system & vendor.
Your software will be updated and you won't lose any data. You will lose root however.
I got the same error from OTA with no root. Only had 9 for 2 days, got OTA rite out of box no issue.
Yesterday for new build i get little error android icon upon reboot/install.
Obviously, something that is being changed by the "root" process is being checked DURING the update process. Probably a checksum on the boot partition. If it doesn't match, it bails on the update.
The likely reason for this is they acknowledge that you don't want to lose your root.
All it means is that you need to do the update manually.
It may be possible for a modified recovery to bypass this check, or possibly even be made to auto-root new boot images.
Thanks, guys. Will try as suggest above and post results.
Update: worked perfectly, needed to root again though.
StuMcBill said:
Download the factory image, flash recovery, boot, system & vendor.
Your software will be updated and you won't lose any data. You will lose root however.
Click to expand...
Click to collapse
has anyone tried this? i would like to update without losing data...
Flash through fastboot and you will be fine. Thats what I did then rerooted with CF autoroot
mk92595 said:
Flash through fastboot and you will be fine. Thats what I did then rerooted with CF autoroot
Click to expand...
Click to collapse
What's the fastboot command for the img? Do you flash as boot, system, etc?
zeebone said:
What's the fastboot command for the img? Do you flash as boot, system, etc?
Click to expand...
Click to collapse
Fastboot flash bootloader bootloader.img
Fastboot reboot-bootloader
Fastboot flash system system.img
Fastboot reboot-bootloader
Fastboot flash boot boot.img
Fastboot reboot-bootloader
Fastboot flash vender vendor.img
Fastboot reboot-bootloader
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot reboot
Not sure if I forgot one but I think thats all of them
mk92595 said:
Fastboot flash bootloader bootloader.img
Fastboot reboot-bootloader
Fastboot flash system system.img
Fastboot reboot-bootloader
Fastboot flash boot boot.img
Fastboot reboot-bootloader
Fastboot flash vender vendor.img
Fastboot reboot-bootloader
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot reboot
Not sure if I forgot one but I think thats all of them
Click to expand...
Click to collapse
Should there be a - sign between reboot and bootloader .. And is fastboot flash vender or vendor... Just making sure .
pantmunu said:
Should there be a - sign between reboot and bootloader .. And is fastboot flash vender or vendor... Just making sure .
Click to expand...
Click to collapse
Yes there should be a - sign and vendor. Sorry i'm not home so I don't have the files near me.
mk92595 said:
Yes there should be a - sign and vendor. Sorry i'm not home so I don't have the files near me.
Click to expand...
Click to collapse
Thank you sir .
Where can i find the images for download. Thx
Google for nexus factory image.
Sent from my Nexus 9 using XDA Premium HD app
Update failed on me too. Completely stock
UPDATE:
Apparently *some* devices didn't get the recovery updated with the last update (LRX21L).
The new update (LRX21Q) requires the newer version of the recovery to install.
Google really messed up the launch of the Nexus 9 with all the HW/SW quality control issues
Serious f#ck-up from Google really
Interesting thing I noticed: I restored factory images manually in order to unroot and the OTA was no longer available. I verified I was still running on L. I manually installed the update and it went in just fine.
Now waiting on the root package to be updated for the Q kernel. You can re-root but you will be running on the L kernel, not the Q kernel.
maarten08 said:
Update failed on me too. Completely stock
Click to expand...
Click to collapse
My too fck Google
Mine failed and Im not even rooted
And im not sure if it did the update as its not showing a new one. Im on L
Haven't seen it around here, so I thought sharing is caring:
Image of Lollipop 5.0 RETEUALL for XT1092 version LXE22.46-19
DOWNLOAD http://motofirmware.com/files/file/1055-reteuall-xt1092-50-lxe2246-19-cid7-cfcxmlzip/
Enjoy!
How to flash (taken from https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images and modified)
After downloading the image for your device:
Unzip the image.
Put your device in fastboot mode. [e.g. by using "$ fastboot reboot"]
NOTE: You must use the Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory). Please do NOT use the Android fastboot utility [better known as "mfastboot.exe" - so you probably change the command "fastboot" to "mfastboot"]
Follow the flashing steps in the .xml file that was included in the package.
A typical flashing sequence includes all these partitions, but might vary depending on your product - so please use the sequence in the .xml file in your package:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img_sparsechunk.0
$ fastboot flash system system.img_sparsechunk.1
$ fastboot flash system system.img_sparsechunk.2
$ fastboot flash system system.img_sparsechunk.3
$ fastboot flash system system.img_sparsechunk.4
$ fastboot flash system system.img_sparsechunk.5
$ fastboot flash system system.img_sparsechunk.6
$ fastboot flash system system.img_sparsechunk.7
$ fastboot flash modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot erase customize [leave that out if you have special customization from motomaker]
$ fastboot erase clogo [leave that out if you have special customization from motomaker]
$ fastboot reboot
You also have the option to erase all the data on your device with
$ fastboot erase userdata
$ fastboot erase cache
Click to expand...
Click to collapse
If you don't know how to flash it - don't! I am not responsible if anything goes wrong!
Whats the method to flash this ?
willy_907 said:
Whats the method to flash this ?
Click to expand...
Click to collapse
added a quick tutorial from motorola with a few modifications and notes.
Hi good afternoon , I Flashed with RSD LITE , and perfect. thank you very much
regards
Is there anyone who would be able to get hold of Motorola signed images? That would be aweosme.
Many thanks for this too
subhramani said:
Is there anyone who would be able to get hold of Motorola signed images? That would be aweosme.
Many thanks for this too
Click to expand...
Click to collapse
What would be the use for this? For devices without an unlockable bootloader? Just curious why this wouldn't suffice.
It will be useful when you want to lock the bootloader back again.
I'm sure you'll want it if you were from a country like mine.
subhramani said:
It will be useful when you want to lock the bootloader back again.
I'm sure you'll want it if you were from a country like mine.
Click to expand...
Click to collapse
Once you request for the unlock code and unlock the bootloader of your device its done, relocking won't help you to claim warranty if the service center guy looks it up.
nithin1992 said:
Once you request for the unlock code and unlock the bootloader of your device its done, relocking won't help you to claim warranty if the service center guy looks it up.
Click to expand...
Click to collapse
Worth keeping it justin case right?
I think it's time to finally unlock the bootloader of my phone, now I have the factory firmware for my model and variant
Thanks for this.
How to know if mine is RETEUALL or other?
Thanks
Edit: solved thanks
Hi, thanks for the upload.
I have a question, as my device is XT1092, the european version. But my carrier, Orange Spain, sells the Moto X unlocked, or they say so, and my phone version goes by 21.21.45.victara_oraeu.oraeuall.en.EU oraes. Should I be able to flash the ROM? I have experience doing so, so my question is just this one.
Thanks.
Yes, you can flash this image.
I myself flashed it on my French Orange Moto X (orafr).
-iNSiGhT- said:
Yes, you can flash this image.
I myself flashed it on my French Orange Moto X (orafr).
Click to expand...
Click to collapse
Good to know, thanks!
I'm pretty sure I flashed this file on my Orange Moto X but I still have "orafr" after "22.21.19.victara_reteu.reteuall.en.eu".
Is it the same for you ?
ichi go said:
Good to know, thanks!
I'm pretty sure I flashed this file on my Orange Moto X but I still have "orafr" after "22.21.19.victara_reteu.reteuall.en.eu".
Is it the same for you ?
Click to expand...
Click to collapse
I have that too, but since i flashed the retail modem (modem and fsg files) i think the "orafr" is related to the efs partition (something we don't "touch" during the flash process.
-iNSiGhT- said:
I have that too, but since i flashed the retail modem (modem and fsg files) i think the "orafr" is related to the efs partition (something we dont "touch" during the flash process.
Click to expand...
Click to collapse
OK, you're probably right.
Thanks for your answer.
NVM Posted in the wrong thread.
Hello to All
Can someone give me a good link to the mg file, the link is broken...
Thank you
cesarium said:
Hello to All
Can someone give me a good link to the mg file, the link is broken...
Thank you
Click to expand...
Click to collapse
http://www.androidgb.com/download-moto-x-2nd-gen-2014-android-5-0-lollipop-factory-image-784/
Nicolae-Daniel said:
http://www.androidgb.com/download-moto-x-2nd-gen-2014-android-5-0-lollipop-factory-image-784/
Click to expand...
Click to collapse
was searching for the 5.0 stock cause each time i've downgraded to stock 4.4.4 and OTA'd to the latest.. and it was timeboggling!
Thank you!
Hi guys
I forget to do a nandroid backup accidentally before test a build of cm12.1 that i make, the problem now installation stuck at 90%, and no progress after that, many tries on internal and external sdcard and with 2 different firmware, (perhaps was for dual sim verison) any solution for that before bring to assistance?
P.S: each day did new progress for cm12.1, hope to got booted rom.
Can't you flash the B052 version with Fastboot?
https://mega.nz/#!lEcGQZCC!X2fmOZ-ShY-Kx-9lwnSUN16Vo52_aU0i4K1KmdBW64Q
Normally you will then be on stock boot, recovery and system images.
olrak said:
Can't you flash the B052 version with Fastboot?
https://mega.nz/#!lEcGQZCC!X2fmOZ-ShY-Kx-9lwnSUN16Vo52_aU0i4K1KmdBW64Q
Normally you will then be on stock boot, recovery and system images.
Click to expand...
Click to collapse
Yes fastboot is working, will report if work, with the following order?
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
???
services in italy are really slow like one month for a stupid reparation.
No, all the commands are normally in a FLASH-ALL.bat file (yeah windows )
Commands are:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash cust cust.img
mfastboot flash system system.img
olrak said:
No, all the commands are normally in a FLASH-ALL.bat file (yeah windows )
Commands are:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash cust cust.img
mfastboot flash system system.img
Click to expand...
Click to collapse
alright, so should use mfastboot instead of fastboot?
Problem solved, thanx a lot :good::good::good::good::good:
hows your progress on that cm12.1 build that youre workin on?
ruben parra said:
hows your progress on that cm12.1 build that youre workin on?
Click to expand...
Click to collapse
i got progress on boot.img, we have hope
haky 86 said:
i got progress on boot.img, we have hope
Click to expand...
Click to collapse
Good luck man , I hope we get a custom rom soon
AmINoS007 said:
Good luck man , I hope we get a custom rom soon
Click to expand...
Click to collapse
I almost finish a cm-12.1 and doesn't boot due to blobs issue and still cannot copy them to the build :/
Probs
Hi everyone
What can I do to upgrade from b052 (after flash with fastboot ) because this Rom cause too much problems to my Huawei p8 lite so if you have a link for download an upgrade to replace B052
Then
haky 86 said:
Problem solved, thanx a lot :good::good::good::good::good:
Click to expand...
Click to collapse
Then did you uptade you're android system?is it possible to install new firmware from B052
So I've got Zenfone 5 A501CG. As you may know, all cyanogens/roms are made for A500CG. It works on A501CG aswell, but once you unlock bootloader on this model, camera will stop working. It's caused by incompatible .bin files for motherboard. But when you relock bootloader, camera is working again, just fine. I did this like 5 times and it always worked.
Now I reverted from Resurrection 5.5.9/TWRP 2.8.7.0 to Stock android (.87 - last update)/Stock recovery with relocked bootloader (like always) and the camera is still not working. I tried using different ifwi/dnx and tried to re-flash stock rom (ADB sideload) with formating cache/data. Camera is still not working.
I even tried to go back and flash 2.22.40.53 (KitKat 4.4.2). Still the same, camera not found.
Can someone help me? Do someone face the same issue?
u have to downgrade all the way back to KK, and then use this http://forum.xda-developers.com/android/general/asus-zenfone-5-root-ww-2-22-40-54-4-4-2-t3128704
I already did this, like mentioned. It didn't help at all.
Hi,
Before flashing your DNX/IFWI, you must downgrade your fastboot image to 2.21.40.30, this way:
Download the fastboot from 2.21.40.30 image
Flash it
Code:
fastboot flash fastboot fastboot-2.21.40.30.img
fastboot reboot-bootloader
Flash your DNX/IFWI
Thanks!
dgadelha said:
Hi,
Before flashing your DNX/IFWI, you must downgrade your fastboot image to 2.21.40.30, this way:
Download the fastboot from 2.21.40.30 image
Flash it
Code:
fastboot flash fastboot fastboot-2.21.40.30.img
fastboot reboot-bootloader
Flash your DNX/IFWI
Thanks!
Click to expand...
Click to collapse
Okay and then I can flash the newest fastboot then firmware right?
Masterfellow said:
Okay and then I can flash the newest fastboot then firmware right?
Click to expand...
Click to collapse
In that order,
fastboot from 2.21.40.30
dnx from latest version
ifwi from latest version
then you can do whatever you want after, like
boot from latest version
fastboot from latest version
dgadelha said:
In that order,
fastboot from 2.21.40.30
dnx from latest version
ifwi from latest version
then you can do whatever you want after, like
boot from latest version
fastboot from latest version
Click to expand...
Click to collapse
Alright, I'll get home and I'll try. Thanks for now.
dgadelha said:
In that order,
fastboot from 2.21.40.30
dnx from latest version
ifwi from latest version
then you can do whatever you want after, like
boot from latest version
fastboot from latest version
Click to expand...
Click to collapse
Oh my gosh it really works! Wow... I didn't expect that... Thank you so much man! Now install/update those 40apps again
Masterfellow said:
Oh my gosh it really works! Wow... I didn't expect that... Thank you so much man! Now install/update those 40apps again
Click to expand...
Click to collapse
Glad it helped! Thanks.
Tested on my own KB2003, work flawlessly. Useful for many cases.
I followed the GUIDE of @s3axel here : https://forum.xda-developers.com/t/...n-os-stock-recovery-with-adb-enabled.4084487/
All credits to him.
Basically, this modded Recovery just saved my a** )))) Just unzip using 7z then flash it to Recovery as normal.
LinhBT said:
Tested on my own KB2003, work flawlessly. Useful for many cases.
I followed the GUIDE of @s3axel here : https://forum.xda-developers.com/t/...n-os-stock-recovery-with-adb-enabled.4084487/
All credits to him.
Basically, this modded Recovery just saved my a** )))) Just unzip using 7z then flash it to Recovery as normal.
Click to expand...
Click to collapse
Can you share your file?
Rootk1t said:
Can you share your file?
Click to expand...
Click to collapse
Sure man, find attachment
Hi, I am facing a strange issue on OOS12 not able to factory reset or enter stock recovery it says boot/recovery.img damaged flash the correct one or contact support can any one help me out with this issue.
houstontaxi said:
Hi, I am facing a strange issue on OOS12 not able to factory reset or enter stock recovery it says boot/recovery.img damaged flash the correct one or contact support can any one help me out with this issue.
Click to expand...
Click to collapse
unpack your firmware, extract stock recovery.img and flash it.
But for flashing do I need to unlock bootloader or it can be done without unlocking?
houstontaxi said:
But for flashing do I need to unlock bootloader or it can be done without unlocking?
Click to expand...
Click to collapse
As far as i remember to flash partitions with stock firmware you don't need unlocked bootloader.
Rootk1t said:
As far as i remember to flash partitions with stock firmware you don't need unlocked bootloader.
Click to expand...
Click to collapse
If it needs to flash recovery the same way as we do for custom roms like fastboot flash recovery in platform tools then i tried that doesn't work to make it work bootloader needs to be unlocked I did that(unlocked the boot loader) then flashed stock recovery and it worked but after locking the boot loader with fastboot oem lock same issue happened again couldn't boot into recovery.
houstontaxi said:
But for flashing do I need to unlock bootloader or it can be done without unlocking?
Click to expand...
Click to collapse
To flash ANY partitions, u must unlock bootloader even if the partition is critical or not. And to prevent the boot/recovery image damaged error, u must flash stock boot/recovery images along with vbmeta.img ( also extracted from stock, same build ).
LinhBT said:
To flash ANY partitions, u must unlock bootloader even if the partition is critical or not. And to prevent the boot/recovery image damaged error, u must flash stock boot/recovery images along with vbmeta.img ( also extracted from stock, same build ).
Click to expand...
Click to collapse
I'm gonna try this also need to know if I have to flash boot.img and recovery.img as there are two files when extracted from the stock rom
houstontaxi said:
I'm gonna try this also need to know if I have to flash boot.img and recovery.img as there are two files when extracted from the stock rom
Click to expand...
Click to collapse
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
LinhBT said:
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
Click to expand...
Click to collapse
I'm gonna try that thanks for the help and I hope it resolves my issue with OOS A12 recovery as I don't face this kind of issue on OOS11
1
LinhBT said:
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
Click to expand...
Click to collapse
Hello, tell me that your recovery cannot decrypt the date section? I need to extract data from the phone, the phone won't boot into the system, I tried to boot into your recovery but I can't access the folders.
lenox30 said:
Hello, tell me that your recovery cannot decrypt the date section? I need to extract data from the phone, the phone won't boot into the system, I tried to boot into your recovery but I can't access the folders.
Click to expand...
Click to collapse
This is simply Stock Recovery with ADB enabled bro. It only can help u in some tasks which need to access adb via Recovery, it won't help to decrypt ur device and/or have any functions as other custom recovery