Database Info

[Q] gramin asusM10 Eglish Rom How to update?

◎Summary：
Welcome to use Garmin-Asus nuvifone M10 updating firmware. You would use this updating program
to update the latest newly version of M10 internal firmware (Firmware and modem). So this will enhance
the M10’s stability and make its performance better. Read the following introduction carefully before
updating.
◎Firmware and Modem Version：
Firmware Version: Garmin-Asus M10_V6.15.0_WWE
Modem Version: V4.7.8-Q2
◎Updating program supports following operation system：
Windows 2000、Windows XP、Windows Vista、Windows7 edition
◎Attention：
1. In order to maintain the computer’s stability and avoid upgrade failures, please close all running programs
before upgrading.
2. Firmware upgrade will erase all data in your device. Use Backup utility to backup your data before starting
update.
((((((3. Do not upgrade your device with the firmware of another language or region.)))))
4. Do not remove the USB cable while upgrading.
5. Make sure M10 is with enough power. Keep the unit turned on.
6. Download updating program nuvifone_M10_V6.15.0_WWE on desktop or PC.
7. Follow below procedures to run updating program.
◎Procedure:
1. Before you start, ensure that your device has at least 60% of battery power left then keep the device on and
turn off the firewall on your computer.
2. Use the USB cable to connect your device with a computer.
3. Ensure that ActiveSync 4.5 or later version for Windows 2000 and Windows XP or WMDC 6.1 or later version
for Windows Vista and Windows7 is installed in your computer.
4. Press Update to start updating.
5. In case of an upgrade failure – please keep USB connected to PC and re-execute firmware, following expert
mode to upgrade.
3 no is not update another region language then how to update English ROM in Italian phone

[Android iA[ JB 4.2.2 Dualboot/Bare metal

Run JB 4.2.2 NATIVE (EFI bios only)
Diualboot with win8/linux/osx. - This is NOT a x86 emu - its bare metal
https://01.org/android-ia/documentation
Required materials:
•1GB or larger USB thumb drive
•A supported target device
•A laptop or PC running Linux, Windows, or Mac OS with working internet connection
Step 1: Back up your existing OS and all data on your device. The Android-IA installer will erase everything and repartition your hard drive automatically.
Step 2: Download the latest installer image for your device from the Downloads page.
Step 3: Prepare the USB thumb drive
Linux users:
•Unzip the downloaded file: `unzip your_installer_file.zip'
•Insert the USB thumb drive into your machine
•Open your terminal application and find the device name of the thumb drive. Run `dmesg' and look near the end for a name like "/dev/sdX" where X is a letter.
•Unmount any partitions that were automatically mounted: `sudo umount /dev/sdX*' (Where X is the letter from above)
•Write the live.img file from the extracted zip to the USB flash: `sudo dd if=live.img of=/dev/sdX bs=1M conv=fsync' (Where X is the letter from above)
Windows users:
•Extract the installer image from the downloaded zip file
•Download "Image Writer" application from https://launchpad.net/win32-image-writer/ and extract it to a folder of your chioce.
•Insert your USB drive into your computer.
•Find the drive letter of your USB drive by opening 'My Computer' on the desktop.
•Run Win32DiskImager.exe from Image Writer's directory.
•In Image Writer's window, select the installer.img you extracted from the downloaded zip
•In Image Writer's window, select your thumb drive's letter that you found in 'My Computer'
•Click "Write" and wait until the process is over.
Mac users:
•Extract the installer image from the downloaded zip file
•Open the Terminal (under Utilities)
•Execute `diskutil list' to get the current list of devices
•Insert your USB drive into your computer.
•Execute `diskutil list' again and determine the device node assigned to your flash media (e.g. /dev/diskN)
•Execute `diskutil unmountDisk /dev/diskN'
•Execute `sudo dd if=live.img of=/dev/diskN bs=1m'
•Execute `diskutil eject /dev/diskN' and remove your flash media when the command completes.
Step 4: Prepare device for installation:
•Set the device to boot from the USB thumb drive (device-specific instructions can be found on the devices page.
•Make sure "UEFI Boot Support" is enabled in the BIOS.
Step 5: Install the system.
• Plug in the USB thumb drive with the Android-IA installer image created in step 1
• Power on the device
• From the boot menu, choose "Install Android to hard disk"
• Wait until the installer finishes
• Unplug the USB thumb drive
• Power off the device by holding down on the power button for 10 sec., then power on the device and choose "Boot Android system" (or let the countdown timer expire)
You're done! Enjoy your Android-IA device.
Click to expand...
Click to collapse
Move post if in wrong section plz...
Sent from nexus 4 AOSP

Hello.
I installed the latest Android-IA (android-4.2.2_r1-ia1) on my Acer Iconia W700, and it works perfectly. The only downside (however, huge one) is the lack of libhoudini - without it half of android apps refuse to load on x86 processor. Which, by the way, scores ~70000 in Antutu (!)...
I searched everywhere, but there's just too little information on both libhoudini as well as Android-IA . Please, can anyone help in porting this library to Android-IA? I know it is not open source, but so are gapps, and Android-x86 already uses libhoudini. So there shouldn't be any real difficulties...
WBR, Draco.

Drakosha said:
Hello.
I installed the latest Android-IA (android-4.2.2_r1-ia1) on my Acer Iconia W700, and it works perfectly. The only downside (however, huge one) is the lack of libhoudini - without it half of android apps refuse to load on x86 processor. Which, by the way, scores ~70000 in Antutu (!)...
I searched everywhere, but there's just too little information on both libhoudini as well as Android-IA . Please, can anyone help in porting this library to Android-IA? I know it is not open source, but so are gapps, and Android-x86 already uses libhoudini. So there shouldn't be any real difficulties...
WBR, Draco.
Click to expand...
Click to collapse
Antutu score 70000!? really? You are using the i5 model?

Drakosha said:
Hello.
I installed the latest Android-IA (android-4.2.2_r1-ia1) on my Acer Iconia W700, and it works perfectly. The only downside (however, huge one) is the lack of libhoudini - without it half of android apps refuse to load on x86 processor. Which, by the way, scores ~70000 in Antutu (!)...
I searched everywhere, but there's just too little information on both libhoudini as well as Android-IA . Please, can anyone help in porting this library to Android-IA? I know it is not open source, but so are gapps, and Android-x86 already uses libhoudini. So there shouldn't be any real difficulties...
WBR, Draco.
Click to expand...
Click to collapse
I remember finding a manual install of libhoudini somewhere but it didnt work. That was with the february version of A-IA, though.
Sent from my 700T using XDA Premium HD app

Drakosha said:
Hello.
I installed the latest Android-IA (android-4.2.2_r1-ia1) on my Acer Iconia W700, and it works perfectly. The only downside (however, huge one) is the lack of libhoudini - without it half of android apps refuse to load on x86 processor. Which, by the way, scores ~70000 in Antutu (!)...
I searched everywhere, but there's just too little information on both libhoudini as well as Android-IA . Please, can anyone help in porting this library to Android-IA? I know it is not open source, but so are gapps, and Android-x86 already uses libhoudini. So there shouldn't be any real difficulties...
WBR, Draco.
Click to expand...
Click to collapse
Did you ever find a solution to this?

DJDrew said:
Did you ever find a solution to this?
Click to expand...
Click to collapse
Hi there
I'd also be glad to hear more about that...From what I could gather so far, there is no fully working ARM translator / libhoudini solutions for android IA. Hence the only solution would be to switch to android x86...

Change dpi and get bluetooth working with android and windows 8.1 at the same time
Do these changes if you are confident in your skills. I'm student and quite busy so if you ask something it can take some time for me to answer. Damages you might do to your system are your own responsibility. I have tested these instructions with Acer W700 on android-4.2.2_r1-ia3 and can confirm that they worked for me.
First changing dpi from original 213 to 160:
1. Get file manager on android like ES file Explorer
2. R/W rights to whole system on android
3. From root go to /system/etc/machine-props/
4. Open acer-w700.prop with ES Explorer and edit line "ro.sf.lcd_density = 213" and change 213 to 160
5. Reboot android and system should now be 160 dpi
Now about that bluetooth. I find it annoying that you have to pair your bluetooth mouse and keyboard again every time when you switch between android and windows 8.1. So I did research and found a way to fix this problem and here's how to do it. I can confirm that this works with Acer bluetooth/cover keyboard and MS Sculpt touch mouse.
1. Pair your bluetooth devices first with android and the with Windows
2. On Windows download PsExec
3.Then from downloaded file copy PsExec.exe in Windows to directory C:\Windows\System32 or to directory where your System32 folder is.
4. Write in the search cmd and run it as administrator
5. Then use command: psexec -s -i regedit.exe
6. Now go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters\Keys
7. From \Keys you can find your paired bluetooth devices. First there is the devices bluetooh mac address and 32 numbers long linkkey. Now write those linkeys and mac addresses up or copy them.
8. Now everything is set on Windows side. Next boot to android.
9. On android you need again for example ES file Explorer and R/W rights
10. With file Explorer fro root go to /data/misc/bluedroid/
11. Open file called BT_config.xml
12. From text find your devices using mac address
13. When you find you devices mac addres scroll down and you should see line with linkkey and 32 number code.
14. Now take that 32 number code you got from Windows
15 You have to change it little so the linkey works and here how it's done:
for example your Windows linkkey is "12345678qwertyuiasdfghjkpoiuytre" now set it as 8 number clusters like this
"12345678 qwertyui asdfghjk poiuytre"
Now you have to reverse those 8 number clusters
Take the set on far right "poiuytre" and mark it like this "po iu yt re"
Now reverse those pairs like this "re yt iu po"
Now "reytiupo" this is the first line in the new linkkey
Do the same for other three cluster. After it's done this example linkkey looks like this "reytiupojkghdfasuityerqw78563412"
16. When you have your modified Windows linkkey ready you can just replace the old one from the file BT_config.xml
17. Now just reboot android and your keyboard and mouse should work.
I've found that sometimes when switching from Windows to android bluetooth doesn't connect. Just reboot android and your bluetooth devices should connect.
I would have posted this on deveopers site where people visit more often but you need 10 posts and this is my first one so if you can you should link my post there so more people can enjoy these instructions.
Thank you for reading this and don't forget to like it :good:

Anyone know where to find the source code for this?

Unlock Bootloader on Android 8/9 (Testpoints, DC Phoenix) [NOT FREE]

Hello,
I just found a way to unlock your bootloader on Android 8 (and possibly 9). This method may also work on other phones if they were released with pre June 2018 Android 8 (where the patch for this "exploit" was release as a Android security patch). Just make sure to use the appropriate versions for your phone (also search for a proper board software for your phone)
If your phone is on Android 8 with a security patch lower than June 2018 or on Android 7, you can just buy 4 credits here, then follow this tutorial.
If you are on a higher security patch than June 2018 (also called GPU Turbo in changelogs by Huawei) or on Android 9 (untested), follow the following steps:
Requirements
DC Phoenix (72h timed license costs 19€)
Accessible testpoints (phone needs to be opened)
Step 1:
Write down your IMEI(s), SN, MAC addresses and the current version you are on (e.g. 8.0.0.385C432)
Step 2:
Buy DC Phoenix and install it
Step 3:
Just follow steps 1 - 4 from this tutorial. If you are having trouble enabling manufacturer mode in step 4 because the rom is in chinese, follow this video which shows where to click. HCU will also output the bootloader code in the log, which you should write down.
Step 4:
Now we are doing things a bit differently than in the linked tutorial above: In DC Phoenix click on "Download files" and search for the Android version you had before downgrading to the chinese Android 7 testrom (e.g. 8.0.0.385C432). If you can't find the same one, use a higher one (focus in the 385 part which is the build, also called B385. also make sure the C number matches because that is the region). You should be able to find the main update.app and one customization update.app file. If you have problems with DC Phoenix because it does not enter upgrade mode, put it there manually (described in step 1 here). Your phone should now boot up. To a working android 8 version. If it boots with a google/android logo and your settings says something like "0QT6" for the version, you need to go to to androidhost.ru and search for your phone. It should yield a few results, just pick the same version (or a higher) you flashed with DC Phoenix (e.g. for 8.0.0.385C432 it's this one). There will be a document detailing how to install it via DLOAD (use force upgrade method). After that, your C numer should be fine and updates can be installed (you can update to android 9, then unlock you bootloader via the code from HCU and then install a custom rom)
That's it basically.

p40 pro downgrade drove me nuts

I have ELS-NX9(C636R4), managed to downgrade from EMUI 12 to 11, but i couldn't downgrade it to 10.1.0.131 or lower to get lzplay working any more. i have spent more than 10 days on it, burned midnight oil and no luck.
1) I tried hisuite 610 with proxy v3.0.1, but site
(https://professorjtj.github.io/v2/)
can only provide 10.1.0.158. no lower version.
if I tried to use the old one (https://professorjtj.github.io/) by fetching individual base, cust, and preload for 10.1.0.114, hisuite always got update EMUI 12 instead of the old roll back version.
2) I found a firmware els-nx9-10.1.0.114(C636E8R4P1) online from this thread: https://forum.xda-developers.com/t/downgrade-els-nx9-from-182-to-131-for-gms.4246379/, put it on sd card, dload, but it always shows the error: incompatible version. why????
can you please shed some light? million thanks

finally I got it work.
1) the MOST important thing:
change your DNS server to 114.114.115.115 and make sure restart the proxy and hisuite again.
it is described here: https://forum.xda-developers.com/t/...news-discussion-support.4346741/post-86489617
and my comments here: https://forum.xda-developers.com/t/...ernet-connection.4032695/page-2#post-87199475
2) I followed the video in post #106.
[badmania98] Huawei P40 (Lite, Pro, Plus) Guides, News, Discussion & Support
Hello! Because I answered to the same questions on different threads, I decided to create this thread, where I will provide my experience to you, in one place. The followings messages (2-7) contain all major info and tutorials links from this...
forum.xda-developers.com
and used: the proxy 2.4.0 and hisuite 550_ove in the attachment.
please make sure: 1) you run both in admin 2) hisuite the setting has proxy 127.0.0.1 and port 7777
basically,
A) you start hisuite first as admin and connect phone with it. then start proxy as admin, clear all fields in package url and package name, then follow the following steps in 3) to select rom, proxy UI will be automatically populated.
B) in proxy, select roll back OS, and click on set up.
C) restart hisuite as admin because it will be closed in step B.
3) then used the following version 10.1.0.122 from https://professorjtj.github.io/
by choosing model: ELS-N29, region C636 and target version: 10.1.
later now lzplay worked fine. also notice phone will lose usb connection capability after the downgrade, thus I needed to use huawei nm card for later store installation usb capability will be resumed in the future after phone update to emui 11.0.0.249 version

for my own record ELS-NX9, C636R4, the following package urls are package names:
base:
http://update.dbankcdn.com/download/data/pub_13/HWHOTA_hotaMigrate_900_9/e3/v3/26d5deaede104f5fb6055f988d7eb62a/
ELS-LGRP4-OVS 10.1.0.122
393319
cust:
http://update.dbankcdn.com/download/data/pub_13/HWHOTA_hotaMigrate_900_9/03/v3/55c56bb1de574079b24b990b8b289251/
ELS-N29-CUST 10.1.0.7(C636)
384169
preload
http://update.dbankcdn.com/download/data/pub_13/HWHOTA_hotaMigrate_900_9/90/v3/32563083177f4d25a05fb69b252f1470/
ELS-N29-PRELOAD 10.1.0.1(C636R4)
382875

damn, after upgrade to EMUI12, I got the error : the device is not play protect certified
try this, it didn't work:

tried the following steps and it worked again, not sure how long it is going to last:
-turn off wifi
-settings-> apps-> apps -> show system processes(...) -> search google
-google service framework(version 10), clean cache + manage storage(clear all data) + force stop
-google play service, clean cache + force stop // note: no manage storage in this step
-google play store, clean cache + manage storage(clear all data) + force stop
-reboot
-settings-> apps-> apps -> show system processes(...) -> search google
-google play service, clean cache + manage storage(clear all data) + force stop
-reboot
-enable wifi
the above steps are from this magic video:

How To Guide How to un-freeze an unresponsive Samsung Galaxy A32 5G with reboot, reset, factory reset, odin mode, download mode, android recovery mode & debug mode

Recently I had to replace my Samsung Galaxy A32 5G under warranty (losing all my sdcard0 data) because my previous unrooted free T-Mobile A32-5G was frozen, so what I want to do for the future is document, in words, the exact steps to copy data off and to unfreeze & reload new firmware onto the unrooted T-Mobile SM6U I have, for me in the future (if needed) and for others (if they need it).
For the hardware modes below, I'm heavily borrowing from this YouTube video titled
Samsung a32 5g Hard Reboot - Download Mode​
But I'm doing all the steps myself and writing them up step by step so they are extremely clear to anyone (and I'm adding information).
Wake
Click power button to wake the phone (assume this fails)
Shutdown or Restart
Hold both volume down & power button to shutdown/restart (assume this fails)
Fastboot Mode
Connect the A32-5G to the Windows PC via USB
C:\> adb devices
C:\> adb reboot-bootloader
In red, "fastboot mode... " shows up on the phone
You can now run fastboot commands, such as:
C:\> fastboot flashing unlock
Debug Mode (mandatory)
Settings > About phone > Software information > Build number (press 7 times)
This enables Developer mode (if you don't already have it enabled)
Settings > Developer options > USB debugging = on
Settings > Developer options > Disable adb authorization timeout = on (otherwise authorization is revoked in 1 to 7 days)
Settings > Developer options > Default USB configuration = Transferring files
Settings > Developer options > Stay awake = off (but know this exists to turn it on if your screen becomes cracked)
Debug Mode (optional)
Settings > Developer options > Wireless debugging = on
Settings > Developer options > Quick settings developer tiles > Wireless debugging = on (that adds a brand new tile to your pulldown area)
Permanently add that new "Wireless debugging" tile to the front of your swipe-down quick tiles since this button goes off whenever Wi-Fi is turned off
Android Recovery Mode
Hold both volume down & power until the screen cycles past the poweroff/restart screen to a black screen and then hold both volume up & power until the phone cycles past the "Secured by Knox" screen and keep holding until you see Android Recovery mode which has the following options, selectable by your volume button and executed when you press the power button with any selection below highlighted.
The screen will be black with orange writings saying "Android Recovery Mode" and the following options...
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Mount /system
View recovery logs
Run graphics test
Run locale test
Power off
Repair apps
Recovery mode (using the PC)
C:\> adb devices
C:\> adb reboot recovery
That will put your phone into recovery mode
Download mode (aka Odin mode)
With the phone turned off, press & hold the volume up & volume down & power buttons and plug in a USB cable from the PC at the same time as you're pressing the three buttons to put the phone into Download Mode (also known as Odin Mode).
The screen will turn light blue saying...
Warning A custom OS can cause critical problems in phone and installed applications.
If you want to download a custom OS, press the volume up key.
Otherwise press the volume down key to cancel
Volume up = Continue
Volume down = Cancel (reset phone)
Side key = Show Barcode {IMEI, SN, Device ID}
In summary, my last A32-5G was toast because I didn't know to access it from the computer with USB debugging on, nor did I know how to reload the firmware, so I don't want that ignorance to happen to me or to anyone else moving forward - which is why this thread is created so we can all pitch in.
What we need to add to this are the steps to access an A32-5G phone to mirror it over USB using FOSS scrcpy tools when the screen is unresponsive, or at least to copy the data off the sdcard0 but that will be only for those who already had the foresight to set USB debugging on permanently.
1. First let's outline all the ways to get the Galaxy A32-5G into debug mode, odin mode, download mode, factory reset mode, android recover mode, etc. - all of which I tried today.
2. Then let's run through a firmware recovery process using Odin & Samfw - which I have never done so I rely heavily on others.
Note the "official" ODIN is here for flashing stock firmware.
3. Then let's recover Samsung firmware again, this time using Odin & Frija - which I have never done but I will try soon.
4. Then let's cover how to mirror your screen over USB (and later, over Wi-Fi) - which I do all the time.
5. And then let's cover how to mount the Android file system
(both sd cards) over Wi-Fi as Windows drive letters using WebDAV - which I do all the time.
6. Then let's add a section on how to recover your old adb authentication keys if they have expired so that you can again trust the computer.
Linux = ~/.android/{adbkey,adbkey.pub,adb_known_hosts.pb}
Windows = C:\Users\you\.android\{adbkey,adbkey.pub,adb_known_hosts.pb}
macOS = ?
Android: /data/misc/adb/adb_keys
7. I don't know if the A32-5G SM6U can be rooted yet, but if it
can be rooted, I'll likely add a section on how to root it after that.
This is required reading to understand the terminology, all of which is new to me (and likely to those of you who read this).
And this is required reading for the OEM Unlock option.
--
If you've enjoyed it or it has helped you, a thumbs or or thanks is always appreciated! Feel free to share and link to this thread for newbies to messing with Android devices like I am.

Here is how to download firmware using SAMFW & how to flash with Odin. (make sure you get the right odin!)
The assumption is the first post was followed which is to proactively:
1. Turn USB debugging = on
2. Connect by USB cable once to a trusted PC & save the authentication
3. Turn off the automatic release of those authentication keys
4. Set the default USB mode = file transfer
Click to expand...
Click to collapse
WARNING: Everything below is a work in progress for the step-by-step tested procedure to download the firmware for the T-Mobile USA Samsung Galaxy A32 5G using Windows 10 as shown below.
Determine the name, model, and baseband version
Settings > About phone > Model name Galaxy A32 5G, Model number SM-A326U
Settings > About phone > Software information > Baseband version = A326USQS8BVJ1
With that information, get the latest Samsung firmware
Frija is one way to download the latest Samsung firmware
But my first test was with https://samfw.com/
In the SamFW web page on Windows 10, enter the device name or model code = SM-A326U / Galaxy A32 5G
That brings you to here which has hundreds of files, many with the designation "A326USQS8BVJ1" and some for Android 12.
https://samfw.com/firmware/SM-A326U
I'm not sure which "A326USQS8BVJ1" "Android 12" file to pick next (is there any way to intelligently choose from the many that do exist)?
Most (if not all) are USA files, so I arbitrarily selected one of the "AIO" CSC (whatever that means) files and that brings up three files that are for Android 12, the latest being:
Build Date = 20221012183750
Download the firmware flash for Samsung Galaxy A32 5G with the code is SM-A326U. This firmware for the region with CSC code is AIO (AIO - United States). Please make sure the code is correct. You can check model code in Setting - About, in Download mode or you can find it by flipping your phone or among the things you found in the box. This product PDA version is A326USQS8BVJ1 and Android version is S(Android 12). This firmware size is 5.83 GB.
This firmware is official from Samsung Cloud Server. Of course, we recommend you are using official Samsung tool like Samsung Smart Switch or Samsung Kies. Samfw.com will not responsible for any damage caused by using the files on this website
AP VERSION A326USQS8BVJ1
CSC VERSION A326UOYN8BVJ1
ANDROID VERSION S(Android 12)
BIT (BINARY/U/SW REV.) 8
SIZE 5.83 GB Full Files
MD5 9019690daf609d85d21bbf6eccebb9b8
Click to expand...
Click to collapse
That process of creating the firmware took me an hour and perhaps a bit more as it automatically generated a "A326U_AIO_A326USQS8BVJ1_fac.zip" file of 5.83GB size which I then had to manually download when it was finally 100% finished, creating.
Name: Samfw.com_SM-A326U_AIO_A326USQS8BVJ1_fac.zip
Size: 6259616116 bytes (5969 MiB)
SHA256: 89B5CF61033173BAFABBF7E7980F7FE1F8F43D88AD99C82729A4643884E5045B
Can someone advise me as to what's the next step?
OK. This seems to be the next set of steps.
1. Extract (unzip) that Samsung firmware zip archive.
Application Processor (or PDA)
AP_A326USQS8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT_meta_OS12.tar.md5 (6,331,637,961)
Bootloader
BL_A326USQS8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5 (2,959,548)
Core Processor
CP_A326USQS8BVJ1_CP23036338_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5 (41,666,760)
Consumer Software Customization
CSC_OYN_A326UOYN8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5 (86,405,314)
HOME_CSC_OYN_A326UOYN8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5 (86,384,839)
USERDATA_AIO_A326USQS8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5 (887,490,760)
_FirmwareInfo_Samfw.com.txt (719)
Note that nowadays, the CSC contains the Partition Information Table file (PIT) in most cases, but you might have a PIT file if not.
Also note the difference between the CSC and the HOME_CSC where you can only burn one, not both.
CSC = Updates the firmware using the PIT which means it wipes the device entirely and reformats the super partition containing everything from /boot, /system and /vendor
HOME CSC = updates the firmware but without the PIT file so that it does NOT wipe the device
2. Download the Windows Samsung Odin Tool 3.13.1
Name: Odin3_v3.13.1_3B_Patched_Samfw.com.rar
Size: 1080120 bytes (1054 KiB)
SHA256: 796DBCD0A2262228AF0492B69BCFF0555CDC9AFE422045BC295BB2ABF74FF107
3. Extract that Odin RAR file (I used 7zip).
Name: Odin3 v3.13.1_3B_Patched_Samfw.com.exe
Size: 3172864 bytes (3098 KiB)
SHA256: 1E84628BD5EF44EB6A00954A7DE5445375C953879F889EF82CB73DB0358CEEAF
4. Run that unpacked executable file on Windows with its associated ini file in the same directory to make sure it brings up the Odin GUI which makes no sense to a noob like me. (Need to add more here since this is a critical step in the process which has no good instructions yet). OK. I think I got it. See Odin file upload steps below.
5. Put the Samsung A32-5G into "Download Mode" by holding volume up, volume down, and power and then right away plug in the USB cable from the computer port such that all four are done simultaneously.
Immediately this puts the phone screen blue which is apparently Download Mode (aka Odin Mode) which will say...
Warning A custom OS can cause critical problems in phone and installed applications.
If you want to download a custom OS, press the volume up key.
Otherwise press the volume down key to cancel
Volume up = Continue
Volume down = Cancel (reset phone)
Side key = Show Barcode {IMEI, SN, Device ID}
6. In the Odin tool on Windows 10, you have two use models, the first of which is to add the five BL, AP, CP, CSC, and USERDATA files separately, or together as one HOME_CSC file.
I don't know where to load the HOME_CSC file so I'll load the five BL, AP, CP, CSC & USERDATA files separately into the Windows Odin GUI (the CSC and HOME_CSC being different in that the home version is said to not wipe user data).
In Windows Odin, click the BL button and navigate to the file named BL_A326USQS8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5 file.
In Windows Odin, click the AP button and navigate to the file named AP_A326USQS8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT_meta_OS12.tar.md5 (notice this will take a while as this is the largest file).
In Windows Odin, click the CP button and navigate to the file named CP_A326USQS8BVJ1_CP23036338_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5
In Windows Odin, click the CSC button and navigate to the file named HOME_CSC_OYN_A326UOYN8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5 or CSC_OYN_A326UOYN8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5 (the difference is said to be the HOME version doesn't wipe user data clean).
In Windows Odin, click the USERDATA button and navigate to the file named USERDATA_AIO_A326USQS8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5 where the "home_csc" is said to not wipe userdata but the "csc" will wipe user data.
7. Make sure re-partition is NOT ticked in the Windows 10 Odin GUI "Options" tab which has the following settings by default
[x] Auto Reboot
[_] Nand Erase
[_] Re-Partition
[x] F. Reset Time
[_] DeviceInfo (mine is grayed out)
[_] Flash Lock
8. In the Windows 10 Odin GUI, with the phone connected to the Windows 10 PC in blue Download Mode (aka Odin Mode), now click the Odin GUI START button to begin reflashing.
Please improve if/when you test this out as I only ran up to the last steps but I did not actually install the firmware.

Here (will be) how to download firmware using Frija & flash with Odin.
[Frija is the wife of Odin in Norse Mythology.]
WARNING: Everything below is a work in progress for the step-by-step tested procedure to download the firmware for the T-Mobile USA Samsung Galaxy A32 5G using Windows 10 as shown below.
This is a work in progress... to be updated as I test it and document the steps.
Please improve if/when you test this out as I only ran up to the last steps but I did not actually install the firmware.

Here is how to mirror the phone on the desktop over USB or over Wi-Fi using the FOSS scrcpy software.
1. Read the FOSS scrcpy readme explanatory file.
[https://github.com/Genymobile/scrcpy#readme]
The two fundamental steps are
C:\> adb devices
(That should report the adb-name-of-your-android-device.)
C:\> scrcpy -s adb-name-of-your-android-device
(That should mirror your phone onto the PC over USB or Wi-Fi.)
2. Download both the adb & scrcpy commands from this zip file.
[https://github.com/Genymobile/scrcpy]
Note that you can use any adb from anywhere so if you already have adb from Android Studio, then use that if you want to.
3. Turn on USB Debugging & default mode is file transfer.
4. Connect your Galaxy A32-5G to the PC over the USB cable.
The notifications should say "USB for file transfer".
5. For this test, I purposefully turned off Wi-Fi on the phone so that the connection would only be via USB cable.
6. If necessary install Windows drivers to ensure the phone shows up as "Galaxy A32 5G" on the Windows network.
6. Run the adb daemon and obtain your device name over USB.
C:\> adb devices
You should see something like:
ABCD##ABCDE device
x. Run scrcpy to mirror the device onto your Windows 10 PC.
C:\> scrcpy -s ABCD##ABCDE
Where the "1ABCD##ABCDE" is the unique name as reported by adb but if you only had one device connected to the adb daemon, you don't even need that '-s' option; yet it's a good habit to use it.
At this point all the following work seamlessly together
Your PC will show what's on your phone screen.
Your PC mouse will manipulate your phone screen.
Your PC keyboard will type into your phone screen.
Your PC & Android clipboards will be interchangeable.\
Here are some useful things you can do with scrcpy.
To take a movie of the entire session (on either USB or over Wi-Fi):
C:\> scrcpy --record foo.mp4
C:\> scrcpy -r bar.mkv
To perfectly screenshot just the phone window on demand in Windows:
C:\> Irfanview
Irfanview:Options/Capture Screenshot > (o)Foreground window - Client area
File name: capture_$U(%Y%m%d_%H%M%S)_###
(Or you can automatically capture every half second or whatever)
DETAILS:
1. Install adb on Windows as per instructions here.
<https://www.xda-developers.com/install-adb-windows-macos-linux/>
<https://dl.google.com/android/repository/platform-tools-latest-windows.zip>
<https://dl.google.com/android/repository/platform-tools_r31.0.3-windows.zip>
Note you do not need to be root on the phone nor admin on the Windows PC.
Note: You can skip this step if you ONLY want to run scrcpy as
scrcpy comes with its own adb which works fine for that purpose.
2. On the phone, check if you have Developer Mode turned on.
Settings > About phone > Software information > Build number
If you tap once & it says "Developer mode has already been turned on"
then you don't need to tap it 7 times to turn Developer Mode on.
3. On the phone, enable the USB Debugging mode option.
Settings > Developer options > USB debugging = on
4. Connect your phone via USB to the PC & run a quick test.
C:\> adb devices
On Windows you will see some debugging information:
* daemon not running; starting now at tcp:55555
* daemon started successfully
List of devices attached
ABCD##ABCDE unauthorized
On your phone’s screen, you should see a prompt to allow or deny USB Debugging access which you should grant permanently for this computer so that when the screen is broken, it will still connect!
Grant USB Debugging access when prompted (and tap the always-allow check box if you want).
Then run the command again:
C:\> adb devices
List of devices attached
ABCD##ABCDE device
5. From the PC you should now be able to access even the phone root filesystem.
Optional test:
C:\> adb pull /system/etc/hosts .\hosts.txt
[That should copy the Android hosts file over to your Windows machine.]
Find the number of packages you have which have "google" in the name.
C:\> adb shell pm list packages google | find /c /v ""
6. And from the PC, you should now be able to bring up Android Activities.
Optional teset:
Bring up the gms "Reset AD ID" Activity on Android from Windows:
C:\> adb shell am start -n com.google.android.gms/.ads.settings.AdsSettingsActivity
That should pop up the "Reset AD ID" settings page on your phone.
[GMS is a set of "google mobile services" products native on Android.]
You can close that page on Android from Windows by running this:
C:\> adb shell am force-stop com.google.android.gms
Which you can put into a "closegms.bat" one-line file for convenience.
7. Obtain the Windows "Screen Copy" code to mirror the Android screen.
<https://www.khalidalnajjar.com/take-screenshots-of-secure-conversations-on-android/>
<https://github.com/Genymobile/scrcpy>
Save to C:\installer\editor\android\scrcpy\scrcpy-win64-v1.23.zip
Name: scrcpy-win64-v1.23.zip
Size: 35446869 bytes (33 MiB)
SHA256: D2F601B1D0157FAF65153D8A093D827FD65AEC5D5842D677AC86FB2B5B7704CC
Extract to C:\app\editor\android\scrcpy
Note there is an adb.exe which comes with that zip file
You can now interact with your phone using the Windows kebyoard & mouse
11. To record a mirrored Android session as an MP4 video run this:
C:\> scrcpy --record file.mp4
C:\app\editor\android\scrcpy\scrcpy-server: 1 file pushed, 0 skipped. 1.4 MB/s (41123 bytes in 0.027s)
[server] INFO: Device: samsung SM-A326U (Android 11)
INFO: Renderer: direct3d
INFO: Initial texture: 720x1600
INFO: Recording started to mp4 file: file.mp4
Note you can press control+c to end the recording when desired.
14. If desired, use the TCP/IP Wi-Fi connection between Windows & Android which requires the USB connection first, and then you can disconnect after establishing the Wi-Fi connection.
C:\> adb connect 192.168.1.2:5555
Where 191.168.1.2 is the IP address of your phone on your LAN.
C:\> scrcpy
Or you can establish the Wi-Fi connection from the start but this always requires interacting with the screen first.
(WORK IN PROGRESS TO ADD THESE STEPS.)
I do this all the time so I just need to document it.

This is a placeholder work in progress to document the WebDAV solution which enables you to mount the entire Android file system onto Windows 10 as drive letters (one Windows drive letter for each sdcard).
I do this all the time so I just need to document it.

This is a placeholder for recovering old keys if you no longer have the computer trusted and you can no longer access the screen.
Accessing An Android Device With Broken Screen Via ADB and Unauthorized Machine in 2022
Just as a datapoint, while I use a variety of adb implementations, I looked for these stored keys and found the files, albeit they were rather old.
adb shell ls /data/misc/adb/adb_keys
Directory of C:\Users\username\.android
11/25/2022 03:39 PM <DIR> .
11/25/2022 03:39 PM <DIR> ..
12/14/2020 01:27 PM 1,732 adbkey
12/14/2020 01:27 PM 709 adbkey.pub
11/25/2022 03:39 PM 936 adb_known_hosts.pb
08/06/2022 08:16 AM 185 analytics.settings
12/16/2020 12:37 AM <DIR> avd
12/14/2020 04:57 PM <DIR> breakpad
08/06/2022 09:15 AM <DIR> cache
12/14/2020 01:26 PM 2,107 debug.keystore
12/14/2020 01:29 PM 0 debug.keystore.lock
12/16/2020 12:36 AM 4,640 emu-last-feature-flags.protobuf
12/16/2020 12:36 AM 67 emu-update-last-check.ini
12/16/2020 12:37 AM 119 maps.key
12/16/2020 12:36 AM 171 modem-nv-ram-5554
12/14/2020 12:59 PM <DIR> studio
10 File(s) 10,666 bytes
Note that I do not use the adb inside of Android Studio much, since any adb works for what I use it for, so this is probably a feature of AS perhaps?
Do you think _old_ keys would work in an emergency situation?
This is something we should flesh out for the general user.

TimmyP said:
If you have bootloader version 3 or lower (probably not anymore, 5th number from right in baseband version) look at this thread: https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-a32-5g-mediatek.4286631/
Click to expand...
Click to collapse
I really would like to try to root my T-Mobile Samsung Galaxy SM-A326U.
Unfortunately, my baseband is A326USQS8BVJ1 where the 5th character from the right is {8} (which is a lot bigger than 3).
In Android 12 Settings > About phone > Software information >
Service provider software version =
Current CSC = SAOMC_SM-A326U_OYN_TMB_12_0008TMB
Best CSC for SIM card 1 = TMB
Best CSC for SIM card 2 (if dual SIM is possible) = TMB
Factory CSC that cannot be changed = TMB
The CheckFirm Android app by Bluesion reports
SM-A326U (TMB)
Latest official firmware = A326USQS8BVJ1/A326UOYN8BVJ1/A326USQS8BVJ1
Likewise Windows Frija & BitFrost tools report similar information:
Model = SM A326U
CSC = TMB
Version = A326USQS8BVJ1/A326UOYN8BVJ1/A326USQS8BVJ1
Size = 5970 MB
OS = S(Android 12)
Filename = SM-A326U_2_20221020211950_3bw6oqi4sf_fac.zip.enc4
Windows Frija downloaded that firmware for me which resulted in:
Name: SM-A326U_2_20221020211950_3bw6oqi4sf_fac.zip
Size: 6260154041 bytes (5970 MiB)
SHA256: 04B3FE98BD303DA3F56DB166838E846C82BEC4D2659569C0BE9025764511464D
Unpacked, that resulted in the following set of SM A326U firmware.
Application Processor (or PDA)
Name: AP_A326USQS8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT_meta_OS12.tar.md5
Size: 6331637961 bytes (6038 MiB)
SHA256: DD2A0B508160644462C7717B8FBBB6AC0288CA64B71E524214855395E6AA9CBD
Bootloader
Name: BL_A326USQS8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5
Size: 2959548 bytes (2890 KiB)
SHA256: D21FEFE7A3C5F5883F0F74A9FCF05709A97CAFAAC129A255480A2BE4195A1C29
Core Processor
Name: CP_A326USQS8BVJ1_CP23036338_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5
Size: 41666760 bytes (39 MiB)
SHA256: D56AD0641F4CAE6E3488CD7842DCEAE91E941091A0E392397A83B8F9ABC92632
Consumer Software Customization (with PIT)
Name: CSC_OYN_A326UOYN8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5
Size: 86405314 bytes (82 MiB)
SHA256: 59EE866BC393D0B3E017712229BDA2F07EA17FB165609D53BE0724EB419291A7
Consumer Software Customization (w/o PIT)
Name: HOME_CSC_OYN_A326UOYN8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5
Size: 86384839 bytes (82 MiB)
SHA256: 865A0563845EA2AB9575C5BDD350A6F07B9B145004B8385DA922CDABAD86E001
User Data (supposedly not used on newer devices)
Name: USERDATA_TMB_A326USQS8BVJ1_CL24355525_QB57258298_REV00_user_low_ship_MULTI_CERT.tar.md5
Size: 861655240 bytes (821 MiB)
SHA256: 7C03E8DA8784F14B6EEC924BF052E6EC30701B3F8FB539F344CD6106E4494FBC
I picked up Windows Frija here.
https://github.com/SlackingVeteran/frija/releases
https://github.com/SlackingVeteran/frija/releases/download/v1.4.4/Frija-v1.4.4.zip
Name: Frija-v1.4.4.zip
Size: 6533283 bytes (6380 KiB)
SHA256: 1067F48DE201E26596F473613CB2CEAC31F1A10550CE6AE352827CCE9FA23161
Unpacked:
Name: Frija.exe
Size: 3445248 bytes (3364 KiB)
SHA256: 76C6E277C9E2D167FCFCF4077D13481111C1750909CDAEFB195480609BC16516
I picked up the BitFrost from here, which does what Frija does.
https://www.ytechb.com/samsung-firmware-downloader/
https://github.com/zacharee/SamloaderKotlin/releases
https://github.com/zacharee/SamloaderKotlin/releases/download/1.0.11/Bifrost_Windows.zip
Name: Bifrost_Windows.zip
Size: 73379150 bytes (69 MiB)
SHA256: 6E8335FD91B0135F92421C54C55D1363D5B246720F492D4B120DB962E8113A40
Unpacked
Name: Bifrost.exe
Size: 462848 bytes (452 KiB)
SHA256: 9A71CF4A6F2C74F15C5C00D9BBB7BE2D68AF3E9A22111D0BAE35BD23713B66AC
Still, I'd love to be able to root this phone (if possible).
I tried the methods to root described here, the first test is
Go to OneClickRoot on any web browser
a. I clicked on "Samsung",
b. and typed the model "SM-A326U",
c. and selected "Galaxy A32 5G (SM-A326U)"
d. Then I selected "Android 12" as the Android version
e. And then pressed on "Verify Device Rootable"
f. It reported "We're Sorry"
"Your Samsung Galaxy A32 5G (SM-A326U) is not rootable."
Then I installed SuperSU on the SM-A326U but it failed.
https://download.chainfire.eu/696/supersu/
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Name: UPDATE-SuperSU-v2.46.zip
Size: 4017098 bytes (3922 KiB)
SHA256: D44CDD09E99561132B2A4CD19D707F7126722A9C051DC23F065A948C7248DC4E
Name: Superuser.apk
Size: 5904943 bytes (5766 KiB)
SHA256: 624B7205B818F1A36877DA0E3575B5B671F4933DFD0FDDF31EE168583C6B2090
Then I installed KingoRoot on both the PC & the SM-A326U, but it too failed to root.
https://www.kingoapp.com/
https://d.kingoapp.com/android_root.exe
https://d.kingoapp.com/default/KingoRoot.apk
Name: android_root.exe
Size: 19128680 bytes (18 MiB)
SHA256: 2F400F0B2FE121B8E5B1415A99DFDA2F5502B7AA2E7002EF6E464F0D587DBA0F
Name: KingoRoot.apk
Size: 6615009 bytes (6459 KiB)
SHA256: E6B2EC7E8663229A0F8DD903D7704CCFDE81F7AE0B1881407E068E63A7F125B8
I've installed Magisk but I'm not sure what the next steps are.
https://f-droid.org/en/packages/com.topjohnwu.magisk/
https://en.wikipedia.org/wiki/Magisk_(software)
https://github.com/topjohnwu/Magisk
Name: Magisk-v25.2.apk
Size: 11278270 bytes (10 MiB)
SHA256: 0BDC32918B6EA502DCA769B1C7089200DA51EA1DEF170824C2812925B426D509
Yet the referenced thread (TWRP for Galaxy A32 5G) implies that we CAN root the SM-A326U where the thread clearly says the SM-A326U US model is supported and the thread even points to a bootloader unlock thread for this USA model over here (Bootloader Unlock for Samsung US/Canada Devices) so this is extremely confusing conflicting information.
This is all very very very confusing.
Either we can root this Galaxy A32-5G SMA326U or we can not root it.
Which is it?
Has anyone been successful with that TWRP/Bootloader unlock process with a bootloader fifth-from-right digit of 8?

NO FOR THE BILLIONTH TIME

TimmyP said:
March 2021 is bootloader 5. The device was rootable though that update. Anything after that no known exploit im sure the people I paid to root mine here would be "advertising" their services if there was.
Click to expand...
Click to collapse
Thanks for the confirmation that anything with a bootloader version of 6 or above (mine is 8) can't be rooted by anyone.
Settings > About phone > Software information > Baseband version = A326USQS8BVJ1
All the articles that say the Galaxy A32-5G can be rooted must have been done using the older bootloader (version 5 or lower).
How to ROOT A32 5G