yashsingh1/xdaforums huggingface dataset:
[Asus ZenWatch 3] TheSura:
Hello, as I wrote on title, I can't go on with wear os tutorial. I'm going to explain my situation. I sent the watch to Asus for a warranty repair and when it comes back, it was on the stock wear os 2.0. I updated all apps through play store after setting up the watch and a wear os update was available (it was even before sending it to Asus and I used the update with no problems). A notification shows saying I should tap to update the clock. I did it and after the reboot, if I finish the Wear OS tutorial the clock seems working, but if I try to open the app wheel, it closes showing me again the tutorial. I tried to factory reset 3 or 4 times, but with no luck. What should I do?
[Asus ZenWatch 3] Misterjunky:
Zenwatch 3 Update

[MENTION=6338121]TheSura[/MENTION]

#1: Uninstall the Wear OS app from your phone.

#2: Start all over again and do a system reset, the watch will tell you to

go to the plays store and install the Wear OS app using your phone when

your watch prompts you to do so and continue the setup on your watch.

Good luck, have a great day!
[Asus ZenWatch 3] TheSura:
Thanks, it works!
[HTC Tornado] elsmacko:
Trying to CID and SIM unlock a "Sample SDA" not for sale not FCC auth. phone

Wow I bought this SDA off of Craigslist. When I booted it I noticed it said not for resale. Well I figured it was just some custom ROM the guy put on it, so I didn't even ask about it.

A month later I decide to start playing with it; wanted to CID, SIM unlock and upgrade it to WM6 like I did once before with one of these. BUt the App unlock tool and all the other tools do not seem to work on this one like on the other one.

When you take the back off the phone, under the battery where the Memory Card slot is, it says "Not FCC authorized. Sample, not for sale"

Also I noticed it is WM5, and the music buttons and t-zones button don't do anything when pressed.

Otherwise, it is a fine phone, everything else seems normal. Wifi works on it..

Oh this is what is has on it:

ipl 0.34

sil 0.34.0000

gsm 0.21.0.0

os 10.10.0
[HTC Tornado] elsmacko:
Here are pics ..
[Shield Android TV General] nadia p.:
I own a Shield TV 2017 (16GB) remote only (P2894, Darcy) which currently has Nvidia 7.1.0 developer OS, unlocked bootloader and the boot.img was patched using Magisk Manager 6.2.1/Magisk 18.0.

It has been noted patching boot.img using Magisk Manager 6.2.1/Magisk 18.0 only performs a partial root and that something else in the "DTB" information needs to be modified in order to allow full root access to read/write.

I'm new to this so please forgive me if I ask something obvious.

I've connected my Shield TV to my PC via ADB and executed

fastboot oem dtbname

...

(bootloader) tegra210-darcy-p2894-0050-a08-00.dtb

OKAY [ -0.000s]

finished. total time: -0.000s

I don't know how to extract the *.dtb information or know what's required to patch it.

The command to flash it is

fastboot flash DTB tegra210-darcy-p2894-0050-a08-00.dtb

Can someone else help provide what's required to extract, modify, etc... in order to flash and gain full root access?
[Shield Android TV General] nadia p.:
It's my understanding that this is required to allow TWRP 3.2.3.0 foster to work properly. If not can someone please clarify this for us beginner users?

NOTE: The patched DTB file above is not for the same version as the one I have.
[Shield Android TV General] nadia p.:
Noting this too...
[Shield Android TV General] Downunder35m:
Thanks for the confirmation!

The fastboot -w should only be required if the forced cyption was already in use on the device.

But if I am not mistaken than on the developer version only the data prtition is encrypted, which is no issue.
[Shield Android TV General] Mogster2K:
AFAIK the patched DTB is for booting custom ROMs. More work still needs to be done to get TWRP working again.

---------- Post added at 09:45 PM ---------- Previous post was at 09:42 PM ----------

Is root not working for you now? If you have never upgraded the stock ROM past 7.1, then it should work without needing a patched DTB.
[Shield Android TV General] nadia p.:
I'm quite the beginner at all of this Android stuff, although I have experience with several other software related things. I'm currently stuck trying to install TWRP 3.2.3.0 foster on my Shield TV 2017 (16GB, remote only + usb keyboard + usb mouse). I haven't been able to backup the entire device yet to use that to see if I can restore everything back to that exact state yet. I don't know how to tell how "rooted" I really am yet.

Steel01 says TWRP 3.2.3.0 fosters is working on Darcy. I'm still trying to confirm this. My main reason for TWRP is to complete a full backup which I can later restore back to that exact state if/when something should happen if accidentally updated and it breaks everything again.
[Shield Android TV General] Mogster2K:
TWRP works for darcy IF AND ONLY IF it has never been upgraded to stock rom 7.2 or higher. 7.2 majorly broke a lot of things, including TWRP, which is why this thread has so much traffic lately and I why asked whether you had upgraded past 7.1. Please confirm whether you have or not.
[Shield Android TV General] nadia p.:
Hello Mogster2K, Originally without any modifications the factory installed Nvidia software upgraded itself through on-line updates to 7.2.1 which then broke other 3rd party Apps for me. I then attempted to downgrade to 6.3.0 developer OS, however because it was my first time unlocking the bootloader it wiped everything so once it 6.3.0 was successfully flashed, I had to connect to the internet, sign-in again to Google Play and meanwhile it forced itself to update back to 7.2.1 again. Later by following ACiDxCHRiST's guide HERE, I was able to successfully downgrade to 7.1.0 developer by patching the 7.1.0 boot.img then manually flashed each line item in flash-all.bat.

Later I tried to install TWRP 3.2.3.0 so I could backup the device, however I've not been successful with that since I have a Shield TV 2017 (16GB) remote only model so I must use a USB keyboard and USB mouse to do it. I was reading these other posts here about what the issues might be preventing me from installing TWRP and using it to back everything up. Does this help answer your question?

So I'm currently on 7.1.0 developer OS, patched boot.img using Magisk Manager 6.2.1/Magisk 18.0. So far the Apps that were broken by 7.2.0 "factory" are again working fine in 7.1.0. I don't game, I mainly watch movies and tv series with my device so I don't have many requirements other than I'd like to back everything up so in case it accidentally gets updated somehow I can revert back to a working archive and continue from there.
[Shield Android TV General] nadia p.:
I realized I wasn't sure if by upgrading the "stock" rom this included updating the device to 7.2.0 (or later) via on-line updates or just flashing the rom itself to 7.2.0 (or later).
[Shield Android TV General] nadia p.:
Does anyone know how to test for certain criteria to help determine if:

A) anything needs to be modified in regards to DTB

B) if their device has been updated in such a way that it currently breaks TWRP (or other things) in such a way there is no fix as of today

This should prove quite useful to help us understand if/anything needs to be done or where the device resides at any given moment.
[Shield Android TV General] Mogster2K:
Both. Anyway, I did not realize at the time that darcy could be fully downgraded to 7.1, sorry. It doesn't work on my foster, so I can't use TWRP at all. Also, to the best of my knowledge, TWRP requires at least a USB mouse to function regardless of which ShieldTV model you have. And the modified DTB is just for booting modified images on darcy 7.2+. You're fine without it on 7.1.
[Shield Android TV General] nadia p.:
Stuck... post backup TWRP 3.2.3.0, now corrupt w/black screen

I'm not sure if this had anything to do with it but I'm suck at a black screen after backing up TWRP.

More information can be found at this POST.
[Shield Android TV General] Mogster2K:
7.2 sources still have not been released yet, anyway. I found a reference to a new branch "rel-30-r2-partner-o" but that's all.
[Shield Android TV General] nadia p.:
First of all thank you so much for putting all this in layman's terms so someone like me can understand it. Total respect!

Since my device is useless if there is some way I can offer you remote access to a PC, the device and anything else I can assist you with please don't hesitate to let me know.

If you need me to send you my device with remote that you can use to complete these things and get everyone unstuck from this dreadful situation I'm all for that too.

I wish there were a means, like with computers, that we can purchase a band new device, fully back it up before even connecting it to the internet and being forced to sign-in to Google Play before we even have access to the device. We'd also need a way to wipe, format and reinstall this backup without any issues. Is this too much to ask for in an Android world?

EDIT: I have time, access to certain hardware PCs, Macs and Linux, and have some basic skills with computers, phones, etc... If I can assist you or anyone with certain time consuming things let me know. The only Android device I currently own now is the Shield TV.
[Shield Android TV General] Adromir:
Would it Work to just flash the system/vendor files without updating the Bootloader?
[Shield Android TV General] Mogster2K:
Sorry, I've lost track of your particular situation. Are you unable to reflash Stock 7.2 or 7.2.1? I realize it's hardly ideal, but it would at least make the ShieldTV usable.
[Shield Android TV General] whiteak:
From what I understand the dtb file is in the blob file, so simply flashing back a blob file would put back the stock dtb file. The only issue with flashing blob files is if you tried flashing back a Nougat blob file if you were already on a Oreo Firmware, as long as you only try flashing a Oreo Firmware blob file you shouldn't run into any problems, I would have to go back and have a read, but I'm sure I read that you may have done this and if you had tried to flash a Nougat blob file when you were already on an Oreo Firmware, that could be where you first ran into problems. But I'm not too sure if you are asking where to get the modified dtb file or not, I'm not sure if you have already flashed the modified dtb file or you are asking where to get the modified dtb file. I checked the dtb version on my 2017 Darcy Shield and it came up with a different number version than yours, mine came back with: tegra210-darcy-p2894-0050-a04-00.dtb whereas you have posted you have the tegra210-darcy-p2894-0050-a08-00.dtb. I done the check on what version of the dtb I had before and after using the modified dtb and also after when I flashed back a Oreo blob file and back to a Full Stock Oreo firmware and they both came back as the a04 version.

I would try and flash back to the latest Stock 7.2.1 image released on Nvidia's site: https://developer.nvidia.com/gameworksdownload

If successful then I would look at downgrading back to 7.1 Stock Firmware. I'm still a bit confused if this is what you have done or you only have a black screen when trying to boot to system?

The Fifth and Sixth version on the downloads screen are the versions for the 2017 model, one being the Developer version and the one below being the Stock version of 7.2.1. I would try flashing the Stock Version first and see if that gets you back up and running again. If it does, I would again check the dtb version as I am sure the 2017 Darcy model should be showing the a04 version and not a08.

---------- Post added at 01:06 PM ---------- Previous post was at 12:55 PM ----------

I just had a quick read back, you have said you have flashed the Developer image and then also flashed a patched boot.img. I have not done this combo as it is not the way I would do things. I would use just the Stock Firmware and not the Developer image with a patched boot.img. I do not know 100% for sure if the only difference between the Developer version and the stock version is the boot.img but if you are going to use a patched boot.img anyway, this is the reason why I say there is no need to flash the Developer version as you are going to use a Patched boot.img anyway, I would just stick with the Stock version.
[Shield Android TV General] nadia p.:
Hello Mogster2K, from the factory install which was updated OTA to 7.2.1 I was able to 1st unlock the bootloader and flash 6.3.0 developer OS to my device successfully, or so I thought so. What I mean by this is based on what Downunder35m said once the device has been updated to 7.2.0 regardless of how when flashing previous versions of OS (developer or recovery) it may not revert the bootloader to 6.3.0. This we still have to see and test to confirm, unfortunately he nor I have any way to test things right now. That being said because I unlocked the bootloader (forced wipe) then flashed 6.3.0 that all went fine accept when booting to the Nvidia home screen it required me to connect to the internet and then sign-in to Google Play. Doing this the OS forces it to update itself again back to 7.2.1 (at that time).

So now that the previous steps were useless I then discovered ACiDxCHRiST's guide HERE and followed that since the bootloader was already unlocked I could modify the boot.img form 7.1.0 then flash that. Well two things happened, it worked perfectly however it's most likely Magisk didn't truly root the device 100%, it only rooted it partially. So now the device worked fine on 7.1.0 and everything was going well UNTIL I decided to install TWRP and backup my device. Doing so totally screwed it, now I have a black screen.... Read THIS.

So one of the reasons I started this thread was to find out more about DTB and how do we start to first test a devices current state, perhaps patch it to what we need to recover from the 7.2.0 changes and restrictions. The benefit of all of this is we should be able, with expertise, be able to climb our way out of this hole and get back to a working device.
[Shield Android TV General] nadia p.:
In short the 7.2.1 update broke the factory install by affecting other apps I use and that were working perfectly fine in 7.1.0 before the update occurred. This was the sole reason I attempted to revert back to a previous OS.

Just flashing 6.3.0 didn't work as it updated itself back to 7.2.1 forcibly. I then had to work around that issue and the only way I found was to download 7.1.0, patch it's boot.img file, flash 7.1.0 developer to keep the bootloader uplocked so it wouldn't wipe the system whereby deleting the user info, apps, etc..., make sense? The only issue is that Magisk didn't fully root the device properly and with the new OS verification added to 7.2.0 it created all sorts of other protections where we're not able to fully wipe everything and flash back normally. These protections kick in and prevent it. This is why we're trying to see how to undo the protection settings so we can actually do what we need to do. DTB is part of this.
[Xiaomi Mi Mix 3 Questions & Answers] Mhappah:
I get this error in the TWRP, both wiping the device and installing the Rom. I don't really know how to continue the process, I tried everything but I'm always getting stuck here.

[IMG="This is the error"]https://imgur.com/a/WkWJgmg[/IMG]
[Moto G4 Play Guides, News, & Discussion] RedCrane3:
Have you had VoLTE working? I can't remember if I had it working a couple of years ago when I got this phone. Moved the SIM from a Nokia 929, so already had a good SIM. But I've never had the original firmware back on the device - always some ROM or other.
[Moto G4 Play Guides, News, & Discussion] jasonmerc:
That's something I shouldve mentioned, I did not get VoLTE working on this regardless of stock/custom firmware. So perhaps it's not FULLY working, but still much better than others I've seen online that say their G4 Play flat out doesn't work at all

Just updated the OP with that bit of info too
[Moto G4 Play Guides, News, & Discussion] RedCrane3:
Interesting, ok. I guessed probably not... but you never know :)

I bought my 1607 from motorola, havan't had any issues with it on Verizon.

Thanks for the info!
[Moto G4 Play Guides, News, & Discussion] jasonmerc:
Funny thing is the G4 Play actually shows up as "not compatible" on Verizon's own IMEI checking tool. So if you go by what Verizon themselves say you're SOL. This strikes me as weird because Verizon themselves once sold their own G4 Play which is basically the same thing as the 1607 but minus an unlockable bootloader. According to the rep it has to do with Verizon "changing/upgrading their network" which for some apparent reason supposedly makes older phones like this mysteriously not work anymore. Regardless, the only reason I could even attempt at getting it to work was because I proved to the rep that Motorola themselves said this'll work with Verizon (which isn't simple to do since the G4 Play is no longer listed on their site) and I basically told the dude "Motorola says it works and I'm not gonna buy a new phone so do whatever you can to make it work" (and believe me, he sure as hell tried to sell me a new expensive phone during the process)

I figure this guide can also serve as a signal to onlookers that not only will this work with Verizon, it'll work even though they themselves want to assure you it wont
[Moto G4 Play Guides, News, & Discussion] mmortal03:
The real question is, has anyone ever figured out a way to get this phone to do VoLTE on Verizon/MVNOs? I'm testing it on Page Plus using AICP 16.1, and VoLTE is provisioned, but I only get 1xRTT for voice.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] alissonlauffer:
This ROM is awesome, runs smoothly, with awesome customizations and a good battery.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Jorge Lucas:
Update Soon
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] 50percentsuccessrate:
Hi, I'm having an issue with the front Flash functionality; I've tried gcam and moto camera, but neither work. Other than that, this rom is really good!
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] tedyanggara:
whats the difference between 6.0 and 6.1 ??
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] mad_fitter:
Changelog is here:

https://blog.aospextended.com/AospExtended-v6.1-Changelog/
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] tedyanggara:
i mean major difference, because i dont see any significant difference
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] 50percentsuccessrate:
Quite a few of the things there are significant depending on your usage of android. Many of these features are things I regularly use, so if you look through the list and search up what was done, it warrants a change from 6.0→6.1 with the effort it took to add features.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] mad_fitter:
Yessir. Not to mention a lot of changes are "under the hood" so to speak, so while you may not see the changes, you can certainly feel them. Bug squashes and improved performance, battery life, etc...
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] tedyanggara:
Currently at this rom right now, what version of gcam that this rom supported?? what version is the best one ?
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] luisgamma13:
Hello , is fingerprint working good, i mean unlock and gestures? Thanks
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] 50percentsuccessrate:
Yes, both unlock and gestures work perfectly. I've been using this rom for a week with no issues whatsoever.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] fgugg:
Last rom update installed yesterday.

No issues, no bugs.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Dhan...:
anyone tested auto call recording working on dailer ??
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] triadd:
Settings/extensions/statusbar/statusbar items gives me a system UI force close. Anyone else experiencing this? Clean install, magisk root with TWRP treble r22. No logs at this time. I can try to capture later today.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] triadd:
Logs attached for the aforementioned force close.

Moto Sanders xt1806

Magisk root

No gapps
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] bruno2676:
link is dead
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] triadd:
Official build is up on the website. FYI.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] prupet:
View attachment 4689225
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] rom3osv8:
This ROM have bugs yet, update pls
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] triadd:
Official build is on the website. Not the original download link. I'm not really familiar with the rules on posting external links, but there's a link to the AospExtended website in the OP. Click the download icon in the top right of the homepage, then the menu icon in the top left of the downloads page, scroll down to Motorola. The official build fixed the only issue I experienced, which I posted about a few days ago. Battery life seems to be improved on this build as well.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] prupet:
Very nice and stable, thanks! Just one issue, I have downloaded ROM from your site, but in system software update information in phone I have still notice about updating to the new version which is already installed. But never mind the feature "automatic update" is cool!
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] g0ms!:
Camera not working on Moto G5s Plus

I installed the rom on my Moto G5s Plus, and found that it is not supporting Google Camera, crashing again and again, plus depth effect is missing from Moto Cam2. Can you fix this. ?
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] rom3osv8:
These problems were the ones I found on my device with this ROM (xt1800): -update notice being in the last build downloaded from the official page. -in some beginnings and restarts is stuck in the message starting Android forcing me to restart forcefully. -sometimes also when start or restart is stuck as in a black screen. -a small error would be that when I return from a section of configuration of the interface is stuck forcing me to press home to solve the small problem of ui.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] prupet:
I tried several ROMs with Android 9 on Moto G5s Plus, and everywhere was the problem with the Moto Cam2 (especially with Black and White Mode) and with FM radio app. I think we have to wait until original ROM for f.e. Moto G6 will be realized and then developers can check it easily. But this ROM is very good!:good:
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] 50percentsuccessrate:
Download link seems to be gone, could you reup please?
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] prupet:
Try to download from the developer's homepage: https://downloads.aospextended.com/sanders
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] rom3osv8:
What happen with messages app.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] g0ms!:
Official or Unofficial Rom!!!!

Is this really unofficial, or you just messing up with our heads:eek: by using different headings on website and XDA forum.

Well for now, before reinstalling it, I wanted to know if Banking apps are working, and if camera issue can be fixed as Moto Cam2 and google camera both were not working when I installed it last week.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] prupet:
Here you can find some screenshots of my ROM modification

https://ibb.co/HxwJNQH

https://ibb.co/tK29HXS

https://ibb.co/QPTHyxr

https://ibb.co/GFcss9n

https://ibb.co/HpmzwSh
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] rom3osv8:
Update soon?
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] omegaorgun:
My only complaint is eBay notification text is too light to read. It is the same on crdroid.

Otherwise great ROM.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] rom3osv8:
I need to know if this ROM will have updates soon please!
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] fgugg:
new update

just downloaded

https://downloads.aospextended.com/sanders