[Q] Top Reasons Why People Brick The Z1? - Xperia Z1 Q&A, Help & Troubleshooting

I have been reading alot in this forum and i get the feeling its about 50/50 that you will break the Z1, Obviously it's not 50/50. But i get that feeling. I have been rooting and doing stuff on Samsung phones and i never ever bricked any phone. But with this phone it feels like dark territory.
Can someone enlighten me what people are doing wrong that bricks the phone so easily?

Gnubaver said:
I have been reading alot in this forum and i get the feeling its about 50/50 that you will break the Z1, Obviously it's not 50/50. But i get that feeling. I have been rooting and doing stuff on Samsung phones and i never ever bricked any phone. But with this phone it feels like dark territory.
Can someone enlighten me what people are doing wrong that bricks the phone so easily?
Click to expand...
Click to collapse
Flash wrong kernel
Restore TA-partition from some other device

schickel said:
Flash wrong kernel
Restore TA-partition from some other device
Click to expand...
Click to collapse
Flashing wrong kernel only softbricks your phone right?
And restoring another TA-Partition hardbricks?

Hard brick:
- Flash other phones TA
- Flash other phones bootloader
All other things shouldn't cause a hard brick unless you really screw it
Sent from my C6903 using xda app-developers app

Double Post

krabappel2548 said:
Hard brick:
- Flash other phones TA
- Flash other phones bootloader
All other things shouldn't cause a hard brick unless you really screw it
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
So as long as i double check everything and have common sense it should be alright at all times?
And how do i check exactly what model i have? I have seen a few models Z1F Z1, 6903, 6907.

Its all Rookie mistakes.
as long as you know what your are doing and not rushing, your phone should never brick.
Plus most of the bricks you hear about happened because people were installing Stock rom. if you are interested in AOSP roms then you dont have to worry.
is only happened when people used the flashtool to reinstall the kernel and baseband.
Back up the TA and Use flashtool carefully. thats all.

omar300 said:
Its all Rookie mistakes.
as long as you know what your are doing and not rushing, your phone should never brick.
Plus most of the bricks you hear about happened because people were installing Stock rom. if you are interested in AOSP roms then you dont have to worry.
is only happened when people used the flashtool to reinstall the kernel and baseband.
Back up the TA and Use flashtool carefully. thats all.
Click to expand...
Click to collapse
I'm not sure i follow you, installing stock rom? Why would that brick?
And i'm mostly interested in kernels

Gnubaver said:
I'm not sure i follow you, installing stock rom? Why would that brick?
And i'm mostly interested in kernels
Click to expand...
Click to collapse
btw stock i mean rom based on sony roms. many poeple are interested in those. including myself
the sony roms are built around different versions of phone means different baseband and if your are using lte and install european phone version rom your lte can stop working thus u install baseband for your phone from flashtool.
if you interested in kernel you should be good. install any kernel for z1. they all are same.
but confirm that though. it never cause issue for me

omar300 said:
btw stock i mean rom based on sony roms. many poeple are interested in those. including myself
the sony roms are built around different versions of phone means different baseband and if your are using lte and install european phone version rom your lte can stop working thus u install baseband for your phone from flashtool.
if you interested in kernel you should be good. install any kernel for z1. they all are same.
but confirm that though. it never cause issue for me
Click to expand...
Click to collapse
So what you are saying is, people tend to brick the phone by flashing a stock rom not meant for the specific model?
And by doing this and the lte stops working, this is only a semi brick right? Redoing the right FW restores the phone and LTE support in this case without any real harm done?
I think i have a 6903 model.

99% of bricking is because of user mistakes.
Double read everything and make sure you understand what you can flash depending on bootloader status.
Sent from my Z1 via transwarp conduit.

Gnubaver said:
So what you are saying is, people tend to brick the phone by flashing a stock rom not meant for the specific model?
And by doing this and the lte stops working, this is only a semi brick right? Redoing the right FW restores the phone and LTE support in this case without any real harm done?
I think i have a 6903 model.
Click to expand...
Click to collapse
thats not bricking. thats just losing lte or 4g feature. easily can be fixed by installing right baseband from ftf file.
read the developers note in first post. most roms come with 6903/6902 baseband version. in middle of installation you can pick your phone.
so you wont run into that trouble anyways.
Always read the instructions in first post by developer of rom.
same goes for any device even if its a nexus and unbrickable.
what you read about is when sony made some deep changes and people didnt know about it.
now its clearly mentioned in instructions.
i was one of those who bricked the phone. sony replaced the motherboard for my phone no charges.

omar300 said:
thats not bricking. thats just losing lte or 4g feature. easily can be fixed by installing right baseband from ftf file.
read the developers note in first post. most roms come with 6903/6902 baseband version. in middle of installation you can pick your phone.
so you wont run into that trouble anyways.
Always read the instructions in first post by developer of rom.
same goes for any device even if its a nexus and unbrickable.
what you read about is when sony made some deep changes and people didnt know about it.
now its clearly mentioned in instructions.
i was one of those who bricked the phone. sony replaced the motherboard for my phone no charges.
Click to expand...
Click to collapse
And you just told them that it wouldn't boot up and you had no idea what could have caused it?

Gnubaver said:
And you just told them that it wouldn't boot up and you had no idea what could have caused it?
Click to expand...
Click to collapse
Yes. Be creative with excuses. Lol

Related

Bricking your phone.

i am thinking of rooting and modding my nexus one, but i am a little bit afraid of bricking it and voiding the warranty doing so. from what ive read the only way to brick your nexus one atm is to flash the"radio". not exactly sure what the raido is (assuming it has do with carrier/phone frequency).
is there any way to brick your phone besides modding the "radio" which i hope cant happen on accident.
ps:sry if this is a nub question, don't wan to throw 600$ down the toilet.
Okay I really don't quite understand why but EVERY SINGLE DAY there's someone asking the SAME question...
If you search a bit you'll EASILY find an answer to your question.
So, how CAN you brick your phone?
1. Flashing radio and interrupting the process.
2. Flashing SPL and interrupting the process.
NO OTHER WAY.
Cheers.
Possible via subjecting the device to a devastating Solar EMP.
I'm just sayin'.
St.Jimmy! said:
Okay I really don't quite understand why but EVERY SINGLE DAY there's someone asking the SAME question...
If you search a bit you'll EASILY find an answer to your question.
So, how CAN you brick your phone?
1. Flashing radio and interrupting the process.
2. Flashing SPL and interrupting the process.
NO OTHER WAY.
Cheers.
Click to expand...
Click to collapse
Or by flashing Radios/SPL that ARE NOT MENT FOR YOUR DEVICE!!! Can't forget that one!!!
martin0285 said:
Or by flashing Radios/SPL that ARE NOT MENT FOR YOUR DEVICE!!! Can't forget that one!!!
Click to expand...
Click to collapse
Yeah OK I gave that one for granted, but thanks dude.
St.Jimmy! said:
So, how CAN you brick your phone?
1. Flashing radio and interrupting the process.
2. Flashing SPL and interrupting the process.
NO OTHER WAY.
Click to expand...
Click to collapse
Yeah, this is kinda misleading.
Here's another way. Flash your SPL (not interrupt it) and NOT flash to a radio compatible with your SPL will brick it to (or vice versa).
If you double check everything and make sure your good, its easy. If you do it when your tired and in a rush, you can brick pretty easily. Killed my magic that that way.
But currently, on a retail N1, we can only brick it with an incorrect/interrupted radio flash... we cannot flash the SPL "yet!!"
Exactly why I never will flash a radio or spl, though I am good at following directions - I don't have any reception issues, or any other problem that would require a radio change.
Just stay away from it all if you don't want to any troubles or worries.
Or it can be like mine and just randomly die.
Eclair~ said:
Exactly why I never will flash a radio or spl, though I am good at following directions - I don't have any reception issues, or any other problem that would require a radio change.
Just stay away from it all if you don't want to any troubles or worries.
Click to expand...
Click to collapse
true, but you have to live on the edge sometime . as others have said don't interrupt the process and make sure you have plenty of battery or you're connected to a power outlet. it can take 5 minutes or so to complete. i was in downtown Boston yesterday/today and ERE27 wasn't working for me... so i flashed ERE36B and it was working much better. go figure. if ERE36B is flaky when i get home, i'll swap back to ERE27.
Though, if you just take your time, not rush, and follow every single instruction (all well written btw, never had a misleading one) you shouldn't have an issue. Just take your time
cortez.i said:
true, but you have to live on the edge sometime . as others have said don't interrupt the process and make sure you have plenty of battery or you're connected to a power outlet. it can take 5 minutes or so to complete. i was in downtown Boston yesterday/today and ERE27 wasn't working for me... so i flashed ERE36B and it was working much better. go figure. if ERE36B is flaky when i get home, i'll swap back to ERE27.
Click to expand...
Click to collapse
I thought it would be better to ask here than make a new thread but can you flash a radio strait on the phone and not need a computer? Because I have always thought you needed a computer.
More noob questions.
1)flashing the radio, is there any reason to do so? inst the radio for your carrier, and the only reason to flash it is to unlock the phone (or allow it to be used on a different carrier). mine is unlocked so will i ever have to flash the radio to mod my phone?.
2) flashing SPL, it seems that it is not possible to do so atm for the N1. would there be any reason for me to flash the SPL if im looking to root/use custom roms.
thanks for the replies, sry for nub questions.
flashing the radio is done a few different ways, I prefer the .zip method where you can install it just like a ROM. Very quick and easy.
As far as why you flash them, some people have better luck with different radios. I bounce back and forth between the 3 and haven't found a better one yet. But never the less, newer radios will typically be better as far as signal and connectivity. On my G1, the latest radio bumped me up to 4 bars where before I only had 2....wish there was one for my Nexus that did that! LOL
haxxo said:
(or allow it to be used on a different carrier). mine
Click to expand...
Click to collapse
Unlocking your phone in the bootloader sense has nothing to do with being locked to a carrier.
martin0285 said:
Or by flashing Radios/SPL that ARE NOT MENT FOR YOUR DEVICE!!! Can't forget that one!!!
Click to expand...
Click to collapse
Even that is not even possible on an S-ON Nexus One.
coolbho3000 said:
Even that is not even possible on an S-ON Nexus One.
Click to expand...
Click to collapse
flash a radio designed for MyTouch3G and let me know

roms

hi guys sort of a noobish question but does flashing to many roms damage your sgs?
No, it will not.
It is like installing windows or linux on your computer.
You can do it hundreds of time, you will never damage anything.
The best point is that you can always flash back the original samsung rom and have your original phone back
Etienne38 said:
No, it will not.
It is like installing windows or linux on your computer.
You can do it hundreds of time, you will never damage anything.
The best point is that you can always flash back the original samsung rom and have your original phone back
Click to expand...
Click to collapse
yea i know so flashing tons of roms wont damage my sgs thanks
But be careful with bootloaders.. when flashing these, it might brick your phone.
Erakko said:
But be careful with bootloaders.. when flashing these, it might brick your phone.
Click to expand...
Click to collapse
I'm not that noobish I was just wondering and the system is allmost unbrickable
Sent from my GT-I9000 using Tapatalk

[Q]Is it ok to use PrimeHD or miniCM7 even if your phone is not "unlocked"?

Hello, I've been using GingerDX for sometime now and I want to try PrimeHD or miniCM7 but my phone is 11w29+ and I'm afraid it might get bricked... I'm kinda new here... Thanks in advance!
If your phone is not unlocked, that means that you are using the stock kernel. Fortunately, the PrimeHD dev has made a version of the ROM that works with the stock kernel. So yes, you can install it.
If you know what you're doing and ready for?
Hi, If ya still new to Field of Unlocking Bootloader, I strongly recommend you try other roms which are for UNLOCKED BOOTLOADED x8 first.
Because unlocking bootloaders for unexperienced user (means you probably have no idea what are you doing and dunno what's gonna happen) may lead to serious consequences like function failure, or In the worst case, unlocking the boot loader will cause physical injuries or material damage, for example, due to the phone overheating.
Until you're ready and understand whatever it takes, then give it a shot that time BUT, ALWAYS REMEMBER TO DO BACKUP UR FILES via RECOVERY , when u trying to Install NEW ROM everytime. With that, u can restore back to ur previous ROM if u're not satisfied with Newer one
Sincerely,
whitefang
Chris95X8 said:
If your phone is not unlocked, that means that you are using the stock kernel. Fortunately, the PrimeHD dev has made a version of the ROM that works with the stock kernel. So yes, you can install it.
Click to expand...
Click to collapse
Thanks man!
whitefang3456 said:
Hi, If ya still new to Field of Unlocking Bootloader, I strongly recommend you try other roms which are for UNLOCKED BOOTLOADED x8 first.
Because unlocking bootloaders for unexperienced user (means you probably have no idea what are you doing and dunno what's gonna happen) may lead to serious consequences like function failure, or In the worst case, unlocking the boot loader will cause physical injuries or material damage, for example, due to the phone overheating.
Until you're ready and understand whatever it takes, then give it a shot that time BUT, ALWAYS REMEMBER TO DO BACKUP UR FILES via RECOVERY , when u trying to Install NEW ROM everytime. With that, u can restore back to ur previous ROM if u're not satisfied with Newer one
Sincerely,
whitefang
Click to expand...
Click to collapse
Thanks for the the advice! Hehehe... There was one time that I "soft bricked" my phone...
Welcome
MarLeee said:
Thanks man!
Thanks for the the advice! Hehehe... There was one time that I "soft bricked" my phone...
Click to expand...
Click to collapse
No problemo Feel free to post if you have issues
Sincerely,
Whitefang

[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? =/

[Q] The fu...lovely bootloader

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

Categories

Resources