yashsingh1/xdaforums huggingface dataset:
[Redmi Note 10] Zirila:
1.

there is no way around 1 week waiting. if you are unlucky you might have to wait another week. this might happen when you didn't use the phone enough in this week period, or if you reset the mi account.

also, from this unlock faq: https://c.mi.com/thread-2262302-1-0.html

what that means can only be speculated. in worst case this means, if you cover your camera so it is black, or if you have low light conditions in your drawer where to phone lies, or at the moment you press the unlock button, you can't unlock your phone.

or if the front camera can't recognize a face with its AI, so the portrait score is too low, it also might not unlock your phone. or if internet is blocked so it can't send the data home.

imho, this is a privacy nightmare, but there are no details anyware and everybody just seems to accept this insanity.

2.

I don't use aurora services, but webview browser work very well and magisk+microG does work if you get it installed once (this can be tricky because you have to find the right versions and variations that work together). if you choose a ROM that allows signature spoofing it isn't so much trouble, otherwise it gets more tricky. The rest works pretty easy with latest Magisk and MinMicroG (other microG variants I had trouble with).

You always have to reflash: 1) custom 3rd party recovery (like twrp), 2) Kernel, 3) magisk if you flash another ROM. this is always the same on every custom ROM.

3.

nandroid backup and restore is messy with TWRP currently. best way is to do backup with oandbackupX as root and/or a nandroid /data backup without encryption pin. backing up system is useless. in case of restoration install fresh ROM, start it up once for setting up encryption of /data, then restore /data partition.

you can't move /data partition between ROMs, you have to backup your apps with oandbackupX or the like.

nandroid backups on ext. SDCard currently don't work. better make space on your internal memory.

4.

TWRP is currently buggy or features not working correctly. don't expect anything that worked before in non virtual A/B environments to work perfectly fine here. upgrading was always tricky due to A and B slot changes, but thats not all a problem of TWRP but of the ROMs too.

Just read the older posts in the threads of CrDroid and LineageOS and TWRP and you will learn a lot what works and what doesn't work.

5.

Just install a virtual PC with windows 10 and use everything related to Xiaomi software in there. (most things are windows only). you can bridge your usb connected phone to the virtual PC.

There is no need for XiaomiTool V2 if you are on custom ROMs. just use fastboot/adb commands as needed.
[Redmi Note 10] syntheticdingo:
1.

I plan to cover the front camera and not register the fingerprint scanner until I get a custom ROM on it. So I will discover if that is the case or not and let you guys know here.

2.

What is the best way to install microg? magisk module or flashing it via TWRP? I am under the impression one can go both ways about it.

having to flash the kernel is news to me. is there any post in this sub that I can read more about it?

3.

Okay, I will stick with oanbackupX for the time being then, and read about nandroid.

And could you further clarify what you mean by SD cards not working? Is it only for backups or at all? Does that apply to oandbackupX?

4. thanks I will read those posts. hopefully a stable is out soon though.

5.

I have a notebook that I am not sure is capable enough of running a Win VM. So i would really prefer to do these things on my Ubuntu install if I can. Plus it would be a peace of mind knowing i have all it needs and I am not dependent on having Windows machines near me should I have an emergency with the phone.

Is there any issue with XiamiTool V2? Would it not work to do the things i am trying to do?

Thanks in advace for your reply, they are very clarifying in getting me started on this!
[Redmi Note 10] Zirila:
best of luck with unlocking. hope you won't need another week. remember both cameras are eligible for face recognition and brightness measurement.

the way of installing microG may be different for each variation, ROM and phone (remember virtual A/B devices, read-only system, etc.). best way is to read the official installation manual that the microG variant provides. on virtual A/B devices you flash almost everything in Magisk with magisk-modules so you get a systemless patched system. the only thing you flash in recovery, beside kernels and other recoveries maybe, is actually magisk.

about kernels, just read the threads about the two released kernels so far.

well, you might be lucky if you try running the xiaomi software using wine, but it might not work. blame Xiaomi for not releasing all the wanted tools for all OS's.

for unlocking keep in mind that you don't change your setup, keep the same virtual PC, tool, data, etc. in place and don't change anything, they collect also PC data (os, hardware, ip - keep IP the same on PC and phone while unlocking!) for the unlocking process (also a privacy nightmare).. if you want to mitigate that you have to build much more around it than just a virtual pc, though.

I didn't use Xiaomi Tool so I can't really answer that. I think the software is outdated and it's main purpose is to remove some but not all bloatware on non rooted stock rom devices. you can do everything without that tool.

keep in mind that these are unofficial tools and there are many of them, and there are many fake ones uploaded to sharehosters which might be infected with malware. it's hard to find the right sources (but check the official sticky posts in this forum for links) and if you get all these tools by googling around chances are high you get some modified versions with malware.

I'd recommend doing things manually and learning step-by-step how to do things.
[Redmi Note 10] syntheticdingo:
Oh damn, I will definitely cover the back camera after I test it then. Thanks for the heads up.

regarding flashing the kernels, I understand it now. I thought I had to reflash the stock kernel every time. silly me

Do you mean keep the phone connected to the same wifi as the PC during the waiting period? bc otherwise I don't think that is possible at all, given that one must turn off wifi and use carrier data to add the Mi account to device.

I am not sure I understand what you mean :\

And the main purpose of the tool is to unlock bootloaders, install custom ROMs, etc. But you are right, latest version is one year old and I would like to avoid it if I can. Also there are 'official' links to download it from the Github page or the tool website.

I agree with you, I will likely do the bootloader unlock procedure on Windows and then install TWRP via fastboot/adb on my Ubuntu laptop, and move on from there. I believe it is possible to do that much on linux right?
[Redmi Note 10] Zirila:
regarding the IP, I have the suspicion that they (xiaomi) rate the IPs that you use and for some they might block the unlocking attempt. VPN, TOR and other proxies might be suspicious to them and they might block them (this is not necessarily true for all VPNs, TOR nodes, regions, etc., though). There should be no problem with your default ISPs IP address however, but you'll let your pants down using them.

First unlocking on your phone has to be with mobile data, but you could also use VPN,Tor,etc. there, thats why I'm saying it. Some people I've talked to went as far as buying burner sims just for the unlocking process because they are afraid of what china does with their data.

there should be no problem at all if you use normal mobile data for phone Mi account and your default ISP ip on the computer with the unlock tool. They just spy monitor your phone for that week (until you delete the crap) and if the score is good you are good to unlock the phone. nobody besides them knows exactly what they do but you get a clue when you read their Terms of Service. if your ip address varies geographically very much in this week it might also look suspicious, or if the ip-range is used for many different unlocks. all that obviously plays a role in the score at the end.

ok, I didn't use any other tool for unlocking the bootloader than the original and official xiaomi unlock tool. all the rest can be done without additional tools.

the only things you might need is actually MiFlash (to reset/reflash factory ROMs), MIFlash unlock for unlocking the bootloader, and the latest fastboot+adb versions for all the rest.

fastboot+adb requires the correct phone drivers to work on windows, it might be the same on linux. if they are also available for linux it should be ok. for fastboot try the official general android drivers provided by google, they might also be available for linux (or are already implemented)
[Redmi Note 10] syntheticdingo:
I was planning on getting a burner for this. but given the covid restrictions in where I am at, it is gonna be a hassle.

I think Xiaomi does most of that because of the people who buy their phones from China, unlock them, put a custom rom and resell them. I think I should be in the clear though, I wanna get a custom rom working asap, so I wont try using tor and vpn and risk it.

I really don't plan on reflashing the stock rom ever again, unless I absolutely need to. I think i read that there are some cases where one must reflash the stock rom in between custom rom installs(?), but I hope that it is not the case for me. I only plan to try dotos and crdroid, maybe los.

and I would think there is a way to get the drivers for Linux, given that xiomitool v2 does get drivers from somewhere and its available on Linux. I gotta do some digging here though
[General Questions and Answers] Spajdrweps:
Hello. Maybe someone will help me. On my old phone i had video downloader (downloaded videos also from youtube) but that died (some motherboard failure). It was also converter. It had blue icon and when opened it had red interface. Videos was also downloaded by "share" option from youtube. I cannot find it now and i dont remember the name. Cannot find it on Google play because it was downloaded from elsewhere. Please if someone know what app i have in mind tell me. I am out of ideas....
[General Questions and Answers] Musa Besbasi:
To bypass Google account for this model enter this link

New Bypass FRP | SAMSUNG Galaxy J3 Achieve | google account | New Security

Google Account SAMSUNG J3 Bypass FRP SAMSUNG J3 BoostMobile Bypass FRP SAMSUNG J3 SPRINT Bypass FRP SAMSUNG J3 Bypass FRP SAMSUNG SM-J337P UnLock FR

alseery.blogspot.com

100% ...done.
[Redmi 9A Questions & Answers] Rediancool:
I am trying to unlock the bootloader, but official unlock tool can not detect my phone.

I installed the google usb driver. After installing that driver, fasboot detects my phone but the unlock tool can not.

I unlocked the phone previously with xiaomitoolv2, but it doesn't work anymore.

Can you guys recommended me the correct driver please?
[Redmi 9A Questions & Answers] VD171:
Certainly, you have multiple drivera installed.
[G4 Q&A, Help & Troubleshooting] DarrenNewsgroup:
I have used LGUP to revert back to MM (I had a Nougat build that I forgot the lock screen pattern). After going through the initial setup I got the Factory Reset Protection message so I tried the FRP removal tricks. To get one to work I had to downgrade to H815 20c firmware. After doing all that I now got a boot loop. I am back up at v29a using a .TOT file but the boot loop is still there. The screen shows the "unlocked boot loader" screen for 5s then the LG logo screen for 13s then a blank screen for 19s then it all repeats again forever.

Does anyone know what I need to do to fix it?

My when I bought the phone I was told that it had the infamous G4 boot loop fixed so I don't think it is that.

Thanks

Darren
[G4 Q&A, Help & Troubleshooting] DarrenNewsgroup:
My phone is acting really weird now. I managed to use mAid and SALT to get my userdata.img and get my pictures/videos/recordings off the phone. That seems to be the only positive, the rest is all downhill.

My PC is a Windows 10 Home x64 with 16GB RAM if that makes any difference.

I have used LGUP (upgrade and refurbish), various versions of LG Flash Tool (only 2014 did anything, all others had issues with "Failed to Load" messages), LG Bridge, numerous LG USB drivers, downgraded from my broken v29a to 20p, 20d, 20c, 10c and back up to v29a again. I am seeing weird effects such as after flashing a new KDZ and getting to the initial setup I skipped the WiFi and Google logins to get to the basic phone working with ADB and USB debugging to flash TWRP and Magisk.

The phone would reboot when I tried to change the USB settings from MTP. The phone would then loop infinitely whilst connected via USB to the PC but strangely would boot to the normal phone after a few boot loops when connected via USB to a wall charger.

The screen would go blank 2 seconds after getting to the home page of the launcher.

It would also reboot under other repeatable conditions.

I was wondering if certains paritions have been messed up and not even flashing a KDZ (10c, 20c, 20d, 20p) or TOT file (v29a) in Refurbish mode would fix it. I thought a refurbish would put ALL the partitions back to a known state (leaving things like partitions with your IMEI alone). If so, then my phone should then have started behaving itself but it doesn't. After most of these flashings I could actually go through the initial setup stage of the phone but got regular reboots.

Can it really be that I need to setup the WiFi and Google account first? I can't see why that should cause random reboots.

Has anyone got any ideas? Other than the obvious - bin the phone :ROFLMAO:

I managed to update the LAF partition to one that SALT says can now flash partitions but the SALT XDA page says not to flash anything with MM and N. This means SALT is only useful for backups?

Thanks

Darren
[Xiaomi Mi 10T / 10T Pro Questions & Answers] MahathirMohamad_:
Hey guys, currently I'm on 12.1.2.0RJDMIMX with unlocked bootloader, rooted with magisk and TWRP installed. May I know the steps to update to the latest 12.5.1.0.RJDMIXM without losing data and root?

Back then when I was using OnePlus, the procedure to update while rooted was

Download latest update

Boot to TWRP

Flash Magisk Uninstaller ( not sure if this was necessary but did it anyways )

Flash the new update

Install latest Magisk

Reboot

Is the procedure same as for MIUI? Thanks in advance!
[Nook Touch General] nmyshkin:
I'd like to make a few small changes in the framework-res.apk. I thought this might be "easy", but so far it's not.

I decompiled the apk file using apktool and located the two files I wanted to alter in res/layout. I made the changes, then saved the two edited files.

Next I opened the original framework-res.apk archive with WinRAR and then dragged the edited xml files into the proper location ("store", not "normal" or "compress") and then closed the archive.

Finally, I used CWM to copy the new framework-res.apk back to the NST and rebooted.

Boot loop.

Is it not possible to deal with slightly edited xml files in this way?
[Nook Touch General] nmyshkin:
I found a working method: https://xdaforums.com/t/modding-xml-in-framework-res-apk-with-apktool.1545361/post-23589640

But...I want to move the quicknav bar to the top of the screen. The changes I made in the xml files do that, but the status bar covers the top part of the quicknav bar. Ideally I'd like the quicknav bar to cover the status bar (maybe not allowed?), or at least position right beneath it.

The relevant xml code which seems to control the screen position of the quicknav bar looks like this:

<?xml version="1.0" encoding="utf-8"?>
<FrameLayout android:id="@id/quickNavMainView" android:background="@drawable/checker" android:layout_width="fill_parent" android:layout_height="fill_parent"
xmlns:android="http://schemas.android.com/apk/res/android">
<HorizontalScrollView android:layout_gravity="bottom|center" android:id="@id/quickNavHSView" android:layout_width="fill_parent" android:layout_height="wrap_content">
<LinearLayout android:layout_gravity="bottom|center" android:layout_width="wrap_content" android:layout_height="wrap_content">
<ImageView android:id="@id/home" android:clickable="true" android:layout_width="wrap_content" android:layout_height="wrap_content" android:src="@drawable/c_quicknav_home_normal" />
<ImageView android:id="@id/library" android:clickable="true" android:layout_width="wrap_content" android:layout_height="wrap_content" android:src="@drawable/c_quicknav_library_normal" />
<ImageView android:id="@id/shop" android:clickable="true" android:layout_width="wrap_content" android:layout_height="wrap_content" android:src="@drawable/c_quicknav_shop_normal" />
<ImageView android:id="@id/search" android:clickable="true" android:layout_width="wrap_content" android:layout_height="wrap_content" android:src="@drawable/c_quicknav_search_normal" />
<ImageView android:id="@id/settings" android:clickable="true" android:layout_width="wrap_content" android:layout_height="wrap_content" android:src="@drawable/c_quicknav_settings_normal" />
</LinearLayout>
</HorizontalScrollView>
</FrameLayout>

I've changed "bottom" in lines 4 and 5 to "top". That gets the job done, but with the problem mentioned: the status bar covers the top portion of the quicknav bar.

Help?
[Nook Touch General] Renate:
Changing framework or services or whatever you don't need to go to recovery.

They are just part of Android and have no influence on the Linux.

# stop
<do stuff>
# start

How about a screen shot?

I don't even think that I've ever even seen the stock QuickNav.

I'm not sure if this frame is the full screen or what.

How about adding android:layout_marginTop="24dp"?

(That dimension was picked out of the air. YMMV)
[Nook Touch General] nmyshkin:
Thanks for the response. I'll try the marginTop idea. I've been looking all over for something like that but just hadn't generated the proper search string I guess.

Getting screenshots was a lot harder than I anticipated. The quicknav bar seems to disable the side hardware buttons when it is displayed but I finally figured out a way to get reasonable shots. You can clearly see the issue with the status bar when the quicknav buttons are moved to the top.
[Nook Touch General] Renate:
What's the matter? You don't like my AdbGrab.exe (in sig)?
[Nook Touch General] nmyshkin:
You were close (and right, of course)!

The bar becomes a little scrunched for some reason (less white space above and below icons/text) but it just abuts the status bar with android:layout marginTop="18dp". I don't care much about the loss of the white space, so it's on with the rest of my project.

Thanks again for the help.
[Nook Touch General] Renate:
Hmm, something's screwy.

Maybe try this:

<?xml version="1.0" encoding="utf-8"?>
<FrameLayout android:id="@id/quickNavMainView" android:background="@drawable/checker" android:layout_width="fill_parent" android:layout_height="fill_parent"
xmlns:android="http://schemas.android.com/apk/res/android">
<LinearLayout android:layout_width="fill_parent" android:layout_height="wrap_content" android:layout_marginTop="18dp">
<ImageView android:id="@id/home" android:clickable="true" android:layout_width="wrap_content" android:layout_height="wrap_content" android:src="@drawable/c_quicknav_home_normal" />
<ImageView android:id="@id/library" android:clickable="true" android:layout_width="wrap_content" android:layout_height="wrap_content" android:src="@drawable/c_quicknav_library_normal" />
<ImageView android:id="@id/shop" android:clickable="true" android:layout_width="wrap_content" android:layout_height="wrap_content" android:src="@drawable/c_quicknav_shop_normal" />
<ImageView android:id="@id/search" android:clickable="true" android:layout_width="wrap_content" android:layout_height="wrap_content" android:src="@drawable/c_quicknav_search_normal" />
<ImageView android:id="@id/settings" android:clickable="true" android:layout_width="wrap_content" android:layout_height="wrap_content" android:src="@drawable/c_quicknav_settings_normal" />
</LinearLayout>
</FrameLayout>
[Nook Touch General] nmyshkin:
It seems to make no discernible difference. I notice that the line:

<HorizontalScrollView android:layout_gravity="bottom|center" android:id="@id/quickNavHSView" android:layout_width="fill_parent" android:layout_height="wrap_content">

is missing from your version. That, too, seems to make no difference.

There is another xml file which seems to have something to do with the "appicons" (which are just png images stored in the apk, text included):

<?xml version="1.0" encoding="utf-8"?>
<FrameLayout android:id="@id/appIcon" android:layout_width="wrap_content" android:layout_height="wrap_content"
xmlns:android="http://schemas.android.com/apk/res/android">
<ImageView android:layout_gravity="top|left|center" android:id="@id/badgeImage" android:layout_width="wrap_content" android:layout_height="wrap_content" />
</FrameLayout>

Not seeing anything there that jumps out at me. If the android:layout_marginTop="18dp" is changed to something like "100dp" the bar more or less collapses into a fat line, as well as moving further down the display window, so there is some interaction between the "simple" shifting of the vertical display of the bar and the vertical size of the bar itself.

Like I say, it's not a big deal for me. As long as content is not cut off, a slight flattening of quicknav bar is fine.
[Nook Touch General] Renate:
All the tiles are 120 x 112 so that the horizontal scroll is overblown. (5 x 120 = 600).

I was trying to get rid of that.

Use my only Linear Layout and change layout_height="112dp"

For testing purposes you can also add android:background="#cccccc".

That way if the LL expands but the buttons don't you can see the shading.
[Nook Touch General] nmyshkin:
Does the android:background="#cccccc" go in the LinearLayout section or in the overall FrameLayout? Right now it's kinda moot because I can't seem to produce an apk file that does not cause a bootloop. I have a previous trial version with android:layout_ marginTop="20dp" which does NOT produce a bootloop. The file size is about 2874 Kb. Every new version I try to build with Apktool today is coming out around 3366 Kb and they all cause a bootloop. I have no idea what is going on with Apktool, but I'll keep plugging away, with breaks for mental health!
[Nook Touch General] Renate:
In the LL.

When you're floundering in layouts, it's helpful to set some color background for each containing element.

Obviously, on a B&W device you'll not see that, but a screen grab will show it.

(You can just stick to background colors that are differentiable in B&W,)

The FrameLayout is the whole screen which dims the normal screen.

The LinearLayout should be 600 x 120 automatically.

You can even do a reality check by saying (in LL) android:layout_height="500dp".