Related
Hi, got one moto g3, frp lock.
I found a link on ebhttp://www.ebay.com/itm/151884511307ay, he can factory reset the phone to clear the frp lock.
Not sure its a fake or real solution.
Before paying $29 , just want to know if it's a real solution or fake?
Probably fake. In the Samsung specific frp implementation there is a bug which allows to circumvent frp (and Samsung is already fixing this bug). And everybody can do this. No need to pay for such a service.
But I'm not aware of such a bug in the Motorola implementation.
To the best of my knowledge, the data we need to access for this is contained in the /persist partition...in theory, if you take a bootloader unlocked device which has never had a google account set up on it before, dump that device's /persist, then reflash it to another device, you SHOULD be able to bypass the FRP lock.
IN THEORY.....don't quote me, and I'm not responsible for any potential damage...I have NOT tested my theory. I'm only making an educated guess.
hp420 said:
To the best of my knowledge, the data we need to access for this is contained in the /persist partition...in theory, if you take a bootloader unlocked device which has never had a google account set up on it before, dump that device's /persist, then reflash it to another device, you SHOULD be able to bypass the FRP lock.
IN THEORY.....don't quote me, and I'm not responsible for any potential damage...I have NOT tested my theory. I'm only making an educated guess.
Click to expand...
Click to collapse
This will only work on a device where the bootloader was already unlocked before FRP is triggered.
You can only flash/overwrite the /persist partition if the bootloader is unlocked. In order to unlock the bootloader you have to select "Allow OEM Unlock" in developer settings first. Which is only possible if you can logon to the device...
u42671 said:
This will only work on a device where the bootloader was already unlocked before FRP is triggered.
You can only flash/overwrite the /persist partition if the bootloader is unlocked. In order to unlock the bootloader you have to select "Allow OEM Unlock" in developer settings first. Which is only possible if you can logon to the device...
Click to expand...
Click to collapse
Yes, that is correct. It's a very specific set of requirements that the device must meet, but I believe it could be possible. If all the conditions are right, I see absolutely no reason why this would not work.
hp420 said:
Yes, that is correct. It's a very specific set of requirements that the device must meet, but I believe it could be possible. If all the conditions are right, I see absolutely no reason why this would not work.
Click to expand...
Click to collapse
Yes, if the boot loader is unlocked you can definitely break frp. Just by flashing a custom rom frp will also be gone .
u42671 said:
Yes, if the boot loader is unlocked you can definitely break frp. Just by flashing a custom rom frp will also be gone .
Click to expand...
Click to collapse
No, this is totally incorrect. There are several people here who have tried that and all have failed. This is why I suspect it lives in the /persist partition. If it's in system, userdata, either cache, etc. it would be incredibly easy to get around. Google has some sort of persistent location for all this stuff....and there just so happens to be a partition literally titled persist....coincidence??? Probably not, imo
Also, you do not need an unlocked bootloader. All you need is TWRP. If you have TWRP you can boot there, then use ADB shell to get root access and you can then flash the partition in question.
check it out....partition mmcblk0p29 is titled persist:
drwxr-xr-x 2 root root 880 Jan 21 1970 .
drwxr-xr-x 4 root root 1000 Jan 21 1970 ..
lrwxrwxrwx 1 root root 20 Jan 21 1970 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 Jan 21 1970 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 Jan 21 1970 abootBackup -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Jan 21 1970 boot -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 Jan 21 1970 cache -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 Jan 21 1970 carrier -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 Jan 21 1970 cid -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Jan 21 1970 clogo -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 Jan 21 1970 customize -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 Jan 21 1970 dhob -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Jan 21 1970 frp -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Jan 21 1970 fsc -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 Jan 21 1970 fsg -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 Jan 21 1970 hob -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 Jan 21 1970 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Jan 21 1970 hypBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Jan 21 1970 keystore -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 Jan 21 1970 kpan -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 Jan 21 1970 logo -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 Jan 21 1970 logs -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Jan 21 1970 metadata -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 20 Jan 21 1970 misc -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 20 Jan 21 1970 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Jan 21 1970 modemst1 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Jan 21 1970 modemst2 -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Jan 21 1970 oem -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 Jan 21 1970 padA -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 21 1970 padB -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Jan 21 1970 padC -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 Jan 21 1970 persist -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 Jan 21 1970 recovery -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 20 Jan 21 1970 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 Jan 21 1970 rpmBackup -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 Jan 21 1970 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 Jan 21 1970 sp -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 Jan 21 1970 ssd -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 Jan 21 1970 system -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 20 Jan 21 1970 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 Jan 21 1970 tzBackup -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Jan 21 1970 userdata -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 20 Jan 21 1970 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Jan 21 1970 utagsBackup -> /dev/block/mmcblk0p15
Click to expand...
Click to collapse
What is frp?
banerjeeayan1996 said:
What is frp?
Click to expand...
Click to collapse
Factory Reset Protection
Finally done, without bootloader unlocked.
By going to setting and turn on debugging mode. And he run one simple script. And done.
Going to setting is simple (there are video on YouTube)
How were you able to go to settings and enable debug mode when you are logged out of the phone due to frp?
I know how this works on Samsung devices as Samsung automatically brings up a file manager when you connect a USB storage via OTG and then you can start an apk which brings up settings. Thats what also all the Videos on Youtube are showing.
But on my Moto G I cannot replicate this behaviour. It does not automatically bring up file manager when connecting USB stick via OTG. Only after manually starting file manager you can access the USB stick.
u42671 said:
How were you able to go to settings and enable debug mode when you are logged out of the phone due to frp?
I know how this works on Samsung devices as Samsung automatically brings up a file manager when you connect a USB storage via OTG and then you can start an apk which brings up settings. Thats what also all the Videos on Youtube are showing.
But on my Moto G I cannot replicate this behaviour. It does not automatically bring up file manager when connecting USB stick via OTG. Only after manually starting file manager you can access the USB stick.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=aaK6TK-oYJ8
br,
riteshgpt60 said:
you can go to setting by this:
https://www.youtube.com/watch?v=aaK6TK-oYJ8
br,
Click to expand...
Click to collapse
Could someone please translate this from portuguese? I can follow it for the most part, but I'd like to know any finer details he may be talking about. My spanish is terrible, let alone trying to understand portuguese lol
hp420 said:
Could someone please translate this from portuguese? I can follow it for the most part, but I'd like to know any finer details he may be talking about. My spanish is terrible, let alone trying to understand portuguese lol
Click to expand...
Click to collapse
First, the guy on the video is selling a program to do the unlocking.
The first part on the video shows a possible exploit to access the developer options, then enable usb debbugging.
The 190 number that he dials is the emergency police number in Brazil, similar to the 911 in US.
Maybe that´s the trick, when you try to make an emergency call, the system may bypass some security features.
I'm at work now, if you need I may translate to english the whole video, but only at home.
The guy is selling this "Motorola FRP Ulocking" software with a password, so even if you follow all the steps listed, you may need the software.
anyone have an interest in chipping in for this so we can release the exploit publicly?
@hp420, its already available publicly.
riteshgpt60 said:
@hp420, its already available publicly.
Click to expand...
Click to collapse
can you please share the link?
Can someone give me the password for frp unlock app . plss help me bro
https://www.youtube.com/watch?v=btXjGLeN5y0&index=1&list=LLFArHcghMf-E7X6EIvmJCWQ
nokia alkng said:
https://www.youtube.com/watch?v=btXjGLeN5y0&index=1&list=LLFArHcghMf-E7X6EIvmJCWQ
Click to expand...
Click to collapse
Bro i know to goto nova launcher n all other apps.. I need to factory reset my phone... While i goto settings d wipe option is hidden.. Nd i cant find the users menu nd OEM unlock feature option... Plss help me someone...
NOTE:
I'm not a developer or something even near to that. I'm a newbie and will be, seems so. All information provided here is copied and compiled from different internet sources like this and many others.
This information is according to best of my knowledge and comprehension and is just for curious souls like me who want to understand things in quite simple words. It might be wrong and I will open-heartedly welcome any correction or addition from anyone.
I'm not responsible for any harm to you or your device resulting from this.
1. PARTITION TABLE
The Phone's Internal Memory (eMMC or UFS; not the SD card) is solid-state (flash) memory, aka NAND. Raw NAND, as it's called, is basically a pure flash memory dependent on CPU to control it. But in order to use flash memory just like a traditional hard drive (block device), NAND is equipped with an (embedded multimedia) micro-controller. It's called eMMC.
eMMC can be partitioned much like a hard drive on PC. PC's have traditionally been partitioned with BIOS compatible Master Boot Record (MBR) scheme in which first sector of disk contains the details of partitions called Partition Table. Limited size of boot sector (512 bytes) puts a limitation of at maximum 4 (primary) partitions listed in MBR. Extended partition has been used for 4+ partitions.
GUID Partition Table (GPT) was introduced with UEFI booting system which isn't dependent on first boot sector and hence may contain up to 128 partitions. GPT also does CRC check, has backup GPT, identifies partitions by GUID and partitions have a label.
Android devices use GPT. We can view and manipulate GPT using Linux tools such as parted and gdisk while fdisk is the traditional tool for MBR partitions.
To view partition table on internal memory:
Code:
~# parted /dev/block/mmcblk0
(parted) p free
~# gdisk -l /dev/block/mmcblk0
(The external SD Card can also be partitioned to include a section dedicated to storing user apps (like Link2SD does) or to create partitions for secondary or tertiary OS on Android device using some multiboot kernel and recovery system). Even we can put whole OS/ROM on an SD card.
2. BRIEF INTRO
Contents of Android partitions can be partially or completely modified by flashing an image (filesystem .img or executable binary or a flashable zip) to them. But we never need to modify most of them and whatever manufacturer wrote on them, resides there unmodified (read-only) for the whole of device life. A user uses only one partition /data to save personal data like photos, music etc. All the other are for device to run. There are typically in the range of 50 partitions on an Android device but only a few partitions are modified for the purpose of adding new features or upgrading the device. A custom ROM or minor upgrade is also limited to modify /boot, /system and /data partitions usually. Most of the partitions are almost intact, containing bootloaders, firmwares, settings etc. Here is a "summarized" detail to these partitions which matter to a common but interested user.
On most devices /system and /data are larger partitions (on some devices /custom or a similar partition too) covering almost 90% of eMMC. All others are smaller ones of a few KB's or MB's.
3. SoC / CHIPSET / PROCESSORS RELATED PARTITIONS
SoC is the first component when we start a PC or Mobile phone which initialzes hardware and processors and loads bootloaders in memory to bootstrap OS. It's an integrated chip containing multiple things e.g. CPU, GPU, modem, wifi etc. It varies for device manufacturers and SoC vendors (chipset plus processor).
Some partitions are specific to SoC, most of them are closed-source executable binary blobs (like aboot, sbl, rpm, tz, cmnlib, devcfg, keymaster, lksecapp and others on a Qualcomm device), loaded step-by-step by bootloaders.
MODEM or RADIO - the phone's radio
Also called baseband, it is responsible for signals and on older devices may control wifi, bluetooth, and GPS (on most newer devices, these are handled by the kernel and ROM). Upgrades are country dependent and may improve or diminish battery performance, network signal strength, and roaming capability. It is also sometimes required to have a minimum Baseband version to use a ROM so that the RIL will play nice with the Baseband.
Modem firmware is a mini-OS for the cellular radio chip which has its own processor. Firmware is a general term, firmware exists for a lot of things on phone. The wireless chip for WiFi, GPS, and Bluetooth often has a firmware as can the GPU core among other things. These firmware files are usually located inside the SYSTEM or VENDOR partition. The modem firmware is special because it has its own separate Baseband Processor (BP) so the firmware is left out of the system image in its own partition.
Modem is not an Android-specific partition. It is tied to the hardware of the phone, but the kernel has a code allowing Android to interact with the hardware. But the baseband processor (BP) - which runs modem and is responsible for all communication through mobile networks e.g. call, SMS and internet - is totally isolated from Application Processor (the one we call CPU) and is not governed by Android kernel; it runs an independent RTOS.
RIL/Radio Interface Layer
This is not a separate partition, but a part of the ROM and is like a driver for the Radio. RIL daemons provides telephony and cellular data i.e. adds phone to smartphone. There is a matching RIL for each Baseband version and you can flash it to match your Baseband after flashing a ROM. Having mismatched RIL and Baseband can range from having no effect at all, slight battery drain, loss of roaming, or even no connection to the cell network. Many ROMs keep their RIL updated to the latest. Job of the RIL is to translate all the telephony requests from the Android telephony framework and map them to the corresponding AT commands to the modem, and back again. AT set of commands is used to communicate with modem i.e. baseband processor (BP) which is a must have processor on Android devices in addition to normal CPU i.e. Application Processor (AP).
TZ (TrustZone) - used by ARM processors as an additional lock to security features. It combines user's encryption key with a hardware specific key generated by encryption processor (like TPM on Windows) to make security breaching more difficult. It can also be used to implement Trusted Execution Environment (TEE).
RPM (Resource/Power Management) which starts executing Primary/Primitive BootLoader (PBL) in BootROM - controls power to radio, modem etc.
DSP (Digital Signal Processor) - by Qualcomm to assist in things like smooth video playback (realtime media and sensors processor) as well as runs RTOS for modem
HYP (Hypervisor) - Virtual Machine Monitor, to enable Virtual Machine platform
4. BOOTLOADERS
Bootloaders - in many steps - hand over charge to kernel after loading in RAM. These are mostly standalone ELF executable files becuase at this stage no filesystem is loaded and only executable code may work. These are all closed source components on Android device, provided by SoC vendors - either built-in or as binary blobs.
SBL - Secondary bootloader loaded by SoC, loads ABOOT in memory, also provides (Emergency) Download Mode (EDL) on many devices, a Firmware Update Protocol.
ABOOT (bootloader.img or aboot.mbn file in Factory Firmware) - Applications Bootloader is the main bootloader responsible for loading kernel or recovey and fastboot - a Firmware Update Protocol - as well.
Kernelflinger is a similar bootloader on Intel devices.
Read ANDROID BOOT PROCESS to know more about bootloaders.
5. CORE AOSP PARTITIONS
BOOT - Kernel and initramfs (modern form of of ramdisk and ramfs/tmpfs)
A kernel is a layer of code that allows the OS and applications to interface with your phone's hardware. The degree to which you can access your phone's hardware features depends on the quality of code in the kernel. Several kernel code improvements give us additional features from our hardware that the stock kernel does not. When you flash a custom ROM, you automatically get a kernel. But you can also flash a standalone kernel on top of the existing one, effectively overwriting it. These days, the difference in custom kernels is less about new features and more about alternate configurations. Choosing a custom kernel is basically choosing one that works best with your ROM.
Device Tree Blob (DTB), along with hardware drivers, are baked with kernel source in boot.img. DTB is loaded by bootloader at boot time and passed to kernel so that it can discover hardware and create node points accordingly.
On a Linux system init along with scripts, binaries kernel drivers and modules (in initrd.img), kernel (vmlinuz executable) and bootloader configuration along with modules, they all reside on root or a separate partition (mounted) at /boot. While on Android, init along with a few binaries and configuration files and kernel reside in a separate partition named "boot" with a special filesystem. Boot.img is created using tools like mkbootimg after building kernel.
This is how kenrel and DTB are built:
vmlinux > Image > zImage / Image.gz > Image.gz-dtb
vmlinux: Large sized non-bootable Linux kernel (executable) with debug symbols, just an intermediate step to producing vmlinuz
vmlinux.bin: Same as vmlinux binary but with removed symbols, produced by 'objcopy'
vmlinuz: Compressed and bootable Linux kernel file; one of zImage or bzImage formats; compressed using zlib, LZMA, gzip or bzip2 etc.
zImage: Smaller format, for old kernels
bzImage: Big zImage
Image: vmlinux.bin of embedded devices
Image.gz: zImage or bzImage of embedded devices
.dts (multiple) < > .dtb (1 or more)
Converted using dtc (device tree compiler)
.dtb is appended to zImage / Image.gz i.e. zImage-dtb / Image.gz-dtb (simply concatenate)
zImage-dtb > dtb Can be extracted using split-appended-dtb
Packed as a part of kernel, "--dt" option is not needed when creating boot.img
mkbootimg --kernel *.Image.gz-dtb --ramdisk *.cpio.gz --base . . . --offset . . . --tag-address . . . --cmdline . . .
.dtb is extracted as a part of kernel by unpackbootimg
.dtb < > dtb.img
Converted using mkdtimg
dtb.img is for dtb partition or second stage of boot.img
boot.img is created by using --dt option:
mkbootimg --dt dt.img --kernel *.Image.gz --ramdisk *.cpio.gz --base . . . --offset . . . --tag-address . . . --cmdline . . .
dtb.img is extracted separately by unpackbootimg
Further Reading: Device Tree Overlays and Android Boot and Recovery Images
SYSTEM - ROM / OS
Contains system applications and libraries that have AOSP source code. During normal operation, this partition is mounted read-only; its contents change only during an OTA update or when flashing a new OS. Most ROM's don't allow root level (Admin rights in Windows) access by default. So, "rooting" is required to modify the contents of this partition. This is the actual User Interface we use on our phone i.e. system apps are installed on this partition on /system/app directory. Another important directory is /system/bin which contains executable binaries to perform each and every action by OS in background (as daemons) or by user in shell (bash) scripts or CLI (command line interface). These are native binaries (developed in C / C++ mostly) as opposed to Android apps which are developed in Java. A minimal form of Linux commands is also included in AOSP as toolbox or toybox (or user can add busybox or individual static binaries). /system/lib directory contains native libraries (shared by applications commonly) with .so extensions just like .dll on Windows.
VENDOR
This partition is replaced with a shortcut (symbolic link in fact) to /system/vendor directory. It contains system applications and libraries that do not have source code available on AOSP but added by vendors (OEM's). During normal operation, this partition is mounted read-only; its contents change only during an OTA update. It also contains SoC firmware images i.e. hardware specific libraries and binaries (OpenGL, ISP...).
Proprietary blobs (HALs) usually live in (/system)/vendor as shared libraries (.so files) which are loaded by Android binders when processes call a hardware component. HAL (hardware abstraction layer) is userspace alternative to traditional Linux's system calls for drivers and is a kind of Google's standardization for OEMs/hardware vendors, though being abandoned by mainstream Linux.
PROJECT TREBLE
In an ideal world, there should be a generic AOSP OS and a single kernel for all Android devices, not tied to hardware and vendors. But unfortunately it isn't so because unlike PC world, there is no standardization in mobile world. AOSP is heavily modified on silicon vendor (SoC) as well as phone vendor level. One of the worst outcome of this situation is almost no Long Term Support (LTS). There are delayed or none updates once the consumers have phone, making it vulnerable to security issues and missing new features. Project Treble (starting from Android-8) addresses this issue somewhat by creating a separation between hardware specific code and generic AOSP code.
Previously, phone vendors used to get AOSP code from Google, mixing it with their own cutomizations (UI, apps etc.) and the hardware specific code from SoC vendor. If a minor fix needed to be applied to AOSP code, the whole process had to be repeated because code was intermingled and fixing one thing broke the other. Google resolved this issue by specifying /vendor partition for hardware specific code, /system containing only generic code. Interaction with AOSP code will be through HIDL interfaces, thus making it possible to upgrade the both codes independently. /oem and /odm partitions were added previously for the same purpose.
USERDATA
User applications are installed in different folders under /data. Apps data (user and system) is stored in /data/data. User personal data and some apps data is stored in /data/media. /data/media is also emulated as internal SDCard at /storage/emulated and symlinked at /sdcard. Personalized and apps settings are also stored in this partition. A folder /data/dalvik contains, in simple words, extracted apps to boost loading process. Java bytecode of Android apps is converted to executable code (.odex) by Dalvik Virtual Machine, separate instance of which is launched by zygote (an Android init daemon) for every app.
This partition is not normally touched by the OTA update process. A Factory Reset wipes this partition, normally excluding /data/media i.e. personal data.
When you do a factory reset (AKA: wipe, hard reset, factory wipe, etc.), you are erasing the /data and /cache partitions. Note that a factory reset does NOT put your phone back to its factory state from an OS standpoint. OS upgrades will stay because the OS lives in /system, and that is not touched during a factory reset. So it's not a factory reset. It's a factory DATA reset actually.
RECOVERY
Holds alternate boot partition and the recovery program that lets the device boot into a recovery console for performing advanced recovery and maintenance operations. It contains a second complete Linux system i.e. independent OS, including a user-interface application, kernel and the special recovery binary that reads a package and uses its contents to update i.e. flash or wipe itself or any other partition particularly during OTA updates.
Recovery is also the most commonly used method to flash custom ROM's.
ADB sideload mode through PC is a replacement of flashing files (usually .zip) through Recovery. ADB works when phone is switched on in Recovery (or ROM). ADB/fastboot setup is to be made on PC to use this mode.
CACHE - cached (frequently accessed) data from OS usage and contains the firmware update package downloaded from server during OTA updates. Temporary holding area used by a few applications with the expectation that files can disappear at any time. Major use is by recovery and OTA updates. Recovery last_log is also written to this partition.
6. OTHER PARTITIONS
CUST - also CUSTOM or PRELOAD on some devices, it's used by stock ROM's, holding some preloaded system apps and regional settings which are installed on first use.
MISC - also FOTA on older devices
It's a tiny partition used by recovery to communicate with bootloader store away some information about what it's doing in case the device is restarted while the OTA package is being applied.
It is a boot mode selector used to pass data among various stages of the boot chain (boot into recovery mode, fastboot etc.). e.g. if it is empty (all zero), system boots normally. If it contains recovery mode selector, system boots into recovery mode.
It may also carry some necessarily required information in the form of switches to control hardware or settings related tasks such as CID (Carrier or Region ID) information and USB configurations etc.
PERSIST - contains data which shouldn't be changed after the device is shipped, e.g. DRM related files, sensor reg file (sns.reg) and calibration data of chips; wifi, bluetooth, camera etc.
Some package installers such as OpenGapps also make use of this partition to read configuration file.
EFS, MODEMST1, MODEMST2, FSG, BACKUP
These all are related to IMEI; a unique number used by GSM networks to identify and trace a mobile phone.
EFS may contain hardware info like configuration files, WiFi/BlueTooth MAC’s, IMEI (or ESN for a CDMA based device) etc.
EFS and MODEMST1 may be a single partition on some phones.
FSG (FileSystem Golden copy) and BACKUP are backups of MODEMST1 and MODEMST2 respectively. If MODEMST1 or MODEMST2 are erased (by wrong factory flashing say) and phone notices an invalid partition, FSG and BACKUP will be restored.
MODEMST1 and MODEMST2 also contains modem firmware files.
PARAM - stores a number of parameters, variables and settings of the hardware. It contains info whether MODEMST partitions are backed up or not. Also debug settings, custom ROMs flash count, current stage boot process etc.
OEM - like VENDOR, it incorporates OEM (Original Equipment Manufacturer i.e. hardware manufacturer or Mobile Phone brand) small customization (modifications) to original Android (AOSP) during OTA updates such as customized system properties values etc.
PAD - related to OEM
OTA, FOTA - OTA updates
DDR - Double Data Rate RAM
FSC - Modem FileSystem Cookies
SSD - Secure Software Download, a memory based file system for secure storage, stores some encrypted RSA keys
DEVINFO - device information including: is_unlocked (aboot), is_tampered, is_verified, charger_screen_enabled, display_panel, bootloader_version, radio_version etc. Contents of this partition are displayed by "fastboot oem device-info" command in human readable format. Before loading boot.img or recovery.img, bootloader verifies the locked state from this partition.
CONFIG/FRP/PDB - saves state of Factory Reset Protection (FRP), "Allow bootloader (OEM) unlocking" . (Developer Options), asks already associated account info. This partition is erased/reset if Factory Reset done from Settings.
DEVCFG - used by TZ for upgrades
LKSECAPP - "LK (Little Kernel) Security App", related to RPM, TZ online verification / update
LIMITS - Qualcomm Limits Management Hardware (LMh) driver in SBL writes the data in this partition to use for later reboots
SYSCFG - Qualcomm CPR (Core Power Reduction) Regulator for better performance and power saving of application processor by voltage control
DIP, MDTP - boot verification, use Qualcomm SafeSwitch technology to lock and track theft phones
CMNLIB, KEYMASTER - verified boot
SEC - contains fuse settings, mainly for secure boot (signing bootloaders for chain of trust) and oem setting
KEYSTORE - related to /data Full Disc Encryption (FDE)
MCFG - (Modem Configuration Framework) - on dual SIM devices, loads MBN (modem binary) files depending on SIM/carrier
SPLASH - splash image or boot logo which appears when device boots (at ABOOT stage).
CHGLOGO - charging screen that appears when charger is connected to powered off device.
MSADP, APDP, DPO - related to debug policies
GROW - empty for future expansion
7. FILESYSTEMS
Supported filesystems by your kernel can be viwewd by:
Code:
~# cat /proc/filesystems
Partitions with Mountable Filesystems
Following partitions are mounted during boot process:
system, vendor, odm, userdata (mounted at /data), cache, cust, persist (mounted at /persist or /mnt/vendor/persist), modem (mounted at /firmware or /vendor/firmware_mnt), dsp (mounted at /dsp or /vendor/dsp)
Modem is formatted as vfat while all others are usually ext4 or f2fs on newer devices.
All of these are listed in /fstab.* file which is processes by init. Starting with Android 8.0 (Treble release), fstab.* is moved to /vendor/etc/ and system, vendor and odm entries are included in dtb.
Other partitions don't contain a mountable filesystem. However, we may try to get an idea of the contents by reading smaller partitions e.g.:
Code:
~# cat /dev/block/bootdevice/by-name/config | strings
~# cat /dev/block/bootdevice/by-name/misc | strings
Pseudo / Virtual / in-Memory Filesystems (Kernel space)
These filesystems don't rely on a physical persistent storage but just live in RAM, to provide kernel services interfaces in user space.
rootfs (/) - mounted by kernel before calling init. More details here
sysfs (/sys) - information related to devices, populated by kernel
devpts (/dev/pts) - character device files representing slave side of pseudo terminal pairs
proc (/proc) - information related to all processes, updated as processes are started / killed
tmpfs (/dev) - all device nodes updated from sysfs, accessible from user space
configfs (/config) - intergrated with userspace sdcardfs, controls apps permissions to directories on internal/external sdcard by VOLume Daeomon, a replacement of fusefs
pstore (/sys/fs/pstore) - persistent storage, a replacement of /proc/last_kmsg, saves last kernel console messages on panic / crashes / sudden reboots, solution to volatile nature of pseudo filesystems
cgroup - cgroups manage hardware resources allocation to processes as per load
selinuxfs (/sys/fs/selinux) - implementation of Security-Enahanced Linux, a mandatory access controls (MAC) to manage file permissions, better than traditional Discretionary Access Control (DAC) mechanism (Read-Write-eXecute) of Linux
debugfs (/sys/kernel/debug) - to monitor and debug kernel space implementations from user space
tracefs (/sys/kernel/debug/tracing) - debugfs with better security
functionfs (/dev/usb-ffs/adb) - integrated with configfs, manages USB gadgets, ADB is implemented through functionfs on Android
FILESYSTEM TREE MOUNTED BY INIT: ANDROID vs. LINUX
8. Factory Firmware and Flashable ROMs:
When you flash a custom ROM, that ROM typically includes a kernel and an OS. That means the /boot and /system partitions will be modified at a minimum. Some ROMs require a clean install, so a format of the /data and /cache partitions is sometimes built into the .zip that you flash. This is essentially doing a Factory Reset.
Read here to know more about flashing partitions.
Factory Firmware contains original iamge files of almsot all important partitions. It's provided by OEM's, usually as a package which also incude a flasher software for PC. Or a general flasher software may be uses such as QFIL.
ROM Development
A ROM developer downloads AOSP source code from Google while device tree, driver binaries and kernel source code is provided by (ODM's through) OEM's, if they are generous enough. OEM's manufacture and sell devices themselves while ODM's sell to white-labelers who brand them under their own names. Original Android kernel tree is provided by Google which in turn is taken from Linux and then modified by Google for Android-specific needs.
RELATED:
An Introduction to Android Firmware
First off, don't need be like your never be a dev, lol you never know. Secondly it's a good share. Appreciated
Drivers Partition
What are partitions responsible on drivers like sound and camera,
I restored ROM using TWRP but now, Sound and Camera don't work,
any help?
saprey said:
What are partitions responsible on drivers like sound and camera,
I restored ROM using TWRP but now, Sound and Camera don't work,
any help?
Click to expand...
Click to collapse
Camera and sound are related to your rom i.e. system partition. Do factory data reset or clean install rom
Thanks, but why is my phone talking about a primary partition and a secondary partition?
Tia,
A real newbie
TommyWhite said:
Thanks, but why is my phone talking about a primary partition and a secondary partition?
Tia,
A real newbie
Click to expand...
Click to collapse
At what point talking about primary / secondary partitions? Are you creating new partitions or using some tool / app to view partitions?
Oh, I misunderstood.
It was about public storages (so whats accessible without root, right??).
It said
Public storage (primaire): /storage/emulated/0
Public storage (secondaire): /storage/94F1-34D8 (I didnt realise that was my sd card ...)
RootFs: /
System: /system
Like a said 'a real newbie'
TommyWhite said:
Oh, I misunderstood.
It was about public storages (so whats accessible without root, right??).
It said
Public storage (primaire): /storage/emulated/0
Public storage (secondaire): /storage/94F1-34D8 (I didnt realise that was my sd card ...)
RootFs: /
System: /system
Like a said 'a real newbie'
Click to expand...
Click to collapse
Something like this attachment?
mirfatif said:
Something like this attachment?
Click to expand...
Click to collapse
yes, sorry for the very late response.
While on some devices there is no bootloader partition at all and bootloader(s) resides on SoC.
Click to expand...
Click to collapse
Great post btw! With the bootloader section mentioning like the above, I have a question: I'm having a device with Snapdragon 810 SoC and wasn't able to find the bootloader partition (or at least I didn't know it has because I couldn't get it to boot into that mode). So does that mean the bootloader is on the SoC? How do I figure it out if it exists on the chip?
Hi @mirfatif , what a post! Hats off to you. By the way, where does the blobs/ HALs go when we flash a new ROM zip?
argon9898 said:
Great post btw! With the bootloader section mentioning like the above, I have a question: I'm having a device with Snapdragon 810 SoC and wasn't able to find the bootloader partition (or at least I didn't know it has because I couldn't get it to boot into that mode). So does that mean the bootloader is on the SoC? How do I figure it out if it exists on the chip?
Click to expand...
Click to collapse
Booting in bootloader (or it's equivalent; like fastboot) mode is dependent on the phone manufacturer. Though most of the hardware manufacturers allow users to access bootloader for repair/maintenance or modified boot chain, some may restrict this for Digital Rights Management or to gain forced customer loyalty , irrespective of where bootloader resides. On most phones it's a partition. You may check your partition table to know about all partitions.
azoksky said:
Hi @mirfatif , what a post! Hats off to you. By the way, where does the blobs/ HALs go when we flash a new ROM zip?
Click to expand...
Click to collapse
Thanks for mentioning. I have added this to my post. By "blolbs" you mean DTB or hardware drivers? Well AFAIK, the blobs are included in every ROM where "ROM" is boot.img and system.img at least.
A ROM developer downloads AOSP source code from Google while device tree (map of hardware components), driver binaries and kernel source code is provided by (ODM's through) OEM's, if they are generous enough. OEM's manufacture and sell devices themselves while ODM's sell to white-labelers who brand them under their own names. Original Android kernel tree is provided by Google which in turn is taken from Linux and then modified by Google for Android-specific needs. DTB and drivers are baked with kernel source in boot.img though DTB may live on a separate dtb partition as specified by AOSP (and was the proposed solution for ARM based embedded Linux devices before Android's birth) but I don't think that is widely practiced. DTB is loaded by bootloader at boot time and passed to kernel so that it can discover hardware and create node points accordingly. Proprietary blobs (HALs) usually live in (/system)/vendor as shared libraries (.so files) which are loaded by Android binders when processes call a hardware component. HAL is userspace alternative to traditional Linux's system calls for drivers and is a kind of Google's standardization for OEMs/hardware vendors.
Click to expand...
Click to collapse
Hello everyone. I tell you that one day flashing my oneplus 5 lost the wifi. The MAC address shows me the typical 02: 00: 00: 00: 00: 00 address. The way to fix it is updating the Oreo but I could never do it, it is always in bootloop, I read all the forums and there is no case, do what I always do the same. It happens in many oneplus 5. So I forgot to fix it in that way. The other thing I saw is hundreds of forums with that problem but I could not fix it either, I've been doing it for three months now. What I am trying now is to erase all the partitions except recovery or bootloader but the phone does not start anymore. What I want is to delete all the partitions associated with wifi, delete modem1, modem2, persist, fsg but nothing, I just managed to lose the imei that does not matter to me because I have back up of the efs folder and even the qcn file of the phone. I know it's a lot of work but if someone tells me that they control each partition, I could erase it, load everything from scratch and that's it. Would someone give me a hand so I can fix that damn wifi on the phone ?. Thank you.
--------------------------------------------------------------------------------------------------------------------------------------
drwxr-xr-x 2 root root 1440 1970-05-03 14:23 .
drwxr-xr-x 4 root root 1600 1970-05-03 14:23 ..
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 LOGO -> /dev/block/sde18
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 abl -> /dev/block/sde16
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 ablbak -> /dev/block/sde17
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 apdp -> /dev/block/sde31
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 bluetooth -> /dev/block/sde24
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 boot -> /dev/block/sde19
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 boot_aging -> /dev/block/sde20
lrwxrwxrwx 1 root root 15 1970-05-03 14:23 cache -> /dev/block/sda3
lrwxrwxrwx 1 root root 15 1970-05-03 14:23 cdt -> /dev/block/sdd2
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 cmnlib -> /dev/block/sde27
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 cmnlib64 -> /dev/block/sde29
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 cmnlib64bak -> /dev/block/sde30
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 cmnlibbak -> /dev/block/sde28
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 config -> /dev/block/sda12
lrwxrwxrwx 1 root root 15 1970-05-03 14:23 ddr -> /dev/block/sdd3
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 devcfg -> /dev/block/sde39
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 devinfo -> /dev/block/sde23
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 dip -> /dev/block/sde14
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 dpo -> /dev/block/sde33
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 dsp -> /dev/block/sde11
lrwxrwxrwx 1 root root 15 1970-05-03 14:23 frp -> /dev/block/sda6
lrwxrwxrwx 1 root root 15 1970-05-03 14:23 fsc -> /dev/block/sdf4
lrwxrwxrwx 1 root root 15 1970-05-03 14:23 fsg -> /dev/block/sdf3
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 fw_4g9n4 -> /dev/block/sde45
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 fw_4j1ed -> /dev/block/sde43
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 fw_4t0n8 -> /dev/block/sde46
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 fw_8v1ee -> /dev/block/sde44
lrwxrwxrwx 1 root root 15 1970-05-03 14:23 hyp -> /dev/block/sde5
lrwxrwxrwx 1 root root 15 1970-05-03 14:23 hypbak -> /dev/block/sde6
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 keymaster -> /dev/block/sde25
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 keymasterbak -> /dev/block/sde26
lrwxrwxrwx 1 root root 15 1970-05-03 14:23 keystore -> /dev/block/sda5
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 limits -> /dev/block/sde35
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 logdump -> /dev/block/sde40
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 logfs -> /dev/block/sde37
lrwxrwxrwx 1 root root 15 1970-05-03 14:23 md5 -> /dev/block/sdf5
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 mdtp -> /dev/block/sde15
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 mdtpsecapp -> /dev/block/sde12
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 mdtpsecappbak -> /dev/block/sde13
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 minidump -> /dev/block/sde47
lrwxrwxrwx 1 root root 15 1970-05-03 14:23 misc -> /dev/block/sda4
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 modem -> /dev/block/sde10
lrwxrwxrwx 1 root root 15 1970-05-03 14:23 modemst1 -> /dev/block/sdf1
lrwxrwxrwx 1 root root 15 1970-05-03 14:23 modemst2 -> /dev/block/sdf2
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 msadp -> /dev/block/sde32
lrwxrwxrwx 1 root root 15 1970-05-03 14:23 oem_dycnvbk -> /dev/block/sda7
lrwxrwxrwx 1 root root 15 1970-05-03 14:23 oem_stanvbk -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 1970-05-03 14:23 param -> /dev/block/sda9
lrwxrwxrwx 1 root root 15 1970-05-03 14:23 persist -> /dev/block/sda2
lrwxrwxrwx 1 root root 15 1970-05-03 14:23 pmic -> /dev/block/sde8
lrwxrwxrwx 1 root root 15 1970-05-03 14:23 pmicbak -> /dev/block/sde9
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 recovery -> /dev/block/sde22
lrwxrwxrwx 1 root root 15 1970-05-03 14:23 reserve -> /dev/block/sdd1
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 reserve1 -> /dev/block/sda10
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 reserve2 -> /dev/block/sda11
lrwxrwxrwx 1 root root 15 1970-05-03 14:23 rpm -> /dev/block/sde1
lrwxrwxrwx 1 root root 15 1970-05-03 14:23 rpmbak -> /dev/block/sde2
lrwxrwxrwx 1 root root 15 1970-05-03 14:23 sec -> /dev/block/sde7
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 splash -> /dev/block/sde34
lrwxrwxrwx 1 root root 15 1970-05-03 14:23 ssd -> /dev/block/sda1
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 sti -> /dev/block/sde38
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 storsec -> /dev/block/sde41
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 storsecbak -> /dev/block/sde42
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 system -> /dev/block/sde21
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 toolsfv -> /dev/block/sde36
lrwxrwxrwx 1 root root 15 1970-05-03 14:23 tz -> /dev/block/sde3
lrwxrwxrwx 1 root root 15 1970-05-03 14:23 tzbak -> /dev/block/sde4
lrwxrwxrwx 1 root root 16 1970-05-03 14:23 userdata -> /dev/block/sda13
lrwxrwxrwx 1 root root 15 1970-05-03 14:23 xbl -> /dev/block/sdb1
lrwxrwxrwx 1 root root 15 1970-05-03 14:23 xblbak -> /dev/block/sdc1
thank you
This is one of the best posts that I've ever read. I'm a hobbyist and reverse engineer learn. My primary phones are Samsung S 6 7 and 8 and I've soft bricked phones them more times than I can count (but recovered) justifying it as a learning experience. Sort of like putting your hand in the fire several times and calling it a learning experience. your post opens up more questions which are great. I root all my phones and I have a fear of new security patches disguised as updates disabling what methods work last week so to speak
So if I understand finally there is a section in bootloaders which is the first bootloader that is static yet upgradable but not downgradable as you referred to like the BIOS on PCs which acts as a verification process so you can't flash downgradable security patches. Much like I've encountered with partcyborg great work on rooting the S8 snapdragon however once you upgraded to the bootloader 2 you couldn't go back to the bootloader one. This is in reference to the build, not the partition.
If someone does reply, I'd like to know can you mod a certain file and Odin in the bootloader section when flashing an update to ensure that you stay at a certain bootloader level while the other files such as AP CP and CSC remain intact from the sam mobile stock firmware.(which I assume the term combo firmware file originates)
My most recent encounters are the device and binary are not the same which I attribute to this problem.
In theory from what I understand the phone has a section that is not Factory resettable which is the NAND that contains read-only but system upgrade information? However, it can be modified by a power Superuser rooted? This obviously risking hard bricking a phone
When upgrading firmware specifically the bootloader file in Odin what file(s) {bin} are essential to the new modification patches and can those files be substituted?
Any comment is considered very helpful. Odin itself is coming out with different versions for structures (prince cosmey) for example.
I explore the system file structure often wondering what I could change or alter as simple as a 0 or 1 or a true or a false to enable or disable my ability to access what I feel I need to access.
I could buy the z3x Samprotools but it defeats my intentions to learn the details.
If you do have a suggestion on a GUI Windows-based tool it would be great. Don't know Linux just as a footnote
Once again what a great post and definition of the different sections of terminology it's just enough to educate me and confuse me at the same time keep doing what you're doing. Any tricks or tips will be very appreciated.
partitions
What are partitions responsible on drivers like sound and camera,
Curious Q.!
what about these two ?
Code:
rpm -> /dev/block/mmcblk0p2
rpmbak -> /dev/block/mmcblk0p11
my phone is MOTO-G5-PLUS (potter)
whole partition table is here:
Code:
←7←[r←[999;999H←[6n←8potter:/ # ls -l /dev/block/bootdevice/by-name
total 0
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 DDR -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 20 1970-08-28 23:29 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 abootbak -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 apdp -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 boot -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 cache -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 carrier -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 cid -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 20 1970-08-28 23:29 cmnlib -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 1970-08-28 23:29 cmnlib64 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 cmnlib64bak -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 cmnlibbak -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 20 1970-08-28 23:29 devcfg -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 devcfgbak -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 dip -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 dpo -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 dsp -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 frp -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 fsc -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 fsg -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 hw -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 20 1970-08-28 23:29 keymaster -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 keymasterbak -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 limits -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 logo -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 logs -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 metadata -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 misc -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 modem -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 modemst1 -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 modemst2 -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 mota -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 msadp -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 oem -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 padA -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 persist -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 20 1970-08-28 23:29 prov -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 provbak -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 recovery -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 20 1970-08-28 23:29 rpm -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 rpmbak -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 1970-08-28 23:29 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 sbl1bak -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 sec -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 sp -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 syscfg -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 system -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 20 1970-08-28 23:29 tz -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 tzbak -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 userdata -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 utags -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 1970-08-28 23:29 utagsBackup -> /dev/block/mmcblk0p26
potter:/ #
GEEKOFIA said:
what about these two ?
Code:
rpm -> /dev/block/mmcblk0p2
rpmbak -> /dev/block/mmcblk0p11
my phone is MOTO-G5-PLUS (potter)
Click to expand...
Click to collapse
RPM (Resource/Power Management) or Primary BootLoader (PBL); controls power to radio, modem etc.
koler386 said:
What are partitions responsible on drivers like sound and camera,
Click to expand...
Click to collapse
Kernel and system
mirfatif said:
what about these two ?
RPM (Resource/Power Management) or Primary BootLoader (PBL); controls power to radio, modem etc.
Click to expand...
Click to collapse
I got a script from a xda thread in which OP mentioned that this script is for wiping dalvik/ART cache.
Before flashing it i decided to analyse it,what i found that it was erasing my RPM partition on mmcblk0p2.
Is it really for dalvik cache ?
Hi guys!
You can donate to me here https://paypal.me/penvineeth and @cerg2010cerg2010 through paypal.
@cerg2010cerg2010 PAYPAL EMAIL: [email protected] OR QIWI: +79157840294
Disclaimer:
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Bootloader is unlocked in LG G4c!
-> Requirements:
(1) LG UP
(2) Device must be: LG G4c
Fixed: Brightness.
Make sure you have Lollipop firmware.
(1) Download this patched aboot file: https://drive.google.com/file/d/11xFfJipkSTZ1-DRRI1kebmotIm0zM89K/view?usp=drivesdk
(2) Connect your phone to the computer. In command prompt, type "adb shell".
(3) Transfer the aboot file into /sdcard/ folder.
(4) Type "su" to enter the root shell. Then type "dd if=/sdcard/aboot_5120.bin of=/dev/block/mmcblk0p5" (without quotes).
(5) Restart your phone by typing "reboot".
You have unlocked your bootloader!
Refer Notes for more information.
-> Notes:
1) The aboot_5120.bin is the patched version of aboot partition of your device. Secure boot validation has been patched such that secure boot is always valid, so you can flash your own TWRP and Custom ROM.
2) Don't upgrade to any updated version of Android if you get any through OTA update. It might brick your device.
@pvineeth97 how do we flash twrp after the bootloader unlock?
ahmed546 said:
@pvineeth97 how do we flash twrp after the bootloader unlock?
Click to expand...
Click to collapse
Using flashfire app
Wysłane z mojego LG-H525n przy użyciu Tapatalka
---------- Post added at 02:07 PM ---------- Previous post was at 02:06 PM ----------
Isn't that mmcblk0p7 partition ?
Wysłane z mojego LG-H525n przy użyciu Tapatalka
@pvineeth97 can you post this guide also in the g4c forum?
ahmed546 said:
@pvineeth97 can you post this guide also in the g4c forum?
Click to expand...
Click to collapse
There is no proper LG G4c forum. First tell mods to create that then I will post it there.
Anyways I posted: https://forum.xda-developers.com/android/development/guide-bootloader-unlocked-t3637155
pvineeth97 said:
There is no proper LG G4c forum. First tell mods to create that then I will post it there.
Anyways I posted: https://forum.xda-developers.com/android/development/guide-bootloader-unlocked-t3637155
Click to expand...
Click to collapse
You sure it's mmcblk0p5 partition not mmcblk0p7 ?
<Snip - Mod EDIT>
And about the patched aboot for LG G4. They asked me to patch their bootloader to try if it works. Patched aboot method doesn't support phones with Snapdragon 8xx. It only supports Snapdragon 410 SoC. Even after I told them they don't listen.
DonOleq said:
You sure it's mmcblk0p5 partition not mmcblk0p7 ?
Click to expand...
Click to collapse
Yep, check one of my very few earlier posts. We got the mapping done and it's the right partition.
Guys lets keep it civil. This is why we dont have any lg devs left everyone wants to raise cain and scream and hollar. No one wants to read this crap. This patch works on the 410s. Doesnt work on 8 series.
Dont hate because your devices are not included thats just how it is blame lg and qualcomm
<Snip - Mod EDIT>
Did you even test it? I don't think so. It's against XDA rules, I'll report this today let's see what mods will do. I wouldn't trust any of your work
Sent from my LG-H815 using Tapatalk
Minto107 said:
Did you even test it? I don't think so. It's against XDA rules, I'll report this today let's see what mods will do. I wouldn't trust any of your work
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Yes. I got it tested. I gave you the link for proof too. I don't care what you trust and what you don't!
Here is the link: https://forum.xda-developers.com/showpost.php?p=73030513&postcount=105
If you show this aggression towards LG rather than accusing me atleast you might even get bootloader unlock for G4.
<Snip - Mod EDIT>
@Minto107 it was tested. The user @Willstetictac even send @pvineeth97 a PM about his issue. He just had a problem with his brightness thats all. TWRP worked and the bootloader unlock worked. @pvineeth97 already gave proof that it worked, the mods will see that.
ahmed546 said:
@Minto107 it was tested. The user @Willstetictac even send @pvineeth97 a PM about his issue. He just had a problem with his brightness thats all. TWRP worked and the bootloader unlock worked. @pvineeth97 already gave proof that it worked, the mods will see that.
Click to expand...
Click to collapse
Lol ive had briteness issues in twrp before. On a lot of devices actually.
I always chalked it to twrp. Not being say faulty but naturally dim.
---------- Post added at 05:55 AM ---------- Previous post was at 05:42 AM ----------
Minto107 said:
Did you even test it? I don't think so. It's against XDA rules, I'll report this today let's see what mods will do. I wouldn't trust any of your work
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
I would thank you also. Im outa thanks for the day. But this is the proper procedure. If it is found to be be a fluke they will end it. As stated it has been suposedly confirmed now if that 1 confirmation is also "in on it"
The mods will be able to tell. I just hate to see people fightin. Throughout the threads.
Im just trying to keep the peace. Wich i understand exactly where you are coming from.
Sorry I didn't check the link, stuff is working, sorry that I was rude. I just wanted to warn people that they should proceed with caution as you already tried to unlock G4 Dual sim and we all know how it ended. I don't own G4c so obviously I couldn't give it a try but as its tested and proofed to be working then it's all right of course
Once again sorry for being rude
Sent from my LG-H815 using Tapatalk
So i have it straight from the 1 confirmation. The backlight isnt working in o.s. so aboot needs to be reworked.
DO NOT ATTEMPT UNTIL FIXXED
Said problem isnt in twrp so yes twrp works but this has broight on a diffrent issue.
---------- Post added at 06:45 AM ---------- Previous post was at 06:42 AM ----------
pvineeth97 said:
Yes. I got it tested. I gave you the link for proof too. I don't care what you trust and what you don't!
Here is the link: https://forum.xda-developers.com/showpost.php?p=73030513&postcount=105
If you show this aggression towards LG rather than accusing me atleast you might even get bootloader unlock for G4.
Click to expand...
Click to collapse
So it does seem as if this does bring out an issue that needs to be fixxed. Props on the modded aboot without a secure boot error. But backlight in os is kinda a big deal. U need to disclose this
TheMadScientist420 said:
So i have it straight from the 1 confirmation. The backlight isnt working in o.s. so aboot needs to be reworked.
DO NOT ATTEMPT UNTIL FIXXED
Said problem isnt in twrp so yes twrp works but this has broight on a diffrent issue.
---------- Post added at 06:45 AM ---------- Previous post was at 06:42 AM ----------
So it does seem as if this does bring out an issue that needs to be fixxed. Props on the modded aboot without a secure boot error. But backlight in os is kinda a big deal. U need to disclose this
Click to expand...
Click to collapse
I just got to know yesterday night.
TheMadScientist420 said:
So i have it straight from the 1 confirmation. The backlight isnt working in o.s. so aboot needs to be reworked.
DO NOT ATTEMPT UNTIL FIXXED
Said problem isnt in twrp so yes twrp works but this has broight on a diffrent issue.
---------- Post added at 06:45 AM ---------- Previous post was at 06:42 AM ----------
So it does seem as if this does bring out an issue that needs to be fixxed. Props on the modded aboot without a secure boot error. But backlight in os is kinda a big deal. U need to disclose this
Click to expand...
Click to collapse
I have updated the "main post". Sorry I forgot to update before. Thanks for reminding.
https://forum.xda-developers.com/g4/development/guide-bootloader-unlocked-t3637105/
Minto107 said:
Sorry I didn't check the link, stuff is working, sorry that I was rude. I just wanted to warn people that they should proceed with caution as you already tried to unlock G4 Dual sim and we all know how it ended. I don't own G4c so obviously I couldn't give it a try but as its tested and proofed to be working then it's all right of course
Once again sorry for being rude
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
No problem.
Hi all,
Just to remove the last few doubts, I've checked on my phone the partition layout.
The aboot is /dev/block/mmcblk0p5 .
It's for a French Open H525n.
C:\android-sdk\platform-tools>adb shell
[email protected]:/ $ su
[email protected]:/ # ls -al /dev/block/platform/7824900.sdhci/by-name
lrwxrwxrwx root root 1970-03-16 06:08 DDR -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-03-16 06:08 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-03-16 06:08 abootbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-03-16 06:08 boot -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-03-16 06:08 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-03-16 06:08 cust -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-03-16 06:08 drm -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-03-16 06:08 eksst -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-03-16 06:08 encrypt -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-03-16 06:08 factory -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-03-16 06:08 fota -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-03-16 06:08 fsc -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-03-16 06:08 fsg -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-03-16 06:08 grow -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-03-16 06:08 hyp -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-03-16 06:08 hypbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-03-16 06:08 laf -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-03-16 06:08 metadata -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-03-16 06:08 misc -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-03-16 06:08 modem -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-03-16 06:08 modemst1 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-03-16 06:08 modemst2 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-03-16 06:08 mpt -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-03-16 06:08 pad -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-03-16 06:08 persist -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-03-16 06:08 persist-lg -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-03-16 06:08 persistent -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-03-16 06:08 rct -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-03-16 06:08 recovery -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-03-16 06:08 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-03-16 06:08 rpmbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-03-16 06:08 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-03-16 06:08 sbl1bak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-03-16 06:08 sec -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-03-16 06:08 sns -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-03-16 06:08 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-03-16 06:08 system -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-03-16 06:08 tz -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-03-16 06:08 tzbak -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-03-16 06:08 userdata -> /dev/block/mmcblk0p39
Any news in fixing the bootloader?
Yesterday I flashed BitO-KU kernel with dtb and blob file provided in this thread https://forum.xda-developers.com/sh.../tweaked-kernel-nvidia-shield-tablet-t3069776 on my Shield Tablet K1. Since then the problem started and my tab didn't boot.
How problem started?
Flashed BitO-KU kernel https://forum.xda-developers.com/sh.../tweaked-kernel-nvidia-shield-tablet-t3069776
Reboot (working fine)
Flashed dtb file "tegra124-tn8-p1761-1270-a04-e-battery.dtb" (provided in same thread)
Reboot (stuck on bootloader)
Flashed blob file (provided in same thread)
Reboot (stuck on bootloader)
After that I flashed factory images provided on Nvidia official site for K1 Tablet but still not booting. Although many times I have successfully flashed firmware images before, but only this time it's not booting. I think that the dtb and blob files I flashed previously with BitO-KU kernel were for Original Shield Tablet not for K1, that's why my tablet bricked.
What's working and what's not:
Bootloader is working and able to flash files using fastboot. But it's niether showing any error nor booting after flashing firmware images.
Recovery Not Working. Flashed various versions of TWRP from official website, none of them is working. Even tried directly booting to twrp recovery instead of flashing, still not working.
Any help is appreciated.
Sorry for my bad English!
Did you flash the stock system file and the stock blob? I think the instructions (recovery image) say to flash a few other things (recovery, userdata) but I was able to just flash the system and blob (flashing stock recovery might not hurt either).
Also, please don't apologize for your bad English. Your post is very well written, and I never would have guessed you are not a native English speaker.
redpoint73 said:
Did you flash the stock system file and the stock blob? I think the instructions (recovery image) say to flash a few other things (recovery, userdata) but I was able to just flash the system and blob (flashing stock recovery might not hurt either).
Also, please don't apologize for your bad English. Your post is very well written, and I never would have guessed you are not a native English speaker.
Click to expand...
Click to collapse
Hi @redpoint73, thanks for your response. Yes I did flash the stock system file, stock blob file and stock boot file. Still it wasn't booting.
And thanks for your compliment about my English.
Hello,
I was in a similar situation but finally managed to fix this boot issue on my K1.
What I have, Nvidia Shield Tablet K1
What I did wrong, flashed via fastboot a stock ROM image from Nvidia GameWorks - SHIELD Open Source Resources and Drivers
But not the correct one for Shield K1
I had the following steps for this recovery ROM (not for K1 tablet...):
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
fastboot reboot
Flashing them failed on userdata (not enough space) and results in K1 to be stuck on boot and the Nvidia logo for ages.
(For a K1 tablet, you don't have a userdata and dtb flash image steps). I think what messed up my K1 is the dtb flashing step because formating, erasing and flashing recovery, boot, system and userdata partitions didn't have any effects on being stuck at boot.
What I did to get out of this mess and what you need:
Stock ROM K1: nv-recovery-image-shield-tablet-k1-factory0_0_0
fastboot + adb
twrp for K1 for revovery partitions
And know your K1 partitions
Via adb shell:
cd /etc
cat recovery.fstab
shieldtablet:/etc # cd /etc
shieldtablet:/etc # cat recovery.fstab
Result:
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,data=writeback,nodelalloc wait,formatable
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,data=writeback,noauto_da_alloc wait,check,formatable,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/RP3 /usercalib ext4 noatime,data=writeback wait,formatable
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/MDA /metadata emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/devices/platform/sdhci-tegra.2/mmc_host* auto vfat defaults voldmanaged=sdcard1:auto,encryptable=userdata
/devices/tegra-ehci.0/usb* auto vfat defaults voldmanaged=usb:auto
/dev/block/platform/sdhci-tegra.2/by-num/p1 /sdcard vfat defaults recoveryonly
Via adb shell:
cd dev/block/platform/sdhci-tegra.3/by-name/
ls -al
Resust:
shieldtablet:/dev/block/platform/sdhci-tegra.3/by-name # ls -al
total 0
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
drwxr-xr-x 2 root root 520 2019-11-19 08:27 .
drwxr-xr-x 4 root root 600 2019-11-19 08:27 ..
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 APP -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 CAC -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 CHG -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 DTB -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 2019-11-19 08:27 EKS -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 2019-11-19 08:27 FB -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 FBP -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 FCG -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 FCT -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 GPT -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 LBP -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 LNX -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 MDA -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 MSC -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 20 2019-11-19 08:27 NCT -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2019-11-19 08:27 RP1 -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2019-11-19 08:27 RP2 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 2019-11-19 08:27 RP3 -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 2019-11-19 08:27 RP4 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 SOS -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 2019-11-19 08:27 TOS -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 UDA -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 USP -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 20 2019-11-19 08:27 WB0 -> /dev/block/mmcblk0p5
MAP boot, system, blob (staging) partitions with corresponding memory block
Ex: boot -> LNX -> /dev/block/mmcblk0p12
Via adb shell and using the images from K1 ROM nv-recovery-image-shield-tablet-k1-factory0_0_0 (check if your tablet k1 has the same partitions)
dd if=boot.img of=/dev/block/mmcblk0p12
dd if=system.img of=/dev/block/mmcblk0p13
dd if=blob of=/dev/block/mmcblk0p16
By getting from another ROM: tegra124-tn8-p1761-1270-a04-e-battery.dtb (renamed tegra124.dtb)
dd if=tegra124.dtb of=/dev/block/mmcblk0p11
Still failing... and stuck at boot so I decided to restore nv-recovery-image-shield-tablet-k1-factory0_0_0 via fastboot a last time but cleaned everything first:
twrp wipe all system cache data
then
fastboot flash system
fastboot erase boot
fastboot flash boot
fastboot erase staging
fastboot flash staging blob
fastboot reboot
And my Shield Tablet K1 was working again!! And very happy to have my Nvidia Shield K1 back (with latest LineageOS 15.1 ROM and working like a charm)!
I did a lot of stock ROM erase / format / restore on these partitions before and they all failed before. But I thing here the main difference is around the DTB partition.
May be the dd if=tegra124.dtb of=/dev/block/mmcblk0p11 step did properly restore the dtb info and partition or actually "corrupt" it in a way that cause the K1 to properly boot back. I don't know.
Hope that can help someone in the same situation!
Phone: TCL C5 with Android 8.1
i have tested mtk-su and it works
i can make a copy of the boot partition and everything
i have unlocked the bootloader
for some reason i have 2 boot files ( or more )
lrwxrwxrwx 1 root root 21 2020-12-03 16:24 boot -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 2020-12-03 16:24 boot2 -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 20 2020-12-03 16:24 boot_para -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 23 2020-12-03 16:24 preloader_a -> /dev/block/mmcblk0boot0
lrwxrwxrwx 1 root root 23 2020-12-03 16:24 preloader_b -> /dev/block/mmcblk0boot1
i don't know what is going on here but i can patch boot and boot2 with magisk
the files goes from 24 MB to 7.7 MB so i think this is kinda weird
i want to know how i can make a good backup of everything before trying to flash anything
so i can prevent bootloop
and i want to know if there is any way to test the boot.img before flashing it
if not i would like some help to backup everything before flashing it
i patch the boot.img and try doing "fastboot boot boot.img"
but the magisk manager doesn't show installed or anything so i don't think "fastboot boot" works in this situation
is there anything i can do to be sure before flashing?
Update: seems like i only need boot and boot2
maybe patching both and flashing it?
seems a little risky, they both are the same file with the same md5sum hash