[Q] bootloader - XPERIA X8 Q&A, Help & Troubleshooting

Do you have to unlock the bootloader before you can install any rom's

zack19 said:
Do you have to unlock the bootloader before you can install any rom's
Click to expand...
Click to collapse
Yes and No
You only need to unlock the boot loader IF ...
a) you checked that your phone is safe for boot loader unlock.
b) you want to make use of a custom ROM that REQUIRES a custom kernel
ROMs where the description says "STOCK" or "Stock Kernel" also run on the default Kernel - and are the only ones you can use if you can not unlock the boot loader on your phone.
Please see the "Hard brick warning - Read before boot loader unlock" Sticky in the X8 General board to educate yourself on the matter.

Related

[Q] unlock boot loader

i need to unlock boot loader again if my brick my phone when install rom? for example i install naa kernel then install xxx rom but phone brick then i rescue my phone uing flash tool. does i need to unlock again to flash custom kernel
chbea said:
i need to unlock boot loader again if my brick my phone when install rom? for example i install naa kernel then install xxx rom but phone brick then i rescue my phone uing flash tool. does i need to unlock again to flash custom kernel
Click to expand...
Click to collapse
First of all, if you want to unlock your phone, check the date of manufacturing first! It is well documented here plenty of examples of newer phone brick when unlocking bootloader, so better be careful!
Secondly, if you ran into problem, you need to re-lock your phone using flash tool. Then re-unlock again! I previously lost my phone GSM radio when unlocking bootloader (while on GingerExperia). I have to flash into stock ROM (it's a must) using flash tool, and relocked again.
Finally, it is safest to unlock bootloader in stock rom.
chbea said:
i need to unlock boot loader again if my brick my phone when install rom? for example i install naa kernel then install xxx rom but phone brick then i rescue my phone uing flash tool. does i need to unlock again to flash custom kernel
Click to expand...
Click to collapse
No, you don't need to unlock it again. BL is the flash partition of the phone, what contains a secret code. When you unlock the BL, you'll remove the code and the flash partition will be open. When you flash a new ROM, it changes the system partition. When you flash a new kernel, it changes the flash partition but nothing else. So you'll not need to unlock BL again.
Sent from my E15i using xda premium

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.

rooted now what is the next step

now im downloading kitkat 4.4.4 to flash and then i will root with the new tool ,, i need to what is the next step to flash recovery and custom firmware and mods
i read about dual recovery , fastboot ,flashtool , boot loader , unlock boot loader but i dont understantd so if anyone can help me in this !!
If you root with the newtool it will install recovery as well.
Dual recovery is just a recovery package that gives you the option of 3 recoveries
You do not need to unlock the bootloader to get recovery, but you do if you want to flash a custom kernel.
i rooted now using the new tool from this topic and nw i have recovery .. can i flash custom roms ?
http://forum.xda-developers.com/xperia-z1/development/newroot-z1-t2807092
Mohaakotb said:
i rooted now using the new tool from this topic and nw i have recovery .. can i flash custom roms ?
http://forum.xda-developers.com/xperia-z1/development/newroot-z1-t2807092
Click to expand...
Click to collapse
From the development section yes.
If you want to flash custom roms from the original development section you need to unlock the bootloader
Mohaakotb said:
i rooted now using the new tool from this topic and nw i have recovery .. can i flash custom roms ?
http://forum.xda-developers.com/xperia-z1/development/newroot-z1-t2807092
Click to expand...
Click to collapse
yes you can flash custom rom base on sony stock, not AOSP (CM, PA, AOKP...)
i didnt get it !! what is the difference ? and how to unlock boot and is it dangerous ?
The difference is the kernel. Locked bootloaders will not boot on a custom kernel. In order to unlock your bootloader just Google "Sony unlock bootloader "
Sent from my C6903 using XDA Premium 4 mobile app
ok what i lose if i unlocked bootloader ? and is it easy to lock it again or factory reset ?

[HELP] Recovery Mode

Hello everyone, i am pretty bad at english so dont judge me becouse of this, and i am also noob here
So, i have problem. Why i cannot enter into recovery mode? I want to flash custom rom in my phone, i already have succesfully rooted with this method http://forum.xda-developers.com/xperia-z/general/guide-how-to-root-10-5-1-0-283-t2872873 and now i want custom rom, but i cant flash it becouse i cant enter in recovery mode, whats the problem? And another question, did i need unlocked bootloader for custom roms? What if i need it but i have already rooted? Did its big risk to unlock bootloader for already rooted phone? Sorry guys i am noob here, thanks for help!
First, did you install any recovery like CWM or TWRP or Phil...
on the page it talks about XZDualRecovery: you may choose any other if you prefer
if not there is no GUI based recovery in Sony Software and you need to install them separately.
Since you have already Rooted the Phone..
1. Start with This, go to the below link and backup your TA partition
http://forum.xda-developers.com/showthread.php?t=2292598
This backup is very important if you want to revert back to factory image so keep it safe. WITHOUT THIS BACKUP DO NOT UNLOCK YOUR BOOTLOADER
2. Only on successful backup of TA, think about unlocking your bootloader. from your dialer dial *#*#7378423#*#*, and check if you have "Bootloader unlock allowed: Yes"
Unlocking the bootloader means you can install any of the ROM's available for your phone. If you don't want to unlock or cannot unlock then you may be restricted ROM's with Sony Kernels only.

Install Custom Rom then re-lock?

I would like to install a custom ROM. But I really hate that screen when you first boot saying you have unlocked your phone blah blah. I would like to install a custom ROM with my boot loader unlocked. After it's up and running I want to re lock it so that message does not appear on boot. Also is it possible to disable the DM- verity check message as well when booting with a custom ROM? The goal is to have a custom ROM on the phone with no warning messages at all about anything.
That's not possible. To be able to re-lock you need a kernel that is signed for the locked bootloader which effectively makes it impossible to run any ROMs using any other kernel and recovery than stock OOS and also makes it quite a mess to update ROMs as you would have to unlock bootloader everyone to run TWRP and also unlocking and relocking also factory restores the phone everytime so you would lose all your data all the time. ?
It's possible to remove the DM message at boot. Look in the stickied Q&A thread for details.

Categories

Resources