[Knowledge] About FIH Firmware Build Version Format + OTA Package Name Correction

[Knowledge] About FIH Firmware Build Version Format + OTA Package Name Correction - Nokia 6 Guides, News, & Discussion

This article is translated and sorted from my original article in Zhihu (You can treat is as Chinese version of Quora): https://zhuanlan.zhihu.com/p/45079436
FIH, or FIH Mobile is the manufacturer behind all the HMD Nokia phones.
If you want to translate or repost to another forum or website, please send DM or Email to me for permission, and send me your reposted link after you finished.
Click to expand...
Click to collapse
This is what you definitely need to know if you plan to flash a Nokia or Sharp (not the Japanese exclusive models) Android phone.
The "Software Version" in "About Phone" (e.g.00CN_5_620_SP04)is not FIH firmware build version. The exact FIH firmware build version is located in systeminfo partition, or "fver" file in the OTA package for A-only partition based Android phones.
In many cases you can dial *#*#227#*#* to open "BBox" app and check out your firmware revision, take this one from my Nokia 2 for example:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's actual firmware revision is
E1M-0650-0-00WW-B01
In somecases, the selinux seems misconfigured for this app, so you can't check anything in BBox or only few of them.
You can also use these methods to check firmware build version:
Under ADB Shell or internal BASH:
Code:
$ cat /proc/fver
Or under fastboot/download mode:
Code:
./fastboot oem getversions
Let's divide it into 4 parts:
E1M - The FIH internal project code or codename. Unlike regular codename (in this example, dynamo), this FIH internal codename is widely used everywhere. A project code stands for a device, so keep it in your mind. Next time when I mentioned a FIH internal codename on Twitter, you need to react immediately - Oh this project code represents my device.
0650 - Firmware version number. This is what you will see such as V0.650. Or it will be combined with branch and revision part (e.g. 0650.B01), which I'll mention later. In some cases the first digit won't change when an Android revision upgrade releases, like Nokia 5/6 from Android 8.0 to 8.1.
First digit means the number of Android version it's running. In this example, Nokia 2 had Android 7.1 running when released and it's the first version, so the first digit is zero. And next version is Android 8.1, so it will change to 1 - for example, E1M-115P-0-00WW-B01.
Second digit means the major function revision. It changes a lot in China. Take Nokia 7 Plus in China for example, from B2N-213C-0-00CN-B04 (April 2018) to B2N-213E-0-00CN-B04 (May 2018), then B2N-233A-0-00CN-B03 (June 2018), B2N-233C-0-00CN-B01 (July 2018) and B2N-242C-0-00CN-B02 (August 2018).
Third digit means bugfix revision. This bugfix is mainly related to FIH itself, like driver issue.
Fourth digit means Android Security Patch Level revision. The base build usually ends with zero or an upper case letter. When a base build is stable enough, FIH will apply Android Security Patch Level with their own patch method and push it to users. But it's usually unrelated. Take Nokia X6 sold in China for example, from DRG-237E-0-00CN-B01 (August 2018) to DRG-237H-0-00CN-B01 (September 2018), then DRG-237I-0-00CN-B01 (October 2018). If you own a leak source of FIH internal OTA packages, you will notice few packages has unusual version, like NB1-5113-0-00WW-B01 (ends with 3) or PDA-209k-0-00CN-B01 (ender with lower case K) These updates are mainly internal minor fix updates and you may unable to get newer updates based on it, so be careful.
Don't care about the third zero.
00WW - Region code. This should be easy to understand. So far Nokia phones only has "00CN" and "00WW". Few variants like Sharp Aquos C10 (Europe Variant of Aquos S2 FS8010) uses "00E0". In fact this is the last 4 characters of the SKUID. I've attached the SKUID_Info.xml dumped from another FIH made phone with codename "ANT", hope this will help you understand the meaning of SKUID easier.
B01 - branch and revision. Recently, Branch A are mainly used on prototype devices, Branch B are mainly used on retail devices. In some cases, FIH decided to swith your current branch to B instead of A, but you can't switch branch B back to branch A due to different signatures.
I think this will help you understand your current build version.
Unhide follow to read known project codes.
FRT - Nokia 1 (The exact project code is frontier)
E1M - Nokia 2 (The exact project code is dynamo)
E2M - Nokia 2.1 (The exact project code is dynamo2)
NE1 - Nokia 3 (The exact project code is essential)
ES2 - Nokia 3.1 (The exact project code is essential2)
ROO - Nokia 3.1 Plus (The exact project code is rooster)
DPL - Nokia 3.2 (The exact project code is deadpool)
PAN - Nokia 4.2 (The exact project code is panther)
ND1/D1A - Nokia 5 (The exact project code is core)
CO2 - Nokia 5.1 (The exact project code is core2)
PDA - Nokia 5.1 Plus / Nokia X5 (The exact project code is panda)
D1C/PLE - Nokia 6 (The exact project code is plate)
PL2 - Nokia 6.1 (The exact project code is plate2)
DRG - Nokia 6.1 Plus / Nokia X6 (The exact project code is dragon)
TAS - Nokia X71 (The exact project code is taishan)
C1N - Nokia 7 (The exact project code is charm)
B2N - Nokia 7 Plus (The exact project code is onyx)
CTL - Nokia 7.1 (The exact project code is crystal)
PNX - Nokia 8.1 / Nokia X7 (The exact project code is phoenix)
NB1 - Nokia 8 (The exact project code is bang)
A1N - Nokia 8 Sirocco (The exact project code is avenger)
AOP - Nokia 9 (The exact project code is olympic beholder)
VN3 - Sharp Z3
SS2 - Sharp Aquos S2 SDM630 / Aquos C10 (The exact project code is sato)
SAT - Sharp Aquos S2 SDM660 (The exact project code is sato)
HH1 - Sharp Aquos S3 SDM630
SD1 - Sharp Aquos S3 SDM660
SG1 - Sharp Aquos S3 mini
After you understood the build version, let's talk about internal OTA update filename formats.
Internal OTA update packages leaked from either FIH OTA Server of my own private source has a fixed filename format for OTA packages.
Take the recently leaked OTA package for Nokia 5 and 6 for example:
Android Pie for Nokia 5 Differed OTA: ND1-612E-0-00WW-B01-558K-0-00WW-B01-update.zip
Android Pie for Nokia 6 Full OTA: D1C-612D-0-00CN-B01-update.zip
Here's the formula:
Differed OTA: [fih_internal_codename]-[fw_version_after_update}-0-[region_code_after_update]-[branch_and_revision_after_update]-[fw_version_before_update}-0-[region_code_before_update]-[branch_and_revision_before_update]-update.zip
Full OTA: [fih_firmware_build_version_after_update]-update.zip
It will make much more sense after I colored the filename.
With this specific file name format, DO NOT rename it casually, otherwise it can't be recognized with internal OTA update app - anyway, FIH will gradually remove the internal OTA update app in Nokia 7 Plus Global Variant, but it still worth preserves, and it will help you pick the correct OTA package for your current firmware version.
However, Google renamed these OTA packages to it's checksums, it will be harder to restore it as it's original filename provided by FIH.
So my thought is simple - you need to know the firmware build before update and the firmware build after update.
As I said, you can obtain your current firmware version by either dialing *#*#227#*#* or simply read systeminfo partition of your current slot - if you have root permission. But if it's an A-only device OTA package, you can check "fver" file in the package with any text editor - that's what it will be written to systeminfo partition.
TBA: Does anyone know how to dump payload.bin from a differed OTA package for A/B seamless update devices?
UPDATE: Looks like I need to try payload dumper under Linux distro.
Click to expand...
Click to collapse
At least you will know the FIH internal codename of your device.
When it's a full OTA, you can rename the filename as the formula shown above.
What if I don't know at all?
Simple. Rename it to
[fih_internal_codename]-999Z-0-00WW-B09-update.zip
Nothing can be newer than 999Z.B09 right?
After update finished, you can check exact firmware revision by method mentioned above.
Hope this will help you feedback issues from stock firmware or leaked OTA update easier.
Why did I write this topic?
Because many Chinese users only asked me "How to install B02 update on my device? " But they don't know B02 only means the branch and revision, not the firmware itself. At least please use this expression like this: "How to install D1C-612D build on my device? "

First of all thank you for your kind sharing.. :fingers-crossed:
I know linuxprobe.org reflects OTA files in SWUpdate server for all Chinese OTA
Is there any specific way to get informed about full SWImage package like above?
I have so much problems with finding them by manual changing those 50000**** digits

X1111 said:
First of all thank you for your kind sharing.. :fingers-crossed:
I know linuxprobe.org reflects OTA files in SWUpdate server for all Chinese OTA
Is there any specific way to get informed about full SWImage package like above?
I have so much problems with finding them by manual changing those 50000**** digits
Click to expand...
Click to collapse
I personally use a python script to list them.

Related

Breaking: Android 4.3 For Google Nexus 4 Leaks (JWR66N) - Here's The System Dump

Breaking: Android 4.3 For Google Nexus 4 Leaks (JWR66N) - Here's The System Dump
For the past few hours, I've been observing a curious case of Jeff Williams on Google+. Jeff posted a screenshot of what he claimed was a Nexus 4 he bought from a Googler... with a build of Android 4.3 on it. The same build, JWR66N, that we saw leaked earlier on a Galaxy S4 GPE by SamMobile.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In disbelief, some have called him a hoaxer, but a number of resourceful folks decided to get Jeff on IRC (channel #Android43 on freenode) and worked with him for hours, trying over and over to get the magical system dump that would prove Jeff's story to be real.
The system dump, which we have since confirmed as legitimate and along with dozens of other IRC members mirrored to multiple destinations, indeed belongs to a Nexus 4 (mako), and the build number is indeed JWR66N. The radio and bootloader are missing right now - Jeff promised them tomorrow - so I have my doubts about a working port to other Nexus 4s for the time being.
In the meantime, the system dump itself is ready to go, and Ron and I are ripping through it as we speak. We'll have a teardown ready for you soon if we do dig something up, and by the looks of things, there's enough for a post.
I'd like to thank Jeff for his persistence as well as IRC users efrant, gravufo, Jason__, vividboarder, Introspection, and everyone else who drove this one to the finish line.
Update: There's chatter on IRC that restoring the backup via TWRP recovery seems to work. We haven't tested this, so if you do decide to proceed, do so with caution and after making a full backup of your entire system.
AP mirror #1
AP mirror #2
AP mirror #3
AP multi-mirror
Even more mirrors (by hackthevoid)
Breaking: Android 4.2.2 (Build JDQ39) Update Rolling Out To GSM Galaxy Nexus, Nexus 7, Nexus 10
exus owners may have a reason to stay up tonight, as a couple of Reddit users report that Android 4.2.2 has begun rolling out to the GSM Galaxy Nexus and the Nexus 7.
There's not much word regarding what the update (which carries build JDQ39) includes just yet, but readers may remember that Google promised a Bluetooth A2DP audio streaming fix in the "next release" of 4.2 after 4.2.1.
At the moment it would seem that Reddit users in the thread linked below are the only ones reporting success at grabbing the update, so it's hard to judge the thread's veracity. If 4.2.2 has hit your device, though, let us know in the comments below.
Update: It looks like the update is rolling out after all. We've received confirmation from a number of users on Google+, including Marco Duran, who kindly provided some shots of the 47.6MB download from the Nexus 10.
Source: Android Police

4.2.2 nexus 7
NEED OTA LINK FOR NEXUS 7:laugh::laugh:

Here's The Android 4.2.2 JDQ39 Update For The GSM Galaxy Nexus
Here's The Android 4.2.2 JDQ39 Update For The GSM Galaxy Nexus [Manual Installation Instructions]
A couple of hours ago, Google started rolling out the Android 4.2.2 update to a very limited subset of Nexus devices (build JDQ39). At this point, almost nobody can get the OTA pulled by going through the Settings screen, but don't worry - one of our loyal readers extracted the OTA url for the Galaxy Nexus and sent it over to us (great work, Daniel Koch!).
For now, we only have the link for the takju Galaxy Nexus variant, i.e. GNex handsets bought from the Play Store. Once we get the yakju build, we'll update this post.
Note: Every Custom ROM flashing May have risk. So, please do it at your own Wish.
If you're not sure whether you have a takju or yakju variant, download Nexus Update Checker from the Play Store and see what it says.
Click to expand...
Click to collapse
What's New?
We don't have any reliable information at this point because Google hasn't pushed the 4.2.2 files to AOSP yet or published any changelogs. We suspect the Bluetooth bug has been fixed, but are unclear what else has changed right now.
There is a new radio in this OTA.
Prerequisites
Your device should be running build JOP40D before trying to install the update manually. If you for some reason don't have JOP40D, Google has it available in factory image form here.
For those ready to download and install manually, the process is easy. If you
have a custom recovery, just download the zip (linked below), move it to your device, and flash as usual
have the stock recovery, keep the zip file on your computer and follow a few easy instructions below
Manual Instructions
Step 1.
Reboot your Galaxy Nexus, holding the Volume Up and Volume Down buttons while it boots up. Once you see the fastboot menu and "Start," press Volume Up to navigate to "Recovery" and press the power button. Once you see an Android with a red exclamation point icon, press Volume Up and the Power button together, which will bring you to a new menu. Navigate to "apply update from adb."
Step 2.
Connect your Galaxy Nexus to your computer with a USB cable.
Make sure you have a recent version of adb that supports the sideload command (if you don't, download the latest Android SDK to ensure your adb is up-to-date).
Open up a command prompt (cmd in Windows, regular shell in Linux and Mac) in the same directory as the zip file you've downloaded.
Type in the following:
adb sideload 472aafeb9fe3.signed-takju-JDQ39-from-JOP40D.472aafeb.zip
Click to expand...
Click to collapse
You should see a progress bar, which will eventually hit 100%. At this point, your device is installing the update.
Step 3.
Reboot and enjoy! You are now running Android 4.2.2 on your Galaxy Nexus.
Download
Here's the OTA, hosted on Google's servers: takju build JDQ39.
AP mirror just in case it goes down: AndroidFileHost.
MD5: d37cd3aeeacc0d25a523acbebb5557f4
File size: 46.4 MB (48,672,997 bytes)
Source: Android Police

Shouldn't this file word being updated from recovery the normal way to?
I'm on Galaxy Nexus takju with TWRP recovery, and my updated failed..
EDIT: I get this error. assert failed: apply_patch _check ("system/lib/li
E: Error in /sdcard/filename.zip
(status7)
Error flashing zip
Updating partition details
/Söder

Re: Breaking: Android 4.2.2 (Build JDQ39) Update Rolling Out To GSM Galaxy Nexus, Nex
Good update
Sent from my GT-I8150 using xda app-developers app

soder said:
Shouldn't this file word being updated from recovery the normal way to?
I'm on Galaxy Nexus takju with TWRP recovery, and my updated failed..
EDIT: I get this error. assert failed: apply_patch _check ("system/lib/li
E: Error in /sdcard/filename.zip
(status7)
Error flashing zip
Updating partition details
/Söder
Click to expand...
Click to collapse
Try to flash using CWM buddy. Also are you applying the commands..??

soder said:
Shouldn't this file word being updated from recovery the normal way to?
I'm on Galaxy Nexus takju with TWRP recovery, and my updated failed..
EDIT: I get this error. assert failed: apply_patch _check ("system/lib/li
E: Error in /sdcard/filename.zip
(status7)
Error flashing zip
Updating partition details
/Söder
Click to expand...
Click to collapse
Dude it's not a regular flashable zip. You need a takju stock recovery.

m.kochan10 said:
Dude it's not a regular flashable zip. You need a takju stock recovery.
Click to expand...
Click to collapse
But, as I remember it, the 4.2.1 update was that kind of that kind of zip to?
And I was told I could flash it in a custom recovery? Or do I remember it wrong?
EDIT: This is where I got that info I think
http://forum.xda-developers.com/showthread.php?p=34706283#post34706283
and also from here
http://forum.xda-developers.com/showthread.php?t=1592689&page=84
Also:
"For those ready to download and install manually, the process is easy. If you
have a custom recovery, just download the zip (linked below), move it to your device, and flash as usual"
EDIT2: I now remember that I might have edited my gps.conf, and created a new file. That might have anything to do with it? How do I get back an "untouched" version? I go have a backup of the stock rom, but how do I get the file back untouched?
/Söder

Re: Breaking: Android 4.2.2 (Build JDQ39) Update Rolling Out To GSM Galaxy Nexus, Nex
Now the source needs to be updated so I can get it on my Samsung galaxy s1
Sent from my SCH-I500 using Tapatalk 2

Android 4.2.2 (JDQ39) Source Has Started Pushing To AOSP
Android 4.2.2 (JDQ39) Source Has Started Pushing To AOSP [Updated]
It's begun - the newest version of Android, 4.2.2, is being pushed to AOSP right now. We saw the accompanying Nexus OTA rollout start last night, with update files slowly springing up thereafter. Right now, 4.2.2 builds can be downloaded for the Takju Galaxy Nexus, Nexus 7 (Wi-Fi), and Nexus 10.
The build number is JDQ39 and the tag in AOSP is android-4.2.2_r1. Here are a few of the many directories that have been updated:
/device/common/+/android-4.2.2_r1
/platform/dalvik/+/android-4.2.2_r1
/platform/build/+/android-4.2.2_r1
While the push has just started this morning, source will likely continue to show up throughout the day, and we'll update this page as that happens. The Android Building Google Group should have a post by JBQ when the push is complete.
Update: It appears the push has finished, all Android 4.2.2 code should be in AOSP now.
They're working on compiling a full developer changelog right now, and once we've done that, we'll try to come up with a more human-readable one.
[Developer Changelog] Here's What's New In Android 4.2.2 (JDQ39)
Following yesterday's Android 4.2.2 OTAs to various Nexus devices, Google today followed up with the push of all 4.2.2 open source code changes to AOSP. There is a lot here to parse through this time around compared to the minor 4.2.1_r1.2 commit from 10 days ago.
We've already identified some obvious user-facing changes, which we'll post about separately soon to keep it clean and organized. The purpose of this post is, as before, to find the low-level changes that may not be obvious. So move the beard out of the way and dig in.
Update: Ron detailed some new things here: New Android 4.2.2 Features: Toggle From Quick Settings, Better App Download Notifications, and Some New Sounds!
What's New?
Things we've discovered so far, in brief:
Play Store downloads now show time left to download.
Long-pressing Wi-Fi and BT now toggles them in the notification Quick Settings.
More secure ADB thanks to the new whitelist.
BT bug fixes? I've seen conflicting reports whether this is fixed - citation needed if anything's been done to it. Can you spot the right commits?
Update #1: Play a tone when wireless charging begins (if below 95% battery). Use new low battery and wireless charging sounds on Mako. Here are the new sounds: WirelessChargingStarted.ogg and LowBattery.ogg.
Here is the list of developer commits in 4.2.2 (AOSP tag android-4.2.2_r1, JDQ39) compared to 4.2.1's latest revision (AOSP tag android-4.2.1_r1.2, JOP40G).
Note: For whatever reason, some of these we may have seen before - perhaps someone who understands the intricacies of AOSP's git structure can explain why they're getting included in the diff, but for the most part, this is all new stuff.
Code:
Project name: /platform/development
•Chris Banes - Update bitmapfun sample to call recycle()
•Dirk Dougherty - Add redirect for removed file.
•Dirk Dougherty - Minor updates to keep androiddevdocs redirect in sync with devsite version (in frameworks/base)
•Adam Koch - Bitmapfun Sample: Fix bug where background image loading could hang
•Chet Haase - Cherrypick from Change-Id: I4ae984cf776604cede32b98db6b1eb3cb6c59c7e
•Adam Koch - Bitmapfun Sample: Change cache memory calculation to use maxMemory()
•Adam Koch - Bitmapfun Sample: Fix inSampleSize selection and update dependencies
•Katie McCormick - Network sample: fix typo in manifest
•Xavier Ducrohet - Update platform tools rev to 16.0.2
•Dirk Dougherty - Add ko and ru to validLangs.
•Joe Malin - Android Training: Threads sample app
•Dirk Dougherty - Add redirect for IAB v3 restructure.
•Dianne Hackborn - SDK Only: Fix search interaction with various samples.
•Dirk Dougherty - Redirects /guide/google to /google/.
•Xavier Ducrohet - Move plat-tools SDK component rev to 16.0.1
•&& repo sync -j8 - Doc change: sample app for Notifications class
•Scott Main - docs: update redirects for articles
•Scott Main - docs: add redirects for best practices pages that moved to training
•Scott Main - docs: a few bonus redirects for dac
•Andy Stadler - Cleanup eclipse .classpath for Gallery2
•Scott Main - docs: redirect next steps to building first app class
Project name: /platform/cts
•Leo Liao - DO NOT MERGE Add missing features of JB and JB MR1
•Leo Liao - Add missing features of JELLY_BEAN to feature list
•Brian Muramatsu - Updated Holo test assets for JB MR1
•Nick Kralevich - FileSystemPermissionTest: add directories
•Brian Muramatsu - DO NOT MERGE Update CTS Verifier to R4
•Brian Muramatsu - DO NOT MERGE Update CTS Verifier to R5
•Laurent Tu - Restore CtsVerifier rate for passive updates
•Brian Muramatsu - Some Holo Test Improvements
•Nick Kralevich - Try reading every file on /sys
•Brian Muramatsu - DO NOT MERGE Update CTS Verifier version again
•Marco Nelissen - Improve testSetNextMediaPlayer test
•Brian Muramatsu - DO NOT MERGE Update CTS Verifier version to 4.2 R3
•Brian Muramatsu - DO NOT MERGE Update CTS Verifier version to 4.1_R4
•Laurent Tu - Assert mean and stdev of update deltas
•Nick Kralevich - Add CVE to Exynos vulnerability test.
•Brian Muramatsu - DO NOT MERGE Update CTS Verifier Version to 4.1_R3
•Laurent Tu - DO NOT MERGE Relax LocationVerifier assertions.
•steven_huang - DO NOT MERGE Filter out the overdue location cases in GPS test
•Brian Muramatsu - DO NOT MERGE Update CTS Verifier Version to 4.2_r2
•Laurent Tu - DO NOT MERGE Relax LocationVerifier assertions.
•Brian Muramatsu - DO NOT MERGE Update CTS Verifier Version to 4.2_r2
•Laurent Tu - DO NOT MERGE Relax LocationVerifier assertions.
•Brian Muramatsu - DO NOT MERGE Update CTS Verifier Version to 4.1_R3
•Laurent Tu - DO NOT MERGE Relax LocationVerifier assertions.
•steven_huang - DO NOT MERGE Filter out the overdue location cases in GPS test
•Nick Kralevich - Add Exynos vulnerability tests.
•Adam Momtaz - CTS tests for UiAutomator at API 17
•Marco Nelissen - Add test for MediaScanner misbehavior
•Andreas Huber - Add a CTS test that iterates through all codecs using MediaCodecList and
•Andreas Huber - Adds a CTS test verifying audio encoder functionality. (AAC, AMR-NB, AMR-WB)
•Adam Momtaz - Fixed a mistakenly deleted line from the last submit
•Marco Nelissen - Fix ringtone test
•Brian Muramatsu - Update BuildVersionTest to support 4.2.2
•Fabrice Di Meglio - Fix bug #7664208 android.widget.cts.TextViewTest#testResetTextAlignment failures on JD
•Eino-Ville Talvala - CTS Verifier: Fix Camera Formats preview orientation.
•Fabrice Di Meglio - Fix bug #7664305 android.widget.cts.TextViewTest#testResetTextDirection failures on JD
•Adam Momtaz - UiAutomator test APK and Tests for CTS
•Fabrice Di Meglio - Add more CTS tests for the reset of RTL properties
•Keun young Park - DO NOR MERGE make reboot default in CTS (merge from mr1)
•Keun young Park - add log to print time-out when time-out happens
•Nick Kralevich - Add more tests for restricted broadcasts.
•Keun young Park - add 4.2.1 to version list
•Svetoslav Ganov - Cannot move edit text cursor to first position using character granularity.
•Keun young Park - change all file writes to random access with O_SYNC
•Brett Chabot - Add UiAutomator test skeleton to CTS.
•Svetoslav Ganov - Fix the shell commands used to clean up after the accessibility tests.
•Svetoslav Ganov - Add NumberPicker CTS tests.
•Nick Kralevich - FileSystemPermissionTest: Expand block device tests.
•Keun young Park - force reboot after accessibility test
•Guru Nagarajan - Version number for CTS 4.2 modified: tools/tradefed-host/src/com/android/cts/tradefed/build/CtsBuildProvider.java
•Brian Muramatsu - Report suite name to result server
•Igor Murashkin - Camera: New test to check app firing intent after capturing picture/video
Project name: /platform/prebuilts/sdk
•Ying Wang - Drop official SDK 17
Project name: /platform/prebuilts/misc
•Brett Chabot - Manually update tradefed prebuilt from jb.
•Xavier Ducrohet - Update Layoutlib_api to API 9. do not merge.
Project name: /platform/hardware/libhardware
•Mathias Agopian - Fix HWC documentation.
Project name: /platform/hardware/libhardware_legacy
•Eric Laurent - audio policy: notification delay - DO NOT MERGE
•Eric Laurent - audio policy: fix volume problem - DO NOT MERGE
•John Grossman - audio policy: fix dynamic parameter - DO NOT MERGE
•Jason Simmons - audio policy: direct output fix - DO NOT MERGE
•Irfan Sheriff - Fix stop supplicant api
Project name: /platform/hardware/ril
•Wink Saville - Update documenation for DATA_REGISTRATION_STATE
remaining Can be view here -> [URL="https://gist.github.com/archon810/4772945#file-changelog_android-4-2-1_r1-2_android-4-2-2_r1-txt"]ile-changelog_android-4-2-1_r1-2_android-4-2-2_r1-txt[/URL]
Detailed Changelog
Full_changelog_android-4.2.1_r1.2_android-4.2.2_r1.txt
Source: Android Police

Thanks for change log, I have not yet received the update but know that flashing will be good to get a fresh start.

nexus4?

Android 4.2.2 adds new sounds and notification toggles
Android 4.2.2 adds new sounds and notification toggles
Why just the other day, we told you that Android 4.2.2 was being sent out to the Google Nexus 10, Google Nexus 7 and the Samsung GALAXY Nexus. While there has not yet been any changelist, we do have some information from those who have installed it on their tablet or phone. First of all, there is a new notification bar that shows you the time remaining and the percentage left of an in-progress app download. A change to Quick Settings lets you long press on the Bluetooth or Wi-Fi square to turn them into toggle switches. Now here is where it gets confusing. The Airplane Mode box is a single press toggle while some boxes do not change any settings.
Calculate speed of in-progress downloads and estimate time remaining until completion. Uses a moving average that is weighted 1:1 with the most recent 500ms sample. Funnels timing data to notifications through DownloadHandler."-How Google calculates the time remaining of an app download
Click to expand...
Click to collapse
Android 4.2.2 also brings a couple of new sounds, The two short bursts that tell you that your battery is low has been replaced while there is now a sound for wireless charging. Previously, the latter had no sound at all.
It should be interesting to see how the Android 4.2.2 update affects the next distribution data from Google. Also, we could see Android 4.0 drop more as some devices get updated to Android 4.1. The large chunk of Android users sporting a device powered by Gingerbread is only going to dissipate slowly as those owners start to upgrade once their 2-year contract expires. Those Android 2.3 phones will be replaced by Android 4.1 by the time the updates are in full swing, providing another reason to expect Ice Cream Sandwich to continue to melt.
If you have installed the Android 4.2.2 update on any of your devices, drop us a comment with some of the other changes that you might have noticed.
Source: PhoneArena

The Nexus 4 Finally Gets Android 4.2.2 (JDQ39) As Well - Here Are Instructions For In
ctakah27 said:
nexus4?
Click to expand...
Click to collapse
The Nexus 4 Finally Gets Android 4.2.2 (JDQ39) As Well - Here Are Instructions For Installing It Manually
Good news, everyone! The Nexus 4 Android 4.2.2 OTA (JDQ39) is finally here, surprisingly late in the update cycle, following the Nexus 10 and older Nexus devices, such as both variants of the Nexus 7 and both variants of the Galaxy Nexus. Chances are you probably don't have the coveted update notification just yet, but who wants to wait if you can sideload it manually? Rooted, unrooted, stock or custom recovery - it matters not.
What's New?
To see what's new in Android 4.2.2, see New Android 4.2.2 Features: Toggle From Quick Settings, Better App Download Notifications, and Some New Sounds!
Code:
[B]Heads up:[/B] There is also a new radio in this update.
Prerequisites
Your device should be running build JOP40D before trying to install the update manually. If you for some reason don't have JOP40D, Google has it available in factory image form here.
For those ready to download and install manually, the process is easy. If you
have a custom recovery, just download the zip (linked below), move it to your device, and flash as usual
have the stock recovery or a custom recovery that supports sideloading, keep the zip file on your computer and follow a few easy instructions below
Manual Instructions
Step 1.
Reboot your Nexus 4, holding the Volume Down button while it boots up. Once you see the fastboot menu and "Start," press Volume Up to navigate to "Recovery" and press the power button. Once you see an Android with a red exclamation point icon, hold Power and press Volume Up a few times, which will bring you to a new menu. Navigate to "apply update from adb."
Step 2.
Connect your Nexus 4 to your computer with a USB cable.
Make sure you have a recent version of adb that supports the sideload command (if you don't, download the latest Android SDK to ensure your adb is up-to-date).
Open up a command prompt (cmd in Windows, regular shell in Linux and Mac) in the same directory as the zip file you've downloaded.
Type in the following:
Code:
adb sideload de8b8d101614.signed-occam-JDQ39-from-JOP40D.de8b8d10.zip
You should see a progress bar, which will eventually hit 100%. At this point, your device is installing the update.
Step 3.
Reboot and enjoy! You are now running Android 4.2.2 on your Nexus 4.
Download
Here's the OTA, hosted on Google's servers: build JDQ39.
MD5: 1c752738f65acfd48f2d3b6e6e11a654
File size: 51.0 MB (53,529,568 bytes)
Source: AndroidPolice

Thank You
Thanks for change log!

rishabhgangwar said:
Thanks for change log!
Click to expand...
Click to collapse
Pressing thanks button can speak louder then words in Xda buddy..

question
do we need to wipe data to complete this action? is there any problem could face SDCARD folder?

New 4.3 Update found Check the OP.:good:
Breaking: Android 4.3 For Google Nexus 4 Leaks (JWR66N) - Here's The System Dump

Disturbed™ said:
New 4.3 Update found Check the OP.:good:
Breaking: Android 4.3 For Google Nexus 4 Leaks (JWR66N) - Here's The System Dump
Click to expand...
Click to collapse
thanks for the convincing statements :good:

Elephone P6000 Pro MTK6753 Information Thread: Root, Recovery, ROMS and more

General information - P6000 Pro 2gb / 3gb
This is a great mid range phone, and packs the performance of larger devices such as the P8000 into a smaller profile. Ideal if you want a responsive device, but don't want the phablet bulge in your trousers.
Important:
This thread is for the P6000 Pro - not the P6000. That's a separate (older) model.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Specification:
Dimensions: 144.5 * 71.6 * 8.9mm
Weight: 165g (with battery)
CPU: MediaTek MTK6753
GPU: ARM MALI-T720
RAM: 2GB / 3GB versions
Storage: 16GB ROM
Display: LG, 5.0" 1280*720 pixels
Battery: 2700 mAh
OS: Android 5.1 stock
Camera: Samsung rear-13MP, front-2.0MP
SIM card: Dual Micro SIM card,dual standby
Wi-Fi: 802.11n wireless
USB: 2.0 Micro USB
Bluetooth: 4.0
Positioning: GPS, A-GPS
Launch date: July 2015
Official Website:
http://www.elephone.hk/P6000-Pro-3gb.html
http://www.elephone.hk/P6000-Pro-2gb.html
http://bbs.elephone.hk/forum.php?gid=283#.VghRY_lVhBc (forum)
Reviews:
1. http://bbs.elephone.hk/thread-7585-1-1.html#.Viae_fmrS70 [Credit: @megthebest]
2. [Credit: @megthebest]
3.
4.
Hardware teardown:
http://www.gizmochina.com/2015/07/30/teardown-of-elephone-p6000-pro-3gb-version/

Root Information
Rooting is the process of allowing users of smartphones, tablets and other devices running the Android mobile operating system to attain privileged control (known as root access) over various Android subsystems.
The P6000 Pro's stock firmware is rooted as shipped, and does not require any hacks to activate it. Just install Chainfire's SuperSU from the Google Play store:
https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en_GB

Custom Recovery Information
Philz 6 recovery:
- This version includes modified kernel with working Touch screen. SD Card also supported:
http://forum.xda-developers.com/showpost.php?p=64038183&postcount=52 Credit: @lion567
- No touch:
http://4pda.ru/forum/index.php?showtopic=686517&st=100#entry43546180 (Release thread)
https://yadi.sk/d/HZfsB0nZjbkhJ (Download link)
CWM Custom Recovery:
- No touch or SD card support
CWM can apply software changes to the device. Unlike the stock recovery, CWM is able to entirely replace the device's primary Android operating system ("flashing a new ROM").
An unofficial version of ClockwordMod (CWM) Custom Recovery has been released by for the P6000 Pro:
http://www.needrom.com/download/cwm-carliv-6-from-hypoturtle/
Credit: @HypoTurtle, @yuweng and @carliv
Installation:
1. Install SuperSU from Google Play store
2. Install Flashify from Google Play store
3. Flash the downloaded file (CWM-P6000Pro-recovery.img) with Flashify app (Grant root rights with SuperSU when requested)
Accessing Recovery once installed:
Method 1:
1. Turn your phone off
2. Push and hold Vol Up and Power buttons together until a menu appears. It takes about 3 seconds. You should have the following options:
[Recovery mode]
[Fastboot mode]
[Normal mode]
Use the Vol Up button to scroll through the menu options, and press Vol Down to select.
Method 2:
Choose the option 'Reboot to recovery' from within Flashify

Android Development
ROM Reading / Writing with SP Flash Tool:
Smartphone Flash Tool (SP Flash Tool) is a Windows application for reading and writing to MediaTek SOC powered devices.
To read or write to a specific device, you need a 'scatter file' for the correct type of CPU. The scatter file defines the memory ranges within the chip. P6000 Pro uses the MediaTek MT6753 SOC:
http://androidurdu.net/mediatek-scatter-files-download/
Instructions to read back from SP Flashtool:
1. Load the Scatter file (download from above)
2. Select the 'Readback' tab, press 'Add' to add a range
3. Double click on the row that appears in the table. Type a filename to save this memory range to (Eg. recovery.img if you're reading the recovery memory area)
4. Enter the start address and length of the section you are reading back - copy them from the scatter file.
3. Push 'Read Back' button
4. Remove the battery from the phone
5. Connect the phone to USB. No need to power it on. It will connect and commence reading. The recovery memory range took about 3 seconds to read back.
6. It will say 'Readback OK' and you will now have a img file from that memory range.
Available ROMs:
Stock Android 5.1 20150910:
http://bbs.elephone.hk/thread-7986-1-1.html#.VghUSflVhBc
https://mega.nz/#!ghgSHQCL!xxvBWtgCQsaXe2I7yOBxIl5w5SV2hpfFRtefAEmWxPU
Stock Android 5.1 20151031:
http://bbs.elephone.hk/thread-9362-1-1.html#.Vl9bd_nhC70
https://mega.nz/#!M5YFWRiC!pYiql0Q556CmFyB0t8XRUxgTxMe-LW1pfSfuqUxEYvY
FlyME 4.5.3a:
http://bbs.elephone.hk/thread-7380-1-1.html#.VghUevlVhBc
https://mega.nz/#!z8NRAKyS!BkQQc44aTciy9vuT-d4-kWnyr8pnHkI595U7nEfXMGU (26.08.2015)
DCU v12.1 (AOSP):
http://bbs.elephone.hk/thread-8759-1-1.html
http://4pda.ru/forum/index.php?showtopic=686517
https://yadi.sk/d/637BNhDQjdwtr (09.10.2015)
https://yadi.sk/d/ylE2JKN5jroQN (20.10.2015)
Eragon 5.1 Lollipop (AOSP):
http://forum.xda-developers.com/android/development/rom-18-11-eragon-v1-0-p6000-pro-android-t3251881 (Credit: @skeleton1911)
IUNI OS Android 5.1.1:
http://4pda.ru/forum/lofiversion/index.php?t686517-320.html (release thread)
https://yadi.sk/d/UGEdEkb2jutMp (22.10.2015)
Upcoming ROMS:
Elephone have announced Android 6.0 Marshmallow will be released for the P6000 Pro:
http://www.elephone.hk/readnews/8160.html
Custom Kernel:
[Kernel][1.5 Ghz] visi0nary's kernel for P6000 Pro credit: @BlueFlame4
Stagefright Patch:
The stock ROM is vulnerable to Stagefright CVE-2015-6602 and CVE-2015-3864. A patch is available:
http://forum.xda-developers.com/android/development/bug-fix-stagefright-t3193219 Credit: @superdragonpt
Note: Modification to the loader script or manual installation via ADB required, due to the P6000 Pro using different partition names. A modified version by @ahorntaler is available on needrom but may not be the latest version.
Source Code:
Elephone have released via Github the source code for the P8000, which shares the same CPU (MTK6753) and GPU (ARM MALI-T720) as the Elephone P6000 Pro:
https://github.com/elephone-dev/P8000-Kernel
Discussion: http://forum.xda-developers.com/ele...el-elephone-p8000-kernel-source-code-t3163314
Compiled P8000 kernel: http://forum.xda-developers.com/elephone-p8000/orig-development/kernel-visi0narys-kernel-t3226081 Credit: @BlueFlame4

Other Guides
Engineering Mode:
Use the secret menu carefully.. if you don't know what you are doing... don't do it!!
On the stock 5.1 ROM, you can access P6000 Pro Engineering mode with the following code entered on the dialer: *#*#3646633#*#*
Note: This is the same as P6000.
If you are not running the stock 5.1 ROM, you can download MTK Engineering Mode from the Google Play store.
It has the available menus:
Telephony
Connectivity
Hardware Testing
Location
Log and Debugging
Others
Manual IMEI Programming:
If you experience "can't detect SIM cards" or "can't make a phone call" error messages, you should check your IMEI code hasn't been accidentally overwritten. If your IMEI codes are not valid as can happen after flashing an image, please go through the following tutorial to reprogram your original IMEI. Your original IMEI numbers are printed on the label under the battery.
1. Enter Engineering Mode (as above)
2. Click on "CONNECTIVITY"
3. Click on "CDS INFORMATION"
4. click on "RADIO INFORMATION"
5. then to "PHONE 1" for the 1st IMEI, and write in:
AT +EGMR=1,7,"00000000000" (Replace the "zeros" with your own IMEI No.)
6. Press 'SEND AT COMMAND'
7. "PHONE 2" for the 2nd IMEI and write in:
AT +EGMR=1,10,"0000000000" (Replace the "zeros" with your own IMEI No.)
8. Press 'SEND AT COMMAND'
IMPORTANT: All typing on keyboard
Demo:
Other IMEI tools:
MTKdroid Tools 2.5.3d does not support MTK6753.
Chamelephon does not support MTK6753 (Appears to work, but corrupts the IMEI)

Reserved for future use
Reserved for future use
To be updated

Can you add how save and restore imei ?

Krystyna said:
Can you add how save and restore imei ?
Click to expand...
Click to collapse
Good idea.
Do you have P6000 Pro? I think MTKdroid Tools would work, but I didn't try it. (see here: http://androidxda.com/backup-and-restore-imei-nvram)
Do you have any confirmation or alternative method?

blahmartinblah said:
Good idea.
Do you have P6000 Pro? I think MTKdroid Tools would work, but I didn't try it. (see here: http://androidxda.com/backup-and-restore-imei-nvram)
Do you have any confirmation or alternative method?
Click to expand...
Click to collapse
I tried MTKdroid Tools 2.5.3.d tonight on my P6000 Pro. It doesn't support NVRAM download/restore from MTK6753.
So I think manual programming of the IMEI through the Engineering Mode is the only option at present. I have confirmed it is working fine.
The IMEI are printed under the battery, so no real need to "back up".

Updated with links to DCU v12.1 ROM.

blahmartinblah said:
Stagefright Patch:
http://www.needrom.com/download/stagefright-patch-p6000-pro-2/ (for Stock ROM Android 5.1 20150910. Credit: @superdragonpt and @ahorntaler)
Click to expand...
Click to collapse
Who tha hell is ahorntaler?
The patch was compiled by me ...
And why are you linking to that stupid website?
Stagefright patch for some Mediatek devices is here at xda:
http://forum.xda-developers.com/android/development/bug-fix-stagefright-t3193219

superdragonpt said:
Who tha hell is ahorntaler?
The patch was compiled by me ...
And why are you linking to that stupid website?
Stagefright patch for some Mediatek devices is here at xda:
http://forum.xda-developers.com/android/development/bug-fix-stagefright-t3193219
Click to expand...
Click to collapse
Thanks for stopping by, and for your original work on the Stagefright patches.
I guess with a little reading, you could see that @ahorntaler is someone who modified your works to suit the Elephone P6000 Pro, and gave you credit. Out of the box, the patch doesn't work. (See post 63163952) I also prefer hosting files on xda to needrom, but mirroring the authors work would have been equally bad IMO. We all appreciate your work You seem disgruntled, which I didn't intend to cause. Can I amend the post in some way that remains useful to P6000 Pro owners, but still makes you happy?

blahmartinblah said:
Thanks for stopping by, and for your original work on the Stagefright patches.
I guess with a little reading, you could see that @ahorntaler is someone who modified your works to suit the Elephone P6000 Pro, and gave you credit. Out of the box, the patch doesn't work. (See post 63163952) I also prefer hosting files on xda to needrom, but mirroring the authors work would have been equally bad IMO. We all appreciate your work You seem disgruntled, which I didn't intend to cause. Can I amend the post in some way that remains useful to P6000 Pro owners, but still makes you happy?
Click to expand...
Click to collapse
Modified what?
It's very well explained, the partition stuff in my thread ...
Quote from my op:
For other devices that don't use the mmcblk0p17 as /system partition:
The flash may fail, if that's your case, simply extract all the files, and push via adb to your device.
Click to expand...
Click to collapse
I need to update the stagefright thread with a new build btw... there's new stagefright bugs around (they are fixed on our Lp build, i need to update the thread for other devices ...)
ps: No im not pissed, i just didn't know who that guy is/was
Ps2: Nothing against you, i just really hate needrom these days,,, all the KANGers are posting "their work" there.
cheers

superdragonpt said:
Modified what?
Did he compiled the libs by any chance?
Click to expand...
Click to collapse
No lib changes judging by the file time stamps. I believe the modifications are to the updater-script, to include the correct paths.
Flashing this modified update is a lot more convenient for newbies like me
He also retains your credits in the updater script.
In the future, I agree it's better to link to your thread like you suggest, and I'll include instructions on how to modify the updater-script. That way we P6000 Pro users can benefit from future updates to the patch you release.

superdragonpt said:
Modified what?
Did he compiled the libs by any chance?
It's very well explained, the partition stuff in my thread ...
Quote from my op:
I need to update the stagefright thread with a new build btw... there's new stagefright bugs around (they are fixed on our Lp build, i need to update the thread for other devices ...)
ps: No im not pissed, i just didn't know who that guy is/was
cheers
Click to expand...
Click to collapse
Hi superdragonpt,
I'm very sorry that You are disappointed. I don't want any credit for the patch. I only modified installation script to make it useable for P6000 Pro users and I wrote that the patch is not my work, but Yours. So why are You pissed? I'm only a simple user who wanted to share the benefit of Your work with others. I don't (want to) earn any Money with programming. Next time I ask You. The question is: why didn't you modify installation script? Credit would have been Yours. I wanted to be You only help.

ahorntaler said:
Hi superdragonpt,
I'm very sorry that You are disappointed. I don't want any credit for the patch. I only modified installation script to make it useable for P6000 Pro users and I wrote that the patch is not my work, but Yours. So why are You pissed? I'm only a simple user who wanted to share the benefit of Your work with others. I don't (want to) earn any Money with programming. Next time I ask You. The question is: why didn't you modify installation script? Credit would have been Yours. I wanted to be You only help.
Click to expand...
Click to collapse
It's nothing against you...
i thought it was some "random guy" from needrom ...
(im a bit pissed with needrom in general...)
PS: Tell me something guys, your latest official rom is Lollipop v 5.0 or 5.1 ?
PS2: Re-Download the latest stagefright app from Zimpherium to check what are new bugs...
I need to release a new build for other MTK phones (yours included)
Cheers

superdragonpt said:
PS: Tell me something guys, your latest official rom is Lollipop v 5.0 or 5.1 ?
Click to expand...
Click to collapse
:good:
P6000 Pro stock ROM is Lollipop 5.1.

What ROM ?!!
i Have just bought a P6000 pro , the battery lasts about 7 hours what rom should i flash to improve battery life?
Thanks in advance.

blahmartinblah said:
:good:
P6000 Pro stock ROM is Lollipop 5.1.
Click to expand...
Click to collapse
Can you give me the build ID?
(check under build.prop), i may need to make some small corrections for the stagefright, depending on the android build
cheers

superdragonpt said:
Can you give me the build ID?
(check under build.prop), i may need to make some small corrections for the stagefright, depending on the android build
Click to expand...
Click to collapse
From build.prop on the Elephone P6000 Pro 20150821 stock ROM:
Code:
ro.build.id=LMY47D
ro.build.display.id=ALPS.L1.MP3.V2_NB6753.65U.L1_P22
ro.build.version.incremental=1440142279
ro.build.version.sdk=22
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.1

[GUIDE/ODIN/FW/BL] SM-P610 USA/XAR WIFI ONLY: Stock Firmwares + Modded BL WarningText

THIS IS YOUR FIRST WARNING (WILL BE REITERATED PLENTY OF TIMES!) IN BIG RED BOLD LETTERS - THESE FILES ARE FROM/FOR THE USA ("XAR") REGION, SM-P610 WIFI MODEL ONLY!
(with the exception of the Odin utility, as well as possibly the modified boot splash screen, which may work on other variants, though untested and done solely at your own risk - read all the notes!!)
I already went through the work, so I figured I would share these files for those who also own the same exact tablet. Again, it's for the USA/XAR region Samsung Galaxy Tab S6 Lite WiFi Model ONLY - "SM-P610" / "gta4xlwifi". LTE model is a different variant; do NOT flash the stock firmware files to that device! Also, sorry, I will not support or answer questions for other variants (other than what I will mention in this OP). Downloading firmwares for other variants will be a huge PITA, and I don't have / pay for any "premium" accounts which would allow me to quickly download the huge firmware files. I'm only sharing these I'm posting because I already took the time to acquire and archive them for personal usage, and might as well share them for those who own the same device / variant.
Use these files at your own risk, and only flash if you know what you're doing!! I'm not responsible for any problems user may incur from usage of these files, the usual warnings apply, etc. This device is just a backup / playaround device for me, and so it doesn't get daily usage out of me, nor will I likely be very active on this subforum (sorry! just being honest). Also, I immediately installed LOS on my device anyway, so I don't run stock ROM myself and therefore won't be sharing pre-patched Magisk boot images either. Sorry to those who are used to that from me =)
So anyway... what's in this post?
Odin3 v3.14.4 (version I've been using on this device, and working perfectly fine as of this initial posting)
Stock firmware zips for USA/"XAR" Region SM-P610, WiFi Only
Modified BL file (Odin-flashable), to remove the warning boot text
Odin3 v3.14.4:
I posted this in another thread, but figured I would also link to it here so it's easy to find in one place. This worked perfectly fine for me to root / install TWRP / flash BL files, etc.
Download Link: https://www.androidfilehost.com/?fid=10763459528675582443
Stock Firmware Files:
USA/XAR WIFI ONLY! October 2020 Update - Firmware Version P610XXU2BTJ5
Download Link: https://www.androidfilehost.com/?fid=10763459528675592742
USA/XAR WIFI ONLY! September 2020 Update - Firmware Version P610XXU2BTI3
Download Link: https://www.androidfilehost.com/?fid=10763459528675592159
Firmware files for other variants, see this post. Follow the links, use the resources, consider the context for other variants: https://forum.xda-developers.com/showpost.php?p=83083249&postcount=2
Modified [BL-slot] Odin-Flashable File To Remove Warning Splash Screen Text:
My Thoughts On This...After unlocking the bootloader and flashing non-stock images, we all know we end up with that annoying, ugly splash screen screaming that the device is modified. Most of us modifying our devices understand the security implications involved, and ironically choose to modify our devices to increase security in other ways. Yet, these warning splash screens, in the unfortunate event of possible theft, may very well end up being the reason a more tech-savvy thief is able to break into the device, or find someone who can. So, thanks to users' posts Awesomeslayerg's hint and blascogm's guide, I quickly came up with an Odin-flashable file to change the splash screen, as seen below:
(if the pic doesn't show, probably the imgur link I used is dead, but I also attached it to this post)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know some people may be thinking "why not just remove the PRESS POWER KEY TO CONTINUE line completely and have it stay at the normal boot screen seamlessly the whole time", and the reason I decided not to do this is because it generally wouldn't make the average person suspect the device is modified, and it's still good for us to know that it's at the boot stage where we can hit the power key to skip the ~10 second timeout. It's exactly the same image, so it's still very seamless and stock-like. I even took the time to center the power key text exactly, by the pixel, from left to right and from top bottom relative to the knox and android logos.. ; )
And if it really bothers you that much, follow the guide I linked above and do it yourself. =)
I should also mention that, for our devices, the .bin.lz4 file that needs to be decrypted is actually "up_param.bin.lz4" and not "param.bin.lz4" as suggested in the guide, as it's for a different device. You will need the lz4 utility (check Awesomeslayerg's thread, or google lz4 github) to decrypt the lz4 file to a regular bin file, and then you can extract and/or replace the .jpg files using an archiver program (I recommend 7-zip for this).
The hash checksums for every single file/jpg in each up_param.bin were identical between the September and October firmwares. Therefore, at least as of this posting, the same modified Odin-flashable file will work on either firmware version, and likely future versions until they make any significant changes. I did test this myself too btw. Also, if you look at the structure and contents of the up_param.bin file for yourself, you'll see that they are simply .jpg files containing the screens, backgrounds, and text you're all familiar with when going into bootloader / download mode. Assuming they follow the same file naming structure, I suspect you can probably flash this to other variants, although it will change the text language to English (assuming they localize the bootloader / download mode text per every region; I have no idea about this as I only own US variants). To see what I'm talking about, here's a quick screenshot (better resolution pic, and just in case imgur link dies, also attached to this post):
Now that I (hopefully) tricked you into reading this entire section so that you now have some basic understanding of how it works before proceeding to flashing the warning text removal mod, here are the instructions / link for install:
- Download the .tar file provided below.
- Boot device into Download mode.
- Place .tar file into bootloader [BL] slot in Odin and flash.
Download Link: https://www.androidfilehost.com/?fid=10763459528675592179
To revert back to stock splash screen with warning text, for whatever reason:
Pull the stock up_param.bin.lz4 from the stock firmware file (from the BL****.md5 file within the firmware zip).
- Convert it to up_param.bin uzing lz4 utility.
- Add up_param.bin to an archive as .tar file, uncompressed (recommend using 7-zip).
- Flash the .tar file, which should contain only the stock decrypted up_param.bin file, in Download mode using Odin in the BL slot.
I uploaded my custom jpg's, as well as the stock untouched jpg's, for those that are curious or want to edit them further. Feel free to snag them here: https://www.androidfilehost.com/?w=files&flid=320350
* As we can see, we're only modifying the .jpg files provided by up_param.bin, so it's a relatively harmless process (unlike modifying aboot files in the old days of HTC devices, which if done improperly could literally result in an unrecoverable brick). But even so, please only flash if you know what you're doing and can recover from any potential mistakes or errors.

Not sure if there were any changes since the September / October 2020 firmwares, but here's a new one directly modified from the March 2021 (Android 11) firmware base:
NEWEST DOWNLOAD, BASED ON 2021-03 FIRMWARE:
https://www.androidfilehost.com/?fid=14943124697586346609

And another

Hi,
Thanks for these resources. I'm actually not at these steps yet. I'm having trouble gaining access to the OEM Bootloader Unlock option in developer options. Here are things I've tried already based on what I researched before my attempt.
Android 10 is the current OS installed after unboxing.
1. Disable Automatic Date and time
2. Select a date more than 7 days prior to current date of attempt.
3. Under Settings > About Phone > Software Information. Select/Tap Build Number 7-8 times to unlock Developer Option.
4. Disable Auto Update System (Apply Updates When Device Restarts) - *This was somehow already disabled the first time I entered Developer options*
5. Under Software Updates > Disable Automatic Updates -*This was also already disabled on unboxing and it says Automatically download updates over Wifi. It does not say Automatic Updates*
6. Reboot device and return to Developer Options after booting to OS.
7. The OEM Bootloader Unlock option should appear greyed out at this point. Toggle it to unlock bootloader with consideration that it will wipe the device data.
These are the steps I've found and tried with no success in gaining access to the Bootloader unlock option. I am also certain that my device is the international model SM-P610 with Exynos chipset and Mali-G72 GPU. Something else to note, I did uncheck many default options tied to improving privacy on the device before attempting the steps to gain access to the bootloader unlock option. I do not know if that would make a difference. If you recognize anything wrong with the steps I've tried already, please let me know where I'm going wrong or where I can find the correct way to unlock the bootloader. I've been posting in other threads, but nobody seems to be replying to me. Any help will be appreciated.

Hi
I've flashed your modded file on my PHN (Netherlands), no problems at all working ootb!

Hi. I used blascogm's guide for my P615 with latest firmware for SEC UI 3.1and all are OK! Thanks for all.
Add. I add link . Flash via Odin(BL).
https://androidfilehost.com/?fid=14943124697586347282

i5lee8bit said:
Not sure if there were any changes since the September / October 2020 firmwares, but here's a new one directly modified from the March 2021 (Android 11) firmware base:
NEWEST DOWNLOAD, BASED ON 2021-03 FIRMWARE:
https://www.androidfilehost.com/?fid=14943124697586346609
Click to expand...
Click to collapse
I flashed ths when I'm running lineageos 18.1 annd this is the only mod that worked for me

Thanks for posting your images and linking to the guide, worked perfectly and the images just fit to the pixel <3

Confirmed working as of March 2022. Device is running base P610XXU2DUL9. Thanks for the hard work.

can you make one for SM-P613 model plz?

[INFO][INDEX] Hot Pepper™ Chilaca (HPP-L60A) 4G-LTE Smartphone | General Info & Discussion Thread

Hot Pepper™ Mobile
Chilaca 4G-LTE Smartphone
T-Mobile® Certified
Model No. HPP-L60A
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
General Info &
Discussion Thread
OVERVIEW:
The Chilaca is a T-Mobile certified 4G-LTE smartphone, manufactured by Hot Pepper Mobile for eligible recipients of the federal Lifeline program and the Affordable Connectivity Program (ACP) -- government sponsored initiatives which assist low-income individuals and households with mobile phone service and mobile devices.
For an entry-level device, the Chilaca is a surprisingly capable smartphone. The MediaTek Helio A22 chipset platform utilizes CorePilot technology, which provides power-aware scheduling, CPU thermal management and persistent UX monitoring. These attributes work in harmony to assign the appropriate workload to CPU cores at a calculated and specific frequency and voltage, balancing the needed performance load demand with the optimal power efficiency. This landmark feature shines bright on the Chilaca, giving the user palpably smooth performance, the ability to maintain heavy workloads, all while maintaining impressive battery life in between charges. Moreover, the Chilaca's certification with T-Mobile provides remarkable network connectivity, excellent upload/download speeds, and extended range LTE coverage by way of Band 12 & 71 support.
HARDWARE SPECS:
Chipset: MediaTek Helio A22 (MT6761V/CAB)
CPU: Quad-core ARM Cortex-A53
CPU Max Clock: 2.0 GHz
Architecture: armv7l (32-bit)
CPU Process: 16 nm
GPU: IMG PowerVR Rogue GE8300
GPU Max Clock: 660 MHz
Display: 6.51" 1600 x 720 HD
Screen Density: 280 dpi (hdpi)
Internal Storage: 32GB eMMC (23.9 GB useable)
LTE Modem: Cat 7 DL; Cat 13 UL
LTE Bands: 2, 4, 5, 12, 25, 26, 41,66, 71
Bluetooth: v5.0, LE
WLAN Support: 802.11a/b/g/n/ac (2.4 & 5 GHz)
Battery: Li-Ion 3200 mAh
RAM: 2.0 GB (+ 1.386 GB zRAM)
Cameras: 5 MP Main; 2 MP Front
Ports: Type-C USB | 3.5mm Headphone Jack
FIRMWARE INFO:
OS/Version: Android 12 (Go Edition)
Firmware Build: HPP-L60A-3.0.18
Build ID: 12/SP1A.210812.016
Kernel Version: Linux v4.19.191
Radio: MOLY.LR12A.R3.MP.V208.3.P5
Security Patch Level: September 5, 2022
API Level: 31
Partition Scheme: Dynamic (Non A/B)
Project Treble: Supported
DEVELOPMENT STATUS:
Hot Pepper Mobile CEO Shawn Sun has selected me as a tester for the Chilaca 4G-LTE smartphone. Accordingly, the Chilaca has not yet been released within the mainstream US smartphone market. . This thread will serve as a general info & discussion forum for the Chilaca as more handsets become available via their release and distribution in the Lifeline program throughout the US.
I have obtained the factory firmware for the Chilaca, but have not yet experimented with bootloader unlocking or rooting the phone. I will keep this thread updated with any news in this regard. Should any members need the stock firmware, just leave a comment with the request.
UPDATE: February 17, 2023:
A recent OTA firmware rollout updates the current build to vHPP-L60A-3.0.19 with the December 05, 2022 security patch level.
I have also discovered that, per contractual terms between T-Mobile and the manufacturer, the bootloader on the Chilaca is not supported for unlocking. However, it appears that the Chilaca can be exploited using the MTK Client utility. Once I confirm bootloader unlocking I plan on writing a full tutorial with the step-by-step instructions and the required files for the task. It does appear that the Chilaca has been distributed throughout several US states via the federal Lifeline and ACP initiatives, making the device prominent on the mainstream market. I would ask that any Chilaca device owners leave a comment below.
UPDATE: March 23, 2023:
Another recent OTA security update has bumped the firmware build to HPP-L60A_3.0.20 with the February 1, 2023 security patch level.
In order to exploit the bootloader using MTK Client, you must be running the HPP-L60A_3.0.18 firmware build, or an earlier build. More recent builds have blocked user-initiated access to BROM mode which is essential to proper device recognition while using MTK Client. Fortunately, device owners may downgrade via the firmware package provided below in conjunction with the SP Flash Tool.
UPDATE: April 15, 2023:
An OTA update dated April 12, 2023, has bumped the firmware build to HPP-L60A_3.0.21, with a security patch level of March 5, 2023. This update included some bug fixes on premature kernel panic triggering and some baseband radio issues involving extended range LTE Band 71.
USEFUL LINKS:
• Factory Firmware HPP-L60A_3.0.18
• Chilaca Factory Firmware Restoration Guide
• SP Flash Tool v5.1924 (32 & 64-bit)
• Chilaca FCC Test Report
• Chilaca HPP-L60A User Manual (PDF)
• MTK Client Setup & Usage Guide **
Credit goes to @Sidharth09 for his guide on setting up and using MTK Flash Tool. Please consider hitting the thanks button on his thread.

Where can I find the decryption key?

MrAx714 said:
Where can I find the decryption key?
Click to expand...
Click to collapse
The download link is fixed.

Hi, guys.
New sign up but get info from y'all pros for long time.
My question about this phone:
Does anyone know if there is a source for a replacement screen for these anywhere yet? Have searched far and wide and no joy... they are very delicate at best.
Thanks and if this is posted in the wrong place just trash the post.
TIA
Peace

b4byl0n said:
Hi, guys.
New sign up but get info from y'all pros for long time.
My question about this phone:
Does anyone know if there is a source for a replacement screen for these anywhere yet? Have searched far and wide and no joy... they are very delicate at best.
Thanks and if this is posted in the wrong place just trash the post.
TIA
Peace
Click to expand...
Click to collapse
Splendid question. I'll see what I can find out on replacement parts.
My preliminary search for the availability of screen replacements and other parts for the Chilaca has been unfruitful. However, I will reach out to the CEO of Hot Pepper Mobile with this inquiry. I'll post back as soon as I know anything.

have you tried mtkclient with this?

luridphantom said:
have you tried mtkclient with this?
Click to expand...
Click to collapse
Indeed. Works on the older HPP-L60A-3. 0.18 firmware build. On newer builds BROM mode has been disabled. But on a positive note you can downgrade to 3.0.18 from a newer build using the firmware from my restoration guide.

wonder how i can be a tester to get my hands on one...
first feedback is to leave a BROM backdoor so we can always mtkclient unlock that baby

luridphantom said:
wonder how i can be a tester to get my hands on one...
first feedback is to leave a BROM backdoor so we can always mtkclient unlock that baby
Click to expand...
Click to collapse
The Chilaca has already completed all testing phases and has received Google Play Certification and T-Mobile certification. It is now being distributed via Lifeline and ACP channels throughout the US.
On unlocking the bootloader, all you need to do is flash my 3.0.18 firmware package and use MTK Client to exploit the bootloader. Once unlocked, you can install OTA updates as long as you are not yet rooted. Once updated to the latest 3.0.20 build, use MTK Client once again to dump your /boot partition in .img format. Use Magisk 26.1 to patch that boot.img, then use fastboot mode to flash the patched image to achieve root.
I have requested the latest full firmware build (3.0.20) for this phone. I should have it this week.

Hi ,. I recently brought a HPPL 69A , Pretty good device honestly but I want to do more with it ,So I looking into Rooting it , Is this could be possible ?

Could I root it without a PC

daremoNo said:
Could I root it without a PC
Click to expand...
Click to collapse
The HPP-L60A cannot be rooted without a PC. In fact, rooting it with a PC is a tedious and daunting task to put it mildly The bootloader must first be exploited using MTK Client. Afterwards, Magisk can be used to achieve systemless root. Also, in order to exploit the bootloader, you must be running the HPP-L60A-3.0.18 firmware build. The newer builds have blocked access to BROM mode. You can downgrade using SP Flash Tool to flash the firmware provided above.

So I just got one from the Lifeline program and I like it so far. I need to downgrade to the firmware ref. in the post above so I am attempting that right now. I am running win 11 and am having slight trouble turning off the driver verification for a 64bit os. I was trying to do it from the command line but ran into issues. edit: I turned off the driver enforcement (or at least I thought I was) in the local group policy editor, but I am still not able to install the mtk inf file. I get the error of " the digital inf doesn't contain any driver information. "
Any help would be great please.

ffreylu00x7 said:
So I just got one from the Lifeline program and I like it so far. I need to downgrade to the firmware ref. in the post above so I am attempting that right now. I am running win 11 and am having slight trouble turning off the driver verification for a 64bit os. I was trying to do it from the command line but ran into issues. edit: I turned off the driver enforcement (or at least I thought I was) in the local group policy editor, but I am still not able to install the mtk inf file. I get the error of " the digital inf doesn't contain any driver information. "
Any help would be great please.
Click to expand...
Click to collapse
Use this guide. Works on Win 10 & 11. https://windowsreport.com/driver-signature-enforcement-windows-10/

So I am thinking its file and not me messing up the driver enforcement. Has anyone vetted the link and what's provided in the link as to it being the proper thing to download or can you suggest a place to find a better firmware? I am trying to downgrade then hopefully achieve root access after that. I'll keep an updated post as I figure more out

ffreylu00x7 said:
So I am thinking its file and not me messing up the driver enforcement. Has anyone vetted the link and what's provided in the link as to it being the proper thing to download or can you suggest a place to find a better firmware? I am trying to downgrade then hopefully achieve root access after that. I'll keep an updated post as I figure more out
Click to expand...
Click to collapse
The firmware provided is directly from the servers of the manufacturer. It is official digitally signed firmware. It was provided to me by Hot Pepper Mobile months before the phone was released to the public. I beta tested this phone for the manufacturer. I've also installed this firmware with SP Flash Tool, via the debug and standard installations. There are no issues with the firmware archive.
If you want to efficiency disable driver signature enforcement, follow the guide I linked. Otherwise , you will likely have issues with installing the unsigned vCom drivers which will, in turn, complicate proper device recognition.
If you are having issues with device recognition with SP Flash Tool, here is a great step-by-step guide on configuring the MediaTek vCOM drivers on your PC or laptop. https://forum.xda-developers.com/t/...32-64-bit-driver-install-tutorial-m2.3267033/

So I don't know I it's my os on my computer or why I'm not getting the same options as y'all have instructed but I can't seem to figure out how to install these drivers. I disabled the driver verification enforcement and then went to device manager and this is where things were different. I'm not seeing the COM & PORTS...I installed the drivers from what was provided and followed the instructions. So after there is a new category called "SAMSUNG Android Phone" and I obviously don't have a Samsung so I'm not sure why that happened.

Afq
ffreylu00x7 said:
So I don't know I it's my os on my computer or why I'm not getting the same options as y'all have instructed but I can't seem to figure out how to install these drivers. I disabled the driver verification enforcement and then went to device manager and this is where things were different. I'm not seeing the COM & PORTS...I installed the drivers from what was provided and followed the instructions. So after there is a new category called "SAMSUNG Android Phone" and I obviously don't have a Samsung so I'm not sure why that happened.
Click to expand...
Click to collapse
Did you install the vCOM preloader drivers from the link I posted?

I have this phone. Someone from assurance wireless came knocking on my door and I didn't like truconnect anymore.
Anyway I searched and found your post. Bingo! Currently rooted.
Mine came with .18 on it and I had almost updated. I got mtk client working (used python mtk_gui) and backed up all partitions except the user data. Enabled dev mode. OEM unlocking. Went to the flash tab and did unlock bootloader. Installed magisk 26.1 on phone, adb pushed boot.bin to boot.img, patched file, adb pulled it, back into preloader, wrote the boot partition, don't know if it was necessary since I did a factory reset from the recovery menu, but I used mtk reset. I noticed that every time you use the cli mtk file you have to re enter preloader. Anyway, I did that, set it up, working great.
Now I want to remove the assurance wireless (T-Mobile lifeline mvno) subsidy lock, can mtkclient do that by erasing partitions like I've seen for some other phones? It's not a big deal right now and eventually it'll pass the auto unlock.
This is my first MediaTek root that worked. I have a Lenovo tab m8 tablet I tried it with before and didn't work but I didn't put much time into it. Was a few years back. Also I have a cloud stratus c7 which is also a mt6761 but the app I tried didn't work. But that was an on phone app. I'll have to try mtkclient with it.
Couple of questions. I used mtkgui and generated keys. No idea why or what I might use it for but I like to click things does it serve a purpose with this phone?
When I first ran the magisk patch install, after installing magisk 26.1 on the chilaca unrooted, there was a checkbox option for something about vbmeta in the boot image? I had checked it the first time but didn't use that image. But it doesn't show up anymore, so.. should I have used that?
Lastly, is there a way around the bootup having to press power to boot the phone or it'll shut off? Untrusted device message.
I've done plenty of rooting and jailbreaking and hardware hacking tinkering and such, but I owned a couple Samsung Galaxy s5s, then s7 edge, s8, then went to pixels. Got a pixel 3xl and 6 pro and Google makes everything super easy. I know that on the pixel you get a warning message that goes away after a few seconds (or you can press power to pause/unpause the warning) when bootloader is unlocked. I haven't tried it yet myself but I'm also aware of the ability to sign a rooted boot image (pixels are a/b devices if that matters) and relock the phone with it. Would that work on the chilaca you think? I can give it a shot.
I'm about to do the update to .20 right now. I restored the image through magisk manager so it'll patch the it's fine, just gotta reboot. Bootloader will remain unlocked you said? I'll find out
I'm gonna look into finding a kernel source for the mt6761 and see if I can't get a functional source tree up. Then it'd be nice to patch in sdk 32 (a13) pixel experience source tree will be useful for patch pulling guidance. Also I'm curious if twrp can be built, I started to read up on it and saw something about MediaTek and Qualcomm handling things very different, so we'll see.
Anyway thanks for the thread!!

A14 5G Root Avaliable?

Hello,
Theres no Samsung Galaxy A14 5G forum to post this in since it's somewhat a new phone. I have the SM-A146U One UI 5.0 Android 13, baseband ver A146USQU1AVL2
Kernel version 4.19.191-25583387-abA146USQU1AVL2 #1 Sun Dec 4 16:04 KST 2022
SE Enforcing SEPF_SM-A146U_12_0001
Sun Dec 4 16:15:21 2022
Service Provider Software Version SAOMC_SM-A146U_OYN_CHA_13_0011 CHA/CHA/CHA
Security Software Version
ASKS v5.8 release 20221121
ADP v3.0 release 20191001
SMR Nov-2022 Release 1
Android Security Patch level
November 1st 2022
Is there a root avaliable for this phone & has anyone sucessfully done it?

If Android's Linux kernel is version 5.10+ you can try to root device's Android at your own via
GitHub - tiann/KernelSU: A Kernel based root solution for Android
A Kernel based root solution for Android. Contribute to tiann/KernelSU development by creating an account on GitHub.
github.com

xXx yYy said:
If Android's Linux kernel is version 5.10+ you can try to root device's Android at your own via
GitHub - tiann/KernelSU: A Kernel based root solution for Android
A Kernel based root solution for Android. Contribute to tiann/KernelSU development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
If you read my post you would see the kernel version.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Moxiipc said:
Hello,
Theres no Samsung Galaxy A14 5G forum to post this in since it's somewhat a new phone. I have the SM-A146U One UI 5.0 Android 13, baseband ver A146USQU1AVL2
Kernel version 4.19.191-25583387-abA146USQU1AVL2 #1 Sun Dec 4 16:04 KST 2022
SE Enforcing SEPF_SM-A146U_12_0001
Sun Dec 4 16:15:21 2022
Service Provider Software Version SAOMC_SM-A146U_OYN_CHA_13_0011 CHA/CHA/CHA
Security Software Version
ASKS v5.8 release 20221121
ADP v3.0 release 20191001
SMR Nov-2022 Release 1
Android Security Patch level
November 1st 2022
Is there a root avaliable for this phone & has anyone sucessfully done it?
Click to expand...
Click to collapse

Moxiipc said:
Hello,
Theres no Samsung Galaxy A14 5G forum to post this in since it's somewhat a new phone. I have the SM-A146U One UI 5.0 Android 13, baseband ver A146USQU1AVL2
Kernel version 4.19.191-25583387-abA146USQU1AVL2 #1 Sun Dec 4 16:04 KST 2022
SE Enforcing SEPF_SM-A146U_12_0001
Sun Dec 4 16:15:21 2022
Service Provider Software Version SAOMC_SM-A146U_OYN_CHA_13_0011 CHA/CHA/CHA
Security Software Version
ASKS v5.8 release 20221121
ADP v3.0 release 20191001
SMR Nov-2022 Release 1
Android Security Patch level
November 1st 2022
Is there a root avaliable for this phone & has anyone sucessfully done it?
Click to expand...
Click to collapse
device galaxy a146p 5G
Download firmware update + ODIN(new method) from:
SamMobile - Your source for all Samsung news
SamMobile.com is the leading source for the latest Samsung news, firmware, product reviews, tutorials, tips, opinions, polls, and podcasts.
www.sammobile.com
"A146PXXU1AWAA_A146POJM1AWB1.....zip"
Then extract ... to five md5 files
Rename the file :
AP_...................OS13.tar.md5 "5.5 Gb"
To
AP_...................OS13.tar
Then i made image by :
Magisk [25.2].apk
Rename the extension .img to .tar
Finally flash this file using ODIN
Additional important steps like : OEM unlock ... bootloader ....
check page :
Galaxy A14 (SM-A145 and SM-A146) Custom Kernels and TWRPs
Galaxy A14 SM-A145P 4g and SM-A146P 5g Custom Kernels Kernel source code https://github.com/physwizz?tab=repositories NOTE: TWRPs in posts 3, 4 & 5
forum.xda-developers.com

lmrdy said:
device galaxy a146p 5G
Download firmware update + ODIN(new method) from:
SamMobile - Your source for all Samsung news
SamMobile.com is the leading source for the latest Samsung news, firmware, product reviews, tutorials, tips, opinions, polls, and podcasts.
www.sammobile.com
"A146PXXU1AWAA_A146POJM1AWB1.....zip"
Then extract ... to five md5 files
Rename the file :
AP_...................OS13.tar.md5 "5.5 Gb"
To
AP_...................OS13.tar
Then i made image by :
Magisk [25.2].apk
Rename the extension .img to .tar
Finally flash this file using ODIN
Additional important steps like : OEM unlock ... bootloader ....
check page :
Galaxy A14 (SM-A145 and SM-A146) Custom Kernels and TWRPs
Galaxy A14 SM-A145P 4g and SM-A146P 5g Custom Kernels Kernel source code https://github.com/physwizz?tab=repositories NOTE: TWRPs in posts 3, 4 & 5
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for this I will look into it & this works for 146U?

Does anyone by any chance have a scatterfile for this device? or preloader.bin ? i was on A146USQU1AWA7 before i completly messed up by using metkutility (android utility) now stuck on it only showing as mediatek usb port or mediatek da agent or mediatek preloader in device manager... ive tried various things to restore it but get errors when trying to use sp flash tool..

exnfox said:
Does anyone by any chance have a scatterfile for this device? or preloader.bin ? i was on A146USQU1AWA7 before i completly messed up by using metkutility (android utility) now stuck on it only showing as mediatek usb port or mediatek da agent or mediatek preloader in device manager... ive tried various things to restore it but get errors when trying to use sp flash tool..
Click to expand...
Click to collapse
I'm exactly on the same situation. I just could get a MTK rom (scatter rom) that flashes only the preloader (after that, sp flash tool keeps saying me "status_partiton_not_found 0xc0040006"), But despite it flashes successfully the given preloader, the phone wont get alive (not even want to enter into download mode). You can get your own scatter files, by using android utility (tab Android>Firmware utils, option "Extract samsung rom". You just need to have available an unzipped unencrypted Odin rom) the issue is that generated scatter supposedly belongs to a MT6853 instead of a MT6833, but changing all references of 6853, to 6833, it works, but as i say you, just enough to flash the preloader. If I get more advances, i will say you. But if you can to unbrick your phone before mines, please tell me how.

Camilo Gil said:
I'm exactly on the same situation. I just could get a MTK rom (scatter rom) that flashes only the preloader (after that, sp flash tool keeps saying me "status_partiton_not_found 0xc0040006"), But despite it flashes successfully the given preloader, the phone wont get alive (not even want to enter into download mode). You can get your own scatter files, by using android utility (tab Android>Firmware utils, option "Extract samsung rom". You just need to have available an unzipped unencrypted Odin rom) the issue is that generated scatter supposedly belongs to a MT6853 instead of a MT6833, but changing all references of 6853, to 6833, it works, but as i say you, just enough to flash the preloader. If I get more advances, i will say you. But if you can to unbrick your phone before mines, please tell me how.
Click to expand...
Click to collapse
yes i will let you know however ive tried many things including what you mentioned... i even went as far as paying 5 dollars to download a dead boot repair file from some site all it was just the firmware extracted like with mtk utliity... i wonder whats going on here. with the scatter file saying its mt6853 when the phones chipset is mt6833 and how do we flash it when we try to just change the value in notepad but it still fails everything except preloader?
preloader_s96902aa1.bin
preloader.img
im thinking the bin might be something differnt than whats suppose to be on the preloader partition? idk still expirmenting

exnfox said:
Does anyone by any chance have a scatterfile for this device? or preloader.bin ? i was on A146USQU1AWA7 before i completly messed up by using metkutility (android utility) now stuck on it only showing as mediatek usb port or mediatek da agent or mediatek preloader in device manager... ive tried various things to restore it but get errors when trying to use sp flash tool..
Click to expand...
Click to collapse
I want you guys to conduct an experiment with me in flashing your device.
The phone has Mediatek MT6833 or Dimensity 700.
I wil use different set of tools to have it fixed for you.
Let me know if we can do that. I will use Anydesk or Teamviewer to do it and then if your device is fixed we can make a tutorial to help out others.

mvikrant97 said:
I want you guys to conduct an experiment with me in flashing your device.
The phone has Mediatek MT6833 or Dimensity 700.
I wil use different set of tools to have it fixed for you.
Let me know if we can do that. I will use Anydesk or Teamviewer to do it and then if your device is fixed we can make a tutorial to help out others.
Click to expand...
Click to collapse
Okay want me to pm you my teamviewer Id?

exnfox said:
yes i will let you know however ive tried many things including what you mentioned... i even went as far as paying 5 dollars to download a dead boot repair file from some site all it was just the firmware extracted like with mtk utliity... i wonder whats going on here. with the scatter file saying its mt6853 when the phones chipset is mt6833 and how do we flash it when we try to just change the value in notepad but it still fails everything except preloader?
preloader_s96902aa1.bin
preloader.img
im thinking the bin might be something differnt than whats suppose to be on the preloader partition? idk still expirmenting
Click to expand...
Click to collapse
My friend, I also found this site that assures to have available for download, a SM-A146U scatter rom. The issue (at least to me), is that it charges for its download (and you have to sign up to this site). So I'll share you the link, and if you decide to invest on that download, please test it and, if you can bring back to life your Samsung, please share it (or at least its scatter file). Have a good luck with it.
SM-A146U Scatter Firmware

Camilo Gil said:
My friend, I also found this site that assures to have available for download, a SM-A146U scatter rom. The issue (at least to me), is that it charges for its download (and you have to sign up to this site). So I'll share you the link, and if you decide to invest on that download, please test it and, if you can bring back to life your Samsung, please share it (or at least its scatter file). Have a good luck with it.
SM-A146U Scatter Firmware
Click to expand...
Click to collapse
No need to pay anyone. We can make our own file.

exnfox said:
Okay want me to pm you my teamviewer Id?
Click to expand...
Click to collapse
Hey there,
Yes please PM me your ID. I will available in an hour from now.

mvikrant97 said:
I want you guys to conduct an experiment with me in flashing your device.
The phone has Mediatek MT6833 or Dimensity 700.
I wil use different set of tools to have it fixed for you.
Let me know if we can do that. I will use Anydesk or Teamviewer to do it and then if your device is fixed we can make a tutorial to help out others.
Click to expand...
Click to collapse
I have the file already the scatter doesn’t work so nevermind my initial request for that

exnfox said:
I have the file already the scatter doesn’t work so nevermind my initial request for that
Click to expand...
Click to collapse
I can make it work

mvikrant97 said:
I can make it work
Click to expand...
Click to collapse
I sent you my details

I also written to android utility's developer exposing the issue, to see if it's an android utility's issue or if i'm doing something wrong. I think is more probably is an issue of that program, and I cannot blame to the developer, because according to as i know, this phone's model is very recent; so i don't think it has yet many compatibility with many current softwares, including this one.
So, based on this hypothesis, also for that i think i informed to the developer, to he can fix that issue, on an upgrade of his program (which is currently on 108 version)
As aditional info, his webpage is https://www.androidutility.com/

Another thing that I knew by experimentation was, that even on Brom mode, the device won't let downgrade its firmware. I tried with an earlier samsung firmware, turned into scatter firmware; and sp flash tool showed me this warning: "status_sec_violate_anti_rollback 0xc0020021" that supposedly means that the device is rejecting the loaded firmware by being an old one.

Database Info

welcome