Related
I have a droid razr m which i rooted using motochopper.
I berly found out that motochopper roots your phone without unlocking the bootloader.
The root was successful, and I want to install a custom rom but i know that i have to have the bootloader unlocked first. so any help if i should Unroot the phone first and then unlock the bootloader, or just try to install the rom
I used this utility to get the job done. Its a rather large download, but it works really well.
http://forum.xda-developers.com/showthread.php?t=2249773
You could also try simply getting the unlocking tool from this thread and follow the directions. The larger download in the thread I first linked uses the exact same method, but it has a ton of other tools and lets you install cwm or twrp as well.
Also, you could try to use safestrap, which allows you to install a ROM on a locked bootloader.
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
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.
its 3 days since i am trying to unlock my rooted razr M with motopocalypse but when i get into fastboot it will say that the device in still locked code 00
2 question s:
1) is there a way to unlock my bootloader ?
2) is there a way to flash my moto with bliss or any other costum rom without unlocking the bootloader ,if yes how
sewershark said:
its 3 days since i am trying to unlock my rooted razr M with motopocalypse but when i get into fastboot it will say that the device in still locked code 00
2 question s:
1) is there a way to unlock my bootloader ?
2) is there a way to flash my moto with bliss or any other costum rom without unlocking the bootloader ,if yes how
Click to expand...
Click to collapse
not enough information provided... What ROM are you on presently? Exact build number?
rahimali said:
not enough information provided... What ROM are you on presently? Exact build number?
Click to expand...
Click to collapse
the verizon one (stock) jb 4.1.2
9.8.1Q-66
here is a screenshot of motopocalypse message.as it can be seen the bootloader stays locked
sorry, personally I have no idea if the bootloader on that particular JB build is unlockable, maybe one of the senior/more experienced members can shed light on this.
BUT the bootloader is unlockable on the stock 182 / 183.46.10 KitKat builds. for further information, look here
can i use safestrap to install others costum Roms ?
sewershark said:
can i use safestrap to install others costum Roms ?
Click to expand...
Click to collapse
Simply a big NO.
Just do the upgrade to .10 (not .15!!!) and then unlock your bootloader, it's worth it.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
182.46.10 or 183.46.10 Kit Kat ROM from sbf-developers.com is completely unlockable. I have unlocked my phone from this ROM version.
I'm pretty sure .66 was the unlockable JB version. They locked up on .78, which was the next OTA. Are you granting root access to Motopocalypse when the pop-up shows up on your phone?
Sent from my HTC6525LVW using Tapatalk
Now i have 183.46.10.xt907.Verizon.en.Us
what should i exactly do ,with witch program/app at witch link am afraid to get stuck again in fastboot mode like before.....
sewershark said:
Now i have 183.46.10.xt907.Verizon.en.Us
what should i exactly do ,with witch program/app at witch link am afraid to get stuck again in fastboot mode like before.....
Click to expand...
Click to collapse
install supersu from the play store but don't open it yet.
install towelroot, ensure you have internet connectivity, then open it and use it to get root
use motocalypse (i've had better luck with the apk version than the adb version) to unlock your bootloader
profit
everything is detailed in the @ATTACK thread here. Do try and read it thoroughly before you proceed.
Now, grab Motopocalypse APK and Towelroot. Root it with Towelroot (and install SuperSU from Play Store), then launch the Motopocalypse app, grant it root permission, and run the unlocking procedure. After this, reboot. If you go to Fastboot menu, you will see Status 3 in the Fastboot information screen. Status 3 = unlocked bootloader. Also, another way to know you're unlocked is the scary warning in black background and teal fonts mentioning that you have unlocked the bootloader, before the operating system boots.
EDITED: I suppose I am a tad slow, so I'm Ninja'd.
Dr. Mario said:
Now, grab Motopocalypse APK and Towelroot. Root it with Towelroot (and install SuperSU from Play Store), then launch the Motopocalypse app, grant it root permission, and run the unlocking procedure. After this, reboot. If you go to Fastboot menu, you will see Status 3 in the Fastboot information screen. Status 3 = unlocked bootloader. Also, another way to know you're unlocked is the scary warning in black background and teal fonts mentioning that you have unlocked the bootloader, before the operating system boots.
EDITED: I suppose I am a tad slow, so I'm Ninja'd.
Click to expand...
Click to collapse
Ninja'd, LOL.
Sent from my HTC6525LVW using Tapatalk
done what you said ....Not working
here is a video of what i did in case somebody have the patience to see what i did wrong...as you can see in the end code is still zero on fastboot and remains locked
https://www.youtube.com/watch?v=1YA-j7w_mEw
sewershark said:
done what you said ....Not working
here is a video of what i did in case somebody have the patience to see what i did wrong...as you can see in the end code is still zero on fastboot and remains locked
https://www.youtube.com/watch?v=1YA-j7w_mEw
Click to expand...
Click to collapse
What's the date on the fastboot screen? You have root access, I'm not sure why it's not working.
Sent from my HTC6525LVW using Tapatalk
Gettin' curiouser and curiouser. Check the Fastboot date and write it down.
yes as shown in the begining of the video of youtube that i linked i have root access
ap fastboot flash mode
19.9b(*) (sha-61146a2,2014-05-02 00:54:39)
any hops to unlock it ?
thanks
Huh? I remembered that Fastboot AP date - I did unlock my phone on that version no problem. Odd. Probably you may try the Motopocalypse USB utility. I will look for the link.
Try this: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
sewershark said:
the verizon one (stock) jb 4.1.2
9.8.1Q-66
Click to expand...
Click to collapse
did you try this: http://forum.xda-developers.com/showthread.php?t=2249773
hugh a, he updated to Kit Kat.
This METHOD was developed ONLY for an UNLOCKED Motorola Droid Razr Maxx HD XT926m phone that is already updated to the last version of KitKat 4.4.2 (System version "183.46.15.XT926.Verizon.en.US").
IF YOU HAVE AN LOCKED BOOTLOADER AND TRY THIS METHOD IT WILL BE ONLY YOUR RESPONSABILITY IF YOU DAMAGE YOUR PHONE !!!
My Motorola XT926m had an UNLOCKED BOOTLOADER (ICS 4.0.4) and I flashed via RSD Lite the last stock firmware, "183.46.15"... After that, I was, of course, unhappy, because I read on different forums that this firmware version didn't support root... I tried to download the Hydrogen Peroxide xt926 application that others users recommended here on XDA forum, without success.
But now, after I applied this method, my phone is again rooted... Enjoy the steps, but be carefull, it was developed for XT926 phones with UNLOCKED BOOTLOADER!
1. Download the files "VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml" and "VZW_XT926_4.4.2-KDA20.62-15.1_CFC_1FF.xml" from the Motorola firmware site: "motofirmware.com/files/file/"...
2. Unpack the files...
3. Substitute/replace the "gpt", "tz" files (FROM the folder with "15.1" version TO the folder with "10.1" version)... You should replace all the files that "RSD Lite" will tell you that don't fit when you try to flash the new stock firmware. You will obtain a MODIFIED version of "183.46.10" stock KitKAt 4.4.2 firmware!!!
4. Flash this MODIFIED "10.1" firmware with "RSD Lite v6.1.5 Multi-Flash" (without using Rsd Script Generator.jar), but don't forget to remove the first two 'getvar' lines in the xml file.
5. Download and install the "Towel Root.apk" and root the phone...
6. Now your phone should be ROOTED.
What to do NEXT:
7.Download from the Play Store and install "Superuser.apk" made by ClockWordMode and after reboot the application will ask you to update SU binary. In my case, the SU binary didn't support an online update and I installed the "Superuser.zip" file downloaded from the ClockWorkMode site, via recovery method, in order to gain this update (you can do this as well, if you already have a TWRP or CWM recovery installed on your phone). With the other version of superuser, like "SuperSU.apk" or "Superuser.apk" ("eu.chainfire.supersu-2.apk", the last version, 5.6mb, for example) you will need to follow the same steps...
8. Using "Total Commander.apk", you can go to "File System root"/"Etc"/"installrecovery.sh", and finally rename this last file... Or you can use "ES3 File Explorer.apk" in order to rename the same "installrecovery.sh" file in "Device"/"Etc" folder (choose, for example, the name "installrecovery.shbak")...
9. Flash with "Flashify.apk" (downloaded form PLay Store) a new "recovery img.": "TWRP.img" (2.8.3.0) or "CWM.img" (6.0.4.8) for KitKat... You can find them on "rootjunkysdl.com/?device=Droid%20Razr%20HD&folder=Firmware"...
10. If you flashed "TWPR recovery.img" you will need to install "Stericson.busybox-1.apk" (from Play Store...), because TWRP works with this busy box... (You could install "TWRP.apk" as well, but you must be careful, because you will need to be able to boot into Recovery mode directly from your phone (with the combination key), not from this app... Many times, the phone is able to boot into recovery mode from TWRP application, but not from the bootloader... That's why it is better to uninstall TWRP application if you have this problem). If you flashed a "CWM.img" you can install "RomManager.apk".
11.Now it is the time to backup your system to SD card!
That's it. My phone was unlocked, and I didn't have any issue following all this steps... If you're locked don't try it.
But.. If you're locked you could instead use an application named 'Safestrap' for some purposes (read more here on XDA forum please), because is destinated for the phones with locked bootloader...
Hi ,
Since this is a guide it does not belong to XDA Assist
Please Read The Purpose of XDA Assist
Please Standby when Moderators Move the Thread To Your Device Specific Forum
RAZR HD General
jackeagle said:
Hi ,
Since this is a guide it does not belong to XDA Assist
Please Read The Purpose of XDA Assist
Please Standby when Moderators Move the Thread To Your Device Specific Forum
RAZR HD General
Click to expand...
Click to collapse
THANKS!
I know you took a lot of time to write this up, but there is a downgrade method posted on here already. Also, there is no need to rename recovery.sh. All you need to do after flashing recovery is power off the phone and immediately boot straight back into recovery so the install script completes.
To answer your question, no, you can't unlock .15.
RikRong said:
I know you took a lot of time to write this up, but there is a downgrade method posted on here already. Also, there is no need to rename recovery.sh. All you need to do after flashing recovery is power off the phone and immediately boot straight back into recovery so the install script completes.
To answer your question, no, you can't unlock .15.
Click to expand...
Click to collapse
Thank you, I wasn't able to find another downgrade method, could you give me the link, please?
http://forum.xda-developers.com/showthread.php?t=2789743
But... to flash CWM or TWRP for update the binaries, you need to be bootloader unlocked... to flash a custom recovery...
joel_sinbad said:
But... to flash CWM or TWRP for update the binaries, you need to be bootloader unlocked... to flash a custom recovery...
Click to expand...
Click to collapse
Correct. That's why this method is flawed and probably should be pulled before someone bricks their phone.
RikRong said:
Correct. That's why this method is flawed and probably should be pulled before someone bricks their phone.
Click to expand...
Click to collapse
Yeah, unfortunately this post makes no sense, I mean, if you accidently flash the gpt.bin, you're screwed... and so many risks, plus, you can't flash custom recovery, and you can maybe downgrade the system and boot, but you still can't downgrade the bootloader...
joel_sinbad said:
Yeah, unfortunately this post makes no sense, I mean, if you accidently flash the gpt.bin, you're screwed... and so many risks, plus, you can't flash custom recovery, and you can maybe downgrade the system and boot, but you still can't downgrade the bootloader...
Click to expand...
Click to collapse
This method is for an XT926 with UNLOCKED BOOTLOADER, with the last 183.46.15 update and the root access lost. I only described the steps that I already done with my phone. My Maxx HD is working and has root access again... I flashed custom recovery too (TWRP 2.8.3.0), I haven't any other problem.
RikRong said:
http://forum.xda-developers.com/showthread.php?t=2789743
Click to expand...
Click to collapse
Thank you, unfortunately is not working for the xt 926 phone that already took the last 183.46.15 update:
"..........************WARNING*************
this guide only works completely if you did NOT take the 183.46.15 update rolling out around 9/9/14 .............".
Until now I don't have any other option, I'm forced to preserve the method that I mentioned in my thread.
ciprianv. said:
Thank you, unfortunately is not working for the xt 926 phone that already took the last 183.46.15 update:
"..........************WARNING*************
this guide only works completely if you did NOT take the 183.46.15 update rolling out around 9/9/14 .............".
Until now I don't have any other option, I'm forced to preserve the method that I mentioned in my thread.
Click to expand...
Click to collapse
The piece you are referring to that doesn't work on .15 is the unlock and root. The downgrade should work on an unlocked phone.
That aside, your steps are very confusing and could easily cause a locked user to brick their phone. Please clarify or I will continue reporting this thread until it gets removed.
RikRong said:
The piece you are referring to that doesn't work on .15 is the unlock and root. The downgrade should work on an unlocked phone.
That aside, your steps are very confusing and could easily cause a locked user to brick their phone. Please clarify or I will continue reporting this thread until it gets removed.
Click to expand...
Click to collapse
I just edited the post. I clearly specified that this methid is ONLY FOR UNLOCKED BOOTLOADERS (XT926M).
ciprianv. said:
I just edited the post. I clearly specified that this methid is ONLY FOR UNLOCKED BOOTLOADERS (XT926M).
Click to expand...
Click to collapse
Thanks for doing that, I just want to make sure no one messes up their phone.