TF701T NvFlash Unbrick Solution(tested) - Asus Transformer TF701

TF701T NvFlash Unbrick Solution(tested)
(continue of the threadhttps://forum.xda-developers.com/showthread.php?t=2655888)
Charge tab before unbricking.
Connect tab to PC.
If your tab not started already in APX mode, then run APX mode by pressing button combination Vol+ and Power.
Insall drivers from "usb_drivers" if needed.
If there is a problem with the installation of drivers, use Google to search- how to install unsigned drivers.
When device installed correctly run "tf701t_flash.bat".
If flash process interrupts with error like ...read\write error..., then probably EMMC memory chip is damaged and need to replace.
If flash process complete, then we ready to next step.
Prepare fat32 formatted microSD card.
Download from ASUS site update package.
https://www.asus.com/us/Tablets/The_New_ASUS_Transformer_PadTF701T/HelpDesk_BIOS/
It _MUST_ be Version V10.14.1.47, SKU(region)- of your choice.
The downloaded file will look like **_epaduser_10_14_1_47_UpdateLauncher.zip
There will be another archive inside that archive.
Extract it, and rename it to t4_sdupdate.zip
Put t4_sdupdate.zip in root of microSD card.
Insert microSD card in tab, then start tab in recovery mode by pressing Vol- and Power key combination.
Follow onscreen instructions to complete recovery process.
After all you tab must be restored to factory state JB Android.
Now you may update firmware version using OTA or sdcard.
NvFlash TF701T Unbrick
http://mega.nz/#!mk8k0Y5S!TQJVfcQudH9HIMnapiGZWccV3VvygnTjDWYLxJte4lo
mirror
http://smartjtagbox.com/owncloud/index.php/s/T8DKqDuhSZzffSp

What is this? A covert ad campaign for Mega? How about hosting the file somewhere that does not force you to download an app, open an account and all that cr***? I'd be really curious to see the code, but not like this.....
Sent from my TF700T using Tapatalk

berndblb said:
What is this? A covert ad campaign for Mega? How about hosting the file somewhere that does not force you to download an app, open an account and all that cr***? I'd be really curious to see the code, but not like this.....
Click to expand...
Click to collapse
Where did you see the ad or need to register, or requirement of install the program for downloading?
Just checking in IE and FF.
I see a big red button- "download", no ads, and no requirements.
Ok, for those who have problems with mega.nz added a mirror for download.

TF701t - Hard Reset Fails ...
Dear Community,
I wanted to hard reset my TF701t to delete my data and give it to another one.
But now it stucks in "deleting data" ... that endures a minute then a dead android is on the screen.
When I want to reboot it, the hard reset comes again and want to delete everything, but the dead android is coming back :/
I can't go in Recovery Mode (Volume-down + Power)
Connection to APX works but, see pic below ...
I don't know what I could try anymore ...
Hope somebody have an idea.
Best greetings,
Symbic
Bild -> url: ibb.co/iFP5JH
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Symbic said:
Dear Community,
I wanted to hard reset my TF701t to delete my data and give it to another one.
But now it stucks in "deleting data" ... that endures a minute then a dead android is on the screen.
When I want to reboot it, the hard reset comes again and want to delete everything, but the dead android is coming back :/
I can't go in Recovery Mode (Volume-down + Power)
Connection to APX works but, see pic below ...
I don't know what I could try anymore ...
Hope somebody have an idea.
Best greetings,
Symbic
Bild -> url: ibb.co/iFP5JH
Click to expand...
Click to collapse
Link to the picture is broken, so we cannot see what result you got...
What's your situation: Bootloader unlocked? Custom recovery? I guess not since you get the dead Android?

link to screenshot ok.
as i can see- problems begin after trying access to EMMC chip.
"Taking backup of EKS"
unfortunately with 90% certainty i can say that the EMMC chip damaged.

mr.bin said:
link to screenshot ok.
as i can see- problems begin after trying access to EMMC chip.
"Taking backup of EKS"
unfortunately with 90% certainty i can say that the EMMC chip damaged.
Click to expand...
Click to collapse
Can I do anything else to test the EMMC chip?

Symbic said:
Can I do anything else to test the EMMC chip?
Click to expand...
Click to collapse
In that state the EMMC chip can be tested with the special equipment like EasyJtag box.

Hello Mr Bin, registered an account just to say thank you...
You have no idea.. was helping a friend to update, but the guy who sold it(tf701) had bought it from different region and turned it to US, so we ended up hard bricking it.
Long story short, we hard bricked it.
Thank you for your hard work in making the fix, and a big THANK you for sharing it...
Perfect fix, its better than before because it got updated to .47 (we couldnt update, no OTA no manual, too old version for custom recoveries)
Again.. thanks :good::good:

Thanks.
But, after clicking to RCK, shows Android with blue procesing line and after few seconds android with open door and red triangle !. After few minutes bootloop....nothing more.
What can i doing again?

Wow! It's back!
Hi.
First of all: Thank you very much! I was sure my tablet was a goner... It is actually back. One tip I'd like to add: I had to try around a bit to get into APX mode. But essentially I just had to connect the tablet to my PC and then push "Volume up" and power at the same time - and ignore that the screen did not light up ...
Again: Thanks a lot!

Mr.Bin,
You have resurrected my TF701T! Thank you SOOOO MUCH! You are an actual genius! Thanks!

Help w installation
I have the same problems although i have not installed any custom OS but after few months of not using it didnt load up and ended in APX mode.
Tried this solution, installed the driver, started the .bat file and ended up here :
Nvflash 3.08.1704 started
Using blob 3.08.1704
chip uid from BR is: 0x600000015c3e10080c000000190301c0
rcm version 0X350001
Skipping BoardID read at miniloader level
System Information:
chip name: unknown
chip id: 0x35 major: 1 minor: 2
chip sku: 0x3
chip uid: 0x000000015c3e10080c000000190301c0
macrovision: disabled
hdcp: enabled
jtag: disabled
sbk burned: true
board id: 0
warranty fuse: 0
dk burned: true
boot device: emmc
operating mode: 6
device config strap: 0
device config fuse: 17
sdram config strap: 0
RCM communication completed
sending file: flash.bct
- 8192/8192 bytes sent
flash.bct sent successfully
BCT sent successfully
odm data: 0x82098000
downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
sending file: bootloader.bin
data send failed NvError 0x120002
command failure/warning: bootloader download failed (bad data)
I would be very thankful for any information you could read from this. Just would like to know if i even have a chance of getting it back on.

So, I was running fine with CROMi-X KitKat, but wanted to upgrade to Marshmallow (to install sw not supported in KitKat), so decided to try KatKiss 6.0. It's been years since I've played with flashing ROMs, but I did a little reading to refresh my memory. Then I rebooted into recovery (ClockworkMod), backed everything up, then wiped everything, formatted /data, and tried flashing the KatKiss zip file. At that point, it just sat there forever at the ASUS logo screen:
I've tried several times to boot back into recovery by holding the Vol+ and Power buttons, but it either doesn't boot, or boots to the above screen. I've connected it to my Mac w/ the Android SDK Platform Tools, but adb doesn't see any device listed. [I've got an old Windows laptop (XP?)] I could use if it will do something the Mac can't.]
Any advice on how I can save this tablet?

This method can be apply to tft300t?

Hi! What a great thread! After lurking on this forum for many years, i've registered to expose my issue with an old tf701 that was given to me by a friend. He say me he installed esexplorer and deleted file to clean space. Next day he rebooted and never been able to boot system. Now tablet is in bootloop ending with blackscreen and backlight on. Im able to open in fastboot and talk with minimal adb and fastboot. RCK update ending with fallen robot, Wipe data/cache ending with fallen robot. APX mode also working and ive run mr.bin's Nvflash unbrick tool with this result:
Nvflash 3.08.1704 started
Using blob 3.08.1704
chip uid from BR is: 0x600000015c3e10060400000001058440
rcm version 0X350001
Skipping BoardID read at miniloader level
System Information:
chip name: unknown
chip id: 0x35 major: 1 minor: 2
chip sku: 0x3
chip uid: 0x000000015c3e10060400000001058440
macrovision: disabled
hdcp: enabled
jtag: disabled
sbk burned: true
board id: 0
warranty fuse: 0
dk burned: true
boot device: emmc
operating mode: 6
device config strap: 0
device config fuse: 17
sdram config strap: 1
RCM communication completed
sending file: flash.bct
- 8192/8192 bytes sent
flash.bct sent successfully
BCT sent successfully
odm data: 0x82098000
downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
sending file: bootloader.bin
| 1463232/1463232 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
Taking backup of EKS
Receiving file: EKS_0400000001058440.bin, expected size: 4194304 bytes
/ 4194304/0 bytes received
file received successfully
Taking backup of PER
Receiving file: PER_0400000001058440.bin, expected size: 8388608 bytes
/ 8388608/0 bytes received
file received successfully
Taking backup of ABT
Receiving file: ABT_0400000001058440.bin, expected size: 4194304 bytes
/ 4194304/0 bytes received
file received successfully
Continuing create using flash.cfg
setting device: 2 3
deleting device partitions
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: DFI
creating partition: BMP
creating partition: ABT
creating partition: GP1
creating partition: SOS
creating partition: DTB
creating partition: LNX
creating partition: APP
creating partition: CAC
creating partition: APD
creating partition: ADF
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: CRA
creating partition: MDA
creating partition: EKS
creating partition: UDA
creating partition: GPT
sending file: bootloader.bin
| 1463232/1463232 bytes sent
bootloader.bin sent successfully
sending file: xusb_sil_rel_fw
- 126464/126464 bytes sent
xusb_sil_rel_fw sent successfully
sending file: ABT_0400000001058440.bin
/ 4194304/4194304 bytes sent
ABT_0400000001058440.bin sent successfully
sending file: recovery.img
\ 7272704/7272704 bytes sent
recovery.img sent successfully
sending file: boot.img
- 6760704/6760704 bytes sent
boot.img sent successfully
sending file: PER_0400000001058440.bin
/ 8388608/8388608 bytes sent
PER_0400000001058440.bin sent successfully
sending file: EKS_0400000001058440.bin
/ 4194304/4194304 bytes sent
EKS_0400000001058440.bin sent successfully
failed executing command 26 NvError 0x120002
command failure/warning: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x40005 (0x14000
5) flags: 0
Click to expand...
Click to collapse
Advise would be great help. I dont know if mmc could be dead, it showing some successful tranfert but keep failing at same place. Thanks!

Hello. These commands for nvflash make a backup and installation of the system.
REED
@cls
@nvflash.exe --blob blob.bin --bl bootloader.bin --read 9 recovery.img --read 11 boot.img --read 12 system.img
@pause
WRITE
@cls
@nvflash.exe --blob blob.bin --bl bootloader.bin --download 9 recovery.img --download 11 boot.img --download 12 system.img
@pause
Thanks mr.bin for a great tool

Important information who uses nvflash!
3 files (ABTxxxxxxxxxxxxxxxx.bin, EKS_xxxxxxxxxxxxxxxx.bin, PER_xxxxxxxxxxxxxxxx.bin, which are created after running nvflash, must be flashed again. Otherwise, it will be impossible to unlock the tablet again and the serial number will be lost. Save in a safe place and then rename the files to EKS, ABT, PER.
To do this, create a second file with the bat extension. In a text editor, type these lines
Code:
nvflash --wait --blob blob.bin --bl bootloader.bin --download 7 ABT --download 21 EKS --download 18 PER --go
If these files are saved on the unlocked tablet, then after their firmware unlocking will be restored.
Also, using nvflash, you can resize partitions, flash a bootloader with file system markup, recovery.

There is no way to load an unlocked bootloader in this process ??

Related

[STICKY][Guide] Creating and Flashing Custom Boot Logo's (Replace Viewsonic Logo)

ADVANCED USERS ONLY - NVFLASH REQUIRED
I would like to reiterate the importance of when I say this is not for the faint of heart. You should be familiar with nvflash, know how to pull the partition table, know how to do a full restore, etc. You are directly and blindly flashing a partition. A small percentage of devices have a different partition table, which this guide would not work for.
1)Follow this guide to setup Nvflash, and enter APX mode: http://wiki.tegratab.com/index.php/Nvflash_FAQ
2)Download boot logo if you don't have one.
3)Open a command line and change directory to the image location on your hard drive.
4)Enter APX mode
5)Run command:
Code:
nvflash --bl bootloader.bin --download 6 (imagename).bmp
-a)Note: 6 is the number of the partition that this image is stored on, nothing else resides on this partition, and nothing else will be damaged
6)Reboot and you should see something other than the Viewsonic Birds
Sample:
Do not save this image preview as template(it is a png instead of bmp).
Download here: http://www.multiupload.com/OWS9JEPVXE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Creating Logo:
Tools:
Gimp (or equivalent)
-free photo editing software
1)Open my sample image in Gimp
2)Find logo that you want
-a)For example you could find a android image
3)Select and delete tegra logo
4)Paste your logo onto the white tegra background (this has correct dimensions)
5)Merge layers
6)Save as .bmp
7)Flash like above method
Bootloader
Correct bootloader.bin is located in the stock Gtablet TnT Nvflash restore(one without 46 in name): http://db.tt/Wm25t7U
Cool Tip thanks for sharing
Hey thanks, that's awesome! By any chance, would you know how to change the GTablet Oval Graphic and the animated X that's after it?
BTW, what do you guys think of a possible animated logo for Roebeets and Rothnics builds. I think they deserve their own animated logos ala Cyanogen Mod. What do you guys think? Hoping someone with some graphics talent sees this. ;P
The animated X is easily changable, I know its just a zip file you replace. (From what I read about my Droid 2.) I would assume it would be the same in this case. I've not done it though.
I also would like to know how to remove the gTablet oval logo that shows up after the Viewsonic birds logo.
Its gone in CM6.1 but TNT is way more stable/functional
KnightCrusader said:
The animated X is easily changable, I know its just a zip file you replace. (From what I read about my Droid 2.) I would assume it would be the same in this case. I've not done it though.
I also would like to know how to remove the gTablet oval logo that shows up after the Viewsonic birds logo.
Click to expand...
Click to collapse
gTablet logo is in the boot.img, and could be replaced with a little effort.
The main animation is the zip file, like you point out, and it is easily replaceable. I have used the Nexus One animation in the ZPad 2.2 ROM. I believe it is under /system/media.
Hmm.....any thoughts?
EDIT: Ignore me. Read that you can't use stock NVIDIA bootloader.bin ::face palm::. Working now
Code:
c:\Program Files (x86)\NVIDIA Corporation\tegra_froyo_20101105>nvflash --bl boot
loader.bin --download 6 tegra.bmp
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x1714118842c051d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 933404/933404 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: tegra.bmp
\ 1441792/1843256 bytes sentdata send failed NvError 0x30012
command failure: partition download failed
h8rift said:
Hmm.....any thoughts?
EDIT: Ignore me. Read that you can't use stock NVIDIA bootloader.bin ::face palm::. Working now
Code:
c:\Program Files (x86)\NVIDIA Corporation\tegra_froyo_20101105>nvflash --bl boot
loader.bin --download 6 tegra.bmp
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x1714118842c051d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 933404/933404 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: tegra.bmp
\ 1441792/1843256 bytes sentdata send failed NvError 0x30012
command failure: partition download failed
Click to expand...
Click to collapse
ummm yea, I got the same thing. I have the version of NVFLASH from week one with the original files that we used to bring it back to stock.
What am I missing?
EDIT: I'M WITH YOU, SORRY FALSE ALARM, guess I grabbed the wrong one (idiot)
Nice find Rothnic
Also, if you find another boot up logo you want (where the malata, nexus, ect. animated screen is), its just a .zip that can be replaced in /system/media Nice little change!
deleted...
So its not working for me. It connects, downaloads and starts the bootloader, then downloads the bmp successfully. I shut the tab off and restart and I see those damn birds....
Any ideas?
I already redownloaded the nvflash files. Still doesn't work.
I formated partition 6 with nvflash and put my picture there and still have the damn birds. Every time it says it's successful! Damn It! LOL!
Noob question: Where do I get bootloader.bin?
-=Sent from my ViewSonic G Tablet (Zpad 2.2) using Tapatalk=-
Bump...
Seriously... I managed to modify the boot.img and change the g-tablet logo, but I can't get this one done! It's very frustrating. Something so simple, yet it won't work!
I used nvflash in Win 7
I used nvflash in Ubuntu
I formated partition 6
I dumped 16MB from partition 6 and tried to view it
NUTIN!
Does anyone have any ideas?
Make sure you are not using the nvidia nvflash but the one in the other folder.
Lil Help
So I was trying to get this to work, realized I could format partition 6 (to try to get the file to copy) and did that, must have removed some stuff that needs to be there cause now I keep getting an error, process acore stopped. The on screen keyboard no longer pops up.
So there must be more than just the .bmp file in partition 6?
Can someone please look at partition 6 and maybe zip or list the files and folders in it. I would rather rebuild partition 6 than rebuild my whole setup.
Aditionally rothnic can you add step 1a to the instructions.
1a) replace the bootloader.bin file with one from the original or a custom rom specifically for the gtab.
I did get the new image installed though
it2steve said:
ummm yea, I got the same thing. I have the version of NVFLASH from week one with the original files that we used to bring it back to stock.
What am I missing?
EDIT: I'M WITH YOU, SORRY FALSE ALARM, guess I grabbed the wrong one (idiot)
Nice find Rothnic
Also, if you find another boot up logo you want (where the malata, nexus, ect. animated screen is), its just a .zip that can be replaced in /system/media Nice little change!
Click to expand...
Click to collapse
i dont get it, how did you guys get this to work? did you have to download the bootloader.bin from else where and not use the one included in the folder?
please help!
thanks!
popezaphod said:
Noob question: Where do I get bootloader.bin?
-=Sent from my ViewSonic G Tablet (Zpad 2.2) using Tapatalk=-
Click to expand...
Click to collapse
I'm with you and lost. I am running TnT Lite 2.2. I've got nvflash up and running, but I guess am misssing the bootloader.bin file as I get an erro at the end.
realsol said:
Make sure you are not using the nvidia nvflash but the one in the other folder.
Click to expand...
Click to collapse
what other folder? could you please explain?
thanks!
liquidcaffeine said:
I'm with you and lost. I am running TnT Lite 2.2. I've got nvflash up and running, but I guess am misssing the bootloader.bin file as I get an erro at the end.
Click to expand...
Click to collapse
yea i get you get the same error im getting. look below:
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x17141188445fd217
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 933404/933404 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: tegra.bmp
/ 1835008/1843256 bytes sentdata send failed NvError 0x30012
command failure: partition download failed
liquidcaffeine said:
I'm with you and lost. I am running TnT Lite 2.2. I've got nvflash up and running, but I guess am misssing the bootloader.bin file as I get an erro at the end.
Click to expand...
Click to collapse
The really weird thing now is after a reboot, half if the new graphic is showing up!
i got past the error when pushing out the tegra.bmp file but now the screen turns black and says "entering nvlash recovery mode / nv3p server"
i followed this...
http://forum.xda-developers.com/showthread.php?t=859834
felizf said:
i got past the error when pushing out the tegra.bmp file but now the screen turns black and says "entering nvlash recovery mode / nv3p server"
i followed this...
http://forum.xda-developers.com/showthread.php?t=859834
Click to expand...
Click to collapse
That means you are done, now restart.

Dell Streak Stuck in APX, can't relash with NVFLASH

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?

[Q] New O2X dead or super bricked ? - help

First of all I would like to welcome the entire XDA community.
I have searched all known forums for the rosolution of my problem with no luck.
I've bought a new P990. I have updated it with the LG update toll to the new official android version 2.3.4. After the update the phone worked ok for about an hour (just enough for me to remove all the stickers) after that it started crashing. I had to take out the battery after it froze and it started. There were still some issues with apps so I turned it off with the power switch.
Now the drama begins...
After I switched it off it went dead. I can't turn it on at all not even in recovery mode. It doesn't charge if connected (although I've checked the battery is good). After connected to the PC by original USB cable it is not seen at all.
The phone is only seen in APX mode so after finding the http://forum.xda-developers.com/showthread.php?t=1007825 I was sure I can bring it back to life. But I was wrong
It went successfuly through the whole nv flashing process a few times but the phone would still not turn on at all.
Now each time i run the flash.bat I get the following error:
C:\o2x>.\nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_
x8.bct --setbct --odmdata 0xC8000 --configfile 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: 4
chip sku: 0xf
chip uid: 0x046c620540a08157
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.. FAILED!
command failure: create failed (bad data)
bootloader status: partition table is required for this command (code: 8) messag
e: nverror:0x2 (0x2) flags: 0
I have run the nvflash on 4 different computers with different OS on different USB cables. Is there anything else I can try? Some way to fix the partition table or something?
Or maybe my O2X is physically damaged - in that case will LG honor my warranty?
I have to go abroad within 2 days so any help would be most appreciated.
Regards,
Bartek
Sounds like hw. Contact LG
Send to the warranty and wait for repair
Hi bpraniuk,
it's possible that this is a hardware failure, but you should try this method:
|Download Smartflash P990:
Here
|Download Drivers:
Here
|Download Good stock ROM:
Here
I think, the good rom is:
Here
>>>>How to do<<<<
1)Install drivers
|Turn device off, remove battery, plug device in while holding volume down - you should see a software update message on screen and the COM port should be filled automatically in the flash application below after installing the drivers if required.
2)Launch SmartFlash P990
3)Unzip the zip rom
4)Select the 'ROM Copy D/L' tab
5)Ensure 'Normal Mode' is selected
6)Ensure 'Erase CAL' is NOT selected
7)Click the browse button next to 'CP Bin:' and select the .FLS file
8)Click the browse button next to 'AP Bin:' and select the .BIN file
9)Choose COM
10) Start!!
When it's done return battery and power on your phone and redo the update
If the Phone crash again go to LG SAV -_-'
Hoping to have you helped
Bye
It certainly looks like hardware failure, try to return it with warranty before you do anything else.
Sent from my LG-P990 using XDA Premium App
may be your NV file was damaged try another sources
The Smartflash won't work because my o2x is not recognized by it. The binaries for nvflash are good I have downloaded it on several locations and checked the MD5.
I guess I'll try to return it to warranty I just hope they will honor it.

Optimus 2X Brick

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

Bricked Optimus2X

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??

Categories

Resources