Hi guys,
in moment of insanity I bricked my Tab using Odin. Now it's stuck in APX mode and I need help using nvflash. This is what I get:
D:\nvflash>nvflash --bl bootloader.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 4
chip sku: 0x4
chip uid: 0x0384018441400517
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: bootloader.bin
\ 1941020/1941020 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader failed NvError 0x0
command failure: bootloader download failed
Please note that in system information for chip name stands "unknown" instead "t20". I tried to drain battery, I even opened it and disconnected battery, with no result.
Thx for assistance
I have a Dell Streak 7 that I can trying to reflash with NVFlash and I am getting the following error when I try to reflash:
c:\nvflash>.\nvflash.exe --bct flash.bct --setbct --bl bootloader.bin --configfi
le flash.cfg --rawdevicewrite 0 1536 p2.img --rawdevicewrite 1536 256 p3.img --r
awdevicewrite 1792 1024 p4.img --rawdevicewrite 2816 256 p5.img --rawdevicewrite
3072 1024 p6.img --rawdevicewrite 4096 256 p7.img --rawdevicewrite 9216 8192 p8
.img --rawdevicewrite 17408 8192 p9.img --rawdevicewrite 25600 8192 p10.img --ra
wdevicewrite 33792 172032 p11.img --rawdevicewrite 205824 57344 p12.img --rawdev
icewrite 263168 8192 p13.img --rawdevicewrite 271360 286720 p14.img
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x028040404040e657
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928945/928945 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 31 NvError 0x120002
command failure: writedeviceraw failed (bad data)
I was thinking that maybe if I reformatted the partition tables I would have better success with copying the img files over, but when I attempt to format I get the following:
c:\nvflash>nvflash --format_all --bl bootloader.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x028040404040e657
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
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
Anyone have any suggestions for me?
Thanks,
Mark
Hi, I've been trying to get a problem resolved.
Problem: Device (Dell Streak 7) is stuck in boot loop. Attempts to flash to any partition via fastboot or nvflash complete with no error, however the original data is still intact. New data doesn't get written. It was running stock 2.2.2 fine. The battery died and when I turned it back on, this is what had happened.
I have tried .\nvflash --format_all --bl bootloader.bin --go and the command successfully completes with no errors. However, when I do .\nvflash --read <whatever partition> partition.bin --bl bootloader.bin I get a file that's the same size as the last .img file I successfully flashed to that particular partition. I tried to write a smaller .img file to that same partition, and when I read it back, it's still the original size, not the smaller size image I just tried to flash. This indicates that the writes are not actually happening. This happens to any partition I try to write to.
When I try to format a single partition-> .\nvflash --format_partition 9 --bl bootloader.bin
.....
Formatting partition 9 please wait.. done!
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x40005 (0x140005) flags: 0
困惑：
However if I try to format the recovery partition with fastboot -> fastboot erase recovery -w it succeeds. But when it reboots, I can still get into the stock recovery?
：疯狂：
I tried to flash a custom rom with nvflash and this is what I get:
<create partitions successful>
Formatting partition 2 BCT please wait... FAILED!
command failure: create failed (bad data)
bootloader status: partition table is required for this command (code: 8) message: nverror:0x2 (0x2) flags: 0
It should be noted that I had previously flashed this custom rom with no issues, before going back to the stock rom.
All this points to all the partitions being write protected, since all attempts to modify data on any partition fails even though the software being used claim success.
Is there a way to remove any write protection with either nvflash or fastboot? adb is not available since device is stuck in bootloop, and I can't even execute adb logcat
I've seen many people with similar problems with Tegra 2 devices during my many hours spent searching the net. Any insight would be greatly appreciated.
wzsad said:
Hi, I've been trying to get a problem resolved.
Problem: Device (Dell Streak 7) is stuck in boot loop. Attempts to flash to any partition via fastboot or nvflash complete with no error, however the original data is still intact. New data doesn't get written. It was running stock 2.2.2 fine. The battery died and when I turned it back on, this is what had happened.
I have tried .\nvflash --format_all --bl bootloader.bin --go and the command successfully completes with no errors. However, when I do .\nvflash --read <whatever partition> partition.bin --bl bootloader.bin I get a file that's the same size as the last .img file I successfully flashed to that particular partition. I tried to write a smaller .img file to that same partition, and when I read it back, it's still the original size, not the smaller size image I just tried to flash. This indicates that the writes are not actually happening. This happens to any partition I try to write to.
When I try to format a single partition-> .\nvflash --format_partition 9 --bl bootloader.bin
.....
Formatting partition 9 please wait.. done!
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x40005 (0x140005) flags: 0
困惑：
However if I try to format the recovery partition with fastboot -> fastboot erase recovery -w it succeeds. But when it reboots, I can still get into the stock recovery?
：疯狂：
I tried to flash a custom rom with nvflash and this is what I get:
<create partitions successful>
Formatting partition 2 BCT please wait... FAILED!
command failure: create failed (bad data)
bootloader status: partition table is required for this command (code: 8) message: nverror:0x2 (0x2) flags: 0
It should be noted that I had previously flashed this custom rom with no issues, before going back to the stock rom.
All this points to all the partitions being write protected, since all attempts to modify data on any partition fails even though the software being used claim success.
Is there a way to remove any write protection with either nvflash or fastboot? adb is not available since device is stuck in bootloop, and I can't even execute adb logcat
I've seen many people with similar problems with Tegra 2 devices during my many hours spent searching the net. Any insight would be greatly appreciated.
Click to expand...
Click to collapse
Yes thanks its a big problem me too I can resolve this problem....DO ypu find any solution?
so i had the infinit cyanogen7 animation boot loop and im trying to find a way to fix it but i cant find any for me LG-p990 (Lg optimus 2x) i tried Nvflash but i get this error>
===============================================================
===============================================================
One Click Stock Recovery Flash for T-Mobile G2x
===============================================================
===============================================================
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 4
chip sku: 0xf
chip uid: 0x043c708042412317
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 downloaded successfully
failed executing command 14 NvError 0x120000
command failure: partition 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 . . .
i cant find anyway to fix it i dont know wat to do now i really need someones help please
is your phone an LG O2X or is it a T-mo G2X ?
Yeah, you just mentioned 2 phones in your post. the O2X P990, and the G2X P999. So we're guessing the problem is knowing which tools and ROMs work for your exact model.
Btw, there's a separate G2X forum if that's the phone that you have. This is exclusive for the P990.
Friends..i am beginner+ to this forum.. i got stuck in a bad problem(bootloop) below. Please help me to save my O2x
Thanks in advance and appreciate all your help ..!!
Reason for bootloop:
===============
Flashed temasek CM7 and it worked perfectly.
Then flashed Horsepower 2X extreme kernel and it came up and worked.
Then when i re-started the phone, it enters into BOOTLOOP and stuck there forever.
Logs here:
--------------
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Tried below solutions:
===============
Read forums and tried Nvflash. Even it didn't work out. Exception are sometimes with bad data and other with Bootloader not specified.
Please suggest me some solutions to overcome this pblm...
See log below:
----------------------
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]?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: 0x038820c440c09417
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
| 983040/1024992 bytes sentdata send failed NvError 0x120000
command failure: bootloader download failed
-------------------------------
Program will now exit
Press any key to continue . . .
Just reflash the Temasek ROM .zip and you'll probably be fine.
Re-flashestemask cm7..not working
wiped cache/data/david cache... and then flashed temask cm7 ...it again bootloops.... e:/can;t mount cache..
I tried with nandroid backup that i had taken during CM10..i didn't work out and bootloops...!!
Is there any possible solution to this ?
All my tries always ended up in -->
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Power it off, remove battery, hold vol- and insert USB cable.
If it shows something about SW Update on the screen, then just smartflash a stock ROM, then start again. Saves dicking around.
sw upgrade boot doesn't work either
Thanks for ur reply Rusty...!!
I tried SW upgrade boot also, it didn't work .. flashes lg logo and turns off... if i keep on holding vol - button, it blinks again and again.
I think i bricked my phone.. Internal sd-card /emmc,/cache)is not recognized/mounted.
It's pretty much impossible to brick it. NVFlash will fix it.
When you tried, was the phone plugged directly to the motherboard or through a hub/front ports? Direct is best.
Yes, i tried through serial port and tried with other port also, didn't enter S/W upgrade screen.. (Mine is Dell XP15 - win7 )
Have installed latest LG drivers and nvflash drivers are latest and showing up in device manager also..!!
Through nvflash it stucked - bad data or hangs for hours..!! (have tried changing data cable too)
Logs:
-------
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
\ 655360/1024992 bytes sentdata send failed NvError 0x120000
command failure: bootloader download failed
Is there any way to overcome this bad data error in nvflash ?
Any small clue to restore my O2X will be very helpful ..!!
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
data send failed NvError 0x120002
command failure: bootloader download failed (bad data)
vsnstarguy said:
Is there any way to overcome this bad data error in nvflash ?
Click to expand...
Click to collapse
Before giving up, borrow some time on a desktop computer, connect directly to a port on the motherboard, try again. Use a USB2 port.
Re- Use a USB2 port.
When i connect to usb3 ports, it detects APX device and 'NVIDIA USB Boot-recovery driver for Mobile devices' appears in device manager.:angel:
But when i try usb 2 port, it prompts as unkown device(usb device not recognized) -[ Lg drivers work with usb 3 ports] and not able to proceed further.
I have always used usb3 ports for rooting O2x and all- it went fine, should i still need to debug on usb2 unknown device issue ?
Nvflash worked..enters sw upgrade screen
Friends, nvflash works successfully and files sent successfully and phone enters S/W upgrade screen.
If i release usb cable, put the battery and power on with vol-down, it again enters into CWM and not S/W upgrade screen.
Need to know what are the next steps to do , also what are the files that i have to put in sdcard ?
addition to this.. adb also working..
Friends,.. now nvflash works and i am to do some basic ADB commands also..!! [Smartflash not working - due to phone not entering s/w upgrade]
C:\Users\Senthilnathan\AppData\Local\Android\android-sdk\platform-tools>adb shell
~ #
~ # ls
ls
boot init sys
cache init.rc system
data proc tmp
datadata res ueventd.goldfish.rc
default.prop root ueventd.rc
dev sbin ueventd.tegra.rc
emmc sd-ext
etc sdcard
Need your help - What are next steps i should do ? What are the files i need to download to make my O2x work? :fingers-crossed:
Well if you can ADB in recovery, I guess you should download a ROM, stick it on your SD card and flash it.
OR
Remove battery, hold vol down and plug in USB cable to get the S/W Update mode, then you can smartflash.
Rusty! said:
Well if you can ADB in recovery, I guess you should download a ROM, stick it on your SD card and flash it.
OR
Remove battery, hold vol down and plug in USB cable to get the S/W Update mode, then you can smartflash.
Click to expand...
Click to collapse
OR
http://forum.xda-developers.com/showthread.php?t=1054492
Smartflash not working.. removed battery, vol down and lug usb cable enters - just blinks again and again..
I tried adb to flash rom- below are the results... ( flashing through cwm again results in boot loop) ..
C:\Users\Senthilnathan\AppData\Local\Android\android-sdk\platform-tools>adb push Miui_v4_2.7.20-O2x-MultiLang.zip /sdcard/Miui_v4_2.7.20-O2x-MultiLang.zip
1947 KB/s (178451090 bytes in 89.495s)
C:\Users\Senthilnathan\AppData\Local\Android\android-sdk\platform-tools>fastboot -w update /sdcard/Miui_v4_2.7.20-O2x-MultiLang.zip
error: failed to load '/sdcard/Miui_v4_2.7.20-O2x-MultiLang.zip'
~#ls -lrth
-rwxrwxrwx 1 root root 170.2M Sep 16 2012 /sdcard/Miui_v4_2.7.20-O2x-MultiLang.zip
Still in same cwm bootloop.. CWM-5.0.2.7.. Please help -
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
MMarkkk said:
OR
http://forum.xda-developers.com/showthread.php?t=1054492
Click to expand...
Click to collapse
When i tried to push part5.img file form link provided,it gets through, but while re-startintg phone - it stucks in lg logo..!!
Logs:
====
G:\NVFlash>nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 14 part5.img
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x038820c440c09417
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 downloaded successfully
sending file: part5.img
/ 1566720/1566720 bytes sent
part5.img sent successfully
Still in cwm bootloop.. Can you please tell what should i have to do avoid this 'E: Can't mount cache/recovery/command' ?
vsnstarguy said:
When i tried to push part5.img file form link provided,it gets through, but while re-startintg phone - it stucks in lg logo..!!
Logs:
====
G:\NVFlash>nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 14 part5.img
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x038820c440c09417
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 downloaded successfully
sending file: part5.img
/ 1566720/1566720 bytes sent
part5.img sent successfully
Still in cwm bootloop.. Can you please tell what should i have to do avoid this 'E: Can't mount cache/recovery/command' ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1893047
Waiting for bootloader to initializer
Hi vsnstarguy,
I have a situation like yours. My device is dead and nothing shows on screen. I've tried that methods, nvflash, smartflash but my device is realy dead and I got the same status like you:
C:\O2x\NVFlash>nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final
_emmc_x8.bct --bl fastboot.bin --download 5 recovery-clockwork-5.0.2.0-p999.img
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 4
chip sku: 0xf
chip uid: 0x037c7008427f85d7
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
Nothing happens after this!!!!
Hekp me!
I've opened a thread about this but nobody could help me yet!
Thing is, most people manage to get passed that point. If you've plugged directly into the motherboards USB ports, have you tried another computer?
@cl06 - nvflash and adb works..!!
@cl06 - Dude, is you phone p990 or p999 ? you seem to be trying with p999.
Nvflash p990 correctly, it will work.. (got this from Rusty thread)
or navigate it to your nvflash folder for p990 and try below command--
nvflash --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 14 cwm-int.img
In above nvflash command - after download for p999 it will be 5 for p990 it will be 14.
For some intermittent issues, i changed usb cable and now nvflash works but im still in bootloop for which our friends here will help us
I have LG Optimus 2X P990 which was working normally till last two months.
In last two months it get slower and slower and now wont turn on and wont flash.
When I connect it to PC - PC recognize it and I can start flash process, but it always stuck
at the same step :
Nvflash started
rcm version 0X20001
System information:
chip name : unknown
chip id: 0x20 major:1 minor: 3
chip sku: 0xf
chip uid: 0x0280414640802297
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 strip: 0
sending file: 0-bct-settings.bct
- 4080/4080 bytes sent
0-bct-settings.bct sent successfully
odm data: 0xc8000
downloading bootloader -- load address: 0x10800 entry point: 0x108000
sending file: 0-fastboot.img
/ 1024992/1024992 bytes sent
0-fastboot.img sent successfully
waiting for bootloader to initialize
bootloader download successfully
setting device: 2 3
creating partition : BCT
failed executing command 16 NvError 0x120002
command failure: create failed <bad data>
bootloader status: failed to create partition <code:10> message: nverror:0x5 <0x1000005> flags:0
In this proccess, phone boot up with S/W upgrade... please wait text on it.
I have tried at 3 PC and 1 laptop PC - on Windows XP SP2/SP3 and Windows 7 32-bit
All drivers were installed and I dont know what to do to get phone boot and get to flash it..
Any ideas ?
Thx.