Related
After using flashtool to install new roms and kernals, I think I may have installed a rom that was not for my exact spec. So after flashing the rom, my phone does not allow me to use any touch screen keys, and I think has overwritten CWM. I have tried Sony Update through PC Companion and it told me that my phone could not be updated. What can I do ?
try to download stock/rooted rom for your device exactly and install it trough flashtool, maybe that will work
I have tried this now. Flashtool does install, but I cannot get past first screen after install. The touch keys stiil do not work.
Masteq said:
try to download stock/rooted rom for your device exactly and install it trough flashtool, maybe that will work
Click to expand...
Click to collapse
andy200 said:
After using flashtool to install new roms and kernals, I think I may have installed a rom that was not for my exact spec. So after flashing the rom, my phone does not allow me to use any touch screen keys, and I think has overwritten CWM. I have tried Sony Update through PC Companion and it told me that my phone could not be updated. What can I do ?
Click to expand...
Click to collapse
well, read here and use that CWM recovery just flash it and enter recovery mode ( I mean you don't have a working rom but a recovery ) when in recovery try to navigate menus then use back sensor-button
if this is working is a good sign if not you have to replace touchscreen I suggest to perform this check before !
I tell you this because you just flashed a ROM ...are you sure it was made for your phone ?
if not it's possible to cause damage to your phone drivers usually are placed in boot.img -your kernel be careful when flashing a new kernel!
Right now my phone does not respond to the install CWm2file, is this the correct thing to do when you say "use that CWM recovery just flash it and enter recovery mode". I am really hoping this phone can be saved somehow.
ruscan.calin said:
well, read here and use that CWM recovery just flash it and enter recovery mode ( I mean you don't have a working rom but a recovery ) when in recovery try to navigate menus then use back sensor-button
if this is working is a good sign if not you have to replace touchscreen I suggest to perform this check before !
I tell you this because you just flashed a ROM ...are you sure it was made for your phone ?
if not it's possible to cause damage to your phone drivers usually are placed in boot.img -your kernel be careful when flashing a new kernel!
Click to expand...
Click to collapse
andy200 said:
After using flashtool to install new roms and kernals, I think I may have installed a rom that was not for my exact spec. So after flashing the rom, my phone does not allow me to use any touch screen keys, and I think has overwritten CWM. I have tried Sony Update through PC Companion and it told me that my phone could not be updated. What can I do ?
Click to expand...
Click to collapse
Download this file, extract it and flash the ftf file inside it via flashtool (Make sure u tick wipe cache & wipe user data on the ftf selection page):
https://rapidshare.com/files/477812782/wt19i_stock_rom_0.62_with_root.zip
Its a rooted stock ROM for Live with walkman...Then download the attached file to get CWM...extract the files to a folder and do as directed in the notepad file (make sure u keep usb debugging and unknown sources on...use the install-cwm2 file..its the one for our phone)..
Now, you should be having a stock kernel, stock rom, with root and CWM...check ur touch keys now...
*IMPORTANT*And always remember...once you've rooted ur phone and unlocked the bootloader...never use PC companion OR OTA updates (on the phone) for updating..it'll brick ur phone..:crying: *IMPORTANT*
PS: Hope i could help..Hit thanks if i did!
PS2: this thread contains all the ROMs which are made for our phone..so before flashing a ROM..please make sure u check if its made for our phone...
http://forum.xda-developers.com/showthread.php?t=1588674
andy200 said:
Right now my phone does not respond to the install CWm2file, is this the correct thing to do when you say "use that CWM recovery just flash it and enter recovery mode". I am really hoping this phone can be saved somehow.
Click to expand...
Click to collapse
firstly I hope you solve that problem because I don't like problems too
-is your bootloader unlocked can you see something on screen when starting
-what about last rom flashed
-can you flash any rom but made for your phone only
-don't use PC Companion at this time
Bootloader IS unlocked. When starting I get Sony Ericsson Start up, and then home screen. Volume works, On/off works. but no touchscreen at all. I can flash a rom using Flashtool, but when try and flash a kernal Flashtool does not let me use flashboot mode. It tell me that Device not connected. This happened before messing up my touchscreen, and I solved it by putting phone in different connection mode.
All this came about because I flashed '[GB rom] X-royal v14 only for lww' and rage kernal, and prob was not for my spec phone.
From this webpage: http://forum.xda-developers.com/showthread.php?t=1650365
So phone has been off for two days now.
Has the problem been solved?
andy200 said:
Bootloader IS unlocked. When starting I get Sony Ericsson Start up, and then home screen. Volume works, On/off works. but no touchscreen at all. I can flash a rom using Flashtool, but when try and flash a kernal Flashtool does not let me use flashboot mode. It tell me that Device not connected. This happened before messing up my touchscreen, and I solved it by putting phone in different connection mode.
All this came about because I flashed '[GB rom] X-royal v14 only for lww' and rage kernal, and prob was not for my spec phone.
From this webpage: http://forum.xda-developers.com/showthread.php?t=1650365
So phone has been off for two days now.
Click to expand...
Click to collapse
Has the problem been solved? :fingers-crossed:
Does your CWM work?? i think the problem is that you're using stock kernel...because none of the other custom kernels show Sony Ericsson at startup...not even the ICS official sony stock kernel...Try flashing a different kernel...
Hope i helped
PS: Don't forget to Hit Thanks!
Hi! Yesterday I tried to restore my Xperia J to .31 fw from Seraphic Season 7 because I got some problem with this ROM...
When I tried to restore, flashtool has stalled at "Flashing loader.sin finished" and no longer went on for half an hour so I unplugged the device and tried to turn it on but remained in bootloop... What can I do to restore my device? Can I unbrick it? :crying:
-Powered by Google Translate
Have u wiped data and dalvic cache before flashing?
Sent from my ST26i using xda app-developers app
mehdithereddevil said:
Have u wiped data and dalvic cache before flashing?
Sent from my ST26i using xda app-developers app
Click to expand...
Click to collapse
Yes... Flashtool wiped data and cache...
Had this same problems when I tried to go from a cyanogenmod rom to a newer custom rom. I've bricked it 5 or six times over the last few days trying to get CWM that works permanently like the one I had before 1st brick.
To unbrick mine I found I hadn't got the latest Flashtool [ver 0.9.18.4] this has BLU written beside the flash sign.
Plugged phone whilst in off state whilst holding down vol button for Flash mode
Hit BLU then I locked bootload then flashed ST26i_11.0.A.3.28_WE.ftf
the last time after locked bootload I used PC companion which gave me a Jelly Bean update.
But now I stuck as I can't find a permanent CWM.
This worked because I had ST26i_11.0.A.3.28_WE.ftf in my SD card. But it would seem from what I've encountered some ROMs ,kernals and other stuff people post don't like mixing together and having bootload locked you might be able to flash .ftf files or use PC companion to get phone back into a working state.
MrPetje said:
Had this same problems when I tried to go from a cyanogenmod rom to a newer custom rom. I've bricked it 5 or six times over the last few days trying to get CWM that works permanently like the one I had before 1st brick.
To unbrick mine I found I hadn't got the latest Flashtool [ver 0.9.18.4] this has BLU written beside the flash sign.
Plugged phone whilst in off state whilst holding down vol button for Flash mode
Hit BLU then I locked bootload then flashed ST26i_11.0.A.3.28_WE.ftf
the last time after locked bootload I used PC companion which gave me a Jelly Bean update.
But now I stuck as I can't find a permanent CWM.
This worked because I had ST26i_11.0.A.3.28_WE.ftf in my SD card. But it would seem from what I've encountered some ROMs ,kernals and other stuff people post don't like mixing together and having bootload locked you might be able to flash .ftf files or use PC companion to get phone back into a working state.
Click to expand...
Click to collapse
I have bootloader unlocked and .31 firmware (with Seraphic Season 7) on my phone... So I have to relock bootloader and then flash again the .31 firmware?
Xp3r14J said:
I have bootloader unlocked and .31 firmware (with Seraphic Season 7) on my phone... So I have to relock bootloader and then flash again the .31 firmware?
Click to expand...
Click to collapse
That is what worked for me. Once it needed doing twice [can't remember if it was the relock or the firmware flash] it came up with error message first time but second attempt it worked. Good idea to have the plastic back off phone for dropping out the battery if you get into a loop.
Once locked Sony PC Companion sees phone as well but will probably give you Jelly Bean software. [tick box repair phone]
Hello everyone, I have a Moto G (2013) aka first generation Moto G & I live in India. I had unlocked my bootloader. I even flashed cwm touch via fastboot but it doesn't go to recovery mode at all. I get a black screen. I tried flashing the official TWRP 2.8.4.0 today, but I get a message that reads, "Partition size mismatch" & I'm stuck. The phone is usable & it boots up normally & I use it daily. But it is the recovery that is messed up. I tried updating to lollipop by ota but the device got stuck on a black screen once the ota was downloaded. I tried downloading the KitKat factory image, but the link is dead. Please, somebody help!! Thanks in advance!
Sent from my XT1033 using xda premium
The partition size mismatch error can be ignored, You get that error because the TWRP 2.8.4.0 is for the XT1032 and not the XT1033. To flash the OTA, you have to use the stock recovery only. Your system should not be modified (eg. It shouldn't be rooted, and if it had been rooted previously, you will have to unroot it.) To flash the stock recovery again, download the Asian XT1033 4.4.4 firmware and just flash the "recovery.img" from it. The flash the OTA. The numerous guides regarding this in the general section should help you.
I have a similar question.
I have unlocked bootloader & rooted moto g.
I received official OTA update today but its not installing. Do I need to lock bootloader or do something else to install the official OTA update?
Facing a similar issue. Updated the moto g and was successful. It was used for a couple of days before the error cropped up.
Now, it boots up but goes to a black screen after the boot animation. However, it still connects to the computer and I'm able to see the phone and its files in explorer. Beyond that, I can't interact with the phone because the screen is totally black.
Additionally, I can access the bootloader, but selecting 'factory' or 'recovery' isn't doing anything - just black screens everywhere.
The phone was perfectly fine for a few days after the update. (The phone is unrooted and unmodded and was running stock at lolipop update.)
Another thread suggests that I should
Code:
fastboot erase cache
fastboot erase userdata
Is that a viable course of action? Has anybody been able to recover from this issue?
pr.itdude said:
I have a similar question.
I have unlocked bootloader & rooted moto g.
I received official OTA update today but its not installing. Do I need to lock bootloader or do something else to install the official OTA update?
Click to expand...
Click to collapse
No need to lock. Unroot, reflash stock signed recovery and you should be good to go. Also undo any modifications you made to the filesystem and wiping /cache should help prevent errors.
---------- Post added at 02:42 AM ---------- Previous post was at 02:40 AM ----------
SoberDogs said:
Facing a similar issue. Updated the moto g and was successful. It was used for a couple of days before the error cropped up.
Now, it boots up but goes to a black screen after the boot animation. However, it still connects to the computer and I'm able to see the phone and its files in explorer. Beyond that, I can't interact with the phone because the screen is totally black.
Additionally, I can access the bootloader, but selecting 'factory' or 'recovery' isn't doing anything - just black screens everywhere.
The phone was perfectly fine for a few days after the update. (The phone is unrooted and unmodded and was running stock at lolipop update.)
Another thread suggests that I should
Code:
fastboot erase cache
fastboot erase userdata
Is that a viable course of action? Has anybody been able to recover from this issue?
Click to expand...
Click to collapse
Try fastboot erase cache, it shouldn't delete any of your data and it might be enough to get the device working again. You might want to wipe the dalvik-cache as well. If all else fails, since you can access you filesystem, backup all important files and do a factory reset.
skyguy126 said:
No need to lock. Unroot, reflash stock signed recovery and you should be good to go. Also undo any modifications you made to the filesystem and wiping /cache should help prevent errors.
Click to expand...
Click to collapse
Ok. Few more Q pls:
1. Reflashing stock recovery wipes system data & apps? After this my phone will be rooted or not? Any links where i can read more about it?
2. I have stock ROM but yes I installed xposed framework & few modules. Is it a filesystem modification?
3. Any other alternative to this?
pr.itdude said:
Ok. Few more Q pls:
1. Reflashing stock recovery wipes system data & apps? After this my phone will be rooted or not? Any links where i can read more about it?
2. I have stock ROM but yes I installed xposed framework & few modules. Is it a filesystem modification?
3. Any other alternative to this?
Click to expand...
Click to collapse
1. No it should not. If you had root before you will still have it. Search in the forum for more info.
2. Yes but you can easily uninstall xposed with the click of a button.
3. This is by far the easiest and safest method. I know of one alternative is to flash the ota update zip through custom recovery but you are on your own there.
skyguy126 said:
1. No it should not. If you had root before you will still have it. Search in the forum for more info.
2. Yes but you can easily uninstall xposed with the click of a button.
3. This is by far the easiest and safest method. I know of one alternative is to flash the ota update zip through custom recovery but you are on your own there.
Click to expand...
Click to collapse
ok so Here what i am planning:
1. Uninstall all modules & xposed framework
2. Unroot using supersu
3. Restore/reflash stock recovery (just recovery not whole firmware as I already have stock rom)
4. Install the update either manually via recovery or using auto install.
Am i on right path? Pls help me on step 3, any link or step-t-step guide? I couldn't find one, every post is abt restoring whole firmware.
TIA. Cheers !!
pr.itdude said:
ok so Here what i am planning:
1. Uninstall all modules & xposed framework
2. Unroot using supersu
3. Restore/reflash stock recovery (just recovery not whole firmware as I already have stock rom)
4. Install the update either manually via recovery or using auto install.
Am i on right path? Pls help me on step 3, any link or step-t-step guide? I couldn't find one, every post is abt restoring whole firmware.
TIA. Cheers !!
Click to expand...
Click to collapse
Yep you should be good good luck!!!
I have an M2, I did, something to it which involved flashing something and unlocking the bootloader, It got bricked, and the only way i could recover it is with the tiny off button next to the Sim-Slot (Lifesaver, Thanks Sony) and putting it into that flash mode thing where the light goes blue, and Flashing a stock firmware, Or so I thought, It was customised, Also in the whole process I somehow Downgraded to Jelly Bean, and the Updater says that I have custom firmware, I have clockworkmod, But it didnt work properly and now i have no recovery menu at all also Miracast is broken, HSDP (Some sort of DRM thing) failed probably caused by one of these issues
So yeah does anyone have a Firmware for my device so that the Sony Updater will accept it? Don't care which android version, as long as It can be updated back up to KitKat and is UK GENERIC no customisations
All i wanted was to root my phone to get a WiFi password that I lost
Thanks
bigglescat5 said:
I have an M2, I did, something to it which involved flashing something and unlocking the bootloader, It got bricked, and the only way i could recover it is with the tiny off button next to the Sim-Slot (Lifesaver, Thanks Sony) and putting it into that flash mode thing where the light goes blue, and Flashing a stock firmware, Or so I thought, It was customised, Also in the whole process I somehow Downgraded to Jelly Bean, and the Updater says that I have custom firmware, I have clockworkmod, But it didnt work properly and now i have no recovery menu at all also Miracast is broken, HSDP (Some sort of DRM thing) failed probably caused by one of these issues
So yeah does anyone have a Firmware for my device so that the Sony Updater will accept it? Don't care which android version, as long as It can be updated back up to KitKat and is UK GENERIC no customisations
All i wanted was to root my phone to get a WiFi password that I lost
Thanks
Click to expand...
Click to collapse
I guess XperiFirm is what you need:
http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
quake73 said:
I guess XperiFirm is what you need:
http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
Click to expand...
Click to collapse
Will Version "Customised UK" allow me to Update using the Sony Updater?
bigglescat5 said:
Will Version "Customised UK" allow me to Update using the Sony Updater?
Click to expand...
Click to collapse
No the sony software picks up any device if the bootloader is unlocked. it will only re-flash the firmware if the bootloader is locked.
However you can use flash tool http://www.flashtool.net/index.php and it will do it for unlocked bootloaders.
HatchetEgg said:
No the sony software picks up any device if the bootloader is unlocked. it will only re-flash the firmware if the bootloader is locked.
However you can use flash tool and it will do it for unlocked bootloaders.
Click to expand...
Click to collapse
Can I Re-Lock the bootloader? And how can Flashtool update my phone?
bigglescat5 said:
Can I Re-Lock the bootloader? And how can Flashtool update my phone?
Click to expand...
Click to collapse
Make sure the drivers are installed for your phone on you laptop/PC first.
once you have downloaded a Firmware for the M2 you put the firmware in the firmware folder of the flashtool directory then you select the thunderbolt icon. select flash mode and follow the instructions. Also it will say press the back button in the instructions instead you need to press vol down for flash mode or up for fastboot mode.
Once done you get a little window that shows and just select the firmware you want to flash and the way you go.
you can unlock and re-lock bootloaders with flashtool but I think you need to have unlocked it with flash tool to do that.
Try these links:
Device: Xperia M2 (D2303)
CDA: 1281-1548
Customization : CE
Release: 18.0.C.1.13 / R1B
https://drive.google.com/file/d/0BxfA3HIG47hxLXFjQV92UC0zNTg/edit?pli=1
Device: Xperia M2 (D2303)
CDA: 1281-1548
Customized CE1
Release: 18.3.1.C.1.13 / R1B
https://docs.google.com/file/d/0BxfA3HIG47hxMElLNzFhQUFXOTg/edit?pli=1
bigglescat5 said:
Will Version "Customised UK" allow me to Update using the Sony Updater?
Click to expand...
Click to collapse
If you only need a functional KK 4.4.4 phone then choose Customized UK 18.3.1.C.1.13 in xperifirm, download it, wait for it to unpack the files.
Then you need to use flashtool, got to Tools->Bundles->Create to create a flashable .ftf file. Select all the files in the folder where you downloaded the rom, fill in the fields for version/branding/device and click create.
Lastly, you click the Lightning button in flashtool, select flashmode, select your newly created ftf.
When it asks to connect your phone, power off the phone, press&hold the VolDown button when inserting the usb cable, the led should blink briefly green once. The flashing should begin at that moment.
quake73 said:
If you only need a functional KK 4.4.4 phone then choose Customized UK 18.3.1.C.1.13 in xperifirm, download it, wait for it to unpack the files.
Then you need to use flashtool, got to Tools->Bundles->Create to create a flashable .ftf file. Select all the files in the folder where you downloaded the rom, fill in the fields for version/branding/device and click create.
Lastly, you click the Lightning button in flashtool, select flashmode, select your newly created ftf.
When it asks to connect your phone, you press&hold the VolDown button when inserting the usb cable. The flashing should begin at that moment.
Click to expand...
Click to collapse
XperiFirm just throws a error, wants me to reinstall JRE, I have, and I have uninstalled JDK and stuff too with the latest version
WHY DO ALL MY DEVICES HATE ME!
bigglescat5 said:
XperiFirm just throws a error, wants me to reinstall JRE, I have, and I have uninstalled JDK and stuff too with the latest version
WHY DO ALL MY DEVICES HATE ME!
Click to expand...
Click to collapse
from the xperifirm page:
** If you have Flashtool installed, Java Runtime is bundled with it and doesn't have to be installed separately. Just extract XperiFirm's files to Flashtool's folder and run XperiFirm.exe from there.**
quake73 said:
from the xperifirm page:
** If you have Flashtool installed, Java Runtime is bundled with it and doesn't have to be installed separately. Just extract XperiFirm's files to Flashtool's folder and run XperiFirm.exe from there.**
Click to expand...
Click to collapse
Its downloading now , Is there any way to make it so when I flash it later it will not wipe my phone, Not essential, but i hate reinstalling and reconfiguring everything
bigglescat5 said:
Its downloading now , Is there any way to make it so when I flash it later it will not wipe my phone, Not essential, but i hate reinstalling and reconfiguring everything
Click to expand...
Click to collapse
At the ftf selection window, under [Wipe:], uncheck [DATA]. That way, your data will not get erased and It might save you from reinstalling everything.... In theory
Try with DATA unchecked first, see if all is fine. If not then reflash the clean way, with DATA checked. Tell us here how it went.
quake73 said:
At the ftf selection window, under [Wipe:], uncheck [DATA]. That way, your data will not get erased and It might save you from reinstalling everything.... In theory
Try with DATA unchecked first, see if all is fine. If not then reflash the clean way, with DATA checked. Tell us here how it went.
Click to expand...
Click to collapse
Flashed without data, It seemed to flash everything but When I booted the phone, It was still JellyBean where did all the flashes go?
bigglescat5 said:
Flashed without data, It seemed to flash everything but When I booted the phone, It was still JellyBean where did all the flashes go?
Click to expand...
Click to collapse
Then, 2 possibilities come to mind, you either didnt download the latest version (18.3.1.C.1.13) or didnt select it correctly in flashtool. I hope you only unchecked DATA, not checked everything under Exclude
How much time did the flashing process take, it should be, maybe more than 5 minutes
I downloaded Kitkat for sure, The only other thing i deselected was TA, because I heard that TA is bad and kills your phone
bigglescat5 said:
I downloaded Kitkat for sure, The only other thing i deselected was TA, because I heard that TA is bad and kills your phone
Click to expand...
Click to collapse
Then i'm out of ideas. as for that TA, i honestly am not sure what that exactly is or wheteher it is lost during unlocking. i leave it unckecked, have heard that flashtool decides if it needs to be flashed.
here is how i would flash 4.4.4:
(do you have all those parts? the ones in red? maybe not all but system.sin is THE android, kernel is important, too)
quake73 said:
Then i'm out of ideas. as for that TA, i honestly am not sure what that exactly is or wheteher it is lost during unlocking. i leave it unckecked, have heard that flashtool decides if it needs to be flashed.
here is how i would flash 4.4.4:
Click to expand...
Click to collapse
I will try flashing TA
bigglescat5 said:
I will try flashing TA
Click to expand...
Click to collapse
ok, now i saw...seems you downloaded 18.0.C.1.13
the lates android version for m2 in xperifirm is 18.3.1.C.1.13, i guess you got the wrong version.
Oh wait, I must be flashing the wrong rom lol
Ok i figured it out i somehow made the bundle thing wrong and Flashtool didnt pick it up, i am a total idiot , I flashed the rom i orginally used to un-brick my phone
I have not rooted my phone yet and previously come from using nexus devices.
I'm on stock lollipop rom and was wondering how I should proceed.
step one would be backing up the TA partition.
following that, unlock the bootloader. After that I was wondering if I need to downgrade to kitkat to continue or if I could flash a kernel with twrp and try to get into twrp, wipe everything and flash cm12.1 + gapps + supersu and proceed from there.
My question is, do I need to downgrade to kitkat stock to proceed or is there a way for me to gain recovery and flash a rom without downgrading?
you will need to downgrade to KK to get root access then install a stock rom that had been pre-rooted for lollipop, you don't have to unlock the bootloader but if you do then you can use a kernel that has recovery built in
Richy99 said:
you will need to downgrade to KK to get root access then install a stock rom that had been pre-rooted for lollipop, you don't have to unlock the bootloader but if you do then you can use a kernel that has recovery built in
Click to expand...
Click to collapse
But to flash a rom one does not need root, just recovery, or am I wrong there? Wouldn't it be possible to flash a kernel using fastboot just to gain access to twrp (I know that would cripple the stock rom), and then wipe everything and then just go ahead and flash cm12.1 using a microsd card?
I might be totally wrong. If there is not other way I guess I need to downgrade.
Oh and my end goal is to flash cm12.1.
Arju007 said:
But to flash a rom one does not need root, just recovery, or am I wrong there? Wouldn't it be possible to flash a kernel using fastboot just to gain access to twrp (I know that would cripple the stock rom), and then wipe everything and then just go ahead and flash cm12.1 using a microsd card?
I might be totally wrong. If there is not other way I guess I need to downgrade.
Oh and my end goal is to flash cm12.1.
Click to expand...
Click to collapse
But you cannot flash a kernel with a locked bootloader, and you cannot backup the TA without root...
So, you need to root before unlocking the bootloader.
So, downgrade to KK FW .93, root, backup TA partition (If you are going to unlock the boot, otherwise there is no point), install recovery, flash a pre-rooted lollipop rom.
No need for unlocking the boot at all unless you want a custom kernel
But if you want CM12,
downgrade to KK FW .93, root, backup TA, unlock boot, install a recovery of your choice either by a LB way (e.g. dual recovery) or by fastboot a boot.img, flash CM12.1
gregbradley said:
But you cannot flash a kernel with a locked bootloader, and you cannot backup the TA without root...
So, you need to root before unlocking the bootloader.
So, downgrade to KK FW .93, root, backup TA partition (If you are going to unlock the boot, otherwise there is no point), install recovery, flash a pre-rooted lollipop rom.
No need for unlocking the boot at all unless you want a custom kernel
But if you want CM12,
downgrade to KK FW .93, root, backup TA, unlock boot, install a recovery of your choice either by a LB way (e.g. dual recovery) or by fastboot a boot.img, flash CM12.1
Click to expand...
Click to collapse
Ah I see, root is needed to backup TA partition.
I know my bootloader needs to be unlocked as I flash Cyanogenmod 12.1 on it. I fell more secure using fastboot soo I'll probably go that way.
So to downgrade, do I use flashtool and find a kk fw .93 ftf file to flash? If I understand correct, this can be done without unlooking the bootloader.
Then from there I'll have to root with looked bootloader, backup TA partition and then unlock bootloader, and then flash kernel with twrp and then proceed to flash cm12.1 or anyother custom rom.
(Sorry If my question is a mess).
Arju007 said:
Ah I see, root is needed to backup TA partition.
I know my bootloader needs to be unlocked as I flash Cyanogenmod 12.1 on it. I fell more secure using fastboot soo I'll probably go that way.
So to downgrade, do I use flashtool and find a kk fw .93 ftf file to flash? If I understand correct, this can be done without unlooking the bootloader.
Then from there I'll have to root with looked bootloader, backup TA partition and then unlock bootloader, and then flash kernel with twrp and then proceed to flash cm12.1 or anyother custom rom.
(Sorry If my question is a mess).
Click to expand...
Click to collapse
Yes that's the way,
Downgrade to FTF ending in .93 using flashtool, root using griefroot, backup TA using backup TA tool, unlock boot, fastboot a kernel, flash CM12
gregbradley said:
Yes that's the way,
Downgrade to FTF ending in .93 using flashtool, root using griefroot, backup TA using backup TA tool, unlock boot, fastboot a kernel, flash CM12
Click to expand...
Click to collapse
If u read the CM12 thread there is no way why I would flash it. It is more or less unusable.
Sent from my D6603 using XDA Free mobile app
ondrejvaroscak said:
If u read the CM12 thread there is no way why I would flash it. It is more or less unusable.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
There are plenty of reasons to flash it, only one of them is if it is stable....
gregbradley said:
Yes that's the way,
Downgrade to FTF ending in .93 using flashtool, root using griefroot, backup TA using backup TA tool, unlock boot, fastboot a kernel, flash CM12
Click to expand...
Click to collapse
Thank you! Makes much more sense now.
ondrejvaroscak said:
If u read the CM12 thread there is no way why I would flash it. It is more or less unusable.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
Well there are unofficial builds with fixes from members who has the Leo build. The official one does not have all fixes as of yet. There are cm12.1 unofficial builds out now. Being able to test out the latest and greatest is the beauty of it.
gregbradley said:
There are plenty of reasons to flash it, only one of them is if it is stable....
Click to expand...
Click to collapse
I agree, development, testing etc. I was more wondering why people experiment with such ROMs when they lack basic knowledge about flashing, TA etc. But it's a bit OT.
Sent from my D6603 using XDA Free mobile app
ondrejvaroscak said:
I agree, development, testing etc. I was more wondering why people experiment with such ROMs when they lack basic knowledge about flashing, TA etc. But it's a bit OT.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
For some its a first step into something new, it is always a learning curve. Some just like to have the "latest" version.
ondrejvaroscak said:
I agree, development, testing etc. I was more wondering why people experiment with such ROMs when they lack basic knowledge about flashing, TA etc. But it's a bit OT.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
Coming from a different device does not mean that one does lack basic knowledge. I previously used lg g2 and prior to that I used nexus 5, nexus 4 and older devices. All could be managed using fastboot. Those phones does not have drm keys that needs to be backed up. Hence I did not need that knowledge.
Either way, thank you for enlightning me. I felt to ask here in Q&A section rather than being sorry about not asking.
Arju007 said:
Coming from a different device does not mean that one does lack basic knowledge. I previously used lg g2 and prior to that I used nexus 5, nexus 4 and older devices. All could be managed using fastboot. Those phones does not have drm keys that needs to be backed up. Hence I did not need that knowledge.
Either way, thank you for enlightning me. I felt to ask here in Q&A section rather than being sorry about not asking.
Click to expand...
Click to collapse
OK. Sorry for being a bit too sceptical. Sometimes it is frustrating here with all the same questions and stories of ignorance seems not your case.
Sent from my D6603 using XDA Free mobile app
ondrejvaroscak said:
OK. Sorry for being a bit too sceptical. Sometimes it is frustrating here with all the same questions and stories of ignorance seems not your case.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
That's fine, I totally understand you! Hope to be pro xperia user soon haha :silly:
@gregbradley Had a noob moment here and now I'm stuck. I tagged you incase you would know how to help me.
So I downgraded to .93 kitkat. All worked well.
Then I managed to root it using giefroot. All worked well.
Then I installed xzdualrecovery. It booted into twrp, I wiped everything beside internal storage and tried to flash cm12.1. I received an error.
I forgot to unlock the bootloader (ofcourse).. which is the mistake I did.
So now I'm stuck. When I turn on the phone the sony bootsplash screen comes on and it does not go past that, due to my device not having a rom.
I tried holding down the volume key and plugging in the device to my computer. My computer does not recognize what device it is but it does make a notification sound saying that I have connected a device to my computer. Fastboot doesn't work on lockedbootloader as far as I know. The flashtool recognizes the device as a flash device for around a minute when connected to the computer using volume down. After a minute my device just turns off and on leaving flash mode. So that's the current status.
Do you or anyone else have any suggestions to how I can revive my phone?
and yes I know, I feel like a noob!
Never mind, I gave it another go with flashtool and managed to get it boot!
and yes, I feel like a pro!
Don't forget to backup the ta patition before unlocking the bootloader.
Also no need to wipe system when flashing
gregbradley said:
Don't forget to backup the ta patition before unlocking the bootloader.
Also no need to wipe system when flashing
Click to expand...
Click to collapse
I backed up TA partition 3 times. I've been getting error in twrp when I try to flash cm12.1. I did infact wipe everything even system. could that be the reason for me getting an error in twrp? (can't currently remember what the error was but i wasn't able to flash it.). Is there some problem caused by wiping system?
I finally understand Flashtool and have no problem using it. I also have tested restoring ta partition so I know how stock sony works now. It's just custom roms I have trouble installing. I've been using xzdualrecovery and that recovery pushes me automatically to twrp after I install it. Is there some other recovery i should use instead?
Arju007 said:
I backed up TA partition 3 times. I've been getting error in twrp when I try to flash cm12.1. I did infact wipe everything even system. could that be the reason for me getting an error in twrp? (can't currently remember what the error was but i wasn't able to flash it.). Is there some problem caused by wiping system?
I finally understand Flashtool and have no problem using it. I also have tested restoring ta partition so I know how stock sony works now. It's just custom roms I have trouble installing. I've been using xzdualrecovery and that recovery pushes me automatically to twrp after I install it. Is there some other recovery i should use instead?
Click to expand...
Click to collapse
Use NDRUtils app to boot to a different recovery
Or just press volume up when the phone vibrates twice when you are booting it to get to CMW
Arju007 said:
I backed up TA partition 3 times. I've been getting error in twrp when I try to flash cm12.1. I did infact wipe everything even system. could that be the reason for me getting an error in twrp? (can't currently remember what the error was but i wasn't able to flash it.). Is there some problem caused by wiping system?
I finally understand Flashtool and have no problem using it. I also have tested restoring ta partition so I know how stock sony works now. It's just custom roms I have trouble installing. I've been using xzdualrecovery and that recovery pushes me automatically to twrp after I install it. Is there some other recovery i should use instead?
Click to expand...
Click to collapse
/edited
i would wipe really everything despite usb otg and external sd card in advanced wipe of twrp before succeeding.
tell me if that works for you
um, i read you already had that issue again even after unlocked bootloader, try flashing a rooted lollipop .zip in recovery.
and then try wiping and flashing cm12.1 again if a full wipe (also sdcard) doesn't work
---------- Post added at 01:55 PM ---------- Previous post was at 01:51 PM ----------
Arju007 said:
I backed up TA partition 3 times. I've been getting error in twrp when I try to flash cm12.1. I did infact wipe everything even system. could that be the reason for me getting an error in twrp? (can't currently remember what the error was but i wasn't able to flash it.). Is there some problem caused by wiping system?
I finally understand Flashtool and have no problem using it. I also have tested restoring ta partition so I know how stock sony works now. It's just custom roms I have trouble installing. I've been using xzdualrecovery and that recovery pushes me automatically to twrp after I install it. Is there some other recovery i should use instead?
Click to expand...
Click to collapse
well, as you wrote me in pm you did mount "system", just do nothing in the mount menu after entering recovery. i also never did that.