Hi there - I just bought myself a motorola defy , and though I'm still convinced that it was a good decision (Even after reading about all the problems with motorola-android support and getting custom roms running)
As far as I have understood - it is not possible to load kernels on to motorola smartphones (save the Droid) which haven't been signed by motorola due to the special bootloader, that is only capable of loading signed kernels.
I was only able to find some information on pc bootloaders in wikipedia
(http)://en.wikipedia.org/wiki/Booting#Boot_loader.
The bootloader is a software component it self that resides in the first sector of the flash memory.
My Question:
If the bootloader is on flash memory just as the actual kernel that is to be loaded - why isn't it possible to overwrite the motorola bootloader with an open-source variant?
Obviously it is not possible, or it would have been done already right?
Thanks in advance.
Regi.
Related
I am just jumping into the android moding world, and I just can't seem to find clarification on a particular issue. It seems that most phones are rootable but many have a locked bootloader. From what I can glean through reading many posts here and searching the web, the geekish options that you give up on a phone with a locked bootloader is the ability to flash the ROM. However, this is contradicted by examples here on this site of ROMs for phones with locked bootloaders. (Moto Atrix for example.) Is it that custom ROMs can only go so far with rooting alone, like the inability to replace the kernel? What exactly do you give up by only achieving root with a locked bootloader vs a rooted phone with an unlocked bootloader? Is it ROM related at all?
notmuchpastnothing said:
I am just jumping into the android moding world, and I just can't seem to find clarification on a particular issue. It seems that most phones are rootable but many have a locked bootloader. From what I can glean through reading many posts here and searching the web, the geekish options that you give up on a phone with a locked bootloader is the ability to flash the ROM. However, this is contradicted by examples here on this site of ROMs for phones with locked bootloaders. (Moto Atrix for example.) Is it that custom ROMs can only go so far with rooting alone, like the inability to replace the kernel? What exactly do you give up by only achieving root with a locked bootloader vs a rooted phone with an unlocked bootloader? Is it ROM related at all?
Click to expand...
Click to collapse
You can't flash a custom rom without root. Root is needed to write to system partition etc.
But you can get root without a custom rom.
A locked bootloader means you will have to stay on stock rom. Means no custom kernels, no custom firmware.
Someone correct me if im wrong.
still confused
As mentioned there seem to be custom ROMs for for phones with a locked bootloader. The new Motorola Atrix is an example. While there is complaining that the bootloader is locked there are custom ROMs (2, I believe, so far) available from members of this forum. What is it that can't be done with a locked bootloader?
I'm still confused, but I appreciate the reply.
I'm sorry but I have googled and searched here trying to get a clear answer, but I think it comes down to my lack of understanding.
What is the difference between the bootloader being locked vs unlocked and what does that mean for the development? I currently have the Acer Iconia and love it, but if there will be more/better development on the transformer I may switch.
I also want to try and figure this out as I have a Droid X and use the bootstrapper to load ROMS but again I do not have the understanding I think I need for this subject matter.
Thanks all for your work and contributions. XDA has taught me alot and I am trying to further my understanding so please forgive me if this is the wrong forum to ask this in.
Well i downloaded the latest update from asus and applied it to my tablet. I now can't use CWM on my SD, i could before.
There's three types out there right now:
Unlocked bootloader: You can flash whatever you want
Locked bootloader: It verifies a signature before flashing. Usually the signature check isn't all that hard to really defeat (the Thunderbolt's was defeated in somewhere around a day, IIRC).
The Droid X bootloader, on the other hand, is Encrypted, in addition to being Locked. This is the reason that you have to bootstrap custom roms, and can't just install them directly. Motorola is the only one that's using an Encrypted Bootloader, AFAIK.
Well i can help with the unlocking, I just need to know what to do.
KitsuneKnight said:
Motorola is the only one that's using an Encrypted Bootloader, AFAIK.
Click to expand...
Click to collapse
Nop, Sony Ericsson also encrypt their bootloader in all 2010 Xperia Series
Hey guys,
I've been playing around with the firmware on my Moto G and I didn't understand some things related to bootloader/partition table version and I hope someone more knowledgeable can explain me some things, in a more technical way if possible. Links to documentation are also appreciated!
So, apparently you have to keep an eye on bootloader, partition table, and OS versions so they match. You also cannot easily downgrade bootloader versions.
Also, I saw that you can brick your device if you try to flash 5.0.1 ota, then go back to 4.4.2 and flash 4.4.4 ota because of mismatched bootloader versions and will have to wait for official motorola 5.0.1 images.
My first question is why does this happen? If I get stuck on a particular bootloader version (in this case 5.0.1 GPE, right?) why can't I just boot the corresponding OS, why does the device brick (is it incompatible bootloader and partition table, so the bootloader can't find stage 2)?
Second question, apparently you CAN downgrade the bootloader versions, but have to follow some specific steps and use specific files. Why is that? What checks does the devices makes when upgrading bootloaders and what kind of files allow me to downgrade while passing those checks?
Third, why can't you boot older android versions with newer bootloaders? Doesn't the bootloader just initialize some devices and loads the kernel, can't you modify and older kernel to boot with the new bootloader or chainload and older kernel from a newer one? Also why does the boot processes change so frequently when it should be something very stable?
Fourth, what is the rationale behind not allowing you to freely switch bootloader versions?
Well, thats it. Sorry for the long post and thanks to anyone that can help me . Maybe I should post this in android development instead?
I follow .
I believe on Nexus hardware changing Bootloader is an easier process as those devices are deliberately Developer friendly. Motorola are open enough to allow unlocking, but as you have discovered, flashing an older Bootloader is a messy and dangerous process. Perhaps if enough people petitioned for a change, things might be different.
The Bootloader and Kernel are interrelated and that is why newer Bootloader versions break compatibility with previous iterations of Android (each with a unique Kernel.)
It's possible Kernel DEVs could offer a solution, but I suspect the reality is so few people care. The majority of users will get OTA Updates and never go back.
Uh, bump?
Anyone can tell me if there is a more appropriate place to ask question like these?
I hope it will give you some reference in these topics.
http://elinux.org/Android_Booting
http://androidforums.com/threads/android-partitions-kernels-explained.278898/
aryal.subasha said:
I hope it will give you some reference in these topics.
http://elinux.org/Android_Booting
http://androidforums.com/threads/android-partitions-kernels-explained.278898/
Click to expand...
Click to collapse
Thanks, but I already found those in Google and they aren't very useful. Too superficial and both focus on what happens AFTER the kernel is loaded, I'm interested more in the bootloader, how it verifies the signatures, etc.
Anyone?
I'm interested in buying Nubia X.
I have never owned a zte or nubia phone before and have no idea about their Android updates, rooting, etc.
History-wise, can nubia phones be rooted / unlocked (bootloader)? And possible to have custom rom installed? Are there developers usually working on nubia phones?
The other phones are very easy to unlock, in fact I would say too easy. The Z11 and Z17 do not have passwords for unlocking so it's simply a case of plugging your device in and running oem unlock, there is no wipe. So be aware anyone with knowledge will be able to bypass your lock screen by simply unlocking the phone and removing the lockscreen files...
Be careful and encrypt your device if you get one.
Monotoko said:
The other phones are very easy to unlock, in fact I would say too easy. The Z11 and Z17 do not have passwords for unlocking so it's simply a case of plugging your device in and running oem unlock, there is no wipe. So be aware anyone with knowledge will be able to bypass your lock screen by simply unlocking the phone and removing the lockscreen files...
Be careful and encrypt your device if you get one.
Click to expand...
Click to collapse
Ok thanks. I was asking in terms of being able to flash custom rom though. I currently use oppo and not being able to flash custom rom sucks. Just curious about nubia's history of practice (updates, bootloader unlock, custom rom support). And this phone has 2 screens, will there be likely custom roms made for this phone?
I'm really interested in buying this phone for the hardware part and flashing a custom rom to get newer android versions
Dual OS
I was wondering if I could create a custom rom in a way that works similar to a DualBoot, or rather, did to switch between two operating systems to run both simultameamente, sharing all the hardware except the display. For example, run Pure Android Pie on the home screen, and windows 10 on the back screen.
Sorry for the bad english and "invade" another topic.
Thank you.
Azevolve said:
I was wondering if I could create a custom rom in a way that works similar to a DualBoot, or rather, did to switch between two operating systems to run both simultameamente, sharing all the hardware except the display. For example, run Pure Android Pie on the home screen, and windows 10 on the back screen.
Sorry for the bad english and "invade" another topic.
Thank you.
Click to expand...
Click to collapse
Yes that is a good idea. Won't it eat too much storage though? There's no sd slot here. What about battery life, will it be affected? So i guess it should be the 128gb version so you have enough storage for apps and files.
To this moment, NubiaX has no root solution yet. This should not be a surprise as the phone just launched for 20 days.
Good news is historically, all Nubia devices can be rooted, including it's latest flagship Z18 which launched on 9/5.
Bad news is that there used to be only 2 ROM developers working on Nubia devices' rooting, not sure when X will get their attention.
Hello guys, This is my first thread on XDA forum.
I just bought Xiaomi device (Poco X3 Pro Global) a few days ago.
So this is my first time to try custom rom, I searched what I'm trying to do, I'd like to make sure whether what I understand is correct or not since I'm totally new on custom rom.
the sources I mainly referred to:
source1
source2
Basic assumption:
1. Only flash custom rom without rooting
2. All unlocking bootloader and flashing custom rom process done perfectly, and all resouces (recovery, rom, ADB tool etc...) used during process are 100% clean and genuine.
3. No cold boot attack (source2) happens on me.
Q1. source1 is really helpful, but it's from 2012, is this still valid today?
Q2. source1 is posted on Galaxy Nexus forum, but is this applied to all android based devices, right?
Q3. This threat model assumes attacker has physical access to device, then I guess unlocking bootloader itself is 100% totally irrelevant to software level security risks like malware or OS vulnerability, is this right? (assuming no rooting and 100% genuine rom and resources)
Q4. From source1 you can choose between [device encryption] and [relocking bootloader] to protect security, which methods do you recommend using?
I feel I'm much more inclined to try device encryption method since I don't know if it's possible to relock bootloader safely after migrating from Global stock rom to xiaomi.eu rom. (Can anyone confirm this?) I fear it become bricked during relocking process.
Q5. So if I set device encryption with strong password and turn off USB debugging mode, I need not too worrysome?
Are there any other points in terms of security to bear in mind if you use device with unlocked bootloader?
Thank you for reading my thread
[INFO] Understanding the risks of having an unlocked bootloader
While unlocking the bootloader on a Galaxy Nexus unleashes the full potential of the bootloader, it also poses a security risk. Even with your lockscreen protected with a pattern/PIN/password, not having flashed a custom recovery, having an...
forum.xda-developers.com
jwoegerbauer said:
[INFO] Understanding the risks of having an unlocked bootloader
While unlocking the bootloader on a Galaxy Nexus unleashes the full potential of the bootloader, it also poses a security risk. Even with your lockscreen protected with a pattern/PIN/password, not having flashed a custom recovery, having an...
forum.xda-developers.com
Click to expand...
Click to collapse
that's what I linked in thread (source1)
Only a side-remark:
An Android Smartphone bootloader is processor-specific and every OEM has its own version of bootloader specific for the hardware present in its environment.
It's the primary task of every bootloader to verify the Android OS to be loaded is genuine means signed by OEM to ensure the Android OS ( it's by nature a Custom ROM ) works flawlessly as it can be expected by user. People who use a phone as a tool and not as a toy probably never come up with the idea to unlock the bootloader because they know about the strengths and weaknesses of the phone when they bought it, they can expect that OEM did their best with regards to a phone's performance - OEMs are certainly not dumber than generally claimed by the modder / hacker scene.
My POV: Unlocking a phone's bootloader is an unnecessary action at all. If people do so they indirectly admit that they have purchased a phone that does not meet their expectations - they have made a wrong purchase.
Thanks for comment.
I understand your POV.
I realized later Global rom can't do call recording, that's the main reason why I try to flash xiaomi.eu rom and other optimazations are second reason.
And this phone will be my main phone so I wanted to make sure about security risk before I will change rom.
cromcromc said:
Thanks for comment.
I understand your POV.
I realized later Global rom can't do call recording, that's the main reason why I try to flash xiaomi.eu rom and other optimazations are second reason.
And this phone will be my main phone so I wanted to make sure about security risk before I will change rom.
Click to expand...
Click to collapse
Having an unlocked bootloader doesn't need to be a risk whatsover as long as you're not flashing untrusted ROMS and other components to the device and critically control anything being flashed to the device. If you're flashing a signed ROM from the manufacturer as it sounds like is your plan, there is nothing to worry about. You can even lock the BL again after flashing & optimizing if you absolutely wish to although usually not recommended.