Related
Q&A for [HACK]Partition Table Tool for LG L90(really more data)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [HACK]Partition Table Tool for LG L90(really more data). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Hello, I've tried your script but now I'm not able ro mount cache or flash the stock rom. If you could help me this would be great!
http://forum.xda-developers.com/lg-l90/help/flash-stock-rom-t2953340
Kind regards
I think that this is not a fault repartitioning but rather drivers. Try select "CS_EMERGENCY" for PhoneMode.
If you can not to mount cache format try in recovery. If not working try this:
Code:
adb shell
make_ext4fs /dev/block/mmcblk0p33
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p33
reboot recovery
BigMajster said:
I think that this is not a fault repartitioning but rather drivers. Try select "CS_EMERGENCY" for PhoneMode.
If you can not to mount cache format try in recovery. If not working try this:
Code:
adb shell
make_ext4fs /dev/block/mmcblk0p33
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p33
reboot recovery
Click to expand...
Click to collapse
Hello, thank you for helping me! But when I boot the phone into Cyanogenmod, your commands doesn't work.
Code:
C:\adb>adb shell
$ make_ext4fs /dev/block/mmcblk0p33
make_ext4fs /dev/block/mmcblk0p33
open: Permission denied
$
Edit.: Oh man, just forgot the su! Now I'm able to mount cache! Thanks a lot! But I still can't flash the stock rom. Any idea?
j8o said:
Hello, thank you for helping me! But when I boot the phone into Cyanogenmod, your commands doesn't work.
Code:
C:\adb>adb shell
$ make_ext4fs /dev/block/mmcblk0p33
make_ext4fs /dev/block/mmcblk0p33
open: Permission denied
$
Edit.: Oh man, just forgot the su! Now I'm able to mount cache! Thanks a lot! But I still can't flash the stock rom. Any idea?
Click to expand...
Click to collapse
Code:
adb shell
su
make_ext4fs /dev/block/mmcblk0p32
make_ext4fs /dev/block/mmcblk0p33
make_ext4fs /dev/block/mmcblk0p34
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p32
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p33
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p34
reboot recovery
BigMajster said:
Code:
adb shell
su
make_ext4fs /dev/block/mmcblk0p32
make_ext4fs /dev/block/mmcblk0p33
make_ext4fs /dev/block/mmcblk0p34
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p32
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p33
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p34
reboot recovery
Click to expand...
Click to collapse
I've run all this commands but it didn't helped.
j8o said:
I've run all this commands but it didn't helped.
Click to expand...
Click to collapse
Code:
adb shell
su
parted -s /dev/block/mmcblk0 print
and upload screenshot
BigMajster said:
Code:
adb shell
su
parted -s /dev/block/mmcblk0 print
and upload screenshot
Click to expand...
Click to collapse
Code:
# parted -s /dev/block/mmcblk0 print
sh: parted: not found
#
You boot system, so how problem have you now?
You boot system, so how problem have you now?
Click to expand...
Click to collapse
I'm not able to flash the stock rom.
Update. I get the phone to read adb serial # but it says offline. I'm having trouble trying to flash a custom recovery into it right now. Its a little more own tho.. I spend some time guessing random passwords. Should I stop that? I probably won't pick it by I might do more damage. Dammit my other one a brick too. Now all I have left that work are this galaxe s3 and an evo 4g with a cracked to hell screen. I can experiment on the l90 and the lg lucid till they work or break. Any help is appreciated..
To the op, you might want to put a disclaimer on this thread. Seems a little chancy to me.
[help] D405n stuck after trying tu use "Partition Table tool for LG L90"
Hi,
First this is my first post on this forum, so I can't post directly on the "Partition Table Tool for LG L90" thread
I use candy5 rom and twrp.
My problem is after I have used the partition tool, I have re-flash candy5 custom rom, and now it's stuck at the rom boot, and I'm unable to enter the recovery. So it seems to be bricked :-/
In adb my devices is detect but offline.
Can someone help me?
Thanks.
grizzzlly said:
Hi,
First this is my first post on this forum, so I can't post directly on the "Partition Table Tool for LG L90" thread
I use candy5 rom and twrp.
My problem is after I have used the partition tool, I have re-flash candy5 custom rom, and now it's stuck at the rom boot, and I'm unable to enter the recovery. So it seems to be bricked :-/
In adb my devices is detect but offline.
Can someone help me?
Thanks.
Click to expand...
Click to collapse
What is size of partition? Gapps installed?
I have choose "maximal" option, gapps not installed
Try to install CM11 maybe Candy takes up too much space
yup, but my real problem now is just I can't enter in the recovery.
Why? You can go to recovery by key combo
exactly, the key combo works but the device reboot before entering the recovery.
If you want to restore it to life using this method http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479 but select "CS_EMERGENCY" for PhoneMode.
Unless there is no other option.
thanks, ill try this.
But I think it will not work cause my device don't boot and so is no detected on my computer.:crying:
Hi guys,
first please be lenient with my english, I do my best to express myself.
My friend gave me a Kindle Fire HD7 2nd generation, which is bricked, cause he installed cyanogenmod on it and one day, he tried to reset the kindle by soft-resetting. But now the kindle stucks on the recovery TWRP's logo.
So I tried to unbrick it. I tried lots of fixes, always failed. First, I've installed the kindle adb drivers, and now the tablet is reconized as plugged and in recovery.
I can go in a shell, try an adb shell id and everything's okayas you can see, I'm root.
Code:
adb shell id
uid=0(root) gid=0(root)
But now, I can't access to the reocvery, I've tried the following commands and this is where I am.
Code:
adb shell
~ # idme bootmode 4002
/sbin/sh: idme: not found
~ # ls -a /sbin/
[
[[
adbd
adjtimex
arp
ash
awk
base64
basename
bbconfig
blkid
blockdev
brctl
bunzip2
busybox
bzcat
bzip2
cal
cat
catv
chattr
chcon
chgrp
chmod
chown
chroot
clear
cmp
comm
cp
cpio
crond
crontab
cut
date
dc
dd
depmod
devmem
df
diff
dirname
dmesg
dnsd
dos2unix
dosfsck
dosfslabel
du
dump_image
e2fsck
echo
ed
egrep
env
erase_image
exfat-fuse
expand
expr
false
fb2png
fbsplash
fdisk
fgrep
find
fix_permissions.sh
flash_image
flash_lock
flash_unlock
flashcp
flock
fold
free
freeramdisk
fsck.exfat
fstrim
fsync
ftpget
ftpput
fuser
getenforce
getopt
getprop
getsebool
grep
groups
gunzip
gzip
halt
head
hexdump
id
ifconfig
inetd
insmod
install
ionice
iostat
ip
kill
killall
killall5
less
libaosprecovery.so
libblkid.so
libbmlutils.so
libc.so
libcutils.so
libdl.so
libexfat.so
libext2_blkid.so
libext2_com_err.so
libext2_e2p.so
libext2_profile.so
libext2_uuid.so
libext2fs.so
libext4_utils.so
libflashutils.so
libjpeg.so
liblog.so
libm.so
libminadbd.so
libminuitwrp.so
libminzip.so
libmmcutils.so
libmtdutils.so
libopenaes.so
libselinux.so
libsparse.so
libstdc++.so
libstlport.so
libtar.so
libz.so
linker
ln
load_policy
losetup
ls
lsattr
lsmod
lsusb
lzcat
lzma
lzop
lzopcat
make_ext4fs
man
md5sum
mesg
minivold
mkdir
mkdosfs
mke2fs
mkexfatfs
mkfifo
mkfs.exfat
mkfs.ext2
mkfs.vfat
mknod
mkswap
mktemp
modinfo
modprobe
more
mount
mount.exfat
mountpoint
mpstat
mv
nanddump
nandwrite
nbd-client
nc
netstat
nice
nohup
nslookup
ntpd
od
openaes
patch
pgrep
pidof
pigz
ping
pipe_progress
pkill
pmap
postrecoveryboot.sh
poweroff
printenv
printf
ps
pstree
pwd
pwdx
rdev
readlink
realpath
recovery
renice
reset
resize
restorecon
rev
rm
rmdir
rmmod
route
run-parts
runcon
rx
sed
seq
setconsole
setenforce
setprop
setsebool
setserial
setsid
sh
sha1sum
sha256sum
sha3sum
sha512sum
sleep
sort
split
start
stat
stop
strings
stty
sum
swapoff
swapon
sync
sysctl
tac
tail
tar
taskset
teamwin
tee
telnet
telnetd
test
tftp
tftpd
time
timeout
toolbox
top
touch
tr
traceroute
true
ttysize
tune2fs
ueventd
umount
uname
uncompress
unexpand
uniq
unix2dos
unlzma
unlzop
unpigz
unxz
unzip
uptime
usleep
uudecode
uuencode
vi
watch
watchdogd
wc
wget
which
whoami
xargs
xz
xzcat
yes
zcat
So as you can see, idme is not here. Then I've tried to manually replace all folders and files in each directory of the kindle, but after a manual reboot the kindle resets. Also, I've tried to use the Kindle Fire Utility but it didn't work.
I can't do anything else, if you have questions I'm here to answer you for details, but I don't have any idea of what can I do, I tried all the solutions proposed in the differents threads in the forum.
Thanks
Jb-kun said:
Hi guys,
first please be lenient with my english, I do my best to express myself.
My friend gave me a Kindle Fire HD7 2nd generation, which is bricked, cause he installed cyanogenmod on it and one day, he tried to reset the kindle by soft-resetting. But now the kindle stucks on the recovery TWRP's logo.
So I tried to unbrick it. I tried lots of fixes, always failed. First, I've installed the kindle adb drivers, and now the tablet is reconized as plugged and in recovery.
I can go in a shell, try an adb shell id and everything's okayas you can see, I'm root.
But now, I can't access to the reocvery, I've tried the following commands and this is where I am.
So as you can see, idme is not here. Then I've tried to manually replace all folders and files in each directory of the kindle, but after a manual reboot the kindle resets. Also, I've tried to use the Kindle Fire Utility but it didn't work.
I can't do anything else, if you have questions I'm here to answer you for details, but I don't have any idea of what can I do, I tried all the solutions proposed in the differents threads in the forum.
Thanks
Click to expand...
Click to collapse
see 2nd generation forums
link in Fire Index: Which Amazon (Kindle) Fire Do I have?
Sent from my XT1254 using XDA Labs
sd_shadow said:
see 2nd generation forums
link in Fire Index: Which Amazon (Kindle) Fire Do I have?
Sent from my XT1254 using XDA Labs
Click to expand...
Click to collapse
Thanks a lot, I've never seen this thread, I'll check it !
Okay, now I've flashed boot.img and recovery.img, thanks to this thread. Now the tablet bootloop on the "kindle fire" orange logo, and the kindle is not reconized as connected for my pc anymore (and so not detected in adb or fastboot). Any idea?
My device is a Xiaomi Mi A2 / Android 8.1, rooted with Magisk v16.0. I am running Termux. Now, look at this:
Code:
$ whoami
u0_a88
$ su
# echo foo >bar
# ls -l bar
-rw-r--r-- 1 root root 4 2018-08-21 22:08 bar
# chown u0_a88.u0_a88 bar
# exit
$ ls -l bar
-rw-r--r-- 1 u0_a88 u0_a88 4 2018-08-21 22:08 bar
$ echo baz >bar
bash: bar: Permission denied
A reboot does not help. The file remains inaccessible to user u0_a88 despites having been made the owner.
What is going on here?
feklee said:
What is going on here?
Click to expand...
Click to collapse
SELinux is going on:
Code:
$ su
# getenforce
Enforcing
To get permissions to bar:
Code:
$ su
# restorecon bar
# exit
$ echo baz >bar
I don't why Moto banned 5Ghz wifi on G8 family. This is really a stupid decision. But our wifi chip is wcn3390, I'm 100% sure our hardware supports 5Ghz.
Here I provide a method to unlock it on custom ROMs. Because I'm not sure if vendor_overlay could work on Official firmware.
You only need to flash Magisk module, it works on both stock and custom ROMs now.
Step 1 Mount product partition
flash twrp and boot into it. Mount product partition in Mount menu.
Then connect to your PC, run this adb command to make product partition writable.
Code:
adb shell mount -o remount,rw /product
Step 2 Create floder
Run these adb commonds:
Code:
adb shell mkdir /product/vendor_overlay/29/etc/wifi
adb shell chmod -R 755 /product/vendor_overlay/29/etc/wifi
Step 3 Push custom wlan config
Download the WCNSS_qcom_cfg.zip provided by me, unzip it, then copy WCNSS_qcom_cfg.ini to the adb tool root floder.
Run these adb commonds:
Code:
adb push WCNSS_qcom_cfg.ini /product/vendor_overlay/29/etc/wifi/
adb shell chmod -R 644 /product/vendor_overlay/29/etc/wifi/WCNSS_qcom_cfg.ini
Reboot, I think you already unlocked the 5Ghz wifi bands, you could enjoy 433Mbps speed now.
Also provide a kernel which built-in upsteam qcom wifi kernel drivers. But this is not necessary. You could replace it with anykernel or AIK.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I will try this as soon as im home, i never knew you had moto's sjll, i thought you were sony only lol
My stock rom for Moto G8/G Fast had this built into it, I had access to 5G access point out of the box, the custom roms I use all have it as well, so...
Moto g8 doesnt have access to 5g networks as far as i know, only g fast. @PimpMy5Ton
I was unable to get the 5Ghz result in my WiFi after following the instructions listed. I am running Havoc-OS 22-12-20 Build (https://forum.xda-developers.com/t/rom-rav-sofia-10-unofficial-havocos-3-12.4165007)
Code:
# dmesg output on config file in system
rav:/ # dmesg | grep -i wcnss
[ 18.838954] ueventd: firmware: loading 'wlan/qca_cld/WCNSS_qcom_cfg.ini' for '/devices/platform/soc/c800000.qcom,icnss/firmware/wlan!qca_cld!WCNSS_qcom_cfg.ini'
[ 18.849240] ueventd: loading /devices/platform/soc/c800000.qcom,icnss/firmware/wlan!qca_cld!WCNSS_qcom_cfg.ini took 10ms
# --- ADB SHELL (TWRP) --- #
# File and directory permissions
sofiar:/ # ls -l /product/vendor_overlay/29/etc/
total 28
drwxr-xr-x 2 root root 4096 2020-12-22 08:35 audio
-rw-r--r-- 1 root root 15269 2020-12-22 08:35 audio_policy_configuration.xml
drwxr-xr-x 2 root root 4096 2020-12-22 08:35 init
drwxr-xr-x 2 root root 4096 2021-01-23 19:10 wifi
sofiar:/ # ls -l /product/vendor_overlay/29/etc/wifi
total 16
-rw-r--r-- 1 root root 12972 2021-01-17 13:15 WCNSS_qcom_cfg.ini
# Sha1sum
sofiar:/ # sha1sum /product/vendor_overlay/29/etc/wifi/WCNSS_qcom_cfg.ini
3bb6d285c81234714266233d5febb100d25c0872 /product/vendor_overlay/29/etc/wifi/WCNSS_qcom_cfg.ini
dylantjb said:
I was unable to get the 5Ghz result in my WiFi after following the instructions listed. I am running Havoc-OS 22-12-20 Build (https://forum.xda-developers.com/t/rom-rav-sofia-10-unofficial-havocos-3-12.4165007)
Code:
# dmesg output on config file in system
rav:/ # dmesg | grep -i wcnss
[ 18.838954] ueventd: firmware: loading 'wlan/qca_cld/WCNSS_qcom_cfg.ini' for '/devices/platform/soc/c800000.qcom,icnss/firmware/wlan!qca_cld!WCNSS_qcom_cfg.ini'
[ 18.849240] ueventd: loading /devices/platform/soc/c800000.qcom,icnss/firmware/wlan!qca_cld!WCNSS_qcom_cfg.ini took 10ms
# --- ADB SHELL (TWRP) --- #
# File and directory permissions
sofiar:/ # ls -l /product/vendor_overlay/29/etc/
total 28
drwxr-xr-x 2 root root 4096 2020-12-22 08:35 audio
-rw-r--r-- 1 root root 15269 2020-12-22 08:35 audio_policy_configuration.xml
drwxr-xr-x 2 root root 4096 2020-12-22 08:35 init
drwxr-xr-x 2 root root 4096 2021-01-23 19:10 wifi
sofiar:/ # ls -l /product/vendor_overlay/29/etc/wifi
total 16
-rw-r--r-- 1 root root 12972 2021-01-17 13:15 WCNSS_qcom_cfg.ini
# Sha1sum
sofiar:/ # sha1sum /product/vendor_overlay/29/etc/wifi/WCNSS_qcom_cfg.ini
3bb6d285c81234714266233d5febb100d25c0872 /product/vendor_overlay/29/etc/wifi/WCNSS_qcom_cfg.ini
View attachment 5196947
Click to expand...
Click to collapse
This is interesting, according to @Beetle84 only G fast supports 5Ghz, can you check the wifi chip with device hw info?
From Googling the difference it looks like the G fast comes with 5Ghz out of the box.
Seems to be the same supported WiFi chip though.
dylantjb said:
From Googling the difference it looks like the G fast comes with 5Ghz out of the box.
Seems to be the same supported WiFi chip though.
View attachment 5197299
Click to expand...
Click to collapse
Oops, I read that wrong. Mine is the wcn3990 and not wc3390.
dylantjb said:
Oops, I read that wrong. Mine is the wcn3990 and not wc3390.
Click to expand...
Click to collapse
Do G8 & G fast share the same official firmware?
Are both of them are rav?
Sjll said:
Do G8 & G fast share the same official firmware?
Are both of them are rav?
Click to expand...
Click to collapse
The Moto G Fast (US, 2020) has model number XT2045-3 which comes under rav in lolinet so they should.
dylantjb said:
The Moto G Fast (US, 2020) has model number XT2045-3 which comes under rav in lolinet so they should.
Click to expand...
Click to collapse
However the G Fast is US only (RETUS) and my Moto G8 is European (RETEU).
dylantjb said:
However the G Fast is US only (RETUS) and my Moto G8 is European (RETEU).
Click to expand...
Click to collapse
Can you dump your partitions and uploaded them?
In twrp:
adb shell mkdir /tmp/dump/
adb shell dd if=/dev/block/by-name/apdp of=/tmp/dump/apdp.img
adb shell dd if=/dev/block/by-name/cid of=/tmp/dump/cid.img
adb shell dd if=/dev/block/by-name/devinfo of=/tmp/dump/devinfo.img
adb shell dd if=/dev/block/by-name/dpo of=/tmp/dump/dpo.img
adb shell dd if=/dev/block/by-name/fsc of=/tmp/dump/fsc.img
adb shell dd if=/dev/block/by-name/fsg_a of=/tmp/dump/fsg_a.img
adb shell dd if=/dev/block/by-name/fsg_b of=/tmp/dump/fsg_b.img
adb shell dd if=/dev/block/by-name/hw of=/tmp/dump/hw.img
adb shell dd if=/dev/block/by-name/kpan of=/tmp/dump/kpan.img
adb shell dd if=/dev/block/by-name/logfs of=/tmp/dump/logfs.img
adb shell dd if=/dev/block/by-name/misc of=/tmp/dump/misc.img
adb shell dd if=/dev/block/by-name/mmcblk0 of=/tmp/dump/mmcblk0.img
adb shell dd if=/dev/block/by-name/mmcblk0rpmb of=/tmp/dump/mmcblk0rpmb.img
adb shell dd if=/dev/block/by-name/msadp of=/tmp/dump/msadp.img
adb shell dd if=/dev/block/by-name/multiimgoem_a of=/tmp/dump/multiimgoem_a.img
adb shell dd if=/dev/block/by-name/multiimgoem_b of=/tmp/dump/multiimgoem_b.img
adb shell dd if=/dev/block/by-name/multiimgqti_a of=/tmp/dump/multiimgqti_a.img
adb shell dd if=/dev/block/by-name/multiimgqti_b of=/tmp/dump/multiimgqti_b.img
adb shell dd if=/dev/block/by-name/prodpersist of=/tmp/dump/prodpersist.img
adb shell dd if=/dev/block/by-name/ramdump of=/tmp/dump/ramdump.img
adb shell dd if=/dev/block/by-name/ramdump_padding_0 of=/tmp/dump/ramdump_padding_0.img
adb shell dd if=/dev/block/by-name/ramdump_padding_1 of=/tmp/dump/ramdump_padding_1.img
adb shell dd if=/dev/block/by-name/ramdump_padding_2 of=/tmp/dump/ramdump_padding_2.img
adb shell dd if=/dev/block/by-name/sp of=/tmp/dump/sp.img
adb shell dd if=/dev/block/by-name/spunvm of=/tmp/dump/spunvm.img
adb shell dd if=/dev/block/by-name/ssd of=/tmp/dump/ssd.img
adb shell dd if=/dev/block/by-name/storsec_a of=/tmp/dump/storsec_a.img
adb shell dd if=/dev/block/by-name/storsec_b of=/tmp/dump/storsec_b.img
adb shell dd if=/dev/block/by-name/uefivarstore of=/tmp/dump/uefivarstore.img
adb shell dd if=/dev/block/by-name/utags of=/tmp/dump/utags.img
adb shell dd if=/dev/block/by-name/utagsBackup of=/tmp/dump/utagsBackup.img
adb pull /tmp/dump
Some of your requested partitions couldn't be dumped:
/dev/block/by-name/mmcblk0rpmb: read error: I/O error
/dev/block/by-name/ramdump: No such file or directory
/dev/block/by-name/ramdump_padding_0: No such file or directory
/dev/block/by-name/ramdump_padding_1 No such file or directory
/dev/block/by-name/ramdump_padding_2: No such file or directory
dylantjb said:
Some of your requested partitions couldn't be dumped:
/dev/block/by-name/mmcblk0rpmb: read error: I/O error
/dev/block/by-name/ramdump: No such file or directory
/dev/block/by-name/ramdump_padding_0: No such file or directory
/dev/block/by-name/ramdump_padding_1 No such file or directory
/dev/block/by-name/ramdump_padding_2: No such file or directory
Click to expand...
Click to collapse
Doesn't matter, can you upload the rest img you dumped?
Sjll said:
Do G8 & G fast share the same official firmware?
Are both of them are rav?
Click to expand...
Click to collapse
g fast is rav_t, g8 is rav. Different firmwares are provided for both phones.
Sjll said:
Doesn't matter, can you upload the rest img you dumped?
Click to expand...
Click to collapse
[REDACTED]
vache said:
g fast is rav_t, g8 is rav. Different firmwares are provided for both phones.
Click to expand...
Click to collapse
Thanks for this info! This is very interesting, Mine is G Fast, but the vendor I used is G8's. 5Ghz works for me.
dylantjb said:
https://emckclac-my.sharepoint.com/:u:/g/personal/k20001430_kcl_ac_uk/EXPN-5RuYb5EmFB4d2PQME4BxmZNVZ97FcE1unpHqlJfvw?e=3lW4ze
Click to expand...
Click to collapse
Thanks, I will try to restore your dumps on my G fast.
------------------EDIT----------------------
emmmm, I am so sorry, you dumped
Code:
mmcblk0
, this is the whole image of your EMMC.
My bad, it is too large, 44GB....
Can you delete it and repack the dumps again? The normal size of useful partitions should be under 500MB I think.
Code:
adb shell mkdir /tmp/dump/
adb shell dd if=/dev/block/by-name/apdp of=/tmp/dump/apdp.img
adb shell dd if=/dev/block/by-name/cid of=/tmp/dump/cid.img
adb shell dd if=/dev/block/by-name/devinfo of=/tmp/dump/devinfo.img
adb shell dd if=/dev/block/by-name/dpo of=/tmp/dump/dpo.img
adb shell dd if=/dev/block/by-name/fsc of=/tmp/dump/fsc.img
adb shell dd if=/dev/block/by-name/fsg_a of=/tmp/dump/fsg_a.img
adb shell dd if=/dev/block/by-name/fsg_b of=/tmp/dump/fsg_b.img
adb shell dd if=/dev/block/by-name/hw of=/tmp/dump/hw.img
adb shell dd if=/dev/block/by-name/kpan of=/tmp/dump/kpan.img
adb shell dd if=/dev/block/by-name/logfs of=/tmp/dump/logfs.img
adb shell dd if=/dev/block/by-name/misc of=/tmp/dump/misc.img
adb shell dd if=/dev/block/by-name/msadp of=/tmp/dump/msadp.img
adb shell dd if=/dev/block/by-name/multiimgoem_a of=/tmp/dump/multiimgoem_a.img
adb shell dd if=/dev/block/by-name/multiimgoem_b of=/tmp/dump/multiimgoem_b.img
adb shell dd if=/dev/block/by-name/multiimgqti_a of=/tmp/dump/multiimgqti_a.img
adb shell dd if=/dev/block/by-name/multiimgqti_b of=/tmp/dump/multiimgqti_b.img
adb shell dd if=/dev/block/by-name/prodpersist of=/tmp/dump/prodpersist.img
adb shell dd if=/dev/block/by-name/ramdump of=/tmp/dump/ramdump.img
adb shell dd if=/dev/block/by-name/sp of=/tmp/dump/sp.img
adb shell dd if=/dev/block/by-name/spunvm of=/tmp/dump/spunvm.img
adb shell dd if=/dev/block/by-name/ssd of=/tmp/dump/ssd.img
adb shell dd if=/dev/block/by-name/storsec_a of=/tmp/dump/storsec_a.img
adb shell dd if=/dev/block/by-name/storsec_b of=/tmp/dump/storsec_b.img
adb shell dd if=/dev/block/by-name/uefivarstore of=/tmp/dump/uefivarstore.img
adb shell dd if=/dev/block/by-name/utags of=/tmp/dump/utags.img
adb shell dd if=/dev/block/by-name/utagsBackup of=/tmp/dump/utagsBackup.img
adb pull /tmp/dump
Sjll said:
My bad, it is too large, 44GB....
Click to expand...
Click to collapse
That makes a lot more sense now, took quite a lot of space on my laptop!
dylantjb said:
That makes a lot more sense now, took quite a lot of space on my laptop!
Click to expand...
Click to collapse
Okk, I tried, I still have 5Ghz after restoring your imgs.
IMEI didn't change, some info must stored in other places. let me upload mine.
You can try:
Code:
dd if=/tmp/dump/apdp.img of=/dev/block/by-name/apdp
dd if=/tmp/dump/cid.img of=/dev/block/by-name/cid
dd if=/tmp/dump/devinfo.img of=/dev/block/by-name/devinfo
dd if=/tmp/dump/dpo.img of=/dev/block/by-name/dpo
dd if=/tmp/dump/fsc.img of=/dev/block/by-name/fsc
dd if=/tmp/dump/fsg_a.img of=/dev/block/by-name/fsg_a
dd if=/tmp/dump/fsg_b.img of=/dev/block/by-name/fsg_b
dd if=/tmp/dump/hw.img of=/dev/block/by-name/hw
dd if=/tmp/dump/kpan.img of=/dev/block/by-name/kpan
dd if=/tmp/dump/logfs.img of=/dev/block/by-name/logfs
dd if=/tmp/dump/misc.img of=/dev/block/by-name/misc
dd if=/tmp/dump/msadp.img of=/dev/block/by-name/msadp
dd if=/tmp/dump/multiimgoem_a.img of=/dev/block/by-name/multiimgoem_a
dd if=/tmp/dump/multiimgoem_b.img of=/dev/block/by-name/multiimgoem_b
dd if=/tmp/dump/multiimgqti_a.img of=/dev/block/by-name/multiimgqti_a
dd if=/tmp/dump/multiimgqti_b.img of=/dev/block/by-name/multiimgqti_b
dd if=/tmp/dump/prodpersist.img of=/dev/block/by-name/prodpersist
dd if=/tmp/dump/sp.img of=/dev/block/by-name/sp
dd if=/tmp/dump/spunvm.img of=/dev/block/by-name/spunvm
dd if=/tmp/dump/ssd.img of=/dev/block/by-name/ssd
dd if=/tmp/dump/storsec_a.img of=/dev/block/by-name/storsec_a
dd if=/tmp/dump/storsec_b.img of=/dev/block/by-name/storsec_b
dd if=/tmp/dump/uefivarstore.img of=/dev/block/by-name/uefivarstore
dd if=/tmp/dump/utags.img of=/dev/block/by-name/utags
dd if=/tmp/dump/utagsBackup.img of=/dev/block/by-name/utagsBackup
Sjll said:
Okk, I tried, I still have 5Ghz after restoring your imgs.
IMEI didn't change, some info must stored in other places. let me upload mine.
You can try:
Code:
dd if=/tmp/dump/apdp.img of=/dev/block/by-name/apdp
dd if=/tmp/dump/cid.img of=/dev/block/by-name/cid
dd if=/tmp/dump/devinfo.img of=/dev/block/by-name/devinfo
dd if=/tmp/dump/dpo.img of=/dev/block/by-name/dpo
dd if=/tmp/dump/fsc.img of=/dev/block/by-name/fsc
dd if=/tmp/dump/fsg_a.img of=/dev/block/by-name/fsg_a
dd if=/tmp/dump/fsg_b.img of=/dev/block/by-name/fsg_b
dd if=/tmp/dump/hw.img of=/dev/block/by-name/hw
dd if=/tmp/dump/kpan.img of=/dev/block/by-name/kpan
dd if=/tmp/dump/logfs.img of=/dev/block/by-name/logfs
dd if=/tmp/dump/misc.img of=/dev/block/by-name/misc
dd if=/tmp/dump/msadp.img of=/dev/block/by-name/msadp
dd if=/tmp/dump/multiimgoem_a.img of=/dev/block/by-name/multiimgoem_a
dd if=/tmp/dump/multiimgoem_b.img of=/dev/block/by-name/multiimgoem_b
dd if=/tmp/dump/multiimgqti_a.img of=/dev/block/by-name/multiimgqti_a
dd if=/tmp/dump/multiimgqti_b.img of=/dev/block/by-name/multiimgqti_b
dd if=/tmp/dump/prodpersist.img of=/dev/block/by-name/prodpersist
dd if=/tmp/dump/sp.img of=/dev/block/by-name/sp
dd if=/tmp/dump/spunvm.img of=/dev/block/by-name/spunvm
dd if=/tmp/dump/ssd.img of=/dev/block/by-name/ssd
dd if=/tmp/dump/storsec_a.img of=/dev/block/by-name/storsec_a
dd if=/tmp/dump/storsec_b.img of=/dev/block/by-name/storsec_b
dd if=/tmp/dump/uefivarstore.img of=/dev/block/by-name/uefivarstore
dd if=/tmp/dump/utags.img of=/dev/block/by-name/utags
dd if=/tmp/dump/utagsBackup.img of=/dev/block/by-name/utagsBackup
Click to expand...
Click to collapse
I did it but still got 2.4Ghz speed on my WiFi.
I replaced old /system/bin/toybox with a new binary from http://landley.net/toybox/bin then I created symlinks with for i in $(./toybox); do ln -s toybox $i. There is su in symlinks.
Now I cannot open Magisk anymore, stuck at splash screen mask.
Also MiXplorer cannot browse root dirs.
With Terminal Emulator I can still browse root dirs.
If I type which su I get /sbin/su which is a symlink to /sbin/magisk.
I have not yet tried to reboot because I fear to get stuck, maybe it would repair by itself but who knows?
If I type whoami I get bad uid 0, after su shell I get bad uid 2000 and so on.
How can I restore root? I can access TWRP recovery.
how about /sbin/su -c unlink /system/bin/su or wherever you symlinked toybox applets?
are you sure that binary is actually a replacement including all android specific applets (like getevent) for built-in toybox?
why did you replace system files in first place if you're actually on Magisk and could just use systemless overlays instead?
If I try to unlink it says it's read-only file system. I could try to do it in recovery but I'm afraid to reboot...
What is strange is that which su points to /sbin/magisk, so it should not consider the other su symlink to toybox
Another thing I noticed is that new symlink to toybox created with my script are root both UID and GID, while existing ones are root UID and shell GID
Toybox binary is specific for my Android ARMv8 http://landley.net/toybox/downloads/binaries/0.8.9/toybox-aarch64.
You are right about systemless overlays.
aarch64 is only the cpu architecture, doesn't say anything about android.
how did you install toybox on read-only file system? remount -o,rw /
ok, however the arch is right for my Snap855, I tried other applets embedded in toybox, like factor, and they work.
I used MiXplorer to write to system, I gave it root permissions so it could work on it. Now MiX is unarmed and Terminal Emulator can only read into root dirs but not write.
quick check with my toybox yours is missing all android specific applets
Code:
:/ $ cd $HOME
:/data/user/0/jackpal.androidterm/app_HOME $ ls -la
total 780
drwxrwx--x 2 u0_a152 u0_a152 4096 2023-01-30 14:46 .
drwxr-x--x 6 u0_a152 u0_a152 4096 2023-01-28 01:58 ..
-rwx--x--x 1 u0_a152 u0_a152 783680 2023-01-30 14:24 toybox
:/data/user/0/jackpal.androidterm/app_HOME $ ./toybox --version
toybox 0.8.9
:/data/user/0/jackpal.androidterm/app_HOME $ toybox --version
toybox 0.7.6-android
:/data/user/0/jackpal.androidterm/app_HOME $ for i in $(toybox); do ./toybox | grep -qw $i || echo $i; done
chcon
dd
diff
expr
getenforce
getfattr
gzip
load_policy
lsof
modprobe
more
restorecon
runcon
sendevent
setenforce
setprop
start
stop
stty
tr
traceroute
traceroute6
you should reinstall stock toybox from TWRP backup.
edit: this might help
Code:
:/ $ ls -lZ /system/bin/toybox
-rwxr-xr-x 1 root shell u:object_r:toolbox_exec:s0 352532 2008-12-31 17:00 /system/bin/toybox
I renamed the old toybox, so I could restore it from recovery.
Btw, I get this with ls -lZ
-rwxr-xr-x 1 0 2000 ? 825176 2023-01-29 07:34 /system/bin/toybox
Seem to have lost context there.
Thanks for your quick replies.
either you're on Jelly bean or you lost secontext. repair with chcon
Code:
chcon u:object_r:toolbox_exec:s0 /system/bin/toybox
You are right, new toybox does not have specific Android applet, like chcon or restorecon.
So, please correct me if I'm wrong, I reboot in TWRP, restore old toybox.
Then should I run chcon / restorecon or reboot straight away?
I lost secontext in all root dirs /, /system, /vendor, /sdcard...
not sure what ROM you're talking about. maybe you used ls of wrong toybox?
Don't understand your answer, what ROM are you referring to?
If I ./"toybox old" restorecon I get restorecon: Needs 1 argument (see "restorecon --help")
If I restorecon I get toybox: Unknown command restorecon (see "toybox --help")
Please advise me if it's right to restore old toybox via TWRP and reboot to system or there's the need to chcon / restorecon, thanks
please give the output of
Code:
grep ro.build.fingerprint /system/build.prop /system*/system/build.prop
it's very unlikely you lost every secontext. either it never existed or you just can't view.
restorecon won't help you much. only restoring TWRP backup could restore secontext as it was before.
grep ro.build.fingerprint /system/build.prop
ro.build.fingerprint=Xiaomi/cepheus_eea/cepheus:10/QKQ1.190825.002/V11.0.9.0.QFAEUXM:user/release-keys
ro.build.fingerprint_real=Xiaomi/cepheus/cepheus:10/QKQ1.190825.002/20.7.2:user/release-keys/1593694646
so your ROM is stock ROM Android 10 it must have secontext of course. in case it's true you lost every secontext best is download cepheus_eea_global_images_V11.0.9.0.QFAEUXM_20200421.0000.00_10.0_eea_31715f4bd1.tgz and flash_all_except_storage.bat
(you can backup boot in TWRP beforehand and flash boot.emmc.win from fastboot right after)
edit: build.prop usually is in /system(_root)/system/build.prop on new devices, so most likely what you think is build.prop is just from the TWRP image used.
maybe you didn't mount System?
Resolved
Rebooted into TWRP, restored original toybox, deleted my symlinks, checked secontexts ok, rebooted to system, all fine.
Thank for your support
you can place toybox in /data/adb/modules/toybox/system/xbin/toybox, make a diff and only symlink missing applets in there.
then create modules.prop, reboot and done.