Hello,
First sry for my bad english.
I had try to flash Pie with adb fastboot but i had one error failed.
Device is xt1710-09 reteu.
This is the failed error> failed to parse build number in post-build-incremental
Is this a big problem because the phone boots normally good.
Try to update via OTA. Copy update file to phone memory and simply go to settings -> system update.
Related
Hello everyone
So I have a m8 and converted it to the GPE edition. I changed my CID & MID and installed 4.4.4. My phone was rooted and I installed custom recoveries and went back to the stock recovery.. Here is what went wrong.
Today the update 5.0.1 came, when I tried to install it the update was failing and said my Version is not the right one. So I found out, that I flashed an old recovery and because of that it could not install it. Ok, downloaded the original OTA of 4.4.4 extracted the recovery.img and flashed that one. Now the verification check went trough..
It startet installing and after 5 minutes the update failed! Saying something like, it could not create symlinks on the system... I tried again, and now it stops with this error:
fileexist(): check the existence of /system/lib/libgoogle_recognizer_jni_1.so failed, error no such file or directory() installation aborted...
My system partition is broken now and i cannot start any system anymore...
I would like to save my data or install anything that my phone is working again, but I want to keep my data.. My phone is encrypted! :/ I tried with custom recoveries, but they apparently don't support disk encryption on the m8...
I think I cannot flash 4.4.4 with RUU as this would also delete the data... adb backup only works if the system is up, because the shell command tells me that a system dialog will appear and ask me for my password....
Anybody has any suggestion how to save my data?
Thanks!
should be in Q&A mate
I have requiested the mods to move this
So first things first. You are not bricked, you are just stuck. Bricked means your device cannot boot, cannot turn on, cannot access any bootloaders or recovery.
You messed something up and it is failing to boot, it isnt bricked.
Second, running disk encryption on rooted devices is especially dangerous for these scenarios. Disk encryption attempts to prevent many of the things running roms, custom recoveries and such put on the device.
Now, I cannot recall if a full GPE version can do this or not, but from Fastboot you should be able to flash just the system partition. But being you are encrypted it may fail to access your old data. The command for that would be:
Fastboot flash system system.img (if you were able to obtain a system.img)
Again that works on Nexus devices, I cant recall if the GPE fastboot accepts it as well.
Wish you well, but honestly I would expect to lose your data. The reason the update failed the second time was because you are Rooted. 5.0+ has a new OTA system where any changes to the system partition can/will fail the OTA.
tschakk said:
Hello everyone
So I have a m8 and converted it to the GPE edition. I changed my CID & MID and installed 4.4.4. My phone was rooted and I installed custom recoveries and went back to the stock recovery.. Here is what went wrong.
Today the update 5.0.1 came, when I tried to install it the update was failing and said my Version is not the right one. So I found out, that I flashed an old recovery and because of that it could not install it. Ok, downloaded the original OTA of 4.4.4 extracted the recovery.img and flashed that one. Now the verification check went trough..
It startet installing and after 5 minutes the update failed! Saying something like, it could not create symlinks on the system... I tried again, and now it stops with this error:
fileexist(): check the existence of /system/lib/libgoogle_recognizer_jni_1.so failed, error no such file or directory() installation aborted...
My system partition is broken now and i cannot start any system anymore...
I would like to save my data or install anything that my phone is working again, but I want to keep my data.. My phone is encrypted! :/ I tried with custom recoveries, but they apparently don't support disk encryption on the m8...
I think I cannot flash 4.4.4 with RUU as this would also delete the data... adb backup only works if the system is up, because the shell command tells me that a system dialog will appear and ask me for my password....
Anybody has any suggestion how to save my data?
Thanks!
Click to expand...
Click to collapse
First, your phone isnt bricked, its not bricked as long as you can access HBOOT, second, why would you encrypt your phone? uhg... I dont know what to tell you, try RUUing to stock, but dont expect to keep your data...
I also had the idea with just flashing the system.img from fastboot. but that doesn't work..
target reported max download size of 1830617088 bytes
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.010s
i now try to flash it with dd directly to the block..
tschakk said:
I also had the idea with just flashing the system.img from fastboot. but that doesn't work..
target reported max download size of 1830617088 bytes
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.010s
i now try to flash it with dd directly to the block..
Click to expand...
Click to collapse
You can only flash boot and recovery individually, you would have to put system.img and android-info.txt in a zip and flash in ruu mode
UNBELIEVABLE!
I could restore the system with dd... Just copied the system.img from Android 4.4.4 to the block device.. now the phone is booting up and i can see my data... uffff.. :victory:
so now i will do a backup and then go on...
Solution
If someone should encounter the same issue, this is what I have done to fix it:
I didn't want to lose my data, so I did not reinstall the RUU.. I couldn't get my data with ADB backup, because you need a system display to do it. And I also couldn't find any recovery which supported device encryption for the m8.. So I thought to backup my data partition with 'dd' to an external SD card and then if necessary I would reinstall the full system with RUU..
Code:
$ cat /fstab.qcom #to find the needed partitions
$ dd if=</dev/block/DATA-DEVICE> of=/external-sd/backup.bin
Now I knew I had a backup and was on the safe side. So I wanted to try to rewrite the system partition with the system.img from 4.4.4 GPE RUU. But fastboot flash didn't work. I always got this error message:
Code:
$ fastboot flash system system.img
...
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.010s
So what the hell, I used 'dd' also for this... :
Code:
$ cat /fstab.qcom #again to find the needed partitions
$ dd if=/external-sd/system.img of=</dev/block/SYSTEM-DEVICE>
And this actually worked, my m8 booted up with Android 4.4.4. First thing I did when Android booted was a full Android backup with adb.. To be safe to have my data back, because I didn't really know how to extract my encrypted data from the bin file I've created before... Then I just installed the update to 5.0.1 and this time it worked...
Hi all!
I'm in a big trouble. Recently I bricked my M8s, and I had to get back to stock. Unfortunately, RUU for my phone didn't work (constant htc_fastboot crashes during the process), and trying to flash zip from bootloader ended in "Device halted due to Large Image update fail!" error, so I had to flash the raw system.img image to the /system partition in twrp. The OS eventually booted up but now I'm unable to apply any system upgrade! While installing downloaded update in recovery I get this error:
Code:
Verifying current system...
/dev/block/bootdevice/by-name/system has been remounted R/W
reflash device to reenable OTA updates
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
The same thing happens when I try to apply update from OTA package provided by mr Lalleman.
I don't know anymore what to do, can someone help?
Hey Guys I need your help.
I think I bricked my OnePlus 3. (BTW yes its unlocked)
What still works:
1. Fastboot
2. TWRP and Stock recovery
3. ADB Sideload
I use twrp 3.1.0-0
Fastboot looks like this:
FASTBOOT MODE
PRODUCT_NAME: msm8996
VARIANT - MTP UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMER - [censored]
SECURE BOOT - enabled
DEVICE STATE - unlocked
But I cant boot into any system. I think I corrupted the /data partition or sth.
What I tried:
1. Flashing boot.img and system.img via fastboot -> Result: Still won't boot. I get the Oneplus and android logo and a blackscreen after this.
2. Flashing stock rom / lineage rom / newest stock rom via TWRP Sideload or Stock-recovery Sideload -> TWRP gives me this error: Updater process ended with ERROR: 7
Any Ideas?
Premaider said:
Hey Guys I need your help.
I think I bricked my OnePlus 3. (BTW yes its unlocked)
What still works:
1. Fastboot
2. TWRP and Stock recovery
3. ADB Sideload
I use twrp 3.1.0-0
Fastboot looks like this:
FASTBOOT MODE
PRODUCT_NAME: msm8996
VARIANT - MTP UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMER - [censored]
SECURE BOOT - enabled
DEVICE STATE - unlocked
But I cant boot into any system. I think I corrupted the /data partition or sth.
What I tried:
1. Flashing boot.img and system.img via fastboot -> Result: Still won't boot. I get the Oneplus and android logo and a blackscreen after this.
2. Flashing stock rom / lineage rom / newest stock rom via TWRP Sideload or Stock-recovery Sideload -> TWRP gives me this error: Updater process ended with ERROR: 7
Any Ideas?
Click to expand...
Click to collapse
Flash stock recovery and flash stock oos
v.konvict said:
Flash stock recovery and flash stock oos
Click to expand...
Click to collapse
says "installation failed" when I try to install stock oos on stock recovery via adb sideload
edit: If I manually flash (via fastboot) boot.img and system.img and then twrp recovery twrp says I do not have a system installed. why that?
edit2: while flashing system.img it first says "Invalid sparse file format at header magi" but then continues normally. does this help?
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
try this
save all your data before
Spector_Prophet said:
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
try this
save all your data before
Click to expand...
Click to collapse
He could also try the one that flashes OxygenOS 4.0.3: Newer unbrick tool
Hey guys, coming from 8.0.0, trying to flash OTA for 8.1 that was just released.
Unfortunately, after reboot to recovery, pressing power + vol up, choosing to sideload from adb, and running "adb sideload [ota filename].zip" I get the following error on my phone:
E: failed to verify whole-file signature
Update package verification took 77.5s (result 1).
E: Signature verification failed
E: error: 21
I've confirmed I'm using the latest sdk platform tools, and initially I figured it might have been a bad ota file download so I tried downloading a 2nd time but got the same results. I then checked the SHA256 hash of the file and it matched what the Google images pages says it should be so the download isn't corrupt. I'm stock, other than an unlocked bootloader (and critical), magisk, and flash kernel. Any ideas what the heck is going on here??? Thanks!
ohlin5 said:
Hey guys, coming from 8.0.0, trying to flash OTA for 8.1 that was just released.
Unfortunately, after reboot to recovery, pressing power + vol up, choosing to sideload from adb, and running "adb sideload [ota filename].zip" I get the following error on my phone:
E: failed to verify whole-file signature
Update package verification took 77.5s (result 1).
E: Signature verification failed
E: error: 21
I've confirmed I'm using the latest sdk platform tools, and initially I figured it might have been a bad ota file download so I tried downloading a 2nd time but got the same results. I then checked the SHA256 hash of the file and it matched what the Google images pages says it should be so the download isn't corrupt. I'm stock, other than an unlocked bootloader (and critical), magisk, and flash kernel. Any ideas what the heck is going on here??? Thanks!
Click to expand...
Click to collapse
Try downloading the November factory image, unzip and edit the flash-all.bat and remove the "-w" at the end
Reboot into bootloader and run flash-all.
This will remove flash kernel and magisk
Then try to take the December ota
Dielahn said:
Try downloading the November factory image, unzip and edit the flash-all.bat and remove the "-w" at the end
Reboot into bootloader and run flash-all.
This will remove flash kernel and magisk
Then try to take the December ota
Click to expand...
Click to collapse
Thanks! I decided to try a slightly different route and just ended up downloading the full December (8.1) image, then removed the "-w" as suggested, and ran the "flash-all.bat" script from fastboot/bootloader mode. Booted back up perfectly fine with data intact and now just re-patching boot.img so I can get Magisk back up and running…running into another Magisk related issue but otherwise looks good. Thanks!
I have received a OTA update today 8.0.0.340 (559 MB)(current version 8.0.0.320). But I am unable to install the update due to TWRP recovery and unlocked bootloader.
Is there a way to install update it without flashing stock firmware again?
Download FullOTA firmware for 8.0.0.320-C675-D4 (Make sure your version match correctly)
Extract that firmware with Huawei Update Extractor
You will find RECOVERY_RAMDIS.img in the folder. (not eRecovery)
Boot into fastboot mode:
Power Off > Connect USB cable to PC > Plug USB to phone and hold Volume down
Make sure device is connected by typing: fastboot devices
Flash Stock Recovery by typing: fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
Reboot
You can now update using OTA.
(I always recommend Factory Reset for major updates , but it's optional. Also log out off Google Account before factory resetting)
Hi @antariksh , thx for the brief tutorial. After flash stock recovery, can I flash the 1.7GB Firmware file or do I need to upgrade via OTA?
Also, got this error while flashing recovery:
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.889s
Any idea on how to extract version.img from stock ROM?
techack said:
Hi @antariksh , thx for the brief tutorial. After flash stock recovery, can I flash the 1.7GB Firmware file or do I need to upgrade via OTA?
Also, got this error while flashing recovery:
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.889s
Click to expand...
Click to collapse
What's your current build number and what command are you using to flash stock recovery?
You should try the OTA first and factory resetting the device will get you back to a Fresh stock version. Unless you know exactly which version to flash for your device.
You can also use HWOTA or HuRUpdater if you are on TWRP. But go through the entire thread thoroughly.
I have bricked my device for silly reasons, although I got Honor to replace entire SoC for free.
Flashing on EMUI devices is still not as robust as Stock Android ROMs
Thanks for your prompt reply, will try during next weekends and let you know.
Also, some other way to contact u quickly like Telegram/Whatsapp? so that I don't mess things up