Database Users

Verizon VK810 rooted and TWRP

Wheres the roms? This thing is finally rooted with recovery, are there any known working roms?
Sent from my VK810 4G using XDA Premium HD app

Chance77 said:
Wheres the roms? This thing is finally rooted with recovery, are there any known working roms?
Sent from my VK810 4G using XDA Premium HD app
Click to expand...
Click to collapse
Give it time, grasshopper. These things take time. There are just enough differences between the 500/501 and 810 and the dev's need time to mod the kernel, build and find testers.
Also, as far as I know, we don't have source for the VK810 yet so that may slow things down a bit.
Believe me, i'm also waiting on an AOSP / GPE experience to make this thing perfect.

LG already released source. https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=vk810

edgemaster191 said:
Give it time, grasshopper. These things take time. There are just enough differences between the 500/501 and 810 and the dev's need time to mod the kernel, build and find testers.
Also, as far as I know, we don't have source for the VK810 yet so that may slow things down a bit.
Believe me, i'm also waiting on an AOSP / GPE experience to make this thing perfect.
Click to expand...
Click to collapse
I wish I shared your optimism. I hope I'm wrong but it isn't looking good. The only reason we got TWRP support is because someone that has the other device helped with the 810. There seems to be next to no momentum on the 810 side. There just doesn't seem to be a lot of developers who have that device.

prana22 said:
I wish I shared your optimism. I hope I'm wrong but it isn't looking good. The only reason we got TWRP support is because someone that has the other device helped with the 810. There seems to be next to no momentum on the 810 side. There just doesn't seem to be a lot of developers who have that device.
Click to expand...
Click to collapse
I would do something but I have never even compiled CM11 let alone tweaked it to work with a new device. I can work with a developer who doesn't have one, but I don't know enough to do it on my own.

That is where I am as well. I know just enough to get myself in trouble.
Sent from my VK810 4G using XDA Free mobile app

anyone care to share a system dump of the VK810?
boot.img and system partition would be useful
my local verizon store refuses to sell it to me without a contract............ sigh
probably going to get it from amazon

Sure, how do I do that? <-- I am a noob

popezaphod said:
Sure, how do I do that? <-- I am a noob
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2450045
info about the various partitions,good reading: http://www.all-things-android.com/content/review-android-partition-layout
if you have the custom recovery installed, you could do a backup of the device from recovery and share the files
don't share your EFS partition because it contains your unique IMEI/ESN number, and sometimes devices break if you flash someone else's EFS partition. don't share your userdata partition obviously
(if you can't figure out which is the EFS partition from the WAY #2 image, or how to do a system dump, I just need the following partitions and partition layout)
What I need:
1) Following partitions
BOOT - contains ramdisk info necessary to compile a working boot image
RECOVERY - not that necessary, but more info is useful
SYSTEM - probably contains modem libraries not present in the v500 system partition
2) Partition Layout
needed to compile a working ROM
more info is better... so a complete system dump (minus EFS and userdata) would be great
thanks for helping...

Good Amount of Info
ro.product
Code:
[ro.product.board]: [MSM8960]
[ro.product.brand]: [lge]
[ro.product.cpu.abi2]: [armeabi]
[ro.product.cpu.abi]: [armeabi-v7a]
[ro.product.device]: [altev]
[ro.product.locale.language]: [en]
[ro.product.locale.region]: [US]
[ro.product.manufacturer]: [LGE]
[ro.product.model]: [VK810 4G]
[ro.product.name]: [altev_vzw]
[email protected]:/ # getprop | grep ro.build.
ro.build
Code:
[ro.build.characteristics]: [tablet]
[ro.build.date.utc]: [1392900914]
[ro.build.date]: [Thu Feb 20 21:55:14 KST 2014]
[ro.build.description]: [altev_vzw-user 4.2.2 JDQ39B VK81010C.1392900840 release
-keys]
[ro.build.display.id]: [JDQ39B]
[ro.build.fingerprint]: [lge/altev_vzw/altev:4.2.2/JDQ39B/VK81010C.1392900840:us
er/release-keys]
[ro.build.host]: [LGEARND9B11]
[ro.build.id]: [JDQ39B]
[ro.build.product]: [altev]
[ro.build.tags]: [release-keys]
[ro.build.target_country]: [US]
[ro.build.target_operator]: [VZW]
[ro.build.target_region]: [US]
[ro.build.type]: [user]
[ro.build.user]: [hyungjin.yoo]
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [VK81010C.1392900840]
[ro.build.version.release]: [4.2.2]
[ro.build.version.sdk]: [17]
Stock aBoot img
https://www.dropbox.com/s/kf3fysyhvlyw8l0/aboot.img
Boot IMG w/ TWRP Installed(Not sure if that matters or not)
https://www.dropbox.com/s/egm0rp381cahbeo/boot.img
TWRP Recovory
https://www.dropbox.com/s/ypwreq1c07yj36v/VK810_twrp_2.7.0.1.zip
Recovory IMG w/ TWRP Installed
https://www.dropbox.com/s/23xy2o8qydqsunu/recovery.img
Stock build.prop
https://www.dropbox.com/s/4rqciye90mhp1cj/build.prop
Partitions
Code:
7 0 5229 loop0
7 1 22901 loop1
179 0 15388672 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 2048 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 24576 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 780 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8 mmcblk0p17
179 18 16384 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 8192 mmcblk0p20
179 21 512 mmcblk0p21
179 22 512 mmcblk0p22
179 23 2195456 mmcblk0p23
179 24 1392640 mmcblk0p24
179 25 8192 mmcblk0p25
179 26 262144 mmcblk0p26
179 27 24576 mmcblk0p27
179 28 3072 mmcblk0p28
179 29 8 mmcblk0p29
179 30 32768 mmcblk0p30
179 31 512 mmcblk0p31
259 0 512 mmcblk0p32
259 1 8 mmcblk0p33
259 2 16384 mmcblk0p34
259 3 11247616 mmcblk0p35
259 4 4079 mmcblk0p36
254 0 5229 dm-0
254 1 22900 dm-1
lrwxrwxrwx root root 1970-01-13 12:13 DDR -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-13 12:13 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-13 12:13 bnr -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-13 12:13 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-13 12:13 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-13 12:13 drm -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-13 12:13 eksst -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-13 12:13 encrypt -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-13 12:13 factory -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-13 12:13 fota -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-13 12:13 fsg -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-13 12:13 grow -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-13 12:13 m9kefs1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-13 12:13 m9kefs2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-13 12:13 m9kefs3 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-13 12:13 misc -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-13 12:13 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-13 12:13 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-13 12:13 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-13 12:13 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-13 12:13 persist -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-13 12:13 rct -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-13 12:13 recovery -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-13 12:13 reserved -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-13 12:13 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-13 12:13 rpmbak -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-13 12:13 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-13 12:13 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-13 12:13 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-13 12:13 sns -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-13 12:13 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-13 12:13 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-13 12:13 tombstones -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-13 12:13 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-13 12:13 tzbak -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-13 12:13 userdata -> /dev/block/mmcblk0p35
Right now I have a lot of stuff removed from my rom but I do have a stock backup so later I will revert back and and post partition images.
As for stock recovery.img and stock boot.img, I do not have that so maybe someone else can grab that for us that didn't install TWRP yet(Didn't even think of getting it before I installed it and would be nice to have to go back to stock for warranty exchange)
Also let me know of anything else I can do to help you. Thank You

NICG said:
Right now I have a lot of stuff removed from my rom but I do have a stock backup so later I will revert back and and post partition images.
As for stock recovery.img and stock boot.img, I do not have that so maybe someone else can grab that for us that didn't install TWRP yet(Didn't even think of getting it before I installed it and would be nice to have to go back to stock for warranty exchange)
Also let me know of anything else I can do to help you. Thank You
Click to expand...
Click to collapse
Thanks for posting....
Slightly strange values...
VK810 (LTE):
Code:
BOARD_BOOTIMAGE_PARTITION_SIZE := 25165824 # 24M
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 25165824 # 24M
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 2248146944 # 2114M
BOARD_USERDATAIMAGE_PARTITION_SIZE := 11517558784 #10984
BOARD_FLASH_BLOCK_SIZE := 131072 # (BOARD_KERNEL_PAGESIZE * 64)
V500 (wifi):
Code:
BOARD_BOOTIMAGE_PARTITION_SIZE := 23068672 # 22M
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 23068672 # 22M
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 880803840 # 840M
BOARD_USERDATAIMAGE_PARTITION_SIZE := 6189744128 # 5.9G
BOARD_FLASH_BLOCK_SIZE := 131072 # (BOARD_KERNEL_PAGESIZE * 64)
can you post the output of the below command? Want to verify the BOARD_FLASH_BLOCK_SIZE settings
cat /proc/mtd
EDIT1:
Who wants to be a guinea pig for my first cm-11.0 build? (requires you to have TWRP recovery)
0) Post here saying that you are testing the ROM. If someone else posted, then wait and see what happens
1) Perform a backup in TWRP recovery
2) Did I say to perform a backup?
3) Flash the cm-11 zip file in TWRP recovery. the boot.img is already LOKI patched
<removed>
4) Reboot
See if the device starts up properly.
If it doesn't, then go back to TWRP recovery and restore your backup
Risky? Maybe. If you are afraid, then don't flash it and wait for someone else to do it.....

I tested the download and it seems there is a device name mismatch somewhere:
installing '/extenal_sd/cm-11-20140512-UNOFFICIAL-vk810_loki.zip'
checking for MD5 file...
skipping MD5 check no MD5 file found
This package is for "vk810" devices; this is a "altev"
E: Error executing updater binary in zip
error flashing zip
failed

traccdma said:
I tested the download and it seems there is a device name mismatch somewhere:
installing '/extenal_sd/cm-11-20140512-UNOFFICIAL-vk810_loki.zip'
checking for MD5 file...
skipping MD5 check no MD5 file found
This package is for "vk810" devices; this is a "altev"
E: Error executing updater binary in zip
error flashing zip
failed
Click to expand...
Click to collapse
probably.... vk810 is the device name, altev is the model/board/product name... probably a mismatch somewhere.....
I'll recompile when I get home
(v500 = awifi = wifi only version, v510 = palman = GPE version)

paperWastage said:
probably.... vk810 is the device name, altev is the model/board/product name... probably a mismatch somewhere.....
I'll recompile when I get home
(v500 = awifi = wifi only version, v510 = palman = GPE version)
Click to expand...
Click to collapse
i think we should stick with v500/v510/vk810 convention.....
http://forum.xda-developers.com/showpost.php?p=48103469&postcount=22
from this, it looks like the recovery image needs to be fixed...
http://forum.xda-developers.com/showpost.php?p=48331517&postcount=10
for now, I've manually edited the META-INF/com/google/android/updater-script to include "altev" as part of the check
0) Post here saying that you are testing the ROM. If someone else posted, then wait and see what happens
1) Perform a backup in TWRP recovery
2) Did I say to perform a backup?
3) Flash the cm-11 zip file in TWRP recovery. the boot.img will be LOKI-patched during the flash (which means don't use my previous upload where I pre-patched the boot.img)
http://d-h.st/tAq
4) Reboot
See if the device starts up properly.
If it doesn't, then go back to TWRP recovery and restore your backup
Risky? Maybe. If you are afraid, then don't flash it and wait for someone else to do it.....

with cm-11-20140513-unofficial-vk810.zip:
set_metadata_recursive: some changes failed
E: error executing updater binary in zip
error flashing zip
updating partition details...
tried booting it anyway and it brings up LG logo once, powers off/back on, and boots up to recovery (TWRP) on its own

traccdma said:
with cm-11-20140513-unofficial-vk810.zip:
set_metadata_recursive: some changes failed
E: error executing updater binary in zip
error flashing zip
updating partition details...
tried booting it anyway and it brings up LG logo once, powers off/back on, and boots up to recovery (TWRP) on its own
Click to expand...
Click to collapse
http://www.xda-developers.com/android/how-to-fix-a-broken-rom-flash-in-certain-kitkat-roms/
hmm, not sure why TWRP is complaining. need to investigate tomorrow. if the update_script failed, then the boot.img wasn't patched, so the new boot image won't boot at all.
were you able to restore from nandroid backup?
you also try replacing the update-binary in the ROM with this
http://forum.xda-developers.com/showthread.php?t=2532300

that got much further and even booted into CyanogenMod 11 with the VZW Gpad V810!!
After unzipping your file, overwriting the update-binary file in meta-inf\com\google\android with the file from the thread you posted, it said successful. Rebooted once while it said Android is updating app xxx of xxx, then Welcome to CyanogenMod
Seems to be missing drivers though. First boot seemed stable except it didn't recognize Verizon mobile data (or SIM card). I was in there at least 10 minutes. In settings, I used the slider to try and turn on wifi, but it never turned blue and a few seconds later it reverted back off. I slid bluetooth on, and it did the same thing and went into a boot loop. It gets to the android desktop for about 5 seconds then reboots. I wiped cache and dalvik cache and it got no further.

traccdma said:
with cm-11-20140513-unofficial-vk810.zip:
set_metadata_recursive: some changes failed
E: error executing updater binary in zip
error flashing zip
updating partition details...
tried booting it anyway and it brings up LG logo once, powers off/back on, and boots up to recovery (TWRP) on its own
Click to expand...
Click to collapse
whenever that happens get a recovery log, They are very helpful

traccdma said:
that got much further and even booted into CyanogenMod 11 with the VZW Gpad V810!!
After unzipping your file, overwriting the update-binary file in meta-inf\com\google\android with the file from the thread you posted, it said successful. Rebooted once while it said Android is updating app xxx of xxx, then Welcome to CyanogenMod
Seems to be missing drivers though. First boot seemed stable except it didn't recognize Verizon mobile data (or SIM card). I was in there at least 10 minutes. In settings, I used the slider to try and turn on wifi, but it never turned blue and a few seconds later it reverted back off. I slid bluetooth on, and it did the same thing and went into a boot loop. It gets to the android desktop for about 5 seconds then reboots. I wiped cache and dalvik cache and it got no further.
Click to expand...
Click to collapse
good to hear...
need two things:
system dump of stock ROM.
The proprietary libs I'm using right now is from v500 which probably doesn't have the radio libs. maybe wifi/bt driver is different too
logs
As Drgravy said, logs are helpful. Recovery log, /proc/last_kmsg from kernel boot, ...

Sorry been a little busy but here you go.
Stock Rooted System IMG
https://www.dropbox.com/s/rpxmbp1lgb5a4k9/system.img

[Q] LG F70 D315 From tracfone No download mode

I achive for now:
!!!! Restore from any softbrick (any partition ful corrupted emmc) almost infalible!!! i have soft bricked bootloaders gpt, more than 10 times and resurrected again
A clowermod recovery
Semi flashed with f70 d315 stock?
I´m working when i can i post my results
Root
root is easy just use Towelroot
Clowermod Recovery
Tanks to OpenBump
put in sdcard and
Code:
adb shell
su
dd if=/sdcard/cwmrecovery_bumped.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
reboot recovery
Clower mod for L31L
Boot loader
The bootloader has some protection in aboot
if you disasemble with idapro is idem to the f70 d315, g2 mini and family the block that you have to patch
but this file is protected if you pach a single bit it bring you a raw disk when conect the phone (Q9006 mode)

-----OLD POST--------
I have a LG F70 D315 from tracfone whit this company the models change to LGL31L but I verify and many references says that is F70 an no other
I wan to flash whit a lesser restrictive firmware that not belong to this company to later flash a custom room, volume down while conet to get DOWNLOAD MODE are removed from this phone
I have KDZ, extracted to , i rooted sucefully the phone, got recovery mode
but the only way I find to flash is via download and this mode dosent apear
I think is rplace with a batery charging becouse that is what I see whit
Code:
adb reboot-bootloader
and others
and when try key conbinations to power up to download mode it bring me to the batery loader again
In the original extracted f70 d315 kdz the download mode is in the laf partition
I have it have a diferent size of the original fone laf
there is a way to push this to get download mode?
Sorry for my bad English and for post in this secction becouse I dont find LG 70 board
thanks
The partition info off the phone is this
Code:
shell># cat /proc/partitions
major minor #blocks name
179 0 7634944 mmcblk0
179 1 65536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 2048 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 32768 mmcblk0p14
179 15 22528 mmcblk0p15
179 16 22528 mmcblk0p16
179 17 22528 mmcblk0p17
179 18 3072 mmcblk0p18
179 19 512 mmcblk0p19
179 20 512 mmcblk0p20
179 21 512 mmcblk0p21
179 22 512 mmcblk0p22
179 23 512 mmcblk0p23
179 24 8192 mmcblk0p24
179 25 8192 mmcblk0p25
179 26 20480 mmcblk0p26
179 27 32768 mmcblk0p27
179 28 1024 mmcblk0p28
179 29 32768 mmcblk0p29
179 30 512 mmcblk0p30
179 31 2097152 mmcblk0p31
259 0 921600 mmcblk0p32
259 1 4220416 mmcblk0p33
259 2 40943 mmcblk0p34
179 32 512 mmcblk0rpmb
shell># ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-01-02 20:09 DDR -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 20:09 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 20:09 abootb -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 20:09 boot -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 20:09 cache -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-02 20:09 drm -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 20:09 eksst -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-02 20:09 encrypt -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 20:09 factory -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-02 20:09 fota -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-02 20:09 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 20:09 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 20:09 grow -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-02 20:09 laf -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 20:09 misc -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 20:09 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 20:09 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 20:09 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 20:09 mpt -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-02 20:09 pad -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 20:09 persist -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 20:09 rct -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 20:09 recovery -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 20:09 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 20:09 rpmb -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 20:09 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 20:09 sbl1b -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-02 20:09 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 20:09 sns -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-02 20:09 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 20:09 system -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-02 20:09 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 20:09 tzb -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 20:09 userdata -> /dev/block/mmcblk0p33
shell># parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Model: MMC 8WMB3R (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 8389kB 75.5MB 67.1MB fat16 modem
2 75.5MB 76.5MB 1049kB sbl1
3 76.5MB 77.1MB 524kB rpm
4 77.1MB 77.6MB 524kB tz
5 77.6MB 78.1MB 524kB sdi
6 78.1MB 80.2MB 2097kB aboot
7 80.2MB 80.7MB 524kB rpmb
8 80.7MB 81.3MB 524kB tzb
9 81.3MB 83.4MB 2097kB abootb
10 83.4MB 85.5MB 2097kB pad
11 85.5MB 88.6MB 3146kB modemst1
12 88.6MB 91.8MB 3146kB modemst2
13 91.8MB 109MB 16.8MB misc
14 109MB 143MB 33.6MB ext4 persist
15 143MB 166MB 23.1MB laf
16 168MB 191MB 23.1MB boot
17 191MB 214MB 23.1MB recovery
18 214MB 217MB 3146kB fsg
19 218MB 219MB 524kB fsc
20 219MB 219MB 524kB ssd
21 226MB 227MB 524kB DDR
22 235MB 235MB 524kB encrypt
23 235MB 236MB 524kB rct
24 243MB 252MB 8389kB ext4 drm
25 252MB 260MB 8389kB ext4 sns
26 260MB 281MB 21.0MB factory
27 281MB 315MB 33.6MB fota
28 319MB 320MB 1049kB sbl1b
29 320MB 353MB 33.6MB ext4 mpt
30 353MB 354MB 524kB eksst
31 361MB 2508MB 2147MB ext4 system
32 2508MB 3452MB 944MB ext4 cache
33 3452MB 7774MB 4322MB ext4 userdata
34 7776MB 7818MB 41.9MB grow
(parted) q
I copy laf to recovery partition with dd and bring me to Download Mode when I enter to recovery but i dont find a way to flash yet

unlock boot loader
I maybe try to flash via custom recovery but i have to unlock bootloader
This method
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
says change bites in this string 20 00 EB 00 00 50 E3 E0 FF FF 0A
The stock firmware have this string in aboot.img 20 00 eb 00 00 50 e3 e0 ff ff 0a 60 00 9f e5
but the aboot of my phone the string change to
20 00 eb 00 00 50 e3 08 00 84 e5 07 00 00 0a
and is the string only string that match to 20 00 eb 00 00 50 e3
20 00 eb 00 00 50 e3 e0 ff ff 0a 60 00 9f ->stock firm
20 00 eb 00 00 50 e3 08 00 84 e5 07 00 00 0a ->current room
If i change this with this conditions the phone may not boot anymore?

I am trying to get the download mode for the L31l and am wondering how you copied the files to the recovery partition.
I got the kdz file extracted it and extracted the dz files and have the binfiles.
I have also created an image file by combining the bin files but don't think this will do anything.
I am planning to use the method from:
htt p://ww w.lg-phone s.org/how-to-flas h-unbrick-lg-f70-bac k-to-stoc k.htm l
(Remove spaces)
To flash the kdz file of I can get download mode to work.
Thanks

Download mode
To get download mode:
1-To get download mode I rooted easy with towelroot
2-With dd made a backup of all partitions (nandroid backup)
3-Flash laf partition to recovery (change msm_sdcc I dont know exactly the name because I don´t have phone here and my tools):
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/dev/block/platform/msm_sdcc.1/by-name/recovery
4-Do
Code:
adb shell
reboot recovery
and you will enter to download instead of recovery
but for me was unseful because the firmware is for Lgf70 and is a lgl31l
and any flash sofware detected
I do the last I posted and dead:silly: to usb qualcom mode that see as raw disk
http://forum.xda-developers.com/showthread.php?t=2582142
this mode is easy to recover but intead I fail and dd other partition sbl
and have a mode that is very very triky and dont find how to solve
cause nothing worme form my phone
This a mode who I'am now QDLoader 9008
{
"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"
}
http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830/page17#post58460319

I also got into download but couldn't get it to load the F70 rom.
Anybody have any ideas?

Thanks for your work. Have you been able to load the portion of the f70 rom that contains the hidden menu for unlock?
I know there is some information about adding it back to the verizon g2 available.
Thanks again

Any more info to share?
You mentioned a f70 rom. Any more luck getting it to work?
Thanks

f70 rom
1god 1Bad news I flash the f70 but the unlock menu says that not more atemps left (usseless)
Flash f70 room bricks me the phone many times with a backup I can bring back ever I want but may sometimes have to open the phone and make a tespoint
Frist backup all your phone whit dd
I backup all single partition
dd if=/dev/block/platform/msm_sdcc.1/by-name/xxx of=/sdcard/backup
and after backup the GPT partition table
you beter dd all then phone mmc instead
of course copy to a PC or any external
Extract boot.img and system.img of F70 room kdztools etc...
For f70 room you have to bumped boot.img of F70
frist have to repack whit bootimg.exe http://en.miui.com/thread-27657-1-1.html
descompress and compress
and after used open bump
http://forum.xda-developers.com/lg-g2/orig-development/tool-bump-sign-boot-images-t2950595
Better put frist system.img to sdcard
1)whit dd flash the recovery to the boot img after that youre phone start always in recovery
because no recovery convination
2)flash boot.img to recovery
3) Now when you turn your phone start in the recovery mount /sdcard /system...
conect in and this recovery have adb
flash whit dd system partition
don't exit recovery
4)wipe cache factory reset
5) in avanced revot recovery will boot system (anytimes you power on have to do this)
The gide is not easy and safe i can made a better but flash f70 dosen't worst
yes you have more usb modes enabled, wifi theter and hotspot
but no unock , even any unlock boxes that have f70 direct unlock
all becuse the nvram is not accesible????

i brick my d315 with update v10e
hello,
I have got a LG D315 with root and TWRP 2.8.0.0.
today i see there is a update v10e for my phone.
so i accept the install. the update download , pass de verify ( no problem cause root) and reboot.
but the phone boot on TWRP only and the update no run . i can't reboot normaly , I'm blocked on TWRP ( reboot on system, bootloader or recovery >> return to TWRP) , the phone refuse to upgrade or reboot normaly ?
any ideas ???
please help !!
ps : sorry I'm french and i write bad english

willowlefou said:
hello,
I have got a LG D315 with root and TWRP 2.8.0.0.
today i see there is a update v10e for my phone.
so i accept the install. the update download , pass de verify ( no problem cause root) and reboot.
but the phone boot on TWRP only and the update no run . i can't reboot normaly , I'm blocked on TWRP ( reboot on system, bootloader or recovery >> return to TWRP) , the phone refuse to upgrade or reboot normaly ?
any ideas ???
please help !!
ps : sorry I'm french and i write bad english
Click to expand...
Click to collapse
I resolved my problem ,
I have backup the LAF files so in TWRP I 've restore the laf
Code:
dd if=/sdcard/backup/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
after i reboot in download mode ( power off / button up + plug usb cable )
the LGFlashTool2014 detect my phone i Ican retore the D31510e_00.kdz file with this tools.
my data aren't destroy.
thanks!

Hi guys! My lg f70 phone broken after use flash tool, (Qdloader 9008), i search fixing on internet, and finding them QFIl and qpst.. My phone cpu msm8926, need emmc firehose 8926 file for flashing emmc and fastboot restore file, somebody help? Sorry my bad english!

[RESOLVED] fastboot not recognizing phone in bootloader mode

So let me tell you the dumb things I did.
1. I thought I saw an update for TWRP in Tapatalk, so I downloaded it and flashed it in TWRP. Turned out it was for the OnePlus One... Tapatalk didn't sync with my XDA subscribed threads correctly...
2. Rebooted into recovery, and we all know what happened here.
3. No problem, I can use fastboot to flash recovery. Booted into bootloader, and did this:
{
"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"
}
Basically, it saw the device, I tried to flash the TWRP image file, but it got stuck waiting for the phone. That was the last time it ever saw it.
4. Rebooted into Android just fine. Everything work exactly the way they should.
5. I figured the only way I can flash recovery now is by using dd over ADB shell.
6. I grabbed the last log written by the recovery, and found the following information by doing "cat /cache/recovery/last_log":
Code:
/recovery | /dev/block/sde14 | Size: 64MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: [B]/dev/block/sde14[/B]
Display_Name: Recovery
Storage_Name: recovery
Backup_Path: /recovery
Backup_Name: recovery
Backup_Display_Name: Recovery
Storage_Path: /recovery
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
[B]<truncated>[/B]
[IMAGE FLASH STARTED]
Image to flash: '/sdcard/Download/TWRP+3.0.3-2-TugaPower.img'
Calculating restore details...
I:Image filename is: TWRP+3.0.3-2-TugaPower.img
I:Reading '/sdcard/Download/TWRP+3.0.3-2-TugaPower.img', writing '[B]/dev/block/sde14[/B]'
[IMAGE FLASH COMPLETED]
I:Set page: 'action_complete'
I:operation_end - status=0
I:Set page: 'clear_vars'
I:Set page: 'flashimage_confirm'
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'reboot'
I:Set page: 'rebootcheck'
I:Copying file /cache/recovery/log to /cache/recovery/last_log
Rebooting...
I:InfoManager saving '/data/media/0/TWRP/.twrps'
I:Saved settings file values
So the recovery partition is /dev/block/sde14.
7. I first made a backup of the partition just to make sure.
Code:
[email protected]_ii:/ # dd if=/dev/block/sde14 of=/sdcard/badrec.img
dd if=/dev/block/sde14 of=/sdcard/badrec.img
131072+0 records in
131072+0 records out
67108864 bytes transferred in 1.281 secs (52387871 bytes/sec)
8. Then I "flashed" the right TWRP image file.
Code:
[email protected]_ii:/ # dd if=/sdcard/TWRP.img of=/dev/block/sde14
dd if=/sdcard/TWRP.img of=/dev/block/sde14
35824+0 records in
35824+0 records out
18341888 bytes transferred in 1.552 secs (11818226 bytes/sec)
9. I rebooted into recovery, and it worked.
In conclusion, Android and recovery themselves work fine now. I'm just worried because fastboot won't see my device in bootloader. That's a fail-safe that I can't not have. I'm not flashing anything else until I get to the bottom of it.
EDIT: I noticed in the backup section of TWRP, fastboot is listed as having 0 MB. Did it get wiped? I'm not sure how to get it back.
Within Android:
Within TWRP:
Code:
~ # [6nls -al /dev/block/platform/soc
ls -al /dev/block/platform/soc
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 4 root root 80 Mar 16 1970 .
drwxr-xr-x 3 root root 60 Mar 16 1970 ..
drwxr-xr-x 4 root root 1100 Mar 16 1970 624000.ufshc
drwxr-xr-x 3 root root 100 Mar 16 1970 74a4900.sdhci
~ # [6nls -al /dev/block/platform/soc/624000.ufshc/by-name
ls -al /dev/block/platform/soc/624000.ufshc/by-name
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 940 Mar 16 1970 .
drwxr-xr-x 4 root root 1100 Mar 16 1970 ..
lrwxrwxrwx 1 root root 16 Mar 16 1970aboot -> /dev/block/sde11
lrwxrwxrwx 1 root root 16 Mar 16 1970 apdp -> /dev/block/sde21
lrwxrwxrwx 1 root root 16 Mar 16 1970 bluetooth -> /dev/block/sde16
lrwxrwxrwx 1 root root 16 Mar 16 1970 boot -> /dev/block/sde12
lrwxrwxrwx 1 root root 15 Mar 16 1970 cache -> /dev/block/sda2
lrwxrwxrwx 1 root root 15 Mar 16 1970 cdt -> /dev/block/sdd2
lrwxrwxrwx 1 root root 16 Mar 16 1970 cmnlib -> /dev/block/sde19
lrwxrwxrwx 1 root root 16 Mar 16 1970 cmnlib64 -> /dev/block/sde20
lrwxrwxrwx 1 root root 15 Mar 16 1970 cryptkey -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 Mar 16 1970 ddr -> /dev/block/sdd3
lrwxrwxrwx 1 root root 15 Mar 16 1970 devcfg -> /dev/block/sda5
lrwxrwxrwx 1 root root 16 Mar 16 1970 devinfo -> /dev/block/sde15
lrwxrwxrwx 1 root root 15 Mar 16 1970 dip -> /dev/block/sde9
lrwxrwxrwx 1 root root 16 Mar 16 1970 dpo -> /dev/block/sde23
lrwxrwxrwx 1 root root 15 Mar 16 1970 dsp -> /dev/block/sde8
lrwxrwxrwx 1 root root 16 Mar 16 1970 echarge -> /dev/block/sde25
lrwxrwxrwx 1 root root 15 Mar 16 1970 [B]fbop -> /dev/block/sda6[/B]
lrwxrwxrwx 1 root root 15 Mar 16 1970 frp -> /dev/block/sda7
lrwxrwxrwx 1 root root 15 Mar 16 1970 fsc -> /dev/block/sdf3
lrwxrwxrwx 1 root root 15 Mar 16 1970 fsg -> /dev/block/sde4
lrwxrwxrwx 1 root root 15 Mar 16 1970 hyp -> /dev/block/sde3
lrwxrwxrwx 1 root root 16 Mar 16 1970 keymaster -> /dev/block/sde18
lrwxrwxrwx 1 root root 15 Mar 16 1970 keystore -> /dev/block/sda4
lrwxrwxrwx 1 root root 16 Mar 16 1970 lksecapp -> /dev/block/sde17
lrwxrwxrwx 1 root root 16 Mar 16 1970 mdtp -> /dev/block/sde10
lrwxrwxrwx 1 root root 15 Mar 16 1970 misc -> /dev/block/sda3
lrwxrwxrwx 1 root root 15 Mar 16 1970 modem -> /dev/block/sde7
lrwxrwxrwx 1 root root 15 Mar 16 1970 modemst1 -> /dev/block/sdf1
lrwxrwxrwx 1 root root 15 Mar 16 1970 modemst2 -> /dev/block/sdf2
lrwxrwxrwx 1 root root 16 Mar 16 1970 msadp -> /dev/block/sde22
lrwxrwxrwx 1 root root 15 Mar 16 1970 persist -> /dev/block/sdf5
lrwxrwxrwx 1 root root 15 Mar 16 1970 pmic -> /dev/block/sde6
lrwxrwxrwx 1 root root 16 Mar 16 1970 recovery -> /dev/block/sde14
lrwxrwxrwx 1 root root 15 Mar 16 1970 reserve -> /dev/block/sdd1
lrwxrwxrwx 1 root root 15 Mar 16 1970 rpm -> /dev/block/sde1
lrwxrwxrwx 1 root root 15 Mar 16 1970 sec -> /dev/block/sde5
lrwxrwxrwx 1 root root 16 Mar 16 1970 splash -> /dev/block/sde24
lrwxrwxrwx 1 root root 15 Mar 16 1970 ssd -> /dev/block/sda1
lrwxrwxrwx 1 root root 16 Mar 16 1970 sti -> /dev/block/sde26
lrwxrwxrwx 1 root root 16 Mar 16 1970 system -> /dev/block/sde13
lrwxrwxrwx 1 root root 15 Mar 16 1970 tz -> /dev/block/sde2
lrwxrwxrwx 1 root root 15 Mar 16 1970 userdata -> /dev/block/sda9
lrwxrwxrwx 1 root root 15 Mar 16 1970 xbl -> /dev/block/sdb1
lrwxrwxrwx 1 root root 15 Mar 16 1970 xblbak -> /dev/block/sdc1
lrwxrwxrwx 1 root root 15 Mar 16 1970 ztecfg -> /dev/block/sdf4
fastboot is now a partition to pick from when I choose an image to flash. Huh? Is that the fbop (/dev/block/sda6) partition? When I run cat on it I still see data on it.
EDIT 2: I see this in the recovery logs:
Code:
/fastboot | /dev/block/sda6 | Size: 0MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/sda6
Display_Name: fastboot
Storage_Name: fastboot
Backup_Path: /fastboot
Backup_Name: fastboot
Backup_Display_Name: fastboot
Storage_Path: /fastboot
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
Using dd to grab it gives me a 128 KB image. Seems normal compared to the ones uploaded here. It's mostly empty data, though, it seems.
==========FIXED==========
You're not going to believe this. I think Windows decided to update the ADB device driver right after I plugged it in (refer to the screenshot above where it just stopped working for no reason).
I went into Device Manager and saw this:
Seems normal, right? Well, if I try to update it using Windows' list of known devices, I see these:
I checked afterward; the one that's currently installed is the top one. So, I chose the second one (the supposedly outdated one).
And now we are presented with result.
I hate you, Windows.

Try a different USB port. I had issues with my m8 randomly not picking up my device in fastboot but working from adb on the same port

silverxbv2 said:
Try a different USB port. I had issues with my m8 randomly not picking up my device in fastboot but working from adb on the same port
Click to expand...
Click to collapse
I actually think something happened to my fastboot partition/binary/whatever. Check the bottom of OP.

What model are you using? And what sw version?

I fixed it! See OP for details.

I'm glad you got it working

Good troubleshooting. Glad you got whole again. ..... I also hate Windows
Sent from my Nexus 6 using XDA-Developers mobile app

My believe is not windows problem , is the new software installed on the device, when is detected and have usb debugging enable automatically install or update drivers.
So is part of ZTE doing. But good find

I had almost the same problem, device manager showed only !Android Device in fastboot mode, however, worked nicely in adb. I had to install manually the Google usb driver from here https://developer.android.com/studio/run/win-usb.html#top

<3<3<3<3<3
One thanks button is not enough. You saved me from many hours of failing!!!

How can I Create a byte-for-byte image of my Internal Memory (from Recovery or ADB)

I am looking for a way to create a perfect, byte for byte, image of my internal memory so that I can recover data from the image in a safer way and from a copy where I cant destroy the original. I am really just looking to recover files I had under the /sdcard (USERDATA mount) however, since my partitions are messed up, I want to broaden the scope and capture everything. Can anyone point me in the right direction?
Help is greatly appreciated.

re: byte for byte
waypoint.delta said:
I am looking for a way to create a perfect, byte for byte, image of my internal memory so that I can recover data from the image in a safer way and from a copy where I cant destroy the original. I am really just looking to recover files I had under the /sdcard (USERDATA mount) however, since my partitions are messed up, I want to broaden the scope and capture everything. Can anyone point me in the right direction?
Help is greatly appreciated.
Click to expand...
Click to collapse
You would need to develop or find a developer who knows
how to create a very specific & special application to do that.
At the present time there is no applications that can do it.
You would be way better off to simply copy whatever good
files are in your internal memory to your computer because
any other way would result in many unusable files since
you said that the partition is all messed up.
By creating a byte for byte image of your internal memory
you would simply end up with a lot of unusable files since
your partitions are messed up.
Good luck, have a great day!

Thanks for the response Mr Junky. I can tell you I am fairly determined, short of hopping the NSA fence and demanding justice. Anyways, The partitions only matter so much since they do not define the files, the 1's and 0's do. There's tons of recovery software already, so no need to go that far, just need to get the data off my phone so it can be analysed. Square one is I grabbing a quality snapshot of the Internal Memory and putting it on my PC. At that point I can rebuild my phone without concern.
Misterjunky said:
. . .
Click to expand...
Click to collapse

Does anyone know if the partition/sector offsets ever change, or are they static? I ask because I ran "Repair or Change File System" on /data which shares a mount with /sdcard (i think). If they are static, it wont matter that the partition table was rebuilt, the lost data should still reside there. I can simply use DD to capture /dev/block/sda18 to a file. As a side note, I'm really glad i had busybox installed.
Code:
~ # ←[6n[COLOR="DarkGreen"][B]busybox fdisk -l /dev/block/sda[/B][/COLOR]
Note: sector size is 4096 (not 512)
Found valid GPT with protective MBR; using GPT
Disk /dev/block/sda: 62464000 sectors, 2336M
Logical sector size: 4096
Disk identifier (GUID): 52444e41-494f-2044-4d4d-43204449534b
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 7807994
Number Start (sector) End (sector) Size Code Name
1 1024 2047 4096K 0700 BOTA0
2 2048 3071 4096K 0700 BOTA1
3 3072 8191 20.0M 0700 EFS
4 8192 10239 8192K 0700 PARAM
5 10240 20479 40.0M 0700 BOOT
6 20480 32255 46.0M 0700 RECOVERY
7 32256 34303 8192K 0700 OTA
8 34304 45055 42.0M 0700 RADIO
9 45056 45311 1024K 0700 TOMBSTONES
10 45312 45567 1024K 0700 DNT
11 45568 45759 768K 0700 PERSISTENT
12 45760 45823 256K 0700 STEADY
13 45824 48127 9216K 0700 PERSDATA
14 48128 1148927 4300M 0700 SYSTEM
15 1148928 1200127 200M 0700 CACHE
16 1200128 1238527 150M 0700 HIDDEN
17 1238528 1239807 5120K 0700 CP_DEBUG
[COLOR="Red"][B] 18 1239808 7806719 25.0G 0700 USERDATA[/B][/COLOR]
~ # ←[6n
C:\adb>
C:\adb>adb shell
/dev/block/platform/155a0000.ufs/by-name # ?[6n[COLOR="darkgreen"][B]ls -l[/B][/COLOR]
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
lrwxrwxrwx 1 root root 15 Jan 2 12:45 BOOT -> /dev/block/sda5
lrwxrwxrwx 1 root root 15 Jan 2 12:45 BOTA0 -> /dev/block/sda1
lrwxrwxrwx 1 root root 15 Jan 2 12:45 BOTA1 -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 Jan 2 12:45 CACHE -> /dev/block/sda15
lrwxrwxrwx 1 root root 15 Jan 2 12:45 CPEFS -> /dev/block/sdd1
lrwxrwxrwx 1 root root 16 Jan 2 12:45 CP_DEBUG -> /dev/block/sda17
lrwxrwxrwx 1 root root 16 Jan 2 12:45 DNT -> /dev/block/sda10
lrwxrwxrwx 1 root root 15 Jan 2 12:45 EFS -> /dev/block/sda3
lrwxrwxrwx 1 root root 16 Jan 2 12:45 HIDDEN -> /dev/block/sda16
lrwxrwxrwx 1 root root 15 Jan 2 12:45 OTA -> /dev/block/sda7
lrwxrwxrwx 1 root root 15 Jan 2 12:45 PARAM -> /dev/block/sda4
lrwxrwxrwx 1 root root 16 Jan 2 12:45 PERSDATA -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 Jan 2 12:45 PERSISTENT -> /dev/block/sda11
lrwxrwxrwx 1 root root 15 Jan 2 12:45 RADIO -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 Jan 2 12:45 RECOVERY -> /dev/block/sda6
lrwxrwxrwx 1 root root 16 Jan 2 12:45 STEADY -> /dev/block/sda12
lrwxrwxrwx 1 root root 16 Jan 2 12:45 SYSTEM -> /dev/block/sda14
lrwxrwxrwx 1 root root 15 Jan 2 12:45 TOMBSTONES -> /dev/block/sda9
[COLOR="Red"][B]lrwxrwxrwx 1 root root 16 Jan 2 12:45 USERDATA -> /dev/block/sda18[/B][/COLOR]
/dev/block/platform/155a0000.ufs/by-name # ?[6n

I created the dd image of the USERDATA partition and saved it to the external SD card using the following command
Code:
dd if=/dev/block/sda18 of=/external_sd/dev/block/sda18.dd bs=4096
I then ran it against photorec which only returned 2 elf files. I will run it against testdisk as well, but I'm thinking either the data is gone or I did not use DD correctly.

In TWRP, when you go to "Wipe" -> "Advanced Wipe" you see a list of partitions, among them are "Data" and "Internal Storage". I wiped the "Data" partition as I thought "Internal Storage" would be untouched (since it was listed seperatly). Nope. Apparently they map to the exact same partition
Code:
/dev/block/sda18 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/sda18 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
I used "Change File System" on "Data" in order to make it usable again, I must have destroyed all the data I was trying to recover. Had I build the image before I fixed the data partition, I would probably have recovered most everything.
Thanks go out to Samsung for enabling auto update by default and for thoroughly testing the update which blew up my phone! Great job guys : )

waypoint.delta said:
I am looking for a way to create a perfect, byte for byte, image of my internal memory so that I can recover data from the image in a safer way and from a copy where I cant destroy the original. I am really just looking to recover files I had under the /sdcard (USERDATA mount) however, since my partitions are messed up, I want to broaden the scope and capture everything. Can anyone point me in the right direction?
Help is greatly appreciated.
Click to expand...
Click to collapse
You need to use photorec directly on the block device, not a copy. Copies don't copy detached inodes, even with dd.
Sent from my SM-G935T using Tapatalk

Everything I've read online negates that statement. however, I've yet to recover anything from the images I've copied, but I believe it may be due to hardware error. As a test, I put an photo on my /system mount and deleted the image. then I cloned the system block device and attempted recovery using photorec. this test failed to recover the file. so either DD is not copying the raw bytes or I am doing something incorrectly. I will try the same test using scalpel and also on another android phone.
toastido said:
You need to use photorec directly on the block device, not a copy. Copies don't copy detached inodes, even with dd.
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse

Onn 11.6 Pro 100043279 with keyboard, no wifi after installing magisk (solved + minor tutorial)

Hi, I bought a 11.6 inch onn Tablet Pro yesterday, running android 11, model hardware 100043279. I followed this guide onn tablet magisk guide and I used this firmware link to thread with firmware. I'm running Linux as my host machine and using adb. I'm not sure if I made a huge mistake because this is my first time installing Magisk, it's possible that I messed up by not ensuring wifi was connected before flashing the image, or that I incorrectly did so.
I was able to install Magisk and am able to get root permissions. The main issue is that wifi is no longer working. I try to set it on in the toolbar and it just turns off automatically and greys out. I tried to set it using adb with ``` adb shell su -c 'svc enable wifi' ``` and
```
adb shell am start -a android.intent.action.MAIN -n com.android.settings/.wifi.WifiSettings
adb shell input keyevent 20 & adb shell input keyevent 23
```
and no luck. Wifi refuses to start. I tried to reset the device a few times already and re-flash the device using the boot.img that came with the mega.nz download. I also tried resetting it in various ways. No luck. I think I may have made a mistake by not logging in fully and setting everything up before flashing the device (I had set up google and wifi the first time, but then turned on fastboot and didnt set up everything a second time) so maybe its stuck in some kind of "setup" phase. But thats just my un-educated guess, I'm a complete noob at the moment.
Any advice or anything that I could try? Maybe I'm doing something blatantly incorrect that you could point out? It's kind of tough jumping into the rooting scene when everyone knows what everything means so there are no posts that bother to explain it, and every post and youtube video is entirely different in a thousand ways.

meili_33 said:
Any advice or anything that I could try?
Click to expand...
Click to collapse
I believe the problem is that the WiFi driver is outside the kernel.
So if you replace the working kernel with a different one (where all the kallsyms are different) everything will work except external modules.
When you Magisk'ed I presume that you took the boot image from somewhere and not directly off your device?
If you had taken it off your device there would have been no discrepancy.
Solutions (pick one):
Find the original boot image of your device and Magisk that
Find the WiFi driver that is compatible with your updated kernel

Renate said:
I believe the problem is that the WiFi driver is outside the kernel.
So if you replace the working kernel with a different one (where all the kallsyms are different) everything will work except external modules.
When you Magisk'ed I presume that you took the boot image from somewhere and not directly off your device?
If you had taken it off your device there would have been no discrepancy.
Solutions (pick one):
Find the original boot image of your device and Magisk that
Find the WiFi driver that is compatible with your updated kernel
Click to expand...
Click to collapse
Thank you, I'm wondering where I would be able to get the original boot image since I already overwrote mine? Is it potentially still there?

I'm replying to my own thread for the sake of being a completion-ist. I found the firmware for the 11.6 Pro 100043279 from a secondary source and it looks identical to what is linked in my original comment (I am not 100% sure admittedly). It was under a Youtube video with the title of the device in the name. I cannot say that this is safe otherwise I would link it. Yall can message me if you really really need to and I can point you there or provide you with my copy.
I downloaded it and went through and flashed every single image (vbmeta, vbmeta_system, vbmeta_vendor, super.img etc... anything I could flash, I did) and the tablet has wifi again. I'm going to try to use magisk on the image and retry the process. I also switched to a better cord and used the older USB port on my PC.
# Side note - the keyboard has to be disconnected for USB debugging to be recognized and should not be connected during the entire process.

And we have a success! Im happy thats my first ever magisk install. I'm going to list some of the resources that helped me and some general help.
Here is the output of
> adb shell ls -l /dev/block/by-name
Code:
total 0
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 boot_a -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 boot_b -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 20 2023-06-23 23:00 boot_para -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 cam_vpu1_a -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 cam_vpu1_b -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 cam_vpu2_a -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 cam_vpu2_b -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 cam_vpu3_a -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 cam_vpu3_b -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 dtbo_a -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 dtbo_b -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 20 2023-06-23 23:00 expdb -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 flashinfo -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 20 2023-06-23 23:00 frp -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 gz_a -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 gz_b -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 lk_a -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 lk_b -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 logo -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 20 2023-06-23 23:00 md_udc -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 2023-06-23 23:00 metadata -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 18 2023-06-23 23:00 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx 1 root root 23 2023-06-23 23:00 mmcblk0boot0 -> /dev/block/mmcblk0boot0
lrwxrwxrwx 1 root root 23 2023-06-23 23:00 mmcblk0boot1 -> /dev/block/mmcblk0boot1
lrwxrwxrwx 1 root root 22 2023-06-23 23:00 mmcblk0rpmb -> /dev/block/mmcblk0rpmb
lrwxrwxrwx 1 root root 20 2023-06-23 23:00 nvcfg -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2023-06-23 23:00 nvdata -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 nvram -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 otp -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 20 2023-06-23 23:00 para -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 persist -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 23 2023-06-23 23:00 preloader_a -> /dev/block/mmcblk0boot0
lrwxrwxrwx 1 root root 23 2023-06-23 23:00 preloader_b -> /dev/block/mmcblk0boot1
lrwxrwxrwx 1 root root 30 2023-06-23 23:00 preloader_emmc_a -> /dev/block/by-name/preloader_a
lrwxrwxrwx 1 root root 30 2023-06-23 23:00 preloader_emmc_b -> /dev/block/by-name/preloader_b
lrwxrwxrwx 1 root root 15 2023-06-23 23:01 preloader_raw_a -> /dev/block/dm-4
lrwxrwxrwx 1 root root 15 2023-06-23 23:01 preloader_raw_b -> /dev/block/dm-5
lrwxrwxrwx 1 root root 30 2023-06-23 23:00 preloader_ufs_a -> /dev/block/by-name/preloader_a
lrwxrwxrwx 1 root root 30 2023-06-23 23:00 preloader_ufs_b -> /dev/block/by-name/preloader_b
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 proinfo -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 20 2023-06-23 23:00 protect1 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 protect2 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 scp_a -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 scp_b -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 sec1 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 seccfg -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 spmfw_a -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 spmfw_b -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 sspm_a -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 sspm_b -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 super -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 tee_a -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 tee_b -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 userdata -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 vbmeta_a -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 vbmeta_b -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 vbmeta_system_a -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 vbmeta_system_b -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 vbmeta_vendor_a -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 vbmeta_vendor_b -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 vendor_boot_a -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 vendor_boot_b -> /dev/block/mmcblk0p44
Installation
The Magic Mask for Android
topjohnwu.github.io
the above link is very helpful in giving clarity as to what images you should be using and how to handle separated vbmeta files. In the case of the 11.6 Pro android 11, the vbmeta files are separate and we are booting from the Ramdisk, so we are flashing "boot" and NOT "boot_recovery" or otherwise.
Hook up the device to the PC, enable the developer mode by going into settings > tablet info (at the bottom) > and tap the firmware 7 times or so. Then enable USB debugging.
On linux you just need to install adb on your PC and run:
adb devices
adb reboot bootloader
flasing unlock
fastboot devices
fastboot flashing unlock
fastboot reboot
Boot your tablet into fastboot mode. With the device powered off, hold the Power and Volume Up buttons for several seconds, until a boot mode menu appears on your tablet display. Use Volume Up to navigate to Fastboot Mode and then press Volume Down to select it.
(Mine was already in fastboot for some reason and I thought the screen was frozen, it was NOT. Its just unresponsive. It looked like a menu but fastboot was already selected and all I had to do was move to the next step which was to boot in and install magisk)
1.) Download Magisk from the github page and use adb to install it with:
adb install /path/to/Magisk.apk
2.) Copy local boot image from the firmware zip archive to the tablet device (explicitly called "boot.img" there are a lot of img files so it could be confusing) with:
adb push /path/to/directory/boot.img /sdcard/download
(the path is the relative path to the boot.img file. it could be in the directory that you are in for example and the full relative path would be ./boot.img on linux and .\boot.img\ on windows. You can also do this without the dot slash but it is important to note that you are specifying the path whether you are in the working directory with the files or not. I did it while inside the firmware directory to make it easy)
3.) Open magisk, hit install, patch image and click on the image you pushed to the device in the previous step. This will produce a patched image.
Then use:
adb pull /storage/emulated/0/Download/magisk_patched-26100_[random-string].img .
(the DOT is the current directory) this will copy the image to where your current dir.
Finally run these commands:
adb reboot bootloader
fastboot flash boot ./magisk_patched-26100_peoUE.img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
NOTE: that this is for the 11.6 Pro with the keyboard. The above github link will help you determine these last two commands. It IS important so please read it. Some devices use boot_recovery or something else and some devices use a different command to flash the vbmeta files based on your configuration. You can use the "adb shell ls -l /dev/block/by-name" command to see if you have separate vbmeta files or not. The above link has more info on this process but this is the general idea.
Note that they keyboard must NOT be connected to the device otherwise it wont be recognized by the PC for USB debugging. To fix the broken wifi, I downloaded the firmware and flashed ALL images listed in /dev/block/by-name and restarted the process. I hope this helps clarify some things for someone out there messing around with niche hardware. Good luck and feel free to ask me questions. I had to learn the hard way, Idk a lot about the topic but I can help guide a little bit. Thanks.