hi, all!
Modify /init.rc configure file is my plan, in android(linux) box, /(rootfs) locate RAM.
So, modify ramdisk.img(initrd.img) is aim, However, I find any image file except recovery backup image:
[email protected]:/ # /system/xbin/busybox find / -name '*.img'
/mnt/sdcard2/clockworkmod/backup/2012-01-01.00.03.03/boot.img
/mnt/sdcard2/clockworkmod/backup/2012-01-01.00.03.03/recovery.img
/system/etc/firmware/modem.img
Did the partition that ramdisk.img save in not mount by kernel ?
My phone information:
all partition:
[email protected]:/ # ll /dev/block/
brw------- root root 254, 0 2012-11-30 22:08 dm-0
brw------- root root 7, 0 2012-11-30 22:07 loop0
brw------- root root 7, 1 2012-11-30 22:07 loop1
brw------- root root 7, 2 2012-11-30 22:07 loop2
brw------- root root 7, 3 2012-11-30 22:07 loop3
brw------- root root 7, 4 2012-11-30 22:07 loop4
brw------- root root 7, 5 2012-11-30 22:07 loop5
brw------- root root 7, 6 2012-11-30 22:07 loop6
brw------- root root 7, 7 2012-11-30 22:07 loop7
brw-rw---- root system 179, 0 2012-11-30 22:07 mmcblk0
brw------- root root 179, 32 2012-11-30 22:07 mmcblk0boot0
brw------- root root 179, 64 2012-11-30 22:07 mmcblk0boot1
brw------- root root 179, 1 2012-11-30 22:07 mmcblk0p1
brw------- root root 179, 2 2012-11-30 22:07 mmcblk0p2
brw------- root root 179, 3 2012-11-30 22:07 mmcblk0p3
brw------- root root 179, 4 2012-11-30 22:07 mmcblk0p4
brw------- root root 179, 5 2012-11-30 22:07 mmcblk0p5
brw------- root root 179, 6 2012-11-30 22:07 mmcblk0p6
brw------- root root 179, 96 2012-11-30 22:07 mmcblk1
brw------- root root 179, 97 2012-11-30 22:07 mmcblk1p1
drwxr-xr-x root root 2012-11-30 22:07 platform
drwxr-xr-x root root 2012-11-30 22:07 vold
mounted partition:
[email protected]:/ # mount|/system/xbin/busybox grep mmc
/[email protected] /system ext4 ro,noatime,user_xattr,commit=1,barrier=1,data=ordered,noauto_da_alloc 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/[email protected] /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
had be linked partition:
[email protected]:/ # ll / |/system/xbin/busybox mmc
lrwxrwxrwx root root 1970-01-01 08:00 [email protected] -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 08:00 [email protected] -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 08:00 [email protected] -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 08:00 [email protected] -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 08:00 [email protected]_ro -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 08:00 [email protected] -> /dev/block/mmcblk0p5
[email protected]:/ # cat /proc/mtd
dev: size erasesize name
[email protected]:/ #
My phone do not use mtd ?
what other technology my phone used? and, what can I locate recovery and boot partition ?
Ramdisk is inside boot.img, you must use dsixda's kitchen to decompile it.
Sent from my PC36100 using xda app-developers app
Yes, the ramdisk is inside the boot.img. The recovery.img contains its own ramdisk. The partition is a basic format created just for android. The first 0x30ish bytes contain offsets and sizes for the kernel image, ramdisk, kernel command line, and stuff like that. And no, the ramdisk is not compiled; you do no decompile it. It is compressed. You can pull the ramdisk out of the partition and decompress it using standard commandline tools.
Hi guys, I hope one guru here can help me to unbrick my TF300T.
Yesterday I unlock the tablet with the ASUS utility and flashed lastest TWRP. After that the tablet always boot into TWRP but it can't mount any partition. I was able to go to fastboot with adb reboot-bootloader and boot Android from the Android icon. Then I tried to flash ASUS stock image to system (fastboot -i 0x0b05 flash system blob) and now I can't get it to boot.
fastboot send the image but doesn't write it, I get no error, but the process is to fast and the tablet freeze after it:
Code:
./fastboot devices
015d262e0b20101a fastboot
sudo ./fastboot -i 0x0B05 flash recovery recovery.img
sending 'recovery' (5644 KB)...
OKAY [ 2.471s]
writing 'recovery'...
OKAY [ 3.162s]
finished. total time: 5.633s
./fastboot devices
???????????? fastboot
./fastboot reboot
rebooting... <------ freeze!
I'm able to go to adb shell, then I push the recovery image and tried to flash it with but with no luck:
Code:
./adb devices
List of devices attached
0123456789ABCDEF recovery
./adb push recovery.img /root
1327 KB/s (5779560 bytes in 4.250s)
./adb shell
~ # cd root
/root # ls -alh
drwx------ 2 root root 0 Apr 16 07:21 .
drwxr-xr-x 19 root root 0 Apr 16 07:21 ..
-rw-rw-rw- 1 root root 5.5M Apr 15 20:25 recovery.img
/root # flash_image recovery recovery.img
failed with error: -1
/root #
Please tell me that I doesn't send 420€ to trash...
PS: I used Ubuntu for all this stuff.
I have read some threads with similar problems and tried some of the solutions with no luck:
http://forum.xda-developers.com/showthread.php?p=32792384
http://forum.xda-developers.com/showthread.php?t=1916952
http://forum.xda-developers.com/showthread.php?t=2228447
jmsosso said:
I have read some threads with similar problems and tried some of the solutions with no luck:
http://forum.xda-developers.com/showthread.php?p=32792384
http://forum.xda-developers.com/showthread.php?t=1916952
http://forum.xda-developers.com/showthread.php?t=2228447
Click to expand...
Click to collapse
I think, we must spam mail asus to release new nvflash
jmsosso said:
Hi guys, I hope one guru here can help me to unbrick my TF300T.
Yesterday I unlock the tablet with the ASUS utility and flashed lastest TWRP. After that the tablet always boot into TWRP but it can't mount any partition. I was able to go to fastboot with adb reboot-bootloader and boot Android from the Android icon. Then I tried to flash ASUS stock image to system (fastboot -i 0x0b05 flash system blob) and now I can't get it to boot.
fastboot send the image but doesn't write it, I get no error, but the process is to fast and the tablet freeze after it:
Code:
./fastboot devices
015d262e0b20101afastboot
sudo ./fastboot -i 0x0B05 flash recovery recovery.img
sending 'recovery' (5644 KB)...
OKAY [ 2.471s]
writing 'recovery'...
OKAY [ 3.162s]
finished. total time: 5.633s
./fastboot devices
????????????fastboot
./fastboot reboot
rebooting... <------ freeze!
I'm able to go to adb shell, then I push the recovery image and tried to flash it with but with no luck:
Code:
./adb devices
List of devices attached
0123456789ABCDEFrecovery
./adb push recovery.img /root
1327 KB/s (5779560 bytes in 4.250s)
./adb shell
~ # cd root
/root # ls -alh
drwx------ 2 root root 0 Apr 16 07:21 .
drwxr-xr-x 19 root root 0 Apr 16 07:21 ..
-rw-rw-rw- 1 root root 5.5M Apr 15 20:25 recovery.img
/root # flash_image recovery recovery.img
failed with error: -1
/root #
Please tell me that I doesn't send 420€ to trash...
PS: I used Ubuntu for all this stuff.
Click to expand...
Click to collapse
OK, first of all, it sounds like you've updated to the 4.2.1 firmware and flashed a recovery for the 4.1.1 firmware. So, make sure that the new recovery you're flashing is the patched TWRP with -42 at the end of the name. It's not the newest TWRP. If you're trying to flash the same version of TWRP as before, you won't fix anything, if you can even get it to flash.
Second, when you're in ADB shell, what happens when, instead of using flash_image, you use
Code:
su
dd if=/root/recovery.img of=/dev/block/mmcblk0p4
?
The worst that can happen is that you get the same error. That's if flash_image uses dd to flash the recovery. Otherwise, there's a chance it could work. I say it's worth a try.
Putting the ILLA in KILLA since 1985
---------- Post added at 04:18 AM ---------- Previous post was at 04:14 AM ----------
If that doesn't work, try this guide: http://forum.xda-developers.com/showthread.php?p=40343188
Putting the ILLA in KILLA since 1985
EndlessDissent said:
OK, first of all, it sounds like you've updated to the 4.2.1 firmware and flashed a recovery for the 4.1.1 firmware. So, make sure that the new recovery you're flashing is the patched TWRP with -42 at the end of the name. It's not the newest TWRP. If you're trying to flash the same version of TWRP as before, you won't fix anything, if you can even get it to flash.
Second, when you're in ADB shell, what happens when, instead of using flash_image, you use
Code:
su
dd if=/root/recovery.img of=/dev/block/mmcblk0p4
?
The worst that can happen is that you get the same error. That's if flash_image uses dd to flash the recovery. Otherwise, there's a chance it could work. I say it's worth a try.
Click to expand...
Click to collapse
I downloaded openrecovery-twrp-2.4.4.0-tf300t-4.2.blob and renamed it to twrp.blob then:
Code:
./adb push twrp.blob /root
1328 KB/s (7680104 bytes in 5.644s)
./adb shell
~ # cd root
/root # ls
twrp.blob
/root # su
/sbin/sh: su: not found
/root # dd if=twrp.blob of=/dev/block/mmcblk0p4
15000+1 records in
15000+1 records out
7680104 bytes (7.3MB) copied, 0.091978 seconds, 79.6MB/s
/root # exit
./adb reboot
Then the tablet boot directly into TWRP 2.5.0.0, the version that I installed at the beginning
Latter I'll try the other suggestion. Thanks a lot!
There aren't any partition mounted at boot and I can't mount any manually. I think the problem is in /dev/block:
Code:
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 486.8M 48.0K 486.8M 0% /dev
~ # cat /etc/fstab
/system ext4 rw
/cache ext4 rw
/external_sdcard vfat rw
/sd-ext ext4 rw
~ # mount -a
mount: mounting /system on ext4 failed: No such file or directory
mount: mounting /cache on ext4 failed: No such file or directory
mount: mounting /external_sdcard on vfat failed: No such file or directory
mount: mounting /sd-ext on ext4 failed: No such file or directory
~ # cd root
/root # mkdir test
/root # mount /dev/block/mmcblk0p4 test
mount: mounting /dev/block/mmcblk0p4 on test failed: No such file or directory
~ # ls -alh /dev/block/
drwxr-xr-x 2 root root 200 Apr 16 13:52 .
drwxr-xr-x 10 root root 2.1K Apr 16 13:53 ..
brw------- 1 root root 7, 0 Apr 16 13:52 loop0
brw------- 1 root root 7, 1 Apr 16 13:52 loop1
brw------- 1 root root 7, 2 Apr 16 13:52 loop2
brw------- 1 root root 7, 3 Apr 16 13:52 loop3
brw------- 1 root root 7, 4 Apr 16 13:52 loop4
brw------- 1 root root 7, 5 Apr 16 13:52 loop5
brw------- 1 root root 7, 6 Apr 16 13:52 loop6
brw------- 1 root root 7, 7 Apr 16 13:52 loop7
i just noticed of /proc/partitions is empty. Can anybody publish here a valid one? I don't know if just editing the file with the right values will solve my situation.
jmsosso said:
There aren't any partition mounted at boot and I can't mount any manually. I think the problem is in /dev/block:
Code:
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 486.8M 48.0K 486.8M 0% /dev
~ # cat /etc/fstab
/system ext4 rw
/cache ext4 rw
/external_sdcard vfat rw
/sd-ext ext4 rw
~ # mount -a
mount: mounting /system on ext4 failed: No such file or directory
mount: mounting /cache on ext4 failed: No such file or directory
mount: mounting /external_sdcard on vfat failed: No such file or directory
mount: mounting /sd-ext on ext4 failed: No such file or directory
~ # cd root
/root # mkdir test
/root # mount /dev/block/mmcblk0p4 test
mount: mounting /dev/block/mmcblk0p4 on test failed: No such file or directory
~ # ls -alh /dev/block/
drwxr-xr-x 2 root root 200 Apr 16 13:52 .
drwxr-xr-x 10 root root 2.1K Apr 16 13:53 ..
brw------- 1 root root 7, 0 Apr 16 13:52 loop0
brw------- 1 root root 7, 1 Apr 16 13:52 loop1
brw------- 1 root root 7, 2 Apr 16 13:52 loop2
brw------- 1 root root 7, 3 Apr 16 13:52 loop3
brw------- 1 root root 7, 4 Apr 16 13:52 loop4
brw------- 1 root root 7, 5 Apr 16 13:52 loop5
brw------- 1 root root 7, 6 Apr 16 13:52 loop6
brw------- 1 root root 7, 7 Apr 16 13:52 loop7
i just noticed of /proc/partitions is empty. Can anybody publish here a valid one? I don't know if just editing the file with the right values will solve my situation.
Click to expand...
Click to collapse
Hmmm... I think it's interesting that dd seemed to successfully write the recovery and exited with no errors, but didn't actually write anything. Not sure what that means or how it could help, but that wasn't at all what I expected. I thought it would either error out or successfully flash your recovery. It obviously did neither.
As for your request, I hope this helps, though I'm not sure if editing the file will help much. I guess it's better than nothing.
Code:
[email protected]:/ $ cat /proc/partitions
major minor #blocks name
7 0 6269 loop0
7 1 5229 loop1
7 2 41612 loop2
7 3 22901 loop3
7 4 9387 loop4
179 0 31039488 mmcblk0
179 1 786432 mmcblk0p1
179 2 438272 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 835584 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 28924416 mmcblk0p8
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
254 0 6268 dm-0
254 1 5229 dm-1
254 2 41611 dm-2
254 3 22900 dm-3
254 4 9387 dm-4
[email protected]:/ $ ls -al /dev/block/
brw------- root root 254, 0 2013-04-14 03:40 dm-0
brw------- root root 254, 1 2013-04-14 03:40 dm-1
brw------- root root 254, 2 2013-04-14 03:40 dm-2
brw------- root root 254, 3 2013-04-14 03:40 dm-3
brw------- root root 254, 4 2013-04-14 03:40 dm-4
brw------- root root 7, 0 2013-04-14 03:36 loop0
brw------- root root 7, 1 2013-04-14 03:36 loop1
brw------- root root 7, 2 2013-04-14 03:36 loop2
brw------- root root 7, 3 2013-04-14 03:36 loop3
brw------- root root 7, 4 2013-04-14 03:36 loop4
brw------- root root 7, 5 2013-04-14 03:36 loop5
brw------- root root 7, 6 2013-04-14 03:36 loop6
brw------- root root 7, 7 2013-04-14 03:36 loop7
brw------- root root 179, 0 2013-04-14 03:36 mmcblk0
brw------- root root 179, 16 2013-04-14 03:36 mmcblk0boot0
brw------- root root 179, 32 2013-04-14 03:36 mmcblk0boot1
brw------- root root 179, 1 2013-04-14 03:36 mmcblk0p1
brw------- root root 179, 2 2013-04-14 03:36 mmcblk0p2
brw-rw---- root system 179, 3 2013-04-14 03:36 mmcblk0p3
brw-rw---- root system 179, 4 2013-04-14 03:36 mmcblk0p4
brw------- root root 179, 5 2013-04-14 03:36 mmcblk0p5
brw------- drm drm 179, 6 2013-04-14 03:36 mmcblk0p6
brw------- root root 179, 7 2013-04-14 03:36 mmcblk0p7
brw------- root root 179, 8 2013-04-14 03:36 mmcblk0p8
drwxr-xr-x root root 2013-04-14 03:36 platform
drwx------ root root 2013-04-14 03:36 vold
Good luck.
Putting the ILLA in KILLA since 1985
Edit: I almost forgot to mention that the guide I posted earlier uses fastboot, but theoretically you can do it with dd in ADB shell like you tried with the recovery. You'll need to know which partition is the bootloader, though, and substitute that in place of mmcblk0p4 in the dd command.
I was unable to modify the partitions file. I think that the problem is related to the new 4.2 encrypted file system:
http://forum.xda-developers.com/showthread.php?t=2180376
It is, and you're done.
In TWRP, there are no mmcblk devices, and so nothing to mount or mount to. Nothing to 'dd' to either.
In RCK, fastboot will lock the tablet trying to flash anything.
Nvflash won't help because you needed to use it BEFORE it was bricked.
There are likely lots of newly bricked TF300T's because of this.
Folks will say it's because you didn't read, but the directions on the Teamwin website will still result in a brick if they are followed after taking the 4.2.1 OTA update. In my case, I bricked mine in between the time TWRP 2.4.4.0 came out (I used the -JB release), and the time 2.4.4.0-4.2 was released - following those directions exactly. I'd imagine there is even more of this happening now that 2.5.0.0 was released (without a 4.2 compatible version), no change in the instructions on their website, and even more folks that have taken the 4.2.1 OTA update.
splashg said:
It is, and you're done.
In TWRP, there are no mmcblk devices, and so nothing to mount or mount to. Nothing to 'dd' to either.
In RCK, fastboot will lock the tablet trying to flash anything.
Nvflash won't help because you needed to use it BEFORE it was bricked.
There are likely lots of newly bricked TF300T's because of this.
Folks will say it's because you didn't read, but the directions on the Teamwin website will still result in a brick if they are followed after taking the 4.2.1 OTA update. In my case, I bricked mine in between the time TWRP 2.4.4.0 came out (I used the -JB release), and the time 2.4.4.0-4.2 was released - following those directions exactly. I'd imagine there is even more of this happening now that 2.5.0.0 was released (without a 4.2 compatible version), no change in the instructions on their website, and even more folks that have taken the 4.2.1 OTA update.
Click to expand...
Click to collapse
Oh my god! the worst of my nightmares :crying:
My error was, when reading a guide to flash TWRP, to go to the official website and download the latest -jb release and not to use the recommended one. As you said they must include some type of message at the download page.
After that, I was able to boot Android using ADB reboot, but then, trying to go back I flashed the official ASUS system partition. The result was that the command erased the working partition but doesn't flash nothing.
Now I think my better choice is to wait some time. If nobody found a solution then buy a motherboard at eBay and try to replace it.
Thanks for your support folks!
Best regards.
+1 for Asus
Wow, Asus fixed my tablet under warranty without any cost
I received it yesterday after it traveled from Spain (were I live) to Czech Republic and back in 14 days.
When I called to Asus I tell the guy at the phone that I brick the tabled trying to root. He told me that if the tablet was rooted and my answer was not. And he told me then that it's under warranty. :good:
So guys with the same problem, and with the tablet under warranty, try with Asus!
Best regards.
Hi,
i have problem to reflash the lates ROM for P3100.
first i install the lates rom with success, after few days i have error "Can't load native library. CPU arch invalid for this build" then my tab restart. i tried to re flash thr ROM and its success but still same problem then i flash other version ROM its success but when its booting still on the same ROM. i also try to flash stock rom using odin, its success but same problem, booting and still using SlimROM. i have no idea with this problem please help
ROM SlimKAT
Recovery : TWRP
[email protected]:/ $ ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name/
ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name/
lrwxrwxrwx root root 2014-05-16 23:08 CACHE -> /dev/block/mmcbl
k0p7
lrwxrwxrwx root root 2014-05-16 23:08 DATAFS -> /dev/block/mmcb
lk0p10
lrwxrwxrwx root root 2014-05-16 23:08 EFS -> /dev/block/mmcblk0
p1
lrwxrwxrwx root root 2014-05-16 23:08 FACTORYFS -> /dev/block/m
mcblk0p9
lrwxrwxrwx root root 2014-05-16 23:08 HIDDEN -> /dev/block/mmcb
lk0p11
lrwxrwxrwx root root 2014-05-16 23:08 KERNEL -> /dev/block/mmcb
lk0p5
lrwxrwxrwx root root 2014-05-16 23:08 MODEM -> /dev/block/mmcbl
k0p8
lrwxrwxrwx root root 2014-05-16 23:08 PARAM -> /dev/block/mmcbl
k0p4
lrwxrwxrwx root root 2014-05-16 23:08 RECOVERY -> /dev/block/mm
cblk0p6
lrwxrwxrwx root root 2014-05-16 23:08 SBL1 -> /dev/block/mmcblk
0p2
lrwxrwxrwx root root 2014-05-16 23:08 SBL2 -> /dev/block/mmcblk
0p3
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 20480 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 716800 mmcblk0p7
259 0 20480 mmcblk0p8
259 1 1433600 mmcblk0p9
259 2 12640239 mmcblk0p10
259 3 524288 mmcblk0p11
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
179 24 15724544 mmcblk1
179 25 15723520 mmcblk1p1
any idea ? seems every i install apk its success but after restart the phone the program gone, same with when i uninstall apk, when reboot the phone the program still there. whatever im done all coming back
attach recovery log
anyone?
First of all if there is any way for those like me with less than perfect eyesight and experienced with the structure of these most complicated I've seen to date, I would like to respectively ask that the captchas be reduced in difficulty.
My issue is that I seem to have hit an impasse in that I can't post a question here to a How-to guide published for non-experts unless I am an expert, qualified by posting 10 helpful comments in an area I am just beginning to learn. If I think back to other operating systems I have learned over the years other than Linux, there were sometime years that passed before I felt qualified to help someone with understanding the OS.
So I am in a catch 22.
All I want to do is make a backup with a possibility of restore of my full OS on a Blu Studio 5.5s that I have factory reset for just that purpose, to have a customized OS that I could restore. It would also be nice to be able to learn how to someone share this image online, assuming that others can use it where none are available otherwise, but that is my second objective and not the first.
Now understanding my first objective is just a backup and restore capability and also understanding that the two bootloader recovery packagers out now don't (yet?) support my phone, I at last found this article and was excited that it would accomplish what I needed. I went through the hoops of days of research, getting hardcodes out of Windows device manger, altering Google driver INF files with dummied up hardware codes with a new device, overriding windows and getting the drivers installed and to work, installing the 64 bit version of SDK, and careful with the 32bit Java, relocating, renaming the SDK, modified the PATH to find my variables, installing Cgwin64, researching and comparing old package to new info and testing it all to see that it worked.
So in short, I am stuck in the middle of this how-to guide with my phone stripped to the bone for a backup but I can't ask a question here until after I have learned the answer to the question I am asking.
THE QUESTION:
reference: http://forum.xda-developers.com/showthread.php?t=1818321
My phone directory structure is not documented online and does not match the examples in the backup guide, plus it appears I may also have some permission restrictions? How do I continue? Thanks
My results thus far:
===================NOTE: PHONE IS BLU STUDIO 5.5S================
[email protected] /blustudio
$ nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0.raw
0 B 0:00:00 [ 0 B/s] [<=>
===================
[email protected] ~
$ adb forward tcp:5555 tcp:5555
[email protected] ~
$ adb shell
[email protected]:/ $ su
su
1|[email protected]:/ $ /system/xbin/busybox nc -l -p 5555 -e /system/xbin/busybox dd if =/dev/block/mmcblk0
555 -e /system/xbin/busybox dd if=/dev/block/mmcblk0 <
dd: can't open '/dev/block/mmcblk0': Permission denied
1|[email protected]:/ $ ls -lR /dev/block
============================
ls -lR /dev/block
/dev/block:
brw------- root root 7, 0 2014-06-27 21:34 loop0
brw------- root root 7, 1 2014-06-27 21:34 loop1
brw------- root root 7, 2 2014-06-27 21:34 loop2
brw------- root root 7, 3 2014-06-27 21:34 loop3
brw------- root root 7, 4 2014-06-27 21:34 loop4
brw------- root root 7, 5 2014-06-27 21:34 loop5
brw------- root root 7, 6 2014-06-27 21:34 loop6
brw------- root root 7, 7 2014-06-27 21:34 loop7
brw-rw---- root system 179, 0 2014-06-27 21:34 mmcblk0
brw-rw---- root system 179, 32 2014-06-27 21:34 mmcblk0boot0
brw------- root root 179, 64 2014-06-27 21:34 mmcblk0boot1
brw------- root root 179, 1 2014-06-27 21:34 mmcblk0p1
brw------- root root 179, 2 2014-06-27 21:34 mmcblk0p2
brw------- root root 179, 3 2014-06-27 21:34 mmcblk0p3
brw------- root root 179, 4 2014-06-27 21:34 mmcblk0p4
brw------- root root 179, 5 2014-06-27 21:34 mmcblk0p5
brw------- root root 179, 6 2014-06-27 21:34 mmcblk0p6
brw------- root root 179, 7 2014-06-27 21:34 mmcblk0p7
drwxr-xr-x root root 2014-06-27 21:34 platform
drwxr-xr-x root root 2014-06-27 21:34 vold
brw------- root root 253, 0 2014-06-27 21:34 zram0
/dev/block/platform:
drwxr-xr-x root root 2014-06-27 21:34 mtk-msdc.0
/dev/block/platform/mtk-msdc.0:
drwxr-xr-x root root 2014-06-27 21:34 by-num
lrwxrwxrwx root root 2014-06-27 21:34 mmcblk0 -> /dev/block/mmc blk0
lrwxrwxrwx root root 2014-06-27 21:34 mmcblk0boot0 -> /dev/bloc k/mmcblk0boot0
lrwxrwxrwx root root 2014-06-27 21:34 mmcblk0boot1 -> /dev/bloc k/mmcblk0boot1
lrwxrwxrwx root root 2014-06-27 21:34 mmcblk0p1 -> /dev/block/m mcblk0p1
lrwxrwxrwx root root 2014-06-27 21:34 mmcblk0p2 -> /dev/block/m mcblk0p2
lrwxrwxrwx root root 2014-06-27 21:34 mmcblk0p3 -> /dev/block/m mcblk0p3
lrwxrwxrwx root root 2014-06-27 21:34 mmcblk0p4 -> /dev/block/m mcblk0p4
lrwxrwxrwx root root 2014-06-27 21:34 mmcblk0p5 -> /dev/block/m mcblk0p5
lrwxrwxrwx root root 2014-06-27 21:34 mmcblk0p6 -> /dev/block/m mcblk0p6
lrwxrwxrwx root root 2014-06-27 21:34 mmcblk0p7 -> /dev/block/m mcblk0p7
/dev/block/platform/mtk-msdc.0/by-num:
lrwxrwxrwx root root 2014-06-27 21:34 p1 -> /dev/block/mmcblk0p 1
lrwxrwxrwx root root 2014-06-27 21:34 p2 -> /dev/block/mmcblk0p 2
lrwxrwxrwx root root 2014-06-27 21:34 p3 -> /dev/block/mmcblk0p 3
lrwxrwxrwx root root 2014-06-27 21:34 p4 -> /dev/block/mmcblk0p 4
lrwxrwxrwx root root 2014-06-27 21:34 p5 -> /dev/block/mmcblk0p 5
lrwxrwxrwx root root 2014-06-27 21:34 p6 -> /dev/block/mmcblk0p 6
lrwxrwxrwx root root 2014-06-27 21:34 p7 -> /dev/block/mmcblk0p 7
/dev/block/vold:
brw-rw---- root root 179, 0 2014-06-27 21:34 179:0
brw-rw---- root root 179, 1 2014-06-27 21:34 179:1
brw-rw---- root root 179, 2 2014-06-27 21:34 179:2
brw-rw---- root root 179, 3 2014-06-27 21:34 179:3
brw-rw---- root root 179, 4 2014-06-27 21:34 179:4
brw-rw---- root root 179, 5 2014-06-27 21:34 179:5
brw-rw---- root root 179, 6 2014-06-27 21:34 179:6
brw-rw---- root root 179, 7 2014-06-27 21:34 179:7
[email protected]:/ $
Thanks in advance for any advise.
Hi,
This is my first project that I'm currently working on.
I recently bought a android dashcam which UI I would like to change based on my personal preferences. Unfortunately I'm struggling to setup an environment where I can test the changes I make before replacing the original UI on the device itself. I identified the SystemUI.apk to be the place where the manufacturer made customization. I will be using the SystemUI.apk built from AOSP and making my changes based on that. I had no luck trying to decompile the SystemUI.apk in a way that I could build it again.
I was thinking that I could use an android emulator to use the same ROM as the device itself. The manufacturer did not provide any support in providing stock firmware images in any way. So I used the following steps to 'export' the firmware.
1. Unlocking the bootloader using the Identifier Token so I can flash images using fastboot. TWRP was not an option here because I could not find any images for my device nor could I port an TWRP image myself.
2. Enable ADB debugging over usb
3. Enable ADB root privileges using the password: 2846 (if i remember correctly)
4. Use ADB remount and ADB root to gain privileges over the partitions
5. Gain information on partition data
6. Use ADB pull to export images based on partitions
After following the above steps the next thing was to import the images into an emulator. I used the following steps to do this:
1. Create a new device within Android Studio that has the same screen size and os.
2. Replace the system.img, ramdisk.img with the exported variants in ~/Android/Sdk/../arm64-v8a
3. Turn off EncryptUserData inside advancedFeatures.ini to prevent errors like partitions that are unable to encrypt
4. Use the command below to start the emulator
Code:
~/Android/Sdk/emulator/emulator -avd Junsun_A104_API_27 -verbose -show-kernel
5. After running the emulator I receive the error below and the screen of the emulator stays black.
Code:
Please append a correct "root=" boot option; here are the available partitions:
fe00 2867200 vda driver: virtio_blk
fe10 67584 vdb driver: virtio_blk
fe20 819200 vdc driver: virtio_blk
fe30 409600 vdd driver: virtio_blk
fe40 524288 vde driver: virtio_blk
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
My assumption is that the emulator does not contain the same partition model used on the device. I could try to export each partition but I wouldn't know how to let the emulator know how to use these partitions. I tried to export the kernel and import it inside the emulator without luck. I did not receive any errors that way.
So my main question is:
- Is there any way I can import the device's rom inside an android emulator
Spoiler: Emulator Config
AvdId=Junsun_A104_API_27
PlayStore.enabled=false
abi.type=arm64-v8a
avd.ini.displayname=Junsun A104 API 27
avd.ini.encoding=UTF-8
disk.dataPartition.size=800M
fastboot.chosenSnapshotFile=
fastboot.forceChosenSnapshotBoot=no
fastboot.forceColdBoot=no
fastboot.forceFastBoot=yes
hw.accelerometer=yes
hw.arc=false
hw.audioInput=yes
hw.battery=yes
hw.camera.back=virtualscene
hw.camera.front=emulated
hw.cpu.arch=arm64
hw.cpu.ncore=4
hw.dPad=no
hw.device.hash2=MD5:7834f5e80eb849ceb46ce01cd4c704f7
hw.device.manufacturer=User
hw.device.name=Junsun A104
hw.gps=yes
hw.gpu.enabled=no
hw.gpu.mode=off
hw.initialOrientation=landscape
hw.keyboard=yes
hw.lcd.density=120
hw.lcd.height=320
hw.lcd.width=1480
hw.mainKeys=no
hw.ramSize=2560
hw.sdCard=yes
hw.sensors.orientation=yes
hw.sensors.proximity=yes
hw.trackBall=no
image.sysdir.1=system-images/android-27/default/arm64-v8a/
runtime.network.latency=none
runtime.network.speed=full
sdcard.size=512M
showDeviceFrame=no
skin.dynamic=yes
skin.name=1480x320
skin.path=_no_skin
skin.path.backup=/home/dangelo/Android/Sdk/skins/tv_1080p
tag.display=Default Android System Image
tag.id=default
vm.heapSize=48
Spoiler: Partition data
$ cat /proc/partitions
major minor #blocks name
1 0 8192 ram0
1 1 8192 ram1
1 2 8192 ram2
1 3 8192 ram3
1 4 8192 ram4
1 5 8192 ram5
1 6 8192 ram6
1 7 8192 ram7
1 8 8192 ram8
1 9 8192 ram9
1 10 8192 ram10
1 11 8192 ram11
1 12 8192 ram12
1 13 8192 ram13
1 14 8192 ram14
1 15 8192 ram15
254 0 1572864 zram0
179 0 30670848 mmcblk0
179 1 5120 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 35840 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 6144 mmcblk0p5
179 6 6144 mmcblk0p6
179 7 1024 mmcblk0p7
259 0 1024 mmcblk0p8
259 1 1024 mmcblk0p9
259 2 1024 mmcblk0p10
259 3 4096 mmcblk0p11
259 4 1024 mmcblk0p12
259 5 1024 mmcblk0p13
259 6 1024 mmcblk0p14
259 7 1024 mmcblk0p15
259 8 1024 mmcblk0p16
259 9 1024 mmcblk0p17
259 10 1024 mmcblk0p18
259 11 1024 mmcblk0p19
259 12 10240 mmcblk0p20
259 13 2048 mmcblk0p21
259 14 25600 mmcblk0p22
259 15 1024 mmcblk0p23
259 16 10240 mmcblk0p24
259 17 20480 mmcblk0p25
259 18 1024 mmcblk0p26
259 19 35840 mmcblk0p27
259 20 2867200 mmcblk0p28
259 21 153600 mmcblk0p29
259 22 409600 mmcblk0p30
259 23 1024 mmcblk0p31
259 24 1024 mmcblk0p32
259 25 27059183 mmcblk0p33
179 24 4096 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
253 0 27059167 dm-0
output using the ls command with arguments that I forgot
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 boot -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 cache -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 fbootlogo -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 gpsbd -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 gpsgl -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_deltanv -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_fixnv1 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_fixnv2 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_gdsp -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_ldsp -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_modem -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_runtimenv1 -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_runtimenv2 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 logo -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 misc -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 miscdata -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 pm_sys -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 prodnv -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 recovery -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 sml -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 sml_bak -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 system -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 trustos -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 trustos_bak -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 uboot -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 uboot_bak -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 uboot_log -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 userdata -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 vbmeta -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 vbmeta_bak -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 vendor -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 wcnmodem -> /dev/block/mmcblk0p20
Spoiler: Device information
Device name: Junsun A104
Android: 8.1. Oreo API level 27
CPU:
64bit
ARM64-V8A
Spreadtrum SC9832e
Memory: 2GB
Kernel architecture: aarch64
Kernel version: 4.4.83-00001-g213b4e3
dangelob said:
Hi,
This is my first project that I'm currently working on.
I recently bought a android dashcam which UI I would like to change based on my personal preferences. Unfortunately I'm struggling to setup an environment where I can test the changes I make before replacing the original UI on the device itself. I identified the SystemUI.apk to be the place where the manufacturer made customization. I will be using the SystemUI.apk built from AOSP and making my changes based on that. I had no luck trying to decompile the SystemUI.apk in a way that I could build it again.
I was thinking that I could use an android emulator to use the same ROM as the device itself. The manufacturer did not provide any support in providing stock firmware images in any way. So I used the following steps to 'export' the firmware.
1. Unlocking the bootloader using the Identifier Token so I can flash images using fastboot. TWRP was not an option here because I could not find any images for my device nor could I port an TWRP image myself.
2. Enable ADB debugging over usb
3. Enable ADB root privileges using the password: 2846 (if i remember correctly)
4. Use ADB remount and ADB root to gain privileges over the partitions
5. Gain information on partition data
6. Use ADB pull to export images based on partitions
After following the above steps the next thing was to import the images into an emulator. I used the following steps to do this:
1. Create a new device within Android Studio that has the same screen size and os.
2. Replace the system.img, ramdisk.img with the exported variants in ~/Android/Sdk/../arm64-v8a
3. Turn off EncryptUserData inside advancedFeatures.ini to prevent errors like partitions that are unable to encrypt
4. Use the command below to start the emulator
Code:
~/Android/Sdk/emulator/emulator -avd Junsun_A104_API_27 -verbose -show-kernel
5. After running the emulator I receive the error below and the screen of the emulator stays black.
Code:
Please append a correct "root=" boot option; here are the available partitions:
fe00 2867200 vda driver: virtio_blk
fe10 67584 vdb driver: virtio_blk
fe20 819200 vdc driver: virtio_blk
fe30 409600 vdd driver: virtio_blk
fe40 524288 vde driver: virtio_blk
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
My assumption is that the emulator does not contain the same partition model used on the device. I could try to export each partition but I wouldn't know how to let the emulator know how to use these partitions. I tried to export the kernel and import it inside the emulator without luck. I did not receive any errors that way.
So my main question is:
- Is there any way I can import the device's rom inside an android emulator
Spoiler: Emulator Config
AvdId=Junsun_A104_API_27
PlayStore.enabled=false
abi.type=arm64-v8a
avd.ini.displayname=Junsun A104 API 27
avd.ini.encoding=UTF-8
disk.dataPartition.size=800M
fastboot.chosenSnapshotFile=
fastboot.forceChosenSnapshotBoot=no
fastboot.forceColdBoot=no
fastboot.forceFastBoot=yes
hw.accelerometer=yes
hw.arc=false
hw.audioInput=yes
hw.battery=yes
hw.camera.back=virtualscene
hw.camera.front=emulated
hw.cpu.arch=arm64
hw.cpu.ncore=4
hw.dPad=no
hw.device.hash2=MD5:7834f5e80eb849ceb46ce01cd4c704f7
hw.device.manufacturer=User
hw.device.name=Junsun A104
hw.gps=yes
hw.gpu.enabled=no
hw.gpu.mode=off
hw.initialOrientation=landscape
hw.keyboard=yes
hw.lcd.density=120
hw.lcd.height=320
hw.lcd.width=1480
hw.mainKeys=no
hw.ramSize=2560
hw.sdCard=yes
hw.sensors.orientation=yes
hw.sensors.proximity=yes
hw.trackBall=no
image.sysdir.1=system-images/android-27/default/arm64-v8a/
runtime.network.latency=none
runtime.network.speed=full
sdcard.size=512M
showDeviceFrame=no
skin.dynamic=yes
skin.name=1480x320
skin.path=_no_skin
skin.path.backup=/home/dangelo/Android/Sdk/skins/tv_1080p
tag.display=Default Android System Image
tag.id=default
vm.heapSize=48
Spoiler: Partition data
$ cat /proc/partitions
major minor #blocks name
1 0 8192 ram0
1 1 8192 ram1
1 2 8192 ram2
1 3 8192 ram3
1 4 8192 ram4
1 5 8192 ram5
1 6 8192 ram6
1 7 8192 ram7
1 8 8192 ram8
1 9 8192 ram9
1 10 8192 ram10
1 11 8192 ram11
1 12 8192 ram12
1 13 8192 ram13
1 14 8192 ram14
1 15 8192 ram15
254 0 1572864 zram0
179 0 30670848 mmcblk0
179 1 5120 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 35840 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 6144 mmcblk0p5
179 6 6144 mmcblk0p6
179 7 1024 mmcblk0p7
259 0 1024 mmcblk0p8
259 1 1024 mmcblk0p9
259 2 1024 mmcblk0p10
259 3 4096 mmcblk0p11
259 4 1024 mmcblk0p12
259 5 1024 mmcblk0p13
259 6 1024 mmcblk0p14
259 7 1024 mmcblk0p15
259 8 1024 mmcblk0p16
259 9 1024 mmcblk0p17
259 10 1024 mmcblk0p18
259 11 1024 mmcblk0p19
259 12 10240 mmcblk0p20
259 13 2048 mmcblk0p21
259 14 25600 mmcblk0p22
259 15 1024 mmcblk0p23
259 16 10240 mmcblk0p24
259 17 20480 mmcblk0p25
259 18 1024 mmcblk0p26
259 19 35840 mmcblk0p27
259 20 2867200 mmcblk0p28
259 21 153600 mmcblk0p29
259 22 409600 mmcblk0p30
259 23 1024 mmcblk0p31
259 24 1024 mmcblk0p32
259 25 27059183 mmcblk0p33
179 24 4096 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
253 0 27059167 dm-0
output using the ls command with arguments that I forgot
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 boot -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 cache -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 fbootlogo -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 gpsbd -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 gpsgl -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_deltanv -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_fixnv1 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_fixnv2 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_gdsp -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_ldsp -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_modem -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_runtimenv1 -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_runtimenv2 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 logo -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 misc -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 miscdata -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 pm_sys -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 prodnv -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 recovery -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 sml -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 sml_bak -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 system -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 trustos -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 trustos_bak -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 uboot -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 uboot_bak -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 uboot_log -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 userdata -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 vbmeta -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 vbmeta_bak -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 vendor -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 wcnmodem -> /dev/block/mmcblk0p20
Spoiler: Device information
Device name: Junsun A104
Android: 8.1. Oreo API level 27
CPU:
64bit
ARM64-V8A
Spreadtrum SC9832e
Memory: 2GB
Kernel architecture: aarch64
Kernel version: 4.4.83-00001-g213b4e3
Click to expand...
Click to collapse
All you should need is the system.img and the kernel, then extract the system.img untill you find the /system/app and/or the /system/priv-app(whichever folder contains your UI.apk), extract a copy of the UI.apk. Then use APKtool to remove the signature on the apk file then decompile the apk file then make your modifications then recompile and re-sign the apk file. Then place the newly modified UI.apk in the system folder where you extracted it from(overwrite/delete the old version of the apk). Then compress all the files back into the system.img like it was originally and then try to use your newly modified system.img in your emulator.
Try using Bluestacks or one of the other leading android emulators instead of using Android Studio.