Hi everyone, I have a problem in the downgrade procedure to emui10 of a matepad pro (MRX-W09), using hisuite and hisuite proxy the rome is downloaded correctly but then the installation fails, i attach the hisuit log file with errors.
Can everyone help me?
Thanks
lele78c said:
Hi everyone, I have a problem in the downgrade procedure to emui10 of a matepad pro (MRX-W09), using hisuite and hisuite proxy the rome is downloaded correctly but then the installation fails, i attach the hisuit log file with errors.
Can everyone help me?
Thanks
Click to expand...
Click to collapse
I managed to complete the installation from hisuite but now the installation from the tablet fails, furthermore hiproxy as soon as the download finishes gives me a message that says "Apparently Firm(s) is/are not approved for installation and proccess will most likely fail in phone. You might want to consider canceling it to avoid time waste." I have tried several roms but they all fail.
Can anyone help me?
lele78c said:
I managed to complete the installation from hisuite but now the installation from the tablet fails, furthermore hiproxy as soon as the download finishes gives me a message that says "Apparently Firm(s) is/are not approved for installation and proccess will most likely fail in phone. You might want to consider canceling it to avoid time waste." I have tried several roms but they all fail.
Can anyone help me?
Click to expand...
Click to collapse
Related
PLEASE PLEASE CAN someone help me. I download the latest ROM from www.o2.co.uk/xda (Xda_II_172181) I also downloaded the instructions and followed it word for word. When i got to the stage to click on 'UPGRADE'. All seemed ok, but sudendly i got an error message saying there was a problem i had to disconnect my device from the cradle and reset and start again, so i did exactly this, but now i get the error message i get is >>>>
"The contents of this file cannot be unpacked. The executable you are attempting to run has been corrupted. Please obtain another copy of the file, verify its integrity, and try again."
(please see my attachment for screen shot)
I went back to the O2 site and downloaded the same ROM again and attempted to load it, again following the instructions given by O2 and got exactly the same error message. I have given my XDA II a hard reset but all i get on the display is 'USB V1.03' I cannot connect to ActiveSync, can anyone please offer me any advice.
Thank you in advance,
Regards
Try downloading from my post here.
Thank you sooooo much dcs, i downloaded your copy of the rom and its now working perfectly fine, once again i really apprectiate your help. i AM so happy now
just need to install all my apps.
DCS, just a quick question does the True Fax software work with this new rom, i could never get it working with my previous rom
Kind Regards,
nya
problems....
I've successfully update the 1.72 Rom for my XDAII but my previous backup was not successful!! is it because different rom? The Hong Kong O2 told me to do a backup first, but after upgrade it seems that my previous Rom 1.62 doesnt' support... is that the case? :shock:
hello
i have rooted the device using the "1 CLICK ROOT TOOL" and now i have the dead android bot with error when i enter recovery.
i have tried the "fastboot erase cache" command at fastboot mode but it did not help
is their a way to fix it?
Try pressing Volume + key and Power. Don't hold just press. It might take a few goes to get it right. I had the same problem. That means that the update you have downloaded (saved on your system) fails to install.
hello and thanks
i can enter recovery by pressing the keys. this is not the issue
its just that i want to completely solve the problem
koby058 said:
hello and thanks
i can enter recovery by pressing the keys. this is not the issue
its just that i want to completely solve the problem
Click to expand...
Click to collapse
Awh sorry, I thought you can't get into recovery.
Try sideloading the stock Firmware. Go to official ASUS website and download it from there. It's about 1 GB. On this website you can find instructions on how to do it. http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596 Section 3.2)
After that you can download OTA updates and install them using method described here http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835, "Steps to Apply OTA manually".
OTA can be downloaded from there (look at the later posts for newer OTA) http://forum.xda-developers.com/zenfone2/general/ota-links-stock-rom-t3093999
I had a very similar problem few days ago. That solved it. Had a similar problem a few days ago coz I messed up my build.prop
hello
i have already did a "adb siedeload" for the stock rom downloaded from the asus web site but the issue remain.
also i downloaded the latest ota, and "adb sideloaded" them as well. it worked flawlessly .
but the small thing with the recovery is annoying.
i thinking about looking inside tmp directory and delete something called "last update"
what do you say?
koby058 said:
hello
i have already did a "adb siedeload" for the stock rom downloaded from the asus web site but the issue remain.
also i downloaded the latest ota, and "adb sideloaded" them as well. it worked flawlessly .
but the small thing with the recovery is annoying.
i thinking about looking inside tmp directory and delete something called "last update"
what do you say?
Click to expand...
Click to collapse
You're not understanding because the information he gave you is slightly wrong. When you try to enter stock recovery it will ALWAYS say installing update and pop up an error Android bot. It's not about having some update data somewhere that fails to install properly. It will ALWAYS do that. That's normal.
rlaw said:
You're not understanding because the information he gave you is slightly wrong. When you try to enter stock recovery it will ALWAYS say installing update and pop up an error Android bot. It's not about having some update data somewhere that fails to install properly. It will ALWAYS do that. That's normal.
Click to expand...
Click to collapse
Owh, this is embarrassing. I was playing with it a lot and I was kind of sure that if you have a working installed update, which is the same as a zip of an OTA update you have on an SD card it will skip installing the update and go to recovery without an error, but I was very very wrong. I'm very sorry for missleading you, and I've learned something new. Thank you.
NiKiToS-04 said:
Owh, this is embarrassing. I was playing with it a lot and I was kind of sure that if you have a working installed update, which is the same as a zip of an OTA update you have on an SD card it will skip installing the update and go to recovery without an error, but I was very very wrong. I'm very sorry for missleading you, and I've learned something new. Thank you.
Click to expand...
Click to collapse
No worries, I've made the same mistake before. We've all been there, still learning new things about this phone after months of using it!
ok let me tell why i begin asking about it.
when i just got the phone i update all of the ota updates and after that i rooted it with "1 CLICK ROOT TOOL" .
two days ago i receive tha 2.20.40.58 ota . i downloaded and install but the instalation failed .
so i unroot it with "1 CLICK ROOT TOOL" and then i checked for update . but there was no update.
so i assumed the problem is because of the recovery issue.
the qustion is why i cannot install ota automatically ?
koby058 said:
ok let me tell why i begin asking about it.
when i just got the phone i update all of the ota updates and after that i rooted it with "1 CLICK ROOT TOOL" .
two days ago i receive tha 2.20.40.58 ota . i downloaded and install but the instalation failed .
so i unroot it with "1 CLICK ROOT TOOL" and then i checked for update . but there was no update.
so i assumed the problem is because of the recovery issue.
the qustion is why i cannot install ota automatically ?
Click to expand...
Click to collapse
The 2.20.40.58 OTA was bugged and pulled from release. Just flash the full stock 2.20.40.59 firmware available from ASUS site and stop modifying your phone if you want to remain trouble-free with OTA updates. Or if you choose to continue to root and tinker with your phone accept that some things might get broken.
My phone is running the BOG5 5.0.1 software and it is a retail edition.
I recieved a notification on my device prompting me that a new update is available (finally! 5.1.1!) I tap "download now", the download eventually finishes and it proceeds to install.
My phone boots into recovery, "installing update" and very shortly after I see the droid triage error and below it says "error!" and then my phone reboots. When I unlock my phone it says, "Sorry, there was a problem updating your SAMSUNG SM-N910V. No changes were made."
I looked under software update in settings and it says "software not updated to N910VVRU2BOK3" and the error code is 410.
I also notice that when I go into recovery it says "dm-verity verification failed...."
I looked in Kies to see if the update was available there, and of course it wasn't. And I can't find the ROM anywhere as of yet to flash with ODIN.
I would appreciate all of the help I can get.
Thank you.
traceestarr said:
My phone is running the BOG5 5.0.1 software and it is a retail edition.
I recieved a notification on my device prompting me that a new update is available (finally! 5.1.1!) I tap "download now", the download eventually finishes and it proceeds to install.
My phone boots into recovery, "installing update" and very shortly after I see the droid triage error and below it says "error!" and then my phone reboots. When I unlock my phone it says, "Sorry, there was a problem updating your SAMSUNG SM-N910V. No changes were made."
I looked under software update in settings and it says "software not updated to N910VVRU2BOK3" and the error code is 410.
I also notice that when I go into recovery it says "dm-verity verification failed...."
I looked in Kies to see if the update was available there, and of course it wasn't. And I can't find the ROM anywhere as of yet to flash with ODIN.
I would appreciate all of the help I can get.
Thank you.
Click to expand...
Click to collapse
I'm having the exact same issue and symptoms, have you made any progress with this? If I find a solution I'll share here too. I've tried Kies and VZW Software Upgrade Assistant, neither finds the update, but I can get it on my retail VZ Note 4, just won't successfully install.
Keiller said:
I'm having the exact same issue and symptoms, have you made any progress with this? If I find a solution I'll share here too. I've tried Kies and VZW Software Upgrade Assistant, neither finds the update, but I can get it on my retail VZ Note 4, just won't successfully install.
Click to expand...
Click to collapse
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.
traceestarr said:
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.
Click to expand...
Click to collapse
I have similar issue ,i don't have a update yet showing on my device so i await for it to show up. Please let us know if flashing it makes the difference.
traceestarr said:
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.
Click to expand...
Click to collapse
Sounds like something worth trying, I'll watch for an update on how it goes for you. Thanks!
I have found a solution (albeit requires a full wipe, which is worth having 5.1.1 for me)
Firstly, I attempted flashing the "stock restore" file in odin and resulted in an error, I then tried the full firmware instead (mind you for BOG5, if you're having problems on your current version I'd suggest using your current build) with success, proceed with a data wipe in recovery and noticed that the "dm-verity verification failed...." message is now gone and now that bottom area of the screen has information about applying Multi-CSC.
Restart the phone, set up as normal and go straight for the software update. My phone downloaded and installed the update perfectly! For safety just boot into recovery and do a full wipe again, and there you have it!
The stock firmwares for RETAIL SM-N910V are here: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
traceestarr said:
I have found a solution (albeit requires a full wipe, which is worth having 5.1.1 for me)
Firstly, I attempted flashing the "stock restore" file in odin and resulted in an error, I then tried the full firmware instead (mind you for BOG5, if you're having problems on your current version I'd suggest using your current build) with success, proceed with a data wipe in recovery and noticed that the "dm-verity verification failed...." message is now gone and now that bottom area of the screen has information about applying Multi-CSC.
Restart the phone, set up as normal and go straight for the software update. My phone downloaded and installed the update perfectly! For safety just boot into recovery and do a full wipe again, and there you have it!
The stock firmwares for RETAIL SM-N910V are here: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
Click to expand...
Click to collapse
Thank you for reporting back with what worked for you. I've tried following the same steps you took, but after flashing the full BOG5 firmware and doing a data wipe and then doing basic setup on my phone, the OTA is still failing, Error Code: 404. I'll try again, but so far no success. Still stuck on the buggy 5.0.1, the version where you can't flash back to 4.4.4....
Keiller said:
Thank you for reporting back with what worked for you. I've tried following the same steps you took, but after flashing the full BOG5 firmware and doing a data wipe and then doing basic setup on my phone, the OTA is still failing, Error Code: 404. I'll try again, but so far no success. Still stuck on the buggy 5.0.1, the version where you can't flash back to 4.4.4....
Click to expand...
Click to collapse
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.
traceestarr said:
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.
Click to expand...
Click to collapse
You're right, I thought I had seen that message earlier in the week while trying to get the OTA for 5.1.1 to work, but I didn't write it down. Your description of symptoms matched mine so well I figured it had to be the same issue or something so similar that running through the same process would work for me too.
I may take the phone into Verizon to show them the update fail and see if they are willing to do anything for me....
Glad you got yours up and running, but I am just a little bit jealous
Keiller said:
You're right, I thought I had seen that message earlier in the week while trying to get the OTA for 5.1.1 to work, but I didn't write it down. Your description of symptoms matched mine so well I figured it had to be the same issue or something so similar that running through the same process would work for me too.
I may take the phone into Verizon to show them the update fail and see if they are willing to do anything for me....
Glad you got yours up and running, but I am just a little bit jealous
Click to expand...
Click to collapse
I've found that most times the OTA update fails prior to rebooting to install the update and I get the 404 error I reported earlier. However, when it does make it to the point of doing the OTA update after reboot, after that fails, I get the same 410 error you reported, see attached, and I also the dm-verity fail message in recovery. Then after using Odin to install BOG5, the verity fail disappears, replaced by a Multi-CSC message, I do a complete data wipe/factory reset, set up my basic google account and try the OTA, which fails every time. But once the dm-verity fail is gone, I can try doing an update from external storage, which I've tried with the BOK3 5.1.1 zip file posted here: http://forum.xda-developers.com/not...id-5-1-1-according-to-website-t3290683/page20 However, this still fails to load.
At this point I'm pretty convinced that I some other issue with my phone. I found elsewhere that someone was able to take their phone into Best Buy and have them flash the 5.1.1 update for them via Kies. That is probably my next step.
But I wanted to share what I've tried in case anyone else is experiencing the same dead end or in the off chance that someone has found a solution.
Sure would love to see the full 5.1.1 BOK3 tar.md5 sometime before Marshmallow hits, pretty sure using Odin to install the update that way would work....
traceestarr said:
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.
Click to expand...
Click to collapse
The full OTA for 5.1.1 was posted and I was able to update using Odin, following the instructions on this post: http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
Just wanted to update this post with the solution which finally worked for me.
Hi Folks,
Did anyone managed to install Y538C237B160 on a Huawei Y538?
My phone has an annoying notification that says a new version has been downloaded, if I clear this notification it comes back later.
If I try to upgrade the phone reboots and the process always fails at 28%.
When I try to upgrade from HiSuite it says that I'm already in the latest version.
Do you guys have any suggestions?
Thanks!
Marty_mcfly10 said:
Hi Folks,
Did anyone managed to install Y538C237B160 on a Huawei Y538?
My phone has an annoying notification that says a new version has been downloaded, if I clear this notification it comes back later.
If I try to upgrade the phone reboots and the process always fails at 28%.
When I try to upgrade from HiSuite it says that I'm already in the latest version.
Do you guys have any suggestions?
Thanks!
Click to expand...
Click to collapse
Have you a link for this firmware ?
y538-c237b160
i need it pls
achraf31001 said:
Have you a link for this firmware ?
y538-c237b160
i need it pls
Click to expand...
Click to collapse
I don't but it turns out that is not the latest, I was able to upgrade and the latest FW is y538-c237b173 I believe.
Do you have a Y538? When you try to upgrade the phone saves a copy of the dload file in the internal memory.
I am using ARROW Os (pie), Now i want to get back to official stock rom with locked bootloader plox help me how to do so.
JUST now I HAVE FLASHED Lenovo_Z2_Z2132_Q01017.1_M_ZUI_2.0.093_ST_160811_QPST with QFIL and it is showing error ownload Fail:Sahara Fail:QSaharaServer Fail:The directory name is invalid. plz help me
having exactly same issue
hilarioustiwari said:
I am using ARROW Os (pie), Now i want to get back to official stock rom with locked bootloader plox help me how to do so.
JUST now I HAVE FLASHED Lenovo_Z2_Z2132_Q01017.1_M_ZUI_2.0.093_ST_160811_QPST with QFIL and it is showing error ownload Fail:Sahara Fail:QSaharaServer Fail:The directory name is invalid. plz help me
Click to expand...
Click to collapse
keep posting so that solution come out
hilarioustiwari said:
I am using ARROW Os (pie), Now i want to get back to official stock rom with locked bootloader plox help me how to do so.
JUST now I HAVE FLASHED Lenovo_Z2_Z2132_Q01017.1_M_ZUI_2.0.093_ST_160811_QPST with QFIL and it is showing error ownload Fail:Sahara Fail:QSaharaServer Fail:The directory name is invalid. plz help me
Click to expand...
Click to collapse
Dude, this post is not a valid one.
To solve your error, extract the stock ROM files in a close directory to the pathname like ( c:\Stock\) .
ANd the next error you did was u did not launch qfil using admin rights.
do both the steps and try flashing stock.
hope I helped you. press the thanks button if so.:laugh:
@Az Biker
Try QFIL 2.7.460.
Here is the link https://www.google.co.in/amp/s/www....atest-qualcomm-flasher-qfil-qpst-2-7-460/amp/
Bro this post is a valid one
akshay pro said:
Dude, this post is not a valid one.
To solve your error, extract the stock ROM files in a close directory to the pathname like ( c:\Stock\) .
Andd the next error you did was u did not launch qfil using admin rights.
do both the steps and try flashing stock.
hope I helped you. press the thanks button if so.:laugh:
@Az Biker
Click to expand...
Click to collapse
Ok after successfully flashing my zuk z2 plus this is what i have to say about sahara.
I Still dont know why this error happens, i reinstalled new windows after which i followed the whole step. basically a fresh start.
although there are lots of tutorial available in youtube and xda dev forms the one i suggest is attached below:
https://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-z2131-only.104/
and for youtube walkthrough there is this link:
https://www.youtube.com/watch?v=wSHX-9S_oRc
now there are multiple workaround mentioned which i don't claim to be not useful or useful, but may workout for you:
shortening the path of zui rom from where it will be flashed: they recommend to past it directly to root of a drive
running the QPST Application with admin privileges which i would personally recommend
Disable Driver Signature Verification through out the process:
Click the Start Start menu and select Settings.
Click Update and Security.
Click on Recovery.
Click Restart now under Advanced Startup.
Click Troubleshoot.
Click Advanced options.
Click Startup Settings.
Click on Restart.
On the Startup Settings screen press 7 or F7 to disable driver signature enforcement.
You can search in google for more accurate steps, but one of the issue i faced was in latest version of window 10 i couldn't see the startup setting straight away. but at the bottom there is a link for additional option where you will find it.
[*]Downgrading to lower version or Upgrading to Higher Version QPST which for me, personally seems misleading and suggest you to stay with latest version
[*] and Last which i think made mine work, that is to reinstall Zuk Driver if there is an error which is persistent​
​
HAPPY FLASHING
Anthony Finix said:
Ok after successfully flashing my zuk z2 plus this is what i have to say about sahara.
...
HAPPY FLASHING
Click to expand...
Click to collapse
A really simple solution is to use MiFlash @mi-globe.com/download-xiaomi-mi-flash-tool-all-versions instead of any others along with the Qualcomm QDLoader drivers @AndroidFileHost.com
I had the problem but when i flashed the proper firmware in order, the problem resolved itself
ps i used an old version of qfil 2.0.xxx or something idk