Help With a (Potentially) Soft-Bricked Sony Xperia Z2 Tablet - Xperia Z2 Tablet Q&A, Help & Troubleshooting

Hey guys,
I am sorry if I am in the wrong place or am asking something wrong. This is my first time using these forums (and forums in general). If I need to be somewhere else kindly redirect me.
Anyway, I was with Verizon for a while but after some shady stuff I decided to break up with them. Beforehand I had bought outright a Sony Xperia Z2 Tablet. Because I did not want anything Verizon on it I decided to root it, and flash a good ROM onto it (Cyanogenmod was my idea, but at the time I don't think they supported it? I'm not good with ROMS). Anyway, the rooting was completely successful and I had a custom recovery (TWRP) installed. I was ready to flash the ROM. Unfortunately, I wasn't paying attention and grabbed the wrong ROM. What ended up happening is when I attempted to reboot after "flashing", the device didn't show anything on the screen and just kept vibrating. After some digging around I found it might be "soft-bricked". I had at one time found a guide that told me how to undo this by using SDK Tools and Fastboot Mode (blue LED), but cannot find the guide anymore.
I was wondering if ANYONE could help me undo this mistake, and get the tablet back to it's original state or with a nice compatible ROM. I am currently in Fastboot mode and it is plugged into my ASUS Laptop running Windows 7. Any and all help would be GREATLY appreciated. Thank you so much for taking time to read this.
EDIT: So a breakdown is I cannot interact with the tablet directly. There is absolutely no interface. Just a screen that won't turn on. Meaning if there is a method it can't be done on the tablet. The old guide I found was explaining how to do it through Windows while the tablet was plugged into it via USB.
Also the bootloader was never unlocked so I think that was also an issue.

First of all, if your bootloader is locked, you cannot install CM because you cannot change the Kernel. You can only use Sony-certified Kernels which won't work with CM. So Sony-based ROMs are your only options
But what you can do is:
- Go into fastboot mode (turn off your tablet, connect it to your PC and press volume up. If the blue LED shows up, you are in fastboot)
- With fastboot, you should be able to flash a ROM (preferably Android 4.4, so you can root again)
- Then root, install dual recovery
- Flash the correct ZIP
Alternative:
- Unlock Bootloader
- Flash recovery
- Flash CM

BabelHuber said:
First of all, if your bootloader is locked, you cannot install CM because you cannot change the Kernel. You can only use Sony-certified Kernels which won't work with CM. So Sony-based ROMs are your only options
But what you can do is:
- Go into fastboot mode (turn off your tablet, connect it to your PC and press volume up. If the blue LED shows up, you are in fastboot)
- With fastboot, you should be able to flash a ROM (preferably Android 4.4, so you can root again)
- Then root, install dual recovery
- Flash the correct ZIP
Alternative:
- Unlock Bootloader
- Flash recovery
- Flash CM
Click to expand...
Click to collapse
Can you simplify this? Where do I find the ROM (again, this was a tablet from Verizon so I assume on top of the Sony ROM I need the Verizon version of it?) And I understand I cannot install CM unless the bootloader is unlocked; do you know how to do this?
I'm confused by the first set of instructions as I cannot use the tablet directly. How will I flash the ROM (and which is the right ROM and where can I find it?) through the computer since the tablet can't be interacted with. There is absolutely no interface to interact with whatsoever. Which ROM do I download for the Verizon Sony Xperia Z2 Tablet and how do I flash it using Fastboot? I assume I do it thru my computer?

Sorry, but you'll have to Google a little bit - I haven't had your exact problem.
But as long as you can get into fastboot mode, nothing is lost.
There also is the Sony ftf tool or so, the Windows program name is Emma. This should be easier than using fastboot.
Also there is a sony site for bootloader unlocking. You can check whether your bootloader can be unlocked at all.

Related

[Q] Create stock recovery update.zip from CWM (6+) backup?

I have two identical nexus s phones.
Phone 1:
- has no usb connectivity, and thus can't be used with fastboot or adb
- unlocked bootloader
- stock jellybean
Phone 2:
- rooted
- has CWM 6.0.3.1 installed
- stock jellybean
I've taken a backup of phone 2 and want to flash it using the stock recovery on phone 1. I'm on OS X.
I've found a couple threads on this but they're all leading to dead ends. One used a utility called unyaffs, but the CWM file format has changed to use hashed blobs so that 's not going to work.
I've also seen a couple posts saying that CWM had a "soon to be released" option to create an update.zip file, but I don't see that option. Those posts are from last August. That sounds great if it existed and the image could be used with stock recovery.
All I really need to do is flash the bootloader from phone 2 on to phone 1 (I previously flashed the wrong bootloader on phone 1 which led to the loss of usb, which is what I'm trying to fix.) I tried zipping the correct bootloader image from the google download page and installing from stock recovery but it refuses to flash that image. (Not sure if fastboot images can be flashed in recovery mode?)
Argh, need a little help here.
Thanks in advance.
slide mon said:
I have two identical nexus s phones.
Phone 1:
- has no usb connectivity, and thus can't be used with fastboot or adb
- unlocked bootloader
- stock jellybean
Phone 2:
- rooted
- has CWM 6.0.3.1 installed
- stock jellybean
I've taken a backup of phone 2 and want to flash it using the stock recovery on phone 1. I'm on OS X.
I've found a couple threads on this but they're all leading to dead ends. One used a utility called unyaffs, but the CWM file format has changed to use hashed blobs so that 's not going to work.
I've also seen a couple posts saying that CWM had a "soon to be released" option to create an update.zip file, but I don't see that option. Those posts are from last August. That sounds great if it existed and the image could be used with stock recovery.
All I really need to do is flash the bootloader from phone 2 on to phone 1 (I previously flashed the wrong bootloader on phone 1 which led to the loss of usb, which is what I'm trying to fix.) I tried zipping the correct bootloader image from the google download page and installing from stock recovery but it refuses to flash that image. (Not sure if fastboot images can be flashed in recovery mode?)
Argh, need a little help here.
Thanks in advance.
Click to expand...
Click to collapse
ok your post isnt making sense. first of all how did you flash thethe wrong bootloader to phone 1? and when you compare the phones bootloaders, what is the bootloader version number for each one? so what youre saying is that phone 1 will never give you an adb connection at all, even when youre booted into android? when you plug phone 1 into the computer from within android what happens? and when you boot phone 1 into bootloader and execute fastboot mode then connect it to your computer do you see anything when you run the command ./fastboot devices? or ./adb devices when youre in adb mode on your phone? if your computer can see phone 2 and not phone 1 at all via usb then there is likely a problem with the usb port on your phone 1. you should be able to boot directly into fastboot mode by holding vol up and power button while powering on the phone, then it should take you straight to fastboot mode where you can then connect to the computer. remember to put the phone in fastboot mode then connect sometimes the computer wont see the phone if it was already plugged in upon entering fastboot mode/
haxin said:
ok your post isnt making sense. first of all how did you flash thethe wrong bootloader to phone 1? and when you compare the phones bootloaders, what is the bootloader version number for each one? so what youre saying is that phone 1 will never give you an adb connection at all, even when youre booted into android? when you plug phone 1 into the computer from within android what happens? and when you boot phone 1 into bootloader and execute fastboot mode then connect it to your computer do you see anything when you run the command ./fastboot devices? or ./adb devices when youre in adb mode on your phone? if your computer can see phone 2 and not phone 1 at all via usb then there is likely a problem with the usb port on your phone 1. you should be able to boot directly into fastboot mode by holding vol up and power button while powering on the phone, then it should take you straight to fastboot mode where you can then connect to the computer. remember to put the phone in fastboot mode then connect sometimes the computer wont see the phone if it was already plugged in upon entering fastboot mode/
Click to expand...
Click to collapse
I was trying to downgrade the phone to ICS using the factory image from google. I picked the wrong image from the google site (picked soju, needed sojus) and flashed it using fastboot. As soon as I flashed the wrong bootloader the USB connection stopped working so I didn't flash the radio or os. I no longer can connect to the phone using fastboot or adb, usb debugging stopped working. The USB debugging option is set in developer options. So, trying to get the phone working now without USB. Hope that makes sense now. :good:

[Q] unable to get to bootloader or fastboot

hi,
i am trying to install CWM recovery on my phone (eventually want to install custon rom)
The phone is a huawei inspira, there no development for this phone. No info anywhere..
Withins the phones readme, it says its a U8666E, so going by the little development for that phone i am trying to install CWM.
I was able to root the phone, and i think i unlocked hte boot loader too (using the unlockbootloader.zip).
I have tried really hard, but am not able to install CWM as the phone is not coming in bootloader mode.
if i press hte power + vol down button phone is stuck in huawei logo (as it should) but PC does not detect it.
If i reboot bootloader (from adb) it just does a normal reboot.
i have tried a whole lot of things (new pc / usb port / cables / drivers etc etc). I every tried putting recovery on sdcard and flashing from terminal emulator of phone with no luck..
i am at a point where i am ready to flash the rom directly.. (risky i know).. but looks like everythong i want to do required me to go to bootloader mode.
I am not begening to think the carrier of my phone (tracphone) has locked the phone so i cant get into bootloader mode.
an any of you experts help me with my problem?
1) how to verify if the bootloader is unlocked?
2) can i flash CWM OR even a custom ROM with out getting into bootloader mode?
3) i have done a nandroid backup of the phone and kept a copy on external SD as well as PC< how do i restore the backup (if required) without CWM?

Bricked my phone please help

Okay, so i am using a xperia z2, cant rmb the version of the firmware, but i successfully rooted my device so i went on to try and flash cm11 onto my device. However, upon flashing cm11 and gapps into my phone through dual recovery i was no longer able to boot up my phone. Holding the power switch causes the device to vibrate, like perhaps every two seconds, but does nothing meaningful. Holding the powerswitch and the volume up key boots into fast boot, which is just a blank screen, but with the blue led that i read on the internet meant fastboot. Problem is, I am unable to get windows to install the relevant drivers for S1 Fastboot as it is displayed on my device manager window, and nothing i try will help. Ive downloaded usb drivers from numerous sources, including but not limited to flashtool, and nothing can get the fastboot to be recognised by the computer. Kindly advise on what i could do to restore my phone please! any help is greatly appreciated!!!!
I live in Singapore and i understand that bootloaders are by default unlocked? I'm not sure if i have to install any form of kernel , but i have a feeling this may be the cause of the problem? Please be kind, I am new to this entire rooting business. Once again any assistance is greatly appreciated!
http://forum.xda-developers.com/showthread.php?p=53220435
Folow this to unbrick your device
You need an unlocked bootloader to flash cm11, no bootloader comes unlocked
There is unlockable and non unlockable

Xperia z3 tablet compact cant boot into recovery

Hi,
I'm quite new to the world of custom roms and I would appreciate some help to get my z3 tablet working again. I wanted to install this ROM as my Z3 was still running on Lollipop with no update in sight.
I managed to unlock the bootloader following the instructions from Sony's homepage and I was able to flash TWRP using the version provided in the thread linked above. Unfortunately now I can neither boot into recovery nor do anything else with the tablet except start the fastboot mode (solid blue light after holding power up and connecting the power cable).
Is there any whay to start TWRP? Did I use the wrong image? I'm on Windows 7 64-bit. Thank you for your help!
I used this solution to get out of the very same situation on my SGP611.
If your tablet is soft bricked, stuck at boot, restart display SONY and keep restarting you can do the bellow steps, but after that you will need to root and install TWRP again.
To turn off your tablet which is keep restarting, press and hold POWER and VOLUME UP until the tablet vibrates 3 times and turns off.
On your PC open Sony Xperia Companion, click Software repair, check My device cannot be detected or started, Next, chose Xperia phone or tablet, Next, check I know my Google credentials, wait until instruction are displayed how to connect to your PC.
Make sure your tablet is turned off, press and VOLUME DOWN while connecting the USB cable to PC, when the program starts the next step you can release the VOLUME DOWN.
Now wait and do not disconnect the tablet from PC.
Hi, I used Lightheadeds link and I managed to install the stock rom that way. I also tried luk71s solution but Xperia Companion did not work because my tablet has an unlocked bootloader.
Many thanks, I now have a working tablet again!!!
Hello everyone. I have the same problem. I just changed from my Z2 tablet to a Z3 Tablet compact. Unlocked boot loader but I can not install twrp using ADB or Flash to update to oreo.
I don't even have the oem unlock under developper status.
I will be gratefull for any help
Thanks
dsman said:
Hello everyone. I have the same problem. I just changed from my Z2 tablet to a Z3 Tablet compact. Unlocked boot loader but I can not install twrp using ADB or Flash to update to oreo.
I don't even have the oem unlock under developper status.
I will be gratefull for any help
Thanks
Click to expand...
Click to collapse
Since you already unlocked your bootloader it makes sense that you do not have an OEM unlock option. In developer settings you must enable USB debugging and reboot in bootloader mode to flash twrp. What happens if you send the command 'fastboot devices'?
Thanks for replying my Sos.I did not have the unlock oem optoon before unlocking the bootloader. When I write adb devices the computer sees it in normal mode but does see the tablet in fastboot mode.
dsman said:
Thanks for replying my Sos.I did not have the unlock oem optoon before unlocking the bootloader. When I write adb devices the computer sees it in normal mode but does see the tablet in fastboot mode.
Click to expand...
Click to collapse
I checked my tablet and it has no OEM unlock option either, so maybe it is simply not implemented. This means you should be able to unlock.
To see your tablet in fastboot mode you must install the correct drivers on your PC. For me the easiest way was to install Flashtool from www.flashtool.net. It has an option to install drivers and it is also useful if you want to go back to stock. You may also want to backup your TA partition if you consider returning back to a pristine state.
Suite
M1chiel said:
I checked my tablet and it has no OEM unlock option either, so maybe it is simply not implemented. This means you should be able to unlock.
To see your tablet in fastboot mode you must install the correct drivers on your PC. For me the easiest way was to install Flashtool from www.flashtool.net. It has an option to install drivers and it is also useful if you want to go back to stock. You may also want to backup your TA partition if you consider returning back to a pristine state.
Click to expand...
Click to collapse
I have wiped off everything from the Tablet it's mega clean but i really want to remove all bloatware and instal a better rom. have already installed fashtool but once I am in fastboot mode ( Blue light) there is no communication with computer.
I have installed the correct driver
Checked in the devices settings it there is no Triangle
Checked the s1 driver , the Z3 tablet compact driver No triangle.
Sony companion regognises the Tablet
But when in Fatsboot mode, there is no communication.
Heeeeeeelp and thanks to all the developpers and other testers
dsman said:
I have wiped off everything from the Tablet it's mega clean but i really want to remove all bloatware and instal a better rom. have already installed fashtool but once I am in fastboot mode ( Blue light) there is no communication with computer.
I have installed the correct driver
Checked in the devices settings it there is no Triangle
Checked the s1 driver , the Z3 tablet compact driver No triangle.
Sony companion regognises the Tablet
But when in Fatsboot mode, there is no communication.
Heeeeeeelp and thanks to all the developpers and other testers
Click to expand...
Click to collapse
You may have to disable driver signature verification: https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
Also close Sony Companion and Flashtool if you run the fastboot commands.
Z3 Tablet Root
M1chiel said:
You may have to disable driver signature verification: https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
Also close Sony Companion and Flashtool if you run the fastboot commands.
Click to expand...
Click to collapse
Ok i'll do that and will keep you posted
Z3 tablet Root 2018
So I finally managed to root my lovely and Tiny Tablet. Info those interested.
Step by Step. My machine Windows 10 Pro 1803 : Did not work with this computer and changed on a second one Same windows Pro 1803
that does not mean it will not work on yours)
Phone is Z3 Tablet Compact with Marshmallow.
A On Computer
1 Installed Flashtool 64
2 Installed ADB FlashTool 5contains drivers also)
3 Installed Phones Driver (it may be included with Flash tool)
4 Installed Sony Flashtool
5 Unlocked Bootloader with Flashtool or Go to Sony's Site to obtain Unlockboot loader Code. Sorry Too long to explain ( I used Flashtool)
6 Downloaded SGP621_23.0.1.A.0.167_CE.ftf or other Firmware that fits you xperia device with Sony Flashtool :: ATTENTION This downgraded my phone to Android 5 Lollipop.
ON Phone
If you are here, you already know that you have to unlock your Developper mode, Allow Debbuging mode, Allow mock locations, Go to de security option and allow Unkown sources.
1 Installed Kingroot 4.50 (Install it even if Google says it may be dangerous)
2 Ran Kingroot 4.50 IT IS NOT the latest but it worked for me on Android Lollipop. (I had tried the lastests versions of Kingroot, Kingoroot, and other it did not work on Marshmallow and it did not work for me)
It did not work the first time. SO i tried a second time as proposed and it then worked.
2 bis I rebooted verified with a root checker afterwards: Rooted Yeeeeeeeeeeeeeeeeees
3 Then downloaded Root checker, Titanium Backup, Rom Manager, Official TWRP,SuperSU,Busy Box
4 Once rooted, I removed purify that came with Kingroot and other bloatwares and Installed the above apps. You don't have to do it but that is what I did.
As from here, you choose what you want to do. You are FREE to debloat and install what you want.
I will like to thank all the developpers on this site and thoses who a have showed my ways to find a solution. It is not always clear. But atleast they have tried.
So I am transmitting my experience for others.
Second stage finding the best Nougat or Oreo setup for me in a week or two.
Have a nice day

[SGP321][NON-UNLOCABLE BL] Possibility to unlock BL or install custom kernel/ROM

Hey everyone,
My questions are at the end below, but they need a bit of history which might be useful to someone in similar position.
I have SGP321 and used it stock for a number of years without much issues. Lately though it seems the age of the device shows itself and I wanted to try a custom LineageOS ROM on it - I 've done this before with several other devices.
I tried to follow this guide - [Guide/tutorial] Sony Xperia Tablet Z LTE or Wifi Any version to Android 8 - however the service menu of the tablet showed that the bootloader cannot be unlocked. Attempts to unlock the device using fastboot oem unlock 0xYOURUNLOCKKEY using and unlock code from https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/ showed that the bootloader of the tablet is indeed locked and the lock cannot be removed. I also tried to use the Flashtool to unlock the bootloader - again unsuccessfully.
Being stubborn as I am, I rooted the tablet using this guide - [Guide][Easiest Way]How to Root Xperia Z Android 5.1.1 Without PC and Get SuperSu - which works for Tablet Z as well. Having root access gives possibility to work around the bootloader lock to some extend since access to the tablet storage happens from the OS. I proceeded to copy twrp-3.3.1-0-pollux.img to the external sdcard of the device and executed from a root terminal on the device:
dd if=/sdcard1/twrp-3.3.1-0-pollux.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel​which completed without complaint, then I rebooted and tried to enter recovery by using repeated presses of volume-up and volume-down buttons as well as other combinations like holding them pressed simultaneously, combining the volume buttons with the power button - no positive result (most probably as I read later because the stock BL doesn't support recovery). Then I decided to install the official TWRP app and the used it to install the image to the recovery partition - again no result booting into recovery. Then (foolishly) I used the app to try to install the TWRP image in the boot partition - no problems there, however on the next reboot the tablet was bricked
In this state when trying to power-on the tablet the indicator LED starts flashing in red and the screen remains black. Power-off was possible through pressing volume-up and power buttons for more than 10 seconds. It was also possible to enter fastboot mode by powering-off the tablet and holding volume-up while inserting a USB cable that was plugged to a PC - success was indicated by a continuous blue indicator LED. Attempts to use fastboot flash or fastboot boot with TWRP image didn't give any positive result - the first failed with "Operation not allowed", the second failed with "Too many links". I also tried the same with kernel.sin and fotakernel.sin files from the stock ROM FTF file downloaded using the Flashtool - again unsuccessfully.
Using the Flashtool itself to restore the stock ROM failed initially because the on-screen instructions for getting into flash/download mode - powering off and then holding the volume-down button while inserting a USB cable that was plugged to a PC - didn't work in my case. Then I decided to use this sequence:
powering off
first pressing and holding the volume-down button
second pressing and holding the power button
finally - inserting a USB cable that was plugged to a PC
I was awarded with short green flash of the indicator LED and the Flashtool recognized the device as being in flash/download mode. I then proceeded to flash the downloaded stock ROM using the default settings. The flash was successful, and I was back to square one. I also rooted the device again as described above.
My questions:
Does anyone know of a method that allows to use the root shell of the device itself to remove the bootloader lock? For example, custom copy/flash using the dd command from a root shell and partition images extracted form TWRP/Custom non-stock ROMs.
Is it possible in the situation of my device to install/flash custom recovery/kernel/ROM if we assume that the bootloader cannot be changed?
Thanks in advance for your time and thoughts...
iiontihy said:
Hey everyone,
My questions are at the end below, but they need a bit of history which might be useful to someone in similar position.
I have SGP321 and used it stock for a number of years without much issues. Lately though it seems the age of the device shows itself and I wanted to try a custom LineageOS ROM on it - I 've done this before with several other devices.
My questions:
Does anyone know of a method that allows to use the root shell of the device itself to remove the bootloader lock? For example, custom copy/flash using the dd command from a root shell and partition images extracted form TWRP/Custom non-stock ROMs.
Is it possible in the situation of my device to install/flash custom recovery/kernel/ROM if we assume that the bootloader cannot be changed?
Thanks in advance for your time and thoughts...
Click to expand...
Click to collapse
Hello!
1. If you have operator carrier device like DOCOMO or Orange, then you're out of luck. Carrier branded devices cannot be unlocked, so no TWRP and custom ROMs like LOS, RR, CR, etc.
2. If you have ordinary device, you can unlock the bootloader and install whatever ROM you like, no limitations here.
Root access nor recovery are needed for bootloader unlock.
Thanks Rootk1t, the device was purchased and is locked to a local carrier - so I guess I'm out of luck.
Still, a valuable experience while trying to flash it and having it rooted might allow to squeeze a bit more life out of it
iiontihy said:
Thanks Rootk1t, the device was purchased and is locked to a local carrier - so I guess I'm out of luck.
Still, a valuable experience while trying to flash it and having it rooted might allow to squeeze a bit more life out of it
Click to expand...
Click to collapse
Stock 5.1.1 + root + XZDR + Xposed + some mods (like SDFix for Lollipop; XReality+SuperVivid; xLOUD) is not bad at all.

Categories

Resources