yashsingh1/xdaforums huggingface dataset:
[Redmi 7A Questions & Answers] stormy1777:
Dear Mofi69 in a small town by Berlin :) :)

Thank you SOOO much for such nice explanations, goes a long way to "trickle" down information to lowly people :) :)

Not moving to ROM 12, due to lack of time to "play with this", have several phones, and it would mean more time spent on it, for no "visible" significant benefit. I don't work for CIA or have anything secret, phone is not used in public places, mostly home, and wifi, so, security is not really an issue as they make it.. switching ROM sounds too many moving-parts and there are TONS of old apps that are already working, many not from app store :) we live with it fine. on a new phone, we'll upgrade, I'm certain ...

in next few days will try the magisk patching again (I was selecting "recovery" due to the ramdisk=no confusion), MAYBE they fixed it, and will produce a valid image, I can't think that the magisk binary would not have full control of their output, so as to make it exactly the right size/layout.. if it fails, will try the python patcher. Thanks so much for this info!!

Stormy.
[Redmi 7A Questions & Answers] MOFI69:
Oh, oh, what kind of garbage did I write there, it comes from when you are not careful in English class ...🥴

Only for you... :giggle:

there is now the "OLD" boot.img, ready pached with the oss-patcher. Please install Magisk via TWRP (magisk.zip), boot.img from

miui_PINEGlobal_V10.2.5.0.PCMMIXM_7380681456_9.0

Important: I cannot test it! Please let me know if it works.

Best regards

Michael
[Redmi 7A Questions & Answers] stormy1777:
Thanks friend for the help!!! Spent few more hours, eventually managed to get it, but not sure HOW :) :)

Starting point, Magisk 21.4/Manager 8.0.4 (not hidden), rooted, boot into TWRP, and flash:

1) patched boot.img from you

2) flash Magiskv22.zip confirmed md5sum:

e14132835b4cc0878639fcf645db479c Magisk-v22.0.zip

noticed that this flashing of zip appears to overwrite the boot.img, ignored it for the time being.

booted OK, said Magisk 22 is installed on the TOP part of the app, BUT, on the bottom, it showed Latest v22, and installed 8.0.4, and said, your device needs more updates, it will now download v22 and install, click ok,

rebooting in 5 seconds, and it comes back to the same spot, again, your machine needs more updates , click OK, again, download, rebooting in 5 seconds, and no change. Clicking CANCEL allows pressing the UPDATE button.. that doesn't help either.

Went to TWRP again, flashed your boot-patched.img , it then appear to not have any Magisk installed at all :) :)

so, installed v22 APK from the running phone, it then showed app/manager v22, but no magisk installed, so recalling that flashing the ZIP made it appear that magisk v22 IS installed, so flashed the ZIP in TWRP and it booted ok, and appears to have v22 installed on both parts of the app.

I'm thinking the steps should be:

1) Install Magisk v22 APK from phone

2) reboot into TWRP and flash the patched boot.img

3) if does not work, flash magisk v22 from twrp..

Sorry for "reinventing" what is known to all :) just couldn't find a "guide" with correct order for Redmi 7a...

Stormy.

PS: @MOFI69 , after an hour or so, got a pop up with long hex value and it said to send 1 BTC there to continue using the phone, I did that, then same message appeared on Android TV, did that, now on the Android Dog Collar :) :) do you think it has anything to do w/that boot.img u patched :) :)

Just kidding friend, have fun!!
[Redmi 7A Questions & Answers] MOFI69:
Since the phone was already rooted (with a manipulated boot.img unknown to me) it can lead to strange malfunctions.

The best and easiest way is to uninstall Magsik (from the manager); REBOOT TO TWRP; INSTALL THE ORIGINAL boot.img and immediately afterwards my leased and immediately magisk V22, no reboot in between.

Then reboot into the system and install the magisk V22.apk, sometimes it is already there as a "shadow", then just start, it installs itself.
[Redmi 7A Questions & Answers] stormy1777:
ok, may try that, only thing is that uninstalling magisk mgr, will lose all the "settings", like which app is granted root, and modules installed?

the way i did seems to work (i don't know exactly the steps yet), but it kept all settings/permissions, of all rooted apps...

Strange is that flashing magisk v22 appear to patch the boot.img, so question is why your boot.img is needed if it gets flashed later... not doubting it is, just asking.. ok, will try another phone and see...

S
[Redmi 7A Questions & Answers] MOFI69:
Yes, the settings of Magisk have to be recreated again, as with a first-time installation. All possibly installed modules must be removed beforehand!

The boot.img is always pached by magisk, which is not possible without a boot.img edited with oss-patcher. The 32 bit ramdisk is missing (the operating system is recognized as this by magisk), so it cannot be installed. The patch only adds an interface so that magisk can install "redirection" for root access.

I think the boot.img you have used so far already contains a permanently installed magisk version, is often done this way on other chinese telephones, it works, but an update of magisk is mostly not possible, hence your problems.

In "my" boot.img there is no magisk preinstalled and updates are possible at any time. Unfortunately, I can't tell you whether your type of installation will work in the long term, you'll notice that with the next update ;-)
[Redmi 7A Questions & Answers] stormy1777:
Thanks for the GREAT explanation!! yes, current boot.img I could not apply magisk updates smoothly, had to always flash from recovery, and that worked fine.

Manage to update without having to reinstall all modules, all remained, vanced, etc. so far leaving it.. I used to have 5 days to play with such things, now, 5 hours is hard to get, naively I expected it to be 5-min :) :)

Also managed to root a totally brand new phone using your boot.img + magisk v22, here one must add vbmeta.img as well as Permissiver_v4.zip, not entirely clear on right order, eventually it worked :) :)

Thanks much to @MOFI69

Stormy.
[Redmi 7A Questions & Answers] MOFI69:
Super that makes me happy!

Then have fun with your Redmi

Best wishes
[MeMO Pad 7 Q&A, Help & Troubleshooting] fakuivan:
I've had this ME176C unplugged and in its box for about two years or so, the battery is almost surely dead. When I got it it would not turn on, even while plugged in it would not display the charging animation. So today I tried plugging a working battery to it and pressing a combination of buttons I do not remember (volume up or down while holding the power button). To my surprise, it turned on, so something kinda worked. Now I'm on this UEFI looking screen, I don't have an OTG adapter in hand so I'm not able to browse the interface. Has this happened to anyone here before? How can I recover this?
[MeMO Pad 7 Q&A, Help & Troubleshooting] fakuivan:
Following the instructions on https://github.com/me176c-dev/me176c-boot#recovery I was able to bring up fastboot. However I'm not able to flash the ESP partition. Any ideas on how I could fix this? Utimately I would like to flash the stock ASUS OS, but I'm not sure how I can do that only with fastboot access.

# fastboot flash ESP esp.img
target reported max download size of 536870912 bytes
sending 'ESP' (33792 KB)...
OKAY [ 1.219s]
writing 'ESP'...
FAILED (remote: flash_cmds error!
)
finished. total time: 1.301s
[Xiaomi Mi A1 Questions & Answers] I need help pls asap:
I attempted to install LineageOS 17.1 on my Mi A1, but while wiping storage, I accidentally also clicked Internal Storage and wiped it too. Now, I tried to restore my backup but when I go to restart to turn on my Mi A1, it gets stuck in a boot loop. I also tried using XiaoMiFlash and the original ROM to get all the firmware settings to stock. Now, I tried also installing custom ROM again, LineageOS 17.1 but it also gets stuck in a boot loop. Is there anything else I can do?? I'm very frustrated... I hope my device isn't completely bricked. Any help is appreciated.
[Xiaomi Mi A1 Questions & Answers] orb3000:
Welcome to XDA!

Its not recommended to open more than 1 thread on same topic, please have a read of the forum rules and most importantly, enjoy your stay!
[Xiaomi Mi A1 Questions & Answers] lafactorial:
It should be ok with mi flash tool
[Xiaomi Mi A1 Questions & Answers] I need help pls asap:
I have already tried that, the only issue now is that the Custom ROM after installing (LineageOS 17.1) will not boot properly. Maybe this is because I skipped TWRP Recovery? Well, I don't know why but TWRP Recovery zip will not copy into phone storage. it is originally .img file, but the guide I'm following has .zip file so I converted into zip via Windows Explorer (file manager). But, it does not copy and when I use img to zip website converter iand it does copy, but it says "invalid zip file format" once flashing.

One thing I should note, the backup does work now. I had a typo when making the folder so it wouldn't work. Backup does work now, but something really stupid is happening. When I go to turn on screen lock, it will keep looping me into "which type do you want to choose, fingerprint + pin, password, pattern" after completing the process. If I don't choose fingerprint, it finishes but the screen lock isn't effective. Any help on this?
[Xiaomi Mi A1 Questions & Answers] User699:
You cannot just convert that image file into a zip file like that.

Where did you get that twrp file from?

If you want to install twrp, you need to flash the twrp.img file via fastboot, then sideload the twrp.zip via trwp.

(maybe just flashing the img file works too, but I often read that you have to do both).
[Touch Pro, Fuze General] Gigs:
Hy guys,

Just to know, I'm coming from my trusty Eten M700. I bought the HTC Touch Pro about one week ago here, in Romania.

And I must say the video playback seems way too sluggish for a phone like this. On the M700, with same coreplayer version (latest), with raw frame buffer and medium quality and no other modification I could play every video I wanted. Including 720x576 xvid clips.

On this one...no matter what I set (QTV, raw frame buffer, direct draw), everything seems a little too sluggish compared to M700.

do you have the same impression, or is it just me?

I just read another thread here about video performance but it had too much dissipated info.
[Touch Pro, Fuze General] P0ll0L0c0:
Which is why it's great that you started a new thread to dissipate the info further. Read the other thread(s) again, this has already been answered and solved within coreplayer.
[Touch Pro, Fuze General] nolovelust:
which topic is it? i have smilar issues
[Touch Pro, Fuze General] Gigs:
Untill now I have found that QTV with Medium acceleration, and dither on has the best performance, anyway less than m700. Setting the buffer to 8000 kb did not had any effect. Still want to hear from another pro owners what they think about this.
[Touch Pro, Fuze General] krabicka3:
I agree, video playback just sucks! I hate Qualcomm processors, Xscale rulezzz!

However when I put QTv, my screen goes black and there's only sound.

How did you achieve to run it on QTv???
[Touch Pro, Fuze General] Gigs:
It depends on what kind of file you want to play with it. On mine, some 3gp and some clips compressed for mobile devices don't show anything on screen. Try to switch to raw frame buffer, and restart core player, maybe it helps?
[Touch Pro, Fuze General] puerrican85:
Unfortunately the HTC Touch Pro is not the mulitmedia phone you want if your looking to run your non-mobile encoded videos. However it still can be a awesome video player if you encode videos to the right dimension and specs.

I took this past Sunday to play around with finding just the right video format and encode settings to play video as close to vga as possible. Unfortunately the Touch Pro can't play videos in full-vga resolution. HOWEVER, it can perfectly play videos in 480x320 which when you compare to a 640x480 video on the touch pro's 2.5inch screen there is no difference in quality what so ever.

When you play small videos on such a small screen you wont notice the difference in the resolution, however comparing a qvga (320x240) to the half vga 480x320 resolution you can definitely see a difference.

I use two different encoders, one being pocket divx encoder and the other videora iphone converter.

I encoded a bunch of animes and movies using pocket divx set to 480x320, 2-Pass, vhq enabled, around 850 video bitrate and 128kb stereo bitrate and all my videos look crisp on the Touch Pro and plays smoothly.

I suggest others to try it out and benchmark the playback yourself and you'll see it'll run at a easy 135%+ which is perfect for 100% smooth playback.
[Touch Pro, Fuze General] puerrican85:
1.) I suggest check two things, one be sure you are running the latest build which I assume you are,

2) under preferences and under the Qtv page look to make sure "Tytn 2 driver mode" is enabled.

3) some builds have a issue of zoomed in pictures to a an extreme amount that only a black screen shows when first installed, set the zoom to 50% and then reset to the normal or best fit.

Hopefully those changes should help you out

UPDATE: Also there is one bug I know of with Coreplayer. When coreplayer is launched and left running in the back (or if still active on screen) should the device go into sleep mode and then come back you will not be able to see any video playing when choosing to start. You'll have to close coreplayer and reopen again, I noticed this the other day and just came into mind when experiencing just now again.
[Touch Pro, Fuze General] Gigs:
I almost agree with you puerrican but I think it's such a burden to reencode....I managed to get easy after I saw that everything encoded with h264, mkv and encoders like this can't be played in the pro. However, everything I had in my computer encoded in divx, xvid, normal things works just fine with the settings I put in some posts above. I just tried 700 MB DVDrip(around 1000 kbit/s and 640x272) and some videoclip(624x352 vbr around 2300kbits) both xvid and they worked ok. 688x400 AVC1 (h264) killed the pro.It's not just the resolution but also the encoder used.

EDIT: just saw the update and I wanted to mention that I'm also using the 1.2.5 build 4506 with tytn 2 mode enabled and qtv on medium selected. And touchflo3d is disabled and I'm using the spb shell (or something like that with icons on screen).

IDEA: I think it would be interesting playing back xvid 640x480 and h264 640x480 to test this idea of mine
[Touch Pro, Fuze General] puerrican85:
Definitely it is pain to go and do that. Plus reencoding speed relies heavily on your pc specs, on a high end specs your looking at around 4-5 mins for a 2-pass encoded video of 24 min length. While a movie length of 90 mins or so your looking at at least 16-22 mins.

So expect much longer wait on a lower end thats not even dual core or lower clock rate.

Until pdas start sporting dedicated gpus from nvidia or other names windows mobile wont ever benefit on being a media playback alternative which is a nice plus for those not looking to carry 2-3 devices for music, pmp, pda, and phone. Wish HTC would look into intel processors for their next unit and possibly throw in a nvidia mobile gpu like the 5500 with a decent amount of video memory. I mean at this point in the technology chain its not even remotely impossible to do so... so whats the hold up with companies???
[Touch Pro, Fuze General] Brendo:
yeah, i have no problem with mp4 at 640x480 (640x360 widescreen). mkv at high res (above 640x480) is a little juttery. my movies are usually 24fps, 1000kbps, 640x360

got same settings as gigs

coreplayer is working on fix for v1.3
[Touch Pro, Fuze General] puerrican85:
I'm at a lost, I tried playing 640x480 videos on my touch pro and it stutters way too much, how are you guys managing to have to it playback flawlessly?
[Touch Pro, Fuze General] toxical:
I dont really get whats good about watching movies on a 2.5 inch screen...do you do that on such a regular basis that this is so important ?

Regarding Video, i just watch some short youtube clips and stuff like that...

Ever tried to watch a full length movie on such a small screen ? I did that on holiday on my ipod and its really hurting the eyes to concetrate on such a small screen for 90+ minutes... not really anything you want to do regularly...besides not reencoded videos take up alot of space on your memorystick...

i dont have a problem with reencoding some videos and stuff, full length movies arent meant to be watched on a phone anyway
[Touch Pro, Fuze General] Mr.Sir:
Well, a 2,5 inch screen is a bit too small, but our Touch Pros have a 2,8 inch screen ;)
[Touch Pro, Fuze General] JIGGY24:
I have a zune and it has a 3 in screen and was perfect for watching tv videos or movies, and thats half the resolution then a TP. Cant wait to get my hand on the TP !!!
[Touch Pro, Fuze General] puerrican85:
To each his own, some ppl like being able to watch videos whenever the call comes. Sometimes when I have to wait for something like a class to start or I'm away from my pc, or even on a airplane or public transportation I like to be able to watch few episodes easily and clearly. A full blown movie yea its gonna be a nuisance for a long time depending on the person. But some are accustomed to it, I for one can easily watch 4-6 episodes in a row without getting any kind of headahce.
[Touch Pro, Fuze General] Brendo:
yep, its quite convient. all in one device. it has tv out as well, so since it is simalar res to tv, it looks great :)

music + movies on phone, no ned for mp3 player. plus i can stream movies off my pc
[Touch Pro, Fuze General] toxical:
yeah i see that there is room for this, but i dont think many people use this so regulary that converting a few movies is that much of a pain. You will save a lot of space on your memorystick as well.
[Touch Pro, Fuze General] TomasNM:
I have modifying 2 regentries and the video is now much better.

Look here:

http://xdaforums.com/showthread.php?t=438318

Using CorePlayer the benchmark was before 75-95%,now 145%. on same videofile - Uncompressed VGA XviD.

Edit... I am sorry. It wasn't working. I just forgot,that I set the video quality to medium before.
[Touch Pro, Fuze General] DSF:
You have to chose Medium Quality on Video Settings (with Qtv selected), otherwise it lags so much ..

Even on medium on motion scenses some frame drops

Video used for tests: RL_XQ_640x480_1500_128.avi (found somewhere here on this forum.. can't remember the topic name :( )
[Touch Pro, Fuze General] Smaniac:
I also use this setting, a few days ago I was watching a 848x4xx concert, and it was playing fine. The quality isn't great, but it's acceptable.

I just had to adjust A/V delay a bit because I'm using A2DP and it was out of sync. But after the adjustment it works great.
[OnePlus 3T Questions & Answers] kridster:
I'm using the LOS 17.1 Official Build for my OnePlus 3T and wanted to upgrade to LOS 18.1 with a fresh start. The device itself was working fine, except for both volume buttons, which don't work for quite some time now. I made a nandroid backup of the LOS 17.1 system.

I wiped everything and clean flashed LOS 18.1 which worked fine. Than I wanted to revert to my TWRP backup of LOS 17.1 which I restored in TWRP. Booting worked, but now my PIN is not recognized properly. This seems to be a common problem with encrypted devices and can be solved by deleting some files:

How to Fix PIN Errors After Restoring from TWRP Android Backups

Making TWRP backups is a must if you're going to be rooting and tweaking Android.

www.howtogeek.com

The problem is, that I cannot boot into neither recovery nor bootloader without using the volume buttons:

Because of the locked state on the system boot I cannot use the extended reboot menu

ADB is also not working, no devices is being detected.

In the boot menu (after cold boot) I cannot select another option except the normal boot

So, how to come out of that pickle?
[Nokia Lumia 1020] DaneGleesak:
Hey there,

Just curious if any one knows what communications bands this devices uses?

I'm trying to get it operating on either Band 4 or Band 13
[Nokia Lumia 1020] Brusterel:
Not really, but I would like to.
[Other SmartWatches] rafrgt:
Hello person my name is Rafael I bought a nubia alpha chinese version watch, i would like to know if there is a developer to help unlock this watch for new functions, mine is a chinese version with 4g in google play has an app but it is downgraded in nubia website has a but asks for a registration with chinese number this application has more functions like some more apps and 7 screens for the clock but this aplicitvo looks pretty buggy i just managed to pass the apps but the screens still not, if anyone can let me know

Nubia apk V5.0.01.0826

http://ui.nubia.cn/app/detail/82

View attachment 5269571
[Other SmartWatches] rafrgt:
nubia site apk

V5.0.01.0826

http://ui.nubia.cn/app/detail/82
[Other SmartWatches] hellraisertg72:
hi!

thanks for the tip/link!

I tried it, but... - how did you manage to start/login to this app? The "older" version does not need any registration (via WeChat for example)...
[Other SmartWatches] DorkyDev:
So this version will allow us to register? I bought the 4G Alpha Chinese Global Edition too, but mine the app's I've tried so far it won't even get past the pairing screen, it just sits there starring blankly at the QR Code and Manual Pairing just gives me a black screen with a blue bluetooth image and pulsing blue circles, but it doesn't do anything else other then that.
[Other SmartWatches] DorkyDev:
Okay still nothing acquire code and zilch

I'm ticked off that I spent $195 on this and can't do crap with it

I'm literally at the setup screen and stuck
[Other SmartWatches] DorkyDev:
So I did discover pressing the toggle wheel 3 to 5 times took me in to the watch skipping past the screen, so is there a way I can set the time.

Or would I be better off returning it for the wifi edition.

Any known american cellular providers who will activate the esim?
[Xiaomi Mi 5s ROMs, Kernels, Recoveries, & Other De] Fasic:
Tanks for this one, before i test it, what is best ROM you all use on mi5s, right now i am on PE-10, didn't update it for like 6 months. Now i want fresh installation, and i don't need latest anything, just OS that works, it is as fluid as it can be. So:

-this

-PE10

-PE11

-Official LoS16

-Unofficial LoS18

-or something else, what is best right now? Did anyone test more then one ROM.
[Xiaomi Mi 5s ROMs, Kernels, Recoveries, & Other De] unicastbg:
Official LOS anything is gone for Mi5s. LOS16 was official, but due to the fingerprint issues it will never get 17.1 or 18.

I personally use LOS16 because everything works. And we still have regular security patches.

I have tried briefly the LOS18 and found it's not to my liking.

This is what I wrote in 18.1's forum (Link) based on my experience:

Well... Not sure if related somehow to Viper4Android, but the fingerprints are getting deleted after some time. And after restart. But when present, I think it unlocks faster than compared to LOS 16. However there are a few design features of Android 11 that made me switch back to 9.

Viper4android currently not working.

Apps that rely on fixed SU folder will fail.

Cannot disable Camera - Lens Cap app.

Cannot record calls. There might be a better app that does it ok, but I haven't searched much.

And finally - cannot limit the battery charge percentage - have it charged to 90% for example. I've tried with Floppy kernel as well.
[Xiaomi Mi 5s ROMs, Kernels, Recoveries, & Other De] unicastbg:
The only thing that I really miss is the EIS that we had in MIUI. But the customization there is very limited compared to Lineage.

I haven't played much with other ROMs, maybe PE has it all sorted out and EIS and the fingerprint reader are both working just fine...