I'm not the kind of person to ask for help if the answer to my problem might be out there already. I've followed relevant threads. I've searched XDA and googled. I've tried some things. I'm stuck.
I have an unlocked bootloader and FRP. When I go into Settings, OEM unlocking is greyed out. (Yes, I can use the phone.)
I do not have TWRP (anymore). I flashed stock recoveries.
I'm on build B101 and System Update is prompting my to update to B130. I can download it and, when prompted, reboot into recovery to update automatically.
I get to 100% and get the following error:
Software install failed!
Failed to check the update files.
Please download the package again.
Reboot system now
(See screenshot attached)
Now that it's available in Firmware Finder, I attempted to load B150 as well. Same thing.
I tried relocking bootloader, but it immediately prompts me to factory reset. After doing that, I get to reboot into recovery by default, other recovery by pressing the buttons, or fastboot via my PC.
Now, since we STILL don't have full firmware (supposed to have gotten it Friday, right?) I'm reluctant to use the images from here, especially if I'm not sure that would actually fix my issue.
What is going on with my software update? How do I fix this?
Did they actually release the BND-L24 firmware and no one noted it here?
Help, please!
Thanks.
johncro13 said:
I'm not the kind of person to ask for help if the answer to my problem might be out there already. I've followed relevant threads. I've searched XDA and googled. I've tried some things. I'm stuck.
I have an unlocked bootloader and FRP. When I go into Settings, OEM unlocking is greyed out. (Yes, I can use the phone.)
I do not have TWRP (anymore). I flashed stock recoveries.
I'm on build B101 and System Update is prompting my to update to B130. I can download it and, when prompted, reboot into recovery to update automatically.
I get to 100% and get the following error:
Software install failed!
Failed to check the update files.
Please download the package again.
Reboot system now
(See screenshot attached)
Now that it's available in Firmware Finder, I attempted to load B150 as well. Same thing.
I tried relocking bootloader, but it immediately prompts me to factory reset. After doing that, I get to reboot into recovery by default, other recovery by pressing the buttons, or fastboot via my PC.
Now, since we STILL don't have full firmware (supposed to have gotten it Friday, right?) I'm reluctant to use the images from here, especially if I'm not sure that would actually fix my issue.
What is going on with my software update? How do I fix this?
Did they actually release the BND-L24 firmware and no one noted it here?
Help, please!
Thanks.
Click to expand...
Click to collapse
I'm not certain why that happens, But I have a guess.
On each update that I have looked at, the recovery gets and update too. So different signatures and such.
Maybe the "stock" recovery you have re-flashed, is not correct version for your installed and update rom.
I cannot confirm this as I am missing the update app.
If you could help me with my missing files , I could help you with your update problem.
You could help me by pulling a list of packages installed so I can see what apps I have missing, and hopefully get them back (stock only, preferably done after a fresh factory reset.)
Directions for this on this thread.
See attached.
johncro13 said:
See attached.
Click to expand...
Click to collapse
thank you that helps.
I see I am missing an entire folder.
/data/hw_init
Could you see if it is accessible .
Code:
mkdir %userprofile%\Desktop\hw_init
adb pull /data/hw_init %userprofile%\Desktop\hw_init
I think it is not permitted though.
Uploaded. See referenced thread. I hope it helps!
johncro13 said:
Uploaded. See referenced thread. I hope it helps!
Click to expand...
Click to collapse
I will see what I can do with that. And hopefully can get past any file verification. And if I figure that out it should help you too.
Or , with my luck, the moment I figure it out , the stock firmware will come out.
I pushed the hw_init folder to /data while in twrp, then put stock recovery back(the version I expect should be correct) and I got same update failed error, as the OP.
That tells me maybe is probably some other reason , besides the version of stock recovery is causing this trouble.
Not sure if there is confirmation of successful update while bootloader is unlocked or not. Too late for me to try tonight, but next I will re-lock bootloader and try again.
My last (really current) phone needed to be re-locked in order to take updates.
**UPDATE**
re-locking bootloader did not help any at all. I still have error failed to check file, please download again.
On the manual update to oreo thread, they are using a "stock-ish" recovery named "no-check"
I am thinking I might flash that recovery to try and force this update to install.
BND-RECOVERY-NoCheck.img? Is that region-specific? Will it work with the BND-L24?
johncro13 said:
BND-RECOVERY-NoCheck.img? Is that region-specific? Will it work with the BND-L24?
Click to expand...
Click to collapse
tried it earlier today. Same error. will not finish update
johncro13 said:
BND-RECOVERY-NoCheck.img? Is that region-specific? Will it work with the BND-L24?
Click to expand...
Click to collapse
I have ordered a second 7x. I plan to pull the hw_init folder , and the remainder of /data that might be missing from this device , because of a result of formating it in twrp. I plan to restore that as an image, in hopes of getting updater to complete properly. And if that works, you will be able to use my backup and update your phone too.
If not , well , doesn't hurt to try.
I'm comparing the images pulled from my device and the images available for the Indian "return to stock thread. And I see the problem with the USA L24 version.
The cust.img for usa has no app folder.
It did not make sense to me before why there was apps only installed in /data. Because /data should be able to be fully wiped and your system will recreate the file structure. But The apps should have been on one of the images.
My second phone arrived today. I pulled the hw_init folder from it.
did a diff comparison on the updater app from the new phone and and the one that I had to apply patches to , to bring it up from b101 to b140. The result was 100% same.
and three more apps where in the hw_init folder as well. (bloat apps really)
now the bad news.
My original phone (the one that I had formatted /data on). Now has the same /data/hw_init folder as the brand new device. But always shows no update available.--It showed update once, the first time checked, install failed , now shows nothing available.
And the new phone does show an update available (B150) , but fails to install. Then after the failed install, now it shows no update available.
That's insane.
So... in summary, neither will update? Neither the original nor the unaltered brand-new device?
If anyone else has had this issue but has since resolved it, would you mind letting us know how? @mrmazak is working on it and I've also been told by the FUT team that I should expect some kind of communication from "Oscar Felix."
(If you've searched the forums for other Honor or Huawei devices, you probably already know that there is some speculation about whether or not Oscar Felix is a real person.)
I have the same problem but I'm stuck on update b140 and I can't even get the face unlock feature update. I was rooted with twrp recovery but now I have reinstalled the stock recovery and removed root
Sonny1732 said:
I have the same problem but I'm stuck on update b140 and I can't even get the face unlock feature update. I was rooted with twrp recovery but now I have reinstalled the stock recovery and removed root
Click to expand...
Click to collapse
Did you get the Oreo update today?
No I didn't, did you find out what can we do about this?
Is it a way I can update my phone manually
I'm watching this thread , myself. That might be the key.
Hopefully something comes up soon or is there a rom I can get if I reroot my phone?
Related
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.
Official updates for our M2 tablet,
although having installed another
recovery and root access, already.
- Disclaimer
Well, whatever you do with this guide is all up to you and in your own responsibility. You
should have basic knowledge about ADB and flashing, which is explained in many other
threads here on our beloved XDA.
- Issue
When you used this guide (https://goo.gl/r04XjJ) or any other one to give your M2 tablet
another recovery and therefore root rights, you have now the problem, that EMUI will show
you new updates, but you are not able to install them, because of the missing stock recovery,
of course.
- Solution
So, you have to flash back the original stock recovery, getting the official update and then you
can flash back your TWRP recovery.
- Guide
1. You should start your EMUI update programme/app and start the download of your update.
When it is finished, it will ask you to reboot into recovery and install automatically. As you have
no stock recovery I strongly advise not to do so. Usually nothing happens, but there is one case
reported, where it somehow ****ed up the guy's tablet. I am not sure, if that story is true, but
well, I have warned you.
2. Just turn your tablet off after you have finished downloading the update (it will wait now in
the directory "HwOUC" on your tablet and it is called "update.zip" - just let it sleep there).
3. Start the tablet in the fastboot recovery mode, meaning plugging in the USB cable (connected
to the computer) and hold the buttons "power" and "volume down", immediately, until a white
screen appears, which is the fastboot recovery screen. It should tell you, it has the bootloader
unlocked, which is normal, because you did that earlier on with any of the other guides (see above).
4. Copy the downloaded stock recovery of your choice to your ADB directory. In my case this is
"c:\ADB", but this depends on your way of installation.
5. Now open up a command line in Windows (with Windows key + R) and type "cmd") and go to
your ADB directory, using commands like "cd .." and "cd adb".
6. When having arrived in the ADB directory, you have to enter these commands one after the other:
fastboot flash recovery stock-recovery.img
fastboot reboot
If you renamed the recovery file, then you have to consider that in the command, of course.
7. The device will reboot directly into the recovery, because it "sees" the update in the update
directory et voila ... you are getting your awaited update. Sometimes it will boot not into the EMUI
recovery directly, but then you hast have to start the tablet normally, open up the EMUI app and
download the update again and do the OTA update properly with the reboot it tells you to do,
when it is finished.
8. Okay, now you have received your update, but if you want to have back your TWRP, you just
have to turn off your tablet and boot into the fastboot recovery again (see 3.).
9. You have to copy your TWRP recovery to your ADB directory (in my case "twrp.img" in "c:\ADB").
10. Now open up a command line in Windows (with Windows key + R and type "cmd") and go to
your ADB directory, using commands like "cd .." and "cd adb".
11. When having arrived in the ADB directory, you have to enter these commands one after the other:
fastboot flash recovery twrp.img
fastboot reboot
12. The tablet will reboot and you are back to a working lovely updated M2 tablet.
- Root:
If you want to have root rights, I strongly recommend flashing Magisk within TWRP, because it is
just a nice and more modern approach to having root. It works very fine on my M2 10 tablet. The
link for the files and guide is here:
https://goo.gl/UXYk4d
It is very easy. You just flash Magisk 12 in TWRP and then install the Magisk Manager app from the
Play store.
- Files for M2-802L and M2-A01L:
https://ufile.io/0df492 (all four recoveries here)
https://files.fm/u/aajdmadr (all four recoveries here)
https://www.file-upload.net/download-12438839/HuaweiM2recoveries.rar.html (all four recoveries here)
Have fun with your updated tablet. ... and I am happy, if I could help you - any coffee appreciated.
...
..
.
+++ saved +++
Additionally, I can offer you the updates B007 and B010 (most current one) for the
M2 10 LTE (M2-A01L), because I managed to save them/back them up. These are the
European versions of B007 and B010 with all language files, I believe.
So, who is having a M2-A01L and is still sitting on B006 or B007, might try a manual
update, which is as easy as pie. It is just one simple step.
Also, an update from B009 to B010 might be possible.
Of course, I cannot give any guarantee for Huawei's update files, which you will
understand, I guess.
what android version ?? M2-801L, thanks
Eagle-no1 said:
what android version ?? M2-801L, thanks
Click to expand...
Click to collapse
M2-A01L, not M2-801L. For all 8 models you find your ROMs here:
https://forum.xda-developers.com/me...om-8-0-models-stock-marshmallow-roms-t3535466
or
https://forum.xda-developers.com/me...-b207-android-6-0-marshmallow-emui-4-t3533572
or
https://forum.xda-developers.com/mediapad-m2/development/rom-stock-rooted-xposed-t3519031
xsycox said:
Additionally, I can offer you the updates B007 and B010 (most current one) for the
M2 10 LTE (M2-A01L), because I managed to save them/back them up. These are the
European versions of B007 and B010 with all language files, I believe.
So, who is having a M2-A01L and is still sitting on B006 or B007, might try a manual
update, which is as easy as pie. It is just one simple step.
Also, an update from B009 to B010 might be possible.
Of course, I cannot give any guarantee for Huawei's update files, which you will
understand, I guess.
Click to expand...
Click to collapse
I'd greatly appreciate it, if you could share. Got the problem that my A-01L got corrupted. The only official ROM I've been able to find has been B005 what is somewhat old. As it seems to be a pre-release version the tablet doesn't find any updates. Thus I'd like to try to upgrade to B007, or even B010 manually when I'm back home. Currently I'm on a weekend trip as friends of mine are going to marry tomorrow. Thus I'd be able to download them on Sunday evening if you'd provide them.
Regards
Sent from my htc_pmeuhl using XDA Labs
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
5m4r7ph0n36uru said:
I'd greatly appreciate it, if you could share. Got the problem that my A-01L got corrupted. The only official ROM I've been able to find has been B005 what is somewhat old. As it seems to be a pre-release version the tablet doesn't find any updates. Thus I'd like to try to upgrade to B007, or even B010 manually when I'm back home. Currently I'm on a weekend trip as friends of mine are going to marry tomorrow. Thus I'd be able to download them on Sunday evening if you'd provide them.
Regards
Click to expand...
Click to collapse
https://forum.xda-developers.com/me...om-official-manual-updates-m2-tablet-t3595211
zedoc said:
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
Click to expand...
Click to collapse
I have Magisk running on several devices, including the M2-A01L, but I must admit,
I never got the Safetynet passed, even with Magisk hide enabled.
I just use it as systemless root and with systemless Xposed, which is great.
zedoc said:
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
Click to expand...
Click to collapse
xsycox said:
I have Magisk running on several devices, including the M2-A01L, but I must admit,
I never got the Safetynet passed, even with Magisk hide enabled.
I just use it as systemless root and with systemless Xposed, which is great.
Click to expand...
Click to collapse
After enabling magisk hide, you have to reboot your device. Got the 801L working with that and safetynet passes.
Noob Question on recovery files
Hi, and thanks for a incredible well detailed guide for updating. Came here because I haven't found any good recovery files for the wifi model. I've been trying (unsuccessfully may I add...) to install TWRP and magisk. So, my question is: can the recovery files for the LTE model be used on the wifi model? (M2-A01w). Thanks for your help!
myst771 said:
Hi, and thanks for a incredible well detailed guide for updating. Came here because I haven't found any good recovery files for the wifi model. I've been trying (unsuccessfully may I add...) to install TWRP and magisk. So, my question is: can the recovery files for the LTE model be used on the wifi model? (M2-A01w). Thanks for your help!
Click to expand...
Click to collapse
Sorry, I have been on vacation.
To be honest, I am not sure, if the recovery for M2-A01L works on M2-A01w, too, but you can just try it.
I think, there should not be that big a problem, because the recovery has nothing to do with Wi-Fi or LTE, at all. It is just important, that partition tables and drives are accessible the same way and well, I really think, there is not much difference in between the M2 10 models.
From M2 8 to 10 there is a difference, of course. That is why I uploaded both recoveries (for 802L and A01L).
Just use that guide (https://forum.xda-developers.com/mediapad-m2/how-to/guide-unlock-bootlader-twrp-root-huawei-t3322340) without the SuperSU flashing and my recoveries in this guide.
Hi guys,
I need help, I have a M2 10 LTE previously modded with TWRP for root and I've just followed this guide to update from 007 to 010 version.
So I've flashed the stock-recovery, rebooted the tablet, requested the firmware update (I don't know if I got any error during the process) and the tablet has rebooted. Now it's stuck on HUAWEI logo..
I use this tablet for work so I really need to recover it asap.
Please help.
Shocker580 said:
Hi guys,
I need help, I have a M2 10 LTE previously modded with TWRP for root and I've just followed this guide to update from 007 to 010 version.
So I've flashed the stock-recovery, rebooted the tablet, requested the firmware update (I don't know if I got any error during the process) and the tablet has rebooted. Now it's stuck on HUAWEI logo..
I use this tablet for work so I really need to recover it asap.
Please help.
Click to expand...
Click to collapse
Could upload the B010 fullstock ROM/firmware. Thus you could reset the device to the latest stock ROM using the /dload method and gain a factory rested Huawei, as if out of the box. Just quote me if you'd want me to upload and I'll share the link asap. Took that way myself as soon as I found the full stock ROM.
Sent from my htc_ocnuhl using XDA Labs
thanx
Dear xsycox
I have an issue where I updated my W version tablet to L version accidentally and I am having issue getting it back..
I am currently trying to get some help in this thread: https://forum.xda-developers.com/me...-m2-installed-wrong-update-zip-t3563105/page2
Can you please help me out? do you have any idea what ican do to get back to W version?
Thanks!
First things first. I surrender. I'm a noob with android. I had windows phone previously and only now came to android.
Here's the scenario:
1. My z2 force was properly rooted with magisk and twrp. I followed the guide in xda only.
2. My device was brought from India so carriers like sprint, t-mobile are not applicable I think.
What I Did:
0. Wanted to unroot my device. So, I decided to first uninstall the modules in magisk that I had installed.
1. Tried to uninstall magisk modules and rebooted from the magisk application.
2. Got into Boot loop, so went to recovery mod and wiped everything. Hard reset was done.
3. Installed magisk app again and clicked uninstall to remove root. I wanted to install the latest security update. Update kept failing so I decided to unroot. I choose uninstall completely option.
4. Rebooted the phone manually after clicking uninstall in magisk manager. Using the 'root checker' app I checked if unrooting was successful but it said, 'root was not properly installed' or something like that. So, I installed magisk manager again and again uninstalled root completely.
5. Still same issue. Root checker said the same thing again. So, installed magisk manager again and this time I wanted to remove root using ES file manager as I saw in an online guide. But I couldn't give it root permission because it was not properly installed as said by root checker. So, I decided to root my phone properly but stupid me, clicked 'install' in magisk manager and chose the recommended option (don't remember exactly what it was). It downloaded magisk zip and did some changes and asked to reboot. After rebooting, my phone went straight to the black screen with an android icon and 'no command' written below it. It kept going there again and again.
6. I assume that is the recovery mode. I press volume up and power button and choose the wipe everything again(Like I did before) to hard reset phone. Wiping was successful but it still kept booting to that black screen.
Additional Info:
1. Phone wasn't carrier version. It was bought in India. It is running Oreo 8.0.
2. In bootloader menu : (Not stating all)
BL: MBM-3.0-nash_retail-641a15b-180306
Product/Variant: nask xt1789-06 64GB PVT
Console[NULL] :null
Tools Mode Config: DISABLED
Power OK
flashing_unlocked
Software Status : Modified
Transfer Mode : USB Connected.
3. Yes, Bootloader menu is accessible.
4. Choosing recovery mode in bootloader menu reboots phone and takes me to that blank screen I mentioned before.
5. Connecting to USB to my PC when in bootloader menu, it connects as 'Fastboot nash S'. ADB terminal says no devices found.
What I want:
1. Boot into OS.
2. Remove root completely so I can install system update.
Please help or offer suggestions as I do not have a secondary device with me. If I have to absolutely go to a service center, I will.
You should flash it back to stock.
You posted that your phone is nash xt1789-06 64GB PVT, you can grab the latest firmware here.
The flashing instructions are here in post #5, and any question you might have is most likely answered in that thread.
Just download the firmware, boot into bootloader mode, and follow the instructions.
FYI in fastboot mode adb commands don't work, it's fastboot. To verify that you're connected and ready type
Code:
fastboot devices
and you should see your serial# like you do in adb.
That should put you back to stock and good to go.
41rw4lk said:
You should flash it back to stock.
You posted that your phone is nash xt1789-06 64GB PVT, you can grab the latest firmware here.
The flashing instructions are here in post #5, and any question you might have is most likely answered in that thread.
Just download the firmware, boot into bootloader mode, and follow the instructions.
FYI in fastboot mode adb commands don't work, it's fastboot. To verify that you're connected and ready type
Code:
fastboot devices
and you should see your serial# like you do in adb.
That should put you back to stock and good to go.
Click to expand...
Click to collapse
Thank you for the reply. I figured it out and went ahead with it. But now, I'm not seeing the May security update. The device shows it has March update and that no other update is available. Any idea why? Also, root checker still says 'root not properly installed'. How to unroot completely? Thanks a lot!
Sparkzz27 said:
You should flash it back to stock.
You posted that your phone is nash xt1789-06 64GB PVT, you can grab the latest firmware here.
The flashing instructions are here in post #5, and any question you might have is most likely answered in that thread.
Just download the firmware, boot into bootloader mode, and follow the instructions.
FYI in fastboot mode adb commands don't work, it's fastboot. To verify that you're connected and ready type
Thank you for the reply. I figured it out and went ahead with it. But now, I'm not seeing the May security update. The device shows it has March update and that no other update is available. Any idea why? Also, root checker still says 'root not properly installed'. How to unroot completely? Thanks a lot!
Click to expand...
Click to collapse
Did you look to see if the May Security Update has been released for your specific device? When you downloaded the stock firmware did you look to see what month security patch it contained? Have you tried to perform a system update to see if you can OTA to the latest security patch?
Now, if you completely flashed back to stock then root is removed. Root checker says that because root access is not installed at all. Flashing back to stock removes any trace of root, IIRC.
Sent from my Moto Z2 Force using XDA Labs
Don't forget, if you followed the flashing instructions from the other post they were omitting the gpt.bin and bootloader. So if you didn't flash those then that's why you're probably not seeing any updates, you need to be on full stock all matched up. Just reflash the firmware you downloaded in its entirety. @fast69mopar is right, once you flash a new boot.img root is gone, and since you flashed back to stock it's definitely gone.
Sparkzz27 said:
Thank you for the reply. I figured it out and went ahead with it. But now, I'm not seeing the May security update. The device shows it has March update and that no other update is available. Any idea why? Also, root checker still says 'root not properly installed'. How to unroot completely? Thanks a lot!
Click to expand...
Click to collapse
If you flash with factory image you should be unroot completely and root checker will keep telling you "root not properly installed" if you are not rooted just ignore root checker if you not planning to be rooted.
Hi there I have a xt1789-06 I was not getting updates and flashed the first Oreo update from here https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/
My phone now does the updates and everything works fine.
However I did try to flash a custom ROM and root I made a mistake and ended up both a hard brick, because I was on Oreo I thought that flashing the Oreo blank flash would rectify the problem, but it was not working so I tried flashing the N blank flash and it worked.
I've come from using Samsung phones so I'm use to Odin and have not used fastboot commands. After reading many threads I know what I had done was not decrypting my device which ended up with a hard brick I will in the future flash a custom ROM now I know a little bit more.
Blank flash files are here
https://mirrors.lolinet.com/firmware/moto/nash/blankflash/
Then once back to fastboot flash the flash all from the link at the top of my post.
41rw4lk said:
Don't forget, if you followed the flashing instructions from the other post they were omitting the gpt.bin and bootloader. So if you didn't flash those then that's why you're probably not seeing any updates, you need to be on full stock all matched up. Just reflash the firmware you downloaded in its entirety. @fast69mopar is right, once you flash a new boot.img root is gone, and since you flashed back to stock it's definitely gone.
Click to expand...
Click to collapse
Hi, sorry I was busy with work. I managed to use my phone that way. I didn't use the instructions in that post. Instead, I download flashallutilities (In how to return to stock post in xda for z2 force), then ran the batch file which did all the work. I noticed other problems too,
1. My Jio sim(4g LTE) does not show 'enhanced LTE mode' in options. Also when I call someone, it fails immediately saying 'call failed. try another method.' However, internet connection works from the sim. My other sim works fine for calls and data.
2. I'm seeing other keyboards in manage keyboards section. I don't recall seeing google pinyin input, zhuyin input, etc before. What's worse is my office's app shows option to switch to chinese version of the website for logging in. My language and time zone are set correctly though - English India and GMT +5:30.
3. The web browser I used before couldn't be found in the play store anymore. My launcher still shows the icon with a green arrow in left bottom of the icon to direct me to playstore to download it but playstore says item not found. The app name is simply 'browser'. I searched for it on desktop website too (without logging in), still couldn't find it. Guess it's a coincidence,
Also: Herehttps://www.getdroidtips.com/moto-z2-z2-play-z2-force-stock-rom/#Moto_Z2_Force_Android_80_Oreo_Firmware, the carrier global version says 'OCX' instead of 'OPX'. Any idead about that?
Sparkzz27 said:
Hi, sorry I was busy with work. I managed to use my phone that way. I didn't use the instructions in that post. Instead, I download flashallutilities (In how to return to stock post in xda for z2 force), then ran the batch file which did all the work. I noticed other problems too,
1. My Jio sim(4g LTE) does not show 'enhanced LTE mode' in options. Also when I call someone, it fails immediately saying 'call failed. try another method.' However, internet connection works from the sim. My other sim works fine for calls and data.
2. I'm seeing other keyboards in manage keyboards section. I don't recall seeing google pinyin input, zhuyin input, etc before. What's worse is my office's app shows option to switch to chinese version of the website for logging in. My language and time zone are set correctly though - English India and GMT +5:30.
3. The web browser I used before couldn't be found in the play store anymore. My launcher still shows the icon with a green arrow in left bottom of the icon to direct me to playstore to download it but playstore says item not found. The app name is simply 'browser'. I searched for it on desktop website too (without logging in), still couldn't find it. Guess it's a coincidence,
Also: Herehttps://www.getdroidtips.com/moto-z2-z2-play-z2-force-stock-rom/#Moto_Z2_Force_Android_80_Oreo_Firmware, the carrier global version says 'OCX' instead of 'OPX'. Any idead about that?
Click to expand...
Click to collapse
Your Z2 is a xt1789-06 correct? It's an international version, the flashall in the utilities zip from the return to stock thread is for US based phones, TMO and Sprint specifically. What was or wasn't flashed using that flashall I couldn't tell you, I don't have an international phone. That's why I linked to the post that deals with that version of the Z2 and has all the answers and links you need to sort your phone. Others in that thread might be better suited to help you along. This is the thread that deals with the xt1789-06.
As for calling and sim, might be related to how you flashed or simply an apn issue. You can go to network settings, mobile, access point names, and reset those to default. That should pull the apns from your sim so you'll have the correct apns.
As for keyboards and browsers, I don't know what is included in the international stock versions, but they are subject to change based on initial setup/default language and rom version. As for the OCX vs OPX, I'm not sure what the difference is. I know 'O' is for Oreo but for the rest I don't know. Maybe one is gsm one is cdma? I don't know. I do know that the thread I linked to will have more info and be able to help you better since it's for your version of the Z2. Sorry I can't help you more, but post any questions you have over there and they should be able to sort you out.
My phone arrived last night. I immediately, following the instructions I found here, magisk'd it. As soon as I flashed the patched image and rebooted... I found that the touch screen had stopped working.
So I booted into recovery (which was hard, because I can't figure out any way to shut my phone down), and wiped data / factory reset. The bootloader is still showing as unlocked. And the touch screen is still not working.
Does anybody know why this might be or what I should do about it? Note that I didn't buy from Google, I bought new from a well-reputed ebay seller...
Send it back. It sounds like a hardware issue.
sic0048 said:
Send it back. It sounds like a hardware issue.
Click to expand...
Click to collapse
Alright.
Problem number 2: if I lock the bootloader, it tells me there's no valid operating system on the phone and won't start up. It only starts up while the bootloader is locked. So... do I send it back with the bootloader unlocked and hope they don't mind?
DanHakimi said:
Alright.
Problem number 2: if I lock the bootloader, it tells me there's no valid operating system on the phone and won't start up. It only starts up while the bootloader is locked. So... do I send it back with the bootloader unlocked and hope they don't mind?
Click to expand...
Click to collapse
If they are a reputable seller on ebay they probably wouldn't want to sell you a broken phone as it hurts their reputation; I'm not saying it didn't happen, but individual sellers are usually careful on that end.
Have you at least tried fastboot flashing the stock "bonito" image yet and see if that restores your touch? https://developers.google.com/android/images
*Also, keep in mind that Q is supposed to be coming out pretty soon(which may or may not help you situation). Pixel phones supposedly get official Q on Sep 3rd or you can join the beta program if you can't wait until then.
good luck:good:
Reflash the factory image and relock the bootloader... It is an official process from Google, if that fails contact the seller and RMA the unit.
Hey buddy! I was in the same boat as you, so maybe your situation was the same as mine. My problem was that I had flashed the incorrect boot image. What I'd suggest is what I did: use a mouse to navigate through the phone and check the system version, then download the exact same OS version from google, extract, and flash that stock boot image. If it works, you can patch that same stock boot image with magisk and flash that one to get root and keep the touch screen working.
I hope this works out for ya. Cheers!
As it's new and you've got nothing to worry about saving I'd just flash the latest factory image via fastboot and once it's up extract the boot from that image and patch it. The fellow above is probably correct but there is one other thing, use an A to C cord, not the C to C cord for all your flashing.
Bob nesta said:
If they are a reputable seller on ebay they probably wouldn't want to sell you a broken phone as it hurts their reputation; I'm not saying it didn't happen, but individual sellers are usually careful on that end.
Have you at least tried fastboot flashing the stock "bonito" image yet and see if that restores your touch? https://developers.google.com/android/images
*Also, keep in mind that Q is supposed to be coming out pretty soon(which may or may not help you situation). Pixel phones supposedly get official Q on Sep 3rd or you can join the beta program if you can't wait until then.
good luck:good:
Click to expand...
Click to collapse
Yes, I've tried multiple versions of the bonito image, and none of them would flash properly. I'm really just trying to figure out if they're going to blame me because I unlocked the bootloader.
Will Q actually release tomorrow? Like, stock images up and everything? Oh, well, I might as well wait until tomorrow while I try to figure out their return policy.
DanHakimi said:
Yes, I've tried multiple versions of the bonito image, and none of them would flash properly. I'm really just trying to figure out if they're going to blame me because I unlocked the bootloader.
Will Q actually release tomorrow? Like, stock images up and everything? Oh, well, I might as well wait until tomorrow while I try to figure out their return policy.
Click to expand...
Click to collapse
You can relock the bootloader. Instructions are in the link I provided earlier. How would they know you unlocked it?
As far as Q - maybe? That's why I said "supposedly" it comes out the 3rd (https://www.theverge.com/platform/a...ndroid-10-pixel-september-3-release-leak-date) , but there are no guarantees in life (except death & taxes).
Again, just to be sure, you are using a USB A to C and not a C to C, correct?
DarkShadowMX said:
Hey buddy! I was in the same boat as you, so maybe your situation was the same as mine. My problem was that I had flashed the incorrect boot image. What I'd suggest is what I did: use a mouse to navigate through the phone and check the system version, then download the exact same OS version from google, extract, and flash that stock boot image. If it works, you can patch that same stock boot image with magisk and flash that one to get root and keep the touch screen working.
I hope this works out for ya. Cheers!
Click to expand...
Click to collapse
I don't have a USB-C mouse, but I guess I could keep trying images until one of them works...
krabman said:
Again, just to be sure, you are using a USB A to C and not a C to C, correct?
Click to expand...
Click to collapse
Yes, A to C.
Bob nesta said:
You can relock the bootloader. Instructions are in the link I provided earlier. How would they know you unlocked it?
Click to expand...
Click to collapse
No, again, like I said, I can't. I tried fastboot OEM lock. And I tried flashing multiple stock images. Nothing seems to be working. I can try again and get you the exact error messages...
DanHakimi said:
No, again, like I said, I can't. I tried fastboot OEM lock. And I tried flashing multiple stock images. Nothing seems to be working. I can try again and get you the exact error messages...
Click to expand...
Click to collapse
Please do. I'm no dev & can probably offer little to no help, but if you post your errors someone else may be able to help you out.
It could just be a cable/driver/fastboot issue & not the phone, so please provide error info.
Ok, do the full smash. This assumes a basic familiarity with flashing mechanics.
1. Download and install the latest fastboot package.
2. Download the latest image from google again.
3 Use a known good A to C usb cord
4 Before flashing the image type all the following commands one by one in fastboot...
fastboot erase system_a
fastboot erase system_b
fastboot erase boot_a
fastboot erase boot_b
fastboot reboot-bootloader
5 Flash the image using the flash all script.
6 Once you're up extract the boot from the image you flashed and patch it in magisk.
7 Flash the patched boot image.
DanHakimi said:
I don't have a USB-C mouse, but I guess I could keep trying images until one of them works...
Click to expand...
Click to collapse
I don't either. I used a USB OTG cable
Had a **** ton load of issues trying to go from rooted and TWRP with custom rom to Android 10.. Every time I ran the flash-all.bat it would fail at one stage or another.. Finally grabbed the Pie Ota from the site, sideloaded it through TWRP then wiped everything through stock recovery and then took the Android 10 update. My point is, use the OTA and sideload it
I was rooted on Android 10 beta 6 and trying to download the OTA through the phone update failed every time. I uninstalled magisk and restored images..but still failed. I finally had to sideload the OTA image and it finally updated. That was the only way to get mine to work. Then I took the boot image from beta 6 that was already patched through magisk and re-flashed it because the boot image from Android 10 official patched through magisk would not give root...kept failing. Then when I re-flashed last months beta 6 image, upon reboot the screen would freeze and no apps would load. I then booted into recovery and did a factory reset and upon reboot magisk was identified and root was acquired....phone worked perfectly after that and no issues....weird. I then just reloaded all of my apps from backup and was on Android 10 official, rooted through magisk.
I used the dongle included with the phone to make my usb-wireless mouse work. The OS is currently showing the July 5 version of Android 9. When I try flashing that specific version, I see what I attached in my screenshot. Other versions show similar bugs, although perhaps a few more. I haven't tried Android 10 yet...
DanHakimi said:
I used the dongle included with the phone to make my usb-wireless mouse work. The OS is currently showing the July 5 version of Android 9. When I try flashing that specific version, I see what I attached in my screenshot. Other versions show similar bugs, although perhaps a few more. I haven't tried Android 10 yet...
Click to expand...
Click to collapse
I suspect you are running out of hard disk space on the computer that you are using to try to flash all this with. I ran into a similar issue once when the C drive of my computer was nearly full. The system file ends up needing a lot of disk space in order for it to be unpacked. The error you are getting is that you are running out of space and it cannot unpack it. Again, this isn't phone memory space, this is actual computer hard drive space.