Database Users

Warning: Update to LRX21Q fails when rooted.

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

Meizu PRO 5 bootloop no recovery locked bootloader

Hi all,
I am in trouble with the PRO 5.
Actual situation:
No recovery mode available
The phone boots but when is time to go in the home screen, the screen becomes black and only the power button response so I only turn it off or restart.
Fastboot mode available but the bootloader is locked
I tried many time with the Multiupgrade tool and TestPCTool but the answer is "Token sign failed"
Could someone help me before to put the phone in the trash

Upppppp!!!!!

You could try to unlock it using "fastboot oem unlock", but if it works it probably wipes the userdata partition, and it may fail. If you manage to unlock it, just reflash the stock image, but without the bootloader.
If this doesn't work, there is a similar thread in a different forum which may help you:
https://forum.meizufans.eu/topic/5376/meizu-pro-5-have-rooted-rom-but-lost-recovery-phone-can-boot-pls-help

Daniel Abrecht said:
You could try to unlock it using "fastboot oem unlock", but if it works it probably wipes the userdata partition, and it may fail. If you manage to unlock it, just reflash the stock image, but without the bootloader.
If this doesn't work, there is a similar thread in a different forum which may help you:
https://forum.meizufans.eu/topic/53...rom-but-lost-recovery-phone-can-boot-pls-help
Click to expand...
Click to collapse
I know the italian guy of this 3D and I can tell u, "fastboot oem unlock" doesn't work unfortunately :crying:

Thanks Pycon.
He is right, no way to unlock the bootloader, at the moment

just try this. good luck man. http://forum.xda-developers.com/meizu-pro-5/how-to/meizu-customer-service-flash-tools-save-t3447678

tzzzz said:
just try this. good luck man. http://forum.xda-developers.com/meizu-pro-5/how-to/meizu-customer-service-flash-tools-save-t3447678
Click to expand...
Click to collapse
Thanks but tried many times: Token signature fail...

Have you tried flashing the whole system (20150923195421_demo_prd_stable) as described in the M86 firmware upgrade tutorial.pdf ?

st0rm77 said:
Have you tried flashing the whole system (20150923195421_demo_prd_stable) as described in the M86 firmware upgrade tutorial.pdf ?
Click to expand...
Click to collapse
Where is that tutorial?

DarginMahkum said:
Where is that tutorial?
Click to expand...
Click to collapse
It resides in the Meizu Tools post, but never mind that. I dove into the security and fastboot uses secure boot so unless there is an exploit your stuck.
Are you able to flash the boot partition ?
If so, you might be able to flash the recovery.img onto the boot (bootimg) partition. Then drop an update.zip into the root of userdata and reboot.
Good luck.

Hey Grumpy,
I extracted the kernel and ramdisk from the recovery image (flyme_5.6.1.19_daily). Unpack these files into a directory, then run
# fastboot boot kernel ramdisk
If it boots you can:
- erase to factory default
- maybe ?? flash /sdcard/update.zip ??
Good luck :good:

st0rm77 said:
Hey Grumpy,
I extracted the kernel and ramdisk from the recovery image (flyme_5.6.1.19_daily). Unpack these files into a directory, then run
# fastboot boot kernel ramdisk
If it boots you can:
- erase to factory default
- maybe ?? flash /sdcard/update.zip ??
Good luck :good:
Click to expand...
Click to collapse
Nope...
creating boot image...
creating boot image - 15699968 bytes
downloading 'boot.img'...
FAILED (remote: permission denied!)
finished. total time: 0.000s

Partition table doesn't exist

Hi, I try to flash a new boot.img, and it's printed the message Partition table doesn't exit.
Anyone have a solution for this.
Now, my mobile have a infinite bootloop
Thanks

Which boot.img did you try to flash?

cafernan said:
Hi, I try to flash a new boot.img, and it's printed the message Partition table doesn't exit.
Anyone have a solution for this.
Now, my mobile have a infinite bootloop
Thanks
Click to expand...
Click to collapse
Also show which command exactly did you use. "Partition table doesn't exist" error is shown when you try to flash partition which..doesn't exist - usually a typo in command. Also there are some "fake" Mi A1 being sold (Mi 5x with A1 ROM), verify that you have really A1 here https://www.mi.com/verify/#imei_en

Hey man Mi A1 has dual partition. You have to specify which partition you are flashing.
fastboot flash boot_a boot.img
(boot_a or boot_b depending upon your current slot)

mearjunsha said:
Hey man Mi A1 has dual partition. You have to specify which partition you are flashing.
fastboot flash boot_a boot.img
(boot_a or boot_b depending upon your current slot)
Click to expand...
Click to collapse
I was getting that error trying to flash my own personal backed up boot.img. I was using the
Code:
fastboot flash boot_a boot.img
command as well as trying slot b.
I got jack of it and just used MiFlash and flashed the rom without overwriting storage. Problem solved.

ludditefornow said:
I was getting that error trying to flash my own personal backed up boot.img. I was using the
Code:
fastboot flash boot_a boot.img
command as well as trying slot b.
I got jack of it and just used MiFlash and flashed the rom without overwriting storage. Problem solved.
Click to expand...
Click to collapse
thanks, problem solved

Need help also, where do you fill in code (fastboot flash boot_a boot.img)?
Can someone explain the given answer above with the two partition?

juby2 said:
Need help also, where do you fill in code (fastboot flash boot_a boot.img)?
Can someone explain the given answer above with the two partition?
Click to expand...
Click to collapse
wait for this answer too,

juby2 said:
Need help also, where do you fill in code (fastboot flash boot_a boot.img)?
Can someone explain the given answer above with the two partition?
Click to expand...
Click to collapse
What do mean, adb&fastboot ? You need it if you don't
want to flash with miflash or twrp.
https://forum.xda-developers.com/showthread.php?t=2317790
The mi a1 has two partition a and b, if you want to flash separately, but you don't have to or what is your question exactly ?
Edit: on one partition a or b you use your current system, the other one is for updating in the background like ota update.

I have custom ROM installed but after using OTA update i lost TWRP, now i have to flash it to certain partition A or B.
How do i know to which partition to flash it, A or B and how to check for that ???

i have that type of problem too
when i write fastboot system system.img it says
C:\platform-tools>fastboot flash system system.img
Sending sparse 'system' 1/38 (131056 KB) OKAY [ 5.453s]
Writing 'system' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed

godsavesmeeverytime said:
i have that type of problem too
when i write fastboot system system.img it says
C:\platform-tools>fastboot flash system system.img
Sending sparse 'system' 1/38 (131056 KB) OKAY [ 5.453s]
Writing 'system' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
Click to expand...
Click to collapse
Did you figure out how to solve it?

Zato83 said:
Did you figure out how to solve it?
Click to expand...
Click to collapse
no but i did recovered my phone using spflash you can do it too

godsavesmeeverytime said:
no but i did recovered my phone using spflash you can do it too
Click to expand...
Click to collapse
hell yeah hahahaha I get recover it back, but my goal gonna figure out how Install TWRP on my phone, thank for reply

wh
Zato83 said:
hell yeah hahahaha I get recover it back, but my goal gonna figure out how Install TWRP on my phone, thank for reply
Click to expand...
Click to collapse
hey where I can get the scatter-loading file for mi a1

Moto Z 8.0 Full firmware [stock][oreo][griffin]

Many thank @erfanoabdi for the link
https://androidfilehost.com/?fid=890278863836283516
extract ROM ,extract file attack ,put all to the same folder, (hold power + volume down to get into bootloader mode) and run file: retail_AS_800.bat ( no need to run commands)
Done.

Hey, thanks for the tool, just few questions, will this relock my device bootloader ? and am i taking the risk to hard brick it ? Do i need to have adb and fastboot installed ?
thanks for this tool and for your time

K1li4n said:
Hey, thanks for the tool, just few questions, will this relock my device bootloader ? and am i taking the risk to hard brick it ? Do i need to have adb and fastboot installed ?
thanks for this tool and for your time
Click to expand...
Click to collapse
No relock anything. No risk to hard brick. If you flash down to 711 and then OTA update,it will. No need adb and fastboot install. Install usb and motorola driver

thanks for the quick answer. no relock, so if something go wrong i would still be able to flash some custom and rsolve the issue , right ?

thuybang said:
Many thank @erfanoabdi for the link
https://androidfilehost.com/?fid=890278863836283516
extract ROM ,extract file attack ,put all to the same folder, (hold power + volume down to get into bootloader mode) and run file: retail_AS_800.bat ( no need to run commands)
Done.
Click to expand...
Click to collapse
Hi, at the end of the batch say
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
So all data will be erased ?
BTW, I ran the process and the phone went back to encrypted mode again, TWRP is not working any more and root access is gone..Any way to revert back ?

K1li4n said:
thanks for the quick answer. no relock, so if something go wrong i would still be able to flash some custom and rsolve the issue , right ?
Click to expand...
Click to collapse
Yes,sure.

[email protected] said:
Hi, at the end of the batch say
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
So all data will be erased ?
BTW, I ran the process and th phone went back to encrypted mode again
Click to expand...
Click to collapse
Yes,it will erese all.

thuybang said:
Yes,it will erese all.
Click to expand...
Click to collapse
And we lose custom recovery and root asscess

my phone reteu dual sim not retail can i flash this rom ?

t_assal said:
my phone reteu dual sim not retail can i flash this rom ?
Click to expand...
Click to collapse
If you unlockbootloader, i can say : yes.

Nice it works to me ,
I just wanted to know if now im stock with unlocked bootloader , so no updates ? Like security updates ?

lima002 said:
Nice it works to me ,
I just wanted to know if now im stock with unlocked bootloader , so no updates ? Like security updates ?
Click to expand...
Click to collapse
Unlock bootloader always get update as normal,guy. . Any update, security,system....

thuybang said:
Unlock bootloader always get update as normal,guy. . Any update, security,system....
Click to expand...
Click to collapse
Cool thanks

Thanx for this, updates working and all.. Only the wifi seems to be be working bad (no internet access, disconnecting) , although could be my connection..

Hi, can I flash 1650-05 retcn Android 7.0 with an unlocked bootloader on this firmware?

it should work on xt1650-03?
btw, my carrier is tefcl but i think that isn't important for flashing

thuybang said:
Many thank @erfanoabdi for the link
https://androidfilehost.com/?fid=890278863836283516
extract ROM ,extract file attack ,put all to the same folder, (hold power + volume down to get into bootloader mode) and run file: retail_AS_800.bat ( no need to run commands)
Done.
Click to expand...
Click to collapse
I try to flash it, but where is error on system.img_sparsechunk.14 flashing..
C:\adb-fastboot-latest\adb-fastboot-latest>fastboot flash system system.img_spar
sechunk.14
target reported max download size of 536870912 bytes
sending 'system' (151532 KB)...
OKAY [ 4.038s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 4.786s
Click to expand...
Click to collapse
And error on erasing DDR
C:\adb-fastboot-latest\adb-fastboot-latest>fastboot erase DDR
erasing 'DDR'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.035s
Click to expand...
Click to collapse
Phone now in boot loop. Can't start, but goes to fastboot.
How to flash it correctly.

mike331967 said:
I try to flash it, but where is error on system.img_sparsechunk.14 flashing..
And error on erasing DDR
Phone now in boot loop. Can't start, but goes to fastboot.
How to flash it correctly.
Click to expand...
Click to collapse
Can you try flash by RSD lite 6.2.4sofware?

thuybang said:
Unlock bootloader always get update as normal,guy. . Any update, security,system....
Click to expand...
Click to collapse
i got notification about security update (patch may 2018) but error while instaling. any solution? please help.

Ceptoz said:
i got notification about security update (patch may 2018) but error while instaling. any solution? please help.
Click to expand...
Click to collapse
Same here.
Help!

Stock ROM to UPDATE IN 2021

Hello, good day. I just wanted to ask, (Im using custom rom now and my old backup is nowhere to be found) If I am going to flash my device to official stock rom, like if I flashed the older version (lets say the MM) can I still update my device today (up to nougat) through OTA update?
i think huawei cloud is the site where we download OTA updates from but I think is already dead.
(sorry if my poiint is confusing, I just really don't know how to explain it clearly)

emmanueldlauron said:
Hello, good day. I just wanted to ask, (Im using custom rom now and my old backup is nowhere to be found) If I am going to flash my device to official stock rom, like if I flashed the older version (lets say the MM) can I still update my device today (up to nougat) through OTA update?
i think huawei cloud is the site where we download OTA updates from but I think is already dead.
(sorry if my poiint is confusing, I just really don't know how to explain it clearly)
Click to expand...
Click to collapse
Hi,
in fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
and post results.

thanks for resonding
(bootloader) :Elite ROM v7.7
(bootloader) HUAWEI VNS-L31
vendorcountry: hw/spcseas
FAILED (remote: 'invalid command')

emmanueldlauron said:
thanks for resonding
(bootloader) :Elite ROM v7.7
(bootloader) HUAWEI VNS-L31
vendorcountry: hw/spcseas
FAILED (remote: 'invalid command')
Click to expand...
Click to collapse
Okay, last question - single SIM or dual SIM?

Dual Sim

emmanueldlauron said:
flash my device to official stock rom
Click to expand...
Click to collapse
So if I not mistaken, your build number is VNS-L31C185 EMUI 5 (correct me if I'm wrong).
Firmware finder and Huawei old server are down, so download service ROM.
IMO now you have two possibilities:
A) flash Service ROM using dload method, guide can be found in ReleaseDoc folder. The process will erase all your data and lock the BL again!
B)
- from downloaded ROM extract BOOT.img
RECOVERY.img
SYSTEM.img
CUST.img via 'Huawei update extractor' , follow Guide
(Note: CUST.img on Nougat can be found in the second archive)
- In fastboot mode flash extracted partitions using commands
fastboot flash boot BOOT.img
fastboot flash recovery RECOVERY.img
fastboot flash system SYSTEM.img
fastboot flash cust CUST.img
- fastboot reboot
- Factory reset in stock recovery

-Alf- said:
So if I not mistaken, your build number is VNS-L31C185 EMUI 5 (correct me if I'm wrong).
Firmware finder and Huawei old server are down, so download Service ROM
IMO now you have two possibilities:
A) flash Service ROM using dload method, guide can be found in ReleaseDoc folder. The process will erase all your data and lock the BL again!
B)
- from downloaded ROM extract BOOT.img
RECOVERY.img
SYSTEM.img
CUST.img via 'Huawei update extractor' , follow Guide
(Note: CUST.img on Nougat can be found in the second archive)
- In fastboot mode flash extracted partitions using commands
fastboot flash boot BOOT.img
fastboot flash recovery RECOVERY.img
fastboot flash system SYSTEM.img
fastboot flash cust CUST.img
- fastboot reboot
- Factory reset in stock recovery
Click to expand...
Click to collapse
I don't have sd card on me right now. is there any way I can flash service rom without sd card?
Edit: and also this device is C636xxx.
neverming the first paragraph I said. I'm confused with CUST.img thing, I donwloaded the C635 update but there's no second archive on what I had downloaded

emmanueldlauron said:
flash service rom without sd card?
Click to expand...
Click to collapse
Nope.
emmanueldlauron said:
this device is C636xxx.
Click to expand...
Click to collapse
Okay, then download C636

-Alf- said:
Nope.
Okay, then download C636
Click to expand...
Click to collapse
Thanks for the tips and ideas, I somehow understand something new today.

emmanueldlauron said:
there's no second archive on what I had downloaded
Click to expand...
Click to collapse
VNS-L31_hw_xxxxx

-Alf- said:
VNS-L31_hw_meafnaf
Click to expand...
Click to collapse
Oh yeah. I just figured it out but had to rename that to update.app so update extractor can accept the file. Thanks by the way.

for now SYSTEM and CUST takes time to finish extracting.

-Alf- said:
So if I not mistaken, your build number is VNS-L31C185 EMUI 5 (correct me if I'm wrong).
Firmware finder and Huawei old server are down, so download service ROM.
IMO now you have two possibilities:
A) flash Service ROM using dload method, guide can be found in ReleaseDoc folder. The process will erase all your data and lock the BL again!
B)
- from downloaded ROM extract BOOT.img
RECOVERY.img
SYSTEM.img
CUST.img via 'Huawei update extractor' , follow Guide
(Note: CUST.img on Nougat can be found in the second archive)
- In fastboot mode flash extracted partitions using commands
fastboot flash boot BOOT.img
fastboot flash recovery RECOVERY.img
fastboot flash system SYSTEM.img
fastboot flash cust CUST.img
- fastboot reboot
- Factory reset in stock recovery
Click to expand...
Click to collapse
UPDATE: I did the B. they're all finished without any errors, but I ended with bootloop, like I can't go to recovery and when I tried to it vibrates twice and show nothing but just the huawei logo with "powered by android" texts.

emmanueldlauron said:
UPDATE: I did the B. they're all finished without any errors, but I ended with bootloop, like I can't go to recovery and when I tried to it vibrates twice and show nothing but just the huawei logo with "powered by android" texts.
Click to expand...
Click to collapse
Try command
fastboot erase userdata
and reboot.
Check your current build number etc.
https://forum.xda-developers.com/t/stock-rom-to-update-in-2021.4320501/post-85489493

-Alf- said:
Try command
fastboot erase userdata
and reboot.
Check your current build number etc.
https://forum.xda-developers.com/t/stock-rom-to-update-in-2021.4320501/post-85489493
Click to expand...
Click to collapse
emmanueldlauron said:
(bootloader) :Elite ROM v7.7
(bootloader) HUAWEI VNS-L31
vendorcountry: hw/spcseas
FAILED (remote: 'invalid command')
Click to expand...
Click to collapse
still the same with these

emmanueldlauron said:
still the same with these
Click to expand...
Click to collapse
Bro try this way out...
Download and install TWRP (if possible) and let me know
Upd.: nevermind, I forgot you don't have an sd card,.
Upd.2.: without SD you can try to flash Service ROM (or B361 firmware) using TWRP and sideload method. Unfortunately, sideload is Greek to me , so google it.

-Alf- said:
Bro try this way out...
Download and install TWRP (if possible) and let me know
Upd.: nevermind, I forgot you don't have an sd card,.
Upd.2.: without SD you can try to flash Service ROM (or B361 firmware) using TWRP and sideload method. Unfortunately, sideload is Greek to me , so google it.
B361 firmware is a fullOTA-MF-PV version, download and instructions here
Click to expand...
Click to collapse
I can still go fastboot mode and install everything without any errors but I don't why, it confuses me that let say I just flashed recovery (custom or stock) but when I'm going to access it (volume up + power button) phone just vibrates twice but nothing will happen.

emmanueldlauron said:
I can still go fastboot mode and install everything without any errors but I don't why, it confuses me that let say I just flashed recovery (custom or stock) but when I'm going to access it (volume up + power button) phone just vibrates twice but nothing will happen.
Click to expand...
Click to collapse
Flash TWRP over eRecovery, run command
fastboot flash recovery2 twrp.img
fastboot reboot
when a yellow warning appears on the screen, pres and hold Vol Up for 3 sec.
Edit: maybe your data partition is formatted with f2fs (after installing Elite ROM) , it should be ext4. I'm out of ideas bro, sorry.

-Alf- said:
Flash TWRP over eRecovery, run command
fastboot flash recovery2 twrp.img
fastboot reboot
when a yellow warning appears on the screen, pres and hold Vol Up for 3 sec.
Edit: maybe your data partition is formatted with f2fs (after installing Elite ROM) , it should be ext4. I'm out of ideas bro, sorry.
Click to expand...
Click to collapse
No problem. I think I hard bricked my phone, I just got boot logo and fastboot but I can't find any fix or solution or anything to do with this.
Flashing recovery or recovery2 finished w/o any errors but I can't boot to recovery.
Thanks for your help by the way. I appreciate it! Kudos and have a nice day. Keep safe.

emmanueldlauron said:
I think I hard bricked my phone,
Click to expand...
Click to collapse
IMO you only need an SD card and flash the Service ROM.