Related
Hello, i think my Optimus 2x is bricked. I flashed a wrong ROM and it would "freeze" at the LG logo. So I followed a guide that said would flash the phone to stock with NVflash. Anyway the guide said that I should go back to EXT3 FIRST before flashing but I forgot and now the phone won't even boot. Nothing happens when trying to turn it on. However my PC still sees APX/Nvidia recovery whatever when i plug it in.
Help.
If you download the nvflash kit from modaco by Paul, it will flash v10d on your phone. It creates the partitions and does not require ext3 or any specific format. It has always worked for me. I am not on my PC and hence cannot give you the link. Remember, remove battery and plug USB cable with both, I repeat both volume up and down pressed down to get into nvflash mode.
hackworks said:
If you download the nvflash kit from modaco by Paul, it will flash v10d on your phone. It creates the partitions and does not require ext3 or any specific format. It has always worked for me. I am not on my PC and hence cannot give you the link. Remember, remove battery and plug USB cable with both, I repeat both volume up and down pressed down to get into nvflash mode.
Click to expand...
Click to collapse
It doesn't work. The phone doesn't enter NVflash mode(the screen stays black). It's strange though that my PC still sees it.
I tried this http://forum.xda-developers.com/showthread.php?t=1229407 this is what i get:
Please pick a recovery, or exit [1,2,X]?1
Attempting to flash internal recovery...
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x033c2087415ff597
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
download command failed NvError 0x120002
command failure: bootloader download failed (bad data)
bootloader status: Bct file not found (code: 21) message: flags: 1073840124
I'll try to find that nvflash kit...
But if that doesn't work either... ??
Still stays black? If I remember rightly, with NVFlash.. you remove the battery, Hold down some buttons (MAKE SURE YOU ARE HOLDING DOWN THE RIGHT ONES as per pauls/rustys instructions) plug in the phone, then have to install the drivers. The screen will stay black.
You then run NVFlash itself.
Scougar said:
Still stays black? If I remember rightly, with NVFlash.. you remove the battery, Hold down some buttons (MAKE SURE YOU ARE HOLDING DOWN THE RIGHT ONES as per pauls/rustys instructions) plug in the phone, then have to install the drivers. The screen will stay black.
You then run NVFlash itself.
Click to expand...
Click to collapse
Do you have a link to pauls/rustys instructions and thread?
Have you tried smartflash tool? It have always solve my problems.
You can find instructions here http://forum.xda-developers.com/showthread.php?t=1008070
In dev section is a thread with firmawares to download to flash. If the links are dead, google for some, you will find it somewhere on the net.
Memhis said:
Have you tried smartflash tool? It have always solve my problems.
You can find instructions here http://forum.xda-developers.com/showthread.php?t=1008070
In dev section is a thread with firmawares to download to flash. If the links are dead, google for some, you will find it somewhere on the net.
Click to expand...
Click to collapse
It doesn't work. My phone seems to be stuck in APX mode. Doesn't matter what I do, if i plug it Windows says APX. There has to be a way! But the phone doesn't react to any buttons, whatever I hold, or do, it's still in APX mode and dead.
plig in your tel in nvflash mode and go to menage\device menager and unistal nvidia drivers for apx , reinstal lg usb driver with new and istall again nvidia usb driver (APX) and flash stock rom via nvflash method ....
Any luck?
xalix said:
plig in your tel in nvflash mode and go to menage\device menager and unistal nvidia drivers for apx , reinstal lg usb driver with new and istall again nvidia usb driver (APX) and flash stock rom via nvflash method ....
Click to expand...
Click to collapse
itsanden said:
Hello, i think my Optimus 2x is bricked. I flashed a wrong ROM and it would "freeze" at the LG logo. So I followed a guide that said would flash the phone to stock with NVflash. Anyway the guide said that I should go back to EXT3 FIRST before flashing but I forgot and now the phone won't even boot. Nothing happens when trying to turn it on. However my PC still sees APX/Nvidia recovery whatever when i plug it in.
Help.
Click to expand...
Click to collapse
Hi there,
Did you have any luck getting your p990 out of this state? same happened to mine and I don't know what else to do!?
Thanks!
EDIT:
This is what rusty's NVFlash gives me (which actually is the same problem as for itsanden's code.):
(I don't know how to copy the text from the NVFlash by modaco, since the window closes automaticaly)
"
-------------------------------
Russ' NVFlash Recovery Flasher
1. CWM 4.0.1.5 Internal
2. CWM 4.0.1.5 External
X. Exit
-------------------------------
Please pick a recovery, or exit [1,2,X]?2
Attempting to flash external recovery...
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x028841484180d657
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
download command failed NvError 0x120002
command failure: bootloader download failed (bad data)
bootloader status: Bct file not found (code: 21) message: flags: 1073840124
-------------------------------
Program will now exit
"
You need to access at least your cwm recovery to flash stock v20q then reset to factory reset or hard format
Sent from my Optimus 2X using xda premium
mdjpinto said:
Hi there,
Did you have any luck getting your p990 out of this state? same happened to mine and I don't know what else to do!?
Thanks!
EDIT:
This is what rusty's NVFlash gives me (which actually is the same problem as for itsanden's code.):
(I don't know how to copy the text from the NVFlash by modaco, since the window closes automaticaly)
"
-------------------------------
Russ' NVFlash Recovery Flasher
1. CWM 4.0.1.5 Internal
2. CWM 4.0.1.5 External
X. Exit
-------------------------------
Please pick a recovery, or exit [1,2,X]?2
Attempting to flash external recovery...
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x028841484180d657
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
download command failed NvError 0x120002
command failure: bootloader download failed (bad data)
bootloader status: Bct file not found (code: 21) message: flags: 1073840124
-------------------------------
Program will now exit
"
Click to expand...
Click to collapse
Firstly try to flash a baseband (I suggest 208 v10b, or the latest v20s' one), then go with nvflash..
grimmyrippy said:
You need to access at least your cwm recovery to flash stock v20q then reset to factory reset or hard format
Sent from my Optimus 2X using xda premium
Click to expand...
Click to collapse
That would b straight forward if I could turn on my phone. NVFlash Recovery doesn't fix as well, despite running and detecting the phone.
The only way it responds is the APX on windows. I've tried NVFlashing it to restore the rom to 2.2 but it gives me an error when transferring System.img
This it what i got from cmd:
C:\Users\Dinis\Desktop\desktop\android\Emergency>. \nvflash.exe --bct E1108_Hynix
_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --setbct --odmdata 0xC8000 --co
nfigfile android_fastboot_emmc_full.cfg --create --bl fastboot.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x028841484180d657
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct
- 4080/4080 bytes sent
E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct sent successfully
odm data: 0xc8000
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBR
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: EB1
creating partition: LNX
creating partition: EB2
creating partition: DRM
creating partition: EB3
creating partition: SOS
creating partition: EB4
creating partition: UDA
creating partition: EB5
creating partition: UDB
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBR please wait.. done!
Formatting partition 6 APP please wait.. done!
Formatting partition 7 CAC please wait.. done!
Formatting partition 8 MSC please wait.. done!
Formatting partition 9 EB1 please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 EB2 please wait.. done!
Formatting partition 12 DRM please wait.. done!
Formatting partition 13 EB3 please wait.. done!
Formatting partition 14 SOS please wait.. done!
Formatting partition 15 EB4 please wait.. done!
Formatting partition 16 UDA please wait.. done!
Formatting partition 17 EB5 please wait.. done!
Formatting partition 18 UDB please wait.. done!
done!
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
sending file: system.img
- 851968/358400000 bytes sentdata send failed NvError 0x120002
command failure: create failed (bad data)
---------- Post added at 08:52 AM ---------- Previous post was at 08:47 AM ----------
markop90 said:
Firstly try to flash a baseband (I suggest 208 v10b, or the latest v20s' one), then go with nvflash..
Click to expand...
Click to collapse
Is there a way to do that without SmartFlashTool? because if my phone is stuck in APX smartflash won't detect! I have multiple bb ready to flash but i can't do it with smartflash.
Thanks though!
It could be an hw problem.. maybe nand is damaged..
Inviato dal mio Optimus 2X
Byteater said:
It could be an hw problem.. maybe nand is damaged..
Inviato dal mio Optimus 2X
Click to expand...
Click to collapse
(probably noob question) what is nand?
mdjpinto said:
(probably noob question) what is nand?
Click to expand...
Click to collapse
It includes the main partition ("/", where system files are located) and the internal storage
Inviato dal mio Optimus 2X
hELLO.
I bricked my phone 2 days ago.
only one thing worked for me
http://forum.xda-developers.com/showthread.php?t=1715272
NV Flash Homero Rom.
(If you got some problem to fdownload the roms concerned, even part 1 of the rom works by itself)
No battery in your phone. button Volume - and volume +. nothing appears on the phone when you plug it, but it is good to flash with nvflash.
Enjoy and thanks to Homero.
Aggree.
I got mine totally black, no sparks when I plugged the charger. Using google I found a similar case which lead me to use nvflash.
First thing I did was make sure that my win7 can recognize nvidia chip.
Next I downloaded some nvflash packages, which consist stock rom. ( some of packages provided w/ .bat file. Many of them can‘t be used on mine ).( watch out for antivirus responses )
Now I got froyo back on my 2x.
Sent from my LG-P990 using xda app-developers app
Hi, can you guys think of a reason why neither a Win7(64 bit) nor Vista(64 bit) PC wouldn't recognise the phone in NVfalsh mode as an APX device? I was able to do it a while ago but I think back then I was running XP(32 bit). I've read that (64 bit) machines struggle sometimes with the NVFlash process but I thought I'd be able to get my system to recognise the APX device. I really need to flash a clean rom as CM10 is going berserk on my phone. Keep getting BSODs and in general the device feels sluggish most of the time. Any advice?
bedevil99 said:
Hi, can you guys think of a reason why neither a Win7(64 bit) nor Vista(64 bit) PC wouldn't recognise the phone in NVfalsh mode as an APX device? I was able to do it a while ago but I think back then I was running XP(32 bit). I've read that (64 bit) machines struggle sometimes with the NVFlash process but I thought I'd be able to get my system to recognise the APX device. I really need to flash a clean rom as CM10 is going berserk on my phone. Keep getting BSODs and in general the device feels sluggish most of the time. Any advice?
Click to expand...
Click to collapse
try this method
http://forum.xda-developers.com/showthread.php?t=2007325
there is a problem in win7 x64 (or 8 x64) with driver signature sometimes... so try to add the apx drivers manually from device manager...
Thanks for your help mate, I'll give this a go
Sent from my LG-P990 using xda app-developers app
Hello, i think my Optimus 2x is bricked. I flashed a wrong ROM and it would "freeze" at the LG logo. So I followed a guide that said would flash the phone to stock with NVflash. Anyway the guide said that I should go back to EXT3 FIRST before flashing but I forgot and now the phone won't even boot. Nothing happens when trying to turn it on. However my PC still sees APX/Nvidia recovery whatever when i plug it in.
Help.
Try this: http://forum.xda-developers.com/showthread.php?t=1229407
Also if nvflash doesn't work, try smartflash!
There is numerous threads with title brick, bricked and etc. Little search would be nice...
You can read my answer here -> http://forum.xda-developers.com/showpost.php?p=24024818&postcount=6
SP1996AC said:
Try this: http://forum.xda-developers.com/showthread.php?t=1229407
Also if nvflash doesn't work, try smartflash!
Click to expand...
Click to collapse
Tried that... The thing is, the phone seems to be completely DEAD. Reacts to nothing.
Please pick a recovery, or exit [1,2,X]?1
Attempting to flash internal recovery...
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x033c2087415ff597
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
download command failed NvError 0x120002
command failure: bootloader download failed (bad data)
bootloader status: Bct file not found (code: 21) message: flags: 1073840124
I got the same results even when not holding vol up and down. But I'll try Memhis link.
Memhis said:
There is numerous threads with title brick, bricked and etc. Little search would be nice...
You can read my answer here -> http://forum.xda-developers.com/showpost.php?p=24024818&postcount=6
Click to expand...
Click to collapse
Yeah sorry I'm just really worried right now. It's not really my phone, so I'm trying to get it fixed quick. Thanks for the link
Memhis said:
There is numerous threads with title brick, bricked and etc. Little search would be nice...
You can read my answer here -> http://forum.xda-developers.com/showpost.php?p=24024818&postcount=6
Click to expand...
Click to collapse
It doesn't work! The phone is stuck in APX mode! Doesn't matter what I do, if i plug it Windows says APX. There has to be a way! But the phone doesn't react to any buttons, whatever I hold, or do, it's still in APX mode and dead.
install lg drivers and flash kdz firmware and then root the phone!
on the first post, i had the same problem a week ago. what fixed my phone was flash stock ROM using smartflash, with the .fls and .bin file. its just like newly bought phone after the flash. hope it helps!
Sent from my Optimus 2X using XDA
mrgian said:
on the first post, i had the same problem a week ago. what fixed my phone was flash stock ROM using smartflash, with the .fls and .bin file. its just like newly bought phone after the flash. hope it helps!
Sent from my Optimus 2X using XDA
Click to expand...
Click to collapse
I guess I have my p990 also stuck in APX mode. Smartflash doesn't detect my phone, and NVFlash (recovery) returns:
Please pick a recovery, or exit [1,2,X]?2
Attempting to flash external recovery...
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x028841484180d657
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
download command failed NvError 0x120002
command failure: bootloader download failed (bad data)
bootloader status: Bct file not found (code: 21) message: flags: 1073840124
Which is the same problem as ITSANDEN
Thing is, I ran xda forum end to end looking for people with same trouble as I and I could not find any help. It's like a loop! LOL
If nvflash doesn't work use Smartflash, and vice versa.... LOL :frustrated:
Anyway, I'll keep looking.
---------- Post added at 08:15 PM ---------- Previous post was at 07:33 PM ----------
mrgian said:
on the first post, i had the same problem a week ago. what fixed my phone was flash stock ROM using smartflash, with the .fls and .bin file. its just like newly bought phone after the flash. hope it helps!
Sent from my Optimus 2X using XDA
Click to expand...
Click to collapse
Memhis said:
There is numerous threads with title brick, bricked and etc. Little search would be nice...
You can read my answer here -> http://forum.xda-developers.com/showpost.php?p=24024818&postcount=6
Click to expand...
Click to collapse
Unfortunately SmartFlashTool doesn't work since the phone is running in APX and doesn't create port connection that SFT software can recognize.
Try to nvflash whole rom not just recovery. Ie pauls v10b. I hope it will work for you.
Sent from my LG-P990 using xda app-developers app
xtrustkillx said:
Try to nvflash whole rom not just recovery. Ie pauls v10b. I hope it will work for you.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
I tried both!
When I do the whole rom procedure it gives an error message, but since the cmd window closes right away i can't copy (or i am not aware of a way to retrieve the text....).
Supposedly after NVFlashing the whole ROM I should unplug the cable, install the battery and boot the phone.
At this point the phone doesn't boot, or at least nothing is showing on the screen.
Volume down+ power also doesn't work so I cannot do to CMW.
Do I need to send it to LG?
Thanks for your help anyways!
EDIT:
Actually I managed to keep the CMD window open and this is what I got:
Code:
C:\Users\Dinis\Desktop\desktop\android\Emergency>.\nvflash.exe --bct E1108_Hynix
_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --setbct --odmdata 0xC8000 --co
nfigfile android_fastboot_emmc_full.cfg --create --bl fastboot.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x028841484180d657
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct
- 4080/4080 bytes sent
E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct sent successfully
odm data: 0xc8000
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBR
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: EB1
creating partition: LNX
creating partition: EB2
creating partition: DRM
creating partition: EB3
creating partition: SOS
creating partition: EB4
creating partition: UDA
creating partition: EB5
creating partition: UDB
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBR please wait.. done!
Formatting partition 6 APP please wait.. done!
Formatting partition 7 CAC please wait.. done!
Formatting partition 8 MSC please wait.. done!
Formatting partition 9 EB1 please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 EB2 please wait.. done!
Formatting partition 12 DRM please wait.. done!
Formatting partition 13 EB3 please wait.. done!
Formatting partition 14 SOS please wait.. done!
Formatting partition 15 EB4 please wait.. done!
Formatting partition 16 UDA please wait.. done!
Formatting partition 17 EB5 please wait.. done!
Formatting partition 18 UDB please wait.. done!
done!
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
sending file: system.img
- 851968/358400000 bytes sentdata send failed NvError 0x120002
command failure: create failed (bad data)
Can you enter fastboot now or still stuck in apx? Just in case: Turn off the phone. Remove battery and
hold it removed for few secs. Put it back and press and hold vol - and power button. Keep it pressed and then try smartflash.
Sent from my LG-P990 using xda app-developers app
xtrustkillx said:
Can you enter fastboot now or still stuck in apx? Just in case: Turn off the phone. Remove battery and
hold it removed for few secs. Put it back and press and hold vol - and power button. Keep it pressed and then try smartflash.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Still stuck in APX.
SmartFlash keeps not detecting it!
Thanks For Helping out!
Thats strange. Try to nvflash again without sim and sd card, different cable, different usb port (prefere those which are directly on motherboard on the back of your pc). Just a bunch of ideas.
Sent from my LG-P990 using xda app-developers app
xtrustkillx said:
Thats strange. Try to nvflash again without sim and sd card, different cable, different usb port (prefere those which are directly on motherboard on the back of your pc). Just a bunch of ideas.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Totally strange!! Now I tried again to nvflash with modaco's [ android.modaco.com/topic/335474-25-mar-nvflash-stock-rom-release-v10b-dated-1300166062-15032011/ ]
and it fails in the same way as Rusty's
Code:
(...)
Formatting partition 18 UDB please wait.. done!
done!
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
sending file: system.img
| 2818048/358400000 bytes sentdata send failed NvError 0x120002
command failure: create failed (bad data)
I tried 3 cables, and 3 usbports in my laptop. It worked before, so something must have gone wrong.
Weekend is coming, if I cant fix it Ill have to send to LG and buy a new one while waiting some (hopefully not many) time to get it back!
EDIT:
After some tries the data transferred increased
Code:
(...)
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
sending file: system.img
| 339935232/358400000 bytes sentdata send failed NvError 0x120002
command failure: create failed (bad data)
EDIT 2:
Until I turned off all services, browser and dropbox and what not and:
Code:
(...)
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
sending file: system.img
- 358400000/358400000 bytes sent
system.img sent successfully
sending file: boot.img
- 3420160/3420160 bytes sent
boot.img sent successfully
sending file: recovery.img
- 3958784/3958784 bytes sent
recovery.img sent successfully
But afterwards, it booted LG logo and sound and nothing else. I waited 20 minutes for something to happen until I removed the baterry and turned on again. and LG Logo only....
Then, I tried to battery off and volume down+data cable and i could smartflash. as result it booted once, No LG logo with blue halo but sound played, and again nothing happened for another half hour until i turned off and NVFLashed again and bricked the phone again.
So, now, back to step 1, My phone is stuck in APX and I don't think NVFlash will solve even if it works after 30 tries.
Maybe I have the solution:
Just download the right version of stock gingerbread, check this link:
http://www.todomovillg.es/elforodehomero/index.php?topic=317.0
With this .kdz file, you have to use the KDZ Updater and the LG driver.
Download the latest LG driver here and intall it right after: http://www.lg.com/ca_en/support/mc-support/mobile-phone-support.jsp
UNPLUG your phone before installing this driver.
And the KDZ Updater here: http://forum.xda-developers.com/attachment.php?attachmentid=420545&d=1287222698
When that's done, extract the KDZ Updater folder on your desktop.
1. Open it and install the msxml.msi file.
2. After that, run the KDZ_FW_UPD.exe
3. In that software, you will choose Type: 3GQCT and the PhoneMode: DIAG
4. Choose your recently downloaded .kdz file but DON'T LAUNCH SOFTWARE UPDATE yet.
5. PowerOff your phone and pull out the battery.
6. Hold Volume Down and plug in it to your computer with your USB cable.
7. Your phone must be in S/W UPGRADE Please wait while upgrading...
8. When that's done, just push the Launch Software Update button.
9. WAIT until it reboot and put your battery in.
10. When kdz updater finish, unplug your phone and Enjoy. :good:
Hope that help.
JasonBourne.Qc said:
Maybe I have the solution:
Just download the right version of stock gingerbread, check this link:
http://www.todomovillg.es/elforodehomero/index.php?topic=317.0
With this .kdz file, you have to use the KDZ Updater and the LG driver.
Download the latest LG driver here and intall it right after: http://www.lg.com/ca_en/support/mc-support/mobile-phone-support.jsp
UNPLUG your phone before installing this driver.
And the KDZ Updater here: http://forum.xda-developers.com/attachment.php?attachmentid=420545&d=1287222698
When that's done, extract the KDZ Updater folder on your desktop.
1. Open it and install the msxml.msi file.
2. After that, run the KDZ_FW_UPD.exe
3. In that software, you will choose Type: 3GQCT and the PhoneMode: DIAG
4. Choose your recently downloaded .kdz file but DON'T LAUNCH SOFTWARE UPDATE yet.
5. PowerOff your phone and pull out the battery.
6. Hold Volume Down and plug in it to your computer with your USB cable.
7. Your phone must be in S/W UPGRADE Please wait while upgrading...
8. When that's done, just push the Launch Software Update button.
9. WAIT until it reboot and put your battery in.
10. When kdz updater finish, unplug your phone and Enjoy. :good:
Hope that help.
Click to expand...
Click to collapse
I was trying your solution, but no luck.... I got in KDZ updater : connecting to phone. PHONE WAS NOT FOUND! Finished. any idea? I installed LG drivers, my phone is stuck, no power on, no volume down + power .... looks like its fully bricked, please help me guys
Do not use Smartflash, bro.
Use nvflash in this post, I used to have a half-brick O2X but this post saved me
http://www.modaco.com/topic/335474-25-mar-nvflash-stock-rom-release-v10b-dated-1300166062-15032011/
Good luck! Yuo will need it.
Try to use stefan's ics nvflash version, i think his thread is on page 3/4, then boot it up, if you're planning to use cm10 with the new bootloader use aio tool, or you can download the stock gb/froyo from modaco then nvflash it
Sent from my LG-P990 using Tapatalk 2
Someone fixed the problem yet??
Hey there!
I hope you could help a total beginner getting his phone working again.
The whole thing started a couple of weeks ago when my optimus had several factory resets and was so slow I couldn't use it any longer.
I sat down and searched on the interwebz for a solution and the answer I got was: Put a different ROM on it, then it will be a SOLID phone.
So after some fiddling I got CM7 on it, but I couldn't use the Play store, and I eventually got an error which kept popping up all the time so I was, once again, unable to use the phone.
Then I thought, Hey! This wasn't that hard, maybe I'll try something else!
Well, it was.
I tried getting Jellybam on it, but because I'm a total idiot I did a complete wipe of the phone so I had no OS installed (I took no backup of course)
I've tried and I've tried to fix it but quite frankly I'm at a loss.
This is the error I get:
__________________________________________________________________________________________
The phone will display a S/W download.. screen,
while the command-window will inform you of the progress.
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x02884182415fb057
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
download command failed NvError 0x120002
command failure: bootloader download failed (bad data)
bootloader status: Bct file not found (code: 21) message: flags: 1073844220
An error occured. Read above lines for details.
** Remove the usb-cable from the phone. **
press a key when ready and retry from step 2.
________________________________________________________________________________________
I use this phone daily at work and it's been a real pain in the bum to not have it
Can anyone please help me? I would be very grateful!!!
Thank you for your time!
This could help
So if ur able to access the recovery mode just flash this rom http://forum.xda-developers.com/showthread.php?t=216719 . It is as far the most stable rom for p990 as per my usage and also install proper cm10.1 gapps. dont nv flash the phone see the instructions for wiping !
This might fix you problem try it
Hey! Thanks for the response!
It seems the link to the thread is dead unfortunately
I am not able to reach recovery mode.
http://forum.xda-developers.com/showthread.php?t=2020737
Try this. this phone is unbrickable.
Sent from my LG-P990 using xda premium
wawyed said:
http://forum.xda-developers.com/showthread.php?t=2020737
Try this. this phone is unbrickable.
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
Hey!
It's unbrickable?! That's great!!
I've tried out the toolkit and I'm trying to use function 4 (Partitions), the problem is that it gets stuck sending the bootloader, it looks like this;
==============================================================
Change layout to NEW ICS Partition layout (Point of NO Return)
==============================================================
The phone will display a S/W download.. screen,
while the command-window will inform you of the progress.
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x02884182415fb057
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: star.bct
- 4080/4080 bytes sent
star.bct sent successfully
odm data: 0xc8000
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1027184/1027184 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBR
creating partition: AP2
creating partition: CAC
creating partition: EB1
creating partition: MSC
creating partition: EB2
creating partition: LNX
creating partition: EB3
creating partition: DRM
creating partition: EB4
creating partition: SOS
creating partition: EB5
creating partition: UDA
creating partition: EB6
creating partition: VE
creating partition: EB7
creating partition: UDB
creating partition: EB8
creating partition: APP
creating partition: EB9
creating partition: FOT
creating partition: SWP
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBR please wait.. done!
Formatting partition 6 AP2 please wait.. done!
Formatting partition 7 CAC please wait.. done!
Formatting partition 8 EB1 please wait.. done!
Formatting partition 9 MSC please wait.. done!
Formatting partition 10 EB2 please wait.. done!
Formatting partition 11 LNX please wait.. done!
Formatting partition 12 EB3 please wait.. done!
Formatting partition 13 DRM please wait.. done!
Formatting partition 14 EB4 please wait.. done!
Formatting partition 15 SOS please wait.. done!
Formatting partition 16 EB5 please wait.. done!
Formatting partition 17 UDA please wait.. done!
Formatting partition 18 EB6 please wait.. done!
Formatting partition 19 VE please wait.. done!
Formatting partition 20 EB7 please wait.. done!
Formatting partition 21 UDB please wait.. done!
Formatting partition 22 EB8 please wait.. done!
Formatting partition 23 APP please wait.. done!
Formatting partition 24 EB9 please wait.. done!
Formatting partition 25 FOT please wait.. done!
Formatting partition 26 SWP please wait.. done!
done!
sending file: ics-bootloader.bin
I've waited for 1 hour and the phone doesn't seem to recieve the bootloader
Any tips?
Thanks!
have you tried to change it back to Old Bootloader?
I also encountered this problem ages ago, my solutions was NVFlashing a Stock Froyo ROM from Modaco. I was also a complete idiot back then
Ok, I've fixed it now!
What I did was to try a different USB-port, After I did that the file was sent succesfully,
thank you for your supportl!
castpnt said:
Ok, I've fixed it now!
What I did was to try a different USB-port, After I did that the file was sent succesfully,
thank you for your supportl!
Click to expand...
Click to collapse
THANK YOU!!!! i did the same and it worked!
Good job you guys!
you just Zombified your phone!
Hi Guys,
been trying different USB Ports since yesterday, 3 different PCs with USB 2.0 and three different Cables, LG Original, Sony Xperia Arc S and a SGS3 Cable, but with every Cable I get the NvFlash error with "Bad Data".
Code:
sudo nvflash --bct 0-bct-settings.bct --setbct --odmdata 0xC8000 --configfile progmaq-default-partitions.cfg --create --bl 0-fastboot.img --go
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x0288414143604097
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: 0-bct-settings.bct
- 4080/4080 bytes sent
0-bct-settings.bct sent successfully
odm data: 0xc8000
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: 0-fastboot.img
/ 1024992/1024992 bytes sent
0-fastboot.img sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBR
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: EB1
creating partition: LNX
creating partition: EB2
creating partition: DRM
creating partition: EB3
creating partition: SOS
creating partition: EB4
creating partition: UDA
creating partition: EB5
creating partition: UDB
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBR please wait.. done!
Formatting partition 6 APP please wait.. done!
Formatting partition 7 CAC please wait.. done!
Formatting partition 8 MSC please wait.. done!
Formatting partition 9 EB1 please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 EB2 please wait.. done!
Formatting partition 12 DRM please wait.. done!
Formatting partition 13 EB3 please wait.. done!
Formatting partition 14 SOS please wait.. done!
Formatting partition 15 EB4 please wait.. done!
Formatting partition 16 UDA please wait.. done!
Formatting partition 17 EB5 please wait.. done!
Formatting partition 18 UDB please wait.. done!
done!
sending file: 0-fastboot.img
/ 524288/1024992 bytes sentdata send failed NvError 0x120002
command failure: create failed (bad data)
Been trying it on Ubuntu, on Windows 7, with and without Battery plugged in.
What the hell am I doing wrong, how could I solve this ?
Is there any fix, which resolves this USB issue ?
BTW this is the promaq fix @ ubuntu 12.04 LTS
Greetings
Alpha
You have to keep trying.
I have the same problem, but after the 15th or the 16th times it works.
Try to flash the bootloader only after the partitionating.
So the partitionating done then it will fail after sending the bl.image file. Disconect then reconnect the phone then download the boatloader to the 4th partition.
To make the phone works you need the bootloader on the 4th (EBT) partiton and cwm recovery on the 14th (SOS) partition. Then you can boot into cwm and flash custom rom.
Sent from my LG-P990 using xda app-developers app
nvflash
EDIT: This is stolen from AIO Toolkit
Code:
sudo nvflash --bct star.bct --setbct --odmdata 0xC8000 --configfile ics-stock.cfg --create --bl fastboot.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x0288414143604097
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: star.bct
- 4080/4080 bytes sent
star.bct sent successfully
odm data: 0xc8000
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1027184/1027184 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBR
creating partition: AP2
creating partition: CAC
creating partition: EB1
creating partition: MSC
creating partition: EB2
creating partition: LNX
creating partition: EB3
creating partition: DRM
creating partition: EB4
creating partition: SOS
creating partition: EB5
creating partition: UDA
creating partition: EB6
creating partition: VE
creating partition: EB7
creating partition: UDB
creating partition: EB8
creating partition: APP
creating partition: EB9
creating partition: FOT
creating partition: SWP
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBR please wait.. done!
Formatting partition 6 AP2 please wait.. done!
Formatting partition 7 CAC please wait.. done!
Formatting partition 8 EB1 please wait.. done!
Formatting partition 9 MSC please wait.. done!
Formatting partition 10 EB2 please wait.. done!
Formatting partition 11 LNX please wait.. done!
Formatting partition 12 EB3 please wait.. done!
Formatting partition 13 DRM please wait.. done!
Formatting partition 14 EB4 please wait.. done!
Formatting partition 15 SOS please wait.. done!
Formatting partition 16 EB5 please wait.. done!
Formatting partition 17 UDA please wait.. done!
Formatting partition 18 EB6 please wait.. done!
Formatting partition 19 VE please wait.. done!
Formatting partition 20 EB7 please wait.. done!
Formatting partition 21 UDB please wait.. done!
Formatting partition 22 EB8 please wait.. done!
Formatting partition 23 APP please wait.. done!
Formatting partition 24 EB9 please wait.. done!
Formatting partition 25 FOT please wait.. done!
Formatting partition 26 SWP please wait.. done!
done!
sending file: ics-bootloader.bin
\ 891024/891024 bytes sent
ics-bootloader.bin sent successfully
sending file: ics-recovery.img
\ 7200768/7200768 bytes sent
ics-recovery.img sent successfully
sending file: ics-recovery.img
\ 7200768/7200768 bytes sent
ics-recovery.img sent successfully
just tried this one, seems to work now, could get into recovery.
Has anyone had errors when copying the ROM zips from PC to internal mem ?
Is the internal sd formated as fat32?
Sent from my LG-P990 using xda app-developers app
-.-
Tried to install MIUIv4 from ext.SD - Failed because of a symlink error - ok.
Tried then to copy the ZIP to internal SD - get a freeze after copying about 90 Megabytes.
Is this normal ???
Is that MIUIv4 for new bootloader? Because you are on the new partition layout and using the new bootloader. If that MIUI is for the old bootloader and pt layout, then your partition layout is got damaged. This could explain the symlink error and the freezing copy to the internal sd.
=(
Yes now it is formatted FAT32
O2X totally freezes - regardless of taking cwm or twrp ...
Now trying to push it via ADB - Maybe it doesn't freeze then ...
Got to think more about what to write always have a 5 Minutes Timeout between Posts
Ok - just done adb shell ls -l /sdcard and got 100 MB less than expected
tried to push another file to this directory but had no succes - stops after 4096 KB
now adb shell /sdcard doesnt do anything .. wtf is wrong with this device ?
alph4d0g007 said:
Yes now it is formatted FAT32
O2X totally freezes - regardless of taking cwm or twrp ...
Now trying to push it via ADB - Maybe it doesn't freeze then ...
Got to think more about what to write always have a 5 Minutes Timeout between Posts
Ok - just done adb shell ls -l /sdcard and got 100 MB less than expected
tried to push another file to this directory but had no succes - stops after 4096 KB
now adb shell /sdcard doesnt do anything .. wtf is wrong with this device ?
Click to expand...
Click to collapse
I don't really know. I've never performed nvflash from linux, but I think this not the problem.
Maybe your phone and Ubuntu does not like eachother. Try the copy on windows. If it still failing to copy the zip file, then perform the whole nvflashing on windows.
I hope the phone's internal flash memory don't get damaged.
Edit: I remember when I was copying files to my phone on ubuntu. It hanged up for 2-3 minutes at some point but the copying was finished after all
Some output from dmesg
And here's what dmesg says to this phenomenon:
Code:
[15270.208474] usb 2-1.3: new high-speed USB device number 21 using ehci_hcd
[15270.315821] usb 2-1.3: New USB device found, idVendor=1004, idProduct=61a6
[15270.315826] usb 2-1.3: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[15270.315829] usb 2-1.3: Product: LG-P990
[15270.315832] usb 2-1.3: Manufacturer: LGE
[15270.315834] usb 2-1.3: SerialNumber: 0288414143604097
[15270.331213] scsi13 : usb-storage 2-1.3:1.0
[15271.330649] scsi 13:0:0:0: Direct-Access LGE P990 Storage 0000 PQ: 0 ANSI: 2
[15271.332641] scsi 13:0:0:1: Direct-Access LGE P990 SD Card 0000 PQ: 0 ANSI: 2
[15271.333971] sd 13:0:0:0: Attached scsi generic sg2 type 0
[15271.335823] sd 13:0:0:1: Attached scsi generic sg3 type 0
[15271.381063] sd 13:0:0:1: [sdc] Attached SCSI removable disk
[15271.397036] sd 13:0:0:0: [sdb] Attached SCSI removable disk
[15887.818655] sd 13:0:0:0: [sdb] 9734144 512-byte logical blocks: (4.98 GB/4.64 GiB)
[15887.822636] sd 13:0:0:0: [sdb] No Caching mode page present
[15887.822641] sd 13:0:0:0: [sdb] Assuming drive cache: write through
[15887.830649] sd 13:0:0:0: [sdb] No Caching mode page present
[15887.830655] sd 13:0:0:0: [sdb] Assuming drive cache: write through
[15887.832771] sdb:
[15946.692396] sd 13:0:0:0: Device offlined - not ready after error recovery
[15946.692406] sd 13:0:0:0: [sdb] Unhandled error code
[15946.692408] sd 13:0:0:0: [sdb]
[15946.692410] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
[15946.692412] sd 13:0:0:0: [sdb] CDB:
[15946.692414] Write(10): 2a 00 00 03 9d 78 00 00 c0 00
[15946.692422] end_request: I/O error, dev sdb, sector 236920
[15946.692440] sd 13:0:0:0: rejecting I/O to offline device
[15946.692443] sd 13:0:0:0: killing request
[15946.692462] sd 13:0:0:0: rejecting I/O to offline device
[15946.692465] sd 13:0:0:0: [sdb] killing request
[15946.692468] sd 13:0:0:0: rejecting I/O to offline device
Tried to NvFlash from windows yesterday @ Home, Will try again later that day if I'm home from work, but if this fails too I think this is related to the internal SD on the device (PLEASE correct me ) -.-
Will be back in about 2 hours or so ...
alph4d0g007 said:
And here's what dmesg says to this phenomenon:
Code:
[15270.208474] usb 2-1.3: new high-speed USB device number 21 using ehci_hcd
[15270.315821] usb 2-1.3: New USB device found, idVendor=1004, idProduct=61a6
[15270.315826] usb 2-1.3: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[15270.315829] usb 2-1.3: Product: LG-P990
[15270.315832] usb 2-1.3: Manufacturer: LGE
[15270.315834] usb 2-1.3: SerialNumber: 0288414143604097
[15270.331213] scsi13 : usb-storage 2-1.3:1.0
[15271.330649] scsi 13:0:0:0: Direct-Access LGE P990 Storage 0000 PQ: 0 ANSI: 2
[15271.332641] scsi 13:0:0:1: Direct-Access LGE P990 SD Card 0000 PQ: 0 ANSI: 2
[15271.333971] sd 13:0:0:0: Attached scsi generic sg2 type 0
[15271.335823] sd 13:0:0:1: Attached scsi generic sg3 type 0
[15271.381063] sd 13:0:0:1: [sdc] Attached SCSI removable disk
[15271.397036] sd 13:0:0:0: [sdb] Attached SCSI removable disk
[15887.818655] sd 13:0:0:0: [sdb] 9734144 512-byte logical blocks: (4.98 GB/4.64 GiB)
[15887.822636] sd 13:0:0:0: [sdb] No Caching mode page present
[15887.822641] sd 13:0:0:0: [sdb] Assuming drive cache: write through
[15887.830649] sd 13:0:0:0: [sdb] No Caching mode page present
[15887.830655] sd 13:0:0:0: [sdb] Assuming drive cache: write through
[15887.832771] sdb:
[15946.692396] sd 13:0:0:0: Device offlined - not ready after error recovery
[15946.692406] sd 13:0:0:0: [sdb] Unhandled error code
[15946.692408] sd 13:0:0:0: [sdb]
[15946.692410] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
[15946.692412] sd 13:0:0:0: [sdb] CDB:
[15946.692414] Write(10): 2a 00 00 03 9d 78 00 00 c0 00
[15946.692422] end_request: I/O error, dev sdb, sector 236920
[15946.692440] sd 13:0:0:0: rejecting I/O to offline device
[15946.692443] sd 13:0:0:0: killing request
[15946.692462] sd 13:0:0:0: rejecting I/O to offline device
[15946.692465] sd 13:0:0:0: [sdb] killing request
[15946.692468] sd 13:0:0:0: rejecting I/O to offline device
Tried to NvFlash from windows yesterday @ Home, Will try again later that day if I'm home from work, but if this fails too I think this is related to the internal SD on the device (PLEASE correct me ) -.-
Will be back in about 2 hours or so ...
Click to expand...
Click to collapse
It seems like your phone got a bad sector on the internal sd partition. I hope it is not true, and this happening due the timeout error (what you had during the nvlfash) which I have with nvflash and smartflash.
bitdomo said:
It seems like your phone got a bad sector on the internal sd partition. I hope it is not true, and this happening due the timeout error (what you had during the nvlfash) which I have with nvflash and smartflash.
Click to expand...
Click to collapse
ok how could I get rid of this USB Timeout ?
ps: some news from dmesg:
[18515.672887] sdc: detected capacity change from 15820914688 to 0
Now managed to get MIUI installed (recovery said so) but I'm now starving @ the Bootlogo ...
Just wondering if after half an hour the boot process could be canceled ...
Is there a way to get the system installed on a partitioned ext_sd instead of the internal ?
I ran into this problem before. This caused by the format of the DRM partition, and this is only happens with miui. If you check the dmesg log you can see the problem. So ADB is working even if you stucked at the boot logo. Here is my post about solving this problem. It is for windows, but you seem to be clever, so flashing the drm partition on linux would not cause you problem.
To see the flashing commands look at the content of the flash.bat file.
Edit: Answering to your question. Yes you can install rom to your external sd card, but you have to do a little work. If you are intrested in, then I can help you. I was able to boot up a rom from external sdcard.
bitdomo said:
I ran into this problem before. This caused by the format of the DRM partition, and this is only happens with miui. If you check the dmesg log you can see the problem. So ADB is working even if you stucked at the boot logo. Here is my post about solving this problem. It is for windows, but you seem to be clever, so flashing the drm partition on linux would not cause you problem.
To see the flashing commands look at the content of the flash.bat file.
Edit: Answering to your question. Yes you can install rom to your external sd card, but you have to do a little work. If you are intrested in, then I can help you. I was able to boot up a rom from external sdcard.
Click to expand...
Click to collapse
Just asking myself why I just didn't wait for you to answer :crying:
While you were typing this hint I nvflashed agin and, now I'm unable to install MIUI again
TWRP just says "Error unable to open Zip", CWM sometimes says it has a wrong header, sometimes there are some symlinks that cant be created and so on ...
Now trying to install via twrp ADB Sideload ... maybe I get as far as before ... will post if I have success.
You don't have to stick to MIUI. I had a lot of problem with that. It is RAM hungry. Bunch of google app dont work. After a day or two the phone become slow, even if I enabled 128 mb swap. I recomend to use tonyp's paranoidandroid or cm10.1 rom. You will save yourself from a lot of suffer.
Hello!
I have problem with my device.
First i tried upgrade from v20q to v30a software.
First
I was tried flash by offline kdz And fail.
I was tried via smart flash flashing near 4-6x and fail.
And last try was bricked device.
When i plug device to usb he was know as APX(only).
I was try aio, nv flash and fail i cant repartytion this
Code:
[Back]
E:\2x-v10b-1300166062-nvflash>.\nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR
-0DM_300MHz_final_emmc_x8.bct --setbct --odmdata 0xC8000 --configfile android_fa
stboot_emmc_full.cfg --create --bl fastboot.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x0288500542616057
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct
- 4080/4080 bytes sent
E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct sent successfully
odm data: 0xc8000
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBR
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: EB1
creating partition: LNX
creating partition: EB2
creating partition: DRM
creating partition: EB3
creating partition: SOS
creating partition: EB4
creating partition: UDA
creating partition: EB5
creating partition: UDB
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBR please wait.. done!
Formatting partition 6 APP please wait.. done!
Formatting partition 7 CAC please wait.. done!
Formatting partition 8 MSC please wait.. done!
Formatting partition 9 EB1 please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 EB2 please wait.. done!
Formatting partition 12 DRM please wait.. done!
Formatting partition 13 EB3 please wait.. done!
Formatting partition 14 SOS please wait.. done!
Formatting partition 15 EB4 please wait.. done!
Formatting partition 16 UDA please wait.. done!
Formatting partition 17 EB5 please wait.. done!
Formatting partition 18 UDB please wait.. done!
done!
sending file: fastboot.bin
\ 917504/1024992 bytes sent
When i try via nv for near xxx tries fastboot.bin was sent complety and was closed.
And device is only on s/w upgrade.....
I dont know memory sectors was broken? Mainboard fully broken?
arthurus said:
Hello!
I have problem with my device.
First i tried upgrade from v20q to v30a software.
First
I was tried flash by offline kdz And fail.
I was tried via smart flash flashing near 4-6x and fail.
And last try was bricked device.
When i plug device to usb he was know as APX(only).
I was try aio, nv flash and fail i cant repartytion this
Code:
[Back]
E:\2x-v10b-1300166062-nvflash>.\nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR
-0DM_300MHz_final_emmc_x8.bct --setbct --odmdata 0xC8000 --configfile android_fa
stboot_emmc_full.cfg --create --bl fastboot.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x0288500542616057
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct
- 4080/4080 bytes sent
E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct sent successfully
odm data: 0xc8000
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBR
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: EB1
creating partition: LNX
creating partition: EB2
creating partition: DRM
creating partition: EB3
creating partition: SOS
creating partition: EB4
creating partition: UDA
creating partition: EB5
creating partition: UDB
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBR please wait.. done!
Formatting partition 6 APP please wait.. done!
Formatting partition 7 CAC please wait.. done!
Formatting partition 8 MSC please wait.. done!
Formatting partition 9 EB1 please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 EB2 please wait.. done!
Formatting partition 12 DRM please wait.. done!
Formatting partition 13 EB3 please wait.. done!
Formatting partition 14 SOS please wait.. done!
Formatting partition 15 EB4 please wait.. done!
Formatting partition 16 UDA please wait.. done!
Formatting partition 17 EB5 please wait.. done!
Formatting partition 18 UDB please wait.. done!
done!
sending file: fastboot.bin
\ 917504/1024992 bytes sent
When i try via nv for near xxx tries fastboot.bin was sent complety and was closed.
And device is only on s/w upgrade.....
I dont know memory sectors was broken? Mainboard fully broken?
Click to expand...
Click to collapse
Try other pc, usb cable, usb port or usb3 port. I have been suffering from this issue, but after 8-10 tries i can successfully flash the rom.
bitdomo said:
Try other pc, usb cable, usb port or usb3 port. I have been suffering from this issue, but after 8-10 tries i can successfully flash the rom.
Click to expand...
Click to collapse
Thanks
I was tried on my netbook and succefull
i was flashed cm10 promaq and how i can back it to stock rom?
arthurus said:
Thanks
I was tried on my netbook and succefull
i was flashed cm10 promaq and how i can back it to stock rom?
Click to expand...
Click to collapse
With offline kdz flash