yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] MickBert:
Forgotten thread?

I am doing some test in this days with Simple SMS Messenger, installed from f-droid.

I disabled the battery optimization and enable background for the app. Then it seems to work, once you started the app after a reboot, it works good, even if I close the all the apps, and load a number of other big apps. Of course I am not granted that the garbage collector will not flush it any more. But I keep going with my tests.

What I cannot find is a way to let it start automatically after reboot.

Note that I still have play services active, though.
[Touch Diamond, MDA Compact IV General] TheMafioso:
Hi,

I've a HTC Diamond, UK version with the following rom:

1.35.401.3 WWE

30-05-2008

0.93.25.NS26

52.26.25.09H

I've try install different versions of tomtom, actually the 6.32, but impossible to detect the integrated gps... I've only bluetooth, wired and Others NMEA...

I've try all Bauds settings possibles on NMEA but noone work...

Any solution plz? I've 1 day for decide if I buy this Diamond for replace my Touch Cruise or not... And i want be sure the GPS is working...

Plz if you know, say me how can i have this gps working with tomtom...

Maybe an other rom? If yes wich? Or a special version of TomTom? Or any fix?
[Touch Diamond, MDA Compact IV General] woetyke:
choose: other nmea gps

COM 4

baudrate works with 9600

(other may also work)

then you need to have "waiting for gps signal" in gps status

grtz
[Touch Diamond, MDA Compact IV General] TheMafioso:
I can't chose the port... Only the baud rate...

And i have "not gps device found" always
[Touch Diamond, MDA Compact IV General] woetyke:
i use 6.030.

in other postst you can find more information about used versions
[Touch Diamond, MDA Compact IV General] TheMafioso:
I've try this version too but same problem... any idea?
[Touch Diamond, MDA Compact IV General] woetyke:
you can check the settings from you internal gps receiver.

settings->external gps

you find there 3 pages with settings(com port etc)
[Touch Diamond, MDA Compact IV General] TheMafioso:
yes

Programs: Ports: COM 4

Hardware: Port: None, Baud rate: 4800

But if i change anything, i click ok and come back, it is back to default value... I can't set 9600 Baud or other value... if i click ok and enter again in external GPS options, it's back to 4800...

This mobile does really have GPS??? I'ts not writed in the box and in the manual too... I see nothing about GPS... The manual is very little and the box is a "diamond looking box"...
[Touch Diamond, MDA Compact IV General] sandervanzijl:
offcourse it has gps. everybody is using it.

you do not need to change the settings in extarnal gps.

just open up tomtom, choose other nmea gps, 4800 baud and com 4.

i have tomtom 6.010 (i do not know what the newer versions have different)

and it works very good.
[Touch Diamond, MDA Compact IV General] TheMafioso:
Strange because nothing say in the box or manual that it got gps... And it's not detected by tomtom...

Any idea??? Tommorow i have to give the diamond back or keep it so i've to decide today... And i want a mobile with gps working...
[Touch Diamond, MDA Compact IV General] sandervanzijl:
you can also use google maps. that has a gps function.
[Touch Diamond, MDA Compact IV General] TheMafioso:
But google maps need to connect via gprs someitmes and that isn't totally free... I want a totally free use gps... Not a "net depending" gps...
[Touch Diamond, MDA Compact IV General] sandervanzijl:
just for testing purposes!!

or use this program

http://gps.pdatopsoft.com/download/?pid=11555

install it, and it will look for your gps unit.

it will be installed under programs > gps test
[Touch Diamond, MDA Compact IV General] TheMafioso:
Lol don't ask me how and why but i've hard reset the phone and reinstall tomtom, and now i've the choice of port and baud... I've chose 4800 baud and port com 4 and it works... lol
[Touch Diamond, MDA Compact IV General] s1rl4ncel0t:
[ironic mode ON]So it seems like Diamond has GPS although it is not writen in the box...[/ironic mode OFF]

Bye
[Touch Diamond, MDA Compact IV General] p3eps:
I have to say I was dubious when reading the specs too, as they say 'GPS and A-GPS Ready' - which normally leads you to believe that you need another bit of kit to use them.

Then I found confirmation - and was happy to order the phone.
[Touch Diamond, MDA Compact IV General] Tuut_Tuut:
QuickGPS

I order to get a good working signal start the program QuickGPS, download in this program the latest gps file from server.

Start Tom-Tom and use the settings mention above:

choose other nmea gps,

4800 baud and

com 4.

Be sure to stay outside free to air and you get your signal in about 30 to 45 seconds.
[Touch Diamond, MDA Compact IV General] tiburone:
And that's all. good explanation. i did the same and working. But why doesn't detect integrated antena like kaiser? any answer...
[Touch Diamond, MDA Compact IV General] s1rl4ncel0t:
Do you guys have the following problem?

When I open the settings of the gps, inside the phone's settings, I try to change the settings, but when I press "ok" it doesn't save the changes. For example, if I change the baud rate from 4800 to 33600 and press ok, if I immediatly open it again, the setting goes back to 4800 again. :confused:

This happens also if I change the COM port from "none" to other. :confused:

Having "Manage GPS automatically" under "Access" tab activated or not, doesn't make a diference.

Bye
[Repurposing Old Devices] raha2699:
Do you have an older Android device? If yes, do you still use it in any way? ?, Share your story here.

Android OS is dynamic (I'd say unstable ?). The device you are buying today might become older enough in a couple of months in terms of the Android version. However if you're lucky to have a truly rich and supporting community, your device will be alive for an eternity.

In the revolution of Android ecosystem, you would possibly like to upgrade your device after major Android updates. Or you have to be satisfied and hanker after the newer Android features otherwise.

Now it's time to share mine ?. I got a local, cheap Jellybean device, when I was introduced to Android in early 2014. Now I have still that Android 4.2 device which I love more than the prettier material design or even the notification dots and others.

I have been using that device for my development purpose for a long time alongside my primary device. As I used it in my first step to Android root, mods, hacking and the system insight. I still remember the day I got this device into bootloop for the first time ?. Those days have passed away.

Now I am learning and developing Android apps. Since my laptop is even smaller than its small configuration (? You can call me a poor guy), it is quite impossible to test and debug apps on Android emulator while running Android studio in parallel with 4GB of RAM and i5. So, I started using my old friend as a helping hand in development. I keep it connected via USB while developing my apps, run and test them with it which frees nearly 700MB of RAM on my tiny machine and boost the build time also. For other Android versions, I have to do them on emulator separately ?.

What you're thinking of me I don't care ?. The phone is much more to me. Feel free to share yours...
[Repurposing Old Devices] MohdAhmed:
What is your phone name and model?

Have you installed a custom rom on it yet?

What are your apps which you have developed?
[Fire TV Q&A, Help & Troubleshooting] NiteVibe:
Many SIDELOADED apps do not display the app's icon when viewed in the app library. The apps installed correctly and launch as they should. The icons themselves simply show a grayed out broken link picture. These same apps had none of these issues upon install on the 1st Gen Cube.

Attempts to fix:

Cleared cache

Cleared data

Deleted and reinstalled each app

Restarted device

Factory reset device

Software updates are current

TV App Repo doesn't work of course

Even tried to install the launcher version from the 1st Gen Cube onto the 2nd Gen Cube but it will not execute. Tried to delete the launcher and install the 1st Gen version but I don't have root access to do so.

Any suggestions to help?
[Fire TV Q&A, Help & Troubleshooting] AmznUser444 Dev:
You can use sideload launcher from [MENTION=631273]Chainfire[/MENTION] or launch via ES File explorer

What the brand of your LED TV?
[Fire TV Q&A, Help & Troubleshooting] david2descent:
On fire cube 1 generation, this happens as well. Some apps icons aren’t recognized by FireTV.
[Fire TV Q&A, Help & Troubleshooting] Michajin:
The icon size doesnt fit the TV icon format. I personally use appstarter to see all apps when needed.
[Redmi 7A Questions & Answers] stormy1777:
Got a second Redmi 7A, I'm 99.99% certain it came with *global* 10.2.5 PCMMIXM (it was what ordered, and saw it too, pretty certain), decided to let it upgrade OTA, it picked 11.0.6 OTA, and it came to:

MIUI Global 11.0.6 PCMEUXM (notice the EU there), which, I'm assuming from this url: https://mirom.ezbox.idv.tw/en/phone/pine/

to be this one:

Redmi 7A – EEA Stable ROM
Lstest V11.0.6.0.PCMEUXM(History)
MIUI 11
Android 9.0
Update at 2019-10-31 19:05:57
Changelog Expand Official Link
Recovery miui_PINEEEAGlobal_V11.0.6.0.PCMEUXM_bcc90ca1df_9.0.zip
Filesize 1.5G
MD5 bcc90ca1df89a4f3d8cc7b9705a70d83

which is a bit confusing, it says Global, but has "EU" in the name.. in any event, flashed TWRP as per:

https://xiaomifirmware.com/guides-and-tips/how-to-install-twrp-and-magisk-root-on-redmi-7a/

choose the LRTeam version:

2a3296af05267160cba2891bff446203 TWRP-3.3.1-1003-REDMI7A-CN-wzsx150.img

seemed newest, all is great, it boots into TWRP recovery.. Next, trying to get Magisk on it, got the manager apk installed 7.4 all fine, it says 20.1 needs to be installed so...

unzipped the boot.img from above zip file, it has this md5, this is original , unmodified boot.img:

036d1b6c5a99e9417f8d3e98d5718368 boot_Global_V1106PCMEUXM.img

following this guide: https://romprovider.com/2019/01/create-pre-rooted-patched-boot-img-magisk/

Magisk successfully patched the boot.img on the same phone (running 11.0.6) and got this file:

dad219422c9302a460d4d2370adafb4f magisk_patched_Global_V1106PCMEUXM.img

transferred to PC, attempted to flash:

c:\XiaomiADB\bin>fastboot flash boot magisk_patched_Global_V1106PCMEUXM.img
target reported max download size of 535822336 bytes
sending 'boot' (14914 KB)...
OKAY [ 0.470s]
writing 'boot'...
OKAY [ 0.190s]
finished. total time: 0.665s

c:\XiaomiADB\bin>fastboot reboot
rebooting...
finished. total time: 0.003s

Phone boots fine, however, magisk still says it needs to be installed... :(

in developer's options, the USB debugging is enabled, and boot loader is definitely unlocked, it says on splash screen and the OEM Unlocking is greyed out and says "bootloader already unlocked".

Also, attempted to flash boot image from within TWRP, selecting the above boot.img file and selecting the boot partition, flashes OK, however, after normal reboot, as if nothing happened, phone boots, but magisk is NOT installed (no root).

Is there anything missing in these steps? does anyone have a correctly patched 11.0.6 image with magisk in it from an 7A phone?

Only thing that appears as an "error" are these family of cmds to unlock boot loader:

fastboot oem unlock
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.004s

however, i think that is normal/expected, since the bootloader is already unlocked.. able to flash twrp, etc.

Thanks so much for any ideas...

Stormy.
[Redmi 7A Questions & Answers] stormy1777:
Forgot to mention that attempted to install Magisk 20.1 zip file downloaded by the app, from within TWRP, attached screenshot of how that looks like all seems okay but after reboot it still says that magisk needs to be installed... Very strange..

Appreciate any thoughts..

Stormy
[Redmi 7A Questions & Answers] stormy1777:
noticed in above screenshot that it detected a patched boot image so decided to try installing the

v20.1 Magiskk zip file with the stock Boot, the install results in a screenshot, after reboot it still says that magisk has to be installed.!

also attaching screenshots showing the device is unlocked as well as USB debugging and OEM unlocking are all there.

Should this be posted in The magisk forum or is this something specific to the 7A? Or my steps?

How to debug further?
[Redmi 7A Questions & Answers] stormy1777:
Attempted with the other TWRP image TWRP_v3.3.1-1_all.img, same results also reinstall the magisk manager 7.4 and same results....hmm.. maybe the OTA update took wrong ROM version. (EU and not pure Global)?...
[Redmi 7A Questions & Answers] stormy1777:
Digging a bit more, found this pretty cool tool: https://www.xiaomitool.com/V2/latest called: "XiaoMiTool V2 ", which basically automated (almost) Everything !! Tried to do TWRP, as well as Magisk, it too followed similar steps I did, all automatically, rebooting, patching, etc. but outcome is still same, when phone boots normally, Magisk Manager says that Magisk 20.1 needs to be installed...

Then tried to flush miui_PINEGlobal_V11.0.4.0.PCMMIXM_674ed79f0b_9.0.zip using that tool, it said all is OK, phone rebooted , wiped all, but it still runs the EU version for some reason.. Now trying to find the path to "downgrade" from 11.0.6 to 11.0.4, or switch from EU to Global.. maybe that's the source of all issues, not sure what else to try :)
[Redmi 7A Questions & Answers] stormy1777:
Reporting progress, to keep track of what was attempted. So, decided to WIPE all and start with 11.0.4 Global fresh, from TWRP, wiped everything, to the point it said "no OS installed, are you sure u want to reboot" :) it rebooted into fastboot, then downloaded the 11.0.4 Global .tgz and flashed, phone booted OK this time into 11.0.4 :) Flashed TWRP, and then attempted to flash Magisk via both routes, one by patching the boot.img from the .tgz and flashing, all using the Phone (to avoid any PC/driver/adb issues). The flashing worked fine, but upon reboot, Magisk Manager claimed that Magisk is not installed. Second try was to flash the stock boot.img, then flash magisk zip file, did that for v20.1, v19.4 and 19.3, each time from stock boot.img, and reboots to test, none of them showed that magisk is installed...

all this time, usb debugging is enabled despite most work done on the actual redmi 7A phone itself.

Then uninstalled magisk manager 7.4, and tried with 7.2, but that doesn't change much since any action there wants to update to v7.4..

next step will wipe again, and go for the Global 10.2.5... if that doesn't work then I really don't know what can be going on...

If anyone does have a 7A with MIUI 11 with a properly patched boot.img, would love to try it... all my patching attempted booted fine, but none showed that Magisk is installed... finding it hard to think it's a magisk bug, more likely some MIUI 11, lets see how 10 works out...

Stormy
[Redmi 7A Questions & Answers] stormy1777:
OK, some success! so, wiped ALL again, to the point of no-OS installed; phone only boots into fastboot (brick), using flash_all.sh from 10.2.5 fastboot Global ROM flashed entire phone and it booted OK.

btw, not easy to find 10.2.5 now, as places already updated links to 11.0.x..

Once in 10.2.5, tried to patch Magisk in all possible ways (twrp or patching boot.img on phone the flashing from Windows10/PC) as also described in this thread few weeks ago:

https://xdaforums.com/showpost.php?p=80498891&postcount=179

but it did NOT work, well, the procedure appeared OK, no errors and when booting, it says magisk needs to be installed.

The only thing that works is the provided boot global .img file [size 14.5 MB (15,269,888 bytes)], as soon as this one is flashed, via phone/twrp or PC, then the magisk is correctly detected.

Very mysterious, why only that boot.img is working on my 7A phones.. maybe there's an additional step, to "sign" or fix the boot.img before it can be flashed?

now took a full TWRP backup, and will try to move to 11.0.4 see if magisk is retained, and if not, if possible to re-gain it.. if not, then, will restore from TWRP backup.

Any thoughts welcomed..

Stormy.
[Redmi 7A Questions & Answers] stormy1777:
Did not manage to get it working with MIUI 11 yet, so backed to MIUI 10.2.5.. all is fine there.

Noticed that TWRP did not "stick", flash but after normal boot, it came back to original recovery. I think this is b/c of Verify Boot in android Pie/9.. so I *think* what helped here is to flash a vbmeta.img from first post of this thread:

https://xdaforums.com/redmi-7a/how-to/custom-gsi-firmware-t3965820

Even after flashing this, and even in 10.2.5, patching the STOCK 10.2.5 from the phone using Magisk 20.1 and installing using TWRP did not work, not sure if this is a bug in magisk or what, but only way to get root was using the provided boot.img as described above. I'll keep using 10.2.5 for now. feel free to add any ideas here , maybe one day will get more time and a spare phone to try MIUI 11 :)

Stormy.
[Redmi 7A Questions & Answers] xsstest:
hey , I have the same problem. I noticed you mentioned 'sign', what should I sign what things? and how to sign?
[Redmi 7A Questions & Answers] depaul9999:
I was going to ask for the same thing : is there any method to root Redmi 7A under MIUI 11?

For my case :

-I can flash and boot to TWRP,

-I can 'flash' (install) Magisk through TWRP,

-However : this has no effect. Still Magisk Manager tells me that Magisk was not found!

The Redmi is unlocked and I can install custom roms (Mokee, LineageOS...). I see no reason why the phone can't be rooted it's probably just some bad configuration.

Thank you very much
[Redmi 7A Questions & Answers] KnowTheyself:
Don't bother rooting Redmi 7A, it just isn't possible, not even with the miui 10 (I've tried). There's no way to flash magisk successfuly, because when you do, magisk is still uninstalled, therefore no root and if you try SU instead, it happens some kind of error. If you try magisk without TWRP and flash a patched recovery it still doesn't work either. Since I can only follow tutorials because I understand nothing about Android I can say that there is no tutorial out there that works and all of them are wrong. I just don't understand why people bother to make tutorials that do not work just to make people waste their time.
[Redmi 7A Questions & Answers] depaul9999:
Thanks indeed that's the case for the moment. Hopefully we could soon manage to root the phone successfully.

My biggest motive is to install App2SD and move games to external storage, since with my 16GB version I can barely install one or two games and MIUI only allows installation to internal. (I know I should've bought a phone with bigger storage).
[Redmi 7A Questions & Answers] KnowTheyself:
I've read that the 16GB version of the Redmi 7A is possible to put a micro SD card and format it as internal storage and that was the reason I've bought it, although I'm not yet sure because I'm waiting to buy a microSD card, it's still on the way.

I want to root it because of privacy reasons and that's the only reason. For now I'm using a VPN to block 99% of the google and xiaomi apps, etc. to the internet this way I got some privacy. I have unlocked the phone too so I did uninstalled several apps from the system using the PC.
[Redmi 7A Questions & Answers] stormy1777:
I don't think that's correct.. I've rooted several 7A, as many others on the forum, just look around, all these posts, many HAVE done based on the topics...

There are few more mysteries, even to experts, so don't feel bad (like how to path boot.img from Magisk, did it for other phones, but not possible for this one for some reason).. agree, there is no current/updated guide that works for everyone, but one can piece things together..

The reason there is no complete guide is not b/c people want to waste your time, they are really trying to SAVE time, however, there are many FACTORS at play, like initial ROM/state of the phone, some Global, some EU, some 10.x other 11.x and so forth, which change over time...

Once the bootloader is unlocked, then one should be able to:

- flash vbmeta.img

- flash twrp (I'm using 3.3.1-1003 'wzsx150').

boot into twrp and flash a properly patched boot.img (that matches your phone), now that's the tricky part, b/c one cannot be re-generated, u'd have to dig through some of the posts, like this: https://xdaforums.com/redmi-7a/how-to/custom-gsi-firmware-t3965820 and find the boot.img that works, it had magisk 19.3 in it, but then update is easily possible.

it's important to flash vbmeta otherwise the "verified boot" will revert things back to a "working state", and you'll lose twrp..

Once my phone got to MIUI 11 it was not possible to root (since there is no boot.img that's patches correctly, and i couldn't do it), so i've flashed the whole phone back to 10.2.5 and from there rooting was pretty easy, the trick is to find the right boot.img.

Good luck.
[Redmi 7A Questions & Answers] KnowTheyself:
Well, if you say so... If you're right then I got the wrong Redmi 7A model. It came with the EU version of the miui.

I already knew the tutorial in the link you gave, but that seems very complicated and I do not really know what's going on there so it's better I do not try it. And if I followed that tutorial I would have to flash the phone again with the miui 10, because I have the 11 now. I already wasted many hours trying to root the phone and I had to flash the rom about 4 times because the phone became bricked. Anyway the tutorials I've followed were not the one in the link above and all the other ones I've tried did not work and yet they claim it does, specially using magisk only, without TWRP.

I'll wait for an easier method than the one you shared, if that will ever happen. For now I just use a VPN, it's the closest thing to root I have found, to deny system and apps permission to the internet.

Thank you
[Redmi 7A Questions & Answers] stormy1777:
btw, the magisk/patching boot.img did not work for me, and was reported in that same thread:

https://xdaforums.com/showpost.php?p=80560039&postcount=206

MDV106 said that both EU and global boot.img were posted in that thread, and i agree i used one of them, not sure exactly which, but definitely it was the Global, not the EU. and i think it's not goot to mix up.. if u have an EU, stick with it, it might impact Wifi or similar "regional" things..
[Redmi 7A Questions & Answers] boody shaban:
Same problem, but it works on mokee

Add-on-su on mokee open source ROM works fine, can enable root from developer options only, magisk and supersu don't work.

I have been trying to make them work but it seems impossible, I have looked in system/xbin and found no su files, maybe the problem is in the meta-INF because it doesn't properly know where to install it.
[Redmi 7A Questions & Answers] stormy1777:
Thanks for this data point, yeah, root was/is also possible with MIUI 10.2.5, I'm sure other ROMs can root pretty easily.. the "goal" of this thread is to somehow figure how to do it on MIUI 11 so we can take the security updates and still retain rootness :) :)