v20b - FACTORY install - original x-loader and u-boot - needed by all - LG Optimus L9 P760, P765, P768, P769

if you had a v20b FACTORY install, can you please respond to this thread. we need your x-loader and u-loader to unlock specific phones that meet specific conditions ( http://forum.xda-developers.com/showthread.php?t=2461483 ). you can get them on your internal OR external sdcard by being rooted with busybox installed, and typing:
Code:
# internal sdcard
adb shell su -c busybox dd if=/dev/block/mmcblk0p1 of=/sdcard/p1.bin
adb shell su -c busybox dd if=/dev/block/mmcblk0p2 of=/sdcard/p2.bin
# OR external
adb shell su -c busybox dd if=/dev/block/mmcblk0p1 of=/sdcard/external_sd/p1.bin
adb shell su -c busybox dd if=/dev/block/mmcblk0p2 of=/sdcard/external_sd/p2.bin
they are very small files and won't take you but a second to upload. it HAS to be FACTORY, other wise, you will NOT truly have the v20b's x-loader and u-boot. you can be rooted and install busybox (actually, you will HAvE to, if you want to copy those files), and it won't hurt - but your phone has to have been SHIPPED with v20b. you may be helping us to help you later down the road - because i don't know that those EXACT files exist any where on the internet (i've been looking).
thanks in advance.

I think the x&u of P760 is the same, whether it is extracted from KDZ (as Lelus did and provide) or it is from a phone that comes with v20b factory.

Related

Extracting Rogers images

I'm trying to extract boot, recovery, system from my Rogers Notes, and need some clarification. Do I need to be rooted first? When I try now, I cannot access /dev/block to extract any image.
It seems all the root methods available somehow modifies the kernel or recovery or system, which kinda makes it impossible to extract stock images?
Help please
I have used adb to shell into the Note and extracted the various images. I'm looking for stock Rogers images. The ones DAGr8 posted still has the Telus brand on them.
c:\> adb shell
$ su
# dd if=/dev/block/mmcblk0p24 of=/sdcard/system.img
# dd if=/dev/block/mmcblk0p22 of=/sdcard/recovery.img
# dd if=/dev/block/mmcblk0p8 of=/sdcard/boot.img
# exit
c:\> adb pull /sdcard/system.img
c:\> adb pull /sdcard/recovery.img
c:\> adb pull /sdcard/boot.img
ha! i'm on the boat, i'm trying to extract all the original stuff before going crazy on it
just a few min ago i PMed DAGr8 for details
seems like you beat him to it
i know the radio was already done
so i'll just do those 3 mentioned above
firefly9 said:
c:\> adb shell
$ su
# dd if=/dev/block/mmcblk0p24 of=/sdcard/system.img
# dd if=/dev/block/mmcblk0p22 of=/sdcard/recovery.img
# dd if=/dev/block/mmcblk0p8 of=/sdcard/boot.img
# exit
c:\> adb pull /sdcard/system.img
c:\> adb pull /sdcard/recovery.img
c:\> adb pull /sdcard/boot.img
Click to expand...
Click to collapse
firefly9 said:
I have used adb to shell into the Note and extracted the various images. I'm looking for stock Rogers images. The ones DAGr8 posted still has the Telus brand on them.
c:\> adb shell
$ su
# dd if=/dev/block/mmcblk0p24 of=/sdcard/system.img
# dd if=/dev/block/mmcblk0p22 of=/sdcard/recovery.img
# dd if=/dev/block/mmcblk0p8 of=/sdcard/boot.img
# exit
c:\> adb pull /sdcard/system.img
c:\> adb pull /sdcard/recovery.img
c:\> adb pull /sdcard/boot.img
Click to expand...
Click to collapse
Once I get adb running do I just input the above commands into the command prompt?
Does the "adb pull" command just copy the images from the device or does it remove them?
Sorry for the basic adb questions. I've always had Nexus phones so I'm not sure if things work differently on other phones.
Once in the shell on the device, denoted by the "$" prompt, enter the commands outlined. After the "dd" commands have been completed, enter "exit" (twice, actually) and then the "adb pull" commands to copy the images from the device to you local computer. The images are copied so they will remain on the device until you delete them.
i find this easier...
adb shell dd if=/dev/block/mmcblk0p13 of=/sdcard/amss.bin
adb shell dd if=/dev/block/mmcblk0p17 of=/sdcard/mdm.bin
adb shell dd if=/dev/block/mmcblk0p24 of=/sdcard/system.img
adb shell dd if=/dev/block/mmcblk0p22 of=/sdcard/recovery.img
adb shell dd if=/dev/block/mmcblk0p8 of=/sdcard/boot.img
adb pull /sdcard/amss.bin
adb pull /sdcard/mdm.bin
adb pull /sdcard/system.img
adb pull /sdcard/recovery.img
adb pull /sdcard/boot.img

[Q] Read partitions without rooting

I'm trying to find an universal way to read userdata partition(dump partition) without rooting the device.
Assumption :
the device can be boot in fastboot mode
Possible ways :
1. Using fastboot
I've looked into fastboot.c, it taking usb as a usb_handle pointer. I'm trying to move from that point. Fastboot is mostly to write or erase, but I assumed if writing and erasing are possible, reading should be possible as well.
2. Using nvflash, tftp...
It won't be the solution, since it's chip dependent but using chip vendor's download tool to dump partitions.
Go for it!
How does using adb dumping from /dev/mmcblk0p1 sounds?
can I unmount mmcblk0p1, and mount back to readable position?
what device? more info please.
dd if=dev/mmcblk0p? of=data.img bs= 8096 is usually the easiest. (<--just an example)
also this may be helpful:
http://forum.xda-developers.com/showthread.php?t=1247908
chrisrotolo said:
what device? more info please.
dd if=dev/mmcblk0p? of=data.img bs= 8096 is usually the easiest. (<--just an example)
also this may be helpful:
http://forum.xda-developers.com/showthread.php?t=1247908
Click to expand...
Click to collapse
Thanks for the link. using dd command is the exact way I used to dump mmc block as root. Or can it be run under not-rooted phones?
Rooting depends on the kernel version of devices, so when I have to dump various phones, it's very cumbersome to root different kinds of devices and dump.
So I'm finding a way to walk around the problem by using fastboot or if possible adb.
I think fastboot is my best bet so far.
How about adb?
adb shell
df -h
kkiqq1208 said:
How about adb?
adb shell
df -h
Click to expand...
Click to collapse
df -h will only show usage of storage medias. Is there anyway I can read off the actual data?
As already mentioned, dd, but via ADB. I believe that it functions at a low enough level that you should be able to dump mmcblk0 without having to be rooted. If dd can't be directly accessed via adb, you could extract a busybox install from a rooted phone and set it up in your adb directory and then run it from there with busybox (in theory).
Волк said:
As already mentioned, dd, but via ADB. I believe that it functions at a low enough level that you should be able to dump mmcblk0 without having to be rooted. If dd can't be directly accessed via adb, you could extract a busybox install from a rooted phone and set it up in your adb directory and then run it from there with busybox (in theory).
Click to expand...
Click to collapse
Question.
Feels like i'm on the different page from you. If i run dd for /dev/mmcblk0 it does give me an error message saying "Access Denied" of couse mmcblk0 is owned by root. And busybox too(I haven;t tried this), it's just a set of linux commnads, I'm not sure how it can access a file(in this case, a device) which does not have its ownership.
Please correct me if I'm wrong.
Hi All,
There is a way to dump any partition to SD card partition on unrooted device vi ADB.
Paste this couple of lines into the terminal :
adb kill-server
adb wait-for-device
adb shell "echo ro.kernel.qemu=1 > /data/local.prop"
adb reboot
adb wait-for-device
adb shell "mount -wo remount rootfs /"
adb shell "rm /data/local.prop"
adb shell dd if=/dev/block/mmcblk0p1 of=/sdcard/mmcp1.dump
The phone may reboot many time after that, so make sure the file /data/local.prop is deleted after this operation. or execute this :
adb reboot
adb wait-for-device
adb shell "rm /data/local.prop"
adb reboot
hope that helps
__________________
HTC One X (SFR)
Wissam said:
Hi All,
There is a way to dump any partition to SD card partition on unrooted device vi ADB.
Paste this couple of lines into the terminal :
adb kill-server
adb wait-for-device
adb shell "echo ro.kernel.qemu=1 > /data/local.prop"
adb reboot
adb wait-for-device
adb shell "mount -wo remount rootfs /"
adb shell "rm /data/local.prop"
adb shell dd if=/dev/block/mmcblk0p1 of=/sdcard/mmcp1.dump
The phone may reboot many time after that, so make sure the file /data/local.prop is deleted after this operation. or execute this :
adb reboot
adb wait-for-device
adb shell "rm /data/local.prop"
adb reboot
hope that helps
__________________
HTC One X (SFR)
Click to expand...
Click to collapse
Has anyone verified if this works for reading partitions on a non-rooted phone?
This doesn't work on an unrooted, locked device.
Code:
C:\Windows\System32>adb shell "echo ro.kernel.qemu=1 > /data/local.prop"
/system/bin/sh: can't create /data/local.prop: Permission denied
This did not work for my phone.
I got "permission denied" right after
adb shell "echo ro.kernel.qemu=1 > /data/local.prop"
Most of the above will only work on a rooted device with superuser.
The loop holes for shadow copies are mostly fixed since 6.0.
Partitions that can be accessed without root can be dumped with DD through ADB if ADB itself is supported and not internally limited to prevent just this.
Try
Code:
adb reboot recovery
adb root
adb shell
In my device, I can able to read those /data /dev without bootloader unlocking or root.
HemanthJabalpuri said:
Try
Code:
adb reboot recovery
adb root
adb shell
In my device, I can able to read those /data /dev without bootloader unlocking or root.
Click to expand...
Click to collapse
So, ... You are lucky. If I try these commands, I am getting "error: closed". And believe it or not, I have my bootloader UNlocked. It's a doomed chinese tablet, Allwinner 100 SOC.
observingman said:
So, ... You are lucky. If I try these commands, I am getting "error: closed". And believe it or not, I have my bootloader UNlocked. It's a doomed chinese tablet, Allwinner 100 SOC.
Click to expand...
Click to collapse
I found that it is common for many Realme devices to able to use `adb root` in recovery mode.
I have a Realme C12 which has Mediatek Helio G35 MT6765G SoC. So we can also able to `readback` partitions by using SP Flash Tool with the help of MTK-bypass.

[Q] how to go to v20f to cm10.1?

So I kinda messed up on my bootloader unlocked p769 and updated to v20f with no root on accident. However, I've decided that I want to go back to cm10.1 on jellybean v20d. How do I accomplish this? I don't have recovery or anything now. What's the easiest way to do this? Thanks
If anyone could help I'd be very grateful!
nfilipac said:
If anyone could help I'd be very grateful!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2338816 root your phone
Download and copy following to the sdcard :
http://forum.xda-developers.com/showpost.php?p=40441852 (unzip p1.zip)
https://www.dropbox.com/s/gw74cg1ntwmwlij/cwmtouch.img
http://forum.xda-developers.com/showthread.php?t=2355816 cm10.1 for p769
from your computer:
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/p1.bin of=/dev/block/mmcblk0p1
adb shell su -c busybox dd if=/sdcard/external_sd/p2.bin of=/dev/block/mmcblk0p2
adb shell su -c busybox dd if=/sdcard/external_sd/cwmtouch.img of=/dev/block/mmcblk0p4
adb reboot recovery
or phone
Code:
su
busybox dd if=/sdcard/external_sd/p1.bin of=/dev/block/mmcblk0p1
busybox dd if=/sdcard/external_sd/p2.bin of=/dev/block/mmcblk0p2
busybox dd if=/sdcard/external_sd/cwmtouch.img of=/dev/block/mmcblk0p4
reboot recovery
wipe data/cache/dalvik
install cm10.1
Lelus said:
http://forum.xda-developers.com/showthread.php?t=2338816 root your phone
Download and copy following to the sdcard :
http://forum.xda-developers.com/showpost.php?p=40441852 (unzip p1.zip)
https://www.dropbox.com/s/gw74cg1ntwmwlij/cwmtouch.img
http://forum.xda-developers.com/showthread.php?t=2355816 cm10.1 for p769
from your computer:
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/p1.bin of=/dev/block/mmcblk0p1
adb shell su -c busybox dd if=/sdcard/external_sd/p2.bin of=/dev/block/mmcblk0p2
adb shell su -c busybox dd if=/sdcard/external_sd/cwmtouch.img of=/dev/block/mmcblk0p4
adb reboot recovery
or phone
Code:
su
busybox dd if=/sdcard/external_sd/p1.bin of=/dev/block/mmcblk0p1
busybox dd if=/sdcard/external_sd/p2.bin of=/dev/block/mmcblk0p2
busybox dd if=/sdcard/external_sd/cwmtouch.img of=/dev/block/mmcblk0p4
reboot recovery
wipe data/cache/dalvik
install cm10.1
Click to expand...
Click to collapse
Thank you very much, that's exactly what I was looking for! however, there's just a little problem... when i open superuser to see if it rooted properly, I get "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" I've tried both the method you linked and this method http://forum.xda-developers.com/showthread.php?t=2173465 but i get the same results. I've rooted before, but i dont know what I'm doing wrong this time!
EDIT: Figured it out I'm a noob. Thanks!

[Q] Make a full backup for flashing with busybox

Hello
There's a way for making a backup with RAW extension that can be flashed with fastboot in asus fonepad (i don't know about others)
See this: http://forum.xda-developers.com/showthread.php?t=1818321
Back up of the whole memory block (via adb)
Connect the phone in ADB mode and unlock the screen.
Open one Cygwin Terminal and enter (replace mmcblk0 if needed):
Code:
adb forward tcp:5555 tcp:5555
adb shell
su
/system/xbin/busybox nc -l -p 5555 -e /system/xbin/busybox dd if=/dev/block/mmcblk0
You will see the cursor blinking at the left. Now the phone is waiting to send the block over the network.
Open another Cygwin terminal and type:
Code:
adb forward tcp:5555 tcp:5555
cd /path/to/store/the/backup
nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0.raw
You will see how the image size is growing until it finishes. Now you have the whole phone backed up in raw format. You can see the contents of the GPT partition with gptfdisk tool, available for windows, linux and such. See official website and sourceforge to get it. You can do it the same from ClockWorkMod Recovery but you have to mount first the /system partition since the busybox included with clockworkmod does not come with netcat and you have to use the one from the system partition.
With further linux tools you could edit or extract single partitions from the whole block.
Click to expand...
Click to collapse
But it's for rooted devices only. how can i make a backup with busybox non-root?

Curious about Philz Touch Recovery files....

I have a question here. Recently the LG G PRO 2 android handphone received OTA update. If I let the OTA run. After OTA updated, if I still want to re-install Philz Touch Recovery, is that mean the latest newer file provided by OTA update will be overwrite when I re-install the recovery that released 1 yr ago?
Below is the command that will install the files if I re-install the recovery. I dont know if these file important or not if replaced by recovery installation. I have no idea the purpose of these files. Please advice.
What I hope is to make sure latest stable file running on my phone.
adb shell su -c "dd if=/sdcard/img/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
adb shell su -c "dd if=/sdcard/img/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot"
adb shell su -c "dd if=/sdcard/img/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot"
adb shell su -c "dd if=/sdcard/img/dbi.img of=/dev/block/platform/msm_sdcc.1/by-name/dbi"
adb shell su -c "dd if=/sdcard/img/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf"
adb shell su -c "dd if=/sdcard/img/persist.img of=/dev/block/platform/msm_sdcc.1/by-name/persist"
adb shell su -c "dd if=/sdcard/img/rpm.img of=/dev/block/platform/msm_sdcc.1/by-name/rpm"
adb shell su -c "dd if=/sdcard/img/sbl1.img of=/dev/block/platform/msm_sdcc.1/by-name/sbl1"
adb shell su -c "dd if=/sdcard/img/tz.img of=/dev/block/platform/msm_sdcc.1/by-name/tz"
adb shell su -c "dd if=/sdcard/img/modem.img of=/dev/block/platform/msm_sdcc.1/by-name/modem"

Categories

Resources