Database Users

[WORK IN PROGRESS] Current state of root / flashing / nvflash (updated May 6th)

As of today 6th May 2011 the Eee Pad is pretty much cracked. We can flash boot and recovery and have a working root and unsecure boot and koush's Clockworkmod recovery.
The one thing we can't do is use nvflash to try custom bootloaders etc. This is because APX has been locked with a SBK and we have currently no method to get around that. Thus nvflash will fail with the error
Code:
rcm version 0X4
Command send failed (usb write failed)
It is interesting to note that the ASUS German blog claims that the bootloader and root privileges are both openly accessible, which (at the moment) is not true.
Here a few key combinations for anyone interested:
VOL_DOWN + POWER (continue holding VOL_DOWN when it starts booting until you get a prompt) = Bootloader which offers two prompted options: (1) Recovery if you press VOL_UP within 5 seconds or (2) Data wipe if you press VOL_UP later. None of these seem to offer any USB devices like fastboot etc.
VOL_UP + POWER or VOL_DOWN + VOL_UP + PLUG IN USB = NVFlash mode. It clearly is the NVFlash APX device that we see appearing, but it barfs as soon as we run any sort of nvflash on it (Many Windows and Linux versions have been tried). Please note that in this mode the screen stays completely blank and the only way to get out of it is the following option:
Hold POWER for ~10s = Forced power off. This always helps if you are stuck in some weird mode and nothing on the screen

I'll repost this in here then, as it adds a bit more info to the post above:
-Volume down button + power button for 5 secs = Life surges into the pad
Eee Pad logo + Asus logo ... keep holding buttons for 1 more sec = New screen with:
Android_WWeeepad-user bootloader < e> released by ww_epad-8.2.2.6.1-20110325".
Checking for android ota recovery
Checking for RCK... Press key <VOLUME_UP> in 5 secs to enter RCK
-Pressing up = next screen below
Booting recovery Kernal Image
Image in middle of screen and some sort of loading bar
(then goes straight to)
Exclamation mark (!) + android logo on screen
-Not touching any other buttons = screen then goes to:
Press <VOL_UP> to execute or <VOL_DOWN> to cancel wiping data (with a pulsing "Wipe data" icon in middle of screen)
-Pressing volume up = well... I didnt do that for obvious reasons.
-Pressing volume down = boots linux... and back into honeycomb normally.
-Volume up + power button dont seem to do anything.
-Power button for 5 secs = normal boot up.
-An 8-9 second hold down of the power button seems to switch it off from any screen.

'Rooting / Flashing'
I was expecting to see an HD link to some video's from spankwire

Maybe a stupid question but we do not need the dock to get an adb shell isnt it?

Great find
Need to learn about Android now, I'll chuck this in the reference thread (When i make one )
Thanks

Cpasjuste said:
Maybe a stupid question but we do not need the dock to get an adb shell isnt it?
Click to expand...
Click to collapse
No, adb works fine without the dock. Now we just want to change that $ to a #

stridger said:
No, adb works fine without the dock. Now we just want to change that $ to a #
Click to expand...
Click to collapse
Hehe thats great, just ordered one an should get it around the 5 april
The # will be easy to get and will be available very soon believe me. Ill also make an oc/uv kernel !

The root from me and paul should be out late this week early next week
its not perfect but it will do for now

Thanks.

Apache14 said:
The root from me and paul should be out late this week early next week
its not perfect but it will do for now
Click to expand...
Click to collapse
Great work
I'll create a Sticky / Rollup thread later this week.
Badwolve1

Can some one run fastboot and type...
"fastboot getvar secure"
"fastboot getvar all"

zambezy said:
Can some one run fastboot and type...
"fastboot getvar secure"
"fastboot getvar all"
Click to expand...
Click to collapse
We cannot activate fastboot on this device until we have the right nvflash tool... Once we have nvflash there shouldn't be any further obstacles.

What NVFlash commands have you tried... can you even run these?
nvflash --bl fastboot.bin --go -w
nvflash --bl fastboot.stock.bin --go -w
You would need those files in your directory... Its like booting image with fastboot without writing....

zambezy said:
What NVFlash commands have you tried... can you even run these?
nvflash --bl fastboot.bin --go -w
nvflash --bl fastboot.stock.bin --go -w
You would need those files in your directory... Its like booting image with fastboot without writing....
Click to expand...
Click to collapse
As I said, nvflash doesn't work. Not a single command.

So it doesn't seem that open after all. Nvflash has not changed this much. Have you only ran those commands in Nvflash mode.
Is the device recognised when you boot in recovery.
Sent from my ADR6400L using XDA App

zambezy said:
So it doesn't seem that open after all. Nvflash has not changed this much.
Click to expand...
Click to collapse
yes, it's either locked, or as simple as a new revision of nvflash is required.
Have you only ran those commands in Nvflash mode.
Is the device recognised when you boot in recovery.
Click to expand...
Click to collapse
Recovery and normal boot both offer ADB. We get the right device in NVFlash mode, it's just the software we have cannot talk to it after the first few bytes...

Thanks
Enviado desde mi Desire HD usando Tapatalk

My current root method will be out today
p.s. its nothing special .... in fact stupidly simple

Apache14 said:
My current root method will be out today
p.s. its nothing special .... in fact stupidly simple
Click to expand...
Click to collapse
Sweet Jesus!!!

I know Apache14 has already said this but Paul's just posted on twitter "Transformer ClockworkMod Beta and MCR Beta online this afternoon... @BumbleDroid is posting root too. ".
Very fast well done guys!

[Q] cLK Fastboot Ignores that Recovery is Installed

Hi guys,
First, I'd like to point out this is my very first post here! And nice noob video, very entertaining
Anyway, before I get yelled at...
I've looked everywhere on this website for a solution, and nothing has worked, and I know there are many people with the same problem. This isn't a Noob question (though I'm not a tech savvy,) but rather a deep mystery that's frustrating.
Have you ever had a time where you do exactly what you've been told, yet you don't get the results expected? Well this is precisely the same thing.
I'm using a T-Mobile HTC HD2 and I'm trying to install a custom Android NAND ROM on it, with cLK as the bootloader.
Whenever I try running CWM through cLK (held the home button as phone rebooted), it goes and stays on fastboot as if CWM was never installed (which I'm sure I did.)
Actually, it doesn't ignore the installed CWM completely, because if I boot with the home button held, as opposed to not, I notice some extra lines in the bootloader..
I'm gonna copy down exactly what is on my HD2's screen right now (even though I could be wasting my time. But just in case .) My phone is connected to my computer via USB at the moment.
I bolded the lines that caught my eye, though I don't know what to do about them:
cedesmith's LK (CLK) v1.4.0.1
[180] 4.0.1
[180] boot reason 6
[180] android reboot reason 0
[180] load address 11800000
[190] flash init
[190] nandid: 0x5551b3ad maker=0xad device=0xb3 page_size=2048
[200] spare_size=64 block_size=131072 num_blocks=8192
[200] nandcfg: aad40000 6744e (initial)
[200] nandcfg: ea5400c0 6744e (used)
[200] ptn 0 name='misc' start=00000219 len=00000008 end=00000221
[200] ptn 1 name='recovery' start=00000221 len=00000028 end=00000249
[200] ptn 2 name='boot' start=00000249 len=00000028 end=00000271
[200] ptn 3 name='system' start=00000271 len=000004b0 end=00000721
[200] ptn 4 name='cache' start=00000721 len=00000028 end=00000749
[200] ptn 5 name='userdata' start=00000749 len=000017f8 end=00001f41
[210] flash_read misc partition
[210] flash_read: misc 800 800
[700] flash_read_image: failed (511 errors)
[700] ERROR: Cannot read recovery_header
[700] flash_read: boot 0 800
[2330] flash_read_image: failed (2560 errors)
[2330] ERROR: Cannot read boot image header
[2330] ERROR: Could not do normal boot. Reverting to fastboot mode.
[2340] USB init ept @ 0x28023000
[2380] fastboot_init()
[2380] udc_start()
[2380] -- suspend --
[2500] -- reset --
[2500] -- portchange --
[2670] -- reset --
[2670] -- portchange --
[3020] fastboot: processing commands
Click to expand...
Click to collapse
I'm REALLY sure I did the install-Android-into-HD2 process correctly. But I'll tell you guys everything I did:
1. I downloaded HD2 Toolkit (4.1), which a lot of people had success installing their ROMs with.
2. I then installed HD2 Toolkit using its setup program on my computer.
3. Then, opened the HD2 Toolkit on my computer.
4. Afterwards, I clicked the Wipe (Task29) button located on the lower right of the Toolkit.
5. I connected HD2 device to my computer through its USB cable.
6. I immediately hold the Volume Down button on the device as it automatically boots up (because that's what happens when I connect it while it's shut down.)
7. Multicolored screen (red, green, blue, then white) shows up on my HD2's screen.
8. On it, it says that I have HSPL 2.08 installed (yes, unmistakably HSPL, not SPL.)
9. I turned my focus back to the computer, and continued with the Wipe process.
10. The HD2 showed a progress bar and I waited until it reached 100%, and rebooted by itself. I help the Volume Down button once again in preparation for the next step.
11. Once I was finished with the "Wipe (Task29)" process, I select the "cLK repartition" button at the top of the Toolkit window, which was the next step.
*This button both installs and repartitions cLK, I don't know what that means but that's what it said on the Toolkit's thread.
12. I then chose "150 MB" inside the selection box labeled "Choose System Partition Size (cLK)."
13. Directly below the same box, I check the 5MB below a label "Cache Size."
14. I then click Install to finally begin the cLK installation&repartition process.
15. With the multicolored screen already shown up on my HD2, I began the 2nd process.
16. Just like the "Wipe (Task29)" process, no confusion occured. The similar-looking progress bar as earlier reached 100%, and the device reboots once again. This time, I DIDN'T hold the Volume Down button but held the Back button, as it's cLK's fastboot's turn to do its job (which means no multicolored screen this time, just white text on a completely black background.)
17. I take a glance at my device. The USB cable is still connected.
18. Turning my focus back to the computer (Toolbox once again, to be exact,) I click on the "cLK Install Recovery," confidently predicting that nothing will go wrong, because I followed all the steps, so far, without any confusion.
19. A command window pops up (on my computer,) and tells me to press a key to begin the CWM Recovery installation process.
20. I press the spacebar button.
21. The installation process begins.
22. In under 5 seconds, the process is finished, and the command window tells me to press any key once again to reboot my phone.
23. I press the spacebar button once again, and the command window closes on its own, and the phone reboots.
24. At the same time, I start holding the home button on my device (the tutorial mentioned that doing that while it's rebooting will launch CWM Recovery)
25. To my surprise, the set of lines above (in the quote) with the errors happen. CWM Recovery was never launched.
This is all the details I can think off that I can give you. The device handles a Custom ROM with MAGLDR 1.13 just fine, so I don't think anything's broken on my device.
Can anyone solve my little problem I got going on? Thanks a bunch

maybe an issue with the toolkit
personally i just just fastboot to install CWM

It's not a toolkit problem
I attempted to reinstall cLK once again (after Task29) using a couple more tutorials that I found in this website. I noticed these tutorials were all very similar, they all basically told me to install the same things the same way as I did the first time, but I still end up in the same fastboot rut.

then its something you are doing wrong
download the fastboot adb drivers
restart the phone in fastboot mode
flash using the fastboot flash recovery command

Richy99 said:
then its something you are doing wrong
download the fastboot adb drivers
restart the phone in fastboot mode
flash using the fastboot flash recovery command
Click to expand...
Click to collapse
The fastboot adb drivers?
I saw a google-usb_driver folder or zip in the tutorials, and I installed them through the "android_winusb.inf" file within them, if that's what you mean?

yes that zip, boot the phone into fastboot mode and then use the command promt to use the fastboot commands

I remember trying that once when I was going through other tutorials. Anytime I typed a command in for it (after Shift+Right clicking in the folder where the recovery img file is and click "open command prompt here") it'd say something like "there is no external fastboot connection" or something like that.
I don't know the exact words, but maybe that relates to the first current problem I'm having.
Two tutorials suggested that cmd method, and both times the same "there is no external connection" message would show up on the cmd. Again, I paid a lot of attention to those tutorials, and there were two of them. Nothing was too complicated to understand, so I'm absolutely sure I haven't messed up in following the steps, at least.
I also saw somewhere it might be a radio problem, so I downloaded two radios and experimented with them both. For each of them, nothing was fixed. (I tried 2.07.50.27_2 then 2.09.50.29_2) So the same fastboot problem persists.
EDIT: Is there a command on cmd to make fastboot go to recovery without pressing the home button?

the home button is for CWM and back arrow boots it into fastboot mode, afaik the phone cannot be put into fastboot mode without this method
it sounds like the drivers are not correctly installed if it is failing to find the phone if you are getting a conenction error
your radio has to be 2.08 and above for android to work properly from what i have read

I am also facing the same issue. Phone is HD2 and was working earlier with MAGLDR but it got corrupted and could not load android so decided to switch to cLK.
when try to load into CWM by holding the home button it loads with one error. As mentioned in the first post the first error but not the second one. Then it just reboots itself again but never goes into the recovery.
I used fastboot to flash the recovery and got the success message on the PC screen and also the phone gets rebooted everytime i try to reflash the recovery.
But when i type the command
fastboot devices
nothing is displayed.
It seems like the device is not connected then how come the recovery is flashed from the fastboot menu.
I checked in the computer management- devices and I see the Android phone without the "!" mark signifying that the fastboot drivers are installed properly.
Please help.
Got it resolved. Used HD2 toolkit to flash the cLK recovery.

[Q] Accessing CWM from powerd-off

Hi! Is there any way for me to access the CWM from powerd-off mode? My ViewPad 10s has just stopped booting into Android, and it's kinda frustrating. I'm currently running JB Beta 3 and was hoping that I could flash the Beta 5 via CWM, so I don't lose my data. Or can I make the NVFlash version keep my data in one or another way?

I don't think you can get into recovery from boot with these tablets. Best bet is to remove the micro sd card and back up the information that you can. Then reinstall using nv flash. And try and restore and data you can that way.
Sent from my Galaxy Nexus using Tapatalk 2

2minuutes said:
Hi! Is there any way for me to access the CWM from powerd-off mode? My ViewPad 10s has just stopped booting into Android, and it's kinda frustrating. I'm currently running JB Beta 3 and was hoping that I could flash the Beta 5 via CWM, so I don't lose my data. Or can I make the NVFlash version keep my data in one or another way?
Click to expand...
Click to collapse
(Probably no use to you now but may help others...) You could try and flash recovery.img to the boot partition via nvflash:
sudo nvflash --bl bootloader.bin --download 7 recovery.img from linux or
nvflash.exe --bl bootloader.bin --download 7 recovery.img from windows

recovery?
the only thing i know you can do from power off is enter recovery mode, connect your vega to a pc by a usb cable..
Hold the power button, and count 6 seconds, after 6 seconds the screen will blink off, at this exact point release the power button and begin holding the back button for 6 seconds, after those 6 seconds keep the button held but hold the power button also for 2 seconds, so both are pressed, after those 2 seconds you should see the safely remove icon pop up in your startbar (like when you plug in a usb stick) and then let go of back, wait a second and let go of power
NOTE THIS WORKS ON ALL ROMS
at this point the screen will be blank but if you unplug every usb device but the vega cable, and the safely remove is still there then its in recovery.
if you havent used recovery mode before then install the vega recovry drivers off the myadventvega website by opening device manager, clicking your vega (should have a yellow triangle with a ! next to the icon) and click install driver, choose not to search online, say you have a CD or files, and point it to the folder which you downloaded from myadventvega [NOTE NOT THE FOLDER INSIDE THE FOLDER YOU DOWNLOADED< JUST THE FOLDER WITH TWO OTHER FOLDERS INSIDE IT.}
after you are free to download the rom of your choice (The nvflash mode) and run it to install it

[TUTORIAL][CM11][4.4.2] CyanogenMod Tutorial for Sony Xperia Tablet Z (pollux)

I went through a lot of searching and trouble to install CM11 on my Xperia Tablet Z, and I'd like to share a tutorial I made for anyone who is also wanting to accomplish this.
All links are in Dark Green because I cannot post links yet.
1. Download and extract the ADB+Fastboot+Drivers zip (alexpja.com/sony/adb-fastboot-win.zip)
2. Now we’ll unlock the bootloader.
a. If you do not have a Phone app (like I don’t on the SGP351), you can either get the IMEI from About -> Status in the settings OR you can find the IMEI right after the IC code, nearby the barcode on the bottom of the tablet.
b. If you do have a Phone app, enter *#06# to retrieve the IMEI.
c. Save this for later use.​3. Place the tablet into fastboot mode and connect it to the computer.
a. Power off the device
b. Connect USB to computer
c. While plugging in the other side of the USB cable into the tablet, hold down the Vol + button.
d. If your speakers are on, you should a sound.
e. We have to install the drivers for fastboot. Open devmgmt.msc via the Run window or in the Start menu and in Other Devices section, you should see S1 Service or S1 Fastboot (anything containing S1).
i. If it is showing a yellow exclamation mark: Follow 3.e.i.1. If it is not, continue to 3.f.
1. We need to download Flashtool and use the driver setup. Download Flashtool (unrestrict.li/flashtool) and install it.
2. Find cmd.exe, right click it, and select Run as administrator.
a. Type in
Code:
bcdedit /set testsigning on
and press enter.
b. Reboot your computer.​3. Once you have rebooted the computer, open the folder where you installed Flashtool (default: C:\Flashtool).
4. Open up the drivers folder and open Flashtool-drivers.exe.
5. Select the first two driver choices (Flashmode and Fastboot) and select “Xperia Tablet Z Drivers” and continue.
6. A new window will appear, continue on with that.
7. A window like this may appear a few times, just press Install this driver software anyway.
8. Run 3.e.2. again and run
Code:
bcdedit /set testsigning off
. Reboot your PC now or after the tutorial.​f. The LED pulse light above it should be emitting a blue-ish color. The screen will be dark.​4. Now we’ll verify if you have fastboot running.
a. Open the tools folder that was extracted from the ADB ZIP and double-click on START.cmd to open Command Prompt in the current directory (all it does is literally open cmd.exe, you can edit the script to verify).
b. Run the command
Code:
fastboot -i 0x0fce getvar version
. If you get
Code:
<waiting for device>
, then you did something wrong. Retrace your steps! (For example, I get
Code:
version: 0.5
)​5. Go to (unlockbootloader.sonymobile.com) and continue until you reach the screen where you put type in the IMEI and an email address. Type in the first 14 digits of the IMEI (remove the last one) and your email address (not sure if name is required). You should get an email instantly with the key.
6. In the Command Prompt, run
Code:
fastboot -i 0x0fce oem unlock 0xKEY
where KEY is the key you received in the email from Sony.
7. Download whatever release you would like to use on the tablet (I’m using CM 11 nightly) from (download.cyanogenmod.org/?device=pollux)
a. Optional: Also download gapps for Google apps such as Gmail, Google Play Services, etc. (wiki.cyanogenmod.org/w/Google_Apps)​8. Extract the ZIP file (but don’t delete it either) and copy boot.img to the tools folder.
9. If your device is still turned off, turn it on and enable USB storage mode. Copy the CM zip to either the internal storage (sdcard) or, if one is inserted, the microSD card (sdcard1).
10. Place it into fastboot mode again (#3).
11. Go back into the Command Prompt and enter:
a.
Code:
fastboot -i 0xfce flash boot boot.img
b.
Code:
fastboot -i 0xfce reboot
c. Enter recovery.
1. Once it shuts down, rapidly tap the Vol + button in order to get into the recovery.
2. Grep_The_Truth's tip: Look at the LED. It will turn orange and afterwards it'll turn purple. You want to press Vol+ as soon as it changes colors.​12. Select “wipe data/factory reset” and wipe it. Afterwards, go back to main menu.
13. Select “Install zip” and either select “Choose zip from /sdcard” (internal storage) or “Choose zip from /storage/sdcard1” (microSD card).
I’ve had varying experience with installing from the /sdcard because sometimes it doesn’t want to mount /data while wiping (/data/media which is /sdcard is safe in wipe) the tablet, so if you were to install the zip from /sdcard with the error present, it would screw things up. I prefer the microSD card route (/storage/sdcard1), and you don’t even need a big one. 512MB works just fine. The actual path would be /sdcard/0/ when looking for the cm.zip in the internal storage.
14. When you have chosen to install from either /sdcard or /storage/sdcard1, select the cm.zip and install it.
a. If you downloaded gapps.zip, install it the same way as you did with the cm.zip.​15. Go back to the main menu now and select “reboot system now”
a. Once, I had the option to install root access before rebooting, I declined (was planning on rooting after tutorial) but it gave me root anyway.​
That’s it! You can now use CyanogenMod with the Sony Xperia Tablet Z.

Getting in to recopvery
I just struggled with entering recovery for way too long and I want to help others avoid this. I kept finding vague instructions.
The step I want to clarify is:
c. Once it shuts down, rapidly tap the
Code:
Vol +
button in order to get into the recovery.
Click to expand...
Click to collapse
This didn't work for me because if you press Vol+ too soon it goes right back in to fastboot mode. If you press it too late you will miss the recovery mode. You only have to press Vol+ once.
Please change step c. to read:
Look at the LED. It will turn Orange and then Purple. You want to press Vol+ as soon as it changes from Orange to Purple to enter recovery mode.

Grep_The_Truth said:
I just struggled with entering recovery for way too long and I want to help others avoid this. I kept finding vague instructions.
The step I want to clarify is:
This didn't work for me because if you press Vol+ too soon it goes right back in to fastboot mode. If you press it too late you will miss the recovery mode. You only have to press Vol+ once.
Please change step c. to read:
Look at the LED. It will turn Orange and then Purple. You want to press Vol+ as soon as it changes from Orange to Purple to enter recovery mode.
Click to expand...
Click to collapse
I'll add it along with mine, because I can do it with no problem.

alexpja said:
I'll add it along with mine, because I can do it with no problem.
Click to expand...
Click to collapse
alexpja Thanks for your tutorial, this is very detailed and easy to follow.
my Xperia is SGP321.
I put it into practice and the results it gives me the "oem unlock" is:
FAILED: (remote: Command nor allowed).
I guess you should treat my tablet has the bootloader locked and not allowed (for now??) the unlocked.
I hope someone gives us the opportunity to unlock the devices and in the future can be unlocked.

I had the same experience where at times the steps were a little confusing, especially for a beginner. Each set of instructions would either leave something out or skim over it as if everyone already knew it. That's understandable since they were probably written for that audience. I soft-bricked my SGP311 at least 10 times.
I was even going to write something like this but I got lazy.
One suggestion I would offer is to request the bootloader unlock key first since it sometimes takes a little while and a person can reduce the possibility of having to stop and wait just when they are making progress.
And for anyone going this route for the first time, don't make my mistake - flash exactly what the instructions say to flash, particularly boot.img. Once you have that recovery flashed you have a lot more control over your device. If something goes wrong in a following step like getting boot loops you can still fix it. But if you get annoyed and start poking at it then you can mess up the recovery. Then you have to reset everything to stock and just about start over.
While I don't want to say something stupid like claiming the tablet is indestructible, I found that whether I got stuck in a boot loop I couldn't get out of or screwed it up so bad that all I could get from the tablet was an occasional LED flash, I could always restore it using Emma. It's annoying to have to start all over but it's a huge relief when it boots normally.

for me flashing was fine and without any error but my Tab doesn't boot up with CM flashed...any idea?

Hanging at reboot
Hi.
I tried this procedure on my sony xperia tablet z 311. It unlocked fine and wrote boot.img fine but on reboot command, I get a red light and it hangs there.
I've managed to get it back to fastboot mode (pressing power and vol+, some white blinking lights).
But that's it, that's all I can do with this right now. It's a brick that can get into fastboot mode and that's it. Any time I write a boot.img (have tried a different one also), it writes fine but hangs with a red light at reboot.
Edit:
Used Sony's Emma in flash mode to get back to stock, tried again and it worked.
Maybe the problem was using the pollux instead of pollux_windy download, my bad.

Guess my bootloader won't be unlocked. This is A lot of work. Good job on the write up though maybe one day I'll tackle it.

BOOT LOOP Step 9
All was going well, but step 9 powering on device, now its looping.....Ill use flash tools to put jelly bean on and try again, since i was trying with kitkat...why i suspect kitkat is the issue, before i used to be able to unlock and lock boot-loader with jelly bean but with kitkat it didn't work, which i then forced it via cmd

No GPS
I used the tutorial for my Pollux Windy (WiFi Only) and used the latest nightly. everything went well but my GPS is now broken. Is this a known issue?

kevinsickles said:
Is this a known issue?
Click to expand...
Click to collapse
yep! use search to find out more.

mulebreath said:
Hi.
I tried this procedure on my sony xperia tablet z 311. It unlocked fine and wrote boot.img fine but on reboot command, I get a red light and it hangs there.
I've managed to get it back to fastboot mode (pressing power and vol+, some white blinking lights).
But that's it, that's all I can do with this right now. It's a brick that can get into fastboot mode and that's it. Any time I write a boot.img (have tried a different one also), it writes fine but hangs with a red light at reboot.
Edit:
Used Sony's Emma in flash mode to get back to stock, tried again and it worked.
Maybe the problem was using the pollux instead of pollux_windy download, my bad.
Click to expand...
Click to collapse
Hi,
I've been trying with my Xperia Tablet Z Wi-Fi SGP311. Ran into the same problem. On reboot command the LED was stuck on red for 10 minutes and the cmd window was still open. I unplugged the USB and the LED would not turn off. Tried some things, I don't remember specifically what, but it got the LED to turn off. Now my device can't be detected. I've downloaded Emma and it is not recognising my tablet. I've tried to plug the USB in while hold Vol +, Vol -, and the Power button. No detection for any. All I can do with my tablet is make the LED flash white, purple and red in rapid succession by holding Vol + and Power for 5 seconds.
Anyone know what's happened? I suspect I've completely bricked it :L
EDIT: Apparently there are different modes which you can cycle through. If you hold down Vol + and Power for 5 seconds, the LED will flash according to which mode the tablet is in. The different modes give these flashes:
- 1 White flash
- 3 Rapid which flashes
- A white, purple and red flash in quick succession
To switch between the modes, I hold down Vol+ and Power, and after 5 seconds it will take around 3 more seconds to change modes. One of these modes will not appear unless plugged into a PC. What do these mean and can I do anything with it? Tablet is still bricked.
EDIT2: I've managed to get Emma to recognise my tablet. Turns out the modes do have different purposes. I should be fine now, problem solved. I will just leave the solution here in case anyone runs into the same problem.
Unplug your device and hold Vol + and Power for 10 seconds. At the 5 second mark your LED should flash white ONCE. Keep both buttons held and within 5 more seconds, your LED will flash white THREE times consecutively. This will allow you to enter Flashmode (plug in USB while holding Vol -) and Fastboot (plug in USB while holding Vol +). For Emma to recognise your device, enter Flashmode and you can restore and try again.

Bootloop
I've tried many times to flash cyanogenmod onto my Xperia Tablet Z (SGP311). This is a Wi-Fi only tablet and I have downloaded the versions of CM from (download.cyanogenmod.org/?device=pollux_windy) I've followed all of the steps and tried all of the versions of CM down to 10.2 (I used GApps10.2 for CM10.2). Each version gets stuck in bootloop. I've cleared all data (in CWM - wipe data/factory reset, wipe cache partition, wipe delvik cache) before flashing CM and GApps; however, when I try to clear data I get an error. This is what the tablet says:
-- Wiping Data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cacha
Formatting /sd-ext...
Formatting /sdcard/.android_secure!
Skiiping format...
Data wipe complete.
Click to expand...
Click to collapse
I'm thinking the "Error mounting /data" is the problem, but I'm not entirely sure, nor am I sure of how to fix it.
Any suggestions?
EDIT: Turns out I'm just really bad with Android stuff. I ended up flashing the original Xperia software, unlocking the bootloader (according to this tutorial's instructions), then I downgraded to 4.1.2, rooted my tablet (forum.xda-developers.com/showpost.php?p=53063218&postcount=14) and installed the PhilZ and TWRP custom recoveries. I didn't get to use them in the end. For some reason CWM kept coming up no matter what combination of buttons I pressed while rebooting. After downgrading and rebooting, I followed the rest of the instructions on this tutorial (from step 7). This time I got no errors while cleaning the disk, cache and delvik cache. Flashed the zip files, rebooted the device and voila, Cyanogenmod11!
Again, I'll leave this edit here in case someone runs into a similar problem. I couldn't get any version of CM until I rooted first.

I followed this guide and bricked my device. If anyone has any tips - PLEASE HELP!
I tried to flash CM11, all seemed to be going great until CM11 and Gapps where installed any I hit "Reboot system now" in CVM. The device never booted again (I which I knew why!), and is now pretty much dead. I can however:
- Enter Flashmode
- Enter Fastboot mode
- Relock/Unlock bootloader
- Emma recognizes my device just fine in flashmode.
So I still think there is some hope, right?
I have tried installing the firmware that Emma suggests, doesn't work.
I have tried flashing a firmware I found on the internet with Flashtool, doesn't work.
I have tried relocking the bootloader and trying to repair the device through SUS, doesn't work.
So, PLEASE, help my sort this out! I would be forever greatful!

tp_88 said:
I followed this guide and bricked my device. If anyone has any tips - PLEASE HELP!
I tried to flash CM11, all seemed to be going great until CM11 and Gapps where installed any I hit "Reboot system now" in CVM. The device never booted again (I which I knew why!), and is now pretty much dead. I can however:
- Enter Flashmode
- Enter Fastboot mode
- Relock/Unlock bootloader
- Emma recognizes my device just fine in flashmode.
So I still think there is some hope, right?
I have tried installing the firmware that Emma suggests, doesn't work.
I have tried flashing a firmware I found on the internet with Flashtool, doesn't work.
I have tried relocking the bootloader and trying to repair the device through SUS, doesn't work.
So, PLEASE, help my sort this out! I would be forever greatful!
Click to expand...
Click to collapse
download a proper stock (not bricked) firmware for your device and flash with flashtool.

Rootk1t said:
download a proper stock (not bricked) firmware for your device and flash with flashtool.
Click to expand...
Click to collapse
What makes you think that the stock firmwares I've tried are bricked? I've since my post tried one which I downloaded through Flashtool - same result.

[Q] Nexus 7-APX Looping even after successful flashing of a working bootloader 4.23

I was running stock rooted Android KK 4.4.4 on Nexus 2012 Wifi Only with bootloader as unlocked. I attempted the Lollypop update 5.0.2 by OTA but it gave an error while installing and device rebooted to Kit Kat normally.....working fine. OTA was not getting done for some reason may be because i was rooted.
I downloaded the factory image nakasi-lrx22g-factory-2291c36b.tgz from google and attempted to flash it using Nexus Root Toolkit(v 2.0.2) with option "No Wipe Mode" as selected and then the device ran into fastboot mode... NRT run commands like erase system etc then the script gave an error "Failed" "remote -invalid state" while attempting to write bootloader. I thought that the problem is with "No Wipe" selected so i re-attempted it with "No Wipe" being unselected. BUt same error.
I searched the forum & found that the issue may be due to incorrect/corrupted bootloader. I replaced the bootloader-grouper-4.23.img which was in the factory image with the 4.23 bootloader taken from JWR66V as most people over XDA have said that its the working bootloader.
I had flashed the img downloaded from here - http://forum.xda-developers.com/showpost.php?p=45043044&postcount=15
Flashing succeeded and Nexus Root Toolkit did not give error this time it said "OKAY" instead of "FAILED". But it did not proceed forward to flashing other files like system img etc. NRT was stuck at the Flash Bootloader - OKAY cmd.
I powered of the Tablet and Powered On again it showed "Booting Failed" at the Google Screen. I rebooted into Fastboot mode with "vol- and power" held together. It displayed the same screen as it did before i.e. displaying the information of Bootloader.
Product Name - Grouper
Variant - Not Defined Yet
HW Version - ER3
Bootloader version - 4.23
Baseband version - NA
Signing - Not Defined Yet
LOCK STATE = UNLOCKED
Then I read somewhere that after flashing the Bootloader img you have to run the bootloader by rebooting tablet with vol+,vol- and power button all held together.
I did that and wat i saw on computer screen was "APX device found" (((((
The device went into APX mode and since 2 days has not come out.
I tried pressing Power button for like 3mins with power adapter connected/disconnected by usb
I tried pressing vol- and power button for more than 5min. with system connected/disconnected with usb
Nothing worked...
I am wondering what took the device to APX because the bootloader was good one from "JWR66V". It was flashed with success by Nexus Root Toolkit. the device did run into fastboot mode once after flashing it. The Device went into APX after all the 3 keys "vol+ vol- and power" were pressed together. But according to key combo terms APX mode is activated when "Power" and "vol+" are pressed and it exits when "Power" alone is held for 15+ seconds.
What I feel now is that the device is in APX looping (similar to Bootlooping) due to some reason. Corrupted Bootloader can be one of that but its unlikely as flashing was successful and img used was authentic. One more reason of APX looping may be that nothing apart from Bootloader is present in it, no system no recovery. only bootloader is present.
Now what do I do to come out of APX ? Power button and Power+vol- etc not working tried them numerous times. It won't accept fastboot or adb commands as its in apx mode.
Its Out of Warranty so only 2 options left for me now
1. Battery Removal
2. NVFlash
I want to keep things simple so I am thinking of battery removal first. Does the battery removal reset nexus 7 ?
I have a feeling that its effect is same as the power button holding for 15sec. but will have to try. Although the Warranty is voided but will Asus people agree to provide paid service to me if i myself attempt battery removal by opening the back side of the device.
Incase this dont work I will move to nvflash
But I have a few questions regarding nvflash.
1. Does nvflash require blob n sbk even for an unlocked bootloader?
2. I can generate the SBK for my device using the CCSN number and try though but I want only a simple command which will reboot nexus into fastboot mode exiting APX mode.
any help will be appreciated.

BrightHeart said:
I was running stock rooted Android KK 4.4.4 on Nexus 2012 Wifi Only with bootloader as unlocked. I attempted the Lollypop update 5.0.2 by OTA but it gave an error while installing and device rebooted to Kit Kat normally.....working fine. OTA was not getting done for some reason may be because i was rooted.
I downloaded the factory image nakasi-lrx22g-factory-2291c36b.tgz from google and attempted to flash it using Nexus Root Toolkit(v 2.0.2) with option "No Wipe Mode" as selected and then the device ran into fastboot mode... NRT run commands like erase system etc then the script gave an error "Failed" "remote -invalid state" while attempting to write bootloader. I thought that the problem is with "No Wipe" selected so i re-attempted it with "No Wipe" being unselected. BUt same error.
I searched the forum & found that the issue may be due to incorrect/corrupted bootloader. I replaced the bootloader-grouper-4.23.img which was in the factory image with the 4.23 bootloader taken from JWR66V as most people over XDA have said that its the working bootloader.
I had flashed the img downloaded from here - http://forum.xda-developers.com/showpost.php?p=45043044&postcount=15
Flashing succeeded and Nexus Root Toolkit did not give error this time it said "OKAY" instead of "FAILED". But it did not proceed forward to flashing other files like system img etc. NRT was stuck at the Flash Bootloader - OKAY cmd.
I powered of the Tablet and Powered On again it showed "Booting Failed" at the Google Screen. I rebooted into Fastboot mode with "vol- and power" held together. It displayed the same screen as it did before i.e. displaying the information of Bootloader.
Product Name - Grouper
Variant - Not Defined Yet
HW Version - ER3
Bootloader version - 4.23
Baseband version - NA
Signing - Not Defined Yet
LOCK STATE = UNLOCKED
Then I read somewhere that after flashing the Bootloader img you have to run the bootloader by rebooting tablet with vol+,vol- and power button all held together.
I did that and wat i saw on computer screen was "APX device found" (((((
The device went into APX mode and since 2 days has not come out.
I tried pressing Power button for like 3mins with power adapter connected/disconnected by usb
I tried pressing vol- and power button for more than 5min. with system connected/disconnected with usb
Nothing worked...
I am wondering what took the device to APX because the bootloader was good one from "JWR66V". It was flashed with success by Nexus Root Toolkit. the device did run into fastboot mode once after flashing it. The Device went into APX after all the 3 keys "vol+ vol- and power" were pressed together. But according to key combo terms APX mode is activated when "Power" and "vol+" are pressed and it exits when "Power" alone is held for 15+ seconds.
What I feel now is that the device is in APX looping (similar to Bootlooping) due to some reason. Corrupted Bootloader can be one of that but its unlikely as flashing was successful and img used was authentic. One more reason of APX looping may be that nothing apart from Bootloader is present in it, no system no recovery. only bootloader is present.
Now what do I do to come out of APX ? Power button and Power+vol- etc not working tried them numerous times. It won't accept fastboot or adb commands as its in apx mode.
Its Out of Warranty so only 2 options left for me now
1. Battery Removal
2. NVFlash
I want to keep things simple so I am thinking of battery removal first. Does the battery removal reset nexus 7 ?
I have a feeling that its effect is same as the power button holding for 15sec. but will have to try. Although the Warranty is voided but will Asus people agree to provide paid service to me if i myself attempt battery removal by opening the back side of the device.
Incase this dont work I will move to nvflash
But I have a few questions regarding nvflash.
1. Does nvflash require blob n sbk even for an unlocked bootloader?
2. I can generate the SBK for my device using the CCSN number and try though but I want only a simple command which will reboot nexus into fastboot mode exiting APX mode.
any help will be appreciated.
Click to expand...
Click to collapse
U have done it in wrong way
U should have flashed the recovery and system and bootloader manually without nrt
Are able to detect your device via computer in fastboot mode

shivambhai said:
U have done it in wrong way
U should have flashed the recovery and system and bootloader manually without nrt
Are able to detect your device via computer in fastboot mode
Click to expand...
Click to collapse
I used NRT normally as its directed in NRT's thread. Bootloader taken from "JWR66V" was flashed successfully but NRT didnot proceed forward. I powered of the tablet then pressed both volume plus & minus buttons along with power button simultaneously, I read somewhere that pressing all 3 butons is needed to start the bootloader, This resulted in device going in APX mode, although APX mode is activated by holding only vol plus and power button simultaneously. The device seems to be looped in APX i.e. not coming out of it.
It was detectable as a fastboot device earlier but after it went into APX its detected as an "Unknown Apx device" asking for driver, The Asus Transformer Pas driver is installable for it, but i doubt will it work in nvflash.
I jus need a little information about battery removal & nvflash. I have googled about them already but had a couple of queries which I have posted above.
Thanxxxx

Update
Okay last night I attempted battery removal from the device. I took off the back panel of nexus 7 and disconnected the battery cable which is connected to motherboard socket. I reconnected it after 10mins and still no success. I removed it again and connected the device to computer by USB and I found something very strange. the computer detected the Nexus 7 as "Unknown APX Device" even after the battery was disconnected. I was wondering from where is the device drawing power to run? Is it by computer's USB port alone or is there any other power source in nexus7's motherboard like a CMOS cell is present in Computer's MotherBoard which keeps the clock ticking.
Whatever may be the case but it seems that APX Mode is capable of running in minimal power input.
Next test which I performed was to Hold the power button while it was connected to system by USB. After about 7-8secs the device powered off as the computer displayed USB device disconnected message and sound but it repowered on its own in next couple of seconds and again it was detected as "APX device" . Same result observed with simultaneous holding of volume minus+power button as well.
Now I have every reason to believe that device is hard bricked and looped in APX i.e. The Bootloader is corrupted or is not running due to some reason. The device has no option but to go in APX and sit there forever unless its flashed at low level.
I would like to give nvflash a try but i know that theres no1 yet who has made it success and then the only option remaining for me is to visit Asus service center and get some paid service done.
Query - If I visit Asus service center then will they perform software reprogramming i.e. Bootloader fixing or will they replace the hardware ? Incase if they replace the hardware then will they replace the whole board or just the memory unit(which contains Bootloader) from the board?
Experts here please put some light on this

No idea brightheart

Did you have any luck with this BrightHeart? I seem to be in the same boat now...
BrightHeart said:
Okay last night I attempted battery removal from the device. I took off the back panel of nexus 7 and disconnected the battery cable which is connected to motherboard socket. I reconnected it after 10mins and still no success. I removed it again and connected the device to computer by USB and I found something very strange. the computer detected the Nexus 7 as "Unknown APX Device" even after the battery was disconnected. I was wondering from where is the device drawing power to run? Is it by computer's USB port alone or is there any other power source in nexus7's motherboard like a CMOS cell is present in Computer's MotherBoard which keeps the clock ticking.
Whatever may be the case but it seems that APX Mode is capable of running in minimal power input.
Next test which I performed was to Hold the power button while it was connected to system by USB. After about 7-8secs the device powered off as the computer displayed USB device disconnected message and sound but it repowered on its own in next couple of seconds and again it was detected as "APX device" . Same result observed with simultaneous holding of volume minus+power button as well.
Now I have every reason to believe that device is hard bricked and looped in APX i.e. The Bootloader is corrupted or is not running due to some reason. The device has no option but to go in APX and sit there forever unless its flashed at low level.
I would like to give nvflash a try but i know that theres no1 yet who has made it success and then the only option remaining for me is to visit Asus service center and get some paid service done.
Query - If I visit Asus service center then will they perform software reprogramming i.e. Bootloader fixing or will they replace the hardware ? Incase if they replace the hardware then will they replace the whole board or just the memory unit(which contains Bootloader) from the board?
Experts here please put some light on this
Click to expand...
Click to collapse

Same Issue!
seanet1970 said:
Did you have any luck with this BrightHeart? I seem to be in the same boat now...
Click to expand...
Click to collapse
Looks like this problem is quite common and mostly affecting Nexus 7 2012 devices. Mine to got botched after a OTA update. Any possibilities of Google fixing this /RMA beyond warranty ?