Bricked my 10.1 I/O, all buttons dead, nvflash still working I think

Search This thread
By:
Advanced…
W

woeds

Senior Member
Aug 13, 2008
424
12
Leiden
Ok, here's the story. I managed to brick my 10.1 Google I/O edition. It won't boot and I can't get it into recovery or download mode.

Here's what I did.

- I tried to flash this rom using Odin.
- The tablet started bootlooping
- I installed a CWM recovery, to do a full wipe.
- Then I saw this and flashed it using Odin.

When setting the PIT-file Odin got stuck and I had no option but to unplug and reset the tablet. Now the tablet is dead. When I hook it up using USB and use nvflash, it does seem to communicate bit.
Code: 
E:\Android\nv\nvflash>nvflash --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: 0x0288420042601557
   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: 1073840124
Code: 
E:\Android\nv\nvflash>nvflash --getpartitiontable test.txt
Nvflash started
rcm version 0X20001
System Information:
   chip name: t20
   chip id: 0x20 major: 1 minor: 3
   chip sku: 0x8
   chip uid: 0x0288420042601557
   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

command failure: no bootloader was specified

Can anyone please help me to breathe some life back into this thing? :(
 
used2hvatreo

used2hvatreo

Senior Member
Jun 26, 2008
496
60
Houston
woeds said:
Ok, here's the story. I managed to brick my 10.1 Google I/O edition. It won't boot and I can't get it into recovery or download mode.

Here's what I did.

- I tried to flash this rom using Odin.
- The tablet started bootlooping
- I installed a CWM recovery, to do a full wipe.
- Then I saw this and flashed it using Odin.

When setting the PIT-file Odin got stuck and I had no option but to unplug and reset the tablet. Now the tablet is dead. When I hook it up using USB and use nvflash, it does seem to communicate bit.
Code: 
E:\Android\nv\nvflash>nvflash --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: 0x0288420042601557
   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: 1073840124
Code: 
E:\Android\nv\nvflash>nvflash --getpartitiontable test.txt
Nvflash started
rcm version 0X20001
System Information:
   chip name: t20
   chip id: 0x20 major: 1 minor: 3
   chip sku: 0x8
   chip uid: 0x0288420042601557
   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

command failure: no bootloader was specified

Can anyone please help me to breathe some life back into this thing? :(
Click to expand...
Click to collapse

Ok, first thing, the second batch of code, the partition table stuff, won't work unless you have got the bootloader running from the first section of code.

Second, are you sure that you have a good bootloader.bin? try redownloading the nvflash stuff and start from scratch.

Once you have bootloader going, flash stock recovery and do a factory reset.

Then flash CWM so you can go back to the stock 3.1. After you get there we will continue.

(I played this game last night, and with some help you can get thru this prob)
 
W

woeds

Senior Member
Aug 13, 2008
424
12
Leiden
I redownloaded the nvflash stuff from http://xdaforums.com/showthread.php?t=1130574, but am still getting the same error.

Could it have anything to do with the fact that I tried to flash the TouchWiz rom and used the pit file? Could the partition table be screwed up?
I also tried extracting the bootloader from the TouchWiz rom, to no avail
Code: 
E:\Android\nv\nvflash>nvflash --bl tw.bin --go
Nvflash started
rcm version 0X20001
System Information:
   chip name: t20
   chip id: 0x20 major: 1 minor: 3
   chip sku: 0x8
   chip uid: 0x0288420042601557
   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: 1073840124

Does this rom contain a bootloader I can try? http://xdaforums.com/showthread.php?t=1162302
I opened the tar, but it only contains boot.img and system.img. I can't seem to open the boot.img file (I'm on Windows)
 
Last edited:
used2hvatreo

used2hvatreo

Senior Member
Jun 26, 2008
496
60
Houston
woeds said:
I redownloaded the nvflash stuff from http://xdaforums.com/showthread.php?t=1130574, but am still getting the same error.

Could it have anything to do with the fact that I tried to flash the TouchWiz rom and used the pit file? Could the partition table be screwed up?
I also tried extracting the bootloader from the TouchWiz rom, to no avail
Code: 
E:\Android\nv\nvflash>nvflash --bl tw.bin --go
Nvflash started
rcm version 0X20001
System Information:
   chip name: t20
   chip id: 0x20 major: 1 minor: 3
   chip sku: 0x8
   chip uid: 0x0288420042601557
   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: 1073840124
Click to expand...
Click to collapse

OK, based on these two links:

http://xdaforums.com/archive/index.php/t-1054492.html

http://xdaforums.com/showpost.php?p=14866282&postcount=3

You need to use nvflash to fix the BCT partition, and then run --bl bootloader bla blah blah.

I am at work, and I can try and post it later, but you should try and get that in the mean time. Maybe you backed it up???
 
W

woeds

Senior Member
Aug 13, 2008
424
12
Leiden
I've already tried searching for the .bct from an original Tab I/O 10.1, but can't find one. Could someone use nvflash to dump that for me?
 
K

Kitinas

Senior Member
Aug 24, 2009
50
8
Wow. I'm in almost the same situation you're in, except I'm able to flash the bootloader via nvflash, and from there flash via fastboot/recovery/odin, and boot into the OS. The tablet absolutely refuses to turn on without using nvflash.

I'd love to get a hold of the BCT file for this thing as well, if someone could post it.

I'm not sure how much help I can really offer here, but here's the bootloader.bin I'm using, and it works fine. Maybe yours went bad somehow.
 

Attachments

  • bootloader.zip
    964 KB · Views: 264
W

woeds

Senior Member
Aug 13, 2008
424
12
Leiden
Tried using the .bct with both the original and Kitinas' bootloader. No luck
Code: 
E:\Android\nv\nvflash>nvflash.exe --bct part2.bct --bl blnew.bin --go
Nvflash started
rcm version 0X20001
System Information:
   chip name: t20
   chip id: 0x20 major: 1 minor: 3
   chip sku: 0x8
   chip uid: 0x0288420042601557
   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: 1073840124


E:\Android\nv\nvflash>nvflash.exe --bct part2.bct --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: 0x0288420042601557
   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: 1073840124

I'm a total n00b with nvflash, haven't used it before today. I'm probably doing something wrong, but I don't know what.
 
W

woeds

Senior Member
Aug 13, 2008
424
12
Leiden
Is there a way I can reformat and repartition the nand memory? I think that because I used Odin with a .pit file, the partitioning got screwed up.

So in theory I hope this would work
-Repartition the memory to the standard layout
-Boot the bootloader
-Write the Tab 10.1 I/O system files and partitions.

Is this possible? can someone explain me how to do this? I've been doing some reading, and it seems I need a .cfg file if I want to repartition, where do I get that?
Seems to me I need to run the following command

"nvflash .exe" --bct XXXX.bct --setbct --bl bootloader.bin --configfile XXX.cfg --create --go (as seen here http://xdaforums.com/showthread.php?t=967915)
 
Last edited:
K

Kitinas

Senior Member
Aug 24, 2009
50
8
Well, following your link, I was able to at least pull a partition table for the tablet, as well as most of the partitions themselves. Looks like it could be used to create a config file, but there's a few things missing/that I'm not sure of.

I could pull all partitions except 14. For some reason it had an expected size listed, but the file went far, far beyond what it had listed. It was expected at about 350mb, but it reached over 5GB before I stopped it. Part14 is listed as HID, might be the actual storage space.

That being said, I really don't know how much good this will do, if any. While I'm no expert on this, I'm willing to bet that a .cfg file would really be nice here.

I've uploaded the partition table file, just in case it'll help.
 

Attachments

  • partition.txt
    1.6 KB · Views: 217
W

woeds

Senior Member
Aug 13, 2008
424
12
Leiden
Thanks! :D

So now, I have the partition info, and .cfg-file from another tablet
Code: 
PartitionId=2
Name=BCT
DeviceId=18
StartSector=0
NumSectors=1536
BytesPerSector=2048


PartitionId=3
Name=PT
DeviceId=18
StartSector=1536
NumSectors=256
BytesPerSector=2048


PartitionId=4
Name=EBT
DeviceId=18
StartSector=1792
NumSectors=1024
BytesPerSector=2048


PartitionId=5
Name=EB2
DeviceId=18
StartSector=2816
NumSectors=1024
BytesPerSector=2048


PartitionId=6
Name=GP1
DeviceId=18
StartSector=3840
NumSectors=2048
BytesPerSector=2048


PartitionId=7
Name=EFS
DeviceId=18
StartSector=5888
NumSectors=6144
BytesPerSector=2048


PartitionId=8
Name=SOS
DeviceId=18
StartSector=12032
NumSectors=2560
BytesPerSector=2048


PartitionId=9
Name=LNX
DeviceId=18
StartSector=14592
NumSectors=4096
BytesPerSector=2048


PartitionId=10
Name=APP
DeviceId=18
StartSector=18688
NumSectors=295936
BytesPerSector=2048


PartitionId=11
Name=CAC
DeviceId=18
StartSector=314624
NumSectors=229376
BytesPerSector=2048


PartitionId=12
Name=MSC
DeviceId=18
StartSector=544000
NumSectors=1024
BytesPerSector=2048


PartitionId=13
Name=MDM
DeviceId=18
StartSector=545024
NumSectors=6144
BytesPerSector=2048


PartitionId=14
Name=UDA
DeviceId=18
StartSector=551168
NumSectors=14871808
BytesPerSector=2048


PartitionId=15
Name=OTA
DeviceId=18
StartSector=15422976
NumSectors=4096
BytesPerSector=2048


PartitionId=16
Name=HID
DeviceId=18
StartSector=15427072
NumSectors=153600
BytesPerSector=2048


PartitionId=17
Name=GPT
DeviceId=18
StartSector=15580672
NumSectors=512
BytesPerSector=2048
Code: 
[device]
type=hsmmc
instance=3

[partition]
name=BCT
id=2
type=boot_config_table
allocation_policy=sequential
filesystem_type=basic
size=3145728
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=PT
id=3
type=partition_table
allocation_policy=sequential
filesystem_type=basic
size=4096
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=EBT
id=4
type=bootloader
allocation_policy=sequential
filesystem_type=basic
size=4194304
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=bootloader.bin


[partition]
name=SOS
id=5
type=data
allocation_policy=sequential
filesystem_type=basic
size=5242880
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=recovery.img

[partition]
name=LNX
id=6
type=data
allocation_policy=sequential
filesystem_type=basic
size=8388608
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=boot.img

[partition]
name=BAK
id=7
type=data
allocation_policy=sequential
filesystem_type=basic
size=5242880
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=GP1
id=8
type=GP1
allocation_policy=sequential
filesystem_type=basic
size=1048576
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=APP
id=9
type=data
allocation_policy=sequential
filesystem_type=basic
size=536870912
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=system.img

[partition]
name=CAC
id=10
type=data
allocation_policy=sequential
filesystem_type=ext3
size=554700800
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=MSC
id=11
type=data
allocation_policy=sequential
filesystem_type=ext3
size=2097152
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=USP
id=12
type=data
allocation_policy=sequential
filesystem_type=ext3
size=554700800
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0


[partition]
name=PER
id=13
type=data
allocation_policy=sequential
filesystem_type=basic
size=5242880
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=YTU
id=14
type=data
allocation_policy=sequential
filesystem_type=basic
size=524288
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=UDA
id=15
type=data
allocation_policy=sequential
filesystem_type=ext3
size=18432
file_system_attribute=0
partition_attribute=0
allocation_attribute=0x808
percent_reserved=0

[partition]
name=GPT
id=16
type=GPT
allocation_policy=sequential
filesystem_type=basic
size=0xFFFFFFFFFFFFFFFF
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
It seems as if I can multiply NumSectorsxBytesPerSector for every partition and use that numer as the 'size' value. Does anyone know if that will work? It would lead to the following .cfg file
Code: 
[device]
type=hsmmc
instance=3

[partition]
name=BCT
id=2
type=boot_config_table
allocation_policy=sequential
filesystem_type=basic
size=3145728
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=PT
id=3
type=partition_table
allocation_policy=sequential
filesystem_type=basic
size=524288
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=EBT
id=4
type=bootloader
allocation_policy=sequential
filesystem_type=basic
size=2097152
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=bootloader.bin


[partition]
name=EB2
id=5
type=data
allocation_policy=sequential
filesystem_type=basic
size=2097152
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0


[partition]
name=GP1
id=6
type=data
allocation_policy=sequential
filesystem_type=basic
size=4194304
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=boot.img

[partition]
name=EFS
id=7
type=data
allocation_policy=sequential
filesystem_type=basic
size=12582912
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=SOS
id=8
type=GP1
allocation_policy=sequential
filesystem_type=basic
size=5242880
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=recovery.img

[partition]
name=LNX
id=9
type=data
allocation_policy=sequential
filesystem_type=basic
size=8388608
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=boot.img

[partition]
name=APP
id=10
type=data
allocation_policy=sequential
filesystem_type=ext3
size=606076928
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=system.img

[partition]
name=CAC
id=11
type=data
allocation_policy=sequential
filesystem_type=ext3
size=469762048
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=MSC
id=12
type=data
allocation_policy=sequential
filesystem_type=ext3
size=2097152
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0


[partition]
name=MDM
id=13
type=data
allocation_policy=sequential
filesystem_type=basic
size=12582912
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=UDA
id=14
type=data
allocation_policy=sequential
filesystem_type=basic
size=30457462784
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=OTA
id=15
type=data
allocation_policy=sequential
filesystem_type=ext3
size=8388608
file_system_attribute=0
partition_attribute=0
allocation_attribute=0x808
percent_reserved=0

[partition]
name=HID
id=16
type=data
allocation_policy=sequential
filesystem_type=basic
size=314572800
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=GPT
id=18
type=GPT
allocation_policy=sequential
filesystem_type=basic
size=1048576
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

Before I go and try to use this on my Tab, I'd be really nice if someone could tell me if this won't brick it any further :)
 
Last edited:
stinky73

stinky73

Senior Member
Aug 28, 2010
375
116
Courchevel
You are using the wrong command string!

Basics first, you must have a binloader.bin in your working nvflash directory, it does not matter which one...this file is effectively loaded into meomry and allows you to address the tegra...if you use the correct command :)

...this one bootloadersmall.rar will do to put into partition 4 of your device (I say this because the "odin run" changes partiton size and the standard I/O bootloader is too big for the resized partition) this bootloader will give you recovery and download from the two button start up combination. Unrar it twice, once "as is" then again renaming it bootloader.img

So in your nvflash directory you now have a bootloader.bin and a bootloader.img

You say you think you have a bad bct partition as well but you have the file for that, so let's start with the bootloader and do this step by step so you can visually confirm the process

these are the strings from command window in the nvflash directory

#1 "nvflash --bl bootloader.bin --go"

You should get a message like this
sending file: bootloader.bin
/ *******/******* bytes sent
bootloader.bin sent successfully
waiting for bootloader to intialize
bootloader downloaded successfully

It will then return to the cursor so next step is

#2 "nvflash --resume --download 4 bootloader.img"

That should re-write the bootloader in your tegra, try to reboot and see what happens. If the bct is ok then it should work, if not reload the bct using the same two commands above but substitute 2 for 4 for the partiton you are addressing and your filename for bct as opposed to bootloader. I think another error is that the file should be named .img and not .bin......can't swear to this but does ring alarm bells especially because of your error "bct file not found"

Hope this helps

(You can actually do it all in one command but the way I showed you above will reassure you that the process is advancing - full string would be "nvflash --bl bootloader.bin --download 4 bootloader.img"
 

Attachments

  • bootloadersmall.rar
    1.1 MB · Views: 231
W

woeds

Senior Member
Aug 13, 2008
424
12
Leiden
Hey stinky73

Thank you for the detailed reply. I unpacked the bootloader twice, renamed one to img, and ran the command you said.
Code: 
C:\nvflash>nvflash --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: 0x0288420042601557
   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: 1073840124

Unfortunately, the result is the same as before :/
 
K

Kitinas

Senior Member
Aug 24, 2009
50
8
Hm. That config file is a bit different than the one I built. Unfortunately, it's at home and I'm at work. I'm rather weary of using either of them, just cause my tablet does actually sorta work. I also calculated the sizes differently(though they were the same in the end). I just pulled each partition and noted the file size. Part14 caused a problem though, like I said before. I also see yours skips partition17.

What tablet/tegra device did you grab that config file from? Mine was from a g-tab(I think the Toshiba). It only had I think 13 partitions listed, though the final partition had "size=0xFFFFFFFFFFFFFFFF" same as the config you have. I'm willing to bet it needs that so the last partition just takes up the remaining space.
 
W

woeds

Senior Member
Aug 13, 2008
424
12
Leiden
Kitinas said:
Hm. That config file is a bit different than the one I built. Unfortunately, it's at home and I'm at work. I'm rather weary of using either of them, just cause my tablet does actually sorta work. I also calculated the sizes differently(though they were the same in the end). I just pulled each partition and noted the file size. Part14 caused a problem though, like I said before. I also see yours skips partition17.

What tablet/tegra device did you grab that config file from? Mine was from a g-tab(I think the Toshiba). It only had I think 13 partitions listed, though the final partition had "size=0xFFFFFFFFFFFFFFFF" same as the config you have. I'm willing to bet it needs that so the last partition just takes up the remaining space.
Click to expand...
Click to collapse

I think this one is from an Eee Pad Transformer
 
P

pershoot

Inactive Recognized Developer
Dec 1, 2008
8,021
4,375
as per my PM to you:

if you feel you have tried all button combos, then do this:

plug in to usb
power + vol up until you hear the notification on your pc. this is APX mode.
unplug usb.
wait till battery runs out.
plug in to wall.
now boot it with power.
it should boot.
 
  • Like
Reactions: emstone and woeds
You must log in or register to reply here.

Similar threads

djR3Z
  • Sticky
[GUIDE] How to Root the Samsung Galaxy Tab 10.1 [Video Walkthrough]
Replies
508
Views
795K
L
losreelos@hotmail.com
Y
Official ICS for GALAXY Tab 10.1 P7500
Replies
168
Views
211K
G
Genjuro01
T
  • Sticky
Super Easy Root Method for Tab 10.1 (Noob Friendly Guide)
Replies
233
Views
257K
H
hugopugo
Jiia
  • Sticky
[GUIDE] Rooting Galaxy Tab 10.1 - ICS
Replies
47
Views
176K
W
wqhjstudios
M
Tutorial: How to Restore Your Galaxy Tab 10.1 back to stock using ODIN
Replies
37
Views
152K
K
kristotab

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 2
    P
    pershoot
    as per my PM to you:

    if you feel you have tried all button combos, then do this:

    plug in to usb
    power + vol up until you hear the notification on your pc. this is APX mode.
    unplug usb.
    wait till battery runs out.
    plug in to wall.
    now boot it with power.
    it should boot.
    View
    1
    used2hvatreo
    used2hvatreo
    woeds said:
    I've already tried searching for the .bct from an original Tab I/O 10.1, but can't find one. Could someone use nvflash to dump that for me?
    Click to expand...
    Click to collapse

    Try this.

    just change extension from txt to bct.

    good luck

    fyi size should be: 3145728 bytes
    View
    1
    stinky73
    stinky73
    Config file is here http://droidbasement.com/galaxy/nvflash/ in the nvflash.zip file

    Thanks to Pershoot, of course :)
    View
    1
    W
    woeds
    EViL3666 said:
    Mine seems to go into APX mode without USB just by pressing the power button, but it possibly powers it self off if nothing is connected - so I'm thinking a bit of sticky tape across the power button should do it.

    But I'm not confident this will fix it, essentially the partitions are damaged.. this seems more like a "leap of faith" but I'm know expert, and willing to try anything ;)
    Click to expand...
    Click to collapse

    Hmm, mine actually does the same thing. And if I press power for 10secs and then connect it, it comes up as the APX device.

    So I now disconnected it, pressed power for about 10 secs, and let it be. If I'm not mistaken, it should be in APX mode now and draining.
    View
    1
    G
    grkmaster
    so my device somehow bricked on its own after the screen became unresponse, went to reboot and nothing.. nvflash only.. so i did what evil was talking about.. connected the usb and it connects and disconnects .. so now removed the usb and being patient

    so i know its on a auto reboot now .. hoping to kill the battery faster this way lol.. i already rma'd it back to newegg.. so im just hoping to get my **** off of it .. or cancel the rma...
    View

New posts