yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] lwclam:
Same as my previous upload WWE version, but this is CHI version. ;)

Enjoy~

http://rapidshare.com/files/131983144/RUU_Diamond_hTC_Asia_HK_CHT_1.93.832.2.exe

http://www.badongo.com/file/10756068

http://www.sendspace.com/file/gabvfu

http://www.megaupload.com/?d=HDX9LH2H

RUU_Diamond_hTC_Asia_HK_CHT_1.93.832.2.part1.rar

RUU_Diamond_hTC_Asia_HK_CHT_1.93.832.2.part2.rar

RUU_Diamond_hTC_Asia_HK_CHT_1.93.832.2.part3.rar
[Touch Diamond, MDA Compact IV ROM Development] s1rl4ncel0t:
Any changes between them?...

There should be, as this one is version 2 and the HK is version 1...

HastaSSSS :)
[Touch Diamond, MDA Compact IV ROM Development] lwclam:
no difference.

all changes are the same. :o
[Touch Diamond, MDA Compact IV ROM Development] s1rl4ncel0t:
Thanks, m8 :)

HastaSSSS:)
[Touch Diamond, MDA Compact IV ROM Development] terrense:
yohoooo~~ ok, now i'm gonna flash my diamond again - twice in 2 hours =.= that's my record....\\ thanks lwclam! you are great!
[Touch Diamond, MDA Compact IV ROM Development] elvislee58:
any people will cook this CHT ROM??
[Touch Diamond, MDA Compact IV ROM Development] michaelcat:
THANK YOU:)

HTC Page is very slow
[Touch Diamond, MDA Compact IV ROM Development] dtosun:
Anyone do it for Diam200 model. I get Invalid Device ID?
[Touch Diamond, MDA Compact IV ROM Development] siuwy:
which Hard-SPL do I need to flash this rom? ATM I'm using 1.37 but the phone can't be flashed. It stays on 0%.
[Touch Diamond, MDA Compact IV ROM Development] natesiy:
Lifesaver!

Thanks a lot for posting up this ROM.
[Touch Diamond, MDA Compact IV ROM Development] FYfans:
Thank you so much
[Huawei Y5 (2017) Questions & Answers] abdjsr:
Is anyone facing this problem on Huawei Y5 2017 (MYA-U29)?

When I tap 'message' on someone's profile on Facebook, my messenger app opens with a prompt to switch accounts instead of opening the message box. Is there any solution to this?
[Samsung Galaxy Note 10 Questions & Answers] TheGhost1951:
Would it be possible to flash an SM-N970U US model phone snapdragon version with an international, Chinese, or other version firmware to get root and then overlay it with English fonts etc... just looking for a workaround for root?
[Samsung Galaxy Note 10 Questions & Answers] iceepyon:
That may work. But I wouldn't risk it. As some of the modem drivers maybe different
[Samsung Galaxy Note 10 Questions & Answers] Gregbmil1:
Would that really maybe work? I feel like someone would have thought of that already. But man, it's tempting to try.
[Samsung Galaxy Note 10 Questions & Answers] bot42:
Unfortunately the two models do not share the same CPU... So it would absolutely brick your phone.
[Samsung Galaxy Note 10 Questions & Answers] TheGhost1951:
Thanks for the feedback guys....nothing ventured nothing gained
[Samsung Galaxy Note 10 Questions & Answers] ghostwheel:
Every site I checked said the sm-n9700 has the snapdragon 855, which is the same as the sm-970u and u1 have.

https://www.sammobile.com/samsung/galaxy-note-10/specs/
[Samsung Galaxy Note 10 Questions & Answers] bot42:
SM-N970U and U1 have the Qualcomm Snapdragon 855 and SM-N9700 has Exynos 9825.
[Samsung Galaxy Note 10 Questions & Answers] ghostwheel:
It would be nice if you provided a source for your claim, since I did so. For example, you could say: "I own the n9700, and it is exynos", or "I'm there engineer that designed the note 10, and the n9700 is exynos"

Someone who has the n9700 could check with cpu-z and settle this dispute.
[Samsung Galaxy Note 10 Questions & Answers] bot42:
Here you go https://www.techwalls.com/samsung-galaxy-note-10-model-number-sm-n970-differences/
[Samsung Galaxy Note 10 Questions & Answers] ghostwheel:
But I think that site says sm-n9700 is snapdragon.
[Samsung Galaxy Note 10 Questions & Answers] xeu100:
The Hong Kong Note 10 is a Snapdragon, one of the few international variants with bootloader unlock and snapdragon. Not sure if it would work, otherwise people would do it. Good luck if you try, but be careful.
[Samsung Galaxy Note 10 Questions & Answers] mafijas:
I have n9700 and its Snapdragon
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] theonlyrick:
Hi - If I debloat my Fire HD 10, 7th Gen, will it support multiple users/profiles?

Does it effectively become stock Android? What version? 8?

Thanks, Rick
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] AmznUser444 Dev:
This Fire tablet is not supporting multiple users because the Fire OS is useless and have a greater risk to security threats.

You have to use LineageOS:

Android 5.1.1 Lollipop: https://xdaforums.com/hd8-hd10/orig-development/rom-lineage-12-1-t3953677

Upgrade to Android 7.1.2 Nougat: https://xdaforums.com/hd8-hd10/orig-development/rom-lineage-14-1-t3973703

If your Fire tablet isn't rooted. You can unlock and root it using exploit (follow the steps carefully): https://xdaforums.com/hd8-hd10/orig-development/unlock-fire-hd-10-2017-suez-t3913639

There is no Android 8.x Oreo for your Fire HD 10 (suez).
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] theonlyrick:
So do you know if my Fire would then support multiple users, like this: https://www.howtogeek.com/333484/how-to-set-up-multiple-user-profiles-on-android/ ?

Unfortunately that is one thing that I really need on the tablet.

Thank you, Rick
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] scoutdriver73:
It will support multiple users with LineageOS, as @AmznUser444 Dev pointed you toward.
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] theonlyrick:
Cool, thanks. Will get onto it.

Rick
[Samsung Galaxy Tab A series Questions & Answers] CaptainChris2018:
I have installed TWRP and Magisk on my SM-T380. I have files in my internal storage of my SM-T380 just in case I get in a brick that is not fixed by deleting files. The files are RMM Bypass (I have a snapdragon Device but rmm will still brick the device if the domt flash rmm bypass), The custom kernel that is needed to make magisk work, magisk itself, and the Tab A Forced encryption thing so I can get out of magsik bricks for example with factory reseting. But if I factory reset, it will delete these files, and dont have access to a pc at all times. So is there a way to like make sure the files dosent get deleted in case of a factory reset. I have a microSD card and a USB OTG dongle and a flash drive, both can be read by Android, but not by TWRP.
[Samsung Galaxy Tab A series Questions & Answers] Deleted member 10802473:
A factory reset in TWRP does NOT format Internal Storage which is where your files are, it only formats Data, Cache, and Dalvik so, you are fine leaving the files on your Internal Storage as long as you don't format it. Did you try going to mount and select storage then changing it to your MicroSD card or your USB flash drive? If TWRP doesnt recognize them you can always just leave the files on your computer then use ADB to move them to your phone (because TWRP supports ADB).
[Google Pixel 4 XL Guides, News, & Discussion] i5lee8bit:
[UPDATE/KEEP ROOT GUIDE] Jun 2020 (QQ3A.200605.001) "CORAL" Magisk-Patched Boot Image

IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!!

Hey guys, yup, I'm still furloughed... ;_;

So anyway, here are the factory and Magisk Patched (v.24 is still the latest as of typing this) boot images for the June 2020 (QQ3A.200605.001) update.

ALL FILES BELOW ARE FOR JUNE 2020 QQ3A.200605.001!

Magisk v20.4 Patched Boot Image: https://www.androidfilehost.com/?fid=4349826312261824138

Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=4349826312261824136

Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=4349826312261824137

THESE FILES ARE FOR "10.0.0 (QQ3A.200605.001, Jun 2020)" ONLY! PLEASE ONLY FLASH IF YOU KNOW WHAT YOU'RE DOING!

Everything seems to work fine so far. Magisk v.24 and EdXposed 5.0.0 (4548 YAHFA). SafetyNet Passing for now... Kirisakura 4.7.5 (just released today!) works great too!

If these files and/or guides are helpful, please drop a thanks and let me know. Thanks! =)
[Google Pixel 4 XL Guides, News, & Discussion] i5lee8bit:
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS

(using a PC - a very intuitive, effective, and relatively safe method).

** You can only follow this guide exactly if coming

EXACTLY from build qq2a.200501.001.b2, May 2020

. But the general idea is the same for other builds, you just need the correct files for your device.

coral-qq2a.200501.001.b2-factory-dtbo.img: https://www.androidfilehost.com/?fid=4349826312261824163

coral-qq2a.200501.001.b2-factory-boot.img: https://www.androidfilehost.com/?fid=4349826312261796399

June 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-qq3a.200605.001-3b5bb1bd.zip

I DID NOT BOOT BACK INTO O/S UNTIL ALL STEPS WERE COMPLETED - I DID THIS TO ENSURE EVERYTHING WOULD BOOT BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY

1. boot into bootloader

----------------

** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images

2. fastboot flash boot coral-qq2a.200501.001.b2-factory-boot.img

3. fastboot flash dtbo coral-qq2a.200501.001.b2-factory-dtbo.img

......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.

-----------------

4. use volume keys to change selection to boot to Recovery Mode

......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten

5. choose option "Apply update from ADB"

6. adb sideload coral-ota-qq3a.200605.001-3b5bb1bd.zip

7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)

8. fastboot flash boot coral-qq3a.200605.001-magisk_patched-20.4.img

9. done, start the phone

(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it. I've only personally tested with Kirisakura though.)

This was a 100% seamless update that required no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.

...More details and guide / cleanups to come. I'm home alone today and taking care of our 5 month old, and he just woke up!!!
[Google Pixel 4 XL Guides, News, & Discussion] i5lee8bit:
Issues after updating?

If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:

1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.

2. I would recommend checking Tulsadiver's thread: https://xdaforums.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557

Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.

- See this post (or thread) for more tips / context / an example: https://xdaforums.com/showpost.php?p=82509691&postcount=16
[Google Pixel 4 XL Guides, News, & Discussion] Shayded:
Doesn't work. Even recreating all the patched img files on my own, after a full factory reset, results in a boot to black screen with only the power menu available.

No clue why, unrooted with stock boot.img works fine

edit: should note that this is even without any modules
[Google Pixel 4 XL Guides, News, & Discussion] i5lee8bit:
Weird that it wouldn't work even after a full factory reset. Unfortunately I don't have a means of testing that. I edited my 3rd post with some troubleshooting instructions, sort of copied and pasted from my previous thread. You said you already factory resetted and it still doesn't work, but I would have otherwise recommended checking Tulsadiver's thread (he has an updated pre-made Magisk Core-Only mode boot image on his thread) in order to find and disable the bad module. Again, since you already tried factory reset, that wouldn't really apply and that's very strange.

I attached screenshots to the OP that shows it working... Sorry I can't help much more. The baby needs to be fed now...!! Typed all this while warming up the milk bottle... :eek:
[Google Pixel 4 XL Guides, News, & Discussion] Shayded:
yeah it's very odd. The second I try to boot even a clean factory image with a patched boot.img it just gives the black screen.
[Google Pixel 4 XL Guides, News, & Discussion] baleskoil:
You guys still have motion sense ?

i can't make it work with magisk....

i tryed factory reset, it worked but once magisk is installed no more motion sense for me..( safetynet is ok...just in case )

any help please ?

i tryed a few things with props edit but no luck
[Google Pixel 4 XL Guides, News, & Discussion] lightweaponx:
Used this guide to come from the April update, everything seems to be working without issue.
[Google Pixel 4 XL Guides, News, & Discussion] xxxtncxxx:
****EDIT

So was bored and wanted to do some testing and it seems to be magisk modules that are most likely causing the majority of the issues

I flashed via fastboot then booted from the 6-2-20 image of this post and disabled all of the modules except the riru core and edxposed

Then rebooted to fastboot and flashed the patched boot image from OP works like a charm for anyone having issues.

EDIT***
[Google Pixel 4 XL Guides, News, & Discussion] tysj:
Really strange outcome after doing this method for this month's update.

I'm on the smaller Pixel 4 but having been using your threads as a cheat sheet for a while. After the update was installed and magisk-patched boot images was flashed, it booted but I couldn't pull down my notification bar the second time to get into settings, couldn't enable mobile data, couldn't access storage from PC (notification to select USB options wasn't there), no notifications where shown but sounds were still coming in, no developer options, and a ton of other weird stuff. Overall, it seemed like it somehow only installed half the system since it felt like it was missing a lot of options and features. Tried reflashing the full factory image which did not seem to help. Only was able to get it functioning again through a clean install. No clue as to what could've happened this time around.
[Google Pixel 4 XL Guides, News, & Discussion] onlyguynamedniles:
Copy and pasted method, just as you did in previous month. Your EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS is flawless for me.
[Google Pixel 4 XL Guides, News, & Discussion] i5lee8bit:
That's weird. I just tested it and it worked fine. I only have it enabled for alarms, and that's all I tested for though.

edit: I just tested on my wife's phone which I just updated (it's a Pixel 4, non-XL) and she uses the pause / skip motion sense, and it all works fine after updating... sorry man.

I'm attaching a list of all of my Magisk and EdXposed modules being used to this post. So far, I haven't had any issues whatsoever. Not sure if it'll be helpful, but seems ppl are having scattered issues with this update. :confused: Tbh, I don't have a huge number of modules, at least I think relatively.

Oh no, please don't tell me you flashed any of the files from this thread? They're very different phones in that sense and you need to use the correct files. We just put the little guy down to sleep so I'll write up that thread really quick on the P4 forums. Flashing a full factory image is pretty much the same as a clean install though? Are you sure you were using the correct files? Anyway, the post for P4 will be up in just a few min. (I'm actually updating my wife's phone as I type this, lol)

edit: here ya go: https://xdaforums.com/pixel-4/how-to/update-root-guide-jun-2020-qq3a-200605-t4109307

Thanks for the feedback, you're welcome!
[Google Pixel 4 XL Guides, News, & Discussion] tysj:
No worries, mate. I used my own files. Downloaded many times just to make sure I had the right package. Still not really sure what happened as flashing the factory images should have fixed whatever was going on. Not an ideal situation, but works out since I had to do a factory reset to fix a separate backup issue anyway.
[Google Pixel 4 XL Guides, News, & Discussion] i5lee8bit:
Lol, I edited the post with the link to the other thread right after you responded I guess. Anyway, yeah, that's weird. Could be the cable, corrupt files, or a big number of things. Glad you got it sorted out though! :good:
[Google Pixel 4 XL Guides, News, & Discussion] sphinxy:
Thanks for this. I've been following your guide the last few months since its brainless work for me. I checked for your thread yesterday but it wasn't up yet so didn't bother updating. I will tonight but thought I'd say thank you for the guide in advanced - its much appreciated :)
[Google Pixel 4 XL Guides, News, & Discussion] baleskoil:
[MENTION=321827]i5lee8bit[/MENTION]

Thx for your answer i ll try a bit more on my own
[Google Pixel 4 XL Guides, News, & Discussion] i5lee8bit:
Hey what modules are you using? Try booting up in Magisk Core Only Mode (or just try disabling all modules and reboot). You can easily boot in core mode if you're not bootlooping by just going to Magisk Manager settings and toggling core only mode. The only thing I could think of is a module not playing nicely, especially if it works when stock. Either that, or maybe there's something you need to Magisk Hide. The only things I have hidden are the stuff recommended in eg1122's thread (https://xdaforums.com/pixel-4-xl/how-to/xposed-discussion-thread-t3992607) plus a few extra things like Netflix and some banking apps. But seeing as how it works when stock for you, it's definitely not hardware related so I would suspect another tweak messing with it. Good luck!

Edit/PS: I got curious this morning and tried on my own phone, and all motion sense functions still work, btw
[Google Pixel 4 XL Guides, News, & Discussion] baleskoil:
ouch ...dumb mistake.... I was so focused on passing safetynet i forgot about magisk hide ^^

thx for your help ^^
[Google Pixel 4 XL Guides, News, & Discussion] knudsen83:
"** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images"

Does this mean I only need to flash the boot.img and not the dtbo.img if I'm using the stock kernel?
[Google Pixel 4 XL Guides, News, & Discussion] i5lee8bit:
Correct, I'm guessing you already got it sorted out by now but in case you're wonderinf it wouldn't hurt to flash stock dtbo over stock dtbo either.
[Google Pixel 4 XL Guides, News, & Discussion] dadoc04:
No magisk modules installed here and your guide worked perfectly. Thanks for the write up.

Looking forward to July. ??
[Google Pixel 4 XL Guides, News, & Discussion] MohamedRaafat:
Hi,

I haven't updated since January so does anyone know how to proceed while preserving root ?
[Google Pixel 4 XL Guides, News, & Discussion] farfegnugen:
Do you know if Google FI ESIM will work after we got through this process?
[Google Pixel 4 XL Guides, News, & Discussion] mydjtl:
Will this work coming from pixel 4xl QQ2A.200305.003? Last update was March 2020. I still don't see an option to update. If not anyone have a link to the files I would need? Thanks.
[Google Pixel 4 XL Guides, News, & Discussion] i5lee8bit:
If you're rooted, you won't get OTA updates the normal way. OTA's rely on stock recovery anyway, and when you flash Magisk, you lose that stock recovery, so if anything it's a good thing they prevent OTA's from working when rooted.

Anyway, you can try following this guide: https://xdaforums.com/pixel-4-xl/how-to/guide-update-retain-root-t4003839

Or, you can download the full June 2020 factory image and edit the flash-all.bat file and remove the "-w" flag from the line

fastboot -w update image-coral-qq3a.200605.001.zip

which is what will wipe your phone otherwise. Just note that I haven't needed or tried using this method yet (I only got the phone in March), but this is a common known method of flashing full factory image among Pixel phones. If you choose to go this route, IIRC it will automatically boot into O/S and then you can reboot into bootloader and flash the June 2020 Magisk Patched image to re-root. (thanks to user [MENTION=6839136]aramisathei[/MENTION] on this post). Either disable all Magisk modules before trying anything, or just go full steam ahead and if you bootloop, see post #3 of this thread.

If you're paranoid and want to be super safe, you could also go incrementally by following these posts, one by one:

March -> April: https://xdaforums.com/pixel-4-xl/how-to/april-2020-boot-images-coral-qq2a-t4078579/

April -> May: https://xdaforums.com/pixel-4-xl/how-to/2020-qq2a-200501-001-b2-coral-magisk-t4094277

May -> June: this thread

(although it does seem the full factory image method should be fine, quicker, and easier at this point - JUST MAKE SURE TO REMOVE THE -w FLAG!!)

edit: download the full factory image zip from here, AND READ THE INFO GOOGLE GIVES. You'll need the SDK tools (fastboot, adb, etc) and they'll need to be properly added to your PATH environment variable to run properly: https://developers.google.com/android/images

Sorry, busy with school and stuff. I didn't own the phone until March, so your best bet is to go with the full factory image flash, as mentioned in the reply above. Again, make sure you remove the -w flag.

I would LOOOOVE my new carrier (Xfinity Mobile) to support eSIM, but they don't yet. So I can't say for sure, but there's no reason it shouldn't. There's really nothing different about this than taking an OTA normally. You're just basically reverting to stock and pushing the OTA manually, then rerooting before booting back up. Nothing would actually wipe the eSIM data, unless there was an inherent bug in this month's update. This month's update is the same across all carriers except Telstra, so you should be fine.
[Google Pixel 4 XL Guides, News, & Discussion] jefrymm:
Hi, are you guys still passing safetynet?
[Google Pixel 4 XL Guides, News, & Discussion] mjoach:
Well, that's weird, I just rooted Pixel 4XL and can't pass ctsProfile check, despite Magisk Core mode only. And I had GPay working fine on my Pixel 4 yesterday.
[Google Pixel 4 XL Guides, News, & Discussion] nithinmanne:
I just noticed, and I'm facing the same issue as well, enabling core only mode it's not helping
[Google Pixel 4 XL Guides, News, & Discussion] tysj:
Mine failed for the first few days since the patch. Then started suddenly passing for 2-3 days. Now it's failing again. No changes to any modules, MagiskHide, apps. Not sure what Google's doing in the background to trigger it so inconsistently.
[Google Pixel 4 XL Guides, News, & Discussion] mjoach:
Thanks, so it's not just my phone then. I did still try clean flash of May update and had the same result. Perhaps they are indeed closing this SafetyNet hole as was announced a while back.
[Google Pixel 4 XL Guides, News, & Discussion] RashidAlawadi:
Tried this method. Worked flawlessly! Retained my root and didn't have to disable and renable models (what a hassle).

Many thanks... Next step should be to update without needing a PC lol.
[Google Pixel 4 XL Guides, News, & Discussion] KACE321:
Just rooted my phone, went fine but not passing ctsProfile check either??