Related
INSTRUCTIONS:
Download the 90.78ch Boot Loader from here. Boot Loaders lower than the version you currently have (eg. attempting to flash 90.73 on a bootloader 90.78 milestone CAN brick, and I think you can flash back to the stock 90.78 bootloader after flashing this one, untested). Unpack to safe location.
Install RSD Lite & Drivers (mentioned in another thread). Choose the SBF with 90.78ch boot loader in it in the RSD Lite window.
Reboot in bootloader mode, via Holding Up while turning milestone on (you'll get screen like BOOT LOADER 90.78ch READY TO PROGRAM, BLAH BLAH).
Start the update from RSD Lite. When it reboots the phone, hold up on the Dpad to re-enter boot loader mode, or else it will succeed (and you won't get a brick) but RSD Lite will say fail. To exit boot loader, press Power for about three seconds, and then turn it back on again.
DO NOT REMOVE USB CABLE WHILE THE SCREEN SAYS "SW UPDATE IN PROGRESS". IF ON A LAPTOP, CONNECT CHARGER. IF THE BOOT LOADER FAILS TO FLASH, YOU WILL HAVE A BRICK.
If all goes well, Boot loader should say 90.78ch. You're running the latest bootloader, originally from the XT702 (Sholes Tablet?)
WARNINGS:
I am not responsible if you blow up your Milestone or it randomly starts swearing at you for flashing a dodgy boot loader or your girlfriend hates you after flashing the boot loader. You are on your own. Read the instructions carefully. I also will not offer support if you just say "Doesn't work". Tell me what didn't work eg. "Got stuck at 53% upload, then said fail" or "BSOD while Flashing!"
Enjoy the latest boot loader.
Is there any reason to flash this "new" bootloader?
Is this one not locked?
I am not sure I get it.
It's still locked, but it's the same one that the XT702 device uses. That would mean if the bootloader on that device is hacked, the hack could be useful for us people with Bootloader 90.78ch installed.
EDIT: I have a hunch that the "ch" part just means a Chinese version of the boot loader, which might mean some slight code mods...
nice work, thank's!
Coburn64 said:
EDIT: I have a hunch that the "ch" part just means a Chinese version of the boot loader, which might mean some slight code mods...
Click to expand...
Click to collapse
Actually "ch" is the country code for switzerland
what are the benefits?
Coburn, I see the logic in what you are doing. It is a pretty good idea.
However, I believe that the XT702 is not exactly a popular phone, thus the chances of its booloader being hacked are even fewer.
By contrast, if you were able to flash a Droid X bootloader on our milestone....now THAT would be something.
However, I am assuming that is not possible due to the fact it is a CDMA [Verizon] phone.
Absolutely no reason to do that for now,only if you want to see how easy is to brick a perfectly good device.i seriously doubt that ANY bootloader wiil be totaly bypassed (unlock is out of the question).
Sent from my Milestone
I did it!
yesterday, I loaded the new bootloader to my device without any issues, I came from 90.73, the phone since yesterday it´s working normally.
now that´s make me wonder if it´s possible modify the droid´s bootloader and try to port it to the Milestone, of course I don´t know which are the current methods used to try to hack the Milestone´s bootloader or even if someone tried that before, but thinking about the fact that both devices are very similars in hardware, I think it could be done!
if my last comment it´s outdated please forget it!
PS: sorry for my bad English!
So I suppose there is more chance the latest bootloader from motorola would be hacked then an older version ? takin into consideration its not possible to downgrade atm one could only think how great of an idea it would be to install this ,<insert sarcasm>
Coburn64 said:
That would mean if the bootloader on that device is hacked, the hack could be useful for us people with Bootloader 90.78ch installed.
Click to expand...
Click to collapse
long time that no talk about this project..
I have a question, this process only will work with the hack of liberation the Milestone XT702 or to with a bootloader of XT702 for install in Motola Milestone?
if exist a ROM of XT702 able make swape will serve for Milestone?
I made some boot logos,should used to unlocked motox.
Tips:Locked Devices like Verizon's motox can't Use it!!!
Use RSD Lite flash it.
China Dragon HongKong Boot LOGO:
http://forum.xda-developers.com/attachment.php?attachmentid=2578202&stc=1&d=1392347277
Turkey Boot LOGO:
http://forum.xda-developers.com/attachment.php?attachmentid=2578203&stc=1&d=1392347277
Valentine's day roses Boot LOGO:
http://forum.xda-developers.com/attachment.php?attachmentid=2578204&stc=1&d=1392347515
:laugh:
Welcome to download!!!
thanks for your work, but some screenshots would be nice..,,
Dusty tears said:
I made some boot logos,should used to unlocked motox.
Tips:Locked Devices like Verizon's motox can't Use it!!!
Use RSD Lite flash it.
Click to expand...
Click to collapse
I didn't download your files, but from the way you posted, it appears these are LOGO.BIN files for use on a Moto X with an UNLOCKED BOOTLOADER, rather than the CLOGO.BMP for use by those who have a locked bootloader and never unlocked/relocked it? Is that correct?
BTW, RSDlite is really meant to flash an entire rom/sbf/fxz file, so its probably easier to use FASTBOOT to flash the logo only..
for unlocked bootloader phone, or one that has been unlocked and relocked, it would be...
Code:
adb reboot bootloader
fastboot flash logo name.bin
(where name.bin is the name of your new logo file)
and these steps should be performed with phone normally booted, and USB Debugging enabled.
The first command mitigates the need to power off and try and mess with buttons while powering on
On a side note... For those interested in making your own LOGO.BIN...
There is already a thread discussing how to do that -> Moto X Boot Logos which includes a script by carock -> <HERE> to help make it easier. NOTE1: you might want to see THIS POST with tips on formatting the graphics you want to use with the script. NOTE2: The LOGO.BIN format was different between 4.2.2 and 4.4. This script does work with KitKat 4.4. I have not looked to see if the KitKat 4.4.2 logo.bin has changed or not.
For my contribution of sharing...
I took the 24 CLOGO's from -> HERE, converted them to logo.bin's using carock's script. And did one or two others I found that I liked. I put them in -> http://mark.cdmaforums.com/X-STUFF/X-LogoBins.zip (when you un-zip it, there will be two folders, one containing the original graphics so you can see them and choose without flashing, and one with the logo.bin's. NOTE: the originals can be used by those with locked booloaders looking to flash their clogo.bmp). These flash fine on my Verizon Moto X Developer Edition with unlocked bootloader and KitKat 4.4.
KidJoe said:
I took the 24 CLOGO's from -> HERE, converted them to logo.bin's using carock's script. And did one or two others I found that I liked. I put them in -> http://mark.cdmaforums.com/X-STUFF/X-LogoBins.zip (when you un-zip it, there will be two folders, one containing the original graphics so you can see them and choose without flashing, and one with the logo.bin's. NOTE: the originals can be used by those with locked booloaders looking to flash their clogo.bmp). These flash fine on my Verizon Moto X Developer Edition with unlocked bootloader and KitKat 4.4.
Click to expand...
Click to collapse
Thanks, man,I understand!!!
I'm a new convert from Moto phones and I'm loving this Pixel!
The one thing I miss is that on the Moto phones, once the bootloader is unlocked, there is a way to override the logo partition in the phone by customizing the images in the "logo" partition (logo.bin). That image would hide the ugly "bootloader unlocked" screens that show up on startup. Is there a way to do this on the Pixel series? I can't even seem to find the logo partition to get started with...
I was wondering about this myself. I also just converted from Moto to Pixel and would like to get rid of the bootloader unlocked screen.
BTW, the Pixel is the easiest to root phone that I've ever had.
Hello guys.
I unlocked the bootloader but I can't update the Motorola One Vision anymore. Is there any way to reverse the bootloader? or can I update without reverting?
obs: I saw a tutorial to revert the bootloader with the stock rom and using a code to "restore" the OEM of the cell phone. Does anyone know if it works?
I'm a bit of a layman with that.
obs2: I'm sorry for the text it was translated by Google Translate.
If you just unlock by code provided from Motorola and just that , you simply lock bootloader from settings - developer option - lock OEM .
That's it . I've done myself some time ago . I received after , several OTA updates .
but I don't have TWRP installed on my phone, do I have to install it? because without it, from what I saw, I can't pull the OEM Deblocking arrow to the side.
After further testing (well actually I mean bricking my device a few times) it turned out that rebranding is not needed for the update from mm to nougat, although your device will boot into a "test" system instead (This is likely due to the vendor information being mismatched). Your p9 would still work with HWOTA7.
The original post has not been changed.
I got hold of an EVA-AL10 model from China. However it was still stuck on emui 4.1 Android 6.
Spoiler
After some research, I found out that Chinese internet was ridiculously unreliable and riddled with useless information, and the fact that most Chinese are tech-illiterate does not help either. Then I turned to good old XDA and found out a few (pretty obsolete posts) that had similar problems and got them solved. However, they all (unsurprisingly) involved the European model (EVA-L0X), which had different firmware.
I then got in contact with a former Chinese colleague. With his help, I managed to send an email to Huawei China and get a representative. After giving him his phone number and all information in the about section of the phone (IMEI and stuff) they took an entire day only to phone him back saying he needs to go to a repair shop. They told him that the oldest version of EMUI available for update was for emui 8 (Android 8) so that was a dead end.
After more searching, I stumbled across a thread about rebranding an European model into the one I got to get to, ironically, emui 8.
Spoiler
According to a Chinese nationalist blogger, it turns out that Huawei severely displeased our international community due to halting the provision of bootloader unlock codes, and they dicided to get us back by not updating us to emui 8. Although there might be more reasons than that, the fact is clear that they had to change their model.
Luckily, XDA is the perfect platform to find help.
Spoiler
Although the in-house search engine is relatively good at dealing with the Chinese e-thefts which take the hard work of this community and sell it shamelessly in China,
a fair amount of time was taken to Google search, however it was definitely worth the effort. Soon, I drew out a simple flowchart to update my p9:
1. Unlock bootloader
2. Rebrand the phone to European model
3. Update to Android 7
4. Rebrand back
5. update to Android 8
(6. Do cool stuff)
Unlocking the bootloader is now a hard part for some. (make sure you have backed up your data on the phone because it will do a factory reset)
Spoiler
While unlocking services here are mostly genuine, it is 75% scam in China. My friend maaged to get my bootloader unlocked from a (crazy) shopping site in China named Taobao, which is well-known for selling fake sneakers and even Uranium. It only costed me two dollars.
Make sure to keep the unlock code. You need it later. If you forgot your unlock code but have it unlocked, no worriess. You can root your phone (I used good old supersu) follow this guide (the commands are the important part, I personally have not verified this method though)
You can also try this tool:
Huawei Nova 2 Plus Bootloader Unlock (Solution)
Hello Developers! I have found an easy way to unlock the bootloader of our Huawei Nova 2 Plus. No need to use Testpoint or pay for software to unlock. it is an Python Script which would brute force the code through the IMEI number you have...
forum.xda-developers.com
However it was intended for another device so your luck may vary.
After that, I used SRKtool to rebrand the phone, although the software of the phone itself has not changed. Keep in mind after the rebrand not to reboot into the system, as it will cause an error. (see below post) If you do manage to get into the system unfortunately, it will ask you for your password (bootloader unlock code) Do not enter the code, shut down your phone and get into fastboot by holding down power and volume down WHILE cable is attached to computer.
After trying hard to get into TWRP, I used this guide to boot into it (turns out I was not quick enough)
I then used this file to update it to the European android 7, which worked perfectly. You do need to enter the unlock code again though, and you need an SDcard or an USB disk that supports OTG(so the device can recognise it in twrp).
After that, you can follow this guide to get it to Android 7 Chinese version(399). I got my friend to set up a vpn connecting to China, where the Chinese system recognized that it could update to android 8. If yours does not, follow the guide to update it to android 8. It already contains the firmware, so do not download other firmware (unless you prefer). If you already got the firmware, use the androidfilehost link he provided and find in the older versions V1.1, which did not have the firmware to save time (and possibly bandwidth)
You will have your bootloader locked at this stage. If you want to stay on the Chinese firmware (Which has a lot of bloatware and needs you to manually sideload playstore apk) do not unlock it. If you do want to go further and install a custom treble GSI, go ahead and unlock the bootloader, and follow the instructions,
Error after force rebranding location with SRKtool:
After using SRKtool to rebrand, your system boot warning will turn from unlocked to unverified (text color orange to red)
If you continue to boot, it will go to a screen where you have to enter a password (the bootloader unlock code) you should not enter the code.
If you still proceed to enter the code, you will be "greeted" with a message telling you that the data on your phone is corrupt and you have to factory reset. after you boot into the OS, you will see this "mix" of the classic nexus 2012 style wallpaper with some android app icons (such as settings) in the aosp style, with everything else that are Huawei-branded seen in 2012-style icons. This has to do with a theme engine bug.
In the about page you might also notice that the system version has been slightly changed. the "al10" part has been deleted but the c00 still remains. The page where the CE and FCC stuff are displayed (forgot precise wording) now lists the phone as "eva-l09"
Go into settings and developer options as usual. You should now see that there is an oem unlock opion that has been toggled off. turn it on.
Reboot into fastboot again. You would see that most commands you would usually use such as flash recovery and erase would not work anymore(returns command not allowed) This has to do with the bootloader locked although it technically unlocked. Unlock it as you would normally do. If this does not work, reboot and turn off oem unlock, go to fastboot and enter the unlock command (it would obviously not work but it registers that wants to be unlocked), reboot and turn on oem unlock again and reboot into fastboot, then you should unlock the bootloader and flash recovery again.