Hi, i'm experiencing some crazy battery drain for a while and now i decided to contact htc support, before send the device to the worst support ever, i tried the battery stats reset method 2 weeks ago and nothing has improved.
While factory resetting i noticed this error:
E: can't open /sys/class/power_supply/battery/capacity error
Before send the device i want to try to fix this any solution?
Sc6oTch said:
Hi, i'm experiencing some crazy battery drain for a while and now i decided to contact htc support, before send the device to the worst support ever, i tried the battery stats reset method 2 weeks ago and nothing has improved.
While factory resetting i noticed this error:
E: can't open /sys/class/power_supply/battery/capacity error
Before send the device i want to try to fix this any solution?
Click to expand...
Click to collapse
I noticed the same error message on mine while wiping the partition cache but haven't found any explanation or fix online. Have you found out something in the meantime?
Flash RUU.
Benny-Boy said:
Thank you. Need to get the following HTC Stock ROM.
Software No. 3.16.401.2 (for Europe)
Cannot find an official HTC link.
Click to expand...
Click to collapse
It's the most post posted ruu here at xda at the moment i guess, it's been reposted in many different threads.
Open google :
3.16.401 ruu HTC10 XDA
I bet you will find it instantly
https://drive.google.com/drive/folders/1gXmx0QDCuoEWWpx0p6g_wIdC_-gPGa9O
There, and i am not even online for like 15 minutes.........
Benny-Boy said:
D'OH! The moral of the story... Seek and ye shall find.
Thank you. I'll try that (Flash RUU) when I get the Stock ROM.
Click to expand...
Click to collapse
Search boxes are made on XDA for a specific reason mate, so are the XDA rules which clearly state sto use them
i edited my previous post, just because its such a nice Sunday.
Benny-Boy said:
D'OH! The moral of the story... Seek and ye shall find.
Thank you. I'll try that (Flash RUU) when I get the Stock ROM.
Click to expand...
Click to collapse
That doesn't make sense. Flashing RUU will give you the stock ROM.
Benny-Boy said:
I would actually like the stock rom for now as HTC haven't given any answers regarding the "E:can't find /sys/class/power_supply/battery/capacity" error on the Recovery Mode screen.
But if you have any further info on what you reckon I wouldn't mind hearing it. Many thanks.
Click to expand...
Click to collapse
I have no idea what you are after. Flash this ruu and you are on htc stock software. Please don't make this so confusing for yourself.
Benny-Boy said:
Nothing confusing here.... Just saw someone reporting exactly the same issue that I am seeing.... And here we are.
Click to expand...
Click to collapse
Im talking about the stock rom software.......the ruu is exactly that, so flash that first and see if it solves anything.
Reading your text make me think you wanted some official HTC website with the stock software, the ruu posted here is 100% the full stock software.
------nevermind-----
?
Hello. Can someone who tried the ruu confirm it fixes the issue?
1potato said:
Hello. Can someone who tried the ruu confirm it fixes the issue?
Click to expand...
Click to collapse
What issue?
1potato said:
Hello. Can someone who tried the ruu confirm it fixes the issue?
Click to expand...
Click to collapse
Noticed this problem just yesterday on my 10, bought 2nd hand 2 months ago.
It has (and i knew) the battery problem, like over 25% overnight discharge.
The phone was already soff and personalized from the previous owner.
As oreo viper news got me to upgrade to oreo (by ruu nougat and ota to oreo), when i open recovery just noticed this error.
This file (/sys/class/power_supply/battery/capacity) on other rooted device just has current battery percentage (just a number like 52 as 52%)so i just don't understand the error.
Going to try:
root and twrp on the device; edit file permissions, ruu again to see if it makes any good.... also wold like to get oreo 401 europe in exe format (still searching np)
If i won't get back here in the mean time, just quote me to get my attention to see if i got any news regarding this error.
yldlj said:
What issue?
Click to expand...
Click to collapse
the "E:can't find /sys/class/power_supply/battery/capacity" error on the stock Recovery Mode, being discussed from the beginning of this thread...
Kind regards to all!
EDIT:
So, had stock Oreo 401 (Europe) and on stock recovery there is this error above.
Put twrp on it, rooted it and started the phone with stock FW rooted. With a root explorer went to the directory of this file "capacity" (in twrp the file manager interpreted this
"capacity" file as a folder and it could not open it) and it gave an error opening this file with a editor. According to the file explorer this file was corrupted, had no permissions and was as if the file system had an error there. Did not do anything to this file nor the file system.
Gone to twrp, wiped everything to be able to flash correctly a custom Oreo FW. After reboot, as custom fw was rooted already, just installed a root explorer and to my surprise the file "capacity" was seen by the explorer as a file containing data, had permissions and after open it it had the current battery capacity.
On stock oreo and on custom oreo, the battery behaved the same way. On custom oreo, disabled many background services (all google related also) and still had the same battery discharge.
My next step (in a few days) is to downgrade to MM and check the battery behavior, see if it discharges as much as on N or O but my guess is that its needed to replace the battery. Just need to get a official battery as there are around many fake htc 10 batteries. As i do mobile repairs i know how bad (horrible) some batteries are and some may even damage the phone behind repair! Not to tell about the problem opening our incredibly beautiful but very hard to disassemble HTC 10!
Take care!
яι¢αя∂σ said:
Noticed this problem just yesterday on my 10, bought 2nd hand 2 months ago.
It has (and i knew) the battery problem, like over 25% overnight discharge.
The phone was already soff and personalized from the previous owner.
As oreo viper news got me to upgrade to oreo (by ruu nougat and ota to oreo), when i open recovery just noticed this error.
This file (/sys/class/power_supply/battery/capacity) on other rooted device just has current battery percentage (just a number like 52 as 52%)so i just don't understand the error.
Going to try:
root and twrp on the device; edit file permissions, ruu again to see if it makes any good.... also wold like to get oreo 401 europe in exe format (still searching np)
If i won't get back here in the mean time, just quote me to get my attention to see if i got any news regarding this error.
the "E:can't find /sys/class/power_supply/battery/capacity" error on the stock Recovery Mode, being discussed from the beginning of this thread...
Kind regards to all!
EDIT:
So, had stock Oreo 401 (Europe) and on stock recovery there is this error above.
Put twrp on it, rooted it and started the phone with stock FW rooted. With a root explorer went to the directory of this file "capacity" (in twrp the file manager interpreted this
"capacity" file as a folder and it could not open it) and it gave an error opening this file with a editor. According to the file explorer this file was corrupted, had no permissions and was as if the file system had an error there. Did not do anything to this file nor the file system.
Gone to twrp, wiped everything to be able to flash correctly a custom Oreo FW. After reboot, as custom fw was rooted already, just installed a root explorer and to my surprise the file "capacity" was seen by the explorer as a file containing data, had permissions and after open it it had the current battery capacity.
On stock oreo and on custom oreo, the battery behaved the same way. On custom oreo, disabled many background services (all google related also) and still had the same battery discharge.
My next step (in a few days) is to downgrade to MM and check the battery behavior, see if it discharges as much as on N or O but my guess is that its needed to replace the battery. Just need to get a official battery as there are around many fake htc 10 batteries. As i do mobile repairs i know how bad (horrible) some batteries are and some may even damage the phone behind repair! Not to tell about the problem opening our incredibly beautiful but very hard to disassemble HTC 10!
Take care!
Click to expand...
Click to collapse
hello, have you solved the problem? If so, what are your paths?
Related
Hi, I just received my P6 and rooted it using eRoot. I have tried upgrading to B125 (running B109 out the box) by downloading the B125 file, passing it to dload on SD and performing a local upgrade, once the device boots to perform this it immediately says FAIL, and if i select the file manually it says "E:\signature verification failed" any ideas on how to solve this? Am I meant to update to something else inbetween before jumping to B125? (I've downloaded the file twice just to make sure it isn't corrupted or anything). I am a complete noob with this device, used to doing this sort of thing through CWM on my Nexus 7.
I have looked around this forum and seen various answers involving using TWRP first which if I could avoid I'd like to avoid as my aim is to load stock firmware without any of the bloatware that comes with my service provider, I'll leave the CFW stuff like AOSP for my tablet.
Any help would be greatly appreciated!
JK666 said:
Hi, I just received my P6 and rooted it using eRoot. I have tried upgrading to B125 (running B109 out the box) by downloading the B125 file, passing it to dload on SD and performing a local upgrade, once the device boots to perform this it immediately says FAIL, and if i select the file manually it says "E:\signature verification failed" any ideas on how to solve this? Am I meant to update to something else inbetween before jumping to B125? (I've downloaded the file twice just to make sure it isn't corrupted or anything). I am a complete noob with this device, used to doing this sort of thing through CWM on my Nexus 7.
I have looked around this forum and seen various answers involving using TWRP first which if I could avoid I'd like to avoid as my aim is to load stock firmware without any of the bloatware that comes with my service provider, I'll leave the CFW stuff like AOSP for my tablet.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Make sure you unplugged the usb cable when upgrading. :good:
Nope
warea said:
Make sure you unplugged the usb cable when upgrading. :good:
Click to expand...
Click to collapse
Yeah no, just retried it without any USB connection)(charging or PC) and it gives me the same error.
JK666 said:
Yeah no, just retried it without any USB connection)(charging or PC) and it gives me the same error.
Click to expand...
Click to collapse
Do you have enough battery? It failed for me once when I was at a low charge.
Battery level is fine
bokchoi2020 said:
Do you have enough battery? It failed for me once when I was at a low charge.
Click to expand...
Click to collapse
It was sitting on 89% charge when I initiated the procedure...
Any idea if using CWMR from this link: http://forum.xda-developers.com/showthread.php?t=2417919 would be any better? It keeps stock recovery, just figured another option wouldn't hurt?
JK666 said:
It was sitting on 89% charge when I initiated the procedure...
Any idea if using CWMR from this link: http://forum.xda-developers.com/showthread.php?t=2417919 would be any better? It keeps stock recovery, just figured another option wouldn't hurt?
Click to expand...
Click to collapse
Try to do a MD5 sum check. Probably your download or copying to SD card is corrupted.
Redownload the B125, but worse comes worse, try B118 or B122.
bokchoi2020 said:
Try to do a MD5 sum check. Probably your download or copying to SD card is corrupted.
Redownload the B125, but worse comes worse, try B118 or B122.
Click to expand...
Click to collapse
Re-downloaded it and used a proper zip program to unzip the file and it worked!!! So happy
Quick question what would you guys recommend I do to get rid of the service provider bloatware that came with my phone because with the upgrade all that stuff still stayed on my device? I tried uninstalling it normally and it just says system application cannot uninstall...
Battery life is a HUGE improvement. Sitting on 40% after 15 hours of abuse. Thanks again guys!
JK666 said:
Re-downloaded it and used a proper zip program to unzip the file and it worked!!! So happy
Quick question what would you guys recommend I do to get rid of the service provider bloatware that came with my phone because with the upgrade all that stuff still stayed on my device? I tried uninstalling it normally and it just says system application cannot uninstall...
Battery life is a HUGE improvement. Sitting on 40% after 15 hours of abuse. Thanks again guys!
Click to expand...
Click to collapse
That's great to hear!
BTW to get rid of system apps you do not want, install this. Your phone must be rooted in order for this to work.
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp
Tho becareful, don't get rid of vital apps.
If you haven't rooted your phone, head here.
http://forum.xda-developers.com/showthread.php?t=2390491
Good luck!
Hello,
I'm new to this forum, and I could not find anything related to this issue. I'm successfully downloading the latest update and when I try to install it, the installation goes up to 25% and I get the red exclamation mark afterwards. The phone then restarts, and I'm back at the beginning, where I have to re-download the update all over again. I don't have any custom ROMs flashed on my device, it's just like I bought it, the latest update that I made was the update to Android v6.0.1. Current software number is v2.10.401.1, if that is of any importance. I've factory reset the phone, and tried applying the update on a fresh phone, but it still won't work.
Also, while I'm here, I might just ask... I'm getting frequent app crashes/unresponsive app, mostly on the apps that I'm using the most, Facebook and Instagram. Facebook is more stable, crash/unresponsiveness does not happen very often, but for Instagram it's always happening after scrolling 3-4 images. Also, the Sense Home app is always getting unresponsive after a phone restart, and I have to restart it several times until it gets back to normal, since it cannot recover from it, I'm not seeing the home screen at all.
I was very satisfied with my phone before the update to Android 6, but after upgrade, I'm frequently having these minor problems, another one of which is the SD card "unexpectedly removed" error, which is happening when I open up the gallery or the file manager. I'm running low on patience, I really hoped that this last update will fix things, but I'm very close to slamming the phone off the wall, that's how frustrated I am. Please help
Well I'm no expert here but I've also experienced the freezes in such apps and even normal restart didn't work, so I had to force restart it. This happened in marshmallow and lollipop both so i tried removing my sd card and freezes were gone. In my case it was the sd card, so you can try that.
And for the update check if your bootloader is locked, assuming you bought it refurbished or used, the previous owner might have done some tinkering.
Hope you find the solution soon :good:
spiderwebmkd said:
Hello,
I'm new to this forum, and I could not find anything related to this issue. I'm successfully downloading the latest update and when I try to install it, the installation goes up to 25% and I get the red exclamation mark afterwards. The phone then restarts, and I'm back at the beginning, where I have to re-download the update all over again. I don't have any custom ROMs flashed on my device, it's just like I bought it, the latest update that I made was the update to Android v6.0.1. Current software number is v2.10.401.1, if that is of any importance. I've factory reset the phone, and tried applying the update on a fresh phone, but it still won't work.
Also, while I'm here, I might just ask... I'm getting frequent app crashes/unresponsive app, mostly on the apps that I'm using the most, Facebook and Instagram. Facebook is more stable, crash/unresponsiveness does not happen very often, but for Instagram it's always happening after scrolling 3-4 images. Also, the Sense Home app is always getting unresponsive after a phone restart, and I have to restart it several times until it gets back to normal, since it cannot recover from it, I'm not seeing the home screen at all.
I was very satisfied with my phone before the update to Android 6, but after upgrade, I'm frequently having these minor problems, another one of which is the SD card "unexpectedly removed" error, which is happening when I open up the gallery or the file manager. I'm running low on patience, I really hoped that this last update will fix things, but I'm very close to slamming the phone off the wall, that's how frustrated I am. Please help
Click to expand...
Click to collapse
If you are willing to, you can unlock the bootloader from http://www.htcdev.com/bootloader/ and flash a stock sense ROM or other custom ROMs and that might solve the app crash problem.
bilal.fanatic said:
Well I'm no expert here but I've also experienced the freezes in such apps and even normal restart didn't work, so I had to force restart it. This happened in marshmallow and lollipop both so i tried removing my sd card and freezes were gone. In my case it was the sd card, so you can try that.
And for the update check if your bootloader is locked, assuming you bought it refurbished or used, the previous owner might have done some tinkering.
Hope you find the solution soon :good:
Click to expand...
Click to collapse
I've already tried removing the SD card, and I've seen slight improvement in the app crashes, but they were still occurring. My bootloader is locked, but I'm going to unlock it now and flash a new ROM, I can't play around with it anymore
spiderwebmkd said:
I've already tried removing the SD card, and I've seen slight improvement in the app crashes, but they were still occurring. My bootloader is locked, but I'm going to unlock it now and flash a new ROM, I can't play around with it anymore
Click to expand...
Click to collapse
Before you do that .. as there is almost no custom ROM available for M8s except CM which is in progress, I don't suggest to unlock bootloader.. try to find and install 2.10.401.1 RUU
Installing RUU will usually fix this kind of problem if the data partition is sort of corrupted but not damaged.
ckpv5 said:
Before you do that .. as there is almost no custom ROM available for M8s except CM which is in progress, I don't suggest to unlock bootloader.. try to find and install 2.10.401.1 RUU
Installing RUU will usually fix this kind of problem if the data partition is sort of corrupted but not damaged.
Click to expand...
Click to collapse
You are suggesting to install the same software version that I currently have? Where do I find it and how do I install it manually?
spiderwebmkd said:
You are suggesting to install the same software version that I currently have? Where do I find it and how do I install it manually?
Click to expand...
Click to collapse
Yeah, same version then after OTA to 2.20.401.1
You can read this - http://forum.xda-developers.com/htc...lp-thread-htc-one-m8s-to-stock-howto-t3190238
and this - http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
on how to manually install RUU
And for the RUU .. I have to check my PC for the full filename so it is easier to find link. I'll let you know tomorrow (on mobile now)
spiderwebmkd said:
I've already tried removing the SD card, and I've seen slight improvement in the app crashes, but they were still occurring. My bootloader is locked, but I'm going to unlock it now and flash a new ROM, I can't play around with it anymore
Click to expand...
Click to collapse
If thats what you want to do I'd suggest you try cm12.1 . Unfortunately its the only ROM available to us but its way better than stock in terms of performance imho. But do that if you're willing to sacrifice some things such as double tap to wake and also any 3rd party camera apps, because they crash alot and yeah no boomsound. :fingers-crossed:
bilal.fanatic said:
If thats what you want to do I'd suggest you try cm12.1 . Unfortunately its the only ROM available to us but its way better than stock in terms of performance imho. But do that if you're willing to sacrifice some things such as double tap to wake and also any 3rd party camera apps, because they crash alot and yeah no boomsound. :fingers-crossed:
Click to expand...
Click to collapse
I'll try with @ckpv5 suggestion, to install 2.10.401.1 RUU and then try OTA upgrade to 2.20.401.1. If it fails, or if it succeeds but apps are still crashing as they were before, I'll definitely switch to cm, whatever version is stable at the moment. Double tap to wake is really annoying and I don't need it, I don't use 3rd party camera apps, and I guess I'll have to live without boomsound Thanks for the tip, though.
ckpv5 said:
Yeah, same version then after OTA to 2.20.401.1
You can read this - http://forum.xda-developers.com/htc...lp-thread-htc-one-m8s-to-stock-howto-t3190238
and this - http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
on how to manually install RUU
And for the RUU .. I have to check my PC for the full filename so it is easier to find link. I'll let you know tomorrow (on mobile now)
Click to expand...
Click to collapse
I did a bit of digging, and what I found is this:
0PKVIMG_M8_QL_UL_M60_SENSE70_HTC_Europe_2.10.401.1_Radio_1.0.U20410.1 @ 60201_20.05_018_F_release_479349_combined_signed.zip
which I downloaded from https://ruu.lalleman.net/ -> Firmware (Expert) -> Firmware Crypted (Original HTC)
I'll wait for you to confirm that this is the one that I need, before I continue with the procedure (rename, put to SD, boot to bootloader, fastboot)
does someone have stock marshmallow twrp backup. I accidentally deleted mine and now stuck with cm only
spiderwebmkd said:
I did a bit of digging, and what I found is this:
0PKVIMG_M8_QL_UL_M60_SENSE70_HTC_Europe_2.10.401.1_Radio_1.0.U20410.1 @ 60201_20.05_018_F_release_479349_combined_signed.zip
which I downloaded from https://ruu.lalleman.net/ -> Firmware (Expert) -> Firmware Crypted (Original HTC)
I'll wait for you to confirm that this is the one that I need, before I continue with the procedure (rename, put to SD, boot to bootloader, fastboot)
Click to expand...
Click to collapse
I can't access that site but it is the same file that I have that I got from different link.
Yes .. use that one.
I cant update the firmware either. Stucks at 25% the same. Couldn't solve. Tried to flash the firmware mentioned above. Didnt change. :/
EDit: Nevermind it passed 25% barrier lol. 70% and installing
parser said:
I cant update the firmware either. Stucks at 25% the same. Couldn't solve. Tried to flash the firmware mentioned above. Didnt change. :/
EDit: Nevermind it passed 25% barrier lol. 70% and installing
Click to expand...
Click to collapse
It passed after you flashed the RUU? the same procedure that I'm about to do?
spiderwebmkd said:
It passed after you flashed the RUU? the same procedure that I'm about to do?
Click to expand...
Click to collapse
yep sameway. Downloaded and flashed the firmware after renaming. Downloaded the ota via software update and voila.
took a little long but worked at the and.
parser said:
yep sameway. Downloaded and flashed the firmware after renaming. Downloaded the ota via software update and voila.
took a little long but worked at the and.
Click to expand...
Click to collapse
Worked for me as well. I'm at v2.20 now, so far no app crashes, the "SD card unexpectedly removed" is still there, but I'll live. Thanks a lot @ckpv5 for your suggestion, I practically got a brand new phone now!
spiderwebmkd said:
Worked for me as well. I'm at v2.20 now, so far no app crashes, the "SD card unexpectedly removed" is still there, but I'll live. Thanks a lot @ckpv5 for your suggestion, I practically got a brand new phone now!
Click to expand...
Click to collapse
hey! can you, if you have, send me a clean backup of the v2.20. I kinda rushed in and forgot to take a backup and now I am stuck with cm :/.
parser said:
hey! can you, if you have, send me a clean backup of the v2.20. I kinda rushed in and forgot to take a backup and now I am stuck with cm :/.
Click to expand...
Click to collapse
I don't have a backup of v2.20. I flashed the v2.10 from https://ruu.lalleman.net/ -> Firmware (Expert) -> Firmware Crypted (Original HTC) , and then I downloaded the OTA update on top of it.
spiderwebmkd said:
https://ruu.lalleman.net/ -> Firmware (Expert) -> Firmware Crypted (Original HTC)
Click to expand...
Click to collapse
no no not that. I mean TWRP backup. I dont want to go back to zero relock the phone and flash the zip and re-unlock the phone root again bla bla.
Since you did the same process, I thought maybe you took a backup of the rom after you updated it.
I made a mistake by not taking a backup of it so now it is a problem for me :/
Edit: damn! thanks anyway. I have a long night in front of me clearly. I hate this phone :/
V4A is not working anymore with the latest update. Is it me or everyone has the same problem.
hey community
I've tested CAN-L11C432B320 a while and miss the equalizer-app, also have an extreme powersaving device (...) but if i'm running runtastic they will turn off gps after 30 seconds display-off-time, background-services like whatsapp, pushbullet, etc.. will close after a few hours "inactivity", bad fingerprint-performace, some xposed-plugins have massive battery-drain and wont work....
so on.. i still search a while if its possible to get my stock emui 4.1 back...
...and yesterday i found this post:
h**p://w*w.htcmania.com/showthread.php?p=24388723
it looks like there was a full CAN-L11C432B100 and CAN-L01C432B100 firmware but i could not install them
i put the update.app in SDCARD:\dload and tried to install them with original EMUI5-recovery and the extracted EMUI4.1-recovery - everytime it hangs up at 5% and reboots after ~5 minutes.
i'm clueless.. maybe someone will also downgrade and found a solution how to get them work...
sorry from my bad english and the link-modification but i'm new here
I think we need to flash first the EMUI 4.1 recovery.img
Houamei said:
I think we need to flash first the EMUI 4.1 recovery.img
Click to expand...
Click to collapse
i've flash erecovery.img and recovery.img extracted from the update.app --> reboots too on 5%
extracted 4.1 Recovery: mega.nz/#!1MdXmART!Bbd3COTNnCsOB4iVMwQ0vOQhdEvzWDaWVnRhMwFMg08
xCite86 said:
hey community
I've tested CAN-L11C432B320 a while and miss the equalizer-app, also have an extreme powersaving device (...) but if i'm running runtastic they will turn off gps after 30 seconds display-off-time, background-services like whatsapp, pushbullet, etc.. will close after a few hours "inactivity", bad fingerprint-performace, some xposed-plugins have massive battery-drain and wont work....
so on.. i still search a while if its possible to get my stock emui 4.1 back...
...and yesterday i found this post:
h**p://w*w.htcmania.com/showthread.php?p=24388723
it looks like there was a full CAN-L11C432B100 and CAN-L01C432B100 firmware but i could not install them
i put the update.app in SDCARD:\dload and tried to install them with original EMUI5-recovery and the extracted EMUI4.1-recovery - everytime it hangs up at 5% and reboots after ~5 minutes.
i'm clueless.. maybe someone will also downgrade and found a solution how to get them work...
sorry from my bad english and the link-modification but i'm new here
Click to expand...
Click to collapse
There is a link for a rollback update, but i'm not home. When I get there, I send it. About battery, try to use greenify to help it to last long.
You can't just try to use a full package because of versioning scheme they use.
Here http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v72696/f1/full/update.zip
Same problem here, still drops at 5% even with the new file
I just wana know the best way to revert to stock
---------- Post added at 07:32 PM ---------- Previous post was at 07:28 PM ----------
and sorry I don't have an SD Card
Vinnom said:
Here http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v72696/f1/full/update.zip
Click to expand...
Click to collapse
thanks for the file but it won't work for me too..
the install process stops at 5% "Installing update" and reboots after a few minutes
can we extract all from the ota update zip and install via flash? can this work?
xCite86 said:
thanks for the file but it won't work for me too..
the install process stops at 5% "Installing update" and reboots after a few minutes
Click to expand...
Click to collapse
Hmmm, sorry, I thought it would help. In fact, the package is listed as a rollback to M, but it is for CAN-L11. The rollback for CAN-L01, I didn't find. As there isn't many differences between those models, I thought it would work
EDIT: now that I read the op again, I noticed that your model is CAN-L11. I wonder why it didn't work
Houamei said:
can we extract all from the ota update zip and install via flash? can this work?
Click to expand...
Click to collapse
No, it won't.
The reason behind this is because system partition get smaller (because nougat way of update) after updating it to emui 5. So the old system.img won't fit the new partition
My phone only hangs up at 5% when the usb cable is connected. When i open the download mode without connected usb cable, it works.
Mikey94 said:
My phone only hangs up at 5% when the usb cable is connected. When i open the download mode without connected usb cable, it works.
Click to expand...
Click to collapse
So you downgraded?
Mikey94 said:
My phone only hangs up at 5% when the usb cable is connected. When i open the download mode without connected usb cable, it works.
Click to expand...
Click to collapse
did you downgrade your nougat successfully with the files above??
edit: i tried it without a connected usb cable and got "software install failed!" after short time
Is a restore of a CAN-L11 backup from Android 6 in TWRP not possible?
i think this should work if you or someone else share a backup i could try..
Michiel0912 said:
Is a restore of a CAN-L11 backup from Android 6 in TWRP not possible?
Click to expand...
Click to collapse
no, in my opinion the nougat bootloader want work with mm.
I would flash the firmeware of mm and after that flash twrp and restore the backup after that [emoji106]
It will work. There is a backup within twrp thread, from bluesmothie.
Vinnom said:
It will work. There is a backup within twrp thread, from bluesmothie.
Click to expand...
Click to collapse
found it...
https://forum.xda-developers.com/showpost.php?p=70259615&postcount=2
re-unlocked bootloader
flashed twrp with fastboot flash recovery twrp_huawei_generic_a53_YYYYMMDD.img
copied all the dropbox files to /external_sd/TWRP/BACKUPS/FPFDU16930014596/1970-03-18--16-40-58_CANC432B100/...
wipe all partitions except sd-card
recover the complete backup
so @Vinnom many thanks for your help. i got my phone back to life (after fomatted data partition) and got downgraded to CANC432B100 now.
Michiel0912 said:
Is a restore of a CAN-L11 backup from Android 6 in TWRP not possible?
Click to expand...
Click to collapse
Yeah, thanks Vinnom...
xCite86 said:
found it...
https://forum.xda-developers.com/showpost.php?p=70259615&postcount=2
re-unlocked bootloader
flashed twrp with fastboot flash recovery twrp_huawei_generic_a53_YYYYMMDD.img
copied all the dropbox files to /external_sd/TWRP/BACKUPS/FPFDU16930014596/1970-03-18--16-40-58_CANC432B100/...
wipe all partitions except sd-card
recover the complete backup
so @Vinnom many thanks for your help. i got my phone back to life (after fomatted data partition) and got downgraded to CANC432B100 now.
Click to expand...
Click to collapse
Did the same thing, but first TWRP didn't find the backup. So i did a small backup just of the boot partition, so that TWRP makes a new backupfolder "FPF4C16A07000014"". Now i renamed the " FPFDU16930014596" to the new "FPF4C16A07000014" and TWRP found the backup and i was able to restore :highfive::highfive:
Small Addition:
It was a freaking fight to get my bootloader unlocked again, cause i lost the unlock code.
The websites (english and asian) are freaking BS. Was not able to get to the page where you get the code, so i downloaded DC-Tool and payed 4 dollars for the damn code.
Now the code is saved in my owncloud, dropbox, google drive, on a sheet of paper and google notes. No way to lose it again
B100 firmware is much smoother than B320 but has a lack of comfort, like i'm missing the new quick settings with double pull down and the touch responsibility of slide bars (like the volume bars) is not very good in B100... But i won't upgrade to 320 again, because of the following points that make it a no go for daily driver:
- Camera is very slow and hangs up
- Video playback is very slow and buggy (no matter if it's in the galery or youtube, ect.)
- Fingerprint is too slow
- Whole system gets very slw if you dont clean up the app history
Will upgrade again when there is a new version out
please am having same issue here. tried restore but still not booting.
problem is cust. what do i do about it.
HELP ME
Hello,
hopefully you can help me with my seemingly bricked Honor Pro 8 because of root and stock rom update procedures. I bought the phone with amazon and the package seemes to give me the information to have an EU-version of the phone.
The fastboot get-oem-information code or so also puts out the status of an European bootloader.
Regarding my working steps first of all the phone took the new update. Then I was successful in unlocking the bootloader, installing TWRP and rooting it by supersu.
But after that I was curious about the "Magisk" rooting abilities. Therefore I tried a superuser-unroot via script finding inside this forum following by flashing a extracted boot.img of an update.app file of a DUK-L09C432B130 update. After ending in a bootloop by trying the 1.30 beta version of magisk I was able to boot the normal android desktop after I uninstalled the beta version and having flashed the normal 1.20 version.
But then I tried to install 2 certain modules inside of magisk. In consequence the problem was to see the rebooted android not to load any icons. In the other side it put up the message of not having enough mobile disk memory after some minutes which couldn't be true in fact. So I tried a factory reset inside TWRP and also a full wipe. Disappointingly I haven't been successful in rebooting android once more.
Therefore I unseccessfully tried to flash the Full-OTA-MF stock rom of DUK-L09C432B130 in two versions and the L09-C432b120a via the EMUI-install mode by pressing vol+ and - and power buttons. To do that I prepared a SD card as a exfat format. But I just received the message of "software install failed" when reaching 5 %.
So I got to the frustrating point not to know what stock rom I can flash in another try or doing anything else. I would be very glad if U could help me in this desperating situation. :fingers-crossed:
Thanks and best regards.
Can you boot to erecovery?
adriansticoid said:
Can you boot to erecovery?
Click to expand...
Click to collapse
I can but it just puts out the message "Getting package info failed"
Filo83 said:
I can but it just puts out the message "Getting package info failed"
Click to expand...
Click to collapse
Please try another version of firmware.
adriansticoid said:
Please try another version of firmware.
Click to expand...
Click to collapse
That is my problem not to know which version to use because three dowloaded EU-versions weren't successful to install. It resulted in an error at 5 % of the 3-buttons-install mechanism.
Filo83 said:
Hello,
hopefully you can help me with my seemingly bricked Honor Pro 8 because of root and stock rom update procedures. I bought the phone with amazon and the package seemes to give me the information to have an EU-version of the phone.
The fastboot get-oem-information code or so also puts out the status of an European bootloader.
Regarding my working steps first of all the phone took the new update. Then I was successful in unlocking the bootloader, installing TWRP and rooting it by supersu.
But after that I was curious about the "Magisk" rooting abilities. Therefore I tried a superuser-unroot via script finding inside this forum following by flashing a extracted boot.img of an update.app file of a DUK-L09C432B130 update. After ending in a bootloop by trying the 1.30 beta version of magisk I was able to boot the normal android desktop after I uninstalled the beta version and having flashed the normal 1.20 version.
But then I tried to install 2 certain modules inside of magisk. In consequence the problem was to see the rebooted android not to load any icons. In the other side it put up the message of not having enough mobile disk memory after some minutes which couldn't be true in fact. So I tried a factory reset inside TWRP and also a full wipe. Disappointingly I haven't been successful in rebooting android once more.
Therefore I unseccessfully tried to flash the Full-OTA-MF stock rom of DUK-L09C432B130 in two versions and the L09-C432b120a via the EMUI-install mode by pressing vol+ and - and power buttons. To do that I prepared a SD card as a exfat format. But I just received the message of "software install failed" when reaching 5 %.
So I got to the frustrating point not to know what stock rom I can flash in another try or doing anything else. I would be very glad if U could help me in this desperating situation. :fingers-crossed:
Thanks and best regards.
Click to expand...
Click to collapse
you download the nocheck recoveries from my rebranding guide, download the corresponding firmware by morph (important!), flash both recovery images just like stated in the guide, boot into recovery mode like you would do to boot into twrp, do a factory reset, reboot and insert the microsd with the dload folder from extracted downloaded firmware and boot into force dload mode (vol+ and vol- and power) - the installation should start now and reset everything back to full stock.
Regards
Thank you very much OldDroid. You're my hero. It worked fine.
But to install the new 130-update the phone starts inside TWRP and ends with an "error 9" and the words "block image verify", "asserts failed". Could it be possible to perform the update by starting the forced update process by pressing the three hardware buttons on booting? And is it possible not to wipe the data and losing root by using a update?
Viele Grüße aus Berlin nach Berlin
Filo83 said:
Thank you very much OldDroid. You're my hero. It worked fine.
But to install the new 130-update the phone starts inside TWRP and ends with an "error 9" and the words "block image verify", "asserts failed". Could it be possible to perform the update by starting the forced update process by pressing the three hardware buttons on booting? And is it possible not to wipe the data and losing root by using a update?
Viele Grüße aus Berlin nach Berlin
Click to expand...
Click to collapse
OTA packages cannot be installed via twrp at the moment
you should use stock recovery for that!
Best regards
Grüße zurrück aus Berlin nach Berlin
Could you explain me a bit more please? Is it the standard system update ins the systems menu, here it wants to load the 2,9 GB file. Updating this way with the "no check recovery" resulted in an checking error at about 12 %.
Or could it be via recovery shortly after starting the phone? But there are no choices to choice. It just automaticely begins installing something stopping at 5 %.
Hope you can help one more please.
Filo83 said:
Could you explain me a bit more please? Is it the standard system update ins the systems menu, here it wants to load the 2,9 GB file. Updating this way with the "no check recovery" resulted in an checking error at about 12 %.
Or could it be via recovery shortly after starting the phone? But there are no choices to choice. It just automaticely begins installing something stopping at 5 %.
Hope you can help one more please.
Click to expand...
Click to collapse
soooo, if you flashed one of @-=MoRpH=- 's firmwares, your device is back to stock and the recoveries have been overwritten again! I don't recommend flashing OTA updates or other things through the NoCheck version as it is only intended for worst-case cenarios.
But could you tell me the single steps to update from Morph's DUK-L09C432B120 version to the newest version DUK-L09C432B130?
I only got errors to update the firmware DUK-L09C432B130 from the stock rom thread in this forum and the russian website mentioned there.
Filo83 said:
But could you tell me the single steps to update from Morph's DUK-L09C432B120 version to the newest version DUK-L09C432B130?
I only got errors to update the firmware DUK-L09C432B130 from the stock rom thread in this forum and the russian website mentioned there.
Click to expand...
Click to collapse
extract the firmware and flash manualy using fastboot
thilak devraj said:
extract the firmware and flash manualy using fastboot
Click to expand...
Click to collapse
That is just needed to be done as last resort. Better stick with dload.
adriansticoid said:
That is just needed to be done as last resort. Better stick with dload.
Click to expand...
Click to collapse
he said he got some errors doing dload, so this method works too
thilak devraj said:
he said he got some errors doing dload, so this method works too
Click to expand...
Click to collapse
He must find the right firmware first.
adriansticoid said:
He must find the right firmware first.
Click to expand...
Click to collapse
finding a firmware for huawei devices is a pain in the ass, you know
thilak devraj said:
finding a firmware for huawei devices is a pain in the ass, you know
Click to expand...
Click to collapse
That's why we have Firmware Finder.
adriansticoid said:
That's why we have Firmware Finder.
Click to expand...
Click to collapse
even in firmware finder, it will be difficult sometimes for sone devices
thilak devraj said:
even in firmware finder, it will be difficult sometimes for sone devices
Click to expand...
Click to collapse
Maybe. But they are constantly improving.
adriansticoid said:
Maybe. But they are constantly improving.
Click to expand...
Click to collapse
i appreciate the firmware finder, but sometimes, its just inappropriate
Yesterday i was upgrading my phone from B368 to B369, and wronging by impatience, i decided to shut down while my phone was apparently blocked on the NAG screen (your phone has been unlocked and can't be trusted screen at startup); in truth, it wasn't blocked but it was just applying updates during reboot and he was tooking some more time than usual... The result? My model number changed from BLN-L21 to generic_a15, and so apps like camera was keeping crashing and became not usable.
After had restored a TWRP backup made before updating, and so on B368 build, i ended up with BLN-L21C432B369 as build number, but without having the latest security patch and latest improvements. In poor words, the B369 build was shown even if i was on B368 at all, and so system update wasn't detecting any other updates since that i was apparently on the latest build.
[DISCLAIMER: don't point your finger on me if you end up with your phone exploding, emitting toxic spores or radiations, please. I'm just putting this simple guide here as a way to possibly solve your issue, but i can't know if it'll works on EVERY different model, variant or kind of issue; in mine case it worked like a charm, but BE CAREFUL. I'm not responsable for anything]
What i did for fix this issue was very, very simple, much simpler than what i thought to face; i just started combing here and there in the various root folders thanks to a root explorer (i used MiX, for example) containing the various local.prop and build.prop files scattered around the system folders, until i found the right one to tweak with. The path to follow is very simple: you just need to browse to
Code:
root/version/special cust/BLN-L21/hw/eu/prop/local.prop
(note that the path will obviously change if you own a BLN-L22, a BLL-L22, ecc. but the road will be always the same - you'll find other folders name after special cust, BLL-L22 other than BLN-L21, china instead of eu for example, but often it's always straight to the last folder that finally contains the local.prop file)
and once there, with the help of a text editor, correct all the errors that you'll find mismatching with your actual build number. The voices that i had to correct are circled in orange in the picture that i attached here below, (note: the picture shows voices already fixed) and there was four of them to adjust;
Code:
ro.build.display.id=BLN-L21C432[B][COLOR="Red"]B369[/COLOR][/B]
ro.build.version.incremental=C432[B][COLOR="red"]B369[/COLOR][/B]
ro.build.description=BLN-L21 -user 7.0 HONORBLN-L21 C432[B][COLOR="red"]B369[/COLOR][/B] release-keys
ro.build.fingerprint=HONOR/BLN-L21/HWBLN-H:7.0/HONORBLN-L21/C432[B][COLOR="red"]B369[/COLOR][/B]:user/release-keys
since that in this case i was on B368 other than B369, as shown by phone info in settings menu, i just tried to modify that number with an 8 instead of a 9, gave the phone a reboot and... It's done!
**Method Update!**
@BakedOnSomeSour pointed out a way to definitely correct the build number, permanently and safer than my method!
To do this, flash the version.img matching your firmware build, an image that you can extract from the UPDATE.APP of each update.zip package through TWRP (flash the file as image of course, by selecting the dedicated option in TWRP menu). In this way, the build number will be definitely fixed!
Thanks to BakedOnSomeSour for finding a faster and more efficient method.
Be aware, and backup before doing this or everything you're dubious about.
Cheers
nice one buddy and a detailed one...Thanks for sharing with us. as usual, great effort.
shashank1320 said:
nice one buddy and a detailed one...Thanks for sharing with us. as usual, great effort.
Click to expand...
Click to collapse
Thanks mate. I discovered how to do by myself while trying to get rid of this error, and so i thought to share with others who could face this in future.
nice one D
just curious, can we use the same trick to revert the model number when it's changed to generic_a15
sreekantt said:
nice one D
just curious, can we use the same trick to revert the model number when it's changed to generic_a15
Click to expand...
Click to collapse
Nice question dude, i was just asking myself the same. Maybe, modifying eventual errors in the same file, or alternatively in the one in root/version/etc/component_version.txt (here there is a file with only one string with the general model; mine shows "Version-BLN-L21-432000 5.0.0.1(N.17110801)" obviously, but if it should show something relative to generic_a15, modifying it could do the trick) it could be possible to easily fix this issue. I'd like to test it by myself, but at the moment I'd like to avoid to mess up my phone again also since that I'm busy with other stuff anyway I'll finally test this sooner, and eventually I'll update the guide.
RedSkull23 said:
Nice question dude, i was just asking myself the same. Maybe, modifying eventual errors in the same file, or alternatively in the one in root/version/etc/component_version.txt (here there is a file with only one string with the general model; mine shows "Version-BLN-L21-432000 5.0.0.1(N.17110801)" obviously, but if it should show something relative to generic_a15, modifying it could do the trick) it could be possible to easily fix this issue. I'd like to test it by myself, but at the moment I'd like to avoid to mess up my phone again also since that I'm busy with other stuff anyway I'll finally test this sooner, and eventually I'll update the guide.
Click to expand...
Click to collapse
yeah same with me - don't wanna delay other things as of now... :highfive:
I would like to switch my build number so i can receive an OTA since it is currently messed up. Every time i change the build number i get an update available. But in order to install i have to remove root and TWRP. When i remove those the build goes back to original and my phone cant find an update because it says im on the lastest build. Why does it switch back when i remove twrp and root? Im assuimg it may have something to do with the boot image?
BakedOnSomeSour said:
I would like to switch my build number so i can receive an OTA since it is currently messed up. Every time i change the build number i get an update available. But in order to install i have to remove root and TWRP. When i remove those the build goes back to original and my phone cant find an update because it says im on the lastest build. Why does it switch back when i remove twrp and root? Im assuimg it may have something to do with the boot image?
Click to expand...
Click to collapse
Yes, i assume that too... Maybe when the root is removed and the original boot.img is restored, the error is restored too. You could maybe solve that by flashing the boot.img of the build just before the one you'd like to update to (but be aware and take a backup before, in case something happens. Once i flashed a boot.img of a previous build instead of the one that i had to flash, and at phone startup, my code to unlock wasn't anymore recognized, so i had to restore a backup)
RedSkull23 said:
Yes, i assume that too... Maybe when the root is removed and the original boot.img is restored, the error is restored too. You could maybe solve that by flashing the boot.img of the build just before the one you'd like to update to (but be aware and take a backup before, in case something happens. Once i flashed a boot.img of a previous build instead of the one that i had to flash, and at phone startup, my code to unlock wasn't anymore recognized, so i had to restore a backup)
Click to expand...
Click to collapse
Flashing a boot.img is having no effect on the build number. The strange thing is im on b366 but my phone wont accept that firmware with the dload method. It only accepts firmware much lower. I just need that build number to change without root but no amount of flashing does anything. Ive had a ton of android phones and they've never been as unpredictable as this one.
Edit: Flashing a version.img and vendor.img see to do it.
BakedOnSomeSour said:
Flashing a boot.img is having no effect on the build number. The strange thing is im on b366 but my phone wont accept that firmware with the dload method. It only accepts firmware much lower. I just need that build number to change without root but no amount of flashing does anything. Ive had a ton of android phones and they've never been as unpredictable as this one.
Edit: Flashing a version.img and vendor.img see to do it.
Click to expand...
Click to collapse
Reading that i was worrying, since that I'm about to update to B369 again after that Magisk V15.0 ****ed up my build.prop and other stuff too, and i thought the boot.img could fix that... But I'm glad you solved it. Both of them are needed so, or only one it's ok? By the way yeah, i can say that Huawei and their cosmos of firmware builds, different for every variant, is way too complicated. A project like Project Treble is what they need.
RedSkull23 said:
Reading that i was worrying, since that I'm about to update to B369 again after that Magisk V15.0 ****ed up my build.prop and other stuff too, and i thought the boot.img could fix that... But I'm glad you solved it. Both of them are needed so, or only one it's ok? By the way yeah, i can say that Huawei and their cosmos of firmware builds, different for every variant, is way too complicated. A project like Project Treble is what they need.
Click to expand...
Click to collapse
Well after flashing them the phone booted but I was unable to get into developer settings. It just kept crashing. It did change the build number though even after flashing to stock recovery without root. I flashed both through twrp. Maybe that was the problem. Maybe you can just try flashing version.img and let us know if it helped. I would try it without vendor.img first.
BakedOnSomeSour said:
Well after flashing them the phone booted but I was unable to get into developer settings. It just kept crashing. It did change the build number though even after flashing to stock recovery without root. I flashed both through twrp. Maybe that was the problem. Maybe you can just try flashing version.img and let us know if it helped. I would try it without vendor.img first.
Click to expand...
Click to collapse
I can extract the version.img of B368, but once i have it it's possible to flash it through fastboot/TWRP, or i have to follow another path, like typing somethin' by adb like "dd if=/sdcard/version.img of=/dev/block/mmcblck..." ?
RedSkull23 said:
I can extract the version.img of B368, but once i have it it's possible to flash it through fastboot/TWRP, or i have to follow another path, like typing somethin' by adb like "dd if=/sdcard/version.img of=/dev/block/mmcblck..." ?
Click to expand...
Click to collapse
try fastboot first. So "fastboot flash version VERSION.img". If that doesn't work flash it in TWRP.
After its flashed try removing root and flash a stock recovery and see if the build number stays.
BakedOnSomeSour said:
try fastboot first. So "fastboot flash version VERSION.img". If that doesn't work flash it in TWRP.
After its flashed try removing root and flash a stock recovery and see if the build number stays.
Click to expand...
Click to collapse
Yeah got that, thanks. I'll write here a feedback as i'll be able to do this
@BakedOnSomeSour okay i bring nice notices, here's what i did.
I tried first to flash the BLN-L21_data_hw_eu package from official firmware around 700MB by TWRP, but after some bloat apps installed that i always remove as i update, it failed with error 7 (if i don't remember bad). So i restored a backup made just before flashing it, to avoid issues of any kind.
Then i tried to flash version.img by fastboot, but it failed with error command not allowed.
Finally, i simply flashed the version.img through TWRP, then i completely removed Magisk, i flashed by fastboot the stock boot and recovery images as i do when i make an update, and... It worked. After booting to OS, my build number remained correct. It stopped from turning back to B369 after a reboot (even if I'm on B368 at all), solving the issue that i was facing. Thanks for the tip, I'll add it to the guide if you'd like to be credited
RedSkull23 said:
@BakedOnSomeSour
Then i tried to flash version.img by fastboot, but it failed with error command not allowed.
Click to expand...
Click to collapse
New mess with Huawei every day. They keep stopping us and we keep trying them
RedSkull23 said:
@BakedOnSomeSour okay i bring nice notices, here's what i did.
I tried first to flash the BLN-L21_data_hw_eu package from official firmware around 700MB by TWRP, but after some bloat apps installed that i always remove as i update, it failed with error 7 (if i don't remember bad). So i restored a backup made just before flashing it, to avoid issues of any kind.
Then i tried to flash version.img by fastboot, but it failed with error command not allowed.
Finally, i simply flashed the version.img through TWRP, then i completely removed Magisk, i flashed by fastboot the stock boot and recovery images as i do when i make an update, and... It worked. After booting to OS, my build number remained correct. It stopped from turning back to B369 after a reboot (even if I'm on B368 at all), solving the issue that i was facing. Thanks for the tip, I'll add it to the guide if you'd like to be credited
Click to expand...
Click to collapse
Im glad it all worked out :victory: Sure if you want to give me credit. Im just glad i could help
shashank1320 said:
New mess with Huawei every day. They keep stopping us and we keep trying them
Click to expand...
Click to collapse
What a bore is this, man?! :laugh: never admitting a loose against them!
BakedOnSomeSour said:
Im glad it all worked out :victory: Sure if you want to give me credit. Im just glad i could help
Click to expand...
Click to collapse
Of course, you deserve that :highfive: thanks for the idea, even faster than my workaround (and maintains properties overall)
RedSkull23 said:
What a bore is this, man?! :laugh: never admitting a loose against them!
Of course, you deserve that :highfive: thanks for the idea, even faster than my workaround (and maintains properties overall)
Click to expand...
Click to collapse
Never
Happy new year brother. Hope we continue to grow in year ahead with more mess and fixes with Huawei phones :silly:
shashank1320 said:
Never
Happy new year brother. Hope we continue to grow in year ahead with more mess and fixes with Huawei phones :silly:
Click to expand...
Click to collapse
Thanks pal, wish you the same i can say that until I'll have an Honor device, that will be almost at day order