Am not such a noob, I've been unlocking, flashing, rooting and messing with xdas since my first oldschool qtek ... but am going to ask totally noobish question, which has probably been answered many times and you'll probably hate me for doing so.
anyways...
after my xperia mini pro got smashed accidentaly, I've bought xperia sola today, I couldn't resisted and am just playin' with now...
am probably all about to unlock, flash, overclock and reinstall it, but I'm not going to trust sony completely, so I'm worried about things that got me in past like broken buttons, failing audio jacks etc etc. and for problems like those you're glad for your warranty, long story short, the noobish question is:
please, give me hint, link, short tutorial - which is best way to backup stock rom and state of the phone before unlocking and flashing another bootloader and roms?
for example, am I able to extract some .ftf image of rom or something like that? to be able completely revert all my activity on that phone in case I would have to let it repaired because of some hw issues? simply, which is the safest and best way to revert and fool the service guys if I would have to?
thanx a lot for any link, suggestion or kickstart...
4n60 said:
Am not such a noob, I've been unlocking, flashing, rooting and messing with xdas since my first oldschool qtek ... but am going to ask totally noobish question, which has probably been answered many times and you'll probably hate me for doing so.
anyways...
after my xperia mini pro got smashed accidentaly, I've bought xperia sola today, I couldn't resisted and am just playin' with now...
am probably all about to unlock, flash, overclock and reinstall it, but I'm not going to trust sony completely, so I'm worried about things that got me in past like broken buttons, failing audio jacks etc etc. and for problems like those you're glad for your warranty, long story short, the noobish question is:
please, give me hint, link, short tutorial - which is best way to backup stock rom and state of the phone before unlocking and flashing another bootloader and roms?
for example, am I able to extract some .ftf image of rom or something like that? to be able completely revert all my activity on that phone in case I would have to let it repaired because of some hw issues? simply, which is the safest and best way to revert and fool the service guys if I would have to?
thanx a lot for any link, suggestion or kickstart...
Click to expand...
Click to collapse
you will need... download these things
1) flashtool
2) stock ftf ICS (from dev section)
3) stock ftf GB (may be needed)
just keep these things handy whenever doing anything.....
for everything else read the stickies in this section itself........
@[email protected] said:
you will need... download these things
1) flashtool
2) stock ftf ICS (from dev section)
3) stock ftf GB (may be needed)
just keep these things handy whenever doing anything.....
for everything else read the stickies in this section itself........
Click to expand...
Click to collapse
so, flashing some stock ftf roms and then maybe update via companion or something like that must be sastifying and enough.
anything I might mess up and change via flashtool etc might be reflashed back to locked and stock via ftf...
so, its safe then, if I can revert. thanx...
and any way how to get ftf from stock rom I bought it with? or its too difficult and flashing stock roms from dev section and updating after is enough?
Hi, noobs are welcome! Or half-noobs or whatever...
OK so the official story from Sony is that if you root or unlock the bootloader, they will know and they are not obliged to accept your warranty. However, I've good news, if you return your phone to stock, for example using PC Companion or Update Service (with locked bootloader, or it will brick) then they are unlikely to refuse warranty - in fact, I've never heard of Sony refusing becuase of root.
Even better, many users here who unlocked their bootloaders have sent away for repair and their phone was repaired under warranty, with no cost! That's really good news! :victory:
4n60 said:
so, flashing some stock ftf roms and then maybe update via companion or something like that must be sastifying and enough.
anything I might mess up and change via flashtool etc might be reflashed back to locked and stock via ftf...
so, its safe then, if I can revert. thanx...
and any way how to get ftf from stock rom I bought it with? or its too difficult and flashing stock roms from dev section and updating after is enough?
Click to expand...
Click to collapse
to backup the rom u got with ur fone perform these steps:
1. You need to reinstall the firmware using SUS (Sony Update Service )
2. After completing go to C:\Program Files\Sony Mobile\Update Service\db\13740270\blob_fs\
3. Copy 2 files One of 15 mb and other around +- 200/300 MB into a New folder
4. Run FlashTool > Tools > Decrypt Files
5. Source folder : New folder that you created
6. From Files, Select both of the files and select OK
7. Wait till the decrypting finishes , after it does, a list will appear on the left
8. From Folder list, select all and move everything to the right
9. Fill all the details in the box
10. If the firmware that you are backing up is ICS then mark Disable Final Verification Check and select OK
11. Select your device > Ok
12. You will see the backed up firmware in > C: > flashtool > firmwares
Related
Is there a way to root my officialy updated to ICS, Xperia Mini(ST15i) without unlocking bootloader?(in order to downgrade etc...) I just want to root my xperia mini without messing up with the warranty....Any way to root it with locked bootloader? (4.1.B.0.431)
Thanks in advance
You have to downgrade to Gingerbread, root it and then upgrade to ICS using THIS tutorial.
There could be a different way: you should flash the 4.0.3 kernel (for example the Arc one), but I can't find the tutorial. Use the search button and see if you can find it
Feanor88 said:
You have to downgrade to Gingerbread, root it and then upgrade to ICS using THIS tutorial.
There could be a different way: you should flash the 4.0.3 kernel (for example the Arc one), but I can't find the tutorial. Use the search button and see if you can find it
Click to expand...
Click to collapse
downgrading needs unlocked bootloader... :/ i had bricked my mini some time ago because i tried to downgrade with locked... (( any other way?
Thanks
EDIT: flashing xperia arc's or Neo V's for example would brick my phone....wouldn't it? (and it also needs bootloader unlock...so i don't think i would do that... BUT thanks for your help mate
No, flashing a .ftf does NOT need an unlocked bootloader. You need to unlock it only if you want to flash a custom kernel, but for custom ROMs you can use flashtool.
Same for the 4.0.3 kernel. It's a stock kernel, so you can flash it via flashtool
It WILL end in bootloop, though. The tutorial says you can use DoomLord's root kit anyway, root the phone and then flash again the 4.0.4 kernel. But find it and read it carefully, cause I didn't try it and I can't assure you it will work.
I tried the first one I suggested, though, and my bootloader is locked!
Feanor88 said:
No, flashing a .ftf does NOT need an unlocked bootloader. You need to unlock it only if you want to flash a custom kernel, but for custom ROMs you can use flashtool.
Same for the 4.0.3 kernel. It's a stock kernel, so you can flash it via flashtool
It WILL end in bootloop, though. The tutorial says you can use DoomLord's root kit anyway, root the phone and then flash again the 4.0.4 kernel. But find it and read it carefully, cause I didn't try it and I can't assure you it will work.
I tried the first one I suggested, though, and my bootloader is locked!
Click to expand...
Click to collapse
man i have a problem...when i place my phone into flashmode (down key) it disconnects on its own...and that's why i bricked my phone long time ago....now i am afraid to do that i have installed the flashtool drivers from Flashtool/drivers.... but they mustn't work for my mini....any solution please give me the drivers you use for your Mini and work with it if you can i would really appreciate that!
What do you mean, it disconnects? How much time does it take for it to disconnect? Mine does the same. If I plug it and wait for a minute or so doing nothing, it disconnects. But if I start flashing a ROM it doesn't.
The drivers I installed are in \Flashtool\drivers.
Feanor88 said:
What do you mean, it disconnects? How much time does it take for it to disconnect? Mine does the same. If I plug it and wait for a minute or so doing nothing, it disconnects. But if I start flashing a ROM it doesn't.
The drivers I installed are in \Flashtool\drivers.
Click to expand...
Click to collapse
it takes about 1-2 minutes to disconnect.But, what if it disconnects while on downgrading?
It doesn't. At least, mine doesn't! And I flashed firmware twice a day in the last week
Anyway, both ways need the use of flashtool... so if you don't want to try it, you can't root ICS
Feanor88 said:
It doesn't. At least, mine doesn't! And I flashed firmware twice a day in the last week
Anyway, both ways need the use of flashtool... so if you don't want to try it, you can't root ICS
Click to expand...
Click to collapse
Pfff i'm a bit scared.....there is no hope that there will be somewhen another way to root...?
No, I'm sorry. Anyway, just follow this steps:
1) DON'T plug your phone.
2) Open flashtool
3) Click the lightning icon and select flashmode
4) Select the .ftf you want to flash: if you want to downgrade, select wipe data. If you want to flash the 4.0.3 kernel, unckeck wipe data and check "exclude" for everything apart from kernel. Which means you'll only flash the kernel
5) Start: you'll be asked to plug your phone. Plug it now in flashmode. This way you'll avoid it being unplugged.
Flashing will start, and your phone won't be unplugged. I suppose it's unplugged automatically when you're not doing anything, it's the same for me, but I repeat, whenever I flash something (kernel, whole ROM, whatever) everything just goes fine
Feanor88 said:
No, I'm sorry. Anyway, just follow this steps:
1) DON'T plug your phone.
2) Open flashtool
3) Click the lightning icon and select flashmode
4) Select the .ftf you want to flash: if you want to downgrade, select wipe data. If you want to flash the 4.0.3 kernel, unckeck wipe data and check "exclude" for everything apart from kernel. Which means you'll only flash the kernel
5) Start: you'll be asked to plug your phone. Plug it now in flashmode. This way you'll avoid it being unplugged.
Flashing will start, and your phone won't be unplugged. I suppose it's unplugged automatically when you're not doing anything, it's the same for me, but I repeat, whenever I flash something (kernel, whole ROM, whatever) everything just goes fine
Click to expand...
Click to collapse
i maybe try it later... thanks for your replies man DD i appreciate that
kwstas 13 said:
i maybe try it later... thanks for your replies man DD i appreciate that
Click to expand...
Click to collapse
Let me know if you need more help!
Feanor88 said:
Let me know if you need more help!
Click to expand...
Click to collapse
A friend of mine told me that if i try with locked bootloader is a simple suicide!!! :/ Now i am confused again :S
kwstas 13 said:
A friend of mine told me that if i try with locked bootloader is a simple suicide!!! :/ Now i am confused again :S
Click to expand...
Click to collapse
Who is that friend of you? He is trolling. Stay away from him. And learn this. Feanor here is a better friend for you than him, when it comes to rooting your phone.
Just do as in the tutorial Fenor had shared in his first post. Everything will be fine.
And you say you bricked your phone. May we know how your repaired it?
Thanks,
Rick
Sent from my SK17i using XDA
DragonClawsAreSharp said:
Feanor here is a better friend for you than him, when it comes to rooting your phone.
Click to expand...
Click to collapse
Blushing
But don't forget I'm a noob after all... I'll just keep pointing other people's tutorials, like for example yours, Rick
DragonClawsAreSharp said:
Who is that friend of you? He is trolling. Stay away from him. And learn this. Feanor here is a better friend for you than him, when it comes to rooting your phone.
Just do as in the tutorial Fenor had shared in his first post. Everything will be fine.
And you say you bricked your phone. May we know how your repaired it?
Thanks,
Rick
Sent from my SK17i using XDA
Click to expand...
Click to collapse
while i was downgrading with locked bootloader the procces stopped on its own at 43%....and my phone wouldn't turn on and didn't even worked with flashtool....i sent it to a service centre and they fixed it ( i think i hadn't installed the proper drivers....am i right?)
kwstas 13 said:
while i was downgrading with locked bootloader the procces stopped on its own at 43%....and my phone wouldn't turn on and didn't even worked with flashtool....i sent it to a service centre and they fixed it ( i think i hadn't installed the proper drivers....am i right?)
Click to expand...
Click to collapse
That's strange. Anyway, if you installed PC Companion you have adb drivers. Install flashmode drivers from Flashtool installazion folder, you find the executable in \Flashtool\drivers. If Windows prompts you that the drivers are dangerous, just install them anyway.
What I can say is that you DON'T need to unlock your bootloader to use flashmode in Flashtool. Otherwise, my phone would have exploded long ago
Now let me tell you this: if you are SURE you did everything the right way, and still your phone got bricked, then maybe you shouldn't try. you never know.
If you tried to to something you didn't know how to do, you probably made a mistake, and that's why the phone got bricked.In this case, I'd give it a try.
But we're not able to see your phone and test it, so whatever you do, unfortunately, you always do it on your own risk.
I couldn't be more sincere.
kwstas 13 said:
while i was downgrading with locked bootloader the procces stopped on its own at 43%....and my phone wouldn't turn on and didn't even worked with flashtool....i sent it to a service centre and they fixed it ( i think i hadn't installed the proper drivers....am i right?)
Click to expand...
Click to collapse
On all probability you are correct.
They (The service centre people) flashed a firmware using Flashtool. That's what they must have did. See. I will explain things a bit.
Your phone has some memory in it (this corresponds to what was known as phone memory in older phones). This memory is of Read Only type. That is ROM. Now, of all the types of ROMs, androids have EEPROM. That stands for Electronically Erasable Programmable ROM. So you can electronically erase the data stored in the ROM and write new data on it (even though it is called Read Only). This process of writing new data on the ROM is called flashing.
For flashing, the tool that is available to us as an open source, is Flashtool. Using it we can flash ROMs into our phones, erasing the earlier ones.
Now, Sony will not want us to flash Cyanogen Mod to our phones. So they have made up the concept of locking the bootloaders. With locked bootloaders custom ROMs can not be flashed to your phone. This is because most custom ROMs are designed for a specific Kernel (the intermediate between the OS and the hardware), and flashing a custom kernel requires unlocked bootloaders.
If you want, you can flash firmwares (ROMs + Kernels released by Sony) even if you are on locked bootloader, as long as the firmware files are signed by Sony.
This restriction however is against the OpenSource spirit of Android, and thus Sony gives us the scope to unlock bootloader at the cost of loosing the warranty, and the DRM keys (search google for that).
Now coming to your problem of unability to flash properly, make sure that you have installed all the drivers. For that open up /drivers folder in /flashtool and install the .exe there. Also install the adb drivers of your device. For that have PC Companion installed on your PC. Flashing will happen properly then.
Thanks,
Rick
Sent from my SK17i using XDA
DragonClawsAreSharp said:
On all probability you are correct.
They (The service centre people) flashed a firmware using Flashtool. That's what they must have did. See. I will explain things a bit.
Your phone has some memory in it (this corresponds to what was known as phone memory in older phones). This memory is of Read Only type. That is ROM. Now, of all the types of ROMs, androids have EEPROM. That stands for Electronically Erasable Programmable ROM. So you can electronically erase the data stored in the ROM and write new data on it (even though it is called Read Only). This process of writing new data on the ROM is called flashing.
For flashing, the tool that is available to us as an open source, is Flashtool. Using it we can flash ROMs into our phones, erasing the earlier ones.
Now, Sony will not want us to flash Cyanogen Mod to our phones. So they have made up the concept of locking the bootloaders. With locked bootloaders custom ROMs can not be flashed to your phone. This is because most custom ROMs are designed for a specific Kernel (the intermediate between the OS and the hardware), and flashing a custom kernel requires unlocked bootloaders.
If you want, you can flash firmwares (ROMs + Kernels released by Sony) even if you are on locked bootloader, as long as the firmware files are signed by Sony.
This restriction however is against the OpenSource spirit of Android, and thus Sony gives us the scope to unlock bootloader at the cost of loosing the warranty, and the DRM keys (search google for that).
Now coming to your problem of unability to flash properly, make sure that you have installed all the drivers. For that open up /drivers folder in /flashtool and install the .exe there. Also install the adb drivers of your device. For that have PC Companion installed on your PC. Flashing will happen properly then.
Thanks,
Rick
Sent from my SK17i using XDA
Click to expand...
Click to collapse
You, and all developers/people here, are simply awesome!.... But this sh*t with unlocking bootloader and loosing warranty is so....stupid....I think i will give it a try and i am gonna sure thank you.... Somethink else....my phone has also a problem on the screen while scrolling....do you know if that is a hardware or a firmware problem?
What do i mean when i say scroll problem:
1st example: While browsing the Internet and scroll with fast moves, links are pressed on its own and new tabs are opened,as links are pressed.
2nd example: While i scroll the app drawer,fast s make apps open without my will....
3nd exapmle and the most representative: While playing fruit ninja and do fast moves to cut the fruits, the touchscreen doesn't even fell that i touch the screen!!! I do fast moves to cut the fruits and nothing happens!! As a result i always lose! (just joking....)
My phone is fast and really smooth only when my moves are slow....any thoughts about that? :/
Thanks once again for your BRAVE help!
You have a Mini, right? That's a hardware problem. Very common, even if not everyone realizes it. Check THIS thread for a (possible?) solution.
I have no idea what I'm doing so I thought following a step by step guide would help me...but apparently not.
I followed this guide because I wanted this ROM:
http://forum.xda-developers.com/showthread.php?t=1206625
BUT I used xRecovery from here (also I used this guide to get root access):
http://forum.xda-developers.com/showthread.php?t=1682966
I already had the baseband so I didn't do the optional step, but I did download the file after searching the topic for a live link (I wanted all the files I might need before starting so I could focus on the job).
My phone is now in an infinite loop of turning on, saying Sony Ericsson, then shutting down after a minute or so and retrying. I'm not sure what info to provide so I will just list off things I wrote down beforehand:
FIRMWARE: 2.1-UPDATE1
KERNEL: 2.6.29
BUILD: 2.1.1.A.0.6
SI: 1248-0835
I just wanted to let anyone who wants to help know I restored the backup through xRecovery...so it's like I never did anything....but I still really need to get rid of the OS I have and replace it with something clean, preferably what I tried the first time (first link).
next time post questions in X10 mini pro section, This is X10 section.
I dont know much about it but did you unlock your bootloader?
Thread Moved
Please take more care when opening a thread
THeLogiC said:
next time post questions in X10 mini pro section, This is X10 section.
I dont know much about it but did you unlock your bootloader?
Click to expand...
Click to collapse
I'm really sorry, I got lost by accident. I'm not used to this sort of forum .
I did not unlock a bootloader, I will go look at it now, thanks so much!
Alunny said:
I'm really sorry, I got lost by accident. I'm not used to this sort of forum .
I did not unlock a bootloader, I will go look at it now, thanks so much!
Click to expand...
Click to collapse
You don't need to unlock the bootloader becasue you're trying to install a modified stock-rom from SE, which will run on SonyEricsson's stock kernel with no problem.
I hope you did all the wipes in xRecovery?
wipe data/factory reset
wipe cache
Go into advanced menu
wipe dalvik-cache
wipe battery stats
Usually a bootloop on a rom that is proven to work is due to left-over junk in the cache or dalvik-cache. You can do these after you've installed the ROM.
Oh okay. I hadn't unlocked the bootloader and I was having trouble keeping my phone off and connected to my puter so thought I had better leave it for a day when I have time to focus on it. That was the part of rooting I was afraid of.
I did the first two cache but not the other two. Will try again in a few minutes and do those!
Same thing. Think I'm going to have to try the bootloader thing.
Alunny said:
Same thing. Think I'm going to have to try the bootloader thing.
Click to expand...
Click to collapse
If you want that particular ROM there is no need to unlock the bootloader.
It is more dangerous than just rooting your phone and only needed if you need a custom kernel, which you don't for this ROM.
If you have flashtool (you can get it from here if you don't have it)
Make sure USB-debugging is on on your phone
Start flashtool
Connect your phone to your computer
Root it using the ROOT button in flashtool (the button with the lock on it)
Install xRecovery using the button with the cross on it.
Use the menu to boot into xRecovery
Choose Install zip from sd-card (no need to rename the zip this way)
Choose zip from sd-card (it wil show you the content on your sd-card)
Choose your ROM's zip
Choose yes
After the install is done reboot your phone.
If it won't boot the zip-file you downloaded may be corrupted.
You can get back to your original firmware by using Sony Update Service or PC Companion, so your phone will work again.
I gave my XZU, which has an unlocked bootloader, is rooted, and is running 4.4.2 to my mother. I want to return the device to stock, as she has no need for root, and upgrade it to stock lollipop. The problem is, I rooted it a long time ago, I don't remember how I did it, and even then, I was stumbling through the process. There are many more guides about rooting than there are about unrooting, so I'm concerned that I may brick the phone or mess it up in some way. Here are the steps I found on XDA for returning to stock:
1. Make sure you have root
2. Backup any data/photos/etc on the phone
3. Restore your TA backup with the TA backup tool above
--------If you are on a custom kernel or ROM you ZU will not boot at this stage
4. Start flashtool and load a FTF
5. Start the flash and wait for the onscreen instructions to connect the ZU
6. Connect your ZU in flashmode
---------With the ZU powered off
---------Connect to PC while holding the volume down key
---------Flash will start
7. Wait for flash to complete
Is this the appropriate way to approach what I'm trying to do here? I am not running a custom kernel or ROM, I don't think. Certainly not a custom rom, though I'm not sure how kernels work anymore. But I'm pretty sure it's not custom. Just to be certain I am doing this properly, I want to write this out with the guide and see if it makes sense.
1. I do have root.
2. Done.
3. I have my TA partition saved as a .zip from when I originally rooted the phone. I'm not completely sure how I restore the partition. I am getting the Backup TA program from here: https://github.com/DevShaft/Backup-TA/releases. But I can't find actually how to restore it. After I do this, my bootloader is now relocked, and then I can just flash stock .ftf's? Is this correct?
4. I am downloading flashtool from here: http://www.flashtool.net/downloads.php and I am using this .ftf: [STOCK ROM] [FTF] Xperia Z Ultra (C6806) 14.3.A.0.681 "US Unbranded", which I am getting from here: http://forum.xda-developers.com/xpe...tf-depository-sony-firmware-releases-t2829387. I haven't used the flashtool since the original rooting I did, but I think I can figure it out.
5. Etc.
6. Etc.
7. Etc.
At this point, I should be back on stock, right? And then I could just update through Sony's PC Companion at this point, yes? I'm basically just looking for a "Yes, you're going in the right direction" or "Yes, this is how you would return the device to stock."
Thanks!
That is the most up to date instructions that I know of, sorry I can't answer about the TA restore. Just one suggestion would be to flash a lollipop ftf, rather than kitkat and trying to get it to upgrade. An even easier solution would be to leave it unlocked and flash this http://forum.xda-developers.com/xpe...llipop-5-0-2-c6806-14-5-0-242-rooted-t3082449 in recovery.
adfurgerson said:
That is the most up to date instructions that I know of, sorry I can't answer about the TA restore. Just one suggestion would be to flash a lollipop ftf, rather than kitkat and trying to get it to upgrade. An even easier solution would be to leave it unlocked and flash this http://forum.xda-developers.com/xpe...llipop-5-0-2-c6806-14-5-0-242-rooted-t3082449 in recovery.
Click to expand...
Click to collapse
I appreciate it. I think I'm going to try it now. I really want it on stock for any updates. It needs to stay as simple and as up-to-date as possible without as little effort as possible. Do you know where the stock lollipop .ftf's are?
Snarging said:
I appreciate it. I think I'm going to try it now. I really want it on stock for any updates. It needs to stay as simple and as up-to-date as possible without as little effort as possible. Do you know where the stock lollipop .ftf's are?
Click to expand...
Click to collapse
This tool might work.
http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
Hi All,
I am looking for a tutorial that explains how to root the cellphone build under 32.2.a.0.305 running with Marshmallow. I haven't found any topic that state someone succeeded to root this one. Any chance someone can give me some guidance. On some other website it is mentionned that we cannot root it for the moment. So I was thinking maybe downgrade it and go back to Lollipop? But even for that I need some guidance.
Thanks in advance.
Cheers.
francisci said:
Hi All,
I am looking for a tutorial that explains how to root the cellphone build under 32.2.a.0.305 running with Marshmallow. I haven't found any topic that state someone succeeded to root this one. Any chance someone can give me some guidance. On some other website it is mentionned that we cannot root it for the moment. So I was thinking maybe downgrade it and go back to Lollipop? But even for that I need some guidance.
Thanks in advance.
Cheers.
Click to expand...
Click to collapse
Theres a perfectly detailed guide in general section , you should downgrade to lolipop so you can use the temp root tool to back up drm keys before unlocking the bootloader , but if you dont care about drm keys , you can in fact just skip to the boorloader unlock part and root. Its so simple , but i would suggest going through the whole proccess and back up your drm keys cuz once lost , forever lost so ... Yah
madshark2009 said:
Theres a perfectly detailed guide in general section , you should downgrade to lolipop so you can use the temp root tool to back up drm keys before unlocking the bootloader , but if you dont care about drm keys , you can in fact just skip to the boorloader unlock part and root. Its so simple , but i would suggest going through the whole proccess and back up your drm keys cuz once lost , forever lost so ... Yah
Click to expand...
Click to collapse
Hi Madshark
Thanks for your prompt reply. Appreciate it.
I'm at rookie level in terms or rooting smartphone, so I don't know even the basics. Can you send me the link of the "detailed guide" and also explain me what does the "drm keys" stand for?
francisci said:
Hi Madshark
Thanks for your prompt reply. Appreciate it.
I'm at rookie level in terms or rooting smartphone, so I don't know even the basics. Can you send me the link of the "detailed guide" and also explain me what does the "drm keys" stand for?
Click to expand...
Click to collapse
this is the link to the post that I used and followed its instructions to root my phone personally.
http://forum.xda-developers.com/z5-compact/general/how-to-backup-restore-ta-partition-root-t3479532
if you lose DRM keys (and that happens when unlocking the bootloader) then some functions in the device will stop working like Bravia engine, Track ID, etc and on our z5 compact some say even stock camera stops from working, and when you lose those keys you can NEVER get them back because each device has its OWN TA partition that includes its OWN DRM keys and no other device has the same so thats why each and every one who owns an Xperia device must perform this TA backup in case they ever wanted to get back to stock (unroot and relock bootloader) they can restore these keys and functions to factory functionality. if you dont back them up and unlocked the boot loader then you will never get some functions to get back to working properly if you ever wanted to get back to stock and relock your boot loader!
However; there is some thing that is called DRM fix in certain roms that when you install these roms, you will not feel like you lost your functions because they already include a fix that behaves like the DRM keys.
still, losing your DRM keys will cause your device to lose its warranty and if you didnt back them up then you will never get it back even if you relocked your bootloader. so I personally backed them up because my device has a 2 year warranty and I dont want to waste them if any thing goes wrong I would restore them and send it to get fixed.
yet the only problem is warranty to me so if you have no warranty or dont care about it you can skip the back up process but yet again I dont like taking chances so just back them up its a 2 minute thing.
and I say again, all stock based roms in this Z5 compact forum have drm fix...
and to give you my personal opinion I dont like the Xperia z5 compact rooted because as I saw, there is so little roms and so little kernel variations and all the stable roms are based on stock MM firmware and CM roms arent fully stable yet , (they are but they have bugs that I hate having) and I only rooted so i can increase the volume of my phone speakers and headset and increase the strength of the torch but it all turns out to be that all sound mods have bugs and torch mod only work properly on any thing but STOCK ftf but any thing besides stock ftf isnt fully stable so I dont see any point in rooting this device I so regret buying it I should have checked how little the modifications are that can be made on it I owned Z2 and HTC devices in the past and boy! if I wanted to try different things every day for the past 2 years I wouldnt have finished by now there is sooo much to test and so much to try and to customize ...
the only rom that can be customized and can be enjoyed as much that we have is Kryptonian - the rom of awesomeness!
I hope I was helpful
madshark2009 said:
this is the link to the post that I used and followed its instructions to root my phone personally.
http://forum.xda-developers.com/z5-compact/general/how-to-backup-restore-ta-partition-root-t3479532
if you lose DRM keys (and that happens when unlocking the bootloader) then some functions in the device will stop working like Bravia engine, Track ID, etc and on our z5 compact some say even stock camera stops from working, and when you lose those keys you can NEVER get them back because each device has its OWN TA partition that includes its OWN DRM keys and no other device has the same so thats why each and every one who owns an Xperia device must perform this TA backup in case they ever wanted to get back to stock (unroot and relock bootloader) they can restore these keys and functions to factory functionality. if you dont back them up and unlocked the boot loader then you will never get some functions to get back to working properly if you ever wanted to get back to stock and relock your boot loader!
However; there is some thing that is called DRM fix in certain roms that when you install these roms, you will not feel like you lost your functions because they already include a fix that behaves like the DRM keys.
still, losing your DRM keys will cause your device to lose its warranty and if you didnt back them up then you will never get it back even if you relocked your bootloader. so I personally backed them up because my device has a 2 year warranty and I dont want to waste them if any thing goes wrong I would restore them and send it to get fixed.
yet the only problem is warranty to me so if you have no warranty or dont care about it you can skip the back up process but yet again I dont like taking chances so just back them up its a 2 minute thing.
and I say again, all stock based roms in this Z5 compact forum have drm fix...
and to give you my personal opinion I dont like the Xperia z5 compact rooted because as I saw, there is so little roms and so little kernel variations and all the stable roms are based on stock MM firmware and CM roms arent fully stable yet , (they are but they have bugs that I hate having) and I only rooted so i can increase the volume of my phone speakers and headset and increase the strength of the torch but it all turns out to be that all sound mods have bugs and torch mod only work properly on any thing but STOCK ftf but any thing besides stock ftf isnt fully stable so I dont see any point in rooting this device I so regret buying it I should have checked how little the modifications are that can be made on it I owned Z2 and HTC devices in the past and boy! if I wanted to try different things every day for the past 2 years I wouldnt have finished by now there is sooo much to test and so much to try and to customize ...
the only rom that can be customized and can be enjoyed as much that we have is Kryptonian - the rom of awesomeness!
I hope I was helpful
Click to expand...
Click to collapse
Very helpful ! Thanks v much - I'll let you know if I succeed!
Ok, 2 more things.
Probably the most important: warranty has nothing to do with DRM keys, unlocked bootloader or what more. Sony is not/never gonna repair smartphones when there're problems caused by custom ROM or kernel, they're not gonna fix a bootloop caused by a bad flashing procedure and so on. But it's not true that you're automatically losing warranty by unlocking bootloader or getting root access.
Next to that, you don't have to go through that process of backing up your own TA, if you don't want. It's much easier to root and flash a kernel with DRM keys patched. Procedure to root is really simple. Flash new rom, unlock bootloader, fastboot to flash compatible twrp , flash supersu, flash modded kernel, done. There're already quite some tutorials to guide you through this proces.
--jenana-- said:
Ok, 2 more things.
Probably the most important: warranty has nothing to do with DRM keys, unlocked bootloader or what more. Sony is not/never gonna repair smartphones when there're problems caused by custom ROM or kernel, they're not gonna fix a bootloop caused by a bad flashing procedure and so on. But it's not true that you're automatically losing warranty by unlocking bootloader or getting root access.
Next to that, you don't have to go through that process of backing up your own TA, if you don't want. It's much easier to root and flash a kernel with DRM keys patched. Procedure to root is really simple. Flash new rom, unlock bootloader, fastboot to flash compatible twrp , flash supersu, flash modded kernel, done. There're already quite some tutorials to guide you through this proces.
Click to expand...
Click to collapse
Yah well if the bootloader is unlocked and the system has modification on it , they have every right to refuse fixing it for you because its hard to prove that what bricked the device isnt some modification that you made... Unless they have a really good heart , i had a z2 before and it was rooted but the ftf on it was custom but was on it for like 7 months and all the mods were working properly untill all of the sudden it wont turn on so they told me that what i.did caused it but i didnt do anything wrong i know they lying but can u prove it!? No..
Hi guys,
How do I flash the boot.img using cmd and fastboot ?
francisci said:
Hi guys,
How do I flash the boot.img using cmd and fastboot ?
Click to expand...
Click to collapse
first you gotta download ADB folder
you can find it here if im not wrong : http://forum.xda-developers.com/showthread.php?t=2588979
then place the adb folder in C:\
I think it automatically place it there when installing so no need to do that if so
2. go to cmd (start - type in CMD) and once it launches direct it to where the adb folder is "cd c:\adb" without the quotes of course
3. to flash boot type in "fastboot flash boot boot.img" without quotes and one space step between words only.
4. to flash recovert just type is "fastboot flash recovery "recovery name".img wihtout the quotes and copy recovery name exactly the way it is.
that it
keep in mind that any time you want to flash any thing , that thing must be inside the adb folder for example ,boot.img file must be there in the adb folder with all the other files when installing adb, and also recovery and every other thing you want to flash using fastboot.
hope this is helpful.
Hi madshark, thanks again for your help. I have been able to flash the boot img and then rename twrp into recovery and flash it as well.
Now I'm stuck the device cannot reboot so I cannot transfert the SuperSU files in to the device...
And when I type adb devices in cmd, it do not mention the device ! Seems that I'm facing an issue.
francisci said:
Hi madshark, thanks again for your help. I have been able to flash the boot img and then rename twrp into recovery and flash it as well.
Now I'm stuck the device cannot reboot so I cannot transfert the SuperSU files in to the device...
And when I type adb devices in cmd, it do not mention the device ! Seems that I'm facing an issue.
Click to expand...
Click to collapse
well youre new, mistakes like these happen Ive been there, sorry for the late reply XDA isnt giving me notification
any way, make sure after backup TA (which is on lolipop firmware) you gotta get back to original .305 firmware (MM) the process of you getting back to lolipop in the first place is so you can use Ivoyroot tool for temporary root so you can backup your TA partition, once that is done you must get back to .305 because you are flashing a kernel (boot.img) that is for build .305 I guess the guide guy didnt mention this?
second when I said copy recovery name as it is I meant what recovery name you have for example
fastboot flash recovery twrp-3.0.2-0-E5823-20160417.img
thats my recovery name the one that I downloaded, yours might say some thing else its OK I meant copy YOUR recovery name to CMD the way it is exactly in the ADB folder
and now your stuck, if your bootloader is already unlocked, just flash .305 firmware with flashtool the same way you flashed the lolipop firmware, once that is done, do the first boot settings and once device is launched into the software , just flash boot again
make sure you follow instructions to the POINT, so you gotta turn of your phone, press the volume up button keep it pressed while connecting your phone to the PC and flash boot and recovery and thats it
and after youre done with this process , then you turn on your phone connect it to your PC and place the superSU zip file in it and then go to recovery and flash it
adb isnt recognizing your device?
thats weird if you just connect your device nothing will happen, so you turn off your phone and press the volume up button and connect it, (thats how you enter fastboot mode) and if still doesnt recognize then do what I told you to do already and see what happens next
keep me updated and if its urgent just send me a PM because I dont see notification otherwise...
Thanks Madshark for your help, it has finally worked!
Hello everyone.
This is my first post here - in hope to get help with my Sony Z5 Compact.
So a week ago I have updated to Nougat,by mistake tbh.
Unfortunately Im really not happy with the device. The volume is OK unless youd like to watch some videos on a website - you won't hear much.
Then, playing a matroska file is impossible - stutters, pauses, gives you 5 fps ( I'm not joking) - it was flawless on MM (305).
So my plan is to go back to MM and I believe I've read every step by step tutorial existing on the Internet but I still have some questions.
1. How do I backup firmware? Every tutorial says about a folder with firmware files that you can import to flashtool to make an ftf backup of your stock firmware. The folder does not exist on my PC.
I've tried "repairing" etc, still, it does not exist.
2. Why do I need a backup firmware ftf for warranty?
3. Where can I find an ftf file?
Xperifirm doesn't give me anything, there are lots of fake websites, xperiablog doesn't send me an approval email for my account.
4. Is there anyone in Lodz, Poland that could help me?
I'd love to downgrade.. The phone is unusable for my work and I can't afford a new one.
Thanks in advance.
Kindest regards.
Michelangelo
Suggest you download Customized SG firmware, the lastest marshmellow is still available for download. Grab it now.
Hello, welcome to xda.
First, please do not open 2 different threads for the same problem - it's against forum rules.
About your problem: which fw you are on? you could try newest nougat firmware .33 first because the problems you described should've been fixed in this. Also you could dirty flash it and won't lose anything.
However if you want to go back to MM anyway, i would recommend 5.11 fw because it's .305 with newer security patch.
Be aware, that if you go back to MM, you will have to make a clean flash.
You can find all 3 firmwares on xperifirm from different regions(also .305). For most regions there are two different available, so click through all firmwares and look on the right side which you can choose.
What do you mean xperifirm gave you nothing?
How to download via xperifirm, create a ftf and flash viaflashtool: https://forum.xda-developers.com/z5...-33-pushed-t3581352/post71662820#post71662820
yup every update sony become worse
the best one was the last 5.1.1 i think (or one b4)
the last 6MM was meh
the last nougat (.33) is far worse from all of them
probably i won't buy sony's anymore
( i was happy with my WT19 sony ericsson arc like(Legacy Xperia) the one of the reasons i bought this sony(also easy roms flash,you just need use flash tool for stock roms you dont even need root or BTunlocked)
anyway i'm usually replace my phone every 5 years in average (when the phone stop run smooth mid-low range .like waze, temple run 2,subway surfer. apps (z5 still mid-high)
so the phones got about 4 more years, at least how i see it.
As Gewiz suggested, if you're on .376 or .378 version of the Nougat firmware, then updating to 2.33 might just fix the problems you're describing.
This is the highly recommended solution, since you won't lose any of your data or settings, and you don't really have to do anything, just wait for the update to become available for your region via OTA or Xperia Companion.
If you insist on downgrading back to MM, then you must perform a clean flash using unofficial (non-Sony) tools, which means you will lose all of your data and settings. Therefore you should backup all your data before doing so.
Being on anything but the latest version means you will forever have a non-dismissible notification nagging you about upgrading to the newest version.
If you're fine with that, then download a MM ROM from XperiFirm, create a FTF from the bundle, then flash it to your phone using Flashtool.
I think you're confused by the numerous tutorials you've read about "backups" and "warranty". You've likely read guides teaching you how to root your phone, which involves making a backup of the TA partition of your phone to preserve the DRM keys that resides within. Rooting the Z5C requires unlocking the bootloader, a process that wipes the DRM keys and voids your warranty. So, guides are there to help people make a backup of the DRM keys, so that they will have the ability to restore the keys to the phone and return the phone to warranty-eligible state when they need warranty service or resell their phone.
Since you have made no mention of rooting your phone, I assume none of this matters to you, don't worry about it.
Thank you all for the replies.
I updated from 376 to 2.33 and the phone is even more pathetic. It's slow and sluggish even with stamina mode off and data transfer/WiFi off. The battery drain is even bigger, now the alarm volume is terrible ( although video volume in chrome browser is now better). Mind you, I always do a reset after updating the phone, so everything that could be done was done.
I'm after 305 since the 5.11 introduced heating an worse performance ( I don't believe it was just a security patch).
I've managed to download 305 firmware with Xperifirm but I've hit one obstacle - I cannot create an FTF file with flashtool as the Xperifirm download unpacks the " FILE" files to many separate files and folders after download.
Could anyone please tell me how should I go about it? I'm really desperate to downgrade this phone as it was perfect until the cursed update and I can afford a new one.
Thanks in advance, and again thanks for all the replies.
MichelangeloJan said:
Thank you all for the replies.
I cannot create an FTF file with flashtool as the Xperifirm download unpacks the " FILE" files to many separate files and folders after download.
Click to expand...
Click to collapse
First: for nougat (7.0) you need flashtool in version v0.9.23.2
version 0.9.23.1 _cannot_ create ftfs out of what you downloaded with xperifirm
Second: here's a tutorial for FTFs:
http://www.xperiablog.net/2014/08/1...re-files-using-xperifirm-and-flashtool-guide/
Please note: in flashtool, you just have to click "Bundles\Create" (you don't need to decrypt, as this is done by xperifirm already)
Ok, guys I have one last question regarding this topic. Im sorry this took me so long but I don't have the Internet connection at home.
The "how to create an FTF file" tutorial says " exclude . Ta files" although the screen from it show only 2 files being excluded.
Some other tutorials either say the same or don't mention the .ta files.
So should I exclude all of them? Or should I leave "simlock. Ta" and "booter" in there?
Thanks again.
Michelangelo
Reflash firmware or make a factory reset. I am on .33 Nougat and rooted. Don't have any issues. Only have Greenify and battery life is good, performance is very good.
I also have flashed Zach's kernel, it makes a difference. However, these issues you have are not from this. Some people have reported such issues when upgrading from MM. If you don't want to unlock bootloader and root, make a factory reset or flash a whole .33 FTF in Flashtool. Also no, I haven't had these issues on .376 either.
I hope one of my tips helps you
---------- Post added at 01:15 AM ---------- Previous post was at 01:12 AM ----------
MichelangeloJan said:
Ok, guys I have one last question regarding this topic. Im sorry this took me so long but I don't have the Internet connection at home.
The "how to create an FTF file" tutorial says " exclude . Ta files" although the screen from it show only 2 files being excluded.
Some other tutorials either say the same or don't mention the .ta files.
So should I exclude all of them? Or should I leave "simlock. Ta" and "booter" in there?
Thanks again.
Michelangelo
Click to expand...
Click to collapse
Don't exclude anything, leave it as is
If you ask me, make a backup of all the stuff of your Internal Storage and wipe Userdata as well (unlocking the bootloader also does this, if you decide to do so).