So I have heard that it is nearly impossible to do a Bootloader unlock for a razr m with the latest update because they patched the hole that was originally exploited, I am wondering if this is indeed true. If so what recovery options are there since CWM and TWRP both need a unlocked device. I would LIKE to have the recovery program so I could switch between multiple roms, but im also able to just flash whatever rom I want and then flash a stock rom back on if I need it, without a recovery program aren't I?
WhatTheCuss said:
So I have heard that it is nearly impossible to do a Bootloader unlock for a razr m with the latest update because they patched the hole that was originally exploited, I am wondering if this is indeed true. If so what recovery options are there since CWM and TWRP both need a unlocked device. I would LIKE to have the recovery program so I could switch between multiple roms, but im also able to just flash whatever rom I want and then flash a stock rom back on if I need it, without a recovery program aren't I?
Click to expand...
Click to collapse
Yeah, so far you can't unlock the BL if you are the newest update. However, you can run SafeStrap and it will allow you to flash custom ROMs to Slot 1. SS is based off of TWRP, but it's not a true recovery replacement. Your stock recovery will still be intact. You won't be able to flash a true custom recovery on a locked BL. There are a few ROMs that were originally designed for SS. IIRC, Energy, Eclipse V1.2, older builds of CM10, Flying Jelly (was originally designed for SS, but may have been re-designed for unlocked BL), and DeadCalm (also originally designed for SS, but may have been redesigned for unlocked BL) all were made for SS.
How to SafeStrap:
http://blog.hash-of-codes.com/how-to-safestrap/
Related
Ok so here is my situation. I took the OTA to NB1(4.4.2) then I downgraded back to MK2 so I could have root access. Then I reinstalled NB1 stock rom. Now I have root access with stock 4.4.2 on my i337 GS4. Now what I'm trying to do is install clockwork mod recovery or TWRP or any other recovery other than safestrap but I'm not able too or cannot find a way. Has any one had this issue I'm new to this and I am trying to run google edition Roms or customer roms. Also with safestrap(3.71) some roms are enabled but once phone reboots it stay on black screen. Any help or advice is appreciated thank you.:silly:
marvelAVENGER said:
Ok so here is my situation. I took the OTA to NB1(4.4.2) then I downgraded back to MK2 so I could have root access. Then I reinstalled NB1 stock rom. Now I have root access with stock 4.4.2 on my i337 GS4. Now what I'm trying to do is install clockwork mod recovery or TWRP or any other recovery other than safestrap but I'm not able too or cannot find a way. Has any one had this issue I'm new to this and I am trying to run google edition Roms or customer roms. Also with safestrap(3.71) some roms are enabled but once phone reboots it stay on black screen. Any help or advice is appreciated thank you.:silly:
Click to expand...
Click to collapse
You cant install any other recovery besides ss, since our bootloader is locked. You also have not been able to run google edition roms since mf3. You can now only run touchwiz roms.
Kamaole said:
You cant install any other recovery besides ss, since our bootloader is locked. You also have not been able to run google edition roms since mf3. You can now only run touchwiz roms.
Click to expand...
Click to collapse
Got it so if I get my boot loader unlocked I'll be able to run other recoveries and roms?
marvelAVENGER said:
Got it so if I get my boot loader unlocked I'll be able to run other recoveries and roms?
Click to expand...
Click to collapse
At this time you cannot unlock your bootloader. As far as I know, @Hashcode is still trying to get Kexec working with safestrap using jeboo's bypasslkm exploit to load unsigned modules. If he gets that working, we will be able to basically put any kernel we want over the stock kernel. I think ran into trouble with flushing the cache.
Kamaole said:
At this time you cannot unlock your bootloader. As far as I know, @Hashcode is still trying to get Kexec working with safestrap using jeboo's bypasslkm exploit to load unsigned modules. If he gets that working, we will be able to basically put any kernel we want over the stock kernel. I think ran into trouble with flushing the cache.
Click to expand...
Click to collapse
I'll keep an eye out for that thanks.
TLDR: Need KitKat bootloader. Can it be installed on a rooted, unlocked device?
I am using CM11 on my phone (Droid Razr M/XT-907). When I try to install cyanogenmod updates using the built-in function, the installation always fails due to my bootloader being outdated. Apparently I still have the bootloader from jelly bean and I need the KitKat bootloader version. Now that my phone is unlocked and has a custom OS and recovery, is there any way to obtain the newest bootloader version and get it installed on my phone?
The only way I know is to rsd to kitkat stock then install. My other devices we just installed the kernel but I haven't seen that here. You are unlocked so you are able to flash down and back up.
Sent from my XT907 using XDA Free mobile app
mmmrower said:
TLDR: Need KitKat bootloader. Can it be installed on a rooted, unlocked device?
I am using CM11 on my phone (Droid Razr M/XT-907). When I try to install cyanogenmod updates using the built-in function, the installation always fails due to my bootloader being outdated. Apparently I still have the bootloader from jelly bean and I need the KitKat bootloader version. Now that my phone is unlocked and has a custom OS and recovery, is there any way to obtain the newest bootloader version and get it installed on my phone?
Click to expand...
Click to collapse
There is this if you don't want to RSD up to KitKat other wise everything you need to update to KitKat is here courtesy of ATTACK
We cannot teach people anything; we can only help them discover it within themselves.
RSD?
mmmrower said:
RSD?
Click to expand...
Click to collapse
RSD lite is the tool used to flash the stock firmware on a Motorola device its like Odin that the Samsung device's use... Read through the XDA thread I linked in the prior post for a better understanding of the procedure
We cannot teach people anything; we can only help them discover it within themselves.
So my next question is:
Within the cyanogenmod .zip that you would normally flash to your device, there is a file called "boot.img." Is this file normally flashed to the boot partition when you install cyanogenmod?
In other words, if I manually did a "fastboot flash boot boot.img", would that replace the bootloader? Or does cyanogenmod not include bootloader data? I've been scouring the web for hours trying to find this out.
To be honest I'm not sure what flashing just the boot image would do... I don't believe it would effect the boot loader... We would have to wait on a more experienced member... Flashing the KitKat firmware doesn't take long at all and you could always back up your app date with your desired back up app
We cannot teach people anything; we can only help them discover it within themselves.
The boot.img and the boot loader are two different things. You'll need to FXZ/update to get the new BL.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
The boot.img and the boot loader are two different things. You'll need to FXZ/update to get the new BL.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I just finished flashing [what I think] is stock firmware. Now, if I update OTA, won't that upgrade me to an "unlockable" bootloader? (whatever the latest one is).
My bootloader is currently unlocked, if that means anything.
[edit] I OTA updated anyways. And I don't think it re-locked my bootloader. But now it keeps overwriting clockworkmod every time I "fastboot" clockworkmod into place. Can't seem to reboot into recovery straight from fastboot mode anymore. The power+volume up combo doesn't work. Maybe that's a sign that the bootloader's locked? I still get the motorola "Bootloader Unlocked" screen every time it boots up.
If your boot loader was already unlocked it will remain unlocked
Sent from my XT907 using XDA Free mobile app
I'm tracing it back to the root of the problem: why do you *need* to upgrade to KK BL? CM11 is also available for JB BL and as for my experience half a month ago, it's more bugfree than the KK BL version (KK BL had WiFi & GPS bugs, don't know what's the situation now).
I see you've already upgraded... So please try out latest CM11 KK BL (moto_msm8960) and see if it has WiFi, GPS or BT issues. If yes, you might wanna fall back to JB BL.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
How would I "fall back" to JB bl?
I'm currently stuck trying to get any sort of ROM installed. It seems the stock image that I flashed re-writes the recovery partition every time I flash CWM. So I can't even boot to recovery anymore. Until I get that figured out, well, we'll see lol.
Know where I could get a system.img and boot.img of ANY functional cyanogen ROM?
I got CM to install ONCE from recovery (the first time I installed it). Subsequent attempts at installing the snapshot builds failed and complained that I needed the kitkat bootloader.
[edit]And now adb doesn't even work. hahahaha
[edit]Got everything working. Seems to be pretty stable.
[edit]Back when I first installed CM, I had the JB BL and installed the KK cyanogen. I had a bug with my wifi, but it was due to me installing incorrectly. Otherwise I didn't find any issues.
Thanks for all your help everyone.
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.
Recently bought a replaced for my wife's dead s3 with a supposedly new unused non-dev s5. Arrived in perfect physical condition and CID starts with 15 but recovery screen revealed it has been OTA updated to 6.0.1 PF4. Can the bootloader be unlocked or downgraded then unlocked ?
rostar17 said:
Recently bought a replaced for my wife's dead s3 with a supposedly new unused non-dev s5. Arrived in perfect physical condition and CID starts with 15 but recovery screen revealed it has been OTA updated to 6.0.1 PF4. Can the bootloader be unlocked or downgraded then unlocked ?
Click to expand...
Click to collapse
Yes! You can unlock the bootloader. Not problem with your bootloader version. Try this:
https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
enmanuel255 said:
Yes! You can unlock the bootloader. Not problem with your bootloader version. Try this:
https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Click to expand...
Click to collapse
I saw that but isn't that just loading roms through safestrap? The bootloader itself remains locked then correct? Also won't safestrap will eat up what little storage she has on a 16g phone (couldn't find 32g).
Thanks
rostar17 said:
I saw that but isn't that just loading roms through safestrap? The bootloader itself remains locked then correct? Also won't safestrap will eat up what little storage she has on a 16g phone (couldn't find 32g).
Thanks
Click to expand...
Click to collapse
People unlock bootloaders for to boot non-native kernels, not to load/flash ROMs.
Safestrap "eats" very little space, 20 MB on /data or so. EMMC partitioning remains the same and you don't really see what's free there on /system.
It's used for unlocking process and there's no need to keep it further in the system.
bbsc said:
People unlock bootloaders for to boot non-native kernels, not to load/flash ROMs.
Safestrap "eats" very little space, 20 MB on /data or so. EMMC partitioning remains the same and you don't really see what's free there on /system.
It's used for unlocking process and there's no need to keep it further in the system.
Click to expand...
Click to collapse
Thanks for clarifying. I have used safestrap before on others phones as a work around for locked bootloader phones. There I was using the ROM slots so of course consuming memory. Does using this method restrict what you can load for kernels and ROMs vs bootloader unlocking in kitkat versions?
rostar17 said:
Thanks for clarifying. I have used safestrap before on others phones as a work around for locked bootloader phones. There I was using the ROM slots so of course consuming memory. Does using this method restrict what you can load for kernels and ROMs vs bootloader unlocking in kitkat versions?
Click to expand...
Click to collapse
ROM slots do not work for SM-G900V.
Everything is simple:
- If your phone has CID15 (check with EMMC Brickbug Check from the Market) then you can unlock it's bootloader and use non-native kernels (say, LOS kernel, TWRP, custom kernels and ROMs that require custom non-Verizon kernels).
- If your phone has CID11 then you cannot unlock the bootloader and you're restricted to native Verizon-Samsung kernels for any Android version. This means no root on 6.0.1 also because you need a modified kernel for to have root on 6.0.1 and above.
That method restricts nothing itself. It's only a modern method of installing a custom ROM and unlocking the bootloader, if possible.
The files like bla-bla-bla-Bootloader_Unlock_AIO.zip usually contain a tool for bootloader unlocking. It's convenient to apply them from Safestrap Recovery.
It's also convenient to flash custom ROMs from Safestrap Recovery.
Safestrup Recovery itself needs root to be installed.
Root itself may be easily gained on Combination 4.4 ROM for any CID.
bbsc said:
ROM slots do not work for SM-G900V.
Everything is simple:
- If your phone has CID15 (check with EMMC Brickbug Check from the Market) then you can unlock it's bootloader and use non-native kernels (say, LOS kernel, TWRP, custom kernels and ROMs that require custom non-Verizon kernels).
- If your phone has CID11 then you cannot unlock the bootloader and you're restricted to native Verizon-Samsung kernels for any Android version. This means no root on 6.0.1 also because you need a modified kernel for to have root on 6.0.1 and above.
That method restricts nothing itself. It's only a modern method of installing a custom ROM and unlocking the bootloader, if possible.
The files like bla-bla-bla-Bootloader_Unlock_AIO.zip usually contain a tool for bootloader unlocking. It's convenient to apply them from Safestrap Recovery.
It's also convenient to flash custom ROMs from Safestrap Recovery.
Safestrup Recovery itself needs root to be installed.
Root itself may be easily gained on Combination 4.4 ROM for any CID.
Click to expand...
Click to collapse
Thanks again for the help. At present there are several posts about unlocking bootloaders and rooting but they are not all up to date and trying to decypher what applies to later verizon (PF4) OTA MM firmware was confusing. I guess I will keep the phone since I can unlock bootloader and load what I want with root. Looking for the unicorn phone (factory new untouched) is elusive to say the least.
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.