I wonder if this could be done, by modifying the Stock Amazon Exclusive Firmware Rom, that way, bootloader wont be necessary to root the device and erase the ads, i mean if the firmware is a zip and can be flashed with ADB, i wonder why it cant be modified to include root and Make a clean rom to work with.
mike_san said:
I wonder if this could be done, by modifying the Stock Amazon Exclusive Firmware Rom, that way, bootloader wont be necessary to root the device and erase the ads, i mean if the firmware is a zip and can be flashed with ADB, i wonder why it cant be modified to include root and Make a clean rom to work with.
Click to expand...
Click to collapse
AFAIK the bootloader or the system checks for the signature when you flash any images to it and thats what the locked bootloader means.
The simple meaning of locked bootloader is that it only accepts the OEM signed images which means it wont accept the modified images as then it wont have the signatures.
Harsh.gundecha said:
AFAIK the bootloader or the system checks for the signature when you flash any images to it and thats what the locked bootloader means.
The simple meaning of locked bootloader is that it only accepts the OEM signed images which means it wont accept the modified images as then it wont have the signatures.
Click to expand...
Click to collapse
The bootloader locks the recovery and the kernel, so you cant actually flash on these partitions but, if you have the stock rom from Motorola, you can flash it because it has the signed images in it, or i'm wrong?
The point is to modify the stock rom with a root based and flash it
mike_san said:
The bootloader locks the recovery and the kernel, so you cant actually flash on these partitions but, if you have the stock rom from Motorola, you can flash it because it has the signed images in it, or i'm wrong?
The point is to modify the stock rom with a root based and flash it
Click to expand...
Click to collapse
Someone with proper and detailed knowledge or experience might be able to answer thisquestion exactly
and i would be happy if i am wrong, but i fear i am not
What could be possible is you may be able to flash the signed, stock ROM... wouldn't give you root but you may be able to have a clean ROM without the ads.
Related
Is it possible to flash a rom via fastboot? bootloader is Locked and im not rooted. fastboot devices returns what looks like a serial number, but adb devices returns nothing...
sorry for being a noob, just trying to get my phone working again. TIA for any help
I am curious about this too. It might be possible with an unlocked bootloader, but I'm not sure.
ImStillLearning said:
I am curious about this too. It might be possible with an unlocked bootloader, but I'm not sure.
Click to expand...
Click to collapse
For stock img files yes. But devs don't make img files. Rsd is the safe way to flash fastboot files.
aviwdoowks said:
For stock img files yes. But devs don't make img files. Rsd is the safe way to flash fastboot files.
Click to expand...
Click to collapse
Tried latest ver of rsd that i could find (6.1.5 i think) but it doesnt read my phone, I have installed drivers.
If its possible to load stock .img files (with locked bootloader) please tell me how to do it. Sorry again for me being complete noob.
BOWTIESNIPER said:
Tried latest ver of rsd that i could find (6.1.5 i think) but it doesnt read my phone, I have installed drivers.
If its possible to load stock .img files (with locked bootloader) please tell me how to do it. Sorry again for me being complete noob.
Click to expand...
Click to collapse
I am no Dev. I do what works on my unlocked M. I do not know much about the locked & RSD.
I do a lot of unconventional stuff.
Is it maybe possible to unlock the bootloader via fastboot
I can still get into the recovery (stock). Any way to flash new rom from there?
No & no.
But what is it exactly? What does it mean?
I mean I already did Autorec and all I know is that it downgraded the bootloader. No idea what that actually means, so I can understand what happened and more importantly how can I restore it (i.e upgrade it back) and what are the consequences of these actions.
Any developer around that can actually explain?
Zalmoxis12 said:
But what is it exactly? What does it mean?
I mean I already did Autorec and all I know is that it downgraded the bootloader. No idea what that actually means, so I can understand what happened and more importantly how can I restore it (i.e upgrade it back) and what are the consequences of these actions.
Any developer around that can actually explain?
Click to expand...
Click to collapse
Jellybean (12B) was the last bootloader to be able to be used with loki (the exploit to be able to flash custom recoveries/ROMs/kernels). Google patched the bootloader in the KitKat update (24A) so loki was useless. You could root, but couldn't flash the previously mentioned items. Being able to downgrade the bootloader allowed this. So even tho you'd be running KK, you're using a JB bootloader.
simon_lefisch said:
Jellybean (12B) was the last bootloader to be able to be used with loki (the exploit to be able to flash custom recoveries/ROMs/kernels). Google patched the bootloader in the KitKat update (24A) so loki was useless. You could root, but couldn't flash the previously mentioned items. Being able to downgrade the bootloader allowed this. So even tho you'd be running KK, you're using a JB bootloader.
Click to expand...
Click to collapse
I know this. I was asking what the bootloader actually is and how does it relate and connect with the other partitions.
Is it like some sort of MBR?
Zalmoxis12 said:
I know this. I was asking what the bootloader actually is and how does it relate and connect with the other partitions.
Is it like some sort of MBR?
Click to expand...
Click to collapse
http://searchenterpriselinux.techtarget.com/definition/boot-loader
Zalmoxis12 said:
I know this. I was asking what the bootloader actually is and how does it relate and connect with the other partitions.
Is it like some sort of MBR?
Click to expand...
Click to collapse
bootloader loads all the partitions and makes sure they work together, two examples of the stuff bootloader handles:
-bootloader boots
-bootloader then loads kernel making sure nothing wrong and if there is then you get no boot and instead you are thrown to fastboot to fix the problem
-after kernel loads bootloader loads system if corrupted/missing you get stuck in a bootloop unless you have custom recovery then you get stuck in recovery
-bootloader loads rest of partitions while the system/kernel begin to boot rom
when doing ota:
-phone reboots and loads bootloader
-bootloader loads ota into a partition on phone designed to decompile and apply ota into system/kernel partitions
-bootloader makes sure that system/ota are correct and compatible to apply update
-bootloader does root check process in the rtf partition and if rooted bootloader cancels ota process
so in short bootloader is most important asset, it is what decides the kernel to boot(you can mod a bootloader so that you can have too kernels and this is also how you create multi boot for boot more than one rom), it boots the rom, and it handles all other partitions in more than one way
Quick question.
I flashed the radio in my 6p.
Can I install the latest OTA Android update over that or do I need to go back to stock?
Also my phone is unlocked, does it need to be locked?
The radio flash didn't solve my problems.
Anyone?
Which radio did you flash?
2.50
Crakinarse said:
2.50
Click to expand...
Click to collapse
There's a lot about your config you haven't told us. Since you're staying your phone is "unlocked", I can only assume you mean the bootloader is unlocked, and you've got a custom recovery (TWRP) installed. If this is indeed the case, then no you should not take any "OTA" as any changes to "stock" (like a custom recovery) will cause it to fail.
You can, however, wipe and flash new Roms through twrp, or with an unlocked bootloader you can download the latest image from Google's sure for our device and flash that through fastboot (Google search to find tutorials on this there's a million of them). Be aware this will wipe EVERYTHING out on the device and reset it back to defaults (your data, recovery, etc.)
ohlin5 said:
There's a lot about your config you haven't told us. Since you're staying your phone is "unlocked", I can only assume you mean the bootloader is unlocked, and you've got a custom recovery (TWRP) installed. If this is indeed the case, then no you should not take any "OTA" as any changes to "stock" (like a custom recovery) will cause it to fail.
You can, however, wipe and flash new Roms through twrp, or with an unlocked bootloader you can download the latest image from Google's sure for our device and flash that through fastboot (Google search to find tutorials on this there's a million of them). Be aware this will wipe EVERYTHING out on the device and reset it back to defaults (your data, recovery, etc.)
Click to expand...
Click to collapse
All I did was unlock the bootloader and
fastboot flash radio image.
That is it.
I did not install a custom recovery.
Crakinarse said:
All I did was unlock the bootloader and
fastboot flash radio image.
That is it.
I did not install a custom recovery.
Click to expand...
Click to collapse
If you didn't flash a custom recovery you can download the ota without any issues. This is assuming that everything is still completely stock about your device. You can upgrade and downgrade your radio as you wish. I would advise to keep your bootloader unlocked so you can fix any problems if you ever have any.
If go to stock and relock bootloader for OTA, what is procedure to unlock again? Do you go back to the Moto site for a new code, or will they expect you to have the original unlock code (thus you could be outta luck if you bought the phone used , with an unlocked bootloader.)
The procedure is the same as when you first unlocked, although if you have the original unlock code you can skip getting a new one from Moto's site (it's the same code anyway), same rules apply, it will wipe everything and you must have OEM Unlocking in Developer options enabled as when the bootloader is relocked this option is turned off and must be turned on again manually.
Be aware you do NOT have to lock the bootloader to get an OTA update, the update script and the OTA server do not care if your bootloader is unlocked or not. The essentials are stock recovery and a stock system and boot image (meaning no root, Xposed, etc).
"Be aware you do NOT have to lock the bootloader to get an OTA update, the update script and the OTA server do not care if your bootloader is unlocked or not. The essentials are stock recovery and a stock system and boot image (meaning no root, Xposed, etc)."
Oh good...I'll try that first when ready . There's a thread somewhere with correct bootimage, recovery, and system I think?
hometech99 said:
"Be aware you do NOT have to lock the bootloader to get an OTA update, the update script and the OTA server do not care if your bootloader is unlocked or not. The essentials are stock recovery and a stock system and boot image (meaning no root, Xposed, etc)."
Oh good...I'll try that first when ready . There's a thread somewhere with correct bootimage, recovery, and system I think?
Click to expand...
Click to collapse
Here ya go..
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
hometech99 said:
"Be aware you do NOT have to lock the bootloader to get an OTA update, the update script and the OTA server do not care if your bootloader is unlocked or not. The essentials are stock recovery and a stock system and boot image (meaning no root, Xposed, etc)."
Oh good...I'll try that first when ready . There's a thread somewhere with correct bootimage, recovery, and system I think?
Click to expand...
Click to collapse
Just look in my sig... if you read there are links to firmware, and instructions to lock and flash, or just flash the factory image. I would recommend flashing the complete system image though, not just the pieces.
acejavelin said:
I would recommend flashing the complete system image though, not just the pieces.
Click to expand...
Click to collapse
..but your flashboot instructions show the pieces. Did you modify the process, and get the whole system image?
Thanks!
hometech99 said:
..but your flashboot instructions show the pieces. Did you modify the process, and get the whole system image?
Thanks!
Click to expand...
Click to collapse
No, I meant each piece of the full image, don't skip any parts.
Hey guys,
want to mod my freshly bought Mi A1 to the max, but I'm not sure if i should OTA first or better start modding right away?
I already unlocked the bootloader and it didnt wipe it - it also has 7.1 installed still. Generally I'm usually reluctant to do official updates because they usually make modding harder - but I tried booting the treble TWRP installer .img through fastboot (without installing it) and it failed because some partition was missing it said.. so I just want to hear if OTA is necessary to use the latest custom roms or if i can keep the old bootloader etc?
Would be cool if someone who knows could say smth about that.
Or is updating through OTA actually recommended even when not planning to ever use stock roms?
zroice said:
Hey guys,
want to mod my freshly bought Mi A1 to the max, but I'm not sure if i should OTA first or better start modding right away?
I already unlocked the bootloader and it didnt wipe it - it also has 7.1 installed still. Generally I'm usually reluctant to do official updates because they usually make modding harder - but I tried booting the treble TWRP installer .img through fastboot (without installing it) and it failed because some partition was missing it said.. so I just want to hear if OTA is necessary to use the latest custom roms or if i can keep the old bootloader etc?
Would be cool if someone who knows could say smth about that.
Or is updating through OTA actually recommended even when not planning to ever use stock roms?
Click to expand...
Click to collapse
If security matters for you yes
The only thing you'll share with a custom ROM is the bootloader
Since may update locking or relocking the bootloader will wipe your data
It's your choice
but it will still work as easy as before to unlock/lock with just a fastboot command, right?
and will a custom rom work with a locked bootloader? Like first unlock, install custom rom + kernel, then relock?
zroice said:
but it will still work as easy as before to unlock/lock with just a fastboot command, right?
and will a custom rom work with a locked bootloader? Like first unlock, install custom rom + kernel, then relock?
Click to expand...
Click to collapse
You have to enable it in Developer settings.
zroice said:
but it will still work as easy as before to unlock/lock with just a fastboot command, right?
and will a custom rom work with a locked bootloader? Like first unlock, install custom rom + kernel, then relock?
Click to expand...
Click to collapse
It will always be that easy to unlock and relock the bootloader
No don't relock on anything that is out of stock (custom kernel , magisk, custom ROM etc) this will lead to a softbrick and you'll have to be on edl more to reflash a stock rom
What's the interest of having a locked bootloader with a custom ROM? You won't pass the safety net anyway
Just keep it unlock
You can do ota with an unlocked bootloader
Dead-neM said:
It will always be that easy to unlock and relock the bootloader
No don't relock on anything that is out of stock (custom kernel , magisk, custom ROM etc) this will lead to a softbrick and you'll have to be on edl more to reflash a stock rom
What's the interest of having a locked bootloader with a custom ROM? You won't pass the safety net anyway
Just keep it unlock
You can do ota with an unlocked bootloader
Click to expand...
Click to collapse
alright. thanks very much for explaining in details - exactly what i was looking for.
What's the use of your android one device if you will not update it, that's what you pay for.
HidekiRyuga said:
What's the use of your android one device if you will not update it, that's what you pay for.
Click to expand...
Click to collapse
hahahaaa exactly the point :laugh:
well once you have everything "perfectly set up" updates can ruin it. but yea relocking the bootloader really was a stupid idea - it was the idea to make it tamper proof but since custom kernels wont boot with locked bootloader that wouldnt work.