Database Info

Cannot enter fastboot mode

Im trying to install CM10, but i need to install bernie's uboot stuff.
I try to go into fastboot mode by using wkparts files but whenever i connect my phone without battery, OMAP4430 does not appear, and i cannot continue the process. How can i fix this?

xplicitjohn said:
Im trying to install CM10, but i need to install bernie's uboot stuff.
I try to go into fastboot mode by using wkparts files but whenever i connect my phone without battery, OMAP4430 does not appear, and i cannot continue the process. How can i fix this?
Click to expand...
Click to collapse
I have the same problem..

Try this before entering fast boot
Posted by xbsall:
On windows 7 sometimes OMAP4430 flashes too fast so you cant install driver.
There is a a windows feature that will help you install the driver easier.
To view devices that were once installed but are no longer attached to the computer, open a Command Prompt window using the Run As Administrator option and enter the command:
SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
Then, from the same command prompt, type devmgmt.msc to open Device Manager. Choose View, Show Hidden Devices. The new instance of Device Manager will show “ghosted” entries for devices that were once present. This technique is especially useful for fixing problems caused by leftover drivers after replacing a network card or video card—you can easily delete the ghosted device or update the OMAP4430 driver.
Sent from my LG-P920 using xda app-developers app

xplicitjohn said:
Im trying to install CM10, but i need to install bernie's uboot stuff.
I try to go into fastboot mode by using wkparts files but whenever i connect my phone without battery, OMAP4430 does not appear, and i cannot continue the process. How can i fix this?
Click to expand...
Click to collapse
berni987654321 said:
Try this before entering fast boot
Posted by xbsall:
On windows 7 sometimes OMAP4430 flashes too fast so you cant install driver.
There is a a windows feature that will help you install the driver easier.
To view devices that were once installed but are no longer attached to the computer, open a Command Prompt window using the Run As Administrator option and enter the command:
SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
Then, from the same command prompt, type devmgmt.msc to open Device Manager. Choose View, Show Hidden Devices. The new instance of Device Manager will show “ghosted” entries for devices that were once present. This technique is especially useful for fixing problems caused by leftover drivers after replacing a network card or video card—you can easily delete the ghosted device or update the OMAP4430 driver.
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
I have the OMAP driver already installed, but after running the omap4boot still nothing happens...
P.S.: Sorry for my english

Are u following the instructions
1 run omap boot
2 connect the phone with no battery
3 as soon as u see a script running insert battery DONT WAIT FOR THE 5 seconds
sent from my lg o3d
a piece of advice:
don't ask alot ..go read.

3 as soon as u see a script running insert battery DONT WAIT FOR THE 5 seconds
I don't see the script running

VladimirCicanci said:
3 as soon as u see a script running insert battery DONT WAIT FOR THE 5 seconds
I don't see the script running
Click to expand...
Click to collapse
if you don't see any script , you did'nt use omap boot , run it chose option 2, pull out battery press vol up , plug phone , omap drivers should be recognize (check in the device manager while doing this ) then pull back the battery without waiting 5 sec as the script tells you , U should see the grey LG logo ( mean that you are in fastboot mode ) , you may also see a new device in device manager called " LG COSMO " or something like that , the drivers are also in the omapboot folder
apologize my english

Yeah just like that also make shure u have omap drivers installed also manually
sent from my lg o3d
a piece of advice:
don't ask alot ..go read.

alphatia said:
Yeah just like that also make shure u have omap drivers installed also manually
Click to expand...
Click to collapse
All is done guys, thanks a lot!

anytime
sent from my lg o3d
a piece of advice:
don't ask alot ..go read.

I see omap4430 but the drivers keep disconnecting and reconnecting.
edit : im in fastboot now, but now when i try to flash things, it keeps saying < waiting for device >
edit 2 : in my device manager, OMAP4430 Fastboot usb device says that it Cannot start the Device . I have tried deleting the drivers and reinstalling, still the same error.

i enter the fastboot mode but then i get stuck after insert the command to flash
OMAP4boot for P920/P720/SU540/SU760/SU870
-------------------------------------------
by wkpark at gmail dot com
1. Prada 3.0 (SU540/KU5400/P940)
2. Optimus 3D (SU760/P920)
3. Optimus 3D Cube (SU870/P720)
x. Exit
-------------------------------------------
Please select 1,2 or exit(x): 2
Optimus 3D selected...
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: 0x3
Checksum Subblock: 0x15
CHIP: 4430
IDEN: 32c8ec90b5aed20c91f78a648de879a3de760dab
MPKH: 5f4092eccddf90fa43f546adf89508b31b9c74795e9516194c 0ea6412fdcb7f6
CRC0: 0983f41c
CRC1: 139c4f4f
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 = aabbccdd
accepted 2ndstage response
sending image to target...
size = 254252
usb_write 4
usb_write 254252
** Done **
------------------------------
Please remove USB cable
and wait until LG Logo on
then reconnent USB cable again
------------------------------
Microsoft Windows [Versão 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Todos os direitos reservados.
C:\Users\moraisbranco\Desktop\ics\omap4boot-for_optimus-v1.17b\omap4boot-for_opt
imus-v1.17b>fastboot flash u-boot u-boot.img
< waiting for device >

i get this problem. any help? only backlight on phone lights. no logo
--------------------------------------------
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] p940 - Prada 3.0 (P940)
[4] su540 - Prada 3.0 (SU540/KU5400)
[5] su760 - Optimus 3D (SU760)
[x] exit
-------------------------------------------
Select device and <ENTER> 2
p920 selected
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: 0x3
Checksum Subblock: 0x15
CHIP: 4430
IDEN: 17d9312b8da001375775a08af4da03d174a8f83e
MPKH: 5f4092eccddf90fa43f546adf89508b31b9c74795e9516194c0ea6412fdcb7f6
CRC0: 0983f41c
CRC1: 139c4f4f
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: 31
usb_read got GEN_FAILURE - got: 0, expected: 4, errno: 31
usb_read failed: 31
usb read = 0
unexpected 2ndstage response
start_fastboot.sh: usbboot: Invalid argument
------------------------------
Please remove USB cable
and wait until LG Logo on
then reconnent USB cable again
------------------------------
fastboot devices (y/N) ? and press <ENTER>

paultje162 said:
i get this problem. any help? only backlight on phone lights. no logo
--------------------------------------------
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] p940 - Prada 3.0 (P940)
[4] su540 - Prada 3.0 (SU540/KU5400)
[5] su760 - Optimus 3D (SU760)
[x] exit
-------------------------------------------
Select device and <ENTER> 2
p920 selected
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: 0x3
Checksum Subblock: 0x15
CHIP: 4430
IDEN: 17d9312b8da001375775a08af4da03d174a8f83e
MPKH: 5f4092eccddf90fa43f546adf89508b31b9c74795e9516194c0ea6412fdcb7f6
CRC0: 0983f41c
CRC1: 139c4f4f
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: 31
usb_read got GEN_FAILURE - got: 0, expected: 4, errno: 31
usb_read failed: 31
usb read = 0
unexpected 2ndstage response
start_fastboot.sh: usbboot: Invalid argument
------------------------------
Please remove USB cable
and wait until LG Logo on
then reconnent USB cable again
------------------------------
fastboot devices (y/N) ? and press <ENTER>
Click to expand...
Click to collapse
No need to multi post
Sent from my LG-SU760 using xda premium

Who need help for fastboot send me a private message with your messenger ID and i'll help you fastest i can.
Good luck.

I also got it working on my win7-32bit. So i went to my parents desktop win7-64bit and it worked out just fine without installing any drivers. (i dont know what they have done on that pc before )

[Q] what have i done wrong here (Root ics)

ive just followed this thread http://forum.xda-developers.com/showthread.php?t=2144738
and this was the output from the window
Code:
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 = aabbccdd
accepted 2ndstage response
sending image to target...
size = 255028
usb_write 4
usb_write 255028
** Done **
< waiting for device >
sending 'recovery' (6187 KB)...
OKAY [ 3.219s]
writing 'recovery'...
OKAY [ 0.766s]
finished. total time: 3.984s
You chooesd ICS//TWRP Recovery
waiting for OMAP44xx device...
when i try any combination of keys to go into recovery its just a black screen. any ideas? id it actually finish? when it says waiting for omap44xx device i tried unplugging and plugging in the cable but it did nothing

just tried to reboot normally and it says security error

if anyone can get this up and running ill thank every one of their posts for a week... i cant believe its gone wrong for me AGAIN

seriously panicing now, cant get into SW mode, i can get into fastboot and SW via wpark but the flash wont go past 17%

flash process now gets to 30% and quits

I got security error as well with that tutorial. Flashing bootloaders and recovery using this http://forum.xda-developers.com/showthread.php?t=1978543 helped.
Also - I used SmartFlash to flash bin and fls

Lg p920 ressurection

you have soft bricked or hard your Phone its easy
Now just follow the Steps and do it properly
And one more essential step is to crack.lg flash tool by changing the system date and entering the serial key the key is present somewhere in the above post search it and enter it u will crack lg flash too
Tools and files needed :-
1-bootv21e.rar from here http://d-h.st/RC5 and after downloading this file unrar it by any unzip or unrar software
2- lg usb drivers and usb cable of LG from here http://csmg.lgmobile.com:9002/data/L...in7_LGEAll.zip
3-http://csmg.lgmobile.com:9002/data/S...shTool_1.1.zip is the LG FLASH tool
4-download the .dll file from here http://www.mediafire.com/?mc6ia9o8iqwqndw
5- Optional Smart flashtool if you get get through the KEy of LG flash tool but this would be hactic and you would also need lg support tool for imei fix download links
-https://docs.google.com/file/d/0B8IkQjiPjX_DS2s1NC1zVGtLWDQ/edit?pli=1 smartflash tool
-Google LG suppot tool
Before you start READ THE GUIDE once so you can understand it and then proceed with repair.
http://d-h.st/U08 omap4420 wkparks
and google omap flashinstaller
Step1.
Install LGflashtool (also copy/paste crack)
P920 users should run LG FlashTool and load BOOTV21E_AP.bin (ONLY THE AP.BIN FILE) and keep it open but NOT ready for flashing.
SU760 users should run LG FlashTool and load SU760V10GROM (ONLY THE AP.BIN FILE) and keep it open but NOT ready for flashing.
Step 2.
Extract WKPARKS omap4boot and follow installation steps:
Install OMAP4430 USB driver
Quote:
If you plug your Phone on PC without battery, OMAP4430 device appeared for seconds and then disappeared in your Windows Device Manager
(check arsen4oo photo guide in post #3)
On windows 7 sometimes OMAP4430 flashes too fast so you cant install driver.
There is a a windows feature that will help you install the driver easier.
To view devices that were once installed but are no longer attached to the computer, open a Command Prompt window using the Run As Administrator option and enter the command:
SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
Then, from the same command prompt, type devmgmt.msc to open Device Manager. Choose View, Show Hidden Devices. The new instance of Device Manager will show “ghosted” entries for devices that were once present. This technique is especially useful for fixing problems caused by leftover drivers after replacing a network card or video card—you can easily delete the ghosted device or update the OMAP4430 driver.
After driver installation ends remove usb cable BUT keep windows device manager open.
Step 3. Run start_fastboot.bat and select option 2
Step 4. Pull out battery
Step 5. Hold Vol+
Step 6. Connect USB cable, the usbboot will start
Step 7. Insert battery while the usbboot is waiting
Step 8. Script tells you to remove cable but i dont think it's necessary in this version
Step 9. Release Vol+ and look in your Windows Device manager
If everything worked ok your phone got recognised and now you are in downoad mode.
Step 10. Change LG USB Serial Port according to LG FlashTool Guide to port 41.
Step 11. Remove cable and battery from P920/SU760
Step 12. Set LG FlashTool ready for flashing.
Step 13. Run Steps 3-9 again and you will see your phone being flashed from LG FlashTool.
It will be stopped at 26-30% because phone will turn off on its own BUT the next time you try to enter NORMAL DOWNLOAD MODE it will be available again.
Step 14. Set LG FlashTool ready to flash your P920 with BOOTV21E_AP.bin again.
SU760 users should use SU760V10GROM bin .
Step 15. Put your phone in DOWNLOAD MODE without using omap4boot this time.
Step 16. LG FlashTool will recognise the phone and flash it completely this time.
P920 after reboot will go to CWM. You can flash your personal backup or reboot to STOCK V21E.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
5-Restoring IMEI
a.Connect phone by USB
b.Activate USB debug mode
c.Enter 3845#*920# in dialer if that doesn’t work try 3845#*925# or 3845#*720# if device is SU760
d.Select Port Settings -> Select CP Image Download
e.A new device should appear at let it install
f.Open Tutty (or hyperterminal) and select serial protocol. Click on open
g.Type AT if response is not OK, change port number (it is possible that when typing you don’t see any letters)
h.Type at%imei, it should display a dummy IMEI
i.Type at%imei=x,x,x,x,x,x,x,x,x,x,x,x,x,x,x where x,x,x... is your orginal IMEI number (found under the battery of your phone). It should response IMEI WRITE OK
j.Reboot phone
if u dont understand it LG support tool will so
6-now open lg suppot tool and remove battery follow step 4 till u get the download mode with S/w and something written in chinese and wait till phone is detected now click customer Support and then recovery Phone then you will be asked for imei insert the imei and it will recognise ur pphone press ok depending on the speed of ur internet connection it will take the time to download the files and update ur phone let the whole procedure complete with me it took around one hour
7- after the process is completed disconnected the phone insert battery and boot ur phoen again it will boot and now again u will find the same issue but this time the trick is simple and easy ur internal memory curropted so format it u will get around 5.57gb and then .Enter 3845#*920# in dialer and do a factory reset or a normal factory reset after reset ur phone wll boot and display android and a package and the loading bar this means the phone is fixed with imei and u will get what you need have a look at the attachment and the vidoe on youtube i have posted [YOUTUBE]http://www.youtube.com/watch?v=BR1_jrsAibk[YOUTUBE]
the last step of factory reset is essential or you wont fix the imei
all the best
download reebooter utility from here http://d-h.st/24C
and do this
Info:
This utility will not work if you don't have Omap Drivers installed
Select task:
1. Flash ICS FastbootLoaders+Recovery
2. Flash V21E Loaders+Recovery
x. Exit
----------------------------------------
Please select 1,2 or exit(x): 2
Ready to Flash V21E+recovery
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: 0x3
Checksum Subblock: 0x15
CHIP: 4430
IDEN: 40a11fbe08c36fb34f6a113fc2516c63395c7947
MPKH: 5f4092eccddf90fa43f546adf89508b31b9c74795e9516194c0ea6412fdcb7f6
CRC0: 0983f41c
CRC1: 139c4f4f
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 = aabbccdd
accepted 2ndstage response
sending image to target...
size = 232512
usb_write 4
usb_write 232512
** Done **
< waiting for device >
sending 'recovery' (5854 KB)...
OKAY [ 3.012s]
writing 'recovery'...
OKAY [ 1.230s]
finished. total time: 4.252s
sending 'u-boot' (512 KB)...
OKAY [ 0.268s]
writing 'u-boot'...
OKAY [ 0.355s]
finished. total time: 0.627s
sending 'x-loader' (128 KB)...
OKAY [ 0.070s]
writing 'x-loader'...
OKAY [ 0.051s]
finished. total time: 0.127s
Loaders have been flashed.
Your P920 is ready to boot into GB again. Reboot.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
GOOD LUCK and lets get those bricks fixed.
TROUBLESHOOTING
If you get the Silver LG Screen u are on Fastboot mode
if you get a message like usb not recognised then u probably have a faulty cable
all the Best f++k the Brick:good:
If something doesn't work for you make a post describing exactly what you did , your phone model and your operating system.
Before making pointless posts READ THE GUIDE.
If you don't know how to make one of the recovery programs work READ THEIR GUIDE .
You can find links in the end of this post.
http://forum.xda-developers.com/showthread.php?p=18134614
http://forum.xda-developers.com/showthread.php?t=1629307
http://forum.xda-developers.com/showthread.php?t=1244490
http://forum.xda-developers.com/showthread.php?t=1540163
Sent from my LG-P920 using xda premium
I will edit this thread for the atachments so wait for it

And one more essential step is to crack.lg flash tool by changing the system date and entering the serial key the key is present somewhere in the above post search it and enter it u will crack lg flash too
Sent from my LG-P920 using xda premium

This is more or less a duplicate of the thread below
http://forum.xda-developers.com/showthread.php?t=1942836&page=58
Thread Closed

somthing intresting help unbrick

[PWRAP] pwrap_init_preloader
[PWRAP] pwrap_init
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=0 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=1 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=2 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=3 rdata=5AA5
[PMIC_WRAP]wrap_init pass,the return value=0.
pl pmic init start
pl pmic efuse start
pl pmic efuse BUCK trim
[0x1C8]=0xF802
[0x1CA]=0x807F
[0x20E]=0xE0
[0x260]=0xF0
[0x286]=0xF0
pl pmic efuse end
pl pmic en rst [0x126]=0x13
[0xE]=0x1
[0x540]=0xA0
Battery exist
[0xE]=0x1
[0x540]=0xA0
pl vm read [0x290]=0x50
pl vm set [0x290]=0x52
pl vm check [0x290]=0x52
pl pmic init done
[PLFM] Init I2C: OK(0)
[PLFM] Init PWRAP: OK(0)
[PLFM] Init PMIC: OK(0)
[PLFM] chip[CA00]
[I2C][PL] [i2c0 write] i2c transaction complate
[BLDR] Build Time: 20140218-141828
==== Dump RGU Reg ========
RGU MODE: 75
RGU LENGTH: FFE0
RGU STA: 40000000
RGU INTERVAL: FFF
RGU SWSYSRST: 0
==== Dump RGU Reg End ====
RGU: g_rgu_satus:2
mtk_wdt_mode_config mode value=35, tmp:22000030
PL RGU RST: ??
SW reset with bypass power key flag
Find bypass powerkey flag
mtk_wdt_mode_config mode value=70, tmp:22000071
kpd register for pmic set!
mt_usb_calibraion: input_reg = 0x0
mt_usb_calibraion: term_vref = 0x0, clkref = 0x0, vrt_vref = 0x0,
[RTC] bbpu = 0x5, con = 0x426
[RTC] irqsta = 0x0, pdn1 = 0x0, pdn2 = 0x201, spar0 = 0x40, spar1 = 0x800
[RTC] new_spare0 = 0x0, new_spare1 = 0x1, new_spare2 = 0x1, new_spare3 = 0x1
[RTC] bbpu = 0x5, con = 0x424
SW reset with bypass power key flag
SW reset with bypass power key flag
[PLFM] WDT reboot bypass power key!
p1 pmic read INT_RSV(bit7)[0x138][0x80]
[RTC] rtc_bbpu_power_on done
[SD0] Bus Width: 1
[SD0] SET_CLK(260kHz): SCLK(259kHz) MODE(0) DDR(0) DIV(193) DS(0) RS(0)
[SD0] Switch to High-Speed mode!
[SD0] SET_CLK(260kHz): SCLK(259kHz) MODE(2) DDR(1) DIV(96) DS(0) RS(0)
[SD0] Bus Width: 8
[SD0] Size: 3696 MB, Max.Speed: 52000 kHz, blklen(512), nblks(7569408), ro(0)
[SD0] Initialized
[SD0] SET_CLK(52000kHz): SCLK(50000kHz) MODE(2) DDR(1) DIV(0) DS(0) RS(0)
msdc_ett_offline_to_pl: size<2> m_id<0x90>
msdc <0> <HYNIX > <H4G1d>
msdc <1> <xxxxxx> <H4G1d>
msdc failed to find
*******EMMC_INFO*******
eMMC partition size(1 block = 512Bytes):
BOOT1:<4096> blocks
BOOT2:<4096> blocks
RPMB :<4096> blocks
GP1 :<0> blocks
GP2 :<0> blocks
GP3 :<0> blocks
GP4 :<0> blocks
USER :<7569408> blocks
*******EMMC_INFO*******
fw id len:1
found:1,i:1
[EMI] DDR2
[EMI] eMMC/NAND ID = 90,1,4A,48,34,47,31,64,4
[EMI] MDL number = 1
[MEM] 1066 MHZ
rank 0 coarse = 15
rank 0 fine = 48
10:| 0 0 1 1 1 0
opt_dle value:8
rank 1 coarse = 15
rank 1 fine = 48
10:| 0 0 1 1 1 0
opt_dle value:8
byte:0, (DQS,DQ)=(8,8)
byte:1, (DQS,DQ)=(8,A)
byte:2, (DQS,DQ)=(8,8)
byte:3, (DQS,DQ)=(8,A)
[EMI] DRAMC calibration passed
[EMI] DQSINCTL:50000
[MEM] complex R/W mem test pass
[PLFM] Init Boot Device: OK(0)
[ROM_INFO] 'v2','0x2700000','0x20000','0x46C0000','0x2C00'
[SEC_K] SML KEY AC = 0
[SEC_K] SBC_PUBK Found
[SEC] AES Legacy : 0
[SEC] SECCFG AC : 1
[SEC] read '0x2700000'
0x41,0x4E,0x44,0x5F,0x53,0x45,0x43,0x43,
[LIB] SecLib.a '20121226-155014'
[LIB] CFG read size '0x4000' '0x1860'
[LIB] Name = SOMC
[LIB] Config = 0x11, 0x11
0x31,0x41,0x35,0x35
0x6F679858
[LIB] HW DEC
0x49494949
[LIB] SEC CFG 'v3' exists
[LIB] Status = 0x43434343
[LIB] ty = 0 , ld = 0
[PART] Image with part header
[PART] name : LK
[PART] addr : FFFFFFFFh
[PART] size : 316772
[PART] magic: 58881688h
[PART] load "UBOOT" from 0x0000000003960200 (dev) to 0x81E00000 (mem) [SUCCESS]
[PART] load speed: 9374KB/s, 316772 bytes, 33ms
[LIB] HW DEC
[SECRO] secroimg '0x41414141'
[SECRO] secroimg '0x35353535'
[SECRO] factory mode enabled
[AUTHEN] rsa.N length = 1024 bytes
[AUTHEN] rsa.E length = 20 bytes
[LIB] Verify 'UBOOT'
0x43434343
[LIB] part load '0x3960000'
[AUTHEN] 0x53,0x53,0x53,0x53
[AUTHEN] verify signature ... pass
[LIB] Verify 'LOGO'
0x43434343
[LIB] part load '0x4D40000'
[AUTHEN] 0x53,0x53,0x53,0x53
[AUTHEN] verify signature ... failed, error is 7
[SECLIB_IMG_VERIFY] Signature Fail.
[LIB] Fail (0x0)
<ASSERT> sec_boot.c:line 181 0
[PLFM] preloader fatal error...
[PLFM] emergency download mode(timeout: 30s).
mtk_arch_reset at pre-loader!
this is console with serial interface
i will post picture with pin layaut

how to unbrick?

botioni said:
[PWRAP] pwrap_init_preloader
[PWRAP] pwrap_init
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=0 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=1 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=2 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=3 rdata=5AA5
[PMIC_WRAP]wrap_init pass,the return value=0.
pl pmic init start
pl pmic efuse start
pl pmic efuse BUCK trim
[0x1C8]=0xF802
[0x1CA]=0x807F
[0x20E]=0xE0
[0x260]=0xF0
[0x286]=0xF0
pl pmic efuse end
pl pmic en rst [0x126]=0x13
[0xE]=0x1
[0x540]=0xA0
Battery exist
[0xE]=0x1
[0x540]=0xA0
pl vm read [0x290]=0x50
pl vm set [0x290]=0x52
pl vm check [0x290]=0x52
pl pmic init done
[PLFM] Init I2C: OK(0)
[PLFM] Init PWRAP: OK(0)
[PLFM] Init PMIC: OK(0)
[PLFM] chip[CA00]
[I2C][PL] [i2c0 write] i2c transaction complate
[BLDR] Build Time: 20140218-141828
==== Dump RGU Reg ========
RGU MODE: 75
RGU LENGTH: FFE0
RGU STA: 40000000
RGU INTERVAL: FFF
RGU SWSYSRST: 0
==== Dump RGU Reg End ====
RGU: g_rgu_satus:2
mtk_wdt_mode_config mode value=35, tmp:22000030
PL RGU RST: ??
SW reset with bypass power key flag
Find bypass powerkey flag
mtk_wdt_mode_config mode value=70, tmp:22000071
kpd register for pmic set!
mt_usb_calibraion: input_reg = 0x0
mt_usb_calibraion: term_vref = 0x0, clkref = 0x0, vrt_vref = 0x0,
[RTC] bbpu = 0x5, con = 0x426
[RTC] irqsta = 0x0, pdn1 = 0x0, pdn2 = 0x201, spar0 = 0x40, spar1 = 0x800
[RTC] new_spare0 = 0x0, new_spare1 = 0x1, new_spare2 = 0x1, new_spare3 = 0x1
[RTC] bbpu = 0x5, con = 0x424
SW reset with bypass power key flag
SW reset with bypass power key flag
[PLFM] WDT reboot bypass power key!
p1 pmic read INT_RSV(bit7)[0x138][0x80]
[RTC] rtc_bbpu_power_on done
[SD0] Bus Width: 1
[SD0] SET_CLK(260kHz): SCLK(259kHz) MODE(0) DDR(0) DIV(193) DS(0) RS(0)
[SD0] Switch to High-Speed mode!
[SD0] SET_CLK(260kHz): SCLK(259kHz) MODE(2) DDR(1) DIV(96) DS(0) RS(0)
[SD0] Bus Width: 8
[SD0] Size: 3696 MB, Max.Speed: 52000 kHz, blklen(512), nblks(7569408), ro(0)
[SD0] Initialized
[SD0] SET_CLK(52000kHz): SCLK(50000kHz) MODE(2) DDR(1) DIV(0) DS(0) RS(0)
msdc_ett_offline_to_pl: size<2> m_id<0x90>
msdc <0> <HYNIX > <H4G1d>
msdc <1> <xxxxxx> <H4G1d>
msdc failed to find
*******EMMC_INFO*******
eMMC partition size(1 block = 512Bytes):
BOOT1:<4096> blocks
BOOT2:<4096> blocks
RPMB :<4096> blocks
GP1 :<0> blocks
GP2 :<0> blocks
GP3 :<0> blocks
GP4 :<0> blocks
USER :<7569408> blocks
*******EMMC_INFO*******
fw id len:1
found:1,i:1
[EMI] DDR2
[EMI] eMMC/NAND ID = 90,1,4A,48,34,47,31,64,4
[EMI] MDL number = 1
[MEM] 1066 MHZ
rank 0 coarse = 15
rank 0 fine = 48
10:| 0 0 1 1 1 0
opt_dle value:8
rank 1 coarse = 15
rank 1 fine = 48
10:| 0 0 1 1 1 0
opt_dle value:8
byte:0, (DQS,DQ)=(8,8)
byte:1, (DQS,DQ)=(8,A)
byte:2, (DQS,DQ)=(8,8)
byte:3, (DQS,DQ)=(8,A)
[EMI] DRAMC calibration passed
[EMI] DQSINCTL:50000
[MEM] complex R/W mem test pass
[PLFM] Init Boot Device: OK(0)
[ROM_INFO] 'v2','0x2700000','0x20000','0x46C0000','0x2C00'
[SEC_K] SML KEY AC = 0
[SEC_K] SBC_PUBK Found
[SEC] AES Legacy : 0
[SEC] SECCFG AC : 1
[SEC] read '0x2700000'
0x41,0x4E,0x44,0x5F,0x53,0x45,0x43,0x43,
[LIB] SecLib.a '20121226-155014'
[LIB] CFG read size '0x4000' '0x1860'
[LIB] Name = SOMC
[LIB] Config = 0x11, 0x11
0x31,0x41,0x35,0x35
0x6F679858
[LIB] HW DEC
0x49494949
[LIB] SEC CFG 'v3' exists
[LIB] Status = 0x43434343
[LIB] ty = 0 , ld = 0
[PART] Image with part header
[PART] name : LK
[PART] addr : FFFFFFFFh
[PART] size : 316772
[PART] magic: 58881688h
[PART] load "UBOOT" from 0x0000000003960200 (dev) to 0x81E00000 (mem) [SUCCESS]
[PART] load speed: 9374KB/s, 316772 bytes, 33ms
[LIB] HW DEC
[SECRO] secroimg '0x41414141'
[SECRO] secroimg '0x35353535'
[SECRO] factory mode enabled
[AUTHEN] rsa.N length = 1024 bytes
[AUTHEN] rsa.E length = 20 bytes
[LIB] Verify 'UBOOT'
0x43434343
[LIB] part load '0x3960000'
[AUTHEN] 0x53,0x53,0x53,0x53
[AUTHEN] verify signature ... pass
[LIB] Verify 'LOGO'
0x43434343
[LIB] part load '0x4D40000'
[AUTHEN] 0x53,0x53,0x53,0x53
[AUTHEN] verify signature ... failed, error is 7
[SECLIB_IMG_VERIFY] Signature Fail.
[LIB] Fail (0x0)
<ASSERT> sec_boot.c:line 181 0
[PLFM] preloader fatal error...
[PLFM] emergency download mode(timeout: 30s).
mtk_arch_reset at pre-loader!
this is console with serial interface
i will post picture with pin layaut
Click to expand...
Click to collapse
how did you check this out?

theonecallednick said:
how did you check this out?
Click to expand...
Click to collapse
I found uart pin on mainboard for debuging .
with serial usb cable pl2303

This is the red light only and unknown hardware found (the unknown hardware is in fact mtk usb vcom driver buth sony version ) if you try sp flash tool for mtk then it comunicates with de phone buth it needs some authentication file.

Help..
I am also having same problem..I falshed wrong rom..
It just shows red led and does not detects by PC...
Were you able to solve the problem..if yes..please help..

botioni said:
[PWRAP] pwrap_init_preloader
[PWRAP] pwrap_init
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=0 rdata=5AA5
.........................
this is console with serial interface
i will post picture with pin layaut
Click to expand...
Click to collapse
Samuel Wankhede said:
I am also having same problem..I falshed wrong rom..
It just shows red led and does not detects by PC...
Were you able to solve the problem..if yes..please help..
Click to expand...
Click to collapse
Try the guide given in thread linked below
http://forum.xda-developers.com/showpost.php?p=57614511&postcount=13

Please share uart pinout
Baudrate should be 115200??
Thanks

uart
please share the uart pinout , thanks

[SOLVED]Missing Preloader on MTK6762, recognized as "MT6227 Phone"

A long time ago I hard bricked my daily dialer and in a fit of desperation I formated the preloader (silly me, should've looked for a boot-lock bypass instead!) and so, I can't flash anything on my phone anymore as it throws a STATUS_BROM_CMD_FAIL error (using the all in one DA or the one provided by Hovatek yields identical results)
The Vol +/- buttons don't let me flash, removing the battery doesn't help, tespins neither and 'lsusb -v' only recognizes my phone as an MT6227 Phone with a V/PID of 0e8d:003.
here's the output of 'lsusb -v'
Code:
Bus 001 Device 079: ID 0e8d:0003 MediaTek Inc. MT6227 phone
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 2 Communications
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0e8d MediaTek Inc.
idProduct 0x0003 MT6227 phone
bcdDevice 1.00
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0043
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 2 Abstract (modem)
bInterfaceProtocol 1 AT-commands (v.25ter)
iInterface 1 comm_if̦data_if̄Љ召
CDC Header:
bcdCDC 1.10
CDC ACM:
bmCapabilities 0x0f
connection notifications
sends break
line coding and serial state
get/set/clear comm features
CDC Union:
bMasterInterface 0
bSlaveInterface 1
CDC Call Management:
bmCapabilities 0x03
call management
use DataInterface
bDataInterface 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 2 data_if̄Љ召呪풅ཊꤛ漢䕄礤
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
can't get debug descriptor: Resource temporarily unavailable
Device Status: 0x0000
(Bus Powered)
I've searched far and wide for documentation on flashing both an MTK6762/5 chip and an MT6227 chip (best I found was a technicall brief).
I tried to get my hands on the DA for the MT6227 but I only ever found ones for a MT626X.
I've tried searching for general flashing tools, found like two and neither work with cdc connections or something.
so my request would be; does anyone of you know of any flash chip documentation repos or guides on low level flashing over a serial usb connection?
I am desperate.

I'm not sure what your exact issue is but there was some recent work bypassing SLA/DAA to be able to flash using SP Flash, maybe give this a try
[MOD][DEV] MediaTek / MTK - Auth Bypass (SLA/DAA) - Utility

StonedEngineer97 said:
I'm not sure what your exact issue is but there was some recent work bypassing SLA/DAA to be able to flash using SP Flash, maybe give this a try
[MOD][DEV] MediaTek / MTK - Auth Bypass (SLA/DAA) - Utility
Click to expand...
Click to collapse
Been there, done that.
you want to know the funny part? the exploits don't work on mine!
Even though it appears to be a 6765 it's actually a 6762 so it's not really supported.
I can dump the rom just fine, but I can't flash anything.
anyway, thanks for replying!

Answering my own thread again.
using MTK Client python script found on github I was able to flash all partitions without fail and only booting as per usual, the script automatically crashes the preloader (if available) to BROM and writes the memory
if there isn't a preloader, it just writes the image.
MTK Client is a God-sent for me and an objective replacement for SP Flash Tool, I can not recomend it enough!

Qwerty_in_me said:
Answering my own thread again.
using MTK Client python script found on github I was able to flash all partitions without fail and only booting as per usual, the script automatically crashes the preloader (if available) to BROM and writes the memory
if there isn't a preloader, it just writes the image.
MTK Client is a God-sent for me and an objective replacement for SP Flash Tool, I can not recomend it enough!
Click to expand...
Click to collapse
Any way you can tell me the script you used? Thanks

Tesh3180 said:
Any way you can tell me the script you used? Thanks
Click to expand...
Click to collapse
it's github.com/bkerler/mtkclient
worked miracles for me, I even got my phone back to operational, but then bricked it again and haven't touched it since

Qwerty_in_me said:
Answering my own thread again.
using MTK Client python script found on github I was able to flash all partitions without fail and only booting as per usual, the script automatically crashes the preloader (if available) to BROM and writes the memory
if there isn't a preloader, it just writes the image.
MTK Client is a God-sent for me and an objective replacement for SP Flash Tool, I can not recomend it enough!
Click to expand...
Click to collapse
How/What did you flash? I've got MTK Client all set up and connected to my phone, and can read the partitions off of it. My phone is hardbricked, can't access fastboot either.

Yuarian said:
How/What did you flash? I've got MTK Client all set up and connected to my phone, and can read the partitions off of it. My phone is hardbricked, can't access fastboot either.
Click to expand...
Click to collapse
I flashed a stock ROM if I recall correctly, it's been a while...

Qwerty_in_me said:
I flashed a stock ROM if I recall correctly, it's been a while...
Click to expand...
Click to collapse
Can you help me with this error?
{
"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"
}

mvikrant97 said:
Can you help me with this error?
View attachment 5851493
Click to expand...
Click to collapse
seems simple enough, if you have a mtk6765/6762 (they're the same chip) you probably have a broken install. if you used the official repo, try cloning it again.
you honestly didn't give me much to work with, I'd need to know the mtkclient version you are using, packaged or built, and the chipset you have as it might not be supported by mtkclient.