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, I recently installed official android 5.1 from factory source but now I have issues "missing" storage.
32GB Nexus 7 2013 (Wifi)
TOTAL: 26,9 GB
Used: 17,3GB
Free: 9,6GB
Theese numbers are not supposed to be what they are right out of the box with barely no apps installed and nothing else stored. I am supposed to have much more free space.
I followed this guide to install every .img file manually that was included in the official factory images.
Install instructions followed:
Flash bootloader and radio (radio does not appear on all devices, if it's not in your tgz, you don't need it)
fastboot flash bootloader <bootloader file name here>.img
fastboot flash radio <radio file name here>.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
NEXUS 9 ONLY - flash this as well
fastboot flash vendor vendor.img
If you want to wipe cache and user data (full wipe), flash these
fastboot flash cache cache.img
fastboot flash userdata userdata.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
The reason that I "manually" flashed every .img file is because I got errors when using the flash-all.bat file
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 842365088 bytes
error: update package missing system.img
Thanks in advance for help!
EDIT:
Confirmed: factory reset/data wipe in stock recovery solved the storage problem
Try formatting data with twrp. That fixed the no storage problem I had a while ago.
yosmokinman said:
Try formatting data with twrp. That fixed the no storage problem I had a while ago.
Click to expand...
Click to collapse
I haven't installed TWRP yet, do you know if it supports 5.1? Any chance that the stock recovery can do the same?
You could try a factory reset/data wipe in stock recovery. Latest twrp works fine.
yosmokinman said:
You could try a factory reset/data wipe in stock recovery. Latest twrp works fine.
Click to expand...
Click to collapse
Confirmed: factory reset/data wipe in stock recovery solved the storage problem
Thank you very much
my nexus 32gb is showing like 26.5gb after the update for 5.1 this is normal value? 6gb is consumed by the OS or something?
my device is fullwiped
I recently re-installed CM 12.1 and have found that I can't encrypt my phone. Every time I try to encrypt, the phone shows the Android working screen for about 5 seconds, then restarts. No encryption.
Very strange, bc previously I was able to encrypt while running the exact same version of CM. Stats below.
Sony Xperia Z1C
CM 12.1-20161016-NIGHTLY-amami
Recovery: TWRP 3.0.2-0
Any idea what I'm doing wrong? Thanks!
Hi,
most likely, this is because you formatted you data partition with a twrp that doesn't support decryption and hence your partition is too big now.
Try my build which support decryption (https://www.androidfilehost.com/?fid=24533103863142425), backup your stuff, format data and try again.
Cheers
most likely, this is because you formatted you data partition with a twrp that doesn't support decryption and hence your partition is too big now.
Click to expand...
Click to collapse
Thank you derf!
Question: I've also been unable to install AICP using this version of TWRP, but I've been able to install CM12 on multiple occasions. Do you think this is related?
Thanks!
@derf elot I can't seem to get the new recovery to install. Terminal says it's successful, but when I boot into recovery, it's still 3.0.2-0, and I get an error when I try to format data. Any ideas? Deets below.
Here's a readout from Terminal:
./fastboot flash recovery twrp-3.0.2-1.img
sending 'recovery' (11660 KB)...
OKAY [ 0.397s]
writing 'recovery'...
OKAY [ 0.774s]
finished. total time: 1.172s
Then I reboot, and then reboot again into recovery. I see TWRP 3.0.2-0. When I try to format data, I get
E:Unable to wipe '/data' - - unknown file system 'atuo'
Unable to format to remove encryptionEven though I'm not encrypted.
What am I doing wrong?
Recovery must be instaled in FOTA i think?
P.S. try Rashr app from the store to flash recovery to FOTA.
zlata said:
Recovery must be instaled in FOTA i think?
P.S. try Rashr app from the store to flash recovery to FOTA.
Click to expand...
Click to collapse
I just tried Rashr. Same results: Even though I'm installing TWRP 3.0.2-1, I still see TWRP 3.0.2.0 when I boot into recovery. And I'm still not able to format data.
How do I install via FOTA? Is there a fastboot or adb command?
Thank you!
@zlata would this command work?
Code:
fastboot flash FOTAKernel twrp-3.0.2-1.img
Hi,
yes, that should work. It might be because of some fstab settings I put in there.
Please try the attached one, unzip and flash the .img. Let me know.
Cheers
derf elot said:
Hi,
yes, that should work. It might be because of some fstab settings I put in there.
Please try the attached one, unzip and flash the .img. Let me know.
Cheers
Click to expand...
Click to collapse
Success! I was able to format data, restore from a backup, and encrypt my phone. Thank you @derf elot!!!
I'm still unable to install AICP for some reason, but it doesn't seem to be a TWRP issue. I'll solve in an AICP thread. Thank you!!!
Hello, when I install new update i forgot to backup /dev/block/mmcblk0p13 (modemimage) partition. I have backup from twrp but twrp not backup modemimage. Now i don't have IMEI and baseband is unknown. How to fix it ?
@edit: I fixed it, extract modemimage from B520 updater.app with huawei extractor. Flash modemimage with fastboot and it's working.
Several weeks ago I tried to install TWRP after permitting an OTA update to install V10.0.2.0.PDLMIFJ.
The TWRP installation failed and resulted in the "Destroyed Recovery".
The phone does boot and operate normally, except that it will not boot into recovery, and the OTA update to v10.0.3.0.PDLMIXM fails.
Is there a way to flash the recovery partition for the current version, or update to v10.0.3.0 and repair the partition without deleteing my data?
I tried using the 10.0.2.0 boot.img file from the thread "xda-developers Xiaomi Mi A2 Lite Xiaomi Mi A2 Lite Guides, News, & Discussion [GUIDE] Install Magisk with proper support for OTA updates by BubuXP" and the commands in the thread "xda-developers Xiaomi Mi A2 Lite Xiaomi Mi A2 Lite ROMs, Kernels, Recoveries, & Other Development [Official] [Recovery] TWRP for daisy by d1ngh, post #299".
This results in the following:-
a2-lite$ fastboot flash aboot_a boot.img
target reported max download size of 534773760 bytes
sending 'aboot_a' (27219 KB)...
OKAY [ 0.798s]
writing 'aboot_a'...
FAILED (remote: size too large)
finished. total time: 0.816s
I read mention of an 'aboot.img' but cannot find one for v10.0.2.0. How are these created or extracted from the released firmware?
Also mentioned is a 'flash.bat' script, but I cannot find the source of that file.
I use kubuntu LTS, but do have access to windows 8.1.
Just download V10.0.3.0 here: https://en.miui.com/download-354.html
Extract it and use the included batch file "flash_all_except_storage.sh" for Linux. This will preserve your data.
If you want to root your device afterwards, check this guide:
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
I suggest to create your own patched_boot.img with Magisk Manager 7.0 for Magisk 18.1.
Edit: As always, make a backup of your important data before and please don't use TWRP for our device, it's a piece of crap.
The fixed twrp version with SD card support is actually pretty good.
Sent from my Phh-Treble vanilla using Tapatalk
thorin0815,
Thanks for the advice. I tried to reflash using the then current installed 10.0.2.0 version but this resulted in a bootloop.
I then tried reflashing with 10.0.3.0 but this did not succeed either. So I used the xiaomi tool from windows to to reflash 10.0.2.0.
That worked with no apparent data loss and the phone has now updated OTA to 10.0.3.0.
Strange that it doesn't worked with 10.0.3.0, but your device works and in the end that's what counts.