Related
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.
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 guys,
My Yotaphone 2 is currently stuck in a boot loop (shows android logo, then black screen, repeat) after a software update. I can get to the 'Downloading...' screen via power + vol. key and so have tried adb/fastboot as suggested in other similar threads. ADB can't see the device, which I guess is probably normal since it isn't booted up, but fastboot seemingly can. I've tried flashing the TWRP recovery which seems to go through fine on the PC end but doesn't seem to do anything at all on the phone itself. Calling a fastboot reboot gets the phone back to the boot loop and power + vol. goes back to the 'Downloading...' screen.
I've also tried using the Yotaphone flashing tool to flash a full android image - this also looked like everything was operating OK on the PC end but didn't seem to change anything on the phone once the process was complete.
Is there anything I'm missing or anything else I can try? Any help/ideas much appreciated!
Cheers.
pjrj said:
Hi guys,
My Yotaphone 2 is currently stuck in a boot loop (shows android logo, then black screen, repeat) after a software update. I can get to the 'Downloading...' screen via power + vol. key and so have tried adb/fastboot as suggested in other similar threads. ADB can't see the device, which I guess is probably normal since it isn't booted up, but fastboot seemingly can. I've tried flashing the TWRP recovery which seems to go through fine on the PC end but doesn't seem to do anything at all on the phone itself. Calling a fastboot reboot gets the phone back to the boot loop and power + vol. goes back to the 'Downloading...' screen.
I've also tried using the Yotaphone flashing tool to flash a full android image - this also looked like everything was operating OK on the PC end but didn't seem to change anything on the phone once the process was complete.
Is there anything I'm missing or anything else I can try? Any help/ideas much appreciated!
Cheers.
Click to expand...
Click to collapse
Do you have any idea what caused the bootloop? (maybe installing xposed or something?)
When you keep vol-up pressed at (not after) the moment the phone vibrates during power on, you will end up in TWRP recovery. There you can at least wipe->factory reset. Don't do this if you have stuff on your phone you'd like to keep though. (you can try to rescue/backup those by trying "adb pull <path_to_file>" when the phone is booted into TWRP)
SteadyQuad said:
Do you have any idea what caused the bootloop? (maybe installing xposed or something?)
When you keep vol-up pressed at (not after) the moment the phone vibrates during power on, you will end up in TWRP recovery. There you can at least wipe->factory reset. Don't do this if you have stuff on your phone you'd like to keep though. (you can try to rescue/backup those by trying "adb pull <path_to_file>" when the phone is booted into TWRP)
Click to expand...
Click to collapse
It was caused by doing an OS update (wasn't rooted or modified), I've only since tried installing the TWRP recovery and using fastboot to flash an official image to fix the looping. Flashing TWRP appears to work according to flashboot but holding the volume up key at the vibrate on power on doesn't do anything sadly.
pjrj said:
It was caused by doing an OS update (wasn't rooted or modified), I've only since tried installing the TWRP recovery and using fastboot to flash an official image to fix the looping. Flashing TWRP appears to work according to flashboot but holding the volume up key at the vibrate on power on doesn't do anything sadly.
Click to expand...
Click to collapse
Maybe I should rephrase: the vol-up should already be pressed once the vibrate starts. For a timing-insensitive, fool-proof (no pun intended) way you can enable bootloader (like you did before: you get the Downloading... screen). Then keep vol-up and power pressed together, after 15 seconds the device reboots hard, keep both keys pressed until you see TWRP 'curtain' screen, then release.
Did you try to use the YotaFlasher Windows application to reinstall an official ROM and restore factory defaults? You can get it from here, also download a ROM for your region here.
i tried rooting my phone huawei p8 lite but got stuck at installing super su now i cannot start my device ..i cannot boot into flash mode or recovery ..i need help ...it wont even charge
pepeline said:
i tried rooting my phone huawei p8 lite but got stuck at installing super su now i cannot start my device ..i cannot boot into flash mode or recovery ..i need help ...it wont even charge
Click to expand...
Click to collapse
What's your build number what version of supersu did you try to flash?
Shutdown your device, put your current build onto 'dload' folder in the sdcard and press the following key combo: POWER, VOL-UP & VOL-DOWN, it should enable automatic update process
amageek said:
What's your build number what version of supersu did you try to flash?
Shutdown your device, put your current build onto 'dload' folder in the sdcard and press the following key combo: POWER, VOL-UP & VOL-DOWN, it should enable automatic update process
Click to expand...
Click to collapse
My phone restarts right at the logo when i press power vol up and vol down
pepeline said:
My phone restarts right at the logo when i press power vol up and vol down
Click to expand...
Click to collapse
Shut it down amd press those 3 keys combo.. upon seeing Huawei Logo and vibration, release the Power key while holding the other 2... That ought to do it
Man, your phone is badly bricked. If you don't have at least access to fastboot, then you're screwed.
Good for me to I have the same problem. I was trying to get to stock ( I have made it several times), but the last time was a fail... The whole process of sending firmware was ok. then a reboot and brick.
Now the huawei screen and the short vibration appears and shutdown.
I was trying everything.
In device manager the phone is displayed as mobile devices \ volume f:\ (drive letter)
in connected devices the phone is detected as
hi6210sft
Phone is not detected in fastboot or ADB.
I met this problem yesterday(I hope the identical ). Because I have two booting animations, one from Vodafone, I guess I shutdown early during installation. It just froze. Then it didn't boot and stock recovery didn't help
My solution needs some recovery software like twrp. Press three buttons at the same time until twrp mode. Copy zip file for SuperSU to phone or sdcard, then flash it. After that my phone works again.
You mentioned that you cannot start recovery. Try more. After installing twrp, starting it is quite annoying. Sometimes it just doesn't start or stock recovery starts. An alternative way is to go to whatever mode, and try adb or fast boot to reboot to recovery. Pressing button requires techniques which j don't have
I can't enter TWRP non combination is working for me. Installing firmware using dload from sd card also.
okay if non of these worked you can try flashing the whole update.app file by fastboot..
tools you will need
1- download the official huawei firmware from the official site
2- download Huawei Update Extractor
3- download minimal adb and fastboot
check the unbricking chapter of this thread
Note: to get in fastboot make sure you connected your phone to computer and press the vol down and power down buttons.. if none of these worked your phone is hard bricked .-. .. try opening the phone and reconnecting the battery worked with someone
if you need any help just pm me or replay on this thread hope that help you
Ok thx. I have already opened the phone to reconnect the battery
And then I was trying the combinations;
Battery connected vol- +power - Huawei logo and vibration and shutdown, no fastboot
Battery disconnected, vol-+power and connecting cable to phone - the same
Battery disconnected combination vol + vol - + ppwer, with sd card dload, the same
Battery connected combination vol + vol - power, sd card dload, the same
Any other suggestions?
The phone is recognized in Windows in device manager as mobile device as volume with a letter, I cant change the drivers to the right ones. I can't enter the storage it's unrecognized format.
Any other suggestions?
mercom said:
Any other suggestions?
Click to expand...
Click to collapse
it is easy to suggest others.. I too advised you.. but today i am facing the same problem...
what I tried:
Reinstalling the same ROM using dload method
Upgrading to other ROM (using both dload and flashing 4 image method)
Downgrading
Restoring from the backup
At one point, the phone booted up all well except the Wifi Module... So I flashed another ROM and stuck again...
the worst thing that I don't have any connection to fastboot Each firmware installation method fails
mercom said:
the worst thing that I don't have any connection to fastboot Each firmware installation method fails
Click to expand...
Click to collapse
yes, mine too... or I could say flashing succeeds but there's some problem with the boot partition... will get my phone today from the Customer Care and try again (if they can't repair).
you can try removing the back cover and unplugging the battery... that is one of the few things I will do today as I get my phone back..
mercom said:
the worst thing that I don't have any connection to fastboot Each firmware installation method fails
Click to expand...
Click to collapse
ok made it back.. just flashed the boot.img from b594 (the one I was using when my mobile got bricked)... somehow made it back. But now I am having a problem with the battery. It doesn't charge when the device is switched on, only when the device is switched off... will see for few days, if there's problem will take it back to service centre again
I have already removed back cover and was trying to reconnect the battery to do clear run. But the only thing is discovered in windows is a driver for storage and I can't change the driver to ADB or FASTBOOT
Now I have connected phone w PC on adb devices I see only emulator-5554 device. In Device manager I see the storage as a Mobile Device.
Nope it was Bluestacks
mercom said:
I have already removed back cover and was trying to reconnect the battery to do clear run. But the only thing is discovered in windows is a driver for storage and I can't change the driver to ADB or FASTBOOT
Now I have connected phone w PC on adb devices I see only emulator-5554 device. In Device manager I see the storage as a Mobile Device.
Nope it was Bluestacks
Click to expand...
Click to collapse
Switch off your device and then connect it to PC but just hold the volume- key.. that should get you in fastboot mode... I did that and then flashed the boot.img of the current ROM. This should boot it up...
Nope it doesn't work I was trying it already
Hi,
I'm in the process of rooting my G6 (870H) but I've been running in an issue which doesn't seem to happen to other users.
I have followed all the steps (unlocking the bootloader etc), but when I flash the twrp img, reboot (I've tried numerous times both with fastboot reboot and simply by holding the PWR + VOL- ) and then select 2 times Yes when I run into the factory reset screen it shows me the TWRP loading screen (which I guess is normal ) but instead of going into the twrp options afterwards, the phone simply boots as it usually would.
Does anyone know anything about this issue ? I couldn't find any information about it.
I had this happen, make sure after the screen goes black after booting into twrp, leave it alone. So from bootloader Volume + Power then when LG logo pops up stop pressing power but quickly hold it down again. Then when the screen changes don't press anything until booted into twrp.
If this doesn't work, I remember when I first ran into a soft bricked device. It refused to boot into twrp even though I had rooted it. Just keep trying and one time you'll get lucky, I'm not sure why this happens, but it's just part of life, so keep at it and maybe try a different twrp.