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...
Related
condensed version
encrypted phone, flashed, not working properly, used flashtool to try to use a stock image to restore phone, did not work, need help to save myself from a expensive waterproof brick
--------
The longer version of the story (in a galaxy far, far away....)
Just tried updating from last AOKP nightly (yer that old) to RR 5.4.0 but ran into issue flashing it namely from what i believe was from my phone being encrypted previously. It seemed to install the ROM well enough but i kept seeing this little error message popup during the recovery install (i did do a complete wipe etc)
Code:
E: cannot load volume /misc
but i assumed all well and good as it did not give a fail or anything so i continue on and try to install gapps for it but then get this error message
Code:
Install failed
E:cannot load volume /misc!
Finding update package…
Opening update package…
Verifying update package…
E: footer is wrong
E: signature verification failed
Installation aborted
E: cannot load volume /misc
accepting defeat after this failing after attempting again, rebooted the rom which loaded up well enough and tried to reinstall a different version of gapps, same problem, tried to install via fastboot same problem. Tried wiping the rom and formatting the internal memory via fastboot but got this
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
erasing 'userdata'...
OKAY [ 1.046s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.007s]
erasing 'cache'...
OKAY [ 0.043s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.008s]
finished. total time: 1.108s
could not flash the rom due to the android-info.txt issue with fastboot, flash a boot.img from RR, got the z1c running again and settled into a life without gapps and actually felt like it was a really good thing after a bit of research and finding alternatives but kept running into odd app errors and force closes and issues with receiving sms that forced me to have to figure out why it was not letting me install zips. Tried my luck on cm-12-20150402-NIGHTLY-amami build but had some issues with a few things got stuck in bootloop so decided i would try to start fresh so i moved on to my next step
Used this reference point for the ftf file and how to repair soft bricks http://forum.xda-developers.com/showthread.php?t=2631291&nocache=1, used flashtool after locking and unlocking my phone option (seen a few threads where people recommended it in the past) tried to flash the ftf file then got this (check attachment from flashtool for log), now really stuck phone reports that OS install failed and to try again but i know better than to keep doing the same thing over and over and to expect a different result so I ask the xda saviours for some assistance in getting me out of this problem.
Thank you for your time if you stopped in here to look at my request for help, it really is appreciated and to show that i will put a bounty/donation up for whoever solves my issue first as a sign of my good will and gratitude for your brains
try to use EMMA with UB to restore your phone.
VooDoo.maGiK said:
condensed version
encrypted phone, flashed, not working properly, used flashtool to try to use a stock image to restore phone, did not work, need help to save myself from a expensive waterproof brick
--------
The longer version of the story (in a galaxy far, far away....)
Just tried updating from last AOKP nightly (yer that old) to RR 5.4.0 but ran into issue flashing it namely from what i believe was from my phone being encrypted previously. It seemed to install the ROM well enough but i kept seeing this little error message popup during the recovery install (i did do a complete wipe etc)
Code:
E: cannot load volume /misc
but i assumed all well and good as it did not give a fail or anything so i continue on and try to install gapps for it but then get this error message
Code:
Install failed
E:cannot load volume /misc!
Finding update package…
Opening update package…
Verifying update package…
E: footer is wrong
E: signature verification failed
Installation aborted
E: cannot load volume /misc
accepting defeat after this failing after attempting again, rebooted the rom which loaded up well enough and tried to reinstall a different version of gapps, same problem, tried to install via fastboot same problem. Tried wiping the rom and formatting the internal memory via fastboot but got this
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
erasing 'userdata'...
OKAY [ 1.046s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.007s]
erasing 'cache'...
OKAY [ 0.043s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.008s]
finished. total time: 1.108s
could not flash the rom due to the android-info.txt issue with fastboot, flash a boot.img from RR, got the z1c running again and settled into a life without gapps and actually felt like it was a really good thing after a bit of research and finding alternatives but kept running into odd app errors and force closes and issues with receiving sms that forced me to have to figure out why it was not letting me install zips. Tried my luck on cm-12-20150402-NIGHTLY-amami build but had some issues with a few things got stuck in bootloop so decided i would try to start fresh so i moved on to my next step
Used this reference point for the ftf file and how to repair soft bricks http://forum.xda-developers.com/showthread.php?t=2631291&nocache=1, used flashtool after locking and unlocking my phone option (seen a few threads where people recommended it in the past) tried to flash the ftf file then got this (check attachment from flashtool for log), now really stuck phone reports that OS install failed and to try again but i know better than to keep doing the same thing over and over and to expect a different result so I ask the xda saviours for some assistance in getting me out of this problem.
Thank you for your time if you stopped in here to look at my request for help, it really is appreciated and to show that i will put a bounty/donation up for whoever solves my issue first as a sign of my good will and gratitude for your brains
Click to expand...
Click to collapse
will do, i think i may have had given emma a shot at saving my little z1c but will double check to be sure, what is UB? cant seem to find anything related to that acronym
cheers for the tip
Unlocked bootloader
Wysłane z mojego D5503 przy użyciu Tapatalka
cheers, emma did the trick, i think i had started to use it as once of my first solutions but then realised it was going to take forever downloading the file in it i decided to try other things first but forgot to come back to it
throw me your paypal dets for a free coffee
VooDoo.maGiK said:
cheers, emma did the trick, i think i had started to use it as once of my first solutions but then realised it was going to take forever downloading the file in it i decided to try other things first but forgot to come back to it
throw me your paypal dets for a free coffee
Click to expand...
Click to collapse
if flashtool fails and you have luckily a unlocked bootloader and fastboot works you can allways restore your phone with EMMA.
unfortunately EMMA works only with unlocked bootloader.
thanks for the offer. but to me it is enough that the phone working again :good:
Hello,
i have big problem wiht my D855. I'm trying to install recovery on my device via fastboot, because flashify method failed resulting in lack of recovery on my phone... When i enter "the place where recovery should be" boot certification error shows up and the only way to get rid of it is to re-insert the battery. Unfortunatelly fastboot is not working somehow. Command where it stuck while flashing says:
Code:
C:\adb\fastboot flash recovery reco.img
target reported max download size of 214743648 bytes
sending 'recovery' (15382 KB)...
OKAY [ 0.557s]
writing 'recovery'...
device:
Code:
[132740] fastboot: flash:recovery
Ive been already waiting about 40 minutes for this process to continue but of course nothing happened. After removing USB cable it says:
Code:
FAILED (status read failed (Too many links))
finished. total time: 649.362s
Other commands also do not work, they crash almost the same way but with sh.. i called "three dot bug"
Code:
C:\Users\Dom\Desktop\2>fastboot flashing unlock
...
It even dont reboot after typing:
Code:
C:\Users\Dom\Desktop\2>fastboot reboot-bootloader
rebooting into bootloader...
I have tried different cables, USB ports, different PC. I have lates LG drivers installed. What can I do. My OS is running but has many issues like not working wifi, crashing camera or random reboots (on new battery), so I cant use this phone anymore. It is impossible to revert it back to factory because recovery, which is used for this process is not working, so do fastboot...
Please help, I'm not android expert (and poor english user).
Cheers
Flash the latest TWRP onto it, it should let you boot. I had this problem a few days ago on a samsung tablet. I used odin on that. But you are going to have to match up the TWRP version and the android version you are running.
If you get TWRP working you wont have any problems, you can fix everything from there. Flash fulmics, unroot, what ever you want. Wipe the whole device ect. Make your goal trying to get TWRP on it.
Well, the problem is that I'm trying to flash TWRP now, it is the "reco.img" file, because I was trying to resolve the recovery instalation problem by changing name of file, which could be a problem somehow.
I found adb method to flash recovery:
Code:
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/yourrecovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Will it work? ADB is working fine, I already tried similar method when removing and reinstalling laf.
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
Having an issue with my XL. I've been on LOS 15.1 for a while and wanted to try out the new Pie image. I made a backup and fired up fastboot as usual. I left the -w tag on as I wanted a complete wipe. Fastboot failed while wiping userdata and now bootloops twice before dumping me in stock recovery. I am completely unable to format data while in stock recovery. Same when I boot TWRP through the PC. Stock recovery says it can't write a new EXT4 partition and TWRP says I have no internal storage, then throws a ton of errors. Flashing OEM images from Google (Oreo or Pie) results in the same thing.
Any ideas? For the first time in years I am stumped.
I'm able to flash just about anything with fastboot, but it will always fail on writing to userdata. I'm unable to erase, format, or mount the userdata partition, and fastboot will always reply "FAILED (remote: flash write failure)". This is using the most recent platform-tools under a root shell in Linux. Device and bootloader are unlocked.
I recently tried the original factory firmware (which includes a userdata.img fastboot file) to no avail. The same "FAILED (remote: flash write failure)" error persists.
caain said:
I'm able to flash just about anything with fastboot, but it will always fail on writing to userdata. I'm unable to erase, format, or mount the userdata partition, and fastboot will always reply "FAILED (remote: flash write failure)". This is using the most recent platform-tools under a root shell in Linux. Device and bootloader are unlocked.
I recently tried the original factory firmware (which includes a userdata.img fastboot file) to no avail. The same "FAILED (remote: flash write failure)" error persists.
Click to expand...
Click to collapse
Is your platform tools updated to the newest one?.
Edit I thought I was on the pixel 2 forum.
Could try to repartition the storage using a method similar to this one for the nexus 7? https://forum.xda-developers.com/nexus-7-2013/general/guide-repartition-nexus72013-to-t3599907
You would need to figure out the proper partition table for the Pixel though.
If you're 100% sure your platform-tools are fresh, you've got me stumped as well. I ran into tons of errors and such due to out of date tools when flashing Pie - obviously updating the tools fixed the issue.
Well I'd try external Type-C USB drive it enables external storage even if internal isn't working and fastboot flash your backup.
caain said:
I'm able to flash just about anything with fastboot, but it will always fail on writing to userdata. I'm unable to erase, format, or mount the userdata partition, and fastboot will always reply "FAILED (remote: flash write failure)". This is using the most recent platform-tools under a root shell in Linux. Device and bootloader are unlocked.
I recently tried the original factory firmware (which includes a userdata.img fastboot file) to no avail. The same "FAILED (remote: flash write failure)" error persists.
Click to expand...
Click to collapse
i got the same problem, i just downloaded the Platform-Tools and opened it in PowerShell and executed flash-all script and it worked
Flash all script is good but I'd rather use external storage .. it's nice to know that there's more than one way to fix the problem outside of platform tools
I had issues with Pixel before and the multi partition thing screwed me up, but the Unified_Android_ToolKit was able to fix it for me. Worth a try for sure. Download Google Factory Image and use the tool.
Thanks for all the help everyone. Lots of good ideas here that I'll save for next time. Ten years tinkering with phones and I've never gotten this stuck.
In the end I flashed back to the factory Pixel XL image (October 2016). Like the previous attempts, it failed on accessing userdata. I used fastboot to flash a userdata.img file again, which similarly failed but somehow the phone still booted after about 20 minutes.
I found similar threads for other phones where people were in the same situation, but nothing they tried did the trick.
Back up and running now.
Sent from my Pixel XL using Tapatalk
Very odd. Based off your last post I'm going to assume you are not sure what triggered the issue?
I am in over my head once more and could use help from someone more experienced.
The problem?
I bought an Alldocube M5X Pro tablet for my kids. First thing I did was root it using Magisk. I found the stock ROM, extracted the boot.img file, patched it with magisk manager, unlocked the bootloader and then used the fastboot command to flash the modified boot.img. Smooth sailing, worked flawlessly, kids were happy. 2 kids, 1 tablet, the happiness didn't last too long. They both wanted to use the tablet all the time. So when I found a sales promotion for the same model tablet, I decided to buy one more. Tablet #2 arrives, also an Alldocube M5X Pro, model T1006, Kernel version 3.18.60, Android version 8.0.0, same as tablet #1. I go through the same steps, but when I try to flash the modified boot.img file on the new tablet, it tells me Remote: Flash WRITE failure.
Here's what I did, step by step:
1. I verified that the 2nd tablet had the same build number as the 1st tablet. It did: T1006_V1.01_20200504
2. I enabled USB debugging in developer options and set the OEM Unlock option to ON
3. I trusted the connected computer in order to use the adb commands
4. I rebooted to the bootloader and executed the command Fastboot OEM unlock
C:\adb>fastboot oem unlock
...
(bootloader) Start unlock flow
OKAY [ 7.825s]
finished. total time: 7.826s
Click to expand...
Click to collapse
5. I executed the command Fastboot Flash boot magisk_patched.img with the img file in the path from where I'm running the command
C:\adb>fastboot flash boot magisk_patched.img
target reported max download size of 134217728 bytes
sending 'boot' (10253 KB)...
OKAY [ 0.468s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 0.633s
Click to expand...
Click to collapse
6. I've tried erasing the cache and user data partitions from the stock recovery and repeating step 5, but received the same error.
And that's where I'm stuck. The tablet can reboot from there, will detect tampering and proceed to run an erase command and starts with the Android Setup tutorial.
Just for the hell of it I tried flashing the stock ROM using the SP Flash tool for Mediatek devices, which works just fine. I then tried tried flashing an older build (0304) but still received the same error when trying to flash the boot.img
I also tried flashing a custom recovery as well as booting a recovery.img but in both cases the tablet ends up booting normally, I assume because the custom recovery isn't compatible with this device.
Everything I find online about flash write failure errors seems to indicate a defective emmc however most of those are specific to the Nexus 5 phone. The difference here seems to be that I can unlock the bootloader just fine, it stays unlocked as far as I can tell and I can overwrite with a new ROM, so I'm thinking the emmc is fine.
I'm just trying to puzzle this together from what I can find online, but I could really use the help of someone with more insight into the inner workings of Android.
Any help would be greatly appreciated.
After flashing 4 different ROMs, formatting the emmc completely and doing lord knows what else, it finally dawned on me that I could simply flash the patched boot image using the SP Flash tool instead of via Fastboot. It does wipe the data, and starts the Android setup wizard, but once that is completed, I was able to install Magisk Manager and download the missing files. The device rebooted after that and came back with systemless root.
Problem solved.