Database Info

[Q] G2x, Bricked ? Help please (tried NVflash)

So, I bought a g2x ,Rooted with a flashed rom (not sure which) .
Would have random reboots one day battery died and it never woke up after.
I used to be able to get into cwm (v. 3.0.5 flashed) Now it just hangs at the LG logo and does nothing. I tried calling the guy who sold it to me to get some info of Recoverys and roms he doesn't answer.
1. A custom Recovery was flashed, but don't know which and how it was flashed.
2. A Custom rom was flashed but don't know which.
3. It will connect to my win7 pc and shows up in Device manager. (Battery out, vol up + vol dwn)
4. NVflash finds it, but never succeeds.
5. One-click finds it, but never succeeds.
Ive tried using NVflash, followed the instructions : Battery out, hold down vol up + dwn, plug in usb, run command. It loads Fastboot, then thedownload of the bootloader is sucessfull but just hangs there never send the img file. Then it just gives NV error. One-click does the same no matter what recovery I try to flash, ext or int.
When I was able to get into Recovery I would give error about not eing able to mount cache and such, even when I tried to go back to a stock rom. Now I'm not bale to get into any Recovery, Vol dwn + Pwr. Only LG logo.
What I think I need is to Repair the internal Memory and partitions. From ADB, only problem is I can't turn the phone one to get my pc to recognize and install the adb drivers.
Any help would be great!

NO HELP ?

Hi, I'm pretty new myself to the g2x device. However, I'm able to install recovery and flashed to a different custom ROM before. so I have some experience in this area. When reading your post, I'm not fully understanding what you're saying. Are you able to turn the phone on at all? Or you stuck at the LG logo?
Are the battery able to charge with the phone off? Just to be sure we have to isolate the battery to determine whether it is the problem. Is there anyone around you that have the g2x. The problem I think is that your phone is unable to install the driver into your computer. You need to use someone device to install the NV driver. Once you install the NV driver.
Attempt to turn it on first. If it still won't boot. Then we can try to reflash the Recovery to the 4.02. If you able to do all this and get to the recovery screen, then I think we are set... The goal is to get to the recovery screen.
I hope this help...But anything more technical, we have to wait for others to help..Best of luck

I'm not exactly new either, I've used NVflash at least once before to flash a recovery onto a Streak. I've rooted and Flashed recovery to a few MYtouch4g's.
But this G2X is just proving to be a problem.
To answer some of your questions.
When The phone does power on, it just hangs at the LG screen.
I tested the voltage of the battery with a meter and shows 3.8-3.7 volts of power, and is able to light a tiny light bulb. I also checked the charging port and power is running to the prongs which would touch the battery to charge. I did put the battery into another G2X and it worked. I no longer have access to the other G2X so do further testing.
I was and can still get the PC to recognize the phone via battery out, Vol up + Vol dwn & connect usb wire. PC recognizes beeps and phone shows up in device manager as "Android usb recovery mode" or something simular. So the APX driver is installed
When I try to NVflash (while keeping vol up + vol dwn) CWM 4 or Stock recovery its the same result, Loads bootloader and just hangs until it spits out an NV error (i'll post the result). (S/W Upgrade screen does show up on phone)
I cannot boot into any recovery via holding Vol dwn + Pwr.
Ieven tried the One-click recovery, no go, errors out.
I did find a Zip file with a recovery which is supposed to load the phone the factory supposed to format partitions and load original files. Uses NVflash, its just a bat file which runs the NVflash commands. found here. But this loads some files then when it gets to the formating partition it errors out. i'll post what it does. link > android.modaco.com/content/lg-optimus-2x-2x-modaco-com/335474/25-mar-nvflash-stock-rom-release-v10b-dated-1300166062-15-03-2011/
Code:
C:\Users\Alan\Desktop\recover>.\nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR
-0DM_300MHz_final_emmc_x8.bct --setbct --odmdata 0xC8000 --configfile android_fa
stboot_emmc_full.cfg --create --bl fastboot.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x02804081423f7117
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct
- 4080/4080 bytes sent
E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct sent successfully
odm data: 0xc8000
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBR
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: EB1
creating partition: LNX
creating partition: EB2
creating partition: DRM
creating partition: EB3
creating partition: SOS
creating partition: EB4
creating partition: UDA
creating partition: EB5
creating partition: UDB
Formatting partition 2 BCT please wait.. |
I think what needs to be done is to fix the internal partition I think they got damaged somehow?

Wow, you doing really good. Unfortunately, I think this problem is out of my league. The worst you can do is call T-mobile. Tell them your device is defective and they can send you a new one. But since your phone is rooted, if they found out then we can run into some problem. Most likely they will charge you 99 dollars for damaging the phone. I hope you'll find a way to fix your device because the G2x rock...
PS: I think the previous might have flash a lg optimus 2x Rom, which could explain why the phone is damage...If your phone is in fact a Optimus 2x and we flash the wrong recovery, that could also explain why we can't install the recovery...
android.modaco.com/content/lg-optimus-2x-2x-modaco-com/335474/25-mar-nvflash-stock-rom-release-v10b-dated-1300166062-15-03-2011/

WARNING: This can destory your internalSD card partitions. If it's not broke don't fix it!
ALL COMMANDS ARE IN RED
I am not responsible for any damage you do to your phone.
I did this same thing to my phone... I was still able to get into recovery though. You can repair the internal partitions through ADB if you can still get into recovery.
Steps to recreate partitions.
Boot into recovery
from your PC open cmd prompt
change to your ADB directory
run adb shell
fdisk -H 1 /dev/block/mmcblk0
once in the fdisk of ../mmcblk0 you might as well delete all the partitions if you believe that they are corrupted
d
1
repeat for partition 2-8
one all of your partitions are gone you now have a blank internal SD and will need to execute the following to restore all the proper partition sizes
Partition 1
n
p
1
First Cylinder start 129
First Cylinder stop 55168
We will repeat this for partitions 2 and 3
Partition 2
n
p
2
Start 55169
Stop 63360
Partition 3
n
p
3
Start 63361
Stop 63616
On to partition 4 which will be extended (this is the last partion you will choose primary or extended)
Partition 4
n
e
4
Start 63617
Stop 975424
Now onto partition 4-8 which are automatically selected as logicall partions (no option is given)
Partition 5
n
Start 63681
Stop 64704
Partition 6
n
Start 64769
Stop 65088
Partition 7
n
Start 65153
Stop 261760
Partition 8
n
Start 261825
Stop 975424
Once you have done this the partitions are ready to be written to the internalSD
I would recommend choosing the command p to verify that all of your start and stop blocks are correct.
From this point you have the option to either quit without saving changes or to write the partition table itself. Once you are sure that you have entered all of your partitions correctly you can choose the command w
At this point you have recreated all the partitions on your InternalSD card. If you have a nandroid backup at this point you should be able to restore it without a problem once you copy it over to the internal or external (depending on which CWR you are running).
If I've forgotten any steps please feel free to comment and include them.
Thanks to TeamWhiskey for helping me resolve this issue when I had it...

casper200519 said:
WARNING: This can destory your internalSD card partitions. If it's not broke don't fix it!
ALL COMMANDS ARE IN RED
I am not responsible for any damage you do to your phone.
I did this same thing to my phone... I was still able to get into recovery though. You can repair the internal partitions through ADB if you can still get into recovery.
Steps to recreate partitions.
Boot into recovery
from your PC open cmd prompt
change to your ADB directory
run adb shell
fdisk -h 1 /dev/block/mmcblk0
once in the fdisk of ../mmcblk0 you might as well delete all the partitions if you believe that they are corrupted
d
1
repeat for partition 2-8
one all of your partitions are gone you now have a blank internal SD and will need to execute the following to restore all the proper partition sizes
Partition 1
n
p
1
First Cylinder start 129
First Cylinder stop 55168
We will repeat this for partitions 2 and 3
Partition 2
n
p
2
Start 55169
Stop 63360
Partition 3
n
p
3
Start 63361
Stop 63616
On to partition 4 which will be extended (this is the last partion you will choose primary or extended)
Partition 4
n
e
4
Start 63617
Stop 975424
Now onto partition 4-8 which are automatically selected as logicall partions (no option is given)
Partition 5
n
Start 63681
Stop 64704
Partition 6
n
Start 64769
Stop 65088
Partition 7
n
Start 65153
Stop 261760
Partition 8
n
Start 261825
Stop 975424
Once you have done this the partitions are ready to be written to the internalSD
I would recommend choosing the command p to verify that all of your start and stop blocks are correct.
From this point you have the option to either quit without saving changes or to write the partition table itself. Once you are sure that you have entered all of your partitions correctly you can choose the command w
At this point you have recreated all the partitions on your InternalSD card. If you have a nandroid backup at this point you should be able to restore it without a problem once you copy it over to the internal or external (depending on which CWR you are running).
If I've forgotten any steps please feel free to comment and include them.
Thanks to TeamWhiskey for helping me resolve this issue when I had it...
Click to expand...
Click to collapse
Can you help me with a video easier to work !!!!!!!! hopefully my phone will return to stock

I love you. Thanks for putting up the instructions.

chulun9999 said:
Can you help me with a video easier to work !!!!!!!! hopefully my phone will return to stock
Click to expand...
Click to collapse
I will try to get some video on it when I get time... If you get stuck on any of the instructions just ask and I'll check back often to try to help

casper200519 said:
I will try to get some video on it when I get time... If you get stuck on any of the instructions just ask and I'll check back often to try to help
Click to expand...
Click to collapse
you can guide me. I really do not understand to be able to work with it. I do not know where to start
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 14 NvError 0x120000
command failure: partition download failed

chulun9999 said:
you can guide me. I really do not understand to be able to work with it. I do not know where to start
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 14 NvError 0x120000
command failure: partition download failed
Click to expand...
Click to collapse
The how-to that I wrote is on recreating the partitions... I understand your error is with allowing nvflash to create them. Are you still trying to put an O2x image on a G2x?

casper200519 said:
The how-to that I wrote is on recreating the partitions... I understand your error is with allowing nvflash to create them. Are you still trying to put an O2x image on a G2x?
Click to expand...
Click to collapse
yes . i try to put an O2x image on a G2x . and now it happen this status . how do i repair my mistake .please help me

I am experiencing the same issue. Any luck resolving this????
I have CWM as my recovery system... So I cannot use ADB -- it won't connect.
Any ideas???

crosses fingers and prays
hope someone figures this out soon, i have been in many weird spots but none more than this g2x, it always worked fine and one day after reinstalling the cm7 nightly it never booted, just the LG boot screen and no more! windows even recognizes the phone but as fastboot only, NV flash says it worked but i never get further than LG screen, CLK Recovery wont pop up! hope someone solves this cus i love this phone!!

tylermauthe said:
I am experiencing the same issue. Any luck resolving this????
I have CWM as my recovery system... So I cannot use ADB -- it won't connect.
Any ideas???
Click to expand...
Click to collapse
ADB works in cwr recovery.if you find my other post labeled [REF]Repair internal SD in the dev area it has some q&a from others
Sent from my LG-P999 using XDA Premium App

Sorry for reviving this post!
This has been so helpful!
My phone was not able to boot in normal mode, but only in CWM! Thanks KAsp3rd!

need help with lg p999
hey am new here but am having the same problem and i need som help because i accedentaly used usde an nvflash tool for a lg p990 on my lg p999 and now am having problems with my baseband, sim,audio and my ime # is gone but the phone works but those are the problems that am having. so if any 1 help please assist

[Q] nvflash doubts

I think I already understood the idea with the Secure Key and bootloader, but I still do not completely understand the remaining options:
Is the --configfile the partition table of the device? Can I download it using --getpartitiontable ?
What is --odmdata for? Where did people get the 0x300d8011 value from?
Can I use the --getbct command to download the BCT from my own Transformer or do I need to use the one being distributed in these forums?
If there is an online guide, please direct me to it
Thanks in advance to everyone.

I'm not an expert by any stretch of the imagination, so if you brick your TF, you've been warned...
The --configfile option is used with the --create or --format_all options and species how the memory is partitioned and formatted. It specifies size, attributes, and file system types.
The partition table from --getpartitiontable is mostly sizes, so you wouldn't be able to reverse engineer the config file from just the partition table, although the reading the partitions would probably tell you the rest of the options.
I think the BCT specifies, among other things, hardware configurations such as 16GB vs 32GB. These are specific and you have to get it right.
This is from something I dug up from the Notion Ink
An output BCT file is the header structure stored on the secondary boot device
i.e.nand/emmc/spi-flash, which primarily stores information:
- required to initialise and configure secondary boot device
- required to initialise and configure SDRAM
- required to locate and verify boot loader
ans other non-volatile information that is shared across boot loader and OS
Click to expand...
Click to collapse
I'm not sure if you can write the BCT without erasing everything first. I thought it was encrypted and tied to the bootloader??

gee one said:
I'm not an expert by any stretch of the imagination, so if you brick your TF, you've been warned...
The --configfile option is used with the --create or --format_all options and species how the memory is partitioned and formatted. It specifies size, attributes, and file system types.
The partition table from --getpartitiontable is mostly sizes, so you wouldn't be able to reverse engineer the config file from just the partition table, although the reading the partitions would probably tell you the rest of the options.
I think the BCT specifies, among other things, hardware configurations such as 16GB vs 32GB. These are specific and you have to get it right.
This is from something I dug up from the Notion Ink
I'm not sure if you can write the BCT without erasing everything first. I thought it was encrypted and tied to the bootloader??
Click to expand...
Click to collapse
The thing is: from what I understood, to use --getpartitiontable you need to use the --bct, which receives a .bct file as an argument. And if this file contains device specific information, then I really should use one that is for my own Transformer. And this is exactly why I tried to use --getbct, but the command is failing. Have you seen any example of its usage? Do you know where people have obtained the .bct they are distributing in the scripts?
Thanks

I've seen a buildbct executable for the Notion Ink that takes a specification file and spits out a bct.
I don't think the bct is specific to each device, just each type of device, and it might be pretty generic at that. It's stuff like ram speed and type. If you have a 32GB version, it might not work, but I don't think it would hurt to try. I've used the getpartitiontable command with the bct file that is floating around with nvflash. It seems to work.
I tried to read the bct from the TF and got an error.

I don't seem to be able to find the buildbct executable anywhere :/ And I also get an error while trying to use --getbct, so I guess that is not the way to go.
Since I'm rather curious about this, I'll try to ask the question in the Dev forums. Someone there will know where the file came from, no?
BTW, do you know anything about the --odmdata argument?

vhda said:
I don't seem to be able to find the buildbct executable anywhere :/ And I also get an error while trying to use --getbct, so I guess that is not the way to go.
Since I'm rather curious about this, I'll try to ask the question in the Dev forums. Someone there will know where the file came from, no?
BTW, do you know anything about the --odmdata argument?
Click to expand...
Click to collapse
No, go fish!
Supposedly this worked on a Gtab, so what could it hurt?
./nvflash --bl bootloader.bin --getbct --bct jl-bct.bct --go
http://forum.xda-developers.com/showthread.php?t=934023
The BCT partition is pretty large, but if you poke around with a hex editor (bad hacker!), it's the same 4080 bytes repeated over and over.
EDIT: some insight into the odmdata. last post- http://forum.xda-developers.com/showthread.php?t=1039547

The thread in [1] seems to agree with you. According to it the BCT partition is written from the .bct file, as long as the --create option is used. If this is true, then running the commands below (still did NOT test it) should allow backing up the original BCT:
./nvflash --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --odmdata 0x300d8011 --bl bootloader.bin --bct transformer.bct --setbct --go
./nvflash -r --getbct -bct backup.bct
[1] http://forum.xda-developers.com/showthread.php?t=1010659

[HELP-THREAD] The Ask-Doom thread! (Need help? New? Ask here!) -Give help too!-

Welcome to the general HELP thread I've made.
The idea was given to me, and the TF doesn't have one, so here it is!
I'll be checking this often and appreciate if others do too, and try to help with problems people have.
I notice many of the same questions have been asked constantly, so I want to try and consolidate questions and answers into one searchable thread in Q&A, also to ask in.
DON'T USE ROM MANAGER ON THE TF101, EVER! It causes bootloops!
Go ahead and ask here!
Abuse towards new users isn't tolerated, but neither are very silly questions either.
Please Search before posting though! Seriously, you find lots of answers and cool stuff!
--
ToD

Thing O Doom said:
Welcome to the general HELP thread I've made.
The idea was given to me, and the TF doesn't have one, so here it is!
I'll be checking this often and appreciate if others do too, and try to help with problems people have.
I notice many of the same questions have been asked constantly, so I want to try and consolidate questions and answers into one searchable thread in Q&A, also to ask in.
DON'T USE ROM MANAGER ON THE TF101, EVER! It causes bootloops!
Go ahead and ask here!
Abuse towards new users isn't tolerated, but neither are very silly questions either.
Please Search before posting though! Seriously, you find lots of answers and cool stuff!
--
ToD
Click to expand...
Click to collapse
I just got my transformer upgraded to .24 and rooted with your PERI tool. I have to say it was the easiest root I've performed on any of my Android devices thus far! Thank you for being an awesome resource to the AT community!
Sent from my SPH-D710 using Tapatalk 2

Your opinion on the most stable kernel to OC/UC for a TF noob?
Sent from my SPH-D710 using Tapatalk 2

Definitly Guevor's kernel.
Can find it here: Guevor ICS Test v21.4 (The latest is 21.10 though available towards the end of the thread as an attachment.)
Make sure to use the AOKP version if you're on aokp, megatron on megatron and normal for stock/arhd/revolver roms.

Hello everyone. I'm new. I want to know why my Pad won't boot into CWM using the Volume Down/Power button method. I have to run the rooting tool again to do that.
I don't know if this is normal or not, because my Samsung boots into CWM easily.

Can you get into stock recovery (android with red !) Or just nothing?
If it's nothing at all, you're doing the button combo wrong,
make sure to hold vol-down before pressing power, then release both when it says 'checking for rck...' then press vol-up immediately when it says that.

Hello!
I'm new here so please be patient with me
I want to ROOT my Asus TF101 for the first time. Version .24.
I don't know so much about the technical stuff, but I can learn (I'm still young ).
My question is if the EazyFlasher tool can be ONLY for root and nothing else? All I want is a root to back-up my data.
by following the steps 1 by 1, will I success rooting my tablet? Or there's something that is obvious for advances and that's why it's not written?
I know my questions are silly for you guys, but I'm scared to do something wrong...
Thank you!

You can use the PERI tool I made (in my signature) to easily get root. Just plug in your tf, run the .bat file, and you should have root in about 15 mins pretty easily.

It boots into stock recovery just fine, just not into CWM even after I installed it.
Sent from my Transformer TF101 using XDA

is adb working? any errors thrown? drivers installed? just a bit more info please

Great effort you're doing
What a noble effort and good cause. I'll chime in when I can help out and ask questions when I need to. I know some people find it easier to tell someone who needs help to 'just Google' or 'can't you read' type responses, but that isn't helpful to someone who's gotten a little lost or confused or just doesn't know the right answer yet. There are ways to gently guide new folks to the proper ways to seek out what they need without being rude about it. Good luck with this and keep up the good work.

In a perfect world - our transformers will grant wishes. They don't though... so this is here x3

TF101 / B90 cant boot beyond ASUS screen
as the title says my transformer stuck at the ASUS screen when booting up and isnt getting any further, stock recovery gives me the dead droid with the red warning.
I tried NVFLASH/Wheelie to flash different stock ROMs 1.11, 1.21, 1.24 .. With the same outcome .. cold booting tens of times, nothing happens
I used EasyFlasher to install the Rogue XM Touch Recovery, and tried to install the stock ROM zip file from my SD card ( i cant read internal memory), But wont it install it (i get STATUS 7 error)
I been working on it for more than a week, and I am about to lose all hope

Are you sure you're using NvFlash properly, and do you have ADB access to the device? Usually Nvflash and ADB not working is a driver issue. Please post a screen of what wheelie does when you try to Nvflash your B90 (use the Sbkv2 bat)

I believe i use NVFlash right (but i cant use ADB, it never finds the tablet) .. this is what i am getting
Code:
D:\My Folders\Desktop\wheelie>"wheelie.exe" -2 --bct transformer.bct --bl bootl
oader.bin --odm 0x300d8011
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x299506994287477335
[=] 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
D:\My Folders\Desktop\wheelie>"nvflash.exe" -r --bct transformer.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
| 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
/ 536870912/536870912 bytes sent
blob.APP sent successfully
D:\My Folders\Desktop\wheelie>"nvflash.exe" -r --go
Nvflash started
[resume mode]

sidneyk said:
What a noble effort and good cause. I'll chime in when I can help out and ask questions when I need to. I know some people find it easier to tell someone who needs help to 'just Google' or 'can't you read' type responses, but that isn't helpful to someone who's gotten a little lost or confused or just doesn't know the right answer yet. There are ways to gently guide new folks to the proper ways to seek out what they need without being rude about it. Good luck with this and keep up the good work.
Click to expand...
Click to collapse
I agree with this 100%. I will browse this thread as well and help out when i can.
I'm running stock ROM and Kernel, rooted and NO random reboots or SODs. Think this is a coincidence? Here to tell you it isn't. If you need help, ask and if I know, I'm all yours.

It looks like Wheelie worked fine, you can't get ADB to detect at all? Try running Wheelie in a Linux virtual box (Puppy/Damnsmalllinux work fine and are very small downloads)

I just cant!! its like the 5 time i did it and i cant!!!
i follow the steps and the tf restart 2 times, and all that stuff
but when i try to go into recovery
it just doesnt go!!
i dont know what to do!!!! :'( ill cry

Which tool are you talking about and what are you trying to do?

Thing O Doom said:
is adb working? any errors thrown? drivers installed? just a bit more info please
Click to expand...
Click to collapse
I'm sure the drivers are installed because I rooted it with my computer. But just to make sure, how do I check?

[Q] New info (in OP bold txt), can you answer? - Power on/Reboot goes into APX mode

Sorry, other post is a bit hard to read, was trying to see if upgrading my TF300t (unlocked, rooted, nvflash run) to v9.4.3.30 would fix it - which unfortunately didn't.
I'm having issues resolving powering up and reboots automatically going into APX mode. Plus lost my icons (fastboot, wipe, ? ) when powering up w/vol down
button. Only have choice of Recovery or let it cold-boot into ICS. The original help post for added details is at:
Original post with more details
I'm thinking the AndroidRoot booloader I've been running from when I originally created my nvflash backups got corrupted. The update (via Install Zip in TWRP) does
not seem to have updated the bootloader. In reading even more posts, another user shows:
The Device is UnLocked
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.3.30-20120604" A03
Checking for android ota recovery
I see the exact same except my version is "WW_epad-9.4.3.30-20120604", which makes me think the bootloader isn't getting updated correctly & is still the original AndroidRoot
version which became corrupted? I also double checked the new EBT blob I'm flashing via a hex editor and it shows it has a US SKU! So does that mean nvflash isn't truly
flashing it? If not, how can I get it to take either with nvflash, ADB, or TWRP?
Also can see (lack of) progress below *sigh*

wha2do said:
Sorry, other post is a bit hard to read, was trying to see if upgrading to v9.4.3.30 would fix it - which unfortunately it didn't.
I'm having issues resolving powering up and reboots automatically going into APX mode. Plus lost my icons (fastboot, wipe, ? ) when powering up w/vol down
button. Only have choice of Recovery or let it cold-boot into ICS. The original help post is at:
Original post with more details
See (lack of) progress below.
Click to expand...
Click to collapse
Well, still need some suggestions/help. I've run:
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
nvflash -r --download 5 twrp2.5.0.0.img
Didn't do anything to fix the APX issue nor get my fastboot icon back. I'm wondering if I should try using
the bricksafe.img file I'd created before - not sure what exactly it contains and if it would be any different.
At this point I'm days away from seeing if I can return the tablet (under a 2 year warranty plan - thought it
was said if they can't fix, get my money back rather than a replacement) and look at something else.
I've read and read and not found anything useful yet and not much on the nvflash backup file use for restoring...
Help!

You could try erasing the misc partition.
I think this this is the right command, but you might have to check the exact command syntax (don't have nvflash handy right now):
nvflash -r --format_partition 3
Sent from my TF300T using Tapatalk

f69m said:
You could try erasing the misc partition.
I think this this is the right command, but you might have to check the exact command syntax (don't have nvflash handy right now):
nvflash -r --format_partition 3
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
Thx & that's the correct syntax, but what is nvflash's partition 3 (misc)? And is this nvflash PartitionId 3 or adb's mount point /dev/block/mmcblk0p3? In
nvflash's partition table list, MSC (assuming this is the same "misc" partition) is listed as PartitionId 12...
When I do a list of partition tables from nvflash, it shows this as type Partition_table and named PT. I did install the Partition Table app
and see where 3 may be coming from, as in the mount point /mmcblk0p3, labelled as MSC?
Looking at other known nvflash/Partition table comparisons, one nvflashes blob.APP (system) to partition 10 yet the Partition Table app
shows /system, labelled as APP mounted on /mmcblk0p1. And with blob.SOS, nvflash sends it to 5 yet the adb command uses /mmcblk0p4...
I maybe interpreting these all wrong and it's ok - just being very cautious about formatting a partition and what effect it will have... Thanks in advance for clarification!

wha2do said:
Thx & that's the correct syntax, but what is nvflash's partition 3 (misc)? And is this nvflash partition 3 or adb's mount point /dev/block/mmcblk0p3?
When I do a list of partition tables from nvflash, it shows this as type Partition_table and named PT. I did install the Partition Table app
and see where 3 may be coming from, as in the mount point /mmcblk0p3, labelled as MSC?
Looking at other known nvflash/Partition table comparisons, one nvflashes blob.APP (system) to partition 10 yet the Partition Table app
shows /system, labelled as APP mounted on /mmcblk0p1. And with blob.SOS, nvflash sends it to 5 yet the adb command uses /mmcblk0p4...
I maybe interpreting these all wrong and it's ok - just being very cautious about formatting a partition and what effect it will have... Thanks in advance for clarification!
Click to expand...
Click to collapse
Sorry, my bad, haven't really used nvflash much. Just assumed it would be the same numbers. :/
Yes, I mean the MSC or misc partition /dev/block/mmcblk0p3.
It holds commands for the bootloader, for eaxample "recovery", etc. Cleaning it might make your bootloader behave. Might.
Sent from my TF300T using Tapatalk

f69m said:
Sorry, my bad, haven't really used nvflash much. Just assumed it would be the same numbers. :/
Yes, I mean the MSC or misc partition /dev/block/mmcblk0p3.
It holds commands for the bootloader, for eaxample "recovery", etc. Cleaning it might make your bootloader behave. Might.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
No problem at all, I appreciate the help and I just always try to be cautious! Just to be doubly sure, here's the excerpt from
getting the partition table info from nvflash earlier today:
PartitionId=12
Name=MSC
DeviceId=18
StartSector=317568
NumSectors=512
BytesPerSector=4096
So doing the nvflash -r --format_partition 12 command should be safe. Wondering, does it make sense to do this first:
nvflash --resume --rawdeviceread 317568 512 msc.img
Should back up what's there if need it afterwards...again being safe, lol!

wha2do said:
No problem at all, I appreciate the help and I just always try to be cautious! Just to be doubly sure, here's the excerpt from
getting the partition table info from nvflash earlier today:
PartitionId=12
Name=MSC
DeviceId=18
StartSector=317568
NumSectors=512
BytesPerSector=4096
So doing the nvflash -r --format_partition 12 command should be safe. Wondering, does it make sense to do this first:
nvflash --resume --rawdeviceread 317568 512 msc.img
Should back up what's there if need it afterwards...again being safe, lol!
Click to expand...
Click to collapse
Yes, this looks like the right one. Unfortunately /proc/partitions does not give a start sector, but the name MSC matches. /proc/partitions gives the size at 2048, but that should be 1K blocks, so maching the 512 4K-blocks shown by nvflash.
Yeah, should be save to erase, but being careful and having a backup never hurts. Might even be interesting to have a glance at the contents.
Sent from my TF300T using Tapatalk

Well, I think if indeed the bootloader is corrupted I've found my flashes of a new one aren't taking. I tried nvflashing blob.EBT, blob.SOS, blob.LNX, and then blob.APP from the stock v9.4.3.30
update (all in same nvflash session) and all listed as successful. The rest did take...but wasn't sure about blob.EBT. I expected to see the US_epad version (and I've checked the blobs
with a hex editor and they indeed have the US SKU).
I ended up sideloading v9.4.3.17 in TWRP and saw the bootloader version stayed the same (WW_epad-v9.4.3.30). With a stock recovery back in place, I tried to see if I could take an OTA
back to v9.4.3.30, but said no updates were available. Ended up sideloading v9.4.3.30 and am back to where I was...
I also let the tablet battery run down completely, charged fully over night hoping something might "reset", but no go...
Last thing I'll be trying later is a factory reset via TWRP (read try doing it three times to be sure) and reload v9.4.3.30. If not, looks like I have two options: 1) try the reformat of the MSC partition
and/or do an nvflash rawdevicewrite of the bricksafe.img file. Just worried with both that it'll create more issues (being very careful since at least I can still get into APX, ADB, and ultimately boot up).
Any recommendations/suggestions on how to get blob.EBT to flash successfully or which step to try next? Please, please, please...lol!

I tried doing a factory reset. Probably overkill, but also wiped cache, Dalvik, and data while in TWRP. Then booted up, skipped set up, and did this two more times. Didn't have any effect,
so I tried sideloading v9.4.3.30 and same old story...
I finally quit and restored my nandroid made prior to the factory resets and now have to decide:
Try the format of the MSC partition or nvflash bricksafe.img. Again just being very cautious since while tedious, I can still use my tablet by restarting via nvflash.
Wish I could get advice from one of the AndroidRoot members!!
Any ideas/recommendations at this point?

[Q] complete reformat and start over

After several ROM installs and getting to bricking, I ended up with folders with names like "0" and "obb". Is there a way to reformat the internal storage and get back the beginning? Currently using KATKISS.
I wanted to put Ubuntu on but "failed" in TRWP when installing the zip.

aknisley said:
After several ROM installs and getting to bricking, I ended up with folders with names like "0" and "obb". Is there a way to reformat the internal storage and get back the beginning? Currently using KATKISS.
I wanted to put Ubuntu on but "failed" in TRWP when installing the zip.
Click to expand...
Click to collapse
0 is for internal storage
Obb is app data folder
we can format 0
but I will only delete data of apps
install different ROM.
press thanks if I helped you.

aknisley said:
After several ROM installs and getting to bricking, I ended up with folders with names like "0" and "obb". Is there a way to reformat the internal storage and get back the beginning? Currently using KATKISS.
I wanted to put Ubuntu on but "failed" in TRWP when installing the zip.
Click to expand...
Click to collapse
why not just return to stock and begin again.
follow this: http://www.transformerforums.com/forum/asus-transformer-tf101-development/31919-frederuco-s-guide-flash-tf101-back-stock.html

barkeater said:
why not just return to stock and begin again.
follow this: http://www.transformerforums.com/forum/asus-transformer-tf101-development/31919-frederuco-s-guide-flash-tf101-back-stock.html
Click to expand...
Click to collapse
Well, I cannot, because I cannot flash TWRP. TO follow the recipe, It calls for TWRP and all I have is CWM. Try as I might, I cannot install TWRP. I tried via ZIP and also from blob. Nothing. As I write this, I am trying to go back to stock via CWM. It is taking a while, so it may work. As of now, I have been able to re-flash CM10_Nightly, but when I try ano other ROM, it boot loops. I may have really hosed it, now, though. We shall see. I am not averse to NVFlashing it , but have not yet found instructions to do that under Linux. I do not have a Windows computer and most of them call for it.

In case it saves someone else's bacon, I thought I'd post my findings.
I rebooted into windows and tried the 'one click transformer root' tool. It runs and then tells me that it cannot deal with my tablet as it is not running ICS. I tried another one called which is supposed to return to stock called EasyFlasher 0.83. It acted like it installed the stock image, but did not do anything. It would always reboot to CWM.
In CWM., I could wipe and flash an image, but it would never boot. Just bootloop. I had CM10 on the tablet and am guessing that the install was not quite kosher. I could not install any other recovery image, either.
To solve it, I downloaded the blob tools
Blob Tools
I already had wheelie since I used the CM page to install it
CM10 install
I unpacked the image by first unzipping the zip from asus. IN it was a file called 'blob'. I then unpacked it:
Code:
./blobunpack latest/blob
it created 4 files called blob.APP, blob.EBT, blob.LNX and blob.SOS
We want the blob.SOS file. I put it in the wheelie directory and modified the commands I used to initially install the CWM recovery:
Code:
# ./wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
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: 0x370018042607097
[=] 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
# ./nvflash -r --download 5 blob.SOS
Nvflash started
[resume mode]
sending file: blob.SOS
\ 4284416/4284416 bytes sent
blob.SOS sent successfully
# ./nvflash -r --go
Nvflash started
[resume mode]
My zip file was in the root of the SD card, so it immediately reflashed itself after it rebooted. Finally!

congrats!
Yeah, I have no experience with cwm or any other os other than Windows. Glad you got it sorted. Happy Holidays!

barkeater said:
congrats!
Yeah, I have no experience with cwm or any other os other than Windows. Glad you got it sorted. Happy Holidays!
Click to expand...
Click to collapse
Like I said, though, I could not get it to do anything in Windows or Linux. I think it was a permissions problem or a directory structure which was incorrect. Regardless, this worked and i was able to root it using one click root. I was unable to flash the twrp recovery by the preferred method and had to first 'fix sdcard write permissions' from the twrp app. Then the app would not flash it. So i used dd via adb and got it. I have flashed katkiss and am trying it out. I feel as though i have been released from cwm/cm10 hell, finally.