So I'm no stranger to this but I've mainly used devices on Verizon and all of which were always fully unlockable and s-off etc etc, mainly I've used HTC devices, the Samsung devices I've used were blessed by Adam Outler, so my point is anything as far as flashing ROMs goes was just fastbooting a recovery did the trick and flashed a ROM and done. When I added a gsm device to the line up I got the Nexus 5 than got the Oneplus One, than picked one of these up for fun because love love live gigantic big F U screens haha.. So the Nexus and Oneplus were the same deal. The Z Ultra is the US LTE gsm unlocked c6806 variant stock not the GPE. So my buddy told me to dial a number via my dialer and see if its bootloader unlockable and it was so I followed Sony's bootloader unlock method and it was successful!!! Woohoo!!! But... This is where I ran in to some snags. Me being me I jumped right in to fastboot and I fastbooted Team Win Recovery the latest one 2.8.3.0 and it was successful as far as the terminal output goes, but when I tried to boot to recovery I noticed I lost my violet LED and all methods to boot to recovery failed.. I thought being unlocked fastbooting a recovery would be no problem but in my case it wasn't.. It took a day of messing around when I finally ran the ZU dual recovery with TWRP and Philz and that worked. I don't know why but it did and now I'm able to boot to both recoveries.. So I rooted with the latest SuperSU and boom I have root no problems! So now my next confusion is flashing ROMs.. I made a nandroid backup and tested it to make sure it did restore and everything was good and it was. So I went ahead and flashed the CM12 fxp build from December 31st on December 31st and flashed a Gapps package and after a few minutes and it booted up no problem. I DID NOT fastboot the boot.img from the zip first I just flashed the ROM flashed the Gapps and it works with no problem, the kernel is indeed the Cyangon kernel built on Dec 31st [email protected] blah blah... That's the ROM I've been on since than and have no problems and I haven't updated yet because there has been so significant changes since than so I found no need to. Why do every ROM threads state to fastboot the boot.img from the zip first than flash the ROM and Gapps? Is this for locked bootloaders only? Am I missing something? So yeah to sum it up basically, if I'm bootloader unlocked #1 how come I can't just fastboot flash recovery openrecovery-twrp-2.8.3.0.img and why doesn't that work? #2 How come when I came from stock 4.4.4 Sony firmware and flashed the ROM and Gapps without fastbooting the boot.img and that worked no problem? I'm trying to understand how Sony devices work so I don't run in to any issues. Sony works slightly different than what I'm use to. Oh also every time I looked for this flashtool people talk about the links are all bad... Please if someone can thoroughly enlighten me I would sincerely appreciate it. Thanks guys and maybe gals I looked forward to some solid replies!!! Feel free to PM as well if you'd like for some one on one if it makes things easier...
I can't believe 113 views and not a single response..... Well I'm glad I at least know Android and familiarized myself with Sony! To anyone hung up with recovery issues or with losing recovery whether you have the violet light or not, my best suggestion would be to just straight up start over period..
What I did was downloaded the latest Flashtool, I downloaded the latest FTF file for my device which my model is the C6806 LTE US Unlocked version...
I backed up my data and launched Flashtool, select the lightening bolt icon and select flashmode, the FTF file was downloaded in a .zip format, thats as in dot zip, you want to extract the zip file so you have the physical firmware FTF file which will end in .ftf as in dot ftf
You need to take that ftf file and navigate to Flashtools firmware folder and copy it to that directory.
Let Flashtool load that file and when completed you'll be greeted with a notification to power off the device and plug it in to the computer while holding volume down.
Flashtool will begin to do it's thing, I left all the Flashtool settings at their default settings.
When completed you will see in Flashtools window that the device is connected in flashmode, might I also add through the whole process for me the screen was black and there were no lit LED lights..
I rebooted back to complete stock, than rerooted my Z Ultra with the latest version of Easyroot Tool to regain root access.
A that point I downloaded NUTs latest version of his DualRecovery and ran the installer via my Macbook Pro to get back my custom recovery
I flashed the latest version of SuperSU version 2.45 at the time of this post and than made a Nandroid backup all for safe purposes, than rebooted the device and made sure everything was good to go.
Went back to recovery and wiped all reinstalled the latest CM12 and Gapps and here is where I went wrong last time at this point I flashed the DualRecovery flashable zip which I didn't do last time and it was clearly stated in NUTs OP to always refresh the recoveries after flashing any custom ROM to make sure you don't lose recovery like I did last time lol!
Now at this very moment I'm on the latest CM12 with my recoveries working and I have ZERO issues finally!!!!! Thanks to me for figuring it all out and some minor assistance from my boy es0tricha0s for reassurance... ANYONE having problems with their devices and recovery issues I can now most likely help you out now that I'm beginning to understand the way Sony works.... I'll even go as far as Teamviewing in to you and helping you remotely fix your device up so you don't end up the way I did....
Also FYI I started all of this bootloader unlocked and remained bootloader unlocked
Related
Hi all, i have been trying to root and install a custom rom for my Sony Xperia Z2, running stock firmware version 314. Previously i tried using the Dual Recovery that i found on this forum and using that to flash the rom, but it did not boot, so i had to use flashtool to restore my phone to a stock firmware, found on this forum as well. It is also the reason i am running firmware version 314, which i believe is not the latest version available, but i am unable to access OTA sony updates anymore.
I am still able to gain proper root access for my phone (verified using root checker from the play store), but for some reason am unable to flash in a working custom recovery that will help me install CM11 on my phone. I understand now that CM11 requires a custom kernel to operate, but am unable to flash one using Dual Recovery either. I am at a loss as to what to do. Any advice or help is greatly appreciated!
@Taeyeonist9 What did you use to root m8? I think you should read this first m8. You install dual recovery after rooting. If you have any more Q's I'll try and help you. Hope this helps a bit m8:good:
---------- Post added at 04:54 PM ---------- Previous post was at 04:51 PM ----------
Oh, forgot to say that .314 is the latest firmware. May I ask if you have unlocked your bootloader, if you don't have OTA updates You wont get OTA updates if you are on the latest firmware.
Rooting Xperia Z2 Sirius
Hi its the same person here, i've no idea why i have two xda accounts and my desktop's browsers registers taeyeonist9 in chrome, while my laptop's registers taeyeonist, when both chromes are synced to the same google account. Anyhow, thanks for taking the time to look at my issue!
So yea, i realised that 314 is actually the latest version. And ive rooted using the easy root tool in that very link you posted above, i believe. So root access is not the issue. After rooting, I flashed XZ's Dual Recovery ,which includes TWRP, CWM and another third recovery i believe was included in the package. The Dual Recovery as i understand is only meant for devices which run stock kernels, with locked bootloaders. however from my understanding, legal regulations in Singapore, my country of residence, forces telcos to sell their devices without locking their bootloaders. Hence my bootloader is already unlocked and I BELIEVE this is not the issue ( pls correct me if im mistaken).
So the issue comes after i've successfully flashed XZ's Dual Recovery. At first i went on to straightaway flash the corresponding CM11 package for my phone and a copy of Gapps for Kitkat, and my phone soft bricked. Had to use flashtool to restore it with a stock kernel that was obtained from this forum, which resulted in my current condition of the phone - running stock firmware 314, and i was unaware that 314 is actually the latest firmware release, my apologies for that. I've tried flashing a custom kernel package using XZ's Dual Recovery too, DoomKernel v10, DoomLord's Advanced Stock Kernel package that includes CWM in it, neither worked, i ended up in the same softbrick situation. I've tried using fastboot to manually flash the kernels as well, perhaps due to my incompetence, i was unable to get the flash to be successful, it fails no matter what i try. So I'm at a loss now.... my Question is, is there any way i can get CWM onto my Xperia Z2 easily without it softbricking, so that i can then go on to flash CM11 using custom recovery method successfully? It's really frustrating because i know it can be done, i've seen the videos on youtube with ppl using CM11 on their Xperia Z2 devices, and I've tried it out on my spare phone, a SGS3, on which CM11 works wonders, and i really want to experience the magic that is CM11 on my Xperia Z2.
Sorry for my lack of technical knowledge, please go slow on the explanations. And once again, i extend my sincere gratitude to you or any other kind developer here who is willing to shed some light on my problem. i apologise for the wall of text
Thank you!
To clarify, when i say softbrick, i was only able to get the device in fastboot mode, and through flashtool, flash a copy of stock kernel obtained from another xda thread to restore it to factory condition. Other than this restoration method, my phone was essentially a brick. Nevrvewrecking:/ Appreciate the advice!
newbe at XZ2
Hi!
May I include my understanding of the issue.
I will get in the same situation in a view days when my Z2 will arrive.
At first, you have already root rights (rooted device) this doeasnt meen that you can flash what ever you want. It only means that you have more access right to your system than normal.
Bootloaders are locked by default but in some special cases it is not allowed to unlock it. (check service menu to get the info if unlockable or not)
If you want to flash roms with locked bootloader be shore to use roms with are able to be flashed with locked bootloader (LB), because the didn't change your kernel.
If you want to flash roms with a different kernel than stock you have to unlock you bootloader first, than you can flash almost every rom also the one statet (UB).
BTW: I thougt CyanogenMod uses there own kernel so its necessarry to unlock your bootloader if you want to flash CM.
However if you need to unlock the bootloader at first get root rights and backup your DRM keys because if they are lost you are unable to restore them any more, and they are necessarry if you will recover your phone to stock.
Hello, I am an inexperienced n00b, though I have read (a lot) and learned (something) in the past week. Any help would be greatly appreciated. Making fun of me is fine, too- just try and do it with simple language so I get it.
I purchased a used Z Ultra GPe, and want to root it to fix the SD card issue. I was able to unlock the bootloader using Sony's website, which had documentation even I could follow. Unfortunately now I have mucked up the ROM flashing, and all the phone will do is show the Google splash screen and the sick Android (I think that is the image for recovery mode, but I can't actually get into recovery mode). I can still get into fastboot, no problem, by holding the volume-up button when I plug it into the computer.
My phone was already running 5.0 (last OTA update)
I attempted to follow the instructions in this thread, which gives two ways of rooting in 5.X. The first way did not work for me because 1) I don't think I quite understand the three steps and 2) ADB would not work for me in fastboot, only when the phone was running android. However, DooMLoRD's three images in this thread seemed like exactly what I needed to get a rooted 5.0
Whenever I tried:
flashboot boot boot_5.0.img
With the boot_5.0.img from DooMLoRD, I would get an error in cmd saying that it wasn't a bootable image
the system_5.0 (fastboot flash system sytem_5.0.img) and the FOTA (fastboot flash recovery FOTA...img) seemed to work fine. But the phone would not boot.
I also tried flashing:
ZU_GPe-AdvStkKernel-KOT49H.S2.2052-v01.img (is this a boot image?)
DooMLoRD_ZU-GPE_port_Z1-KOT49H.S2.2052-ROM-v2.zip (This is a Rom of 4.4x I believe)
because it seemed like they went together, but that didn't work, either. Before each time, I followed these instructions to wipe the device:
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot erase FOTAkernel (the other three would work, but this always returned an error).
I am sure that I am doing something very wrong. Anyone care to point out what I should do to try and get the phone running again (if possible)? I really have read through a ton of threads, but it seems like there is always something I just don't get. Sorry for not raising the bar on the discussion here. I imagine you get a lot of folks asking dumb questions and nobody wants to go way, way back to the basics
I don’t even understand why DooMLoRD’s original 5.x post included 3 files, while most ROM flashing tutorials talk about only two. And is the Kernel the Boot file? And why is the Sony provided Stock ROM for the ZU Gpe neither an .img or a .zip, but rather a .tar? What does one do with that? And it doesn’t come with a Kernel / boot file..
So ignorant… sigh
Thank you-
It looks like you tried flashing the 5.0 port rom for non gpe z ultra's to your gpe z ultra.
The Sony ZU and the Google ZU have two very different partitions, so by flashing a rom for the wrong type of Z Ultra probably borked up your device.
Doomlord's gpe port rom is for the Sony ZU, not for the GPE ZU.
It would have been alot more easier for you to have used the root tool program since your a beginner.
Hey guys so I've been killing myself just trying to find ways to get my newly rooted xperia z2 phone to boot into recovery mode.
Essentially I followed this guide to the bone and successfully rooted my phone --> http://forum.xda-developers.com/xperia-z2/development/stock-d6502-23-1-0-726-complete-guide-t3085893
The big problem is whatever I do, no matter the selection of recovery apps(quickboot, twrp manager, etc.) I install I can never get back into recovery mode, my phone turns off and goes into normal bootup, even when I try to do manual recovery mode the light indicator on top doesn't show up and the phone ends up starting normally.
I have factory resetted my phone a couple of times to have a fresh start each time I try something new but nothing seems to work.
On top of that SDFix and it's other variants does not work on my phone, so I can't install any apps on my micro sdcard. I'm really at a loss for what to do here(been at it for 3 days now) so I'm seeking help.
I'm not sure what information to give but I'll try to give as much details as I can about my situation, I'm really desperate to have recovery and my sd card working normally as I am currently very limited with the stuff I want to do on my phone. :crying::crying:
Info:
Model Number: D6503
Android Version: 5.0.2
Kernel Version: 3.4.0-perf-g72984dd [email protected] #1
Build Number: 23.1.A.0.726
SuperSU Installed
Phone is factory reset and rooted.
No other mods & apps installed aside from pre-installed apps and SuperSU
I would very much appreciate it if someone can help me with this problem, thank you!! :cyclops::laugh:
I can't access recovery mode either. Led light doesn't come on when I turn on the phone as well.
I was thinking abt rooting my phone but nvm now.
saedted said:
I can't access recovery mode either. Led light doesn't come on when I turn on the phone as well.
I was thinking abt rooting my phone but nvm now.
Click to expand...
Click to collapse
I think it doesn't matter whether your phone is rooted or not for you to be able to access recovery mode(not sure about this to be honest). I know rooting(and all this headache) is worth it for any android phone especially the xperia z2 which is why I'm hellbent on getting this fixed.
I wanna install cyanogen mod but those two things I've mentioned in my first post is really limiting what I can do with this phone sadly.
disenx34 said:
I think it doesn't matter whether your phone is rooted or not for you to be able to access recovery mode(not sure about this to be honest). I know rooting(and all this headache) is worth it for any android phone especially the xperia z2 which is why I'm hellbent on getting this fixed.
I wanna install cyanogen mod but those two things I've mentioned in my first post is really limiting what I can do with this phone sadly.
Click to expand...
Click to collapse
Sony devices don't have recovery partition, either unlock your BL (and lose DRM keys) and flash a kernel with a built-in recovery , or keep your BL locked and install nut's dual recovery (you need a rooted system before installing).
All the info needed for both options is here on xda but i think you guys need to read a lot more before you start messing with your devices....
ptmaniac said:
Sony devices don't have recovery partition, either unlock your BL (and lose DRM keys) and flash a kernel with a built-in recovery , or keep your BL locked and install nut's dual recovery (you need a rooted system before installing).
All the info needed for both options is here on xda but i think you guys need to read a lot more before you start messing with your devices....
Click to expand...
Click to collapse
I already did everything I possibly could think of (i.e. unlocked bootloader through sony website, rooted, etc.) like I mentioned in the OP, I actually just recently discovered(like 15 minutes ago) that apparently there's this thing called Sony RIC and that's what's disabling me from installing anything on the system and limiting what I can do with my phone because everything(sd card + system folders) are read only and not write-able.
I found out from this thread (http://forum.xda-developers.com/xperia-z2/general/4-4-4-sony-ric-killer-t2953141/page3) that there's no updated version of 'Sony RIC KILLER' for lollipop version 5.0.2. so I guess I'm stuck. I tried installing TWRP recovery through TWRP manager on my phone and it wouldn't even get to the recovery mode.
I'm gonna keep trying other variants of dual recoveries till one successfully works, I'll also try your suggestion of flashing a kernel with a built-in recovery that's one area I haven't dabbled in yet, this is my first android device so I'm still figuring out where the red line is on everything. :laugh::good:
disenx34 said:
I already did everything I possibly could think of (i.e. unlocked bootloader through sony website, rooted, etc.) like I mentioned in the OP, I actually just recently discovered(like 15 minutes ago) that apparently there's this thing called Sony RIC and that's what's disabling me from installing anything on the system and limiting what I can do with my phone because everything(sd card + system folders) are read only and not write-able.
I found out from this thread (http://forum.xda-developers.com/xperia-z2/general/4-4-4-sony-ric-killer-t2953141/page3) that there's no updated version of 'Sony RIC KILLER' for lollipop version 5.0.2. so I guess I'm stuck. I tried installing TWRP recovery through TWRP manager on my phone and it wouldn't even get to the recovery mode.
I'm gonna keep trying other variants of dual recoveries till one successfully works, I'll also try your suggestion of flashing a kernel with a built-in recovery that's one area I haven't dabbled in yet, this is my first android device so I'm still figuring out where the red line is on everything. :laugh::good:
Click to expand...
Click to collapse
On stock rom / kernel only nut's dual recovery will work. IT will also disable sony ric for you in the process. check here: http://forum.xda-developers.com/showthread.php?t=2261606
On custom kernel you have to choose a kernel with the recovery you want and flash that (don't forget to unlock BL before or you'll end up with softbrick). Recovery managers won't work as there is no recovery partition on your device...
install latest version of nuts recovery for z2 and install it after finish phone well reboot into recovery
Then dont update busybox it well break recovery
I have an Xperia Z5 Compact with German T-Mobile factory ROM, which is not too much use to me coz I don't live in Germany or use T-Mobile. I wanted to flash a stock ROM with no bloatware. Root probably later, I'd like to use the phone a bit first. It isn't simlocked btw, and was OTA updated to Marshmallow before I tried anything.
So I unlocked the bootloader, then flashed the recovery and boot images from the first post here without noticing they are old versions and further down the thread they are updated. Now I can get into TWRP recovery, but when I try to start the phone normally it freezes on the pink T-Mobile splash screen. Recovering from my Nandroid backup doesn't help... coz I only created it from within TWRP after I did this flash.
I can't use Flashtool, it says USB debugging is turned off. I guess what I flashed before has reset that to off. I tried following the Lollipop instructions here to turn it back on using adb, but I can't pull the file mentioned there. Anyone got instructions for doing the same on Marshmallow please?
Not exactly panicking here, but I really wish I practiced on my old HTC Hero before jumping in blind....
moyabrit said:
I have an Xperia Z5 Compact with German T-Mobile factory ROM, which is not too much use to me coz I don't live in Germany or use T-Mobile. I wanted to flash a stock ROM with no bloatware. Root probably later, I'd like to use the phone a bit first. It isn't simlocked btw, and was OTA updated to Marshmallow before I tried anything.
So I unlocked the bootloader, then flashed the recovery and boot images from the first post here without noticing they are old versions and further down the thread they are updated. Now I can get into TWRP recovery, but when I try to start the phone normally it freezes on the pink T-Mobile splash screen. Recovering from my Nandroid backup doesn't help... coz I only created it from within TWRP after I did this flash.
I can't use Flashtool, it says USB debugging is turned off. I guess what I flashed before has reset that to off. I tried following the Lollipop instructions here to turn it back on using adb, but I can't pull the file mentioned there. Anyone got instructions for doing the same on Marshmallow please?
Not exactly panicking here, but I really wish I practiced on my old HTC Hero before jumping in blind....
Click to expand...
Click to collapse
use adb and flash androkernel to fix the incorrect kernel that you installed. you can do that by renaming it boot.img and sending the command fastboot flash boot boot.img
i haven't messed with androplus in a while but if you were on marshmallow i believe v34 will work and if you were on the absolute newest marshmallow i think its v35 off the top of my head.
fyi you dont need usb debugging on to use flashtool, you can get into fastboot mode with no rom at all installed.
Hey everyone,
So! I bought a Sony Xperia 1 (J8110-2019) phone from someone on Facebook Marketplace at a very solid price of £250 (RRP is still £850 in the UK) due to the seller describing it as 'in retail demo mode' so they lowered the price. I jumped the gun thinking I was getting a solid deal and just stupidly assumed it to be a feature I could just disable with *#*#73556673*#*#- me believing I was some insane developer with mad coding skills where in realityI had once flashed and rooted my Xperia XZ back in 2016. [Insert 'Hackerman' meme]
Yes... I am fully aware I'm a complete idiot for not doing a full assessment on the phone and am now having to learn a very important lesson from this situation!!
It seems to have a Store Front firmware installed and unsure what firmware to download and flash? I've tried some of the official stock ROMs from XperiFirm and it just continues to boot into constant 10-second cycles of demo videos making general functionality like phone calls pretty much impossible. without interruption. I've tried Customized and UK Service Provider Firmware such as EE and O2 but it always goes back into Store mode.
I was hoping if anyone would have or could elaborate on how to make an executable system flash zip for a 2019 Xperia 1? When I extract files from XperiaFirm ROMS (FTF,ZIP,SIN etc), I don't seem to get any META-INF files and thus cant make the proper .zip that TWRP needs to successfully flash a new repacked stock ROM? It always ends in a boot loop."
Here are some key points to hopefully give you some background:
I've installed TWRP successfully and have attempted to use 3 official firmware to flash whilst in recovery but have been unsuccessful each time with 'Invalid .ZIP format'. I've only a few times got booted whilst bundling together FTF files via Flashtool and doing it that way round but only ever seems to solve half the problem
I can't use the SinExtract feature in Flashtools as the SIN file errors as not being supported yet to use different file versions.
I can't use PRFCreator as it errors as the FTF file being unsupported (Due to it being new I assume)
I attempted to create my own META-INF>Updater-script but am unable to identify what partition my phone would use for mounting on "/dev/block". I only ever seem to get MANIFEST.MF from the files and nothing else. On my XZ I think I used something like:
(package_extract_file("boot.img", "/dev/block/mmcblk0");
package_extract_file("system.sin","/dev/block/platform/msm_sdcc.1/by-name/system");
Click to expand...
Click to collapse
I have been able to install Magisk for rooting and verified.
I have used Minimal ADB and Fastboot to install programs like TWRP, SuperSu, Magisk but have never attempted, nor would I even know how to wipe my phone completely and install a clean stock ROM - is this possible?
All drivers, software, and systems are correct and up to date (as far as I am aware)
Would installing the' Service Exchange Firmware' be recommended (if I ever make it that far!) due to it being StoreFront?
I checked the IMEI number to see if it was blacklisted/blocked and it's all good. Not lost or stolen.
Thank you for your time to read and wallow in my woes with me my lovelies! Any help would be GREATLY appreciated you magnificent beasts! x
Bump x
...
the last chance... :good: