Sample Header Ad - 728x90

Android Enthusiasts

Q&A for enthusiasts and power users of the Android operating system

Latest Questions

0 votes
0 answers
378 views
adb sideload factory mode file ends up in error
On Pixel 8a, I was trying to downgrade from Android 15 to Android 14. So, I downloaded https://dl.google.com/dl/android/aosp/akita-ap2a.240905.003.a1-factory-39b3cda7.zip which is the last factory release of Android 14. However, `adb sideload` the above zip ends up in an error. It says: ERROR: recov...
On Pixel 8a, I was trying to downgrade from Android 15 to Android 14. So, I downloaded https://dl.google.com/dl/android/aosp/akita-ap2a.240905.003.a1-factory-39b3cda7.zip which is the last factory release of Android 14. However, adb sideload the above zip ends up in an error. It says: ERROR: recovery: footer is wrong ERROR: recovery: Signature verification faield ERROR: recovery: error 21 Install from ADB completed with status 2. Installation aborted. On the top of the phone, I also get WARNING: Previous installation has failed. Your device may fail to boot if you reboot or power off now. And Reboot to bootloader is highlighted. Should I be doing this? The other options are Reboot system now (unlikely this should be done given the above message) Enter fastboot Apply update from adb Apply update from sdcard Wipe data/factory reset Mount /system View recovery logs Run graphics test Run locale test Power off What should I be doing here? Would wipe data/factory reset resolve the issue? I may note that I checked the sha256sum and it does match. I can try sideloading again, but the device is no longer listed at this point.
user3236841 (141 rep)
Dec 8, 2024, 04:11 AM • Last activity: Dec 8, 2024, 05:48 AM
1 votes
0 answers
57 views
To what extent are the "factory settings" immutable?
**Context**: I have a Samsung phone and I am doing a "reset to factory settings" **Question**: could an app that was installed before have altered the factory settings? I am not very acquainted with Android (as opposed to Linux) but my understanding is that, for a given Android installation, specifi...
**Context**: I have a Samsung phone and I am doing a "reset to factory settings" **Question**: could an app that was installed before have altered the factory settings? I am not very acquainted with Android (as opposed to Linux) but my understanding is that, for a given Android installation, specific code is loaded during boot. This code ("Android OS") is initially present on a market phone and then updated with the vendor patches as they are published. They modify this original code. You end up with an "up-to-date Android OS". I guess that the updates are signed so the OS you have is always "vendor-certified". This "patched up-to-date Android OS" is what you get by restoring your phone to factory settings. With the above in mind - **is there a way for a non-vendor application to modify this "up-to-date Android OS"?** Note: I am not addressing here the situation with alternative OS reflashes.
WoJ (633 rep)
Nov 6, 2024, 10:14 AM • Last activity: Nov 6, 2024, 02:05 PM
1 votes
0 answers
162 views
How to successfully execute a script from init.rc
I have an old stock Android 5.1.1. It has custom twrp recovery and is rooted. I have the stock boot.img file and am able to edit the init.rc and repack and flash it back with `fastboot flash boot boot.img`. No problem there. And after flashing the boot.img, I can `cat /init.rc` and can see the chang...
I have an old stock Android 5.1.1. It has custom twrp recovery and is rooted. I have the stock boot.img file and am able to edit the init.rc and repack and flash it back with fastboot flash boot boot.img. No problem there. And after flashing the boot.img, I can cat /init.rc and can see the changes that I made to run a script from /system/xbin/. However, the script does not execute at all. On the very end of init.rc, I placed this line of code on property:sys.boot_completed=1 start initAsic service initAsic /system/xbin/script.sh seclabel u:r:init:s0 user root group root oneshot disabled The script.sh is already chmod to 755 in /system/xbin/script.sh and in script.sh, there this echo "hello" > /data/local/tmp/file.test iptables -P FORWARD DROP The problem is, it doesn't work. So googling further revealed that I need to set selinux mode to permissive. And so I did with, setenforce 0 It does set SELinux to permissive, however it's only temporary, because on reboot it goes back to enforcing mode. I was wondering if there was any way for me to modify the content within boot.img that would lead SELinux to be permissive always.And also, is permissive mode the real reason why my init script isn't running, or am I doing something wrong?
randomuser (11 rep)
Aug 10, 2024, 08:09 AM • Last activity: Aug 10, 2024, 08:15 AM
8 votes
3 answers
15443 views
Unable to flash factory ROM on Pixel
I'm trying to restore the factory ROM on my Pixel. I've downloaded and unpacked a [factory image](https://developers.google.com/android/images) for my phone, and when I run `sudo ./flash-all.sh` I get `FAILED (remote: partition [bootb] doesn't exist)`. Here's the whole transcript. Can anyone suggest...
I'm trying to restore the factory ROM on my Pixel. I've downloaded and unpacked a [factory image](https://developers.google.com/android/images) for my phone, and when I run sudo ./flash-all.sh I get FAILED (remote: partition [bootb] doesn't exist). Here's the whole transcript. Can anyone suggest a workaround? target reported max download size of 536870912 bytes sending 'bootloaderb' (32728 KB)... OKAY [ 0.836s] writing 'bootloaderb'... (bootloader) Valid bootloader version. OKAY [ 1.600s] finished. total time: 2.435s rebooting into bootloader... OKAY [ 8.593s] finished. total time: 8.693s target reported max download size of 536870912 bytes sending 'radiob' (57192 KB)... OKAY [ 1.428s] writing 'radiob'... OKAY [ 0.909s] finished. total time: 2.337s rebooting into bootloader... OKAY [ 0.006s] finished. total time: 0.106s target reported max download size of 536870912 bytes archive does not contain 'boot.sig' archive does not contain 'recovery.img' archive does not contain 'system.sig' archive does not contain 'vendor.sig' wiping userdata... Creating filesystem with parameters: Size: 122633060352 Block size: 4096 Blocks per group: 32768 Inodes per group: 8192 Inode size: 256 Journal blocks: 32768 Label: Blocks: 29939712 Block groups: 914 Reserved block group size: 1024 Created filesystem with 11/7487488 inodes and 518062/29939712 blocks -------------------------------------------- Bootloader Version...: 8996-012001-1610061102 Baseband Version.....: 8996-012511-1611190200 Serial Number........: XXXXXXXXXXXX -------------------------------------------- checking product... OKAY [ 0.050s] checking version-bootloader... OKAY [ 0.051s] checking version-baseband... OKAY [ 0.050s] sending 'bootb' (24821 KB)... OKAY [ 0.642s] writing 'bootb'... (bootloader) Flashing active slot "_b" FAILED (remote: partition [bootb] doesn't exist) finished. total time: 1.095s
Jack O'Connor (131 rep)
Dec 16, 2016, 04:33 PM • Last activity: Jan 21, 2024, 02:36 AM
2 votes
0 answers
316 views
simg2img silenting failing to convert Fairphone 4 super.img?
I want to mount super.img from [Fairphone 4's factory images](https://support.fairphone.com/hc/en-us/articles/18896094650513). ```bash > file super.img super.img: Android sparse image, version: 1.0, Total of 1572864 4096-byte output blocks in 229 input chunks. ``` I installed the [android-simg2img p...
I want to mount super.img from [Fairphone 4's factory images](https://support.fairphone.com/hc/en-us/articles/18896094650513) .
> file super.img      

super.img: Android sparse image, version: 1.0, Total of 1572864 4096-byte output blocks in 229 input chunks.
I installed the [android-simg2img package](https://aur.archlinux.org/packages/android-simg2img) to convert this to an ext4 image. After executing simg2img, no errors are generated, but trying to mount the file fails.
> file super.raw.img
super.raw.img: data
> sudo mount -o loop ./super.out.img /mnt/image
mount: /mnt/image: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
       dmesg(1) may have more information after failed mount system call.
> sudo dmesg

[1074956.090619] loop0: detected capacity change from 0 to 12582912
[1074956.092396] FAT-fs (loop0): bogus number of reserved sectors
[1074956.092398] FAT-fs (loop0): Can't find a valid FAT filesystem
[1074956.092450] EXT4-fs (loop0): VFS: Can't find ext4 filesystem
[1074956.092560] EXT4-fs (loop0): VFS: Can't find ext4 filesystem
[1074956.092632] EXT4-fs (loop0): VFS: Can't find ext4 filesystem
[1074956.093484] NILFS (loop0): couldn't find nilfs on the device
How can I mount the image?
Mattwmaster58 (234 rep)
Dec 9, 2023, 09:39 AM
0 votes
1 answers
1044 views
ADB sideload regularly loads LineageOS ROM, but gets stuck at 0% with stock firmware, why?
I'm trying to restore the stock firmware for a Samsung S10e. It's currently setup with the LineageOS recovery image, and the LineageOS firmware. I've rebooted in the (LineageOS) recovery, factory reset everything, and now I'm trying to sideloading the factory image (`G970foo_bar_baz.zip`), however,...
I'm trying to restore the stock firmware for a Samsung S10e. It's currently setup with the LineageOS recovery image, and the LineageOS firmware. I've rebooted in the (LineageOS) recovery, factory reset everything, and now I'm trying to sideloading the factory image (G970foo_bar_baz.zip), however, it's stuck at 0%. If I try to sideload LineageOS again, it sideloads without any problem. Should I keep waiting? Since the factory ROM is very large (5.9GiB vs 800 MiB), it's possible that it's normal that it takes a long time before the sideload starts, however, I don't know how long should I wait.
Marcus (103 rep)
Feb 22, 2023, 11:37 AM • Last activity: Feb 23, 2023, 03:18 PM
1 votes
1 answers
2527 views
Adding stock image as secondary ROM in MultiROM
I have a Nexus 5 and root. I also use the MultiROM application. I want to create a secondary ROM from stock. However, I cannot flash factory images, hence need to make flashable zip out of it. How do I do it? What other method is recommended?
I have a Nexus 5 and root. I also use the MultiROM application. I want to create a secondary ROM from stock. However, I cannot flash factory images, hence need to make flashable zip out of it. How do I do it? What other method is recommended?
Kj1594 (21 rep)
Oct 13, 2015, 07:06 PM • Last activity: Mar 13, 2022, 10:03 AM
1 votes
1 answers
1562 views
When should I use/not use '-w' for fastboot flashing?
When should I use/not use '-w' for fastboot flashing? Say I were to be manually flashing each img in the zip of a [factory image][1]. Why one way or another? Do certain .img's need to be erased first? I recently had a misflash where my internal storage was reduced from 64gb to 32gb and I am wonderin...
When should I use/not use '-w' for fastboot flashing? Say I were to be manually flashing each img in the zip of a factory image . Why one way or another? Do certain .img's need to be erased first? I recently had a misflash where my internal storage was reduced from 64gb to 32gb and I am wondering if it could have been avoided. I resolved my particular problem by using Format Data in TWRP.
Status3543 (1250 rep)
Jun 22, 2015, 08:06 PM • Last activity: Feb 9, 2022, 02:04 AM
2 votes
1 answers
1174 views
MediaTek K80 is stuck , computer store tells me the firmware chip is corrupted
To start with I did a factory reset to wipe out my files and apps before giving my tablet to my niece. After the reset the tablet is stuck at the screen with the android guy in the corner and MEDIATEK across the screen. it will not boot any further. I took the tablet to a repair store and 3 days lat...
To start with I did a factory reset to wipe out my files and apps before giving my tablet to my niece. After the reset the tablet is stuck at the screen with the android guy in the corner and MEDIATEK across the screen. it will not boot any further. I took the tablet to a repair store and 3 days later he tells me the chip is corrupted and he cant(be bothered?) do anything because its a Chinese clone? I have researched many sites but cannot find a scatter file or rom image etc.. the following is what I have found inside my tablet: On a stickered chip: E960 V1.2 YK18091021 6580A/WA/1+16/3G/B15 GXQ 2018/09/26 DL_BT_MM_QC_ ALSO, TAKEN FROM "ABOUT TABLET" : Android Version:7.0 Android Security Patch level: 1Feb.2016 Baseband version: MOLY.WR8.W1449.MD.WG.MP.V23, 2017/05/16 17:00 Kernel version: 3.18.19 c@c-S2600JF #2 ThuOct11 17:29:47 cst 2018 Build Number: MRA58K test-keys Custom Build version: E960v1.1_HJC_03_3G_HBOE_FL_WXGA_bigbattery_4_64 I am completely lost and would really appreciate any help possible. Thank you in advance, John Sweeney
John Sweeney (21 rep)
Feb 18, 2021, 02:17 AM • Last activity: Dec 16, 2021, 04:15 PM
2 votes
0 answers
2293 views
Couldn't unlock phone and stuck in a reboot loop after my battery completely died once, sideload doesn't fix
So one day my Pixel 3a's battery died (and since I quite urgently need the phone) I force it to boot up (cause sometimes you can still juice out a few minutes) but as it booted up, the wallpaper displayed correctly but the date/time is wrong, when I drag down the control center it's blank (though it...
So one day my Pixel 3a's battery died (and since I quite urgently need the phone) I force it to boot up (cause sometimes you can still juice out a few minutes) but as it booted up, the wallpaper displayed correctly but the date/time is wrong, when I drag down the control center it's blank (though it sometimes pop up fine, but I think just once), stuck within plane mode (though I doesn't turn it on prior the shutdown), battery showing blank while in power off it clearly shows it charged to certain percentage of battery, and unlocking doesn't do anything. Then after a while the phone just reboots itself again and now I'm stuck within this loop. My first thought is to just re-install the system through adb sideload as perhaps something corrupted (as once in a while, after many reboot a recovery mode like notice will pop up stating that the system might be corrupted and if you saw this message multiple times, you might need to try factory resetting). But now I sideload the newest pixel 3a official image (11.0.0 (RQ3A.210805.001.A1, Aug 2021)) I'm still stuck in the loop I described above, I still can't unlock my phone and my phone just keeps rebooting it. Previously (prior to sideloading) I remember recovery mode showing: > WARNING: Previous installation has failed. > Your device may fail to boot if you reboot or power now. (Though it may be result of me for doing other thing like testing apply update from SD card or letting adb to timeout as I forget to download the image first.) But it seems that after sideloading the warning doesn't show up, so perhaps I did sideload it correctly? (So as getting a 0-return value) But still the issue persists. But since I've gone to the newest version of the image, it seems that I couldn't downgrade it anyway. So is there any other way to solve my problem (besides factory resetting it as I kinda want to maintain the data within it, and I still couldn't access my data through USB currently). I don't think I've enabled USB debugging prior this event, so unless enabling it is possible to achieve without needing to enter the system (like settings), otherwise it makes no help. I thought sideloading official image meant the system will be re-install completely such that any corrupted file would be fixed. Is it the case? And since there seems to be no cache in Pixel 3a, does it means something ***other*** than system might have corrupted? And if so is there still hope to recover it?
Andrew.Wolphoe (121 rep)
Aug 28, 2021, 03:16 PM • Last activity: Aug 28, 2021, 03:23 PM
2 votes
0 answers
1196 views
Which files do I need to flash with fastboot to get a stock device state?
I have downloaded the stock ROM for my Mediatek (MT6580) device. Extracting the files leads me to a couple of `*.img` files and SP Flash Tool. I am currently on a Linux distro and have `adb` and `fastboot` packages installed, and am not able to use the SP Flash Tool. I was wondering which files do I...
I have downloaded the stock ROM for my Mediatek (MT6580) device. Extracting the files leads me to a couple of *.img files and SP Flash Tool. I am currently on a Linux distro and have adb and fastboot packages installed, and am not able to use the SP Flash Tool. I was wondering which files do I need to flash to get a factory version of the phone. fastboot getvar all shows these outputs
(bootloader) 	max-download-size: 0x8000000
(bootloader) 	partition-size:userdata: 32000000
(bootloader) 	partition-type:userdata: ext4
(bootloader) 	partition-size:cache: 10000000
(bootloader) 	partition-type:cache: ext4
(bootloader) 	partition-size:system: 5d000000
(bootloader) 	partition-type:system: ext4
(bootloader) 	partition-size:metadata: 2560000
(bootloader) 	partition-type:metadata: raw data
(bootloader) 	partition-size:nvdata: 2000000
(bootloader) 	partition-type:nvdata: ext4
(bootloader) 	partition-size:tee2: 500000
(bootloader) 	partition-type:tee2: raw data
(bootloader) 	partition-size:tee1: 500000
(bootloader) 	partition-type:tee1: raw data
(bootloader) 	partition-size:frp: 100000
(bootloader) 	partition-type:frp: raw data
(bootloader) 	partition-size:expdb: a00000
(bootloader) 	partition-type:expdb: raw data
(bootloader) 	partition-size:logo: 800000
(bootloader) 	partition-type:logo: raw data
(bootloader) 	partition-size:para: 80000
(bootloader) 	partition-type:para: raw data
(bootloader) 	partition-size:keystore: 800000
(bootloader) 	partition-type:keystore: raw data
(bootloader) 	partition-size:secro: 600000
(bootloader) 	partition-type:secro: raw data
(bootloader) 	partition-size:oemkeystore: 200000
(bootloader) 	partition-type:oemkeystore: raw data
(bootloader) 	partition-size:recovery: 1000000
(bootloader) 	partition-type:recovery: raw data
(bootloader) 	partition-size:boot: 1000000
(bootloader) 	partition-type:boot: raw data
(bootloader) 	partition-size:lk: 60000
(bootloader) 	partition-type:lk: raw data
(bootloader) 	partition-size:seccfg: 40000
(bootloader) 	partition-type:seccfg: raw data
(bootloader) 	partition-size:protect2: a00000
(bootloader) 	partition-type:protect2: ext4
(bootloader) 	partition-size:protect1: a00000
(bootloader) 	partition-type:protect1: ext4
(bootloader) 	partition-size:nvram: 500000
(bootloader) 	partition-type:nvram: raw data
(bootloader) 	partition-size:proinfo: 300000
(bootloader) 	partition-type:proinfo: raw data
(bootloader) 	partition-size:preloader: 40000
(bootloader) 	partition-type:preloader: raw data
(bootloader) 	off-mode-charge: 1
(bootloader) 	warranty: no
(bootloader) 	unlocked: yes
(bootloader) 	secure: no
(bootloader) 	kernel: lk
(bootloader) 	product: RS615
(bootloader) 	version: 0.5
all: Done!!
finished. total time: 0.012s
atheros (393 rep)
Sep 11, 2020, 05:03 AM • Last activity: Jul 31, 2021, 11:25 AM
1 votes
0 answers
70 views
How factory reset process looks in details?
So I tried to find answer for this question, but it is very hard to find something other than simple instruction of doing factory reset and backuping data. I'm interested of detailed process of the factory reset. When I force system to do this, what is going under the shell. It is some image on hidd...
So I tried to find answer for this question, but it is very hard to find something other than simple instruction of doing factory reset and backuping data. I'm interested of detailed process of the factory reset. When I force system to do this, what is going under the shell. It is some image on hidden partition from bootloader boots "clear" system? Or maybe it's just deleting user configuration files, and every corrupted system file states same as before reset. Or maybe there is the way of checking hash of critical files and repair them from some kind of recovery image?
rozumir (111 rep)
Jul 22, 2021, 01:35 PM
1 votes
0 answers
684 views
How to mount image file without root?
In rooted android phone, ext4 image file is mounted using these commands in android terminal : # mknod /dev/block/loop52 b 7 0 # losetup /dev/block/loop52 /sdcard/ext1.img # mkdir /mnt/ext # mount -t ext4 -o rw,noatime /dev/block/loop52 /mnt/ext I have an ext4 image file stored in sdcard. How can I...
In rooted android phone, ext4 image file is mounted using these commands in android terminal : # mknod /dev/block/loop52 b 7 0 # losetup /dev/block/loop52 /sdcard/ext1.img # mkdir /mnt/ext # mount -t ext4 -o rw,noatime /dev/block/loop52 /mnt/ext I have an ext4 image file stored in sdcard. How can I mount the ext4 image file in my non rooted android phone or Is there any other way to access it ?
jonny789 (385 rep)
Jul 21, 2021, 06:00 AM
1 votes
1 answers
6286 views
What does the ROM files (FACTORYFS, HIDDEN, CACHE, PARAM, etc.) mean?
Flashing my Galaxy S 2 `i9100` (after breaking with CyanogenMod update `CM-13.x`) I used the following command: sudo heimdall flash \ --FACTORYFS factoryfs.img \ --CACHE cache.img \ --HIDDEN hidden.img \ --MODEM modem.bin \ --PARAM param.lfs \ --BOOT boot.bin \ --SBL1 Sbl.bin \ --no-reboot \ --KERNE...
Flashing my Galaxy S 2 i9100 (after breaking with CyanogenMod update CM-13.x) I used the following command: sudo heimdall flash \ --FACTORYFS factoryfs.img \ --CACHE cache.img \ --HIDDEN hidden.img \ --MODEM modem.bin \ --PARAM param.lfs \ --BOOT boot.bin \ --SBL1 Sbl.bin \ --no-reboot \ --KERNEL zImage ### Question I'm wondering what's the role of the different files? **update**: I encourage you to use CM-12.1 instead of CM-13 for your i9100 as the later is not officially supported.
Édouard Lopez (200 rep)
Apr 15, 2016, 08:16 AM • Last activity: Jul 17, 2021, 06:52 PM
2 votes
1 answers
3902 views
How can I find the exact factory image version that my Pixel is using?
I have a Pixel 3XL on android 10 and a Pixel 3a on android 11. I had previously [installed magisk on the Pixel 3a][1] when android 11 was in beta. Recently I found that it had lost root, presumably because android 11 is out of beta and the phone had upgraded to the latest android 11 and was not usin...
I have a Pixel 3XL on android 10 and a Pixel 3a on android 11. I had previously installed magisk on the Pixel 3a when android 11 was in beta. Recently I found that it had lost root, presumably because android 11 is out of beta and the phone had upgraded to the latest android 11 and was not using the magisk-patched boot image anymore. So, I patched the corresponding boot image for the latest android 11 factory image for pixel 3a, and fastboot flashed it, and it worked. Unfortunately, I had mixed up my two phones in the fastboot flash step at first, and so then I ended up with the Pixel 3a with android 11 rooted again, but also with the Pixel 3XL stuck on boot, I guess because it had a wrong boot image (for pixel 3a actually) flashed into it. I tried to fix the Pixel 3XL by getting the latest android 10 factory image for it and patching the boot image with magisk. However, after fastboot flash of that patched boot image, it only worked partially. Namely, it could boot, adb shell works, etc., *but* it no longer responds to touch, so can't be used except for adb shell. I'm guessing the problem is that I didn't know what was the factory image actually installed on my Pixel 3L, so I just guessed it was the latest, but the boot image from the latest might have some incompatibility with the actual factory image in the phone. I would like to find out what is the actual factory image installed on the Pixel 3L, so I can try to patch the matching boot image. Hence, my question, how can I know what is the exact version of the android 10 factory image installed on my Pixel 3L? Googling doesn't seem to help, as most pages talk about how to install factory images, not how to find out what is the version installed. In answering my question, please note that I can't interact with the phone now through touch, so cannot check anything under "Settings" with the touch GUI, but can only see the fastboot info (see screenshot below) as well as anything I can access with adb shell (for example, any file in the phone I can check to find out the factory image version installed on the phone?) fastboot mode screen
auspicious99 (523 rep)
Dec 21, 2020, 02:09 PM • Last activity: Dec 27, 2020, 07:28 AM
1 votes
0 answers
70 views
What are the chances of a malware being persistent if I dd to write system.img and userdata.img from twrp
If I had a malware on my phone, say malware like xhelper, or strandhogg or something even critical than that, what are the chances of it being persistent even after using `dd` to write the **system.img** and **userdata.img** to the phone for eg `dd if=system.img of=/dev/block/platform/mtk-msdc.0/by-...
If I had a malware on my phone, say malware like xhelper, or strandhogg or something even critical than that, what are the chances of it being persistent even after using dd to write the **system.img** and **userdata.img** to the phone for eg dd if=system.img of=/dev/block/platform/mtk-msdc.0/by-name/system to write system as brand new. Is it possible that the malware could snoop into /cache or /nvdata to attain persistence. Is it feasible to use dd to flash those partitions as well? Which places would a malware use to hide itself to maintain persistence even after stock image flashing?
silly goose (31 rep)
Sep 21, 2020, 08:18 PM
1 votes
1 answers
132 views
Do "unlocked" phones come pre-unlocked or just the ability to be unlocked?
When you buy an unlocked (carrier-free) device, do the phones usually come unlocked already, or just with the ability to be unlocked easily? e.g. would the fastboot unlocked status be locked when it arrived? I believe this is referring to the bootloader lock and not the sim/carrier lock if those are...
When you buy an unlocked (carrier-free) device, do the phones usually come unlocked already, or just with the ability to be unlocked easily? e.g. would the fastboot unlocked status be locked when it arrived? I believe this is referring to the bootloader lock and not the sim/carrier lock if those are different.
user58446 (163 rep)
Aug 18, 2020, 12:07 AM • Last activity: Aug 18, 2020, 01:59 PM
0 votes
0 answers
51 views
How to get checksum for the running firmware?
I have seen other questions and answers that say given a new phone shipped from a retailer, it is only possible to verify the integrity of the firmware by comparing checksums. However, I'm not sure how to get the checksum of the currently running firmware on my device. Is this even possible? I may h...
I have seen other questions and answers that say given a new phone shipped from a retailer, it is only possible to verify the integrity of the firmware by comparing checksums. However, I'm not sure how to get the checksum of the currently running firmware on my device. Is this even possible? I may have misinterpreted the other advice as comparing checksums for downloaded images, but I am specifically looking to check the firmware that came loaded on the phone against a valid source before re-imaging it if that's what I decide to do. Hoping for generic advice, but manufacturer is LG if it matters. Please suggest tools and process. Final note: The phone has been used since it was received, so if there is a way to capture the pre-loaded firmware, I want to make sure it is not affected by any software/user option changes that would be made after the device setup was complete. I'm guessing I want to get a checksum of the current software version, so not sure if I have to make an image first and if that firmware image that is created would be static.
user58446 (163 rep)
Aug 18, 2020, 12:03 AM
0 votes
0 answers
1136 views
How can I install a supersu root zip on a system.img to create a pre-rooted system?
I'm looking to create a pre-rooted system.img for a specific device. running Marshmellow (6.0) on ARM. I have a SuperSU zip for marshmellow and the compiled system.img for my device. OK. I know you cant flash a zip to a .img - but, can i decompile the img, add the resources, and recompile? I specifi...
I'm looking to create a pre-rooted system.img for a specific device. running Marshmellow (6.0) on ARM. I have a SuperSU zip for marshmellow and the compiled system.img for my device. OK. I know you cant flash a zip to a .img - but, can i decompile the img, add the resources, and recompile? I specifically want to know - 1. Most importantly, is this possible...? 2. If yes, What files do I need from the zip? 3. How do I decompile the .img while not losing any important data? 4. Where in the decompiled .img do I put the files from the zip? 6. How do I create symlinks and set the permissions for the new files? 5. How do I recompile the .img maintaining all linux permissions etc.? Note, working environment is preferably windows. (although if I can get detailed instructions for Ubuntu, that'd be great too.) This question begs quite a detailed answer, and I'll be most grateful for any assistance on the subject, even incomplete. The device in question happens to be a VN220LTE, but I assume that the approach would be generic.
sh7411usa (153 rep)
May 10, 2020, 05:01 AM
0 votes
1 answers
4154 views
Can't Flash Google Factory Image - No Boot Partition
I seem to have bricked my phone but thankfully the bootloader is unlocked so I'm sure there is a way to fix it. I am having a hell of a time though, I think I need to re-create the boot partition manually. Here is what I get when I try `flash-all.bat` I can't find instructions how to re-create parti...
I seem to have bricked my phone but thankfully the bootloader is unlocked so I'm sure there is a way to fix it. I am having a hell of a time though, I think I need to re-create the boot partition manually. Here is what I get when I try flash-all.bat I can't find instructions how to re-create partitions, but I noticed this in fastboot --help, does anybody have experience creating partitons with fastboot? And/Or can somebody get the partition map from their device and/or share/extrapolate the commands needed. erase Erase a flash partition. format[:[][:[]] Format a flash partition. Can override the fs type and/or size the bootloader reports. I get the same in both slot_a and slot_b and I have manually flashed bootloader.img & boot.img C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all.bat target reported max download size of 536870912 bytes sending 'bootloaderb' (36336 KB)... OKAY [ 0.156s] writing 'bootloaderb'... OKAY [ 0.516s] finished. total time: 0.672s rebooting into bootloader... OKAY [ 0.016s] finished. total time: 0.016s target reported max download size of 536870912 bytes sending 'radiob' (60388 KB)... OKAY [ 0.261s] writing 'radiob'... OKAY [ 0.837s] finished. total time: 1.101s rebooting into bootloader... OKAY [ 0.002s] finished. total time: 0.003s target reported max download size of 536870912 bytes archive does not contain 'boot.sig' archive does not contain 'recovery.img' archive does not contain 'system.sig' archive does not contain 'vendor.sig' wiping userdata... Creating filesystem with parameters: Size: 120909180928 Block size: 4096 Blocks per group: 32768 Inodes per group: 8192 Inode size: 256 Journal blocks: 32768 Label: Blocks: 29518843 Block groups: 901 Reserved block group size: 1024 Created filesystem with 11/7380992 inodes and 511380/29518843 blocks -------------------------------------------- Bootloader Version...: TMZ20k Baseband Version.....: g8998-00253-1809191716 Serial Number........: 710KPMZ0311515 -------------------------------------------- checking product... OKAY [ 0.000s] checking version-bootloader... OKAY [ 0.000s] checking version-baseband... OKAY [ 0.000s] sending 'bootb' (40960 KB)... OKAY [ 0.188s] writing 'bootb'... FAILED (remote: No such partition.) finished. total time: 0.219s Press any key to exit...
FreeSoftwareServers (232 rep)
Mar 18, 2019, 12:18 AM • Last activity: Apr 8, 2020, 07:01 AM
Showing page 1 of 20 total questions