I have installed 4.2.2 on nexus 7. As I had skipped account login at welcome screen, i could not login the account. I altered the apk of login. After factory reset my device has hanged on setup on welcome screen. I tried installing custom rom through stock bootloader but the bootloader says installation failed. How do I solve thia problem guys???
subin.nexus7 said:
don't know the exact steps, but i got it out of the APX mode and into the bootloader.
1. Tablet plugged into computer.
2. Held Volume Down + Volume Up + Power (simultatenously) for three seconds
3. And then released all, and pressed Power again.
4. Tablet booted into bootloader.
I thought that unlocking the bootloader ALWAYS voided the warranty, but in anycase I flashed reflashed ALL stock and locked the bootloader. Will be sending it to ASUS now. Thanks again!
EDIT:
So I wanted to verify that it was a CPU problem, and I downloaded StabilityTest again and ran the CPU load test. It crashed within two minutes, and went into AXP mode again. To get it out of AXP mode, the correct instructions:
1. Plug in the usb into computer
2. Hold Volume Down + Volume Up + Power simultaneously for like 15 seconds
3. The bootloader should show up.
4. If it doesn't, unplug the usb cable, and plug it back in and then repeat the these procedures.
Click to expand...
Click to collapse
Very helpful! I don't have a problem but I've read about others stuck in APX mode. This should be pinned if it works for those stuck in APX. Maybe you should change the thread title to something about APX solution so it draws some attention.
kieso said:
Very helpful! I don't have a problem but I've read about others stuck in APX mode. This should be pinned if it works for those stuck in APX. Maybe you should change the thread title to something about APX solution so it draws some attention.
Click to expand...
Click to collapse
Well... being stuck in APX doesn't necessarily mean your hardbricked. (Corrupt or erased bootloader).
But being hardbricked DOES mean your device will default to APX mode.
To use a mathematical metaphor, one is a SUBSET of the other.
-------
bftb0 has posted an exhaustive list of Nexus 7 button press combos here...
http://forum.xda-developers.com/showthread.php?t=2133986
... which includes how to pro-actively get into APX mode... although until somebody figures how to nvFlash the N7, APX is sort of redundant.
Rgrds,
Ged.
Delete
subin.nexus7 said:
I have installed 4.2.2 on nexus 7. As I had skipped account login at welcome screen, i could not login the account. I altered the apk of login. After factory reset my device has hanged on setup on welcome screen. I tried installing custom rom through stock bootloader but the bootloader says installation failed. How do I solve thia problem guys???
Click to expand...
Click to collapse
I'm sort of confused about the relationship between your edited post and what (apparently ?) kieso quoted, but I'll throw out a few suggestions:
1) AFAIK, there is no way to flash a dev ROM using fastboot (only the boot image of a dev ROM can be flashed this way). You said "bootloader", not "custom recovery" ... so that implies using fastboot. If that is not the case, then your use of terminology is not correct. (It's a computer - reporting details correctly is incredibly important).
2) If you bypass the WiFi login, an account can be added at any time later using the settings menu or simply by launching the Google Play (market) app - there is no need to "alter the apk of login", whatever that means.
3) I would recommend at this point that you start completely over by flashing a factory ROM using fastboot - see the sticky thread about returning to stock using fastboot. If you already have the 4.18 bootloader installed, I recommend you avoid like the plague any operation involving flashing the bootloader.
4) It should be obvious from the trouble that you got yourself into that you should learn what nandroid backups are and that you START USING THEM. The first thing you do after rooting is "make a backup", not "flash a ROM"
good luck
Thanq so much.But still some clarification needed
Now What do I do? My nexus 7 can't pass through at welcome screen saying saying unfortunately setup wizard has stopped. and in recovery{i have no custom recovery, I use bootloader 4.18} i cant flash any rom. I just want to start device any how.. any way.. Is there any way??
subin.nexus7 said:
Now What do I do? My nexus 7 can't pass through at welcome screen saying saying unfortunately setup wizard has stopped. and in recovery{i have no custom recovery, I use bootloader 4.18} i cant flash any rom. I just want to start device any how.. any way.. Is there any way??
Click to expand...
Click to collapse
I guess I am having trouble understanding the sum total of information you have provided - I guess you have omitted some information or mis-stated something. No custom recovery sort of implies a full stock device, but yet you previously mentioned modifying/changing an .apk in /system... normally that would be possible only with a rooted ROM or a custom recovery to do that.
If your tablet is 100% stock, a factory reset of the tablet should allow you to boot once again - at the cost of deleting everything you put on the device, including all files you put on the (pseudo-) SD card.
If that is the case:
- press and hold power+vol-down until the bootloader screen shows up
- use vol-up/vol-down to select "start recovery" and press the power button
- an android lying on it's back should show up; this is the stock recovery splash screen, so
- press power+vol-up simultaneously for about one second - the stock recovery menu should show up
- select factory reset (with vol-up/vol-down) and press the power button.
good luck
bftb0 said:
I guess I am having trouble understanding the sum total of information you have provided - I guess you have omitted some information or mis-stated something. No custom recovery sort of implies a full stock device, but yet you previously mentioned modifying/changing an .apk in /system... normally that would be possible only with a rooted ROM or a custom recovery to do that.
If your tablet is 100% stock, a factory reset of the tablet should allow you to boot once again - at the cost of deleting everything you put on the device, including all files you put on the (pseudo-) SD card.
If that is the case:
- press and hold power+vol-down until the bootloader screen shows up
- use vol-up/vol-down to select "start recovery" and press the power button
- an android lying on it's back should show up; this is the stock recovery splash screen, so
- press power+vol-up simultaneously for about one second - the stock recovery menu should show up
- select factory reset (with vol-up/vol-down) and press the power button.
good luck
Click to expand...
Click to collapse
when you say at the cost of deleting everything, does this include deleting everything in the bootloader because thats what I did when I used the command "fastboot erase bootloader"
Related
I tried downloading 2.3.1 through rom manager, but it failed for some reason. So I accidentally downloaded it through the phone, and as soon as it began installing, I got a little Android image with a triangle that has an ! in it...How can i please fix this?
edit:i tried holding down the up and power keys with no luck...someone please help
monkeytuner said:
I tried downloading 2.3.1 through rom manager, but it failed for some reason. So I accidentally downloaded it through the phone, and as soon as it began installing, I got a little Android image with a triangle that has an ! in it...How can i please fix this?
edit:i tried holding down the up and power keys with no luck...someone please help
Click to expand...
Click to collapse
You might get more help if you rename your topic title to something more descriptive.
Second, try searching the forum; this has been discussed in numerous threads on both this forum and the developer's section, along with how to fix it.
Try the threads about the update, or dialing a certain code to force it manually (that's where I learned the timing trick to get into stock recovery on the NS). On the screen you're at, try pressing and holding power, then pressing/holding volume up, that should get you into stock recovery.
Also, if you can get into fastboot, you can fastboot flash the CWM recovery back to the device. If you made an nandroid before doing anything, you can at least go back to the device's state before you tried the update.
i could not find anything on this issue on google or here
i tried doing vol up and power, but its still at the screen, and my computer doesnt recognize my phone
use the instruction on the topic to ROOT the phone
http://forum.xda-developers.com/showthread.php?t=875875
and in one of the steps you can use the ADB to push a good ROM back into the phone to be re-flashed
Try just pulling the battery.
If not, you'll have to use fast boot from the SDK. Just follow the howto at the top of this forum to flash original images.
thank you so much!
i locked my bootloader again, and i've been trying to get the 2.3.1 update, but everytime i do try, it freezes at the android warning sign. i also tried installing it via rommanager when i was rooted...whats going on?
any ideas what could be wrong?
monkeytuner said:
i could not find anything on this issue on google or here
i tried doing vol up and power, but its still at the screen, and my computer doesnt recognize my phone
Click to expand...
Click to collapse
monkeytuner said:
any ideas what could be wrong?
Click to expand...
Click to collapse
Are you able to get into Fastboot?
I wonder if part of your problem is that you relocked the bootloader. (Why'd you do that anyways? No advantage, imo.)
Fastboot oem unlock will completely wipe your phone, I mean WIPE EVERYTHING, including the sdcard (photos, music, some apps' data, etc), but such a wipe might get you back to stock firmware and stock recovery, then at least you could boot up. You could also then reflash CWM.
Before doing that, let's try this if you haven't:
Turn off phone.
Hold vol-up, then press/hold power.
You should then be in fastboot mode.
The timing's critical (on my phone anyways) for this step: Select recovery, and have your hands on the power button and volume button ready to push.
Watch the screen very closely, for a bout a half second or so, the screen will flash a box with an arrow dumping out onto the android dude. While that screen is showing, press/hold the power button, then press/hold the vol up button. Important to do the power button FIRST this time (at least it is on my phone).
You should then be able to get into the stock recovery.
Once there, maybe we can figure out where to go, but we need to know how messed up your phone is at this point.
Once in Recovery, you could try wiping cache if it's an option, then trying to reboot. Worth a shot, but not likely to work.
You could also do the factory reset wipe in there, this one shouldn't wipe your sdcard if there's anything critical/valuable on it. It will reset all your settings and logins and wipe the apps you've installed, though. Again, might let you boot up normally.
I just reset mytouch 4g phone and during restart the recovery screen just come out but I can't move down or up anything on the screen it just stuck..
I just update cm to version 3 of something
please I really need help on this my phone is already S-off
when I plug the phone with USB it response something by HBOOT has changed to HBOOT USB PLUG
I use Stock Rom just update Kernal only
Need more specifics. "3 of something" is too vague.
If you flashed clockwork mod recovery 3 (the text is orange) while using a stock ROM you will have issues. Clockwork 3 is for gingerbread based ROMs only.
If that is so, download CyanogenMOD 7 RC1 and try to flash it. Rebooting may help get recovery working right again. If not, and you are unable to re-flash a ROM, you will need to use fastboot to re-flash a good recovery image.
Marine6680 said:
Need more specifics. "3 of something" is too vague.
If you flashed clockwork mod recovery 3 (the text is orange) while using a stock ROM you will have issues. Clockwork 3 is for gingerbread based ROMs only.
If that is so, download CyanogenMOD 7 RC1 and try to flash it. Rebooting may help get recovery working right again. If not, and you are unable to re-flash a ROM, you will need to use fastboot to re-flash a good recovery image.
Click to expand...
Click to collapse
when I upplug battery, and turn the phone on, it won't boot it just re direct to the Clockwork Mod screen and the screen lock volume up and down can't navigate anything power botton won't work tooo..I try to un plug battery again and turn on again the result is the same...
wibul_10 said:
when I upplug battery, and turn the phone on, it won't boot it just re direct to the Clockwork Mod screen and the screen lock volume up and down can't navigate anything power botton won't work tooo..I try to un plug battery again and turn on again the result is the same...
Click to expand...
Click to collapse
In clockwork you use the trackball to navigate. Volume buttons won't work.
Lakeshow423 said:
In clockwork you use the trackball to navigate. Volume buttons won't work.
Click to expand...
Click to collapse
no response on trackball too. it just stuck on this screen and can't move anywhere....any solution
Your attached image is of the Bootloader, not CWM Recovery.
The Bootloader is controlled by volume up / volume down to move between selections, and the power button is used to select.
jggimi said:
Your attached image is of the Bootloader, not CWM Recovery.
The Bootloader is controlled by volume up / volume down to move between selections, and the power button is used to select.
Click to expand...
Click to collapse
when I turn the phone on everytime it just show this bootloader and no response on all volume up/down and power button...only way to turn off is to unplug battery ....
You might see if the Bootloader can communicate with fastboot on your PC. If so, you will have options for un-bricking from your PC.
See http://forum.xda-developers.com/showthread.php?t=928370 for info on installing adb and fastboot to your PC, and using them.
Fastboot is designed to communicate with the bootloader. As far as I know, however, adb requires a functioning Android or Recovery system.
jggimi said:
You might see if the Bootloader can communicate with fastboot on your PC. If so, you will have options for un-bricking from your PC.
See http://forum.xda-developers.com/showthread.php?t=928370 for info on installing adb and fastboot to your PC, and using them.
Fastboot is designed to communicate with the bootloader. As far as I know, however, adb requires a functioning Android or Recovery system.
Click to expand...
Click to collapse
One more question, after following your advice, I found that I now can restart my phone again but when I shut down the phone and turn it on again it still stuck on bootloader screen all the times...any suggestion would be appreciate...
You can "restart my phone again" -- is it running Android at that point? If so, you can restore your phone to stock, and do a full factory reset, by putting the P15IMG.zip file on the root of your SD card and rebooting. The bootloader (if it is functional) should find it and begin the restore procedure.
Dowload, rename this, and stick it on your SD card, and reboot. If after a successful return to factory defaults, your phone still isn't working, the problem is likely not software.
http://www.filedropper.com/pd15imgglaciertmous1175312radio1228b60140e26030226mrelease155771signed
(Link borrowed from Phateless's .sig)
jggimi said:
You can "restart my phone again" -- is it running Android at that point? If so, you can restore your phone to stock, and do a full factory reset, by putting the P15IMG.zip file on the root of your SD card and rebooting. The bootloader (if it is functional) should find it and begin the restore procedure.
Dowload, rename this, and stick it on your SD card, and reboot. If after a successful return to factory defaults, your phone still isn't working, the problem is likely not software.
http://www.filedropper.com/pd15imgglaciertmous1175312radio1228b60140e26030226mrelease155771signed
(Link borrowed from Phateless's .sig)
Click to expand...
Click to collapse
I can't download it...need new link
anyway thank very much for your help
Hey all, requesting some assistance...
I had used the nexus 7 toolkit to unlock the bootloader and root my tablet.
Earlier this afternoon, I decided to cave and flash cm10 on my tablet. Before doing so, instructions stated to wipe. In my ignorance, I wiped one too many things and also wiped the internal memory.
As a result, I am unable to get my tablet to fastboot and when I searched for the .zip to flash, I was presented with an ominously empty file directory to my sdcard's root. I have tried various things with the nexus 7 toolkit and have been unsuccessful in my endeavors, as many of those functions require the tablet to be in fastboot mode before any of them will work.
The device is stuck on the Google screen, and if I push the volume buttons with the power button, it will flicker and eventually return to this screen.
I do have a nandroid backup stored on my machine, but I am unable to use it as I am unable to even boot to the recovery (because I can't get to fastboot)... Any suggestions? I really hope I didn't brick this...
I believe you can get to fastboot mode with the v4.13 bootloader from any other mode so long as the battery is not dead and the screen is working.
When the battery has a good charge, hold the power button down until the google logo appears (could be up to 15-18 seconds). At that very moment that the black-and-white google logo image appears, press the Vol-down button.
Voila. Fastboot.
You do need to see that screen appear though; maybe that's the rub. Note that the timing is important - you only get one second or two to do this immediately after the image first appears.
As a bonus, glance at the bottom of that image. Shows an unlocked padlock for an unlocked bootloader, nothing if locked.
It worked! Thanks a bunch!
qwertyx7 said:
It worked! Thanks a bunch!
Click to expand...
Click to collapse
No worries. Glad it worked. Actually, I only stumbled across a reference to that button sequence a couple days ago.
If you see someone else reporting that they "can't get to fastboot", let them know - you can get there from ANY MODE.
[REF] Nexus 7 Button Combinations
Don't be this guy...
Please I really need some help! I think I've totally killed my nexus 10
I can get to fast boot but cannot flash anything. As soon as I try and say flash TWRP I get "FASTBOOT STATUS - DATA005fe000".
I've tried using the stock firmware and using flash-all.bat but get the same issue. The erase commands work, but then command to flash the boot loader gets the same issue.
I'm hoping I'm going to get flamed for not searching, 'cause that means I've missed something, but I've tried to search to no avail.
PLEASE HELP!!!!
kipperfish said:
Please I really need some help! I think I've totally killed my nexus 10
I can get to fast boot but cannot flash anything. As soon as I try and say flash TWRP I get "FASTBOOT STATUS - DATA005fe000".
I've tried using the stock firmware and using flash-all.bat but get the same issue. The erase commands work, but then command to flash the boot loader gets the same issue.
I'm hoping I'm going to get flamed for not searching, 'cause that means I've missed something, but I've tried to search to no avail.
PLEASE HELP!!!!
Click to expand...
Click to collapse
How did you got to that "state"? You should try using WugFresh toolkit.
lKBZl said:
How did you got to that "state"? You should try using WugFresh toolkit.
Click to expand...
Click to collapse
That's how I got into this mess! I tried to unlock and then root my tablet.
It rebooted and wouldn't pass the nexus X logo.
Now I can't flash anything.
In the Nexus Root Toolkit it says that if all goes wrong try Odin.
I've downloaded a version (I'm familiar with it from my Galaxy S), and got the drivers working... does anyone know where I can download the tar files?
kipperfish said:
That's how I got into this mess! I tried to unlock and then root my tablet.
It rebooted and wouldn't pass the nexus X logo.
Now I can't flash anything.
Click to expand...
Click to collapse
Did you get a chance to do the first twrp factory data reset? If not you may be able to boot into recovery mode and try a manual factory reset..
If your tablet is on, power it off.
Press and hold Volume Up + Volume Down + Power until the device powers on. You should see an image of an Android lying on its back.
Press Volume Down twice, until the screen says "Recovery mode."
Press Power to restart into "Recovery mode." You should see an image of an Android with a Red triangle after a few minutes.
While holding down Power, tap Volume Up
Use the volume keys to scroll to "wipe data/factory reset" and press Power to select it
Scroll down to "Yes - erase all user data" and press Power to select it
for some reason with wugfresh the first twrp factory reset failed on 2 out of 3 tests. I had do just do the manual factory reset above and all was well. Good luck! :good:
midgetzombiekiller said:
Did you get a chance to do the first twrp factory data reset? If not you may be able to boot into recovery mode and try a manual factory reset..
If your tablet is on, power it off.
Press and hold Volume Up + Volume Down + Power until the device powers on. You should see an image of an Android lying on its back.
Press Volume Down twice, until the screen says "Recovery mode."
Press Power to restart into "Recovery mode." You should see an image of an Android with a Red triangle after a few minutes.
While holding down Power, tap Volume Up
Use the volume keys to scroll to "wipe data/factory reset" and press Power to select it
Scroll down to "Yes - erase all user data" and press Power to select it
for some reason with wugfresh the first twrp factory reset failed on 2 out of 3 tests. I had do just do the manual factory reset above and all was well. Good luck! :good:
Click to expand...
Click to collapse
+1, exactly what I was thinking, you have to do a wipe data after unlocking in some cases.
Press and hold Volume Up + Volume Down + Power until the device powers on. You should see an image of an Android lying on its back.
Click to expand...
Click to collapse
Yes
Press Volume Down twice, until the screen says "Recovery mode.
Click to expand...
Click to collapse
Yes
Press Power to restart into "Recovery mode." You should see an image of an Android with a Red triangle after a few minutes.
Click to expand...
Click to collapse
I just get a black screen
While holding down Power, tap Volume Up
Use the volume keys to scroll to "wipe data/factory reset" and press Power to select it
Scroll down to "Yes - erase all user data" and press Power to select it
Click to expand...
Click to collapse
By using 4.2.0 (rather than 4.2.2) and trying the flash stock and unroot option I can now install CWM or TWRP as a boot loader.
I installed CWM and did a factory reset, then retried the above. This got the data error when installing system and then when finished got a file veririfcation error in the fastboot status. When I reboot I just get the Google logo and the unlock at the bottom.
kipperfish said:
Yes
Yes
I just get a black screen
By using 4.2.0 (rather than 4.2.2) and trying the flash stock and unroot option I can now install CWM or TWRP as a boot loader.
I installed CWM and did a factory reset, then retried the above. This got the data error when installing system and then when finished got a file veririfcation error in the fastboot status. When I reboot I just get the Google logo and the unlock at the bottom.
Click to expand...
Click to collapse
Wow i haven't had my n10 long enough to help you much more. Sounds like you might have some corrupt files from wugrfresh download/install? Maybe download from another mirror and try again? good luck !!!! Keep me posted!
Re: [Q] Bricked my nexus 10!
Not to be rude or anything but toolkits are the devil when it comes to Nexus devices. They are so easy to root and ROM that anyone can do it. Toolkits encourage ignorance to what and how things are getting done.
For starters go Google the fastboot files for the Nexus 10. Google Fastboot.exe and add it to your system folder on windows if you are using such.
Extract the downloaded "manta....." File and then extract the zip file contained.
From here make sure you are in your boot loader and type "fastboot devices" ensure your serial shows.
Then one by one go into the extracted folder and erase then flash each partition EXCEPT the bootloader. Don't mess with that at this point. After flashing the recovery, system, boot and data files reboot into the recovery and perform a factory reset. It should boot from this point.
On Manta, you MUST do a factory reset after flashing the data partition or unlocking the device. For some reason it fails to boot without performing that step.
Sent from my Nexus 10 using Tapatalk HD
altimax98 said:
Not to be rude or anything but toolkits are the devil when it comes to Nexus devices. They are so easy to root and ROM that anyone can do it. Toolkits encourage ignorance to what and how things are getting done.
For starters go Google the fastboot files for the Nexus 10. Google Fastboot.exe and add it to your system folder on windows if you are using such.
Extract the downloaded "manta....." File and then extract the zip file contained.
From here make sure you are in your boot loader and type "fastboot devices" ensure your serial shows.
Then one by one go into the extracted folder and erase then flash each partition EXCEPT the bootloader. Don't mess with that at this point. After flashing the recovery, system, boot and data files reboot into the recovery and perform a factory reset. It should boot from this point.
On Manta, you MUST do a factory reset after flashing the data partition or unlocking the device. For some reason it fails to boot without performing that step.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Yeah after my experience with toolkits I have leaned that the google sdk fastboot is the best method and you also learn the fastboot/adb commands and what's actually happening step by step.
midgetzombiekiller said:
Wow i haven't had my n10 long enough to help you much more. Sounds like you might have some corrupt files from wugrfresh download/install? Maybe download from another mirror and try again? good luck !!!! Keep me posted!
Click to expand...
Click to collapse
Ok, given all the feedback, especially with regards to corrupt items, I dug out an old laptop and was still getting the same problems, re-downloaded the 4.2.2 image and tried again.... and was more patient this time, and voila! back up and running!
Thanks to everyone who replied, I would not have persevered without your comments.
Lessons learned:
1) On Manta, you MUST do a factory reset after flashing the data partition or unlocking the device. For some reason it fails to boot without performing that step.
2) For me the downloads seem to have been unreliable, try, re-try, cry, weep, try again, punch the desk until your knuckles bleed, try some more and eventually you'll get there!
3) Be VERY patient. I was less patient than my normal impatient self when I saw how super lightning fast the N10 is.
Thanks again to everyone.
kipperfish said:
Ok, given all the feedback, especially with regards to corrupt items, I dug out an old laptop and was still getting the same problems, re-downloaded the 4.2.2 image and tried again.... and was more patient this time, and voila! back up and running!
Thanks to everyone who replied, I would not have persevered without your comments.
Lessons learned:
1) On Manta, you MUST do a factory reset after flashing the data partition or unlocking the device. For some reason it fails to boot without performing that step.
2) For me the downloads seem to have been unreliable, try, re-try, cry, weep, try again, punch the desk until your knuckles bleed, try some more and eventually you'll get there!
3) Be VERY patient. I was less patient than my normal impatient self when I saw how super lightning fast the N10 is.
Thanks again to everyone.
Click to expand...
Click to collapse
Glad to hear it worked out. I found out that wipe step the hard way.
Use the MD5 to verify your downloads if you have any doubts, i personally haven't had any failures
Sweet!
Sent from my Nexus 10 using xda premium
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.