Database Info

[Q] Getting Open Etna on the LG GW620 on a Mac

Hello everybody,
I know, there is a GIANT Thread on this but even with the search I cannot find my Error-signs etc. so I have to open another one.
To begin I should say, that I am workin' on a Mac, but I got all the utilities, that I need. (I think) To sum up:
The latest SDK, including fastboot and the upgrades,
the System.img and
boot.img from the Openetna-site.
And I got the V10H_00.kdz and I this would be it
Now to my problem: I tried to update my phone like in the tutorials on the Openetna-site: openetna.com/openetna/about/
I never had a Problem to get into the Fastbootmode, it shows the usual stuff. The only strange thing is that the serialnumber is "UNKNOWN"
The first -w Step to delete the data is no problem and is displayed on the phone but then everything I try is unsuccesful:
flashall results to: neither -p product specified nor ANDROID_PRODUCT_OUT set
devices: ???????????? Fastboot
I think that these are my mainproblems but some further information.
When I try to do as in the tutorial, like I did the first time of many many many times (fastboot flash boot boot.img & fastboot flash system system.img [yes they are in the same directory with those exact names] fastboot just shows me: error: cannot load 'boot.img' and error: cannot load 'system.img'
And sometimes in between, even when I tried it on my roommates PC I get "Waiting for device" I think this comes with every other command than those I just described...
great, don't you think? Do you have any ideas, that could help? My Phone doenst work any more, and I really need it... It appeared so easy in the lots of videos... But it wasn't...
Please Help
Thanks a lot,
Julien

Something stupid...
Hey Guys and Gals again...
Isn't it ironic, that the minute after I posted this Thread I realize how stupid I was? I symply forgot to "cd" my terminal. Here is how it should look like...
Julien-Blues-MacBook:~ julienbluehirte$ /Users/julienbluehirte/Desktop/SDK/tools/fastboot flash boot /Users/julienbluehirte/Desktop/SDK/tools/boot.img
sending 'boot' (2754 KB)... OKAY
writing 'boot'... OKAY
Julien-Blues-MacBook:~ julienbluehirte$ /Users/julienbluehirte/Desktop/SDK/tools/fastboot flash system /Users/julienbluehirte/Desktop/SDK/tools/system.img
sending 'system' (98929 KB)... OKAY
writing 'system'... OKAY
Julien-Blues-MacBook:~ julienbluehirte$
STUUUUUUUUPID AND SILLY ME...
I'm sorry to maybe have stolen your time, Have a nice day
Julien

[GUIDE] How to get CWM back after flashed the ICS OTA

It seems that many guys don't know what to do after flashing official ICS OTA and finding no CWM.
The OTA contains its stock recovery,and ever more,there is a script (/etc/install-recovery.sh) checking and rewriting the recovery on every normal boot.
So to get CWM back and revert to gingerbread, we can use fastboot.
Requirement:
Working SDK with fastboot, adb is optional.
1) Poweroff your phone
2) Boot into bootloader(fastboot) by pressing vol down and power
3) Plug the cable in and open your terminal.
4) Download CWM img from the following URL.
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-crespo.img
5) In your terminal type the following command.
fastboot flash recovery <Path of the recovery you downloaded in 4)>
Things should goes like this:
D:\android-sdk-windows\tools>fastboot.exe flash recovery recovery-clockwork-5.0.
1.0-crespo.img
sending 'recovery' (4116 KB)...
OKAY [ 0.520s]
writing 'recovery'...
OKAY [ 0.558s]
finished. total time: 1.078s
6) DO NOT REBOOT! Boot into recovery DIRECTLY!!!
7) Now CWM is back,and the evil official OTA can't stop you from reverting to gingerbread now.
8) Optional : If you really like the ICS OTA even it can't be rooted yet, CWM is still very important,right? So you need to delete some evil scipt.
In CWM ,you can use adb to delete the script which checks and rewrites recovery every normal boot.
You can mount /system in CWM ,and use the following command to delete it.
adb shell
rm /system/etc/install-recovery.sh
PS: Sorry for my poor English.

Thanks - just what i was looking for.
Is there a way of getting root back? i have super user on my phone but for some reason it wont root

I've tried it this way.
But in bootloader, fastboot can't find the device.
Any advice?
When my rom is booted it's listed at adb devices

I just flashed the ics stock rom. I tried several guides but it's not ****ing working, how the hell can a total noob get back cwm, so that i can flash back to my old rom?
Would be amazing if anybody can tell me! especially in german, since that would be the easiest way!

Stothex said:
I just flashed the ics stock rom. I tried several guides but it's not ****ing working, how the hell can a total noob get back cwm, so that i can flash back to my old rom?
Would be amazing if anybody can tell me! especially in german, since that would be the easiest way!
Click to expand...
Click to collapse
First download this : http://www.4shared.com/zip/XG506hyV/icsroot-fastboot-recovey.html
Just unpack it , conected your device at the PC and click run.bat.....
After that you need : remove install-recovery.sh just in .....
run in windows-> Start->at the search bar write cmd and navigate into your android sdk is installed
For me :
C:/"Programs and Files (x86)"/Android/android-sdk/tools/>adb shell
# rm /system/etc/install-recovery.sh
#exit
or with Root Explorer into system/etc/install-recovery.sh just renam it (ex. : .sh.old)

Did work for me. Those new driver Files made it.
Didn't need to delete install-recovery.sh ... it's somehow allready gone.

[Q][Kernel][i9023] Help : flashing kernel killed my phone

Hello everybody,
Before telling you about my issue, i should mention that i am a complete newbie regarding flashing kernels. This was my first try, and it didn't work out too well.
I needed to test the USB OTG/Host Functionality for a project at work, and i read that it was possible to enable it on the Nexus S by flashing a custom kernel (kernel_usbhost_build5_icsnexuss from sztupy). It's probably worth mentioning that prior to this i updated the phone to Android 4.0.3.
So i started this morning by rooting it, unlocking the bootloader and installing CWM.
At that point i realized that the recovery mode wasn't accessible : the graphics of the droid with an open belly appears for half a second, and then it gives me the black screen treatment for about a minute before rebooting.
However since there are other ways to flash kernels, i figured i could do without recovery so i didn't look more into it.
I then flashed the kernel using fastboot with this command :
Code:
C:\Program Files\Android\android-sdk\tools>fastboot flash:raw boot H:\data\Downloads\kernel_usbhost_build5_icsnexuss\kernel\zImage
creating boot image...
creating boot image - 3446784 bytes
sending 'boot' (3366 KB)...
OKAY [ 0.422s]
writing 'boot'...
OKAY [ 0.500s]
finished. total time: 0.922s
From the trace i figured that all went well, but when i reboot it stays blocked on the splash screen with the Google logo. Since then i tried flashing several other kernels, without any success. Also tried to flash an update.zip (both ICS and GB) over fastboot but i get this error :
Code:
C:\Program Files\Android\android-sdk\tools>fastboot update H:\data\Downloads\upd
ate.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
So to sum it up i now only have access to the bootloader, without recovery mode.
Before you all jump on me, i know what i did is bad habits (i should have tested the kernel before flashing it), i did it in a hurry without checking i had all sufficient knowledge, and to be honest i would probably have been more careful if was doing it on my personal device.
Truth is now i'm really desperate because i turned my company issued phone into a brick and don't have the slightest idea what to do about it...
Is there any guru out there who knows how i could get out of this ?
Thanks a lot !

Download clockworkmod recovery and use fastboot to flash it.
Fastboot flash recovery yourfilename.img
Enter recovery and mounts and storage and mount USB storage
Transfer the kernel you want to your SD card. The one you flashes isn't a kernel I'm almost sure.
Try a different one.
Then transfer a rom to your SD card.
Factory reset/full wipe, then go to mounts and storage and format everything except your sdcard.
DO NOT FORMAT YOUR SD CARD!!!
Once that is done go to install zip from sdcard and flash the rom and then the kernel and reboot. Should be fine then. Keep me posted.

..

Election Day said:
The image you need would be this ClockworkMod img. Save it somewhere, cd to the sdk/platform-tools/ directory and then do:
Code:
fastboot flash recovery /path/to/saved/file/recovery-clockwork-5.0.2.0-crespo.img
Just drag and drop the file in your terminal, after typing the space after "recovery".
Furthermore, what nodstuff said.
Click to expand...
Click to collapse
Ha ha oops! Forgot that part!
I usually just cd to the one where I have recovery saved!

..

Thanks a lot for answering so quickly !
I'll give it a try on Monday, let you know how it goes.

Election Day said:
Yes, you can also do that, of course. In that case you'd have to provide the full path for fastboot. Or maybe you don't have to on Windows? I don't really use that operating system to be honest.
In that case it would be something like:
Code:
C:\Program Files\Android\android-sdk\tools\fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
Looking at OP's quotes that is probably the most logical way in this case, you're right.
Click to expand...
Click to collapse
No I just cd to downloads (where recovery file would be) in terminal, type: fastboot flash recovery xxxxxx img
And that's it.
I set the path to fast boot and adb in environmental variables in device manager.
Maybe that's why.

..

Just tried out your tips, worked like a charm !
However I had to wipe everything twice before it would let me update to 4.0.3, I would get this weird error :
file_getprop: failed to stat "/system/build.prop": No such file or directory
Anyway now I'm back on ICS and, following your advice, i found another kernel to flash : Matr1x. No problem with this one, now I can test USB OTG.
Thanks again, you guys rule !

[TOOL] Moto X FXZ Flashing Script (100% back to stock) [10/03/2013]

Hello fellow moto x owners!
Downgrade fail notice!
Just a notice, I tried downgrading after the AT&T camera update, and my flash failed because the bootloader did not allow the downgrade. See this post for more details!
My build number is still the updated version: 13.0Q2.X-116-X-17-54
The original version is: 13.9.0Q2.X-116-X-17-51
Introduction
I didn't make the goals in my previous OP revisions this clear, but let me lay this out to keep the trolls away.
First off, I am making a python fastboot frontend library. So that you can more easily control fastboot with a python script.
Normally, I hack on kernels, but with the bootloader on my phone still locked, I wanted to contribute something to the community.
Second, I'm creating a suite of tools called 'moto-x-tools'; hence the github repository name. The first tool I've made is the only useful one (sorry, doing stuff takes time and testing...).
The first one I created is a small python tool to allow you to flash back to stock on any platform with the FXZ's supplied by Skrilax_CZ. NOTE: The script currently doesn't check if you are flashing a different version of an FXZ image's bootloader as what you have installed on your device. I plan on fixing this soon!
So, you cannot Downgrade your device with this tool. You can only go back to stock with the version of the bootloaders that you have installed. This is only a limitation on LOCKED BOOTLOADERS. So for now, it's a big deal, but soon, you won't have to worry about that crap. Shuve on.
Expect more useful tools to come soon!
Current State
I have tested this script on Mac OS X 10.8.5 and Ubuntu Linux 13.04 Raring Ringtail.
For now, DO NOT USE THIS ON WINDOWS!
I kept getting:
Code:
(bootloader) Preflash validation failed
FAILED (remote failure)
This might be a driver issue, but I'll have to figure this out later. Anyone got more info on this error?
In v0.2.0 I have reworked the package so that it is a proper PyPI package. For each release I flash my AT&T xt1058 (16G) back to 100% stock on my Mac OS X 10.8.5 and Ubuntu Linux 13.04 Raring Ringtail before I tag the release and push changes to GitHub.
Requirements
Mac OS X
On Mac OS X you need to install the Motorola Device Manager.
Linux
On Linux, you will need to setup u-dev to set the permissions so that you can use fastboot.
Create a new file with the following contents in /etc/udev/rules.d/50-fastboot.rules:
Code:
# AT&T XT1058 16G NAND
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}=="2e23", MODE="0660", GROUP="plugdev"
(these are the vendor-id and product-id I found by putting my phone in fastboot mode, plugging it into my linux laptop, and typing lsusb -n. It maybe different for other vendor/carrier devices. Please post your vendor-id and product-id and model so that I can add to this list! Thanks!)
and type the command groups to make sure your are in the plugdev group.
If you are not, type:
Code:
sudo adduser plugdev
After that is done, logout and log back in to have your session reflect that you are now in the plugdev group.
Then reload the udev rules with:
Code:
sudo udevadm control --reload-rules
Download the android sdk. Run the SDK Manager to Install/Update the platform tools.
Add the platform-tools directory to your operating system's "PATH" environment variable. On linux and mac, just add:
Code:
export PATH="/path/to/platform-tools:$PATH"
to your ${HOME}/.profile file.
Windows
(CURRENTLY NOT SUPPORTED, YET)
On Windows you need to install the Motorola Device Manager.
Also, check out this stack-overflow. (got a better tutorial for this, let me know!)
Also, you will need to get and install the latest 2.7 version of python from python.org. I tested with python 2.7.5 (x86_64)
Download
Releases can be downloaded from here.
The github repository is here.
Changes to the code can be found here.
I've released this as GPLv2, so enjoy!
I test every release on my own phone on Linux and Mac OS X (soon Windows 8 ).
Install moto-x-tools
Download the latest release from the release link above.
Starting with v0.2.0, moto-x-tools is now a python package.
Install this like you would any normal python package:
Code:
python setup.py install
Instructions
In a command prompt; extract the FXZ zip file for your device and change into the directory with the firmware binaries and xml file.
No need to remove the 'getvar' line in the xml, the script I made will ignore it and move on.
Put your phone in fastboot and at the command prompt type:
Code:
moto-x-flash ATT_XT1058_4.2.2-13.9.0Q2.X-116-X-17-51_CFC_1FF.xml
(obiously changing the xml filename to what xml filename your firmware has!)
Now wait. The script will check MD5 checksums of files it will flash, so the checksum and flashing progress will take a while.
At the end of the script it will either tell you if a problem happened or if it was successful and will reboot your device into your fresh 100% stock install.
Attached is a log of flashing my device.
Issues? Problems? Suggestions?
If you find issues, please use the issue tracker on github.

$ fastboot getvar all
will return the identifier of the latest signed software flashed on a device in the ro.buildfingerprint field
(bootloader) ro.build.fingerprint[0]: motorola/ghost_att/ghost:4.2.2/1
(bootloader) ro.build.fingerprint[1]: 3.9.0Q2.X-116-X-17-51/12:user/bl
(bootloader) ro.build.fingerprint[2]: dacfg,release-keys
So, anyone up to just add logic so that this exact version is reflashed on the device (and only this version, and auto-download the right one)..
might play with it this week-end.
<SNIP>

planktoid said:
$ fastboot getvar all
will return the identifier of the latest signed software flashed on a device in the ro.buildfingerprint field
(bootloader) ro.build.fingerprint[0]: motorola/ghost_att/ghost:4.2.2/1
(bootloader) ro.build.fingerprint[1]: 3.9.0Q2.X-116-X-17-51/12:user/bl
(bootloader) ro.build.fingerprint[2]: dacfg,release-keys
So, anyone up to just add logic so that this exact version is reflashed on the device (and only this version, and auto-download the right one)..
might play with it this week-end.
Click to expand...
Click to collapse
Shouldn't take but a moment. Good tip!
Sent from my XT1058 using Tapatalk 4

Refactored the whole package, it's now v0.2.0.
Trying to get it up on PyPI. I seem to be having issues with XDA on my mac. I'll update the OP in a little while.

planktoid said:
$ fastboot getvar all
will return the identifier of the latest signed software flashed on a device in the ro.buildfingerprint field
(bootloader) ro.build.fingerprint[0]: motorola/ghost_att/ghost:4.2.2/1
(bootloader) ro.build.fingerprint[1]: 3.9.0Q2.X-116-X-17-51/12:user/bl
(bootloader) ro.build.fingerprint[2]: dacfg,release-keys
So, anyone up to just add logic so that this exact version is reflashed on the device (and only this version, and auto-download the right one)..
might play with it this week-end.
Click to expand...
Click to collapse
In the latest v0.2.0 release, I've modified the getvar wrapper to return the result as a dictionary. For now it does not work with 'all', but I did test with ro.build.fingerprint and others. Soon it will also return a dictionary for 'all' too.
Sent from my XT1058 using Tapatalk 4

Thanks for this.
One question, is it possible to downgrade with this tool?
I am trying to easily flash back to the stock AT&T release and re-root.

gunnyman said:
Thanks for this.
One question, is it possible to downgrade with this tool?
I am trying to easily flash back to the stock AT&T release and re-root.
Click to expand...
Click to collapse
I'm not sure. I also have an at&t phone, but my bootloader is still locked.
Sent from my XT1058 using Tapatalk 4

Mine too

gunnyman said:
Mine too
Click to expand...
Click to collapse
What did you flash to it. I'll reproduce and try back to stock.
Sent from my XT1058 using Tapatalk 4

I'm under nda not to say lol. But the att update is rolling out.

gunnyman said:
I'm under nda not to say lol. But the att update is rolling out.
Click to expand...
Click to collapse
Hah! Well, if the bootloader allows downgrading, then it should work.
Sent from my XT1058 using Tapatalk 4

gunnyman said:
I'm under nda not to say lol. But the att update is rolling out.
Click to expand...
Click to collapse
bhundven said:
Hah! Well, if the bootloader allows downgrading, then it should work.
Click to expand...
Click to collapse
Well, the update rolled out. Lets find out!

bhundven said:
Well, the update rolled out. Lets find out!
Click to expand...
Click to collapse
Seems to be a negatory, sir.
My log from my script says everything flashed successfully, but on the fastboot framebuffer, I saw lots of 'preflash validation failed' messages like this:
Code:
Partition (boot) Security Version Downgraded
preflash validation failed for boot
and a few other partitions
My script seems to think the flash was successful. Attached is the log.

The phone rebooted and seems fine, though.
When I check for an update, it says there aren't any. So I wonder if the downgrade attempt even did anything at all.
Strange...

I hope new FXZs are released to reflect the update.

Actually, I see the FAILED messages in the log. So, it looks like I need to update the script to check the return codes from fastboot and not the command return code!
Hang tight! I'll have an update soon. I'm also going to add a version check to make sure you don't try to downgrade!
Also, I'm going to do the md5sum check before trying to flash.

<SNIP>
Not sure exactly what your tool is going to do that a normal script kiddy hasn't already done. Flashing fxz files using the fastboot command is childs play, and many scripts exist for this very purpose.
YOU CAN NOT BUILD A TOOL that is going to allow you to downgrade your firmware on a bootloader locked Motorola phone. On older devices the secure version was contained in the CDT.bin file and on newer phones it is contained in the gpt.bin file. Once this has been upgraded then you can only flash that version of firmware. That is why you get preflash validation errors. It will not matter if you try in Windows, OSX, or Linux.
Look around XDA and you should find other more detailed explanations.

jimmydafish said:
Not sure exactly what your tool is going to do that a normal script kiddy hasn't already done. Flashing fxz files using the fastboot command is childs play, and many scripts exist for this very purpose.
Click to expand...
Click to collapse
Have you looked at the github repository? The name of the repo is called "moto-x-tools". Sorry, this one tool out of the set is the only one I've done. And I only did it a few days ago. Also, if you noticed, I'm making a python fastboot frontend library. It still needs some love, but it's work in progress.
jimmydafish said:
YOU CAN NOT BUILD A TOOL that is going to allow you to downgrade your firmware on a bootloader locked Motorola phone.
Click to expand...
Click to collapse
Did I say that was the goal of the project?
jimmydafish said:
On older devices the secure version was contained in the CDT.bin file and on newer phones it is contained in the gpt.bin file. Once this has been upgraded then you can only flash that version of firmware. That is why you get preflash validation errors. It will not matter if you try in Windows, OSX, or Linux.
Click to expand...
Click to collapse
This tool was designed to allow you to go back to stock on the same version as say a modified version of the the stock rom, with the same bootloader version. This check in my one script is coming soon! Trust me. I was asked to test how it handled flashing an old FXZ with a newer update. And obviously it did not go well. My phone still works fine, because the bootloader was smarter then I was.
jimmydafish said:
Look around XDA and you should find other more detailed explanations.
Click to expand...
Click to collapse
You'd be surprised what I've learned by searching around the last few days. Sorry for journaling my progress of learning.
BTW, could you not QUOTE THE ENTIRE OP!?!?!?
Thanks,
-Bryan

bhundven said:
Hang tight! I'll have an update soon. I'm also going to add a version check to make sure you don't try to downgrade!
Click to expand...
Click to collapse
Just quoting... you know... to make it even more clear.

Interesting to note:
Code:
Running: fastboot flash partition gpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.180s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 0.880s
Running: fastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'motoboot' (1588 KB)...
OKAY [ 0.298s]
writing 'motoboot'...
(bootloader) flashing sbl3 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing sbl2 ...
OKAY [ 4.960s]
finished. total time: 5.258s
From that failed flash; While gpt.bin failed to flash, motoboot.img (which contains aboot and sbl[1-3]) flashed fine. Maybe it wasn't updated in 139.12.54?

[GUIDE][BRICKED] [BOOTS ONLY TO RECOVERY][All ASUS TRANFORMERS]

This is a general users guide to unbrick your Transformer tablet.
This guide will help you if your Asus tablet will only boot into recovery
and the command
Code:
adb reboot-bootloader
does not work to get you booted back to bootloader screen ..
If the above command works then skip to the first fastboot command ..
WHAT YOU NEED
An Asus tablet that will only boot into recovery …
Woking adb and fastboot on your PC
Windows drivers (if using Windows)
A fully charged tablet
Asus data cable
Stock firmware blob (from Asus's web site, make sure you get the right one)
_that's bootit.ko (unzipped and placed with fastboot.exe)
Downloads
Asus Stock firmware---MAKE SURE YOU GET THE CORRECT SKU FOR YOUR TRANSFORMER TABLET
click me
_that's bootit.ko----click me
INSTRUCTIONS
Extract your stock firmware in your downloads folder twice...You will see a blob file rename it boot.blob and move it to the same folder as your fastboot.exe or if in linux to your home folder
Unzip the bootit.ko and place it wth the above blob file.
Let start with this command to make sure that your PC can see your table as an ADB device in recovery
Code:
adb devices
OUTPUT
Code:
[email protected] ~ $ adb devices
List of devices attached
015c7d7a445c260c recovery
Then lets push the bootit.ko to the root of the device like this
Code:
adb push bootit.ko /
OUTPUT
Code:
[email protected] ~ $ adb push bootit.ko /
673 KB/s (27690 bytes in 0.040s)
Then lets insmod this .ko file
Code:
adb shell insmod /bootit.ko
This should reboot the tablet into the bootloader menu, lets verifiy.
Once in the bootloader screen lets make sure your PC can see the device in fastboot.
Code:
fastboot devices
OUTPUT
Code:
[email protected] ~ $ fastboot devices
015c7d7a445c260c fastboot
So now its time to erase the misc & cache partitions, as that is most likely the partitions that is making it boot to recovery...
Code:
fastboot erase misc
OUTPUT
Code:
[email protected] ~ $ fastboot erase misc
erasing 'misc'...
OKAY [ 1.021s]
finished. total time: 1.021s
Code:
fastboot erase cache
OUTPUT
Code:
[email protected] ~ $ fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 2.096s]
finished. total time: 2.096s
Once these two command run with OKAY as the OUTPUT .
It is time to make sure we can reboot into the bootloader with the hardware buttons
So from where you are at in the bootloader screen use the VOL DOWN & POWER buttons to boot the tab back into the bootloader screen ..
Run these command in fastboot in this order
The next command is to just verify your computer can see your device
Code:
fastboot devices
OUTPUT
Code:
[email protected]:~ > fastboot devices
015d2bbce2501405 fastboot
Code:
fastboot erase system
OUTPUT
Code:
[email protected]:~ > fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.954s]
finished. total time: 2.954s
Code:
fastboot erase recovery
OUTPUT
Code:
[email protected]:~ > fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.945s]
finished. total time: 1.945s
Code:
fastboot -w
OUTPUT
Code:
[email protected]:~ > fastboot -w
erasing 'userdata'...
OKAY [ 23.188s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29618601984
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7231104
Block groups: 221
Reserved block group size: 1024
Created filesystem with 11/1810432 inodes and 157662/7231104 blocks
sending 'userdata' (139133 KB)...
writing 'userdata'...
OKAY [ 26.358s]
erasing 'cache'...
At this point it will either hangs on erasing 'cache'
Or it will give you an error, either way you will need to
reboot the tablet back into fastboot with the hardware buttons
Once that is done continue on the path
Code:
fastboot erase boot
OUTPUT
Code:
[email protected]:~ > fastboot erase boot
erasing 'boot'...
OKAY [ 1.209s]
finished. total time: 1.209s
Code:
fastboot erase misc
OUTPUT
Code:
[email protected]:~ > fastboot erase misc
erasing 'misc'...
OKAY [ 0.978s]
finished. total time: 0.978s
Code:
fastboot erase cache
OUTPUT
Code:
[email protected]:~ > fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 2.843s]
finished. total time: 2.843s
Code:
fastboot -i 0x0B05 flash system boot.blob
During the sending/writing process of this step you will get the blue bar on your screen.....
OUTPUT
Code:
[email protected]:~ > fastboot -i 0x0B05 flash system boot.blob
erasing 'system'...
OKAY [ 2.339s]
sending 'system' (800927 KB)...
OKAY [133.094s]
writing 'system'...
[OKAY [178.036s]
finished. total time: 313.469s
Code:
fastboot -i 0x0B05 reboot
OUTPUT
Code:
[email protected]:~ > fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.020s
Let it boot into stock ROM ....

Credits
@_that for his bootit.ko
TEAM CROMBi and TEAM ZOMBi-X @sbdags @hardslog

Troubleshooting
Here is some troubleshooting
Check out this thread for fasboot.exe, adb.exe and driver help ...CLICK ME

A message from _that
_that said:
Here is the original thread where the bootit module was tested for the first time -> http://forum.xda-developers.com/showthread.php?t=2291974
The problem was that the installed recovery was too old and incompatible with the bootloader and so could not access the eMMC at all. The bootloader command to boot to recovery is stored in the MSC partition (mmcblk0p3), and the recovery could not clear it. Since the bootloader checks the MSC partition before checking for volume-down, it is impossible to get to fastboot without some additional kick in the butt (aka "bootit.ko").
The correct bootit.ko file to use is the one in "bootit-bootloader.zip": http://forum.xda-developers.com/attachment.php?attachmentid=1985941&d=1369339132 - the older version turned out to be too weak. Note that this is a zipped kernel module, not a recovery-installable ZIP. You need to unzip it on your PC before adb push.
After making it to the bootloader menu and working fastboot, you can fastboot flash a current version of TWRP and install the custom ROM of your choice. No real need for the stock blob, unless you want to make sure you have the current bootloader and a known working ROM.
Here is another thread where bootit.ko didn't help, maybe it was really a hardware problem. But lots of good background info from me. -> http://forum.xda-developers.com/showthread.php?t=2437376
And here is another success story -> http://forum.xda-developers.com/showthread.php?p=47525770
Click to expand...
Click to collapse
Thx for all your help @_that

Great Guide: a happy Transformer Prime User you made of me!
Dear lj50036,
Thanks so much for your excellent guide. I went along with it all the way to the end and it just worked, splendid! You set up the scenario quite clearly and for those guys who are in the same situation this is a very handy guide.
Excellent piece of work!
My congratulations on your great work!
mitsublw

mitsublw said:
Dear lj50036,
Thanks so much for your excellent guide. I went along with it all the way to the end and it just worked, splendid! You set up the scenario quite clearly and for those guys who are in the same situation this is a very handy guide.
Excellent piece of work!
My congratulations on your great work!
mitsublw
Click to expand...
Click to collapse
I am glad to see you up and running ..... :good:
Thx Josh

Do I need a specific blob other than a US blob considering US is my area?

xerotix said:
Do I need a specific blob other than a US blob considering US is my area?
Click to expand...
Click to collapse
The tablet will tell you what the SKU is ....
When on the bootloader screen in the upper left is will tell you the SKU ...
Thx Josh

I just put together a Win 8 64 bit with a quad core i5...to the best of my knowledge I'm having trouble with it recognizing my tf300t. while it's physically connected on my front and/or rear usb ports, as I hear it recognized physically connecting, no visual signs of it connecting in my file explorer in twrp, prior recovery, and off after having all of the drivers and such installed to the best of my knowledge using your link as well...Suggestion?

xerotix said:
I just put together a Win 8 64 bit with a quad core i5...to the best of my knowledge I'm having trouble with it recognizing my tf300t. while it's physically connected on my front and/or rear usb ports, as I hear it recognized physically connecting, no visual signs of it connecting in my file explorer in twrp, prior recovery, and off after having all of the drivers and such installed to the best of my knowledge using your link as well...Suggestion?
Click to expand...
Click to collapse
Dont use windows 8 ..
That is all I can give you, never used it.
Not going to sit here and fill you with BS like I have all the answers.....
My solution would be to us some kind of a Linux OS .... I prefer Mint but @hardslog hates it .....
He will get a kick out of that ... LOL
Thx Josh

lj50036 said:
Dont use windows 8 ..
That is all I can give you, never used it.
Not going to sit here and fill you with BS like I have all the answers.....
My solution would be to us some kind of a Linux OS .... I prefer Mint but @hardslog hates it .....
He will get a kick out of that ... LOL
Thx Josh
Click to expand...
Click to collapse
I'm trying to figure out how to install Mint on my computer after I partitioned my hard drive to give me the space to install it...I'm searching google for it but haven't run across anything as of yet.

xerotix said:
I'm trying to figure out how to install Mint on my computer after I partitioned my hard drive to give me the space to install it...I'm searching google for it but haven't run across anything as of yet.
Click to expand...
Click to collapse
Is Mint going to go on its own hdd or are you going to dual boot from a hdd with windows on it ?
Thx Josh

lj50036 said:
Is Mint going to go on its own hdd or are you going to dual boot from a hdd with windows on it ?
Thx Josh
Click to expand...
Click to collapse
Dual boot on 2 tb hdd

xerotix said:
Dual boot on 2 tb hdd
Click to expand...
Click to collapse
You're dual booting with windows, yes ?
http://itsfoss.com/guide-install-linux-mint-16-dual-boot-windows/
There is all kinds of info out there ...
Thx Josh

lj50036 said:
My solution would be to us some kind of a Linux OS .... I prefer Mint but @hardslog hates it .....
He will get a kick out of that ... LOL
Thx Josh
Click to expand...
Click to collapse
Lol, LIES. I don't hate MINT. I just like to give @sbdags a hard time when something goes wrong with it. Any popular Linux distro should work well, and if you don't want to install it on a hard drive you can always install it on a USB and run from that

Thank you. You learn something new everyday...lol. I'm about to go to Full Sail here in Orlando where I live for software development. I was told I will be learning a lot in conjunction with Software Development parallel to Android development(which they teach as well)...I'm loving it.

I have tried everything I can think of...turned safe boot off after going into BIOS and searching more in BIOS, nothing thus far...

I have vista on another hard drive...would it work on vista?

xerotix said:
I have vista on another hard drive...would it work on vista?
Click to expand...
Click to collapse
It may work under vista .....
Thx Josh

lj50036 said:
It may work under vista .....
Thx Josh
Click to expand...
Click to collapse
It's gonna be a PITA to install that hard drive on this computer as I built this computer because of that POS. I'm unsure but hopefully I can figure out a way to connect both hard drives and have some sort of dual boot to use this hard drive with my new processor as opposed to the AMG with 1 gb of ram in the previous one from 5+ years ago. I already gutted it cuz it's of no use to anyone other than parting out. I have windows 7 on an old laptop I don't use anymore but I'm unsure of how to use that hard drive as to whether I can connect that one to that of my new desktop in a way/shape/or form so to speak