Some general information please :) - Sony Xperia P, U, Sola, Go

Hello all,
I've just gotten an Xperia S and my previous phone was the X8. As some of you might know that the X8 is very outdated and it doesn't have all these new cool features, when I first came into this forum I do not understand a single thing
So I would like to ask a few questions that has arose when I looked through the Android Development forum. Namely:
1. What is sytem.img? Is it a ROM, firmware or what ? I know this also applies to Xperia 2011 models, but I do not own them.
2. What is the bootloader issue that everyone has been raging about? And is it true that DooMLord has fixed it in his kernel?
3. What is firmware and I heard there is SG generic Italy generic etc... In X8 I think the firmware changes with each ROM but on this phone it doesn't seem so. Why would you want to flash stock firmware when you can flash custom ROMs?
4. Can Xperia S bootloader be unlocked by test point, so that DRM keys are not damaged?
5. How to root this phone? I know no one has found an exploit yet, but I read on DooMLord's thread that his kernel auto-roots the phone, and that we can flash prerooted system.img(what the heck is that) and flash a pre-rooted image(what. All this is really confusing and I really hope I can get help on this!!
6. Just checking, kernel can be boot.img, kernel.sin and kernel.elf right?
7. This is a list of terms I came across so far and I need some explaination on them.
-system.img
-firmware(just to clarify, because I thought I knew it until I read DooMLord's thread.
-fastboot drivers and fastboot binaries.
Yep I guess that's all. I do hope someone will take the time to answer these question. I'm sorry for being such a noob, but hey, everyone's got to start somewhere right? I'll be sure to thank you if you've helped me!

Every single question has been answered at least once, if not 20 times. When you use search you actually have to read too.
XperienceX8 said:
flash prerooted system.img(what the heck is that) and flash a pre-rooted image(what. All this is really confusing and I really hope I can get help on this!!
Click to expand...
Click to collapse
rooted - to have root access.
pre - before, earlier, first
Work it out

I guess that's reasonable but I searched in the forums. The replies were quite vague, or maybe jut too complicated and I couldn't understand. Hoping someone would like really explain what each feature does. Btw I've search for system.img everywhere yet could not find the answer

just go to the development section!!!!

XperienceX8 said:
Hello all,
I've just gotten an Xperia S and my previous phone was the X8. As some of you might know that the X8 is very outdated and it doesn't have all these new cool features, when I first came into this forum I do not understand a single thing
So I would like to ask a few questions that has arose when I looked through the Android Development forum. Namely:
1. What is sytem.img? Is it a ROM, firmware or what ? I know this also applies to Xperia 2011 models, but I do not own them.
2. What is the bootloader issue that everyone has been raging about? And is it true that DooMLord has fixed it in his kernel?
3. What is firmware and I heard there is SG generic Italy generic etc... In X8 I think the firmware changes with each ROM but on this phone it doesn't seem so. Why would you want to flash stock firmware when you can flash custom ROMs?
4. Can Xperia S bootloader be unlocked by test point, so that DRM keys are not damaged?
5. How to root this phone? I know no one has found an exploit yet, but I read on DooMLord's thread that his kernel auto-roots the phone, and that we can flash prerooted system.img(what the heck is that) and flash a pre-rooted image(what. All this is really confusing and I really hope I can get help on this!!
6. Just checking, kernel can be boot.img, kernel.sin and kernel.elf right?
7. This is a list of terms I came across so far and I need some explaination on them.
-system.img
-firmware(just to clarify, because I thought I knew it until I read DooMLord's thread.
-fastboot drivers and fastboot binaries.
Yep I guess that's all. I do hope someone will take the time to answer these question. I'm sorry for being such a noob, but hey, everyone's got to start somewhere right? I'll be sure to thank you if you've helped me!
Click to expand...
Click to collapse
1. It is an archive with all files on /system that can be flashed via fastboot.
2. This is fixed, but the fix itself is not public.
3. Stock firmwares appeared before custom ROMs and there are still only two custom ROMs that don't change much. So the stock firmware is good for average use if you don't want themes or something. There are different firmwares for different countries and carriers, customized with some local apps and/or bloatware.
4. No one tried it yet AFAIK, but DRM keys haven't been found useful.
5. You need to unlock bootloader and flash a prerooted image or DooMKernel. As I said before, system.IMG is an archive with all system files. Superuser app and su binary are added to prerooted images so that you can flash them and have instant root. DooMKernel also has these built in and it roots the device automatically on boot, so you can use it with any firmware. You can roll back to stock kernel and root will stick until you fully reflash your device.
6. The filename can be anything, what's important is what's inside.
7. Firmware is a set of files that are preinstalled on your phone. It includes Android, some media and applications.
Fastboot is a low level tool for flashing ROMs. The binary is fastboot.exe itself (fastboot ELF if you use *nix). The drivers are Windows specific files you need to make the OS recognize your device in fastboot mode.
Sent from my LT26i using XDA

Related

Strange problem with flashing kernel

I would like to ask for some ideas what could possibly cause my problem with flashing one particular kernel.
Here`s my starting point:
1. I know what I`m doing, I`m comfortable with flashing custom kernels & roms, that means my bootloader is unlocked etc... /talking about U20i/
2. I` ve done extensive search on this forum and elsewhere
3. I went through SEUS update
4. I`ve got latest flashtool, but tried also older versions, tried on various PCs
5. There`s only this one .ftf in the firmware folder
5. I` ve got the right kernel file, triple-checked that, re-re-downloaded, md5
matches, nobody else reported this problem
When I try to flash it with flashtool, it gives me this error line:
ERR_SEVERITY="MAJOR";ERR_CLASS="MEMORY_CLASS";ERR_STATIC="HASH_VER";ERR_DYNAMIC="Failed to init erase"
After that, I can flash ANY other kernel w/o problems.
Questions:
1. Is there anybody with the same problem?
Talking about this: http://www.mediafire.com/?ish1obpr8mtxdh6 , but you could possibly have the problem with other kernels too
2. Is there a possibility that my boot partition is somehow corrupted?
3. Is there a way to check for that and make some repair?
4. Am I loosing my mind? /I am, no need to answer to this,
thank you /
i also had this problem on my X8 when flash kernel Alfs CM8, but when i tried Kernel nAa, it is succes
drfr said:
I would like to ask for some ideas what could possibly cause my problem with flashing one particular kernel.
Here`s my starting point:
1. I know what I`m doing, I`m comfortable with flashing custom kernels & roms, that means my bootloader is unlocked etc... /talking about U20i/
2. I` ve done extensive search on this forum and elsewhere
3. I went through SEUS update
4. I`ve got latest flashtool, but tried also older versions, tried on various PCs
5. There`s only this one .ftf in the firmware folder
5. I` ve got the right kernel file, triple-checked that, re-re-downloaded, md5
matches, nobody else reported this problem
When I try to flash it with flashtool, it gives me this error line:
ERR_SEVERITY="MAJOR";ERR_CLASS="MEMORY_CLASS";ERR_STATIC="HASH_VER";ERR_DYNAMIC="Failed to init erase"
After that, I can flash ANY other kernel w/o problems.
Questions:
1. Is there anybody with the same problem?
Talking about this: http://www.mediafire.com/?ish1obpr8mtxdh6 , but you could possibly have the problem with other kernels too
2. Is there a possibility that my boot partition is somehow corrupted?
3. Is there a way to check for that and make some repair?
4. Am I loosing my mind? /I am, no need to answer to this,
thank you /
Click to expand...
Click to collapse
I guess u want an ISC kernel (nAa kernel) for an nAa's MiniCM9...
try this buddy
Naa released an new version of his ics kernel. Take a look to this site
http://forum.xda-developers.com/showthread.php?t=1636504
This iss U20_naa_ics_02
I hope my post helped you good luck
Thank you all. I'm using nAa's ics kernel and miniCM9 since the day it was released for our devices, so the above problem doesn't really matter no more. But the question remains - how such thing as described could possibly happen at all, when everybody else had no such problem with the same kernel and I am dead sure I had the right one and did everything I should. Well, **** happens and it's not always possible to explain why, obviously.
Sent from my U20i using xda premium
drfr said:
Thank you all. I'm using nAa's ics kernel and miniCM9 since the day it was released for our devices, so the above problem doesn't really matter no more. But the question remains - how such thing as described could possibly happen at all, when everybody else had no such problem with the same kernel and I am dead sure I had the right one and did everything I should. Well, **** happens and it's not always possible to explain why, obviously.
Sent from my U20i using xda premium
Click to expand...
Click to collapse
Seriously? Since the day it was released for your phone.. While you could not flash the kernel? Why didn't you say it had worked or something like that and close this thread as solved?
SmG67 said:
Seriously? Since the day it was released for your phone.. While you could not flash the kernel? Why didn't you say it had worked or something like that and close this thread as solved?
Click to expand...
Click to collapse
I can see I'm being misunderstood. The problem I described doesn't get solved if I flash OTHER kernel. The question remains the same: how could that thing happen at all? OK, I don't need that kernel mentioned in OP anymore, but still I hoped I could hear from people whether they hadn't experienced such things with other kernels and what could be possible solution. This would be useful if somedy in the future will search forums for help, don't you think?
Sent from my U20i using xda premium
Ah, you managed to flash the ICS2 kernel instead of ICS1, is that right?
I guess sometimes things fail for some reason, it seems this was a random bug that not many people experienced.
Have fun anyway with your new Rom, glad it worked out in the end.
SmG67 said:
Ah, you managed to flash the ICS2 kernel instead of ICS1, is that right?
I guess sometimes things fail for some reason, it seems this was a random bug that not many people experienced.
Have fun anyway with your new Rom, glad it worked out in the end.
Click to expand...
Click to collapse
As you say, for some reason - I hoped somebody could try to explain the nature of the actual reason. As nobody did, we can conclude it was, as you say, a random bug and close this thread, OK.

[Q] Help needed for a newbie

Hi all,
Sorry if this is the wrong section and has possibly been covered many times before but I am new to this Android stuff and wanted instant answers due to not understanding things covered in posts and threads on the forum.
The phone:
I have a Sony Xperia x10i which was previously on Orange but has now been unlocked. It had Gingerbread 2.3 before but now has been what I assume is "debranded" and is now 2.1 (I dont know what)
The Problem:
I have tried to update via SonyPC companion where it shows "update avaliable" as I go to proceed it fails after clicking the next button (which sometimes comes up hidden in the dialog box)
I want to update the android market app to GooglePlay but due to being stuck on 2.1 it wont allow it unless 2.2 upwards.
Using Google - i typed in the build number which seems to throw back that it is a Greek rom of some kind?
Final note:
I want to keep my phone up to date without destroying the software or installing custom roms, basically keeping it original and simple. I want the latest firmwares etc so that it is all up to date. Also I would like to keep it unlocked without having to shell out to get it unlock again after it has been done once.
Hope someone can help me out. I can answer questions if more info needed.
Many thanks in advance.
(UK using o2 SIM)
I dont know 100% on what to do because im certainly no professional, but in the system phone menu at the bottom does it definatly show Android 2.1?
It says firmware 2.1 -update1 if that means anything?
It needs to mod the build.prop file to set device as global generic one and update with PC companion.
But it requires root first.
Evenit is very strange, almost all of the x10i got 2.3.3 fw.
Or second solution - download 2.3.3 stock fw and flash it via flashtool
Thanks for the reply.
Can you explain a bit better as I dont understand sorry.
Did you mean I have to modify the build somehow?
I thought about the new rom solution but not sure if my device network unlock would still be there after installing new roms. Can someone point me to a simple guide on installing a new rom etc.
tarmac animal said:
Thanks for the reply.
Can you explain a bit better as I dont understand sorry.
Did you mean I have to modify the build somehow?
I thought about the new rom solution but not sure if my device network unlock would still be there after installing new roms. Can someone point me to a simple guide on installing a new rom etc.
Click to expand...
Click to collapse
You must be sure if what you want first
If you want to install a custom ROM, you will only need to root your device,install recovery and flash whatever ROM you want.
Or you can flash the stock 2.3.3 with Flashtool (thing thats the easiest solution for you) update and decide for custom roms later.
You have X10i rignt? Not X10a yes?
After you will decide what you want will provide further information.
HeliumX10 said:
Or you can flash the stock 2.3.3 with Flashtool (thing thats the easiest solution for you) update and decide for custom roms later.
Click to expand...
Click to collapse
I think I will go with this option first and try the roms later when i have more understanding on what i am doing
Definately x10i. (what is the difference between the "i" and "a" by the way for interest)
I think i have tried rooting by using superoneclick and it is rooted (any way to double check?)
I appreciate your help a lot with all this..
tarmac animal said:
I think I will go with this option first and try the roms later when i have more understanding on what i am doing
Definately x10i. (what is the difference between the "i" and "a" by the way for interest)
Click to expand...
Click to collapse
The X10i is version for europe and parts of asia and so on. X10a is mainly from USA and Canada (other GSM module). Also exists SO-01B which is a Japanese version of X10i.
tarmac animal said:
I think i have tried rooting by using superoneclick and it is rooted (any way to double check?)
Click to expand...
Click to collapse
Yes on google play exists app called Root check However it is not so important because we dont need a root at this time.
tarmac animal said:
I appreciate your help a lot with all this..
Click to expand...
Click to collapse
Everytime someone helps you, hit the "Thanks"button below his post, it will give him more good feelings Its a good habit everywhere here on XDA.
So here we go:
1.) Download the Flashtool form here:
http://androxyde.github.com/Flashtool/
2.) Donwload the generic SE WWE 2.3.3 ROM (here from my older post):
http://forum.xda-developers.com/showpost.php?p=26141346&postcount=13
3.) Once complete - extract the file.ftf form ROM archive and place it in Flashtool directory called "firmwares"
4.) Run Flashtool, select Flash, choose Flash Mode (not fastboot) and then follow the onscreen steps
5.) Hint - maybe you will have problems to get your device into the Flash mode, see my post here:
http://forum.xda-developers.com/showpost.php?p=26135308&postcount=4
Enjoy!
Smashing! I will definately give this a go next week as going away so dont want to screw the phone up before go lol. Will report back when Ive cracked it.

[Q] Newbie : Using custom roms, unlock bl etc.

Hello guys
I want to use certain custom roms and upgrade from my 2.1 ....
I kept reading 10-15 threads but I'm still a bit confused so just in case, i'll ask just to be sure and avoid bricking it.
So, here's the info of my phone :
1. Xpeia X10 Mini Pro U20i
2. Manufacture Date : 10W35
3. Base Band Version : M76XX-TSNCJOLYM-53404006
4. Kernel Verion : 2.6.29
5. Firmware Version 2.1
Now, I posted everything ...
Few questions:
1. Is there a chance of briking it ?
2. In order to install custom ROMS, I need to unlock the bootloader first?
Now ....
I do read the threads fully, but being a noob coming to this .. (not stupid thouh ) .. it's a bit confusing but I will manage to do it .. just need some starting points.
So, anything I should do before flashing the ROM , please enumerate here.
Thanks
maxijuni0r said:
Hello guys
I want to use certain custom roms and upgrade from my 2.1 ....
..
Thanks
Click to expand...
Click to collapse
First of all, you need to update your firmware, the baseband needs to read 4015 on the end before you install any roms.
Second: There are ROMS that will run fine on your current kernel, so if you choose one of those, there is no need to unlock the bootloader.
If you want to run a ROM that states it needs a custom (usually nAa) kernel, then you do need to unlock your bootloader, otherwise you can't flash the new kernel.
With the 10w35 datestamp you won't get a hard brick with unlocking, but it may still go wrong, depending on some other factors, namely your simlock-certificate.
I would recommend to start with a rom that runs on stock kernel, to get some experience, and do the other things once you feel more comfortable
SmG67 said:
First of all, you need to update your firmware, the baseband needs to read 4015 on the end before you install any roms.
Second: There are ROMS that will run fine on your current kernel, so if you choose one of those, there is no need to unlock the bootloader.
If you want to run a ROM that states it needs a custom (usually nAa) kernel, then you do need to unlock your bootloader, otherwise you can't flash the new kernel.
With the 10w35 datestamp you won't get a hard brick with unlocking, but it may still go wrong, depending on some other factors, namely your simlock-certificate.
I would recommend to start with a rom that runs on stock kernel, to get some experience, and do the other things once you feel more comfortable
Click to expand...
Click to collapse
Thanks man ...
This is exactly the info I needed ... I will start with a stock one, need to find now how to update my firmware.
By the way, is there a way of getting adobe flash ...after update ? If so, is there any ROM you suggest in that matter ?
maxijuni0r said:
Thanks man ...
This is exactly the info I needed ... I will start with a stock one, need to find now how to update my firmware.
By the way, is there a way of getting adobe flash ...after update ? If so, is there any ROM you suggest in that matter ?
Click to expand...
Click to collapse
If I remember correctly Android supported flash since 2.2 frozen yogurt, so any custom roms could run it, you'll just have to find the flashplayer for armv6, there should be a link somewhere on this forum. Try the Mini Themes and Apps section
Never be afraid of flashing. Because you can always recover it. the only tough thing is unlocking the BL. read carefully and pay attention. Goodluck.
PS if you HARD BRICK your phone because you fail to unlock the BL it can still be repaired via JTAG.
zenesis said:
Never be afraid of flashing. Because you can always recover it. the only tough thing is unlocking the BL. read carefully and pay attention. Goodluck.
PS if you HARD BRICK your phone because you fail to unlock the BL it can still be repaired via JTAG.
Click to expand...
Click to collapse
Thanks man for the warnings .
I kept reading for two days now I'm ready to do it ....
Wish me luck.

[Q] Need some info about flashing kernel - locked/unlocked bootloader.

Hey guys,
First of i'm not sure if this is a appropriate thread to ask this, if not i'm sorry and will move/remove it.
Anyways it's been awhile since i've been in the android scene and xda in general, had an iphone for about a year or two and just recently got my Z2:victory: so i'm back but things changed a little and i need a little info if anyone can help,
Basically i'm looking to flash [Xperia Z2] DooMKernel v09 kernel but i read it requires an unlocked bootloader... so basically i need to know if my bootloaders unlocked now that i flashed recovery (check signature) (Does flashing recovery unlock a bootloader?) and can i just flash the zip?
or do i need to still unlock my bootloader even though i have dual recovery and then flash the kernel?
Your bootloader is still locked, what you did is you installed recovery for locked bootloader.
Do not try to flash custom kernel on locked bootloader, you'll soft brick your phone.
What you need in order to flash custom kernel is to unlock bootloader, but firstly you need to back up your TA keys ( click here )
For more info click HERE (about unlocking)
Proceed carefully!
Regards!
hey thanks for the info, that' clears up everything, I did already backup my TA partition so I guess all I need to do is unlock bootloader then flash the kernel! quick question have you flashed your kernel? I know I read the info an features of it but is there any upside to it on a z2? my device is pretty fast an stable as is, just looking for a reason to flash mine, any further advice you can give me? is it worth it?
Zeyn Karim said:
hey thanks for the info, that' clears up everything, I did already backup my TA partition so I guess all I need to do is unlock bootloader then flash the kernel! quick question have you flashed your kernel? I know I read the info an features of it but is there any upside to it on a z2? my device is pretty fast an stable as is, just looking for a reason to flash mine, any further advice you can give me? is it worth it?
Click to expand...
Click to collapse
Well to be honest, I haven't, I didn't find any reason to do so, the stock is doing good for me at the moment.
As for the side affects, or as you say upside downs, there is no any, not at least that I'm aware of, but as far as I saw it's not compatible with every rom, only with stock as with stock based ones, I mean developer does not guarantee for it's stability if it's being used along with any other rom. I have rooted and flashed recoveries only to use existenz rom. I heard for Doomlord's kernel, that it has "fix" for a video recorder mic, you can control it's sensitivity and it's far more battery friendly.
Ah I see! thanks, think I'll stick with the stock kernel for the time being, I don't have any complaints at the moment with it but if I ever do decide to switch to the doom kernel atleast I know what to do first, I've got one last question though sorry, do I need to unlock my bootloader to flash a custom rom? I don't think I do, I'm pretty sure I don't, but just want to make sure, used to have only low end droid devices back in the day when I used to be here, didn't have things like dual recoveries etc so yeah I'm kind of reading an learning as I'm going along, pretty awesome device though sleek and powerful I've only been doing minor adjustments to the stock rom using xposed modules, haven't used a custom rom as yet but I will soon...
Zeyn Karim said:
Ah I see! thanks, think I'll stick with the stock kernel for the time being, I don't have any complaints at the moment with it but if I ever do decide to switch to the doom kernel atleast I know what to do first, I've got one last question though sorry, do I need to unlock my bootloader to flash a custom rom? I don't think I do, I'm pretty sure I don't, but just want to make sure, used to have only low end droid devices back in the day when I used to be here, didn't have things like dual recoveries etc so yeah I'm kind of reading an learning as I'm going along, pretty awesome device though sleek and powerful I've only been doing minor adjustments to the stock rom using xposed modules, haven't used a custom rom as yet but I will soon...
Click to expand...
Click to collapse
Well, yes and no, LB means its for locked bootloaders and UB means for unlocked bootloaders, search for those to two words when you find the rom which you can flash.
Some roms require unlocking, some do not. All stock based roms usually dont require, but as I told you, it will be stated in Rom's thread name or in OP.
Regards!
Ah! I'll be sure to look out for those, thanks for the valuable info, think that's all I needed to find out. I should be ok from here on out

Trying to root SGP521 from 6.0.1

Hi, I've been going through threads in here for the last 3 months trying to figure out a way to root this thing. A lot of the threads are pretty old so I have a couple of questions about how I should proceed.
Is it still the case that the firmware needs downgraded to 4.4.2 in order to root? I have the 4.4.2 ftf file but was having some issues with flashtool (the latest version 'Emma' wouldn't open on my PC).
Is flashtool the best method? I've seen threads mentioning easyroot being the best tool but haven't looked into it yet.
KingRoot doesn't work on this tablet version. I was almost going to buy OneClick Root yesterday I was getting so frustrated because I keep hitting a dead end with this.
Great forum by the way, i'm learning a lot from reading the threads, even if I'm not having success with my device!
Same Here Ive been looking at threads and still cant find away to root my sony xperia z2 tablet the only thing ive seen is something called one click root but i dont know if it wokrs or not if your willing to test it out and it works please message me
lionelglitchie said:
Hi, I've been going through threads in here for the last 3 months trying to figure out a way to root this thing. A lot of the threads are pretty old so I have a couple of questions about how I should proceed.
Is it still the case that the firmware needs downgraded to 4.4.2 in order to root? I have the 4.4.2 ftf file but was having some issues with flashtool (the latest version 'Emma' wouldn't open on my PC).
Is flashtool the best method? I've seen threads mentioning easyroot being the best tool but haven't looked into it yet.
KingRoot doesn't work on this tablet version. I was almost going to buy OneClick Root yesterday I was getting so frustrated because I keep hitting a dead end with this.
Great forum by the way, i'm learning a lot from reading the threads, even if I'm not having success with my device!
Click to expand...
Click to collapse
Just wait a little bit , here is a thread about easy rooting latest firmware http://forum.xda-developers.com/z3/general/recovery-root-mm-575-291-lb-t3435214
And it will be available to root Z2 Tablet also, just read whole thread and dont forget to hit thanks for @shoey63
It's not the damn stock firmware idea is it? That's a workaround by definition
Dadovvv said:
Just wait a little bit , here is a thread about easy rooting latest firmware http://forum.xda-developers.com/z3/general/recovery-root-mm-575-291-lb-t3435214
And it will be available to root Z2 Tablet also, just read whole thread and dont forget to hit thanks for @shoey63
Click to expand...
Click to collapse
Thanks for pointing it out,
I've just rooted my SGP551 Z2 Tablet!
If someone is interested, post kernel.sin (23.5.A.0.575 or another previous MM kernel) I can add into his script like I did
Cheers!
Dadovvv said:
Just wait a little bit , here is a thread about easy rooting latest firmware http://forum.xda-developers.com/z3/general/recovery-root-mm-575-291-lb-t3435214
And it will be available to root Z2 Tablet also, just read whole thread and dont forget to hit thanks for @shoey63
Click to expand...
Click to collapse
Thanks, i'm going to try this just now with easyroot. Only thing i'm concerned about is my build number is 23.5.A.0.570, I don't know if this matters.
Still struggling with this, wasted another few days with the continuing problems with flashtool. I downloaded shoey's zip's and renamed them .ftf. But the main problem is Flashtool doesn't detect any ftf's on my computer.
Ok so the ftf should be downloaded with Xperiafrim inculded with flashtool
the ftf should be in the .flashtool folder in your c drive
just renaming it will not work
You should be able to root now with out downgrade check the general section
then it's just a matter of sideload with adb the recovery you need then your home free
Thanks, I had a look at Xperiafirm. All it lets me do is download the latest .291 firmware which is on my device anyway. I know I must be missing something very simple.

Categories

Resources