Hello, i have a big problem. Since yesterday i try to revive my bricked p920, but without sucess.
After flashing the ICS update with the LG flasher
the display stayed black. I tried many "how to's" on how to enter the fastboot mode, but without sucess.
Code:
--------------------------------------------
OMAP4boot for P920/P720/SU540/SU760/SU870
--------------------------------------------
by wkpark at gmail dot com
[1] cx2 - Optimus 3D Cube (SU870/P720)
[2] p920 - Optimus 3D (P920)
[3] p920emu - Optimus 3D (P920 EMU)
[4] p940 - Prada 3.0 (P940)
[5] su540 - Prada 3.0 (SU540/KU5400)
[6] su760 - Optimus 3D (SU760)
[x] exit
-------------------------------------------
Select device : 2
p920 selected
============================================================
You have to hold volume-up button to enter S/W donwload mode
============================================================
waiting for OMAP44xx device...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
reading ASIC ID
usb_write 4
usb_read 81
[*] read 0 bytes
NumOfSubblocks: 0x5
Subblock ID: 0x1
Subblock Size: 0x5
CH enabled: 0x7
ROM revision: 0x2
Checksum Subblock: 0x15
CHIP: 4430
IDEN: 12bd240a5cbb4df74165e28847c766b87268a144
MPKH: 6d473e6a0470e01a52601081128b053b74490ee000000000000000000000000
CRC0: 31b46fa0
CRC1: 611e8642
sending 2ndstage to target... f0030002
usb_write 4
usb_write 4
wait 5-seconds...
[*] msg size = 4
usb_write 21504
[*] data size = 21504
usb_close
Reopen usb...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
waiting for 2ndstage response...
usb_read 4
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
1. I already tried omap4boot 1.21 and 1.25a
2. I already tried a different computer.
3. I Installed the driver, OMAP 4430 USB is recognized at the pc.
4. I am using Windows 7 64bit
5. I am startign with battery out, connecting then after or while wait 5 sec, putting bat back in. Tried with VOL +, without VOL +, With battery and without, tried almost all compination possible.
Does someone have an idea ? What else could i try ?
Daniil S. said:
Hello, i have a big problem. Since yesterday i try to revive my bricked p920, but without sucess.
After flashing the ICS update with the LG flasher
the display stayed black. I tried many "how to's" on how to enter the fastboot mode, but without sucess.
Code:
--------------------------------------------
OMAP4boot for P920/P720/SU540/SU760/SU870
--------------------------------------------
by wkpark at gmail dot com
[1] cx2 - Optimus 3D Cube (SU870/P720)
[2] p920 - Optimus 3D (P920)
[3] p920emu - Optimus 3D (P920 EMU)
[4] p940 - Prada 3.0 (P940)
[5] su540 - Prada 3.0 (SU540/KU5400)
[6] su760 - Optimus 3D (SU760)
[x] exit
-------------------------------------------
Select device : 2
p920 selected
============================================================
You have to hold volume-up button to enter S/W donwload mode
============================================================
waiting for OMAP44xx device...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
reading ASIC ID
usb_write 4
usb_read 81
[*] read 0 bytes
NumOfSubblocks: 0x5
Subblock ID: 0x1
Subblock Size: 0x5
CH enabled: 0x7
ROM revision: 0x2
Checksum Subblock: 0x15
CHIP: 4430
IDEN: 12bd240a5cbb4df74165e28847c766b87268a144
MPKH: 6d473e6a0470e01a52601081128b053b74490ee000000000000000000000000
CRC0: 31b46fa0
CRC1: 611e8642
sending 2ndstage to target... f0030002
usb_write 4
usb_write 4
wait 5-seconds...
[*] msg size = 4
usb_write 21504
[*] data size = 21504
usb_close
Reopen usb...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
waiting for 2ndstage response...
usb_read 4
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
1. I already tried omap4boot 1.21 and 1.25a
2. I already tried a different computer.
3. I Installed the driver, OMAP 4430 USB is recognized at the pc.
4. I am using Windows 7 64bit
5. I am startign with battery out, connecting then after or while wait 5 sec, putting bat back in. Tried with VOL +, without VOL +, With battery and without, tried almost all compination possible.
Does someone have an idea ? What else could i try ?
Click to expand...
Click to collapse
Use the omap4boot (EMU version) from here http://forum.xda-developers.com/showthread.php?t=2246001 and folloe the guide's steps.
Karim Kahale said:
Use the omap4boot (EMU version) from here http://forum.xda-developers.com/showthread.php?t=2246001 and folloe the guide's steps.
Click to expand...
Click to collapse
Thank you, but i end up with the same problem. Any other ideas ?
Daniil S. said:
Thank you, but i end up with the same problem. Any other ideas ?
Click to expand...
Click to collapse
Try another port, reinstall omap drivers, change usb cable, try different pc.
try v1.2 of this tool
Karim Kahale said:
Try another port, reinstall omap drivers, change usb cable, try different pc.
Click to expand...
Click to collapse
Thank you, but used a different pc (New Driver install, different port...) same thing there. Also tried the ALLINONE Tool 1.2, and also replaced the cable...
Daniil S. said:
Thank you, but used a different pc (New Driver install, different port...) same thing there. Also tried the ALLINONE Tool 1.2, and also replaced the cable...
Click to expand...
Click to collapse
go back to LG Flash tools and flash "28b large partition" by xbsall and then install the 1.25 bootloader.
p-vlad said:
go back to LG Flash tools and flash "28b large partition" by xbsall and then install the 1.25 bootloader.
Click to expand...
Click to collapse
Can you find a "how to" for what you told me to do ? Sorry, not a pro =)
Daniil S. said:
Can you find a "how to" for what you told me to do ? Sorry, not a pro =)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=39269819
drastic00 said:
http://forum.xda-developers.com/showthread.php?p=39269819
Click to expand...
Click to collapse
you were faster
do it till point 6.. then you can install you favorite ROM/MOD
drastic00 said:
http://forum.xda-developers.com/showthread.php?p=39269819
Click to expand...
Click to collapse
Followed this how to till f6 - f7, the phone is not beeng recognized as "LGE CDMA USB SERIAL PORT" or simmilar, no drivers are installed. It shows up for a second as "OMAP4430" as before, and disappears again. Battery is not in the phone, connecting while Vol +
Am i doing something wrong ? And yes, the OMAP driver is installed, rebooted ect..
Daniil S. said:
Followed this how to till f6 - f7, the phone is not beeng recognized as "LGE CDMA USB SERIAL PORT" or simmilar, no drivers are installed. It shows up for a second as "OMAP4430" as before, and disappears again. Battery is not in the phone, connecting while Vol +
Am i doing something wrong ? And yes, the OMAP driver is installed, rebooted ect..
Click to expand...
Click to collapse
Did you install LG drivers ?
Karim Kahale said:
Did you install LG drivers ?
Click to expand...
Click to collapse
Yes, installed, uninstalled, reinstalled. Currently, they are installed.
Daniil S. said:
Yes, installed, uninstalled, reinstalled. Currently, they are installed.
Click to expand...
Click to collapse
Did you try another PC ?
Karim Kahale said:
Did you try another PC ?
Click to expand...
Click to collapse
Yes, two computers, all USB ports, two cables... Both Win 7 64bit, but it shouldn't be a prob.
Daniil S. said:
Yes, installed, uninstalled, reinstalled. Currently, they are installed.
Click to expand...
Click to collapse
I suggest rechecking driver install carefully. Disable all antivirus before downloading or extracting anything.
drastic00 said:
I suggest rechecking driver install carefully. Disable all antivirus before downloading or extracting anything.
Click to expand...
Click to collapse
Just reinstalled everything, disabled antivirus, uninstalled ALL DRIVERS, rebooted, installed drivers again. Same thing, installing OMAP4430 drivers like described, everything okay. Disconnecting phone, connecting again while pressing V+ and no battery, it installs as OMAP4430 and not "LGE CDMA USB SERIAL PORT" or "LG USB driver".
Daniil S. said:
Just reinstalled everything, disabled antivirus, uninstalled ALL DRIVERS, rebooted, installed drivers again. Same thing, installing OMAP4430 drivers like described, everything okay. Disconnecting phone, connecting again while pressing V+ and no battery, it installs as OMAP4430 and not "LGE CDMA USB SERIAL PORT" or "LG USB driver".
Click to expand...
Click to collapse
There are two separate times that the phone is connected to pc in the driver install process. Once while forcing omap win usb to install... After that, another when LG Drivers take. If you had wkpark bootloaders, check that detail. If you were unable to catch and force omap4430 to install under other devices, check that detail. Be sure you are using the driver from the fastboot folder, not in the omap 4 flash installer folder. Part 1 is tricky the first few times you do it. Don't be in a hurry. Read carefully. The devil is in the details.
drastic00 said:
There are two separate times that the phone is connected to pc in the driver install process. Once while forcing omap win usb to install... After that, another when LG Drivers take. If you had wkpark bootloaders, check that detail. If you were unable to catch and force omap4430 to install under other devices, check that detail. Be sure you are using the driver from the fastboot folder, not in the omap 4 flash installer folder. Part 1 is tricky the first few times you do it. Don't be in a hurry. Read carefully. The devil is in the details.
Click to expand...
Click to collapse
At first, what's the wkpark bootloader ? I had 2.3.3 Original ROM branded by T-Mobile Germany, was updating to ICS German after what it died.
Yes there are two times i connect the phone. At first it shows up in devices, i install the omap driver. Disconnect, connect again with vol up and no batt, and it should automatically as "LG USB" as i understand, but it is only recognized as the omap3340 that i installed previously. nothing more.
Daniil S. said:
At first, what's the wkpark bootloader ? I had 2.3.3 Original ROM branded by T-Mobile Germany, was updating to ICS German after what it died.
Yes there are two times i connect the phone. At first it shows up in devices, i install the omap driver. Disconnect, connect again with vol up and no batt, and it should automatically as "LG USB" as i understand, but it is only recognized as the omap3340 that i installed previously. nothing more.
Click to expand...
Click to collapse
If you had custom bootloader the LG logo would always be grey when you started the phone so probably not.
Battery is always out of the phone when doing driver install, the whole time.
Did you uninstall all things LG in Programs and Features and reboot pc before beginning? There would have been LG drivers and software left on your pc from your flash attempt that have to be removed first.
When you ran the 2 LG driver installers in the pack, you should have seen a warning one is unsigned, about 3 times. PC should especially be restarted after that too.
I would triple check everything. I can't imagine a bad flash would screw up your phone this bad, but it's possible that you can't enter 'normal download mode,'
If you are totally, completely sure that everything was done correctly you might then look at xbsall's unbrick guide or Karim Kahale's unbrick guide.
The good news is O3D can't be killed unless you hit it with a hammer.
Hello friends
Its too early that Xiaomi Released Kernel Source for Mi 4i, even faster that samsung does.
Here is the official link https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/ferrari-l-oss
I think now we will have development @200x
good news
Anyone taking up CM4i
prashant3285 said:
Anyone taking up CM4i
Click to expand...
Click to collapse
I'll do my best... Unfortunately, i've not too much spare time... Right now, I'm syncing the sources
Cool! By the way the kernel source doesn't include the WiFi drivers, ya'll need to port it manually.
dh.harald said:
I'll do my best... Unfortunately, i've not too much spare time... Right now, I'm syncing the sources
Click to expand...
Click to collapse
Well i guess this the time taking part
Sent from my Mi 4i using Tapatalk
Account removal
Deleted
today's progress:
got wifi drivers from qualcomm, fix it a little bit.
kernel compiled, dt.img not
Code:
Target dt image: out/target/product/msm8916_64/dt.img
DTB combiner:
Input directory: 'out/target/product/msm8916_64/obj/KERNEL_OBJ/arch/arm64/boot/dts/'
Output file: 'out/target/product/msm8916_64/dt.img'
=> Found 0 unique DTB(s)
chmod: cannot access ‘out/target/product/msm8916_64/dt.img’: No such file or directory
I'll dig into it tomorrow
@dh.harald compile the kernel manually so we can see the error that's causing it. Then build with 2>&1 tee | kernel.log so we can get an output.
Gnome said:
@dh.harald compile the kernel manually so we can see the error that's causing it. Then build with 2>&1 tee | kernel.log so we can get an output.
Click to expand...
Click to collapse
I try to follow Xiaomi's wiki about boot.img creation with caf build environment, but it's not too informative... (kernel compiled successfully [vmlinux], i've got ramdisk.img, but something wrong with dt.img)
Here's the command:
Code:
$ out/host/linux-x86/bin/dtbTool -v -s 2048 -o out/target/product/msm8916_64/dt.img -p kernel/scripts/dtc out/target/product/msm8916_64/obj/KERNEL_OBJ/arch/arm64/boot/dts/
DTB combiner:
Input directory: 'out/target/product/msm8916_64/obj/KERNEL_OBJ/arch/arm64/boot/dts/'
Output file: 'out/target/product/msm8916_64/dt.img'
=> Found 0 unique DTB(s)
But the directory is full with *.dtbs:
Code:
$ ls -la out/target/product/msm8916_64/obj/KERNEL_OBJ/arch/arm64/boot/dts/*.dtb|wc -l
15
EDIT:
i've tried dtbToolCM, and it looks working:
Code:
Target dt image: out/target/product/msm8916_64/dt.img
DTB combiner:
Input directory: 'out/target/product/msm8916_64/obj/KERNEL_OBJ/arch/arm64/boot/dts/'
Output file: 'out/target/product/msm8916_64/dt.img'
Found file: msm8916-mtp.dtb ... chipset: 206, rev: 248, platform: 0, subtype: 0
additional chipset: 0, rev: 0, platform: 249, subtype: 0
Found file: msm8916-mtp-smb1360.dtb ... chipset: 206, rev: 248, platform: 0, subtype: 0
additional chipset: 0, rev: 0, platform: 249, subtype: 0
... duplicate info, skipped
Found file: msm8939-sim.dtb ... chipset: 239, rev: 241, platform: 0, subtype: 0
additional chipset: 0, rev: 0, platform: 263, subtype: 0
Found file: msm8939-cdp.dtb ... chipset: 239, rev: 241, platform: 0, subtype: 0
additional chipset: 0, rev: 0, platform: 263, subtype: 0
... duplicate info, skipped
Found file: msm8939-cdp-jdi.dtb ... chipset: 239, rev: 241, platform: 0, subtype: 0
additional chipset: 0, rev: 0, platform: 263, subtype: 0
... duplicate info, skipped
Found file: msm8939-mtp.dtb ... chipset: 239, rev: 241, platform: 0, subtype: 0
additional chipset: 0, rev: 0, platform: 263, subtype: 0
... duplicate info, skipped
Found file: msm8939-mtp-jdi.dtb ... chipset: 239, rev: 241, platform: 0, subtype: 0
additional chipset: 0, rev: 0, platform: 263, subtype: 0
... duplicate info, skipped
Found file: msm8939-mtp-smb1360.dtb ... chipset: 239, rev: 241, platform: 0, subtype: 0
additional chipset: 0, rev: 0, platform: 263, subtype: 0
... duplicate info, skipped
Found file: msm8936-qrd-skuk.dtb ... chipset: 233, rev: 240, platform: 0, subtype: 0
additional chipset: 0, rev: 0, platform: 242, subtype: 0
Found file: msm8936-cdp.dtb ... chipset: 233, rev: 240, platform: 0, subtype: 0
additional chipset: 0, rev: 0, platform: 242, subtype: 0
... duplicate info, skipped
Found file: msm8936-cdp-smb1360.dtb ... chipset: 233, rev: 240, platform: 0, subtype: 0
additional chipset: 0, rev: 0, platform: 242, subtype: 0
... duplicate info, skipped
Found file: msm8936-mtp.dtb ... chipset: 233, rev: 240, platform: 0, subtype: 0
additional chipset: 0, rev: 0, platform: 242, subtype: 0
... duplicate info, skipped
Found file: msmtellurium-rumi.dtb ... skip, failed to scan for 'qcom,msm-id = <' tag
Found file: msm8936-mtp-smb1360.dtb ... chipset: 233, rev: 240, platform: 0, subtype: 0
additional chipset: 0, rev: 0, platform: 242, subtype: 0
... duplicate info, skipped
Found file: msmtellurium-sim.dtb ... skip, failed to scan for 'qcom,msm-id = <' tag
=> Found 6 unique DTB(s)
Generating master DTB... completed
Target boot image: out/target/product/msm8916_64/boot.img
out/host/linux-x86/bin/boot_signer /boot out/target/product/msm8916_64/boot.img build/target/product/security/verity_private_dev_key out/target/product/msm8916_64/boot.img
out/target/product/msm8916_64/boot.img maxsize=34197504 blocksize=135168 total=25780480 reserve=405504
fingers crossed
EDIT:
Code:
# fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.792s]
booting...
FAILED (remote: dtb not found)
finished. total time: 1.041s
EDIT:
I've tried to
- extract dt.img from original bootloader, and repack into boot.img
- replace only kernel image on original boot.img
with /mkbootimg_tools, but the phone won't boot
Any helps are welcome
Thanks
Dont follow Xiaomi's steps, just do the ordinary compiling of the Linux Kernel. There's a lot of tutorials here in xda like this ONE.
Gnome said:
Dont follow Xiaomi's steps, just do the ordinary compiling of the Linux Kernel. There's a lot of tutorials here in xda like this ONE.
Click to expand...
Click to collapse
Oi why you being lazy and not making gnome kernel and gnome ROM?
PS: you remember me? [emoji14]
Sent from my Nexus 4 using Tapatalk
Of course I know you! LOL! How you've been?
Gnome said:
Dont follow Xiaomi's steps, just do the ordinary compiling of the Linux Kernel. There's a lot of tutorials here in xda like this ONE.
Click to expand...
Click to collapse
Like I said, i've no problem with kernel compiling... I'm linux system administrator for 20years I've problem with boot.img creation Which step is skipped from that guide above...
Well ok, anyways it seems that you've compiled the boot.img successfully, did it boot?
Gnome said:
Well ok, anyways it seems that you've compiled the boot.img successfully, did it boot?
Click to expand...
Click to collapse
Nope, It hangs... Now, I'm trying to create a build environment without caf, so just a linaro-gcc crosscompiler... Because, I can't see the booting msgs, i'll try to find some patches that fix broken stuffz...
Do you have any experience about aarch64 kernels?
yup, I do, will try to build it also. Anyways off to bed now.
Gnome said:
yup, I do, will try to build it also. Anyways off to bed now.
Click to expand...
Click to collapse
ZOMG!
Code:
[email protected]:/ $ cat /proc/version
Linux version 3.10.49 ([email protected]) (gcc version 4.9.3 20150113 (prerelease) (Linaro GCC 4.9-2015.01-3) ) #1 SMP PREEMPT Thu Jul 2 15:35:05 BST 2015
[email protected]:/ $ lsmod
wlan 3877855 0 - Live 0x0000000000000000 (C)
I think, it's a beautiful day
Gnome said:
Of course I know you! LOL! How you've been?
Click to expand...
Click to collapse
LOL! I'm goodd.. how are you? mum got the xiaomi mi4i so im keeping an eye on the mi4i forum for something good and look what i find! maybe an arkenstone comeback damn the thing has real choppy animations when compared with the n4.. even the camera has choppy fps.. and the notification thing going on in miui is terrible compared to the nexus Lollipop.. Hope they fix these things.. She was using a padfone 2 before this so she didnt want the zenfone 2 thats why ended up getting the xiaomi....
dh.harald said:
ZOMG!
Code:
[email protected]:/ $ cat /proc/version
Linux version 3.10.49 ([email protected]) (gcc version 4.9.3 20150113 (prerelease) (Linaro GCC 4.9-2015.01-3) ) #1 SMP PREEMPT Thu Jul 2 15:35:05 BST 2015
[email protected]:/ $ lsmod
wlan 3877855 0 - Live 0x0000000000000000 (C)
I think, it's a beautiful day
Click to expand...
Click to collapse
CM is next
Gesendet von meinem Mi 4i mit Tapatalk