Related
Hi everyone,
I just bought a brand new Z Ultra C6806. I plugged it into my computer, installed the My Companion software, and then proceeded to root the device via the Chinese root, which seemed to work just fine. I then tried to unlock the bootloader with Flash Tool, but couldn't get Flash Tool to recognize my device. It kept on saying that I needed to install drivers. I'm doing this on a windows computer, and I already navigated to the drivers folder and installed the z ultra drivers.
I then got fed up with that and saw the thread that let you flash a recovery with a locked bootloader. So I followed those instructions and had a working CWM and TWRP. Except then I wiped data and system and flashed the CarbonRom custom rom, and now my phone won't boot at all.
I'm hopeful that everything is not lost since when I hold volume up and plug my phone into my computer I see a blue LED, which I have gathered means that it is successfully still entering fastboot mode?
How do I get Flash Tool to recognize my device? And is it possible to unlock the C6806 bootloader or have I been deeply mistaken all along?
Thanks for any help
[HOW-TO] Unbrick your XZU
You can use method A. Read carefully how to install the drivers and do not use a USB 3.0 port.
velgador0 said:
Hi everyone,
Thanks for any help
Click to expand...
Click to collapse
so what you've done is to try and flash a ROM with a locked bootloader. You've found out that it wont....
You just need to use 'flashtool' and flash a FTF file.
But like you said before you'll need to ensure drivers are installed properly. flashtool will need to say:
'device connected in fastboot mode' or
'device detected in flash mode'
Download the latest version of flashtool. Then when you select the type of device, you can select Xperia Z Ultra.
and make sure that ADB is installed (windows will detect new device has been plugged in, and if it wont install drivers, you will need to tell it where to find them)
hamdogg said:
so what you've done is to try and flash a ROM with a locked bootloader. You've found out that it wont....
You just need to use 'flashtool' and flash a FTF file.
But like you said before you'll need to ensure drivers are installed properly. flashtool will need to say:
'device connected in fastboot mode' or
'device detected in flash mode'
Download the latest version of flashtool. Then when you select the type of device, you can select Xperia Z Ultra.
and make sure that ADB is installed (windows will detect new device has been plugged in, and if it wont install drivers, you will need to tell it where to find them)
Click to expand...
Click to collapse
Reinstalled flashtool drivers for z ultra and flashmode and fastboot, pointed my windows drivers interface to the driver file I downloaded from the sony unlock bootloader website and still didn't get anything on my laptop.
Did the exact same things on my desktop and everything is working fine now, flashtool recognized my device, flashed a Sony FTF, unlocked bootloader successfully, playing with CM now.
Still not sure why this is the case, but alls well that ends well I suppose, thanks.
install flashtools driver you can find it in Flashtools folder. PC need driver when xzu in fastboot mode.If you use USB 3.0 like me try different usb slot.
Sent from my Xperia Z Ultra using xda app-developers app
Hi Guys,
My first Sony Phone (previous Samsung User). I have the US Version C6806 LTE model. I have a similar question. I have unlocked my bootloader successfully via Sony's website. I want to be able to install TWRP and backup original ROM before applying custom ROMs. Doesn't look like there is a root available for this phone model yet? I am on firmware 14.1.B.2.257. My questions are:
1 - Is there a TWRP image I can flash on my model via fastboot without having root? Then boot into TWRP and backup the ROM?
2 - If not can I flash any of the images that I seen on XDA via fastboot that include the Root and TWRP in them? Or will those not work with .257 firmware?
3- If none of the options above work can I download an FTF image (older version) that I can root and use TWRP and if so which image do you recommend that would work with my phone model and LTE network on AT&T?
Thanks for all your help and sorry for all the questions I am a noob with Sony Phones. I did research here and seems most of the threads and images are NOT for C6806 which I have.
I think all tyour questions are answered in various threads in the X-ZU forum...
You have gone about it all ass about face, you should have downgraded to .532 then rooted with kingo (looks like is is safe?). Once rooted you should of then backed up your TA partition in case you ever need the phone serviced.
I dont know if TWRP is working well in any of the boot.img but CMR works fine (except for the date of the backups)
any of the firmware/ftf/ROMs will work with any of the Ultras as far as I know
blueether said:
I think all tyour questions are answered in various threads in the X-ZU forum...
You have gone about it all ass about face, you should have downgraded to .532 then rooted with kingo (looks like is is safe?). Once rooted you should of then backed up your TA partition in case you ever need the phone serviced.
I dont know if TWRP is working well in any of the boot.img but CMR works fine (except for the date of the backups)
any of the firmware/ftf/ROMs will work with any of the Ultras as far as I know
Click to expand...
Click to collapse
I flashed a .532 firmware still no safe root method from what I can tell. Looks like I need to flash an earlier version or a FTF hopefully that contains root and custom recovery. I will keep reading and researching. Thanks for the help.
do you want to end up on a rooted stock firmware?
as you have already unlocked the boot loader you can just flash one of the kernel/boot img with recovery and then flash whatever rom you want from there...
I also run into Cyanogen Recovery and have trouble going back to FlashTool with my chromebook. I am a bit panicky, but your post is comforting and ensuring.
I got the C6806 xperia z ultra in year 2014. I have been using it as a home primary PC.
My blog about this amazing device, is http://nocomputerbutphone.blogspot.com/ .
Got my Z Ultra yesterday (£235 C6806) bargain!
I've rooted many a phone in the past and dealt with the dreaded S-OFF that HTC had but for the first time I actually had a brown trousers moment and I'm wondering if anyone could explain a couple of things for me?
I accidentally flashed a 4.4.2 ROM, this booted up but failed to connect to wifi and had a load of wierd issues, I then re-flashed the recovery img file which ended up in the device not booting, all i got was a colourful 'pacman roms' image. With enough manic button pushing I got back into recovery but found the USB mount storage option does not show the device up on my PC, Thank god its got an SD slot as without this I guess it would have been a flash to stock ordeal. I finally managed to install the 4.4.4 GPe Rom after getting into the recovery and now when I power up it has the usual 'google' logo.
So if I want to flash a ROM etc. I have to flash the .img file for a recovery? It's not permanent? Or should I have the recovery on there all the time?
Im assuming I will have fastboot access if required?
Thanks for any help just dont want to get into another panic attack with this thing!
Ed
Its not a HTC device , recovery is not flashed separate like on those devices.
You simply flash a SONY based kernel file with recovery in fastboot if you are right now on a SONY rom. And away you go. You will then be able to reboot in to recovery. After you flash a rom, the kernel and recovery will be changed out to what is included in the .zip file. :good:
Installing the new Sony Bootloader and Recovery
THIS IS FOR ALREADY UNLOCKED DEVICES!
DO NOT TRY THIS ON A GPE!Since a lot of people seem to have problems keeping their recovery when flashing Lollipop-ROMs i decided to put up this little guide...
You can also Skip this whole guide, by just flashing the newest stock-FW at least once!
First off, as already said, this is for already unlocked devices. You can use this Guide until "Install Custom ROM", except the rooting part, for rooting use this, if you haven't already!
Don't do it if you don't atleast somewhat know what you are doing.
I am not responsible for bricked devices, or whatever you might end up with.
So, lets get started.
1. Download Sonys FlashTool "EMMA" and install it: http://developer.sonymobile.com/downloads/tool/flash-tool-for-xperia-devices/
In the .zip file from the FlashTool you'll find a File "customization.ini"
Copy this file to the installation directory of EMMA, usually "C:\Program Files (x86)\Sony Mobile\Emma"
If you don't copy that file, Emma will ask you for a login, don't create an account there, you will NEVER get any activation-email!
2. Open EMMA and boot your Phone into FlashMode (Power off your device -> Press and hold volume DOWN -> while pressing volume DOWN insert USB-Cable)
3. Emma should now recognize your device, but you have to select it manually tough. Select your EXACT model number. Again, I am not responsible for any bricked devices or whatever you end up with!
Now select the "(Open Devices) TA update" and click "Apply Service"
It should take a few seconds and should then display SUCCESS.
You can now close Emma
4. If you haven't already download FastBoot and Drivers: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
(Run as Administrator!)
5. Download the newest version of twrp and put it somewhere:
New Inoffcial twrp-3.0.0 build by me: http://forum.xda-developers.com/xperia-z-ultra/development/togari-twrp-recovery-3-0-0-t3314440
Old official versions: https://twrp.me/devices/sonyxperiazultra.html
6. Finally boot up you Phone in FastBoot-mode (Power off -> press and hold volume UP -> while pressing wolume UP insert USB-Cable
Your LED should now light up blue
Shift+Rightklick in the Folder where you have put TWRP recovery, and select "Open Commandprompt here"
Now write "fastboot flash recovery FILENAME_OF_TWRP_FILE"
You can now unplug your USB-Cable and boot into recovery and continue from there.
Your recovery will be permanent, meaning you won't loose it or replace with any other recovery that might come with your ROM.
I hope this was somewhat helpfull
Any one can flash this to C6806?
jacklau2000 said:
Any one can flash this to C6806?
Click to expand...
Click to collapse
You can try, just select your modelnumber in emma
If the "Open Devices (TA Update)" show up, you're fine. If not just don't do anything.
But do not try this on a GPE!
alia5 said:
You can try, just select your modelnumber in emma
If the "Open Devices (TA Update)" show up, you're fine. If not just don't do anything.
But do not try this on a GPE!
Click to expand...
Click to collapse
tried, but no luck. thanks.
It's really weird, I used emma, and installed their latest ta update. Now I can get into fastboot mode, all commands execute successfully, but the recovery never takes. The vol down + Power doesn't work, nor does 'adb reboot recovery'. Am I missing a step somewhere? This isn't my first android device, but from where I sit, it seems like something is up with my xzu.
If I try and install the 14.4* update through emma, it goes through the whole process, completes "successfully", then boots into 14.5. Something is clearly not working here.
The TA update only unlocks the ability to boot to recovery, it doesn't install one. And no, flashing official TWRP to recovery partition doesn't work, it must be compiled again to work on normal recovery partition and not in FOTAKernel, where it must be flashed to work.
Regards
teddy74eva said:
The TA update only unlocks the ability to boot to recovery, it doesn't install one. And no, flashing official TWRP to recovery partition doesn't work, it must be compiled again to work on normal recovery partition and not in FOTAKernel, where it must be flashed to work.
Regards
Click to expand...
Click to collapse
I´m on CM 11 M12 (looking forward to 12) + the new sony bootloader without any custom Kernel stuff.
Sadly, you are right. It´s not done with downloading twrp-2.8.5.0-togari.img and fastboot flash recovery yourfile.img.
The last offical TWRP release for Xperia Z Ultra is from february 2015, any chance they release an updated version for the new Sony bootloader?
Hermann1222 said:
I´m on CM 11 M12 (looking forward to 12) + the new sony bootloader without any custom Kernel stuff.
Sadly, you are right. It´s not done with downloading twrp-2.8.5.0-togari.img and fastboot flash recovery yourfile.img.
The last offical TWRP release for Xperia Z Ultra is from february 2015, any chance they release an updated version for the new Sony bootloader?
Click to expand...
Click to collapse
I will try to compile one because, you know, summer holidays and no school however I don't know if I will make it.
Regards
Is there any (wish for TWRP) recovery for togari, which use the new bootoader?
FYI:
My device is a brazilian c6843.
Emma recognizes the device automatically and indicates with an exclamation point that there is no services available to the unit.
In the case someone doesn't know, it's basically the c6833 with DTV 1seg. It's totally compatible with c6833 firmware, losing TV, of course.
You sir are the real hero! Thank you!
I have a xzu running cm12.1, and I have 2 quick questions for those with more knowledge than me
Is it possible to flash the new bootloder using the open source FlashTool?
If I have to use emma, is it possible to just apply the open device ta update *without* installing stock firmware first?
pbgapski said:
If I have to use emma, is it possible to just apply the open device ta update *without* installing stock firmware first?
Click to expand...
Click to collapse
You can totally do that, BUT, the newest stock firmware also has some firmware updates regarding nfc, also having the newest stock rom flashed at least once will be kind of a requirement to get everything properly working on marshmallow roms.
So I would say flash the newest stock rom at least once!
missing clues on new recovery partition
alia5 said:
You can totally do that, BUT, the newest stock firmware also has some firmware updates regarding nfc, also having the newest stock rom flashed at least once will be kind of a requirement to get everything properly working on marshmallow roms.
So I would say flash the newest stock rom at least once!
Click to expand...
Click to collapse
I followed your advice, but it seems I am missing a few clues.
My sirius was on cm12.1. I backedup and flashed D6543_23.4.A.1.232_1281-5466_R6C.ftf with flashtool on linux. I tried to use emma (several times) afterwards to check for any TA updates, but all I got was "no services matched this device" or something like that. Google tells me I am not the only one with this issue with emma
Then I used fastboot to install twrp 3 from twrp.me to recovery partition, but I could not access twrp.
I fastbooted recovery again with twrp 2.8.7, and this time I could enter twrp and reflashed CM.
Now I can access twrp using the button combinations while booting, but rebooting to recovery from CM leads to a bootloop. Has anyone experienced this as well?
So it seems I am still missing a few clues to using the recovery partition. Is any build of twrp supposed to work on both FOTAkernel and recovery partitions?
Is there a TWRP 3 build that works from 'coldboot to recovery' and 'cm reboot to recovery' with the new bootloader? Any pointers?
pbgapski said:
Now I can access twrp using the button combinations while booting, but rebooting to recovery from CM leads to a bootloop. Has anyone experienced this as well?
So it seems I am still missing a few clues to using the recovery partition. Is any build of twrp supposed to work on both FOTAkernel and recovery partitions?
Is there a TWRP 3 build that works from 'coldboot to recovery' and 'cm reboot to recovery' with the new bootloader? Any pointers?
Click to expand...
Click to collapse
Well, booting to recovery on separate partition from os, requires the rom to have a patch... the "new" mm-roms (when they finally hit aka. are ready to be shared in public) will have that, so no worry, just wait.
why it said my phone have no available service, i am on c6833
alia5 said:
Well, booting to recovery on separate partition from os, requires the rom to have a patch... the "new" mm-roms (when they finally hit aka. are ready to be shared in public) will have that, so no worry, just wait.
Click to expand...
Click to collapse
I have the same problem but not bootloop just stuck at starting apps screen,BTW did you have a TWRP scripts for flashing TWRP 3.0 into FOTAkernel
hi .. after this update can i relock my phone and restore drm functions?! or phone go to unlocked forever?!
pls help i need answer
erfanzz said:
pls help i need answer
Click to expand...
Click to collapse
Search the forums on how to backup TA partitions. I have mine but never tried to restore them
Hi guys,
Just unlocked my bootloader and began the root process.
I followed part of this guide but without backing up my DRM keys. http://forum.xda-developers.com/z5-compact/general/summary-tutorial-root-sony-xperia-z5-t3360515
I flashed my kernel and the recovery O.K.
fastboot flash recovery recovery.img
flashboot flash boot boot.img
I've tried two versions of TWRP and two different versions of the kernel AndroPlus.
When performing fastboot reboot after flashing both files my phones LED blinks RED once and then does nothing.
Dramatic and scary. What can I do to fix this? When trying to boot without the cable in my phone just vibrates once and does nothing. Screen doesn't light up at all. I'm so worried.
MatMew said:
Hi guys,
Just unlocked my bootloader and began the root process.
I followed part of this guide but without backing up my DRM keys. http://forum.xda-developers.com/z5-compact/general/summary-tutorial-root-sony-xperia-z5-t3360515
I flashed my kernel and the recovery O.K.
fastboot flash recovery recovery.img
flashboot flash boot boot.img
I've tried two versions of TWRP and two different versions of the kernel AndroPlus.
When performing fastboot reboot after flashing both files my phones LED blinks RED once and then does nothing.
Dramatic and scary. What can I do to fix this? When trying to boot without the cable in my phone just vibrates once and does nothing. Screen doesn't light up at all. I'm so worried.
Click to expand...
Click to collapse
did you try to flash first the boot.img and after the recovery ?
acabreram said:
did you try to flash first the boot.img and after the recovery ?
Click to expand...
Click to collapse
I've tried another kernel and it's booting but hanging at the three dots. (bootscreen) been waiting a few minutes. hopefully it gets to system.
MatMew said:
I've tried another kernel and it's booting but hanging at the three dots. (bootscreen) been waiting a few minutes. hopefully it gets to system.
Click to expand...
Click to collapse
Ok yo can try this too
Y tried and working fine root & xposed
It's tus stock kernel but with the habilita to support root
Similar issue for me
I've had almost exactly the same issue today:
- I unlocked boatloader using Sony standard process
- I followed the steps under 'How to Install CM13' within CTXz's guide here
- After flashing the Kernel and THEN the TWRP, I reboot and the phone flashes red LED, then green, then off, then red and then stays on green for a while (screen is blank). My computer registers that there is a new connection by making a sound but doesn't show up any devices that I can see.
- Periodically, I get the device disconnection sound and the green LED goes off, then red comes on, then solid green again until next cycle.
- If I disconnect the cable, the LED goes off. When I try to turn the phone on without cable attached, it buzzes but does nothing - no LEDs. I can't tell whether it is on or not, except that doing hard reset with PWR+Vol.Up gives no reaction.
- When I re-attach cable normally, the red/green LED sequence starts immediately with no need to turn PWR on, which would suggest that the phone is perhaps on.
- I am able to get into bootloader as normal and fastboot registers the device just fine.
- There is no yellow LED
I started with Kernel AndroPlus v24 and TWRP 3.0.0.0.
Failing that, I tried Kernel v20. Then I tried AndroPlus' twrp-2.8.7.0-E5823-32.0.A.6.152.
Have also tried Kernels v20 and v21 with TWRP 3.0.0.0.
I haven't had any fast boot errors - all flashes come back 'OKAY'.
I'd be very grateful for any help? Have I missed something?!
update to my post above:
I used: 'fastboot boot recovery.img' and this fired up the Sony logo with white screen and blue LED. However, after 10 mins of waiting, there was no change in status and I still couldn't get into TWRP with pressing Vol buttons, even after several restarts and unplugging, replugging etc.
Then, I realised the stock ROM on my phone before this whole process was Lollipop 5.1.1 Build 32.0.A.6.200. So, I flashed older versions of the Kernel and TWRP. Now, I can boot into the ROM and use the phone (almost) as normal except, being plugged in, it keeps re-detecting the USB cable. I now also get the Sony boot screen followed by yellow LED.
If I don't touch anything, it boots into the ROM. However, if I press a Vol button while the yellow LED is on during boot, then it just resets.
Thus, I still cannot get into the TWRP interface. Perhaps I need a TWRP version that is specific to my build - the one I have is from AndroPlus website and refers to the previous build (twrp-2.8.7.0-E5823-32.0.A.6.152.img)?
okay, further update (to save someone replying!)
I managed to boot into the system using AndroPlus Kernel v05a (I had Lollipop build ###.200), but still couldn't get into any TWRP.
I then followed the general process explained in this thread, albeit had to do a heck of a lot of research to understand the detail that is omitted from that (otherwise very useful and concise) original post. For example:
- how to actually use Flashtool (installing drivers and then getting hold of the right firmware from within the program);
- the difference between Fastboot and Flashmode;
- having to plug in the phone while it is loaded into the system before then flashing the selected firmware with Flashtool and ONLY THEN unplugging, switching off and booting into Flashmode.
- loading up the system after flashing the Kernel and TWRP so that I connect to computer and re-copy the erased SuperSU .zip file back onto storage, and then re-booting into TWRP and how to flash a zip file with TWRP.
Having now got a stock Marshmallow firmware rooted, my next step is to go back to the original guide I was following and try to install Cyanogen!
Thank you to all the people who have posted help guides throughout this site so that I could piece together what I needed to do - even though it has still taken me about 30 hours of my life to learn all this!
Hopefully my experience might help someone else in due course...
robledog said:
okay, further update (to save someone replying!)
I managed to boot into the system using AndroPlus Kernel v05a (I had Lollipop build ###.200), but still couldn't get into any TWRP.
I then followed the general process explained in this thread, albeit had to do a heck of a lot of research to understand the detail that is omitted from that (otherwise very useful and concise) original post. For example:
- how to actually use Flashtool (installing drivers and then getting hold of the right firmware from within the program);
- the difference between Fastboot and Flashmode;
- having to plug in the phone while it is loaded into the system before then flashing the selected firmware with Flashtool and ONLY THEN unplugging, switching off and booting into Flashmode.
- loading up the system after flashing the Kernel and TWRP so that I connect to computer and re-copy the erased SuperSU .zip file back onto storage, and then re-booting into TWRP and how to flash a zip file with TWRP.
Having now got a stock Marshmallow firmware rooted, my next step is to go back to the original guide I was following and try to install Cyanogen!
Thank you to all the people who have posted help guides throughout this site so that I could piece together what I needed to do - even though it has still taken me about 30 hours of my life to learn all this!
Hopefully my experience might help someone else in due course...
Click to expand...
Click to collapse
I had the same problem and solution is as is written here.
I had to flash Stock Firmware Marshmallow via Flashtool. After this I flashed kernel(boot) and recovery without problems and yellow icon will displayed.
Don't want to warm up this kind of old thread, but I have exactly the same issue (E8523). Would any of you mind to post their (stock) ROM versions which finally worked? I tried almost every combination that came to my mind (Customized CE1 32.2.A.0.224 => v31, several LP versions => more or less 20 to 32...).
Currently after installing the MM I mentioned the stock kernel worked, but when I flash the AndroPlus kernel (fastboot flash boot /path/to/boot.img) it won't boot up, black screen, looks like no dtb found (doesn't even try to load). This is also the message I get when I try to boot this img via fastboot directly.
I am sure I am missing something really stupid (quite new to android devices), but what?
IGNNE said:
Don't want to warm up this kind of old thread, but I have exactly the same issue (E8523). Would any of you mind to post their (stock) ROM versions which finally worked? I tried almost every combination that came to my mind (Customized CE1 32.2.A.0.224 => v31, several LP versions => more or less 20 to 32...).
Currently after installing the MM I mentioned the stock kernel worked, but when I flash the AndroPlus kernel (fastboot flash boot /path/to/boot.img) it won't boot up, black screen, looks like no dtb found (doesn't even try to load). This is also the message I get when I try to boot this img via fastboot directly.
I am sure I am missing something really stupid (quite new to android devices), but what?
Click to expand...
Click to collapse
Pro tip: hold shift and right click inside folder with recover.IMG or voot.IMG to open command prompt from that folder. Then all you have to do is type fastboot flash boot boot.IMG. I suggest trying to put a custom recovery like twrp on and flashing the xpower ROM from that, it will give you everything in one package.
Edit: fwiw I'm pretty sure custom recoveries have been able to flash .IMG fils for a few years now but I've never actually tried it. Might be worth a shot.
Thanks, but I haven't found cmd.exe on my linux machine yet^^ (I suppose wineconsole is cheating )
I know how to flash *stuff* to my phone, but that *stuff* seems only to work if some specific version of stock rom was installed previously. My best guess is the bootloader changes and supports different dtb formats on every version.
Stock Marshmallow 6.0.1 Customized CE1 32.2.A.0.224 does _not_ work for installing any version of AndroPlus kernel (tried a few...). It fails at boot (does not even load system, probably dtb).
Just in case someone might run into similar issues: What finally worked was Stock MM 6.0.1 Customized DE 32.2.A.0.224 with AndroPlus v31. It seems to be some older release (?), it says R2C instead of R9C for Customized CE1.
I could not find this information anywhere on the net (maybe its me), so for those with a slow internet connection the above version should work. You don't have to actually boot it, flashing is enough.
Thanks for sharing the information in this tread, it really helped me to unbrick my phone!
I started with Lollipop on my brand new Z3C and tried to root using AndroPlusKernel v31 / TWRP 3.0. This resulted in a softbick state, only being able to boot in fastboot mode.
After many hours struggling, an upgrade to stock Marshmallow (E5823_32.2.A.0.224) did the trick. This somehow seems ta make the device ready for the new kernel and recovery (I guess it has to do with the partitions in the filesystem).
Anyway, from stock Marshmallow I could start all over and succeeded to flash a custom bootloader, recovery and now have the ability to flash any desired rom! Thanks again.
To updrade to stock MM I used the instructions in this thread:
[GUIDE][18th Dec][4Noobs] Flashing A FTF File Using Flashtool
To set up TWRP recovery I used the instructions in this thread:
[ROM][UNOFFICIAL][6.0.1][E5823/E5803] CyanogenMod 13 for the Sony Xperia Z5C [ALPHA]
The stock rom I used for my E5823 is "E5823_32.2.A.0.224_R1C_CIS Generic_1298-5167.ftf" from xperiablog.net
Since I'm a new registered member I can't post external links
Google it and you're set!
IGNNE said:
Just in case someone might run into similar issues: What finally worked was Stock MM 6.0.1 Customized DE 32.2.A.0.224 with AndroPlus v31. It seems to be some older release (?), it says R2C instead of R9C for Customized CE1.
I could not find this information anywhere on the net (maybe its me), so for those with a slow internet connection the above version should work. You don't have to actually boot it, flashing is enough.
Click to expand...
Click to collapse
I'm having the same problem, where did you get that MM stock version from?
And what do you mean by "you don't have to actually boot it"?
Search for XperiaFirm and Flashtool. There is plenty.
You don't have to start your freshly installed Stock Rom version "...". You just have to flash it (write it to your phone) Now you boot your phone in fastboot mode and flash your custom kernel and mod rom of your choice. Seems to be some incompatible whatever between not matching kernel versions and the "stuff" flashing installs (suspect sth like bootloader, but no idea).
I have flased boot.img nd recovery.img on android 7.1.1 z5 compact my phone won't pass the sony logo
any help ?
---------- Post added at 11:05 AM ---------- Previous post was at 10:54 AM ----------
starchild78 said:
I have flased boot.img nd recovery.img on android 7.1.1 z5 compact my phone won't pass the sony logo
any help ?
Click to expand...
Click to collapse
I've just discovered I can boot into twrp
anything I can do to fix this from there ?
Hello,
I started on a quest last week to try and make my long forgotten Xperia tablet z LTE SGP321 more user friendly.
I stopped using it after being frustrated by the bloatware and its lack of customisation.
So I thought flashing a custom rom might help and wanted a bit of a technological challenge. Boy do I feel like I've got one.
I used kingroot, which worked fine. I tried to install SuperSu but it wont update the binaries.
I've managed to unlock the bootloader (forgot to do the backup TA woops!).
I downloaded TWRP app, flashed pollux_windy to recovery. Now there doesn't seem to be a combination of keys that I can find to boot the sony xperia tablet Z into recovery?? Power and volume up or down or jamming both keys...nothing seems to work. I've found one forum post suggesting it isnt possible and that I need to flash a kernel which is where I'm getting stuck.
SO this is where I am now and was wondering if I should use CWM instead or if there is another way to open recovery?
My main aim is to completely clear the tablet hard drive and start again with a custom rom.
Thanks!
>>>>>>
NEW info
So i've managed to use the ADB to reboot into the boatloader. All that happens is a black screen. I want to try and flash CWM or TWRM but it doesnt seem to work.
Im beginning to think there's something strange about the sony xperia tablet z in that it doesnt have a bootloader in its stock firmware. i've seen something about using a Kernel approach but the guides are unclear.
Any help on flashing a CWM or TWRM into recovery would be much appreciated!!
harpix42 said:
Hello,
I started on a quest last week to try and make my long forgotten Xperia tablet z LTE SGP321 more user friendly.
I stopped using it after being frustrated by the bloatware and its lack of customisation.
So I thought flashing a custom rom might help and wanted a bit of a technological challenge. Boy do I feel like I've got one.
I used kingroot, which worked fine. I tried to install SuperSu but it wont update the binaries.
I've managed to unlock the bootloader (forgot to do the backup TA woops!).
I downloaded TWRP app, flashed pollux_windy to recovery. Now there doesn't seem to be a combination of keys that I can find to boot the sony xperia tablet Z into recovery?? Power and volume up or down or jamming both keys...nothing seems to work. I've found one forum post suggesting it isnt possible and that I need to flash a kernel which is where I'm getting stuck.
SO this is where I am now and was wondering if I should use CWM instead or if there is another way to open recovery?
My main aim is to completely clear the tablet hard drive and start again with a custom rom.
Thanks!
>>>>>>
NEW info
So i've managed to use the ADB to reboot into the boatloader. All that happens is a black screen. I want to try and flash CWM or TWRM but it doesnt seem to work.
Im beginning to think there's something strange about the sony xperia tablet z in that it doesnt have a bootloader in its stock firmware. i've seen something about using a Kernel approach but the guides are unclear.
Any help on flashing a CWM or TWRM into recovery would be much appreciated!!
Click to expand...
Click to collapse
Flash boot.img of any latest custom ROM with TWRP integrated.
Rootk1t said:
Flash boot.img of any latest custom ROM with TWRP integrated.
Click to expand...
Click to collapse
Thanks for your help. I thought I'd start simple and just try and flash TWRP to recovery.
i downloaded the latest TWRP pollux windy img and then used the command fastboot flash recovery twrp.img
It says FAILED (remote: command not allowed)
adb fastboot devices displays my tablet
(by the way in configuration in service info it says bootloader unlocked: Yes)
>>>>>>UPDATE
so i managed to flash a cyanogenmod img using "fastboot flash boot boot.img"
The device then soft bricked and went into a boot loop. Is this because I used the wrong version of cyanogenmod?? Any other I can try that work?
I panicked a bit, mamanged to get the tablet into fastboot somehow andthen flashed a TWRM img to the boot using the same command above which now loads TWRM.
fastboot reboot now caused the device to go into TWRP but its in recovery mood
How can i undo that step i did when I flashed the boot img of the cyanogen mod. I want to put the old boot.img back!
Rootk1t said:
Flash boot.img of any latest custom ROM with TWRP integrated.
Click to expand...
Click to collapse
also can I ask another quick question of you, what do you do to boot into recovery on your xperia tablet Z device?
Thanks!
Sorry about all the updates.
I decided to see what you had installed on your signature and tried resurrection remix. Version 5.8 caused Error 7??
So i went for version 6.9 which i installed successfully.
Only way i know how to get into recovery is to use adb terminal command "adb reboot recovery"
Also before I installed resurrection remix would you recommend a complete wipe of everything or does it not really matter?
Thanks and hopefully that's me all sorted!
Use VOL+ or VOL- on boot to enter recovery.
harpix42 said:
what do you do to boot into recovery on your xperia tablet Z device?
Click to expand...
Click to collapse
2 way for me:
- usually you can set an "advanced reboot menu" under developer option or the ROM customization panel (depends on which ROM do you use)
- turn off your tablet, now push the power button until your screen just turn on, leave the power button and start pressing vol+ and vol- alternately until you boot into recovery