[Q] The fu...lovely bootloader - Sony Xperia T, TL, TX, V

Hi there
I will try and keep this as short as I can. I have an Xperia T which I recently recovered from a bootloop thanks to the helpful folks here at XDA. The issue arose because I tried to flash a custom ROM without unlocking the bootloader (I rooted using Doomlord's Toolkit). I have since done a lot more reading about the process, but it is nearly impossible to read every related link on the internet, so I'd really appreciate if someone could answer the following two questions before I attempt to flash a custom ROM again.
Fortunately, my bootloader is unlockable, although I am currently using the stock firmware without any changes.
The first thing I want to do is backup the TA Partition so I can reinstate Bravia etc once I am happy with the custom ROM. I thought I had backed this up using the Android Flash Tool 0.9.13.0, but I have since read that this doesn't backup the TA Partition in full. For this, I need to use Backup-TA 9.10. My question about this is, do I need to use both the Flash Tool and Backup-TA in order to fully backup and restore the TA Partition, or is Backup-TA sufficient on its own? Also, I don't see an option to restore the backup created in the Flash Tool. How is this done?
The second question I have is, can I unlock the bootloader without going through the formal Sony bootloader unlock process? I have no money to replace my phone and it is under warranty until October this year so I do not want to jeopardise this if it is not possible to unlock the phone without involving Sony. The Android Flash Tool 0.9.13.0 provides a Bootloader Unlock option, yet I have read that it is not possible to unlock the bootloader without informing Sony. If I am able to use the Flash Tool to unlock my bootloader, I have downloaded a file called "LT30_relock_bootloader.ftf" which claims to relock the bootloader should I ever need to do so for the purposes of my warranty, so I have no issue unlocking the bootloader provided I do not need to go through Sony. So, is the information I am currently armed with correct? And is using the Android Flash Tool the best method to unlock the bootloader (so I can install a custom ROM)?
I intend to backup the TA Partition, use Doomlord's Toolkit to root my device, then unlock the bootloader (if possible), then install CWM v8 to flash a custom ROM.
Any clear advice would be greatly appreciated, as ever.

pfhastie said:
Hi there
I will try and keep this as short as I can. I have an Xperia T which I recently recovered from a bootloop thanks to the helpful folks here at XDA. The issue arose because I tried to flash a custom ROM without unlocking the bootloader (I rooted using Doomlord's Toolkit). I have since done a lot more reading about the process, but it is nearly impossible to read every related link on the internet, so I'd really appreciate if someone could answer the following two questions before I attempt to flash a custom ROM again.
Fortunately, my bootloader is unlockable, although I am currently using the stock firmware without any changes.
The first thing I want to do is backup the TA Partition so I can reinstate Bravia etc once I am happy with the custom ROM. I thought I had backed this up using the Android Flash Tool 0.9.13.0, but I have since read that this doesn't backup the TA Partition in full. For this, I need to use Backup-TA 9.10. My question about this is, do I need to use both the Flash Tool and Backup-TA in order to fully backup and restore the TA Partition, or is Backup-TA sufficient on its own? Also, I don't see an option to restore the backup created in the Flash Tool. How is this done?
The second question I have is, can I unlock the bootloader without going through the formal Sony bootloader unlock process? I have no money to replace my phone and it is under warranty until October this year so I do not want to jeopardise this if it is not possible to unlock the phone without involving Sony. The Android Flash Tool 0.9.13.0 provides a Bootloader Unlock option, yet I have read that it is not possible to unlock the bootloader without informing Sony. If I am able to use the Flash Tool to unlock my bootloader, I have downloaded a file called "LT30_relock_bootloader.ftf" which claims to relock the bootloader should I ever need to do so for the purposes of my warranty, so I have no issue unlocking the bootloader provided I do not need to go through Sony. So, is the information I am currently armed with correct? And is using the Android Flash Tool the best method to unlock the bootloader (so I can install a custom ROM)?
I intend to backup the TA Partition, use Doomlord's Toolkit to root my device, then unlock the bootloader (if possible), then install CWM v8 to flash a custom ROM.
Any clear advice would be greatly appreciated, as ever.
Click to expand...
Click to collapse
I haven't read your post completly, but you can't install ANY custom rom if your bootloader is unlockable. You can't install a custom kernel. So all your efforts are worthless....

St.Jimmy90 said:
I haven't read your post completly, but you can't install ANY custom rom if your bootloader is unlockable. You can't install a custom kernel. So all your efforts are worthless....
Click to expand...
Click to collapse
I think that you have a lot of problems with English, he has phone with UNLOCKABLE bootloader, which means that it CAN BE unlocked...
This is not your first post where you're blowing away people not knowing what they are writing.

St.Jimmy90 said:
I haven't read your post completly, but you can't install ANY custom rom if your bootloader is unlockable. You can't install a custom kernel. So all your efforts are worthless....
Click to expand...
Click to collapse
why would u answer the question without understanding what he wrote ? and the fact remains that u admitted that u didnt read it all the way so its pointless to reply jus like u may be saying its pointless for me to reply to your post and not answer the question

Yes, just to confirm my bootloader can be unlocked (unlike some Xperia T variations), but is currently locked. And I am enquiring as to whether it can be unlocked without contacting Sony and how best to go about it.
I would really appreciate some help as I am disinclined to do anything on my phone until I can solve the issues and questions outlined above.

pfhastie said:
Yes, just to confirm my bootloader can be unlocked (unlike some Xperia T variations), but is currently locked. And I am enquiring as to whether it can be unlocked without contacting Sony and how best to go about it.
I would really appreciate some help as I am disinclined to do anything on my phone until I can solve the issues and questions outlined above.
Click to expand...
Click to collapse
no know not of any other ways but sony and flashtool atm

1: Use backup-TA ONLY. You won't be reinstating it and getting back Bravia while you are using a custom ROM though You restore this backup only if you want to go back to stock and restore Bravia/send phone in for service.
2: You need the code from the Sony service. However just because you got the code, doesn't mean you used the code so won't wreck your warranty on its own. You restore the TA backup before your send away under warranty and then they don't even know you ever unlocked in the first place
Don't flash any .ftf to relock your bootloader, thats what you make the TA backup for. Any other method to relock bootloader will show relocked instead of never unlocked status you need for warranty. TA is only thing that will restore Bravia also.
pfhastie said:
Hi there
I will try and keep this as short as I can./QUOTE]
Click to expand...
Click to collapse

nlooooo said:
I think that you have a lot of problems with English, he has phone with UNLOCKABLE bootloader, which means that it CAN BE unlocked...
This is not your first post where you're blowing away people not knowing what they are writing.
Click to expand...
Click to collapse
Doh man, usually I understand everything but it seems I have to read more carefully..... And I shouldn't try to read something while talking to a friend. It won't happen again

Thanks for that, mdc1983uk, I understand about the TA partition now.
My only remaining question is, if I need the Sony code to unlock the bootloader, what happens when you use the Android Flash Tool 0.9.13.0 Bootloader Unlock option? Does it still require you to get a Sony code?

pfhastie said:
Thanks for that, mdc1983uk, I understand about the TA partition now.
My only remaining question is, if I need the Sony code to unlock the bootloader, what happens when you use the Android Flash Tool 0.9.13.0 Bootloader Unlock option? Does it still require you to get a Sony code?
Click to expand...
Click to collapse
As far as I know you need the code. Every phone gets an unique code created from your Imei

OK, thanks for the advice.
New problem: I upgraded to 4.3, now Doomlord's Rooting Toolkit doesn't work. Is there another way to root 4.3? I can't use Backup-TA unless device is rooted.
I swear, I can understand why it sometimes seems a little tetchy round here - every step of every path seems to lead straight into a brick wall!!!

pfhastie said:
OK, thanks for the advice.
New problem: I upgraded to 4.3, now Doomlord's Rooting Toolkit doesn't work. Is there another way to root 4.3? I can't use Backup-TA unless device is rooted.
I swear, I can understand why it sometimes seems a little tetchy round here - every step of every path seems to lead straight into a brick wall!!!
Click to expand...
Click to collapse
What if you flash Darklords pre rooted and deodexed rom?
http://forum.xda-developers.com/showthread.php?t=2647459

Thanks for that, I appreciate that would work, but I still haven't come close to being able to successfully flash a single ROM and I just don't have the time or mental strength required to work my way through every ball-breaking step. No matter how simple it seems, there will be a problem.
Unless there is a simpler solution, I shall just keep watching these forums hoping the mighty Doomlord releases a new Toolkit or another method comes to light. Surely within a few weeks there ought to be another solution given all the high IQ bods on the case.

pfhastie said:
Thanks for that, I appreciate that would work, but I still haven't come close to being able to successfully flash a single ROM and I just don't have the time or mental strength required to work my way through every ball-breaking step. No matter how simple it seems, there will be a problem.
Unless there is a simpler solution, I shall just keep watching these forums hoping the mighty Doomlord releases a new Toolkit or another method comes to light. Surely within a few weeks there ought to be another solution given all the high IQ bods on the case.
Click to expand...
Click to collapse
don't bank on the devs coming up with a new root method for 4.3, currently there isn't a need for one since we can all root on 4.1 then unoffically upgrade with a pre-rooted firmware, this is a relitevly simple procedure and can be done within an hour

It wouldn't be an hour for me, unfortunately. It would likely be three solid days of profound agony and disturbed sleep. Even tonight, it took me hours to connect to PC Companion to run a fresh copy of the firmware and the thread related to the 4.3 pre-rooted firmware suggests there are still a few issues. The great and mighty Doomlord's Toolkit takes seconds and works perfectly. I am sure I am not alone in my concerns.

pfhastie said:
It wouldn't be an hour for me, unfortunately. It would likely be three solid days of profound agony and disturbed sleep. Even tonight, it took me hours to connect to PC Companion to run a fresh copy of the firmware and the thread related to the 4.3 pre-rooted firmware suggests there are still a few issues. The great and mighty Doomlord's Toolkit takes seconds and works perfectly. I am sure I am not alone in my concerns.
Click to expand...
Click to collapse
+1 on what @matt4321 said in the previous post. Downgrade to 4.1.2, root, and then backup your TA partition with Backup-TA, flash CWM v8, and unlock bootloader if so desired.
If you want to be on 4.3, once you're unlocked, and after flashing any Official 4.3 FTF, you can then flash a kernel that can be found in EXR leaked 4.3 thread which comes with CWM already included, and finally proceed to flash SuperSU in recovery.
The minute one of the Official 4.3 FTF's came out I flashed it and tried the kernel I just mentioned; it's been working fine, probably even better than the official stock kernel (even though it is based on a stock kernel, only with CWM, that's why you need to be unlocked), given that I don't have a single one of the bugs that people are reporting exist on the Official 4.3 Roms. Battery is at 40% and I am already at almost 35 hours on a single charge.
If you already have the FTF files, this procedure doesn't take more than 40 minutes, if you're comfortable with and know what you're doing.

I hear you and will very likely give it a shot as soon as I can find the time (if only this was my only concern). At this stage, I'd be inclined to use Doomlord's Rooted&Deodexed ROM as it doesn't require unlocking the bootloader, but it is still a long way around to get root for the 4.3 version I am already using.
What I don't understand is, why would anyone comfortable with this whole process want to run 4.3 anyway when KitKat and supposedly better ROMs are widely available? Doesn't make sense. The truth is, the Sony interface is very well implemented already, and I'm beginning to think that better shortcuts and flashy sidebars are not worth the effort of trying to deal with flashing custom ROMs. I don't want a smartphone - or any computer - loaded with more utilities than apps that actually do stuff. That, I thought, was part of the rank old days.
I read about five web pages devoted to explaining what deodexing actually means and I still don't know, and probably never will.
I'll mull over the situation as I get drunk tonight!

Well, the thing is you need to backup your TA partition, which is the only reason why you'd have to go back to 4.1.2, which lengthens the process.
pfhastie said:
I read about five web pages devoted to explaining what deodexing actually means and I still don't know, and probably never will.
Click to expand...
Click to collapse
Regarding odexing/deodexing, read this.
pfhastie said:
What I don't understand is, why would anyone comfortable with this whole process want to run 4.3 anyway when KitKat and supposedly better ROMs are widely available? Doesn't make sense. The truth is, the Sony interface is very well implemented already, and I'm beginning to think that better shortcuts and flashy sidebars are not worth the effort of trying to deal with flashing custom ROMs. I don't want a smartphone - or any computer - loaded with more utilities than apps that actually do stuff. That, I thought, was part of the rank old days.
Click to expand...
Click to collapse
Obviously, in your case it's simple, since you have an XT and there are several custom ROMS that are currently being actively maintained for that device; you can do pretty much anything you want.
Others, like myself, have an XTX, and apparently none of the devs working on Roms actually have an XTX, so developing for it is a hit and miss. I tried CM11, and it was working flawlessly until I realized that half of the time the phone should be in deep sleep, it does not sleep due to kernel wakelocks. A battery that lasts 6 - 7 hours is no use for me. Therefore, my only option was to go back to JB 4.3.
The people who actually bought an XT have a wide variety of ROMs to choose from. On the other hand, those who have an XTX have about 3 or 4 ROMs (at the most), with the only one actually being maintained, is CM11.

Antiga Prime said:
Well, the thing is you need to backup your TA partition, which is the only reason why you'd have to go back to 4.1.2, which lengthens the process.
Regarding odexing/deodexing, read this.
Obviously, in your case it's simple, since you have an XT and there are several custom ROMS that are currently being actively maintained for that device; you can do pretty much anything you want.
Others, like myself, have an XTX, and apparently none of the devs working on Roms actually have an XTX, so developing for it is a hit and miss. I tried CM11, and it was working flawlessly until I realized that half of the time the phone should be in deep sleep, it does not sleep due to kernel wakelocks. A battery that lasts 6 - 7 hours is no use for me. Therefore, my only option was to go back to JB 4.3.
The people who actually bought an XT have a wide variety of ROMs to choose from. On the other hand, those who have an XTX have about 3 or 4 ROMs (at the most), with the only one actually being maintained, is CM11.
Click to expand...
Click to collapse
Oh, I get you. Still, bit of a faff, isn't it? These devices will be old before they can be utilised perfectly.

Custom ROMS still have a way to go unless stock based. Although the stock 4.3 isn't flawless, its better for me than the 4.3/4.4 custom's running on a 4.1 kernel. Every i've tried comes with the proviso that you will suffer blue screens of death at random until Sony releases the 4.3 kernel open source for them to merge. Some guys are hardcore though and putting up with reboots and crashes is a normal part of the game as it's not a bug - they are waiting for Sony. There's also another huge issue (for me) of the speakerphone never working correctly at the Sony volumes. They have to turn the volume of the whole ROM down to compensate and this makes it hard to hear in a noisy environment, a frustrating bug for me which has hung around since 4.1. You can max the volume up with a file which someone did, but it breaks the speakerphone then so you can only have one or the other.
In a lot of ways I am one of those guys though, I do like to experiment and am comfortable with the processes but I always find what I flash causes me some frustration before long so I go back to stock. If I had the knowledge to help fix problems it would be a different story and i'd stick with custom but as I can't I don't really see the point until 4.3 sources come out and its all a bit more stable.
pfhastie said:
What I don't understand is, why would anyone comfortable with this whole process want to run 4.3 anyway when KitKat and supposedly better ROMs are widely available? Doesn't make sense. The truth is, the Sony interface is very well implemented already, and I'm beginning to think that better shortcuts and flashy sidebars are not worth the effort of trying to deal with flashing custom ROMs. I don't want a smartphone - or any computer - loaded with more utilities than apps that actually do stuff. That, I thought, was part of the rank old days.
I read about five web pages devoted to explaining what deodexing actually means and I still don't know, and probably never will.
I'll mull over the situation as I get drunk tonight!
Click to expand...
Click to collapse

Related

[MINI-GUIDE] Roadmap to a Custom ROM!

Roadmap to Custom ROM​
1.Unlock Bootloader from htcdev.com.
2.Flash a multi hboot recovery.
3.Root using the permanent root solution flashed via recovery, found here.
4.Flash S-OFF Hboot from unlimited.io.
5.Flash custom ROM with no problems.
To check your Unlock Token, Flash Recovery and S-OFF you should use the tool provided by me here .
This is the easiest guide to follow.. I'm also using this step to install custom Rom on my SXL before I got One X.. I'm also don't get it.. why people don't use unlimited.io trick.. it easier for me.
BTW.. it good to see a new dev for sxl.. it a good device.. but lack of developer.. wish you good luck with your project.
Sent from my HTC One X using Tapatalk 2
Agreed.
I've flashed on a lot of devices and the SXL guides are all a bit random.
The info is out there but sometimes you need to dig a lot to find it.
And a lot are out of date.
Hope this becomes the go-to guide for everyone and hope to see some dev work happening.
I think its time to move on for me..... getting flash withdrawal.
Prof Peach said:
Agreed.
I've flashed on a lot of devices and the SXL guides are all a bit random.
The info is out there but sometimes you need to dig a lot to find it.
And a lot are out of date.
Hope this becomes the go-to guide for everyone and hope to see some dev work happening.
I think its time to move on for me..... getting flash withdrawal.
Click to expand...
Click to collapse
I'm just getting familiar with the forum and the device (almost 4 days since i bought it).
Soon enough if i have time (back2school), i will try to work on CM9 or CM10, depends, CM9 seems the obvious road to take as some work was previosly made by [vertigo], and some fixes are needed (he said that are kernel related), so i think i will try to fix his CM9 rather than port it again form scratch.
As for CM10, i think the best road to take is to compile AOSP JB from source and edit the kernel so it likes the jelly flavour.
If everything works as intedend, in a couple of months we should see both CM9 and JB/CM10 up and going.
(The worst thing is that i will surely need help, i think i can find around the forum, some testers already enrolled to the call to arms thread, so maybe we can build up a team., i really like this device )
I will say that some of the guides are if you were on a GB rom, and then installing a custom rom wasn't so easy, but since the upgrade to ICS it has become a lot easier, although I had noticed that it is easier to softbrick the phone if you don't flash the chinese boot.img and then chinese rom. Also s-off isn't essential for flashing custom roms...
[vertigo] said:
I will say that some of the guides are if you were on a GB rom, and then installing a custom rom wasn't so easy, but since the upgrade to ICS it has become a lot easier, although I had noticed that it is easier to softbrick the phone if you don't flash the chinese boot.img and then chinese rom. Also s-off isn't essential for flashing custom roms...
Click to expand...
Click to collapse
Well, i'm fairly new to this device, but from what i've learned, the chinsese rom is optional if you have s-off, as s-off let's you to access all the partitions, system and other things you need.
Maybe i'm wrong, that's why i've started this thread, i think this is easier, and softbricking a phone with Android seems almost impossible to me...as i said, to me
Yeah I know the chinese rom is optional, but as I said from my point of view, once I'd flashed the chinese rom, I didn't manage to softbrick the phone where as before when I was trying various ports I managed to softbrick it a few times. Just my opinion and what I'd noticed with my device...
As for s-off mine (although broken) is still s-on and I've never felt the need to make it s-off. Again just my opinion
[vertigo] said:
Yeah I know the chinese rom is optional, but as I said from my point of view, once I'd flashed the chinese rom, I didn't manage to softbrick the phone where as before when I was trying various ports I managed to softbrick it a few times. Just my opinion and what I'd noticed with my device...
As for s-off mine (although broken) is still s-on and I've never felt the need to make it s-off. Again just my opinion
Click to expand...
Click to collapse
Well, i know what youre pointing at, i was just wandering when i first read te forum, why on earth should i install a Chinsese ROM when i will change it anyways for a new ROM...so the boot.img is a different one in the custom one, and other things.
I'm not so expeirenced with S-Off/On, as this is my first HTC phone i have and changed ROM (not too many HTC's in my area), but from what i've read online, S-Off is the best road to take to ensure you don't softbrick your phone, as you have the real "Full Control" over the Device and the ROM parts you can flash, like you, this is my opinion, a begginers opinion
Double Post because reedited thread
Hi Lexmazter,
Thanks for making this guide, it is easy to follow. But I'm stuck at a small point and face below response; -
>>>>>>>>>>>>>>'fastboot' is not recognized as an internal or external command, operable program or batch file.<<<<<<<<<<<<<
Please let me know where did I do wrong? Thanks.
My steps were: -
factory reset
root via DooMLoRD_v4_ROOT
titanium backup worked and restore all apps and settings
unclocked the bootloader from htcdev.
all data gone, no more, like factory reset again
superuser app still exist, didn't root again
booted and rooted as you said
connect PC to phone via USB in charge mode only.
run your tool
doing select 5 Flash HBOOT S-OFF Unprotected (via adb) - choose hg hi both failed - but face above message 3 repeat lines.
reboot to bootloader FASTBOOT, >>>>>USB<<<<< appear
UNLOCK at top also appear
then select 4 Flash Recovery. (via fastboot) - then choose rei reg both failed - but face above message. 1 line.
Hope can teach me, thank you very much in advance.
And I'm sure I didn't do something right before hand.
cx5 said:
Hi Lexmazter,
Thanks for making this guide, it is easy to follow. But I'm stuck at a small point and face below response; -
>>>>>>>>>>>>>>'fastboot' is not recognized as an internal or external command, operable program or batch file.<<<<<<<<<<<<<
Please let me know where did I do wrong? Thanks.
My steps were: -
factory reset
root via DooMLoRD_v4_ROOT
titanium backup worked and restore all apps and settings
unclocked the bootloader from htcdev.
all data gone, no more, like factory reset again
superuser app still exist, didn't root again
booted and rooted as you said
connect PC to phone via USB in charge mode only.
run your tool
doing select 5 Flash HBOOT S-OFF Unprotected (via adb) - choose hg hi both failed - but face above message 3 repeat lines.
reboot to bootloader FASTBOOT, >>>>>USB<<<<< appear
UNLOCK at top also appear
then select 4 Flash Recovery. (via fastboot) - then choose rei reg both failed - but face above message. 1 line.
Hope can teach me, thank you very much in advance.
And I'm sure I didn't do something right before hand.
Click to expand...
Click to collapse
Extract the contents of the archive in C:/ and try again, it is most likely because you are running from a folder that has spaces (" ").
Thanks for replying so quickly, some questions before sleep tonight.
I moved the folder to c:\xmtool and run as administrator as usual. But without connecting the phone, and select 5 flash H boot. The 3 repeat message appear still. Hahah, may be I want to test in theory.
Anyway, reading more more other post and try again this weekend.
Thanks !!!! many of your post and reply has been insightful.

[Q] Few questions

Okay so, since I'm sort of new, I wanted to ask a few questions:
1. Is it possible to root xperia x8 with manufacturing date 11w48? At least at 95% chance. I'm a bit scared of the bricking part...
2. If it is possible, what kind of "ROM" (if I understood correctly) should I get?
3. If I get hard bricked/soft bricked what's the chance my phone will be still usable.
That's about it. Please don't rage at me for "OMG USE SEARCH BUTTON" type of thing.
I have tried doing it but no results found. Just threads and posts of people updating their.. ROMs I gues? Correct me if I typed anything wrong there.
But yeah, help would be appreciated. Thanks!
Jetboard said:
Okay so, since I'm sort of new, I wanted to ask a few questions:
1. Is it possible to root xperia x8 with manufacturing date 11w48? At least at 95% chance. I'm a bit scared of the bricking part...
2. If it is possible, what kind of "ROM" (if I understood correctly) should I get?
3. If I get hard bricked/soft bricked what's the chance my phone will be still usable.
That's about it. Please don't rage at me for "OMG USE SEARCH BUTTON" type of thing.
I have tried doing it but no results found. Just threads and posts of people updating their.. ROMs I gues? Correct me if I typed anything wrong there.
But yeah, help would be appreciated. Thanks!
Click to expand...
Click to collapse
1. You can safely root your x8 regardless of when it is manufactured, you will not brick it
2. You have 11w48 so it is very risky to unlock your bootloader, i suggest you flash ROMS that is for stock
3. If you get soft bricked you can flash the stock firmware back using flashtool or SEUS, if it is a hard brick, you need to go to the nearest Service center or use a JTAG
Swyped via Tapatalk 2
Thanks a whole bunch. I thought I cannot root because of my manufacturer date. But what is a flash ROM tho?
Jetboard said:
Thanks a whole bunch. I thought I cannot root because of my manufacturer date. But what is a flash ROM tho?
Click to expand...
Click to collapse
you can root your phone. but you can't unlock bl.
when you root your phone, you cam install cwm recovery. simply dl a rom for stock kernel and go to recovery and install(flash) the rom. remember to check the instructions first.
Just because i don't doesn't mean i can't.
All what I found until today was that if I cannot unlock BL I cannot install CWM recovery.
Maybe it is related to model - mine is Sony Xperia J. Y2012.
There is no fastboot available.
Am I wrong, can I have CWM, nandroid backup etc on stock ROM as only such one I may flash ?
F308 said:
All what I found until today was that if I cannot unlock BL I cannot install CWM recovery.
Maybe it is related to model - mine is Sony Xperia J. Y2012.
There is no fastboot available.
Am I wrong, can I have CWM, nandroid backup etc on stock ROM as only such one I may flash ?
Click to expand...
Click to collapse
this is for x8. not sure how it works on J. but yeah we don't havt fastboot either. but we can install cwm even with a locked bl. again that's for se x8.
edit: my advice is go to your phone's subforum. you'll get your answers there.
Just because i don't doesn't mean i can't.
Thank you. I understand that lot of things is device dependent but thought there are non-breakable rules, like gravity,
and what is possible to do under certain circumstances was one of them.
Need walk through XDA forum once more, maybe there is a hope.
F308 said:
Thank you. I understand that lot of things is device dependent but thought there are non-breakable rules, like gravity,
and what is possible to do under certain circumstances was one of them.
Need walk through XDA forum once more, maybe there is a hope.
Click to expand...
Click to collapse
there probably are a few unbreakable rules, but not being familiar with your device i can't guarantee that it's safe or it would work.
Just because i don't doesn't mean i can't.
Despite lot of reading I still am missing knowledge.
Question is:
What is fastboot ?
I found more than one definition of it and compiled into my own.
1.
Of course fastboot.exe is Windows binary (part of flashtool pack) which does certain type of work.
This is not what we are interested in.
2.
I concluded that:
- fastboot is one of modes into what android device can wake up. Just like linux can boot in different ways or Windows into single mode.
- this feature is encoded into boot.img, it is not separate android application.
- boot.img will work only with related kernel.img. They are like love and marriage (which is like horse and carriage - Bundy's).
- Sony sometimes disables stock boot.img to boot into this mode then without replacing boot .img it is impossible.
More comments ?
Fastboot is protocol used to update the flash filesystem in Android devices from a host over USB. It allows flashing of unsigned partition images.
Just because i don't doesn't mean i can't.
Okay, I got one more last question. Is this guide http://forum.xda-developers.com/showthread.php?t=906195&nocache=1 okay to use for rooting? I'm still trying to find the LATEST safe ones =/ I wonder if this one is okay.
Um, I tried that one it didn't work. It said some stuff are missing, then it exited randomly etc.. Can someone give me a link or a short/long guide which I can use that's latest? I do have some X8 drivers in a .zip file but no idea how to install them. Thanks in advance.
Jetboard said:
Okay, I got one more last question. Is this guide http://forum.xda-developers.com/showthread.php?t=906195&nocache=1 okay to use for rooting? I'm still trying to find the LATEST safe ones =/ I wonder if this one is good.
Click to expand...
Click to collapse
I rooted mine with this
Means its safe
Sent from my X8
Having few issues with the SuperOneClick thing... It sometimes randomly exits, tells me that some stuff are missing etc. Any help? =/

Various noob questions

Hello !
I've a new Xperia E1 Dual (2105).
I've successfully rooted it, thanks to the information I've found on this forum.
Now I've some questions :
1) on my previous phone (Xperia X8) I had a recovery screen accessible upon reboot onto which I could make backups of the whole software on the SDCARD. I would like to have the same on the E1 but I can't find nothing to make this work. What should I do ?
2) Is there any advantage to run a custom ROM on this device, given it already has 4.4 ? (the X8 needed a custom ROM to go beyond 1.6 or 2.1 version Sony delivered).
Many thanks in advance for your help !
Recovery requires unlocked bootloader
Yes, you can backup stuff using PhilZ or TWRP. You can get into recovery by tapping the walkman button during Sony logo
We are currently stuck on 4.4.2, but there are many Stock ROM mods that speeds up it up the phone, such as KillaMade, Illumination, etc.. It frees your time enchancing the ROM, or If you are completely new to Android, It avoids you to give a few headache
If you are unsure what to do, check my guide, It is mostly noob-friendly
Kizoky said:
Recovery requires unlocked bootloader
Yes, you can backup stuff using PhilZ or TWRP. You can get into recovery by tapping the walkman button during Sony logo
We are currently stuck on 4.4.2, but there are many Stock ROM mods that speeds up it up the phone, such as KillaMade, Illumination, etc.. It frees your time enchancing the ROM, or If you are completely new to Android, It avoids you to give a few headache
If you are unsure what to do, check my guide, It is mostly noob-friendly
Click to expand...
Click to collapse
Thank you for your answer.
I'm a bit confused because I am not able to install TWRP because it says that my phone is unsupported.
I've cleaned bloatware using RUninstaller (backing up each APK before removing it) and moved the backuped APK to the SDCard and to my PC for a possible re-install. But I would have liked to make a backup of all the files with the device cold before tweaking ... I like having belt and suspender when going wild
georgesgiralt said:
Thank you for your answer.
I'm a bit confused because I am not able to install TWRP because it says that my phone is unsupported.
I've cleaned bloatware using RUninstaller (backing up each APK before removing it) and moved the backuped APK to the SDCard and to my PC for a possible re-install. But I would have liked to make a backup of all the files with the device cold before tweaking ... I like having belt and suspender when going wild
Click to expand...
Click to collapse
Just saying using any TWRP app will always say E1 is incompatible, because it is not supported (officially) daily
However, you can install TWRP here: http://forum.xda-developers.com/xpe.../recovery-main-thread-twrp-xperia-e1-t3323159
As I said It requires unlocked bootloader, otherwise you can't get into recovery
Kizoky said:
Just saying using any TWRP app will always say E1 is incompatible, because it is not supported (officially) daily
However, you can install TWRP here: http://forum.xda-developers.com/xpe.../recovery-main-thread-twrp-xperia-e1-t3323159
As I said It requires unlocked bootloader, otherwise you can't get into recovery
Click to expand...
Click to collapse
Thank you for your answer !
I've read about unlocking the bootloader and saw that it will reset the phone/apps/settings to factory default.
I should have done it long before ....
But I wonder if there is a way to backup everything BEFORE unlocking and, restore after unlocking to get my settings back.
What do you think ?
georgesgiralt said:
Thank you for your answer !
I've read about unlocking the bootloader and saw that it will reset the phone/apps/settings to factory default.
I should have done it long before ....
But I wonder if there is a way to backup everything BEFORE unlocking and, restore after unlocking to get my settings back.
What do you think ?
Click to expand...
Click to collapse
Unfortunately I don't have a locked BL, so I can't really tell you how to make the recovery work, though there are many threads about how to boot into PhilZ under locked BL @xezrunner
If you do however manage to flash PhilZ, you can backup your entire system along with apps, data, and etc..
I suggest backing up TA, If you ever need to relock the BL back again to make use of the warranty
Here's the appropiate thread on how to install recovery on a locked bootloader.
xezrunner said:
Here's the appropiate thread on how to install recovery on a locked bootloader.
Click to expand...
Click to collapse
Thank you very much but I've already used that and installed a recovery. You are late by a couple of hours.
I was able to do a backup of my present configuration and even make a "custom ROM" with the actual phone. So I'm very pleased !
I looked into the service menu and saw that my boot loader is not locked and that I've no DRM installed (maybe that's because my phone is a plain Sony one ? without any paid application ? )
Now, I've just to use the thread about changing the behavior of the Walkman button in order to disable it...
Thank to all who responded and provided help ! I'm an IT guy but far from an Android guy ! And I would not have done this without you !
Edit :
An additional question :
Now, I still have a locked bootloader (because I did not unlock it) and a recovery installed (PhilZ). Do you think I could install TRWP rescue still without unlocking the BL ? (this way I may keep the warranty of the phone ?)
TWRP is in a different image file (recovery.img), which locked BLs will never be able to boot in it
PhilZ is stored in the kernel (boot.img), so you can easily flash another ftf file to erase the kernel If you need to deliver the phone to your provider
(some providers take this seriously as this is a great excuse for them to ask for more money, or even worse, refuse to repair it, however Sony is still pretty calm about things like this)
As long as your BL is locked, and your TA is intact, your warranty is safe
georgesgiralt said:
I looked into the service menu and saw that my boot loader is not locked and that I've no DRM installed (maybe that's because my phone is a plain Sony one ? without any paid application ? )
Click to expand...
Click to collapse
The Xperia E1 has no DRMs whatsoever. What DRMs could you even have? The camera lacks any enchancements Sony has for the other devices...
xezrunner said:
The Xperia E1 has no DRMs whatsoever. What DRMs could you even have? The camera lacks any enchancements Sony has for the other devices...
Click to expand...
Click to collapse
Ah ! OK !
This clarifies a lot of things. I was wondering what's this DRM thing was about.
Last question, do you know if one can backup the official ROM downloaded through Sony PC Companion during "Repair phone" operation ?
georgesgiralt said:
Ah ! OK !
This clarifies a lot of things. I was wondering what's this DRM thing was about.
Last question, do you know if one can backup the official ROM downloaded through Sony PC Companion during "Repair phone" operation ?
Click to expand...
Click to collapse
There's a much better way to get a .ftf file that you can flash with Flashtool. Use XperiFirm.
xezrunner said:
There's a much better way to get a .ftf file that you can flash with Flashtool. Use XperiFirm.
Click to expand...
Click to collapse
Thank you thank you thank you !
It's amazing the volume and quality of information I got asking simple questions.
I would have had to read thousand of pages of this forum to get that much ! You definitely saved me weeks of investment.
Do you know if I can install a Sony software made for a different CDA phone ? Because I have an old X8 which came with Orange branding and it has been so badly configured it is a pity. So I would like to try it with plain Sony Ericsson software and compare with the ROM I tested on it.
Have a bright nice day !
georgesgiralt said:
Thank you thank you thank you !
It's amazing the volume and quality of information I got asking simple questions.
I would have had to read thousand of pages of this forum to get that much ! You definitely saved me weeks of investment.
Do you know if I can install a Sony software made for a different CDA phone ? Because I have an old X8 which came with Orange branding and it has been so badly configured it is a pity. So I would like to try it with plain Sony Ericsson software and compare with the ROM I tested on it.
Have a bright nice day !
Click to expand...
Click to collapse
Absolutely, you can flash any kind of firmware and it will work as long as it's for that specific model. You might experience some issues like no 3G if the firmware was made for a country that has no 3G support or has a different kind of cellular reception. But that's rare. The amount of bloat also varies beetween firmwares, of course. Kizoky has made a thread on all the firmwares available in XperiFirm with the fewest amount of bloat, I'm using the Turkey one and it's working really nice.
Glad to be of help!
Hello !
Here I am again !
I've a question I can't solve myself.
I've searched and didn't find an answer.
When I'm at work, I would like to send some calls directly to the answering machine without the phone even ringing. Mostly the personal calls because I can't get any privacy when at work.
Before the Android Era, I had a phone with a white list and a black list. And you could manage the actions for the white or the black lists. This served me well.
On my Android 4.4 I did not find something similar.
I would be delighted to get some help from you guys !
Thanks in advance for your answer.
georgesgiralt said:
Hello !
Here I am again !
I've a question I can't solve myself.
I've searched and didn't find an answer.
When I'm at work, I would like to send some calls directly to the answering machine without the phone even ringing. Mostly the personal calls because I can't get any privacy when at work.
Before the Android Era, I had a phone with a white list and a black list. And you could manage the actions for the white or the black lists. This served me well.
On my Android 4.4 I did not find something similar.
I would be delighted to get some help from you guys !
Thanks in advance for your answer.
Click to expand...
Click to collapse
Ugh, now that's some tough question.
Try asking in here: http://forum.xda-developers.com/android/help
Kizoky,
Thank you for your answer. Actually, i had an idea to search for just blacklist android. It was more productive this way. I've to learn how to search ...
I've found two ways : the first one (not working) is to activate the black list from the settings in the contacts. The second one is to download an app to do just that. For now, I've to find one acting just on the phone call and not on the SMS. Funny Sony or Google did not think it was a need to fulfil ...

Boot-loader Flashing vs. using Flashfire

(originally posted in the flashfire threads, but it was suggested I post here)
My apologies if this has already been covered (I could not find an answer in searching)
I appreciate that it can be dangerous to use flashfire to flash the bootloader partition and that one should use fastboot. My question is:
If I download a FW package and the bootloader has changed, what happens if I flash to the kernel, system, cache, vendor etc... and do not flash to bootloader and radio? Will the flash fail; will the phone soft brick; will nothing happen and I can go merrily along?
The question derives from this: If the phone can become unusable with a mismatched bootload and radio to the rest of the images, it would require to unpack the package and check for a version prior to flashing other partitions (so I assume). If I go that far, would it not be easier to not use flashfire and simply manually flash the required files when updates are available?
Thanks
N6, unlocked and rooted (previously always updating latest patches and rerooting myself (using TWRP), but wishing to try flashire)
RLBL said:
(originally posted in the flashfire threads, but it was suggested I post here)
My apologies if this has already been covered (I could not find an answer in searching)
I appreciate that it can be dangerous to use flashfire to flash the bootloader partition and that one should use fastboot. My question is:
If I download a FW package and the bootloader has changed, what happens if I flash to the kernel, system, cache, vendor etc... and do not flash to bootloader and radio? Will the flash fail; will the phone soft brick; will nothing happen and I can go merrily along?
The question derives from this: If the phone can become unusable with a mismatched bootload and radio to the rest of the images, it would require to unpack the package and check for a version prior to flashing other partitions (so I assume). If I go that far, would it not be easier to not use flashfire and simply manually flash the required files when updates are available?
Thanks
N6, unlocked and rooted (previously always updating latest patches and rerooting myself (using TWRP), but wishing to try flashire)
Click to expand...
Click to collapse
it is really rare that a bootloader flash is required, and a radio update is never required. if you dont flash them, then you just dont flash them, thats all.
I'd add that going to a major update you'll want to pay close attention. The bootloader probably will need updating. e.g. lollipop to MM, the bootloader had to be updated.
The radio is optional and often with trial and error, you'll find a particular one that for your hardware, in your area, you get the best signal. There is a thread with N6 flashable radios here: http://forum.xda-developers.com/showthread.php?t=3066052.
Had you posted that you had an N6 in your original post, I'd have helped you, because that's what I use
ktmom said:
I'd add that going to a major update you'll want to pay close attention. The bootloader probably will need updating. e.g. lollipop to MM, the bootloader had to be updated.
The radio is optional and often with trial and error, you'll find a particular one that for your hardware, in your area, you get the best signal. There is a thread with N6 flashable radios.
Had you posted that you had an N6 in your original post, I'd have helped you, because that's what I use
Click to expand...
Click to collapse
both mm a lollipop, i never updated my bootloader. i did update it after mm though.
ktmom said:
I'd add that going to a major update you'll want to pay close attention. The bootloader probably will need updating. e.g. lollipop to MM, the bootloader had to be updated.
The radio is optional and often with trial and error, you'll find a particular one that for your hardware, in your area, you get the best signal. There is a thread with N6 flashable radios here: http://forum.xda-developers.com/showthread.php?t=3066052.
Had you posted that you had an N6 in your original post, I'd have helped you, because that's what I use
Click to expand...
Click to collapse
Oh That looks interesting. My Cellular signal sucks even though I am supposedly close to some towers. I am going to try using flashfire with these (hope I don't brick myself lol)
So I assume that when N comes out officially and I need to change bootloaders, I would do so via fasboot, then afterwards I can the the updates via fashfire.
RLBL said:
Oh That looks interesting. My Cellular signal sucks even though I am supposedly close to some towers. I am going to try using flashfire with these (hope I don't brick myself lol)
So I assume that when N comes out officially and I need to change bootloaders, I would do so via fasboot, then afterwards I can the the updates via fashfire.
Click to expand...
Click to collapse
all the radios, and bootloaders, are available in flashable zip for here on xda as well. to flash via twrp recovery
simms22 said:
all the radios, and bootloaders, are available in flashable zip for here on xda as well. to flash via twrp recovery
Click to expand...
Click to collapse
Cool... But I only used TWRP to flash the SU binaries to root. Now that I am rooted, I figured I could simply go back to stock recovery* and use flashfire going forward.
* I figured that because I had no other use for for a custom recovery presently, I may as well stay completely stock and rooted. Furthermore, from my understanding (which can be wrong) I no longer need a custom recovery to flash/install anything, as flashfire can do it all. Of course that brings one to ask "why am I rooted if I am staying stock?". I root my device so I can simulate a power button press without cancelling smart lock operations (either through tasker shell keyevent, gravity screen, or nova prime swipe gesture). I like not having to use the buttons on my phone
Why get rid of custom recovery? Just leave it and keep a backup on hand, then when there is an issue with basically anything you can just restore your backup instead of freaking out and running here using caps and exclamation marks asking how to fix.
scryan said:
Why get rid of custom recovery? Just leave it and keep a backup on hand, then when there is an issue with basically anything you can just restore your backup instead of freaking out and running here using caps and exclamation marks asking how to fix.
Click to expand...
Click to collapse
1 - why use a custom recovery if I do not need to (serious question, not being confrontational - see below)
2 - I totally know how to flash to whatever I want without using any toolkits (and ofc using a custom recovery)
3 - Why would one assume that one panics? (just because I have a low post count and admittedly an Android noob - N6 1st phone - does not mean I am an idiot)
4 - Considering I am not using custom ROMs and staying stock, I would think the likelihood of things going wrong is low (could be totally wrong there lol but I have done everything myself manually since the get go (never even taken an OTA for my upgrades), and never had 1 issue as of yet. This post was a general question in nature. It was not posted because I needed something to be fixed)
If I do not need it, why have it: I am experimenting to see if I can use FF completely stock (and rooted). Please provide some rationale as to why I should keep a custom recovery so I can evaluate (you may be 100% right). The point is: from my understanding one can use FF without a custom recovery so why not try... so far, so good.
On backups: be aware (not that you should care, but you did comment)... I have nothing on my phone that requires backing up at that... I can completely wipe the phone and it only takes time to do a google restore and I am back to where I am (been there, done that. Annoying for time though lol but I have no data on the phone safe from tasker profiles which are on my google drive and easily restored).
And what happens when you flash a bootloader and something screws up? You can't fix it from the stock recovery menu, now can you. So what not have something useful on the recovery partition for that 1 and 1000 chance something goes wrong.... Just my opinion, being I've been flashing phones since the first Android device was released on T-Mobile. The g1 (still have and still flash Roms
Sent from my Nexus 6 using XDA Free mobile app
RLBL said:
1 - why use a custom recovery if I do not need to (serious question, not being confrontational - see below)
2 - I totally know how to flash to whatever I want without using any toolkits (and ofc using a custom recovery)
3 - Why would one assume that one panics? (just because I have a low post count and admittedly an Android noob - N6 1st phone - does not mean I am an idiot)
4 - Considering I am not using custom ROMs and staying stock, I would think the likelihood of things going wrong is low (could be totally wrong there lol but I have done everything myself manually since the get go (never even taken an OTA for my upgrades), and never had 1 issue as of yet. This post was a general question in nature. It was not posted because I needed something to be fixed)
If I do not need it, why have it: I am experimenting to see if I can use FF completely stock (and rooted). Please provide some rationale as to why I should keep a custom recovery so I can evaluate (you may be 100% right). The point is: from my understanding one can use FF without a custom recovery so why not try... so far, so good.
On backups: be aware (not that you should care, but you did comment)... I have nothing on my phone that requires backing up at that... I can completely wipe the phone and it only takes time to do a google restore and I am back to where I am (been there, done that. Annoying for time though lol but I have no data on the phone safe from tasker profiles which are on my google drive and easily restored).
Click to expand...
Click to collapse
1. the only one important thing about having twrp installed.. backups and restores. before dlashing or changing anything, i akways create a backup in twrp. if something doesnt work out, you can always restore your backup, as ive done many many times. its a quicky fix it.
31ken31 said:
And what happens when you flash a bootloader and something screws up? You can't fix it from the stock recovery menu, now can you. So what not have something useful on the recovery partition for that 1 and 1000 chance something goes wrong.... Just my opinion, being I've been flashing phones since the first Android device was released on T-Mobile. The g1 (still have and still flash Roms
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I think that was the whole point of my post was it not? What happens if you DON'T flash a bootloader while using FF (but in the case where it did change)? And like I said, in the 1/1000 chance that something does go wrong and I did not have a backup: Flash the complete package via adb? Like I said, I have nothing to backup, thus nothing to recover. Not saying I shouldn't, just saying I don't. I only used TWRP to gain root access, nothing more (no custom ROMs, kernels, optimizations, anything on my phone...not even local app data saves - I am one of those old farts who uses their phone as a PDA with phone capabilities and that is it. All "data" is cloud based for calendar info etc.)
It was a relatively simple (general) question around some experimentation I am doing to see if it would work if one was completely stock (safe from root); did not think it would turn in an philosophical argument on whether or not one should use a stock recovery (which I have been using a custom up until yesterday, but was thinking about putting it back on this evening anyways, just because)
Anyways, got my answer... thx
simms22 said:
1. the only one important thing about having twrp installed.. backups and restores. before dlashing or changing anything, i akways create a backup in twrp. if something doesnt work out, you can always restore your backup, as ive done many many times. its a quicky fix it.
Click to expand...
Click to collapse
Thanks!... Obviously when I do venture into more with the phone I will do that. Currently it is a work and personal device so the only thing I do is flash Google stock builds instead of waiting for OTAs. Not saying I should not have a backup, but I don't. Only once after the 1st flash I re-locked the bootloader (as per instructions). What I waste of time; but it did show me that in a non-efficient disaster recovery, I can get everything back to where I was.
A restore would have been efficient, but I have found that I really have nothing to back up.. yet.
I guess a (off-topic) question I have for you is: What and Why did things not work out? In my case where I am only flashing stock loads (not waiting for OTAs), what could one anticipate going wrong that a re-flash could not recover from, but a restore could? Example a write corruption of a partition and the only thing I can do is boot into recovery as my PC cannot see the phone via adb? Can something like that happen?
Backing up system is what saves your a**
Sent from my Nexus 6 using XDA Free mobile app
31ken31 said:
Backing up system is what saves your a**
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
cool... but... what if you are stock? Save my ass from what? Will a (re)flash of stock binaries not suffice?
Look I appreciate I am sounding argumentative, but I am curious to understand what can happen and why. I can understand the "need" to do it if customizing a device etc... but I am very curious as to why if you are stock:
example:
A stock user unlocks his bootloader so they can flash files straight from google be it OTAs or the complete package. It is not listed anywhere to have a custom recovery in their instructions which would lead one to believe it is not required if flashing said files... I assume something could go wrong of course and the most efficient way is to do a restore from backup... but I also assume one could simply re-flash and start over.
I am not devaluating the merits of a custom recovery; I was just curious if one could use (easily) flash fire without one - and one can. The purpose of the question was two-fold:
- because I was flashing stock, then reflashing twrp to get root I found the process longer than it needed to be so I thought I could use flashfire and have it do it for me.
- then I realized that flashing re-roots as well so I did not need to flash the custom recovery to obtain root. I thought "hey what if I accidentally checked "recovery" and accidentally went back to stock. No harm done as I can move on and still be rooted.
Not sure my butt needs saving to ask. You may be doing something that having backups is a good and safe idea... what if you are not? No harm in still using a custom of course, but it was just a question (I ask such questions so I know in advance why something happened and what to do so I do not come running to forums in all caps as someone else said lol)
off topic: If one has nothing to backup, what is there to restore?
RLBL said:
cool... but... what if you are stock? Save my ass from what? Will a (re)flash of stock binaries not suffice?
Look I appreciate I am sounding argumentative, but I am curious to understand what can happen and why. I can understand the "need" to do it if customizing a device etc... but I am very curious as to why if you are stock:
example:
A stock user unlocks his bootloader so they can flash files straight from google be it OTAs or the complete package. It is not listed anywhere to have a custom recovery in their instructions which would lead one to believe it is not required if flashing said files... I assume something could go wrong of course and the most efficient way is to do a restore from backup... but I also assume one could simply re-flash and start over.
I am not devaluating the merits of a custom recovery; I was just curious if one could use (easily) flash fire without one - and one can. The purpose of the question was two-fold:
- because I was flashing stock, then reflashing twrp to get root I found the process longer than it needed to be so I thought I could use flashfire and have it do it for me.
- then I realized that flashing re-roots as well so I did not need to flash the custom recovery to obtain root. I thought "hey what if I accidentally checked "recovery" and accidentally went back to stock. No harm done as I can move on and still be rooted.
Not sure my butt needs saving to ask. You may be doing something that having backups is a good and safe idea... what if you are not? No harm in still using a custom of course, but it was just a question (I ask such questions so I know in advance why something happened and what to do so I do not come running to forums in all caps as someone else said lol)
off topic: If one has nothing to backup, what is there to restore?
Click to expand...
Click to collapse
its all a matter of choice, period.
flashing stock, you dont need to do anything. flashing different mods, custom roms, gapps, or supersu, you need to use twrp recovery. you can even flash twrp to be permenant or flash twrp for a one time use. if you are flashing custom roms/mods regularly, its convieniant to have twrp, if your not it doesnt matter. but the one thing twrp is great for is backing up, in case. and you dont need many back ups, just one recent backup. so you can back up, then get rid of twrp until needed again. anyways, its all a personal choice, and thats all it is. for me, flashing twrp then leaving it makes sense, since ill never ever do anything stock. for you, you have your own needs and wants.
simms22 said:
its all a matter of choice, period.
flashing stock, you dont need to do anything. flashing different mods, custom roms, gapps, or supersu, you need to use twrp recovery. you can even flash twrp to be permenant or flash twrp for a one time use. if you are flashing custom roms/mods regularly, its convieniant to have twrp, if your not it doesnt matter. but the one thing twrp is great for is backing up, in case. and you dont need many back ups, just one recent backup. so you can back up, then get rid of twrp until needed again. anyways, its all a personal choice, and thats all it is. for me, flashing twrp then leaving it makes sense, since ill never ever do anything stock. for you, you have your own needs and wants.
Click to expand...
Click to collapse
Thank you for answering the question.
I figure when this phone (or whichever phone) is not my daily driver and no longer linked to sensitive stuff I will start venturing into the domain of custom ROMs and Kernels.
RLBL said:
Thank you for answering the question.
I figure when this phone (or whichever phone) is not my daily driver and no longer linked to sensitive stuff I will start venturing into the domain of custom ROMs and Kernels.
Click to expand...
Click to collapse
custom recoveries just make things easier for you, overall, to do stuff. but kernels, that could be the bomb. but you will need to learn about how to use governors/schedulers to make any kind of headways. for example, i use a completely different governor/scheduler(ondemand/deadline) than any other nexus kernel, and i feel that my way makes my phone much better/faster than any other setup. and thats whats important to me
Update: test passed (I knew it would)
With a stock recovery, I was able to use flashfire and upgrade to the latest update and re-root.

z3 compact how to root? me confused or me stupid

i am deeply sorry if this is the wrong place or already been answered but i have spent almost 6 hours looking for the right solution.
so the story is i have a Z3 compact which is branded to Vodafone UK (not sure if it is relevant)
attached are images of my about page and the configuration page (where you dial *#*#7378423#*#*)
i also (on my search) have my code from the sony site where i selected my phone, sent an email, entered IMEI number and gave me a code to run using fastboot (this did not work for me)
based on theses settings what program/files/tools do i need to install custom rom, which i guess also will root it (im looking at either paranoid android or lineageOS)
paresh90 said:
i am deeply sorry if this is the wrong place or already been answered but i have spent almost 6 hours looking for the right solution.
so the story is i have a Z3 compact which is branded to Vodafone UK (not sure if it is relevant)
attached are images of my about page and the configuration page (where you dial *#*#7378423#*#*)
i also (on my search) have my code from the sony site where i selected my phone, sent an email, entered IMEI number and gave me a code to run using fastboot (this did not work for me)
based on theses settings what program/files/tools do i need to install custom rom, which i guess also will root it (im looking at either paranoid android or lineageOS)
Click to expand...
Click to collapse
You can't unlock you bootloader mate, the screenshot you put up says so. Meaning no custom kernels, which also means no ROMs that aren't based on stock. You're stuck with MIUI and various other zip-ports. No Lineage or AOSPA etc.
You can root it no problem though. Just use google or whatever, there's a couple of ways to do it.
someone755 said:
You can't unlock you bootloader mate, the screenshot you put up says so. Meaning no custom kernels, which also means no ROMs that aren't based on stock. You're stuck with MIUI and various other zip-ports. No Lineage or AOSPA etc.
You can root it no problem though. Just use google or whatever, there's a couple of ways to do it.
Click to expand...
Click to collapse
thank you for your response thought this would be a dead thread.
a few follow up questions if i may:
1. i asume i can find any post with MIUI in the title while should be compatible
2. i read something about down grade of firmware (is that a possible option for me)
3. in my google searching, would i need to state that my BL is locked
paresh90 said:
thank you for your response thought this would be a dead thread.
a few follow up questions if i may:
1. i asume i can find any post with MIUI in the title while should be compatible
2. i read something about down grade of firmware (is that a possible option for me)
3. in my google searching, would i need to state that my BL is locked
Click to expand...
Click to collapse
Just find a MIUI ROM in the dev section if you want MIUI.
You can install any firmware from Sony using Flashtool. Learn to use it, it's gonna be your friend.
That means you download any FTF file for your phone (there's a thread somewhere with a collection of FTFs), and you can flash it. KitKat, Lollipop, Marshmallow, or Concept.
I don't know how to root really, I just do it the old fashioned way since my bootloader is unlocked (and I pray that never changes). I think you'll have to downgrade to KitKat, which, again, is very easy if you know how to use Flashtool.
Np mate, I know the feeling of dead threads. Just happened by luck that I saw yours and got intrigued by the title lol.
someone755 said:
Just find a MIUI ROM in the dev section if you want MIUI.
You can install any firmware from Sony using Flashtool. Learn to use it, it's gonna be your friend.
That means you download any FTF file for your phone (there's a thread somewhere with a collection of FTFs), and you can flash it. KitKat, Lollipop, Marshmallow, or Concept.
I don't know how to root really, I just do it the old fashioned way since my bootloader is unlocked (and I pray that never changes). I think you'll have to downgrade to KitKat, which, again, is very easy if you know how to use Flashtool.
Np mate, I know the feeling of dead threads. Just happened by luck that I saw yours and got intrigued by the title lol.
Click to expand...
Click to collapse
It's difficult trying to find a post that works for your situation.
Top of your head do you know any good miui ROMs. Light ones
And if I downgrade to kitkat or something will I be able to unlock my BL (or is it compleatly different )
I don't have the phone with me will check tomorrow
paresh90 said:
It's difficult trying to find a post that works for your situation.
Top of your head do you know any good miui ROMs. Light ones
And if I downgrade to kitkat or something will I be able to unlock my BL (or is it compleatly different )
I don't have the phone with me will check tomorrow
Click to expand...
Click to collapse
Haven't used MIUI since 2013 so you'll have to find one by yourself lol. I'm more of an AOSP guy -- if I was forced to use a locked bootloader I'd just install the concept FTF. That's about as light as you can get on this phone.
You can't unlock your bootloader, period. No software hack will help you. At least not from home. You'd need something like a riffbox and extensive knowledge of the phone's bootloader software to unlock it.
someone755 said:
Haven't used MIUI since 2013 so you'll have to find one by yourself lol. I'm more of an AOSP guy -- if I was forced to use a locked bootloader I'd just install the concept FTF. That's about as light as you can get on this phone.
You can't unlock your bootloader, period. No software hack will help you. At least not from home. You'd need something like a riffbox and extensive knowledge of the phone's bootloader software to unlock it.
Click to expand...
Click to collapse
Concept it is
Ok thank you for making it super clear (for me and anyone else reading this. )
It's annoying that the sony website gave me a code to unlock it. I'm sure they could have known from the IMEI number whqt it was and stuff.
paresh90 said:
Concept it is
Ok thank you for making it super clear (for me and anyone else reading this. )
It's annoying that the sony website gave me a code to unlock it. I'm sure they could have known from the IMEI number whqt it was and stuff.
Click to expand...
Click to collapse
I think the carriers lock the bootloaders, not Sony. As far to my knowledge, Sony ships out the devices unlocked, and the carriers decide whether to lock them, but don't report back to Sony. Their site just assumes you don't have a s'hitty carrier.
Best of luck man, and welcome to the Z3C forums!

Categories

Resources