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.
Related
OK, so I flashed the wrong ROM today (I9000HVJH1) and the phone now boots into recovery everytime the battery is inserted. I have tried all the tricks to get back to download mode with no luck. The device is recognized by the USB in recovery and was able to push the root update file but can not get it to apply sdcard:update.zip (just sits there and doesn't respond to the power button unless i hold it). Interesting thing is when I plug the USB in and insert the battery, it never goes to charging, it boots into recovery.
Tried:
1. Plug USB
2. Hold vol up (and down but the keys are now backwards in recovery)
3. Insert battery
and
1. Power down (removed battery)
2. Hold vol up + down + power
and
1. Hold vol up (and down too for a few hundred times)
2. Hold power until Samsung logo then release
and
all combo's with and without the USB plugged into the phone.
Beside the tricks shown on the forum, can anything think of a way to get this phone into download mode instead of it constantly booting into recovery? ADB see's the device, just no root access or knowledge of how to get it to apply the update.zip that would root the device.
Thanks~!
http://forum.xda-developers.com/showthread.php?t=741027&page=3
Wrong section. This belongs in general...
Sent from my messenger rabbit
UPDATE!!
After going to T-Mobile on Monday to buy a new Vibrant, I started to think about how to get the "bricked" one working again. I was able to admit defeat for long enough to get a new one but was bothered that I couldn't fix my old one.
I started to think about what I could and couldn't do with the "bricked" one. It would constantly boot start to Android Recovery with error about CSC. No matter what combination of buttons pressed, held, release, the darn phone would never get back to a download mode. Since it could never boot into the OS, ADB seemed impossible. The GOOD news (as it turns out) was when it booted into recovery if I disconnected the USB and reconnected, my computer recognized it and Odin saw it on COM10. I began to look at the batch file for the one click root and noticed the line "adb reboot download". I had messed with ADB the day I screwed up the phone but always tried to do commands after typing "adb shell" and without super user access, I felt doomed. Last night I thought what the heck and powered up the old Vibrant and it went straight to recovery. After another 45 minutes of trying to manually put it into download mode I opened a command prompt and typed "adb reboot download" and the freaking phone rebooted into download mode!!!! So after flashing back to stock I now have fixed the phone
So for anyone who can't get their Vibrant to stop rebooting itself into recovery here is a simple breakdown of what I did.
1 - Power up phone (mine went straight to recovery)
2 - Un-plug the USB and plug it back in (computer should recognize the connection)
3 - Open command prompt and change to the directory that has adb.exe
4 - Type "adb kill-server" and then enter
5 - Type "adb reboot download" and then enter
6 - Phone should reboot into download mode and ready to flash
Make sure you have Odin open with the pit and pda file loaded as there seems to be only a short window of time in which the phone will accept the download and get the status bar moving. If you wait too long, repeat the steps above and start the flash quickly.
I hope this helps someone out that might be experiencing the same problem as me.
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"
Last week, my yotaphone 2 informed that there is a system update from yotaphone. I downloaded and updated but then my phone cannot work. It show only black start screen with word "Android" until battery empty.
I tried to android recovery mode (hold power and volume up),
it show that the error is "e:cannot load volume /misc!".
And I do not know how to solve that problem.
Please help me!
leviet4 said:
Last week, my yotaphone 2 informed that there is a system update from yotaphone. I downloaded and updated but then my phone cannot work. It show only black start screen with word "Android" until battery empty.
I tried to android recovery mode (hold power and volume up),
it show that the error is "e:cannot load volume /misc!".
And I do not know how to solve that problem.
Please help me!
Click to expand...
Click to collapse
You can probably recover.
To reflash a full firmware image you could try the relatively user-friendly yotaflasher application and ROM images from here. I haven't used this myself, but it's software by Yota, so should be safe. You can ask it not to touch /data, to preserve apps, settings etc.
A less user friendly way to reflash a full firmware image:
- Download a full firmware image (EU 1.60 flashable version here, let me know if you require a different one)
- With the phone off, press vol down + power until you see "Downloading ...."
- If you can't turn the phone off normally, keep vol down + power for at least 15 seconds till phone reboots, keep holding till you end up with "Downloading ...."
- connect to a PC with adb+fastboot with a USB cable
- You can now boot TWRP image (fastboot boot recovery_twrp_yd201_alpha2.img , see here.
- if you have important files on your phone, you can back them up now by using adb shell/adb pull (e.g. adb pull /sdcard/Pictures/yeti_sighting.jpg)
- In TWRP go to advanced -> sideload and confirm
- now you can sideload a ROM image from the PC with adb sideload <image>.zip, it should show progress while it's uploading the firmware. If it errors, you probably haven't confirmed initiating sideload in previous step.
- wipe cache&dalvik and reboot
thank you, the first way worked and my phone runs normally now.
thank you
Help please
SteadyQuad said:
You can probably recover.
To reflash a full firmware image you could try the relatively user-friendly yotaflasher application and ROM images from here. I haven't used this myself, but it's software by Yota, so should be safe. You can ask it not to touch /data, to preserve apps, settings etc.
A less user friendly way to reflash a full firmware image:
- Download a full firmware image (EU 1.60 flashable version here, let me know if you require a different one)
- With the phone off, press vol down + power until you see "Downloading ...."
- If you can't turn the phone off normally, keep vol down + power for at least 15 seconds till phone reboots, keep holding till you end up with "Downloading ...."
- connect to a PC with adb+fastboot with a USB cable
- You can now boot TWRP image (fastboot boot recovery_twrp_yd201_alpha2.img , see here.
- if you have important files on your phone, you can back them up now by using adb shell/adb pull (e.g. adb pull /sdcard/Pictures/yeti_sighting.jpg)
- In TWRP go to advanced -> sideload and confirm
- now you can sideload a ROM image from the PC with adb sideload <image>.zip, it should show progress while it's uploading the firmware. If it errors, you probably haven't confirmed initiating sideload in previous step.
- wipe cache&dalvik and reboot
Click to expand...
Click to collapse
I have yotaphone model YD206, but I am in the USA and would like to root and load the best rom I can for my device, it doesn't even have google apps on it. Thanks for any and all help
Kevinreid1 said:
I have yotaphone model YD206, but I am in the USA and would like to root and load the best rom I can for my device, it doesn't even have google apps on it. Thanks for any and all help
Click to expand...
Click to collapse
Root the phone using methods written on this forum > download build 1.60 flammable zip > flash that.
If all you want is Google apps then root the phone then download and flash a gapps package. The full Yota build zip is recommended though.
Can't download yotaflasher application from the link... does anybody have the exe file?
SteadyQuad said:
You can probably recover.
To reflash a full firmware image you could try the relatively user-friendly yotaflasher application and ROM images from here. I haven't used this myself, but it's software by Yota, so should be safe. You can ask it not to touch /data, to preserve apps, settings etc.
A less user friendly way to reflash a full firmware image:
- Download a full firmware image (EU 1.60 flashable version here, let me know if you require a different one)
- With the phone off, press vol down + power until you see "Downloading ...."
- If you can't turn the phone off normally, keep vol down + power for at least 15 seconds till phone reboots, keep holding till you end up with "Downloading ...."
- connect to a PC with adb+fastboot with a USB cable
- You can now boot TWRP image (fastboot boot recovery_twrp_yd201_alpha2.img , see here.
- if you have important files on your phone, you can back them up now by using adb shell/adb pull (e.g. adb pull /sdcard/Pictures/yeti_sighting.jpg)
- In TWRP go to advanced -> sideload and confirm
- now you can sideload a ROM image from the PC with adb sideload <image>.zip, it should show progress while it's uploading the firmware. If it errors, you probably haven't confirmed initiating sideload in previous step.
- wipe cache&dalvik and reboot
Click to expand...
Click to collapse
glax87 said:
Can't download yotaflasher application from the link... does anybody have the exe file?
Click to expand...
Click to collapse
Just click on the YotaPhoneFlasher folder then click the file (yotaphone2_flasher.exe), and save to your harddisk.
Or you can try this link straight to the yotaphone2_flasher.exe file.
https://drive.google.com/file/d/0B0KC5E0zkBYmcHAzMEFKaHRvZ3M/view?usp=sharing
HOW
leviet4 said:
thank you, the first way worked and my phone runs normally now.
thank you
Click to expand...
Click to collapse
Dude I've just bought my phone, and it has the same problem. But I'm a complete noob, how did you fix it? Please, i've just bought it.
On RU build 134 when I tried to swap users my user with Defaut user, the phone blocked, the display is on (time is the same when first happend - just a freeze image) but I can't do nothing on phone. Is a way to reset? because on a normal way I would remove battery but yota dont have this option.
queser.info said:
On RU build 134 when I tried to swap users my user with Defaut user, the phone blocked, the display is on (time is the same when first happend - just a freeze image) but I can't do nothing on phone. Is a way to reset? because on a normal way I would remove battery but yota dont have this option.
Click to expand...
Click to collapse
The analogue method of pulling out the battery is pressing the POWER button for at least 10 seconds. The phone will reboot.
Thanks, I pushed vol down + Power and the phone restarted normaly.
PS: If you know where to get a book from Алекса́ндр Солжени́цын - Aleksandr Solzhenitsyn to read on yota display, send me.
SteadyQuad said:
You can probably recover.
To reflash a full firmware image you could try the relatively user-friendly yotaflasher application and ROM images from here. I haven't used this myself, but it's software by Yota, so should be safe. You can ask it not to touch /data, to preserve apps, settings etc.
A less user friendly way to reflash a full firmware image:
- Download a full firmware image (EU 1.60 flashable version here, let me know if you require a different one)
- With the phone off, press vol down + power until you see "Downloading ...."
- If you can't turn the phone off normally, keep vol down + power for at least 15 seconds till phone reboots, keep holding till you end up with "Downloading ...."
- connect to a PC with adb+fastboot with a USB cable
- You can now boot TWRP image (fastboot boot recovery_twrp_yd201_alpha2.img , see here.
- if you have important files on your phone, you can back them up now by using adb shell/adb pull (e.g. adb pull /sdcard/Pictures/yeti_sighting.jpg)
- In TWRP go to advanced -> sideload and confirm
- now you can sideload a ROM image from the PC with adb sideload <image>.zip, it should show progress while it's uploading the firmware. If it errors, you probably haven't confirmed initiating sideload in previous step.
- wipe cache&dalvik and reboot
Click to expand...
Click to collapse
Sir, i can't even get into recovery mode, i get this problem like it suddenly happen and my battery was 38%.. i was on facebook and it hang and then reboot and then stuck at "POWERED BY ANDROID".
I try to get into recovery mode by pressing volume up + power button, it restart again to "POWERED BY ANDROID"
When i pressing volume down + power button, it show downloding... , and i try to flash it using yotaflasher with HK Firmware 5.0.
When it is done, the phone reboot.
And it still stuck at "POWERED BY ANDROID"
What is the real problem ?
Please help!!!
While trying to solve the network issue on my Yotaphone 2 I managed to brick my phone. He is dead! But since it is a Snapdragon inside it can be fixed.
I need a help from someone who has rooted his Yotaphone2!
I need files from Yotaphone2 software: rawprogram0.xml and patch0.xml
Please!!!
hlmboy said:
Sir, i can't even get into recovery mode, i get this problem like it suddenly happen and my battery was 38%.. i was on facebook and it hang and then reboot and then stuck at "POWERED BY ANDROID".
I try to get into recovery mode by pressing volume up + power button, it restart again to "POWERED BY ANDROID"
When i pressing volume down + power button, it show downloading... , and i try to flash it using yotaflasher with HK Firmware 5.0.
When it is done, the phone reboot.
And it still stuck at "POWERED BY ANDROID"
What is the real problem ?
Click to expand...
Click to collapse
You need to keep pressing the power up button after the showing of "POWERED BY ANDROID", the power does not need to be pressed after then.
If you can still not reach recovery, you probably have a broken recovery (maybe wrong version) and something else is messed up.
When you flash recovery, you need to instantly go into recovery mode by pressing +/up on calling the according command
(fastboot reboot).
It does not look like you changed file system related things, did you change anything on your system/with root permissions?
Are you sure the installation process went without failure etc?
Getting out the cause (kernel logs etc) would be a bit hard without getting into recovery mode[and maybe also nonworking kernel], like stated out here
https://android.stackexchange.com/q...n-i-recover-files-from-a-phone-that-wont-boot
Hi,
I'm not very experienced with those root things and followed a tutorial to do so.
I unlocked the bootloader, had TWRP installed and root. This worked. Now I wanted to remove Root and TWRP and go back to the original state. I couldn't find the stock recovery file, so I installed the P996A04V1.3.0B13_MR2_sd_ssl.zip via TWRP from the SD Card. Till here it worked. I could enter the stock recover and boot the phone.
Then Android wanted to install a security update. I allowed it and this is where the problem started.
The install process stood still on 25% for minutes. I thought it stuck and pressed and hold the power button to reboot that I can wipe the memory. But nothing happened. But the installation Process continued suddenly. I had the feeling that this power key worked like a skip key. So maybe it didn't install a file where it was stuck.
After the installation reached 100% the screen switched to black and nothing worked anymore. I couldn't restart the phone or anything but I think the phone was doing something cause it consumed electricity. When I checked the phone hours later I noticed it was empty.
I can reach the unlocked bootloader now, but none of the selections works. Doing nothing to boot or select Recovery lead to black screen and stuck. Then I have to wait until the battery is empty again. Fastboot, Power Off just restart the phone and I end in the Bootmenu again. I can't even fully charge the phone. As soon as it has enough power to start the Bootmenu appears. So I don't see the display of the charging process.
I don't understand how this could happen. I tried different key combinations when the phone had enough electricty to start. The phone always restarts and end in the bootmenu. Only when I press all three keys it's standing still on the ZTE Logo screen but as soon as I release the keys I end again in the bootmenu.
How can I force another Update?
regards
Let' start with the basic questions:
Do you have proper backup of your data?
Which Android Version did your Axon had before it went unusable?
You could try to reflash TWRP.
Boot your phone into bootmode.
Download a proper TWRP Image on your PC (https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547)
Open a cmd shell (press the windows key and type 'cmd' -> press enter)
Navigate to the folder where the TWRP Image is stored ('
Code:
cd C:\Users\[I]YOUR_USER_NAME[/I]\Downloads\
')
Type: '
HTML:
fastboot flash recovery [I]TWRP_IMG_NAME.img[/I]
'
Afterwards you could try to reboot into recovery mode.
I don't have a backup. But there isn't something imortant on the phone that I want to keep. I can do a full reset and reinstall, too.
Android must have been the latest offical availabe what's in the file. Was it Android 8? V1.3.0B13
The fastboot mode doesn't work. The screen turns black and the LED blinks red but only for a moment. Then the phone restarts and I'm in the bootmenu again. Windows doesn't recognize it as device.
Is there a way to force it to do an update from my SDCard without it needed to be connected to a PC?
Stevie123 said:
I don't have a backup. But there isn't something imortant on the phone that I want to keep. I can do a full reset and reinstall, too.
Android must have been the latest offical availabe what's in the file. Was it Android 8? V1.3.0B13
The fastboot mode doesn't work. The screen turns black and the LED blinks red but only for a moment. Then the phone restarts and I'm in the bootmenu again. Windows doesn't recognize it as device.
Is there a way to force it to do an update from my SDCard without it needed to be connected to a PC?
Click to expand...
Click to collapse
I don't know of any.
But you could boot into EDL Mode (Press and hold Both Volume button and then press the power button) and flash a Stock EDL rom from the Download Center i have linkd before.
It's not visible for the PC. The only thing I see is the charging screen when its total empty and you can't even boot as. As soon as it has enough power to switch to the normal screen the bootloader appears and when I do nothing the screen turns black and nothing happens. I don't even know if it is charging. The LED is off.
Follow this guide to unbrick it and then use MiFlash and flash an EDL ROM
https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229
So I hadn't tried to flash a ROM on my "tube" Shield TV 2019 until the Experience 9 ROMs just leaked. I didn't realize it didn't have a USB port. I have been flashing ROMs on Android phones for over a decade, so I'm good there but what about Fastboot access via network TCP/IP or UDP? I was able to ADB to the Shield with "ADB connect [IP address]" but Fastboot doesn't see the unit at the same IP and I've looked on my router's device list and don't see anything. I have the latest 1.4.3 ADB/Fastboot tools.
So no access to flashing using the SD card slot, ethernet, or network?
THANKS!
KeepingItCuttingEdge said:
So I hadn't tried to flash a ROM on my "tube" Shield TV 2019 until the Experience 9 ROMs just leaked. I didn't realize it didn't have a USB port. I have been flashing ROMs on Android phones for over a decade, so I'm good there but what about Fastboot access via network TCP/IP or UDP? I was able to ADB to the Shield with "ADB connect [IP address]" but Fastboot doesn't see the unit at the same IP and I've looked on my router's device list and don't see anything. I have the latest 1.4.3 ADB/Fastboot tools.
So no access to flashing using the SD card slot, ethernet, or network?
THANKS!
Click to expand...
Click to collapse
I'm sorry, this is slightly off topic, but consider it a bump. haha. A quick question. Do you have a link for the experience rom? I would love to look at it, or do you know what OS they are rolling?
Hello,
trying to do the same but fastboot mode is as far as I get as well. Any ideas on how to flash the image on the tube?
@jenneh
Here you go . The OS is Android 11
KeepingItCuttingEdge said:
So I hadn't tried to flash a ROM on my "tube" Shield TV 2019 until the Experience 9 ROMs just leaked. I didn't realize it didn't have a USB port. I have been flashing ROMs on Android phones for over a decade, so I'm good there but what about Fastboot access via network TCP/IP or UDP? I was able to ADB to the Shield with "ADB connect [IP address]" but Fastboot doesn't see the unit at the same IP and I've looked on my router's device list and don't see anything. I have the latest 1.4.3 ADB/Fastboot tools.
So no access to flashing using the SD card slot, ethernet, or network?
THANKS!
Click to expand...
Click to collapse
Well I figured it out. First copy the downloaded image to the external sd card of the tube. Then:
When you reboot to fastboot using wifi ADB, then first unlock the bootloader.
Then choose "Boot recovery kernel" from the menu. The power button is located above the HDMI port on the tube.
When the dead android image appears, press the power button for 3 seconds and then release.
You should see the recovery menu. If you still see the dead android, then repeat the process by holding the power button pressed for 3-4-5-6 seconds. It can be tricky.
Once in the menu, choose the sd card.
Choose the file.
The process will start. and it should complete after a couple of minutes.
You are then done.
I did some extra steps:
I performed a factory reset and cleared cache from the recovery menu, although this happens automatically when you unlock the bootloader.
I then got back to the fastboot menu and locked the bootloader again. Otherwise you get a warning every time you boot the device.
Be ware that locking/unlocking the bootloader, erases the data of the user partition and the device needs to be setup as from a factory reset. This is by design.
Here is a link with all the images.
Cheers
m33ts4k0z said:
Well I figured it out. First copy the downloaded image to the external sd card of the tube. Then:
When you reboot to fastboot using wifi ADB, then first unlock the bootloader.
Then choose "Boot recovery kernel" from the menu. The power button is located above the HDMI port on the tube.
When the dead android image appears, press the power button for 3 seconds and then release.
You should see the recovery menu. If you still see the dead android, then repeat the process by holding the power button pressed for 3-4-5-6 seconds. It can be tricky.
Once in the menu, choose the sd card.
Choose the file.
The process will start. and it should complete after a couple of minutes.
You are then done.
I did some extra steps:
I performed a factory reset and cleared cache from the recovery menu, although this happens automatically when you unlock the bootloader.
I then got back to the fastboot menu and locked the bootloader again. Otherwise you get a warning every time you boot the device.
Be ware that locking/unlocking the bootloader, erases the data of the user partition and the device needs to be setup as from a factory reset. This is by design.
Here is a link with all the images.
Cheers
Click to expand...
Click to collapse
First of all, THANK YOU for this share~ ~! secondly, would you happen to have any idea why my usb ports have stopped working all of a sudden. I swear I didn't step on the shield this time. Lol
m33ts4k0z said:
he menu, choose the sd card.
Choose the file.
The process will start. and it should complete after a couple of minutes.
You are then done.
I did some extra steps:
Click to expand...
Click to collapse
m33ts4k0z said:
Hello,
trying to do the same but fastboot mode is as far as I get as well. Any ideas on how to flash the image on the tube?
@jenneh
Here you go . The OS is Android 11
Click to expand...
Click to collapse
false alarm Sir!!! I plugged my mouse in where the usbc cord usually goes, and i have access back! i was about to go return this sield to bestbuy for the 5th time for another hahaha
I want to go back from Android 11 to Android 9. It is possible to download a ROM for Shield 2019 Non Pro 8GB ATV 8.2.3? THX
There are links to the recovery firmware 8.2.3 but I can't get past the agree button that shows when klicking on the link..
It could be my old laptop.. but here's the link..
Gameworks Download Center
Get the latest Gameworks software for your game development work.
developer.nvidia.com
Sinse the update most of my aps are gone or not usable..
I can not fint the shield on my network.. and there is no installable apk showing up in any file manager.
I wil do my best to get back to android 9.
Tried to go back using the 8.2.3 recovery img.. but no luck.
I get an error saying cant flash over newer firmware.
Ugg... I didn't see this post that you can't downgrade until I tried it myself and also got the error.
Anybody have any possible work around ideas?
The same here:
The method I used is the one below according to nvidia's instructions:
Hardware Method:
- Disconnect power cable
- Connect power cable to SHIELD and hold down the remote locator button
- Release the keys once you see the fastboot menu on the screen (it's
red in color)
- If the standard boot process starts, disconnect the power cable and
repeat
the process
*******************************************************************************
FASTBOOT MENU NAVIGATION
*****
Once in fastboot mode (it's red in color), navigate the menus using the
remote locator button on the device.
Short press to navigate and long press for ~2s to select.
*******************************************************************************
FLASHING THE DEVICE
*****
To flash the recovery image to your SHIELD from fastboot, download the
image package.
- Download the image package. Copy the same downloaded zip file with
name
'nv-recovery-image-shield-atv-2019_.zip' to a uSD card that is FAT32
formatted
(where corresponds to the image version of the update being
installed).
Insert uSD card into the uSD card slot on the device
- in fastboot mode select Factory Data reset (opp in Recovery menu
scegli wipe data/factory reset)
- Enter recovery kernel by selecting the option "Boot recovery kernel"
from fastboot menu
- Once the device boots into recovery kernel, you will see a "No
command" image on the
screen
- Long press the remote locator button for ~2s and release button.
Recovery menu should show up (it's blue and green).
If not, please try to long press the button again
- On the recovery menu, select the option "apply update from SD card"
(navigate using short
press of remote locator button and long press ~4s to select and
release button)
- From the SD card contents, select the image package
- At anytime if the display goes back to the "No command" picture, press
the button for ~2s and release button
to go back to the previous screen
- Once the image is selected, the update process should start
Unfortunately the process interrupts with "newer build ....error status
7". I deleted the first two rows of UPDATE-SCRIPT, repacked in ZIP and
reflashed but in vain!! the error was:"Signature failure"
I also use SIGNAPK to sign the new ZIP, but in vain....
Any help?
Does anybody found solution to force downgrade (2019 nonPRO of course)?
Hello, I have a device that at this moment, after a failed update, ended up blocking..Now I turn it on, I feel that the nvidia heats up, but I don't have a signal on the television or anything, I've tried to do a reset but I haven't been successful because I am unable to enter to the fastboot screen... Does anyone who has gone through the same problem have any tips? Any help would be nice...Thanks
kuki68ster said:
Hello, I have a device that at this moment, after a failed update, ended up blocking..Now I turn it on, I feel that the nvidia heats up, but I don't have a signal on the television or anything, I've tried to do a reset but I haven't been successful because I am unable to enter to the fastboot screen... Does anyone who has gone through the same problem have any tips? Any help would be nice...Thanks
Click to expand...
Click to collapse
This is exactly what's happening to me. For some reason the network stopped working. I tried to see what happens if I factory reset. After the factory reset the device no longer displays anything. It does turn on and I can turn the tv and receiver on and off with the shield remote. I can enter the bootloader though.
Is this a coincidence or did the latest update screw something up?