Related
LG F490 code name LG Liger. i don't know phone name.
We know F460 as Tiger. F490 as Liger. Is this another version G3 ?
Who needs a system dump pm me.
Odin 8 cores LG ̣(NUCLUN octa-core processor), 32 bit.
Support LTE Cat6
Ram 2GB
Camera 13MP (OIS+), with laser auto-focus and 2.1MP front camera
Battery: 3000mAh
157.8 x 81.8 x 9.45mm
Full HD, 5.9", 480 dpi
Android 4.4.4 (yep, not 4.4.2)
The CPU features four cores clocked at 1.2GHz and four cores clocked at 1.5GHz. GPU: PowerVR Series 6 (PowerVR Rogue Hood).
{
"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"
}
source: lgviet.com
partition info:
ls -la /dev/block/platform/20004000.sdhci/by-name/
lrwxrwxrwx root root 2014-10-22 20:48 BOOT -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-10-22 20:48 CABL -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-10-22 20:48 CABLB -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-10-22 20:48 CACHE -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2014-10-22 20:48 CPBL -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-10-22 20:48 CPBLB -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-10-22 20:48 DRM -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-10-22 20:48 DUMMY -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-10-22 20:48 DUMMY2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-10-22 20:48 EKSST -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-10-22 20:48 ENCRYPT -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-10-22 20:48 FACTORY -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-10-22 20:48 FOTA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-10-22 20:48 GROW -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2014-10-22 20:48 LAF -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-10-22 20:48 MISC -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-10-22 20:48 MODEMBIN -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-10-22 20:48 MODEMBNV -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-10-22 20:48 MODEMNV -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-10-22 20:48 MPT -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-10-22 20:48 MSBL -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-10-22 20:48 PERSIST -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-10-22 20:48 RCT -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-10-22 20:48 RECOVERY -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-10-22 20:48 SYSTEM -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2014-10-22 20:48 TEE -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-10-22 20:48 TEEB -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2014-10-22 20:48 USERDATA -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2014-10-22 20:48 VIDEO -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-10-22 20:48 VIDEOB -> /dev/block/mmcblk0p26
Click to expand...
Click to collapse
It's a smaller version like the Samsung active I think. Saw it today when I was at att actually
Sent from my LG-D850 using XDA Free mobile app
Any chance for some benchmarks? Would be nice to see what LG has come up with in their first SoC
wargreymon89 said:
Any chance for some benchmarks? Would be nice to see what LG has come up with in their first SoC
Click to expand...
Click to collapse
Aututu: 26.466 Not so good.
hoangnova said:
Aututu: 26.466 Not so good.
Click to expand...
Click to collapse
Not that crappy either. Any chance for 3DMark? Thanks for fast reply btw
wargreymon89 said:
Not that crappy either. Any chance for 3DMark? Thanks for fast reply btw
Click to expand...
Click to collapse
3D :crying::crying::crying::crying:
hoangnova said:
3D :crying::crying::crying::crying:
Click to expand...
Click to collapse
Doesnt look too promising :/ Mind testing 3DMark?
wargreymon89 said:
Doesnt look too promising :/ Mind testing 3DMark?
Click to expand...
Click to collapse
wait me
@hoangnova please check your PM regarding system dump
No lg device spotted with lgs new 5.2" screen with smaller edge?
Hey hoangnova dont u support G anymore? any hope for official L
I think its possible by lgs new update policy!
Gesendet von meinem E975 / Optimus G mit Tapatalk
hoangnova said:
wait me
Click to expand...
Click to collapse
help me!
to root F490 liger (LG G3 Screen lollipop 5.02)
thanks
Lollipop antutu 33k mark
Gửi từ LG-F490L của tôi bằng cách sử dụng Tapatalk
Let's collect and share some developer relevant infos about the h60.
KERNEL TOOLBOX:
http://forum.xda-developers.com/honor-6/orig-development/honor-6-kernel-toolbox-t3011000
Latest kernel sources and various stock ramdisks included.
Kernel sources for L01, L02, L03, L11, L12 and L21 are identical.
L04 doesn't boot using a kernel built from sources from above variants.
Seems to be different.
Code:
Kernel address 0x608000
Ramdisk address 0x300000
Secondary address 0x1500000
Kernel tags address 0x200000
Flash page size 2048
Command line "vmalloc=384M [email protected] psci=enable mmcparts=mmcblk0:p1(vrl),p2(vrl_backup),p7(modemnvm_factory),p18(splash),p22(dfx),p23(modemnvm_backup),p24(modemnvm_img),p25(modemnvm_system),p26(modem),p27(modem_dsp),p28(modem_om),p29(modemnvm_update),p30(3rdmodem),p31(3rdmodemnvm),p32(3rdmodemnvmbkp)"
Base: 0x00000000 || 0x001FFF00
Kernel offset: 0x00608000 || 0x00408100
Ramdisk offset: 0x00300000 || 0x00100100
Second offset: 0x01500000 || 0x00D00100
Tags offset: 0x00200000 || 0x00000100
RIL:
libbalong-ril.so and libbalong-ril-1.so are different across variants.
Everything else is identical.
SYSTEM:
build.prop - 6.94 KB from H60-L02V100R001CHNC00B310
PARTITIONS:
Code:
ls -al /dev/block/platform/ff1fe000.dwmmc0/by-name
lrwxrwxrwx root root 2015-01-16 16:33 3rdmodem -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2015-01-16 16:33 3rdmodemnvm -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2015-01-16 16:33 3rdmodemnvmbkp -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2015-01-16 16:33 boot -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-01-16 16:33 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 2015-01-16 16:33 cust -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 2015-01-16 16:33 dfx -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-01-16 16:33 dts -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-01-16 16:33 fastboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-01-16 16:33 fw_hifi -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-01-16 16:33 fw_lpm3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-01-16 16:33 hibench -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-01-16 16:33 hisitest0 -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2015-01-16 16:33 hisitest1 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2015-01-16 16:33 misc -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-01-16 16:33 modem -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2015-01-16 16:33 modem_dsp -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2015-01-16 16:33 modem_om -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2015-01-16 16:33 modemnvm_backup -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-01-16 16:33 modemnvm_factory -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-01-16 16:33 modemnvm_img -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2015-01-16 16:33 modemnvm_system -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2015-01-16 16:33 modemnvm_update -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2015-01-16 16:33 nvme -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-01-16 16:33 oeminfo -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-01-16 16:33 recovery -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-01-16 16:33 recovery2 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-01-16 16:33 reserved1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-01-16 16:33 reserved2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-01-16 16:33 secure_storage -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-01-16 16:33 sensorhub -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-01-16 16:33 splash -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-01-16 16:33 splash2 -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2015-01-16 16:33 splash3 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-01-16 16:33 system -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 2015-01-16 16:33 teeos -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-01-16 16:33 userdata -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 2015-01-16 16:33 vrl -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-01-16 16:33 vrl_backup -> /dev/block/mmcblk0p2
Code:
cat /proc/partitions
major minor #blocks name
7 0 13545 loop0
7 1 49928 loop1
179 0 15267840 mmcblk0
179 1 128 mmcblk0p1
179 2 128 mmcblk0p2
179 3 1664 mmcblk0p3
179 4 1792 mmcblk0p4
179 5 256 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 4096 mmcblk0p7
179 8 2048 mmcblk0p8
179 9 4096 mmcblk0p9
179 10 2048 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 8192 mmcblk0p13
179 14 15360 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 32768 mmcblk0p16
179 17 32768 mmcblk0p17
179 18 8192 mmcblk0p18
179 19 8192 mmcblk0p19
179 20 32768 mmcblk0p20
179 21 20480 mmcblk0p21
179 22 8192 mmcblk0p22
179 23 4096 mmcblk0p23
179 24 8192 mmcblk0p24
179 25 4096 mmcblk0p25
179 26 61440 mmcblk0p26
179 27 4096 mmcblk0p27
179 28 12288 mmcblk0p28
179 29 24576 mmcblk0p29
179 30 131072 mmcblk0p30
179 31 32768 mmcblk0p31
179 32 16384 mmcblk0p32
179 33 65536 mmcblk0p33
179 34 2048 mmcblk0p34
179 35 2048 mmcblk0p35
179 36 524288 mmcblk0p36
179 37 1572864 mmcblk0p37
179 38 262144 mmcblk0p38
179 39 12339200 mmcblk0p39
179 120 4096 mmcblk0rpmb
179 80 4096 mmcblk0boot1
179 40 4096 mmcblk0boot0
31 0 128 mtdblock0
31 1 128 mtdblock1
31 2 4096 mtdblock2
31 3 4096 mtdblock3
31 4 4096 mtdblock4
31 5 61440 mtdblock5
31 6 4096 mtdblock6
31 7 24576 mtdblock7
179 160 15646720 mmcblk1
179 161 15642624 mmcblk1p1
31 8 4096 mtdblock8
253 0 13545 dm-0
253 1 49927 dm-1
@codeworkx Very useful information for the developers...! Have you tried to build a CM. Or at least a cwm recovery...?
root-expert said:
@codeworkx Very useful information for the developers...! Have you tried to build a CM. Or at least a cwm recovery...?
Click to expand...
Click to collapse
1st step: unpack stock boot image, repack it, boot it
2nd step: build kernel from sources, pack it with stock ramdisk, boot it
3rd step: start brewing cm
Just to make it clear.
I don't own a honor 6 so i'll not do any development.
It's up to the community.
Had a look at their kernel sources and tried to build it.
This is a pure mess. I've never seen such a chaos before.
Is it even worse than mtk?
Sent from my H60-L02 using Tapatalk
Problem is that the community for this device is really small, at least the potential developer part of it. Additionally, I'm trying to build CM for it but damn is it a hassle as a newbie..
codeworkx said:
Just to make it clear.
I don't own a honor 6 so i'll not do any development.
It's up to the community.
Had a look at their kernel sources and tried to build it.
This is a pure mess. I've never seen such a chaos before.
Click to expand...
Click to collapse
Thanks very much for your interest!!
I'm reading more guides about CM buildilng from source and I started to set up my computer.
Than I signed on Github and I found your dir.
I googled you before I'he found this thread: I'm really honored of Your concern about Honor 6!
We started a petition too, in order to involve our community and devs and start the development of this device.
Like @panamera2011 said, it would be really great if someone like you, began to support our work!
You're right, almost all developers continue to buy the same devices because with cpu Qualcom is easier to build rom cm
nrpetonr said:
Is it even worse than mtk?
Sent from my H60-L02 using Tapatalk
Click to expand...
Click to collapse
for me it's all the same.
mtk, rockchip, hisilicon....
their kernel sources are a pure accident und the community support is below zero.
and it seems that huawei doesn't make it better.
panamera2011 said:
You're right, almost all developers continue to buy the same devices because with cpu Qualcom is easier to build rom cm
Click to expand...
Click to collapse
Maybe not easier, but there's documentation and sourcecode available.
That's a huge difference.
codeworkx said:
for me it's all the same.
mtk, rockchip, hisilicon....
their kernel sources are a pure accident und the community support is below zero.
and it seems that huawei doesn't make it better.
Click to expand...
Click to collapse
What do you mean by pure accident ? As in really messy coding ?
Didn't have a close look at their code.
The way the hisilocon drivers are organized is messy. And it seems they've copied parts of the userspace into the kernel. That stuff doesn't belong there.
And they've copied samsungs exfat driver from one of the i9100 custom kernels.
I'm not able to build the kernel with enabled balong modem stuff because of their mess.
codeworkx said:
Didn't have a close look at their code.
The way the hisilocon drivers are organized is messy. And it seems they've copied parts of the userspace into the kernel. That stuff doesn't belong there.
And they've copied samsungs exfat driver from one of the i9100 custom kernels.
I'm not able to build the kernel with enabled balong modem stuff because of their mess.
Click to expand...
Click to collapse
Sounds like chaos as you described earlier.. Its too bad that things have been built this way. Would getting information from honor (aka huawei) help ? And if so what information would that be ?
Honor is quite close to the community over on a French forum I'm a member of and they seem to be eager to make a good impression for their phones on the European market so I'm pretty sure they wouldn't mind sharing information as custom ROM development is quite a big deal for android devices and if they get into that their market shares would explode considering how well the phone has been doing so far..! What's missing is really this customisation ..!
Dervisk said:
Sounds like chaos as you described earlier.. Its too bad that things have been built this way. Would getting information from honor (aka huawei) help ? And if so what information would that be ?
Honor is quite close to the community over on a French forum I'm a member of and they seem to be eager to make a good impression for their phones on the European market so I'm pretty sure they wouldn't mind sharing information as custom ROM development is quite a big deal for android devices and if they get into that their market shares would explode considering how well the phone has been doing so far..! What's missing is really this customisation ..!
Click to expand...
Click to collapse
I've already written a mail to huawei. let's see how it goes.
some more information.
@codeworkx
some more information to complete OP that user @spanorg could collect following that thread http://forum.xda-developers.com/showthread.php?t=2450045.
http://pastebin.com/xSuphPVT
http://pastebin.com/pwknz0FA
i attached them in that post as zip cos pastebin is not eternal. xD
desalesouche said:
@codeworkx
some more information to complete OP that user @spanorg could collect following that thread http://forum.xda-developers.com/showthread.php?t=2450045.
http://pastebin.com/xSuphPVT
http://pastebin.com/pwknz0FA
i attached them in that post as zip cos pastebin is not eternal. xD
Click to expand...
Click to collapse
@desalesouche what model of Honor 6 uses?
I use H60-L02
panamera2011 said:
@desalesouche what model of Honor 6 uses?
I use H60-L02
Click to expand...
Click to collapse
from what i know @spanorg use L02
just 4 info:
the kernel sourcecode release from huawei is incomplete and broken.
they didn't release needed tools which they've used to build the kernel and there are some missing vxworks headers.
if you've managed to build a kernel, then baseband and audio will be dead.
i've written a mail. let's see what happens.
Is it possible to built a cm version and use the available compiled kernel?
Julsen1985 said:
Is it possible to built a cm version and use the available compiled kernel?
Click to expand...
Click to collapse
yes, but radio and audio might be broken.
can't say for sure. i've still no honor 6.
Hi guys,
there are tones of LG G4 phones that are bricked, i have tested a technic to get them back to life ( tested with H811) , but such a technic needs Emmc dumps ( all mmcblk0 partitions except userdata cache data and system ) so please i propose to make a database of all G4 dumps in Google drive or somewhere else to help people having bricked LG G4 phones
For me i need H815 dump now
Thanks
leptdre said:
Hi guys,
there are tones of LG G4 phones that are bricked, i have tested a technic to get them back to life ( tested with H811) , but such a technic needs Emmc dumps ( all mmcblk0 partitions except userdata cache data and system ) so please i propose to make a database of all G4 dumps in Google drive or somewhere else to help people having bricked LG G4 phones
For me i need H815 dump now
Thanks
Click to expand...
Click to collapse
Tell me more of your technique? I have an H811 sitting here that could use that. Is it copying the partition table to a microSD card? I've not had luck with that so far, maybe you could elucidate? Thanks!
I'm working on getting some firehose action going on. I think I've got most of the code and tools necessary to prepare the custom files needed, but it's such a steep task, especially as I don't understand its ways yet.
pretty sure we need root for this..
there's alot of interesting file here
http://downloads.codefi.re/autoprime/LG/LG_G4
leptdre said:
Hi guys,
there are tones of LG G4 phones that are bricked, i have tested a technic to get them back to life ( tested with H811) , but such a technic needs Emmc dumps ( all mmcblk0 partitions except userdata cache data and system ) so please i propose to make a database of all G4 dumps in Google drive or somewhere else to help people having bricked LG G4 phones
For me i need H815 dump now
Thanks
Click to expand...
Click to collapse
For now, here you have a list of all particions into 'mmcblk0':
HTML:
Number Start End Size File_system Name
1 16777216B 106954751B 90177536B fat16 modem
2 117440512B 117964799B 524288B pmic
3 117964800B 119013375B 1048576B sbl1
4 119013376B 120061951B 1048576B tz
5 120061952B 120586239B 524288B sdi
6 120586240B 121110527B 524288B hyp
7 121110528B 121634815B 524288B rpm
8 121634816B 123731967B 2097152B aboot
9 123731968B 124780543B 1048576B sbl1bak
10 124780544B 125304831B 524288B pmicbak
11 125304832B 126353407B 1048576B tzbak
12 126353408B 126877695B 524288B hypbak
13 126877696B 127401983B 524288B rpmbak
14 127401984B 129499135B 2097152B abootbak
15 129499136B 130023423B 524288B sdibak
16 130023424B 130547711B 524288B limits
17 130547712B 131071999B 524288B devinfo
18 131072000B 131596287B 524288B apdp
19 131596288B 132120575B 524288B msadp
20 132120576B 132644863B 524288B dpo
21 132644864B 134217727B 1572864B spare1
22 134217728B 150994943B 16777216B misc
23 150994944B 184549375B 33554432B ext4 persist
24 184549376B 186122239B 1572864B modemst1
25 186122240B 187695103B 1572864B modemst2
26 187695104B 189267967B 1572864B fsg
27 189267968B 189792255B 524288B fsc
28 189792256B 190316543B 524288B ssd
29 190316544B 190840831B 524288B keystore
30 190840832B 192937983B 2097152B DDR
31 192937984B 193462271B 524288B sec
32 193462272B 193986559B 524288B encrypt
33 193986560B 194510847B 524288B eksst
34 194510848B 195035135B 524288B rct
35 195035136B 197132287B 2097152B persistent
36 197132288B 201326591B 4194304B spare2
37 201326592B 251658239B 50331648B laf
38 251658240B 293601279B 41943040B boot
39 293601280B 335544319B 41943040B recovery
40 335544320B 343932927B 8388608B ext4 drm
41 343932928B 352321535B 8388608B ext4 sns
42 352321536B 385875967B 33554432B ext4 mpt
43 385875968B 434110463B 48234496B factory
44 434110464B 444596223B 10485760B fota
45 444596224B 448790527B 4194304B raw_resources
46 448790528B 452984831B 4194304B raw_resourcesbak
47 452984832B 4794089471B 4341104640B ext4 system
48 4794089472B 5062524927B 268435456B ext4 cust
49 5066719232B 6358564863B 1291845632B ext4 cache
50 6358564864B 31255953407B 24897388544B ext4 userdata
51 31255953408B 31268519423B 12566016B grow
Variant: H811
Version: v20o
fdisk --> list:
Code:
Disk /dev/block/mmcblk0: 61071360 sectors, 1148M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 56 entries
First usable sector is 34, last usable sector is 61071326
Number Start (sector) End (sector) Size Code Name
1 32768 208895 86.0M 0700 modem
2 229376 230399 512K 0700 pmic
3 230400 232447 1024K 0700 sbl1
4 232448 234495 1024K 0700 tz
5 234496 235519 512K 0700 sdi
6 235520 236543 512K 0700 hyp
7 236544 237567 512K 0700 rpm
8 237568 241663 2048K 0700 aboot
9 241664 243711 1024K 0700 sbl1bak
10 243712 244735 512K 0700 pmicbak
11 244736 246783 1024K 0700 tzbak
12 246784 247807 512K 0700 hypbak
13 247808 248831 512K 0700 rpmbak
14 248832 252927 2048K 0700 abootbak
15 252928 253951 512K 0700 sdibak
16 253952 254975 512K 0700 limits
17 254976 255999 512K 0700 devinfo
18 256000 257023 512K 0700 apdp
19 257024 258047 512K 0700 msadp
20 258048 259071 512K 0700 dpo
21 259072 262143 1536K 0700 spare1
22 262144 294911 16.0M 0700 misc
23 294912 360447 32.0M 0700 persist
24 360448 363519 1536K 0700 modemst1
25 363520 366591 1536K 0700 modemst2
26 366592 369663 1536K 0700 fsg
27 369664 370687 512K 0700 fsc
28 370688 371711 512K 0700 ssd
29 371712 372735 512K 0700 keystore
30 372736 376831 2048K 0700 DDR
31 376832 377855 512K 0700 sec
32 377856 378879 512K 0700 encrypt
33 378880 379903 512K 0700 eksst
34 379904 380927 512K 0700 rct
35 380928 385023 2048K 0700 persistent
36 385024 393215 4096K 0700 spare2
37 393216 491519 48.0M 0700 laf
38 491520 573439 40.0M 0700 boot
39 573440 655359 40.0M 0700 recovery
40 655360 671743 8192K 0700 drm
41 671744 688127 8192K 0700 sns
42 688128 753663 32.0M 0700 mpt
43 753664 770047 8192K 0700 eri
44 770048 778239 4096K 0700 raw_resources
45 778240 786431 4096K 0700 raw_resourcesbak
46 786432 819199 16.0M 0700 operatorlogging
47 819200 901119 40.0M 0700 carrier
48 901120 917503 8192K 0700 felica
49 917504 1011711 46.0M 0700 factory
50 1011712 1015807 2048K 0700 spare3
51 1015808 1036287 10.0M 0700 fota
52 1036288 1048575 6144K 0700 spare4
53 1048576 9822207 4284M 0700 system
54 9822208 12345343 1232M 0700 cache
55 12345344 61046783 23.2G 0700 userdata
56 61046784 61071326 11.9M 0700 grow
parted --> print:
Code:
Model: MMC 032G74 (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name F
1 16.8MB 107MB 90.2MB fat16 modem
2 117MB 118MB 524kB pmic
3 118MB 119MB 1049kB sbl1
4 119MB 120MB 1049kB tz
5 120MB 121MB 524kB sdi
6 121MB 121MB 524kB hyp
7 121MB 122MB 524kB rpm
8 122MB 124MB 2097kB aboot
9 124MB 125MB 1049kB sbl1bak
10 125MB 125MB 524kB pmicbak
11 125MB 126MB 1049kB tzbak
12 126MB 127MB 524kB hypbak
13 127MB 127MB 524kB rpmbak
14 127MB 129MB 2097kB abootbak
15 129MB 130MB 524kB sdibak
16 130MB 131MB 524kB limits
17 131MB 131MB 524kB devinfo
18 131MB 132MB 524kB apdp
19 132MB 132MB 524kB msadp
20 132MB 133MB 524kB dpo
21 133MB 134MB 1573kB spare1
22 134MB 151MB 16.8MB misc
23 151MB 185MB 33.6MB ext4 persist
24 185MB 186MB 1573kB modemst1
25 186MB 188MB 1573kB modemst2
26 188MB 189MB 1573kB fsg
27 189MB 190MB 524kB fsc
28 190MB 190MB 524kB ssd
29 190MB 191MB 524kB keystore
30 191MB 193MB 2097kB DDR
31 193MB 193MB 524kB sec
32 193MB 194MB 524kB encrypt
33 194MB 195MB 524kB eksst
34 195MB 195MB 524kB rct
35 195MB 197MB 2097kB persistent
36 197MB 201MB 4194kB spare2
37 201MB 252MB 50.3MB laf
38 252MB 294MB 41.9MB boot
39 294MB 336MB 41.9MB recovery
40 336MB 344MB 8389kB ext4 drm
41 344MB 352MB 8389kB ext4 sns
42 352MB 386MB 33.6MB ext4 mpt
43 386MB 394MB 8389kB eri
44 394MB 398MB 4194kB raw_resources
45 398MB 403MB 4194kB raw_resourcesbak
46 403MB 419MB 16.8MB operatorlogging
47 419MB 461MB 41.9MB carrier
48 461MB 470MB 8389kB felica
49 470MB 518MB 48.2MB factory
50 518MB 520MB 2097kB spare3
51 520MB 531MB 10.5MB fota
52 531MB 537MB 6291kB spare4
53 537MB 5029MB 4492MB ext4 system
54 5029MB 6321MB 1292MB ext4 cache
55 6321MB 31.3GB 24.9GB ext4 userdata
56 31.3GB 31.3GB 12.6MB grow
---
Diagnosis: 9008, non-ILAPO, caused by me accidentally flashing the v20i bootstack.
I [shoddily] customized gpt_parser.py(based on source from here) to create partition.xml, which I then fed to ptool.py (source) to create the rawprogram0.xml and patch0.xml. Then I fed those into msp.py to create a singleimage.bin that I dd'd over to a microSD card. I inserted the microSD and surprisingly enough my G4 sprang to life instantly!
I booted into TWRP to copy over the what I thought were the correct v20o images to correct the faulty v20i images I had initially used to kill the mofo. That seems to have resulted in a total brick, when I rebooted there was no signs of life at all now, no 9008, no USB peeps at all now. But! the microSD card trick did bring it back from 9008, only it seems I shucked when I should have jived. (me >= woe.)
So maybe I flashed the wrong images *again*? Goddamnit. I should have dipped right into LAF download mode and flashed the stock KDZ. I've been a fool.
Anyway, I'm including the files I used to make all this happen in case anyone finds them useful: [download]
It turns out creating the partition.xml, rawprogram0.xml, and patch0.xml is incredibly simple. Too bad I could not get Firehose to work, it kept throwing this error at me whenever I tried:
Code:
{ERROR: OpenPort:4197 It took 10.01600000 seconds to open port. Which is longer than 3.000. This indicates your target is not stable
I *was* using a firehose 8992_lite.mbn file from who knows where, that could be why maybe? That is one file I'm not sure how to create yet, though the code to create it is in the same repo at the ptool.py link I posted above.
culot said:
Variant: H811
Version: v20o
fdisk --> list:
Code:
Disk /dev/block/mmcblk0: 61071360 sectors, 1148M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 56 entries
First usable sector is 34, last usable sector is 61071326
Number Start (sector) End (sector) Size Code Name
1 32768 208895 86.0M 0700 modem
2 229376 230399 512K 0700 pmic
3 230400 232447 1024K 0700 sbl1
4 232448 234495 1024K 0700 tz
5 234496 235519 512K 0700 sdi
6 235520 236543 512K 0700 hyp
7 236544 237567 512K 0700 rpm
8 237568 241663 2048K 0700 aboot
9 241664 243711 1024K 0700 sbl1bak
10 243712 244735 512K 0700 pmicbak
11 244736 246783 1024K 0700 tzbak
12 246784 247807 512K 0700 hypbak
13 247808 248831 512K 0700 rpmbak
14 248832 252927 2048K 0700 abootbak
15 252928 253951 512K 0700 sdibak
16 253952 254975 512K 0700 limits
17 254976 255999 512K 0700 devinfo
18 256000 257023 512K 0700 apdp
19 257024 258047 512K 0700 msadp
20 258048 259071 512K 0700 dpo
21 259072 262143 1536K 0700 spare1
22 262144 294911 16.0M 0700 misc
23 294912 360447 32.0M 0700 persist
24 360448 363519 1536K 0700 modemst1
25 363520 366591 1536K 0700 modemst2
26 366592 369663 1536K 0700 fsg
27 369664 370687 512K 0700 fsc
28 370688 371711 512K 0700 ssd
29 371712 372735 512K 0700 keystore
30 372736 376831 2048K 0700 DDR
31 376832 377855 512K 0700 sec
32 377856 378879 512K 0700 encrypt
33 378880 379903 512K 0700 eksst
34 379904 380927 512K 0700 rct
35 380928 385023 2048K 0700 persistent
36 385024 393215 4096K 0700 spare2
37 393216 491519 48.0M 0700 laf
38 491520 573439 40.0M 0700 boot
39 573440 655359 40.0M 0700 recovery
40 655360 671743 8192K 0700 drm
41 671744 688127 8192K 0700 sns
42 688128 753663 32.0M 0700 mpt
43 753664 770047 8192K 0700 eri
44 770048 778239 4096K 0700 raw_resources
45 778240 786431 4096K 0700 raw_resourcesbak
46 786432 819199 16.0M 0700 operatorlogging
47 819200 901119 40.0M 0700 carrier
48 901120 917503 8192K 0700 felica
49 917504 1011711 46.0M 0700 factory
50 1011712 1015807 2048K 0700 spare3
51 1015808 1036287 10.0M 0700 fota
52 1036288 1048575 6144K 0700 spare4
53 1048576 9822207 4284M 0700 system
54 9822208 12345343 1232M 0700 cache
55 12345344 61046783 23.2G 0700 userdata
56 61046784 61071326 11.9M 0700 grow
parted --> print:
Code:
Model: MMC 032G74 (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name F
1 16.8MB 107MB 90.2MB fat16 modem
2 117MB 118MB 524kB pmic
3 118MB 119MB 1049kB sbl1
4 119MB 120MB 1049kB tz
5 120MB 121MB 524kB sdi
6 121MB 121MB 524kB hyp
7 121MB 122MB 524kB rpm
8 122MB 124MB 2097kB aboot
9 124MB 125MB 1049kB sbl1bak
10 125MB 125MB 524kB pmicbak
11 125MB 126MB 1049kB tzbak
12 126MB 127MB 524kB hypbak
13 127MB 127MB 524kB rpmbak
14 127MB 129MB 2097kB abootbak
15 129MB 130MB 524kB sdibak
16 130MB 131MB 524kB limits
17 131MB 131MB 524kB devinfo
18 131MB 132MB 524kB apdp
19 132MB 132MB 524kB msadp
20 132MB 133MB 524kB dpo
21 133MB 134MB 1573kB spare1
22 134MB 151MB 16.8MB misc
23 151MB 185MB 33.6MB ext4 persist
24 185MB 186MB 1573kB modemst1
25 186MB 188MB 1573kB modemst2
26 188MB 189MB 1573kB fsg
27 189MB 190MB 524kB fsc
28 190MB 190MB 524kB ssd
29 190MB 191MB 524kB keystore
30 191MB 193MB 2097kB DDR
31 193MB 193MB 524kB sec
32 193MB 194MB 524kB encrypt
33 194MB 195MB 524kB eksst
34 195MB 195MB 524kB rct
35 195MB 197MB 2097kB persistent
36 197MB 201MB 4194kB spare2
37 201MB 252MB 50.3MB laf
38 252MB 294MB 41.9MB boot
39 294MB 336MB 41.9MB recovery
40 336MB 344MB 8389kB ext4 drm
41 344MB 352MB 8389kB ext4 sns
42 352MB 386MB 33.6MB ext4 mpt
43 386MB 394MB 8389kB eri
44 394MB 398MB 4194kB raw_resources
45 398MB 403MB 4194kB raw_resourcesbak
46 403MB 419MB 16.8MB operatorlogging
47 419MB 461MB 41.9MB carrier
48 461MB 470MB 8389kB felica
49 470MB 518MB 48.2MB factory
50 518MB 520MB 2097kB spare3
51 520MB 531MB 10.5MB fota
52 531MB 537MB 6291kB spare4
53 537MB 5029MB 4492MB ext4 system
54 5029MB 6321MB 1292MB ext4 cache
55 6321MB 31.3GB 24.9GB ext4 userdata
56 31.3GB 31.3GB 12.6MB grow
---
Diagnosis: 9008, non-ILAPO, caused by me accidentally flashing the v20i bootstack.
I [shoddily] customized gpt_parser.py(based on source from here) to create partition.xml, which I then fed to ptool.py (source) to create the rawprogram0.xml and patch0.xml. Then I fed those into msp.py to create a singleimage.bin that I dd'd over to a microSD card. I inserted the microSD and surprisingly enough my G4 sprang to life instantly!
I booted into TWRP to copy over the what I thought were the correct v20o images to correct the faulty v20i images I had initially used to kill the mofo. That seems to have resulted in a total brick, when I rebooted there was no signs of life at all now, no 9008, no USB peeps at all now. But! the microSD card trick did bring it back from 9008, only it seems I shucked when I should have jived. (me >= woe.)
So maybe I flashed the wrong images *again*? Goddamnit. I should have dipped right into LAF download mode and flashed the stock KDZ. I've been a fool.
Anyway, I'm including the files I used to make all this happen in case anyone finds them useful: [download]
It turns out creating the partition.xml, rawprogram0.xml, and patch0.xml is incredibly simple. Too bad I could not get Firehose to work, it kept throwing this error at me whenever I tried:
Code:
{ERROR: OpenPort:4197 It took 10.01600000 seconds to open port. Which is longer than 3.000. This indicates your target is not stable
I *was* using a firehose 8992_lite.mbn file from who knows where, that could be why maybe? That is one file I'm not sure how to create yet, though the code to create it is in the same repo at the ptool.py link I posted above.
Click to expand...
Click to collapse
i just wan ask a simple question. If you didn't see a signe of the EMMC memory, so why you bother creating rawprogram etc , i had the same phone , i downgraded from 10N , and i had a hard brick . i was able to turn it back on by the SDcard methode and never been able to see the emmc in TWRP ( /dev directory)
Emmc was fully fleshed out, I perused it before I began dd'ing partitions over to it. Everything seemed normal.
For the H815 variant. I found a working Dump that i flashed into an SD card. I was able to enter download mode and flash a firmware. but as expected the firmware goes to the SD card and the phone is unstable. I have IMEI = 0 and i could not unlock the bootloader.
Bottom line. Ithink that there is some hope of getting the phone to detects the EMMC memory, i dont know how may be a hardware switch or some custum SD card.
I hope that it will soon available
culot said:
Emmc was fully fleshed out, I perused it before I began dd'ing partitions over to it. Everything seemed normal.
Click to expand...
Click to collapse
what did you do to get the 9008 mode working please share :'(
leptdre said:
what did you do to get the 9008 mode working please share :'(
Click to expand...
Click to collapse
It's all right there in my post. Not sure what else to say.? ?
culot said:
It's all right there in my post. Not sure what else to say.? ��
Click to expand...
Click to collapse
i want to know what software did you use and did the phone show sign of life without SD card , cause i have a H811 that i got working with just the SD card and no tweaking what so ever
leptdre said:
i want to know what software did you use and did the phone show sign of life without SD card , cause i have a H811 that i got working with just the SD card and no tweaking what so ever
Click to expand...
Click to collapse
The software I used is detailed in my above post. If you have any specific questions about that let me know.
It was the typical 9008 mode, no signs of life other than showing a 9008 port when USB was plugged in -- that's with no SD card.
I inserted the microSD I formatted with the singleimage.bin, then as soon as I inserted the battery the phone gave its little vibe and began to boot normally. I rebooted into TWRP so I could flash the proper partitions, and then after I rebooted it was dead. Apparently I flashed the wrong ones? I'm not sure, but the microSD trick definitely worked to get it into a state where repair is possible. I should have put it into LAF download mode and flashed a KDZ.
I was overconfident, thinking that no matter what I'd be able to bring it back with that same microSD card. That is not the case: it turns out that whatever I flashed has well and truly bricked it, as now it shows no life signs at all. I was careless, stupid, reckless. So close!
How did you microSD method work? Just flashed full image to the microSD? Details and files are always nice.
culot said:
The software I used is detailed in my above post. If you have any specific questions about that let me know.
It was the typical 9008 mode, no signs of life other than showing a 9008 port when USB was plugged in -- that's with no SD card.
I inserted the microSD I formatted with the singleimage.bin, then as soon as I inserted the battery the phone gave its little vibe and began to boot normally. I rebooted into TWRP so I could flash the proper partitions, and then after I rebooted it was dead. Apparently I flashed the wrong ones? I'm not sure, but the microSD trick definitely worked to get it into a state where repair is possible. I should have put it into LAF download mode and flashed a KDZ.
I was overconfident, thinking that no matter what I'd be able to bring it back with that same microSD card. That is not the case: it turns out that whatever I flashed has well and truly bricked it, as now it shows no life signs at all. I was careless, stupid, reckless. So close!
How did you microSD method work? Just flashed full image to the microSD? Details and files are always nice.
Click to expand...
Click to collapse
1- first you need to resize you micro sd card with SD formatter ( give it its original size)
2- you must low level format it ( not quick format )
3- flash your bin file with win 32 Disk imager ( or DD command in linux ) ( if you dont have a working dump i will upload this evening)
4- put the sd card into the phone , put the battery on , press vol up button and plug a usb cable
5- now you will be able to enter download mode and flash a firmware using LG UP ( flash 10N or above )
obviously the firmware is going to the SD card , from twrp i listed the /dev/block directory , i found no sign of the EMMC memory what so ever, if someone happen to find it please share
culot said:
Variant: H811
Version: v20o
fdisk --> list:
Code:
Disk /dev/block/mmcblk0: 61071360 sectors, 1148M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 56 entries
First usable sector is 34, last usable sector is 61071326
Number Start (sector) End (sector) Size Code Name
1 32768 208895 86.0M 0700 modem
2 229376 230399 512K 0700 pmic
3 230400 232447 1024K 0700 sbl1
4 232448 234495 1024K 0700 tz
5 234496 235519 512K 0700 sdi
6 235520 236543 512K 0700 hyp
7 236544 237567 512K 0700 rpm
8 237568 241663 2048K 0700 aboot
9 241664 243711 1024K 0700 sbl1bak
10 243712 244735 512K 0700 pmicbak
11 244736 246783 1024K 0700 tzbak
12 246784 247807 512K 0700 hypbak
13 247808 248831 512K 0700 rpmbak
14 248832 252927 2048K 0700 abootbak
15 252928 253951 512K 0700 sdibak
16 253952 254975 512K 0700 limits
17 254976 255999 512K 0700 devinfo
18 256000 257023 512K 0700 apdp
19 257024 258047 512K 0700 msadp
20 258048 259071 512K 0700 dpo
21 259072 262143 1536K 0700 spare1
22 262144 294911 16.0M 0700 misc
23 294912 360447 32.0M 0700 persist
24 360448 363519 1536K 0700 modemst1
25 363520 366591 1536K 0700 modemst2
26 366592 369663 1536K 0700 fsg
27 369664 370687 512K 0700 fsc
28 370688 371711 512K 0700 ssd
29 371712 372735 512K 0700 keystore
30 372736 376831 2048K 0700 DDR
31 376832 377855 512K 0700 sec
32 377856 378879 512K 0700 encrypt
33 378880 379903 512K 0700 eksst
34 379904 380927 512K 0700 rct
35 380928 385023 2048K 0700 persistent
36 385024 393215 4096K 0700 spare2
37 393216 491519 48.0M 0700 laf
38 491520 573439 40.0M 0700 boot
39 573440 655359 40.0M 0700 recovery
40 655360 671743 8192K 0700 drm
41 671744 688127 8192K 0700 sns
42 688128 753663 32.0M 0700 mpt
43 753664 770047 8192K 0700 eri
44 770048 778239 4096K 0700 raw_resources
45 778240 786431 4096K 0700 raw_resourcesbak
46 786432 819199 16.0M 0700 operatorlogging
47 819200 901119 40.0M 0700 carrier
48 901120 917503 8192K 0700 felica
49 917504 1011711 46.0M 0700 factory
50 1011712 1015807 2048K 0700 spare3
51 1015808 1036287 10.0M 0700 fota
52 1036288 1048575 6144K 0700 spare4
53 1048576 9822207 4284M 0700 system
54 9822208 12345343 1232M 0700 cache
55 12345344 61046783 23.2G 0700 userdata
56 61046784 61071326 11.9M 0700 grow
parted --> print:
Code:
Model: MMC 032G74 (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name F
1 16.8MB 107MB 90.2MB fat16 modem
2 117MB 118MB 524kB pmic
3 118MB 119MB 1049kB sbl1
4 119MB 120MB 1049kB tz
5 120MB 121MB 524kB sdi
6 121MB 121MB 524kB hyp
7 121MB 122MB 524kB rpm
8 122MB 124MB 2097kB aboot
9 124MB 125MB 1049kB sbl1bak
10 125MB 125MB 524kB pmicbak
11 125MB 126MB 1049kB tzbak
12 126MB 127MB 524kB hypbak
13 127MB 127MB 524kB rpmbak
14 127MB 129MB 2097kB abootbak
15 129MB 130MB 524kB sdibak
16 130MB 131MB 524kB limits
17 131MB 131MB 524kB devinfo
18 131MB 132MB 524kB apdp
19 132MB 132MB 524kB msadp
20 132MB 133MB 524kB dpo
21 133MB 134MB 1573kB spare1
22 134MB 151MB 16.8MB misc
23 151MB 185MB 33.6MB ext4 persist
24 185MB 186MB 1573kB modemst1
25 186MB 188MB 1573kB modemst2
26 188MB 189MB 1573kB fsg
27 189MB 190MB 524kB fsc
28 190MB 190MB 524kB ssd
29 190MB 191MB 524kB keystore
30 191MB 193MB 2097kB DDR
31 193MB 193MB 524kB sec
32 193MB 194MB 524kB encrypt
33 194MB 195MB 524kB eksst
34 195MB 195MB 524kB rct
35 195MB 197MB 2097kB persistent
36 197MB 201MB 4194kB spare2
37 201MB 252MB 50.3MB laf
38 252MB 294MB 41.9MB boot
39 294MB 336MB 41.9MB recovery
40 336MB 344MB 8389kB ext4 drm
41 344MB 352MB 8389kB ext4 sns
42 352MB 386MB 33.6MB ext4 mpt
43 386MB 394MB 8389kB eri
44 394MB 398MB 4194kB raw_resources
45 398MB 403MB 4194kB raw_resourcesbak
46 403MB 419MB 16.8MB operatorlogging
47 419MB 461MB 41.9MB carrier
48 461MB 470MB 8389kB felica
49 470MB 518MB 48.2MB factory
50 518MB 520MB 2097kB spare3
51 520MB 531MB 10.5MB fota
52 531MB 537MB 6291kB spare4
53 537MB 5029MB 4492MB ext4 system
54 5029MB 6321MB 1292MB ext4 cache
55 6321MB 31.3GB 24.9GB ext4 userdata
56 31.3GB 31.3GB 12.6MB grow
---
Diagnosis: 9008, non-ILAPO, caused by me accidentally flashing the v20i bootstack.
I [shoddily] customized gpt_parser.py(based on source from here) to create partition.xml, which I then fed to ptool.py (source) to create the rawprogram0.xml and patch0.xml. Then I fed those into msp.py to create a singleimage.bin that I dd'd over to a microSD card. I inserted the microSD and surprisingly enough my G4 sprang to life instantly!
I booted into TWRP to copy over the what I thought were the correct v20o images to correct the faulty v20i images I had initially used to kill the mofo. That seems to have resulted in a total brick, when I rebooted there was no signs of life at all now, no 9008, no USB peeps at all now. But! the microSD card trick did bring it back from 9008, only it seems I shucked when I should have jived. (me >= woe.)
So maybe I flashed the wrong images *again*? Goddamnit. I should have dipped right into LAF download mode and flashed the stock KDZ. I've been a fool.
Anyway, I'm including the files I used to make all this happen in case anyone finds them useful: [download]
It turns out creating the partition.xml, rawprogram0.xml, and patch0.xml is incredibly simple. Too bad I could not get Firehose to work, it kept throwing this error at me whenever I tried:
Code:
{ERROR: OpenPort:4197 It took 10.01600000 seconds to open port. Which is longer than 3.000. This indicates your target is not stable
I *was* using a firehose 8992_lite.mbn file from who knows where, that could be why maybe? That is one file I'm not sure how to create yet, though the code to create it is in the same repo at the ptool.py link I posted above.
Click to expand...
Click to collapse
plz give me the link of this file firehose 8992_lite.mbn for h811
leptdre said:
1- first you need to resize you micro sd card with SD formatter ( give it its original size)
2- you must low level format it ( not quick format )
3- flash your bin file with win 32 Disk imager ( or DD command in linux ) ( if you dont have a working dump i will upload this evening)
4- put the sd card into the phone , put the battery on , press vol up button and plug a usb cable
5- now you will be able to enter download mode and flash a firmware using LG UP ( flash 10N or above )
obviously the firmware is going to the SD card , from twrp i listed the /dev/block directory , i found no sign of the EMMC memory what so ever, if someone happen to find it please share
Click to expand...
Click to collapse
please give me link bin file for g4 h811
thanks
I kept getting Secure Boot Error when I figured out how to do this. We should just be able to use the KDZ, since everything is on there that is needed to get into Download mode.
LG still holding my phone hostage since the 16th...not happy!
Noksucow1 said:
I kept getting Secure Boot Error when I figured out how to do this. We should just be able to use the KDZ, since everything is on there that is needed to get into Download mode.
LG still holding my phone hostage since the 16th...not happy!
Click to expand...
Click to collapse
Was your bootloadwr previously unlocked?
can i use the full dump "Dump_H811_1GB.img"
http://www.gsm-file.com/files/dumph8111gbzip-2702.html
or i must use dump file *.BIN that i cant find it....
T.E.I.M said:
can i use the full dump "Dump_H811_1GB.img"
http://www.gsm-file.com/files/dumph8111gbzip-2702.html
or i must use dump file *.BIN that i cant find it....
Click to expand...
Click to collapse
you can use it you just need a clean SD card like i sad
culot said:
Was your bootloadwr previously unlocked?
Click to expand...
Click to collapse
No, I had the Unlock OEM checked, other than that no...It's not on the list.
Hello i tought it share my findings here
Huawei P20 Partitions
Code:
HWEML:/dev/block/platform/ff3c0000.ufs/by-name $ ls -la
total 0
drwxr-xr-x 2 root root 1300 2018-03-28 14:54 .
drwxr-xr-x 4 root root 1420 2018-03-28 14:54 ..
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 bootfail_info -> /dev/block/sdd18
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 cache -> /dev/block/sdd58
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 certification -> /dev/block/sdd5
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 cust_a -> /dev/block/sdd56
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 ddr_para -> /dev/block/sdd15
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 dfx -> /dev/block/sdd20
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 dto_a -> /dev/block/sdd43
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 dts_a -> /dev/block/sdd42
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 erecovery_kernel_a -> /dev/block/sdd35
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 erecovery_ramdisk_a -> /dev/block/sdd36
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 erecovery_vbmeta_a -> /dev/block/sdd48
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 erecovery_vendor_a -> /dev/block/sdd37
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 fastboot_a -> /dev/block/sdd28
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 frp -> /dev/block/sdc1
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 fw_hifi_a -> /dev/block/sdd32
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 fw_lpm3_a -> /dev/block/sdd22
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 hdcp_a -> /dev/block/sdd24
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 hhee_a -> /dev/block/sdd26
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 hisee_encos -> /dev/block/sdd13
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 hisee_fs_a -> /dev/block/sdd27
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 hisee_img_a -> /dev/block/sdd25
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 isp_boot_a -> /dev/block/sdd30
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 isp_firmware_a -> /dev/block/sdd31
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 kernel_a -> /dev/block/sdd38
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 misc -> /dev/block/sdd19
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 modem_fw_a -> /dev/block/sdd45
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 modem_om -> /dev/block/sdd8
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 modem_secure -> /dev/block/sdd3
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 modemnvm_backup -> /dev/block/sdd10
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 modemnvm_cust_a -> /dev/block/sdd51
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 modemnvm_factory -> /dev/block/sdd9
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 modemnvm_img -> /dev/block/sdd11
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 modemnvm_system -> /dev/block/sdd12
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 modemnvm_update_a -> /dev/block/sdd50
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 nvme -> /dev/block/sdd4
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 odm_a -> /dev/block/sdd57
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 oeminfo -> /dev/block/sdd6
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 patch_a -> /dev/block/sdd52
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 persist -> /dev/block/sdc2
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 product_a -> /dev/block/sdd55
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 ramdisk_a -> /dev/block/sdd39
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 recovery_ramdisk_a -> /dev/block/sdd40
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 recovery_vbmeta_a -> /dev/block/sdd47
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 recovery_vendor_a -> /dev/block/sdd41
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 reserved1 -> /dev/block/sdc3
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 reserved2 -> /dev/block/sdd16
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 reserved3_a -> /dev/block/sdd23
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 reserved4_a -> /dev/block/sdd46
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 rrecord -> /dev/block/sdd21
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 secure_storage -> /dev/block/sdd7
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 sensorhub_a -> /dev/block/sdd34
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 splash2 -> /dev/block/sdd17
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 system_a -> /dev/block/sdd59
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 teeos_a -> /dev/block/sdd33
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 trustfirmware_a -> /dev/block/sdd44
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 userdata -> /dev/block/sdd60
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 vbmeta_a -> /dev/block/sdd49
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 vector_a -> /dev/block/sdd29
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 vendor_a -> /dev/block/sdd54
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 veritykey -> /dev/block/sdd14
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 version_a -> /dev/block/sdd53
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 vrl -> /dev/block/sdd1
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 vrl_backup -> /dev/block/sdd2
Code:
HWEML:/system $ df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 1.4G 12M 1.4G 1% /
tmpfs 1.7G 684K 1.7G 1% /dev
/dev/block/dm-0 4.3G 3.2G 1.1G 75% /system
/dev/block/dm-1 747M 688M 44M 94% /vendor
/dev/block/dm-2 120M 110M 7.2M 94% /odm
/dev/block/dm-3 27M 516K 26M 2% /version
/dev/block/dm-4 182M 114M 64M 65% /product
/dev/block/dm-5 182M 44M 134M 25% /cust
tmpfs 1.7G 0 1.7G 0% /mnt
none 1.7G 0 1.7G 0% /sys/fs/cgroup
/dev/block/sdd60 111G 3.6G 106G 4% /data
/dev/block/sdd58 122M 60K 119M 1% /cache
/data/media 111G 4.9G 106G 5% /storage/emulated
Hope it helps some one
Can you check for this? https://www.xda-developers.com/how-to-check-android-device-supports-seamless-updates/
Here we go
Cant get the unlock code from the huawei site then i would try phh AOSP
Yes the P20 Lite ANE-LX1 is also Treble enabled but is A only
crucky said:
Here we go
Cant get the unlock code from the huawei site then i would try phh AOSP
Click to expand...
Click to collapse
Hey please tell me what you did?
I just remote helped a guy to bootloader unlock his demo unit
Sent from my DUK-L09 using Tapatalk
IMEI SN Missmatch always the same on the P20 Lite Demo Unit it worked
EDIT:I Saw you posted a tutorial for unlock will try it now with my demo unit
LastStandingDroid said:
Hey please tell me what you did?
I just remote helped a guy to bootloader unlock his demo unit
Click to expand...
Click to collapse
How did you unlock the Demo Unit? Mine has OEM lock and I can't unlock it in the developer options.
Nogorka said:
How did you unlock the Demo Unit? Mine has OEM lock and I can't unlock it in the developer options.
Click to expand...
Click to collapse
Simply by enable developer options and tick oem unlock? You'd have to ask the guy who owns it
Sent from my DUK-L09 using Tapatalk
LastStandingDroid said:
Simply by enable developer options and tick oem unlock? You'd have to ask the guy who owns it
Click to expand...
Click to collapse
The owner is a Provider because it's a Demo unit from "my" shop. And i can't enable the OEM unlock option, it's grayed out. I thought you could help me with unlocking it, sorry!
Nogorka said:
The owner is a Provider because it's a Demo unit from "my" shop. And i can't enable the OEM unlock option, it's grayed out. I thought you could help me with unlocking it, sorry!
Click to expand...
Click to collapse
Greyed out? Sounds like they disabled it.
Is it the demo version which has the demo app? Because on the p20 pro it was possible to unlock. And it was demo store unit
Sent from my DUK-L09 using Tapatalk
LastStandingDroid said:
Greyed out? Sounds like they disabled it.
Is it the demo version which has the demo app? Because on the p20 pro it was possible to unlock. And it was demo store unit
Click to expand...
Click to collapse
Yeah, there ist the retail Demo on it, and a "explore P20" app too. Okay.. than ill have to wait till somebody know how to enable the OEM unlock. Thanks a lot!
Nogorka said:
Yeah, there ist the retail Demo on it, and a "explore P20" app too. Okay.. than ill have to wait till somebody know how to enable the OEM unlock. Thanks a lot!
Click to expand...
Click to collapse
Hello i own a Demo phone to EML-L29 non-pro you can enable oem unlock by factory reseting and connecting wifi also turn on developer options then and connect and disconnect the type c usb.After a while i could enable it and unlocked the bootloader of the demo unit running phh treble aosp rom
crucky said:
Hello i own a Demo phone to EML-L29 non-pro you can enable oem unlock by factory reseting and connecting wifi also turn on developer options then and connect and disconnect the type c usb.After a while i could enable it and unlocked the bootloader of the demo unit running phh treble aosp rom
Click to expand...
Click to collapse
Could you try
https://mega.nz/#!xGYSiSCS!cgkEfytbI_D8BUl2HjQB1qtGuTPc7Rw2630HIHXxGKE
Eml patched
Sent from my DUK-L09 using Tapatalk
LastStandingDroid said:
Could you try
https://mega.nz/#!xGYSiSCS!cgkEfytbI_D8BUl2HjQB1qtGuTPc7Rw2630HIHXxGKE
Eml patched
Sent from my DUK-L09 using Tapatalk
Click to expand...
Click to collapse
Yes will try it tomorrow because today i need my phone and iam currently running phh AOSP not Demo Stock
crucky said:
Yes will try it tomorrow because today i need my phone and iam currently running phh AOSP not Demo Stock
Click to expand...
Click to collapse
That shouldn't matter should work on both stock and phh
Sent from my DUK-L09 using Tapatalk
Can confirm works great Deinstalled the Demo APK
crucky said:
Can confirm works great Deinstalled the Demo APK
Click to expand...
Click to collapse
Do you mean that you're running AOSP with magisk patched boot image on Huawei P20 (EML)?
No switched back to stock. but will try it now again with phh AOSP somone here with a C432 P20 EML-L29 ? maybe you can give me a dump of CUST ? then i would try to rebrand from my demo C652. @LastStandingDroid maybe we can find a solution for rebrand ? because i modded CUST partition the only problem i have now i cant set fingerprint or faceunlock because of that its very annoying. @ectroplasma22 do you have it ? Maybe you could grab the full package firmware ? Still isnt avaible @ FF only funkyhuawei
Great news guys.
There a working twrp for you guys
Bad news I can't share since user who created it is banned.
Also decryption won't work. So it's basically useless for mate P20 pro users.
Good thing lite/regular should be good to go. If having a external Sd!
Edit it did not
Picture tells u what to Google for. Please do not ask for link!
{
"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"
}
Sent from my DUK-L09 using Tapatalk
Ok the patched ramdisk isnt working with RROS
Hi all!
I cant open thread in other channel so i post here. sorry about it.
I've compiled a custom kernel for Samsung S9, but the kernel is bigger than the BOOT partition size. I want to create a new partition (over USERDATA partition) and boot from the new one.
This is the initial GPT /dev/block/sda partition:
Code:
~ # sgdisk --print /dev/block/sda
Disk /dev/block/sda: 15616000 sectors, 59.6 GiB
Logical sector size: 4096 bytes
Disk identifier (GUID): 52444E41-494F-2044-4D4D-43204449534B
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 15615994
Partitions will be aligned on 2-sector boundaries
Total free space is 2677 sectors (10.5 MiB)
Number Start (sector) End (sector) Size Code Name
1 1024 2047 4.0 MiB 0700 BOTA0
2 2048 4095 8.0 MiB 0700 BOTA1
3 4096 9215 20.0 MiB 0700 EFS
4 9216 11263 8.0 MiB 0700 PARAM
5 11264 13311 8.0 MiB 0700 UP_PARAM
6 13312 13313 8.0 KiB 0700 KEYSTORAGE
7 13314 15361 8.0 MiB 0700 BOTA2
8 15362 17409 8.0 MiB 0700 DTB
9 17410 19457 8.0 MiB 0700 DTBO
10 19458 33537 55.0 MiB 0700 BOOT
11 33538 50175 65.0 MiB 0700 RECOVERY
12 50176 62975 50.0 MiB 0700 RADIO
13 62976 63231 1024.0 KiB 0700 NAD_REFER
14 63232 63359 512.0 KiB 0700 PERSISTENT
15 63360 63615 1024.0 KiB 0700 MISC
16 63616 64639 4.0 MiB 0700 STEADY
17 64640 68735 16.0 MiB 0700 DQMDBG
18 68736 1195135 4.3 GiB 0700 SYSTEM
19 1195136 1361535 650.0 MiB 0700 VENDOR
20 1361536 1526911 646.0 MiB 0700 ODM
21 1526912 1680511 600.0 MiB 0700 CACHE
22 1680512 1683071 10.0 MiB 0700 HIDDEN
23 1683072 1695871 50.0 MiB 0700 OMR
24 1695872 1697151 5.0 MiB 0700 CP_DEBUG
25 1697152 15614335 53.1 GiB 0700 USERDATA
I've tried to re-partition /dev/block/sda with sgdisk like this:
Code:
~ # sgdisk --delete 25 /dev/block/sda
~ # sgdisk --new 25:1697152:1716972 /dev/block/sda
~ # sgdisk --change-name 25:BOOT2 /dev/block/sda
~ # sgdisk --typecode 25:0700 /dev/block/sda
~ # sgdisk --new 26:1716973:15614335 /dev/block/sda
~ # sgdisk --change-name 26:USERDATA /dev/block/sda
~ # sgdisk --typecode 26:0700 /dev/block/sda
~ # sgdisk --print /dev/block/sda
Disk /dev/block/sda: 15616000 sectors, 59.6 GiB
Logical sector size: 4096 bytes
Disk identifier (GUID): 52444E41-494F-2044-4D4D-43204449534B
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 15615994
Partitions will be aligned on 2-sector boundaries
Total free space is 2678 sectors (10.5 MiB)
Number Start (sector) End (sector) Size Code Name
1 1024 2047 4.0 MiB 0700 BOTA0
2 2048 4095 8.0 MiB 0700 BOTA1
3 4096 9215 20.0 MiB 0700 EFS
4 9216 11263 8.0 MiB 0700 PARAM
5 11264 13311 8.0 MiB 0700 UP_PARAM
6 13312 13313 8.0 KiB 0700 KEYSTORAGE
7 13314 15361 8.0 MiB 0700 BOTA2
8 15362 17409 8.0 MiB 0700 DTB
9 17410 19457 8.0 MiB 0700 DTBO
10 19458 33537 55.0 MiB 0700 BOOT
11 33538 50175 65.0 MiB 0700 RECOVERY
12 50176 62975 50.0 MiB 0700 RADIO
13 62976 63231 1024.0 KiB 0700 NAD_REFER
14 63232 63359 512.0 KiB 0700 PERSISTENT
15 63360 63615 1024.0 KiB 0700 MISC
16 63616 64639 4.0 MiB 0700 STEADY
17 64640 68735 16.0 MiB 0700 DQMDBG
18 68736 1195135 4.3 GiB 0700 SYSTEM
19 1195136 1361535 650.0 MiB 0700 VENDOR
20 1361536 1526911 646.0 MiB 0700 ODM
21 1526912 1680511 600.0 MiB 0700 CACHE
22 1680512 1683071 10.0 MiB 0700 HIDDEN
23 1683072 1695871 50.0 MiB 0700 OMR
24 1695872 1697151 5.0 MiB 0700 CP_DEBUG
25 1697152 1716972 77.4 MiB 0700 BOOT2
26 1716974 15614335 53.0 GiB 0700 USERDATA
~ # exit
~ adb reboot recovery
~ adb wait-for-any && adb shell
~ # ~ # ls /dev/block/platform/11120000.ufs/by-name/ -la
drwxr-xr-x 2 root root 580 Nov 19 15:32 .
drwxr-xr-x 4 root root 720 Nov 19 15:32 ..
lrwxrwxrwx 1 root root 16 Nov 19 15:32 BOOT -> /dev/block/sda10
lrwxrwxrwx 1 root root 16 Nov 19 15:32 BOOT2 -> /dev/block/sda25
lrwxrwxrwx 1 root root 15 Nov 19 15:32 BOTA0 -> /dev/block/sda1
lrwxrwxrwx 1 root root 15 Nov 19 15:32 BOTA1 -> /dev/block/sda2
lrwxrwxrwx 1 root root 15 Nov 19 15:32 BOTA2 -> /dev/block/sda7
lrwxrwxrwx 1 root root 16 Nov 19 15:32 CACHE -> /dev/block/sda21
lrwxrwxrwx 1 root root 15 Nov 19 15:32 CPEFS -> /dev/block/sdd1
lrwxrwxrwx 1 root root 16 Nov 19 15:32 CP_DEBUG -> /dev/block/sda24
lrwxrwxrwx 1 root root 16 Nov 19 15:32 DQMDBG -> /dev/block/sda17
lrwxrwxrwx 1 root root 15 Nov 19 15:32 DTB -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 Nov 19 15:32 DTBO -> /dev/block/sda9
lrwxrwxrwx 1 root root 15 Nov 19 15:32 EFS -> /dev/block/sda3
lrwxrwxrwx 1 root root 16 Nov 19 15:32 HIDDEN -> /dev/block/sda22
lrwxrwxrwx 1 root root 15 Nov 19 15:32 KEYSTORAGE -> /dev/block/sda6
lrwxrwxrwx 1 root root 16 Nov 19 15:32 MISC -> /dev/block/sda15
lrwxrwxrwx 1 root root 16 Nov 19 15:32 NAD_REFER -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 Nov 19 15:32 ODM -> /dev/block/sda20
lrwxrwxrwx 1 root root 16 Nov 19 15:32 OMR -> /dev/block/sda23
lrwxrwxrwx 1 root root 15 Nov 19 15:32 PARAM -> /dev/block/sda4
lrwxrwxrwx 1 root root 16 Nov 19 15:32 PERSISTENT -> /dev/block/sda14
lrwxrwxrwx 1 root root 16 Nov 19 15:32 RADIO -> /dev/block/sda12
lrwxrwxrwx 1 root root 16 Nov 19 15:32 RECOVERY -> /dev/block/sda11
lrwxrwxrwx 1 root root 16 Nov 19 15:32 STEADY -> /dev/block/sda16
lrwxrwxrwx 1 root root 16 Nov 19 15:32 SYSTEM -> /dev/block/sda18
lrwxrwxrwx 1 root root 15 Nov 19 15:32 UP_PARAM -> /dev/block/sda5
lrwxrwxrwx 1 root root 16 Nov 19 15:32 USERDATA -> /dev/block/sda26
lrwxrwxrwx 1 root root 16 Nov 19 15:32 VENDOR -> /dev/block/sda19
~ # dd if=newboot.img of=/dev/block/sda25
~ # sgdisk --info=10 /dev/block/sda
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 52444E41-494F-2044-424F-4F5400000000
First sector: 19458 (at 76.0 MiB)
Last sector: 33537 (at 131.0 MiB)
Partition size: 14080 sectors (55.0 MiB)
Attribute flags: 0000000000000000
Partition name: 'BOOT'
~ # sgdisk --info=25 /dev/block/sda
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 7CE83C10-10C6-4E3D-A6B4-92B66586A716
First sector: 1697152 (at 6.5 GiB)
Last sector: 1716972 (at 6.5 GiB)
Partition size: 19821 sectors (77.4 MiB)
Attribute flags: 0000000000000000
Partition name: 'BOOT2'
~ # sgdisk --partition-guid=10:R /dev/block/sda
~ # sgdisk --partition-guid=25:52444E41-494F-2044-424F-4F5400000000 /dev/block/sda
~ # sgdisk --info=10 /dev/block/sda
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 6F5BCACB-2AF9-4F16-B2A3-B4B12085EB8F
First sector: 19458 (at 76.0 MiB)
Last sector: 33537 (at 131.0 MiB)
Partition size: 14080 sectors (55.0 MiB)
Attribute flags: 0000000000000000
Partition name: 'BOOT'
~ # sgdisk --info=25 /dev/block/sda
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 52444E41-494F-2044-424F-4F5400000000
First sector: 1697152 (at 6.5 GiB)
Last sector: 1716972 (at 6.5 GiB)
Partition size: 19821 sectors (77.4 MiB)
Attribute flags: 0000000000000000
Partition name: 'BOOT2'
~ # sgdisk --change-name 10:BOOT1 /dev/block/sda
~ # sgdisk --change-name 25:BOOT /dev/block/sda
~ # sgdisk --print /dev/block/sda
Disk /dev/block/sda: 15616000 sectors, 59.6 GiB
Logical sector size: 4096 bytes
Disk identifier (GUID): 52444E41-494F-2044-4D4D-43204449534B
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 15615994
Partitions will be aligned on 2-sector boundaries
Total free space is 13900040 sectors (53.0 GiB)
Number Start (sector) End (sector) Size Code Name
1 1024 2047 4.0 MiB 0700 BOTA0
2 2048 4095 8.0 MiB 0700 BOTA1
3 4096 9215 20.0 MiB 0700 EFS
4 9216 11263 8.0 MiB 0700 PARAM
5 11264 13311 8.0 MiB 0700 UP_PARAM
6 13312 13313 8.0 KiB 0700 KEYSTORAGE
7 13314 15361 8.0 MiB 0700 BOTA2
8 15362 17409 8.0 MiB 0700 DTB
9 17410 19457 8.0 MiB 0700 DTBO
10 19458 33537 55.0 MiB 0700 BOOT1
11 33538 50175 65.0 MiB 0700 RECOVERY
12 50176 62975 50.0 MiB 0700 RADIO
13 62976 63231 1024.0 KiB 0700 NAD_REFER
14 63232 63359 512.0 KiB 0700 PERSISTENT
15 63360 63615 1024.0 KiB 0700 MISC
16 63616 64639 4.0 MiB 0700 STEADY
17 64640 68735 16.0 MiB 0700 DQMDBG
18 68736 1195135 4.3 GiB 0700 SYSTEM
19 1195136 1361535 650.0 MiB 0700 VENDOR
20 1361536 1526911 646.0 MiB 0700 ODM
21 1526912 1680511 600.0 MiB 0700 CACHE
22 1680512 1683071 10.0 MiB 0700 HIDDEN
23 1683072 1695871 50.0 MiB 0700 OMR
24 1695872 1697151 5.0 MiB 0700 CP_DEBUG
25 1697152 1716972 77.4 MiB 0700 BOOT
~ # exit
~ adb reboot
By this process I've written my custom boot image on the new BOOT partition, and replaced both the partition name and GUID with the original BOOT partition's.
After this, the phone still boots the real image (verified with /proc/version). What am I missing here?
I've also tried writing the original boot image to the new boot partition and zero out the original boot partition (sda10) to see what happens and the device didn't boot.
DuduFaruk said:
Hi all!
I cant open thread in other channel so i post here. sorry about it.
I've compiled a custom kernel for Samsung S9, but the kernel is bigger than the BOOT partition size. I want to create a new partition (over USERDATA partition) and boot from the new one.
This is the initial GPT /dev/block/sda partition:
Code:
~ # sgdisk --print /dev/block/sda
Disk /dev/block/sda: 15616000 sectors, 59.6 GiB
Logical sector size: 4096 bytes
Disk identifier (GUID): 52444E41-494F-2044-4D4D-43204449534B
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 15615994
Partitions will be aligned on 2-sector boundaries
Total free space is 2677 sectors (10.5 MiB)
Number Start (sector) End (sector) Size Code Name
1 1024 2047 4.0 MiB 0700 BOTA0
2 2048 4095 8.0 MiB 0700 BOTA1
3 4096 9215 20.0 MiB 0700 EFS
4 9216 11263 8.0 MiB 0700 PARAM
5 11264 13311 8.0 MiB 0700 UP_PARAM
6 13312 13313 8.0 KiB 0700 KEYSTORAGE
7 13314 15361 8.0 MiB 0700 BOTA2
8 15362 17409 8.0 MiB 0700 DTB
9 17410 19457 8.0 MiB 0700 DTBO
10 19458 33537 55.0 MiB 0700 BOOT
11 33538 50175 65.0 MiB 0700 RECOVERY
12 50176 62975 50.0 MiB 0700 RADIO
13 62976 63231 1024.0 KiB 0700 NAD_REFER
14 63232 63359 512.0 KiB 0700 PERSISTENT
15 63360 63615 1024.0 KiB 0700 MISC
16 63616 64639 4.0 MiB 0700 STEADY
17 64640 68735 16.0 MiB 0700 DQMDBG
18 68736 1195135 4.3 GiB 0700 SYSTEM
19 1195136 1361535 650.0 MiB 0700 VENDOR
20 1361536 1526911 646.0 MiB 0700 ODM
21 1526912 1680511 600.0 MiB 0700 CACHE
22 1680512 1683071 10.0 MiB 0700 HIDDEN
23 1683072 1695871 50.0 MiB 0700 OMR
24 1695872 1697151 5.0 MiB 0700 CP_DEBUG
25 1697152 15614335 53.1 GiB 0700 USERDATA
I've tried to re-partition /dev/block/sda with sgdisk like this:
Code:
~ # sgdisk --delete 25 /dev/block/sda
~ # sgdisk --new 25:1697152:1716972 /dev/block/sda
~ # sgdisk --change-name 25:BOOT2 /dev/block/sda
~ # sgdisk --typecode 25:0700 /dev/block/sda
~ # sgdisk --new 26:1716973:15614335 /dev/block/sda
~ # sgdisk --change-name 26:USERDATA /dev/block/sda
~ # sgdisk --typecode 26:0700 /dev/block/sda
~ # sgdisk --print /dev/block/sda
Disk /dev/block/sda: 15616000 sectors, 59.6 GiB
Logical sector size: 4096 bytes
Disk identifier (GUID): 52444E41-494F-2044-4D4D-43204449534B
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 15615994
Partitions will be aligned on 2-sector boundaries
Total free space is 2678 sectors (10.5 MiB)
Number Start (sector) End (sector) Size Code Name
1 1024 2047 4.0 MiB 0700 BOTA0
2 2048 4095 8.0 MiB 0700 BOTA1
3 4096 9215 20.0 MiB 0700 EFS
4 9216 11263 8.0 MiB 0700 PARAM
5 11264 13311 8.0 MiB 0700 UP_PARAM
6 13312 13313 8.0 KiB 0700 KEYSTORAGE
7 13314 15361 8.0 MiB 0700 BOTA2
8 15362 17409 8.0 MiB 0700 DTB
9 17410 19457 8.0 MiB 0700 DTBO
10 19458 33537 55.0 MiB 0700 BOOT
11 33538 50175 65.0 MiB 0700 RECOVERY
12 50176 62975 50.0 MiB 0700 RADIO
13 62976 63231 1024.0 KiB 0700 NAD_REFER
14 63232 63359 512.0 KiB 0700 PERSISTENT
15 63360 63615 1024.0 KiB 0700 MISC
16 63616 64639 4.0 MiB 0700 STEADY
17 64640 68735 16.0 MiB 0700 DQMDBG
18 68736 1195135 4.3 GiB 0700 SYSTEM
19 1195136 1361535 650.0 MiB 0700 VENDOR
20 1361536 1526911 646.0 MiB 0700 ODM
21 1526912 1680511 600.0 MiB 0700 CACHE
22 1680512 1683071 10.0 MiB 0700 HIDDEN
23 1683072 1695871 50.0 MiB 0700 OMR
24 1695872 1697151 5.0 MiB 0700 CP_DEBUG
25 1697152 1716972 77.4 MiB 0700 BOOT2
26 1716974 15614335 53.0 GiB 0700 USERDATA
~ # exit
~ adb reboot recovery
~ adb wait-for-any && adb shell
~ # ~ # ls /dev/block/platform/11120000.ufs/by-name/ -la
drwxr-xr-x 2 root root 580 Nov 19 15:32 .
drwxr-xr-x 4 root root 720 Nov 19 15:32 ..
lrwxrwxrwx 1 root root 16 Nov 19 15:32 BOOT -> /dev/block/sda10
lrwxrwxrwx 1 root root 16 Nov 19 15:32 BOOT2 -> /dev/block/sda25
lrwxrwxrwx 1 root root 15 Nov 19 15:32 BOTA0 -> /dev/block/sda1
lrwxrwxrwx 1 root root 15 Nov 19 15:32 BOTA1 -> /dev/block/sda2
lrwxrwxrwx 1 root root 15 Nov 19 15:32 BOTA2 -> /dev/block/sda7
lrwxrwxrwx 1 root root 16 Nov 19 15:32 CACHE -> /dev/block/sda21
lrwxrwxrwx 1 root root 15 Nov 19 15:32 CPEFS -> /dev/block/sdd1
lrwxrwxrwx 1 root root 16 Nov 19 15:32 CP_DEBUG -> /dev/block/sda24
lrwxrwxrwx 1 root root 16 Nov 19 15:32 DQMDBG -> /dev/block/sda17
lrwxrwxrwx 1 root root 15 Nov 19 15:32 DTB -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 Nov 19 15:32 DTBO -> /dev/block/sda9
lrwxrwxrwx 1 root root 15 Nov 19 15:32 EFS -> /dev/block/sda3
lrwxrwxrwx 1 root root 16 Nov 19 15:32 HIDDEN -> /dev/block/sda22
lrwxrwxrwx 1 root root 15 Nov 19 15:32 KEYSTORAGE -> /dev/block/sda6
lrwxrwxrwx 1 root root 16 Nov 19 15:32 MISC -> /dev/block/sda15
lrwxrwxrwx 1 root root 16 Nov 19 15:32 NAD_REFER -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 Nov 19 15:32 ODM -> /dev/block/sda20
lrwxrwxrwx 1 root root 16 Nov 19 15:32 OMR -> /dev/block/sda23
lrwxrwxrwx 1 root root 15 Nov 19 15:32 PARAM -> /dev/block/sda4
lrwxrwxrwx 1 root root 16 Nov 19 15:32 PERSISTENT -> /dev/block/sda14
lrwxrwxrwx 1 root root 16 Nov 19 15:32 RADIO -> /dev/block/sda12
lrwxrwxrwx 1 root root 16 Nov 19 15:32 RECOVERY -> /dev/block/sda11
lrwxrwxrwx 1 root root 16 Nov 19 15:32 STEADY -> /dev/block/sda16
lrwxrwxrwx 1 root root 16 Nov 19 15:32 SYSTEM -> /dev/block/sda18
lrwxrwxrwx 1 root root 15 Nov 19 15:32 UP_PARAM -> /dev/block/sda5
lrwxrwxrwx 1 root root 16 Nov 19 15:32 USERDATA -> /dev/block/sda26
lrwxrwxrwx 1 root root 16 Nov 19 15:32 VENDOR -> /dev/block/sda19
~ # dd if=newboot.img of=/dev/block/sda25
~ # sgdisk --info=10 /dev/block/sda
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 52444E41-494F-2044-424F-4F5400000000
First sector: 19458 (at 76.0 MiB)
Last sector: 33537 (at 131.0 MiB)
Partition size: 14080 sectors (55.0 MiB)
Attribute flags: 0000000000000000
Partition name: 'BOOT'
~ # sgdisk --info=25 /dev/block/sda
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 7CE83C10-10C6-4E3D-A6B4-92B66586A716
First sector: 1697152 (at 6.5 GiB)
Last sector: 1716972 (at 6.5 GiB)
Partition size: 19821 sectors (77.4 MiB)
Attribute flags: 0000000000000000
Partition name: 'BOOT2'
~ # sgdisk --partition-guid=10:R /dev/block/sda
~ # sgdisk --partition-guid=25:52444E41-494F-2044-424F-4F5400000000 /dev/block/sda
~ # sgdisk --info=10 /dev/block/sda
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 6F5BCACB-2AF9-4F16-B2A3-B4B12085EB8F
First sector: 19458 (at 76.0 MiB)
Last sector: 33537 (at 131.0 MiB)
Partition size: 14080 sectors (55.0 MiB)
Attribute flags: 0000000000000000
Partition name: 'BOOT'
~ # sgdisk --info=25 /dev/block/sda
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 52444E41-494F-2044-424F-4F5400000000
First sector: 1697152 (at 6.5 GiB)
Last sector: 1716972 (at 6.5 GiB)
Partition size: 19821 sectors (77.4 MiB)
Attribute flags: 0000000000000000
Partition name: 'BOOT2'
~ # sgdisk --change-name 10:BOOT1 /dev/block/sda
~ # sgdisk --change-name 25:BOOT /dev/block/sda
~ # sgdisk --print /dev/block/sda
Disk /dev/block/sda: 15616000 sectors, 59.6 GiB
Logical sector size: 4096 bytes
Disk identifier (GUID): 52444E41-494F-2044-4D4D-43204449534B
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 15615994
Partitions will be aligned on 2-sector boundaries
Total free space is 13900040 sectors (53.0 GiB)
Number Start (sector) End (sector) Size Code Name
1 1024 2047 4.0 MiB 0700 BOTA0
2 2048 4095 8.0 MiB 0700 BOTA1
3 4096 9215 20.0 MiB 0700 EFS
4 9216 11263 8.0 MiB 0700 PARAM
5 11264 13311 8.0 MiB 0700 UP_PARAM
6 13312 13313 8.0 KiB 0700 KEYSTORAGE
7 13314 15361 8.0 MiB 0700 BOTA2
8 15362 17409 8.0 MiB 0700 DTB
9 17410 19457 8.0 MiB 0700 DTBO
10 19458 33537 55.0 MiB 0700 BOOT1
11 33538 50175 65.0 MiB 0700 RECOVERY
12 50176 62975 50.0 MiB 0700 RADIO
13 62976 63231 1024.0 KiB 0700 NAD_REFER
14 63232 63359 512.0 KiB 0700 PERSISTENT
15 63360 63615 1024.0 KiB 0700 MISC
16 63616 64639 4.0 MiB 0700 STEADY
17 64640 68735 16.0 MiB 0700 DQMDBG
18 68736 1195135 4.3 GiB 0700 SYSTEM
19 1195136 1361535 650.0 MiB 0700 VENDOR
20 1361536 1526911 646.0 MiB 0700 ODM
21 1526912 1680511 600.0 MiB 0700 CACHE
22 1680512 1683071 10.0 MiB 0700 HIDDEN
23 1683072 1695871 50.0 MiB 0700 OMR
24 1695872 1697151 5.0 MiB 0700 CP_DEBUG
25 1697152 1716972 77.4 MiB 0700 BOOT
~ # exit
~ adb reboot
By this process I've written my custom boot image on the new BOOT partition, and replaced both the partition name and GUID with the original BOOT partition's.
After this, the phone still boots the real image (verified with /proc/version). What am I missing here?
I've also tried writing the original boot image to the new boot partition and zero out the original boot partition (sda10) to see what happens and the device didn't boot.
Click to expand...
Click to collapse
you might need the big guns for this issue. @AthieN you got any words of wisdom for this?
For those who will experience it in the future.
After I reversed S-Boot I notice the bootloader load partition from internal PIT file and the boot section in the GPT is not connected to the boot order.