Related
So after some messing around today with one of the cm12 builds, everytime I try to do anything in twrp I get the error "E: Unable to stat ' /data/power_supply_logger/power_supply_info.bin' " and i have no idea how to solve it. The only effect it seems to have is it makes restoring and backing up data fail at the last second (although as far as I can tell all of the data makes it). The error is always right after "updating partition details". I've tried reflashing 2 or three different versions of twrp (2.7.1.1, 2.6.3.1, and 2.8.1) as well as restoring stock vzw firmware through rsd lite as well as the gpe rom to no avail. Any help would be greatly appreciated.
Also, when flashing cm12, i get "mount: failed to mount /dev/block/platform/msm_sdcc. 1/by-name/userdata at /data: Device or resource busy"
StATicxTW0T said:
So after some messing around today with one of the cm12 builds, everytime I try to do anything in twrp I get the error "E: Unable to stat ' /data/power_supply_logger/power_supply_info.bin' " and i have no idea how to solve it. The only effect it seems to have is it makes restoring and backing up data fail at the last second (although as far as I can tell all of the data makes it). The error is always right after "updating partition details". I've tried reflashing 2 or three different versions of twrp (2.7.1.1, 2.6.3.1, and 2.8.1) as well as restoring stock vzw firmware through rsd lite as well as the gpe rom to no avail. Any help would be greatly appreciated.
Also, when flashing cm12, i get "mount: failed to mount /dev/block/platform/msm_sdcc. 1/by-name/userdata at /data: Device or resource busy"
Click to expand...
Click to collapse
I have the same problem with my moto g falcon XT1032.
Wen I try to flash CM 12 he gives the same error.
BinBug said:
I have the same problem with my moto g falcon XT1032.
Wen I try to flash CM 12 he gives the same error.
Click to expand...
Click to collapse
The first error or the second? I've narrowed the first down to a missing file in my data folder. Unfortunately rsd'ing doesn't help. If anyone'd be willing to upload it for me that'd be awesome. It's the bin file in /data/power_supply_logger/
The first error or the second error
StATicxTW0T said:
The first error or the second? I've narrowed the first down to a missing file in my data folder. Unfortunately rsd'ing doesn't help. If anyone'd be willing to upload it for me that'd be awesome. It's the bin file in /data/power_supply_logger/
Click to expand...
Click to collapse
Wen I try to flash te ROM he give me this:
Code:
Installing 'data/media/0/sideload.zip" ...
Checking for MD5 file ...
Skipping MD3 check : no MD5 file found
mont: failed to mount /dev/block/platform.msm_sdcc.1/by-name/userdata at /data: devices or resource busy
unmount of /data failed (-1): Devices or resource busy
E: Error Exexuting updater binary in zip ' /data/media/0/sideload.zip"
You say that i most change the bin file in /data/power_supply_logger/, but how?
link to rom that i use : CM12 for flacon
BinBug said:
Wen I try to flash te ROM he give me this:
Code:
Installing 'data/media/0/sideload.zip" ...
Checking for MD5 file ...
Skipping MD3 check : no MD5 file found
mont: failed to mount /dev/block/platform.msm_sdcc.1/by-name/userdata at /data: devices or resource busy
unmount of /data failed (-1): Devices or resource busy
E: Error Exexuting updater binary in zip ' /data/media/0/sideload.zip"
You say that i most change the bin file in /data/power_supply_logger/, but how?
link to rom that i use : CM12 for flacon
Click to expand...
Click to collapse
That error is caused by the version of TWRP you are using. Something about different versions and different updater scripts. Some have had sucess with 2.8.1, some with 2.6.3.1 and some with 2.7.1.1. You will need to try all three until you find the one that works for you. Do not touch the power supply file, that's whats causing my first error. Somehow it got deleted, and restoring to complete stock does not replace it, thats why i need someone to upload theirs.
I have an H811 with an unlocked boot loader and rooted with BETA-SuperSU-v2.67-20160121175247.zip. I do not have TWRP installed, but instead opt for fastboot boot trwp-xxx.img when I want to make a nandroid backup. I did not install TWRP specifically so I could use the OTAs when they come in from Tmo. The other day, one came in but the install fails. This is the error message. I'm not sure why GoogleTTS.odex and Hangouts.odex are missing.. I may have froze them in Titanium Backup or accidentally removed them during a bloat cleansing., but it doesn't seem to be barfing on those two Google packages.. just the boot partition. Why?
I've not installed any mod kernels. Only thing I can think of is the unlocked bootloader. I have a stock nandroid that I can restore to the phone, and then possibly apply the patch, but if this is due to the unlocked bootloader that won't matter.
Second question: I have a saved copy of the update.zip from Tmo. I've read that trying to install this from TWRP is a bad idea. Is there another way to kick off the install instead of waiting for the download from Tmo again every night?
Thanks
HTML:
Verifying current system...
failed to stat "system/app/GoogleTTS/oat/arm/GoogleTTS.odex": No such file or directory
failed to stat "system/app/Hangouts/oat/arm64/Hangouts.odex": No such file or directory
contents of partition "/dev/block/bootdevice/by-name/boot" didn't match EMMC:/dev/block/bootdevice/by-name/boot:28227584:bba9b35edd32cf7e117d238d9220ebfedb0b8155:28207104:f3a1ce0f44594bc48e57a0402d2044508ba3d391
file "EMMC:/dev/block/bootdevice/by-name/boot:28227584:bba9b35edd32cf7e117d238d9220ebfedb0b8155:28207104:f3a1ce0f44594bc48e57a0402d2044508ba3d391" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "EMMC:/dev/block/bootdevice/by-name/boot:28227584:bba9b35edd32cf7e117d238d9220ebfedb0b8155:28207104:f3a1ce0f44594bc48e57a0402d2044508ba3d391" has unexpected contents.
"EMMC:/dev/block/bootdevice/by-name/boot:28227584:bba9b35edd32cf7e117d238d9220ebfedb0b8155:28207104:f3a1ce0f44594bc48e57a0402d2044508ba3d391" has unexpected contents.
E:Error in /cache/update.zip
(Status 7)
[LGE][Recovery] Installation aborted. no valid image in CACHE.
I:Saving locale "en_US"
I:timed out waiting for key input; rebooting.
I:Saving locale "en_US"
[email protected]:/cache/recovery #
Nevermind. After some more searching, this is a really common problem with rooting and OTA. Sorry for the static. I'm new to all this.
Hello good night, my problem is the following, I have a huawei P9 EVA L09 and I can not install official firmware C432B136 I have no rom installed in the terminal, I have unlocked the bootloader, twrp 3.0.2.0 installed, cust432 installed with error across Of the twrp, it does not enter to install the firmware with the method of 3 buttons, they do not appear any red letters, nor appears emui installing the firmware, only the symbol of huawei without entering to install, I do not have emui recovery, some expert can lend a hand to me? Thank you for your cooperation in advance.
¿Can someone please help me?
Flash OEMinfo with TWRP to get emui recovery back.
http://nigella.modaco.com/files/oeminfo-huawei-p9-eval09-c432.zip
Thanks for helping me walk, the phone unlocked y frp unlock, having prepared in the card the dload b136, when I flash the c432 oeminfo from the twrp 3.0.2.0 b361-b378 Appears on the screen:
*
Full selinux support is present.
Mtp enabled
Installing zip file '/ sdcard / oeminfo-juawei-p9-eval09-c432.zip'
Checking for md5 file ...
Skipping md5 check: no md5 file found
Flashing oeminfo ...
Done!
Script succeeded: result was [1.000000]
Updating partition details ...
Failed to mount '/ product' (invalid argument)
Failed to mount '/' vendor '(invalid argument)
Failed to mount '/' version '(invalid argument)
is left without twrp And locked bootloader, I try to install with the method 3 buttons and does not go out emui installation.
What I can do?
Try to find a solution through the program SRKToolHuawei-Lod-Chong-V2.0-20161002 (ALREADY I SAW IN A VIDEO THAT ENTERS THE EMUI RECOVERY)
1st method twrp 3.0.2.0 b361-b378 (correct)
2º meto the update.app I try with several, Rollback_Nougat_a_MMEVA-L09C900B300, or the update EVA-L09_B136, or the EVA-L09_C432B378_v74832 with its information, or the C432B182 in the folder dload (WITH NO EMPLOYEES EMUI recovery)
3º flasheo el oeminfo-huawei-p9-eval09-c432.zip error:
*Full selinux support is present.
Mtp enabled
Installing zip file '/ sdcard / oeminfo-juawei-p9-eval09-c432.zip'
Checking for md5 file ...
Skipping md5 check: no md5 file found
Flashing oeminfo ...
Done!
Script succeeded: result was [1.000000]
Updating partition details ...
Failed to mount '/ product' (invalid argument)
Failed to mount '/' vendor '(invalid argument)
Failed to mount '/' version '(invalid argument)
(Even so it flashed because it blocks the bootloader and is left without twrp)
4º meto the Stock Recovery L09-EVA (correct)
5º I use the program SRKToolHuawei-Lod-Chong-V2.0-20161002 with the step 1 to unlock the bootloader since with that step it directly enters emui recovery in a video that I saw, (BUT TO ME MEET TWRP 3.0.2.0) (WITH THE 3 BUTTONS DOES NOT ENTER, IT IS ON THE HUAWEI LOGO)
Other data that do not explain if I am not mistaken .. in the bootloader appears depending on whether I enter the from the twrp:
Android rebboot reason:
Bootloader
NA
Rebboot_enter_fastboot_common_func
After flashing the oem if I enter with low volume and usb output:
Android rebboot reason:
AP_S_COLDBOOT
NA
Volumnkey_down_press_process_func
After flashing the twrp if I enter with low volume and usb comes out depending on how you give it:
Android rebboot reason:
AP_S_abnormal
NA
Volumnkey_down_press_process_func
or
Android rebboot reason:
AP_S_PMU
Press8s_restart
Volumnkey_down_press_process_func
What am I doing wrong because of my lack of experience and knowledge, can you help me?
First flash the same firmware that you had to restore ur phone to a working stat.
In srk tool flash stock recovery.
Find the firmware for ur phone and extract the zip,you will get a file update.app ,copy this file to a folder name 'dload' on ur SD card.
With the phone off,press 3 buttons,power volume up and down till the update start.
I already did it, it does not want to enter, it does not decide to enter, it must be damaged recovery, it does not enter for much that I try with the mode of 3 buttons, it must be wrong recovery emui, no Never comes the emui symbol, only the symbol of huawei, desperate, helps, Can post me some kind of complete help to follow, miss recovery miui
What is not entering?
To boot into recovery,you need to hold volume up + power till you see the huawei logo than remove power key and keep pressing volume up.
Remove any usb before doing this.
Not enter, I already did without usb, turning it off, many times, waiting for the vibration to release the power, and also with the 3 at the same time, there is no way to get the miui logo, the huawei continuously, no I have android start to work ... when I put the dload it well, in the sd card, I feel alone in this problem .. And there where the problem (internal), related to the twrp, must be interfering, my Lack of knowledge, any other method to follow? How to completely erase recovery and re-flash?
Sorry I don't understand what you did and what you use and which firmware.
Do you have unlocked bootloader? Do you have twrp installed? Can you boot twrp?
I have unblocked the bootloader and twrp 3.0.2.0 b361-b378, I explain something important about what twrp 3.0.2.0 b361-b378 shows, once having the twrp, when I unlock with the SRKToolHuawei step 1 instead of going to Logo de miui, it is directed to the twrp, when it is done with 3 buttons it never enters, it stays in huawei logo
1-First boot to twrp, wipe format data,it will ask you type yes.
2-aftet wiping data in twrp go to first page and press reboot and reboot recovery.
3 Flash this in twrp ,copy this 2 files to sd card so you can install.
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v73574/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...3574/f1/full/hw/eu/update_data_full_hw_eu.zip
I really appreciate it, this aside, inside wipes in the twrp comes this when doing wipes
formatting cache using make_ext4fs...
qipping data without wiping/data/nedia...
done.
updating partition details...
Failed to mount '/ product' (invalid argument)
Failed to mount '/' vendor '(invalid argument)
Failed to mount '/' version '(invalid argument)
I will follow his indications to the letter of what he said to me before, I will communicate you here.
Formatting and say if this appears ...
formatting cache using make_ext4fs...
you may need to reboot recovery to be able to use / data again.
updating partition details
Failed to mount '/ product' (invalid argument)
Failed to mount '/' vendor '(invalid argument)
Failed to mount '/' version '(invalid argument)
...done
In twrp " format data "not wipe cache. It should ask you to type yes to confirm.
Leave this... I already did
Formatting and say if this appears ...
formatting data using make_ext4fs...
you may need to reboot recovery to be able to use / data again.
updating partition details
Failed to mount '/ product' (invalid argument)
Failed to mount '/' vendor '(invalid argument)
Failed to mount '/' version '(invalid argument)
...done
Ok reboot to twrp recovery and flash the 2 files above.
Agree to take time to proceed.. it is downloading, is slow.. you are being of great help to the community and laggards that can happen this
One file has 10 min and the other 20 to proceed
HP96 said:
One file has 10 min and the other 20 to proceed
Click to expand...
Click to collapse
Good luck
Hello to all. Sorry for my English, I do not speak it very well. I have a p8 lite 2017 and I'm trying to flash a stock firmware downloaded from firmware finder. My problem is this: when I try to flash 2 of the 3 files (update.zip, full.zip), the twrp gives me an error and in particular
Updating partition details ....
........ done
Full SELinux support is present.
MTP Enabled
Installing zip file '/external_sd/update.zip'
Cheking for MD5 file found .....
Skipping MD5 check: no MD5 file found
mountencrypt: failed to mount / data: No such file or directory
Removing unneeded files ...
Removing empty directorys ....
add link type file ...
write radio image ...
check_write_data_to_partition, write data error
E: UNKNOWN COMMAND (ERRNO) (in red)
update_huawei_pkg_from_ota_zip: update package from zip failed
UPDATER PROCESS ENDED WITH ERROR: 7
ERROR INSTALLING ZIP FILE '/EXTERNAL_SD/UPDATE.ZIP' (in red)
Updating partition details ....
..... done
I can not solve the problem. I also changed twrp, but nothing has changed.
At the moment I can not turn on the phone because it is stopped on the screen "your device is booting ..."
I hope you can help me, I'm going crazy.
thank you so much
alex'82 said:
Hello to all. Sorry for my English, I do not speak it very well. I have a p8 lite 2017 and I'm trying to flash a stock firmware downloaded from firmware finder. My problem is this: when I try to flash 2 of the 3 files (update.zip, full.zip), the twrp gives me an error and in particular
Updating partition details ....
........ done
Full SELinux support is present.
MTP Enabled
Installing zip file '/external_sd/update.zip'
Cheking for MD5 file found .....
Skipping MD5 check: no MD5 file found
mountencrypt: failed to mount / data: No such file or directory
Removing unneeded files ...
Removing empty directorys ....
add link type file ...
write radio image ...
check_write_data_to_partition, write data error
E: UNKNOWN COMMAND (ERRNO) (in red)
update_huawei_pkg_from_ota_zip: update package from zip failed
UPDATER PROCESS ENDED WITH ERROR: 7
ERROR INSTALLING ZIP FILE '/EXTERNAL_SD/UPDATE.ZIP' (in red)
Updating partition details ....
..... done
I can not solve the problem. I also changed twrp, but nothing has changed.
At the moment I can not turn on the phone because it is stopped on the screen "your device is booting ..."
I hope you can help me, I'm going crazy.
thank you so much
Click to expand...
Click to collapse
After having a soft-brick I followed this instructions:
https://forum.xda-developers.com/p8...ck-rom-huawei-prague-pra-xxxc432b182-t3727816
My phone is running without problems
i have a note 8 sm n950 i done the android update a few months ago and and it got my phone stuck in a boot loop, i installed new firmware which i was able to use the phone again but lost data signal, i fixed that but now my calls and text are coming through with a german number (im in the UK) i have tried to install stock firmware using odin and keep getting sw rev check fail device 11 binary 6 (and other variations of that error) i have also tried clearing the cache and wiping the phone from the boot menu but no luck, could anyone help, i would be very grateful
Have you check that you have downloaded and installed the correct version of the OS on your device?
pazler said:
i have a note 8 sm n950 i done the android update a few months ago and and it got my phone stuck in a boot loop, i installed new firmware which i was able to use the phone again but lost data signal, i fixed that but now my calls and text are coming through with a german number (im in the UK) i have tried to install stock firmware using odin and keep getting sw rev check fail device 11 binary 6 (and other variations of that error) i have also tried clearing the cache and wiping the phone from the boot menu but no luck, could anyone help, i would be very grateful
Click to expand...
Click to collapse
The binary error you are getting is because you are trying to flash older filmware than what is already on the phone., this is not possible because of security updates. Downloading the latest filmware for you device should resolve this error, and then hopefully fix the other errors you face.
stonedpsycho said:
The binary error you are getting is because you are trying to flash older filmware than what is already on the phone., this is not possible because of security updates. Downloading the latest filmware for you device should resolve this error, and then hopefully fix the other errors you face.
Click to expand...
Click to collapse
im pretty sure i have tried the latest one for my phone, as i have tried many others but i was never 100% certain it was, could you point me in the direction of one?
pazler said:
im pretty sure i have tried the latest one for my phone, as i have tried many others but i was never 100% certain it was, could you point me in the direction of one?
Click to expand...
Click to collapse
In post number 2 in the thread below, you can install "samfirm" on your Pc, this will give you the latest update to download, at a fast speed. For region (on samfirm) put your service provider, ie BTU or XEU for the UK.
https://forum.xda-developers.com/galaxy-note-8/how-to/official-stock-firmware-update-odin-t3677072
stonedpsycho said:
In post number 2 in the thread below, you can install "samfirm" on your Pc, this will give you the latest update to download, at a fast speed. For region (on samfirm) put your service provider, ie BTU or XEU for the UK.
https://forum.xda-developers.com/galaxy-note-8/how-to/official-stock-firmware-update-odin-t3677072
Click to expand...
Click to collapse
seems to of worked fine, no problems yet, thank you!
pazler said:
seems to of worked fine, no problems yet, thank you!
Click to expand...
Click to collapse
Glad to hear :highfive:
stonedpsycho said:
Glad to hear :highfive:
Click to expand...
Click to collapse
sooooo.... it was working fine for a couple days then the phone froze with a glitched horizontal line on the screen, i rebooted the phone and thought nothing more of it. A day later did the same thing (different place in the screen this time) i have wiped the cache a few time times but it hasnt improved. It is also freezing on the samsung loading screen and or getting stuck in a boot loop, the phone does work normaly for short amounts of time (few hours or so) but keeps happening, i managed to copy this log from the recovery menu if any help
p.s this is simlar to the original problem i was having before i changed the firmware
fail to open recovery_cause(no such file or directory)#
#reboot recovery cause is [unknown]#
support single-sku
file-based OTA
supported API: 3
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
# manual mode v1.0.0#
remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT'(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/cid/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/cid/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/permissioins'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/permissioins'.(No such file or directory)
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : '/proc/device-tree/firmware/android/compatible' : no such file or directory
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : '/proc/device-tree/firmware/android/compatible' : no such file or directory
pazler said:
sooooo.... it was working fine for a couple days then the phone froze with a glitched horizontal line on the screen, i rebooted the phone and thought nothing more of it. A day later did the same thing (different place in the screen this time) i have wiped the cache a few time times but it hasnt improved. It is also freezing on the samsung loading screen and or getting stuck in a boot loop, the phone does work normaly for short amounts of time (few hours or so) but keeps happening, i managed to copy this log from the recovery menu if any help
p.s this is simlar to the original problem i was having before i changed the firmware
fail to open recovery_cause(no such file or directory)#
#reboot recovery cause is [unknown]#
support single-sku
file-based OTA
supported API: 3
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
# manual mode v1.0.0#
remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT'(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/cid/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/cid/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/permissioins'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/permissioins'.(No such file or directory)
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : '/proc/device-tree/firmware/android/compatible' : no such file or directory
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : '/proc/device-tree/firmware/android/compatible' : no such file or directory
Click to expand...
Click to collapse
This is beyond my knowledge. I would take a guess that you have some sort of hardware issue as flashing stock filmware usually resolves any software bug. Hopefully someone who has faced the same or someone more knowledgeable will be able to help you further.
HI Experts i am getting the same issue in my note 8 sm-n950f according to my knowledge i lost its efs and baseband partition by mistake and my phone now stuck on Galaxy Logo now the OEM System is locked by default i am not able to flash TWRP please Suggest me how can i recover pretty phone back in Normal Condition :crying:
mehroz1234 said:
HI Experts i am getting the same issue in my note 8 sm-n950f according to my knowledge i lost its efs and baseband partition by mistake and my phone now stuck on Galaxy Logo now the OEM System is locked by default i am not able to flash TWRP please Suggest me how can i recover pretty phone back in Normal Condition :crying:
Click to expand...
Click to collapse
As we have said many of times before, if you lost your EFS folder and you never made a backup of it then you're screwed and you'll need to send it to Samsung for repair because you can't use anyone else's EFS because the EFS holds your IMEI and the phones serial numbers and such. It's information that's never supposed to be removed or deleted.. However someone else said if you delete certain stuff in the EFS folder and then reflash it that it would work and I tried this method and it failed to work so I don't know any other way except sending it to Samsung repair facility.. It also requires root access which you obviously can't do since it's OEM is not unlocked so I really doubt there's anything you can do short of sending it to Samsung..
https://forum.xda-developers.com/ga...i-detect-sim-card-t4134733/page2#post83127549
This is the link but like I said this didn't work for me..