I am trying to convert a non-JP Google Pixel 4a into a JP Google Pixel 4a by changing the model numbers. After flashing the latest stock firmware (Android 13) sourced from [the official website](https://developers.google.com/android/images) , I installed [Magisk v29.0](https://github.com/topjohnwu/Magisk/releases/tag/v29.0) and rooted my Pixel by following [this guide](https://thedroidwin.com/root-android-magisk) . [Rooting using Magisk] 0. Enable Developer Settings 1. Enable USB Debugging 2. Enable OEM Unlocking 3. Unlock Bootloader

fastboot flashing unlock

4. Extract boot.img

unzip sunfish-tq3a.230805.001.s2.zip
cd sunfish-tq3a.230805.001.s2
unzip image-sunfish-tq3a.230805.001.s2.zip
cp boot.img /run/user/1000/gvfs/mtp:host=***/'Internal shared storage'

5. Patch boot.img 6. Boot using patched boot

adb reboot bootloader
fastboot boot patched_boot.img

7. Install patched_boot using Magisk Now that my phone is rooted, I accessed protected system files to overwrite using [this article](https://thedroidwin.com/how-to-enable-osaifu-keitai-in-non-japanese-pixel-devices) . 1. Enable root access

adb shell
su

(Tap 'ok' on Pixel screen) 2. Extract devinfo.img

dd if=/dev/block/by-name/devinfo of=/sdcard/devinfo.img

3. Copy devinfo to PC

cp /run/user/1000/gvfs/mtp:host=***/'Internal shared storage'/devinfo.img ./devinfo.img

4. Open the file using the hex editor

ghex devinfo.img

I am supposed to find my phone's model number and replace it with the Japanese version's, but all I see is 16 bytes corresponding to "ANDROID-BOOT!..." That's literally the only thing in the file. Is this method not universal for all Pixels? What went wrong?

**Treble** Info app shows VNDK level 31.0. But what Android version is that?

I have just bought a second-hand Oppo Find X6 Pro and it has a global ROM on it. I don't know how they did it because there's no global version of the phone. I think they might have tweaked the firmware because everything seems valid, except it hasn't got any updates and its security patch is of June which is pretty behind for this device. This is the version on it: PGEM10_13.1.1.144(EX01). The (EX01) OPPO Reno 10 Pro 5G has it and it stands for a European version, I think. That's why I say they might have tweaked something because even Google recognizes the device as OPPO Reno 10 Pro 5G. > **Check your Oppo Reno10 Pro 5G** > > Google sent a notification to your Oppo Reno10 Pro 5G. Tap **Yes** on the notification, then tap **17** on your phone to verify that it's you. So I wanted to roll back to stock firmware. I downloaded different stock ROMs, but there wasn't any way to flash them on the device. Can someone help me and go back to the stock ROM? - I tried https://oppostockrom.com/oppo-find-x6-pro-pgem10 but didn't figure it out. - I also used the QPST Flash Tool, but the firmware didn't contain anything to open it inside QPST like .hex or .mbn. It just had .elf for the programmer which when I chose it to flash the ROM, it said error FireHose. - The recovery mode also doesn't have a local update and online update. - When I reboot to EDL using adb, it just shows a black screen, but the computer does recognize Qualcomm 9008. I think the recovery is also not stock. I will attach the system information:

Recently I found my old Samsung S8 (SM-G950F) with a broken display. I ordered a replacement part, and it turned out to be an LCD screen, which was different from the original OLED display. Upon changing the screen, the phone enabled it. The backlight and touch screen are working, but the display is not showing anything. I can successfully connect to an external display with USB-C -> HDMI adapter, but the new screen is blank. I tried flashing the OS to "LineageOS 20" hoping to resolve potential driver issues but with no luck. Is there any firmware or particular driver that could help? Anyone had a similar issue? The exact LCD model no: AMB577MQ01 REV 7.2 BH1740 2 YX

I'm dealing with a very lengthy and drawn-out FRP bypass. This Samsung Galaxy A54 (A546V), which is on Android 13, refuses to let me bypass it, and I literally have done everything except for modding the firmware. If I can mod and root the device, I know I can get in and remove the FRP lock within the CM. If anyone can point me in the direction of where I will find a way to root, and/or help me mod the phone firmware. I am pretty sure I have exhausted all of the methods and options available to bypass FRP.

Can't complete the Stock ROM flash on my galaxy grand prime SM-G530H. The following error is shown inside the Odin message box. Added!! Odin v.3 engine (ID:10).. File analysis.. SetupConnection.. Initialzation.. Get PIT for mapping.. Firmware update start.. aboot.mbn NAND Write Start!! FAIL! (Auth) All threads completed. (succeed 0 / failed 1) I hope the problem is with the NAND Write Start!! part. I tried with three of the stock ROMs and getting the same result. What should I do to overcome this problem?

I have A546U Galaxy SM-A546U. It is frp locked so I am trying to figure out the easiest way to get around frp , I've recently half bricked the phone all ready using odin3 , after a week of staying at it got the phone back to normal frp lock . Anyone please be kind enough to help me ? Ty

Can I flash Sony Xperia 1 V US modem firmware onto Sony Xperia 5 V (XQ-DE54) to get all US bands?

I have located a firmware package of my tablet brand. It also has the same build number. The variant number is also identical to mine. I extracted the zip file and got a boot image. Now reassure myself all was going to be ok; I tried to open it on win 10 PC. The PC, responded with an error message. "The file is corrupt." I have not installed it and am hesitant to use it. Thus, my question above. I intend to use ADB to and Magisk. I have no recovery TWRP for my build and brand tablet.

I have installed several custom Android ROMs in the past, but I'm by no means an expert, so please bear with me if I do something really stupid. I recently bought a new-old-stock OnePlus 6T with the intention of installing postmarketOS on it. I took it out of the box, set up Android, unlocked the bootloader, and so far all was going according to plan. postmarketOS installation with full-disk encryption seems to require TWRP, so I went to the TWRP download page. The latest version of TWRP would not boot with the version of the firmware currently on the device, instead simply showing the Fastboot logo indefinitely until force restarted. I downloaded the oldest version of TWRP available from the page, and that booted successfully, so I installed it to the recovery partition and immediately took a backup of everything TWRP would let me back up, then copied that backup onto my computer, just in case. I then trial-and-errored several more versions of TWRP to see the newest one that would work (3.4.2), and it did not appear to have the command the postmarketOS installation guide uses for partitioning (sgdisk) installed, so I assumed that in order to install it I would need to upgrade to a newer firmware so that I can boot a newer TWRP. I tried to download firmware updates via the system update in Android settings -- no luck, it says I'm up to date, but that can't be right! This is a six-year-old device; I guess the update servers are down. I then followed these two guides to download and flash a firmware update directly: https://xdaforums.com/t/guide-extracting-the-latest-oneplus-6t-firmwares-from-rom-update-package.4376047/ https://xdaforums.com/t/guide-flashing-the-latest-firmware-updates-to-your-oneplus-6t.4376055/ All seemed to go according to plan. I used AuroraDroid to download the app that downloads the firmware file, extracted the payload, rebooted into fastboot, flashed the various firmware parititions, and rebooted again. I had to delete "--slot=all" from all partitions except the modem for fastboot to do anything at all with them, and several partitions failed to write because they were "critical partitions" that the device refused to overwrite, but I thought nothing of it and rebooted anyway. I then got a big scary popup on the phone saying the device was corrupt and it refused to boot Android. Guess that firmware update was bad! I quickly booted TWRP from the recovery partition and restored the backup I took earlier. The restore got to 98% and failed (I don't remember the error message but it involved tar somehow), but I rebooted anyway. Now the phone will not boot anything other than fastboot! If I turn it on it goes directly into fastboot, and if I tell fastboot to "START" or "Reboot reovery", it just reboots into fastboot again. If I try to send it a firmware image via fastboot boot, it fails with Failed to load/authenticate boot image: Load Error. I do not want to send this factory-new device to E-waste only hours after I took it out of the shrink wrap! Can anyone help me? (P.S. I asked this exact question [on XDA as well](https://xdaforums.com/t/bricked-my-6t-with-a-botched-firmware-update-please-help.4704781/) in the hopes of a faster response.)

I have a baseband.bin firmware of device Samsung Galaxy M21. I want to extract it into raw code format and re-edit it upload it to the phone. Please help me, i don't know how to extract this firmware file into raw code format.

I want to change the CSC code for my Samsung Galaxy S21 Ultra for less bloatware, and Google Assistant available. The firmware I wanted to update: . My phone's current build: . I used Odin v3.13.1, but I tried multiple versions, as well as the patched one, with failure. Here is the full traceback of the error:

Odin engine v(ID:3.1301)..
 File analysis..
 Total Binary size: 12081 M
 SetupConnection..
 Initialzation..
 Set PIT file..
 DO NOT TURN OFF TARGET!!
 Get PIT for mapping..
 Firmware update start..
 NAND Write Start!!
 SingleDownload.
 abl.elf
 xbl.elf
 FAIL! (Auth)

 Complete(Write) operation failed.
 All threads completed. (succeed 0 / failed 1)

I also tried unlocking the bootloader, but it didn't work.

I've had my Note9 for a year and even though I thought I would love it, am now being driven mad by the display/writing surface wrapping around the edge of the phone. There must be a way to increase the Bezel size through software! I have searched for apps and settings, but I can't find a way to make the screen smaller. Most apps can run in Pop-up (Windowed) mode, but it is a pain in the ass to get there and it seems like there is no way to make it the default mode to run the app in. I tried "one-handed mode" but not only is it not movable or resizeable to put it in the centre, when it is against one edge, it puts the edge right around the curve of the phone face, so that doesn't help either! It's super frustrating not being able to use the pen (or even your finger sometimes) up to the edge of the screen; there must be a fix! Anyone know a trick to fix this in Android?

Is it possible to run a Firmware Over The Air update server? and is it possible to configure stock devices to point at it?

This question is from a malicious viewpoint to see if its possible that it happened in my case I have got answers before that if my bootloader is locked then a factory reset(/even reflash stock rom) is the way to ensure its clean, how true is this and to what extent? I was thinking of hardware key attestation(/binwalk and hexdump) to detect it but it is hard and i have no idea how to remove it(may require replacement/reverse engineering)? My unlockable phones keeps getting hacked(local media leak, keylogger and sim issues) but shows no sign of compromise so i suspect malicious firmware The reason i suspect its the bootloader because it didnt happen on my phone which didnt have an unlockable bootloader(phone 1) and happened on the phone which had an unlockable bootloader(phone2) (My friend had borrowed both my phones for less than a day and i had noticed there was a spy app in phone 1 and nothing bad in the other phone which had an unlockable bootloader(phone2)) but since it shows symptoms of getting hacked have factory reset and reflashed the stock rom multiple times with no success Does the user-settable root of trust even matter in this case or can the entire thing be bypassed itself by backdoored firmware or such? What are my options in this case? The reason i post this is because it happened for the second time in my 3rd phone (which has an unlockable bootloader and which i had not left alone for more than 4hrs) and i have tossed both previous phones due to age I suspect an evil maid attack and i have not found much info about it on android in google so i am curious to know more

I have a bricked TV Box MeCool HM8 and I need to restore it to factory settings. Unfortunately, I have the stock firmware in zip format. I need to convert it into image format to be able to use an SD card for recovery. Any help, or advice, would be appreciated.

Can someone help add a prebuilt APK to an Android system.img for me? I’ve obtained boot.img, system.img, etc. (the full firmware) from the manufacturer of the device. I’ve been trying for hours to add the .apk files to the system.img. (I’ll share it here) **My steps:​** 1) What I did was extract the image, add my apk to /app, or /priv-app, or vendor/operator/app. 2) Convert the folders/files of the extracted image to an ISO. 3) Convert the ISO back to .img file using WinISO software 4) Added the system.img converted in step 3 back into the main folder where all the original firmware images are. 5) Flashed the new firmware with the modified system.img back to the device. **Problem:​** The device boots up to the brand logo. However, it just gets stuck at the brand logo. VERY IMPORTANT => If the flash is successful, then the brand logo turns into brand logo animation, but every time I flash with my APK, it just gets stuck at the unanimated boot logo. Thus there are two stages: Boot logo = if stuck, then flashing/APK adding failed Boot Animation = everything works (I know this because the stock flash works just fine) = extra info=​ Android: 4.4.2 Flash tool: MTK SP Flash Tool XDA Forums attachment link: https://xdaforums.com/attachments/mx2-wvga_tm-wv3-22-20230418-rar.6039930/ (The above link is the firmware I was able to obtain from the company)

I am currently working for a company that operates screens in some kind of 'kiosk mode' to provide information in malls etc. The devices are basically big monitors connected to a development board (as far as I can see similar to a Raspberry Pi) which runs Android and starts a display app when boot up. Now the problem is that we currently have to set up all the boards manually. Meaning removing certain pre-installed vendor apps, installing our own apps, setting the right configuration, etc. Since this process is quite time-consuming and prone to errors, we thought if there is a solution to configure one device, save the "firmware" (.img) on a computer or USB stick and then use this image as a base for all other devices. Is there an easy way to achieve this? How can we create a snapshot of the Android device? All devices are the same from a hardware point.

I have an Infinix Note 10 Pro. I would like to know if there is any way to fix the 0-byte partitions issue and storage being inaccessible. I saw this when I was trying to copy out the vbmeta and boot.bin files for rooting, and for some reason, I got that issue. Prior to the issue, I upgraded my firmware after a full wipe, and that's when the issue popped. It is also to note that I do not have access to my internal memory for some reason either. I am absolutely clueless about how these Mediatek devices work. I need advice since I have skimmed through multiple forums, and am unable to land on a decisive conclusion. In short, I do not want to ruin more than I already have. Thank you for your time.

*My original problem is at https://android.stackexchange.com/questions/214200/ . You can simply ignore my original problem since it's kinda not related to this question. Just share some backgrounds.* --- Now, I am trying a different (first stock release) ROM and hopefully, this time, it can work. After downloading this ROM, I got the following 5 files:

camera.pit
CODE_GC100XXALJF_413474_REV00_user_low_ship.tar.md5
CSC_HOME_OLB_GC100OLBALJB_409864_REV00_user_low_ship.tar.md5
CSC_OLB_GC100OLBALJB_409864_REV00_user_low_ship.tar.md5
MODEM_GC100XXALJG_REV01_CL1210642.tar.md5

I guess CODE_GC100XXALJF_413474_REV00_user_low_ship.tar.md5 is **AP** option because it has the biggest size. But just a guess. How to use them with Odin? Which one belongs to which option?