Hi, i can´t start in Download mode, and the phone don´t boot, just i can when i trick the vol+, home and start buttons and att the same time putting bak the battery so i see in the display "EMERGECY Dload mode, ARM9 Mode"
Traying to reflash with odin but don´t work, on conection setup, can some one help me please???
now is fixed
Can you give more details? How did you manage? And how did you do to be brick?
Downloading mode help
didul said:
Can you give more details? How did you manage? And how did you do to be brick?
Click to expand...
Click to collapse
Just put off the battery them press and MANTAIN IN PRESS THE BUTTONS FOR DOWNLOAD MODE AND ATT THE SAME TIME PUT BACK THE BATTERY AND YOU WILL BE IN DOWNLOADING MODE, GOOD LUCK
I´VE WRONG FLASHED, AND THAT BRICKED THE PHONE, BUT AFTER THIS I FLASHED BACK THE RIGTH FLASH AND THE PHONE IS OK.
HELP
Hi, i have the same problem, it is bricked and whatever i do it wont boot,
can you tell me precisely how you managed to unbrick it?
Grtz
serch826 said:
Just put off the battery them press and MANTAIN IN PRESS THE BUTTONS FOR DOWNLOAD MODE AND ATT THE SAME TIME PUT BACK THE BATTERY AND YOU WILL BE IN DOWNLOADING MODE, GOOD LUCK
I´VE WRONG FLASHED, AND THAT BRICKED THE PHONE, BUT AFTER THIS I FLASHED BACK THE RIGTH FLASH AND THE PHONE IS OK.
Click to expand...
Click to collapse
Thanks for your answer. For now my phone is in service to Vodafone so expect to see the result (not yet passed the period of seven days in which they said they will fix) and can not play with him to try a little Odin.
Help me please....
serch826 said:
Hi, i can´t start in Download mode, and the phone don´t boot, just i can when i trick the vol+, home and start buttons and att the same time putting bak the battery so i see in the display "EMERGECY Dload mode, ARM9 Mode"
Traying to reflash with odin but don´t work, on conection setup, can some one help me please???
Click to expand...
Click to collapse
Hi... I have the same problem. It's began when I flash the Phone with the wrong ROM (Galaxy ACE ROM). And than I flash again with the KC3 ROM (one package ROM). And now, my phone bricked.
I've tried the same methode, but It still can't flashed. It always show the "connection setup" in a long long time without any progress....
Can you help me to explain step by step what you do to unbrick and flash your phone??? And which ROM you used to fixed the Problem??? I've try used the GB ROM and Froyo KC5 ROM, but it's still can't help....
similar problem...
i dont know if the combination of buttons "Vol Up + Home + Power" is for download mode... but in the screen nothings appears... but ODIN recognize this...
and stuck on "setup connection"
jfrubiom said:
similar problem...
i dont know if the combination of buttons "Vol Up + Home + Power" is for download mode... but in the screen nothings appears... but ODIN recognize this...
and stuck on "setup connection"
Click to expand...
Click to collapse
Same problem to me. Phone wont turn on. Any suggestion.
My friend has similar problem, so this isnt good :/
me the same
i have same problem...i dont want to give it to the service again
Anyone help I got the same problem
Download Start...
<0> Create File...
<1> StartThread Detected : 1
<2> StartThread Detected : 0
<3> StartThread Detected : 0
<4> StartThread Detected : 0
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
<1> setup connection...
The combination for Gio Download Mode is VOL DOWN + HOME + POWER!
The combination for Gio Recovery Mode is HOME + POWER.
Good Luck!
Be sure to enter Download Mode and connect your Gio to computer before pressing the "Start" Odin button.
-----------------------------------------------------------
For your "bricked-that-cant-enter-download-mode" Gio, try this:
1. Remove your battery
2. Press and hold VOL DOWN + HOME + POWER
3. While holding those buttons, insert the battery.
bgm92 said:
The combination for Gio Download Mode is VOL DOWN + HOME + POWER!
The combination for Gio Recovery Mode is HOME + POWER.
Good Luck!
Be sure to enter Download Mode and connect your Gio to computer before pressing the "Start" Odin button.
-----------------------------------------------------------
For your "bricked-that-cant-enter-download-mode" Gio, try this:
1. Remove your battery
2. Press and hold VOL DOWN + HOME + POWER
3. While holding those buttons, insert the battery.
Click to expand...
Click to collapse
I did that....
Both vol down + home + power while inserting the battery.
Odin recognize that so then I press start.
after waiting 30 minutes it stay's here:
<0> Create File...
<1> StartThread Detected : 1
<2> StartThread Detected : 0
<3> StartThread Detected : 0
<4> StartThread Detected : 0
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
<1> setup connection... <--
It won't pass setup connection...
I will try to help ya via Team Viewer.
Sent from my GT-S5660 using XDA
bgm92 said:
I will try to help ya via Team Viewer.
Sent from my GT-S5660 using XDA
Click to expand...
Click to collapse
Alright can you pm me your msn or skype or e-mail ?
Would easy I guess
Erm a mini usb jig would work? When my above problem can't be done?
If so where can I get a cheap usb jig ?
Hey, i have similar problem to u. but when i pressed vol up+home+power, odin recognize it and i am tryin to flash it, but "Stuck" at setup connection...
Nothing appears from my phone, plizzz, help, help me
thanks
bricked=corrupted bootloader (phone is completely dead)
is not bricked because a really bricked phone will not boot in download mode it's like dead better is to say "is not booting" and the way to solve a "bricked" phone is to flash a stock rom that surely works you have to try many times because you don not know what rom was previously on the phone
1.get a stock rom on sammobile
2.also get corresponding Odin an pit file from there
3.flash by Odin in download mode
if not working try another rom also check if you have Android SDK an Kies make sure you have these tools- you need adb interface working and samsung drivers installed
when in download mode open Device Manager start/run/devmgmt.msc and check if you have adb interface active if not install Odin and SDK then restart PC and try again in download mode...
(don't do anything until you see something like this is Dev Manager -you see this only when phone is connected to PC yes in download mode)
tips
-pit file tells Odin how to flash files on phone in what order and how to so unpack rom and check if you see at least 3 md5 files : CSC/Modem/PDA not all roms are complete don't use a pit file until you have these 3 files in archive
-if Odin says "done" but phone is not booting try to enter recovery and (should work if you downloaded a complete rom ) ...and wipe data/cache/Dalvik-cache then reboot
-if you are missing a pit, pda, modem or csc file you don't have a rom complete so check for a rom with all these files inside archive then you can flash it and you can check "re-partition" in Odin
-if you see ADB Interface connected in Dev Manager it means your phone is in download mode and is not bricked so can be solved ! do not believe me just try !
-if you do not see this install (again) everything/ use another computer and try again! if you don't get a sign this is bricked and send it in service don't lose time
-I don't have this phone (only a Samsung Omnia but this is WM phone) but I have some experience with these "bricked" phones so this is not a complete howto but give me some feedback let's solve these "bricked" phones and close this thread
yea, i know but my phone bricked cuz i have wrong flashed recovery Rom using Rom Manager. and if i pressed vol up+power+home odin recognize it but always stuck at setup connection as the others shown. if u can show me how to fix this, then u may close this thead!
Hello everybody, I am very new to this and I am trying to install the Eagles blood 4.0.4 ROM. When I get to the step where you use the "one click recovery flasher" I get the "boot loader failed" error below. I get the S/W upgrade on the screen but when I hold the vol down + power i get the box with the lid open and the arrow like its updating instead of the blue LG logo. I have tried it a few times and i get the same thing. What am I doing wrong? Thanks for the help.
================================================== =============
================================================== =============
One Click ClockWorkMod Recovery Flash for T-Mobile G2x
External SD Support by Koushik Dutta
Version 5.0.2.0
================================================== =============
================================================== =============
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x033c208241415197
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
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader failed NvError 0x0
command failure: bootloader download failed
================================================== =============
================================================== =============
*****Once nvflash has completed successfully then hit any key to close.*****
****If any step failed then repeat the process****
Press any key to continue . . .
Maybe you have an LG-P990 and not a LG-P999. Remove the back cover and look bellow the battery and it will tell your model. If it says LG-P999 you're in the right forums, If it says LG-P990 you're in the wrong forums, you have to go to the OX2 forums right here on xda.
it says LG-P999DW
If you're running windows 7 or vista, did you right click the program and run it as admin?
Follow this guide instead, but basically you need to re-flash recovery.
http://forum.xda-developers.com/showthread.php?t=1056847
That was is! I needed to open it as administrator. Thanks for the help! Im sure ill have more questions.
rootme4g said:
That was is! I needed to open it as administrator. Thanks for the help! Im sure ill have more questions.
Click to expand...
Click to collapse
Anytime
Dimension2035 said:
If you're running windows 7 or vista, did you right click the program and run it as admin?
Click to expand...
Click to collapse
Good deal. I forgot about that one in Windows.
rootme4g said:
Hello everybody, I am very new to this and I am trying to install the Eagles blood 4.0.4 ROM. When I get to the step where you use the "one click recovery flasher" I get the "boot loader failed" error below. I get the S/W upgrade on the screen but when I hold the vol down + power i get the box with the lid open and the arrow like its updating instead of the blue LG logo. I have tried it a few times and i get the same thing. What am I doing wrong? Thanks for the help.
================================================== =============
================================================== =============
One Click ClockWorkMod Recovery Flash for T-Mobile G2x
External SD Support by Koushik Dutta
Version 5.0.2.0
================================================== =============
================================================== =============
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x033c208241415197
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
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader failed NvError 0x0
command failure: bootloader download failed
================================================== =============
================================================== =============
*****Once nvflash has completed successfully then hit any key to close.*****
****If any step failed then repeat the process****
Press any key to continue . . .
Click to expand...
Click to collapse
And, just a tip. Only post your issue once and don't hijack threads.
cool thanks
dude i am Waiting about a day since there appeared to letter "sending file: fastboot.bin".
if you know something about it can you help me?
I have the same problem. Help pls.
I have P990. I installed official ICS yesterday and then rooted it by an img file. I have to go back to GB. I can't use smartflash, it gives me error something like partitions 7 error.. I can't use nvflash it gives me same error in this topic, even if I try as administrator. Did I brick the bootloader?
If you have a p990 then you're in the wrong forum and anything you try from here will not work
Having intermittent power issues with LG P999DW - Hardware Issues ? Help
Hi,
I am having intermittent issues with LG P999DW. When I leave the phone for a couple of day off, battery removed, I am able to perform full recovery with NVFlash.
After a while, (last time less than an hour) the phone is dead. APX is working but NVFlash stops at "waiting for bootloader to initialize"
yesterday, I was able to Root it and afterward install One-Click-G2x-recovery-flasher-04-28-12
nothing much to do now ...
Any one have seen the same issue ?
I am trying to obtain a replacement mainboard (SAFY0400802) but it look like it is impossible to buy.
it is not anymore under warranty.
Thanks in advance
Did you download the driver correctly. Theres a step by step how to use nvflash and driver installation or on youtube.
Sent from my Nexus 4 using xda app-developers app
LG P999DW dead, Jelly bean not working
Hi,
I have two p999dw phones, the procedure from multiple threads/post works (e.g. super one click, CWM boot) have been tried.
My phone is working fine, my wife's stay 'dead'
So this help me in 'clearing out' driver issues.
One phone works perfectly, almost got it on Jelly beans (Android 4.1.1) before rebooting in loops. Got it back to stock recovery.
The other one need 3 days before coming up from deads. I am thinking about putting it in oven since in the cold does not resurrect it.
After trying different threads and removing an assert from scripts in cm-9.9.9-JB-p999-2, I think I am at the point of saying that I will be stuck to froyo for a while with Videotron from the multiple threads/posts .... the JB 4.1 seems to work on P990 & P999, not yet the P999DW ...
tried the forum with cm-9.9.9-JB-p999-2.zip, gapps-jb-20120726-signed.zip, cwm-5.0.2.8
Someone knows about a working rom with P999DW ?
Thanks
I will keep hope, LG seems to have released V30 (Android 4 ICS) in Europe ... for the P990 at least...
LG Optimus 2X P999DW, stuck at froyo for now ... Videotron, Canada
Hello guys!
After a while, i digg up this phone from a drawer and I want to upgrade it. So after a lot of time spent to upgrade from 2.2.2 to 2.3.5,
I finally managed with SmartFlashTool to upgrade to V21e, but after successful flash, phone boots up, but battery doesn't charge. I wanted to root the phone, but this also didn't work. Then I downgraded to V21a_00.kdz and successfully rooted the phone with Superuser 2.3.3. But battery still won't charge.
Can somebody please help me to recharge my battery?
I have tried enabling, and disabling USB Debugging option, restarting phone 100 times, install Battery calibration and still nothing.
I have to mention, that on the Android 2.2.2 charging was absolutely fine, so there is no chance of hardware failure.
So, if anybody knows what to try more, or knows about solution, I'll appreciate a lot!
I have looking trough forum, but with no luck, so if I missing something, please point me to...
Thank You all in advance!!!
mkomarac said:
Hello guys!
After a while, i digg up this phone from a drawer and I want to upgrade it. So after a lot of time spent to upgrade from 2.2.2 to 2.3.5,
I finally managed with SmartFlashTool to upgrade to V21e, but after successful flash, phone boots up, but battery doesn't charge. I wanted to root the phone, but this also didn't work. Then I downgraded to V21a_00.kdz and successfully rooted the phone with Superuser 2.3.3. But battery still won't charge.
Can somebody please help me to recharge my battery?
I have tried enabling, and disabling USB Debugging option, restarting phone 100 times, install Battery calibration and still nothing.
I have to mention, that on the Android 2.2.2 charging was absolutely fine, so there is no chance of hardware failure.
So, if anybody knows what to try more, or knows about solution, I'll appreciate a lot!
I have looking trough forum, but with no luck, so if I missing something, please point me to...
Thank You all in advance!!!
Click to expand...
Click to collapse
You Charging via PC using USB port or the Charger?
Does it show it's charging but no current?
Did you try another usb or charger?
How long you leave it in the charger for?
How long was it in the draw and when you left in the draw did you remove the battery?
Do you have clockwork mod recovery installed? If so, you can try resetting the battery stats via the advanced menu in CWM recovery. Also, are you sure the phone isn't charging and its not just a graphic issue with the battery indicator or something? It's possible the battery is in fact charging, but not showing it is. I would downgrade back to 2.2(Froyo) and see if it still charges like normal then maybe try again from there or just use some Froyo based ROMs.
You Charging via PC using USB port or the Charger?
Doesn't matter, tried with two chargers, and two cables, same cable and same charger tested on another mobile, and works perfectly
Does it show it's charging but no current?
Yes, small icon, in top right corner is showing, that charger is connected, but small red bar is not moving towards green
Battery widget is at 0%
but I can have phone power on, it just has to be connected to the cable
Did you try another usb or charger?
Yes, same thing
How long you leave it in the charger for?
5 hrs now, but no change.
How long was it in the draw and when you left in the draw did you remove the battery?
I took it on Sunday night, recharged battery, and use it all week long, until today, when I updated baseband and rom (.fls and .bin)
ima.monstaaa said:
Do you have clockwork mod recovery installed? If so, you can try resetting the battery stats via the advanced menu in CWM recovery. Also, are you sure the phone isn't charging and its not just a graphic issue with the battery indicator or something? It's possible the battery is in fact charging, but not showing it is. I would downgrade back to 2.2(Froyo) and see if it still charges like normal then maybe try again from there or just use some Froyo based ROMs.
Click to expand...
Click to collapse
Yes, I have tried resetting batt status via the advanced menu in CWM recovery, but didn't resolve my problem.
Yea, I'm gonna try to downgrade to Froyo to see does it work there. I am worried about fls file, probably using wrong one?
So right now, this is data from the phone:
Model number, LG-P920
Android version: 2.3.5
Baseband version: L6260_MODEM_SIC_01.1042.00
Kernel version: 2.6.35.7+
Build number: GRJ90
Software version: LGP920-V21a-NOV_15-2011
If froyo does the same thing i think you may need to replace your battery
defcomg said:
If froyo does the same thing i think you may need to replace your battery
Click to expand...
Click to collapse
It seems to me too, that I need a new battery.
thanks for your time to read this post!
I'll report if the new battery solved problem. Hope it's not charging chip on the motherboard :crying:
mkomarac said:
It seems to me too, that I need a new battery.
thanks for your time to read this post!
I'll report if the new battery solved problem. Hope it's not charging chip on the motherboard :crying:
Click to expand...
Click to collapse
It might have been damaged due to no charging after a long time and you left it in the phone.
http://batteryuniversity.com/learn/article/how_to_store_batteries
I seem to remember when the first P920's came out that some people had early developer models that refused to charge after being upgraded. Not sure if it was ever resolved, it might be worth checking posts from 12 months back when this issue was discussed.
Pete
Sent from my LG-P920 using xda premium
take off your battery from O3D and charge it by using black and red cables from a usb cable or another phone charger (look for a guide in youtube you dont wanna fry anything) and make sure its 5volt you are using.. after about 1 hour put it back in your o3d ( without thoses cables and tell us if it works now...)
mad_sunday said:
I seem to remember when the first P920's came out that some people had early developer models that refused to charge after being upgraded. Not sure if it was ever resolved, it might be worth checking posts from 12 months back when this issue was discussed.
Pete
Sent from my LG-P920 using xda premium
Click to expand...
Click to collapse
Uh, Yes, this is early developer model
I'll try to find old posts about charging O3D... if You find it please post link!
tnx
I have found some old threads talking about developer models, but I haven't found a working solution.
So, I remember, that when I had operational 2.2.2 i have rooted phone, and installed CWM, and I have backup from this stage.
So, can somebody point me to the right direction, how to try to get back to this stage?
I can flash successfully with Smart Flash Tool, .fls and .bin file, and .kdz file alone. So, I understand, if I want to use Froyo (V10 x) ROM I have to have v10 x baseband.
So, what would be the best procedure, to recover my CWM backup of working 2.2.2 and have my O3D charging, and operational again?
xbsall said:
take off your battery from O3D and charge it by using black and red cables from a usb cable or another phone charger (look for a guide in youtube you dont wanna fry anything) and make sure its 5volt you are using.. after about 1 hour put it back in your o3d ( without thoses cables and tell us if it works now...)
Click to expand...
Click to collapse
unfortunately, not
it's interesting that when USB cable is connected to charger, phone is Up and running, but remains cold, and when it's connected to USB port of computer, O3D get warm, I took battery off, and tested it with multimer, and it shows 4,17V. So, 1s battery is fully charged at 4,20V. This means, that battery getting current, and small icon in the top right corner recognize that micro USB is connected or not, but battery status does not change, and battery widget says that is 0% battery capacity. As soon I pull out micro USB cable, the phone warns about low battery voltage, and turns off.
I have tried resetting battery trough CWM, but still nothing.
As I said, I have CWM backup of working 2.2.2, but don't know which is exactly procedure to update bootloader + rom.
Should I flash O3D with SFT, and some Froyo package, for example V10I.bin + V10.fls, root the phone, install CWM, and then restore it with backup I have from working 2.2.2???
Please help me, to get back my phone running. It's early development piece, and I would like to use it... I honestly swear that I'll never it update again
mkomarac said:
unfortunately, not
it's interesting that when USB cable is connected to charger, phone is Up and running, but remains cold, and when it's connected to USB port of computer, O3D get warm, I took battery off, and tested it with multimer, and it shows 4,17V. So, 1s battery is fully charged at 4,20V. This means, that battery getting current, and small icon in the top right corner recognize that micro USB is connected or not, but battery status does not change, and battery widget says that is 0% battery capacity. As soon I pull out micro USB cable, the phone warns about low battery voltage, and turns off.
I have tried resetting battery trough CWM, but still nothing.
As I said, I have CWM backup of working 2.2.2, but don't know which is exactly procedure to update bootloader + rom.
Should I flash O3D with SFT, and some Froyo package, for example V10I.bin + V10.fls, root the phone, install CWM, and then restore it with backup I have from working 2.2.2???
Please help me, to get back my phone running. It's early development piece, and I would like to use it... I honestly swear that I'll never it update again
Click to expand...
Click to collapse
Flash samnos partition test bin with lg flashtool.
it has froyo rom for su760 and it works with p920 v21e baseband (tested myself) on p920.
And see if it works.
If battery works with that then upgrade with my bootv21e.bin and see if its fixed.
Bootv21e has all necessary partitions injected including cwm revovery.
If you dont wanna try froyo and only want cwm recovery just flash my bootv21e and it will take you directly to cwm on first boot...
Sent from my LG-P920 using xda app-developers app
xbsall said:
Flash samnos partition test bin with lg flashtool.
it has froyo rom for su760 and it works with p920 v21e baseband (tested myself) on p920.
And see if it works.
If battery works with that then upgrade with my bootv21e.bin and see if its fixed.
Bootv21e has all necessary partitions injected including cwm revovery.
If you dont wanna try froyo and only want cwm recovery just flash my bootv21e and it will take you directly to cwm on first boot...
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
I can confirm, that now it's officially bricked.
I am trying now resurrection guide, but when I connect USB to PC, with Vol+UP pressed, windows recognize that new device is plugged, but second after indicates that device is removed. No OMAP4430 is recognized. I have tried On win8 32, WinXP 32, and Win7 64.
Win7 64 have device OMAP4430 without driver, but there is no WIN64 driver for OMAP4430.
Win8 32 have reocognized device, with driver, but at Connecting O3D without battery, also indicates that device is plugged in, and second after, unplugged. NO OMAP4430 device detected.
And WinXP 32, doesn't recognize OMAP 4430 device at all.
What to do next???
mkomarac said:
What to do next???
Click to expand...
Click to collapse
Read the guide carefully.
xbsall said:
Read the guide carefully.
Click to expand...
Click to collapse
I'm reading the guide all over again, and nothing has changed.
here is summary:
Set of drivers installed:
LGUnitedModemDriver_WHQL_ML_Ver_4.9.7_All_Win7_LGEAll.zip
LGFlashTool
"File"
OMAPFlashInstaller-4.10(2).zip
Scripts
I am working on WinXP right now, and when I connect O3D without battery inserted, OMAP4430 USB Device is recognized by windows, for 1 sec, and then disconnected. At this point, when Windows ask me about drivers, I point drivers to instalation folder of these drivers: http://csmg.lgmobile.com:9002/swdata/WEBSW/LGP920/AVIVML/20110623_05/OMAPFlashInstaller-4.10(2).zip
installed at C:\Program Files \Texas Instruments\OMAPFlash\usb_drv_windows\ In device manager, new device is installed correctly, and it's ready for use. (says windows in balloon tip on the new hardware icon in task bar)
Pull out USB Cable from O3d, and then start "start_fastboot.bat" procedure, choose option 2, and script says:
Optimus 3D selected...
waiting for OMAP44xx device...
Pull battery out, hold Vol+ and insert USB cable into O3D
Windows recognize OMAP4430 USB device for one second, and then sounds like device is removed/unplugged. Script stays at waiting for OMAP444xx device... and never continues...
In time, that windows recognize device connected, and before sounds like usb device disconnected, I set battery into O3D, but still nothing.
Script stays at waiting for OMAP44xx device...
In Device Manager LGE Mobile USB Serial Port is set to: COM41
In LGFlashTool is loaded with LGP920_110622.dll file, and BOOTV21E_AP.bin file, and USB option selected
In LGFlashTool port is set to port1, bot not set to flash, so No yellow sign with READY
Windows Enabler is NOT loaded.
So I can't continue, because script stays at Waiting for OMAP44xx device...
What to do next?
I am trying the same procedure all over again, on different PC's and Operating systems, but always the same result.
In the meanwhile, while I'm waiting the right solution about my problem, I'am gonna to re-install WinXP 32bit just to be sure there are not leftovers of drivers, and install drivers from scratch.
Here are Youtube videos:
driver installation:
Trying to flash bootloader:
Use the omap drivers included eith omapboot
Sent from my LG-P920 4.0.4 ICS using xda app-developers app
xbsall said:
Use the omap drivers included eith omapboot
Sent from my LG-P920 4.0.4 ICS using xda app-developers app
Click to expand...
Click to collapse
These drivers doesn't work for my WINXP. Windows recognize new hardware, I gave for OMAP Device drivers from package, put each time I plug USB into phone, WINXP has found a new driver, and asks me for drivers.. So procedure never begins..
On Win7 64bit I have some more luck. Windows has Found a New OMAP4430 device,
I have point them to drivers come with WKPARKS package,
I started the procedure, and procedure begins...
unfortunately the procedure got error...
here are the progress
----------------------------------------
OMAP4boot for P920/SU540/SU760/SU870
----------------------------------------
by wkpark at gmail dot com
1. Prada 3.0 (SU540/KU5400)
2. Optimus 3D (SU760/P920)
3. Optimus 3D Cube (SU870)
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: 0x2
Checksum Subblock: 0x15
CHIP: 4430
IDEN: 12bd240a5cbb4df74165e28847c766b87268a144
MPKH: 6d473e6a0470e01a52601081128b053b74490ee0000000000000000000000000
CRC0: 31b46fa0
CRC1: 611e8642
sending 2ndstage to target... f0030002
usb_write 4
usb_write 4
wait 5-seconds...
[*] msg size = 4
usb_write 21504
[*] data size = 21504
usb_close
Reopen usb...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
waiting for 2ndstage response...
usb_read 4
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
usb_read got: 0, expected: 4, errno: 121
And this never ends.
In the moment, I unplug cable from O3D, procedure finishes, with:
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
------------------------------
Please remove USB cable
and wait until LG Logo on
then reconnent USB cable again
------------------------------
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
What ever I do, I always get the same error 121 and procedure never finishes and Phone never enters into download mode.
Hi,
Have a TF300 that was still on ICS. Unlocked bootloader, Shut down to enter fastboot mode and nothing is happening.
Screen is blank, Power Light comes on if connected to charger,but can't connect to computer.
Have reset through pinhole in side of case.
Have turned it off with the internal switch doesn't respond at all.
Has anyone else had this happen?
Any suggestions accepted, greatfull.
Okay have manged to get it to boot using the keyboard/dock.
Have copied the 1st five files for NVFlash access just having drama getting it into APX mode.
Bill
Maniac_au said:
Hi,
Have a TF300 that was still on ICS. Unlocked bootloader, Shut down to enter fastboot mode and nothing is happening.
Screen is blank, Power Light comes on if connected to charger,but can't connect to computer.
Have reset through pinhole in side of case.
Have turned it off with the internal switch doesn't respond at all.
Has anyone else had this happen?
Any suggestions accepted, greatfull.
Okay have manged to get it to boot using the keyboard/dock.
Have copied the 1st five files for NVFlash access just having drama getting it into APX mode.
Bill
Click to expand...
Click to collapse
Check my signature for a link that includes much information about accessing apx.
I hope this helps.
Thanks tobdaryl
Ok have managed to get into APX Mode, However insted of showing up as NVidia APX mode device it shows up as Asus Transformer Prime APX Interface.
When I type "wheelie --blob blob.bin" it responds with error "Failed to open blob file blob.bin"
Is it the device driver that is the problem? After doing even more reading I don't believe it's that cause checking
the naked drivers inf file it matches with the PID & VID.
However had to pinch my wifes Sammy to remove their drivers as mine got wet a few weeks ago.but the device tree shows up as SAMSUNG Android Phone with the Asus Transformer Prime APX Interface under the tree.
Is blob.bin on the tablet? It boots with the correct message AndroidRoot 9.4.3.30r01 in top left corner.
Bill
Maniac_au said:
Thanks tobdaryl
Ok have managed to get into APX Mode, However insted of showing up as NVidia APX mode device it shows up as Asus Transformer Prime APX Interface.
When I type "wheelie --blob blob.bin" it responds with error "Failed to open blob file blob.bin"
Is it the device driver that is the problem? After doing even more reading I don't believe it's that cause checking
the naked drivers inf file it matches with the PID & VID.
However had to pinch my wifes Sammy to remove their drivers as mine got wet a few weeks ago.but the device tree shows up as SAMSUNG Android Phone with the Asus Transformer Prime APX Interface under the tree.
Is blob.bin on the tablet? It boots with the correct message AndroidRoot 9.4.3.30r01 in top left corner.
Bill
Click to expand...
Click to collapse
The way the driver shows is not an issue. Many have reported that and used it with success. That is the price we pay for universal drivers.
wheelie --blob blob.bin
is in the list of files you should have created. Find them and place in your directory with wheelie.
NVFlash Files you should have created ( 8 total )
blob.bin
blob.txt
bootloader.ebt
create.bct
recovery.bct
bricksafe.img
factory-config.img
unlock-token.img
I guess I can assume they are in the folder with fastboot?
Looks like I spoke to fast.
Once your blobs have been generated you will need to retrieve them from the “internal” SD card from the AndroidRoot directory (e.g. /sdcard/AndroidRoot). You can do this either through MTP mode or by pulling them using adb.
tobdaryl said:
The way the driver shows is not an issue. Many have reported that and used it with success. That is the price we pay for universal drivers.
wheelie --blob blob.bin
is in the list of files you should have created. Find them and place in your directory with wheelie.
NVFlash Files you should have created ( 8 total )
blob.bin
blob.txt
bootloader.ebt
create.bct
recovery.bct
bricksafe.img
factory-config.img
unlock-token.img
I guess I can assume they are in the folder with fastboot?
Looks like I spoke to fast.
Once your blobs have been generated you will need to retrieve them from the “internal” SD card from the AndroidRoot directory (e.g. /sdcard/AndroidRoot). You can do this either through MTP mode or by pulling them using adb.
Click to expand...
Click to collapse
Okay thanks for your help got it to work after a few goes.
This is a FrankenTablet that I fitted a Screen & Digitizer from my other JB locked unit.
Its been sitting in a box turned completely off waiting for this.
Bill
Maniac_au said:
Okay thanks for your help got it to work after a few goes.
This is a FrankenTablet that I fitted a Screen & Digitizer from my other JB locked unit.
Its been sitting in a box turned completely off waiting for this.
Bill
Click to expand...
Click to collapse
Great! Welcome back. Sounds like you've had your share of problems.