Database Users

WANTED: Sticky guide for newbies

Hi all
I have several years experience from rooting and applying all kinds of ROM's om both Symbians, Motorola OS, Android and WM devices but I am completely stuck when trying to "fix" the problem with non-existing SD card support on the Xoom.
What I have been looking for is a guide that walks you through Unlocking, Rooting, adding CWM and finally replaces the kernel with a "better" one. I have of course found all kind of guides on any of the topics above, but all of them assumes that you already have performed one or another of these steps.
So if anyone could be an angel and summarize the steps (links are ok) with the assumption that the reader (I) have
- oem locked
- no cwm installed
- unrooted
- Wifi only
- updated 3.1 honeycomb device.
I will certainly cry of joy if someone can do this for the good of the community. I am sure that many like I have already tried both this and that, and bricked or soft-bricked (I did) their devices while trying to get the god damned sd card to become functional . My own device has now been resurrected from coma (RSD Mode 2) and is now alive again, thanks to "fastboot oem unlock" but I can not for my life get the CWM to work. I have installed the recovery-Tiamat-R4c-100611-1150-cwm.img with fastboot. No errors reported either on the tablet och in Windows during flashing. But when pressing VolUp during boot, I just get stuck in "Starting RSD protocol support 3". I can boot normally if I dont press any button. Fastboot mode works too.

Below is a slightly modified of Land Master's NOOB guide. I have only updated a couple of links. I followed this guide when I originally rooted my Xoom, and it worked perfectly. But note that I have not tested this with the updates. All credit for this goes to Land Master!
USE THIS, AND ASSUME ALL RISKS. IT HAS NOT BEEN TESTED WITH THE UPDATED LINKS!
WIFI ONLY! WIFI ONLY! WIFI ONLY!
If you use this guide, or any other guide for that matter, make sure that you read it, reread it, (10 times!) and fully understand every step. One hour now, spent studying this, will save you 10 hours of headaches later. Make sure you follow every step EXACTLY!
"This tutorial was written for the NooB’s among us (like me) that are new to this stuff and are having a hard time “piecing together” all of the steps. While I am actually a not quite a beginner, NONE of these steps/methods/files have been developed by me. I have simply compiled the procedure in a document that I hope will be useful. With this in mind all the credit belongs to the many individuals that contribute in the XDA Developers forum. I have reviewed many posts by many people and have used all of the information along the way.
A)*Installing ADB
ADB stands for Android Debug Bridge and simplistically stated will be used to send commands to your XOOM using the keyboard on your PC. In essence your PC will be acting like a terminal. ADB is included in a package known as the Android SDK. The following steps should be taken to insure a successful install of the SDK, therefore giving you access to ADB.
1.*Install Java JDK :*http://www.oracle.com/technetwork/ja...ad-346242.html
a.*Download appropriate Java SE Development Kit (JDK) from link above
b.*Double click to Install JDK
c.*Accept Setup Defaults
2.*Install SDK Starter Package:*http://developer.android.com/sdk/index.html
a.*Download SDK Starter Package from link above. There are versions available for Microsoft Windows, Linux and Mac OS X. In case of Windows, both an installer and a zip file are available but there isn’t any need to use the installer as a formal installation is not required. Download the ZIP file.
b.*Once you have downloaded the SDK, simply extract the compressed file to a location on your computer. In our case, we have extracted it to the root of our C drive and that makes*C:\android-sdk-windows*the installation location of the SDK. From here onwards, we shall be referring to this location as the ‘SDK folder’.
3.*Download the SDK Platform Tools using the SDK Mamager.
a.*Browse to the SDK folder and launch SDK Manager.
b.*When launching it for the first time, it will present you with a window to choose packages to install. The first option begins with ‘Android SDK Platform-tools’. Make sure it is checked, and uncheck all the other packages for now. You can check/uncheck a package by simply double clicking on the package. Again, the only package you want to install is the Android SDK Platform-Tools.
c.*Once the process is done, you will have a ‘platform-tools’ folder inside your SDK folder. That folder will include ADB and all its dependencies.
d.*Make a copy of the File “fastboot.exe” which is in the “tools” directory and place it in the “platform-tools” directory.
B)*Install XOOM USB Driver
Just to be sure your XOOM is recognized by your PC it is recommended that you install the latest USB drivers for your system.
1.*Install MotoHelper :*http://www.motorola.com/Support/US-E...arging-Drivers
a.*Download the Driver with MotoHelper from the Link above
b.*Double Click downloaded file and follow on-screen instructions to install.
C)*Unlock Bootloader
Unlocking the bootloader gives you full control over the device so you can flash new Recovery’s, kernels, ROM’s, ETC.*THIS STEP*WILL DELETE ALL DATA AND SETTINGS ON YOUR XOOM.
1.*Put XOOM in Debug mode
a.*On the device, go to home screen, press*Apps*> >Settings>>Applications>>Development, and enable*USB Debugging.
b.*Now connect your XOOM to the PC via USB. New hardware installation should begin and it will start looking for and installing the drivers.
c.*A prompt should appear that states the drivers were installed successfully. On my PC the AutoPlay Device Options also appeared. I clicked “Open Device to View Files” and saw the device Storage with 27.8 GB free of 28.7 GB.
2.*Execute ADB Commands
a.*Open a command prompt by navigating to the ‘SDK Folder’, Holding the shift key, right clicking on the “platform-tools” folder and selecting “Open Command Window Here” from the popup menu.
b.*In the new command window type:*adb reboot bootloader*and press enter.
c.*Wait for the Dual Core screen with “Starting Fastboot protocol support” in the upper left corner to appear and then type:*fastboot oem unlock*in the command window and press enter. You should see: “To continue, follow instructions on the device’s display…”.*
d.*Read the WARNING on you XOOM and either Continue Below or Cancel following the on-screen instructions.
e.*If you decided to continue then on the XOOM Push Volume Down Button to change the selection from “Cancel” to “I accept” and then press the Volume Up to select that choice.
f.*You will be questioned again so Push Volume Down then Volume Up to confirm you want to UNLOCK your device. You will see “Device Unlock operation in progress…” “Formatting UDA”
g.*When the operation completes the device will read”Device unlock operation done – rebooting…” and the device will reboot. The windows new hardware “gong” will sound a couple of times during this procedure. After this step when my XOOM rebooted I also saw an “MTP Device” driver Install dialog box on my PC. Unplug the device, and quickly perform the initial set-up. You can “Skip” any steps that will allow you to (like WiFi setup). Just get back to the home screen and continue below:
h.*Verify that USB debugging is still enabled and if not re-enable it as outlined above.
i.*Re-connect your XOOM to the PC and close any AutoPlay dialog.
D)*Install Custom Recovery
A custom recovery allows you to flash files created by community developers such as ROM’s, Radios, Kernels, Themes, ETC. It also allows you to perform special tasks such as system backup’s, partitioning, cache wiping, ETC. As of 6/19/2011 the generally accepted custom recovery for the XOOM is ClockworkMod Recovery v3.2.2.0
a.*Download Clockwork Mod recovery image (not .zip file) from here:http://forum.xda-developers.com/show....php?t=1074979*
CAUTION: Do not install CWM 4.0.0.X from ROM manager!
b.*Place the File “recovery.img” that you just downloaded in the “platform-tools” directory
c.*In the previously open command window (if you closed it then re-open as described above) type:*adb reboot bootloader*and press enter.
d.*The device will reboot into bootloader mode (as described above) and when this completes type:*fastboot flash recovery recovery.img (name must match name of file)
e.*Check the screen of your XOOM and see: “Flashing StorMgr partition recovery STATUS: - done!*
f.*Type:*fastboot reboot*in the command window and press enter.
g.*Wait 3 second after the Moto logo is seen, then pushed Vol Down
h.* Android recovery menu visible, press Vol Up. Go straight into CWM.
i.*Navigate in ClockworkMod Recovery by using the volume up/down to “move” and the power button to “select”. Look for reboot system, highlight it and hit the power button. Your zoom will reboot normally.
OPTIONAL STEPS
l.*At some time later (AFTER YOU ARE ROOTED) to avoid the need to execute ADB commands to enter recovery, I suggest you look for a free application called “Quick Boot”, by Sirius Applications from the market.*
m.*Once Quick Boot is installed run it and simply select “Recovery” to boot into ClockworkMod.*
Next Step: Following Public Animal's guide to rooting >*http://forum.xda-developers.com/show....php?t=1075260*
Last step (optional) install Tiamat 1.0 ROM >*http://forum.xda-developers.com/show....php?t=1117004

Thanks a lot! I am with you all the way to step H (adb reboot recovery). This step ends with the Android, yellow triangle and an exclamation mark. Nothing more. So something must be wrong with the recovery image.
In both your links and other links to the recovery image, the name "recovery-solarnz-XXXXXX-XXXX.img" is used. But the links always leads to the image "recovery-Tiamat-R4c-100611-1150-cwm.img" instead. Could this be the problem? If so, what should the XXXXX be replaced with (for googling).
Thanks again for the guide. Sooner or later I *will* succeed!
Edit: Could this post be something that explains why my CWM flashing does not succeed? http://forum.xda-developers.com/showpost.php?p=13747198&postcount=18
And since the device still not is rooted, I can not rm the suggested files ... gaaah

pingvinen said:
Thanks a lot! I am with you all the way to step H (adb reboot recovery). This step ends with the Android, yellow triangle and an exclamation mark. Nothing more. So something must be wrong with the recovery image.
In both your links and other links to the recovery image, the name "recovery-solarnz-XXXXXX-XXXX.img" is used. But the links always leads to the image "recovery-Tiamat-R4c-100611-1150-cwm.img" instead. Could this be the problem? If so, what should the XXXXX be replaced with (for googling).
? http://forum.xda-developers.com/showpost.php?p=13747198&postcount=18
And since the device still not is rooted, I can not rm the suggested files ... gaaah
Click to expand...
Click to collapse
Not sure that I've completely understood your question, but when you type:*fastboot flash recovery recovery.img, make sure to replace the words "recovery.img" with the actual name of the recovery image file.

cam30era said:
Not sure that I've completely understood your question, but when you type:*fastboot flash recovery recovery.img, make sure to replace the words "recovery.img" with the actual name of the recovery image file.
Click to expand...
Click to collapse
Of course I do. Here is what I type
D:\Java\android-sdk\platform-tools>fastboot.exe flash recovery recovery.img
sending 'recovery' (3998 KB)...
OKAY [ 0.500s]
writing 'recovery'...
OKAY [ 1.031s]
finished. total time: 1.531s
D:\Java\android-sdk\platform-tools>
The tablet says "Flashing StorMgr partition recovery STATUS: - done!
I will try once more with the "timing trick" from this thread
http://forum.xda-developers.com/showthread.php?t=1078019

pingvinen said:
Of course I do. Here is what I type
D:\Java\android-sdk\platform-tools>fastboot.exe flash recovery recovery.img
sending 'recovery' (3998 KB)...
OKAY [ 0.500s]
writing 'recovery'...
OKAY [ 1.031s]
finished. total time: 1.531s
D:\Java\android-sdk\platform-tools>
The tablet says "Flashing StorMgr partition recovery STATUS: - done!
I will try once more with the "timing trick" from this thread
http://forum.xda-developers.com/showthread.php?t=1078019
Click to expand...
Click to collapse
The name of the file is "recovery-Tiamat-R4c-100611-1150-cwm". So you should type:*fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img

It actually worked! What I did was this
1. adb reboot bootloader
2. flashed the same recovery image that I mentioned earlier
3. fastboot reboot
4. applied the 3 second wait once the Moto logo was seen, then pushed Vol Down
5. Android recovery menu visible, press Vol Up. Now I got straight into CWM !!!
6. (prepared the sd card on my SGS with the zip files)
7. Choosed Install zip from sd card and flashed the wifi-root image
8. Reboot the tablet and verified with RomManager that I now had root
THANK YOU VERY MUCH FOR NOT GIVING UP ON ME

cam30era said:
The name of the file is "recovery-Tiamat-R4c-100611-1150-cwm". So you should type:*fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Click to expand...
Click to collapse
For simplicity I renamed the zip to recovery.zip before copying it to the folder and flashing it (see next post also!)

I am going to modify the instructions. Is this correct for what you did?
"f.*Type:*fastboot reboot*in the command window and press enter.
g.*Wait 3 second after the Moto logo is seen, then pushed Vol Down
h.* Android recovery menu visible, press Vol Up. Go straight into CWM.
j.*When my device rebooted into recovery I also saw additional Device Drivers install. This took a little while and I waited to do anything until I received the “Device Driver Installed Successfully” dialog."

cam30era said:
I am going to modify the instructions. Is this correct for what you did?
"f.*Type:*fastboot reboot*in the command window and press enter.
g.*Wait 3 second after the Moto logo is seen, then pushed Vol Down
h.* Android recovery menu visible, press Vol Up. Go straight into CWM.
j.*When my device rebooted into recovery I also saw additional Device Drivers install. This took a little while and I waited to do anything until I received the “Device Driver Installed Successfully” dialog."
Click to expand...
Click to collapse
Yes, everything except the last step (j). I did not see anything on the computer screen. But now I have managed to install CWM, root it and install Tiamat 's latest kernel. The external sd card is now visible inside /sdcard/external! Success!

pingvinen said:
Yes, everything except the last step (j). I did not see anything on the computer screen. But now I have managed to install CWM, root it and install Tiamat 's latest kernel. The external sd card is now visible inside /sdcard/external! Success!
Click to expand...
Click to collapse
Post updated with your input. Thanks for being the first guinea pig!

cam30era said:
Post updated with your input. Thanks for being the first guinea pig!
Click to expand...
Click to collapse
This is an amazing guide! cam30era you and LandMaster are the bomb!
May suggest one thing? When reading it through, I think a real noob might be confused with the asterisks that are on either side of many of the adb commands.
Anyway this should definitely be a sticky!

actually I sat down and wrote my own guide, starting from scratch and ensuring that every assumption and requirement was explained. I called it "idiots guide to ..." . Maybe it would be a good idea to consolidate the best from both guides into a -definitive guide-. What do you think?
Oh, the thread is in the Android development forum. Mod is welcome to move it if so needed

pingvinen said:
actually I sat down and wrote my own guide, starting from scratch and ensuring that every assumption and requirement was explained. I called it "idiots guide to ..." . Maybe it would be a good idea to consolidate the best from both guides into a -definitive guide-. What do you think?
Oh, the thread is in the Android development forum. Mod is welcome to move it if so needed
Click to expand...
Click to collapse
Excellent idea. Go for it.
Sent from my Xoom using XDA Premium App

CWM won't boot.
For the life of me I can't understand what I'm doing wrong. US Wifi Xoom with 3.1, bootloader is unlocked, but not rooted. I use fastboot to flash the latest recovery img, 3.2.0 I beleive. Says it's successful, but like many on here when I either use "adb reboot bootloader" or if I time it and press volume down to get into the recovery, I only get a picture of the robot with the triangle. I can press volume up+power and I get the stock recovery.
I've read every post I can read but most people who have resolved the same issue were just not flashing the correct image. Which I'm sure I'm doing correctly.
Amy help would be appreciated.

bloglos said:
For the life of me I can't understand what I'm doing wrong. US Wifi Xoom with 3.1, bootloader is unlocked, but not rooted. I use fastboot to flash the latest recovery img, 3.2.0 I beleive. Says it's successful, but like many on here when I either use "adb reboot bootloader" or if I time it and press volume down to get into the recovery, I only get a picture of the robot with the triangle. I can press volume up+power and I get the stock recovery.
I've read every post I can read but most people who have resolved the same issue were just not flashing the correct image. Which I'm sure I'm doing correctly.
Amy help would be appreciated.
Click to expand...
Click to collapse
Try pingvinean's guide for "idiots " (no disrespect intended, that's the real name) in the development section.
Sent from my ADR6300 using XDA Premium App

cam30era said:
Try pingvinean's guide for "idiots " (no disrespect intended, that's the real name) in the development section.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
Thank you! Completely missed the part about the recovery being overwritten if I missed the timing and booted into honeycomb.

bloglos said:
Thank you! Completely missed the part about the recovery being overwritten if I missed the timing and booted into honeycomb.
Click to expand...
Click to collapse
Hehe, no disrespect but since the bookshelves are drenched in "for dummies" and "for idiots", I thought it might be ok to use that title. Glad that you finally succeeded!

[Q] Bricked a500- stuck on boot menu.

Yes I am a noob, but a noob in need of help.
I recently decided to root my Acer Iconia a500 16gb WIFI version, running on stock ICS. I realised i had to unlock my bootloader to install CWM etc. So I followed a tutorial, and used blackthund3rs A500 APX Flash Utility v0.4. I used the flash package "Skrilax_CZ's bootloader V8".
So I thought all was going well, however when rebooting it, it just sits on "Skrilax_CZ's bootloader V8: Booting primary kernel image". I'm assuming its bricked, as it doesn't go beyond this point. I can get a few other options by doing the "PWR+VOL" combination and it opens boot-menu mode with the options:
-Reboot
-Fastboot Mode
-Boot Primary Kernel Image
-Boot Secondary Kernel Image
-Boot Recovery
-Set Boot secondary Kernel Image
-Set debug mode off/on
-Wipe Cache
The only option that does the slytest thing is putting it in fastboot mode. When putting it in this mode, it registers in "A500MANAGER" (when connected to my pc via USB) as the device being in fastboot mode. But I dont know what to do from there.
I've looked at multiple threads and cant find anything to fix this problem.
Please Help! Thanks!

boxyJ said:
Yes I am a noob, but a noob in need of help.
I recently decided to root my Acer Iconia a500 16gb WIFI version, running on stock ICS. I realised i had to unlock my bootloader to install CWM etc. So I followed a tutorial, and used blackthund3rs A500 APX Flash Utility v0.4. I used the flash package "Skrilax_CZ's bootloader V8".
So I thought all was going well, however when rebooting it, it just sits on "Skrilax_CZ's bootloader V8: Booting primary kernel image". I'm assuming its bricked, as it doesn't go beyond this point. I can get a few other options by doing the "PWR+VOL" combination and it opens boot-menu mode with the options:
-Reboot
-Fastboot Mode
-Boot Primary Kernel Image
-Boot Secondary Kernel Image
-Boot Recovery
-Set Boot secondary Kernel Image
-Set debug mode off/on
-Wipe Cache
The only option that does the slytest thing is putting it in fastboot mode. When putting it in this mode, it registers in "A500MANAGER" (when connected to my pc via USB) as the device being in fastboot mode. But I dont know what to do from there.
I've looked at multiple threads and cant find anything to fix this problem.
Please Help! Thanks!
Click to expand...
Click to collapse
Sounds like the A500 manager didn't do something right. Happens sometimes.
Here is what I would do. I assume you don't have the Android SDK installed. No need to, as some of the bootloader/CWM packages have the necessary files needed.
1. Boot to the bootloader, select the option "Fastboot Mode"
2. Make sure you have downloaded to PC a CWM package for ICS/JB. Usually the manual packages have the necessary files, such as the CWM image, fastboot.exe, adb, and some dll files. Unzip them to your PC. (Also helps to download a custom ICS or CM10 rom to your sd card first)
3. Open a command window in the same folder you have the files.
4. type "fastboot flash recovery xxxxxxxx.img" (xxxxxxxx is name of cwm recovery img file, do not put the " in) then hit enter.
5. After completion, immediately boot tablet into recovery. I believe holding Vol- and PWR does this. Or, Vol+ and PWR boots to the bootloader menu. Either way.
In recovery, do your wipes and or formats as per ROM installation instructions.
Install ROM
Enjoy. If you have problems locating one of those packages, give a shout back.
MD

Thanks for the fast reply,
I am a noob, so could you perhaps link me a CWM package for ics to download?
Thanks

boxyJ said:
Thanks for the fast reply,
I am a noob, so could you perhaps link me a CWM package for ics to download?
Thanks
Click to expand...
Click to collapse
No problem. I'll post a link in awhile.
MD

Files
Ok, so here are your files.
Unzip the contents of the zip file to a folder on your PC
Boot your tab to the bootloader menu, select Fastboot.
Connect tab to PC, then wait 30 seconds or so (windows has to recognize it)
Then, go to that folder. Hold "Shift" + "Right Mouse Click".
Select "Open Command Window"
Type in the following;
fastboot flash recovery recovery_thor17_403.img
and hit enter. Should transfer good.
When finished, boot tablet to recovery like I mentioned earlier. DO NOT boot to the system. Or you'll be doing this all over again.
Install ICS or CM10 rom following the instructions on the ROM post. I suggest starting out with Civato's ICS Flex****** rom first, or one of the stock rooted ones.
Should be good...... I hope.
MD

Thanks again.
I did the fastboot recovery thing. But when I go to reboot, I have to turn it on and select "Boot Recovery", when I do its stuck on the screen "Skrilax_CZ's bootloader v8: Booting recovery kernel image"
Is this whats supposed to happen or am I supposed to see a different screen?

boxyJ said:
Thanks again.
I did the fastboot recovery thing. But when I go to reboot, I have to turn it on and select "Boot Recovery", when I do its stuck on the screen "Skrilax_CZ's bootloader v8: Booting recovery kernel image"
Is this whats supposed to happen or am I supposed to see a different screen?
Click to expand...
Click to collapse
Shut down the tab. Reboot holding V- and PWR release when you see the text. Should reboot to recovery.

If not, your partitions are probably hosed.
Then it's Timmy Deans Rollback tool time. Will have to turn you over to dibs_nz for that one.
MD

Moscow Desire said:
Shut down the tab. Reboot holding V- and PWR release when you see the text. Should reboot to recovery.
Click to expand...
Click to collapse
That brings me to the screen "Skrilax_Cz's bootloader V8: Booting recovery kernel image." But it doesn't go any further?

Well crap.
Sounds like some partitions are messed.
Try this NVFlash package;
http://d-h.st/32X
It's a version 3 bootloader using NVFlash. Might work.
Put your tab in APX mode (I believe you press and hold the pinhole reset, then PWR. After 3 seconds, release PWR, 2 seconds later release pinhole. Might have to reverse it, don't remember)
Plug tab in. PC should recognize.
Unzip to a folder, open a command window, and run the batch file (type it into the command window, xxxxxxxx.bat then hit enter)
If there's an error, it should show in the command window.
Here is a link to Timmy Deans roll back package;
http://d-h.st/0x7
The issue here, is you need a UID number, which I HOPE you wrote down when you did the V8 bootloader!
MD

Well I cant manually put it into APX mode, tried a few times. Also there is no bat file in that download... as for Timmy Deans roll back package, is it a simple method taht should work? At this point I just want to get my tab working again . And yes I do have my UID number.

Ok,ok.
So this morning I tried to fix it again. And I think i managed to put it in APX mode. Also, I started up APX flash tool and all, did that. Suddenly a cmd window opened and started doing stuff. And now the tablet says in the top right corner "Acer Iconia APX mode", and a yellow glowing 'acer' title in the middle (which is different from what I've been seeing). Another cmd window opened by itself saying "Nvflash started [resume mode]. Where do i go from here??
Thanks!

So I think I've gotten a better understanding of how this all works today. I've tried multiple ways of flashing recovery imgs ect, flashing the bootloader and all that stuff. And all the times I've done this, it always stops at "Nvflash started [resume mode]" and doesn't go any further.
So I'm not really sure what else there is to do.
Please, I need guidance. (below is my last attempt, and what It said in the cmd window).
Flashing bootloader: bootloader_v8.bin ...
Nvflash started
[resume mode]
Formatting partition 4 please wait.. Command Execution failed cmd 13, error 0x12
0002
FAILED!
command failure: format partition failed (bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
Nvflash started
[resume mode]

Please let us know if/how you fixed this problem! Some of us are in the same boat.

timmytutone said:
Please let us know if/how you fixed this problem! Some of us are in the same boat.
Click to expand...
Click to collapse
U guys need to run the babsector.rar file to reset yr tabs partitions and you must have yr cpuid/sbk.
The file and instructions to use it are in post 2 of the root guide in my sig.
If u get any errors you must post the output. You may have a faulty memory chip. If that's the case, a new motherboard is the only fix.
dibb
Sent from my GT-I9300 using Tapatalk 4
EDIT: Link to post2 (babsector.rar file)
http://forum.xda-developers.com/showthread.php?p=35500589

dibb_nz said:
U guys need to run the babsector.rar file to reset yr tabs partitions and you must have yr cpuid/sbk.
The file and instructions to use it are in post 2 of the root guide in my sig.
If u get any errors you must post the output. You may have a faulty memory chip. If that's the case, a new motherboard is the only fix.
dibb
Sent from my GT-I9300 using Tapatalk 4
EDIT: Link to post2 (babsector.rar file)
http://forum.xda-developers.com/showthread.php?p=35500589
Click to expand...
Click to collapse
Thank you so much for the reply. I gave up this afternoon and just flashed the ota 4.0.3 version from Acer and it seems to be running really good. The only reason I was looking to flash something new is because the update from honeycomb to ics didn't take very well and I've always been dealing with problems from it. If the flashed version is still running well I might not try a different Rom again. I'll be putting your tip in my notes in case I do. Thanks again.

dibb_nz said:
U guys need to run the babsector.rar file to reset yr tabs partitions and you must have yr cpuid/sbk.
The file and instructions to use it are in post 2 of the root guide in my sig.
If u get any errors you must post the output. You may have a faulty memory chip. If that's the case, a new motherboard is the only fix.
dibb
Sent from my GT-I9300 using Tapatalk 4
EDIT: Link to post2 (babsector.rar file)
http://forum.xda-developers.com/showthread.php?p=35500589
Click to expand...
Click to collapse
So I rooted and then flashed a Custom Recovery Image. Then I followed the instructions under the babsector portion of your post. I got to this part: Go back into apx mode and run 501 B.bat, Reboot into recovery and do the wipes, Reboot!!!
I wasn't sure what "do the wipes" referred to so I did ALL the wipes. Cache/Dalvik/Battery/ and Data(?) When I rebooted it went back to the green screen and says in yellow: "Invalid primary (LNX) image." and has the same menu as when I rebooted after 501 A.bat
Now what?
EDIT:
So I was sitting there with the green screen/yellow error and decided to boot into recovery again. I then reflashed my custom rom, and did a normal reboot. Everything is working now! My FIRST custom rom after owning android devices since the ancient Motorola i1 way back in the day. I'd still like to know if what I did was right or what happened, so I can detail it in my instructions for my next custom rom project.

timmytutone said:
So I rooted and then flashed a Custom Recovery Image. Then I followed the instructions under the babsector portion of your post. I got to this part: Go back into apx mode and run 501 B.bat, Reboot into recovery and do the wipes, Reboot!!!
I wasn't sure what "do the wipes" referred to so I did ALL the wipes. Cache/Dalvik/Battery/ and Data(?) When I rebooted it went back to the green screen and says in yellow: "Invalid primary (LNX) image." and has the same menu as when I rebooted after 501 A.bat
Now what?
EDIT:
So I was sitting there with the green screen/yellow error and decided to boot into recovery again. I then reflashed my custom rom, and did a normal reboot. Everything is working now! My FIRST custom rom after owning android devices since the ancient Motorola i1 way back in the day. I'd still like to know if what I did was right or what happened, so I can detail it in my instructions for my next custom rom project.
Click to expand...
Click to collapse
Dude I know it's been 4 years since you wrote that but I just wanted to say you really saved my life, THANK YOU!!!
About 2 months ago I tried to unlock my tablet's bootloader but I gave up after reading different articles and obviously ended up with a really bad headache. Last night I realized Android 3 is really old and I almost can't install anything on it. So basically I gave it another shot and been reading and downloading different files for almost 3 hours. Today I managed to unlock bootloader and use your short instruction (more likely a walk-thru that how you fixed your problem) and it worked!!! I owe you man... I owe you
I even took it to so many different mobile centers about 3 weeks ago but they said its files are not anywhere/we can't do it/it's too risky/it's not possible deal with it

Happy to help!

[Beginners Guide] Unlock & Custom ROM your TF300

I have been asked to port my "Beginners Guide" from the TF700 forum for the TF300. Since both tablets are very similar, that was not too hard to do
If I have missed to update a link specific for the TF300, do let me know please.
And the standard disclaimer: I am not responsible if you misunderstand instructions I give here, if my instructions are wrong, if you forget to charge the battery and the tablet dies halfway through a flash or if your house goes up in flames. YOU DO THIS AT YOUR OWN RISK
These instructions assume that you are on the latest Asus bootloader: 10.6.1.27.5
To determine which bootloader you currently have:
From an "Off" state, boot the tablet with Volume Down and Power into the bootloader menu. Read the small script in the upper left. You'll see
US_epad-10.6.1.27.5-20130801" or similar.
US or WW, JP, CN is your SKU or region
10.6.1.27.5 is your bootloader version
20130801 is the build date (and immaterial in most cases).
First things first:
Backup everything on your tablet you care about to an external microSD or your PC. Don't worry about your apps. You can always install them from the Play Store.
This is just common sense. It is not inherently risky to flash custom ROMs. But something can wrong at any time and you have to be careful. If you are, this is a safe procedure.
Basically the process of flashing a custom ROM on the TF300 involves three steps:
1) Unlock the bootloader using Asus' Unlock tool
2) Install a custom recovery on the tablet
3) Flash a custom ROM of your choice using said custom recovery​
Unlocking the bootloader
Your tablet should be fully charged at this point!
Make sure "USB debugging" is checked in Settings > Developer Options (if you don't see it, go to About Tablet and tap 7 times on Build Number)
Go to Asus website: https://www.asus.com/support/Download/28/1/0/9/8BmzkQ4yoz5WzBrW/32/
Choose "Android" for OS and look for the "Utilities" on the resulting page.
Download the Asus Unlock Tool v7 (not v8! It says v7 is for ICS but it'll work fine on JB - see below)
The tool downloads as a .rar file which is an archive you have to decompress. 7zip is a free and very good Windows tool that will do it for you
On your tablet, in Settings > Security check "Unknown Sources"
Copy the .apk you extracted from the .rar archive to your tablet.
Find the apk in your tablet's file browser, tap it and let it install
Open the app and follow the instructions. You will loose your warranty as soon as you click "I agree".
Update 2/15: Google added another wrinkle: It now checks even sideloaded apps and refuses to install them if they are considered not secure. The Unlock tool seems to fail their test. v8 does not install at all anymore. v7 will install if you allow "less secure apps" in your Google account settings. On the web - not your Google account on the tablet
July 2015: And another wrinkel... It seems to be pretty consistent now that the Unlock Tool hangs on the Google account password step. I suspect something changed on the Google side. It probably doesn't allow the tool to check/compare the password anymore. There have been quite a few security changes lately and the unlock tool never gets updated so I suspect that Google now is blocking access by the tool to it's servers.
The work-around is easy enough: Delete the Google account from the tablet (Settings > Accounts), then run the tool again. If that doesn't do it, do a factory reset from Settings, reboot and during the initial setup establish a WiFi connection but skip the google account setup, then run the tool
Click to expand...
Click to collapse
This can be a 5 Minute operation that goes without a hitch or a very frustrating experience with lots of error messages. There is no definite rhyme or reason for this. For some people it works like a charm, for others it works after 15, 25 or 55 attempts, for some never.... This problem is widely discussed on several forums. Google it if you hit that roadblock.
To check if you are unlocked, boot the tablet and read the tiny script. It should say:
The device is unlocked.
Installing a custom recovery on your tablet
I highly recommend you choose TWRP as your custom recovery. If you want CWM, you are on your own.
To push TWRP to your tablet you need to set up "Fastboot" between your tablet and your PC. Fastboot is a protocol that enables you low level access to your tablet.
Practice/Background
Power down your tablet and disconnect it from the dock
Push and hold the Volume Down key (left side of the rocker) and the Power key until you feel the tablet vibrate twice. Let go when you see the tiny script. Read it and it tells you that your tablet is now in fastboot mode and you will see three icons (I assume again you are on a JB 4.2 bootloader. In older bootloaders you had 4 icons and had to select the USB icon to get into fastboot mode):
RCK - (which should be flashing) is your recovery (the stock recovery at this point, but once TWRP is installed this is one way to get into it)
Android - is your system, selecting it boots you back to into your ROM.
Wipe Data - stay away! Especially with custom software installed never, ever use this option!
To toggle between the three icons use Volume Down, to select one use Volume Up. Try it but do not push Volume Up when the 'Wipe data' icon is flashing!​
Installing ADB and fastboot plus the necessary drivers
For a working ADB/fastboot connection from PC to tablet you need:
a) Asus device drivers – if you connect the tablet to your PC and it's recognized as a portable device you should be ok. If not, download the Asus Sync Utility from their support/downloads site and install it to get the drivers, then uninstall the program from your PC if you don't want it. The drivers will stay.
b) Fastboot and ADB drivers which will be installed if you run the tool below.
Windows Vista, 7, 8, 10:
Download and run this cool little tool [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1 - xda-developers (don't forget to hit the Thanks button)
The tool installs the adb and fastboot.exe to a folder on your C:\ drive (look for adb) and the corresponding drivers. Takes about 15 seconds.
On Windows 8 and 10 you need to turn off the driver verification feature. Here's a great video on how to do it:
https://www.youtube.com/watch?v=afrvSGiMAtk
Or - even better - here's a quick command line toggle to achieve the same (thank you @Jack_Hardin):
Jack_Hardin said:
If you're running W10, you can disable Device Driver Signing without following the procedure in the linked video, but by (more simply) right-clicking on the Start button, selecting Command Prompt (Admin) and then typing:
Code:
BCDEDIT /set nointegritychecks ON
Doing the same with OFF at the end of the string, as easy to guess as it looks, will reenable them.
Click to expand...
Click to collapse
Jack_Hardin said:
Win XP (and all other Win versions if the above does not work for some reason)
I recommend the "ADB Install Tool" mentioned above or the 'Minimal ADB Fastboot Tool': [TOOL]Minimal ADB and Fastboot [7-18-13] - xda-developers
Either works fine.
If you need the drivers, get them here and install manually in Device Manager:[ADB/FB/APX Driver] Universal Naked Driver 0.72 (We dont need no stinking HTC Sync) - xda-developers
Win7 and Win8 users seem to have the best luck wth the drivers sbdags provided here: http://forum.xda-developers.com/showthread.php?t=2646279
It's fine if you want to use his Recovery Install Tool from that thread. But I highly recommend you familiarize yourself with basic fastboot commands! There are lots of tuturials all over the web.
Linux:Check out this site https://code.google.com/p/adb-fastboot-install/
iOS:[GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!) - xda-developers or:
http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
The fun begins
Fastboot does not play well with USB 3.0, so use a USB 2.0 port for this. And no hubs and such....
Boot the tablet into fastboot mode and connect it to your computer via the original USB cable
In Windows Explorer navigate to the folder that contains your adb.exe and fastboot.exe
Win 7/8: Shift + right click and select "Open command window here".
For Win XP click here
select 'Run' from the Start menu, type
Code:
cmd
and hit Enter. In the resulting command prompt type
Code:
cd C:\adb\ [I](or whatever the path to your fastboot folder is..)[/I]
In the command window on your PC type:
Code:
fastboot devices
If that command returns a string of numbers and letters, you are good as gold.
Click me: View attachment 3070087
If it returns: "No devices found", fastboot is not working - yet - and you have to troubleshoot.
Getting the correct drivers working can be the hardest part of this exercise. If your computer does not "see" the tablet in fastboot, try to uninstall the existing driver (if any) in Device Manager and manually install the drivers I linked to above. And if Windows does not cooperate at all, PM me and I can hook you up with a Puppy Linux live CD with fastboot/adb set up already.
Let's assume everything is good:
On your computer go here: https://dl.twrp.me/tf300t/
Download the latest version of TWRP.
FYI ONLY: If, for whatever reason, you want to format your data partition:
Formatting /data starting with TWRP 2.7.x and later takes a lot longer than in previous versions (up to 90 minutes). LET IT FINISH. DO NOT INTERRUPT THE FORMATTING.
Rename the file to twrp.blob and place it into the same directory as your fastboot.exe. Note: More recent versions of TWRP download with an .img extension. Leave the extensions as is, rename the first part to watever is easy to type
Again check the connection with
Code:
fastboot devices
If you get the connection, in the command window type:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
or
Code:
fastboot -i 0x0B05 flash recovery twrp.img
This will flash the recovery to the recovery partition
If it is successful type:
Code:
fastboot reboot
and let the tablet boot up normally.
You may get a dialog in TWRP offering to root the stock rom. You can accept or cancel it - doesn't matter. I assume you are going to install a custom rom and they are rooted anyway.
Create a nandroid
Your almost there! You are now on the stock ROM with a custom recovery installed.
Power the tablet down and boot into the bootloader menu with Volume Down and Power buttons.
With RCK flashing, push Volume Up and you should boot into TWRP. Familiarize yourself with the many options of the touch based interface without executing anything yet. TWRP is very user friendly. You basically cannot do anything of consequence "by accident", so don't be shy.
To create your Nandroid (a full system backup) touch "Backup", leave the default selection as they are and swipe the button to create a nandroid of your current system.
This is a very healthy habit to develop: You always want to have a nandroid of your last working system squared away so that you can do a simple restore if you flash something that does not work, or something goes wrong during a flash. With a working recovery and a good nandroid you are minutes away from a working system if you soft brick your tablet.
Hint:
It's a good idea to have at least one good nandroid on external media. Sooner or later you will format your data partition and if you're like me, you may forget to backup your nandroids in the heat of the moment..
Installing a custom ROM
From here on out it's as easy as downloading the installation file of your custom ROM, booting into TWRP, choosing "Install" and navigating to the zip of the ROM you want to flash.
If you see a "signed" in the zip file name (best_rom_ever_signed.zip), make sure you check "verify zip signature" under the "Install" menu. Some devs sign their ROM zips - a better way to ensure file integrity than md5 sum.
Whatever you decide to flash: READ THE OP of the corresponding thread and make sure you have the correct bootloader and the required recovery installed! I can't stress this enough! If you are not sure, DO NOT FLASH!
Look for the ROMs in the Development section of the XDA forum for this tablet: http://forum.xda-developers.com/transformer-tf300t/development
It is mandatory to do a Factory Wipe in TWRP before installing a custom ROM or going from one ROM base to another (a so called clean install).
If you choose 'Wipe' in TWRP, all you have to do is swipe the button - 'Factory Wipe' is the default selection under the 'Wipe' menu. You will loose your apps, but it will not wipe your /data/media/ folder where your files, pictures, etc live.
If you do this right before flashing the custom ROM, make sure you have the zip file of your custom ROM on your microSD - not on your internal SD where it may get wiped....
Once you installed a custom recovery NEVER EVER UNDER ANY CIRCUMSTANCES - AND I REPEAT: NEVER! - use the 'Wipe Data' option from the bootloader menu or the "Factory Reset" option in Settings > Backup&Restore.
In your custom recovery you have the option to wipe, backup and restore every partition on your tablet selectively or collectively. Any wiping, any backup and any restore of the system, data, recovery or boot partitions MUST be done in your recovery (or in fastboot)!
You can safely use Titanium Backup or Asus Backup for apps and settings, but that's it. For everything else use your recovery.
FREE ADVICE
There are alternative methods to flash a recovery to your device using apps like GooManager (currently not supported anyway), TWRP Manager or Flashify from the Play Store which do it right from your tablet. These apps "save you the trouble" of getting ADB and fastboot set up and working on your PC. These methods still exist and they do work - mostly - and if you have root. But I would not recommend them.
If you are not willing to invest the time to learn the basics about ADB and fastboot (google "adb fastboot xda tutorial") and install the necessary drivers on your PC, you should not be flashing anything to your tablet!
GET ADB AND FASTBOOT WORKING!
Sooner or later you will do something stupid (I have done it and so will you) and ADB/fastboot may save your bacon IF you had it working when you didn't really need it.
Hit the 'Thanks' button and rate the thread 5 stars if this helped you
Click to expand...
Click to collapse

Save it for later

Mine

sbdags said:
@stamatis could we sticky this please.
Brilliant post Bernd :good:
Click to expand...
Click to collapse
Can we make that happen here to @stamatis
Thx Josh

Nice one Bernd! :good::good:

boot sequence
Hi,
Is normal to see three TUX and some phrases at the power on ?
Can I hide it ?
tnkx
Nicola

You mean the penguins?
That's normal I'd you're running a Rom that uses _that's preinit scripts. You can't hide them - why would you?

thank you SO much
I love you!
Wow, I've never had so much trouble rooting a device before! And days ago, I rooted my T700 without any problems. So, I guess I should have expected the hubby's TF300T to be problematic! Recoveries didn't work, I tried multiple ones. Eventually, I had a recovery that didn't recognize any partitions. I used fastboot to erase them all and put the stock ROM back on--wouldn't boot up. This thread was an immense help! I've moved the other recoveries and ROMs into my non-working folder!
Thanks again!
Lynne

Awesome
What a well written guide! I have a decent understanding of fastboot and adb (although minimal experience), and I perfectly understood every step.
My advice to all newbies like me.... Read stuff ALL of the way through (and understand it), BEFORE stepping off in it.

ok im a bit lost... i have rooted both Nexus 7s, nook hd and hd+, a tf101, and a few tv boxes.. so im not sure why this is hanging up... im trying to root and install the TWRP recovery on a tf300... followed the instructions and even have the char string that means... every thing should be good to go.... have checked that the twrp is in the dir of adb... but when i try to push the twrp.blob to the tf300, it just give me.. this error..
c:\adb>fastboot devices
015d14febf64041b fastboot
c:\adb>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6800 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.002s
so.. at this point i not sure what else to trouble shoot... the tablet is in fastboot mode.. adb sees the tablet.. at least that is what the char string confirms.... so any help would be very much appreciated.. just a bit lost on this...
chris

scuzzo said:
ok im a bit lost... i have rooted both Nexus 7s, nook hd and hd+, a tf101, and a few tv boxes.. so im not sure why this is hanging up... im trying to root and install the TWRP recovery on a tf300... followed the instructions and even have the char string that means... every thing should be good to go.... have checked that the twrp is in the dir of adb... but when i try to push the twrp.blob to the tf300, it just give me.. this error..
c:\adb>fastboot devices
015d14febf64041b fastboot
c:\adb>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6800 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.002s
so.. at this point i not sure what else to trouble shoot... the tablet is in fastboot mode.. adb sees the tablet.. at least that is what the char string confirms.... so any help would be very much appreciated.. just a bit lost on this...
chris
Click to expand...
Click to collapse
The bootloader is unlocked yes ?
What is your bootloader version ?
Try a different USB port ?
Thx Josh

lj50036 said:
The bootloader is unlocked yes ?
What is your bootloader version ?
Try a different USB port ?
Thx Josh
Click to expand...
Click to collapse
hello,
bootloader is unlocked or at least it says it is at the boot screen.. "your device is unlocked"..
real time... just swapped ports... its says it pushed the recovery.... so... will continue along this path.... and see how it goes.... i think its good to go... just as you suggested... port swap... cool... i bought this just so i could root it and put the kit kat kis rom on it.... thanks for your help and big ups to OP.... great guide ...
thanks again.!

Nice guide!
I've been wanting to put a custom rom on my transformer for a long time. This guide worked like a charm.
The only problem I had was when I tried to flash TWRP recovery, but switching USB port fixed that problem.
I flashed the latest CM12.1 nightly and it works fine.
Many thanks!

Help please, I'm stuck!
I'm trying to flash recovery,
after typing:
fastboot -i 0x0B05 flash recovery twrp.blob
I got this on tablet screen:
"Starting Fastboot USB download protocol"
for about 25-30 already and nothing happens, any ideas?
thanks

You won't see anything on the tablet screen, but what does the command window say?
Go back, read the guide again, it's all in there....
Sent from my K00C using Tapatalk

berndblb said:
You won't see anything on the tablet screen, but what does the command window say?
The command window didn't say anything, just blinking cursor after my command line
Go back, read the guide again, it's all in there....
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Mishka79 said:
I'm trying to flash recovery,
after typing:
fastboot -i 0x0B05 flash recovery twrp.blob
I got this on tablet screen:
"Starting Fastboot USB download protocol"
for about 25-30 already and nothing happens, any ideas?
thanks
Click to expand...
Click to collapse
Thanks,
After writing the question, I've restarted my tablet and did all the steps again.
The second time everything worked as it should. :good:
thanks for your great guide

Really great guide
Amazing guide thanks for the help

Thank you for this good tutorial but I have one question.
I'm a newbie here, here is my dilemma: I've flashed CM android 5.1.1 successfully from stock 4.2. (Thanks for this detailed tutorial), but I lost my root privileges, now I can't use my root apps. How do I apply root to this ROM? My device is an ASUS TF300T. I've tried Kingo Root and King Root but no success.
I would really appreciate your help and inputs.
Cheers!

ANDROIDYER said:
I'm a newbie here, here is my dilemma: I've flashed CM android 5.1.1 successfully from stock 4.2. (Thanks for this detailed tutorial), but I lost my root privileges, now I can't use my root apps. How do I apply root to this ROM? My device is an ASUS TF300T. I've tried Kingo Root and King Root but no success.
I would really appreciate your help and inputs.
Cheers!
Click to expand...
Click to collapse
I have not used CM in quite a while but I think you have to enable root in Developer Options. I think it is not enabled by default.
If hat does not work you can go to Chainfire's website and download the flashable SuperSU and just flash it in recovery

Thanks and a couple of notes on TF300T
Thanks so much for the great guide. My 300TF was nearly bricked due to slowness and freeze-ups. I'd stopped using it. The process worked and am now running KatKiss. Couple of problems and their solutions for anyone who may have the 300TF:
-When trying to "Unlock Bootloader" I kept getting to "enter Google password" but when I did so (correctly) it was not accepted. The solution was to do another factory reset and NOT install google services. Didn't ask for password after that.
-Used fastboot command line to install "twrp.blob" but nothing happened and it timed out. I had to take out other usb connect programs first (in my case "easy-tether" and my LG phone connect app.) After that everything went as per your guide.
Thanks again
Geneg

Bricked while trying to install Full Android rom.. Now Boot loop into twrp. Pls help.

Well,
basically subject says all.
I tried to install zulu99 Full android rom 2.1.
basically 'fastboot flash system system.img worked' but 'fastboot -w' failed ('no space left' error).
So I rebooted hoping to reflash a nandroid backup but now the box keeps on rebooting into twrp trying to wipe cache and data but failing. after a while it stops and black screen appears.
I attach the screen it presents when reboots.
Please tell me I didn't trash 220 euros.
Thanks.

puppinoo said:
Well,
basically subject says all.
I tried to install zulu99 Full android rom 2.1.
basically 'fastboot flash system system.img worked' but 'fastboot -w' failed ('no space left' error).
So I rebooted hoping to reflash a nandroid backup but now the box keeps on rebooting into twrp trying to wipe cache and data but failing. after a while it stops and black screen appears.
I attach the screen it presents when reboots.
Please tell me I didn't trash 220 euros.
Thanks.
Click to expand...
Click to collapse
Theres a hardware method to boot into the bootloader, this i think you can test, just to see if you can at least get into bootloader.....nothing more
Details in the official nvidia link
http://nv-tegra.nvidia.com/gitweb/?...ob_plain;f=README_SHIELD;hb=rel-22r18-partner
There's a thread here on the "questions" thread with users reporting that the timing of the hardware method can be a pain in the you know where.............might be worth looking into that thread for their experiences in booting the bootloader using the hardware method
Disclaimer:If your brave enough to risk a brick, read on
I suspect this might be the 2.1 stock/twrp issue........current twrp, or current stock dont play nice
Its a good sign that SOMETHINGS loading, rather then NOTHING booting, but dont know if theirs a solution
My analysis of the situation, of what little i know, the -w (wipe) command was expecting a stock recovery but instead got twrp, which is why your in this situation.........maybe, i stress maybe, if you could reflash stock again, you might be able to boot into android stock again and try full android again, leaving out twrp, until a twrp fix is found
Edit
Saying that, if the bootloader is, as i suspect, now using twrp to flash things, then you might be boned....... im no expert on bootloaders, stock "recoveries" and how they work, so i might be wrong on that
Reports around here say that 1.3 stock firmware is the recommended back to stock firmware, apparently, flashing any other firmware versions, bring their own issues.............
From 1.3 stock, use nvidias official OTA to upgrade from 1.3 stock, to 2.1 stock, then try 2.1 full android again...........note, i dont think you can skip firmwares i.e. you have to upgrade to 1.4, then to 2.0, then to 2.1, alot of downloading.......the OTA does'nt give you any other choice
Before doing anything that ive suggested, wait till someone with more experience to come along........i dont want to be responsible for you fully bricking your shield..........just wanna give you an idea of what i think has happened
If worse comes to worse, if you have warrenty, get a replacement
Gd luck........remember, this is an analysis of your predicament of what i THINK might of happened, and what steps, i likely might of entertained.......after looking into it more thouroughly, knowing that i could get a replacement if it went downhill.........so your mileage might vary
Edits
Crappy grammer, further musings, clarifications

Thanks.[/QUOTE]
puppinoo said:
Well,
basically subject says all.
I tried to install zulu99 Full android rom 2.1.
basically 'fastboot flash system system.img worked' but 'fastboot -w' failed ('no space left' error).
So I rebooted hoping to reflash a nandroid backup but now the box keeps on rebooting into twrp trying to wipe cache and data but failing. after a while it stops and black screen appears.
I attach the screen it presents when reboots.
Please tell me I didn't trash 220 euros.
Thanks.
Click to expand...
Click to collapse
I had something similar about... shield goes booting in recovery and trying delete some cache and keeps repeat and repeat
Hardware boot in fastboot / bootloader mode
Accessing Bootloader via Hardware
Unplug power from the Shield Android TV. *
Wait a few seconds.
Hold down the power button.
Plug in power
Count to three
Release the power button
You should see the bootloader screen.
If you hold it down too long or not long enough, it simply doesn’t work.
Restore Shield Android TV to Stock
P.s. Personally me I followed this instructions and kind of magically got it in bootloader mode. First done by instruction and then just gave up and pressed randomly and fastboot screen appear. Thanks God I had to done only once, if I would do again I wouldn't had patients
Good luck with this, hope you will get sorted
Here will be link about where I got instructions about hardware boot
http://nvidiashieldzone.com/index.php/shield-android-tv/root-shield-android-tv/
Sent from my Nokia 3310 using free xda app

Thanks a lot fro your help.
I was able to put the box in fastboot mode.
Since I'm not that expert can you tell me where and which rom I have to download (I have a french 16gb version of the box).
Then I'd need to know exactly what commands to performs (even a link to a tutorial is fine).
I really appreciate your help. It seems I can (hopefully) save the box.
EDIT: The fastboot command gave me a (not enough space) when I bricked the box. Is there a risk it could happen again while flashing stock? No idea how much space I have left on the box really.
EDIT2: I found this page: https://developer.nvidia.com/shield-open-source
and I'm downloading this rom called nv-recovery-image-shield-atv-upgrade2_1.zip
and Intend to follow these instructions: http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
Can anyone please confirm I'm doing right?

EDIT with joy : I followed all the steps using that rom and it seems everything worked. I reconfiguring the box now. Thanks for help.
basically the procedure I intend to follow is this part (please confirm it's ok):
To flash this recovery image to your SHIELD, run the following commands from
the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader. Get
DTB file name to use for flashing for your product(see below):
P.s. maybe Since past fastboot commands failed and I only flashed system from zulu99 I could skip the 'fastboot flash boot boot.img' command so if it fails again I still can attempt the fastboot process again?
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb <DTB file name>

puppinoo said:
Thanks a lot fro your help.
I was able to put the box in fastboot mode.
Since I'm not that expert can you tell me where and which rom I have to download (I have a french 16gb version of the box).
Then I'd need to know exactly what commands to performs (even a link to a tutorial is fine).
I really appreciate your help. It seems I can (hopefully) save the box.
EDIT: The fastboot command gave me a (not enough space) when I bricked the box. Is there a risk it could happen again while flashing stock? No idea how much space I have left on the box really.
EDIT2: I found this page: https://developer.nvidia.com/shield-open-source
and I'm downloading this rom called nv-recovery-image-shield-atv-upgrade2_1.zip
and Intend to follow these instructions: http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
Can anyone please confirm I'm doing right?
Click to expand...
Click to collapse
You are on the right way with those links
P.s. You can do manual one by one entering or paste and copy those commands or (I'm doing) drag and drop file "flash-all.bat" on cmd previous opened there where you have abd/fastboot etc files and extracted RIGHT FIRMWARE (like shift and right click mouse "open command prompt here"
And after this all sit down and relax
Anyway you are on the right way.
P.s. Hope you download adb fastboot drivers somewhere from Internet !?!
Sent from my Nokia 3310 using free xda app

Stuck on Bootloop and Flashtool doesn't work...any XDA superheroes out there?

I followed step by step: https://clickitornot.com/install-twrp-recovery-and-root-sony-xperia-x-compact/
(the xda guides lingo was hard to understand and follow, I'm a noob at rooting sony phones. I don't have previous knowledge so I followed the above)
-Got stuck in TWRP recovery mode after following the link posted.
-Looked into it and read something about a boot.img missing?
-Downloaded boot.img from here: https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479
-Flashed recovery on boot_32.img via TWRP, now screen stays at white Sony logo. Cannot go into TWRP at all, computer doesn't recognize phone and Sony flash tools does not recognize phone.
I just need this phone to root and turn on so I can get my old photos and conversation back. :crying:
Been stuck for 12 hours...any help is much appreciated!

1 - what do you ultimately want, rooted stock rom, custom rom, or...?
2 - what was the state of your phone when you started, (fully stock, which fw version, etc)?
3 - Did you do anything else to it besides flashing twrp and flashing boot.img?

levone1 said:
1 - what do you ultimately want, rooted stock rom, custom rom, or...?
2 - what was the state of your phone when you started, (fully stock, which fw version, etc)?
3 - Did you do anything else to it besides flashing twrp and flashing boot.img?
Click to expand...
Click to collapse
1. Anything, I simply just need it to work so I can use a software to get my lost data. In order to get my data back the phone needs to be rooted under the prerequisites for the Dr. Fone software.
2.Fully stock android 8.0
3. No, it was fine and I went through dozens of threads and youtube tutorials. It kept going into TWRP exclusively until I flashed boot.img now it just boot loops or crashes on the white sony screen.
(BTW, my phone finally has been recognized by Flash Tools (Emma). I have updated it via Emma but it has done absolutely nothing.

ThisAintEz said:
1. Anything, I simply just need it to work so I can use a software to get my lost data. In order to get my data back the phone needs to be rooted under the prerequisites for the Dr. Fone software.
2.Fully stock android 8.0
3. No, it was fine and I went through dozens of threads and youtube tutorials. It kept going into TWRP exclusively until I flashed boot.img now it just boot loops or crashes on the white sony screen.
(BTW, my phone finally has been recognized by Flash Tools (Emma). I have updated it via Emma but it has done absolutely nothing.
Click to expand...
Click to collapse
So the whole Emma process completed successfully, but the phone still won't boot? That's strange, because Emma usually overrides everything, (including your userdata, I think, so if you wanted to save it, that may have been the wrong thing to do). If all you did was flash a bad boot img, then re-flashing stock fw should solve the problem, but you might lose your data with Emma, so Androxyde Flashtool might be better choice, since it gives you the option.
Did you unlock the bootloader? If not, then nothing is going to work. If you did, then it will be easy to get the phone booted again...

levone1 said:
So the whole Emma process completed successfully, but the phone still won't boot? That's strange, because Emma usually overrides everything, (including your userdata, I think, so if you wanted to save it, that may have been the wrong thing to do). If all you did was flash a bad boot img, then re-flashing stock fw should solve the problem, but you might lose your data with Emma, so Androxyde Flashtool might be better choice, since it gives you the option.
Did you unlock the bootloader? If not, then nothing is going to work. If you did, then it will be easy to get the phone booted again...
Click to expand...
Click to collapse
The phone itself has been factory reset (long story short x compact said my password was incorrect and factory reset, itself after numerous tries, even though I only have one password) so I know my info is gone but the software can get the most of the things I want.
Yes, boot loader is unlocked. I have basically rooted it but the last step of actually getting to use it is out of reach.

ThisAintEz said:
The phone itself has been factory reset (long story short x compact said my password was incorrect and factory reset, itself after numerous tries, even though I only have one password) so I know my info is gone but the software can get the most of the things I want.
Yes, boot loader is unlocked. I have basically rooted it but the last step of actually getting to use it is out of reach.
Click to expand...
Click to collapse
For TWRP recovery, you need to flash via fastboot. I wasn't clear what you were saying about how you did it before. You should,
- Download TWRP img file (there is official TWRP for xc, so download the latest from TWRP site)
- Open command prompt in the directory you downloaded it to
- Connect the phone in fastboot mode, (power off > hold volume up while connecting cable and don't let go of the button until you see blue led)
- Type
Code:
fastboot flash recovery (name of file).img
Then you can boot into recovery by powering off, and holding volume down while powering on. Then do a reset in recovery.
Now you'll need to flash a boot img...
You said it was stock 8.0, but do you know if it was the latest update? (fw ending in. 118) If so, and if your system files are still intact, then you should be able to download this - https://mega.nz/#!14VkzCCB!GK-KEv0A-ZyhysXc1-IusyJjJEB-D5ZWOLm1DRt31tA - (it's a boot img), and flash it with fastboot. So,
- Download the boot img file
- Open a command prompt in the directory you downloaded it
- Connect the phone in fastboot mode, (power off > hold volume up while connecting cable and don't let go of the button until you see blue led)
- Type in command prompt,
Code:
fastboot flash boot (name of file).img
- Reboot
I'm assuming that since you used Emma already that you have drivers installed, so should work. If the commands complete successfully, but your phone still doesn't boot, then probably system is messed up, and you'll have to flash a new rom.

levone1 said:
For TWRP recovery, you need to flash via fastboot. I wasn't clear what you were saying about how you did it before. You should,
- Download TWRP img file (there is official TWRP for xc, so download the latest from TWRP site)
- Open command prompt in the directory you downloaded it to
- Connect the phone in fastboot mode, (power off > hold volume up while connecting cable and don't let go of the button until you see blue led)
- Type
Code:
fastboot flash recovery (name of file).img
Then you can boot into recovery by powering off, and holding volume down while powering on. Then do a reset in recovery.
Now you'll need to flash a boot img...
You said it was stock 8.0, but do you know if it was the latest update? (fw ending in. 118) If so, and if your system files are still intact, then you should be able to download this - https://mega.nz/#!14VkzCCB!GK-KEv0A-ZyhysXc1-IusyJjJEB-D5ZWOLm1DRt31tA - (it's a boot img), and flash it with fastboot. So,
- Download the boot img file
- Open a command prompt in the directory you downloaded it
- Connect the phone in fastboot mode, (power off > hold volume up while connecting cable and don't let go of the button until you see blue led)
- Type in command prompt,
Code:
fastboot flash boot (name of file).img
- Reboot
I'm assuming that since you used Emma already that you have drivers installed, so should work. If the commands complete successfully, but your phone still doesn't boot, then probably system is messed up, and you'll have to flash a new rom.
Click to expand...
Click to collapse
Thank you, the good news is I can finally get back into TWRP, so that's a relief! I appreciate you for saving me there!
I followed the instructions with the boot.img with the following script
max download size of 536870912 bytes
sending 'boot' (17220 KB)...
OKAY [ 0.556s]
writing 'boot'...
OKAY [ 0.113s]
finished. total time: 0.673s
But I'm back to square one with the screen prompt "your devices has been unlocked and cant be trusted. Your device will boot in 5 sec" with the Sony white screen back to the "your device has been unlocked" screen and then it freezes at the Sony white screen. The only way i can turn off my phone from here is Power button + volume up

ThisAintEz said:
Thank you, the good news is I can finally get back into TWRP, so that's a relief! I appreciate you for saving me there!
I followed the instructions with the boot.img with the following script
max download size of 536870912 bytes
sending 'boot' (17220 KB)...
OKAY [ 0.556s]
writing 'boot'...
OKAY [ 0.113s]
finished. total time: 0.673s
But I'm back to square one with the screen prompt "your devices has been unlocked and cant be trusted. Your device will boot in 5 sec" with the Sony white screen back to the "your device has been unlocked" screen and then it freezes at the Sony white screen. The only way i can turn off my phone from here is Power button + volume up
Click to expand...
Click to collapse
So now you can just decide if you want to go the route of stock rom or custom. Quickest choice to get the phone booted would probably be Omni or something. Just download the rom, download the oem file, and flash in fastboot. Check the Omni threads in "Roms" forum... If you wanted to go stock, I would suggest Androxyde Flashtool, but would be a few more steps... Or you could try Emma again...

levone1 said:
So now you can just decide if you want to go the route of stock rom or custom. Quickest choice to get the phone booted would probably be Omni or something. Just download the rom, download the oem file, and flash in fastboot. Check the Omni threads in "Roms" forum... If you wanted to go stock, I would suggest Androxyde Flashtool, but would be a few more steps... Or you could try Emma again...
Click to expand...
Click to collapse
I tried Emma again but my phone is still frozen on the white Sony screen. I checked out the ROM threads but the "download weekly" links are down for both Pie 9.0 and Oreo 8.1

ThisAintEz said:
I tried Emma again but my phone is still frozen on the white Sony screen. I checked out the ROM threads but the "download weekly" links are down for both Pie 9.0 and Oreo 8.1
Click to expand...
Click to collapse
Strange - I wonder what's going on... I might have a zip I can upload. Meanwhile, maybe try Lineage - https://forum.xda-developers.com/x-compact/development/rom-lineageos-16-0-xperia-x-compact-t4080903

levone1 said:
Strange - I wonder what's going on... I might have a zip I can upload. Meanwhile, maybe try Lineage - https://forum.xda-developers.com/x-compact/development/rom-lineageos-16-0-xperia-x-compact-t4080903
Click to expand...
Click to collapse
Thank you for your help! I checked out the thread but I'm not advanced enough to understand the steps without it being written out as I'm still new to this. Is their any links or tutorials you would recommend? My apologies!

ThisAintEz said:
Thank you for your help! I checked out the thread but I'm not advanced enough to understand the steps without it being written out as I'm still new to this. Is their any links or tutorials you would recommend? My apologies!
Click to expand...
Click to collapse
- Download the zip - https://drive.google.com/open?id=14iXmvLOMXLoZdJoCahcRhBzbUr1Eu7gw (There are 2 options, just pick one - one's a little newer)
- Copy to phone's SD card
- Boot to recovery
- Choose "wipe data/factory reset"
- Choose "install", and select the zip file you downloaded
- Reboot
There are more options, but I think you want to just get the phone to boot at this point. You can do more later if you want...
BTW - what is happening when you flash with Emma? I haven't seen it ever flash successfully, but not work on the phone. Are you getting errors?

levone1 said:
- Download the zip - https://drive.google.com/open?id=14iXmvLOMXLoZdJoCahcRhBzbUr1Eu7gw (There are 2 options, just pick one - one's a little newer)
- Copy to phone's SD card
- Boot to recovery
- Choose "wipe data/factory reset"
- Choose "install", and select the zip file you downloaded
- Reboot
There are more options, but I think you want to just get the phone to boot at this point. You can do more later if you want...
BTW - what is happening when you flash with Emma? I haven't seen it ever flash successfully, but not work on the phone. Are you getting errors?
Click to expand...
Click to collapse
Much appreciated! I will try that out soon. Regarding Emma it seems pretty useless, unless I'm missing something. Every time I use it, it says it's successful but nothing changes.

LEVONE1 YOU ARE THE MAN!!! I cannot thank you enough! It worked! You made my day, I appreciate your patience and willingness to help a stranger out even when you didn't have to!

ThisAintEz said:
LEVONE1 YOU ARE THE MAN!!! I cannot thank you enough! It worked! You made my day, I appreciate your patience and willingness to help a stranger out even when you didn't have to!
Click to expand...
Click to collapse
Glad to hear it... It's been done for me more than once, so....
Maybe your happy with Lineage, but if you're feeling ambitious, you can start messing around with Androxyde Flashtool, and getting back to stock, and you can try my eXistenZ port - https://forum.xda-developers.com/x-compact/themes/existenz-xc-t3867917 - I think eXistenZ is the best rom for this phone, (probably for Sony phones overall). The downside is that it is based on stock, so no updates since 2018 for XC...
The processes are a bit more complicated, so might take some time / learning to get it down, but with TWRP, you can always make a quick backup, and flash right back to where you were any time...

levone1 said:
Glad to hear it... It's been done for me more than once, so....
Maybe your happy with Lineage, but if you're feeling ambitious, you can start messing around with Androxyde Flashtool, and getting back to stock, and you can try my eXistenZ port - https://forum.xda-developers.com/x-compact/themes/existenz-xc-t3867917 - I think eXistenZ is the best rom for this phone, (probably for Sony phones overall). The downside is that it is based on stock, so no updates since 2018 for XC...
The processes are a bit more complicated, so might take some time / learning to get it down, but with TWRP, you can always make a quick backup, and flash right back to where you were any time...
Click to expand...
Click to collapse
Will do. Cheers!