LG G3 system img dump
System dump size: 2.4GB
Rar: 990MB
Download system:
Mega: https://mega.co.nz/#!iI8nQCpR!T0JebFjem_Ga9uxoirXJFOk8dVx6wEJCNhjRNU6yt5M
Download all other partition (include aboot, boot, etc....)
https://mega.co.nz/#!OMMCFLJB!3fmUAZzhDm9WwvXp-U0_TXqBF9GqKLufKyc7SApegt4
Pass unrar: LGViet.com
source: lgviet.com
@OptimusRs
@Hid3rs
@xdabbeb
Thx - I see twice the same downlaod link (dump + partitions)
bender_007 said:
Thx - I see twice the same downlaod link (dump + partitions)
Click to expand...
Click to collapse
Edited thanks
Two aboot's eh?
bobbarker2 said:
Two aboot's eh?
Click to expand...
Click to collapse
LG G3 Full partition info:
G3 has 2 bootloaders ?!
Yes, i'm researching
adb shell ls -la /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 1970-01-01 08:13 DDR -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 08:13 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 08:13 abootf -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-01 08:13 boot -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-01 08:13 cache -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-01 08:13 dbi -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 08:13 dbibak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-01 08:13 drm -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-01 08:13 eksst -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-01 08:13 encrypt -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-01 08:13 factory -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-01 08:13 fota -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-01 08:13 fsc -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-01 08:13 fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-01 08:13 grow -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-01-01 08:13 laf -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-01 08:13 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-01 08:13 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 08:13 modemst1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-01 08:13 modemst2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-01 08:13 mpt -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-01 08:13 pad -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 08:13 pad1 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-01 08:13 pad2 -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-01 08:13 persist -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-01 08:13 rct -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-01 08:13 recovery -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-01 08:13 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 08:13 rpmbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-01 08:13 rpmf -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-01 08:13 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 08:13 sbl1b -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-01 08:13 sdif -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-01 08:13 sns -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-01 08:13 spare1 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-01 08:13 spare2 -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-01 08:13 spare3 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-01 08:13 ssd -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-01 08:13 system -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-01 08:13 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-01 08:13 tzbak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-01 08:13 tzf -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-01 08:13 userdata -> /dev/block/mmcblk0p42
I saw drivers for both IMX214 and IMX135 in the system dump. Any better way to know for sure what camera it's using?
abootf, tzf, rpmf, sdif etc are all blank (00s)... interesting.
would like to see fota partition. possibly misc partition(just edit imei out of misc with hex editor) or PM me with info instead.
wargreymon89 said:
I saw drivers for both IMX214 and IMX135 in the system dump. Any better way to know for sure what camera it's using?
Click to expand...
Click to collapse
That's very interesting. I suppose there are a few possibilities here. One would be that the G3 does use the IMX214 after all, or that the IMX214 and IMX135 are both used in different versions of the G3 (less likely). Perhaps the phone originally was being developed with the 135 and so initial prototypes used it, while the end production model would use the 214? Another possibility would be that perhaps the drivers come as a package from Sony and both the 135 and 214 are supported or come in the same package.
An editor at AndroidCentral claims he was told by LG that the sensor is not the same as the G2, meanwhile Anandtech reported that it was. It'd be nice to have some confirmation, but I suppose thus far the results speak for themselves as the G3 looks to be quite capable, whether that's due to improved software processing or a new sensor or both.
klmd said:
That's very interesting. I suppose there are a few possibilities here. One would be that the G3 does use the IMX214 after all, or that the IMX214 and IMX135 are both used in different versions of the G3 (less likely). Perhaps the phone originally was being developed with the 135 and so initial prototypes used it, while the end production model would use the 214? Another possibility would be that perhaps the drivers come as a package from Sony and both the 135 and 214 are supported or come in the same package.
An editor at AndroidCentral claims he was told by LG that the sensor is not the same as the G2, meanwhile Anandtech reported that it was. It'd be nice to have some confirmation, but I suppose thus far the results speak for themselves as the G3 looks to be quite capable, whether that's due to improved software processing or a new sensor or both.
Click to expand...
Click to collapse
I sure hope and believe it uses IMX214, both due to the obvious improvement in pictures and that LG usually picks the latest and best hardware. I guess only a tear down or D85X system dump with one or the other driver missing will prove what it's using.
autoprime said:
abootf, tzf, rpmf, sdif etc are all blank (00s)... interesting.
would like to see fota partition. possibly misc partition(just edit imei out of misc with hex editor) or PM me with info instead.
Click to expand...
Click to collapse
edited
About the LG Camera
hoangnova said:
LG G3 Full partition info:
G3 has 2 bootloaders ?!
Yes, i'm researching
adb shell ls -la /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 1970-01-01 08:13 userdata -> /dev/block/mmcblk0p42
Click to expand...
Click to collapse
Hi, Do you know the Camera details, These are from CameraApp, Can anyone confirmed the panorama_preview_size?
</item>
<item name="panorama_picture_size"> 4160x2340
</item>
<item name="panorama_preview_size"> 768x432
</item>
<item name="panorama_preview_size_on_screen"> 1920x1080
</item>
<item name="gestureshot_supported"> true
</item>
<item name="beautyshot_supported"> true
</item>
<item name="hdr_supported"> 3
</item>
Here is another config files for LG G3
</item>
<item name="panorama_picture_size"> 4160x2340
</item>
<item name="panorama_preview_size"> 1280x720
</item>
<item name="panorama_preview_size_on_screen"> 2560x1440
</item>
<item name="gestureshot_supported"> true
</item>
<item name="beautyshot_supported"> true
</item>
<item name="hdr_supported"> 2
What is all this info Worth? Does this mean development for cm11 will be easier? Speaking about that do you think it will be easy to root and have cm on this device?
Thanks in advance!
Sent from my SM-G900T using Tapatalk
I'm very thankful for this, cause I deleted some system apks and got myself a nasty bootloop! :silly:
is that for all G3 Variants, does it work with D855?
sycolon said:
is that for all G3 Variants, does it work with D855?
Click to expand...
Click to collapse
Its useless now.
@Ferindel my device is stuck on fastboot mode, cant enter the system or the Download mode.
what can i do i need help.
sycolon said:
@Ferindel my device is stuck on fastboot mode, cant enter the system or the Download mode.
what can i do i need help.
Click to expand...
Click to collapse
I got out of the fastboot loop by downloading the rin image from http://forum.xda-developers.com/lg-g3/orig-development/kernel-rin-kernel-1-0-t2847581 and using
Code:
fastboot boot D855-rin-1.0.1.img
sycolon said:
is that for all G3 Variants, does it work with D855?
Click to expand...
Click to collapse
Ferindel said:
Its useless now.
Click to expand...
Click to collapse
Why exactly is it useless???
It's a perfect way to have all system apps, in case of something went wrong by mistakenly deleting one etc.
i have no system nothing on my phone so i think just this kernel will do nothing, i need to back on stock or to have Download mode to flash KDZ file ...
---------- Post added at 10:43 PM ---------- Previous post was at 10:32 PM ----------
i flashed a aboot image from the file the colores of my screen in the logo where lost, i tried to delete and flash (laf,boot,aboot,recovery) , but nothing work, i couldn't have a Download Mode on my device.
last i did
macbook-proyi-macbook-pro-15:rar macbookpro$ ./fastboot erase boot
erasing 'boot'...
OKAY [ 0.017s]
finished. total time: 0.018s
macbook-proyi-macbook-pro-15:rar macbookpro$ ./fastboot erase aboot
erasing 'aboot'...
OKAY [ 0.008s]
finished. total time: 0.008s
macbook-proyi-macbook-pro-15:rar macbookpro$ ./fastboot erase laf
erasing 'laf'...
OKAY [ 0.017s]
finished. total time: 0.018s
macbook-proyi-macbook-pro-15:rar macbookpro$ ./fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.017s]
finished. total time: 0.017s
macbook-proyi-macbook-pro-15:rar macbookpro$ ./fastboot reboot
rebooting...
Click to expand...
Click to collapse
now my device is dead, black screen, no lights nothing....
any help!!! please, my phone is just 3 months old..... **** and i paid for one month i have a year from now.....
Related
Thought I'll create a thread for developers on LG G Pad 7.0/8.0/10.1
I'll try to keep it updated as best as I can. If I forget/get to busy, PM me and tell me what to change
Help Wanted:
If you own a LG G Pad 8.0/10.1, mind doing the following things? It'll help with kernel development/porting CM11/other ROMs
Dump partition list/info : instructions
Dump /system/build.prop
Possibly need root for stuff below
Dump aboot, boot and recovery partition : need partition list first before posting instructions. probably instructions below will continue to work
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery.img
LG G Pad 7.0
Model Name: v400
Released with KitKat 4.4.?
Kernel Source:
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v400
Root:
Towelroot works
Loki no longer works, can't bypass the locked bootloader to boot custom ROMs/kernels/recovery
Mode Name: v410 (LTE AT&T version)
Root: purpledrake works
LG G Pad 8.0
Unknown device.... not released yet?
LG G Pad 10.1
Model Name: v700, v700n (korean model?)
Released with KitKat 4.4.?
Kernel Source:
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v700
Root:
Towelroot works
paperWastage said:
Thought I'll create a thread for developers on LG G Pad 7.0/8.0/10.1
I'll try to keep it updated as best as I can. If I forget/get to busy, PM me and tell me what to change
Help Wanted:
If you own a LG G Pad 7.0/8.0/10.1, mind doing the following things? It'll help with kernel development/porting CM11/other ROMs
Dump partition list/info : instructions
Dump /system/build.prop
Possibly need root for stuff below
Dump aboot, boot and recovery partition : need partition list first before posting instructions. probably instructions below will continue to work
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery.img
Click to expand...
Click to collapse
Hi, I own a G pad 7.0. It seems that I am the only one in the world I'm gonna try to help a little:
1. Dump partition:
-lrwxrwxrwx root root 1970-03-05 03:01 DDR -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-03-05 03:01 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-03-05 03:01 abootb -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-03-05 03:01 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-03-05 03:01 cache -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-03-05 03:01 cust -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-03-05 03:01 drm -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-03-05 03:01 eksst -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-03-05 03:01 encrypt -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-03-05 03:01 factory -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-03-05 03:01 fota -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-03-05 03:01 fsc -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-03-05 03:01 fsg -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-03-05 03:01 grow -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-03-05 03:01 laf -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-03-05 03:01 misc -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-03-05 03:01 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-03-05 03:01 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-03-05 03:01 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-03-05 03:01 mpt -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-03-05 03:01 pad -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-03-05 03:01 persist -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-03-05 03:01 rct -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-03-05 03:01 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-03-05 03:01 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-03-05 03:01 rpmb -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-03-05 03:01 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-03-05 03:01 sbl1b -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-03-05 03:01 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-03-05 03:01 sns -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-03-05 03:01 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-03-05 03:01 system -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-03-05 03:01 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-03-05 03:01 tzb -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-03-05 03:01 userdata -> /dev/block/mmcblk0p34
- Dump build.prop, boot, aboot and recovery:
http://www37.zippyshare.com/v/4146966/file.html
http://www37.zippyshare.com/v/66268524/file.html
http://www37.zippyshare.com/v/51126864/file.html
http://www37.zippyshare.com/v/44186789/file.html
http://www37.zippyshare.com/v/85458029/file.html
I think for now nothing can be done with it (there is no recovery yet). I hope something can be done.
Hammerhand.17 said:
Hi, I own a G pad 7.0. It seems that I am the only one in the world I'm gonna try to help a little:
1. Dump partition:
-lrwxrwxrwx root root 1970-03-05 03:01 DDR -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-03-05 03:01 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-03-05 03:01 abootb -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-03-05 03:01 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-03-05 03:01 cache -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-03-05 03:01 cust -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-03-05 03:01 drm -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-03-05 03:01 eksst -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-03-05 03:01 encrypt -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-03-05 03:01 factory -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-03-05 03:01 fota -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-03-05 03:01 fsc -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-03-05 03:01 fsg -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-03-05 03:01 grow -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-03-05 03:01 laf -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-03-05 03:01 misc -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-03-05 03:01 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-03-05 03:01 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-03-05 03:01 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-03-05 03:01 mpt -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-03-05 03:01 pad -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-03-05 03:01 persist -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-03-05 03:01 rct -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-03-05 03:01 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-03-05 03:01 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-03-05 03:01 rpmb -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-03-05 03:01 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-03-05 03:01 sbl1b -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-03-05 03:01 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-03-05 03:01 sns -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-03-05 03:01 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-03-05 03:01 system -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-03-05 03:01 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-03-05 03:01 tzb -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-03-05 03:01 userdata -> /dev/block/mmcblk0p34
- Dump build.prop, boot, aboot and recovery:
http://www37.zippyshare.com/v/4146966/file.html
http://www37.zippyshare.com/v/66268524/file.html
http://www37.zippyshare.com/v/51126864/file.html
http://www37.zippyshare.com/v/44186789/file.html
http://www37.zippyshare.com/v/85458029/file.html
I think for now nothing can be done with it (there is no recovery yet). I hope something can be done.
Click to expand...
Click to collapse
thanks for this.
@icedmayhem also provided similar files over PM, forgot to post updates here...
anyways, it looks like this device has the patched aboot source code.
loki won't work anymore (loki provides a way for us to bypass the locked bootloader to load non-stock recovery/kernels. This means there isn't an easy way to boot a custom recovery(TWRP) or custom ROM.
Can you check if you can unlock the bootloader? Don't know if LG provides a process to do this easily (for GPE / non-GPE devices)
strings aboot.img | fgrep overlap
The erase group overlaps the max requested for erase
kernel/ramdisk addresses overlap with aboot addresses.
Device tree addresses overlap with aboot addresses.
Boot image buffer address overlaps with aboot addresses.
Signature read buffer address overlaps with aboot addresses.
Click to expand...
Click to collapse
I wish I now how to do it, but I have no idea of how to do this
FYI I was able to successfully root the G Pad 7.0 At&t version using purpledrake. LG-V410
idelgado782 said:
FYI I was able to successfully root the G Pad 7.0 At&t version using purpledrake. LG-V410
Click to expand...
Click to collapse
Link? Or just any of them?
Thxfor the info looking for it now.
Impala126 said:
Link? Or just any of them?
Thxfor the info looking for it now.
Click to expand...
Click to collapse
Here's the link to the purpledrake thread. Once you download and install on your computer make sure the gpad USB mode is on ptp mode.
http://forum.xda-developers.com/showthread.php?p=54254055
No matter what, I can never stay away from android for long.
idelgado782 said:
Here's the link to the purpledrake thread. Once you download and install on your computer make sure the gpad USB mode is on ptp mode.
http://forum.xda-developers.com/showthread.php?p=54254055
No matter what, I can never stay away from android for long.
Click to expand...
Click to collapse
Yup worked like a champ. Turned on air plane mode, then usb debugging and then ptp. But I had to go to a term win on win7 and run bat file from there. wouldn't run with admin rights from windows explore.
idelgado782 said:
FYI I was able to successfully root the G Pad 7.0 At&t version using purpledrake. LG-V410
Click to expand...
Click to collapse
for your G Pad 7.0 AT&T LTE version, mind posting the same items that Hammerhand.17 provided (for the G Pad 7.0)?
more info the better, just easier for the next developer to try to help out
paperWastage said:
LG G Pad 7.0
Model Name: v400
Released with KitKat 4.4.?
Root:
Towelroot works
Click to expand...
Click to collapse
It works also with a normal V400? I mean with NO at&t version.
(the site is towelroot.com, right?)
Yes, I have root in my normal V400 with no problem.
Hammerhand.17 said:
Yes, I have root in my normal V400 with no problem.
Click to expand...
Click to collapse
Thank you
Hammerhand.17 said:
Yes, I have root in my normal V400 with no problem.
Click to expand...
Click to collapse
One more question, it will work for sure on 4.4.2?
Has anyone tried or been successful pulling a factory image file for the LG V410 which is the AT&T G Pad 7.0? I tried the other day but there was not an image on their servers at that time
Giammysz said:
One more question, it will work for sure on 4.4.2?
Click to expand...
Click to collapse
Yes, 4.4.2 is the version of my tablet.
Giammysz said:
One more question, it will work for sure on 4.4.2?
Click to expand...
Click to collapse
Yes! Even if you have already did the OTA incremental update ..... You will need to install a SU manager though like Super SU etc after rooting with Towel root...
Hammerhand.17 said:
Yes, 4.4.2 is the version of my tablet.
Click to expand...
Click to collapse
Anthonol said:
Yes! Even if you have already did the OTA incremental update ..... You will need to install a SU manager though like Super SU etc after rooting with Towel root...
Click to expand...
Click to collapse
Thank you all
I successfully rooted my tab, it's really simple with towelroot! Install, tap and ready!
Im not really a dev but i know my way around android. I figured this could help kickstart development for us. I have pulled my boot.img and attached it below.
Here are the mount points for building a rom. May differ from the different varients. My model is XT1527 US LTE.
HTML:
ls -al /dev/block/platform/soc.0/by-name
lrwxrwxrwx root root 1970-01-23 12:12 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-23 12:12 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-23 12:12 abootBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-23 12:12 boot -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-23 12:12 cache -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-01-23 12:12 carrier -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-23 12:12 cid -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-23 12:12 clogo -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-23 12:12 dhob -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-23 12:12 factorytune1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-23 12:12 factorytune2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-23 12:12 frp -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-23 12:12 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-23 12:12 fsg -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-23 12:12 hob -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-23 12:12 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-23 12:12 hypBackup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-23 12:12 keystore -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-23 12:12 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-23 12:12 logo -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-23 12:12 logs -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-23 12:12 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-23 12:12 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-23 12:12 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-23 12:12 modemst1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-23 12:12 modemst2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-23 12:12 oem -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-23 12:12 padA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-23 12:12 padB -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-23 12:12 padC -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-23 12:12 persist -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-23 12:12 recovery -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-23 12:12 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-23 12:12 rpmBackup -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-23 12:12 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-23 12:12 sec -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-23 12:12 sp -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-23 12:12 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-23 12:12 system -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-23 12:12 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-23 12:12 tzBackup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-23 12:12 userdata -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-01-23 12:12 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-23 12:12 utagsBackup -> /dev/block/mmcblk0p17
Excellent.... Thank u....I will try to release a ROM within a week
Shawn5162 said:
Excellent.... Thank u....I will try to release a ROM within a week
Click to expand...
Click to collapse
good news, good luck for your build
Shawn5162 said:
Excellent.... Thank u....I will try to release a ROM within a week
Click to expand...
Click to collapse
awesome, if you need a tester, please pm.
Shawn5162 said:
Excellent.... Thank u....I will try to release a ROM within a week
Click to expand...
Click to collapse
Shawn, you got a Moto E 2015? :laugh:
I find myself fortunate getting MotoG 2015 n Moto E 2015, both being worked upon by you! Thanks man!
If anybody who us good at linux knows how to add these mount points to cwm or philz touch im trying to port a build for us pm me.
WIFI tethering
I just picked this phone up today and cricket has ripped out the WIFI tethering. If anyone has a stock rooted rom please send me a link.
Mounting points are different on my cmda moto e2 will try to upload them later
bzo22 said:
Mounting points are different on my cmda moto e2 will try to upload them later
Click to expand...
Click to collapse
yup the cdma models and the 3g only models will probably have different mounts.
cmda xt1526 boostmobile surina
s -al /dev/block/platform/soc.0/by-name <
/dev/block/platform/soc.0/by-name: Permission denied
1|[email protected]_cdma:/ $ su
s -al /dev/block/platform/soc.0/by-name <
lrwxrwxrwx root root 1970-01-31 14:18 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-31 14:18 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-31 14:18 abootBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-31 14:18 boot -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-31 14:18 cache -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-31 14:18 carrier -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-31 14:18 cid -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-31 14:18 clogo -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-31 14:18 dhob -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-31 14:18 factorytune1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-31 14:18 factorytune2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-31 14:18 frp -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-31 14:18 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-31 14:18 fsg -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-31 14:18 hob -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-31 14:18 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-31 14:18 hypBackup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-31 14:18 keystore -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-31 14:18 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-31 14:18 logo -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-31 14:18 logs -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-31 14:18 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-31 14:18 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-31 14:18 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-31 14:18 modemst1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-31 14:18 modemst2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-31 14:18 padA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-31 14:18 padB -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-31 14:18 padC -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-31 14:18 persist -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-31 14:18 recovery -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-31 14:18 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-31 14:18 rpmBackup -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-31 14:18 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-31 14:18 sec -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-31 14:18 sp -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-31 14:18 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-31 14:18 system -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-31 14:18 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-31 14:18 tzBackup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-31 14:18 userdata -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-01-31 14:18 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-31 14:18 utagsBackup -> /dev/block/mmcblk0p17
[email protected]_cdma:/ #
bzo22 said:
s -al /dev/block/platform/soc.0/by-name <
<SNIP>
[email protected]_cdma:/ #
Click to expand...
Click to collapse
How did you get root on the xt1526 boost phone bzo22? Any chance you could post the stock boot loader img file or direct me to a working copy of a bootloader for it?
phliptrip said:
How did you get root on the xt1526 boost phone bzo22? Any chance you could post the stock boot loader img file or direct me to a working copy of a bootloader for it?
Click to expand...
Click to collapse
I used twrp to flash super user the recovery works for our device too...but do not flash it just boot it from fastboot. Which partition is boot loader stored . is it aboot or boot section
aboot.img
bzo22 said:
I used twrp to flash super user the recovery works for our device too...but do not flash it just boot it from fastboot. Which partition is boot loader stored . is it aboot or boot section
Click to expand...
Click to collapse
Here u go the aboot.img
Rooted this Phone
{
"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"
}
phliptrip said:
How did you get root on the xt1526 boost phone bzo22? Any chance you could post the stock boot loader img file or direct me to a working copy of a bootloader for it?
Click to expand...
Click to collapse
---------- Post added at 08:32 PM ---------- Previous post was at 08:29 PM ----------
i have root on this phone look and see.
http://imgur.com/tll9LYH,TeVRm5I,4dBA7v5,TdZJI1m,vJyFZEa
---------- Post added at 08:35 PM ---------- Previous post was at 08:32 PM ----------
here are some more pictures of my phone.
http://imgur.com/tll9LYH,TeVRm5I,4dBA7v5,TdZJI1m,vJyFZEa#1
http://imgur.com/tll9LYH,TeVRm5I,4dBA7v5,TdZJI1m,vJyFZEa#2
http://imgur.com/tll9LYH,TeVRm5I,4dBA7v5,TdZJI1m,vJyFZEa#3
http://imgur.com/tll9LYH,TeVRm5I,4dBA7v5,TdZJI1m,vJyFZEa#4.
there you go. im not giving you the files.because i can
fix-this! said:
Im not really a dev but i know my way around android. I figured this could help kickstart development for us. I have pulled my boot.img and attached it below.
Here are the mount points for building a rom. May differ from the different varients. My model is XT1527 US LTE.
HTML:
ls -al /dev/block/platform/soc.0/by-name
lrwxrwxrwx root root 1970-01-23 12:12 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-23 12:12 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-23 12:12 abootBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-23 12:12 boot -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-23 12:12 cache -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-01-23 12:12 carrier -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-23 12:12 cid -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-23 12:12 clogo -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-23 12:12 dhob -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-23 12:12 factorytune1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-23 12:12 factorytune2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-23 12:12 frp -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-23 12:12 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-23 12:12 fsg -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-23 12:12 hob -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-23 12:12 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-23 12:12 hypBackup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-23 12:12 keystore -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-23 12:12 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-23 12:12 logo -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-23 12:12 logs -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-23 12:12 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-23 12:12 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-23 12:12 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-23 12:12 modemst1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-23 12:12 modemst2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-23 12:12 oem -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-23 12:12 padA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-23 12:12 padB -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-23 12:12 padC -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-23 12:12 persist -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-23 12:12 recovery -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-23 12:12 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-23 12:12 rpmBackup -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-23 12:12 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-23 12:12 sec -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-23 12:12 sp -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-23 12:12 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-23 12:12 system -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-23 12:12 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-23 12:12 tzBackup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-23 12:12 userdata -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-01-23 12:12 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-23 12:12 utagsBackup -> /dev/block/mmcblk0p17
Click to expand...
Click to collapse
hey bro i needed some help. first can this boot image be used for 3g version.
If not then please can you tell me how to extract the boot.img of moto e 3g version
I've got the XT1527 for cricket and I'm willing to test. I'm no dev but ive been flashing roms constantly on all sorts of devices for a few years and id like to get involved and learn more if possible. This is my daily driver though so I might be a little cautious until there's a working twrp or something for the US version but this is a good phone so I'm very eager to see what ends up being made for this phone. Normally I'll look a phone up before buying it to make sure there's plenty of stuff available to keep me busy with it but when I saw this one had very little I actually got excited since Im sure this one will wind up with some good stuff and for the first time I won't be starting with a phone months after the forum died down lol
hakr4life said:
I've got the XT1527 for cricket and I'm willing to test. I'm no dev but ive been flashing roms constantly on all sorts of devices for a few years and id like to get involved and learn more if possible. This is my daily driver though so I might be a little cautious until there's a working twrp or something for the US version but this is a good phone so I'm very eager to see what ends up being made for this phone. Normally I'll look a phone up before buying it to make sure there's plenty of stuff available to keep me busy with it but when I saw this one had very little I actually got excited since Im sure this one will wind up with some good stuff and for the first time I won't be starting with a phone months after the forum died down lol
Click to expand...
Click to collapse
Same here keep me in the loop. I'm eager to brick my new phone
Sent from my MotoE2(4G-LTE) using XDA Free mobile app
+1 for at%t/aio/cricket users on the XT1527 model. there has got to be a workaround for the unlock on this. @mdewii23 @hakr4life
Can someone provide stock recovery?
I've scoured the internet over and over and come up with nothing yet
Sent from my Nexus 4 using XDA Free mobile app
Do not use this root method for 5.1.1!! You will get a soft brick and there is no way to recover! If your on 5.0.2 and did not take the update then you can proceed to this root method.
Here is the untouched update to 5.1.1:
udpate.zip
UPDATE: 6/25
BOOST MOBILE HAS RELEASED AN UPDATE! The update is around 413MB. I pulled the update and will be updating it soon. If you are rooted do not update the phone. It could cause a brick and or unroot the device! So far I just found a new radio.img inside of it. I'll check it out later this afternoon.
Hello everyone,
I wanted to make this thread for the LG G Stylo (Boost Mobile) cause I could not find any forums or any post about this device!
Anyways if you are looking for a ROOT method for this device visit here:
Proof (picture) that the device is rooted at the bottom of this post.
LG One Click Root 1.3 (Graphic UI):
Code:
[url]http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951[/url]
Here is the PARTITIONS from the device:
Code:
[email protected]:/ $ su
[email protected]:/ # ls -al /dev/block/bootdevice/by-name
lrwxrwxrwx root root 1970-01-04 18:18 DDR -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-04 18:18 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-04 18:18 abootbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-04 18:18 boot -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-04 18:18 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-04 18:18 carrier -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-04 18:18 drm -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-04 18:18 eksst -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-04 18:18 encrypt -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-04 18:18 factory -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-04 18:18 fota -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-04 18:18 fsc -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-04 18:18 fsg -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-04 18:18 grow -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-04 18:18 hyp -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-04 18:18 hypbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-04 18:18 laf -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-04 18:18 metadata -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-04 18:18 misc -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-04 18:18 modem -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-04 18:18 modemst1 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-04 18:18 modemst2 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-04 18:18 mpt -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-04 18:18 pad -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-04 18:18 pad2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-04 18:18 persist -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-04 18:18 persistent -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-04 18:18 rct -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-04 18:18 recovery -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-04 18:18 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-04 18:18 rpmbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-04 18:18 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-04 18:18 sbl1bak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-04 18:18 sec -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-04 18:18 sns -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-04 18:18 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-04 18:18 system -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-04 18:18 tz -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-04 18:18 tzbak -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-04 18:18 userdata -> /dev/block/mmcblk0p39
[email protected]:/ #
Here is how to get into STOCK RECOVERY:
Code:
1) Turn the device off
2) While holding the phone on, press and hold VOLUME -(DOWN) at the same time
3) When you see the LG boot logo hurry up and let go of the VOLUME -(DOWN) and hold it again for a few sec (kinda tricky)
4) Then this will get you into recovery mode
Here is how to get into DOWNLOAD MODE:
Code:
1) Turn the device off
2) While holding the VOLUME +(UP) key plug in the device into the pc
3) A screen should pop up and press the VOLUME +(UP) key until you see DOWNLOAD MODE with the progress bar
4) Done
NOTE: Pull out the battery once your done in DOWNLOAD MODE to get out of it and power the device like normal.
SYSTEM DUMP:
NOTE: These files are from 5.0.2 NOT 5.1.1!
Code:
[URL="http://www.mediafire.com/download/grau3kv5m1rbzwa/aboot.img"]aboot.img[/URL]
[URL="http://www.mediafire.com/download/f6cly93iusa83xz/boot.img"]boot.img [/URL]
[URL="http://www.mediafire.com/download/1opyd4a9fimbw8p/laf.img"]laf.img[/URL]
[URL="http://www.mediafire.com/download/qt3o5rrm4h2qo5o/recovery.img"]recovery.img[/URL]
[URL="http://www.mediafire.com/download/t7a3qq60xh2pm0c/system.zip"]system.img[/URL]
All files will be uploaded to my mediafire account!
Please make mirrors if you like.
NOTE: I am not a DEV! I will upload files to help others try to get something going for this device. I will test things as I go.
Just tried this root method on the TMO version of this and out didn't start. Curiously tried the manual method for the G3/G4 and i get a device offline when doing an ADB device list.
Sent from my LG-H631 using XDA Free mobile app
Make sure you install the right drivers. I had to install the drivers and then restart my laptop. It took me like 2-3 times to finally root the device with the Graphical UI method. On a side note I had to toggle MTP and the other one and then let the drivers install for each one. I then put the phone into charge mode and it finally rooted.
I will give it one more try tonight. I had uninstalled and re installed the LG drivers a few times. I can connect fine to my L90 and my G2. But for some reason this thing shows connected but "offline" in ADB. Toggled back and forth between MTP and PTP a few times too. No response when in download mode ekther.
Sent from my LG-H631 using XDA Free mobile app
Any luck Cahiatt on the root? My LG Flex has an issue that I have to send it back for repairs and I've been considering ordering the Stylo. Just need root though for all the stuff I like to do.
Thanks!
Haven't gone back to it yet. Ended up on other chores for the weekend.
Sent from my LG-H631 using XDA Free mobile app
Well the short answer is this worked on the TMO version also.
I don't have a long answer. For whatever reason when I tried again it just worked. There must have been something software related hanging on my desktop PC that was interfering with the port used by ADB or who knows what. I just went back, plugged the phone in and it worked. Woo Hoo!!!!
Sent from my LG-H631 using XDA Free mobile app
Can anyone with the tmobile stylo confirm the 2gb ram and 13mp cam?
Im considering this over the g4, more budget friendly.
I have a few questions.
Hows the lcd? Does it show alot of pixelation? Im hearing its pretty good for 720p.
Does it have a notification led?
I know it has lollipop but is it 5.0, 5.0.2 or 5.1?
Pretty good specs for under $300 id say.
fix-this! said:
Can anyone with the tmobile stylo confirm the 2gb ram and 13mp cam?
Im considering this over the g4, more budget friendly.
I have a few questions.
Hows the lcd? Does it show alot of pixelation? Im hearing its pretty good for 720p.
Does it have a notification led?
I know it has lollipop but is it 5.0, 5.0.2 or 5.1?
Pretty good specs for under $300 id say.
Click to expand...
Click to collapse
LCD is pretty good. I came from a G2 and don't notice any pixelation. Text and video quality is very good. It isn't as bright outdoors and doesn't have auto brightness but am pleased with it.
Camera is 13mp. Pictures seem better than my G2. Better focus.
Does have notification LED.
Running 5.0.2
It does have 2gb of RAM and performs similarly to my G2 before. WiFi and cell reception actually seem better also.
I think it is a pretty solid device for the price. I actually wish it were a little smaller but it is still relatively thin and light for the size.
Sent from my LG-H631 using XDA Free mobile app
i might pick one up today. anybody know if twrp is available so we can have a backup in case of a softbrick? hoping xda make a section for this device.
As far as TWRP no one has compiled it for this device yet. The device is pretty new so I would give it some time.
HTML:
ls -al /dev/block/bootdevice/by-name
lrwxrwxrwx root root 1970-01-01 21:24 DDR -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-01 21:24 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 21:24 abootbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-01 21:24 boot -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-01 21:24 cache -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-01 21:24 drm -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-01 21:24 eksst -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-01 21:24 encrypt -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-01 21:24 factory -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-01 21:24 fota -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-01 21:24 fsc -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-01 21:24 fsg -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-01 21:24 grow -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-01 21:24 hyp -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 21:24 hypbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-01 21:24 laf -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-01 21:24 metadata -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-01 21:24 misc -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-01 21:24 modem -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-01 21:24 modemst1 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-01 21:24 modemst2 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-01 21:24 mpt -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-01 21:24 pad -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 21:24 pad2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-01 21:24 persist -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-01 21:24 persistent -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-01 21:24 rct -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-01 21:24 recovery -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-01 21:24 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 21:24 rpmbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-01 21:24 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 21:24 sbl1bak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-01 21:24 sec -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-01 21:24 sns -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-01 21:24 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-01 21:24 system -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-01 21:24 tz -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 21:24 tzbak -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 21:24 userdata -> /dev/block/mmcblk0p38
[email protected]:/ $
heres the mounts for the tmobile lg g stylo.
and heres a system dump for the tmobile variant. might help get development going.
mega link: https://mega.co.nz/#!R1VwiLiA!GJ2O1Tw-pVw2P8QEHcpM0c464Qlq6Ro8CZty0YAkNs4
I took the plunge yesterday and got the T-Mobile variant. So far, it's been pretty nice. I would ding the camera app a star, though, since it doesn't seem to offer any manual exposure controls. You can choose between standard and HDR mode, and if HDR is off, you can chose off/manual/auto flash. I'm guessing they don't want to steal the G4's thunder. That being said, it takes very nice pictures, and the autofocus is nice and fast.
This morning, I had one glitch: Google Maps and Google Play Music weren't playing any sounds, even though I could hear sound effects when I tapped the screen. I rebooted and the problem went away, and haven't had any further trouble.
I like the screen - it's nice and bright and has good contrast. Sure, it's 720p instead of qHD, but it's plenty sharp for me. The phone seems nice and snappy, and doesn't seem laggy at all. It's nice that the T-Mobile version has 2 GB RAM and 16 GB internal storage.
From what I've seen so far, the battery should hold up nicely. However, the supplied 1.2A charger seems to run a bit hot. I'll be using the 2A charger that came with my Avant instead. I did make sure to unlock the Avant before upgrading; its supplied app unlocked the phone without any hassle.
Overall, for a budget phablet, it's quite good. I had been considering a ZTE Zmax, but I'm glad I held out for the Stylo, even if I rarely use the stylus.
I'm going to have to update my signature.
The lcd is my biggest issue. Even for 720p hd its got alot of pixelation on the fonts. My moto e 2015 actually renders better. :/ i assume this is becuase its a large lcd at 5.7". Wish lg would of gave it 1080p.
Its strong points are the camera and the overall design of the device, very sleek compared to the g3 or g4. Especially the back of the phone. Little choppy performance to but i suspect this is from the 5.0.2 memory leak.
Ill test for a few days before i decide if ill keep it or not. Good budget device though.
Anyone knows if the boot loader is unlocked? I expect the MetroPCS and T-Mobile variants to have one.
fix-this! said:
HTML:
ls -al /dev/block/bootdevice/by-name
lrwxrwxrwx root root 1970-01-01 21:24 DDR -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-01 21:24 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 21:24 abootbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-01 21:24 boot -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-01 21:24 cache -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-01 21:24 drm -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-01 21:24 eksst -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-01 21:24 encrypt -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-01 21:24 factory -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-01 21:24 fota -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-01 21:24 fsc -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-01 21:24 fsg -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-01 21:24 grow -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-01 21:24 hyp -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 21:24 hypbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-01 21:24 laf -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-01 21:24 metadata -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-01 21:24 misc -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-01 21:24 modem -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-01 21:24 modemst1 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-01 21:24 modemst2 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-01 21:24 mpt -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-01 21:24 pad -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 21:24 pad2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-01 21:24 persist -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-01 21:24 persistent -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-01 21:24 rct -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-01 21:24 recovery -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-01 21:24 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 21:24 rpmbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-01 21:24 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 21:24 sbl1bak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-01 21:24 sec -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-01 21:24 sns -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-01 21:24 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-01 21:24 system -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-01 21:24 tz -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 21:24 tzbak -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 21:24 userdata -> /dev/block/mmcblk0p38
[email protected]:/ $
heres the mounts for the tmobile lg g stylo.
Click to expand...
Click to collapse
Could I also get the output of adb shell cat proc/partitions and a backup of the recovery image. I'm going to unpack and repack the image which will cause the signature to change. If the bootloader is unlocked the image will still boot even after the signature has been modified.
Great to see more people on board. I'm almost positive the boot loader is locked by default. I tried to erase my laf and see if it would boot into fast boot but that was a no go. Let me know if anyone can access fast boot?
androidguy1991 said:
Great to see more people on board. I'm almost positive the boot loader is locked by default. I tried to erase my laf and see if it would boot into fast boot but that was a no go. Let me know if anyone can access fast boot?
Click to expand...
Click to collapse
Sounds like the same thing on the G4. What exactly happens after LAF is removed? I'm surprised the Send_Command root method worked for this device as it didn't for the G4.
When I removed laf it goes into the first download screen and says hold volume up to get into download mode or something like that. So I keep holding it and it does nothing. I tried to throw in some fast boot comments while its stuck on that screen and it does nothing. One thing I did find interesting is when you boot into stock recovery there is an option to reboot into bootloader but it just reboots the phone like normal.
Hello, everyone.
Since the ROM version on my OPT is not available for download (I got a phone with Oxygen 2.0.3), I decided to make a flashable image. This is the first time I do this, and I am kind of lost.
From this guide, I gathered that I need to find boot, kernel, system and misc partitions. Here are the partitions on OPT:
Code:
ls -al /dev/block/platform/f9824900.sdhci/by-name
lrwxrwxrwx root root 1970-01-24 09:32 DDR -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-24 09:32 DRIVER -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-24 09:32 LOGO -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-24 09:32 aboot -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-24 09:32 abootbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-24 09:32 apdp -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-24 09:32 bluetooth -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-24 09:32 boot -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-24 09:32 cache -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-24 09:32 config -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-24 09:32 devinfo -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-24 09:32 dpo -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-24 09:32 fsc -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-24 09:32 fsg -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-24 09:32 hyp -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-24 09:32 hypbak -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-24 09:32 keystore -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-24 09:32 limits -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-24 09:32 misc -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-24 09:32 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-24 09:32 modemst1 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-24 09:32 modemst2 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-24 09:32 msadp -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-24 09:32 oem_dycnvbk -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-24 09:32 oem_stanvbk -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-24 09:32 param -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-24 09:32 persist -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-24 09:32 pmic -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-24 09:32 pmicbak -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-24 09:32 recovery -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-24 09:32 reserve1 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-24 09:32 reserve2 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-24 09:32 rpm -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-24 09:32 rpmbak -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-24 09:32 sbl1 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-24 09:32 sbl1bak -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-24 09:32 sdi -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-24 09:32 sec -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-24 09:32 ssd -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-24 09:32 system -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-24 09:32 tz -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-24 09:32 tzbak -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-24 09:32 userdata -> /dev/block/mmcblk0p43
I see boot, system, and misc, but no kernel (there is kernel in the file system, though, I imagine it could be part of system), and I also see a bunch of strange names and a bunch of important-looking names.
Something tells me that Driver, DDR, Logo are somehow important and then there are modem and stuff, and tz looks important enough to back it up. Does anyone know what this all means? I saw links to stock Oxygen ROMs, so I imagine someone knows how to dump it.
Hey,
It's cool that you are trying to do this. Maybe try & send this guy a dm: Naman Bhalla
He's posted several other OxygenOS images, so I'm positive he can guide you in the process.
One interesting thing I noticed:
One OPT lets me connect ADB while it's in recovery rom. That is also automatically root if you do adb shell.
Another OPT does not let me connect with ADB at all. It also does not let me pick a proper ADB driver and insits on using a nexus driver instead. Very strange.
1. Is there anyone with an unlocked bootloader already tried to re-lock the bootloader und succeeded?
2. Anyone tried to re-flash stock B20 after that: boot, recovery and system using @tenfar 's tool?
Theoretically all that should be possiple by now, but is there anyone already succeeded?
My phone won' t be here any soon... Else I would give it a try by myself...
If anyone wants to try it, B20 files from a phone with a locked bootloader can be found here: http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
I'd be interested to see if any device flags change upon doing so.
rczrider said:
I'd be interested to see if any device flags change upon doing so.
Click to expand...
Click to collapse
Just my words, was going to add that , too :good:
Here's how to check: use "fastboot oem device-info"
That's the status on an unaltered A2017U:
Code:
C:\ADB>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.062s]
finished. total time: 0.062s
Thx to @DrakenFX
Btw: Did any of that change with ppl that rooted/TWRPed their phones, with or without unlocked bootloader?
Gachmuret said:
Just my words, was going to add that , too :good:
Here's how to check: use "fastboot oem device-info"
That's the status on an unaltered A2017U:
Code:
C:\ADB>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.062s]
finished. total time: 0.062s
Thx to @DrakenFX
Btw: Did any of that change with ppl that rooted/TWRPed their phones, with or without unlocked bootloader?
Click to expand...
Click to collapse
nop, hasn't change at all, still the same
Code:
C:\ADB>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.062s]
finished. total time: 0.062s
C:\ADB>fastboot reboot
rebooting...
finished. total time: 0.000s
C:\ADB>
and i'm Unlock Bootloader + Rooted + Xposed
I unlocked and immediately re-locked when I did it, just to see. It worked fine. Then I unlocked again, and proceeded to install TWRP, root, and xposed. So far, the only thing keeping me from returning to complete stock if I need to is the b20 bootloader. I haven't tried to reflash back, as I have no need right now. Hopefully, it stays that way.
Thx mate, you're the first to confirm that relocking actually works
BJHiltbrand said:
I haven't tried to reflash back, as I have no need right now. Hopefully, it stays that way.
Click to expand...
Click to collapse
Would be nice if someone tried to return to full stock after B20_boot, just to know if it works (it should, but let's confirm it)
BJHiltbrand said:
I unlocked and immediately re-locked when I did it, just to see. It worked fine. Then I unlocked again, and proceeded to install TWRP, root, and xposed. So far, the only thing keeping me from returning to complete stock if I need to is the b20 bootloader. I haven't tried to reflash back, as I have no need right now. Hopefully, it stays that way.
Click to expand...
Click to collapse
FWIW, we have the stock B20 bootloader.
rczrider said:
FWIW, we have the stock B20 bootloader.
Click to expand...
Click to collapse
You have the Stock B20 bootloader image?
where is it where
DrakenFX said:
You have the Stock B20 bootloader image?
where is it where
Click to expand...
Click to collapse
I thought someone had captured the B20 update (which I thought updated the bootloader). Not true?
rczrider said:
I thought someone had captured the B20 update (which I thought updated the bootloader). Not true?
Click to expand...
Click to collapse
LoL, man you're right
and i found where it go
Code:
package_extract_file("fastboot.img", "/dev/block/bootdevice/by-name/fbop");
mmmmmm i need to re-re-re-re-re-re-re-read some stuff and i'll give it a shot to get back to Stock B20 (Bootloader Lock), but i just need to re-x5-read so i wont screw this hehehehe
DrakenFX said:
LoL, man you're right
and i found where it go
Code:
package_extract_file("fastboot.img", "/dev/block/bootdevice/by-name/fbop");
mmmmmm i need to re-re-re-re-re-re-re-read some stuff and i'll give it a shot to get back to Stock B20 (Bootloader Lock), but i just need to re-x5-read so i wont screw this hehehehe
Click to expand...
Click to collapse
It's confusing! We have a lot of cross-talking in these threads.
If you can give me a link to the OTA, I can add it to my "stock B20" thread.
rczrider said:
It's confusing! We have a lot of cross-talking in these threads.
If you can give me a link to the OTA, I can add it to my "stock B20" thread.
Click to expand...
Click to collapse
mmmm i thought i had that on my thread, here you can use my download link...
update_P996A01_B18_to_B20_ssl.zip
and i'll update my Thread with this info
P.S. that zip file is flashable via Stock Recovery just in case there's someone still on B18
DrakenFX said:
mmmm i thought i had that on my thread, here you can use my download link...
update_P996A01_B18_to_B20_ssl.zip
and i'll update my Thread with this info
P.S. that zip file is flashable via Stock Recovery just in case there's someone still on B18
Click to expand...
Click to collapse
Oh, I meant that I'd just link to your thread. It's hard to find things (some of what I've been looking for has been in posts after the first)...I figure it can't hurt to redirect to other threads where appropriate. Thanks!
DrakenFX said:
LoL, man you're right
and i found where it go
Code:
package_extract_file("fastboot.img", "/dev/block/bootdevice/by-name/fbop");
mmmmmm i need to re-re-re-re-re-re-re-read some stuff and i'll give it a shot to get back to Stock B20 (Bootloader Lock), but i just need to re-x5-read so i wont screw this hehehehe
Click to expand...
Click to collapse
I am not sure what this fastboot image is for, i have only seen it used with Asus firmware. it is probably the fastboot command set. The bootloader is on the /aboot partition i believe and in the China firmwares thats the emmc_appsboot.mbn file. Looking at text in aboot aftre B20_Boot, it will look at fbop to see what command are available so aboot is more dynamic now then in Lollipop. I have not seen the aboot patched yet in our OTAs but unlocking might change it so it would be nice if we can dump it from unlocked for comparing with one we have on idlekernel. Not sure if it can be dumped from OS with root via dd or if it needs to be done from recovery via adb if TWRP does not recognize the partition
peramikic said:
I not sure what this fastboot image is for, i have only seen it used with Asus firmware. it is probably the fastboot command set. The bootloader is on the /aboot partition i believe and in the China firmwares thats the emmc_appsboot.mbn file. Looking at text in aboot aftre B20_Boot, it will look at fbop to see what command are available so aboot is more dynamic now then in Lollipop. I have not seen the aboot patched yet in our OTAs but unlocking might change it so it would be nice if we can dump it from unlocked for comparing with one we have on idlekernel. Not sure if it can be dumped from OS with root via dd or if it needs to be done from recovery via adb if TWRP does not recognize the partition
Click to expand...
Click to collapse
You mind typing the command here so I can copy and paste to try pulling the aboot from terminal?
nvm, I'll try using terminal and I'll upload the file.
DrakenFX said:
You mind typing the command here so I can copy and paste to try pulling the aboot from terminal?
Click to expand...
Click to collapse
If using adb, otherwise just last two lines in terminal
adb shell
su
dd if=/dev/block/bootdevice/by-name/aboot of=/sdcard/aboot.bin
you can probably dump others as well for backup if you want to. That image of your screen you posted when first BL OTA would not flash had the full list i think. Some are unique to phone and hold IMEI and keystore.
peramikic said:
If using adb, otherwise just last two lines in terminal
adb shell
su
dd if=/dev/block/bootdevice/by-name/aboot of=/sdcard/aboot.bin
you can probably dump others as well for backup if you want to. That image of your screen you posted when first BL OTA would not flash had the full list i think. Some are unique to phone and hold IMEI and keystore.
Click to expand...
Click to collapse
One Aboot.bin right up
https://www.mediafire.com/download/sri67r9wecw9xwv
I'll probably do, back not using my phone terminal LoL
Code:
[email protected]_ii:/ $ su
[email protected]_ii:/ # ls -al /dev/block/bootdevice/by-name
lrwxrwxrwx root root 1970-01-14 01:55 aboot -> /dev/block/sde11
lrwxrwxrwx root root 1970-01-14 01:55 apdp -> /dev/block/sde21
lrwxrwxrwx root root 1970-01-14 01:55 bluetooth -> /dev/block/sde16
lrwxrwxrwx root root 1970-01-14 01:55 boot -> /dev/block/sde12
lrwxrwxrwx root root 1970-01-14 01:55 cache -> /dev/block/sda2
lrwxrwxrwx root root 1970-01-14 01:55 cdt -> /dev/block/sdd2
lrwxrwxrwx root root 1970-01-14 01:55 cmnlib -> /dev/block/sde19
lrwxrwxrwx root root 1970-01-14 01:55 cmnlib64 -> /dev/block/sde20
lrwxrwxrwx root root 1970-01-14 01:55 cryptkey -> /dev/block/sda8
lrwxrwxrwx root root 1970-01-14 01:55 ddr -> /dev/block/sdd3
lrwxrwxrwx root root 1970-01-14 01:55 devcfg -> /dev/block/sda5
lrwxrwxrwx root root 1970-01-14 01:55 devinfo -> /dev/block/sde15
lrwxrwxrwx root root 1970-01-14 01:55 dip -> /dev/block/sde9
lrwxrwxrwx root root 1970-01-14 01:55 dpo -> /dev/block/sde23
lrwxrwxrwx root root 1970-01-14 01:55 dsp -> /dev/block/sde8
lrwxrwxrwx root root 1970-01-14 01:55 echarge -> /dev/block/sde25
lrwxrwxrwx root root 1970-01-14 01:55 fbop -> /dev/block/sda6
lrwxrwxrwx root root 1970-01-14 01:55 frp -> /dev/block/sda7
lrwxrwxrwx root root 1970-01-14 01:55 fsc -> /dev/block/sdf3
lrwxrwxrwx root root 1970-01-14 01:55 fsg -> /dev/block/sde4
lrwxrwxrwx root root 1970-01-14 01:55 hyp -> /dev/block/sde3
lrwxrwxrwx root root 1970-01-14 01:55 keymaster -> /dev/block/sde18
lrwxrwxrwx root root 1970-01-14 01:55 keystore -> /dev/block/sda4
lrwxrwxrwx root root 1970-01-14 01:55 lksecapp -> /dev/block/sde17
lrwxrwxrwx root root 1970-01-14 01:55 mdtp -> /dev/block/sde10
lrwxrwxrwx root root 1970-01-14 01:55 misc -> /dev/block/sda3
lrwxrwxrwx root root 1970-01-14 01:55 modem -> /dev/block/sde7
lrwxrwxrwx root root 1970-01-14 01:55 modemst1 -> /dev/block/sdf1
lrwxrwxrwx root root 1970-01-14 01:55 modemst2 -> /dev/block/sdf2
lrwxrwxrwx root root 1970-01-14 01:55 msadp -> /dev/block/sde22
lrwxrwxrwx root root 1970-01-14 01:55 persist -> /dev/block/sdf5
lrwxrwxrwx root root 1970-01-14 01:55 pmic -> /dev/block/sde6
lrwxrwxrwx root root 1970-01-14 01:55 recovery -> /dev/block/sde14
lrwxrwxrwx root root 1970-01-14 01:55 reserve -> /dev/block/sdd1
lrwxrwxrwx root root 1970-01-14 01:55 rpm -> /dev/block/sde1
lrwxrwxrwx root root 1970-01-14 01:55 sec -> /dev/block/sde5
lrwxrwxrwx root root 1970-01-14 01:55 splash -> /dev/block/sde24
lrwxrwxrwx root root 1970-01-14 01:55 ssd -> /dev/block/sda1
lrwxrwxrwx root root 1970-01-14 01:55 sti -> /dev/block/sde26
lrwxrwxrwx root root 1970-01-14 01:55 system -> /dev/block/sde13
lrwxrwxrwx root root 1970-01-14 01:55 tz -> /dev/block/sde2
lrwxrwxrwx root root 1970-01-14 01:55 userdata -> /dev/block/sda9
lrwxrwxrwx root root 1970-01-14 01:55 xbl -> /dev/block/sdb1
lrwxrwxrwx root root 1970-01-14 01:55 xblbak -> /dev/block/sdc1
lrwxrwxrwx root root 1970-01-14 01:55 ztecfg -> /dev/block/sdf4
[email protected]_ii:/ #
DrakenFX said:
One Aboot.bin right up
https://www.mediafire.com/download/sri67r9wecw9xwv
I'll probably do, back not using my phone terminal LoL
Code:
[email protected]_ii:/ $ su
[email protected]_ii:/ # ls -al /dev/block/bootdevice/by-name
lrwxrwxrwx root root 1970-01-14 01:55 aboot -> /dev/block/sde11
lrwxrwxrwx root root 1970-01-14 01:55 apdp -> /dev/block/sde21
lrwxrwxrwx root root 1970-01-14 01:55 bluetooth -> /dev/block/sde16
lrwxrwxrwx root root 1970-01-14 01:55 boot -> /dev/block/sde12
lrwxrwxrwx root root 1970-01-14 01:55 cache -> /dev/block/sda2
lrwxrwxrwx root root 1970-01-14 01:55 cdt -> /dev/block/sdd2
lrwxrwxrwx root root 1970-01-14 01:55 cmnlib -> /dev/block/sde19
lrwxrwxrwx root root 1970-01-14 01:55 cmnlib64 -> /dev/block/sde20
lrwxrwxrwx root root 1970-01-14 01:55 cryptkey -> /dev/block/sda8
lrwxrwxrwx root root 1970-01-14 01:55 ddr -> /dev/block/sdd3
lrwxrwxrwx root root 1970-01-14 01:55 devcfg -> /dev/block/sda5
lrwxrwxrwx root root 1970-01-14 01:55 devinfo -> /dev/block/sde15
lrwxrwxrwx root root 1970-01-14 01:55 dip -> /dev/block/sde9
lrwxrwxrwx root root 1970-01-14 01:55 dpo -> /dev/block/sde23
lrwxrwxrwx root root 1970-01-14 01:55 dsp -> /dev/block/sde8
lrwxrwxrwx root root 1970-01-14 01:55 echarge -> /dev/block/sde25
lrwxrwxrwx root root 1970-01-14 01:55 fbop -> /dev/block/sda6
lrwxrwxrwx root root 1970-01-14 01:55 frp -> /dev/block/sda7
lrwxrwxrwx root root 1970-01-14 01:55 fsc -> /dev/block/sdf3
lrwxrwxrwx root root 1970-01-14 01:55 fsg -> /dev/block/sde4
lrwxrwxrwx root root 1970-01-14 01:55 hyp -> /dev/block/sde3
lrwxrwxrwx root root 1970-01-14 01:55 keymaster -> /dev/block/sde18
lrwxrwxrwx root root 1970-01-14 01:55 keystore -> /dev/block/sda4
lrwxrwxrwx root root 1970-01-14 01:55 lksecapp -> /dev/block/sde17
lrwxrwxrwx root root 1970-01-14 01:55 mdtp -> /dev/block/sde10
lrwxrwxrwx root root 1970-01-14 01:55 misc -> /dev/block/sda3
lrwxrwxrwx root root 1970-01-14 01:55 modem -> /dev/block/sde7
lrwxrwxrwx root root 1970-01-14 01:55 modemst1 -> /dev/block/sdf1
lrwxrwxrwx root root 1970-01-14 01:55 modemst2 -> /dev/block/sdf2
lrwxrwxrwx root root 1970-01-14 01:55 msadp -> /dev/block/sde22
lrwxrwxrwx root root 1970-01-14 01:55 persist -> /dev/block/sdf5
lrwxrwxrwx root root 1970-01-14 01:55 pmic -> /dev/block/sde6
lrwxrwxrwx root root 1970-01-14 01:55 recovery -> /dev/block/sde14
lrwxrwxrwx root root 1970-01-14 01:55 reserve -> /dev/block/sdd1
lrwxrwxrwx root root 1970-01-14 01:55 rpm -> /dev/block/sde1
lrwxrwxrwx root root 1970-01-14 01:55 sec -> /dev/block/sde5
lrwxrwxrwx root root 1970-01-14 01:55 splash -> /dev/block/sde24
lrwxrwxrwx root root 1970-01-14 01:55 ssd -> /dev/block/sda1
lrwxrwxrwx root root 1970-01-14 01:55 sti -> /dev/block/sde26
lrwxrwxrwx root root 1970-01-14 01:55 system -> /dev/block/sde13
lrwxrwxrwx root root 1970-01-14 01:55 tz -> /dev/block/sde2
lrwxrwxrwx root root 1970-01-14 01:55 userdata -> /dev/block/sda9
lrwxrwxrwx root root 1970-01-14 01:55 xbl -> /dev/block/sdb1
lrwxrwxrwx root root 1970-01-14 01:55 xblbak -> /dev/block/sdc1
lrwxrwxrwx root root 1970-01-14 01:55 ztecfg -> /dev/block/sdf4
[email protected]_ii:/ #
Click to expand...
Click to collapse
That's post BL unlock, correct. I'll check it against the idlekernel one, should be identical
peramikic said:
That's post BL unlock, correct. I'll check it against the idlekernel one, should be identical
Click to expand...
Click to collapse
Yeah, unlock + rooted
DrakenFX said:
Yeah, unlock + rooted
Click to expand...
Click to collapse
Yup they are identical. We will need one from B20 virgin to compare