Database Develop

major differences between Z1 and Nexus devices

Hi,
I have a good understanding of Nexus devices and I always used Cyanogenmod.
I'm keen in the differences between Nexus and Xperia devices.
To install CM on a nexus device is extremely straight forward
- unlock the bootloader (fastboot oem unlock) - will wipe userdata
- install TWRP (or CWM): fastboot flash recovery openrecovery-bla
- upload a CM update zip
- optionally encrypt the device / relock the bootloader
Although many say otherwise, a custom kernel will always boot fine with a locked bootloader on a nexus device. With a locked bootloader you're unable to flash a different recovery but if you lock the bootloader *after* having a custom kernel and custom recovery, everything is fine.
If you need to flash another recovery you need an unlocked bootloader.
- The last step - bringing everything back to factory defaults:
- unlock bootloader (fastboot oem unlock)
- flash a google factory image (fastboot also)
- lock bootloader (fastboot oem lock)
The device is now in the "brand new - factory state".
I've read about Xperia devices and my current understanding of the process is:
- use an exploit to gain root (due to the camera bug in unlocking the bootloader). The first question about this: I've seen in many places the fear of backdoors/malware in "rooting" software. Is there an open source - safe method for this?
- backup the TA partition (where can I get more info about the TA partition, what is it, its purpose?)
- unlock the bootloader
- flash TWRP/CWM
- flash cyanogenmod
- restore TA partition. This will relock the bootloader and bring the camera back.
The tricky part. I've seen in many places that a custom kernel won't boot with a locked bootloader. This is false in nexus devices, is there any documentation regarding xperia?
The last question, if I need to bring it back to factory defaults, will I be able to bring it to a 'factory brand new' state? Is there a factory image like the ones for nexus devices?
Thank you.

wkwkwk said:
Hi,
I have a good understanding of Nexus devices and I always used Cyanogenmod.
I'm keen in the differences between Nexus and Xperia devices.
To install CM on a nexus device is extremely straight forward
- unlock the bootloader (fastboot oem unlock) - will wipe userdata
- install TWRP (or CWM): fastboot flash recovery openrecovery-bla
- upload a CM update zip
- optionally encrypt the device / relock the bootloader
Although many say otherwise, a custom kernel will always boot fine with a locked bootloader on a nexus device. With a locked bootloader you're unable to flash a different recovery but if you lock the bootloader *after* having a custom kernel and custom recovery, everything is fine.
If you need to flash another recovery you need an unlocked bootloader.
- The last step - bringing everything back to factory defaults:
- unlock bootloader (fastboot oem unlock)
- flash a google factory image (fastboot also)
- lock bootloader (fastboot oem lock)
The device is now in the "brand new - factory state".
I've read about Xperia devices and my current understanding of the process is:
- use an exploit to gain root (due to the camera bug in unlocking the bootloader). The first question about this: I've seen in many places the fear of backdoors/malware in "rooting" software. Is there an open source - safe method for this?
- backup the TA partition (where can I get more info about the TA partition, what is it, its purpose?)
- unlock the bootloader
- flash TWRP/CWM
- flash cyanogenmod
- restore TA partition. This will relock the bootloader and bring the camera back.
The tricky part. I've seen in many places that a custom kernel won't boot with a locked bootloader. This is false in nexus devices, is there any documentation regarding xperia?
The last question, if I need to bring it back to factory defaults, will I be able to bring it to a 'factory brand new' state? Is there a factory image like the ones for nexus devices?
Thank you.
Click to expand...
Click to collapse
It's a little different than what you think:
1. Yup, use an exploit to gain root. The camera bug in the bootloader isn't a factor here. I don't know if there is an open source alternative to Kingo root or whatever. I think Kingo's safe though...
2. Back up the TA partition. The TA partition contains Sony's DRM keys: unique keys that are necessary for certain Sony software to work (such as the BIONZ image processor. When you lose the keys by unlocking the bootloader, the camera stops working because BIONZ no longer has its keys). The DRM keys can't be restored if they're lost (they're unique to every device), so if you don't back them up, you're screwed. Make sure to back them up, multiple times for security. Link for more about backing up TA: http://forum.xda-developers.com/showthread.php?t=2449244
3. You can flash CWM or TWRP without unlocking the bootloader (http://forum.xda-developers.com/showthread.php?p=45149758#post45149758). You just won't be able to boot a custom kernel. So cyanogenmod won't work on a locked bootloader because it can't boot its kernel. Any ROM that uses the stock kernel will be fine, though.
4. So you can't restore the TA partition if you're running cyanogenmod, as relocking the bootloader will make it unable to boot the custom kernel.
Custom kernels won't boot on a locked Xperia bootloader. I don't know about documentation, but I know from experience.
To restore to factory state, just restore TA partition and reflash stock firmware.

In short from what I figure is
If u use shady root app for pc just uninstall it and replace the superuser app that the shady app installs with the official one
The ta partition has all the Sony device specific DRM keys which are required for Sony stock apps and ****
And if u don't take a backup of it you can't revert to full stock after unlocking the bootloader
And lastly some guys are working on a way to fastboot a custom kernel via kexec or something without unlocking the bootloader so it doesn't break camera
Also don't unlock the bootloader now and just wait unless u really want to overclock by 100mhz CPU and 83mhz GPU and also break camera in the process
Sent from my C6903 using XDA Premium 4 mobile

m666p said:
In short from what I figure is
If u use shady root app for pc just uninstall it and replace the superuser app that the shady app installs with the official one
Click to expand...
Click to collapse
My main concern is that the root exploit will put malware more than in the superuser app. Once it has root access, it can put whatever it wants wherever it wants.
Have there been any real reports of malware or is it just speculation?
m666p said:
And lastly some guys are working on a way to fastboot a custom kernel via kexec or something without unlocking the bootloader so it doesn't break camera
Also don't unlock the bootloader now and just wait unless u really want to overclock by 100mhz CPU and 83mhz GPU and also break camera in the process
Click to expand...
Click to collapse
Sounds good. The main reason for Cyanogenmod is the OpenPdroid support. Would you happen to have a link with the work they're doing for booting a custom kernel on a locked bootloader?
I'm wondering how come booting custom kernels on a locked bootloader works just fine on Nexus devices, it may be 'as per design'.
Thanks.

[Q] Rooting 4.3 Problem

Hey guys i know there is probably an answer in here somewhere but ihave looked everywhere and tried all possible options to get this working. After my pc companion nagging at me to upgrade i bit the bullet and upgraded to JB 4.3 10.4.B.0.569
Afterwards i then found out that it had relocked bootloader and unrooted my phone..
So i went through the sony normal way of unlocked bootloader first of all... this is where i've hit a snag.. first time the Command promp told me it had failed then itried again with my KEY and it said DONE.... now my phone was stuck in a terrifying bootloop. So i then flashed 4.3 firmware using flashtools, and repaired my phone through sony center.... again.. tried to unlock bootloader and was stuck in boot loop. I have re flashed about 4 times and tried to unlock 4 times... still getting boot loops....
Any one care to shed some light on this?
Many thanks
Chris

Bootloader
Is bootloader unlock allowed?

Have you tried relocking it again using flashtool?
Sent from my C6603 using XDA Premium 4 mobile app

Hey
I was playing around with 4.3 all last night and managed to get root on my Z with locked BL,
Here is how I did it..
(Locked bootloader, skip unlocking if already unlocked)
- Flash the .67 firmware via flashtool
- Root 4.2 as you would have
- Unlock your bootloader and Backup the TA partition to relock this without losing any DRM keys
- Using flashtool flash the new firmware .569 (4.3)
- Then flash Doomlords advanced stock kernel
- Boot 4.3 and power down
- Using the recover installed with the kernel flash a superSU.zip from somewhere around here.
- Reboot and you now should have root
[Locked bl]
- Reflash ONLY just .569 kernel from the FTF
- Power on and Restore your TA partition to relock your boot loader and return everything back to normal..but with some root
As for your bootloader not unlocking properly i would first check to see if an unlock is allowed

when i try to flash 4.2 67 firmware..i just got bootloop..please someone help me..what have i done wrong..i still in LB..

Wipe data when flashing.
Sent from my C6603 using Tapatalk

Just unlock your bootloader through Flashtool when on newest firmware, flash advanced stock kernel, root,flash back stock kernel and re-lock your bootloader. should be working for you, and it wont take that much time :good::good:

kuboweb said:
Just unlock your bootloader through Flashtool when on newest firmware, flash advanced stock kernel, root,flash back stock kernel and re-lock your bootloader. should be working for you, and it wont take that much time :good::good:
Click to expand...
Click to collapse
If the warranty and features such as Bravia Engine 2 are important to anyone, please don't just follow this. Your DRM keys that allow BE2 to work and your warranty will be permanently lost.
Follow the earlier post in this thread and downgrade, root and backup your TA partition BEFORE unlocking the bootloader.
Sent from my C6603 using Tapatalk

[Q] Unlocking Bootloader

In the Xperia SP versions which don't allow bootloader unlocking (Bootloader unlock allowed: no) , does the phone not boot in fastboot mode? I can go to Flashtool mode but not to fastboot. Is this the reason why?

update:
I only got you question now.
It is true that fastboot doesn't work with locked bootloaders, and that Flashtool does work.
But that doesn't mean your custom rom or kernel you flash with flashboot will boot. It works for stock.
If you're at 4.1 there are ways to get root and CWM, I don't think there are easy ways to flashing custom rom or installing root or CWM from 4.3 unrooted without unblocking, getting back to 4.1 to get root on 4.3, or perfoming factory reset.

You may want this: http://forum.xda-developers.com/showthread.php?t=2649923
It's a very long way, but at least it works. You can get 4.3 rooted with recovery, but you must go back to 4.1.2 to run CWM once. That is for root; Recovery procedure includes factory resetting...
Hope you can get it working as you want... Locked bootloader really are nasty

[Q] Xperia ZR unable to boot

I can't boot XZR(C5502) since i tried to flash a CWM based Rom.
1)Xperia ZR 10.5.A.0.230 ROOTED[Locked bootloader]
2)Recovery installed Philz touch,cwm,twrp by NUT
3)I have Nandroid backup also have TA backup.
4)I dont remember about USB debugging on or off.
5)I tried to enter in recovery but nothing happend.
6)While entering in fastboot blue LED lights up.nothing on screen.
Please tell what to do?
Please paste a link for ftf file(indian).I can't find 10.5.A.0.230 for C5502 indian.
Is it ok to flash nordic or some other varient of ftf.

1. Did you check if the ROM requires an unlocked bootloader?
2. Did you perform a factory reset in recovery before flashing?
If you can't enter recovery, it's likely that zip you flashed included a kernel, and the kernel flash failed because of the locked bootloader. Find a stock FTF (doesn't matter which variant, only thing that changes is the bloatware and the default language, which you can change on first setup, all Sony media apps are the same), flash it, unlock bootloader (make sure you still have your TA backup, if not, root and take it again), install recovery and try flashing the ROM again.
P.S. Fastboot only shows the blue LED, nothing on the screen, there's nothing wrong.
Good luck!

SirVer said:
1. Did you check if the ROM requires an unlocked bootloader?
2. Did you perform a factory reset in recovery before flashing?
If you can't enter recovery, it's likely that zip you flashed included a kernel, and the kernel flash failed because of the locked bootloader. Find a stock FTF (doesn't matter which variant, only thing that changes is the bloatware and the default language, which you can change on first setup, all Sony media apps are the same), flash it, unlock bootloader (make sure you still have your TA backup, if not, root and take it again), install recovery and try flashing the ROM again.
P.S. Fastboot only shows the blue LED, nothing on the screen, there's nothing wrong.
Good luck!
Click to expand...
Click to collapse
I did all of above things.But should I unlock the bootloader.I am aware about BE 2 stops working.
Will BE 2 work after restoring TA backup.

dtechgeek said:
I did all of above things.But should I unlock the bootloader.I am aware about BE 2 stops working.
Will BE 2 work after restoring TA backup.
Click to expand...
Click to collapse
Yes BE2 will work after restoring TA Backup. I guess (not sure), restoring TA will lock the bootloader as well. Correct me if I am wrong :angel::angel:

anthonythangaraj said:
Yes BE2 will work after restoring TA Backup. I guess (not sure), restoring TA will lock the bootloader as well. Correct me if I am wrong :angel::angel:
Click to expand...
Click to collapse
you are right plus you need to get back to stock kernel before restoring your ta

(SOLVED) rooting status Unknown/Remote command Failed

Hey
If u have flashed FTF or any other zip and lost your IMEI/Service And Major Issue Loosing Root status and unable to flash kernel/recovery using fastboot or flashtool
Rooting Status Unknown in service menu Configuraton *#*#service#*#*
Then you can revert back in two cases.
Case 1
That Worked for me.
You Have TWRP OR CWM Backup of previously working Firmware.
Steps:
1. Install Flashtool & Drivers. If you have already installed,Remove and reinstall. use 0.9.18.4 that worked for me.
2. Follow these steps.
A. Open C:/Flashtool/Custom/mydevices/
B. View The video for further steps and close flashtool folder.
https://www.youtube.com/watch?v=Qkl9UyrQKSo
after above steps/Check wether you can flash Kernel/Recovery Using flashtool/If u succeeded then Cheers.
Otherwise procede to next step.
C. Relock ur bootloader using flashtool. U may have to try 2 to 3 times if it failed/Check adb fastboot drivers,I tried 5 to 6 times and then it relocked my bootloader. If it is locked, dont unlock yet.
3. Download and flash Kitkat 4.4.4 Firmware using flashtool.
4. Download XZDR From the link
http://nut.xperia-files.com/path/XZDualRecovery/XZDualRecovery_2.8.26 [email protected][NUT]'s for awesome work.
5. Start it and browse for Superuser.zip(Copy to storage),Install Kingroot v 4.5 and Busybox and install to phone.
6. Check root status if successfully rooted then Open XZDR and extract it. Run .bat file and check your phone,Give root permission. your phone will reboot to recovery.
7. Now
Wipe cacche/Dalvik/System/Data
8. Install twrp backup that you have already stored in cell phone.
9. Install Superuser.zip. Again Wipe cache/Dalvik cache only.
10. Reboot your phone and all set.
Method 2
If yo dont have twrp backup.
Relock bootloader/Flash Kitkat and root it using above steps.
One you installed recovery. Reboot to recovery and do steps 7 to 10.
Cheers

I have a similar problem, Please Help me
I was flashing a stock rom for my xperia z3 D6653. On flashtool I unticked "SIMLOCK" in MiscTA Exclude. (<----i think This was the problem)
After that, the flashing proccess started and done without any problem. When i put the sim card in the phone, it says: "Invalid Sim card" and in the service menu says: "Rooting status: Unknown". Before this, the service menu said: "Rooting status: Unlock Bootloader allowed: yes" then I unlocked my bootloader without any problem and everything was perfect, but after that flashing on flashtool the Rooting status change to "Unknown" and my sim card are unable to read. There is no problem with my sim card because I tried to put it on another phone and works perfect.
How do I fix it?
How I change the roothing status back to "allowed: yes"
and how I fix it to be able to read my sim card again?
sorry for my horrible english.
Please help me to solve it, im a noob in this kind of things and i dont know how to follow the tutorial.

Well this definitely has something to do with the TA partition. I also installed the 228 update yesterday which resulted in a non-working SIM, together with the "Rooting status: Unknown" error.
After creating a TWRP backup, I just flashed KK 4.4.4 (.292) onto my device. This however did not solve my problem, as it still showed "Rooting status: Unknown".
I have just restored my saved TA-partition (I made a dump of it before unlocking the bootloader months ago, http://forum.xda-developers.com/showthread.php?t=2292598) and this has fixed my problem!!! It now shows "Rooting status: Unlock Bootloader allowed: yes".
So, if you have saved your TA-partition you can try to restore it onto your device. Otherwise you could try to relock and unlock your bootloader, hopefully this will solve your problem.
Good luck