Background information: Tf101 b60 randomly stopped booting while using it. It's unrooted and stock. I tried to nvflash it with different builds to no avail. It just boot loops (asus logo and then turns off). It doesn't read the recovery for some reason, it just says "booting recovery kernel" and then turns off. APX mode works in a sense that I can NVflash, but my pc doesn't really detect it as APX; it just detects it as "unknown device". NVflash succeeds (nothing fails, I've watched it run through it at least 10 times and see nothing fail, but when it's supposed to restart, it just turns off instead. Can somebody please help me or steer me in the right direction? Thank you so much in advance!
EDIT: Additional info: I've also tried wiping and cold booting. It just doesn't work ):
I'll be replying as fast as I can if any other information needs to be provided.
Did you install the drivers? I'd do this anyway,
What Region (SKU) are you on? US, WW, CN? Etc..?
It's important to get the right one, NvFlash Should work too.
ToD
I'm from Canada but I tried both us and ww ill give ww a try and see if it woeks
Drivers are more important, try downloading and flashing either of these:
Take US or WW, I'd prefer US: http://xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)/STOCK+ROMS/ICS+.24
Make sure it says APX and Not Unknown device in Device manager before NvFlashing, or I almost guarentee it won't work. Right click 'Unknown Device' and hit 'Update Driver' Then point it to the APX driver folder included with these downloads above.
Also make sure you're using the proper Sbkversion. (Yours should be sbkv1)
I got the drivers to say APX rather than unknown device, but still didn't change. I used the US version from the link you gave me. :/ any other suggestions? P.S. I really appreciate the help you've given me, regardless if it hasn't worked yet
Just realized : After 1 nvflash the "APX" in device manager changed to NVIDIA USB Boot-recovery driver for Mobile devices. Is this normal?
Can I have a log of what NvFlash says?
You may want to try wiping Via NvFlash and then reflashing.
How do I grab the log and how do I wipe using nvFlash?
Closest I can do to grabbing the log
{
"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"
}
after this it just closes and the tf101 turns off rather than reboots.
Grab the log from CMD prompt by rightclicking, hit 'mark' then drag the entire area of the log, and hit either CTRL-C or Copy. Then it's copied.
Regarding wiping, I'll need to look into that a bit, can't quite remember.
EDIT: The command should be Nvflash --format_all
Posted images, I'll grab it in text form right now.
Code:
C:\Users\Jeff\Desktop\NVFLASH_ICS_9.2.1.24_US_NOROOT>cd C:\Users\Jeff\Desktop\NV
FLASH_ICS_9.2.1.24_US_NOROOT\
C:\Users\Jeff\Desktop\NVFLASH_ICS_9.2.1.24_US_NOROOT>"nvflash.exe" --bct transfo
rmer.bct --setbct --configfile flash.cfg --create --bl blob.EBT --odmdata 0x300d
8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x028842004020a097
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 2
device config fuse: 0
sdram config strap: 0
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: blob.EBT
| 1454712/1454712 bytes sent
blob.EBT 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: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 GPT please wait.. done!
done!
sending file: blob.EBT
| 1454712/1454712 bytes sent
blob.EBT sent successfully
sending file: blob.SOS
\ 4284416/4284416 bytes sent
blob.SOS sent successfully
sending file: blob.LNX
/ 4151296/4151296 bytes sent
blob.LNX sent successfully
sending file: blob.APP
/ 1835008/536870912 bytes sent
Don't see Any errors, really weird...
The command should be Nvflash --format_all
Sent that with my tf101 in APX mode and it said
"Nvflash started
rcm version 0X4
Command send failed (usb write failed)"
Did you try in resume mode -r? I'm really confused as to why NvFlash is being wonky.
I'll give it a try when I'm home, would I put in that command the same way I put in "Nvflash --format_all"? By CDing to the folder and just that command? or..? Sorry if I'm bothering you :/
No bother, cd to nvflash folder, -r --format_all
Getting "[resume mode]
Command failure: no commands found"
-r not working in general.
Bump ): Please Thing o Doom, don't give up hope for me yet ):
Sorry, thought I responded again..
You need to use Wheelie to use resume properly in this instance: http://forum.xda-developers.com/showthread.php?p=26638718
download and overwrite all nvflash files in the stock .zip folder with these, then run in -r
Run wheelie reflash sbkv1 or 2 .bat first, and wheelie to get resume working for format all.
sigh ): It's still not booting. getting the same errors as before :/
I don't know, at this point I'd really have to see it. NvFlash should work.
I'll give everything a try on another computer; if it doesn't work, I give up. Regardless, thank you so much for your time and your help. I'm sure the TF101 community really appreciates it.
Related
I think its done for but I want to be sure. I've used nvflash many times to revert to stock but this time I tried the format rom (http://forum.xda-developers.com/showthread.php?t=974422) just before I tried to revert.
So far I've tried flashing with nvflash following the directions here (http://forum.xda-developers.com/showthread.php?t=861950) using the 1105 and the 1126 images. The format rom still completes but the stock rom gives the following output.
"nvflash.exe" --bct gtablet.bct --setbct --bl bootloader.bin --configfile gtablet.cfg --create --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x1714400940ffc357
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
sending file: gtablet.bct
- 4080/4080 bytes sent
gtablet.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
setting device: 1 0
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBT
creating partition: BLO
creating partition: MSC
creating partition: OGO
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBT please wait.. done!
Formatting partition 6 BLO please wait.. done!
Formatting partition 7 MSC please wait.. done!
Formatting partition 8 OGO please wait.. done!
Formatting partition 9 SOS please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 APP please wait.. done!
Formatting partition 12 CAC please wait.. done!
done!
sending file: part4.img
/ 2097152/2097152 bytes sent
part4.img sent successfully
sending file: part5.img
\ 131072/131072 bytes sent
part5.img sent successfully
sending file: part6.img
/ 4194304/4194304 bytes sent
part6.img sent successfully
sending file: part7.img
/ 16777216/16777216 bytes sent
part7.img sent successfully
sending file: part8.img
/ 3407872/33554432 bytes sentdata send failed NvError 0x120002
command failure: create failed (bad data)
Press enter to continue:
I've tried to use nvflash to get CM .8 back but nothing seems to work. I hope someone has an idea on how to recover from this.
Thanks in advance
ok, I fixed my issue and found a new one.
1. I re-downloaded the format
and the 1126 rom files.
2. I re-ran the format rom.
3. I copied the files from "nvflash_gtablet_46_2010112600.zip" into the same directory as the format rom files and ran the new nvflash_gtablet.bat file.
For some reason this time it worked. I tried this before but for some reason it worked this time.
Once I got in I updated to 3588 using the OTA updater and now it only boots in to APX. Seems others are having the same issue. I'll keep trying to get this resolved but if anyone has some insight into this problem I'd love to hear it.
Well, you probably already know, but for the sake of beginning a new, clean thread-
Using nvflash.exe, you can simply
nvflash.exe --bl bootloader.bin --format_partition 2 --go
And it will reboot your tablet without erasing anything important.
Holding down the volume key will get you into recovery mode as well, if you hold it before you press enter.
Hope we can fix this. Im tired of explaining how i fried something and it wont boot with a computer.
So after many hours of searching the forums and web for different possible solutions, and trying them all, I think I'm going to throw in the towel. Mine is still in the 30 days for a return so I think I'll just return it and get another.
All my issues started when I tried the format rom, so that's one I'll not do again.
Good luck to everyone still fighting to get their gtab to boot out of APX mode.
You might have better luck with the 1105 image. I would give that one more try before you give up. You might also need to reinstall ClockworkMod and repartition your internal sdcard.
When you say you can only get into APX mode, will the unit not power up at all or are you only getting bootloops of the Viewsonic and G-Tablet screens?
notwen said:
When you say you can only get into APX mode, will the unit not power up at all or are you only getting bootloops of the Viewsonic and G-Tablet screens?
Click to expand...
Click to collapse
APX mode is like fastboot mode in other devices.
On the gtablet, it is a blank, unlit screen.
It waits for a command from a host device, and once it gets one, the screen lits up black with a single line of text.
Its as if the unit doesnt power up, but it really does. The only way to tell is to have it plugged up to a computer.
I mean, you can use nvflash to boot it.
And i will try the 1105 image in the next 24 hours and report if it got the device to boot independently.
Hey guys,
I was testing out nvflash and ran the download.bat on my new transformer and now it's stuck in APX mode.
I see when running nvflash, it says:
F:\nvflashtf>download.bat
F:\nvflashtf>cd F:\Chrome DL\nvflash\nvflashtf\
F:\nvflashtf>"nvflash.exe" --bct transformer.bct --setbct --co
nfigfile flash.cfg --create --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x168
2CCD8 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: 0x037c6208417fd657
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
| 943193/943193 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: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 GPT please wait.. done!
done!
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
sending file: recovery.img
\ 5085184/5085184 bytes sent
recovery.img sent successfully
file not found: boot.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
Click to expand...
Click to collapse
Now the screen is black and keeps going into apx.
Before running it I had rooted 3.1 and had just updated to 3.2 which worked fine.
Any help please?
Thanks
I don't think you're supposed to update after you've rooted
I bricked one that way
Hmm, well things seemed to be fine after doing so. It was just the nvflash which finished me off. I'm new to all this.
Any suggestions on getting it back? I have the whole weekend to try now.
Try redownloading the nvflash files? Maybe the checksum failed.
It seems boot.img was not found, but your download.sh script tries to install it.
it is because you have run nvflash in create mode which partitions and installs the android system, but you don't have an android systems images in the same folder as nvflash and the batch file.
download prime 1.6 nvflash edition, put it in the same folder as these files, and run that script again
lilstevie said:
it is because you have run nvflash in create mode which partitions and installs the android system, but you don't have an android systems images in the same folder as nvflash and the batch file.
download prime 1.6 nvflash edition, put it in the same folder as these files, and run that script again
Click to expand...
Click to collapse
Thanks! This made a lot of sense after I read it. I downloaded the nvflash edition and ran the download.bat. It found the missing files and copied them to the transformer successfully. I then rebooted the device and was back in action with prime. Appreciate it!
compywiz said:
Hey guys,
I was testing out nvflash and ran the download.bat on my new transformer and now it's stuck in APX mode.
I see when running nvflash, it says:
Now the screen is black and keeps going into apx.
Before running it I had rooted 3.1 and had just updated to 3.2 which worked fine.
Any help please?
Thanks
Click to expand...
Click to collapse
Just be glad you didn't put your device in a permanent apx bootloop. You're just missing the android system image.
I've had to deal with a few devices that was somehow put in permanent apx bootloop by their owners. Before I actually got my hands on these devices, I honestly thought they didn't really exist and that it was just users' ignorance. But damn, these devices with permanent apx bootloop are hard to unbrick.
goodintentions said:
Just be glad you didn't put your device in a permanent apx bootloop. You're just missing the android system image.
I've had to deal with a few devices that was somehow put in permanent apx bootloop by their owners. Before I actually got my hands on these devices, I honestly thought they didn't really exist and that it was just users' ignorance. But damn, these devices with permanent apx bootloop are hard to unbrick.
Click to expand...
Click to collapse
Definitely glad. The funny thing is I ran the nvflash because I wanted to see if it worked for getting a clean install, little did I know I would make it cleaner than I wanted :x. I had an idea that I needed to supply the files, but really had no idea where to get them. Luckily lilstevie pointed me in the right direction. I've since updated to Prime HC3.2 and loving it so far.
Glad it's back and working now though!
Hi all.
I tried to install rom on my Eee Pad but i failed and my device is broke now
please help me.
that what i did..
- i installed Windows nvflash with APX drivers successfuly
- then i installed SU using Razorclaw_1.0.1.apk successfuly
- then start my device with APX mode with windows 7 on my kaptop
- then i start download.bat from nvflash folder, everything done
but the device just show me .. black screen with message
entering nvflash recvery mode / nv3p server
chip uid : .... some numbers i don't remember
my device info ..
kernal
2.6.36.3
build
HTK75.CN_epad-8.6.5.19-20111107
android
3.2.1
Please any help .. its first day with my Eee Pad Transformer
Thanks
You got an apx bootloop going on there. You need to nvflash your way out of there.
goodintentions said:
You got an apx bootloop going on there. You need to nvflash your way out of there.
Click to expand...
Click to collapse
How?
i know nothing about android at all, some details will help
please
First of all, what's your seriel number?
goodintentions said:
first of all, what's your seriel number?
Click to expand...
Click to collapse
s/n : B70kas151295
This is the log when run download.bat
Code:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x03806209421fa5d7
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: 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
| 943193/943193 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: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 GPT please wait.. done!
done!
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
file not found: recovery.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
Hang on, I'm confused about something. Why did you nvflash after you rooted?
goodintentions said:
Hang on, I'm confused about something. Why did you nvflash after you rooted?
Click to expand...
Click to collapse
i don't have any experiance with that, i did that to access the recovery options
i just tried to install rom from here http://forum.xda-developers.com/showthread.php?t=1245892
Why didn't you flash via cwm? Nvflash isn't exactly for those who are new to android, you know. What a mess...
It looks like the nvflash process went ok. The only thing that's missing is the recovery.
Do this for me. Press down and hold the power button for about 20 seconds. Then wait abou 20 seconds. Then press down and hold the power button for about 5 seconds. Tell me what you see.
goodintentions said:
Why didn't you flash via cwm? Nvflash isn't exactly for those who are new to android, you know. What a mess...
It looks like the nvflash process went ok. The only thing that's missing is the recovery.
Do this for me. Press down and hold the power button for about 20 seconds. Then wait abou 20 seconds. Then press down and hold the power button for about 5 seconds. Tell me what you see.
Click to expand...
Click to collapse
sorry i don't know about cwm
i did it, nothing happened
not turned on
CWM/ClockWorkMod is a common recovery tool. It is somewhat like booting into a recovery partiton that allows you to backup/restore using a MicroSD. Also whiping data.
Sent from my Transformer TF101 using Tapatalk
yes.
what should i do to get my device work again?
What ROM were you trying to flash? Also I noticed you're missing the recovery image so when you try and go through the process it crashes at flashing the recovery and everything after that doesn't get flashed so you don't have a system image either. This is why your TF won't boot.
fadiodeh said:
bootloader.bin sent successfully
file not found: recovery.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
Click to expand...
Click to collapse
What files did you download and from where?
brando56894 said:
What ROM were you trying to flash? Also I noticed you're missing the recovery image so when you try and go through the process it crashes at flashing the recovery and everything after that doesn't get flashed so you don't have a system image either. This is why your TF won't boot.
What files did you download and from where?
Click to expand...
Click to collapse
Hi,
thanks to reply,
i download this .. http://ff06d07.filefactory.com/dl/f...822c5b18bdf8d2e664f2b163ae76fff/n/nvflash.zip
then i tried to set Prime 1.4 files but i can't find boot.img and recovery.img on it, its just contain one file system.img, i download it from here http://www.sdx-downloads.com/devs/roach2010/flash_roms/prime_v1.4.tar.bz2
i want to install Android Revolution HD from this link http://forum.xda-developers.com/showthread.php?t=1245892
or back to stock os at least .
Thanks
how can i get the correct recovery.img and boot.img files for my device ?
IIRC you need to combine the files that came with NVflash with the files that came with Prime. You will flash Android Revolution later (you can actually do it without flashing Prime and just install CWM but I don't really remember the process, search for it) via clockwork mod recovery (CWM).
Here's a guide to read: Guide
I'm uploading the stock images for you.
You really should have read some more before you tried this.
brando56894 said:
IIRC you need to combine the files that came with NVflash with the files that came with Prime. You will flash Android Revolution later (you can actually do it without flashing Prime and just install CWM but I don't really remember the process, search for it) via clockwork mod recovery (CWM).
You really should have read some more before you tried this.
Click to expand...
Click to collapse
i did, but the files in Prime 1.4 is just one file system.img, i can't find recovery.img and boot.img
i got prime 1.4 from here http://www.sdx-downloads.com/devs/roach2010/flash_roms/prime_v1.4.tar.bz2
what should i do ?
I got this ..
ICS Themed Vanilla Release
Prime! v2.1.0
files .. system.img, boot.img and recovery.img
the issue is when start NVflash its disconnected USB automatically,
see the log please ..
Code:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x03806209421fa5d7
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: 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
| 943193/943193 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader failed NvError 0x0
command failure: bootloader download failed
and
Code:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x03806209421fa5d7
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: 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
| 943193/943193 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: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. done!
failed executing command 14 NvError 0x30012
command failure: create failed
its not disconnected in specific step, its randomly
its working now with ICS Themed Vanilla Release
after a lot with tries using Brks_rootkit_v7
Thanks a lot for all there
have a great day
You're welcome and glad you got it fixed!
Original Thread: http://forum.xda-developers.com/showthread.php?p=19724276
I highly recommend running with 'Debug Mode' checked! Please report any issues and I will get to it as soon as I can.
{
"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"
}
*****THIS METHOD IS DESTRUCTIVE TO DATA***** THIS WILL ERASE ALL OF YOUR DATA AND INSTALL A FRESH COPY *****
YOUR ARE RESPONSIBLE FOR ANY DAMAGE THAT MAY OCCUR WHILE USING THIS PROGRAM. MYSELF NOR ANY OTHER PERSON OTHER THAN YOURSELF IS LIABLE FOR ANYTHING THAT MAY OCCUR DURING ITS USE.
What you need:
Nvflashable ROM
Ubuntu Filesystem
SBK2 system
Instructions:
1.) Extract archive to a location of your choice.
2.) Put Ubuntu.img and ROM into main folder ( Ubuntu, system, boot and recovery IMG's, and bootloader.bin )
3.) Run the tool.
4.) Do whatever you like
*note: Ubuntu may have to resize the partition. Let it do its thing it may take a couple of minute to do it.
To use Ubuntu you have to press power and volume down when booting. And then press volume up.
Nvflash and abootimg are property of their respective owners.
##DOWNLOADS##
Frank's Tools *SBKv2* [removed again for development]
Lilstevie's Thread - Ubuntu Filesystem(Ubuntu.img)
In a APX Bootloop from a previous version? Do this and fix that issue.
##Donations##
Donation link *As requested via PM and other threads
This is great to see. I suspect there will be a some happy SBK2 owners lol. I think I saw a post of yours saying something about implementing the 3.1 kernel into this installer, does this or do you have plans of adding it?
Cheers
JoinTheRealms said:
This is great to see. I suspect there will be a some happy SBK2 owners lol. I think I saw a post of yours saying something about implementing the 3.1 kernel into this installer, does this or do you have plans of adding it?
Cheers
Click to expand...
Click to collapse
I plan on loading the ubuntu.img onto my Linux PC and seeing if I can get everything pre-installed and such for the 3.1 kernel, or if there is a way to automatically install everything. When I figure that out I will make a checkbox to install jhinta's 3.1 kernel.
kenshin1388 said:
I plan on loading the ubuntu.img onto my Linux PC and seeing if I can get everything pre-installed and such for the 3.1 kernel, or if there is a way to automatically install everything. When I figure that out I will make a checkbox to install jhinta's 3.1 kernel.
Click to expand...
Click to collapse
Cool I'm on a SBK1 so i cant test but I'm looking forward to seeing how it goes.
Me too
Initially it told me "wlybl.bin" didn't exist so I renamed "whybl.bin" to match, this made it work so I hope it was just a typo.
I was good until...
Code:
ubuntu.img sent successfully
failed executing command 25 NvError 0x30012
command failure: sync failed
Then it booted into Android automatically and I shut it down to test Ubuntu.
Held the Volume Down key and Power but nothing happens.
Holding down the Power key by itself and I get nothing.
This is my first time working with NVFlash, I used the ROM from the bottom of this page because I wanted root- http://http://forum.xda-developers.com/showthread.php?t=1514658- and it doesn't appear that the downloads page works, although I would really like to use Revolver eventually.
Any suggestions? I'm feeling a little bricked ATM.
Thanks for doing all this to make it work for us late-blooming SBK2 owners.
Did you have bootloader.bin, system.img, boot.img, and recovery.img all backed up from your current ROM already? To fix it not booting you could use this PERI tool. Thanks for letting me know about the typo, I'll get to that after work. If you use the wheelie tool try to download everything to the TF101 manually. Here is a list of appropriate partitions:
Partition 4 (EBT) = bootloader.bin
Partition 5 (SOS) = linux.img
Partition 6 (LNX) = boot.img
Partition 9 (APP) = system.img
Partition 16 (UBT) = ubuntu.img
If you would like me to make a batch file prepared for the wheelie tool I can. Apologies for it softbricking your tablet
EDIT: You could try this with wheelie. Save it as a .bat in the same directory as wheelie. Since you already have re-formatted correctly with this tool there is no need to use the download SBKv2 batch contained in the wheelie download to reformat again.
cd %~dp0
"wheelie.exe" -2 --bct transformer.bct --bl bootloader.bin --odm 0x300d8011
"nvflash.exe" -r --download 4 bootloader.bin
"nvflash.exe" -r --download 5 linux.img
"nvflash.exe" -r --download 6 boot.img
"nvflash.exe" -r --download 9 system.img
"nvflash.exe" -r --download 16 ubuntu.img
pause
exit
Thanks for the help, it helped me get back to full stock at least but flashing individual partitions didn't work for me.
I actually got it working with http://forum.xda-developers.com/showthread.php?t=1537566. I'm away from my home Windows machine and using a laptop running Linux. I still want to try to get this to work though so I'm going to wipe and try the tool here later.
Question: How can I get the system, boot, Linux, etc images from a current backup, or is that what cache.ext4.tar, data.ext4.tar, and system.ext4.tar are?
Sent from my MB865 using xda app-developers app
It should (updated yesterday) get the images by itself now.
Ok, a couple of issues.
Wheelie starts up just fine, using wlybl, but then it tries to start nvflash with bootloader.bin before it's pulled it so that fails. Then, download of "4 bootloader.bin" itself fails. I'm trying a couple of things but every time I run it it formats all the partitions whether or not it's going well already so I have to reflash stock with wheelie and then root and install recovery with peri since this is going to overwrite my recovery partition.
Wasn't fast enough to copy a full log, is that saved somewhere? I'm going to try again but provide the *.img files myself and hope that works out.
I'm going to start work on a program written in Java to do this if I cannot get it working. At least now I know exactly why its failing. Thanks for that information, I'll check it out as soon as I can. I should be able to spare the $10 to buy myself a new sync cable on friday. I'll start work on the Java program tonight though, just to get the base built. For this, I'll try to explore why its not waiting for wheelie to finish. Might need to add in a boolean or 2 and try it then.
Thanks for the information though, it was very helpful as I cannot test it myself right now due to a bad sync cable.
Alright that is some very helpful information. I'll see about a temp fix of a 3-click instead. Meaning a click to setup wheelie, another click to get files, then another to flash. Not the best method nor one I am proud to have to do, but its better than softbricking each time it uses. I'm very busy until wednesday though. Hopefully friday I will be able to spare the $10 for a new sync cable so that I should be able to test once that comes in.
Anyways, thanks again. I'll get to it as soon as possible.
I used the dual boot wizard and after completion it bootet into Prime. But once I restart it only goes to APX Mode.
This is the log:
Code:
Nvflash started
[resume mode]
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: UBT
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 UBT please wait.. done!
Formatting partition 17 GPT please wait.. done!
done!
sending file: bootloader.bin
bootloader.bin sent successfully
sending file: linux.img
linux.img sent successfully
sending file: boot.img
boot.img sent successfully
sending file: system.img
system.img sent successfully
sending file: ubuntu.img
ubuntu.img sent successfully
failed executing command 25 NvError 0x30012
command failure: sync failed
Seems like it didn't send recovery.img file?
The recovery.img is a backup file for restore later, its just smart to have one. I am still looking into the problem of why its rebooting into android fine, but not going into Ubuntu. I just got a new cord in for my tablet, but the PC power supply went out so I am back a few days until that comes in. Hopefully I will be able to get it fixed then. Apologies.
farshid.tavakoli said:
I used the dual boot wizard and after completion it bootet into Prime. But once I restart it only goes to APX Mode.
This is the log:
Code:
Nvflash started
[resume mode]
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: UBT
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 UBT please wait.. done!
Formatting partition 17 GPT please wait.. done!
done!
sending file: bootloader.bin
bootloader.bin sent successfully
sending file: linux.img
linux.img sent successfully
sending file: boot.img
boot.img sent successfully
sending file: system.img
system.img sent successfully
sending file: ubuntu.img
ubuntu.img sent successfully
failed executing command 25 NvError 0x30012
command failure: sync failed
Seems like it didn't send recovery.img file?
Click to expand...
Click to collapse
I got this problem too. But it goes to Android after the failure. When I turn it off, it goes into APX Mode
Am stuuck in APX mode, just like described above... anyone figured out a solution?
It'd be greatly appreciated
markvanengelen said:
Am stuuck in APX mode, just like described above... anyone figured out a solution?
It'd be greatly appreciated
Click to expand...
Click to collapse
If you just want to get out of apx mode use easyflasher and install custom recovery from it, then restore backups etc
Hi,
Once I had installed native Ubuntu 11.04 on my TF101's EMMC by repartitioning it. Speacially splitting the sdcard partition into 2 (smaller sdcard and 4GB Ubuntu ext4)
I know this is not related to this thread but I need help and I don't know where to start.
I forgot how I did the repartitioning and the tools I had used. Now I want to restore the original partitioning of TF101 and delete Ubuntu partition.
How can I do this ? I don't want to modify any other partition (system, data etc.) just want to build up sdcard partition as original.
mrmrmrmr said:
Hi,
Once I had installed native Ubuntu 11.04 on my TF101's EMMC by repartitioning it. Speacially splitting the sdcard partition into 2 (smaller sdcard and 4GB Ubuntu ext4)
I know this is not related to this thread but I need help and I don't know where to start.
I forgot how I did the repartitioning and the tools I had used. Now I want to restore the original partitioning of TF101 and delete Ubuntu partition.
How can I do this ? I don't want to modify any other partition (system, data etc.) just want to build up sdcard partition as original.
Click to expand...
Click to collapse
Use the program i mentioned a post above yours should work fine.
JoinTheRealms said:
Use the program i mentioned a post above yours should work fine.
Click to expand...
Click to collapse
where can I find easyflasher ?
Hey guys, I'll try to keep it short and get to the parts that really matter, but any help would really be appreciated.
Long story short, wanted to get onto Jellybean with my B60 TF101.
Started with easyflasher since that seemed like the quickest way to get setup. Couldn't get it working because I had not yet installed APX drivers, but not knowing that yet I moved on to 1 Click transformer root. At this point I discovered the APX drivers were not installed and installed the Universal Naked drivers. Still could not get 1 Click transformer root to work and so I returned to easy flasher. Tried to flash recovery to Roach CWM, but did not work. I figured alright, at this point I will just flash to stock to see if working with a clean slate would help. Flashed to stock using easyflasher and the latest firmware off ASUS website, but it failed. I now am only able to get into APX mode and after running easyflasher a number of times hoping it would fix it to no avail I did some searching and found a few similar threads.
This seemed closest to what I was experiencing, but after going through the thread I could not get anything to work. And that's where I am. I ran Brk's ASUS transformer root, installed the drivers from that thinking maybe the ones I had installed weren't the best and ran the stock flashing section and I still end up in the same place. I'm entirely new to this so pardon my ignorance, but any help would be greatly appreciated.
Thanks in advance.
Here's the log from the last run of Brk's Root Toolkit
Code:
C:\Users\User\Desktop\BRK_RootKit_v8.0_final\tmpboot>cd C:\Users\User\Desktop\BR
K_RootKit_v8.0_final\tmpboot\
C:\Users\User\Desktop\BRK_RootKit_v8.0_final\tmpboot>"wheelie.exe" -1 --bct tran
sformer.bct --bl bootloader.bin --odm 0x300d8011
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 1.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x252308537800151895
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
C:\Users\User\Desktop\BRK_RootKit_v8.0_final\tmpboot>"nvflash.exe" -r --bct tran
sformer.bct --setbct --configfile flash.cfg --create --odmdata 0x300d8011 --sync
Nvflash started
[resume mode]
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 GPT please wait.. done!
done!
sending file: blob.EBT
| 983040/1454712 bytes sentdata send failed NvError 0x120002
command failure: create failed (bad data)
C:\Users\User\Desktop\BRK_RootKit_v8.0_final\tmpboot>"nvflash.exe" -r --go
Nvflash started
[resume mode]
At that point what is on the screen is:
Chip UID: Numbers
!!! Phone update succeeded !!!
!!! Phone update failed!!!
EDIT: Problem solved. Switched to USB port on back of computer and ran reflash_sbkv1.bat included with brk's root toolkit and it worked. After that just started up the toolkit and reflashed the firmware from the GUI and i'm back in business. Not sure which part was the important one, but maybe this will help someone else.