Had my gtab go into reboot loops this morning and tried to just reflash. Ended up with a black screen. OOPS. Brick time. Plugged into my linux box and say that it was in apx mode. Tried to reflash with roebeet's nvflash But nvflash stoped after loading flash.bin. Retrying did not help.
I figured I had nothing to loose and tried ..
LD_LIBRARY_PATH=. ./nvflash --format_all --bl bootloader.bin --configfile flash.cfg --create --go
and the screen flashed showing that it was in apx mode. Rebooted and reran the suggested flash command and restored the system.
As usual, YMMV.
I have installed the apx drivers and put the tab in nvflash mode. I can sync tab with nvflash --sync command. I got recovery.img from this thread. Can anyone confirm the recovery.img is good and post a bootloader.bin please?
I/O bootloader:
http://droidbasement.com/galaxy/sys-backup/bootloader.zip
Hi everyone
2-3 weeks ago i bought my TF from usa amazon and i decided to root it, i followed the guide in here and user brk rootkit v 6.3 for usa 8.6.5.9 firmware after some tries i got it installed and was running it pretty nice.
the problems started like 3-4 days ago, first time it just suddenly restarted, then after that it would power off alone and after a lot of tries pressing power button for like 20 sec and all combinations like power + vol up power + vol down it will power on again....
but now it wont even power on no matter how much i press power button so i thought it was bricked and followed this guide
thing is when i put it on APX mode and execute download bat file it will start but it will close again right when it says "waiting for bootloader to initialize"
i dont know what else to do and im starting to panick i dont even know whats wrong with my TF, if its bricked or not
please any help will be deeply appreciated
thanks
sorry cant post link yet
i see your new here but please post in the correct section.
as for your transformer. do you get any recognition from the computer at all? And are you still in apx mode? if you are in apx then no worries just restart your computor and your transformer and then just follow these again http://forum.xda-developers.com/showthread.php?t=1123429
if not and if it is completely bricked you might be able to send it back to asus. if they cant get it to work they cant say you rooted it so you might be able to get them to fix it as a software problem
sorry for using the wrong sections..
yea i also followed that guide but happens just the same when i execute download bat file
i cant restart my transformer becuz it wont power on how do i restart it
you should just have to hold power for 20~ seconds. have you tried a highspeed usb port? or a different computor?
i have held down power for many times 20 secs but still nothing.... gonna try on another port, i was trying on my case usb port
Run download.bat in a cmd window and it will show you the error
Sent from my MB855 using XDA App
how do i do that? sorry for being so newbish
Make Sure the TF is fully charged. Also make sure the charger is charging. The wall unit should be very warm if it is charging. If it is not, you may not be charging and have a low or dead battery.
windows->run program->cmd
then in the command directory cd to the one with download.bat, then type download.bat
yeah it does get hot when its charging so its not charging issues and this is the CMD error i get
C:\Users\TONY\Desktop\WINDOWS>cd C:\Users\TONY\Desktop\WINDOWS\
C:\Users\TONY\Desktop\WINDOWS>"nvflash.exe" --bct transformer.bct --setbct --con
figfile flash.cfg --create --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682
CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x037c7005405ff0d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 2
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
- 1361037/1361037 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 11 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition (code: 10) message: nverror:0x
3 (0x3) flags: 0
what could it be?
do you have all three of the required files in the nvflash directory?
i believe so ...
i got boot img, recovery img and system img is there anything else requires? or any drivers besides de usbpc
Hello everyone
I desperately need help unbricking my Galaxy Tab 10.1 Wifi using Nvflash or any similar tool. I cannot use Odin since it won't go into download mode. It seems the partitions are messed up so right now I cannot even upload a recovery image on partition 8.
Can anyone post the partition configuration file (cfg) and the boot configuration file (bct) and the bootloader.bin from their previous backup using the nvflash tool? Then I could try
"nvflash .exe" --bct XXXX.bct --setbct --bl bootloader.bin --configfile XXX.cfg --create --go
I wasn't able to find anything for the Galaxy 10.1 on the Internet (but I found plenty of this for the Transformer and Viewsonic tabs). Can anyone help revive my tab?
In the past I has installed several custom ROMs on my A500. Mostly civato's variants. I most recently had CM10-FLEX_V6Supercharged_Rev3.3 installed with the v8 ICS Bootloader.
I then tried to do a dirty install of CM10-FLEX_V6Supercharged_Rev3.4. The thought that this would be ok as it was only a single dot release.
The a500 booted and things appeared to be normal. I did not do a whole lot with the tablet at the time. Later I came back and found the tablet was off. When I tried to reboot, I got stuck at the v8 bootloader screen.
Next I figured I might as well put the v9 bootloader on, wipe everything out, and do a clean install of CM10-FLEX_V6Supercharged_Rev3.4.
Upon first boot, the exact thing happened, except this time the table was stuck on the v9 boot screen.
The is when the journey began. I have tried about everything I have been able to find. I have had times where the only thing that works on my tablet is manual APX mode.
The only thing that somewhat works consistently to bring the table back to life is using Timothy's Tool (not sure why this nvflash is different), and running this command:
nvflash --bct flash.bct --setbct --odmdata 0x100c0105 --configfile flash.cfg --create --bl bootloader.bin --sbk <mykey> --go
Most times this will get me to a stock-like ROM. Sometimes the nvflash fails. At different spots, so I do not know what is going on there. The most frequent error is the below error, right after checksum.img sent successfully:
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x42008 (0x6042008) flags: 0
If the flash is successful, I can boot stock rom.
From there I try a myriad of things to put on a patched custom boot loader. I have used the apxflash tool, and nvflash with several of the .bat files you can find. It looks like I can get v8 and v9 of the ICS boot loader installed and can still boot the stock ROM that gets installed with Timorthy's tool. With either the v8 or v9 bootloader installed I can boot stock rom, custom recovery, or quickboot menu.
From there is where things are bad. I have tried to install several custom ROMs from Recovery (Thor 1.7.3) and they appear to install fine. The aroma installer installs the ROMs. If I try to format a file-system (ie., /system,/data,/cache,/flexrom) those all appear to work fine. Unfortunately after I install any custom ROM (RE-FLEXxx-ShellSHOCK-Rev7.0-CuZ-Edition, CM10-FLEX_V6Supercharged_Rev3.4, CM10-FLEX_V6Supercharged_Rev3.3, cm-10.1-20130606-UNOFFICIAL-a500), the same thing happens. I get stuck at the boot screen where it is trying to boot the primary kernel image. It does not matter if v8 or v9 of the Bootloader is installed. The exact same thing happens.
I have been down every rabbit hole I have been able to find, but I cannot find a solution. Has anyone else run into this issue? Anyone have any suggestions?
Thank You.
gemneye said:
In the past I has installed several custom ROMs on my A500. Mostly civato's variants. I most recently had CM10-FLEX_V6Supercharged_Rev3.3 installed with the v8 ICS Bootloader.
I then tried to do a dirty install of CM10-FLEX_V6Supercharged_Rev3.4. The thought that this would be ok as it was only a single dot release.
The a500 booted and things appeared to be normal. I did not do a whole lot with the tablet at the time. Later I came back and found the tablet was off. When I tried to reboot, I got stuck at the v8 bootloader screen.
Next I figured I might as well put the v9 bootloader on, wipe everything out, and do a clean install of CM10-FLEX_V6Supercharged_Rev3.4.
Upon first boot, the exact thing happened, except this time the table was stuck on the v9 boot screen.
The is when the journey began. I have tried about everything I have been able to find. I have had times where the only thing that works on my tablet is manual APX mode.
The only thing that somewhat works consistently to bring the table back to life is using Timothy's Tool (not sure why this nvflash is different), and running this command:
nvflash --bct flash.bct --setbct --odmdata 0x100c0105 --configfile flash.cfg --create --bl bootloader.bin --sbk <mykey> --go
Most times this will get me to a stock-like ROM. Sometimes the nvflash fails. At different spots, so I do not know what is going on there. The most frequent error is the below error, right after checksum.img sent successfully:
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x42008 (0x6042008) flags: 0
If the flash is successful, I can boot stock rom.
From there I try a myriad of things to put on a patched custom boot loader. I have used the apxflash tool, and nvflash with several of the .bat files you can find. It looks like I can get v8 and v9 of the ICS boot loader installed and can still boot the stock ROM that gets installed with Timorthy's tool. With either the v8 or v9 bootloader installed I can boot stock rom, custom recovery, or quickboot menu.
From there is where things are bad. I have tried to install several custom ROMs from Recovery (Thor 1.7.3) and they appear to install fine. The aroma installer installs the ROMs. If I try to format a file-system (ie., /system,/data,/cache,/flexrom) those all appear to work fine. Unfortunately after I install any custom ROM (RE-FLEXxx-ShellSHOCK-Rev7.0-CuZ-Edition, CM10-FLEX_V6Supercharged_Rev3.4, CM10-FLEX_V6Supercharged_Rev3.3, cm-10.1-20130606-UNOFFICIAL-a500), the same thing happens. I get stuck at the boot screen where it is trying to boot the primary kernel image. It does not matter if v8 or v9 of the Bootloader is installed. The exact same thing happens.
I have been down every rabbit hole I have been able to find, but I cannot find a solution. Has anyone else run into this issue? Anyone have any suggestions?
Thank You.
Click to expand...
Click to collapse
Ok to start off.....
timmy deans euu tool. If u run this and its successful you will be back to stock HC 3.2.1. You will be rooted and you will have cwm recovery mode.
Now, once u r back on HC, you can now begin to think about which rom you want to install. Put it on yr ext sd card. With the troubs you are having try civatos pre-rooted stock ics rom.
Next step is to flash the v8. Use the apxflash method.
Choose to dump yr own bct....
Once you get the PASS...boot direct to recovery mode and complete the full wipes....then flash the rom...done!!!
If you complete each step as it is written here you should be good.
Good luck
dibb
Sent from my GT-I9300 using Tapatalk 4 Beta
dibb_nz said:
Ok to start off.....
timmy deans euu tool. If u run this and its successful you will be back to stock HC 3.2.1. You will be rooted and you will have cwm recovery mode.
Now, once u r back on HC, you can now begin to think about which rom you want to install. Put it on yr ext sd card. With the troubs you are having try civatos pre-rooted stock ics rom.
Next step is to flash the v8. Use the apxflash method.
Choose to dump yr own bct....
Once you get the PASS...boot direct to recovery mode and complete the full wipes....then flash the rom...done!!!
If you complete each step as it is written here you should be good.
Good luck
dibb
Click to expand...
Click to collapse
Yes, I have been down every one of those steps as mentioned in my first post. I can not run timmy deans euu tool (root-3.2.1_v4) as documented, because I can not boot my tablet. What I can do is change to the Image directory on Timmy dean's tool, and manually run --
nvflash --bct flash.bct --setbct --odmdata 0x100c0105 --configfile flash.cfg --create --bl bootloader.bin --sbk <my_key> --go
I have gotten stock booting from v8 and v9 patched boot loaders. It is the next step after that. I do a wipe (factory reset). Do a "real" delete of /data, and go through the Aroma installer (which appears to finish without any problem).
When I boot, it never gets past the bootloader screen. It does not go black or anything. It just shows the booting primary kernel image message and hangs.
Now, I am not even able to run the nvflash command. I am starting to wonder if there is a hardware storage problem. I can't even create the partitons.
After u run timmydeans, can u boot to the OS
Sent from my GT-I9300 using Tapatalk 4 Beta
---------- Post added at 06:12 AM ---------- Previous post was at 06:00 AM ----------
gemneye said:
...
It is the next step after that. I do a wipe (factory reset). Do a "real" delete of /data, and go through the Aroma installer (which appears to finish without any problem).
When I boot, it never gets past the bootloader screen. It does not go black or anything. It just shows the booting primary kernel image message and hangs.
.
Click to expand...
Click to collapse
Tell me which recovery you sre using...cwm 1.7.3 works best. Forget aroma and use that pre rooted stock rom until we get u sorted.
I know u said youve done everything over and over but please run thru those steps EXACTLY as i wrote them
Yes it maybe the chip...can't tell without nvflash output...the only one u posted showed bct error....which apxflash tool fixes
Sent from my GT-I9300 using Tapatalk 4 Beta
About to throw in the towel
dibb_nz said:
After u run timmydeans, can u boot to the OS
---------- Post added at 06:12 AM ---------- Previous post was at 06:00 AM ----------
Click to expand...
Click to collapse
After Timmy's tool, I was able to boot just fine. I got to this point a few times. There was no patched boot loader or no custom recovery. Basically I had a bootable tablet running what looked to be a STOCK ROM.
I could then install v8 or v9 patched ICS loader and custom recovery (CWM THOR 1.7.3). I could boot custom recovery (Vol-down + Power), Quick Menu (Vol-up + Power), or the Stock ROM (Primary Kernel Image). This would work consistently.
Then I would install a custom ROM (tried many of them, even ones that had worked previously) and I could never get the ROM to boot. I would get stuck on the boot loader screen stating Primary Kernel was trying to boot.
Since then I can no longer use Timmy's tool. I am now consistently getting this error:
Formatting partition 2 BCT please wait.. FAILED!
command failure: create failed (bad data)
bootloader status: specified partition is invalid or does not exist (code: 7) message: nverror:0x42008 (0x6042008) flags: 0
Except for getting the tablet to boot a few times after using Timmy's tool, I would venture to guess there is an underlying hardware issue. Once I had it booted to Stock I think it gave me false hope. Now that I am consistently getting storage device type errors using different combinations of nvflash, I am thinking there might be a more serious issue.
I just spent half an hour on a reply, and its not showing. ...grrrrr ... its past my bedtime so I'll get bsck to you in the morning! !!
Sent from my GT-I9300 using Tapatalk 4 Beta
gemneye said:
The only thing that somewhat works consistently to bring the table back to life is using Timothy's Tool (not sure why this nvflash is different), and running this command:
nvflash --bct flash.bct --setbct --odmdata 0x100c0105 --configfile flash.cfg --create --bl bootloader.bin --sbk <mykey> --go
Click to expand...
Click to collapse
This was the only thing that worked to get my a500 out of APX mode! I thought for sure she was a gonner.
dibb_nz said:
Ok to start off.....
timmy deans euu tool. If u run this and its successful you will be back to stock HC 3.2.1. You will be rooted and you will have cwm recovery mode.
Now, once u r back on HC, you can now begin to think about which rom you want to install. Put it on yr ext sd card. With the troubs you are having try civatos pre-rooted stock ics rom.
Next step is to flash the v8. Use the apxflash method.
Choose to dump yr own bct....
Once you get the PASS...boot direct to recovery mode and complete the full wipes....then flash the rom...done!!!
If you complete each step as it is written here you should be good.
Good luck
dibb
Click to expand...
Click to collapse
I have the similar issue to gemneye.
I can use timmy deans euu tool to get to stock hc 3.2.1 and can boot without issues.
I can flash the v8 using apxflash and I install cwm thor 1.7.3.
Still boots up fine after flashing v8/recovery.
No matter what rom I install at this point I am stuck at the screen with "Booting primary kernel image". Even civato's stock rom won't go past this screen.
The only part of your instructions that I have an error is when trying to dumb the bct. I would have to guess that this is the reason I'm stuck. While trying to dumb the bct APX Flash tool pops up and says "Could not find file bct.dec" I can't find any other tool to fix the bct. Any ideas?
RedOmega said:
I have the similar issue to gemneye.
I can use timmy deans euu tool to get to stock hc 3.2.1 and can boot without issues.
I can flash the v8 using apxflash and I install cwm thor 1.7.3.
Still boots up fine after flashing v8/recovery.
No matter what rom I install at this point I am stuck at the screen with "Booting primary kernel image". Even civato's stock rom won't go past this screen.
The only part of your instructions that I have an error is when trying to dumb the bct. I would have to guess that this is the reason I'm stuck. While trying to dumb the bct APX Flash tool pops up and says "Could not find file bct.dec" I can't find any other tool to fix the bct. Any ideas?
Click to expand...
Click to collapse
There is a specific order to doing things successfully with the Acer, any deviation at all and things wont work as they should. You must flash your rom directly after flashing the v8.
Flash the v8/cwm 1.7.3
Boot directly to cwm and complete a full wipe
Flash your rom
reboot.
If u run the v8 from HC and reboot without flashing an ICS rom first you will get stuck with booting primary kernel image...Why?? cos you have HC rom with the unlocked bootloader - the unlocked bootloader will only work with ICS/JB roms!! I'm assuming this is the reason for the "bct.dec" error as well. Try it again in the order I posted above
dibb_nz said:
There is a specific order to doing things successfully with the Acer, any deviation at all and things wont work as they should. You must flash your rom directly after flashing the v8.
Flash the v8/cwm 1.7.3
Boot directly to cwm and complete a full wipe
Flash your rom
reboot.
If u run the v8 from HC and reboot without flashing an ICS rom first you will get stuck with booting primary kernel image...Why?? cos you have HC rom with the unlocked bootloader - the unlocked bootloader will only work with ICS/JB roms!! I'm assuming this is the reason for the "bct.dec" error as well. Try it again in the order I posted above
Click to expand...
Click to collapse
Keep getting format errors when trying to flash anything now. APXFlash would hang repeatedly when trying to flash v8/cwm 1.7.3. Couldn't see any error messages in the cmd windows/debug but some of them closed so fast I may have missed it. So I went back to trying the manual return to 3.2.1 that OP used earlier and now I can't even get that to complete without errors.
nvflash --bct flash.bct --setbct --odmdata 0x100c0105 --configfile flash.cfg --crea
te --bl bootloader.bin --sbk 0x4CA71E00 0x74B3D706 0x9BFA3304 0xA02A2103 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x037c61c04240f357
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0x100c0105
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714385/714385 bytes sent
bootloader.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: GP1
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. FAILED!
command failure: create failed (bad data)
bootloader status: specified partition is invalid or does not exist (code: 7) me
ssage: nverror:0x42008 (0x6042008) flags: 0
I've tried babsector and manuall install of v8 using v8.bat as well and get error messages with those too.
Babsector gives me this:
creating partition: GPT
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x8 (0x19000008) flags: 0
v8.bat gives me some different errors:
Loading bootloader...
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x037c61c04240f357
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader_apx.bin
| 714981/714981 bytes sent
bootloader_apx.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x42004 (0x42004
) flags: 0
*****************************************************************
* Press any key when your A500/501/G100W is in bootloader mode *
*****************************************************************
Press any key to continue . . .
Flashing bootloader: bootloader_v8.bin ...
Nvflash started
[resume mode]
Formatting partition 4 please wait.. Command Execution failed cmd 13, error 0x12
0002
FAILED!
command failure: format partition failed (bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
Reading some of your replies in other posts Dibb, I'm guessing you'd say memory chip issue and that tab is toast?
Oh darn
Yep your conclusions are correct.
Maybe pickup new one off ebay they were going reasonably cheap awhile back sub US$80???
Sent from my GT-I9300 using Tapatalk 4