yashsingh1/xdaforums huggingface dataset:
[Huawei Mate 10  Guides, News, & Discussion] Pituky:
Tried to install Hisuite for that thread and it does not install. Do you know where to find and older Firmware Finder version?

Thank you
[Huawei Mate 10  Guides, News, & Discussion] derausgewanderte:
If it's the full image you can install the latest. If it's an update I suggest you do it stepped. That's how I would do it. Luckily for me the updates trickled in after long waiting.

---------- Post added at 11:03 PM ---------- Previous post was at 11:02 PM ----------

Sorry, I got the files from that thread. Maybe the OP knows.
[Huawei Mate 10  Guides, News, & Discussion] Pituky:
Finally I was able to install Hisuit the old one apk. Now the problem is that on FF the latest fw y see is 110 and I have 112 installed. That is strange.

I know the model bla-a09 (C567) has approved till 119 at least... Why they are not on FF.
[Huawei Mate 10  Guides, News, & Discussion] derausgewanderte:
that's what you see if it's not working correctly in FF. Apparently it's not passing through the proxy settings or similar issue.
[Huawei Mate 10  Guides, News, & Discussion] culiacanazo:
Not very soon, but presumedly with Pie... But did you notice they called me? Lol i guess they got a little heat from me as of late...

Screenshots
[Huawei Mate 10  Guides, News, & Discussion] cervantesjc:
I was in the same version, 8.0.65 for a long time, I contacted Huawei customer support, after a back and forth they said that they were gonna replace my phone, they asked my IMEI, and a few days later I got the update, maybe they forced send the update after I bugged them for so long.
[Huawei Mate 10  Guides, News, & Discussion] nabril15:
I'll try calling them today at the 800 number that shows up in the Huawei app on the phone. Did you call or write them? And what number did you call, if you called?

I'm tempted to try the HISuite method bit using the latest version of that app.
[Huawei Mate 10  Guides, News, & Discussion] cervantesjc:
I called the number in the app, I did it a few times, keep track of the times you've called them, also of the things you've talked to them, they really don't keep track of things very well.
[Huawei Mate 10  Guides, News, & Discussion] nabril15:
Cervantes---I just spoke with them, and blah blah blah. "I will get an email when an update is released", but I kept stressing that I am 5 or 6 updates behind, so getting the latest is not a solution. I would like to get somewhat closer to the latest version, 119.

Aggghhhhh. I have put the phone on sale in Swappa. I love the phone, but getting a firmware update should not be this complicated. I tried the Hisuite method before calling but updating the pc software to the latest version, and it didn't even find an internet connection despite having a perfect connection. I am a stubborn Scorpio that will press on and on, but this is very frustrating. I would like to root and play with different ROMS, but I'm terrified of taking that route. And I have the freaking bootloader unlock code!!!
[Huawei Mate 10  Guides, News, & Discussion] cervantesjc:
Trust me, I did the same thing, just keep calling them, I really pushed forward and got the update after a few days.
[Huawei Mate 10  Guides, News, & Discussion] nabril15:
I'm sorry to be a pain. I will attempt to follow the steps in the OP. Do I have to go one by one 104, then 109, then 112, etc? Or can I just extract the latest one shown in the OP, 112?
[Huawei Mate 10  Guides, News, & Discussion] culiacanazo:
I too have found out that bugging them kinda works

That's why i recorded them, as shown in my screenie

If your bl is unlocked I'd guess it would hold value more since that's unattainable as of late. Good to keep in mind ;)

Perhaps that's why they wanted your IMEI?

You don't have to go one by one.
[Huawei Mate 10  Guides, News, & Discussion] nabril15:
I opened a ticket via chat/email, and they've written back 4 times with the same generic script

"The full update it might take up to a couple of months in order to get it. Just keep on checking the UPDATER option every week or so. Try connecting it to different wifi networks. And reboot it every 3-4 days"

I keep insisting that versions 109 and 110 are probably a year old, and I should at least receive those quickly since they are not new updates. They don't get it. I keep stressing that I am on version 65 which is the equivalent of windows 95, and they keep telling me that win10 updates are coming soon.
[Huawei Mate 10  Guides, News, & Discussion] culiacanazo:
I forgot to mention, the latest isn't 112, it's 119, and it isn't in the op (I'm assuming the dude opened up an account just for this and then never again logged in) but i posted it, let me link it

https://xdaforums.com/showpost.php?p=77248270&postcount=72
[Huawei Mate 10  Guides, News, & Discussion] rogconnect:
My advice DON'T USE THIS METHOD.... It will brick your device. I did it several months ago trying to update from 65 to 110 and BRICKED. Finally unbricked using HOTA.
[Huawei Mate 10  Guides, News, & Discussion] Pituky:
Yes contacted them using the HiDontCare application. They asked the imei to me too.

They say that since I'm located in south America I'm not going to recibe the updates. Even having the model USA Mate 10 Pro BLA-A09 (c567), since they deliver by ranges of ips.

Nonsense. The first time I turned on the phone it updated to 112, was in 110 initially.

I will use NordVpn for a month to see if having an US ip will help.

The guy said, reboot the phone once a week, change wifi connection frequently, go to system and check every 3 days.

Mmmm I feel it will not help at all... Getting an update is very complex.
[Huawei Mate 10  Guides, News, & Discussion] KevinAce:
You can grab .119 from Funkyhuawei but the firmware actually breaks 2 of the camera settings and Huawei knows about this and seems to be in no hurry to fix it.

My other phone is the Mate 10 Pro US Version BLA-A09
[Huawei Mate 10  Guides, News, & Discussion] culiacanazo:
Not following instructions bricks phones. Not this method. Proven!

What the hell does being in South America have to do? Freaking Huawei, they're DUMB AF!

Hahahaha HiDontCare! Good one! xD

Do it manually, [MENTION=2167076]Pituky[/MENTION], just follow instructions.

Sir, the patch HAS BEEN RELEASED FOR A WHILE! I don't know why [MENTION=4572798]duraaraa[/MENTION] doesn't either pull the broken update or provide the patch. That's fixed, is also proven, as stated by me and some others here
[Google Pixel 2 XL Questions & Answers] Krisbo:
Hi guys,

I bought a GS9+ over the weekend, hated it's camera and exchanged it for a Pixel 2 XL.

One feature I did like was the ability to set a video to the lock screen wallpaper.

I've found a few apps that can set a video to a live wallpaper but they can only set the home wallpaper or both. I've yet to find an app that can set the lock screen wallpaper independently of the home screen wallpaper like Google photos does.

Any ideas?

Ta,

Kris
[Mogul, XV6800 General] allofthepeople:
Ive tried and tried wmodem and pdanet but they no longer work for me tethering between my mac and my mogul via bluetooth with the new htc 3.35 rom. When I click unable bluetooth DUN on pdanet it says "unable to assign com port please make sure com7 or com4 is available on your device. bluetooth dun will remain off (err=2404)".

can someone help?

thanks
[Mogul, XV6800 General] Asphyx:
Juts a guess but the new radio assigns Com4 to the GPS which may be why PDANet has an issue.

My guess is PDANet will have to be updated to be a bit more flexible on which com port it wants.
[Mogul, XV6800 General] mhmogul:
PDAnet was working for me...

I did have it working without any mods. Then, it quit working. In my case, I had installed ICS, which I never did get working. Then, PDAnet stopped working. I tried removing/reinstallong (after uninstallling ICS), to no avail. I may just reflash the phone to get it all back to original components, and try PDAnet again.
[Mogul, XV6800 General] catpunt:
I have the same issue with the new ROM and the "USB modem" program from www.mobile-stream.com. When I set it to "Connection: Bluetooth" and click "Enable" it doesn't turn on.
[Mogul, XV6800 General] Gilliland:
It's easy enough to move the internal GPS to COM5, and the GPS works fine that way. So that will free up COM4 for PDANet. Unfortunately, it still won't make Bluetooth DUN work. The only way that I've been able to tether is through a wired PDANet connection. That works fine.
[Mogul, XV6800 General] Asphyx:
Gil - You using XP, Vista or something else?

I noticed that on Vista you can not get BTDUN (even on the stock roms) unless you were operating under an administrator account or stopped the BT tools in Vista and ran them under the administrator account.

For that reason I have always tethered via USB and skipped trying to do it via BT...though BT would be much cooler...
[Mogul, XV6800 General] Gilliland:
I'm on XP. DUN over BT worked fine using PDANet on the old ROM. But on the new ROM it doesn't work at all.

The wired connection is faster anyway, so I'd always prefer that. But sometimes it's handy to be able to do it wirelessly.
[Mogul, XV6800 General] catpunt:
I finally got BT DUN working with the USB Modem app from www.mobile-stream.com. I changed the Mogul GPS port to COM3 but BT DUN still didn't work. I had to remove the BT pairing with the phone from the computer, then enable BT DUN from the USB Modem app THEN re-pair with the phone with the app running. This time it detected the dial-up BT service on the phone and after I completed the pairing, I was able to dial #777 normally.

Also the speed was much faster than the speed with ICS BT PAN. I was getting ~500kbps with BT PAN and I'm getting 1100kbps+ with BT DUN.
[Magisk] BlazzedTroll:
Greetings,

I recently got a Pixel 2 XL and the first thing I did was try to root with SuperSU and TWRP. I had some issues with it and someone suggested Magisk. It worked great and I was able to update from the 8.0 to 8.1 with root. I kept up with the latest Magisk installs until the past week or so.

My phones USB port appears to have failed partially. Luckily I can still charge, but there is no way to see the device storage from a PC. Support has defaulted, after much troubleshooting, to an RMA solution with a refurbished phone. Thankfully, this seems to be covered by warranty and isn't going to pose a cost issue. However, through the troubleshooting I was forced to do a factory reset. I looked up some information regarding factory reset with rooted devices. I cannot find the exact tutorial I followed or thread I gained the how-to information, I'm not sure which it was. I simply searched how to factory reset magisk 8.1 device. It was quick and most of the stuff I find now has the same information.

Open Magisk, uninstall. Open TWRP, uninstall. Device Settings, Factory Reset. Easy

This seemed to have worked. I didn't run into any locked hardware issues thankful because I don't have USB to really flash something to it.

Before I continued, prior to attempting the reset I fully backed up the device to my computer using ES File Explorers FTP transfer over the wifi. This was great, lots of photos were able to be saved with no hassle. I copied the entire root directory and have it backed up.

The problem with the reset is that while Magisk remained uninstalled, TWRP has a basic file installed that upgrades to the full app. I still have root, which would have been nice, except I still need to unroot and go back to factory settings before I can send this device in.

Before I make a mistake moving forward, I want to find the best way to unroot, (preferrably relock the boot also), and return to factory stock as it was the day I got it so I can return in it in the best state I can.

I am running rooted android 8.1.0 Pixel 2 XL with kernel 4.4.88 if the helps. When I reset to factory defaults TWRP remains installed and root persists. I cannot connect via USB and run android dev tools to flash anything directly. How can I restore this device? I should have all original kernels backed up. During the root process I remember them saying to copy the old ROMs first and I performed every step exactly. I do have access to move files to and from the device via WiFi. Is it this even possible?

PS, does anyone think the firmware and rooted install could be the problem with the USB? It seems entirely like failed hardware to me but the troubleshooting was extremely thorough and seems to indicate softare/firmware are likely to be the issue instead of the hardware issue that was determined. Could this still rooted device have corrupted the USB transfer? It seems I should do my best to rule this out as well, more so than just giving them a factory reset device. I'd rather keep my phone if it can be fixed easily, than obtain a possibly low quality heavily used refurbished model.

Regards
[Magisk] teddy0209:
Did you try removing and reinstalling the drivers?
[Magisk] BlazzedTroll:
I assume you mean for the PC. Yes, I have tried uninstalling and reinstalling both using Microsofts found drivers and directly sent packages from the support team. Updates and 2 different PCs. DevKit installed on the one I originally used to root and a new PC with fresh driver installs.

They wouldn't suggest drivers for the phone, if you know of a way to install new drivers for the phone, please let me know, I'd definitely give that a shot.

Regards
[Magisk] BlazzedTroll:
I should include all troubleshooting I mentioned for those that think they have a solution for the dead USB. My original request was for the OTA flash directions without USB, but I think a lot of people will want to suggest fixes for the phone as I suggested in the PS section.

My apologies on readability, I tried to include HTML formatting. I couldn't figure it out, the options support code highlighting but not the code itself.

Additionally, I tried different USB cables, safe mode, and the factory reset that I could perform.
[Magisk] Didgeridoohan:
[MENTION=9077514]BlazzedTroll[/MENTION]

Summary:

You've uninstalled Magisk, so you don't have root access when booted. TWRP still remains, so you have root access there.

If I read you correctly, what you need to do is to get rid of TWRP. Right?

Download the corresponding factory image, extract recovery.img and flash that by issuing the Install Image option in TWRP.

Just make sure you've done everything you need to before doing this, since you can't get back to a custom recovery if your USB really is busted. Other things to do could include flashing the system.img the same way to revert any possible /system modifications, etc.
[Magisk] BlazzedTroll:
When you say corresponding factory image, does that mean I need the exact one that came on the device? Or just the latest factory image for the right device?

*EDIT* Never mind that, I found the backup folder in the Unified Toolkit which contains a compressed zip just like the ones on the site. I'll use that and transfer to my device over WiFi and use TWRP to flash it and come back with the results.

Thank you for your assistance
[Magisk] BlazzedTroll:
[MENTION=4667597]Didgeridoohan[/MENTION]

I have a backup locally saved that resembles those packages. I was unable to locate a recovery.img in either my saved file or the one on the site. My version that was backed up was 1.171019.011, which is 8.1. I know my phone came originally with 8.0 so I tried looking at one of the those for a recovery.img and still could not locate one.

In the zip there are several files

bootloader-taimen-tmz12a.img

flash-all.bat

flash-all.sh

flash-base.sh

another zip

radio-taimen-g8998-00164-17... .img

inside the second zip, many more .img files looked promising

abl.img

aes.img

android-info.txt

boot.img

cmnlib.img

cmnlib64.img

devcfg.img

dtbo.img

hyp.img

keymaster.img

laf.img

modem.img

pmic.img

rpm.img

system.img

system_other.img

tz.img

vbmeta.img

vendor.img

xbl.img

Same files in all 3 zips I checked.

TWRP only expects recovery.img for "BACKUP EXISTING RECOVERY"

TWRP also has "TWRP FLASH", which I did as one of my troubleshooting steps before and got the Google Pixel 2 XL (taimen) flash. These still keep the TWRP and root, which I believe is to be expected for that flash option.
[Magisk] BlazzedTroll:
DELETED
[Magisk] teddy0209:
You're right, I mean for PC...

You can usually get twrp backups from same device with same rom and flash it on yours via twrp ( ask on your device forum)... You will need system.img, recovery.img, and boot.img... I'm not so sure if you can relock the device without working usb/fastboot...
[Magisk] Didgeridoohan:
[MENTION=9077514]BlazzedTroll[/MENTION]

My apologies... I'm still not used to these damned A/B devices. :laugh:

If I remember correctly, recovery is included in the boot image, so what you need to do is flash the stock boot.img file to slot A. Don't know if this is possible in TWRP.
[Magisk] BlazzedTroll:
I'll give this a shot, I have system.img and boot.img, as I said in reply to Didgeridoohan, I do not have a recovery.img in the files.

Sad news about relocking, but that should be OK.

Thanks for lending some help
[Magisk] BlazzedTroll:
That's alright. I don't know much of anything about them. It's easy enough to follow tutorials and if I had my USB connection I could do as you say pretty quickly. The problem is I don't understand what TWRP even is. There doesn't seem to be an option to flash you own custom img. "TWRP FLASH" only lets you select from the latest versions and downloads the one you select and starts the flash. "BACKUP EXISTING RECOVERY" expects a recovery.img and doesn't let me select anything other than that. I could try renaming system.img to recovery.img, but until I find out what the difference between the images is, I'm not to keen on trying that one. Sounds like a good way to get hosed before I return it. At this time, I would think without having USB access the folks at Google would be happy to have root on the phone. Rather return it working, but rooted, than bricked.:eek:
[Magisk] BlazzedTroll:
So I was trying to follow some other suggestions and it seems like maybe the device is actually not rooted anymore.

There is no SU file located in system/bin or system/xbin.

When I download something like "Root Checker" it gets stuck verifying the root.

I tried to use apps like rashr and flashify to flash a stock recovery and neither app will load properly suggesting no root access.

This means when I ran the uninstalls, everything did uninstall and unroot but the TWRP install must not be very clean (I don't think it's being maintained anymore for most devices). So I need to try and find where this app is located and remove it manually before I run the recovery again. If I solve this I'll post back.
[Magisk] Didgeridoohan:
You don't have root access, since you uninstalled Magisk. TWRP has it's own root, so while booted to recovery you can still do root stuff...

The only way to restore the stock recovery is to flash the boot image to your device.

And TWRP is pretty much the only maintained custom recovery for most devices...

Just a small note: this demonstrates the issues with using toolkits... It's just to click away and you never really learn how things actually works. Can bite you in the bee-hind when things go south.
[Magisk] BlazzedTroll:
At this point I've just ordered the RMA replacement and I'll send it in. Hopefully those at Google are able to verify that the hardware malfunction is entirely unrelated to the root and they still honor the warranty. If the USB hadn't failed, I would easily flash back to stock as you have suggested. It's a fairly trivial action.

I agree somewhat with the idea that toolkits can be problematic in this way. There was quite a bit involved in running through the toolkit, it wasn't that One-Click root/jailbreak type stuff. I issued all of the commands over ADB and was fairly knowledgeable about what actions I was performing. This issue lies in this toolkits maintenance. The latest update to TWRP removed a ton of features and I'm unable to find the other version. Magisk was fully uninstalled as expected. TWRP did not make it clear that the flashed recovery would in fact contain was is essentially an ad for their toolkit. The placeholder app, as they call it, is literally just an ad that pops up when your recover that says "Don't forget to install us!". You can't even remove that file from the recovery partition, you must reflash to remove it. So the problem isn't just that you don't learn how it works, it's that you aren't forced to go through the changes with a fine-toothed comb as you would creating your own recovery. Had I created my own recovery I would have left it stock so that in the event of a failure such as this you are returned to factory stock without any changes except the unlocked bootloader. I guess in the future I'll have to do this myself. I did take the easy way out and just run the defaults from the toolkit in most cases.

Thanks to you and the others who threw in some helpful suggestions.

For anyone stumbling across this in the future, the problem is a 'semi-rooted' recovery can't be flashed without USB transfer capabilities. The solution is to RMA the faulty hardware hopefully. They should be reflashing all phones they get after repair/refurbish anyway.

Best Regards
[Magisk] BitaloBhudey:
For future reference...

Try downloading a stock Fastboot Image for your device then unzip it, collect boot.img, then flash just the stock boot.img from TWRP. Should solve the issue upon the following reboot with no more TWRP or root. If youre on magisk or systemless SuperSU. Not locking the bootloader though lol that's hopeless without usb function unless it's possible to lock bootloader using the terminal command with an WiFi ADB app from another device then follow with "adb reboot bootloader", "fastboot boot TWRP.img", then flash stock boot.img from there. I'm just spitballing the second one lol, but if it'll make it to the TWRP part successfully it should work in theory unless the WiFi ADB connection can't make it past reboot which I've never tried. Should probably get an unlock box like NCK Box Pro or whatever supports your device and you'll always know if the port is ****ed or not and flash back to full locked stock with the box if it isn't. It's what I do now. Handy little ****ers lol.