A long time ago I've had an xperia X8, and was thinking about its software.
So, on it, I could install recovery, and then flash any ROM that is built for stock kernel, since I didn't unlock the bootloader.
My question is, couldn't the same concept be used on xperia M? With rachit's recovery for locked bootloader we could flash ROMs that are/will be made for stock kernel, right? If not, can anyone explain this to me?
No since Xperia M doesn't have a default recovery , you should unlock the bootloader in order to install any custom ROMs
XDAOwner!! said:
No since Xperia M doesn't have a default recovery , you should unlock the bootloader in order to install any custom ROMs
Click to expand...
Click to collapse
Actually, yes it would be possible with the concept the OP is describing. Once we have a fully working recovery for locked bootloaders it will be possible to build ROMs and then distribute them for other members to use.
OP just wait until there is a properly built/working recovery built for locked bootloaders (we have people working on it now) and then you will see ROMs built for locked bootloaders popping up.
gamer649 said:
Actually, yes it would be possible with the concept the OP is describing. Once we have a fully working recovery for locked bootloaders it will be possible to build ROMs and then distribute them for other members to use.
OP just wait until there is a properly built/working recovery built for locked bootloaders (we have people working on it now) and then you will see ROMs built for locked bootloaders popping up.
Click to expand...
Click to collapse
Hehe, I knew this would be the case. I've been experimenting with adb lately, and well, I'll try to make a script that (kind of) modifies some basic features until we make some progress with the recovery. Hope it doesn't take too long.
Just remember that only stock kernel works with locked bootloader. In other words, no OC and other things like that and only custom ROMs compatible with stock kernel would work...
Related
Good Evening,
i have a non rooted xperia arc and locked bootloader.
I want to install the Recovery to have Root access on every Rom .
How i must begin ?
dubist said:
How i must begin ?
Click to expand...
Click to collapse
By SEARCHING, then you would have found this - http://forum.xda-developers.com/showthread.php?t=1133650
That guide doesn't mention recovery at all.
At the moment, to use recovery, you need to use Fastboot which is only compatible with handsets that can have their bootloaders unlocked - possibly handsets that have already had bootloaders unlocked but I'm not 100% on that, still waiting for an answer from Bin4ry on that.
It's in beta at the moment though, so you may be safer not using it until some of the kinks have been ironed out.
Also, apart from an early version of CM7, there aren't any ROMs available for the Arc apart from stock SE ones, so there's really no need to use recovery just now.
I want to install a aosp rom on my Z1 compact.
My Z1 compact is running and i am trying to unlock the bootloader. I have entered *#*#7378423#*# which says i cant unlock the bootloader.
Is there any other method to unlock the bootloader?
No, bad luck.
Do you think it will be possible in the future?
325i. said:
Do you think it will be possible in the future?
Click to expand...
Click to collapse
Who knows, it's a tiring subject, so either return your Phone and buy a SimFree Phone or keep it in the hope that maybe you'll be able to, but don't hold your breath.
2ndBoot method possible?
For some Android phones with a locked bootloader, for example Motorola Defy, a "2nd boot" method has been used to use custom roms.
The way I understand it, this leaves the stock kernel in place, so that the locked bootloader can boot the stock kernel that it insists on.
Using root permissions, the system is modified so that at some stage in the stock boot process, the boot process restarts with a possibly different, modified kernel and the definitely different, custom userspace system, for example AOSP.
Has this been done with Xperia devices, especially the Z1C?
Defyner said:
For some Android phones with a locked bootloader, for example Motorola Defy, a "2nd boot" method has been used to use custom roms.
The way I understand it, this leaves the stock kernel in place, so that the locked bootloader can boot the stock kernel that it insists on.
Using root permissions, the system is modified so that at some stage in the stock boot process, the boot process restarts with a possibly different, modified kernel and the definitely different, custom userspace system, for example AOSP.
Has this been done with Xperia devices, especially the Z1C?
Click to expand...
Click to collapse
This is extremely difficult to accomplish unless the kernel supports loading kernel modules on the fly, and the Z1C stock kernel doesn't. In fact, most devices don't these days since it enables things like this once the security of the ROM is compromised.
@325i. You will most likely (like 99.99%) never be able to unlock your current Z1C, return it and get an unlockable one, or change your mind about wanting to unlock it.
Other than warranty issues, and possibly redeeming your Google Drive space, are there any practical ramifications to simply leaving the bootloader unlocked (or, conversely, locked?) on an S-off device? I'm inclined to leave it bootloader unlocked unless I have a warranty issue, as it seems the safest way to make sure I'm never locked out, but I'm curious to know if there are any reasons to lock it from a security perspective.
I say that because right now when I lose root due to an OTA, I just boot (but not install) philz touch recovery to re-root, which I am assuming is allowed because I am s-off. (because otherwise root would be trivial). It seems that as long as I can do that, the bootloader lock/unlock state is somewhat pointless.
You are allowed to flash custom ROMs because you have installed a custom recovery, which was allowed because you unlocked your bootloader. I would leave the bootloader unlocked until a relock is required (if it even comes to that). As far as I know, that poses no threat as long as you know what you're flashing on your device. Anyone with more experience with this may correct me, as I am quite new to the HTC world.
MrKhozam said:
You are allowed to flash custom ROMs because you have installed a custom recovery, which was allowed because you unlocked your bootloader. I would leave the bootloader unlocked until a relock is required (if it even comes to that). As far as I know, that poses no threat as long as you know what you're flashing on your device. Anyone with more experience with this may correct me, as I am quite new to the HTC world.
Click to expand...
Click to collapse
I actually only had TWRP installed briefly to "restore" the Dev Edition nandroid (and by briefly, I mean I booted it once). As soon as the Dev Edition ROM was up, I reverted to the stock DE recovery. Since then, I just "boot" Philz CWM to re-root (since TWRP fails when booted on 4.4.3 for some reason.)
as per he title "Are All Samsung Devices "Bootloader Unlockable""?... I know (i think) that samsung devices dont really have a bootloader in the sense that htc and motorola devices do, but this is my first samsung device so im trying to understand how it works based on terms im familiar with.
so in the sense that htc/motorla needs to have an unlocked bootloader to flash custom images, are all samsung devices "unlocked" once you flash with cf-autoroot? from my understamding, cf works on all samsung devices, right? In addition to that, is cf-autorooting necessary if one is goin to flash custom recovery anyway?
diabl0w said:
as per he title "Are All Samsung Devices "Bootloader Unlockable""?... I know (i think) that samsung devices dont really have a bootloader in the sense that htc and motorola devices do, but this is my first samsung device so im trying to understand how it works based on terms im familiar with.
so in the sense that htc/motorla needs to have an unlocked bootloader to flash custom images, are all samsung devices "unlocked" once you flash with cf-autoroot? from my understamding, cf works on all samsung devices, right? In addition to that, is cf-autorooting necessary if one is goin to flash custom recovery anyway?
Click to expand...
Click to collapse
AutoRoot is not required for a custom recovery
If the device is unlocked, a custom recovery can be flashed through Odin prior rooting the device. I unfortunately can not help you on whether or not all devices are shipped with unlocked bootloaders. I know the T-Mobile and Wifi variants are.
Toneman07 said:
AutoRoot is not required for a custom recovery
If the device is unlocked, a custom recovery can be flashed through Odin prior rooting the device. I unfortunately can not help you on whether or not all devices are shipped with unlocked bootloaders. I know the T-Mobile and Wifi variants are.
Click to expand...
Click to collapse
Thanks, but unfortunately i still dont understand. I flashed cf-autoroot and then flashed custom recovery, but your saying that my device may still be locked? So if i flash stock kitkat firmware via odin and then take the lollipop ota when it comes then there is a chamce i wont be able flash custom recovery again?
diabl0w said:
Thanks, but unfortunately i still dont understand. I flashed cf-autoroot and then flashed custom recovery, but your saying that my device may still be locked? So if i flash stock kitkat firmware via odin and then take the lollipop ota when it comes then there is a chamce i wont be able flash custom recovery again?
Click to expand...
Click to collapse
That is not what I am stating. If you were able to obtain a custom recovery - your bootloader is unlocked.
You are rooted and modified though, you are no longer able to recieve OTA updates. The only way to flash the update now would be through Odin, or returning your device back to factory specs. As of yet, they did not lock the bootloader with the 5.1.1 update. You will be able to root and obtain custom recovery again with 5.1.1 as you did with Kit Kat. The difference is, lollipop requires a custom non SE enforcing kernel usually.
Toneman07 said:
That is not what I am stating. If you were able to obtain a custom recovery - your bootloader is unlocked.
You are rooted and modified though, you are no longer able to recieve OTA updates. The only way to flash the update now would be through Odin, or returning your device back to factory specs. As of yet, they did not lock the bootloader with the 5.1.1 update. You will be able to root and obtain custom recovery again with 5.1.1 as you did with Kit Kat. The difference is, lollipop requires a custom non SE enforcing kernel usually.
Click to expand...
Click to collapse
Thank you! Everything makes more sense now that i know my device was unlocked.. i am so used to locked down devices i assumed that mine was and so i got confused. one last thing , is the download mode screen on samsung devices equivelamt to the bootloader screen on a moto device?
No! Not all Samsung's are unlockable! P605v is not. Any Verizon Samsung and/or AT&T phones are not unlockable
Sent from my SCH-R530U using Tapatalk
Orion116 said:
No! Not all Samsung's are unlockable! P605v is not. Any Verizon Samsung and/or AT&T phones are not unlockable
Sent from my SCH-R530U using Tapatalk
Click to expand...
Click to collapse
Thank you, I am pretty sure I understand the format now. The thing that was throwing me off the most was CF-Autoroot which for some reason I was thinking performed a bootloader unlock. Idk why because I know the difference between root and unlock. I think i was thrown off by one of the posts I read on the autoroot thread.
One final thing I am trying to clear up as per my last post "is the download mode screen on samsung devices equivelamt to the bootloader screen on a moto device? "
I don't know. I have never owned a moto device.
Sent from my SCH-R530U using Tapatalk
for anyone else reading this, according to king root's website "Download Mode is essentially the same as Bootloader Mode."
Good day guys,
Today I received my Mi 6. Friends told me Xiaomis usually come with an option to enable root, but I can't find it here. Can anyone help me?
I think you need to install the Developers Rom and there you have an option to enable root.
Ammmm no, you can't, at least you discover a zero-day exploit with execution code and bla bla bla.
For Root, you need mod boot/system image in the best case, or flash a tool like supersu to make the changes in fly... so you need a unlocked bootloader or custom recovery and flashing custom recovery need a unlocked bootloader.
Theliels said:
Ammmm no, you can't, at least you discover a zero-day exploit with execution code and bla bla bla.
For Root, you need mod boot/system image in the best case, or flash a tool like supersu to make the changes in fly... so you need a unlocked bootloader or custom recovery and flashing custom recovery need a unlocked bootloader.
Click to expand...
Click to collapse
Thanks for the reply, I guess i'm requesting the bootloader unlock to Xiaomi then.
Theliels said:
Ammmm no, you can't, at least you discover a zero-day exploit with execution code and bla bla bla.
For Root, you need mod boot/system image in the best case, or flash a tool like supersu to make the changes in fly... so you need a unlocked bootloader or custom recovery and flashing custom recovery need a unlocked bootloader.
Click to expand...
Click to collapse
what about install TWPR (still locked) then root it? is it possible?
mennas said:
what about install TWPR (still locked) then root it? is it possible?
Click to expand...
Click to collapse
Are you kidding?
No.
When boot loader is locked only code signed by xiaomi will run.
So twrp will just not bootup.
Also fastboot is only enabled on the phone when boot loader is unlocked so you'd have a hell of a time flashing it
And then youd likely softbrick the phone with no recovery to flash a ROM so maybe even hardbricked...
Don't try.
Just unlock.
Dobsgw said:
Are you kidding?
No.
When boot loader is locked only code signed by xiaomi will run.
So twrp will just not bootup.
Also fastboot is only enabled on the phone when boot loader is unlocked so you'd have a hell of a time flashing it
And then youd likely softbrick the phone with no recovery to flash a ROM so maybe even hardbricked...
Don't try.
Just unlock.
Click to expand...
Click to collapse
I don't know if this applies to Xiaomi and if it works on more recent versions of Android but on Xperia Z3, installing TWRP with locked bootloader was actually possible I did it myself, and hundreds of others has done it to (you couldn't change to a non-stock ROM, without unlocking the bootloader of course, but that's a different story)
Obviosly that would need a newer exploit in order to push TWRP.
But of course Google or Xiaomi may had added additional protections to the bootloader since then.
(with this being said, you probably need to be quite experienced to start looking into that kind of stuff)
-Zteam- said:
I don't know if this applies to Xiaomi and if it works on more recent versions of Android but on Xperia Z3, installing TWRP with locked bootloader was actually possible I did it myself, and hundreds of others has done it to (you couldn't change to a non-stock ROM, without unlocking the bootloader of course, but that's a different story)
Obviosly that would need a newer exploit in order to push TWRP.
But of course Google or Xiaomi may had added additional protections to the bootloader since then.
(with this being said, you probably need to be quite experienced to start looking into that kind of stuff)
Click to expand...
Click to collapse
You'll notice on newer xperia phones that's jot possible
You have to unlock.
They wised up and patched the KitKat exploit (although one was found in the 575 kernel)
So yeah potentially it would be possible to find an exploit and modify /system.
But the Z3 (I own one too) required having the mods to be in system if the BL was locked. Wolfbreak obviosuly managed to get twrp installed to system and then used scripts to open it.
But a custom kernel would still brick the phone.
So you were confined to root and recovery and custom ROMs based on stock.
You have to unlock to modify the kernel (which most root now does to avoid safetynet)
So there's not much point in this system level exploit.
Phone wouldn't boot as soon as a non stock or modified kernel was installed (lots of people would try and do this and brick their phones I guarantee)
Much better to just unlock.
Dobsgw said:
You'll notice on newer xperia phones that's jot possible
You have to unlock.
They wised up and patched the KitKat exploit (although one was found in the 575 kernel)
So yeah potentially it would be possible to find an exploit and modify /system.
But the Z3 (I own one too) required having the mods to be in system if the BL was locked. Wolfbreak obviosuly managed to get twrp installed to system and then used scripts to open it.
But a custom kernel would still brick the phone.
So you were confined to root and recovery and custom ROMs based on stock.
You have to unlock to modify the kernel (which most root now does to avoid safetynet)
So there's not much point in this system level exploit.
Phone wouldn't boot as soon as a non stock or modified kernel was installed (lots of people would try and do this and brick their phones I guarantee)
Much better to just unlock.
Click to expand...
Click to collapse
Of course you will be much more limited without unlocked bootloader but on the other hand you don't have to void your warranty, unrooting your phone, without any traces of root is very useful, if you happens to need your warranty.
And you can still use stuff like setcpu, xposed framework, enable EIS and camera api2. just to name a few things.
Safetynet didn't bother me that much.
That's why people are looking for ways to root without unlocking the bootloader.
-Zteam- said:
Of course you will be much more limited without unlocked bootloader but on the other hand you don't have to void your warranty, unrooting your phone, without any traces of root is very useful, if you happens to need your warranty.
And you can still use stuff like setcpu, xposed framework, enable EIS and camera api2. just to name a few things.
Safetynet didn't bother me that much.
That's why people are looking for ways to root without unlocking the bootloader.
Click to expand...
Click to collapse
OK well when the exploit is found you'll have it
Dobsgw said:
Are you kidding?
No.
When boot loader is locked only code signed by xiaomi will run.
So twrp will just not bootup.
Also fastboot is only enabled on the phone when boot loader is unlocked so you'd have a hell of a time flashing it
And then youd likely softbrick the phone with no recovery to flash a ROM so maybe even hardbricked...
Don't try.
Just unlock.
Click to expand...
Click to collapse
10 hours left lol. i hope after 10 hours there will be no more additional trouble coming up.
So, my plan after im able to unlock it is to root>install twrp>flash it back to global stabel(my current is global beta).
im still confused about stay with beta or flash it back to stabel. Any sugesstion?
mennas said:
10 hours left lol. i hope after 10 hours there will be no more additional trouble coming up.
So, my plan after im able to unlock it is to root>install twrp>flash it back to global stabel(my current is global beta).
im still confused about stay with beta or flash it back to stabel. Any sugesstion?
Click to expand...
Click to collapse
Stay with beta its usually better.
Or switch to aosp if you don't like MIUI
Stable Oreo should come soon as the Chinese ROM just got Oreo stable
Dobsgw said:
Stay with beta its usually better.
Or switch to aosp if you don't like MIUI
Stable Oreo should come soon as the Chinese ROM just got Oreo stable
Click to expand...
Click to collapse
ok. ill stay with this beta oreo then thanks
Dobsgw said:
Stay with beta its usually better.
Or switch to aosp if you don't like MIUI
Stable Oreo should come soon as the Chinese ROM just got Oreo stable
Click to expand...
Click to collapse
Wait, is Chinese stable on oreo already?
NickTheSickDick said:
Wait, is Chinese stable on oreo already?
Click to expand...
Click to collapse
Yeah.
Also expecting Oreo kernel sources to release soon too
Dobsgw said:
Yeah.
Also expecting Oreo kernel sources to release soon too
Click to expand...
Click to collapse
Damn, that didn't take long. I remember just how buggy it was when oreo first entered alpha.
NickTheSickDick said:
Damn, that didn't take long. I remember just how buggy it was when oreo first entered alpha.
Click to expand...
Click to collapse
They need to be even quicker 8.1 has been out for a fair while as well....
At least it got to Oreo.
I'm sure there will be more updates for the "stable" branch soon.
In my use I found beta to be better