yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] TraderJack:
Thanks. I just want to confirm what you think about upgrading to newer version that have been patched.

As I mention, I am on 636558520, but the newest appears to be 636559820.

As some users are mentioning above 9820 looks like the patched the exploit. However, I am currently unlocked and rooted on 8520.

If I were to flash 9820 from twrp, would this work? Or would I be unable to root on 9820 do you think?

I'd like to move to Lineage, but not until they fix the wired headphone issue, so in the meantime I'd like the latest security updates and would prefer to move to 9820, but not if I can't root.

Also - to flash in twrp I simply rename the .bin to .zip and flash from SD?

thanks so much.
[Fire HD 8 and HD 10 Original Android Development] TraderJack:
Anyone know if it is possible to get this device certified in the Google Play store?

Whenever I try to download the SafetyNet code for the Magisk check it is giving me "SafetyNet API error"

Ideas?
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Updating from TWRP should be safe, the only difference between the two build likely is the patch for mtk-su.

That doesn't affect using Magisk.
[Fire HD 8 and HD 10 Original Android Development] koop1955:
Yes. Also running Xposed, if anyone cares.
[Fire HD 8 and HD 10 Original Android Development] TraderJack:
Ok, sorry I'm just trying to be super clear because I really don't have to want to crack my case.

[MENTION=8132642]diplomatic[/MENTION] replied in the rapid temporary root thread:

But I'm not sure if it was clear to him I was talking about a device unlocked with your procedure running twrp.

So the mtk-su patch allows your scripts to unlock the bootloader/install twrp. But, once TWRP is installed, then installing any ROM should be safe from within it? And, 9820 patches the exploit that allows mtk-su to be run, but since twrp is already installed, Magisk should still be able to exploit it.

Does this sound correct?

thanks again for the clarity.
[Fire HD 8 and HD 10 Original Android Development] Korin67:
As an unfortunate owner of HD8 7th (when I got it the version is already 9820), I really understand what you are saying. More precisely (I believe), mtk-su is not a patch but it is an independent program that works inside HD8 without root privilege that gives temporal root privilege, a magic program. Unfortunately, patch 9820 (and later as well?) prevents mtk-su from working. Without mtk-su, we cannot unlock the tablet, install the TWRP. Only way so far doing unlock, install TWRP is the HW method reported very clearly. Once TWRP is in your tablet no need to use mtk-su. If you need root privilege, you can install Magisk from TWRP.

Since I just got HD8, I am not brave enough to step into HW method. Maybe in Christmas. LoL
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
You can test the brick-douglas.zip I just added to the OP.

It will brick the preloader and let you continue using bootrom-step.sh without opening the device.
[Fire HD 8 and HD 10 Original Android Development] koop1955:
[MENTION=7104332]k4y0z[/MENTION], you are remarkable. In the best way!
[Fire HD 8 and HD 10 Original Android Development] klister:
Hi guys, unfortunately I had let my tablet update to the 636559820 build prior to knowing the bootloader for Douglas had been unlocked.

I followed Vendo's post for shorting TP28 (which is how I rooted prior to there being the software root using MTK-SU) but I can't seem to get past the first script of bootrom-step.sh . I'm using VMWare/Ubuntu and have tried setting the USB to v1.1, v2, and v3 and all are giving me the following output... ModemManager is disabled.

kelly@KellysVM:~/Downloads/amonet-douglas-v1.1/amonet$ sudo ./bootrom-step.sh

[2019-09-22 17:35:30.079345] Waiting for bootrom

[2019-09-22 17:36:47.436261] Found port = /dev/ttyACM0

[2019-09-22 17:36:47.460840] Handshake

* * * If you have a short attached, remove it now * * *

* * * Press Enter to continue * * *

b''

b'\x00\x01'

Traceback (most recent call last):

File "main.py", line 240, in <module>

main()

File "main.py", line 122, in main

load_payload(dev, "../brom-payload/build/payload.bin")

File "/home/kelly/Downloads/amonet-douglas-v1.1/amonet/modules/load_payload.py", line 123, in load_payload

dev.write32(0x10007008, 0x1971) # low-level watchdog kick

File "/home/kelly/Downloads/amonet-douglas-v1.1/amonet/modules/common.py", line 163, in write32

self.check(self.dev.read(2), b'\x00\x01') # arg check

File "/home/kelly/Downloads/amonet-douglas-v1.1/amonet/modules/common.py", line 90, in check

raise RuntimeError("ERROR: Serial protocol mismatch")

RuntimeError: ERROR: Serial protocol mismatch

Any ideas on what I may be doing wrong here? Also I just noticed after this post that the brick method is posted on the OP and so far my tablet isn't responding. After entering fastboot mode, I run the brick.sh from VM/Ubuntu, type YES and get the following output:

Bricking PL Header

Check instructions on device

< waiting for any device >

target reported max download size of 114294784 bytes

Sending 'brick' (112090 KB)...

Then on the tablet it shows:

USB Transferring...

but then that's all I see after waiting at least 10 minutes.
[Fire HD 8 and HD 10 Original Android Development] klister:
Ok, here's a little more info. I thought there might be a problem with the USB pass-through so I switched from VMWare to VirtualBox (same VMDK) but got the same result there. I switched back to try again in VMWare but this time when I tried to list the fastboot devices it gave me a response of...

"no permissions (user in plugdev group; are your udev rules wrong?)

After Googling it I was able to add a rule for this and now I see the tablet listed in fastboot devices. Now when I run the brick.sh I get the follow which seems like I'm back at the beginning.

kelly@KellysVM:~/Downloads/brick-douglas/amonet$ sudo ./brick.sh

Brick preloader to continue via bootrom-exploit? (Type "YES" to continue)

YES

Bricking PL Header

Check instructions on device

target reported max download size of 114294784 bytes

Sending 'brick' (112090 KB)...

FAILED (data write failure (Protocol error))

Finished. Total time: 73.512s

I might get another virtual running and see if there something screwy with the permissions on this one. Sorry for the run-on...
[Fire HD 8 and HD 10 Original Android Development] Korin67:
Thank you for the good feedback. But, I was silly. I could not wait your post. I started HW method. Everything was smooth until the most critical step, TP28 shortning step. I tried several times without success. bootrom-step.sh did not proceed after go into waiting state. I gave up and close the device. Then, I found it is totally disappointing. I cannot power on. The device seems dead. But the device is not totally dead. PC can recognize my device, yes it is recognized as a adb device. I think I carefully re-connect the digitizer cable, but nothing appears on the screen. Please give me a hint to recover my half-dead tablet.

EDIT: Since my half-dead device is recognized as adb device, I tried brick-douglas, but it stays with this message and did not proceed:

Brick preloader to continue via bootrom-exploit? (Type "YES" to continue)

YES

Bricking PL Header

Check instructions on device

< waiting for any device >
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
I just noticed, that LK got updated in the 9820 build.

I have uploaded a new brick-douglas that works with the 9820.

That sounds like an issue with the LCD-connector, not with the digitizer.

The LCD connector is located at the bottom left of the mainboard.
[Fire HD 8 and HD 10 Original Android Development] Korin67:
Thank you for the suggestion. I think LCD-connector is this in the picture. I check it but

seems okay. Anyway, I can use adb connect to the tablet, I will continue to try with this port.
[Fire HD 8 and HD 10 Original Android Development] Korin67:
My tablet came back. I do not understand what happened, but left my HD8 a couple of hours. Then from PC typed 'adb reboot'. Yes, this time I can see Fire logo and resume to the condition before opened it. Now I am on 9820 version. I will try SW method first. HW method is too difficult for me, I am not that skillful. As I wrote, the new brick.sh did not work. It stays < waiting for any device >, and does not proceed.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
You need to be in fastboot mode to use the brick.sh

adb reboot bootloader
[Fire HD 8 and HD 10 Original Android Development] TraderJack:
Wondering if anyone else has had any issues with random reboots back to TWRP?

Now I haven't been using my FireOS for months and months and only just came back to it now that there is the root/bl unlock.

I was on the tablet for a few minutes this morning just scrolling through some of the setting menus trying to setup notifications the way I like.

When I came back to my tablet just now after it had been sitting for a couple hours I found that it was booted to TWRP.

There is absolutely no way that I could have booted it to TWRP, as doing so is a pretty deliberate process of holding down the volume keys.

So, what's strange is that it seems the tablet just rebooted itself - which isn't necessarily the strangest thing as I have had Android devices just reboot before.

What is strange is that it just rebooted to TWRP.

Any ideas?
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Disable OTA
[Fire HD 8 and HD 10 Original Android Development] TraderJack:
As soon as I posted I thought to myself this might be it. I had disabled/frozen a bunch of stuff right after running your unlock, but last night I had unfrozen everything to do some tests. I thought that the reboot might have been due to an OTA trying to install.

So, immediately after posting my question I went into System Updates and hit "update."

I expected the device to reboot into TWRP and do nothing, which has often been my experience when trying to do OTA updates on a modified devices.

Instead, the device rebooted to TWRP, but instead of just sitting at the TWRP main screen it actually ran an update script and then rebooted to the the FireOS where it did the "Optimizing system storage and applications." It now just completed having upgraded me to 636558720.

I'm not sure that is why my device rebooted before, since it was just sitting at the main TWRP screen, when a manual click of "Update" went through the whole process and upgraded me, rebooting back to the FireOS.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Incremental updates will fail and it will just sit in TWRP.

After a failed incremental update the device will automatically download the full update, which will go through.
[Fire HD 8 and HD 10 Original Android Development] TraderJack:
Totally right! After updating to 636558720 it wanted to update me to 636559820.

I went ahead and clicked to to it and after a quick download it rebooted to TWRP.

I saw what looked like an error (red text?) flash very quickly but then it just sat on the TWRP main screen and I needed to manually reboot.

I then clicked update again where it downloaded the entire update and applied it via TWRP like the last time.

I am now running with 636559820 and all I needed to do was flash Magisk again after each update to get root back.

So, this is also to confirm that you can definitely run 636559820 *AFTER* you have already unlocked and installed TWRP using your process.

I know you have stated this should be possible, I just wanted to confirm this to be the case as I have not read a post yet of anyone stating they have definitively done so!

thanks again.
[OnePlus 6 Questions & Answers] Llondru:
I have been using succesfully this service : https://enterprise.google.com/android/experience for a year, without problem.

Recently I reseted my device due to some problems related to play store, and now, when I want to configure again my work profile, it just get stuck.

The app that enables work profile is that one -> https://play.google.com/store/apps/details?id=com.google.android.apps.work.clouddpc

I tried to :

- Delete my work profile and recreate a new one

- Delete cache and data for the app

It starts the process without any problem, but then it gets stuck at "registering your profile" for 5-10 minutes, after giving up.

Found nothing on the internet, and google support is not helpful either.

I would appreciate some clue on how to solve this.
[OnePlus 6 Questions & Answers] GuestD2559:
Try this app. Maybe it helps. It's open source, don't worry.
[Samsung Galaxy Note 10+ Questions & Answers] Timmothy83:
Does anyone have issues with written text converting to typed text. As soon as I want to convert it, it's says processing and it stays like that and won't finish.

What could be wrong?
[Samsung Galaxy Note 10+ Questions & Answers] pete4k:
works fine on mine (SD, US model)
[Samsung Galaxy Note 10+ Questions & Answers] rcobourn:
Mine works blazingly fast.
[Samsung Galaxy Note 10+ Questions & Answers] winol:
Do you have the same language for device and keyboard?
[Samsung Galaxy Note 10+ Questions & Answers] Timmothy83:
I have English/ German and Dutch installed. I use SwiftKey as a keyboard.
[Samsung Galaxy S9  Questions & Answers] carnivalrejectq:
Can anybody tell me why when searching on sammobile I can find firmware for AIO aka Cricket under G960U1 but not for G960U, even though there is no 0U1 on Cricket? Am I missing something? Would this even be safe to flash? I'm currently on the plain U1 firmware on a cricket S9 and just want to have something incase I ever wanted to turn this back into a regular cricket S9. Didn't realize it'd be such a pita because of ATTs crap lol.
[Samsung Galaxy S9  Questions & Answers] Youdoofus:
Why in Gods name would you want to turn it back into a Cricket phone? I cant imagine the scenario where one would ever "need" any of the Cricket specific apps, but i guess if youre feeling adventurous, you can go ahead and flash the 0U1 and see what happens. As far as it being safe, all the G960Us are identical so the firmware is pretty much all the same. You got a link for the Cricket 0U1 firmware?
[Samsung Galaxy S9  Questions & Answers] carnivalrejectq:
I was on the U1 firmware trying to go back lol. I actually wasn't aware that all 0U was the same just like U1 is. So I simply just downloaded a Verizon release, flashed that and voila back to cricket lol. The reason is ......I have 2 weeks left of my cricket service before I switch to something else, and I didn't realize how much I needed wifi calling. Low signal without it was really hitting my battery life. So I just wanna be able to use the wifi calling for the remainder of my 2 weeks. After that it's back to U1 for me.
[Samsung Galaxy S9  Questions & Answers] Youdoofus:
that makes sense then. nice to see xda is back up and running too lol
[Samsung Galaxy S9  Questions & Answers] YooperNC:
How did it work? I'm curious because my situation is similar. I live in a cell signal desert and must have WiFi calling. My S9 hasn't had an update since July 2020. I found a copy of G960U1UEU8FTK2+G960U1OYM8FTK2 for AIO from Nov 2020, which is (obviously) a U1 build, but my phone is currently a U. Will this allow WiFi calling? Or will I be screwed if I flash it? I'd like to find the July 2020 firmware as a backup, just in case, but I can't track it down anywhere. Thanks!
[HTC Excalibur] jshim000:
Guys/Gals,

Newbie here. I'm trying to modify the sliding panel media homescreen.xml file. My question is more for the general xml programming. Is there a way to include a "plugin clsid" within a "plugin clsid"?

See the attached xml file. There's "CCustomPlugin" section where you can create your own panel. I'm using Good mobile messaging and i want to be able to add the Good mobile email and unread email plugin.

Thanks in advance for your help!
[HTC Excalibur] showaco:
Actually, to add a new panel, you need to add a new dir(name of you choice) in your reg under chome. Under the new dir, copy all of the info from CWelcomeCenter panel into it. Then you can modify all the values(text,picture,url) to what ever you want. No need to change xml except since you have a list of plugins in there(cclock,chome,etc), you need to add it to the list. Once you created the dir, with copied info in it, you could use chome configurator to modify the values(easier).
[HTC Excalibur] jshim000:
Thanks Showaco. Does the method you described allow me to add a plugin as well? What i want to do is this. I want to add a panel with a program (exe file). This program also comes with a plugin clsid that shows my online status. So the end product would be an icon, the program name, and my online status. I think the method your prescribed only would allow me to add the program and the description of the program. But not the plugin clsid...
[HTC Excalibur] NRGZ28:
Showaco didn't understand what you're trying to do. Let me explain...

In the homescreen xml file you can ONLY have two plugins (in the sliding panels configuration). One being CHome and another being the 20 pixels at the top. The top plugin can be anything... 99% of the time it's the iconbar, of course. People like rinku have made different plugins that show different information up there, but.. you lose the iconbar. So, to wrape it up, you can replace the icon bar GUID in the XML with your plugin's GUID(and settings) and have it show up at the top. BUT, you lose the icon bar.. and that's a NO NO if you ask me :)
[HTC Excalibur] showaco:
I gotcha now, I didn't know realtime data involved. The only way I know is to use testuiplugin panel, but it would only work if the info that you want to display is written somewhere in the registry. Does the email program write info to the reg already?
[HTC Excalibur] jshim000:
I understand. So you can't have another plugin within CHOME..that sucks and makes what I want to do harder.

What I'm using is Good Mobile Messaging. I assume this program already writes to the registy? It would be perfect if I can just replace the CCalendar with GoodCalendar and CMessaging with GoodEmail.
[Android Q&A, Help & Troubleshooting] Clone_Cat:
My $20 hoot huawei p20 pro CLONE (here a link /w info about the phone with false specs full of bugs)https://www.freebrowsinglink.com/hoot-p20-pro/ got bricked a week ago after I left it connected to a Windows computer with internet access.

The story starts with when I tried to root the phone with KingoRoot, eventually ads started popping up, facebook, dating or porn sites and malware like that. I uninstalled KingoRoot and installed some anti spam software like avg and avast, but that did not help, ads kept coming. The phone has Android 5.1 Lollipop on it and after I left it connected to a Windows Laptop, like I said before, error messages with 'UI has stopped working' and 'other stuff stopped working' started popping up in a whole sequence of error messages so it rendered the phone unusable.

Next I started messing with it via platform-tools and wanted to flash TWRP on it and eventually a different OS like Lineage, but now the phone is totally shot and I can not use recovery any longer. The only thing that seems to work is fastboot mode, but it doesn't let me install a custom recovery like TWRP. Unlocking the bootloader seems to work, like shown in the attached pix, but other commands like 'fastboot devices' give a funny looking device name: '0123456789abcdef'. Other commands like fastboot erase -w and oem info show failure only; reboot-bootloader works and so on.

Any advice on this one? I'm just trying to learn about phones and android and this seems like a perfect opportunity, unless this cloned smartphone is piece of a worthless brick, which most assuredly is.
[Android Q&A, Help & Troubleshooting] Teddy Lo:
Try to flash corect stock firmwares for your device , check which one is yours .

https://hellostockrom.com/huawei-clone-p20-pro/
[Android Q&A, Help & Troubleshooting] Clone_Cat:
Yo TeddyLo, I tried already a similar website and after 2 hours of downloading through a slow internet connection the files were encrypted WinRaRs and probably useless anyway...thanks bro.
[Android Q&A, Help & Troubleshooting] Clone_Cat:
Hard Bricked Hoot P20 pro Clone

Yo, Teddy Lo, I had been busy last few days and tried to follow your suggestion, but to no avail. The device is now a hard brick, it does not come on at all, no more fastboot mode, or battery status logo when off and loading for that matter. It all happened when I tried to flash this file 'DOOGEE-Shoot_2-Android7.0--20170517' with SP Flash Tool. The device downloaded the files, but is completely dead now.

I am trying to do format and download with different ROMs for whatever is available on the internet for a P20 Pro clone phone, and phone manages to establish connection through USB with SP Flash Tool, but every time I get the following error message:

How can I fix this problem? Thanks.
[Android Q&A, Help & Troubleshooting] manurio:
hi, i had the same problem, and i found this forum , it solved the issue ....

forum.gsmhosting.com/vbb/f296/clone-welcome-huawei-p20-pro-firmware-2574709/

Regards
[Xiaomi Redmi Note 7 Pro ROMs, Kernels, Recoveries,] sriram prakhya:
GZOSP

is GZ-AOSP (Fancy name of AOSP-CAF?) based with a Dark Wolfie theme with full OMS support and has a lot of features.

is GZ-AOSP based with full OMS support and has handpicked useful features.

is based on Slim with full OMS support.

G+ Community

https://plus.google.com/u/0/communit...59573276360638

Substratum G+ Community

https://plus.google.com/u/0/communit...17366580091389

Theme Ready and TBO apps

http://.xda-developers.com/showthread.php?t=3113192

http://.xda-developers.com/showthread.php?t=2283828

Whats working?

Wifi

RIL

Mobile data

GPS

Camera

Flashlight

Camcorder

Bluetooth

FMRadio

Fingerprint reader

Lights

Sound / vibration

Facelock

Known issues

Nothing

Installation Instructions

ALWAYS MAKE A NANDROID BACKUP FIRST!

Coming from another rom/clean install:

Reboot to recovery.

Wipe cache, dalvik/art cache, data

Flash rom zip and gapps

Reboot

Updating from a previous build/dirty flash:

Wipe cache, dalvik/art cache in recovery

Flash rom zip, and any other zips you may use

Reboot

Magisk is included as default Root providing application. However if you prefer any other root providing solution, please flash magisk uninstaller (search in xda) before you proceed.

As an alternate root solution, SuperSU can be flashed, v2.78 works for me. After flashing, your device may boot twice before boot animation, don't worry it'll be fine after that.

Some users reported 2.52 Beta worked for them.

You can use phhSuperuser as well for root access, get the it from here and you need to install the play store app also.

Substratum support is there as long as you have root and latest Substratum app. Some may have a little catching up to do, have fun testing them!

If you have any issues, grab a log after a clean flash, upload and link here please. Add steps to reproduce the issue in your post.

Do not report issues dirty flashing this over some unofficial build or with some kernel flashed.

Logcat Extreme app is great as you can choose to start recording a log just before reproducing an error and stop recording just after so you log just the part you need.

Xposed is not supported here, if you want to run it and have issues, try an Xposed thread for support and bug reports here only welcome with a clean install with no Xposed present.

Make sure to state which rom you are running when asking for support

Dynamic Gapps

http://.xda-developers.com/showthread.php?t=3487192

Open Gapps

OpenGapps

Downloads:-

GZOSP BUILD

XDA:DevDB Information

GZOSP, ROM for the Xiaomi Redmi Note 7 Pro

Contributors

sriram prakhya

Source Code: https://github.com/GZOSP

ROM OS Version: 9.x Pie

ROM Kernel: Linux 4.x

Version Information

Status: Stable

Current Stable Version: 2.1

Stable Release Date: 2019-08-29

Created 2019-08-29

Last Updated 2019-08-29
[Xiaomi Redmi Note 7 Pro ROMs, Kernels, Recoveries,] bskumar7080:
Screenshots please.
[Xiaomi Redmi Note 7 Pro ROMs, Kernels, Recoveries,] lapo_chel:
The file does not flash, writes error 6!
[Xiaomi Redmi Note 7 Pro ROMs, Kernels, Recoveries,] justboryata:
QS tiles styles? Wrappedkey?