yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] andyb2000:
Not sure if this is the right place for this, but here we go!

I bought a cheap Xgody D24_Pro mobile from ebay (Under £100) and it's a pretty decent unit. Hardware-wise it has:

4G

2xSIM slots

5.5inch screen (1280 x 640, 260ppi)

13MP rear and 8MP front cameras

Android 7.0

MediaTek MT6737 Quad-Core 1.3GHz

ARM Mali-T720 MP1

2GB RAM

16GB storage

Fingerprint, etc, etc.

So quite a capable little unit. However after a couple of weeks it started to get really hot when it was sat doing nothing, and battery life was terrible so something odd was going on. I then started to notice that WIFI was turning itself off, seemingly at random intervals. Didn't matter what WIFI I was using, home, work, public, etc, they all got turned off at random times. This was the reason I started digging into it and found something interesting.

An app was consuming almost 100% of the CPU. adb shell debugging helped me track it down:

5515 system 16 -4 91% S 93 1300280K 190604K bg com.mediatek.factorymode

Which seemed an odd process to use so much CPU as searching that simply had tests in it (Test touch, vibrate, LEDs, etc), so why was it running all the time and at 100% CPU?

Well it turns out there was hidden code in that app doing cryptomining! Nice!

(If you're interested in full write up I've done it on my blog: http://www.thebmwz3.co.uk/2018/08/xgody-d24-and-nasty-background-app.html)

So now I've worked around it by running a bit of shell code on my phone to keep killing the process, but now I want to try and root it.

Unfortunately like a lot of the other Mediatek67XX phones root is proving problematic, so I'm hoping somebody can help out or point me in the right direction.

The problems:

No ROM from manufacturer

Chinese recovery menu

No one-click root methods appear to work (temporary or not)

So at the moment I don't appear to be able to gain root no matter which method I'm trying.

I don't have a scatter file, and cannot generate one either since whenever trying to use the various SP_Flash_Tool or similar they identify the phone but won't really do anything as cannot map the partitions out on it.

So I'm interested to know, where to go from here!
[Android Q&A, Help & Troubleshooting] CXZa:
If "cat /proc/parti* " gives you the partitions, you probably can make

it a SP FlashTool scatter file from a scatter file of similar device.

Just change the starting addresses and sizes to match yours.

Finding a similar firmware can be a problem though, especially as some cheaper

tablets has faked hardware specs. Like your MT6737 might be something totally different ...
[Android Q&A, Help & Troubleshooting] CXZa:
And then if above worked ok, you can modify(**) the recovery

enough, so it will flash Chainfire's supersu or something similar.

https://download.chainfire.eu/696/supersu/

(** that is add busybox etc. whatever needed, and also if necessary change RAM disk's file /res/keys...

- or just get TWRP or some other custom recovery from somewhere if available...)
[Android Q&A, Help & Troubleshooting] jasonov:
same problem

i have just got a pro24 and have the same wifi drop problem and excessive data usage.

did you find a root solution?

also i installed blockada as per your advice and this seems to stop the wifi going off.

do you think the phone is safe to use? re banking, passwords etc

thanks for your previous post

j
[OnePlus 3 Questions & Answers] Romanlol:
Hi Guys, I call for help because i'm out of solutions :

My OP3's screen is broken, I need to recover my data, I already tried Vysor, but the thing is that USB DEBUGING isn't allowed, and Vysor needs access...

So I bought an OTG cable to try to activate Usb deguging using a keyboard (blind activation method in a thread on Oneplus Forum)

But my issue is : My OP3 doesn't power my keyboard or any other OTG device ! I bought mine on amazon and it didn't worked, so I asked OnePlus to kindly send me one and they accepted, got it today (nice customer support) but it didn't worked either... So It means that It won't work untill I activate the OTG option in the settings... And with a broken screen and no OTG, I can't do that.... So am I screwed ?

Do you guys see anything else to try ?

Thanks !
[About XDA developers] Casper Young:
Yeah, um. I don't know how to say this without sounding offensive. But the new format this page has. SUCKS! Oh yeah, I gotta ask a question. Alright, here goes. Why is it that I can enter something in the search bar here up to the right, and get NOTHING on a subject that I know for sure is here on XDA? I don't get it, and suddenly feel retarded everytime I try to use it since. It's a good thing I have a buncha bookmarks on my PC or I'd get totally lost within your search parameters. Believe me I already have more than a few times. Yeah, I'm obviously frustrated with it enough to write this little note for all you Admins, Moderators, whoever it is thats running things around here. Look, I should be able to enter something into the search bar and find it. But someone decided to change something that wasn't broke to begin with and now it's being difficult! Take this for an example. I'm researching a project I want to start. So, usually I would first start out in the search bar. Now go ahead, I dare ya! Enter this: Samsung Galaxy S Relay. That's an "exact" search parameter. Again with the no offense but, can any one of you tell me why I get directed to some page not even related? Where'd it lead me too? How to Root Any Device. Please fix your search parameters!
[About XDA developers] Darth:
Sorry you're having trouble, but I get relevant search results using Samsung Galaxy S Relay.

Try clearing your cache? A different xda theme? Or to test, try another browser?

You can browse the devices section too, https://xdaforums.com/galaxy-s-relay-4g

Good luck! :good:
[About XDA developers] Raiz:
Next to the search bar , there's a button called "search plus" , click on it and you'll have the right search bar ( the little one you were using is to search between article from XDA Portal)
[About XDA developers] Casper Young:
Okay, I'm back for a follow up, because this seems to be an obvious difficulty and I'll bet I'm not the only one that may be having issues with this. It's a navigation thing about the current format I see here on XDA. I noticed it a few weeks ago and it's not my cache. When I'm on my tablet I can navigate fine, but when I come here on my PC it's another story, and it's very frustrating. That's why you got this question before you in such a way. You guys who may understand it having set it up know how to get around. As I mentioned before it used to be fairly easy, now it's stupid not to belittle you. The problem is that it has suddenly become difficult to search for things in a normal maner. I use the search bar, which should dirrectly link me to what I am "specifically" looking for and let's put aside the search plus for the moment. If I'm searching for something that I know is there and I type in certain words that should bring me right to it, my question is, why aren't they! I'm getting redirected to some page, often of no relevance. And here's where I'll bet this is happening to others. So what's going on? There's a problem with your search bar, and I'm letting you know it's kinda frustrating. I can navigate through here with other ways, that's not a problem. I got some bookmarked, subscribed to, ect. The issue is that the search bar in itself is broken! Whatever you guys did to it, I saw it, pointing it out! Now fix it please. This might help. I noticed a difference about two weeks ago. Not sure what it is or was. I even cleared out from my PC anything that would suggestively lead to it being my PC settings. Being a good enough percentage to say it's not, it's therefore XDA.

On a side note for all you Admins and Mods. I've been coming here over 10 years now, I got questions and suggestions. But right now my suggestion is to please eliminate some obvious confusion I've noticed that affects an average user to navigate through your search areas.
[About XDA developers] Casper Young:
Oh! Okay, there's the sudden difference!

[QUOTE( the little one you were using is to search between article from XDA Portal)[/QUOTE]

Wow. Really? Let me ask you something about what's that all about and why did this change and for what possible reason. And then why isn't there some notice the the search bar is no longer effective as it's says it is. I'll point for you guys that the search bar says QUOTE; Type device or find apps, ROMs & more. It does not say, "This is where you go to find stuff barely relevant to what you're searching for". Does it! Sorry that this may sound offending buuut. Bad words! To me, the search bar suddenly became a joke, and a bad one at that! Articles are nice but that's not what I was looking for. And in no way was I expecting to end up there.

Okay, so here's a basic question. let's put this on the table so to speak. I don't know why you put a link to articles in the search bar in such a way to begin with. It doesn't really make sense to me. Especially with your nifty new format of where everything is, except articles I'm going to guess. So you put them in the search bar with no notice of. Can you explain all that to me? Cuz right now I'm sorry to admit, I'm kinda laughing at this. I can just imagine all you went through, even deciding on how to change the old format to what I see now. It's good. However, when it comes to the search bar, whatever idea you went with. It's one that didn't notify anyone that the search bar isn't what it says it is~!
[About XDA developers] DSA:
Ignoring your saltiness, why dont you use google and append each search with xda..
[About XDA developers] woodman:
You seem to be angry and it's a pity. Did you try the suggestion provided by RaiZProduction in a previous post? Does the Search Plus button (see my screenshot attached) allow you to find what you are usually looking for on XDA Forum?
[About XDA developers] Casper Young:
You might want to step back a second and read carefully!

I'm far from angry. But check this out. This is the Q & A section is it not? So i'm askinfg a question about a difference I noticed and the A's I'm getting are a joke! Really? Hey Wood Man? You're deflecting. Step off unless you got something relevant to say. To those of you at XDA I now have a minor complaint! You people need to read what I said. I said I noticed a difference with the search bar and could someone tell me whats wrong with it. The answer I got was a confirmation that the search bar was not functional as it says it is and that's it. So. Mr Wood Man. Did I follow the suggestion you mentioned? Ahem! Are you asking to get put down blatantly or what? I made a post, RaiZProduction made a suggestion, what may I ask you is the post after that? Mine! A follow up. Before you decide to jump in there, you might wanna inform yourself better.. This here Q & A asked, "Rather than sending a PM to an individual Moderator, please feel free to ask questions in need of Moderator or Admin assistance. We will all be monitoring this thread, and someone will reply without much delay." Well, I obviously came to the right place didn't I? Everyone has a personal preference and I used the search bar a lot.
[About XDA developers] Darth:
OK, I'll stop this here.

Answers were given, some with ideas, others saying all is fine for them. And also your opinion on the search is noted. However, it seems to work for everyone else, so not sure what more to say.

And honestly, your aggressive posts are getting a bit much, so I'll end this before lines get crossed. I suggest a more respectful approach in the future Sir. :good:

Thread closed.
[Android Q&A, Help & Troubleshooting] ericsanate@gmail.com:
Hi guys, can u help me, on redmi note5 pro i have upgrade miui9.5.19.0 im using jio sim after update miui9.5.19.0 latest stable version but i can't make outgoing calls incoming and sms please help, im trying many solution but can't proceed
[Huawei P10 Lite Questions & Answers] L1nx99:
How to change devices model name on emui 8?
[Huawei P10 Lite Questions & Answers] ndg_2000:
You flash a different oem info then reflash the 8.0 Rom
[Android Q&A, Help & Troubleshooting] Kuxet:
My Redmi 3s ins't working anymore , it all started when I wanted to install nethunter but failed several times I then tried to change the rom got a lot of other roms but yet nothing happened then I found this thread

https://xdaforums.com/redmi-note-4/...er-development/rom-kali-nethunter-os-t3596453

I tried what's there, things went smooth till the process of install gapps it failed and now my phone will never turn on , not even in fast boot .. I think its hard brick , any idea on recovering it back ? I really need the phone ..
[NFC Hacking] Unit ZER0:
Recently, I purchased an S7 Edge, and it has Android 7.0 on it. According to my menus, I have access to NFC, but the NFC system has never worked. The closest I have gotten is the message: "NFC Configuration not Valid", when using the Card Emulator Pro app...

According to my CSC, I should have NFC, and I've even switched countries to see if that makes it work. No such luck

Is there an APK out there I can use to install the appropriate configuration onto my device, or even a reliable way to see if it even has the needed hardware?

I am running stock TouchWiz, but have Magisk Root, and TWRP recovery installed, so flashing components is not an issue.
[Magisk] feklee:
First I unlocked the boot loader, although I doubt that’s needed for installing Magisk:

A2/Android (Oreo 8.1): Enabled developer options, enabled unlocking of boot loader, enabled debugging via USB.

PC/Linux: $ adb reboot bootloader

A2 boots into boot loader.

PC/Linux: $ fastboot oem unlock

Then I tried installing Magisk:

A2/Android: Re-enabled developer options, enabled debugging via USB, disabled automatic system updates (just in case, for later).

PC/Linux: $ adb reboot recovery

A2/Android: On the dialog asking for permission to allow USB debugging, selected to always allow from this computer and hit OK.

A2 displays screen with lying robot, saying No command. I held power, pressed volume-up once, released power.

A2 boots into recovery.

A2/Recovery: Selected Apply update from ADB.

PC/Linux:

$ adb sideload Magisk-v16.0.zip

Total xfer: 1.01x

A2/Recovery: Error message failed to verify whole-file signature

PC/Linux: Checked the zip file. It can be unzipped just fine, so it’s OK.

What else can I try?

PS: I do have detailed screen shots of the critical steps, but I don’t find an option to upload them to the forum.
[Magisk] Didgeridoohan:
You can't sideload the Magisk zip on a stock recovery. If you don't have a custom recovery installed you'll have to patch the boot image first with the Manager and then flash the patched image manually with fastboot. Check the installation instructions in the release thread.
[Magisk] feklee:
Thanks!

Tried that, but did something extremely stupid in the process, knowing full on that this could cause an issue (I assumed things are easy to fix in case something goes wrong):

I did not run any system updates, leaving the Android 8.1 ROM at V9.6.5.0. (no problem so far)

I downloaded V9.6.10.0 of the ROM, and had Magisk patch the included boot.img to create patched_boot.img (still no problem)

I flashed patched_boot.img onto my A2. Now the device did not boot anymore. It hung at the loader animation showing a horizontal bar with varying colors.

To get the A2 to boot again, I obtained V9.6.9.0 of the ROM, I flashed the included boot.img, and I cleared the cache. Unfortunately, while the device boots into Android now, I cannot enable WLAN. It simply doesn’t work. Again, no surprise: V9.6.9.0 ≠ V9.6.5.0

Not being able to find the V9.6.5.0 ROM, I got the idea to update the half broken A2 to the latest ROM, i.e. V9.6.10.0. But how, without WLAN? Well, I found out that it is possible to use the WLAN connection of another Android device via Bluetooth. This is what I used, and I had to be very patient – it’s dog slow. Anyhow, I waited, and the installer started to do its job. The download succeeded, but the installation failed.

Phew, for now I’m out of options, and I’ve a non functioning device. :(

In another thread on the XDA Forums, I did find an unofficial dump of V9.6.5.0. But 1. I’m hesitant to install from unofficial dumps, and 2. the dump does not include a boot.img. Instead it includes one big payload.bin. Don’t know what to make out of that.

The alternative could be to install either V9.6.10.O or V9.6.9.O manually, possibly by flashing each partition image individually from fastboot. I don’t know, however, if that is a great idea.

PS: Sorry about the confusion with all those numbers. ;)
[Magisk] Didgeridoohan:
Oh man... Flashing an update manually (each partition should work fine) is probably a good idea at this point.
[Magisk] feklee:
Went ahead with that. In fact, included in the full ROM archive are scripts for doing the update, sorted by an increasing number of steps performed:

flash_all_except_data.sh

flash_all.sh

flash_all_lock.sh

flash_all_lock_crc.sh

The last one also flashes CRC check sums into crclist and sparsecrclist. Included is a script to generate these check sums form the image files: flash_gen_crc_list.py

Here’s how I got back to a system that boots up fine:

PC/Linux: $ tar xfz jasmine_global_images_V9.6.10.0.ODIMIFE_20180731.0000.00_8.1_2aeda83301.tgz

PC/Linux: $ cd jasmine_global_images_V9.6.10.0.ODIMIFE_8.1

PC/Linux: $ fastboot flashing unlock

(reboot)

PC/Linux: $ fastboot flashing unlock_critical

(possibly reboot again)

PC/Linux: $ ./flash_all_lock_crc.sh

(went through smoothly, flashing CRC possibly not necessary)

Following this success, I did another attempt at installing Magisk:

PC/Linux: $ cp ../patched_boot.img images/boot.img

(created with Magisk Manager from the V9.6.10.0 boot.img)

PC/Linux: $ python2.7 flash_gen_crc_list.py

(thought it’s a good idea, but doesn’t help – see below)

PC/Linux: $ fastboot flashing unlock

(reboot)

PC/Linux: $ fastboot flashing unlock_critical

(possibly reboot again)

PC/Linux: $ ./flash_all_lock_crc.sh

(went through smoothly, flashing CRC possibly not necessary)

Unfortunately, upon reboot I get:

<!>

Your device is corrupt. It can’t be trusted
and will not boot

Visit this link on another device:
g.co/ABH

Eventually the device doesn’t show the message anymore, instead hanging permanently at a androidone logo.

Not locking the boot loader after flashing solves the issue, but: For security reasons, I don’t want to use a device with an unlocked boot loader!

Any idea?
[Magisk] feklee:
Uh-oh! Now it seems like I eclipsed my previous stupidity.

In the Android developer settings, I disabled OEM unlocking. Then I rebooted the device, locked the boot loader: fastboot oem lock This was still possible.

As result, I get the aforementioned error message:

<!>

Your device is corrupt. It can’t be trusted
and will not boot

Visit this link on another device:
g.co/ABH

But now I cannot unlock the device anymore. fastboot oem unlock gives: FAILED (remote: Flashing Unlock is not allowed)

Bricked for good, right? :crying:
[Magisk] Didgeridoohan:
Oh... I saw your first message about getting things working (post #5), but I didn't have time to answer (work, work, work).

Now I wished I would have had the time, since I would have posted that you should never lock your bootloader on a modded device. The risk of something going wrong and not being able to unlock the bootloader again is too great...

If you're lucky there's still some kind of hack available that you can use, but you'd have to take that in your device's forum, where they know the device best.

That sucks... I hope you get things sorted. Good luck.
[Magisk] feklee:
Don’t worry. I like to take systems to their limit.

For security reasons, I don’t like the idea of leaving the boot loader open. While I understand that – due to encryption – it’s not possible to access my data, I assume it would be feasible to modify boot.img to install a rootkit in a few minutes. Just the thought of this being possible makes me uncomfortable and not trust the device for productivity use.

I wonder if I would also get the your device is corrupt message with Lineage installed.

Yes, I’m betting on that, or perhaps the Xiaomi Mi Flash Tool can be used. (looking for an official download location)
[Magisk] Didgeridoohan:
Did you preserve dm-verity when you patched the boot image? That sounds like dm-verity complaining...
[Magisk] feklee:
No:

I’m almost certain that I did not enable dm-verity.

The device is corrupt message appears right after the reboot following ./flash_all_lock.sh or ./flash_all_lock_crc.sh, i.e. without any setup by Magisk Manager, and dm-verity is disabled by default.

BTW I got around to trying Xiaomi Mi Flash Tool, but it’s useless: It seems to be simply an ugly GUI for the fastboot commands. It cannot flash a device in locked state. In the end I was able to revive the device by opening it and using the test point method. Phew, gotta be more careful the next time…
[Galaxy S 4 Q&A, Help & Troubleshooting] audit13:
Doesn't look like the final s4 as the s4 has a 5" screen and rounded corners and home button.

Definitely looks interesting!
[Galaxy S 4 Q&A, Help & Troubleshooting] artur.heise:
Correct - front is rectangle-ish, but look at the back. Usually protos are masked to not give-out much of the final shape.

The screen is reported as 4.7" but in reality it's 5" 1920x1080.

Does regular S4 include S-pen options?

BTW. I saved all possible partitions if anyone is curious. :)
[Galaxy S 4 Q&A, Help & Troubleshooting] artur.heise:
Firmware is buggy, slow and eats battery very fast. Usually to boot I need to connect it to my computer, otherwise it hangs on android logo. Wifi and BT is working, phone - not much, due to imei 0/00. Led and key light, doesn't work, backlight is always max.
[Galaxy S 4 Q&A, Help & Troubleshooting] audit13:
Are you able to determine the model # or firmware version after booting the phone?
[Galaxy S 4 Q&A, Help & Troubleshooting] artur.heise:
Posted it already:

---------- Firmware Information ----------

PDA Version: ADONISLTE_TEST

Baseband Version: IxxxxXXALI1

CSC Version: ADONISLTEOXADLH5

---------- Software Information ----------

Kernel Release: 3.4.0-323456-eng

Kernel Version: #1 SMP PREEMPT Fri Oct 12 16:20:01 KST 2012

ROM Build: adonisltexx-eng 4.1.1 JRO03R ADONISLTE_TEST test-keys

Android Version: 4.1.1

Model number is just: GT-XXXX no number at all. :)
[Galaxy S 4 Q&A, Help & Troubleshooting] audit13:
Yes, I saw the GT-xxxx part. I just thought there may be something else.
[Galaxy S 4 Q&A, Help & Troubleshooting] artur.heise:
Nope, that's all. :)

All late prototypes (v. 0.8 or 0.9) usually had model name revealed, this one must be some early stage.
[Galaxy S 4 Q&A, Help & Troubleshooting] devingubler1:
give you 70 bucks for it
[Galaxy S 4 Q&A, Help & Troubleshooting] artur.heise:
I'm afraid you're too far away... :)
[Galaxy Note 4 Q&A, Help & Troubleshooting] Ferg8080:
SORRY PUT THIS IN THE WRONG FORUM SHOULD BE IN GENERAL HOW DO I DELETE THIS FROM HERE

A question on ROM flashing habits

Can I ask you folk who regularly spend time flashing your phones with the regular builds which may be coming out daily, do you do a full wipe beforehand (and maybe use something like Titanium backup to restore your apps) or do you dirty flash or do you as the official advice seems to be to do a full wipe and reinstall manually.

I just can't believe anyone has the time to do a full wipe and reinstall the apps every time they flash esp if they regularly update. I'd really love to know. I ask this as I'd flashed a ROM back in April and was dreading having to reflash an up to date image (GPS wasn't working) due to time constraints and only got around to it this week. Cumatively it must have taken a whole day due to issues I was having which in the end weren't down to the ROM. But 3 times I wiped and reinstalled and it took up so much time before I finally had things the way I wanted them though still have some niggles.

How often should I be keeping current with ROM updates if my current install is working fine?